EGL Reference Guide for iSeries

Generating for Java

Choosing options for Java generation

Build descriptor options are set in build descriptor parts. To choose build descriptor options for Java generation, start the EGL editor and edit the build descriptor part.

When you begin editing a build descriptor part from the GUI, the EGL editor contains a pane listing all EGL build descriptor options. To limit the display to options that are applicable to a program generated in Java, select a category from the Build option filter drop-down menu.

Select each option you want, and set its value. The value can be literal, symbolic, or a combination of literal and symbolic You can define symbolic parameters in the EGL part editor; for details, see Editing general build descriptor options.

Two build descriptor options--genDirectory and destDirectory--let you use a symbolic parameter for the value or a portion of the value. For example, for the value of genDirectory you can specify C:\genout\%EZEENV%. Then if you generate for a Windows environment, the actual generation directory is C:\genout\WIN.

You do not need to specify all the options listed. If you do not specify a value for a build descriptor option, the default for the option is used when the option is applicable in the generation context.

If you have specified a master build descriptor, the option values in that build descriptor override the values in all other build descriptors. When you generate, the master and generation build descriptors can chain to other build descriptors as described in Build descriptor part.


Related concepts
Build descriptor part


Related tasks
Editing general build descriptor options
Generating Java wrappers


Related reference
Build descriptor options

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

To start a remote build server on AIX(R), Linux, or Windows 2000/NT/XP, 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):

  installDir\wstools\eclipse\plugins
  \com.ibm.etools.egl.distributedbuild\executables
  \ccu.cat.xxx
installDir
Directory in which WebSphere Studio is installed
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 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:

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

Generating Java wrappers

You can generate Java wrapper classes when you generate the related program. For details on how to set up the build descriptor, see Java wrapper.


Related concepts
Generation
Java wrapper


Related tasks
Building EGL output
Generating into a directory
Generating into a project


Related reference
Build descriptor options
Java wrapper classes
Output of Java wrapper generation


[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]