Skip to Content

Runtime parameter* *

*Introduction: </u>In the end of this series, addition of part 1  ()  , [part2 | ]  and part3  (), I will discuss Runtime category. We can set/maintain different different parameter under  the Runtime category.we can do this with transaction SXMB_ADM.Thiese parameter can affect directly or indirectly to the performance of our system in positive or negative ways.</p><p>_Details:_*  

*ENGINE_TYPE : This parameter determines the Integration Engine type for the current client. We can define our XI server depending on client, if we will not do so the clients will NON-XI engine default.</p>Possible values: <p style=”margin: 0in 0in 0pt” class=”MsoNormal”>UNDEFINED = Client is not configured as the Integration Engine<br />HUB = Client is configured as the Integration Server<br />LOC = Client is configured as the sender/receiver system</p><p> </p><p>IS_URL:It define URL or HTTP destination of the relevant Integration Server for the client. It is evaluated during the HTTP communication section Sender -> Integration Server.</p><p>URL : http://<host>:<port>/sap/xi/engine?type=central</p><p>HTTP destination:  </p><p style=”margin: 0in 0in 0pt” class=”MsoNormal”>dest://<destination name>.</p><br />IS_RFC_DESTINATION : It Determines the RFC destination of the relevant Integration Server for the client. We required this for Receiver pre-identification and Access to the API of the key mapping. <p><br />HTTP_TIMEOUT :It defines the timeout between tow data packages in the network. when we set this value we overrides the system profile parameter icm/server_port_n.</p><p>For example if the network load of our company is high and speed is slow then its better to increase this else time out between 800 to 1000 can be sufficient. If you do not set the parameter HTTP_TIMEOUT or if you set the parameter to 0, then the setting for the system profile parameter is used. </p><p>Values : n Seconds, where n is a whole number.</p><br />ERROR_ON_NO_RECV_FOUND :The parameter ERROR_ON_NO_RECV_FOUND defines whether messages with the quality of service Exactly Once (EO) or Exactly Once in Order (EOIO), for which no receiver could be determined, are handled as having errors (value 1) or having no errors (value 0). Note that if you set the value to 1 for EOIO messages, the corresponding qRFC queue is stopped if the system is unable to determine a receiver. <p><br />ACK_SYSTEM_FAILURE :It defines whether system errors are reported (value 1) or not (value 0) for asynchronous messages that expect an acknowledgment.Enabling this parameter results in a slight overhead of system.</p><p><br />CACHE_DIRTY_READ:</p><p>XI use cache to optimize message processing. We need to update/maintain this on regular basis. We can do it either manually or automatically. At any time during message processing we can have two option:</p><p>We can interrupt the message processing and wait for cache refresh</p><p>Or</p><p>Use old cache content and continue process.</p><p>To speed up the processing of messages, you do not access the data required from the Integration Directory directly, but from a cache. If required, this cache can be refreshed automatically. However, it is still possible that a message is being edited just as the cache is being updated.If you set the parameter CACHE_DIRTY_READ to 0, no messages are processed while the cache is being refreshed.If you set the parameter CACHE_DIRTY_READ to 1, message processing is not interrupted by a cache refresh. This is achieved by simply using the status of cache before the cache refresh for the evaluation. Whether this results in outdated data being used depends on whether the messages concerned are in any way connected with the changed data. </p><p>value : 0 or 1.</p><p>QUEUE_COUPLING:*This guarantees serialization across the IS
migration. for

more…

*CACHE_REFRESH_PACKAGE_SIZE: </p>During the XI cache refresh, the configuration data is transported using HTTP from the Integration Directory to the Integration Server cache. The parameter CACHE_REFRESH_PACKAGE_SIZE specifies the size of the package in MB to be used to transfer this data.  <p style=”margin: 0in 0in 0pt” class=”MsoNormal”>We can consider this values after analysis of network speed and connection also configuration size of the ID.</p><p style=”margin: 0in 0in 0pt” class=”MsoNormal”> </p><p style=”margin: 0in 0in 0pt” class=”MsoNormal”>values : 1-500 MB (default setting 10 MB)</p><p><br />ENTRY_LOCK:* Itenables you to completely lock the inbound channel to the Integration Engine. This means that no new messages will be processed.

 SN

 types

 1

 Messages with all types of quality of service

 2

 Normal XI request messages and acknowledgments

 3

 Messages from external Integration Engines or Adapter Engines

 4

 Messages received by ABAP-based adapters (IDoc, RFC in XI 2.0, plain HTTP)

 5

 Messages from the local Business Process Engine

*LOGGING: *It enables you to locally activate the logging of asynchronous messages for all pipelines of an Integration Engine. You can also reactivate logging by using a message. In this case the logging tag in the diagnostic header of the message must be set to 1.

If logging is deactivated, you can reactivate it for particular pipeline services by using the corresponding subparameters. You can select the relevant pipeline services from the input help. Logging of the asynchronous message takes place after the service has been executed. You can also reactivate logging by using a message. In this case the logging tag in the diagnostic header of the message must be set to 1. 

For this only better to deactivate the logging function since we can activate it via header if needed .

values *: 0 (deactivated) or 1 (activated)</p><p><br />LOGGING_SYNC : It enables you to locally activate the logging of synchronous messages for all pipelines of an Integration Engine.Better to  deactivate logging by default and enable by logging only individually through the diagnostic header of the message.</p><p>values : 0 (deactivated) or 1 (activated)</p><p><br />LOGGING_PROPAGATION :It enables you to set locally in the Integration Engine whether the logging of a pipeline is passed on to the message. The parameter is used to pass on the logging settings to a message. Values : 0 (deactivated) or 1 (activated) </p><p><br />MAX_MESSAGE_TRANSFER_SIZE:It enables you toset the maximum size in MB of the message packages to be transferred from one system to another in a message transfer. We use this parameter to specify the maximum size of the message packages to be transferred. Values : 0 to 100 MB </p><p>

MAX_NO_TRANSFER_QUEUES :It enables us to set the maximum number of transfer queues containing the function modules responsible for data transfer called during a message transfer. we can use this parameter to specify the maximum number of transfer queues.</p><p>Values : 1 to 100</p><p>TRACE_LEVEL :TRACE_LEVEL enables you to locally set the trace level for all pipelines in an Integration Engine. However, the diagnostic header of a message can specify the trace level at which it is to be processed. Runtime then uses the higher of the local trace level and the message trace level. </p><p>Set this parameter when you want to analyze message processing as it enables you to document either individual steps or all steps in a pipeline.</p>values : <p> </p><table border=”1″ cellspacing=”1″ cellpadding=”1″ width=”392″ style=”width: 392px; height: 190px; border: #000000 1px solid”><caption></caption><tbody><tr><td> SN</td><td> Meaning</td><td> Value</td></tr><tr><td> 1</td><td> Tracing is deactivated</td><td> 0</td></tr><tr><td> 2</td><td> Document important processing steps</td><td> 1</td></tr><tr><td> 3</td><td> Document important processing steps and details</td><td> 2</td></tr><tr><td> 4</td><td> Document all processing steps and details</td><td> 3</td></tr></tbody></table><p><br />TRACE_LEVEL_PROPAGATION :* enables you to set locally in the Integration Engine whether the tracing of a pipeline is passed on to the message.The parameter is used to pass on the trace level settings to a message.Values : 0 (deactivated) or 1 (activated)

RFC_DEST_EO_PROT_TRANSFER :specifies an RFC destination from which data is transferred for the protocol Exactly Once.This parameter is used in a system relocation or a migration upgrade.

*Practical: *

Start from transaction SXMB_ADM

image

Go for integration Engine Configuration :

image

choose the specific configuration:

image

here you can updated the Runtime Parameter :

image

Available Parameters are :

!https://weblogs.sdn.sap.com/weblogs/images/251873931/RC2.JPG|height=397|alt=image|width=236|src=https://weblogs.sdn.sap.com/weblogs/images/251873931/RC2.JPG|border=0!</body>

To report this post you need to login first.

Be the first to leave a comment

You must be Logged on to comment or reply to a post.

Leave a Reply