
Learn to configure api instances in mule gateway and flex gateway, deploy rest and soap proxy endpoints, apply policies, and monitor APIs across design, implementation, and deployment stages.
Explore the use case of a news app serving politics, sports, and cinema from multiple agencies, connected via an API and defined by API specifications for API consumers.
Import an existing RAML spec into the Anypoint design center by selecting import from file, attaching newapi.zip as NewsAPI, and completing the import to use the RAML for training.
Explore a raml-based news api specification, starting with the root raml newsapi.raml and base uri everydaynews.com, detailing json payloads and the /news and /news/{newsId} resources.
Publish your RAML API spec to exchange by setting asset version 1.0.0 and API version v1, mark as stable, then verify endpoints like /news and /news/{newsId} in exchange.
Generate mule flows from a RAML specification in Anypoint studio, including get, post, and specific news item flows, with listener and APIkit router and console flow testing.
In this video, create a Mule project named news in Anypoint Studio and generate flows by importing the NewsAPI from exchange, showcasing the API integration workflow and generated flows.
Generate and route api requests using raml-based flows in Mule 4, with the APIkit router directing get and post operations on news resources, including error handling and status responses.
Test api flows with postman against the mule runtime on port 8081, calling /api/news and /api/news/{id}, validating get, post, and error responses from the RAML spec.
Export the mule project as a deployable archive from anypoint studio and deploy news.jar to cloudhub via runtime manager in a sandbox, then test GET /api/news with Postman.
Register onPremServerA to the runtime manager, install the mule agent with the registration token and two-way SSL verification, start the server with mule.bat, and verify it runs.
Deploy the news api to onPremServerA via runtime manager by uploading the news jar. Test the API with postman using a GET request to http://localhost:8081/api/news.
Discover how the api manager and api instances enforce policies for the news api, covering out-of-the-box and custom policies to control traffic, security, caching, and logging.
Explore proxy endpoint and basic endpoint API instances, and how proxy applications route client requests to API implementations, with deployment options like Cloud Hub and on premises.
Compare basic endpoint and proxy endpoint API instances in Mule 4, explaining when to use each for Mule and non mule applications, and note the upcoming Flex Gateway.
Configure a proxy endpoint API using Mule Gateway on premises, deploy the auto-generated proxy to the onPremProxyServer, and validate the News API via Runtime Manager and Postman.
Configure an onPremises proxy endpoint using Mule 4 API manager, review NewsAPI instance status, runtime version Mule 4, v1, and deployment on onPremProxyServer with options to deprecate, export, or delete.
Demonstrates end-to-end testing of a Mule 4 API using postman with the proxy URL and an interactive API console, including sending requests to /proxy/news and exploring resource docs.
Apply default and custom policies to an API instance, and explore policy categories such as transformation, security, and troubleshooting, along with policy templates (jar and yaml) and xml/json definitions.
Explore how a policy is downloaded and injected into the onPremProxyServer's proxy app when applied to an API instance, configuring inbound and outbound headers via YAML, XML, and JSON artifacts.
Test header injection policy in Mule 4 API Manager by applying it to all methods or specific methods, verify version header v1 with Postman, and understand method and resource conditions.
Learn how the Mule gateway enforces policies via an agent authenticating with client id and secret to download policies for the correct API instance (proxy or basic endpoint).
Explore auto discovery, showing how the agent retrieves an API id from the API implementation and connects to the API manager with client id and secret to download policies.
Configure a basic endpoint on premises in Mule 4 API manager by manually enabling auto discovery and selecting NewsAPI from exchange.
Configure auto discovery by binding the newsapi-main flow to the API id on the on-premises endpoint. Deploy the news-basic-onprem app via hybrid runtime manager and configure credentials from onPremServerA's wrapper.conf.
Deploy the news-basic-cloud app to Cloud Hub using sandbox client credentials, configure authentication with client_id and client_secret, and validate the endpoint API via Postman with a get request to /api/news.
Configure a proxy endpoint API instance on Cloud Hub using a proxy application that routes to an API implementation deployed on Cloud Hub, with upstream URL and base path /proxy.
Learn how to enable and test inbound request validation for proxy endpoints on CloudHub, using strict validation to guard against invalid requests and ensure API specifications are followed.
Delete two API Manager instances - the proxy endpoint API instance and the basic endpoint API instance - in Mule 4, then remove their associated applications in Runtime Manager, leaving two API instances remaining.
Test basic authentication in mule 4 API manager by inspecting runtime logs, sending requests via postman with basic auth, and verifying the authorization header and successful response.
Configure JSON threat protection policy in Mule 4 API Manager to block inflated JSON requests by setting limits on string length, object entry names, entry count, and depth.
Learn how to grant access to an API instance by registering client applications, issuing client credentials, and enforcing SLA-based approvals via API manager, exchange, and public portal.
discover how to request access from exchange for a client application in a sandbox environment, create EveryDayNewsApp, and obtain the client ID and secret for an approved proxy endpoint contract.
Publish the NewsAPI to the public portal by making the basic endpoint API instance public, then demonstrate how users request access from the public portal.
Configure the client ID enforcement policy to use the http basic authentication header, apply the changes in API manager, and verify access with Postman using the client ID and secret.
Apply the message logging policy to log request and response messages with a dataweave expression, configure multiple logging sets, and verify logs in runtime manager and Postman tests.
Learn how header injection policy adds or overrides headers during requests and responses, configure inbound and outbound header maps, and apply version and x-total-count headers with dataweave expressions.
In this course you will learn how to configure API Instances in API Manager with Mule Gateway and Flex Gateway. You will also learn various Mulesoft Provided policies and Custom Policy.
What this course covers?
Mule Gateway : -
Configuration of API instances - Basic Endpoint and Proxy Endpoint for REST and SOAP API.
Configuration of API instances for Cloudhub and On Premises
HTTPS Proxy Endpoint
Many MuleSoft Provided Policies like -
Basic Authentication, JSON Threat Protection, Rate Limiting, Rate Limiting SLA Based
Client Id enforcement, Message Logging, Header Injection, Http Caching, JWT Validation etc
Custom Policy
(POSTMAN is used for Testing)
Flex Gateway -
Introduction to Docker
Register and Start Flex Gateway using Docker
Configuration of API Instances for HTTP and REST API
Routes
Replicas
Apply Policies
Shared Storage
Logging
Monitoring in Anypoint Platform
Monitoring using Splunk
What this course does not cover?
Many policies are covered but NOT ALL.
Installation instructions are not in scope
Creating/Updating RAML and WSDL specifications are not in scope
Explanation of REST and SOAP API concepts are not in scope.
Explanation of Integration flows are not in scope.
Explanation of Cloudhub and On Premises Mule Runtime not in scope.
Integration flows have hard coded values so no integration with database,Salesforce etc