I am extremely happy to announce a significant set of updates to Anypoint Platform for APIs that were introduced this month. These updates will make it easier for API owners and administrators to publish their APIs in a way that is sure to further their successful adoption. The sections below describe the core new capabilities introduced in this release.
Instant management through automatic deployment
The management of APIs with Anypoint Platform consists of the deployment of a proxy application to an API gateway runtime. The platform makes it easy to generate such proxies through a simple configuration wizard. Since generated proxies are simply Mule applications themselves, this allows API platform users to extend them through the rich capabilities offered by Anypoint Studio and Mule integration components.
This simple little button is quite powerful: When used, we automatically provision an API gateway runtime on the fly in CloudHub for you, then deploy the proxy to it. Once the deployment is done, your API is automatically manageable through the API platform, with the added benefit that you will be able to dig into the operational management details of the proxy’s deployment through a simple click that navigates to the CloudHub management screen for that window.
New and improved portal publishing
The portal publishing capabilities of Anypoint Platform allow users to go from an API that has no documentation, to one one that has a delightful landing page with markdown and HTML based documentation, an interactive RAML based API console, and API Notebook content that shows application developers how easily an API can be used. In this release, the API portal publishing UI of the platform has been significantly enriched with simplified draft editing and publishing, the ability to publish a set of pages in bulk, and an easier way to preview portal content.
Refreshed RAML console
An updated RAML console that uses the paradigm of a file cabinet to browse through the resources and methods of an API. The console also provides a clear separation of the documentation content of a RAML specification versus the “try-it” capabilities that allow for users to make actual calls to an API.