Mule API Manager

API Manager is a component of Anypoint Platform for designing, building, managing, and publishing APIs. Anypoint Platform uses Mule as its core runtime engine.

You can use API Manager on a public cloud, such as CloudHub, a private cloud, or a hybrid.

A hybrid deployment is an API deployed on a private server but having metadata processed in the public cloud.

Sign up to use Anypoint Platform on the Internet or private cloud, or obtain credentials from your administrator. For more additional info Mule Training

If you set up your own account in Anypoint Platform, you are assigned the Organization Administrators role. In this role, you see and can open API Manager when you log into Anypoint Platform.

Alternatively, you can use the Anypoint Platform command line interface (CLI) to interact with API Manager.

The lifecycle of an API involves setup and deployment, management, and engaging users on an API Portal. To perform these tasks, you might need to obtain permissions and roles from the Anypoint Platform administrator for your organization.

The workflow, color-coding tasks as follows:

• Administrative task (orange).
• API or app developer task (blue).
• You can use the auto-discovery process to register and start a Mule app. API Manager can discover and register a Mule app deployed from Studio without user intervention.
• You can deploy an API implementation to a Mule Runtime that runs on a server, such as CloudHub in the public cloud. You can also deploy to a private cloud or hybrid.
• A hybrid deployment is an API deployed on a private server but having metadata processed in the public cloud.
• Regardless of the server location, each server belongs to an environment, such as Dev, Test, or Production.
• Servers are defined in business groups and each business group can have multiple environments.
• You publish your API on the portal and apps request access, as depicted in the following diagram. For more skills learn from Mulesoft Training

In API Manager 2.x, you can use instances of an API in multiple environments, and you can have multiple instances in the same environment. You can create one instance of an API that serves as a proxy.

You can create another to manage directly as a basic endpoint. You can apply caching policies, for example to the proxy, and throttling policies and security policies to the basic endpoint.

Through the Autodiscovery scheme, API Manager can track the API throughout the life cycle as you modify, version, deploy, govern, and publish it. API Manager 2.x is tightly integrated with the following tools:

• Design Center for creating the RAML structure of the API
• The API design capabilities of Design Center replace the Jul 2017 API Designer tool in Anypoint Platform.
• Exchange for storing and publishing API assets
• Assets are components, such as API versions, templates, and connectors owned by MuleSoft or your organization.
• Studio for implementing the API

API changes made in Studio are synchronized using Autodiscovery with the API registered in other tools, such as Design Center and API Manager.

API Manager manages APIs that reside in Exchange or imports the APIs in a ZIP file from the file system. The ZIP is an API object that you exported from API Manager. You set up the API for RAML, HTTP, or WSDL management.

• RAML/OAS for REST APIs: Provide the REST API Markup Language source, which you can write using Design Center.
• HTTP for REST APIs without a specified spec (RAML or OAS): Provide the URL of the inbound HTTP or HTTPS endpoint.
• WSDL for SOAP APIs

Provide the URL where Anypoint Platform can find Web Services Definition Language source.

After configuring the API, you can perform API management tasks, applying policies and setting up SLA tiers, assigning permissions to the API environment, versioning, viewing API analytics, and more.

To get in-depth knowledge, enroll for a live free demo on Mulesoft Online Training