Releasing the Plug-in | ||
---|---|---|
Previous | Next | |
Testing the Plug-in | Using Your Plug-ins |
The plug-in binary is a Jar file that will be deployed in a Semarchy Convergence for MDM instance. Once deployed, the plug-in becomes available for design and run-time.
When the plug-in is tested, or when a new version is available, you can generate the plug-in binary.
To generate the Plug-in Binary:
c:\temp
.
com.acme.phoneStandardizer
.
The jar for the plug-in is created in a
plugins
folder under the selected destination directory. The generated jar file is named after the plug-in ID and version number.
Warning: When selecting the plug-ins and fragments to deploy, make sure to select only the plug-in, and not the JUnit test case fragments as they are not needed for running the plug-in.
If the plug-in was modified or fixed, before generating the new version of the plug-in binary, increment the plug-in version
To increment the Plug-in version:
plugin.xml
file to edit it.
1.0.0
, then the first patch for this plug-in would be
1.0.1
.
You can now generate the plug-in binary .
Note: As the generated jar file is named after the plug-in ID and its version number, you can preserve in this directory the successive versions of the plug-in.
Important: To deploy a plug-in in a Semarchy instance, you must connect with a user that has the Plug-ins Administration Read/Write privileges, or with a Semarchy administrator user (semarchyAdmin role).
To deploy the plug-in binary:
com.acme.phoneStandardizer_1.0.0.jar
.
The plug-in now appears in the list, and can be used in the models and the integration jobs.
Previous | Top | Next |
Testing the Plug-in | Using Your Plug-ins |