Performance of XI Integration Engine

Hi,
Scenario: RFC <=> PI <=> HTTP
In our landscape, we have more number of RFC to HTTP interfaces(syn). I need to know about the effect in the performance of PI Integration Engine as messages per sec will be large. Specifically, how RFC Adapter will perform under high load conditons.
Regards,
Manikandan R

Kindly have the a look at the following links....This will tell you the process to enable High volume of data transfer efficiently
/people/william.li/blog/2008/03/07/step-by-step-guide-in-processing-high-volume-messages-using-pi-71s-message-packaging
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/9056c89c-1a2e-2a10-8a99-eae154e74c4e
http://help.sap.com/saphelp_nw04s/helpdata/en/42/e7bb8f7c9d3ee0e10000000a1553f6/frameset.htm
This will Help you out..................................
BR,
Sainath

Similar Messages

Error: System not configured as XI Integration Engine

Hi All,
I a getting this following error in RWB-->message monitoring -->adapter engine -->audit log
"2007-11-29 09:28:45 Error Received XI System Error. ErrorCode: SYSTEM_NOT_CONFIGURED_AS_XMB ErrorText: ErrorStack: System not configured as XI Integration Engine
2007-11-29 09:28:45 Error Transmitting the message to endpoint http://p2p:8003/sap/xi/engine?type=entry using connection AFW failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: SYSTEM_NOT_CONFIGURED_AS_XMB:.
what might be the possible errors..
regards,
Rajesh

Hi Rajesh,
you can go through these chek steps
1)go to SLD-->Business systems...and check the role of business system Web AS ABAP (tht was created during installation)...check if the role is integration server
2) go to sxi_cache and in the menu tool bar goto "GoTo" and click AE cache and see if the link is fine? whether the link in sxi_cache for AE cache is showing green traffic signal and also perform a delta refresh.
3)Check whether your business system is tied to the integration server in SLD.
4)In the transaction sxmb_adm -> Integration Engine Configuration can you check whether that role has been defined as Integration Server.
hope these checks will solve your problem
Thanks
sandeep sharma
PS:If helpful Plz reward points
Also you may check whether in specific configuration you may need to add Category as Runtime Engine_Type and current value as HUB.

Large Messages fail on Integration Engine

Hello Guys!
I have an integration scenario with large messages going from ECC to XI (RFC -> XI -> JDBC) and these messages frequently fail on Integration Engine (inbound queue SYSFAIL).
1) Can't XI process large messages?
OR
2) Is there an integration engine configuration parameter that limits message size? (I think that's not the case, because sometimes I can manually restart a message that failed on a first attemp)
OR
3) Is there an integration engine configuration parameter that limits processing time of a message?
Thanks
Julio

Hi Julio,
i think you can click on the sysfail to get more info. Check as well SM21 for the error. Assumedly it was too much for Java Runtime and you should find a temporary down destination AI_RUNTIME_JCOSERVER.
SAP note 723909 shows how to tune JVM and increase Java Heap Size.
You should control if more than one msg leads to the error. If that is the case, may be a simple change of QOS to EOIO could solve the task to avoid more than one msg processing parallel. Reducing parallel JCO server threads would be similar strategy.
A direct Java Maping could be another idea. Message Mappings will be generated to Java with a quite huge source code, a direct written mapping could be more performant / stabil.
Regards,
Udo

Message Flow in Integration Engine

Dear Friends,
Kindly can someody share how the message is flowing in Intergration engine after the message taken from Adapter engine.
If you have any block diagram it will be helpful for me

Hi Karthik,
There are 6 stpes for the message processing thats only called
PIPELINE Steps.
what are all the steps involved in the Pipeline processing.
Sender Adapter picks up the file from the file system, converts it to XML and places it in the payload of an XI-SOAP message. Then it posts this message to the Integration Server pipeline via http(s).
XI pipeline steps are:-
->Sender Agreement
->Receiver Determination
->Interface Determination
->Interface Mapping
->Receiver Agreement.
When a source message reaches the Integration server, it performs 6 steps before the message reaches the destination. The steps are:
1) Receiver Determination: This steps determines the system that participates in the exchange of the message.
2) Interface Determination: For each receiver determine which interface will should receiver the message.
3) Message Split: If more than one receivers are found, Xi will instantiate new message for each receiver.
4) Message Mapping: Mapping to transform the source message to destination message format.
5) Technical Routing: Bind a specific destination and protocol to the message.
6) Call outbound Adapter: Send the transformed message to the adapter or a proxy.
One can examine these steps in Runtime Workbench using the Transaction: SXMB_MONI.
message flow in XI
The life cycle of the message is explained in detail by taking an example scenario. The file is picked up by the Sender File adapter and the data is inserted into DB table by Receiver DB Adapter.
       The adapter engine uses the messaging system to log the messages at every stage. This log is called the Audit Log. The audit log can be viewed from the runtime work bench (RWB) to look into the details of the lifecycle of the message. During our journey we will also have a look at the messages that are logged at different stages.
Note: This article is targeted for the newbieu2019s who want to understand the message flow in Adapter Engine. So the insight into the message lifecycle is provided here by taking only the Technical adapters (File/ JDBC/ JMS/ Mail) into consideration. It doesnu2019t delve into the lifecycle of the messages that have reached XI Adapter Engine using RNIF/ BC/ CIDX adapters.
ONWARD JOURNEY:
Fig1. Message flow from Adapter Engine to Integration Server
1.     For the message to be picked up by the communication channel, the channel should be associated with a sender agreement. Here creation of a communication channel doesnu2019t ensure the message to be polled and picked up by the adapter. The message reaches the adapter in its native message format. As the communication in SAP XI happens in XI message format, a module inside the adapter converts the message in native format into XI message format.
2.     During this process, a message ID is generated for the message. To build the XI header (sender agreement details like the sender system, sender message interface and the interface namespace) the details are fetched by performing a CPA lookup(collaboration-partner-agreement are the configuration object details that have been created using the configuration time. The details are updated into the runtime cache when you activate the Configuration objects in Integration builder u2013Configuration time. This cache is referred to as CPA cache).
3.     This message is then sent to module processor for further processing. During the process of sending the message to module processor, the message u201CApplication attempting to send an XI message asynchronously using connection AFWu201D is logged.
4.     The module processor performs steps like structure conversion, communication channel specific conversions (that have been specified in the u201Cmodule tabu201D of the adapter channel). These conversion modules are executed in the same sequence as mention in the communication channel.
5.     After the successful execution of the conversion modules, the appropriate module (call SAP adapter module) of the module processor is called which will send this message for persistent storage. This message is put into the Send Queue of the messaging system for further processing. Messages like u201CMessage trying to put into the send Queueu201D and u201CMessage successfully put into the queueu201D are logged during this process. A confirmation message (success/ failure) is sent back to the sender application at this stage. This confirmation message is used by the channel to perform various steps like deleting the file that has a processing mode as delete.
6.     The message that has been put in the Send Queue has to be picked up and sent to the Integration Engine. The Adapter Engine and XI Integration server use XI Adapter for internal communication purposes. So the XI Adapter picks up message from the send queue and parses the XI message. In this process, the status of the message is set to DLNG and. Messages like u201CThe message was successfully retrieved from the send queue and message status set to DLNGu201Dare logged.
7.     The XI adapter performs a SLD look up (System landscape Directory) to find the Integration server with which the Adapter framework has register itself.
8.     On successful SLD look up, the message is sent via HTTP to the XI IS pipeline, using the pipeline URL (http://hostname:abap-httpport/sap/xi/engine?type=entry). . If this is successful, a message u201CThe message was successfully transmitted to endpoint http://hostname:8000/sap/xi/engine?type=entry using connection AFWu201D is logged and the message statues is set to DLVD means message has been successfully delivered to the endpoint( XI IS in this case)
Fig2. Audit Log of message during onward journey
RETURN JOURNEY:
The return journey commences when the IS has successfully processed the message and delivers it to the Messaging system using the URL u201Chttp://hostname:50000/MessagingSystem/receive/AFW/XIu201D
br>
Fig3. Message flow from Integration Server to Adapter Engine
1.     When the Integration Server (XI IS) finishes processing of the pipeline steps (like receiver determination, interface determination and interface mapping), the message has to be delivered to the required Receiving system. So the XI Integration server will send the message to the messaging system of the Adapter Engine (AE) using the mentioned above. Once the message is successfully received by messaging system, the message u201CThe message was successfully received by the messaging system. Profile: XI URL: http://hostname:50000/MessagingSystem/receive/AFW/XIu201D is logged.
2.     As discussed Integration server and Adapter Engine use XI adapter for internal communication purposes. So the XI message that has been received by the messaging system URL is parsed by the XI Adapteru2019s protocol handler.
3.     The XI message is put into the receive queue and persisted. During this stage messages like u201CUsing connection AFW. Trying to put the message into the request queue; Message successfully put into the queue.u201D are logged.
4.     The XI messages that are put in the receive queue are retrieved by an application (Worker thread) and are sent to AFWListenerBean. AFWListenerBean is a module (an EJB) in Adapter Engine that is capable of parsing the XI message. On successful receive of the XI message by the AFWListenerBean, messages like u201CThe message was successfully retrieved from the request queue.u201D are logged and the status of the XI message is set to DLNG.
5.     The AFWListenerBean reads the receiver agreement and the corresponding channel from the XI header to determine the appropriate adapter. In this stage the adapter channel is logged in the audit log. u201CDelivering to channel: XYZ_Channelu201D
6.     The message is forwarded to the module processor where additional steps like structure conversions and extra modules specified in the adapter are performed.
7.     The exit module is called and the message is sent to the appropriate adapter (DB Adapter in this case). The format conversion will be executed within the specific adapter and sent to the Receiving system (DB in this case) using the channel that has been determined by the AFWListenerBean and the required action is reformed (select statement is performed in this case). On successful processing of the message the status is set to DLVD.

Message Packaging feature and PI Integration engine tuning

Hi Folks,
I am trying to tune up the IEngine.
1. Do i need to restart the system whenever i make a change to any of the IE parameter. eg: EO_OUTBOUND_PARALLEL
2. Can someone help me by giving the useful transaction codes that I would need from a system prospective to check/measure the performance of the system.
Eg. CPU utilization, Dialogue processes free/used,
Message packaging is a new feature with PI 7.1
Can someone please guide me on how to implement this step by step?
Your inputs are very much appreciated!
Thanks,
Hank

Hello,
1. Integration engine tuning - No, you dont need to restart the system after changing a integration engine tuning parameter in SXMB_ADM, its a online change.
2. system performance - use transactions st03 and st06 (cpu and workload). db02 for database. sm66, sm51 (work process)
3. message packaging - check out this document for step by step configuration and a case study of message packaging
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/10b54994-f569-2a10-ad8f-cf5c68a9447c?quicklink=index&overridelayout=true
hope this helps.
regards,
francis

Integration Engine Load

1. Can someone explain how do we inprove the processing time in IE,
2, What are various steps to be taken to improve the speed,

HI,
The Integration Engine load depends upon various factors such as,
1. Valume of data to be transited across the Integration Engine
2. Memory Utilization
3. Usage of JRFC reduces J2EE memory overhead for maaping step
4. Proper system and environment configuration
5. proper integration design.
6. need a stable foundation situation. Not only the PI database, operating system and network connections must be working fine. Any connected middleware or back-end system, supposed to receive or send
information, should comply with the required performance, stability, quality of services and service
level agreement.
7. Enhanced Transaction Handling: Allows design time optimization of transaction handling, avoiding starting and ending one transaction for each integration
process step.
XI is based on SAP WAS so you can use multiple was instances - load balancing for example
have a look at this document:
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/xi/3.0/sap%20exchange%20infrastructure%20tuning%20guide%20xi%203.0.pdf
most of the performance/memory is needed for the mapping in general
Thanks
Swarup
Edited by: Swarup Sawant on Apr 4, 2008 4:44 AM

Use of Integration Engine on Application System

I would like to know - the use of Integration Engine on Application System.
Any links or docs are appreciated
reg

Hi,
The Integration Engine is the runtime environment of SAP NetWeaver usage type Process Integration. It controls the messaging process (receiving, processing, and forwarding) to and from the central Integration Server.
I agree with you about the usage to make easy for integration of systems with Proxy. Just extending to it, the integration engine has the task of receiving, processing, and forwarding XML messages.
Event driven Message Processing is also very much possible with Integration engine to control the messaging across the heterogeneous systems
Message Packaging have imporved the performance of message processing using the integration engine.
Plesae let me know if your are looking for any other things about it.
Thanks
Swarup

Auto Cancellation of Messages in the Integration Engine.

Dear all,
Issue: Auto Cancellation of Messages in the Integration Engine.
Description: Actually Today, I'm facing Problem in message mapping and its showing error "JCO_SYSTEM_FAILURE". Finally the message is Auto Canceled and showing the status in the Message Monitoring as Canceled with Errors.
I have doubt here how the messages are Auto Canceled with Error? Is there any system or ABAP program which cancelling these messages?
Waiting for yours valuable reply on the above issueu2026
Edited by: BhavinPatel on Oct 7, 2010 8:15 AM

Hi Bhavin,
Two report program are there to cancel error msgs automatically..
1) RSQIWKEX
2) RSXMB_CANCEL_MESSAGES
Regds,
Pinangshuk.

