About API Manager (Nov 2017)

API Manager is a component of Anypoint Platform for managing APIs. As an Anypoint Platform user, you might be familiar with environments in the context of deploying APIs. In the Nov 2017 API Manager, a tight integration of Anypoint Platform components extends the use of environments in Runtime Manager to API management. The support for environments in strategic components of Anypoint Platform eliminates the need to construct version names to reflect an environment. Restricting access to and managing environments is also simplified. Permissions to access APIs are environment-based.

In the Nov 2017 API Manager, 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 auto-discovery scheme, API Manager can track the API throughout the life cycle as you modify, version, deploy, govern, and publish it. The Nov 2017 API Manager 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 auto-discovery 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 for REST APIs

    Provide the REST API Markup Language source, which you can write using Design Center.

  • HTTP for non-RAML REST APIs

    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.

The API dashboard shows key information about a deployed API instance:

dashboard legend

Below the auto-discovery credentials, analytics about the deployed API appear:

analytics request

In this topic: