Corporate Info | News | Solutions | Products | Partners | Services | Events | Download | How To Buy
BEA eLink Business Process Option (BPO) Doc Home | BPO Configuration Guide | Previous Topic | Next Topic | Contents | Index

Creating the eLink Platform Configuration Files

This section provides instructions for creating the eLink Platform configuration files for the Business Process Option application. This includes specific instructions for using the eLink Platform Configuration utilities to generate these files. Topics include:

- Overview

- Step 1: Gather Your Configuration Information

- Step 2: Create a New Data Configuration File

- Step 3: Create a New Configuration Setup File

- Step 4: Configure the Application Properties

- Step 5: Add the Machine to the Configuration Tree

- Step 6: Configure the Machine Properties

- Step 7: Add and Configure the Server Groups

- Step 8: Configure the Servers

- Step 9: Configure the Optional Components

- Step 10: Generate the Configuration Files and Scripts

- Step 11: Testing the Configuration

Overview

BEA eLink Platform provides two utilities to assist you in the configuration process. These are:

- Configuration Data Editor - This utility enables you to quickly create and/or modify the Data Configuration file for your Business Process Option Server machine. The Configuration Expert uses this file to create the configuration setup file for generating the BEA eLink Platform configuration files.

- Configuration Expert - This utility enables you to create and modify the BEA eLink Platform Business Process Option configuration files without having to manually create and edit these files. You can also use Configuration Expert to perform a test startup of the new configuration.

Configuration Expert Quick Reference Guide, provides an overview of the main windows and navigation procedures for these utilities.

Note: For more detailed information and instructions on using Configuration Expert, refer to the online document BEA TUXEDO Builder Configuration Expert provided in PDF form with the BEA eLink Platform 1.2 release. This document provides instructions for using Configuration Expert to specifically configure the Business Process Option application.

Note: The examples in this section are taken from a UNIX platform installation. If you are running the Configuration Expert under Windows NT, any local paths, such as the output directory, must be specified following the standard DOS convention of <drive_letter>:\<path>. Any pathnames you specify for the servers must follow the naming convention of the operating system under which the Business Process Servers are to be running.

The eLink Platform Business Process Option Configuration Files

The Configuration Expert uses the information you specify in the configuration screens to generate the following configuration files:

- <application_name>.ubb - This is the eLink Platform UBB file for your new Business Process Option configuration. This file is located in the output directory you specify in the Location field of the Configuration Expert New Configuration screen (see Figure 6-1 in Step 3: Create a New Configuration Setup File).

- <application_name>.checklist - This specifies the tasks to be completed (on each machine) to set up the application.

- tux_start.sh - This is the generated startup script for your new eLink Platform and Business Process Option configuration. This file is located in the output directory you specify in the Location field of the Configuration Expert New Configuration screen (see Figure 6-1).

- tux_stop.sh - This is the generated shutdown script for your new eLink Platform and Business Process Option configuration. This file is located in the output directory you specify in the Location field of the Configuration Expert New Configuration screen (see Figure 6-1).

- crtlog.sh - This is a UNIX script file that creates the device list file for the BEA eLink Platform. This file is located in the output directory you specify in the Location field of the Configuration Expert New Configuration screen (see Figure 6-1).

Overview of Configuration Procedures

The steps involved in creating the BEA eLink Platform configuration files for the Business Process Option are as follows:

Step 1: Gather Your Configuration Information

Step 2: Create a New Data Configuration File

Step 3: Create a New Configuration Setup File

Step 4: Configure the Application Properties

Step 5: Add the Machine to the Configuration Tree

Step 6: Configure the Machine Properties

Step 7: Add and Configure the Server Groups

Step 8: Configure the Servers

Step 9: Configure the Optional Components

Step 10: Generate the Configuration Files and Scripts

Step 11: Testing the Configuration

Detailed instructions for each of these steps are provided in the following sections.

Step 1: Gather Your Configuration Information

Before you begin the configuration process, you can gather the information you will need to complete the configuration. Configuration Information Checklist, in this manual provides a checklist you can use to complete this step.

Step 2: Create a New Data Configuration File

Before you can create a new configuration, you must create a new Data Configuration file for the server machine(s) you intend to add to the new eLink Platform configuration. This file contains some basic information about the machine(s) and informs the Configuration Expert of the existence of the machine(s).

To create a new Data Configuration file:

1. Start the Configuration Data Editor utility.

   On a UNIX platform:

   Enter the following commands at the operating system prompt:

   >     cd <$TUXDIR>/eLink/ConfigExpert/bin

   >     ./ConfigEditor &

   On a Windows NT platform:

   Click Start->Programs->BEA eLink->Configuration Expert Setup.

   This displays the Configuration Data Editor startup screen.

   Note: Refer to the section entitled, Starting the Configuration Data Editor, in Configuration Expert Quick Reference Guide, for an illustration of the Configuration Data Editor startup screen.

2. Go to the Configuration Data Editor main window.

   Choose File->New to display the Configuration Data Editor main window.

   Note: Refer to Starting the Configuration Data Editor, in Configuration Expert Quick Reference Guide, for an illustration of the Configuration Data Editor main window.

3. Enter your machine information.

   Enter the following information in the fields:

   - Name - This is the name of the machine you are configuring with Configuration Expert. This should be the hostname as it appears on the network. This is an identifier for Configuration Expert only, and should match the name you specify in the hostname field.

   - Hostname - This is the name of the machine on which the Business Process Option Servers will run.

   - Description - Enter a brief description of the application for which you are configuring this platform (in this case, the Business Process Option).

   - Operating System - Select the appropriate operating system from the pulldown menu to the right of this field.

   - TUXEDO Directory (TUXDIR) - Enter the full absolute pathname for the location of your eLink Platform installation.

   - Tuxedo version - Select Tuxedo 6.5 from the pulldown menu to the right of this field.

4. Add the machine to the Machines list.

   After entering all of your machine specification information, click Add. The name of the newly defined machine is added to the Machines list on the left.

   Note: Repeat steps 3 and 4 for any other machines that are part of the Business Process Option and eLink Platform installation.

5. Choose File->Save to save your machine specifications.

6. Choose File->Exit to quit the Configuration Data Editor.

Step 3: Create a New Configuration Setup File

After creating a new machine specification with the Data Editor, the next step is to create a new application configuration setup file. This file is not the eLink Platform configuration file you will generate in the final steps of the configuration process. This file simply provides a framework for collecting the information you enter into the Configuration Expert screen forms. When you have completed the configuration and initiate the file generation process, Configuration Expert reads this file and generates the actual eLink Platform configuration files.

To create a new configuration setup file:

1. Start the Configuration Expert utility.

   On a UNIX platform:

   Enter the following commands at the operating system prompt:

   >     cd <$TUXDIR>/eLink/ConfigExpert/bin

   >     ./ConfigExpert &

   On a Windows NT platform:

   Click Start->Programs->BEA eLink->Configuration Expert.

   This displays the Configuration Expert startup screen.

2. Choose File->New.

   This displays the Create New Configuration window, as illustrated in Figure 6-1.

   Figure 6-1 Configuration Expert Create New Configuration Window

3. Enter the name of your application (in this case, BPO) in the Name field in the Create New Configuration window.

   The Configuration Expert creates a file of this name, with the suffix .ce. For example: BPO.ce.

4. Enter the location in which you want the new configuration file to reside.

   In the Location field, enter the full absolute pathname for the location in which the new configuration file should be written. Do not include the filename - this specifies the location of the file, only. It is recommended that you select the default. To do this, click on the elipsis button (...) to the right of the location field. Select the default. Click OK to submit your selection and go back to the Create New Configuration window.

5. Click OK to submit your specifications and go to the Application Properties (General) window.

   After you click OK to start a new setup file, the Application Properties window displays, with the General tab selected. The next step in creating a new setup file is to configure the Application Properties. The following section provides instructions for this procedure.

Step 4: Configure the Application Properties

The next step is to configure the Application Properties. The Application Properties define such information as the application name, the IPC Key, level of system access, number of services, and location of the server environment files.

To configure the Application Properties:

1. Go to the Application Properties window and select the General tab.

   There are several ways to go to the Application Properties window:

   - If you have just created a new application configuration file using the New Configuration window, click OK in the New Configuration window. This leads directly to the Application Properties window with the General tab selected.

   - From the Configuration Expert main window, select the application in the Current Application panel, then click the Props button to display the Application Properties window with the General tab selected.

   - From the Configuration Expert main window, select the application in the Current Application panel, then choose Edit->Properties to display the Application Properties window with the General tab selected.

     Figure 6-2 illustrates the Application Properties window with the General tab selected.

     Figure 6-2 Configuration Expert Application Properties General Window

