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

Similar Messages

What messages does it shows the integration engine(sycn/ asyn)?

What messages does it shows the integration engine(sycn/ asyn)?

Status: TO_BE_DELIVERED
Which means that the message was successfully delivered from Integration Server point of view and it states that the messages is initially handed over to the Messaging System.
TO_BE_DELIVERED occurs while the message is put into the Messaging System receive queue.
Solution:
This is done via the Messaging System receive servlet:
http://<Host>:<PORT>/MessagingSystem/receive/<CONNECTION>
/<PROTOCOL>
Only if this was executed successfully the Messaging System returns HTTP 200 to the Integration Server and the Status TO_BE_DELIVERED moves to DELIVERING
1. Try logging into Sap GUI with two users: XIAPPLUSER & XIAFUSER
to see if they are blocked
2. We can check the messages:
AdapterFramework
com.sap.aii.adapterframework.serviceuser.language
com.sap.aii.adapterframework.serviceuser.name = XIAFUSER
com.sap.aii.adapterframework.serviceuser.pwd
ApplicationSystem
com.sap.aii.applicationsystem.serviceuser.language
com.sap.aii.applicationsystem.serviceuser.name = XIAPPLUSER
com.sap.aii.applicationsystem.serviceuser.pwd
in the exchange profile to make sure the right passwords

Larsen and Toubro Integrated Engineering Services - Looking for NI Platform specialists

L&T IES is looking at hiring LabVIEW developers with core expertise in either Auto/Aero/Industrial/Medical domains.
Strong knowledge of LabVIEW core and other toolkits/add-ons like VeriStand / TestStand / RT / others is required
Experience Level: 1 - 8 years
US Work Visa will be a plus
Core experience in ATE hardware will be an advantage
Please call me @ 9902 363 513 / mail @ [email protected]
Regards
Ashwin Richard
Program Manager
L&T IES

Sir,
I'm a fresher of 2010 passed out with a degree of B.E (Biomedical Instrumentation Engineering)..i've cleared d CLAD certification exam conducted by NI...At present i'm undergoing an internship at NI..How do i apply for the job in your concern?..Please do help me in finding a way for the career in the medical field along with NI products...

SAP MRS product features and modules integrated

Hi
Looking for SAP MRS product details with modules integrated
Regards,
Parameshwar

Yes i possibly feel there are some more services which are not activated in the system.
Try using Transaction NWBC in SAPGUI & then follow the various Applications to to reach to appointment booking.
Once NWBC opens follow the service advisors cockpit. /DBM/SERVICE_ADVISOR.
Step by step it will first ask you to search vehicle / customer & then once vehicle is searched you can continue to proceed to appointment application to book an appointment
Ensure the master data is set up for the vehicle & customer to be able to search in the service advisors cockpit
Ensure you have all the roles of the assigned to your user id these application appear in the your users menus.
Regards,
Sachin Balmiki

Message ID in Integration Engine and Adapter Engine

Hello,
I have one question related to messages generated in XI.
Is the Message ID specified in the Integration Engine same as the Message ID used during the Message transformation in the Adapter engine?
What is the message flow once the message reaches XI and vice versa?
Regards,
Gajendra.

Yes.it is the same ID used .
once the message reaches XI it goes thorough IS which has pipe line steps such as inbound processing receivr determination ,interface determination, techincal routing,mapping,outboundporcessing etc.
for more look at this link
http://help.sap.com/saphelp_nw04/helpdata/en/01/d9d43fb9490c65e10000000a114b1d/frameset.htm

No message reach into Integration Engine ...