Error while testing message from Integration Engine.

Hi,
Trying to send message to Integration engine from RWB, using test mesage tab in Integration engine.
I pasted the payload(IDOC payload) , entered sender service, interface name and namespace and also username and password. Selected quality of servie as Exactly once.
While sending the message getting the following error - "Error while sending".
What could be possible reasons for this error.
Thanks.

Hi,
Please check the following possibilities:
1. Make sure you have selected integration Engine oprtion and not the adapter engine.
2. The USERID and password should be correct.
Please let me know if you still face the problem.
Regards,
Shwetambari.

Java bean, works in Integration Engine but does not work in Adapter Engine.

In connection to the following thread:
PayloadZipBean - variable filename inside the archive
I am trying to use the same bean.
However I can see, that the bean is working correctly when I use Integration Engine.
But if I am using ICo (AAE) and using the same bean in the receiver, I can see, that the bean gets called but does not work correctly.
The audit log added to my bean shows, that the bean could read the filename correctly from the Dyanic Config in the message, but it cannot write the same into the message.
Could you please help on this?

Your above posted system details show multiple Java Console extensions.
You can uninstall (remove) the Java Console extensions and disable the Java Quick Starter extension, you do not need them to run Java applets.
See http://kb.mozillazine.org/Java#Multiple_Java_Console_extensions
See also http://www.java.com/en/download/help/quickstarter.xml - What is Java Quick Starter (JQS)? What is the benefit of running JQS? - 6.0
Disable the Java Quick Starter extension: Tools -> Addons -> Extensions
Control Panel -> Java -> Advanced tab -> Miscellaneous -> Java Quick Starter (disable)
You can try a direct connection: 
Control Panel > Java > General tab > "Network Settings...": "Direct Connection" (enable)

Bypassing integration engine in pi 7.0

Hi
Am supposed to work on bypassing the integration engine in case of file to Jdbc. Am working on version pi 7.0. How can I bypass integration engine ?

hi,
Am supposed to work on bypassing the integration engine in case of file to Jdbc. Am working on version pi 7.0. How can I bypass integration engine ?
as per my knowledge(bypassing the integration engine in case of file to Jdbc) that is possiable from pi 7.1 by using ICO(AAE) concept only .
thanks,

Problems with namespace XML Parsing of ABAP PI 7.0 Integration Engine

Hi,
I discovered the following problem.
The customer sends a SOAP message with is forwarded through a SOAP Adapter in the integration engine.
The structure of the message is very simple:
<Envelope>
<Body>
<ORDERS05>...</ORDERS05>
</Body>
</Envelope>
The customer adds the namespace information a special way:
<Envelope xmlns="http://schemas.xmlsoap.org/soap/envelope">
<Body>
<orders05 xmlns="">...</orders05>
</Body>
<Envelope>
Here the namespaces is declared in the first element. It should be inherited into all child elements. The 'orders05' should not have the namespace ' xmlns="http://schemas.xmlsoap.org/soap/envelope" ', therefore the namespace is overwritten with ' xmlns="" '. However I don't know if this is a correct xml statement, the SAP system did not understand this.
The integration throws an error which is stated in the message in the adapter engine:
2008-11-06 17:31:44 Fehler SOAPFault empfangen vom Integration Server. ErrorCode/Category: XIProtocol/ITEM_MISSING; Params: /@mustUnderstand, ST: ST_XMS_MSGHDR30_RM; AdditionalText: Attribut 'mustUnderstand' erwartet; ApplicationFaultMessage: ; ErrorStack: Das XML-Element /@mustUnderstand fehlt im SOAP-Message Header (SAP XI Extension) Attribut 'mustUnderstand' erwartet
2008-11-06 17:31:44 Fehler Fehler beim Übertragen der Message zum Endpunkt http://kas052.hauni.koerber.de:8036/sap/xi/engine?type=entry über die Verbindung SOAP_http://sap.com/xi/XI/System. Grund: com.sap.aii.af.ra.ms.api.RecoverableException: Received HTTP response code 500 : Error during parsing of SOAP header
If I changed the SOAP message to the common format, it is accepted by the integration engine.
<SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope">
<SOAP:Body>
<orders05>...</orders05>
</SOAP:Body>
</SOAP:Envelope>
Here the namespace ' xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope" ' is defined with a prefix and assigned to the elements 'envelope' and 'body'. The 'orders05' element has no namespace.
However due to the xml syntax both messages are the same, so why the integration engine handle the messages different?
Best regards,
Nils Kloth

