Tag: Mule ESB
Want to leverage existing PHP experience of your development team to accelerate implementation times? In this blog post I’m going to show you how to take advantage of new Mule PHP scripting module, that enables your applications to use good’old PHP as the programming language in Mule scripting components.
Webhooks are a very simple way to tie application together on the Internet. Suppose application A wants to be informed when data changes in application B: the traditional approach consists in having application A poll B for changes. The webhooks approach turns the problem around: B gets configured so it hooks to A via HTTP calls. Whenever data changes in B (or for that matter, whenever anything of interest happens in B), B will call A to let it know. No more polling, just simple HTTP server-to-server callbacks. Webhooks is so simple that there is no spec for it: the HTTP spec is all what is needed really.
SOAP, JMS, Restful, SFTP… Sometimes your integration just comes to the point in which you need to be able to download a file from your browser. From Ubuntu One all the way to Dropbox and Google Drive, the number of file storage services on the cloud just keeps climbing. One that is particularly gaining a lot of momentum and putting a lot of effort on cloud to cloud integration is Box, so we decided to build a Cloud Connector for it and we’ll show it to you in this post.
Today I am going to introduce you to some powerful new features in Mule 3.3:
Improved Error Handling: New exception strategy patterns fully integrated in Studio. Included are Try/Catch, Rollback processing and Conditional Exception processing in Choice routers based on exception type, or just about any criteria!
Iterative Processing using Foreach Scope: Allows for iterative loop type processing while maintaining the original message context
Mule Expression Language: A new, unified expression language to improve consistency and ease of use when validating, filtering, routing, or transforming messages
Cache: Improve performance with “In memory” caching of messages, such as the results of service calls
Graphical Data Mapper: A new graphical tool to easily transform from one data format to another data format while also mapping specific fields within the message structure. Formats supported include XML, JSON, CSV, POJOs, collections of POJOs, and EXCEL
I’m going to provide an overview on how to build a simple contract-first web-service and JAX-WS client that consumes the web-service with Mule Studio.
The sample below is going to build the following:
- Build SOAP/ HTTP web service using Mule & CXF that is CRUD web service to create, retrieve, update and delete an order and returns the order id. This exercise implements only the create operation for this service.
- Build the Order Receiver Service
- Receives the order information from HTTP Inbound Endpoint.
- Invokes CRUDOrder web service to create the order
- Returns the order id to Portal
I was reading John D’Emic’s brilliant post Twitter Complex Event Processing (CEP) with Esper and Drools and got truly inspired. After playing around with the combination of Mule and Esper I was amazed how good they suit each other. Letting Mule do the hard work of shuffling data and intelligent routing while Esper analyzing events on a overall level. It gave me kind of a opportunity to be stateful in a stateless environment. For those who aren’t familiar with Esper, it is what is called a Complex Event Processing engine that allows you to create queries and assertions on streams of events in real-time.
Mule is typically used on the receiving end of service requests. Mule flows, for instance, are generally initiated by external events like a JMS message being sent to a queue, a POSTed HTTP request, or the firing of a Quartz trigger. Since Mule is usually deployed as a server this behavior should be expected. What isn’t so obvious, however, is using Mule as a client of these services. We’ll see in this blog post how MuleClient can be embedded in a non-Mule application to send and consume messages as a client.
Hello friends! How’s it going?
Has the following ever happened to you? You show up to work one morning and your boss tells you, “I need you to take this data and turn it into XML.” Well, this has happened to me, and in this blog post I’m going to show you how to do this quickly.
The architecture of Mule is driven by the principles of Industrial Best Practice as outlined in the well-known Enterprise Integration Patterns which have identified the most common building blocks for every integration problem. These building blocks are what make up Mule Flows, the executable units inside Mule Applications. No matter what the problem, wiring them together into an integration solution is extremely easy and by exploiting the power of Mule’s native support for the Drools Rules Engine, the Integration Developer has a very powerful set of tools to tackle even the most complex of integration problems with the greatest of ease. With this post I hope to be able to demonstrate this to you!