2. Enter your Application Properties General information.

   The Application Properties (General) window contains the following fields:

   - Application Name - This is the eLink Platform application name (in this case, the BEA Business Process Option). This corresponds to the UBB file parameter DOMAINID.

   - IPC Key - This is the Interprocess Communication Key. This is a unique application identification key that all eLink Platform servers and clients use to identify and communicate with the application. Each eLink Platform application must have a unique IPC Key. The corresponding UBB file parameter is IPCKEY. The value must be between 32768 and 262143.

   - Master Machine - This is the controlling machine for the eLink Platform application. For single-server configurations, this tab is disabled. (See Step 6: Configure the Machine Properties.) The corresponding UBB file parameter is MASTER.

   - System Access - This specifies the access mode to the BEA eLink Platform bulletin board. The corresponding UBB file parameter is SYSTEM_ACCESS. Select FASTPATH from the drop down menu to the right of this field. The corresponding UBB file parameter is SYSTEM_ACCESS.

   - Maximum # of Services - This is the size of the Services table in the BEA eLink Platform bulletin board, and is the maximum number of services that may be advertised by all servers running in the application. The corresponding UBB file parameter is MAXSERVICES. The default is 500; the range is 1 to 32768.

3. Enter your Application Properties Environment information.

   Click on the Environment tab to display the Application Properties (Environment) window, as illustrated in Figure 6-3.

   Figure 6-3 Configuration Expert Application Properties Environment Window

   - Available Servers File - This is the location in which the iservers.lst file resides. This is the list of available servers; this list is updated whenever you use the Create button to add new servers. There is no corresponding UBB file parameter.

   - Generated Servers File - This is the location in which the gservers.lst file resides. By default, this file, which is provided as part of this release, resides in the <TUXDIR>/eLink/ConfigExpert/Config directory. Enter the full absolute pathname for this location. There is no corresponding UBB file parameter.

   - Output Directory - This is the directory to which the Configuration Expert output files should be written. The default is $TUXDIR/ConfigExpert/config. There is no corresponding UBB file parameter.

4. Submit your Application Properties information and go to the main window.

   Click OK to submit your Application Properties information and go to the Configuration Expert main window, as illustrated in Figure 6-4.

   Figure 6-4 Configuration Expert Main Window

5. Save your new configuration setup file.

   Although you have created a new configuration setup file, it does not yet exist on disk. Choose File->Save to save the new configuration setup file. Each time you choose File->Save at any step in the configuration process, the current configuration information is written to this file.

   To save your new configuration specifications, click Save, or choose File->Save or File->Save As. If you choose File->Save As, this displays the Save Application Configuration window, as illustrated in Figure 6-5.

   Figure 6-5 Configuration Expert Save Application Configuration Window

   Select the directory to which the configuration should be saved, specify a filename, and click OK.

Step 5: Add the Machine to the Configuration Tree

In Step 2: Create a New Data Configuration File, you defined your server machine and application, and made their existence known to the Configuration Expert. This added the machine to the Available Machines list, but did not add it to the configuration itself. In this step, you add the Business Process Option Server machine to the new configuration by adding it to the configuration tree (left panel in the main window) and thereby make it available for configuration.

To add a machine to the configuration tree:

1. Go to the Configuration Expert main window.

   After completing Step 4: Configure the Application Properties, click OK in the Application Properties window to go to the Configuration Expert main window. The main window displays the machine and application information you specified in the previous steps.

2. Select the machine from the Available Machines list.

   The Configuration Expert main window contains two panels:

   - The Available Machines list (on the right hand side)

   - The Current Application configuration tree (on the left hand side)

     Select a machine from the Available Machines list in the left panel.

3. Click Add to display the Machine Properties (General) window.

   Click Add to add the selected machine to the Current Application panel on the left. This action also brings up the Machine Properties (General) window for configuring the properties of the machine you just added. You can proceed to the next step to configure the machine you just added, or click OK in the Machine Properties (General) window to configure the machine at another time. You can then repeat the process for Step 5: Add the Machine to the Configuration Tree and continue adding as many machines as you want to configure. Each machine must be configured individually, however. Generally, it is easier to proceed to Step 6: Configure the Machine Properties and configure each machine as you add it, before adding another machine. However, this is not mandatory.