The valid SOAP format supported by XI is as follows
<SOAP:Envelope
xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SOAP:Body>
 <m:MessageTypeName xmlns:m="Some-URI">
 <Price>34.5</Price>
 </m:MessageTypeName>
</SOAP:Body>
</SOAP:Envelope>
Ur sender system is not sending the data in correct Soap format and thats the cause of message rejection. The option you have to use the Soap adapter in "no soap" mode.
Regards,
Prateek

Error in integration Engine

Hi All,
In integration Engine im getting error as "Exception occurred during XSLT mapping of the application".
when i tried to test the mapping its showing the warning as "javax.xml.transform.TransformerException: com.sap.engine.lib.xml.util.NestedException: Could not execute operation on Java Object. -> java.lang.reflect.InvocationTargetException at "
Please help me reagrding this issue to proceed further!!!

Hi,
Can u please explain the problem little detail...
Are u getting this error in SXMB_MONI??
If yes then can u copy the source payload and check it in the Message Mapping once??
If problem is coming from mapping... try to analyze.. else u can put now vtz exactly the prblm is..
Babu

HTTP error 403 from Integration engine

Hello,
Problem a)
While posing data from eSourcing to PI box by HTTP , we are getting HTTPerror 403.
The error message states:
ID: E-Sourcing was unable to publish PROP-00090--2010 to ERP. class java.io.IOException Server returned HTTP response code: 403 for URL:
Problem b)
In another observation the sender file adapter after polling the file is unable to send the message to Integration engine and gives a Connection Time out error. it gives the following error.
Transmitting the message to endpoint http://<Host>:<Port>/sap/xi/engine?type=entry using connection File_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Error transmitting the message over HTTP. Reason: java.net.ConnectException: Connection timed out: connect.
I believe that both the errors are for common cause and possibly the Integration engine is not accepting HTTP request.
It looks like these error due to security reason, it seems some authorization profile is missing or may be some other issue,kindly help us at that front.
Thanks and Regards,
Satish

Hi Suraj,
Thanks for the update.We had checked the URL before posting this message,it is picking up correct URL with namespoace, UID and PWD.Exact error that we are getting is as follows:
ID: E-Sourcing was unable to publish PROP-00090--2010 to ERP. class java.io.IOException Server returned HTTP response code: 403 for URL: http://MB1ES1025:50200/sap/xi/adapter_plain?namespace=http://frictionless.esource.com/v2.0&interface=MI_ESI_AWARD_PO&service=FCI_TENANT&QOS=BE&sap-user=pisuper&sap-password=sap$29&sap-client=001&sap-language=EN. Please contact your system administrator.
Here all information are correct.We have checked the SLD check, that is also working fine.Also it is not connectivity related issue, as we are able to transmit XML file to E-Sourcing.
It looks like security issue, but what authorization needs tobe given exactly for HTTP call, we need to know or may be some other issue.
Thanks and Regards,
Satish

HTTP error 403 to Integration engine

Hello,
Problem a)
While posing data from eSourcing to PI box by HTTP , we are getting HTTPerror 403.
The error message states:
ID: E-Sourcing was unable to publish PROP-00090--2010 to ERP. class java.io.IOException Server returned HTTP response code: 403 for URL:
Problem b)
In another observation the sender file adapter after polling the file is unable to send the message to Integration engine and gives a Connection Time out error. it gives the following error.
Transmitting the message to endpoint http://<Host>:<Port>/sap/xi/engine?type=entry using connection File_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Error transmitting the message over HTTP. Reason: java.net.ConnectException: Connection timed out: connect.
I believe that both the errors are for common cause and possibly the Integration engine is not accepting HTTP request.
Please help.
Thanks and Regards,
Himadri
Edited by: Himadri Chakraborty on Feb 9, 2010 3:35 PM

Time Out Error
In order to get rid of it, Your basis person need to play around with follwing three parameters in order to find an appropriate values as per your hardware sizing and requirement......
icm/conn_timeout
icm/keep_alive_timeout
icm/server_port_< n >
How ever, in general SAP recommandation is as follow....
icm/server_port_0 = PROT=HTTP,PORT=1080,TIMEOUT=30,PROCTIMEOUT=600 to allow a maximum processing time of 10 minutes.
Hope this helps !!!
Regards,
J Augastine

Performance of XI Integration Engine

Similar Messages

Maybe you are looking for