Hello,
I have following problem. I send message to XI through SOAP adapter. But the message doesn't reach of Integration Engine. It is delivered into Adapter Engine and then it stays in status "Waiting". When open message detail in RWB I get these information:
Message Data
Attribute     Value
Engine     Adapter Engine
Status     Waiting
Repeatable     Yes
Cancelable     Yes
Start     29.08.2008 12:14:59
End     29.08.2008 12:14:59
+Sender Party     +
Sender Service     BS_GetSupperior
Sender Interface     http://sntcz.cz/xmlns/holidays
MI_Holiday
+Receiver Party     +
+Receiver Service     +
+Receiver Interface     +
Quality of Service     Exactly Once
Error Category     XI_J2EE_ADAPTER_XI_HANDLER
Error Code     GENERAL_ERROR
Message     55C9628075B311DDABE200301875333B
+Reference     +
... and in defaultTrace file occures this message:
#1.5#00301875333B0057000000DE0000109C00045596D2CD72D8#1220006176812#com.sap.aii.af.ra.ms.impl.core.queue.SendConsumer##com.sap.aii.af.ra.ms.impl.core.queue.SendConsumer.onMessage(QueueMessage, boolean)#J2EE_GUEST#0##srvbr05_NW4_2798750#XISUPER#18255d00759d11ddc1a500301875333b#SAPEngine_Application_Thread[impl:3]_31##0#0#Error##Java###Transmitting the message to endpoint using connection failed, due to: .#3#AFW#com.sap.aii.af.ra.ms.api.RecoverableException: Received HTTP response code 500 : Error during conversion of XI message#http://srvbr05:8000/sap/xi/engine?type=entry#
#1.5#00301875333B004B0000009D0000109C00045596D2CE9B64#1220006176890#com.sap.aii.messaging.srt.xmb.XMBWebServiceExtension#sap.com/com.sap.aii.af.soapadapter#com.sap.aii.messaging.srt.xmb.XMBWebServiceExtension#XISUPER#2919##srvbr05_NW4_2798750#XISUPER#ecff64f075af11dda90200301875333b#XI SOAP[BS_GetSupperior_SOAP/BS_GetSupperior/]_2449##0#0#Error##Plain###no message ID available#
#1.5#00301875333B0049000001270000109C00045596D3111C00#1220006181250#XIRWB.com.sap.aii.mdt.api.server.MessageMonitoringBean#sap.com/com.sap.xi.mdt#XIRWB.com.sap.aii.mdt.api.server.MessageMonitoringBean#XISUPER#2920##srvbr05_NW4_2798750##f03f74c075af11ddb4ce00301875333b#SAPEngine_Application_Thread[impl:3]_3##0#0#Error#1#/Applications/ExchangeInfrastructure/RuntimeWorkbench#Plain###enrichMessageData(): Error during retrieving the end-to-end-monitoring information
Thrown:
com.sap.aii.rwb.endtoendmonitoring.util.Sxmb_Get_Pmi_Info_Fault_Exception:
     at sun.reflect.GeneratedConstructorAccessor358.newInstance(Unknown Source)
     at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
     at java.lang.reflect.Constructor.newInstance(Constructor.java:274)
     at java.lang.Class.newInstance0(Class.java:308)
     at java.lang.Class.newInstance(Class.java:261)
     at com.sap.aii.proxy.framework.core.JcoMarshaler.unmarshalException(JcoMarshaler.java:429)
     at com.sap.aii.proxy.framework.core.JcoProxy.send(JcoProxy.java:82)
     at com.sap.aii.proxy.framework.core.AbstractProxy$JcoProxyHelper.send(AbstractProxy.java:173)
     at com.sap.aii.proxy.framework.core.AbstractProxy.send$(AbstractProxy.java:141)
     at com.sap.aii.rwb.endtoendmonitoring.util.PMI_PortType.sxmb_Get_Pmi_Info(PMI_PortType.java:28)
     at com.sap.aii.mdt.api.server.MessageMonitoringBean.enrichMessageData(MessageMonitoringBean.java:965)
     at com.sap.aii.mdt.api.server.MessageMonitoringBean.setMessageList(MessageMonitoringBean.java:762)
     at com.sap.aii.mdt.api.server.MessageMonitoringBean.getPureMessageList(MessageMonitoringBean.java:568)
     at com.sap.aii.mdt.api.server.MessageMonitoringObjectImpl0.getPureMessageList(MessageMonitoringObjectImpl0.java:1016)
     at com.sap.aii.mdt.api.server.MessageMonitoring_Stub.getPureMessageList(MessageMonitoring_Stub.java:1772)
     at com.sap.aii.mdt.server.integrationserver.IntegrationServerMonitoringBean.getMessageList(IntegrationServerMonitoringBean.java:354)
     at com.sap.aii.mdt.api.server.MessageMonitoringBean.setMessageList(MessageMonitoringBean.java:744)
     at com.sap.aii.mdt.api.server.MessageMonitoringBean.getMessageList(MessageMonitoringBean.java:552)
     at com.sap.aii.mdt.api.server.MessageMonitoringObjectImpl1_1.getMessageList(MessageMonitoringObjectImpl1_1.java:657)
     at com.sap.aii.mdt.api.server.MessageMonitoring_Stub.getMessageList(MessageMonitoring_Stub.java:810)
     at com.sap.aii.mdt.util.WebUtil.generateTableViewModel(WebUtil.java:1254)
     at jsp_monitor_new1219936385390._jspService(jsp_monitor_new1219936385390.java:9)
     at com.sap.engine.services.servlets_jsp.server.jsp.JspBase.service(JspBase.java:112)
     at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:544)
     at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:186)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:321)
     at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:377)
     at com.sapportals.htmlb.page.PageProcessorServlet.handleRequest(PageProcessorServlet.java:68)
     at com.sapportals.htmlb.page.PageProcessorServlet.doPost(PageProcessorServlet.java:22)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266)
     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:160)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