Step 6: Configure the Machine Properties

When you clicked Add in Step 5: Add the Machine to the Configuration Tree, the Machine Properties window automatically displayed, with the General tab already selected. At this point, you can elect to click OK in this window to add the machine to the configuration tree, and then add additional machines before proceding to Step 6: Configure the Machine Properties. Generally, it is more convenient to configure each machine as you add it, before adding additional machines to the configuration tree. To do so, you must repeat Step 5: Add the Machine to the Configuration Tree and Step 6: Configure the Machine Properties for each machine you want to add and configure.

Note: You can also go to the Machine Properties (General) window by selecting the machine you want to configure from the configuration tree (left panel of the main window) and then either clicking the Props button or by selecting Edit->Properties. If you elected to add multiple machines in Step 5: Add the Machine to the Configuration Tree,you will need to use one of these methods to get to the appropriate Machine Properties

To configure the machine properties for the selected machine, click on the tab for each category of properties in the Machine Properties window, and enter your information into the appropriate fields. There are three categories of machine properties:

- General - This contains some information concerning the machine name, application directory, environment setup file, and the prefix to be used in naming ULOG files. This is the first Machine Properties window

- Limits - This specifies the maximum number of Native and WS clients allowed for this machine.

- Network - This defines the listener ports, user ID, and group ID.

To configure the machine properties:

1. Go to the Machine Properties (General) window.

   When you click Add in Step 5: Add the Machine to the Configuration Tree, the Machine Properties (General) window automatically displays. You can also go to this window by selecting a machine in the configuration tree (left panel), and then either clicking the Props button, or choosing Edit->Properties. Figure 6-6 illustrates the Machine Properties window with the General tab selected.

   Figure 6-6 Configuration Expert Machine Properties General Window

2. Enter your general properties information for the selected machine.

   The Machine Properties (General) window contains the following fields:

   - Logical Machine ID - This is the name of the machine you specified using the Data Editor in Step 2: Create a New Data Configuration File, above. The corresponding UBB file parameter is LMID.

   - Application Directory - This is the directory to be used as the application working directory by the eLink Platform. Enter the full absolute pathname for the location in which the application servers are located. The corresponding UBB file parameter is APPDIR.

   - Environment File - This is the environment file containing the environment variable assignments for all BEA eLink Platform applications on this machine. Enter the full absolute pathname and filename for the eLink_BPO.env file.There is no default for this field. The corresponding UBB file parameter is ENVFILE.

   - ULOG File Prefix - This is the location and filename for the user log file generated by the eLink Platform. This file is typically referred to as the ULOG file. The final portion of this entry should be a filename, typically ULOG. The eLink Platform will append the suffix .<current_date> to the filename. If you do not specify a pathname, the file is placed in the directory <APPDIR>. The corresponding UBB file parameter is ULOGPFX.

3. Enter your Machine Properties Limits information.

   Click on the Limits tab to display the Machine Properties (Limits) window, as illustrated in Figure 6-7.

   Figure 6-7 Configuration Expert Machine Properties Limits Window

   This window contains the following fields:

   - Maximum Number of Native Clients - This is the maximum number of Native Clients that you can assign to this machine. The range is 1 to 32767. You can accept the default, which is 50. The corresponding UBB file parameter is MAXACCESSERS.

   - Maximum Number of WS Clients - This is the maximum number of Workstation clients you can assign to this machine. The range is 0 to 32767. You can accept the default, which is 50. The corresponding UBB file parameter is MAXWSCLIENTS.

4. Enter your Machine Properties Network information (optional).

   Click on the Network tab to display the Machine Properties (Network) window, as illustrated in Figure 6-8.

   Figure 6-8 Configuration Expert Machine Properties Network Window

   Note: For the standard Business Process Option configuration,which uses only a single machine, it is not necessary to define any Machine Properties Network parameters. Accept the defaults for these parameters.

   This window contains the following fields:

- BRIDGE Listener Port - This is the TCP/IP port number to be used by the BRIDGE process. The corresponding UBB file parameter is BRIDGE.

- TListen Listener Port - This is the TCP/IP port number to be used by the tlisten process. The corresponding UBB file parameter is NLSADDR.

- USER ID - This is the specific USER ID of the BEA eLink Platform administrator on that machine. The corresponding UBB file parameter is UID.

