PI Integration Engine RUNTIME LOGGING_SYNC for individual Interfaces

Hello Colleagues,
the Integration Engine Configuration parameter (SXMB_ADM) RUNTIME, LOGGING_SYNC, 0 is an global parameter and active for all sync. interfaces.
Is there a different configuration available/possible for control individual interfaces.
That means, we need to activate syc. logging for less important interfaces, for the rest interfaces (with high rate of transfer) disable logging.
Any suggestions?
Many thanks in advance!
Regards,
Jochen

Many thanks Amit and Shabarish,
for reply!
The Blog "XI/PI: Personalized logging & tracing" from Michal was already known.
Under "Error Analisys Settings" your are able to set only a less number of "conditions" like Username, Client, MessageID, QOS and QueueID. These conditions are not really usable to control individual interfaces.
Maybe .... If logging is deactivated then it can be reactivated with a message. To do this the logging tag in the diagnostic header of the message must be set to 1 .... this is a possible way for individual control of interfaces?
Regards,
Jochen

Similar Messages

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...

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

Message Monitoring Tool in RWB for Integration Engine Messages not working

Hi all
We currently work on a Pi 7.11 system. I f we start the runtime workbench and going to the message monitoring, we want to get in to a message in the integration engine. Normaly we should get the same sxi_monitor in the web browser, but we only get the soap envelope. The pipeline steps on the left side and also the payload cannot be seen.
We increased the rights of the user to sap_all but this did not changed anything. We also implemented the J2EE monitoring rule.
Seems to me as we forgot a setting after installation, but which??
Thanks in advance for your help.
Oliver

Hi Oliver,
I work on PI 7.0 and I know it's very different from 7.1x releases, but your problem sounds like a similar "problem" on 7.0.
Is your message sycronous? At PI 7.0 the default configuration is defined to remove the payload of sync messages. You can change it on JAVA Visual Administrator.
Try to find this parameter in Java Visual Administrator and set it to "false", below you will find the PI 7.0 path to this:
Server >> Services >> SAP XI AF Messaging >> messaging.syncMessageRemover.removeBody
I hope it helps,
Marcelo Vieira

Atack interface directly in the integration engine

Hi guys.
Id like to know how to make to consume a sender interfece directly attacking the integration engine.
We work with an EDI enterprise and we only provide them the interface XSD, inteface name, interface namespace, remote user and password and they achive to consume this inteface but I don't know how.
There isn't any sender channel assoicate to this sender interface...
How could they get this? Java?
Thanks a lot!!!

Hi,
You can directly post to integration engine from your EDI using the below URL if thats what you are looking for.
http://<host>:8000/sap/xi/adapter_plain?namespace=<ns>&interface=<intface>&service=<BS>&QOS=<EO>&sap-client=<003>&sap-language=<EN>&sap-user=<user>&sap-password=<password>
This would be a direct HTTP communication and no sender channel is required. its served by the integration engine itself.
please check
http://help.sap.com/saphelp_nw04/helpdata/en/82/f4993c03e0cd37e10000000a11405a/content.htm
regards,
francis

Error In Runtime Workbench (Integration Engine)

Hi All,
I have an issue with the PI Netweaver 7.0 SR3.We change the client from 001 to newclient by following SAP NOTE.
Everything is happening fine except while i use Transaction SXMB_IFR and then Run Time Work Bench in component monitoring Integration Engine is not in Healthy State,Its showing Yellow Signal and a message is like this
Is Web service security available?
Description :Communication error Proxy calls are not permitted on sender or receiver side on the IS (client)
Also Business Process Engine is also Showing Yellow Signal as
Schedule Background Job for Missed Deadlines
    Schedule Background Job for Work Items with Errors
    Schedule Background Job for Event Queue
    Schedule background job for clearing report
    Schedule Background Job for Shared-Memory Update of Container Fa
    Schedule Background Job for Deadline Monitoring
So please suggest how to proceed to fix these issues.
Thanks,
Gagan Deep Kaushal

Hi,
for WS security please have a look at this page (last question)
http://help.sap.com/saphelp_NW04/helpdata/en/a5/1b5342d8a7be30e10000000a155106/content.htm
you can also try my answer from:
Re: RWB Integration Engine status yellow
BTW
this cal stay yellow and it does not mean that XI/PI will not work
Regards,
Michal Krawczyk
Edited by: Michal Krawczyk on Nov 29, 2008 1:11 PM

