Exchange Infrastructure (XI)

Integration Engine Configuration








0 – Syntax Check is deactivated


1—Syntax Check is activated

Recommended value: 1

If set ‘On’ check the IDoc is syntactically correct or not by using the metadata of IDoc from IDX2



0 – No IDoc- XML Conversion


1 – Every IDoc is converted to IDoc XML


2 – An IDoc is converted to IDoc-XML only when requested

If IDoc is not converted into IDoc-XML, then it is transported as a table. This is preferred, if source and target systems are sending and receiving IDocs and helps in system performance.


(Sync/Async Communication)


Between 0 and any integer


Measured in seconds

Runtime to wait time between the arrival of synchronous request message and asynchronous response message on the integration server.

System throws an error if the wait time is exceeded.

Sync/Async Communication


0 to 1000

Represents the number of waiting processes on the integration server.

System throws an error if the number of waiting processes are exceeded this number

Business Process Engine


0 – Inbound channel to BPE is not locked


1 – Inbound channel to BPE is locked

To lock the inbound channel of BPE.

Set ‘On’ locks the inbound channel of BPE and none of the new messages are processed but only the messages with QoS as ‘Exactly Once’ can be restarted.

Used while Up gradation of XI.




0 – CCMS Monitoring switched off


1 – CCMS Monitoring switched on

Self explanatory




0 to 999

Default : 7

Number of days to trigger alert from CCMS for XML messages with the status application error.





0 – Restart of a message is not possible in qRFC monitor


1 – Restart of a message is possible in qRFC monitor

Set ‘On’, failed XML message can be restarted in qRFC monitor.

Set ‘Off’, runs into error occurs at runtime.

TCode for qRFC Monitor: SMQR




RFC destination

This destination can be used to communicate with TREX server for indexing messages in Integration Engine


Performance Monitoring


0 – Auditing data is gathered on the Integration Server


1 – In addition to the Auditing data, Runtime data is also gathered includes main processing steps only.


2 – (1 above) + runtime information from persistence layer is also written to header attribute ‘Performance Header’

Default value: 1

Two types of data:

Auditing: Sender, Receiver, Mode of execution and size of message etc…

Runtime: Time taken for each processing step. This data can be viewed through SXMB_MONI in header attribute ‘Performance header’



0 – Runtime data is not persisted


1 – Runtime data is persisted

Set ‘On’, Runtime in header attribute ‘Performance Header’ is persisted in Performance monitoring of RWB



<n> days

Has two Sub parameters:

MEASUREMENT_ITEMS – Runtime data of pipeline services




Number of days runtime data stored in separate tables. Once exceeded data will be marked for deletion.




UNDEFINED: Client is not configured as Integration Engine


HUB: Client is configured as Integration engine


LOCL: Client is configured as sender/receiver system means it has local integration engine

Defines the type of the Integration engine for the current business system, i.e., whether the client is configured as central integration engine or local integration engine.



If IS address, then URL in the format http://<host>:<port>/sap/xi/engine?type=central

If HTTP destination, then dest://<RFC destination>


Determines the address of the Integration Server for the client



<n> seconds

Maximum time needed to establish a HTTP connection.


Incase this is not set, system profile parameter ‘icm/server_port_n’ is used or the value is set to 0



0 – Messages are handled as having no errors


1 – Messages are handled as having errors

Defines the behavior when receiver was not determined with the quality of service EO or EOIO.

Set ‘On’, messages are handled as having errors and for EOIO the corresponding qRFC queue is also stopped



0 – System errors are not reported

1—System errors are reported

System errors of all asynchronous messages with acknowledgement are to be reported or not.



0 – No messages are processed while cache is being refreshed


1 – Messages are processed while cache is being refreshed

Determines the messages are to be processed or not while cache is being refreshed



0 – Inbound channel is not locked

1 – Inbound Channel is locked

Defines whether new messages are to be processed or not.

Used to lock the inbound channel to the IE during SAP XI upgrades


Please send us your feedback/suggestions at webmaster@SAPTechnical.COM 

HomeContribute About Us Privacy Terms Of Use • Disclaimer • SafeCompanies: Advertise on SAPTechnical.COM | Post JobContact Us  

Graphic Design by Round the Bend Wizards

footer image footer image