If I try to send message to XI directly through HTTP adapter the message is not delivered into Integration Engine.
Do you have any idea what to check or where could be problem?
Thank you in advance for every advice!
Best regards,
Zbynek

Hi Zbynek,
I think the problem is in the structure of the xml you want to send. I mean, that the structure of the message you are sending by means of SOAP adapter is not the same that the structure in the Inegration Repository.
When you test your message with a wrong BS it is sent to the IE and you can see this message in sxmb_moni with error status. It`s obvius, there is no configuration for this scenario. However if you test your scenario with right parametes but the content (xml structure) is wrong, the step when the content of the call is converted to the structure of the IR will fail. And the message doesn`t get the IE.
So check the content of your call.
I hope it is useful for you.
Regards,
Carlos

How to find the IDOC for the archived message in integration engine

Hello experts
In my outbound scenario (Idoc to file), I have a message id got processed from integration engine (SXMB_MONI) but failed in adapter engine (RWB) on 1week back, The same message archive in SXMB_MONI but i found same message in adapter engine.
My question is how to find the archive message IDOC num
We can't find in adapter engine it will show only (sender service, receiver service and interface date and time as well and receiver structure in message content tab) but not idoc no,
Kindly provide the solution for the issue, Is there any alternative to find the idoc?
I can search with partner in sap side but i can get lot of idoc's
Thanks & Regards
Rajashekar

> We can't find in adapter engine it will show only (sender service, receiver service and interface date and time as well and receiver structure in message content tab) but not idoc no,
>
> I can search with partner in sap side but i can get lot of idoc's
Hi,
If solution given by experts in above replies doesn't work then you can try below method.
What you can do is, take some unique values from message content tab (which came in some specific segment from IDOC)
Now in R3 use tcode WE09 and set the dates when this was processed. Set other filter criteria as much as possible e.g. direction, idoc basic type, port, partner etc and at the bottom you can "Fast search mode" their you give the segment name and it's value.
This will help you get you IDOC.
Regards,
Sarvesh

Interaction between Qout scheduler and Integration engine

Hello,
I would like to understand more about the XI 3 architecture regarding the place of qRFC. If I understood right, depending on the QOS, the qOUT scheduler is used to send XML documents comming from the Integration Engine. The qOUT scheduler is able to process and queue rfc calls using traditional RFC ports (for example in case of CIF for APO). I imagine that in the case of XML message shipping, the qOUT scheduler is called by the Integration Engine messaging logic layer. But then, I don't understand how outgoing SOAP calls occure. Are the queued RFC calls in destination of the local SOAP framework which uses the ICM to talk SOAP with the partner?
Thanks for your lights,
Christian.