Proxy Runtime errors in Integration Engines at RWB

Hi Experts,
We have configured the point to point configuration scenario in our landscape. I have two ABAP systems exchanges data using PI. I have configured both the ABAP systems as Application Systems and Corresponding Integration server as my PI system.
In RWB of PI I can see both these systems as proxy run time under Integration Engines, but are in error status.
Path to the same is Component Monitoring>Components>Integration Engines (here I can my systems as Proxy Runtime BSAB200, Proxy Runtime BSID200).
When run the test got the below error.
Can the SLD be reached? RFC destination LCRSAPRFC does not exist
Does the Integration Engine know the business system?
Are roles in SXMS_CONF_ITEMS and SLD consistent?
Why do we need to create the RFC destination again when we select the related integration server as PI.
Can any one throw some light whey are these errors are occured.
Thanks,
Chinna

Can the SLD be reached? RFC destination LCRSAPRFC does not exist
Reached to SLD but not to exchange profile.
Does the Integration Engine know the business system?
Yes.
Why do we need to create the RFC destination again when we select the related integration server as PI.
A central SLD scenario involves a central SLD, but not a central exchange profile.
The exchange profile used is always the one on the Integration Server the
application system connects to the exchange profile using the SM59 destination
LCRSAPRFC.
Regards
Pothana

Change status for 18 million messages in the Integration Engine

Hello there!
I have the following situation and I wonder that maybe you could help. Currently I have more than 18 million messages for the BC_XMB object in the Integration Engine for a BI System (connected to a PI system).
The problem here is that the archiving/deletion jobs in this BI system are faulty since maybe a couple of years ago and all of these messages are marked as "Archivable":
What I'm trying to do here is to change the status for these 18 million messages from "can be archived" to "to be deleted" since there is no way that I can archive this 18 million messages (filesystem capacity). I've been looking many option but I cannot figure out how to do it.
Maybe, if you know an alternative way to do this, I will be very pleased to hear it.
Thanks a lot in advance.
Carlos

Raghu.
I've done the following:
1. I've executed SE38 tx code.
2. I've entered the "RSXMB_DELETE_MESSAGES" report as "Program"
3. As the "RSXMB_DELETE_MESSAGES" report does not have a selection screen, it must be executed with default parameters. So, I selected "Program -> Execute -> Background".
4. There are no available variants, so I clicked on the "Execute immed." button.
5. The job starts. I can monitor it on the SM37 tx code.
6. It only deleted 20 messages.
What I get from this, is that the "RSXMB_DELETE_MESSAGES" report cannot delete the big part of the messages since them are marked as "Archivable" and not as "Archived".
what do you think of it??
regards
Carlos.

Registration of Business system for the Integration Engine Java in the SLD issue

Hi,
We have completed the installation of PI-AEX 7.4 SR1 then we ran the below wizards successfully.
- Configuration Wizard: PI-AEX initial setup
- Configuration Wizard: PI Self Test for AEX
However when we were Checking the AEX Configuration as per help.sap.com
Check the registration of a business system for the Integration Engine Java in the SLD:
    Enter https://<host>:<port>/sld .
    Choose Start of the navigation path Business System Next navigation step Integration Engine Java <SID> Next navigation step Integration End of the navigation path.
    The pipeline URL must be: http://<host_fully_qualified>:<port>/XISOAPAdapter/MessageServlet?ximessage=true .
More information: SAP Note 1435392
for us the Pipeline URL is as below
http://<host_fully_qualified>:<port>/XISOAPAdapter/MessageServlet
and the rest " ?ximessage=true " is not there.
Also we ran the below wizard
Configuration Wizard: PI Self Test for AEX
and it finished successfully without any issue.
Any Suggestions what could be missing.
Thanks,
Regard
Ahmed Mohammed

Hi,
I found the below SAPNOTE which confirms that the Pipeline URL should be
http://<host_fully_qualified>:<port>/XISOAPAdapter/MessageServlet
1564449 - PI CTC Wrong Pipeline Url after AEX Initial Setup
However on help.sap.com it is different.
Any one experienced the same ?
Regards
Ahmed Mohammed

