Some system properties of the AS Java are maintained using profile parameters in the profile files of the AS Java. These files are located in the directory
\usr\sap\<SID>\sys\profile and should be saved before and after a change. There is no special tool for maintaining these files in the AS Java. You can use a simple text editor for this purpose. In this way, for example, some properties of the message server and
Properties of the Central Services
The Central Services consist of the message server and the enqueue server. We will first consider the interaction with the message server. As shown in the “Message Server” figure, each node (ICM and servers) of each instance is connected to the message server.
Figure 65: Message Server
When the Central Services are started, the system reads the profile parameters for the message server. The internal communication port for the message server is defined using the parameter rdisp/msserv_internal. Usually, port 39<instance number> is chosen. The HTTP port of the message server is specified with the profile parameter ms/server_port_0. The instance number is also usually used for the last two digits in this case. The HTTP port is required by the SAP Web dispatcher, among other things.
You can obtain the port numbers used to start the message server from the developer trace (dev_ms). The developer trace also contains the hardware key (which is required for requesting a license) and the host on which the message server is running. You can use the SAP NetWeaver Administrator (NWA) to display the parameters with which the message server is running. You can find the parameters in the NWA under Configuration → Infrastructure → Message Server (Quick Link: /nwa/msg-server).
Select Message Server Parameters under Show.
Alternatively, you can use the Config Tool to display the current parameters. Select an entry instance - ID... and choose the tab page Instance Profile. There the corresponding parameters are called MSGSRV_PORT and MSGSRV_HOST. These parameters are used by the ClusterManager (properties ms.port and ms.port).
Figure 66: Message Server: Changes
In the figure “Message Server: Changes”, you can see which areas need to be adjusted if the port or the name of the host on which the message server is running changes.
Ports are, of course, changed in the instance profile of the Central Services instance.
In the example from the figure, internal communication port 3977 and HTTP port 8177 have been set, and the new host is called twdfxxxx.
These changes must now be adjusted in the default profile of the system using the parameters j2ee/scs/host and j2ee/ms/port. Just in case, you should check whether these parameters are also set in the instance profiles. The values there would override the values from the default profile. After you have maintained all of the parameters, you can start all instances.
Enqueue Server
Now that you have seen the settings for the message server, we will consider the enqueue server. The “Enqueue Server” figure shows that each server process has a connection to the enqueue server. The figure shows the profile parameters that are
using the parameter enque/serverinst. The parameter enque/encni/port can be used to select the port for the enqueue server explicitly (including outside of the range 32<instance number>). The default values of the parameters enque/table_size and enque/snapshot_pck_ids are minimum values and should be adjusted to the values shown in the figure. However, these are not maximum values, and it may be necessary to further increase the values.
Figure 67: Enqueue Server
You can obtain the port numbers used to start the enqueue server from the developer trace dev_enqlisten. You can use the SAP NetWeaver Administrator (NWA) to display the parameters that the LockingManager uses to connect to the enqueue server. You can find these parameters in the NWA under Configuration → Infrastructure → Java System Properties. Select the active template, choose the tab page Kernel and select the entry LockingManager. The relevant parameters are enqu.host and enqu.port.
Choose Show Details to display the concrete values.
Alternatively, you can use the Config Tool to display the current parameters. Select an entry instance - ID... and choose the tab page Instance Profile. There the corresponding parameters are called ENQSRV_PORT and ENQSRV_HOST.
Figure 68: Enqueue Server: Changes
In the figure “Enqueue Server: Changes”, you can see which areas need to be adjusted if the port or host of the enqueue server changes. Ports are, of course, changed in the instance profile of the Central Services instance. In the example from the figure, port 3277 has been set, and the new host is called twdfxxxx.
These changes must now be adjusted in the default profile of the system using the parameters j2ee/scs/host and j2ee/enq/port. Just in case, you should check whether these parameters are also set in the instance profiles. The values there would override the values from the default profile. After you have maintained all of the parameters, you can start all instances.
Exercise 7: Further Configuration Activities
Exercise Objectives
After completing this exercise, you will be able to:
• Use the Configuration Wizard
• Configure the Central Services instance
Business Example
You must make various settings after you install an AS Java-based system and when the system is running.