Building IBM Sterling Order Management System deployable packages
For more information about exporting extensions from your developer toolkit environment, see Exporting extensions from your developer toolkit environment.
After you export the extensions into an archive, transfer the package to your drop server so that the packages can be retrieved by the IBM UrbanCode® Deploy Selfserv tool tool for deployment into an IBM Sterling Order Management System.
For more information about transferring the generated package, see Transferring deployable packages to the deployment drop server.
- Build extensions for building modified extensions such as templates, resource files, customized web pages, entities, and more.
- Build resources extensions for building modified user interface resource files, such as themes,
CSS, configuration resources, data types, extended APIs, events, XSL templates, and more. The
process rebuilds the resources.jar Java archive (JAR) file, which includes the
resource extension files. The process rebuilds this archive by using the
deployer.sh utility from the INSTALL_DIR/bin directory.
The following directories are the directories for resource extension files:
- Resource XML files are in the INSTALL_DIR/extensions/global/template/resources directory.
- Event XML files are in the INSTALL_DIR/extensions/global/template/event directory.
- XSL files are in the INSTALL_DIR/extensions/global/template/xsl directory.
- Build database extensions for building modified database extensions. The process rebuilds the entities.jar JAR file by using the deployer.sh utility from the INSTALL_DIR/bin directory. All database extension files need to be stored within the INSTALL_DIR/repository/entity/extensions directory.
- Build template extensions.
When a deployable package is created, transfer the package to your drop server so that the packages can be retrieved for deployment into an IBM Sterling Order Management System.