Skip to content

Shared Mule library that provides reusable flows, resources and configuration settings common for all applications.

License

Notifications You must be signed in to change notification settings

jpontdia/common-core

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

63 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Common configurations for Mulesoft services

Powered by Unit test Code coverage Build Build job

Shared Mule library that provides reusable flows, resources and configuration settings common for all applications.

This project follows the standards defined in the Development Process Document in Anypoint Exchange. The details to compile and package the asset are in the Build Environment section.

Table of contents

  1. Description
  2. Salesforce
    1. JWT configuration
    2. Connector configuration
  3. Snowflake

Description

Multiple common components like flows, sub-flows, etc. to be re-used across the Mule projects. For example, common sub-flows can be used for logging, error-handling, shared business logic, etc.

  1. Reusability: Common assets allow you to reuse existing components across multiple projects. This reduces development time and effort since you don't need to recreate the same functionality from scratch each time. By leveraging common assets, you can ensure consistency, standardization, and maintainability across your projects.

  2. Consistency: When you have common assets, you establish a consistent development approach and design patterns across different projects. This promotes uniformity and makes it easier for developers to understand and maintain the codebase. It also helps in enforcing best practices and following established architectural guidelines.

  3. Efficiency: By having a library of common assets, you can accelerate development cycles and deliver projects faster. Instead of reinventing the wheel, developers can focus on building business-specific logic while leveraging existing, tested, and reliable components.

  4. Maintainability: When changes or updates are required, having common assets simplifies the maintenance process. You only need to modify the common asset in one place, and the changes will propagate to all projects using it. This reduces the effort required to fix issues, implement enhancements, or apply security patches.

  5. Scalability: Common assets enable scalability by providing a foundation for building complex integration solutions. They allow you to easily add new features or functionalities to your projects without starting from scratch. As your organization grows and requirements evolve, having reusable components becomes even more crucial for efficiently managing the integration landscape.

  6. Collaboration: Common assets foster collaboration among developers and teams. When everyone works with the same set of components, it promotes knowledge sharing, reusability, and collaboration across projects. Developers can learn from each other's work, share insights, and contribute to improving the common assets, which ultimately benefits the entire organization.

In summary, having a project with common assets like flows, configurations, and other reusable components brings numerous benefits, including reusability, consistency, efficiency, maintainability, scalability, and collaboration. It empowers developers to build integration solutions more effectively, accelerates development cycles, and ensures high-quality and reliable outcomes.

Salesforce

Salesforce JWT configuration

Find the instrucctions in the Development Process Document in Anypoint Exchange.

Salesforce connector configuration

Connection properties:

Property Description
salesforce.keystore Keystore with the cetificate to connect with Salesforce.
salesforce.consumerkey Connected App Consumer Key
salesforce.principal The user created in Salesforce that has the profile assigned to the Connected App
salesforce.storepassword The password to open the keystore
salesforce.certificatealias The alias of the certificate inside the keystore
salesforce.tokenendpoint The URL to generate the authentication token
salesforce.audienceurl test.salesforce.com for a sandbox environment and login.salesforce.com for production.

Snowflake

Connection properties:

Property Description
snowflake.accountname Account name that was provided when registering for the Snowflake account
snowflake.warehouse Name of the Snowflake warehouse to use
snowflake.database Snowflake database to connect to
snowflake.schema Snowflake database schema to use
snowflake.user Snowflake database username used to initialize the session
snowflake.password Snowflake database password used to authenticate the user
snowflake.role Role assigned to the user

---

About

Shared Mule library that provides reusable flows, resources and configuration settings common for all applications.

Resources

License

Stars

Watchers

Forks

Packages

No packages published

Languages