Running the Jazz Build Engine

Setting up the Jazz™ Build Engine is optional.
Before performing the setup steps, review Lesson 8: Team Builds in the tutorial, Getting Started with Rational Team Concert. The Jazz Build Engine is installed when you install the Jazz Team Server. Register a build engine instance using the Rational® Team Concert client. Use the instructions in the tutorial to create a build engine. Before starting a build engine, create an encrypted password file for the build engine to use to prevent casual observation.
You can complete these steps now, or when you decide to run the Jazz Build Engine on z/OS®. This step is required only if you decide to execute builds on z/OS.
  1. Configure member BLZBPASS in hlq.SBLZSAMP using the instructions contained in the sample JCL. This password file can also be used in your build scripts. Submit the modified JCL. The job must end with a return code 0. Do not save the modified JCL with any password associated with it.
  2. Configure member BLZBENG in hlq.SBLZSAMP using the instructions contained in the sample JCL.
    1. Submit the modified JCL. The job must remain active and the following messages must end the STDOUT: 2008-05-27 11:08:46 Running build loop... and 2008-05-27 11:08:46 Waiting for request. If these messages are not shown in the STDOUT, check the SYSOUT to identify the issues at the initialization process of the build engine.
    2. When you submit a build request to this build engine from Rational Team Concert, a message similar to the following will be displayed:2008-07-24 20:00:38 Found a request for build definition "SampleBuild."
    3. When you want to terminate the build engine, cancel or purge the job.
Notes:
  1. Make sure that the WebSphere® Application Server user ID has read access for the buildData directory folder that hosts the build scripts, and write access for the folder that is used to create the build artifacts. These folders are defined in the build definition and in the build scripts.
  2. When you compile source codes using the Jazz Build Engine running on z/OS, you need to be aware of the difference in the default file encoding used by each platform. For example, if you develop Java™ programs on Windows®, which uses Cp1252 as the default file encoding, the source codes will not compile on z/OS, which uses Cp1047 as the file default encoding, unless you specify -encoding Cp1252 to Java compiler options.

Feedback

Did this help? You can provide feedback at Jazz.net (registration required): Comment in the forums or submit a bug