| MULE onDEMAND | JOIN THE BETA | PARTNERS | MULE OPEN SOURCE | COMPANY |
MuleOnDemand--Integration in the Cloud
Sales inquiries call us toll-free
+1-877-MULE-OSSOffice Address
MuleSource Inc.201 Mission Street
Suite 1380
San Francisco, CA
94105
415-229-2009
MuleOnDemand provides integration-as-a-service to securely move and manage data in and out of your enterprise
Using MoD with a Mule Gateway Server
The most common use of MoD is in conjunction with a Mule Gateway server that sits within your enterprise. The Mule Gateway Server plugs into an enterprise's IT infrastructure or DMZ allowing for any authorized enterprise application to connect to the outside world. The MuleOnDemand network transparently mediates between disparate partner applications and network architectures.
1. Connect your internal systems to MoD
- Configure the Mule Gateway Server to receive data from your internal application via any of Mule's transport methods such as JMS, MQ Series, or HTTP. Mule supports a wide variety of APIs, applications and of course you can always build your own through a POJO.
- The Mule Gateway server acts as the broker between your infrastructure and MuleOnDemand.
- Define MuleOnDemand as your endpoint to receive data from the Mule Gateway Server.
2. Configure MoD to receive your data
- When used in conjunction with a Mule Gateway Server MoD supports a wide variety of transport methods including JMS, Web Services and others. This Mule-to-Mule communication enables complex transactions to occur seamlessly across the network.
3. Define where your data goes next
- Perform transformations, complex routing etc. prior to sending your data out.
4. Send your data to it's destination
- Mule will process your data and send it on to the endpoint you defined.
Using MoD for Integration-in-the-Cloud
MoD enables enterprises to move and manage data regardless of where it resides.
1. Determine the systems and data you want to integrate
- MuleOnDemand's endpoints and integrations are defined the same way as they are in a standard Mule configuration
2. Configure the inbound data to be received and transformed as necessary
- Typical methods to receive data are via Email, HTTP, and Web Services
3. Define where your data goes next
- Perform transformations, complex routing etc. prior to sending your data out b. Examples include Salesforce.com, internal applications such as SAP or third party payment processing
4. Send your data to it's destination
- Mule will process your data and send it on to the endpoint you defined.