- GROUP ID - This is the specific GROUP ID of the BEA eLink Platform administrator on that machine. The corresponding UBB file parameter is GID.

1. Submit your Machine Properties information.

   After you enter all of the appropriate information, click OK to submit your specifications.

   Note: It is recommended that you save your configuration setup file after completing each step, as the information will not be saved automatically. Choose File->Save to save the current file.

Step 7: Add and Configure the Server Groups

The next step is to add the server groups to the configuration and configure each group. You can add and configure one group at a time, or add all of the groups at once, and then configure each group. Each group must be configured individually.

A group is a collection of eLink Platform Servers. Grouping servers facilitates server management by enabling eLink Platform operations (for example, boot or shutdown) to be executed unilaterally across a group.

To add and configure the server groups:

1. Go to the Configure Groups window.

   Choose Go->Groups. You can also click the Right Arrow key next to the Step # status message to go to the next configuration step (in this case, Configure Groups). Figure 6-9 illustrates the Configure Groups window.

   Figure 6-9 Configuration Expert Configure Groups Window

2. Add the required groups to the configuration.

   Select the group in the Available Groups list, and then click Add. The group name should now appear in the Current Application configuration tree in the left frame.

   Add the following groups to the Current Application configuration tree:

   - Default Group

   - BusProcOption Group

     Note: You can customize the list of available server groups by editing the Resource Manager template file. For more information on this procedure, refer to the BEA TUXEDO Builder Configuration Expert online document which is provided on your BEA eLink Platform installation CD-ROM. This document is in PDF form and is readable with Adobe Acrobat Reader.

3. Change the name of the Default group to SYSGRP.

   Select the Default Group in the Current Application configuration tree, and click the Props button (or choose Edit->Properties). This displays the Group Properties (General) window, as illustrated in Figure 6-10.

   Figure 6-10 Configuration Expert Group Properties General Window

   Change the contents of the Group Name field to SYSGRP.

   Note: The Transactions tab is greyed out for this group; you need not enter any transaction information for the group SYSGRP.

4. Click OK to submit the new group name.

5. Change the name of the BusProcOption group to BPOGRP.

   Follow the same procedure as you did to change the name of the Default group.

6. Click OK to submit the new group name.

   Note: It is recommended that you save your configuration setup file after completing each step, as the information will not be saved automatically. Choose File->Save to save the current file.

Step 8: Configure the Servers

The next step is to add and configure the servers. The gservers.lst file defines all servers required by the application. However, if you want to use additional servers - for example, the server mathserv for the MATHAPP sample application - you will need to add those in addition to the servers defined in this procedure. The servers you add are appended to the iservers.lst file.

To configure the servers:

1. Go to the Configure Servers window.

   Choose Go->Servers to display the Configure Servers window. You can also click the Right Arrow key next to the Step # status message to go to the next configuration step (in this case, Configure Servers). Figure 6-11 illustrates the Configure Servers window.

   Figure 6-11 Configuration Expert Configure Servers Window

2. Add the IcCliMgr server to the group SYSGRP.

   To add the server, do the following:

   1. Select the group SYSGRP from the Current Application configuration tree on the left. This displays the servers available to that group.

   2. Select the IcCliMgr server from the Available Servers list, and click ADD.

      The IcCliMgr server should now be listed in the Current Applications frame, under the group SYSGRP.