Thanks Holger for youor quick and precise answer,
You mean, that the connection between the adapter framework and the integration engine is pure rfc based and not Soap-based XI protocol ?
Is XI protocol used between the two engines each time no qRFC is envolved and in this case, the Abap-based Soap framework and the ICM are used by the integration logic layer of the central integration engine to communicate with the adapter engine ?
Thanks,
Christian.

Difference between Integration Engine and Integration server.

can any 1 explained in detail about difference between Integration Engine and Integration server.
thanks in advance

Integration Server and Integration Engine are used synonymous with each other. But there is a sublte difference if you actually look into the XI architecture images provded by SAP.
The Integration Server contains,
1. Adapter Engine
2. Business Process Engine
3. Integration Engine.
So, taking this into picture I guess Integartion server is a collection of these 3 while integration engine is one of the runtime components of XI. All messages are processed in the Integration Engine.
regards
Bhavesh

Adapter PLAINHTTP cannot process message packages

Hi,
I'm receiving 10 lines in one message from ERP and then PI splits them to individual messages. When PI tries to send messages using plain HTTP, I got error saying "Adapter PLAINHTTP cannot process message packages".
Message packaging is not on and SXI_MONITOR shows messages in separate payloads.
br,
Tapio

This is my assumption.
Multiple messages that result from mapping are sent as one bulk message (grouped together) in the Integration engine. The messages are really split into individual mesges only in the adapter engine. Since HTTP adapter live in Integration Engine and you use HTTP as receiver, you get this error.
Refer the conclusion portion of the link for further explanation.
/people/jin.shin/blog/2006/02/07/multi-mapping-without-bpm--yes-it146s-possible

Messages going to the wrong Integration Server

Hello All,
We saw a problem with few messages on the production XI server for a brief period of time. the following is the scenario.
1) An ORDERS05 IDoc comes out of the ECC, gets correlated and was sent out to conversion Agent for translation and was sent out to the vendor.
2) We get the response 997 from the vendor to the file port. This message has been picked up by the file adapter, got translated and was sent out to the XI Integration engine on the development box.
I could see this message on the RWB under the Adapter Engine component. This message did not reach the Integration engine on the Production box. A close look at the message details tells me that the message was sent to the Integration engine on the Development box. This happened to a few messages with in a minute time frame. All the messages before and after the minute time frame made just fine to the XI integration server.
We checked the SLD and found no reference of Production box pointing to the development XI IS.
I appreciate any pointers in this regard.
Thanks.

Hi Balu,
this could happen if your XI DEV system has a file adapter containing the same source directory where your response from vendor is coming for production.....this file adapter will be active....so it is pickng your response and triggering it to XI DEV before XI prod can pick it up.........it is also possibel that your XI PRD system file adapter is currently deactive or has some error in it now.......So just check the file adapters of XI DEV and XI PRD for your this scenario......
Thanks,
Rajeev Gupta

Mail-Adapter Integration Engine Error during parsing of SOAP header

Hello,
we use XI with the mail adapter. Most of the messages are processed correctly. But sometimes I get following errors in the J2EE-logviewer:
Transmitting the message to endpoint http://<xi-host>:<http-port>/sap/xi/engine
?type=entry using connection AFW failed, due to: com.sap.aii.af.ra.ms.a
pi.RecoverableException: Received HTTP response code 500 : Error during
parsing of SOAP header.
Failed to transmit message 4e913640-4cc5-11dc-8560-00e000c55366(OUTBOUND)
due to com.sap.aii.af.ra.ms.api.RecoverableException: Received HTTP
response code 500 : Error during parsing of SOAP header.
Retries exceded, set message
4e913640-4cc5-11dc-8560-00e000c55366(OUTBOUND) to status NON_DELIVERED.
Has somebody else the same problem and solved it or any idea what the matter could be?
Thanks for your help
Christian

