We are proud to announce the newly redesigned Community Forums are up and running. Along with a new clean design, we’ve enhanced the overall user experience by making content easily searchable and accessible. Here are a few other highlights:
As you probably know, Mule provides pretty good support for PGP encryption (check the related links for further info on Mule’s PGP support). What we’re going to do in this blog post is provide a step-by-step, real life use case for PGP encryption. We’ll take a ride all the way from key generation to Mule configuration.
Intacct is an award-winning financial management system with over 5,000 customers worldwide. Intacct is often said to be the next logical step for companies that have outgrown QuickBooks Online. Since MuleSoft uses Intacct internally, it was natural that we needed a cloud connector to it in order to automate our internal business processes.
As an example, we have a fully automated invoice creation process so that when a sales opportunity in Salesforce is marked as won, this triggers an integration processes that automatically creates a customer invoice in Intacct based on the product and customer data captured in the sales opportunity. This integration completely eliminated the need for tedious and error-prone data entry tasks in our accounting department. This is just one example of how you can leverage the Intacct cloud connector in order to automate your business processes.
The alarms go off. You get an alert on your cellphone. You look at your systems dashboard and notice that your Mule server, which was happily chewing messages until just a minute ago, is struggling. What can you do?
We recently pushed out an update to iON which makes building APIs in the cloud better than ever: zero downtime upgrades. Without you having to do anything, we ensure that your application is able to continually serve requests while you’re updating it.
The way this works is simple. Let’s say you have version 1.0 of your application in production and you’re about to release version 2.0. Because version 2.0 may take a few moments to start, iON will keep version 1.0 running while version 2.0 starts. Once version 2.0 is fully started, iON will update your domain name to point to your new Mule instance and shut down version 1.0. With no operations team at all, you’ll have managed to implement what many API providers find extremely challenging to do!
I just read a good post by Sam Charrington on RWW titled, The Disintegration of PaaS. He points out that early PaaS vendors had to build out the whole stack, including application server, database, file storage, etc. This locks applications into a specific stack. He goes on to say that we are now moving into a new evolution of PaaS, where some of the component pieces of the platform, e.g., databases, are available from other service vendors. However, the change we’re seeing is much broader than PaaS. This shift picks at the very fabric of software; we are witnessing the revolution of software development as we know it.
Last month we released Mule 3.3 M1, our first milestone on the way to Mule 3.3. While for production you should use Mule 3.2.1, we hope these milestones are a great way to play around with the latest and greatest features. This is a great opportunity to provide feedback and have an impact on what we are doing for the Mule 3.3 release.
Mule allows us to expose services to the web through CXF, but what happens when these services handle sensitive information that we don’t want just anybody to read or change? We need to be able to authenticate who is consuming the Web service and determine if the user should have access to the service or not.
Complex event processing engines are a natural fit for event driven platforms like Mule. Native CEP support has been available in Mule since version 3.2 by way of the Drools Module. The Esper Module now offers an alternate way to leverage CEP in your integration applications. Esper is a robust, performant, open source, complex event processing engine. Let’s take a look at how to use Esper with Mule and then see how it compares to Drools’ CEP support.