This topic explains the general procedure you might use to define and configure the building blocks for your release process, including the environments that support your release life cycle, applications supporting the release deployment, and finally, the routes and policies that enable you to coordinate the release workflow.
This topic includes the following sections and use cases:
Create all the servers necessary for your release process on all phases.
For more information, see Managing servers.
Create environments that you are planning to use during your product release life cycle.
For more information, see Managing environments.
Create all the components necessary for your release process on all phases.
For more information, see Managing components.
Create and then assign properties to the components.
For more information, see Create properties configuration.
Map components to external objects.
For more information, see Managing components.
Note
If an application depends on components in a separate application, the components in the other application are referred to as remote components. For example, the database component for an application named TravelTime might be supplied by a separate application named Oracle. In this case, the TravelTime application refers to the remote component in the Oracle application.
Create a property and assign components or servers to the property.
For more information, see Managing properties.
Allow modification of property value during the work task creation or request execution.
Create an application for the release.
For more information about applications, see Managing applications.
Add the environments that the application will go through during the release process.
For more information about environments, see Managing environments.
Add components.
For more information about components, see Managing components.
Associate components with the environments.
For more information, see Associating components with environments.
Note
An application might have a three-tier architecture, in which case a component could be an application server, a database, and a load balancer.
Create routes to determine the order in which environments are accessed by the application.
For more information, see Managing routes.
Create a plan template to structure the release plan of your software.
For more information, see Managing plans.
Add stages (Development, QA, Staging, Production and so on) to the plan template.
For more information, see Managing plans.
Create a plan to organize the software release process.
For more information, see Managing plans.
Add routes to a plan.
For more information, see Managing plans.
Create a plan run to assemble requests from different applications and different environments in an executable flow.
For more information, see Managing plan runs.
Create deployment windows or deployment windows series to manage access to the environments.
Create a package to manage binary files for applications.
For more information, see Managing packages.
Add existing properties to the package or create new properties for the package.
For more information, see Managing packages.
Add references to the package.
For more information, see Managing packages.
Assign packages to an application.
For more information, see Managing packages.