Integration Scenario for Enhanced Interface determination

Hello Friends,
I am modeling the integration scenario for 1:N Mapping case, that is 1 outbound Interface and 3 inbound Interfaces. I am finding difficultly in modeling the integration scenario for enhanced interface determination.
Kindly provide me inputs in configuring this case.
Thanks

Have you look this help?
http://help.sap.com/saphelp_nw70/helpdata/en/42/ed364cf8593eebe10000000a1553f7/frameset.htm
2.      Integration Directory: Define the interface determination.
Note the following:
○     The outbound interface of the multi-mapping must be entered as the sender interface in the key of the interface determination.
○     The interface determination type must be set to Enhanced.
○     Select the multi-mapping you defined previously from the Integration Repository.
To select the interface mapping, use the input help ().
The target interfaces of the interface mapping are displayed in the Inbound Interfaces frame.
The number of messages (for an inbound interface) created in the mapping step is displayed in the Occurrence column.

Customize email alert messages for Integration Engine Errors

Hi experts,
I've configured auto-reaction emails for alerts raised by Integration Engine in CCMS.
The email content I got is as below:
Subject: CCMS alerts PI1 20070319 140556
<i>ALERT for PI1 \ IEngine_PI1_001 Integration Server \ Category MAPPING \ Message alerts by Error Codes at 20070319 060447 ( Time in UTC )
RED CCMS alert for monitored object Message alerts by Error Codes
Alert Text:Error code: GENERIC error text: com/sap/xi/tf/_MM_OperationPro cInfo_ODSOperationP~com.sap.ai i.utilxi.misc.api.BaseRuntimeExceptionFatal Error:
System:PI1
Segment:SAP_CCMS_ootspdbs02_PI1_01
MTE:PI1\IEngine_PI1_001 Integration Server\Category MAPPING\Message alerts by Error Codes
Client:001
User:PIAFUSER
Severity: 50</i>
May I know how I can configure the contents of this message?
I can't seem to find them in any of the CCMS alerts settings.
Please help.
Thanks.
Ron

Hi,
Go through these links..
/people/sap.user72/blog/2005/11/24/xi-configuring-ccms-monitoring-for-xi-part-i
http://help.sap.com/saphelp_nw04/helpdata/en/17/550c404a435509e10000000a1550b0/content.htm
https://websmp102.sap-ag.de/monitoring
http://help.sap.com/saphelp_nw04/helpdata/en/2a/ae8d4243a5de54e10000000a155106/frameset.htm
/people/sap.india5/blog/2005/12/06/xi-ccms-alert-monitoring-overview-and-features
http://help.sap.com/saphelp_nw04/helpdata/en/25/27fb1c56ff3b41a5d6807d3174d5c7/frameset.htm
regards
manoj kumar

Runtime analysis for interface(in sproxy)

Hi,
I want to tune an interface(XI - sproxy). What tools can i use?
Specifically, can i use runtime analysis for interface defined in sproxy.
Any inputs will be appreciated. Thank you.

Hi,
When you create a interface using a proxy you are handling two different environments. Runtime analysis will not be applicable to end-to-end (XI->SAP for inbound) solution.
If on the SAP R/3 end you have FM/program which is triggered by the proxy you can execute the FM in standalone to get the runtime analysis of the code.
I hope it clarifies.
You can get back if you have any doubts.
Regards,
Sandeep

When we will go for Ectended Interface Determination

extended interface determination example give me any one...
Regards,
Vinay

