We’re excited to announce the general availability of CloudHub Insight, a new CloudHub platform service. Today’s application integration requires a new kind of integration intelligence to answer questions about how your business is running, diagnose complex problems, and recover from cloud “thunderstorms.” CloudHub Insight provides a new level of visibility by tracking everything your data does, making it instantly searchable and provides advanced error recovery through Message Replay, taking the complexity out of addressing the real life challenges of SaaS integration.
It’s no secret that we are in exciting times where we’re witnessing an incredibly rapid proliferation of APIs and with this has come great challenges. There is no standard place for discovering APIs, nor is there a trusted partner for API publishers – there are many little players trying to solve small problems in silos and this is leading to more and more dis-aggregation of the API landscape. So what is needed now is some sort of a “hub” to bring it all together. This need for something to be brought together isn’t a new trend by any means; books and e-commerce had Amazon, social had Facebook and software development had GitHub. What all these hubs had in common is they shared the following characteristics:
We are making this release of Studio available to the Mule community to get valuable feedback on our latest and greatest features. This blog post contains text and video introductions to the freshly-baked features included in this release.
As you read through this post and try the Studio features, please keep in mind that this is a pre-Beta version. Explore, discover and play, but do not use it to develop Mule apps for use in production.
Integration is becoming such a critical part of application development that we spend many of our cycles on making Mule easier for any developer to use. Mule Studio was built to address the needs of developers who don’t wake up every morning thinking about integration.
If you have used Mule in the last year there is a good chance that you have used Mule Studio. It is an Eclipsed based development environment for building Mule applications either visually or using the XML DSL (with full two-way editing). Mule Studio has become the preferred on-ramp to working with Mule. Of course if you prefer to hack in a text editor Mule continues to embrace Maven for command-line development.
The massive growth of APIs and SaaS applications has created a need to integrate anything, anywhere. This integration wave presents unique challenges for organizations looking to integrate both in the cloud and on-premise. Join Ross Mason, Founder & CTO of MuleSoft, as he discusses the emerging hybrid architectures designed to manage this challenge.
In this webinar, you will:
It’s a pleasure for me to introduce the Mule Dropbox Connector. I’m sure you have heard of Dropbox and many of you have been delighted by its simple features, and now you can take advantage of them in your Mule applications.
Getting the Dropbox Connector
It’s really easy to start using this connector thanks to Mule Studio update site. To install it:
- Go to the menu Help -> Install new software
- Enter the connectors releases repository: http://repository.mulesoft.org/connectors/releases
- Select the Dropbox Cloud Connector available in the Community group
I had the privilege of speaking at the Mule Summit in Chicago a few weeks ago. During my presentation, I covered some key Mule ESB features we leverage at Express Scripts: Component Bindings and Custom Configuration Patterns. Few conference attendees were familiar with these features, so we thought blog posts would help share information about these features with a broader audience. In this post, I’ll focus on Component Bindings. A future post will cover Custom Configuration Patterns.
With the rapidly increasing adoption of SaaS, integration Platform as a Service (iPaaS) has become the preferred way to connect SaaS applications. However, with the explosion of Open APIs on the Web connecting APIs together is becoming the norm for application development. However, typical application containers and even application PaaS offerings don’t help in this new era where applications compose APis together from many different sources.
In the iPaaS world composing APIs together is modus operandi. An application built on an iPaaS is focused on connecting 2 or more systems together via APIs in order to synchronizing data between them. However, we’ve taken this new breed of applications much further with the concept of Integration Apps.
Mule Properties and FLow Variables are one of the most widely used features in Mule. Nevertheless, Mule newcomers may have a hard time understanding how the different property scopes and variables compare to each other, and how to choose the right one for their use cases.
The idea behind this blog post is clarify those differences, comparing side by side INBOUND, OUTBOUND, INVOCATION and SESSION property scopes. We will also cover “flow variables” and “session variables”. For more detailed information, you can go to each scope´s section in the User’s Manual.
Our integration tests should be portable, meaning that if we shared our project, everyone would be able to run our tests on any platform without needing to install any framework or application. This is a very common issue when we test flows that have an SFTP outbound endpoint. In order to do an integration test of our flow, we need to start an SFTP server on our machine or use a public SFTP server, which implies adding network overhead to our tests.
A simple solution to portable SFTP testing is embedding an SFTP server into our tests. A good and really light weight framework to do so is Apache Mina.