Book Image

MuleSoft for Salesforce Developers

By : Arul Christhuraj Alphonse, Alexandra Martinez, Akshata Sawant
Book Image

MuleSoft for Salesforce Developers

By: Arul Christhuraj Alphonse, Alexandra Martinez, Akshata Sawant

Overview of this book

MuleSoft for Salesforce Developers will help you build state-of-the-art enterprise solutions with flexible and scalable integration capabilities using MuleSoft’s Anypoint Platform and Anypoint Studio. If you’re a Salesforce developer looking to get started with this useful tool, look no further. This book will get you up to speed in no time, leveling up your integration developer skills. This essential guide will first introduce you to the fundamentals of MuleSoft and API-led connectivity, before walking you through the API life cycle and the Anypoint Studio IDE. Once you have the IDE set up, you’ll be ready to create Mule applications. You’ll look at the core components of MuleSoft and Anypoint Platform, and before long you’ll know how to build, transform, secure, test, and deploy applications using the wide range of components available to you. Finally, you’ll learn about using connectors to integrate MuleSoft with Salesforce and to fulfill a number of use cases, which will be covered in depth, along with interview and certification tips. By the end of this book, you will be confident building MuleSoft integrations at an enterprise scale and be able to gain the fundamental MuleSoft certification – MCD.
Table of Contents (21 chapters)
1
Part 1:Getting Started with MuleSoft
7
Part 2: A Deep Dive into MuleSoft
14
Part 3: Integration with Salesforce and Other Connectors

Exploring the Mule project structure

Before getting into creating a Mule project, it is important that we get familiar with the Mule project structure. Let us see the project structure of a Mule application in Package Explorer. These are the main folders and files that are important for every Mule project:

  • src/main/mule is for Mule configuration files. It is an .xml file that contains application logic where all the flow components reside. We can store n number of Mule configuration files to have different application logic, flows, or APIs and there is no limit enforced by Mule on the number of Mule configuration files. For example, we can store our API interface, API implementation, error handling, and the global configuration in separate Mule configuration files. This folder is for storing all your Mule XML code.
  • src/main/resources is for Log4j configuration, any environment-specific properties files, DataWeave scripts, and API-related documents, such as the API specification...