Exporting custom extensions from a developer toolkit environment

You can create and export an extensions.jar archive from your developer toolkit environment at any point. For instance, export extensions when you need to package your customizations for deployment into your environments, or to deploy extensions into another developer toolkit environment, or to back up your extensions.

Procedure

In a command-line utility, go to the runtime/bin directory of your developer toolkit environment.

Remember: In case of docker-based developer toolkit, runtime directory is the extracted runtime directory.
Run the following command to create the extensions.jar archive:
./sci_ant.sh -f ../devtoolkit/devtoolkit_extensions.xml export
This command creates a customization package extensions.jar inside the parent directory of your existing developer toolkit environment file structure.
Note: If you have customized build.properties files in the bin directory, you must pass the flag -Dincludebuildprops=true in the command while exporting the extensions to include the customized build.properties files.
As part of the extraction process, the export tool performs certain validations on your customizations to ensure that they conform to the Sterling Order Management System Software cloud deployment standards. For more information about the validations performed by the export tool, see Validations.

What to do next

If you have exported your custom extensions to include the extensions within another developer toolkit environment, import the exported JAR archive into the other developer toolkit environment. For more information about importing the exported custom extensions into an existing developer toolkit environment, see Importing custom extensions into the Developer Toolkit environment.
If you exported your custom extensions to back up your extensions, upload your exported JAR archive into your source code repository. For more information, see the documentation for the tools that you use for working with your repository.