Legacy platform

Self-service deployment with the IBM UrbanCode Deploy Selfserv tool

Use the IBM® Sterling Order Management System self-service process to deploy changes for your IBM Sterling Order Management System service. You must use the IBM UrbanCode® Deploy Selfserv tool when you need to deploy changes for IBM Sterling Order Management System.

With this tool, you can deploy your custom releases and fixes into your IBM Sterling Order Management System environments without the need to open service requests for IBM to deploy your changes. This self-service process provides you with a best practice approach for deploying changes with minimal to no interaction by users or administrators of the target deployment environment. This approach also minimizes the effort and troubleshooting that is required by you, or your System Integrator, during the deployment process. In addition to deployments, you can also use the tool to complete other tasks for your IBM Sterling Order Management System product service.

The self-service deployment process provides you, or your System Integrator, with the ability to use the IBM UrbanCode Deploy Selfserv tool to deploy packages into each IBM Sterling Order Management System environment. By using the IBM UrbanCode Deploy Selfserv tool, you, or your system integrator, can complete deployment-related tasks and view a consolidation of environment information through the IBM UrbanCode Deploy Selfserv tool user interface. For instance, you can view the current versions of deployed packages, deployment history, server status, audit trails, console logs, and more. You do not need to use any command line commands or implement scripts to complete deployments into your development environment or quality assurance environment.

Important: You can use the self-serve deployment process through UCD to deploy Sterling Order Management System into development, quality assurance, pre-production, and production environments. Even after the production site is accessible to customers, you can continue to use UCD to deploy your changes into the production environment.

Available self-service deployment operations

The IBM UrbanCode Deploy Selfserv tool is set up and configured by IBM to enable you to complete specific self-service operations. To complete any of these operations, you do not need to configure any properties file or environment settings file to specify your target IBM Sterling Order Management System environment details.

When you are using the tool, you must select the process, or operation, that you want to run. The processes that are available for you to run are based on the IBM Sterling Order Management System product service application and components that are available for you to access.

Application Process Version required Description
IBM Sterling Order Management System Deploy Yes Build and deploy an enterprise archive (EAR) that is based on the specified deployment.jar build artifact.
  Process Version required Description
IBM Sterling Order Management System Build Customized Runtime Yes Build a deployable customized version of the runtime component for the IBM Sterling Order Management System based on a deployable package. This customized runtime includes an enterprise archive (EAR) that is based on deployment.jar within the specified deployable package.
IBM Sterling Order Management System Update OMS Application Yes Deploy a customized runtime component version to update an IBM Sterling Order Management System application.

Self-service deployment process

The IBM Sterling Order Management System self-service deployment process and IBM UrbanCode Deploy Selfserv tool is built upon IBM UrbanCode Deploy. IBM UrbanCode Deploy is a stand-alone application that provides core deployment services. This application includes an application server, database, workflow engine, security services, deployment agents, and component and application configuration tools. When you use the IBM UrbanCode Deploy Selfserv tool, an agent process runs on your target IBM Sterling Order Management System environment to communicate with the IBM UrbanCode Deploy server.

For more information, see Build and deployment process.

Deployment and version history

As part of managing your deployments, the self-service deployment process tracks and maintains a version history archive of the packages, or component versions, that you use to update an application. These packages, or component versions, are stored within CodeStation, the artifact repository for IBM UrbanCode Deploy Selfserv tool. You can use the IBM UrbanCode Deploy Selfserv tool user interface to import your deployable packages into CodeStation for storage. When you import a package into CodeStation, a complete copy of the package is imported by default. Your original package on your Drop Server is not changed or moved. When the deployment process runs, the imported package is downloaded. If the package is not available within CodeStation, your deployment can fail. By storing your deployable packages within CodeStation, you can review, validate, and improve the management of the packages with the IBM UrbanCode Deploy Selfserv tool user interface.
Note: If you need to revert your component to an earlier state, you can deploy a previous version of the component to replace the current version. For instance, if you need to remove a customization that was deployed before it was ready.