MuleSoft Accelerators - Setup Guide
home
Accelerator components
This asset is used in the following MuleSoft Accelerators:
- MuleSoft Accelerator for Retail — Includes pre-built APIs, connectors, integration templates, and reference architecture to enable retail IT teams to jumpstart digital transformation initiatives.
- MuleSoft Accelerator for SAP — Includes components and use cases for SAP ECC, S/4HANA, and Salesforce, and enables organizations to easily expose SAP ERP data for consumption by all.
- MuleSoft Accelerators for Salesforce Clouds — Includes pre-built APIs, connectors, and integration templates that help unlock business-critical data from external systems such as SAP, ServiceNow, and Jira, which accelerates implementation of essential integration use cases for Service Cloud and Commerce Cloud. These assets guide you to adopt best practices synthesized from thousands of customer implementations and can be used as-is or extended to meet your company's unique needs.
- MuleSoft Accelerator for Healthcare — Includes pre-built APIs, connectors, implementation templates, and a prescriptive end-to-end reference architecture to enable EHR connectivity, power a Patient 360, and bring patient demographics information and COVID-19 lab results from any EHR into Health Cloud using HL7 V2 or FHIR standards.
Quick start
To get started, you must set up your local build environment with the required software and Maven build configuration. Next, download and configure the assets required for the use case(s) you wish to implement. Some use cases will require changes to the systems being integrated (e.g., SAP, Salesforce Service Cloud, and so on) - be sure to read and follow the instructions specified in the use case page(s) carefully. In many instances, additional details are provided in the README.md of individual projects.
Once configured, applications can be deployed individually to your own CloudHub instance, either manually or by using simple Maven commands. There are also some helper profiles available for deploying multiple components at once.
Asset types
The following table provides more information about the types of accelerator assets provided and how they fit into the overall solution.
| Type | Purpose | Example |
|---|---|---|
| API Spec Fragments | Shared RAML specifications reused by multiple APIs. These define standard characteristics, data types and response codes common across most APIs. | Accelerator Global Resources |
| REST APIs | RAML specifications describing the resources and methods an API makes available to consumers. They are categorized into layers - System, Process, Experience - as per MuleSoft's API-led approach. | Accelerator OMS System API |
| Templates | Runtime implementations of individual APIs and other integrations. These must be customized and deployed to your own Mule runtime environment (e.g., CloudHub) to implement desired use cases. | Accelerator OMS System API - Implementation Template |
| Custom | Documentation and downloadable components that do not fit into other categories. | Accelerator POM Parent |
Obtaining accelerator assets
All accelerator assets are available from the main Anypoint Exchange site and are freely downloadable. For API specification and implementation project names referenced in this document, search for each asset in Exchange or visit the solution landing page to see the full list of assets.
Deploying accelerator components
In this release, all accelerator components can be individually configured and deployed to your own environment using a text editor and some simple Maven commands. With the exception of the Accelerator Salesforce OData API, all component dependencies will automatically be resolved from Exchange and other Maven repositories.
Refer to the sections in the page navigation menu on the left for more information about configuring, building, and deploying applications.