Share Applications
|
Standard Support for Mule 4.1 ended on November 2, 2020, and this version of Mule reached its End of Life on November 2, 2022, when Extended Support ended. Deployments of new applications to CloudHub that use this version of Mule are no longer allowed. Only in-place updates to applications are permitted. MuleSoft recommends that you upgrade to the latest version of Mule 4 that is in Standard Support so that your applications run with the latest fixes and security enhancements. |
When working on a team, a Mule runtime engine project increases in size, increases in its number of developers who need to collaborate, and the need to run the project in both test and production environments. However, you can offset this project growth by sharing applications.
Sharing applications is an opportunity for splitting work across teams, whether these teams work on the same overarching project or on different projects that they intent for reuse. Because applications are stored in self-contained archives, they can be shared via a simple file or web server.
To share applications, follow these steps:
-
Document the name and content of the properties file that each application is expecting to use.
The administrators who deploy and run the Mule application can encrypt the properties file as detailed in Secure Configuration Properties. Administrators must keep the decryption key of the properties file secure.
-
Generate the file used to share the application in one of the following two ways:
-
Export the application from Anypoint Studio and generate a deployable archive
.jarfile. -
Package your application into one of the following three types of
.jarfiles using the Mule Maven Plugin:-
Deployable archive
.jarfile to deploy into a running Mule runtime engine. -
Mule app package
.jarfile to import into Studio. -
Mule app lightweight package
.jarfile to then import it into Studio.
-
-
-
Share the
.jarfile with other developers, as appropriate.