Entering content frame

Function documentation Profile Parameters for the Standalone Enqueue Server Locate the document in its SAP Library structure

You have to set the following parameters in the instance profile of the standalone enqueue server.

Some are only relevant, if you are working with a replication server.These are listed later.

ipc/shm_psize_34

The lock table is in the shared memory of the enqueue server. In the standard setup the enqueue server places the lock table in pool 10, which in this case would be a waste of shared memory. If you set this parameter to 0, the lock table is not placed in any pool.As much memory as is needed for the lock table is allocated. So set the parameter ipc/shm_psize_34 = 0 in the profile of the enqueue server.

Caution

Set this parameter only in the instance profile of the enqueue server.

enque/server/replication

The parameter can have the value true or false and this determines whether the enqueue server uses the replication server. The default value is false. If you want to use the replication server, you have to explicitly set this parameter in the enqueue server profile.

Note

For information about using the backup file for locks transferred to the update process when using the replication server, see Using the Backup File.

enque/server/codepage

The non-unicode version of the enqueue server can run in specific code pages.Until now this was only useful, if you were using an SAP J2EE Engine with the enqueue server and the enqueue server was not a unicode server. In the protocol used in such cases, unicode characters are transferred in UTF8 format to the enqueue server. With this parameter you can set the code pages you want to convert these characters to.

Note

The value is the four digit number of the SAP character set.

enque/server/max_requests

The parameter specifies the maximum number of enqueue requests that can be processed simultaneously in the enqueue server.

The value should be at least the same as the total number of work processes in the system (threads in all J2EE Engines).The standard value is 1000.

Caution

Set this parameter only in the instance profile of the enqueue server.

enque/encni/port

You use this parameter, if the TCP port of the enqueue server, used for the communication with the enqueue clients, is not to be set to sapdpXX. It must then be set in all profiles (preferably DEFAULT.PFL).

enque/encni/repl_port

Use this parameter, if the replication port of the enqueue server cannot be set to sapgwXX (for example, if a standalone gateway is being used in the same instance). It should then be set either in DEFAULT.PFL, or in the profiles of the enqueue server and the replication server.

enque/encni/no_addr_resolve

This parameter deactivates the host name resolution in the enqueue server.The default value of the parameter is zero 0 (false), this means that the host name resolution in the enqueue server will be executed (see High Availability with the Standalone Enqueue Server). If this takes too long or there are any problems, you can set the parameter to 1 (true), the IP address is simply output and the host name is not resolved.

enque/server/threadcount

The number of I/O threads. Normally you do not need to change this parameter.It may be useful to change it for increasing system performance, but this should only be done with support from SAP or your hardware provider. Experience up to now shows that a value higher than 4 has never resulted in an increase in throughput.

enque/server/max_clients

This parameter determines the number of processes that can be connected to the enqueue server. Set the parameter to the same value as the total number of work processes in the system. The default value is 1000.

enque/server/use_spinning

With this parameter you can activate a different mechanism for communication between the threads. This mechanism is somewhat quicker, but generates a heavy load on the system.Even with a small enqueue throughput, CPU usage will be 100%. Possible values are true and false. The default value is false, and the parameter is not normally set.

Parameters for Using Replication

You have to set the following parameters if you use replication, that is, when the value of enque/server/replication is true.

To find out more about this parameter see Replication Functions and Polling Concept.

enque/enrep/stop_timeout_s

This parameter specifies how long the enqueue server is to remain in suspended state, before it attempts to update the replication server again. The time period is specified in seconds. The value 0 means that the state suspended remains for as long as there is a connection to the replication server. Only when the replication server is restarted, does the enqueue server leave this state.

enque/enrep/stop_retries

This parameter specifies how often the enqueue server attempts to update the replication server, following the timeout stipulated in enque/enrep/stop_timeout_s. Possible values are whole numbers. The value 0 means that the enqueue server should keep retrying.

enque/enrep/req_block_count

This parameter specifies how many memory blocks (each has 32 KB) are reserved in the replication server for transferring the data. The parameter is needed with a lock table size exceeding 80 MB.

Caution

If your lock table is larger than 80 mb, see note 654744.

 

 

Leaving content frame