The latest release of Anypoint Platform includes major upgrades to our logging service for applications running on CloudHub (now a Platform service). With this release, users will be able to retain more log information per application, using a globally distributed infrastructure, and access the logs via an updated UI. Additionally, users who do hybrid management of on-premises servers and applications will now be able to set up High Availability (HA) for their on-prem servers using the new clustering feature.
Why the shift from CloudHub as product to CloudHub as Platform service?
Over the past 18 months, we have steadily pushed to unify the various aspects of Anypoint Platform: on-premises and cloud-based integration, as well as API design, implementation and management, with the goal of helping IT teams partner with the business in delivering with speed and scale while maintaining control. Anypoint Platform now offers a complete host of platform-level functionality, and we are redefining some of the naming of its components to reflect its new unified/hybrid capabilities. Looking ahead, you’ll see us talking less about Mule ESB, CloudHub and the tooling we’ve built around those products as individual piece-parts. Instead, we’ll be discussing them as ONE solution with a single runtime (Mule), flexible deployment options and a suite of design capabilities, management capabilities, platform services and ways to get connected.
The name CloudHub now refers to a set of Platform services and one of our available deployment targets: a fully-managed, multi-tenanted, globally available, secure and highly available worker cloud for your integrations and APIs.
The new logging upgrade features a globally distributed infrastructure for improved availability while addressing data residency requirements, and offers a 10x improvement on capacity for log retention – 100 MB or 30 days worth of logs, whichever comes first. It will initially be enabled for the following runtimes:
- Mule 3.5.3
- Mule 3.6.2
- Mule 3.7.1
- API GW 2.0.3
Support for the rest of the runtimes will be rolled out over the rest of the year. During the first phase, customers will be able to opt in to use the new logging infrastructure (for supported runtimes). Note that using the new infrastructure will mean the loss of historical log data, so please download your logs before opting to use the new infrastructure. All runtimes will be supported on the new logging system by the end of the year, at which point all applications will be migrated over to the new system and the old system will be deprecated.
If you create an application with one of the above runtimes, you will notice a new setting for enabling enhanced log management which, if checked, will allow your application to use the new logging infrastructure. The new setting is only enabled for runtimes which support the new infrastructure, as listed above.
Once you create an application with the new logging enabled, you will only see runtimes which have the new logging enabled in your runtime dropdown options. Please note that once you start an application with the new logging enabled, if you later uncheck the option, you will lose your log history, so you will be alerted to download all your logs before disabling this option.
If you navigate to the logging UI for this application, you will see that you now have the ability to filter log messages for the application to only view certain deployments or even instances within deployments. The live log view will continue to show messages from all instances as they occur.
It’s possible to download all the logs for a single instance using the download icon next to the instance.
In short, the new logging infrastructure for Anypoint Platform – iPaaS provides more log retention and a more powerful UI with capabilities for filtering and downloading specific parts of the application log.
Clustering for On-Prem Mules and API Gateways
- Mule 3.6.3 (coming Q3 2015)
- Mule 3.7.x
- API GW 2.0.2
When you navigate to the Server management screen on the UI, you will see that there is now a new “Create Cluster” button which will allow you to configure a cluster with supported Mule and API Gateway servers.
When you click that button, you will be taken to a cluster creation page where you can configure the details of the cluster – Unicast or Multicast, and the parameters for each. You will also need to specify a unique name for the cluster. For context, unicast clusters require individual nodes to be configured for clustering using their IP addresses. Multicast clusters, on the other hand, rely on multicast communication being enabled on the underlying network routing fabric, and therefore don’t need individual nodes to be configured with their IP addresses.
Once the cluster has been configured, it will show up as a target for application deployment. Just pick the newly configured cluster, click deploy, and congratulations… you have just deployed your application to a highly available Mule or API Gateway cluster.