Skip to content

Latest commit

 

History

History
261 lines (154 loc) · 20.1 KB

index.adoc

File metadata and controls

261 lines (154 loc) · 20.1 KB
Raw

MuleSoft Documentation

The mission of MuleSoft is to help organizations change and innovate faster by making it easy to connect the world’s applications, data, and devices. With its API-led approach to connectivity, MuleSoft provides the market-leading Anypoint Platform that enables organizations to build their application networks faster.

What is Mule runtime?

Basically, Mule runtime is an engine for processing and orchestrating data. This runtime is the layer that facilitates development and deployment of reliable, highly available applications that define how Mule should support interaction between diverse systems. Using Mule runtime you can build enterprise-grade integration applications, called Mule applications.

Note
 Mule runtime is often referred to as Mule ESB. Call it Mule for short. In more technical terms, Mule runtime is a Java-based enterprise service bus (ESB) based on SEDA (staged-event driven architecture). Download Mule with Studio and start working with processing data across SaaS or backend systems with Mule applications.

What is a Mule application?

A Mule application is a series of functions that act on incoming data. An app does not start until a user-defined event happens, like a change to a file. The event is encoded as a Mule message, which gets passed from one end of the flow to the other, passing information about the event to one or more systems, perhaps enriching the data in the message for a certain destination, like a webpage, device or database. The message is the wrapper for important data, which is typically accessible via the message payload, like #[payload.something]. It is up to the integration developer to design the flow(s) and configure how the components operate on messages that pass through. Components can be configured to connect to existing applications anywhere, cloud or on-prem.

Once a Mule app is deployed to Mule runtime, the app is ready to be kicked off by the event(s) to trigger a flow. You can deploy Mule applications to Mule runtime servers anywhere, and configure security and policies for them as well. In Mule apps you write less custom code, and get more done through reuse.

Tip
 Consider APIs your ally when connecting assets. Starting with API design allows developers to decouple business logic from the APIs used to link digital resources together.

What is Anypoint Platform?

Anypoint Platform is MuleSoft’s integration application and API suite. It comprises a unique toolset that enables organizations to create, integrate, model, build, and deploy services, APIs, and Mule applications.

The Anypoint Platform tools are accessed primarily through a browser but also have command line tools and APIs. Through the platform it is possible to control most aspects of integration applications and APIs throughout their entire lifecycle.

Tip
 An on-premises version is available, enabling you to securely host Anypoint Platform on your infrastructure.

Anypoint Platform Tools

Follow these steps to get an Anypoint Platform account and check out the tools it provides.

Developer Toolkit

After obtaining access to the Anypoint Platform, you are a few steps away from developing integrations with Mule.

  1. Download and Install Anypoint Studio. Studio comes with a test Mule server.

  2. If you are an API developer, ensure you read up on API Manager, accessible from Anypoint Platform, to design, publish and manage APIs.

  3. Check out templates, connectors and more from Anypoint Exchange, where you can find and publish developer resources. You can use Exchange to publish private repositories too.

Note
 If you’re working with Mule outside Studio or you have an enterprise license, see how to Configure Maven to properly manage the dependencies used by your Mule apps.

Deployment Toolkit

For API deployment, see API Manager, accessible from Anypoint Platform.

For Mule application deployment, see deployment strategies. This document explains the standard app-to-runtime deployment workflows and tools.

Tip
 See instructions on how to deploy applications to CloudHub or to local Mule runtime instances via the Anypoint Platform.

Administration Toolkit

If you are an admin, provision access to your organization’s Anypoint Platform instance through the Access Management console.

Tip
 Set up external identities to manage users and clients using your organization’s external federated identity system.

To manage Mule apps and servers, use Runtime Manager, the same platform tool used to deploy apps to Mule anywhere.

For APIs, see API Manager and Anypoint Analytics.

Contribute to the Documentation

MuleSoft welcomes contributions to our documentation from the community. To make a contribution:

  1. Click Edit on GitHub at the top of any page.

    The source page on GitHub appears.

  2. Click Edit this file and make a change using the asciidoc markup language.

  3. Accept the contributor’s agreement so that we can acknowledge your contribution.

For more information about making a contribution, see the README.adoc file. Your positive impact in the community by improving MuleSoft documentation is appreciated and recognized.

See Also