3. Configure the General Properties for the IcCliMgr server.

   The IcCliMgr server manages the startup and shutdown of certain Business Process Engine services, such as the Repository Daemon.

   To configure the general properties for the IcCliMgr server, do the following:

   1. Select IcCliMgr from the Current Applications list, and click Props. (You can also choose Edit->Properties, or simply double-click on the server name in the Current Applications list). This displays the Server Properties window with the General tab selected, as illustrated in Figure 6-12.

      Figure 6-12 Configuration Expert Server Properties General Window

      This window contains the following fields:

   - Server Name - This is the fully qualified path to the eLink Platform Server executable. If you do not specify the path, it is assumed that the file resides in the <APPDIR>.

   - Command Line Options - These are the default server command line options that are to be used for automatic startup of the server. The corresponding UBB file parameter is CLOPT.

   1. Modify the server name field so that it is quoted and contains the fully qualifed path to the executable. For example:

      >     "/work1/ic/tuxapp/IcCliMgr"

   2. Change the location of the logs (optional).

      You can optionally change the location of the log files generated by the server. To do so, add the full pathname before both of the .err and .out entries in the Command Line Options field. For example:

      Note: A backslash indicates that the command should be written in one continuous line; the backslash is not part of the actual command line.

      Before:

      >     -A -e IcCliMgr.err -o IcCliMgr.out --\
      >     -b IcCliMgr.cfg -I IcCliMgr.log

      After:

      >     -A -e /bpo/logs/IcCliMgr.err -o /bpo/logs/IcCliMgr.out --\
      >     -b IcCliMgr.cfg -I /bpo/logs/IcCliMgr.log

      Warning: This entry consists of two parts: the eLink Platform/TUXEDO-specific options, and the server-specific options. These two portions are separated by two minus sign characters ( -- ). The minus signs must be included in your specification. For information on the platform-specific options, refer to your eLink Platform and TUXEDO UBB file documentation.

4. Configure the Process Properties for the IcCliMgr server.

   Click on the Process tab in the Server Properties window. This displays the Server Properties (Processes) window, as illustrated in Figure 6-13.

   Figure 6-13 Configuration Expert Server Properties Process Window

   This window contains the following fields:

   - Minimum # of Processes - This specifies the minimum number of server instances to be automatically started when the server is booted. A blank field defaults to 1. The corresponding UBB file parameter is MIN.

   - Maximum # of Processes - This specifies the maximum number of server instances that can be booted at any given time. A blank field defaults to 1. The corresponding UBB file parameter is MAX.

   - Restartable - This specifies whether the server is restartable. The default is No (checkbox unchecked). Select Yes (checkbox checked) for all servers. The corresponding UBB file parameter is RESTART.

     Note: The following four parameters support the automatic spawning/decaying of servers through the mechanism of the -p eLink Platform/TUXEDO CLOPT parameter. Given the following:
     Grow pool when queue depth over = A
     Seconds to wait before growth parameter = B
     Shrink pool when queue depth under = C
     Seconds to wait before shrinking = D
     Then the CLOPT line should contain the following:
     -p A,B: C,D

   - Grow pool when queue depth over - Specifies the maximum number of messages before spawning a new server. During runtime, if the number of messages is met or exceeded for a time set by the Seconds to wait before growth parameter, a new server is spawned.

   - Seconds to wait before growth parameter - Specifies the time in seconds allowed to elapse before the server pool is expanded.

   - Shrink pool when queue depth under - Specifies the minimum number of messages before deactivating a server. During runtime, if the number of messages is below this value by the time specified by the Seconds to wait before shrinking parameter, a server is deactivated.

   - Seconds to wait before shrinking - Specifies the time in seconds allowed to elapse before the server pool is reduced.

5. Enter 1 as the Minimum # of Processes.

6. Enter 1 as the Maximum # of Processes.

7. Submit the modified IcCliMgr server configuration information.

   Click OK to submit your modifications and return to the Server Configuration window.

8. Add the BPOGRP servers.

   Add each of the following servers to the BPOGRP group, in the oder listed.

   - IcEvtAct - This advertises the Business Process Engine Event/Action Daemon processing services.

   - IcWorker - (First of two IcWorker servers) This advertises the IcGen_eLink services.

   - IcWorker - (Second of two IcWorker servers)This advertises the IcJob_eLink services.

     Note: Add two instances of the IcWorker server.

   - eProcRunner - This is the Business Process Option Server that starts a Business Process Engine job or process, and waits for the process to complete before returning.

   - eProcStarter - This is the Business Process Option Server that starts a Business Process Engine job or process, and returns as soon as the process has started.

   - eTaskAgent - This is the Business Process Option Server that processes Business Process Engine tasks.

   - Define the BPOGRP server properties.

     For each of the BPOGRP servers, do the following:

   1. Select the server from the Current Applications list, and click Props. (You can also choose Edit->Properties, or simply double-click on the server name in the Current Applications list). This displays the Server Properties (General) window, as illustrated in Figure 6-12.

   2. Modify the server name field so that it is quoted and contains the fully qualifed path to the executable. For example:

      >     "/work1/ic/tuxapp/IcCliMgr"

      Note: You need not specify an explicit pathname for the eProcRunner, eProcStarter and eTaskAgent servers. However, you must specify the full path to the eLink_BPO.cfg file for each in the Command Line Options field.

   3. Change the location of the IcWorker server log files.

      To change the log file locations, add the full pathname before each of the .err and .out entries in the Command Line Options field. For example:

      Note: A backslash indicates that the command should be written in one continuous line; the backslash is not part of the actual command line.

      For the first IcWorker server entry:

      >     -A -e /bpo/logs/IcWorker.err -o /bpo/logs/IcWorker.out --\
      >     -b IcWorker.cfg -I /bpo/logs/GenWorker.log

      For the second IcWorker server entry:

      >     -A -e /bpo/logs/IcWorker.err -o /bpo/logs/IcWorker.out --\
      >     -b IcWorker.cfg -I /bpo/logs/IcJobWorker.log

