White Paper

Build integration overview: Rational Team Concert and IBM UrbanCode Deploy (standard and z/OS builds)

Print

Build integration overview: Rational Team Concert and IBM UrbanCode Deploy

Highlights:

  • Overview topology of the main build-related interactions between the IBM UrbanCode Deploy and Rational Team Concert servers.
  • Overview of two common build and deployment processes for mainframe and non-mainframe files

Topology introduction

The following topology diagram is a summary of the main interactions between the IBM® Rational Team Concert™ (RTC) and IBM® UrbanCode™ Deploy (UCD) systems and their various components and target platforms during different types of build process. Arrows show the main points of communication during build and deployment phases, though many other parts communicate at other times.

At the top, several types of clients access the RTC and UCD servers, including users on web browsers and command-line clients.

Below the clients, the CLM system contains the Jazz Team Server and Change and Configuration Management (what most people call RTC) systems. The RTC system contains source code that is stored in components, which are stored in streams. The RTC server also maintains build definitions, which describe how to build deployable packages from source code, and build engines, which are virtual representations of the build agents that build the source code. These build agents, including Build Forge Agents and Jazz Build Engines, are shown below the RTC server.

The UCD server is shown to the right of the RTC server. It contains virtual representations of applications and of the components themselves. On the RTC server, the components contain source code, but on the UCD server, components represent built deployable artifacts and the automated processes that deploy them. At the right-hand side of the topology, a UCD agent connects to the UCD server. UCD agents like this one run on the target environments that host the applications and their components.

UCD-RTC build topology overview

Standard build and deployment process

Building non-mainframe files, such as WSDL and JAR files, as well as some mainframe files, such as USS files, follows this general process:

  1. A client requests a build from RTC.
  2. Using the build definition for instructions, the Jazz Build Engine retrieves source code from the stream and builds a deployable package.
  3. The UCD component, which contains information about where to retrieve the deployable artifacts, triggers a manual or an automatic version import.
  4. The UCD agent that is designated in the UCD component definition retrieves the deployable artifacts from RTC.
  5. The agent creates a UCD component version that includes the artifacts.
  6. A client requests an application deployment from the UCD server.
  7. The specified UCD agent for the deployment checks in with the server.
  8. The application process runs, delivering deployable artifacts and automation instructions (in the form of component processes) to one or more agents.
  9. The agents run the automation instructions to deploy the application components.

See the following topology diagram:

UCD-RTC build topology, distributed case

z/OS build process

When the RTC server builds mainframe packages, it creates deployable packages that it pushes to component versions on the UCD server.

  1. A client requests a build from RTC.
  2. RTC builds the artifacts with a z/OS dependency build.
  3. RTC stores the results as a deployable package in RTC.
  4. Using the UCD z/OS toolkit, the RTC server pushes the deployable package to a component version in UCD.
  5. A client requests an application deployment from the UCD server.
  6. The specified UCD agent for the deployment (in this case, an agent on z/OS) checks in with the server.
  7. The application process runs, delivering deployable artifacts and automation instructions (in the form of component processes) to one or more agents.
  8. The agents run the automation instructions to deploy the application components.

See the following topology diagram:

UCD-RTC build topology, mainframe case