Previous Topic: Establish the Target Directory StructureNext Topic: Security Considerations

Using the Build Tool Server

Using the Build Tool Server

The Build Tool server runs either as a system-started daemon or as a manually started task. The server mode of the Build Tool is designed to handle remote builds and communicate output views to its clients. The server receives requests from Build Tool clients running on Windows, UNIX, and Linux. These clients are not directly logged on to the server machine. This allows Build Tool client users to perform build functions across the network. However, the clients perform all the functions of the Build Tool on local machines without a server.

For UNIX and Linux platforms, the server mode can be started at boot time by adding the S99bldtool script to the /etc/rc3.d directory on UNIX and/etc/rc.d directory on Linux or adding this script to the Cron table. The Build Tool server opens a listening socket using the default port 7776. This listener port can be changed by adding a -i nnnn variable, where nnnn is a port number. If the listener port is changed, it must be changed in both the client and the server.

You can manually start the Build Tool in server mode, passing an unused port to communicate to the individual server. You can run a server for an individual user, separate from the system server. It is flexible and you can start the Build Tool multiple times, each using a unique port listener address.

The Build Tool Server is invoked manually using the following command syntax:

Windows
%GENxx%gen\bldtool.bat -c SERVER

Or

%GENxx%gen\bldtool.bat -c SERVER  [options]

Note: xx refers to the current release of CA Gen. For the current release number, see the Release Notes.

Unix, Linux, and NonStop
$IEFH/bt/bldtool -c SERVER

Or

$IEFH/bt/bldtool -c SERVER  [options]

The options are as follows:

-i

Port number. This is the port number that will be used to connect Build Tool Clients to this server.

Default: 7776

There are several possible modes of the server. A Build Tool daemon could be started by the system at boot time and another Build Tool server started manually (batch). Clients use the daemon copy but can also access the batch copy by specifying the batch port. Starting the server as a batch job is most useful when there is no need for a full time server or you want to isolate your work on a remote platform.

The server receives requests from remote clients and queues them. The Build Tool server then scans the input queue looking for RMT files to split. The splitting of multiple remote files is run simultaneously.

After performing a split, the server looks for the highest priority task in the queue. The priority is as follows:

  1. Building DDL
  2. Building Referential Integrity (Cascade)
  3. Building Operations Libraries
  4. Build Load Modules

The build process is sequential for each model. If the build request contains more than one model, the builds are processed in parallel.

The FTP server on UNIX is used to confirm user ID and password for remote UNIX Build Tool server sessions. Ensure that the FTP daemon is running on the UNIX platform you want to access as a remote Build Tool server. However, the Build Tool Client login credentials are not checked when the Build Tool Server is running under the Windows platform.