9. Configure the Process Properties for each server.

   Click on the Process tab in the Server Properties window. This displays the Server Properties (Processes) window, as illustrated in Figure 6-13. The following table provides the Process settings for each server. You can accept the default settings for all fields except those indicated in the table.

   Note: For all servers, check the Restartable checkbox.

   ####

   Server Name | Min. # Processes | Max. # Processes
   --- | --- | ---
   IcEvtAct | 1 | 1
   IcWorker (IcGen) | 3 | 3
   IcWorker (IcJob) | 1 | 1
   eProcRunner | 1 | 1
   eProcStarter | 1 | 1
   eTaskAgent | 1 | 1

   Warning: The default installation uses eLink as the Business Process Engine service name suffix. If you change this for any reason during the installation of the Business Process Engine, you must update IcTuxConfig files on both the client machine(s) and server machine(s) to reflect this change. These files are in the following locations:
   Client: <PDA_Base_Install_Dir>/Txm/config
   Server: <$IC_HOME>/config
   In addition, you must change the eLink argument for the -s option in the Command Line Options specification for the following servers:
   IcEvt
   IcWorker (IcGen)
   IcWorker (IcJob)

   Note: It is recommended that you save your configuration setup file after completing each step, as the information will not be saved automatically. Choose File->Save to save the current file.

   Step 9: Configure the Optional Components

   The next step is to add and configure the optional components. The optional components are eLink Platform utility servers or add-ons, such as communication gateways. For the Business Process Option, you must add and configure the following components:

   - WSL

   - eLinkJSL

   - IREPSVR

   To add and configure these components:

   1. Go to the Configure Optional Components window.

      Choose Go->Options to go to the Configure Optional Components window. You can also click the Right Arrow key next to the Step # status message to go to the next configuration step (in this case, Configure Optional Components). Figure 6-14 illustrates the Configure Optional Components window, which comes up with the WS tab selected.

      Figure 6-14 Configuration Expert Configuring Optional Components Window

   2. Add the WSL component.

      The Configuring Optional Components (WSL) window contains the following fields:

      - WSL Port Number - This specifies the port number for the Workstation Listener. Enter a port number of 11417. The contents of this field are added to the UBB file CLOPT parameter contents for the WSL Server.

      - Minimum Number of Handlers - This specifies the minimum number of Workstation handlers, or WSH, that are started when the application is booted You can accept the default for this configuration. The contents of this field are added to the UBB file CLOPT parameter contents for the WSL Server.

      - Maximum Number of Handlers - This specifies the maximum number of Workstation handlers that can be started. You can accept the default for this configuration. The contents of this field are added to the UBB file CLOPT parameter contents for the WSL Server.

      - Multiplexing Factor - This specifies the maximum number of clients per WSH. You can accept the default for this configuration. The contents of this field are added to the UBB file CLOPT parameter contents for the WSL Server.

        Enter your WSL component specifications and click Add.

   3. Add the eLinkJSL component.

      To add the eLinkJSL component, do the following:

      1. Click the Jolt tab to display the Configuring Optional Components (Jolt) window, as illustrated in Figure 6-15.

         Figure 6-15 Configuration Expert Configure Optional Components Jolt Window

      2. Select eLinkJSL.

         This displays the Configure Optional Components (Jolt JSL) window, as illustrated in Figure 6-16.

         Figure 6-16 Configure Optional Components Jolt JSL Window

         This window contains the following fields:

      - eLinkJSL Port Number - This is the port number assigned to the eLinkJSL. Enter a port number of 11400. The contents of this field are added to the UBB file CLOPT parameter contents for the eLinkJSL Server.

      - Minimum Number of Handlers - This specifies the minimum number of Jolt handlers, or JSH, that are started when the application is booted. You can accept the default for this configuration. The contents of this field are added to the UBB file CLOPT parameter contents for the eLinkJSL Server.

      - Maximum Number of Handlers - This specifies the maximum number of JSH that can be started. You can accept the default for this configuration. The contents of this field are added to the UBB file CLOPT parameter contents for the eLinkJSL Server.

      - Multiplexing Factor - This specifies the maximum number of clients per JSH. You can accept the default for this configuration. The contents of this field are added to the UBB file CLOPT parameter contents for the eLinkJSL Server.

      1. Enter your eLinkJSL component specifications and click Add.

   4. Add the IREPSVR component.

      To add the IREPSVR component, do the following:

      1. Click the Repository tab to display the Configuring Optional Components (Repository) window, as illustrated in Figure 6-17.

         Figure 6-17 Configuration Expert Configure Optional Components Repository Window

      2. Select IREPSVR.

         This displays the Configure Optional Components (Repository IREPSVR) window, as illustrated in Figure 6-18.

         Figure 6-18 Configure Optional Components Repository IREPSVR Window

         This window contains the following fields:

      - Read-Only Access to Repository Checkbox - If selected, this specifies read only access to the repository file. Make sure this is UNSELECTED so that there is write access to the file. The contents of this field are added to the UBB file CLOPT parameter contents for the IREPSVR.

      - Repository File - This specifies the location of the BEA eLink Platform Repository file. This is the file in which the Business Process Option Process Design Assistant stores information. This file must be accessible by the IREPSVR, which usually means it must be local to the IREPSVR machine. When you installed the Business Process Option, an empty repository file was created and stored in the directory <$TUXDIR>/udataobj.

      1. Enter your IREPSVR component specifications and click Add.

   5. Save the entire configuration file.

      Choose File->Save to save the current file.

   The configuration process is now complete. The next step is to generate the configuration files and scripts, as described in the next section.

   Step 10: Generate the Configuration Files and Scripts

   After entering all of your configuration information and saving your configuration setup file, you can generate the configuration files and scripts. The Configuration Expert reads the contents of your setup file to generate these files. If you modify the contents of your setup file at any time, you must consequently regenerate the configuration files and scripts for these changes to occur in the configuration.

   To generate the configuration files and scripts:

   1. Choose Go->Startup.

      This displays the Generate & Startup window, as illustrated in Figure 6-19.

      Figure 6-19 Configuration Expert Generate & Startup Window

   2. Click the Gen Files button.

      This will produce an output listing in the Command Output frame on the left of the Generate & Startup window, as illustrated in Figure 6-20.

      Figure 6-20 Configuration Expert Generate Files Output

      The following files should be generated:

      - <application_name>.ubb

      - <application_name>.checklist

      - tux_start.sh

      - tux_stop.sh

      - crtlog.sh

        For a description of each of these files, refer to The eLink Platform Business Process Option Configuration Files, in the Overview section of this chapter.

        Note: You can move or copy the generated files into the working eLink Platform application directory ($APPDIR, which in this case is the Business Process Option installation directory).

   3. Save your settings.

   The Business Process Option configuration process is now complete. The next step is to test the new configuration. Instructions for this step are provided in the next section.

   Step 11: Testing the Configuration

   To test your new configuration, you can use the Configuration Expert Activate feature to perform a preliminary startup of the system. Use one of the following methods:

   - Use the Activate button in the Configuration Expert Step 5: Generate a Startup window:

     1. Go to the Configuration Expert main window.

     2. Use the Right Arrow button to the left of the Step status line. Click the Right Arrow until the Step status message Step 5: Generate a Startup displays, as illustrated in Figure 6-21.

        Figure 6-21 Configuration Expert Step 5: Generate a Startup Window

     3. Click the Activate button to initiate a startup.

   - Choose Go->Startup->Activate.

     When the system is started, a series of status and/or error messages are displayed in the Command Output panel in the right half of the main window. You can use the output in this panel to assist in finetuning or debugging your new configuration.

   Copyright © 2000 BEA Systems, Inc. All rights reserved. Required browser: Netscape 4.0 or higher, or Microsoft Internet Explorer 4.0 or higher.