SOAP - RFC scenario EOIO

Hi,
I have configured this scenario and am able to have it work fine from the runtime workbench but
now I am trying to develop a web service client for it and am not sure how this will work.
The scenario is , Netweaver CE calls web service (SOAP) in PI, PI calls RFC in ERP.
I want the RFC to be called in EOIO so EOIO needs to be passed to PI when the soap service is called.
How can you generate a client in netweaver CE that will call the web service with EOIO QOS flag ?
Can you just set this flag somewhere ?
Can other clients also call this web service with EOIO flag ?
Thanks.

Hi,
I had a similar requirement(Best Effort) where i have used the below URL format to make the scenario work....The quality of service should be added at the end of the URL, with the "Use Query String " and "Use Encoded Headers " parameters being checked in your soap channel.
The url to be used is -
http://host:port/XISOAPAdapter/MessageServlet?senderParty=&senderService=abc&interface=xyz&receiverParty=&receiverService=&interfaceNamespace=http://abc.com/xi/testbox/admin&QualityOfService=BestEffort
For EOIO - &QualityOfService=ExactlyOnceInOrder&QueueId=1234
For EO - &QualityOfService=ExactlyOnce
Regards,
Swetha.

Similar Messages

Which is better XI 3.0 or PI 7.1 for SOAP- RFC scenario.

Hi All,
I have to Create SOAP to RFC Sync Scenario.
I know PI 7.1 is advance. So there must be a edge over XI3.0.
Is is better to use PI7.0 insted of Xi 3.0 for this?
then Why?

Hi,
this blog might be interesting:
http://www.sdn.sap.com/irj/scn/index;jsessionid=%28J2EE3417500%29ID0033175050DB10487845846410196322End?rid=/library/uuid/504da602-3bac-2c10-f5a3-bcfa6587d47b
For example it says:
> Further connectivity options are provided on the AAE, such as XI message protocol using the SOAP adapter: For example, this > permits fast access to ABAP backend systems based on the proxy technology.
Regards
Patrick

Explain me SOAP - RFC scenario?

Can any one brifely explain me about the SOAP sender configuration settings (i.e like after we create the wsdl structure how to use it )

Hi praveen,
check this links
Invoke Webservices using SAPXI
http://help.sap.com/saphelp_erp2004/helpdata/en/31/daa0404dd52b54e10000000a1550b0/content.htm
https://www.sdn.sap.com/irj/sdn?blog=/pub/wlg/1442 [original link is broken] [original link is broken] [original link is broken]
http://help.sap.com/saphelp_nw04/helpdata/en/9f/fdca3f01f33e1ce10000000a114084/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/69/a6fb3fea9df028e10000000a1550b0/frameset.htm
Re: WebService
Re: SOAP Client for Synchronous Scenario
regards
srinu

SOAP to RFC Scenario (automatic updation)

Hi All,
I have a requirement, i.e we have a web system. In that gold rates will update in every one hour.
When ever the update will happen that should be update in SAP system via RFC call automatically.
Here sender side I am using SOAP adapter.
I know the process to do the soap--rfc scenario.
But how the gold rates will updates automatically in SAP system, with out triggering some one?
can any one guide me to do this scenario.......
Thanks in advance......

Hi Maridu,
yes with availibility time planning you can choose daily: monday, tuesday, not wednesday (for instance), thursday, etc.., plus for these day, a run which begins at 17:00 during 4 hours (for instance)... so to define a range, but that, it's mainly usefull with a FILE adapter as we have a polling (e.g every 60S or 3600S = 1h).
but as you, you use a sender SOAP, and if I'm not wrong (I have not a PI under eyes just now) you have not a polling. So a solution should be to define several availibility-time plannings (one per hour) on your same sender CC. Low work effort and easy to do.
Another solution is to not use availlibility-time planning, but to define your sender CC as "external" in "RWB -> CC monitoring", and to use an external tools (*) to trigger externally this sender CC, in fact to call an HTTP address by passing the "party | businessComponent | Sender CC" plus an action (STOP or START, this CC). There are several blogs on SDN to know how to trigger externally a CC (sender or receiver).
(*) external tool can be a unix command (wget), or a scheduler tool (to buy) like $universe (for instance) or eventually a sap job which run an abap program which call this HTTP address.
regards
mickael

Payload not visible in cc monitoring for SOAP-RFC synchronous AAE scenario

