To administer the J2EE Engine remotely using shell commands, you have to connect to the J2EE Engine by using a Telnet client over the Telnet protocol. This function is implemented in the J2EE Engine using the Telnet Provider service.
Communication over Telnet is not encrypted. Therefore, in a non-trusted network environment, we recommend that you restrict the access to the J2EE Engine over Telnet.
A remote connection can be established if the remote machine (in the LAN) has the J2EE Engine installed and running, and the local machine has a Telnet client through which a connection to the server can be established.
1. Set the Telnet Provider service port on which J2EE Engine elements listen for connections to Telnet clients. The port is generated at installation time and can be viewed or modified using the Telnet Provider service running on the dispatcher.
2. Run a Telnet client and connect to the target machine by specifying the host and the corresponding port. If a connection is established, the J2EE Engine Telnet Administration Console is open.
Alternatively, you can open a Telnet client from the SAP Microsoft Management Console:
i. Choose the J2EE system on which you want to start Telnet.
ii. 2. Browse to the J2EE Process Table node.
iii. 3. From the right-hand pane, select the dispatcher and from the context menu choose J2EE Telnet.
The J2EE Engine Telnet Administration Console is open.
3. Enter a valid login info (including user name and password) to authenticate yourself.
If the input information is incorrect, the link is disconnected and the console disappears. You must then complete the above steps again to open a new Telnet console.
If your connection is successful, the console remains open. This enables administration of both server processes and dispatchers. That is, separate command prompts are not available for each cluster element.
By default, the Telnet shell is opened on the dispatcher. Once you are connected, you can execute all shell commands available on the different J2EE Engine cluster elements. Use the LSC command to display all server components with their ID, component name, host, port, and type. The first component displayed is the current one.
To pass over from one component to another, use the JUMP command and specify the ID of the target element. For example, executing jump 4001 enables the remote administration of a cluster element with ID 4001.
The JUMP command is available for Telnet administration only.
The shell commands are grouped according to their functions. For more information about how to activate and deactivate a group of shell commands, see Shell Console Administrator. For more information about the functions of each group and the available shell commands, see Shell Administration Commands.
To close the Telnet connection enter exit on the command line.
The J2EE Engine cluster is accessed remotely using a dispatcher. The JUMP command redirects the terminal to a server process. The initial login enables restricted permissions only. You can use the LOGIN command that is available on server processes to obtain authorized access to the server resources.
A security role telnet_login in the security policy configuration (called service.telnet) manages access restrictions when using Telnet. Only users that are in this security role are permitted to connect to the cluster using Telnet. By default, all administrator users can use Telnet. Access restrictions can be changed using the interfaces of the security roles.
Do not allow users that are not administrators to use Telnet.