Components are the centerpiece of the IBM UrbanCode™ Deploy deployment engine. Components associate deployable artifacts with processes that deploy
them.
- Define source types and identify artifacts
- In this step, you create a component. The component defines the agent to import the artifacts, and identify the type of artifacts and their location. A component can contain any number of artifacts, but they must all have the same source type.
- The source type identifies the artifacts that the component uses. The source type can be almost anything that is associated with a software project. Sources are defined with source-type plug-ins.
- Create versions
- Component versions are created when artifacts are imported into the CodeStation. Version history is maintained and components can be rolled back to earlier versions.
- Create component process
- Component processes consist of user-configured steps that operate on components, typically by deploying them. Process steps are provided by automation-type plug-ins. Processes can be created with the process design editor or by using the command-line interface.
- A process defines what IBM UrbanCode Deploy does with the component's artifacts. A process might consist of any number of steps, such as stopping and starting target servers and moving files. In addition to deploying components, processes can import artifacts and run various utility tasks.
The following diagram summarizes the basic steps for creating components:
