Message Server Parameters

The most important message server parameters are described below. Dynamic means that you can change the parameter while the message server is running. To display the parameters and their values and documentation, choose Goto Parameters Change in the message server monitor.

Note Note

Dynamic changes are lost when the message server is restarted. The default values or the values set in the profile then become valid again.

End of the note.

Recommendation

You can also obtain information on the profile parameters using transaction RZ11. Search for parameters that start with ms/, and then choose Documentation.

End of the recommendation.

Parameter Name	Meaning	Default Value	Dynamic
`rdisp/mshost`	This parameter specifies the host on which the message server is running. This entry must be the same on all application servers belonging to one SAP system and for this reason it should be set only in the default profile. The name of the host must be defined in the `hosts` file; this means the following: For UNIX: It must be entered in the `/etc/hosts` file or on the domain name server. For Windows: It must be entered in the `C:\WINDOWS\system32\drivers\etc\hosts` file or on the domain name server.	`$(SAPMSHOST)`	No
`rdisp/msserv`	Name of the service where the message server can be reached. A default name is created from the SAP system name. This entry must be the same on all application servers belonging to one SAP system and for this reason it should be set only in the default profile. The service must be defined in the services database. For UNIX: It must be entered in the `/etc/services` file or on the domain name server. For Windows: It must be entered in the `C:\WINDOWS\system32\drivers\etc\services` file or on the domain name server.	`sapms$(SAPSYSTEMNAME)`	No
`is/HTTP/default_root_hdl`	This parameter determines the processor of an HTTP request with a URL that points to the root directory (this is a URL without path details, for example, "/" or "/index.html"). You can specify AS ABAP or AS Java as the processors for HTTP requests. Permitted values are `abap` and `j2ee`.	`j2ee`	Yes
`is/instname_encoding`	You can use this parameter to control how the SAP NetWeaver AS presents the instance name externally (for example, in an HTTP session cookie). The following values are permitted: `none`: Plain text: For example, ls100_BCO_10 `md5`: MD5 hash of instance name: For example, `FKOuCXKqMVOWyF5syzhQSQ` If you use this parameter, make sure it is set the same on all SAP NetWeaver AS instances and on the message server (preferably in the default profile only) so that all application servers use the same instance name and the message server also observes the parameter. Only then can HTTP load balancing work. Recommendation If you use the SAP Web Dispatcher for load balancing, keep in mind that the parameter does not have to be set in the profile of the SAP Web Dispatcher. End of the recommendation.	`none`	No
`ms/audit`	This parameter is used for logging. You can use this parameter if you detect problems of a sporadic nature with the message server and cannot increase the message server trace level because the file would become too large if you did so. If this parameter is set accordingly, logons to and logoffs from the message server are also logged with trace level 1. This is a bit mask (2 bits); the following values are allowed: `0`: No logging. `1`: Logons to and logoffs from application servers are logged. `2`: Activate and suspend clients are also logged; this means the temporary suspending of a client when it sends more data than can be received.	`0`	Yes
`ms/comment`	Short description of the SAP system. This description is transferred to the domain server when the connection is established. It is displayed there in the list of systems.	`message server $(SAPSYSTEMNAME)`	Yes
`ms/timeout`	Determines the timeout value for the `NiRead` (read from network) and `NiWrite` (write to network) calls in milliseconds. If not all the data has been sent or received within this time interval, the action concerned is interrupted and reinitiated later on.	`5000`	Yes
`ms/conn_timeout`	You log on to the message server in two steps. Establish a connection to the message server Log on to the message server The connection is broken if you do not log on to the message server within a specified time after establishing the connection. Value 0 deactivates this check.	`300` (seconds)	Yes
`ms/server_port_<xx>`	This parameter identifies the message server port at which HTTP(S) requests can arrive. The syntax is the same as for the icm/server_port_<xx> parameter with the following exceptions: Options KEEPALIVE, VCLIENT, and TIMEOUT are ignored. Only HTTP and HTTPS protocols are accepted - an error message is generated for any other protocol. This parameter replaces the `ms/http_port` and `ms/https_port` parameters that were used previously. Do not use these parameters for the message server now. These parameters are only needed by the SAP Web Dispatcher.	-	While the message server is running, you can configure ports in the message server monitor.
`ms/http_bufferln`	Maximum buffer size of an HTTP or HTTPS request. The buffer is dynamically allocated by the message server and released once the request has been processed.	`65536` (bytes)	Yes
`ms/http_domain`	If the parameter is set to 1, the message server uses the domain name with which the client logged on to the message server for the REDIRECT request. If the parameter has the value 0, the domain that the dispatcher communicated to the message server is used.	`1`	Yes
`ms/http_enable_handler`	This parameter is used to control HTTP requests and can have the following values: `1`: HTTP request handlers in the ICF are to be called `0`: HTTP request handlers in the ICF are not to be called The message server calls a few HTTP request handlers in the ICF to fetch information about HTTP load balancing and the distribution of HTTP requests. The message server sends the URL to an application server that contains `default_host/sap/public/icf_info/urlprefix` or `logon_groups`. If there is no HTTP request handler available or an available handler has an error, the handler in question is flagged as incorrect. If this HTTP request handler is to be called again later, this parameter must be set dynamically to 1.	`1`	Yes
`ms/http_logging` and `ms/HTTP/logging_<xx>`	This parameter controls HTTP logging.	`0`	Yes
`ms/http_logging` and `ms/HTTP/logging_<xx>`	This parameter controls HTTP logging.	`ms/HTTP/logging_0 = PREFIX=/, LOGFILE=dev_ms_logging, LOGFORMAT=MSG`	No
`ms/http_lookup`	This parameter specifies which methods are used to search for SAP-specific parameters in the HTTP request. The following values are permitted: 1: Only the URL is searched. 2: First the URL is searched, then the form specification. 3: The URL is searched, then the form specification, and then the cookie. The search is done according to SAP specifications. `sap-trace`: Activates the trace for this request; the trace results are written to the trace file on the message server (`dev_ms`). `sap-group`: Load balancing using the SAP logon groups.	`1`	Yes
`ms/http_max_clients`	Number of HTTP or HTTPS clients that can connect in parallel to the message server.	`500`	No
`ms/http_max_ports`	Number of ports on which the message server can receive HTTP and HTTPS connections. The number of virtual hosts is determined by this parameter. The total number of HTTP, HTTPS, and virtual hosts must not exceed this value. These are defined in the `ms/server_port_<xx>` parameters.	`20`	No
`ms/http_timeout`	If the data cannot be read to or written from the network within the specified time span (seconds), the connection to the HTTP or HTTPS client is closed.	`20`	Yes
`ms/http_was_required`	If a request is to be forwarded to an AS Java server, you can use this parameter to specify that only those servers that also contain AS ABAP are selected. To do this, set the parameter to `1`.	`0`	Yes
`ms/keepalive`	Specifies the maximum time in seconds before the message server checks inactive connections. A data packet is sent to the client for the check. Value 0 deactivates this check.	`300`	Yes
`ms/max_clients`	Number of clients that can log on to the message server at the same time.	`300`	No
`ms/max_open_requests`	Number of open requests that can be stored on the message server at the same time.	`10000`	No
`ms/max_sleep`	Specifies the maximum amount of time in seconds the message server waits for a request.	`20`	Yes
`ms/max_vhost`	The parameter specifies the maximum number of virtual hosts that the message server can open. One virtual host can be assigned to each HTTP or HTTPS port (add VHOSTIDX to `ms/server_port_<xx>`). As soon as an HTTP request is directed via an HTTP or HTTPS port to the message server, only those application servers that have also opened a virtual host with this index are included in load distribution. Dynamic changes for this parameter only affect application servers that log on to the message server after the change is made. The total number of HTTP, HTTPS, and virtual hosts must not exceed the total number of ports (`ms/http_max_ports`).	`16`	Yes
`ms/nitrace`	Activates or deactivates the tracing of incoming and outgoing network connections. The following values are permitted: 0 = Trace is deactivated 1 = Trace is activated rdisp/TRACE* trace parameters For a description of these parameters, see Trace Logging.	`0`	Yes