Starting a build server on iSeries®

The Remote Build Server is a program, named CCUBLDS, that runs as a job on the iSeries®. It listens on a tcp/ip port. Once started, it runs continuously until the job is canceled. The following command is an example of the command to start the build server job: 
SBMJOB CMD(CALL PGM(*LIBL/CCUBLDS) PARM('-p' '2600')) JOB(CCUBLDS) JOBQ(QSYS/QSYSNOMAX)

Here the server port is 2600, but any available port number can be used. The build server must be invoked by an administrator userid that is authorized to access user profiles.

Verifying the iSeries® Remote Build Server

After the build server has started, you should verify that it is running properly. At the Windows™ workstation where the prep step will be run, do as follows:
  1. In the plugin named com.ibm.etools.egl.distributedbuild, locate the directory containing the program ccubldc.exe. Add this directory to the PATH environment variable.
  2. Run the following command from the command line: 
    ccubldc -h host@port -au userId -ap password -b id -r 37 -k 1252
    host
    IP address of the iSeries® host machine
    port
    Port number of the build server
    userID
    Userid that the prep client uses
    password
    Login password for the userid on the iSeries® host
    The following is an example of the expected response: 
    05/03/09 14:58:56 (c) Copyright, IBM Corp. 2001 Copyright (c) 2002 Rational Software Corporation 
05/03/09 14:58:57 *** Success *** 
05/03/09 14:58:57 Command: id 
****************** Build Script Output Follows ***************** 
uid=926(USERID) gid=102(GROUPID) groups=102(GROUPID) 
****************** End Of Build Script Output ****************** 
05/03/09 14:58:58 *--------------------------------------------------------

Setting the language of messages returned from the build server

The build server on Windows™ returns messages in any of the languages listed in the next table, and the default is English.

Language Code
Brazilian Portugese ptb
Chinese, simplified chs
Chinese, traditional cht
English, USA enu
French fra
German deu
Italian ita
Japanese jpn
Korean kor
Spanish esp
To specify a language other than English, make sure that before you start the build server, the environment variable CCU_CATALOG is set to a non-English message catalog. The needed value is in the following format (on a single line): 
  shared_resources\eclipse\plugins
  \com.ibm.etools.egl.distributedbuild_version\executables\ccu.cat.xxx
shared_resources
The shared resources directory for your product, such as C:\Program Files\IBM\SDP70Shared on a Windows™ system or /opt/IBM/SDP70Shared on a Linux™ system. If you installed and kept a previous version of an IBM® product containing EGL before installing your current product, you may need to specify the shared resources directory that was set up in the earlier installation.
version
The installed version of the plugin. If more than one is present, use the one with the most recent version number, unless you have a reason to use an older version.
xxx
The code for the language of interest; one of the codes listed in the previous table

Security Manager

The Security Manager is a server program that the build server uses to authenticate clients that send build requests.

Setting the environment for the Security Manager

The Security Manager uses the following Windows™ environment variables:
CCUSEC_PORT
Sets the number of the port to which the Security Manager listens. The default value is 22825.
CCUSEC_CONFIG
Sets the path name of the file in which configuration data is saved. The default is C:\temp\ccuconfig.bin. If this file is not found, the Security Manager creates it.
CCU_TRACE
Initiates tracing of the Security Manager for diagnostics purposes, if this variable is set to *.

Make sure the CLASSPATH environment variable points at the EGLBATCHGEN.JAR file that was distributed with IBM Business Developer.

Starting the Security Manager

To start the Security Manager, issue the following command. There will be no visible return from this command because it starts the long-running security manager process only.
java com.ibm.etools.egl.distributedbuild.security.CcuSecManager

Configuring the Security Manager

To configure the Security Manager, use the Configuration Tool, which has a graphical interface. You can run the tool by issuing the following command: 
java com.ibm.etools.egl.distributedbuild.security.CCUconfig

When Configuration Tool is running, select the Client Items tab and add, update, or delete the combinations of host name, user ID, and password. The three-part definitions are encrypted and kept in persistent storage, in the file specified by CCUSEC_CONFIG, and remembered across sessions.