Hi Reddy,
We´ve got the following scenario:
Exchange-Server (is always up)
XI Mail-ReceiverAdapter
I use IMAP4 to access the Outlook-Email-Box
Everything works fine. But some Emails aren´t processed.
I think it´s a problem between adapterframework and the integration engine?
There is no difference between the emails?
If you´ll need further informations ask me?
Thanks

Message not passed to Business Process Engine

Hi,
I have a simple test scenario:
File --> Integration Process --> File
The process only has a reveive and a send step and sends the message further using the File adapter (this is just for testing purpose and no real-life scenario).
This works correctly until the message needs to be passed to the Business Process - in message monitoring I can see that the receiver and interface determination worked successfully and that the message needs to be passed to the Integration Process and that's it. No active process, no obvious error message...
Any hints what I could do to analyze what's happening? Where can I find more information on what the problem could be (any additional logs, monitoring, etc.)? What can go wrong when a message is passed from the Integration Engine to the BPE?
Thanks for your help,
regards,
Peter

OK Im trying to understand you....
Your saying that it works correctly until the BPM...
Well this is not possible as the first step would be the sending from the source Business system to the Integration Process so in essence you would have not done anything....
Basically the flow is Comm channel to Pipeline which then sends to BPM which then sends back to the pipeline and to the target system. So in SXMB Moni no receiver would of been foun if you are saying that it doesn't get to the BPM....
Maybe im not understanding properly....
In fact now that I think about it... Have you specified the message in BPM... (Abstract Interface etc)
Message was edited by:
Alex Ong

Undesrtanding Proxy communication with the Integration Engine

I want to understand all the process in a client proxy communication. I know that the Local integration engine sends a PI-SOAP to the Central Integration Engine, and the local integration engine makes the communication with the ICM in the SAP PI side. My question are the next:
1. SAP documentation mentions that the XI Adapter is necessary. Where is it located?, after or before of the ICM in the SAP PI side. What is it function?, because the message is already in PI-SOAP format.
2. How does the local integration engine send the PI-SOAP message? Does it need an XI-Adapter ?.
Thanks in advance.

HI,
1. SAP documentation mentions that the XI Adapter is necessary. Where is it located?, after or before of the ICM in the SAP PI side. What is it function?, because the message is already in PI-SOAP format.
2. How does the local integration engine send the PI-SOAP message? Does it need an XI-Adapter ?.
-->XI Adapter is necessary only at the receiver side not at the sender side, by using proxy pre-configuration steps and proxy framework message from the sender system(Client proxy) will reach PI system. So, in this case XI adapter is not necessary(adapterless communication).
Proxy Framework which consists of Proxy Generator and Proxy Runtime:
Proxy Generator- Converts ABAP corresponding elements to WSDL corresponding elements and viceversa and by using Proxy Runtime, local Integration will be connected to Central Integration.
When a request is sent form client proxy-->ABAP corresponding elements will be converted to WSDL elements and local integration engine will be connected to central integration engine and whole process will be done.
If the receiver system is SAP, and since there can be many SAP systems connected to PI, to send data from PI to that particular receiver SAP system, PI needs the receiver system details like business system name etc. So, XI adapter is manadatory only at the receiver side.
check out this blog for more info:
[http://www.****************/Tutorials/XI/ABAPProxy/page1.htm]
Regards,
Sunitha

Adpater framework using qRFC to send data to integration engine ?

HI Forum,
when adpater framework sends data to the integration engine, i suppose it uses a qRFC, and when integration engine sends data to adpater framework,
Is my assumption correct, if so,
can i get a description about it,

>>>if i have a file to XI scenario, and my file adapter says EO, then it uses tRFC to send data to integration engine,
and if i configure my file adapter as EOIO, then it uses qRFC,
Correct.
>>>when integration engine sends data to adapter.....what does it use qRFC or tRFC, and its governed by what
Same concept. If the message was transmitted using EOIO QoS, then EOIO is maintained in AE also. EOIO is always achieved using qRFC. But the details of how EOIO is achieved with in AE is still a gray area for me..
Regards,
Jai Shankar

Message Packaging feature and PI Integration engine tuning

Similar Messages

Maybe you are looking for