OMS-Docker application processes

IBM provides out-of-the-box application-level processes that are used in IBM UrbanCode Deploy to deploy, update, or remove the entire IBM Sterling Order Management application as well as to update or restart the various application components. Each of these application processes is, in turn, composed of component processes.

The application processes that IBM provides out-of-the-box include:

• Activate Enterprise for Order Server - Activates the promising configuration for an enterprise.
• Build Customized Runtime - Builds the customized runtime image by applying the customizations to the runtime. This image is then used to deploy the EAR, agent server, and integration server.
• Configure OMS as Order Server - Used when performing an Order Server/Promising Server integration. The process configures an OMS deployment to act as an Order Server and is run after running the Deploy OMS Application process.
• Configure OMS as Promising Server - Used when performing an Order Server/Promising Server integration. The process configures an OMS deployment to act as a Promising Server and is run after running the Deploy OMS Application process.
  Note: This process should only be run on an OMS deployment that is non-sharded.
• Deploy OMS Application - Deploys the entire Sterling Order Management application and is composed of deployment processes for all of the components.
• Update OMS Application - Updates the application with the latest component versions. The process requires no downtime. The database and messaging queues are not brought down, and the application server, agent server, and integration server are updated.
• Wipe Deployment - Removes the deployment process for each component.

These application processes are constructed from component-level processes. You can use these processes as is, or you can modify these processes or create new processes to suit your needs.