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:
- Your integration doesn’t have a dedicated operations team
- You may need to integrate with unreliable services
- You may receive data from external partners which is in an unexpected format
- Coordination with multiple people (e.g. end user, internal IT and integration developer) is required.
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.
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 a free self-paced training course for people looking to get to grips with Mule through a structured program.
We also have video 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 ESB and Mule iON.
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.
Why do I want this?
This connector is mainly aimed to situations in which systems integration requires executing shell commands into a remote system. Examples are:
- Config changes (passwords, permissions, accounts, etc)
- Resource provisioning
- File System operations on non FTP-mapped drives or folders
Since Mule is built on Java and Spring, it has native integration capabilities to invoke Java and Spring components. In this tutorial, we shall learn how to pass request received from HTTP endpoint on to Java component and receive response.
Please complete Hello World lesson from last week before proceeding further.
We are really excited to be sponsoring Cloudstock on Thursday March 15th, this is a free cloud developer event in San Francisco hosted by Salesforce.com. We’ll be joining top SaaS and cloud thought leaders along with over 3,000 developers at Moscone West, where throughout the day at our booth, two of our top developers, Dan Diephouse and David Thompson, demonstrate some very cool Mule iON iApps and dig into the code.
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.
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.
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.
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.