Starting a build server on AIX, Linux, or Windows 2000/NT/XP

To start a remote build server on AIX, Linux, or Windows 2000/NT/XP, enter the ccublds command in a Command Prompt window. The syntax is as follows:

where

-p

Specifies the port number (portno) that the server listens to, to communicate with the clients.

-V

Specifies the verbosity level of the server. You may specify this parameter up to three times (maximum verbosity).

-a

Specifies the authentication mode:

0

The server performs builds requested by any client. This mode is recommended only in an environment where security is not a concern.

2

The server requires the client to provide a valid user ID and password before accepting a build. The user ID and password are first configured by the owner of the host machine where the build server runs. You do the configuration by using the Security Manager described below.

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):

  installationDir\egl\eclipse\plugins
  \com.ibm.etools.egl.distributedbuild\executables
  \ccu.cat.xxx

installationDir

The product installation directory, such as C:\Program Files\IBM\RSPD\6.0. If you installed and kept a Rational Developer product before installing the product that you are using now, you may need to specify the directory that was used in the earlier install.

xxx

The language code being supported by the build server; 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 *.

Starting the Security Manager

To start the Security Manager, issue the following command:

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 Server Items tab. Using the button 'Add...', To add the user that you want the build server to support, click the Add ... button. You must define a password for the user ID. You can define the following restrictions and privileges for the user:

• The locations, that is, the values of the -la parameter to ccubldc command, that this user can specify. Different locations are separated by semicolons.

• The name of the build script that this user can specify. (The EGL build plan only uses the javac command as a build script.)

• Whether or not this user can send build scripts from client, that is, use the -ft parameter of ccubldc command. (The EGL generator does not use the -ft parameter. You would specify this parameter if they were using the build for purposes other than preparing Java-generation outputs.)

These definitions are kept in persistent storage, in the file specified by CCUSEC_CONFIG, and are remembered across sessions.

Related concepts
Build script
Build server

Related tasks

Syntax diagram