Console Config Tool

Overview

The Console Config Tool handles SAP J2EE Engine 6.20 configuration, adding new nodes to the cluster, and running the server in background mode as a Windows NT/2000 Service, or a Daemon on Unix-like platforms. Console Config Tool has the same functions as the GUI Config Tool.

There are several ways to run the Console Config Tool:

Run Tools®Console Config Tool from the SAP J2EE Engine 6.20 program folder.
Doubleclick the consoleconfig script file in configtool directory of the installed SAP J2EE Engine 6.20.
Open a console window in the directory where the consoleconfig script file is located, enter consoleconfig on the command line, and choose “Enter.”

Note : Config Tool is XML-based, which enables third-party visualizations to be developed or integrated as part of a more complicated configuration system. For more information, refer to the Development Manual .

Description of Console Config Tool Functions

The Console Config Tool functions for the cluster type of configuration are explained below. The stand-alone configuration procedure is similar.

Step 1: Main Menu

This step lists the available cluster elements and the Console Config Tool general options.

<1> – displays the available dispatcher nodes
<2> – displays the available server nodes
<3> – saves the server configuration in an XML file
<4> – saves the changes
<5> – scans the directory where SAP J2EE Engine 6.20 has been installed
<6> – adds a new dispatcher node (the maximum number of dispatcher nodes is 60)
<7> – adds a new server node (the maximum number of server nodes is 60)
<0> – exits the Console Config Tool

The next step depends on the choice in step 1. To modify the properties of dispatcher services and managers, select <1>.

Step 2: Dispatcher Node Configuration

This step enables you to modify dispatcher services and managers properties.

<1> – lists all services
<2> – lists all managers
<3> – sets the cluster element to run as a Windows NT/2000 Service, or a Daemon on Unix-like platforms
<4> – displays the Main Menu (step 1)
<0> – exits the Console Config Tool

If <1> is the selected option, continue as follows:

Step 2.1: Services Properties

This step displays a numbered list of SAP J2EE Engine 6.20 services. To choose a service, enter the corresponding number. The last option from the list returns to the previous step. Each service has the following configuration menu:

<1> – lists all service properties
<2> – enables you to add a new property by specifying its name and value
<3> – displays a numbered list of all properties and enables you to delete properties
<4> – displays a numbered list of all properties and enables you to change their values
<5> – enables you to change the start-up type of the service. By default, the type is set to always but can be changed as follows

<1> – always starts the service
<2> – starts the service automatically – that is, the first time the service is requested, it starts
<3> – the service is started manually – that is, the service must be started by the system administrator
<4> – returns to the previous step

<6> – saves the changes made in the previous choices
<7> – lists the used ports

<1> – lists the used TCP ports
<2> – lists the used UDP ports
<3> – returns to the previous menu
<0> – exits the Console Config Tool

<8> – returns to the previous menu
<0> – exits the Console Config Tool

Note: After each modification, a confirmation question is displayed with two options: “Y” for yes and “N” for no.

If <2> is the choice in Step 2, continue as follows:

Step 2.2: Managers Properties

This step displays a numbered list of SAP J2EE Engine 6.20 managers. To choose a manager, enter the corresponding number. The last option from the list returns to the previous step. The managers configuration menu does not differ from the services configuration menu. For detailed information on the configuration menu, refer to Step 2.1.

If the choice in Step 2 is <3>, continue as follows:

Step 2.3: Cluster Element as a Windows NT/2000 Service or a Daemon on Unix-Like Platforms

This step enables you to set the cluster element (dispatcher) as a Windows NT/2000 Service, or a Daemon on Unix-like platforms. The default settings are displayed:

Port on which the cluster element listens for requests – the default value is 5501 . Make sure the specified port is not already in use.
Timeout – specifies the timeout period (in milliseconds) before the cluster element is shut down if the service stops its process. The default value is 10000.
Main class – specifies the main class to run. The default is com.inqmy.boot.Start .
Root directory – the directory where the cluster element has been installed. Default is <SAPj2eeEngine_install_dir>/cluster/dispatcher
Java executable path – the path to the Java home directory. The default is C:\jdk\1.3\bin\java .
Parameters – main class input parameters, if required. In this case, no parameters are specified.
Java parameters for starting cluster elements as an NT service

The cluster element default settings described above can be modified using the following options:

<1> – sets port value
<2> – sets timeout
<3> – sets main class
<4> – sets root directory
<5> – sets Java executable path
<6> – sets main class parameters
<7> – sets Java parameters
<8> – sets the cluster element to be a Windows NT/2000 Service
<9> – confirms the current cluster element status and returns to the previous step
<0> – exits the Console Config Tool

Note: For detailed information about setting SAP J2EE Engine 6.20 cluster elements as a Windows NT/2000 Services or a Daemon on Unix-like platforms, refer to the SAP J2EE Engine 6.20 as a Windows NT/2000 Service or Unix Daemon section in this manual.

If <2> is the choice in Step 1, continue as follows:

Step 3: Server Node Configuration

This step enables you to modify the properties of the services and managers running on the server part of the SAP J2EE Engine 6.20 cluster.

<1> – lists all services
<2> – lists all managers
<3> – enables debug mode
<4> – sets the cluster element to run as a Windows NT/2000 Service, or a Daemon on Unix-like platforms
<5> – displays the Main Menu (step 1)
<0> – exits the Console Config Tool

If <1> is the selected option, continue as follows:

Step 3.1: Services Properties

This step displays a numbered list of SAP J2EE Engine 6.20 services. It is the same as for dispatcher nodes therefore, refer to Step 2.1 .

If <2> is the choice in Step 3, continue as follows:

Step 3.2: Managers Properties

This step displays a numbered list of SAP J2EE Engine 6.20 managers. It is the same as for dispatcher nodes therefore, refer to Step 2.2 .

If <3> is the selected option, continue as follows:

Step 3.3: Enable Debug Mode

This step enables you to run the server in remote debug mode. This task can be performed on Stand-alone configuration or on server nodes of SAP J2EE Engine 6.20 Cluster.

To run the cluster element in remote debug mode, set a debug port that enables debugger clients connections. It is opened by the Virtual Machine and must not be among the ports that SAP J2EE Engine uses.

Step 3.4: Cluster Element as a Windows NT/2000 Service or a Daemon on Unix-Like Platforms

This step enables you to set the cluster element (server) as a Windows NT/2000 Service, or a Daemon on Unix-like platforms. It is the same as for dispatcher nodes therefore, refer to Step 2.3 .