Account System API - Database Implementation Template

(1 review)


This template helps you design an Account System API. It provides a means of hiding the complexity of the database implementation from a user while exposing data in a canonical format. The template abstracts account data from a database into a canonical objects that are defined within a CRM System API. This API uses JSON as an exchange format and translates calls into the semantic data structure required by a database.








The CRM System API supports the following operations:


License Agreement

This template is subject to the conditions of the MuleSoft License Agreement. Review the terms of the license before downloading and using this template. You can use this template for free with the Mule Enterprise Edition, CloudHub, or as a trial in Anypoint Studio.

Use Case

This template serves as a foundation for the API led connectivity approach of running an enterprise.

The template is a system API to an underlying database.

This template is a REST API implemented using APIkit and RAML definition. The basic CRUD operations are implemented for Account object. The API uses JSON as an exchange format. Included are example requests and responses.

The sections that follow provide the endpoints for this template.

GET /accounts

Retrieves accounts from a database based on the combination of query parameters. Set at least one of modifiedAfter or name to retrieve the results. See the included RAML definition to learn more about the implemented query parameters.

POST /accounts

Inserts a new account in a database.

GET /accounts/{id}

Retrieves an account based on a native identifier used in the database.

PUT /accounts/{id}

Updates an account with the data in the HTTP request. All fields are overwritten.

DELETE /accounts/{id}

Deletes an account based on a native identifier used in the database.

See the included self-descriptive RAML definition and the corresponding flows to learn more about the application.


To make this template run, there are certain preconditions that must be considered. All of them deal with the preparations, that must be made in order for all to run smoothly. Failing to do so could lead to unexpected behavior of the template.

This template requires a database instance to work. This template comes packaged with a SQL script to create the database table that it uses. Use the script to create the table in an available schema and change the configuration accordingly. The SQL script file can be found in src/test/resources/db_ddl_script.sql.

Run it!

Simple steps to get this template running.

Running On Premises

In this section we detail the way you should run your template on your computer.

Where to Download Anypoint Studio and the Mule Runtime

If you are new to Mule, download this software:

Importing a Template into Studio

In Studio, click the Exchange X icon in the upper left of the taskbar, log in with your Anypoint Platform credentials, search for the template, and click Open.

Running on Studio

After you import your template into Anypoint Studio, follow these steps to run it:

  • Locate the properties file, in src/main/resources.
  • Complete all the properties required as per the examples in the "Properties to Configure" section.
  • Right click the template project folder.
  • Hover your mouse over Run as.
  • Click Mule Application (configure).
  • Inside the dialog, select Environment and set the variable mule.env to the value dev.
  • Click Run.

Running on Mule Standalone

Update the properties in one of the property files, for example in the file, and run your app with a corresponding environment variable. In this example, use mule.env=prod.

Running on CloudHub

When creating your application in CloudHub, go to Runtime Manager > Manage Application > Properties to set the environment variables listed in "Properties to Configure" as well as the mule.env value.

Once your app is all set and started, there is no need to do anything else. Every time a lead is created or modified, the template automatically synchronizes to Salesforce Org B as long as it has an email address.

Deploying a Template in CloudHub

In Studio, right click your project name in Package Explorer and select Anypoint Platform > Deploy on CloudHub.

Properties to Configure

To use this template, you need to configure properties (Credentials, configurations, etc.) either in properties file or in CloudHub as Environment Variables. Detail list with examples:

Application Configuration

Common configuration

  • http.port 9090

Database Connector Configuration

  • localhost
  • db.port 3306
  • db.user joan.baez
  • db.password JoanBaez456
  • db.databasename template-apiled-system-account-db

API configuration

  • api.domain
  • api.basePath /api

Customize It!

This brief guide provides a high level understanding of how this template is built and how you can change it according to your needs. As Mule applications are based on XML files, this page describes the XML files used with this template. More files are available such as test classes and Mule application files, but to keep it simple, we focus on this XML file:

  • system-api.xml


A functional aspect of this template is implemented in this XML file to create or update objects in the system for a represented use case. You can customize and extend the logic of this template in this XML to more specifically meet your needs.

Configuration for connectors and properties place holders are also set in this file. Even though you can change the Connector configuration in the XML file, all parameters that can be modified here are in properties file, and this is the recommended place to do it. In the visual editor, they can be found on the Global Element tab.


Published by
MuleSoft Organization
Published onSep 27, 2019
Asset overview

Asset versions for 2.1.x

Asset versions


SAPNo values left to add
Enterprise ITNo values left to add