mulesoft
8117  Reviews star_rate star_rate star_rate star_rate star_half

Anypoint Platform Development: Production-Ready Integrations

Use integration patterns to address challenges of distributed communication, and gain skills to become a MuleSoft Certified Developer - Level 2. Skills Gained Invoke REST APIs and SOAP web services...

Read More
$3,600 USD
Course Code DEX670
Duration 4 days
Available Formats Classroom, Virtual

Use integration patterns to address challenges of distributed communication, and gain skills to become a MuleSoft Certified Developer - Level 2.

Skills Gained

  • Invoke REST APIs and SOAP web services using various client components taking into consideration the non-functional properties of API invocations.
  • Pass messages asynchronously reliably between Mule flows and Mule applications.
  • Use various modules and techniques to implement message validation across Mule flows and Mule applications.
  • Apply essential Enterprise Integration Patterns to orchestrate multiple Mule applications and API invocations.
  • Use various techniques and Anypoint Platform components to store and manage state in an application network to increase performance and resilience.
  • Identify and extract reusable Mule application code into different Mule runtime extensions.

Who Can Benefit

This course is for software developers who have mastered the fundamentals of creating Mule applications with Anypoint Studio™ and Anypoint Platform™ and now want to learn the skills and best practices to build production-ready integrations — applications that apply essential integration patterns to take on the production challenges of distributed communication. This course together with the the Anypoint Platform Development: Production-Ready Development Practices course prepares you to take the MuleSoft Certified Developer - Level 2 exam. If you complete both courses and have a current MuleSoft Certified Developer - Level 1 certification, you will automatically receive two exam attempts.

Prerequisites

  • Experience developing Mule 4 applications as demonstrated by one of the following: A current MuleSoft Certified Developer - Level 1 certification, Completion of the Anypoint Platform Development: Fundamentals course, or Completion of the Anypoint Platform Development: Mule 4 for Mule 3 Users course
  • Experience using Maven to build Mule 4 applications
  • Note: If you do not have Mule Maven experience, you should first complete the Anypoint Platform Development: Production-Ready Development Practices course.

Course Details

Setup Requirements

  • A computer with: At least 8-16 GB RAM (16 highly recommended), 2GHz CPU, and 10GB available storage and a minimum screen resolution of 1024x768
  • Internet access to ports 80 and 443 (with > 5Mbps download and > 2Mbps upload)
  • The latest version of Chrome, Safari, Firefox, or Edge
  • An Anypoint Platform account
  • OpenJDK 8 (not 11 or a later version)
  • Anypoint Studio 7.14 or later with embedded Mule 4 runtime
  • Advanced REST Client 16.0.1 or later (or any other REST client application)
  • Apache Maven 3.8.6 or later

Course Outline

Invoking web APIs and services

  • Invoke HTTP APIs using the HTTP connector observing the non-functional properties of API invocations
  • Invoke HTTP APIs with an API specification using REST connectors
  • Improve the non-functional properties of API invocations with REST connectors
  • Enable an API client for OAuth 2.0 to enforce API client authentication
  • Invoke a SOAP web service over HTTPS with mutual authentication
  • Implement an HTTP callback

Passing messages asynchronously

  • Publish messages to a VM queue
  • Listen for messages in a VM queue
  • Publish messages to an Anypoint MQ exchange
  • Subscribe to messages in an Anypoint MQ queue

Validating messages

  • Assert flow pre/post conditions and invariants
  • Validate XML messages
  • Validate JSON messages

Orchestrating integration functionality

  • Parallelize integration logic with the Scatter-Gather router
  • Trace transactions across an application network using correlation IDs
  • Retry failed API invocations

Storing objects for persistence, performance, and resilience

  • Temporarily persist data in an Object Store
  • Avoid expensive operations with the Cache scope
  • Apply a caching API policy to an API implementation

Componentizing reusable integration functionality

  • Create an XML SDK component
  • Create a custom API policy
|
View Full Schedule