So you’re using iON to run your Mule application and Maven to manage your development? Great! You’re now ready for the next stage: continuous deployment, which is the easiest way to push your application to iON during your development cycle.
Continue reading We’re happy to announce that a new version of Mule iON is now available which is focused on helping you address many of the challenges of doing integration in the cloud. When running in the cloud, many things change:
This is not an easy task. But in this latest update to iON, we’ve introduced a number of features that make this easier than ever.
Continue reading If you are looking to get started with Mule ESB quickly, we have lots of resources to get you moving. First off, you should be aware we have quick start guides and a free self-paced training course for people looking to get to grips with Mule through a structured program.
We also have tutorials for the major concepts in Mule. You can download Mule and Mule Studio to get started. The following tutorials are a great place to start. Each session introduces a core concept namely endpoints, components, filters, transformers and the Mule message. Note that these tutorials are applicable to Mule Runtime and Cloudhub. <- link
Continue reading We’re proud to announce that a new SSH Cloud Connector for Mule just went public! Let’s take a peak into the features, useful use cases and of course, coding examples.
This connector is mainly aimed to situations in which systems integration requires executing shell commands into a remote system. Examples are:
In 2005 there were 105 open APIs. Today there are over 5,000. What does this mean for you and how you will build your applications? Join MuleSoft’s CTO Ross Mason for some insight into the implications of API proliferation.
Continue reading
This is a series of blogs aimed at developers new to Mule that are just getting started. These lessons will introduce common concepts and implement frequent use case that we see in our community. If you have suggestions for a lesson, please post it in the comments.
The lessons are all based on Mule Studio, the free Eclipse IDE for Mule, you can get the latest version here.
Continue reading As evident by some prominent web applications PHP remains a popular choice when implementing the front-end of a web application. PHP’s lacks a bit, however, when it comes to implementing the backend of such applications. While some very nice frameworks are beginning to fill this gap, the Java ecosystem is often a better choice for implementing the backend of a PHP application.
Despite this, however, integrating PHP and Java isn’t a straightforward task. A robust PHP implementation for the JVM doesn’t exist. HTTP based protocols like SOAP and REST can work, but we usually want something reliable for messaging behind the firewall. JMS might seem like an obvious answer, but most brokers only support Java. Stopgaps like Stomp also exist but, it too, isn’t a reliable transport. What we really need is a reliable transport that works natively with PHP and Java.
Continue reading There’s no need to state the importance of debuggers for developers, and Mule developers are no exception. The goal of this blog post is to provide you with a few handy tips for debugging your custom Java code in Mule Studio.
Getting started
I will assume you have already created your Studio Project and added a custom Java class (a Transformer, Module, etc.). If you are not there yet, you should probably read Getting Started with Mule Studio.
Continue reading
Transactions are a fundamental piece of Mule, since they are essential to guaranteeing that, in the event of an exception or a problem, the consistency of the process will be maintained and that there will be no loss of information. When working with a unique resource (such as one JMS Broker, or one Database), the solution is pretty straight forward. By simply using the <transaction> element you can configure a nice transactional flow.
When dealing with several data sources in the same flow, however, this becomes a little bit more complex since it involves another kind of transaction, the XA Transaction. This also requires some additional configuration in order to make it work correctly. In this blog post, I’ll explain and show you a full working example of am XA Transactional Flow that you can use as starting point and will hopefully save you some time.
Continue reading Mule Enterprise 3.2 introduced a powerful feature allowing to keep track of everything happening during the lifetime of your applications: Business Event Analyzer. This provides a place to monitor business transactions and events across multiple systems. Most businesses need access to information surrounding the following use case examples:
This post provides some tips for working with the Business Event Analyzer. While we worked pretty hard to ensure overheard is very low there are still a number of points to consider before using (and abusing) it.
General Overhead
Business Events are extracted from Server Notifications, the internal notification system in Mule. Event creation has been optimized but is still not free. So the more events will be generated per business transaction the higher performance impact will be. Typical use case (say 5 events per flow) will generate an overhead less than 1 millisecond per flow. On the other hand if your application does not generate events overhead will be null.
Adding Custom Events
Custom events are very handy and you might be tempted to use them a lot. Plus you can benefit the full expression language power! As events are generated synchronously you probably want to consider your expression execution time. As a rule of thumb the more data will be accessed the longer the execution will take. Measure carefully before rolling out in production!
If something breaks
Events are stored locally as soon as they are generated. This acts as a local cache in case the agent has a network issue accessing the Enterprise Management console. Storage is pluggable thus you’re free to have reliability or not depending on your needs. The Enterprise Management Console will retrieve all outstanding events when a connection is made.
Business Intelligence
One of the powerful features of the Business Event Analyzer is that it can expose its data to 3rd party BI tools. This means the data captured can then be analyzed by other tools to glean further insights and for reporting, i.e. transaction audit or compliance. This opens up a new level of visibility and insights about the data running through your ESB.
This is a powerful capability of the the Mule Management Console, you can learn more here or just try it for yourself and download Mule Enterprise.