CONTENTS     

Administration

Shell language is used for cluster administration. The administration is accomplished through telnet clients,applets that simulate telnet client, or other clients. It monitors the processes started by the cluster, and provides the opportunity for a quick and adequate intervention when problems occur. It also automates the processes of the cluster components’ administration.

Shell Language Conventions

The following conventions are used when using the Shell language commands:

• The brackets have a special meaning explained below. There is no need to type them when executing a command on the command line, unless it is indicated explicitly in the corresponding command description.
• The <> type of brackets means that the parameter is required. If this parameter is not specified, the command displays the help message when the command is executed.
• The [] type of brackets means that the parameter is optional.
  For example:
  LISTPROPS [clusterID] <ServiceName>
  where [clusterID] is optional, and <ServiceName> is required.
• The commands are displayed in capital letters – for example, LISTPROPS ; however, you do not have to type them in capital letters in the command line.
• When a command has an abbreusingted alternative it is given in () brackets after the command name.
  For example:
  CHECKPOINT(CP)

Help

To view the help messages for each command, type the command and -? , -h , or –help on the command line – for example:

COMMAND -?

Adding a Group of Commands

The Console Administrator Shell commands can be used after they are added to the Shell environment. When starting SAP J2EE Engine 6.20, the only groups of commands available are ADMIN and SYSTEM, because of their vital importance.

To add a group of commands to the Shell environment, type

ADD [groupName]

on the command line. To view all groups of commands, do not specify the [groupName] variable.

To view all groups and their commands added to the Shell environment, execute the MAN command.

System Variables

• $PATH – the path to look for client scripts
• $CLASSPATH – the path to look for the client classes when IMPORT or REIMPORT command is executed
• $1 , $2 ,..., $n – the parameters with which the current script is started
• $0 – the number of parameters with which the current script is started
• $USER_NAME , $HOST , $PORT – these variables are used and modified by LOGIN command
• $MAX_LINE , $MAX_COLUMN – these variables specify the console size
• $STD_IN , $STD_OUT , $STD_ERR – these parameters are standard Input/Output streams. Possible values are: FileName , SYSTEM , NULL
• $TEMP_BUFFER_SIZE – this is the size of the buffer (in bytes) for storing the temporary information when pipe commands are executed. A temporary file called n1n2temp.tmp is used when this value is exceeded, where n1 is the process number and n2 is a temporary number of this file. After the construction execution, the temporary files are destroyed.
• $PROMPT , $SUBPROMT – the primary and the secondary prompt
• $PASSWORD – the value of this variable is always read from the standard input (until ENTER is reached)
• $ECHO – there are only two values – ON and OFF . When $ECHO = OFF , the result of the command execution is shown directly. When $ECHO = ON, the execution is shown step by step.

Examples:
>SET  $ECHO = ON
>SET  $A = 5
>ECHO  $A
>ECHO 5
>5
>SET  $ECHO = OFF
>SET  $A = 5
>ECHO  $A
>5

• $AUTORUN – contains a script that is executed automatically when the console administrator is started