IBM UrbanCode Deploy

IBM UrbanCode Deploy, formerly known as Udeploy, is a GUI-based deployment automation tool that provides you with the tools you need to orchestrate and automate the installation and deployment of IBM Sterling Order Management. It facilitates fast deployment, and enables you to deploy as often as you like, on demand, on a schedule, and with self-service, while shortening the time to market. UrbanCode Deploy orchestrates and automates the deployment of applications, databases, and configurations into development, test, and production environments, and helps to drive down cost and to speed time to market with reduced risk.

To facilitate the automated installation and deployment of Sterling Order Management, IBM provides a set of sample application processes and component processes that are used to deploy the various Sterling Order Management application components. The application components consist of a database component, application server component, JMS component, Runtime component, agent server component, integration server component, Elasticsearch Server component, and Promising Server component. You can use these out-of-the-box processes as is or you can use UrbanCode Deploy's process editor to customize the processes to suit your needs.

UrbanCode Deploy models the deployment as applications deployed on different environments, and these applications have certain processes associated with them. Applications are the topmost abstraction and have application processes that are typically run in day-to-day operations, and these application processes, in turn, initiate the component deployments. Each application consists of various components (such as application server, database, and JMS) and these components can also have processes that are associated with them. For example, the application server component has associated processes that include deploying the application server and restarting the application server. The component processes are used to construct the application processes.

The following briefly describes some of the basic UrbanCode Deploy terms that are used throughout this documentation:

• Components: Components represent deployable items.
• Applications: An application is a logical group of components that are deployed together. Applications have processes, but their steps usually start processes or modify resources. An application contains environments, which describe all of the deployment locations that are needed in your deployment process, and you run application processes to deploy components to environments.
• Processes: A process plays a coordination role. Processes are authored with a visual drag-and-drop editor, and composed of various steps. For example, to deploy the application, you might run a process that is called Deploy. This Deploy process would, in turn, execute the steps and perform the deployment.
• Environments: An environment is a collection of resources that host the application. Environments typically include host systems and UrbanCode Deploy agents. When a deployment is run, it is always done in an environment. While environments are collections of resources, resources can very per environment.
• Resources: Resources represent the relationship between components, the agents that deploy the components, and the target deployment environments. You create groups to represent target servers and environments, attach the agents that deploy to the environments, and attach components to the agents that run the processes.
• Agents: An agent is a lightweight process that runs on a target host and communicates with the UrbanCode Deploy server.

For detailed information about UrbanCode Deploy, refer to the UrbanCode Deploy documentation.