Enhanced (Mapping-Based) Interface Determination
Use
In an enhanced interface determination, you do not enter the inbound interfaces manually, but first select a multi-mapping. You get the inbound interfaces from the target interfaces of the multi-mapping. The inbound interfaces are determined at runtime during the mapping step.
You typically use an enhanced interface determination if the source message has an element with occurrence 0 ... unbounded (for multiple items of a data record) and you want multiple messages (for the individual items) to be generated at runtime.
For example, you want to split an overall booking for a trip comprising connecting flights into individual booking orders (for each leg of the trip).
You cannot realize this usage case with a standard interface determination (without using an integration process). A standard interface determination does allow you to specify multiple (N) inbound interfaces (with different mapping). In this case, N messages with the same payload and different receiver interfaces are generated from the source message before the mapping step; these are then transformed differently depending on the receiver interface. Therefore it is conceivable to write the mappings in such a way that the first mapping from the source message generates a message that only contains the first item, the second mapping generates a messages that only contains the second item, and so on. However, this no longer works if the number of items can vary with each new source message.
You can use an enhanced interface determination to configure a mapping-based message split for this usage case. You assign the interface determination a multi-mapping that has a target interface with an element with occurrence 0...unbounded. At runtime, the individual messages (for the individual items) are calculated in the mapping step. First, the individual messages are grouped into a bulk message. Then, the bulk message is transferred to the Adapter Engine. The Adapter Engine then splits the bulk message up into the individual messages (see figure).
Procedure at Runtime During Message Split
Note that both the bulk message and all individual messages each have a message header with a receiver interface (see figure).
Receiver Interfaces of Bulk Messages and Individual Messages
The header of the individual messages contains the relevant receiver interface. It is based on the definition of the multi-mapping. Note that the receiver interfaces of the individual messages may be different. The receiver interface of the bulk message is always InterfaceCollection (namespace http://sap.com/xi/XI/System).
If the message split only results in one message, the original message structure remains the same. In this case, a bulk message containing just one individual message is not created.
You can also assign a multi-mapping with multiple different target interfaces to an enhanced interface determination (1:n transformation). Each target interface can contain elements with occurrence 0 ... unbounded.
Messages cannot be sent by using different Adapter Engines in a mapping-based message split. This affects configuration thus: All receiver agreements that have a receiver interface from the mapping entered in the key must only be assigned communication channels with the following adapter types:
-          RFC adapter
-          SAP Business Connector adapter
-          File/FTP adapter
-          JDBC adapter
-          JMS adapter
-          SOAP adapter
-          Marketplace adapter
-          Mail adapter
-          RNIF adapter
-          CIDX adapter
The adapters also have to all run on the same Adapter Engine.
Adapters developed by partners also support a mapping-based message split if they run on the same Adapter Engine.
Attachments from the original message are not appended to the messages resulting from the message split.
Activities
To execute a mapping-based message split, perform the following steps:
       1.      Integration Repository: Define the multi-mapping (see Developing Multi-Mappings for Message Splits).
       2.      Integration Directory: Define the interface determination.
Note the following:
○     The outbound interface of the multi-mapping must be entered as the sender interface in the key of the interface determination.
○     The interface determination type must be set to Enhanced.
○     Select the multi-mapping you defined previously from the Integration Repository.
To select the interface mapping, use the input help ( ).
The target interfaces of the interface mapping are displayed in the Inbound Interfaces frame.
The number of messages (for an inbound interface) created in the mapping step is displayed in the Occurrence column.
regards,
Raj

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

Mapping Runtime failing for all messages

Hi Experts,
We are facing an issue with our mapping runtime in the integration engine. Any message going through the integration engine is giving a mapping error as shown below (for example):
LinkageError during appliction Java mapping com/sap/xi/tf/_MessageAcknowledgement_to_Order_Responce_ERP_Async_In_ Thrown: java.lang.NoClassDefFoundError: com/sap/aii/utilxi/threadutil/ThreadUtil_map
LinkageError during appliction Java mapping com/sap/xi/tf/_MM_Jdbc_test_ Thrown: java.lang.NoClassDefFoundError: com/sap/aii/utilxi/threadutil/ThreadUtil_map
The complete trace of the error is attached here.
The interfaces were working and messages were flowing normally. As part of our SAP HCM to SuccessFactors implementation, we configured 3 interfaces and even this was working fine. To solve a specific issue during implementation, we applied the following SAP notes:
1869807 - SFSFI: PI Content Correction for HTTP Cookie Handling
Pre-requisite for above note - 1838921 - Multiple cookies in HTTP Header
After this, messages of all the interface in this system are failing with the above issue (LinkageError).
Please guide us in resolving this issue.
Thanks & Regards
Sudheer

Hi All,
In addition to the above, if mapping is tested within ESR there is no issue. The problem is happening only during runtime.
BTW, When we applied the note 1838921 we upgraded the Adapter Framework from SP09 to SP12.
Could this be an issue?
Regards,
Sudheer

PI Integration Engine RUNTIME LOGGING_SYNC for individual Interfaces

Similar Messages

Maybe you are looking for