Getting an Overview of Configuration Tools for Server Processes

There are three different configuration tools to configure the AS Java server nodes. This is a bit confusing at first glance, but it is due to when which tool was developed, or for what purpose the tool is used.

In day-to-day operation, most of the configuration tasks can be completed with the SAP NetWeaver Administrator. 

If none of the instances can be started, you will inevitably have to use the Config Tool. There are also a few things that can still only be done with the Config Tool today.

In very special cases or because you prefer a tool based on command line mode, you use the Shell Console Adminstrator.

In the following we want to get an overview of the configuration tools.

system only available in English

The SAP NetWeaver Administrator (NWA) combines the most important administration, configuration and monitoring tools for Java systems in a browser-based user interface.

system only available in English

With the NWA, the standard HTTP port of the AS Java instance is used. As tool a supported browser is needed. At least one application server of the SAP system must be started in order to use the SAP NetWeaver Administrator. It can be called using the following URL: http://<hostname>:<http-port of AS Java>/nwa.

You use the Config Tool to maintain the settings for AS Java in the database. It is therefore necessary that the database is started, so that you can change the settings with the Config Tool.

system only available in English

The settings that you make with the Config Tool only take effect when AS Java is started; that is, you must restart AS Java after maintaining settings.

The Config Tool is available in the file system of each application server. Authentication on the database is usually carried out via Secure Store.

The Shell Console Administrator can also be used to access an AS Java instance. This connection works via telnet and requires at least an up and running Java instance. telnet is available on many operating systems and can therefore be used for administration without additional installation. However, for security reasons the telnet access is by default set to localhost (see Note below). A remote access can be set up by configuring the associated ICM parameter.

Note

For security reasons, access to the SAP system over Telnet is limited to host IP address 127.0.0.1 (localhost).

system only available in English

You can use the Shell Console Administrator to display basic information about an AS Java system. The Shell Console Administrator is also suitable for starting and stopping services.

If necessary, you can use the Shell Console Administrator to shut down the AS Java instance by stopping the ICM and the server processes.

You can use the Shell Console Administrator to configure the services and managers of all Java instances in the Cluster. It is significantly easier to make the changes to managers and services with the Config Tool. Therefore, only specialists should make changes to managers and services using the Shell Console Administrator.

This section describes the features when calling the different tools.

SAP NetWeaver Administrator is a Web-based framework tool for administration, configuration and monitoring. It consists of respective integrated tools that help you to configure,but also administer and monitor your SAP NetWeaver system.

To call the SAP NetWeaver Administrator (NWA), log on to the HTTP port of an AS Javainstance. The AS Java instance must therefore be started. The NWA can be called using the following URL: http://<hostname>:<http-port>/nwa. The start page of the NWA is displayed after the logon.

system only available in English

The management functions included in SAP NetWeaver Administrator are grouped into work centers according to the type of functionality they provide. The work centers are subdivided into work sets grouping related administration options. The number of work sets and their content is dynamic and changes according to the installation scenario.

For example, the function JCo RFC Provider is located in the work set Infrastructure, which in turn is located in the work center Configuration. A function can also be available in several work sets.

Which work sets, work centers and functions you see depends on the profile that is selected. You can change the profile by choosing the Personalize menu.

If you are not sure which work set contains the application you need, use the following ways:

• Search field: You can enter only part of the application name with or without accessory symbols
• Site Map: Find the relevant application and choose its link to open it

The Config Tool is a tool for administering and configuring AS Java. configtool.bat (under Windows) or configtool.sh (under UNIX) is called to start the Config Tool at operating system level of an application server for AS Java. The start file is stored under the following path at operating system level: \usr\sap\<SID>\<instance directory>\j2ee\configtool. To access the configuration data of the SAP system, you have to log on to the database of the system using the Config Tool. To do so, you use the data stored in the Secure Store of the system (user and password) in the default setting. You must still confirm whether you want to use these default settings or whether you want to make other settings. You can then use the Config Tool to edit the parameters (see the figure "Config Tool: Call").

system only available in English

During the start process of the AS Java instance, the parameters for the start and running operation are read from the database and copied to the file system. With the Config Tool, these parameters are maintained in the database. It is therefore necessary that the database is running so that the Config Tool can read the current parameters from the database. When the Config Tool is opened, you can see and change the default settings for logging on to the database by choosing No. The window contains the connection data for the database on the tab page Via SecureStore. This is stored during the installation process. Choose Connect to DB to log on to the database using the data stored in the Secure Store. The Config Tool then displays the configuration settings saved in the database. You can now view these settings and change them if required.

To log on to a remote database using the Config Tool, you can also use the pushbutton Select Security Folder, to store the path for the Secure Store of another system. To do so, use the data stored in the Secure Store of the remote system using a secured network connection. It must be accessible as a share or mount point for example. You can then Connect to DB the "remote" database with these settings.

If you want to access this database repeatedly, you can save this new connection data as a file using Save Connection As and use it again later via the Connection Settings.

You can perform some administration tasks for AS Java with Shell Console Administrator. To do this, you must specify the host name (only localhost in the standard system) and the Telnet port of the AS Java instance when you call the Shell Console Administrator. You are then prompted to log on to the AS Java, as shown in the figure, Shell Console Administrator: Call. You use, for example, the same user to do this as for the NWA. Since you are logging on to the AS Java instance, this must already be running.

After the logon via telnet, you are directly forwarded to the first server node of the respective instance. The command jump <server node-ID> takes you to another node. The command man currently lists available commands. To get further details, man <command name> gives you an explanation of the specified command.