Legacy platform

Building IBM Sterling Order Management System deployable packages

After you complete developing custom extensions, fixes, or upgrades for an IBM Sterling Order Management System service, you must build your changes into a deployable package. After you create a deployable package, you can transfer the package to your drop server and then deploy the package and changes into your IBM Sterling Order Management System environments.
Use the export capability of your IBM Sterling Order Management System developer toolkit environment that is based on the IBM Sterling Order Management System Developer Toolkit to export your custom extensions into a deployable extensions archive.

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.

When you create a deployable package, the package must conform to the required technical specifications for IBM Sterling Order Management System deployable packages. The customized deployable package must be built only using the developer toolkit for IBM Sterling Order Management System, which matches your current cloud version of IBM Sterling Order Management System.
  • 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.
    • JSP and JavaScript files are in the INSTALL_DIR/extensions/global/template/webpages 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.