Hello consultants,
I have a synchronous SOAP-RFC scenario over the AAE (Java only). When I test the service in WSNAVIGATOR the response message contains an error that results in the error message:
"<s:SystemError xmlns:s="http://sap.com/xi/WebService/xi2.0">
          <context>XIAdapter</context>
          <code>ADAPTER.JAVA_EXCEPTION</code>
          <text><![CDATA[
java.io.IOException: Parsing Error: org.xml.sax.SAXParseException: The processing instruction target matching "[xX][mM][lL]" is not allowed." the same errror is present in communication channel monitoring for the SOAP adapter.
The status in message monitoring however is succesful.
Is it possible to check the payload for the response message of the RFC call. In CC monitoring I cannot access the payload, it is not there. It does not have to be in cc monitoring, anywhere would be fine.
Since this is an AAE scenario there are no messages in SXMB_MONI.
All tips are appreciated.
Peter Jonker

Hello!
Please set the "messaging.syncMessageRemover.removeBody" parameter to "false", on the SAP XI AF Messaging Service. Use the help page below for more information.
Properties Related to the Messaging System:
http://help.sap.com/saphelp_nw04s/helpdata/EN/59/25ee41c334c717e10000000a155106/frameset.htm
Best regards,
Lucas Santos

Soap -- XI -- IDOC/RFC scenario

Hello,
I have a jsp page that working in tomcat server.
I want to send values from jsp page to xi to r/3. I think it will have
soap-- xi -- IDOC/RFC scenario
Pls send me pdf /doc to implemet it
Regards

Hi,
Please Refer the Following Links
/people/shabarish.vijayakumar/blog/2006/03/23/rfc--xi--webservice--a-complete-walkthrough-part-1
/people/shabarish.vijayakumar/blog/2006/03/28/rfc--xi--webservice--a-complete-walkthrough-part-2
/people/siva.maranani/blog/2005/09/03/invoke-webservices-using-sapxi - Invoke Webservices using SAPXI
/people/siva.maranani/blog/2005/03/01/testing-xi-exposed-web-services
/people/michal.krawczyk2/blog/2005/03/29/configuring-the-sender-rfc-adapter--step-by-step
https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/2131 [original link is broken] [original link is broken] [original link is broken] [original link is broken]
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/336365d3-0401-0010-9884-a651295aeaa9
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/336365d3-0401-0010-9884-a651295aeaa9
Regards
Khanna

SOAP Sender to RFC Scenario WSDL File

Hi,
I am working on SOAP -> PI -> RFC Scenario. I generated WSDL from sender agreement and gave to the client that can consumed by the third party system. But client is not ready to consume the WSDL. He provided WSDL and asking me to use that. Could you please suggest whether WSDL given by the client can be used in SOAP -> PI -> RFC Scenario. If it is possible, could you please provide steps how it can be done?
Thank you.
Regards,
Cdr.

Thank you Hareesh & Divya,
When we generate WSDL from PI, it gives soap action and soap address location based on the interface we use for SOAP -> PI -> RFC.
When we import WSDL given by the client as external definition, we get messages(Structures). But where do we pass the soap action or address location. I do not see any option in the soap sender communication channel. I am not visualize the link.
Can somebody share their knowledge if they have done in this way.
Thank you.
Regards,
Cdr.

Soap to rfc scenario error

Hi PI Experts,
For the first time i was doing soap to rfc scenario. I have created all the objects in the ID and in the IR and also created a web service from ID an then i have saved the wsdl in my system. I have uploaded the wsdl in altova xml spy and tested it but i got an error like 'no channel specified'. and also got an error 'unable to post the file'.
so kindly please help me to solve this scenario.
Thanks & Regards,
B.Srinivas Prasad.

I have uploaded the wsdl in altova xml spy and tested it but i got an error like 'no channel specified'. and also got an error 'unable to post the file'.
Make sure that its in the below format :
From SAP help :
http://host:port/XISOAPAdapter/MessageServlet?channel=party:service:channel
Under party:service:channel enter the party name, the service name, and the name of the communication channel. If no party has been created, enter the following: channel=:service:channel
and check Sender Soap Channel Status is it activated/not and check Cache Status

SOAP to RFC scenario prolem

Hello Guru's
   Im trying the basic SOAP TO RFC scenario, in which RFC is SXIDEMO_AIRL_FLIGHT_CHECKAVAIL
and the out bound interface consists of only basic feilds i.e.
REQUEST MESSAGE TYPE : AirlineID
                                             ConnID
                                             Fldate
RESPONSE MESSAGE TYPE : Ecnofree
                                                Bussfree
                                                Firstfree
and no fault message type.
i created the scenario with out any errors, and i defined webservies in ID with the following URL
http://starxi:50000/XISOAPAdapter/MessageServlet?Channel=:SXI_BS_SOAPRFC_SENDER:SOAP_RFCSENDER
it is according to the following syntax
htt://<xi server>:<J2EE Port>/XISOAPAdapter/MessageServlet?channel=:<sender business system>:communication channel.
But im not able to post SOAP request to the xi server. it is saying following error
"SOAP Request cannot be posted <with url > 403"
403 is the error code.
please can anyone help me in overcoming the above problem. and where iam wrong.
Thanks in advance
arjun

Hi!
Please check once again reg SOAP URL while generating the WSDL.
[http://<HOST name:5<Port>00/XISOAPAdapter/MessageServlet?channel=:<Channel Name>:<Adapter Name>]
[Re: Using SOAP Sender adapter in PI 7.1]
1. Check whether your SOAP URL s correct or not which you are giving in the receiver SOAP adapter
2. Also check you are giving the SOAP action in the receiver SOAP adatper correctly or not.
3. Finally check the SOAP service is activei or not in SAP>BC>XI-->SOAP in ABAP stack
4. Since FIle is only for ASYN comm and while using FILE for sync interface you need to pass module paramters in the Sender File CC
ERROR 403 means::
This error will be comming mostly in the synch scenarios like SOAP to RFC - SOAP and FIle to RFC--FILE
when the target system is down or service is inactive.
Error: HTTP 403 Forbidden
Description: The server understood the request, but is refusing to fulfill it
Possible Tips:
Path sap/xi/engine not active
u2022 HTTP 403 during cache refresh of the adapter framework - Refer SAP Note -751856
u2022 Because of Inactive Services in ICF u2013Go to SICF transaction and activate the services. Refer SAP Note -517484
u2022 Error in RWB/Message Monitoring- because of J2EE roles u2013 Refer SAP Note -796726
u2022 Error in SOAP Adapter - "403 Forbidden" from the adapter's servlet. u2013Because of the URL is incorrect or the adapter is not correctly deployed.
Regards::
Amar Srinivas Eli

Help SOAP to RFC Scenario using BPM (Synchronous communication)

Hi,
I am doing a scenario from SOAP to RFC scenario(Synchronous communication). Here I am creating a PM Notification in the SAP system through a webservice.
I am using three BAPI'S here,
1. BAPI_ALM_NOTIF_CREATE
2. BAPI_ALM_NOTIF_SAVE
3. BAPI_TRANSACTION_COMMIT
I am successful in calling the first BAPI from the Web Service. For this I have not used BPM. But to commit the transaction(PM notification in this case), I have to execute the other two BAPI's as well. I have to pass the output of first BAPI to the second BAPI and then execute the 2nd BAPI. And finally have to execute the 3rd BAPI. FYI, 3rd BAPI is not dependent on any output. It has to be executed independently after execution of the first two BAPI's.
How can I execute this scenario? Do I have to use BPM? If yes please let me know the steps in detail. I have not done any BPM scenario till now. So please answer me in detail.
Thanks in Advance,
Vijay
p.s. reward points are must

Hi Vijay,
Yes, You will indeed need a BPM in this case...
Based on my understanding of the Scenario u have explained, here are the steps that would be needed.
1. Receive With the Sync-Async Bridge open.
2. Transformation Step (Between the source Request and The BAPI_ALM_NOTIF_CREATE Request)
3. Send Synchronous
4. Fork
5. In one Branch of the fork - Transformation (Between the BAPI_ALM_NOTIF_CREATE Response and API_ALM_NOTIF_SAVE Request)
6. In the other branch of the fork - Transformation (Between a Dummy Source and the BAPI_TRANSACTION_COMMIT Request)
7. Send Synchronous (to make the 2nd BAPI Call)
6. Transformation ( BAPI_ALM_NOTIF_SAVE Response and the source Response)
7. Send Asynchronous (to make the 3rd BAPI call)
8. Send the Source Response and close the Sync-Async Bridge.
There might be alternative ways also of doing it...
Also a better design would be to take care of the 2nd and the 3rd BAPI call within the code of the 1st RFC Function Module.
Regards,
Abhy Thomas

SOAP to RFC Scenario - Error at Sender Communication channel !!

Hi Experts ,
I am trying to execute a SOAP to RFC scenario . At SOAP sender channel level I am getting the error in RWB .
My findings :-
1. Error at RWB 9/24/09 4:24:10 PM   error occured
                         9/24/09 4:24:06 PM   request received
2. At SOAP UI client tool :
   <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
   <SOAP:Body>
      <SOAP:Fault>
         <faultcode>SOAP:Server</faultcode>
         <faultstring>Server Error</faultstring>
         <detail>
            <s:SystemError xmlns:s="http://sap.com/xi/WebService/xi2.0">
               <context>XIAdapter</context>
               <code>ADAPTER.JAVA_EXCEPTION</code>
               <text>com.sap.aii.af.ra.ms.api.DeliveryException: XIServer:UPDATE:HTTP status code401 Unauthorized
     at com.sap.aii.adapter.xi.ms.XIEventHandler.onTransmit(XIEventHandler.java:455)
     at com.sap.aii.af.ra.ms.impl.core.queue.consumer.CallConsumer.onMessage(CallConsumer.java:134)
     at com.sap.aii.af.ra.ms.impl.core.queue.Queue.run(Queue.java:917)
     at com.sap.aii.af.ra.ms.runtime.MSWorkWrapper.run(MSWorkWrapper.java:56)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(AccessController.java:207)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)</text>
            </s:SystemError>
         </detail>
      </SOAP:Fault>
   </SOAP:Body>
</SOAP:Envelope>
3. At SOAP UI level - "requires authentication with the realm 'XISOAPApps'"
1. I don't see any issue in authorization as i am having SAP_ALL .
2. URL string seems to be O.K :
    http://ABC:50000//XISOAPAdapter/MessageServlet?channel=:BSer_SOAP:CC_SOAP_Sender&version=3.0&Sender.Service=BSer_SOAP&Interface=urn:ABC.com:%5EMI_CustomerInfo
Kindly advice !!!
Regards ,

1. Check PI id and password is working fine.
Check if the user you are using has SAP_XI_APPL_SERV_USER role.
Another way is to pass id and pwd in URL
Try to pass the User ID and Password in the URL( the URL which is given to the webservice).
Example: http://host:port/XISOAPAdapter/MessageServlet?channel=party:service:channel &sap-user=xxxx&sap-password=xxxx
2.Provide SOAP URL like -
http://host:port/XISOAPAdapter/MessageServlet?channel=party:service:channel

ERROR During call of SOAP with a SOAP- RFC- SOAP Synchronous scenario

Hello Experts,
I've recently created a SOAP->RFC->SOAP synchronous scenario but every time I'm invoking the SOAP via XMLSpy then i will hang and send a timeout error. Also a log in XI was generated as shown below.
I hope you could help me on this one.
Runtime Errors         DBIF_RSQL_SQL_ERROR
Exception              CX_SY_OPEN_SQL_DB
Date and Time          28.09.2010 09:31:23
Short text
     SQL error in the database when accessing a table.
What happened?
     The database system detected a deadlock and avoided it by rolling back
     your transaction.
What can you do?
     If possible (and necessary), repeat the last database transaction in the
      hope that locking the object will not result in another deadlock.
     Note which actions and input led to the error.
     For further help in handling the problem, contact your SAP administrator
     You can use the ABAP dump analysis transaction ST22 to view and manage
     termination messages, in particular for long term reference.
     Note which actions and input led to the error.
     For further help in handling the problem, contact your SAP administrator
     You can use the ABAP dump analysis transaction ST22 to view and manage
     termination messages, in particular for long term reference.
Error analysis
     An exception occurred that is explained in detail below.
     The exception, which is assigned to class 'CX_SY_OPEN_SQL_DB', was not caught
      in
     procedure "DELETE_LUW_PACKET" "(FORM)", nor was it propagated by a RAISING
      clause.
     Since the caller of the procedure could not have anticipated that the
     exception would occur, the current program is terminated.
     The reason for the exception is:
     The database system recognized that your last operation on the database
     would have led to a deadlock.
     Therefore, your transaction was rolled back
     to avoid this.
     ORACLE always terminates any transaction that would result in deadlock.
     The other transactions involved in this potential deadlock
     are not affected by the termination.
Regards,
Alfred

Normally such an error comes when the DB of SAP PI is full.
Contact your BASIS or ADMIN team and ask them to free the DB space.
Regards,
Abhishek.

SOAP to JDBC/RFC - RFC/JDBC to SOAP XI Scenario

Hello,
Can anybody give me the links for SOAP to JDBC/RFC-BAPI or RFC-BAPI/JDBC ---> XI ---> SOAP XI Scenario?
I tried searching, but there isn't any step-by-step approach for it.
Thank you in advance.
Cheers,
Deepak.

Hi,
Check some links on SOAP,
RFC -> XI -> WebService - A Complete Walkthrough
/people/shabarish.vijayakumar/blog/2006/03/23/rfc--xi--webservice--a-complete-walkthrough-part-1
/people/shabarish.vijayakumar/blog/2006/03/28/rfc--xi--webservice--a-complete-walkthrough-part-2
SOAP with attachments
/people/michal.krawczyk2/blog/2006/04/19/xi-rfc-or-abap-proxy-abap-proxies-with-attachments
/people/padmankumar.sahoo/blog/2005/02/15/an-overview-of-soap
/people/siva.maranani/blog/2005/05/23/communication-between-sap-system-webservice-using-proxies
SOAP
An Overview of SOAP
/people/padmankumar.sahoo/blog/2005/02/15/an-overview-of-soap
JDBC ADAPTER
http://help.sap.com/saphelp_nw04/helpdata/en/7e/5df96381ec72468a00815dd80f8b63/content.htm
/people/saravanakumar.kuppusamy2/blog/2005/01/19/rdbms-system-integration-using-xi-30-jdbc-senderreceiver-adapter
Regards,
phani
Reward points if Helpful

Public URL for Synchronous SOAP to RFC scenario

Hello Everyone,
I have synchronous SOAP to RFC scenario.
i have created the http URL for testing environment through sender agreement.
However, now the user wants a public URL and that too secured one ... means ( https ) in production.
i tried this blog, but Service registry is not configured in our landscape.
http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/23725
is there any other way ..?
Regards,
Ravi

The process of creating the wsdl will remain same. The url in your case will start with HTTPS instead of HTTP. Note that the port at which HTTPS data would be received will be different than HTTP port and thererfore you need to change that as well. You don't have to set any client authentication unless there is a business requirement. You may simply use certificates for SSL.
In some cases, if PI always receives data through web-dipatcher (ask your network team), then the data hostname and port of web-dispatcher should be used.
Regards,
Prateek Raj Srivastava

NO_RECEIVER_CASE_BE error in a SOAP - XI - RFC scenario

Hi gurus:
I'm configuring a SOAP -> XI -> RFC scenario and I'm getting a "NO_RECEIVER_CASE_BE" error when I send a test message using the SOAP adapter.
I have another interfaces using the SOAP adapter of the same XI server and no problems with it. So I think my problem is not into the SOAP adapter.
Thanks to all in advance,
Alejandro Gomez.
Edited by: Alejandro Gómez on May 27, 2008 10:24 AM

Hi:
The entire XML result from MONI is next:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?> <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SAP="http://sap.com/xi/XI/Message/30"><SOAP:Header><SAP:Main xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" versionMajor="003" versionMinor="000" SOAP:mustUnderstand="1" wsu:Id="wsuid-main-92ABE13F5C59AB7FE10000000A1551F7"><SAP:MessageClass>ApplicationMessage</SAP:MessageClass><SAP:ProcessingMode>synchronous</SAP:ProcessingMode><SAP:MessageId>BD9B57A1-2BCC-11DD-C738-001B7899027A</SAP:MessageId><SAP:TimeSent>2008-05-27T09:10:24Z</SAP:TimeSent><SAP:Sender><SAP:Service>Openlab_Desarrollo</SAP:Service><SAP:Interface namespace="http://www.huc.es/xmlns/openlab">ServicioObtencionDatosPaciente</SAP:Interface></SAP:Sender><SAP:Interface namespace="http://www.huc.es/xmlns/openlab">ServicioObtencionDatosPaciente</SAP:Interface></SAP:Main><SAP:ReliableMessaging xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1"><SAP:QualityOfService>BestEffort</SAP:QualityOfService></SAP:ReliableMessaging><SAP:HopList xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1"><SAP:Hop timeStamp="2008-05-27T09:10:24Z" wasRead="false"><SAP:Engine type="AE">af.xi2.xidserver</SAP:Engine><SAP:Adapter namespace="http://sap.com/xi/XI/System">XIRA</SAP:Adapter><SAP:MessageId>BD9B57A1-2BCC-11DD-C738-001B7899027A</SAP:MessageId><SAP:Info/></SAP:Hop><SAP:Hop timeStamp="2008-05-27T09:10:24Z" wasRead="false"><SAP:Engine type="IS">is.00.xidserver</SAP:Engine><SAP:Adapter namespace="http://sap.com/xi/XI/System">XI</SAP:Adapter><SAP:MessageId>BD9B57A1-2BCC-11DD-C738-001B7899027A</SAP:MessageId><SAP:Info>3.0</SAP:Info></SAP:Hop></SAP:HopList><SAP:RunTime xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/"><SAP:Date>20080527</SAP:Date><SAP:Time>101024</SAP:Time><SAP:Host>xidserver</SAP:Host><SAP:SystemId>XI2</SAP:SystemId><SAP:SystemNr>00</SAP:SystemNr><SAP:OS>Windows NT</SAP:OS><SAP:DB>ORACLE</SAP:DB><SAP:Language/><SAP:ProcStatus>023</SAP:ProcStatus><SAP:AdapterStatus>000</SAP:AdapterStatus><SAP:User>XIAFUSER</SAP:User><SAP:TraceLevel>3</SAP:TraceLevel><SAP:Logging>1</SAP:Logging><SAP:LogSeqNbr>001</SAP:LogSeqNbr><SAP:RetryLogSeqNbr>000</SAP:RetryLogSeqNbr><SAP:PipelineIdInternal>SAP_CENTRAL</SAP:PipelineIdInternal><SAP:PipelineIdExternal>CENTRAL</SAP:PipelineIdExternal><SAP:PipelineElementId>5BC3C53B4BB7B62DE10000000A1148F5</SAP:PipelineElementId><SAP:PipelineService>PLSRV_RECEIVER_DETERMINATION</SAP:PipelineService><SAP:QIdInternal/><SAP:CommitActor>X</SAP:CommitActor><SAP:SplitNumber>0</SAP:SplitNumber><SAP:NumberOfRetries>0</SAP:NumberOfRetries><SAP:NumberOfManualRetries>0</SAP:NumberOfManualRetries><SAP:TypeOfEngine client="100">CENTRAL</SAP:TypeOfEngine><SAP:PlsrvExceptionCode/><SAP:EOReferenceRuntime type="TID"/><SAP:EOReferenceInbound type="TID"/><SAP:EOReferenceOutbound type="TID"/><SAP:MessageSizePayload>508</SAP:MessageSizePayload><SAP:MessageSizeTotal>2985</SAP:MessageSizeTotal><SAP:PayloadSizeRequest>508</SAP:PayloadSizeRequest><SAP:PayloadSizeRequestMap>0</SAP:PayloadSizeRequestMap><SAP:PayloadSizeResponse>0</SAP:PayloadSizeResponse><SAP:PayloadSizeResponseMap>0</SAP:PayloadSizeResponseMap><SAP:Reorganization>INI</SAP:Reorganization><SAP:AdapterInbound>AENGINE</SAP:AdapterInbound><SAP:InterfaceAction>INIT</SAP:InterfaceAction><SAP:RandomNumber>00</SAP:RandomNumber><SAP:AckStatus>000</SAP:AckStatus><SAP:SkipReceiverDetermination/></SAP:RunTime><SAP:PerformanceHeader xmlns:SAP="http://sap.com/xi/XI/Message/30"><SAP:RunTimeItem><SAP:Name type="ADAPTER_IN">INTEGRATION_ENGINE_HTTP_ENTRY</SAP:Name><SAP:Timestamp type="begin" host="xidserver">20080527091024.6</SAP:Timestamp></SAP:RunTimeItem><SAP:RunTimeItem><SAP:Name type="ADAPTER_IN">INTEGRATION_ENGINE_HTTP_ENTRY</SAP:Name><SAP:Timestamp type="end" host="xidserver">20080527091024.6</SAP:Timestamp></SAP:RunTimeItem><SAP:RunTimeItem><SAP:Name type="CORE">INTEGRATION_ENGINE</SAP:Name><SAP:Timestamp type="begin" host="xidserver">20080527091024.6</SAP:Timestamp></SAP:RunTimeItem><SAP:RunTimeItem><SAP:Name type="CORE">INTEGRATION_ENGINE</SAP:Name><SAP:Timestamp type="end" host="xidserver">20080527091024.6</SAP:Timestamp></SAP:RunTimeItem><SAP:RunTimeItem><SAP:Name type="PLSRV">PLSRV_RECEIVER_DETERMINATION</SAP:Name><SAP:Timestamp type="begin" host="xidserver">20080527091024.616</SAP:Timestamp></SAP:RunTimeItem></SAP:PerformanceHeader><SAP:Diagnostic xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1"><SAP:TraceLevel>Fatal</SAP:TraceLevel><SAP:Logging>Off</SAP:Logging></SAP:Diagnostic><SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30"><Trace level="1" type="T">Party normalization: sender </Trace>
<Trace level="1" type="T">Sender scheme external = XIParty</Trace>
<Trace level="1" type="T">Sender agency external = http://sap.com/xi/XI</Trace>
<Trace level="1" type="T">Sender party external = </Trace>
<Trace level="1" type="T">Sender party normalized = </Trace>
<Trace level="1" type="B" name="CL_XMS_HTTP_HANDLER-HANDLE_REQUEST"></Trace>
<Trace level="1" type="T">XMB was called with URL /sap/xi/engine?type=entry</Trace>
<Trace level="2" type="T">Request Line = POST /sap/xi/engine?type=entry HTTP/1.1</Trace>
<Trace level="2" type="T">Host = xidserver:8000</Trace>
<Trace level="2" type="T">Server protocol = HTTP/1.1</Trace>
<Trace level="2" type="T">Remote address = 10.137.73.104</Trace>
<Trace level="1" type="T">COMMIT is done by XMB ! </Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-ENTER_XMS"></Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-SET_START_PIPELINE"></Trace>
<Trace level="3" type="T">XMB was called with external pipeline PID = ENTRY</Trace>
<Trace level="3" type="T">Getting type of XMB... </Trace>
<Trace level="1" type="B" name="SXMBCONF-SXMB_GET_XMB_USE">
</Trace>
<Trace level="2" type="T">XMB kind = CENTRAL</Trace>
<Trace level="3" type="T">Start pipeline found </Trace>
<Trace level="2" type="T">Switch to external start pipeline PID = CENTRAL</Trace>
<Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV">
<Trace level="3" type="T">No triggers found. OK. </Trace>
</Trace>
<Trace level="1" type="T">**************************************************** </Trace>
<Trace level="1" type="T">*                                                  * </Trace>
<Trace level="1" type="T">*                                                  * </Trace>
<Trace level="1" type="T">XMB entry processing </Trace>
<Trace level="3" type="T">system-ID = XI2</Trace>
<Trace level="3" type="T">client = 100</Trace>
<Trace level="3" type="T">language = S</Trace>
<Trace level="3" type="T">user = XIAFUSER</Trace>
<Trace level="1" type="Timestamp">2008-05-27T09:10:24Z CET </Trace>
<Trace level="1" type="T">*                                                  * </Trace>
<Trace level="1" type="T">*                                                  * </Trace>
<Trace level="1" type="T">**************************************************** </Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_UC_EXECUTE"></Trace>
<Trace level="1" type="T">Message-GUID = BD9B57A12BCC11DDC738001B7899027A</Trace>
<Trace level="1" type="T">PLNAME = CENTRAL</Trace>
<Trace level="1" type="T">QOS = BE</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC"></Trace>
<Trace level="1" type="T">Get definition of external pipeline CENTRAL</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID">
<Trace level="3" type="T">External PLID = CENTRAL</Trace>
<Trace level="3" type="T">Internal PLID = SAP_CENTRAL</Trace>
</Trace>
<Trace level="1" type="T">Corresponding internal pipeline SAP_CENTRAL</Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="3" type="T">Pipeline attributes </Trace>
<Trace level="3" type="T">PID        = SAP_CENTRAL</Trace>
<Trace level="3" type="T">ENABLE     = 1</Trace>
<Trace level="3" type="T">TRACELEVEL = 0</Trace>
<Trace level="3" type="T">EXEMODE    = A</Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="3" type="T">Pipeline elements </Trace>
<Trace level="3" type="T">ELEMPOS    = 0001</Trace>
<Trace level="3" type="T">PLSRVID    = PLSRV_RECEIVER_DETERMINATION</Trace>
<Trace level="3" type="T">PLSRVTYPE = </Trace>
<Trace level="3" type="T">FL_DUMMY   = 0</Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="3" type="T">ELEMPOS    = 0002</Trace>
<Trace level="3" type="T">PLSRVID    = PLSRV_INTERFACE_DETERMINATION</Trace>
<Trace level="3" type="T">PLSRVTYPE = </Trace>
<Trace level="3" type="T">FL_DUMMY   = </Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="3" type="T">ELEMPOS    = 0003</Trace>
<Trace level="3" type="T">PLSRVID    = PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
<Trace level="3" type="T">PLSRVTYPE = </Trace>
<Trace level="3" type="T">FL_DUMMY   = </Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="3" type="T">ELEMPOS    = 0004</Trace>
<Trace level="3" type="T">PLSRVID    = PLSRV_MAPPING_REQUEST</Trace>
<Trace level="3" type="T">PLSRVTYPE = </Trace>
<Trace level="3" type="T">FL_DUMMY   = </Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="3" type="T">ELEMPOS    = 0007</Trace>
<Trace level="3" type="T">PLSRVID    = PLSRV_OUTBOUND_BINDING</Trace>
<Trace level="3" type="T">PLSRVTYPE = </Trace>
<Trace level="3" type="T">FL_DUMMY   = </Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="3" type="T">ELEMPOS    = 0008</Trace>
<Trace level="3" type="T">PLSRVID    = PLSRV_CALL_ADAPTER</Trace>
<Trace level="3" type="T">PLSRVTYPE = =SWITCH=</Trace>
<Trace level="3" type="T">FL_DUMMY   = </Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="3" type="T">ELEMPOS    = 0009</Trace>
<Trace level="3" type="T">PLSRVID    = PLSRV_MAPPING_RESPONSE</Trace>
<Trace level="3" type="T">PLSRVTYPE = </Trace>
<Trace level="3" type="T">FL_DUMMY   = </Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
<Trace level="2" type="T">Persisting original message </Trace>
<Trace level="3" type="T">Message-Version = 000</Trace>
<Trace level="3" type="T">Message version 000</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
</Trace>
<Trace level="1" type="Timestamp">2008-05-27T09:10:24Z CET Begin of pipeline processing PLSRVID = CENTRAL</Trace>
<Trace level="1" type="B" name="PLSRV_RECEIVER_DETERMINATION"></Trace>
<Trace level="1" type="Timestamp">2008-05-27T09:10:24Z CET Start of pipeline service processing PLSRVID= PLSRV_RECEIVER_DETERMINATION</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="3" type="T">Calling pipeline service: PLSRV_RECEIVER_DETERMINATION</Trace>
<Trace level="3" type="T">Reading Pipeline-Service specification... </Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV) </Trace>
<Trace level="3" type="T">PLSRVID    = PLSRV_RECEIVER_DETERMINATION</Trace>
<Trace level="3" type="T">PLSRVTYPE = </Trace>
<Trace level="3" type="T">ADRESSMOD = LOCAL</Trace>
<Trace level="3" type="T">P_CLASS    = CL_RD_PLSRV</Trace>
<Trace level="3" type="T">P_IFNAME   = IF_XMS_PLSRV</Trace>
<Trace level="3" type="T">P_METHOD   = ENTER_PLSRV</Trace>
<Trace level="3" type="T">FL_LOG     = </Trace>
<Trace level="3" type="T">FL_DUMMY   = 0</Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL"></Trace>
<Trace level="1" type="B" name="CL_RD_PLSRV-ENTER_PLSRV">
<Trace level="1" type="T">R E C E I V E R - D E T E R M I N A T I O N </Trace>
<Trace level="1" type="T"> Cache Content is up to date </Trace>
<Trace level="2" type="T">Start without given receiver </Trace>
<Trace level="1" type="T">No Relation found - accept given Receivers. </Trace>
<Trace level="2" type="T">Classic Receiver Determination via Rules. </Trace>
<Trace level="2" type="T">No Receiver found behaviour: 0 </Trace>
</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST"></Trace>
<Trace level="3" type="T">Persisting message Status = 023</Trace>
<Trace level="3" type="T">Message version 001</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
</SAP:Trace></SOAP:Header><SOAP:Body><SAP:Manifest xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="wsuid-manifest-5CABE13F5C59AB7FE10000000A1551F7"><SAP:Payload xlink:href="cid:payload-bd9b57a22bcc11dd95bc001b7899027a#sap.com"><SAP:Name>MainDocument</SAP:Name><SAP:Description>Main XML document</SAP:Description><SAP:Type>Application</SAP:Type></SAP:Payload></SAP:Manifest></SOAP:Body></SOAP:Envelope>
Thanks,
Alejandro Gomez.

SOAP - RFC scenario EOIO

Similar Messages

Maybe you are looking for