Anypoint Studio January 2015 and Mule ESB 3.6 released

motif

As part of our API-led Anypoint Platform January 2015 launch, I’m pleased to announce the next version of our runtime and tooling, Mule ESB 3.6 and Anypoint Studio January 2015. This release helps users more quickly connect to and design APIs based on a new HTTP connector that adopts a design-first and resource-based approach, all with higher performance. The new release of Anypoint Studio also improves the design experience, upgrades the base Eclipse runtime, and connects to Anypoint Exchange, our expansive library for connector and example information. Finally, major updates to AMQP and our SDLC tooling have been released.

API-led approach to connectivity and design

We at MuleSoft believe strongly in great API experiences (APX) and an API-led approach to connectivity and design. To successfully adopt this approach, teams need a platform which is API-led in all aspects of the API lifecycle. To that end, we’ve gone back to the drawing board on how design and connectivity with HTTP should work inside Mule.  The output: a new HTTP connector built from the ground up for Mule ESB 3.6.0.

This new connector provides a new design experience that is resource centric, simpler to use, and allows you to leverage RAML specs. When used in conjunction with RAML, Anypoint Studio now provides content assist for the API resources and operations, as well as DataSense capabilities – meaning you’ll have instant access to visualize and map the payload. We’ve also brought OAuth in as a core connector capability, making it easy to connect to modern APIs. Take a look in this video:

Finally, we rebuilt the connector to be highly performant, allowing you to scale to very high loads and concurrency. More on this in a separate blog post soon!

Note: for users who are using our previous HTTP connector, we will continue to support it as part of our offering. We do not recommend that you migrate existing applications at this time unless you want to take advantage of the new capabilities. However, we do recommend that you use it for new projects.

Continuous integration and enhanced management analytics

To support our customers looking to better streamline build and release process via continuous integration, this release features a powerful new agent that provides access to MuleSoft’s runtime API for integrating with existing continuous integration processes and SDLC tools like Jenkins. The new agent can also publish details from Mule applications to third party systems like Nagios and Zabbix for actionable management analytics. More details in an upcoming blog post.

Discover connectors and examples

We hope that by now you’ve seen our Anypoint Exchange, our library of assets for the Anypoint Platform and our original home for integration templates. We have now expanded it to include all of our examples and Anypoint Connectors. You can install connectors, discover and open examples, see version histories and find related documentation all from Anypoint Exchange. Simply click the Exchange button on the top bar, the “Start from Example in the menu bar, or click the “Search in Library” link in the Studio palette.  Our internal teams and beta customers are already using Anypoint Exchange for both training and best practice sharing (RE: higher productivity).

Anypoint Studio shared resources and design improvements

It is our goal to continually improve our design experiences inside Anypoint Studio. One of the major improvements we’ve made is to our application launcher to support launching multiple applications and domains. For users who are building integrations that span multiple projects, it now allows you to run and debug them as a group.  Support for shared resources allows you to easily share connectors across many different integration projects and simplifies configuration and resource utilization. There is a new project type for this, called domains, which can be created and managed next to your normal Mule integration projects.

We’ve made some design improvements to Studio as well. In the flow designer, we’ve improved how flows are visualized. Now there is clear demarcation of message sources and flow logic, allowing you to more easily understand how your integration works. You’ll see that exception strategies are now collapsible as well. Finally, there are some new keyboard shortcuts, which you can clearly see by typing Apple-option-M/Ctrl-Shift-M.

Under the hood, we’ve upgraded to Eclipse 4.4, giving you access to the latest Eclipse features, allowing you to take advantage of the latest Eclipse plugins, and creating an improved look and feel.

Note: To update to the new version of Studio, you must download a new copy – you can not upgrade via an update site. Also, Studio now requires JDK 7. 

Expanded solutions for Microsoft

For customers with a portfolio of Microsoft technologies, the new DataSense-enabled connectors for Sharepoint and Dynamics CRM deliver accelerated connectivity on a modern integration platform.  In addition to these new connectors, developers can now build pure-cloud or hybrid cloud messaging with connectivity to the Azure Service Bus APIs, and map between .NET objects and RAML APIs faster with the refactored .NET Connector. Mobile developers can also easily reference and consume these RAML APIs within Visual Studio, or generate ASP.NET Web API2 compatible APIs from a RAML definition.

Official AMQP 0.9 connector

Finally, this release contains an updated, and officially supported version of our AMQP connector, a messaging protocol with increasing prominence in flexible enterprise architectures. It is built on top of the previously-available community AMQP transport, and includes support for multi-channel receivers, fixes many bugs and contains an upgraded client library.

Get Started

We look forward to your feedback in this post’s comments and in our forum. Happy integrating!


We'd love to hear your opinion on this post