FINS Common Resources - Source

This asset is a component of the MuleSoft Accelerator for Financial Services, which accelerates the implementation of essential integration use cases.

The solution boosts time-to-value in your customer 360 initiatives with pre-built APIs, templates, and reference architecture for financial services. Our foundational assets are expertly designed to jumpstart your top integration and business initiatives so that IT teams can spend more time innovating and less time building from scratch.

Project contents

The fins-common-resources project provides a Maven build profile, Postman collections, and other resources helpful for environment setup and testing.

To obtain the source for this project, download the asset and extract the contents into a temporary folder. The archive contains a single project folder, which can be moved/copied to the desired location and/or imported directly into Studio as an existing project.

Build files

Maven module build files are provided to simplify building and deploying all assets required by each use case. All projects in each build file must already exist under the root workspace folder.

Configuration files

The settings-accelerators.xml file is a Maven configuration template that should be used as the basis for building and deploying assets related to the MuleSoft Accelerator for Financial Services. Copy or merge the content of this file to one on your local workstation (the default location is $HOME/.m2/settings.xml on Linux/MacOS, %USERPROFILE%\.m2\settings.xml on Windows) and customize the following sections as per your organization's target Anypoint instance:

• The global-settings-fins global profile properties
• The CloudHub-FINS-DEV deployment profile properties
• Credentials for the anypoint-exchange, anypoint-exchange-v2, anypoint-exchange-v3, accelerator-exchange, and mule-enterprise server entries

Once configured correctly, you will be able to build and deploy any implementation template to your own Anypoint instance using Maven.

Postman collections

The following Postman collections can be found under the collections folder:

• Accelerator-Deployment-Verification - provides a set of test cases to invoke the new /ping endpoint on all accelerator APIs
• Anypoint-MQ-Configuration - can be used to automatically create the Anypoint MQ destinations and client application required by many accelerator components
• Core-Banking-Test-Data - creates a core set of test data in the Core Banking System for demo purposes
• MultiChain-Configuration - helper collection to create wallet addresses and assets in a MultiChain instance

Salesforce

The following scripts and classes can be found under the Salesforce folder which are used by the Salesforce System APIs and Event Listeners:

• CreateApexTriggers.txt - includes apex triggers used to publish the events which are processed by Accelerator Salesforce Party Event Listener and Accelerator Salesforce Financial Account Event Listener
• CreateCustomFields.txt - includes scripts to create custom fields in Salesforce
• CreateCustomObjects.txt - includes scripts to create custom objects in Salesforce
• CreatePlatformEventsCustomFields.txt - includes scripts to create custom fields on a Platform event which is processed by Accelerator Salesforce Party Event Listener and Accelerator Salesforce Financial Account Event Listener
• CustomFieldUtility.apxc - This apex class includes functions which can be used to create custom fields in Salesforce
• CustomObjectUtility.apxc - This apex class includes functions which can be used to create custom objects in Salesforce

Note:
The scripts for creating Custom Fields, Custom Objects and Apex Triggers are consolidated for all the usecases in Accelerators. You may not need to run all of them. Refer the Documentation of the System API or the Event Listener that you are setting up to understand what is applicable for your specific usecase.

Scripts

Docker scripts are provided to assist in deploying the Moov.io ACH and Fedwire containers.

Samples

Samples are the example files to load data to the Snowflake, Databricks, and AWS S3. These files are needed for Use case 5 - Optimize Customer Experiences with CDP.

• FinancialAccountsSample.csv - file to load data to the FINANCIAL_ACCOUNT table of Snowflake.
• FinancialTransactionsSample.csv- file to load data to the FINANCIAL_TRANSACTION table of Snowflake.
• WebEngagementsSample.csv - file to load data to the WEB_ENGAGMENT table in Databricks. Ensure that the csv file does not include a header line, and that the values provided adhere to the WEB_ENGAGEMENT schema.
• ExternalAccountsSample.csv- file to load data related to External Account. Do not make any changes to the header of the file.