Starting a build server on AIX, Linux, or Windows platforms

A build server is available on AIX®, on 32-bit Linux, and on 32-bit Windows platforms.

To install the build server, follow the general EGL installation instructions on the machine where the build server will run. For details, see "Installing the EGL runtime code for Java."

To start a remote build server on AIX, Linux, or Windows platforms, enter the ccublds command in a Command Prompt window. The syntax is as follows:
Syntax: ccublds -p <portno> [-V...] [-a {0|2}]
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):
  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 *.

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 output.)
These definitions are kept in persistent storage, in the file specified by CCUSEC_CONFIG, and are remembered across sessions.

Feedback