Synchronous SOAP to RFC

Hi All,
I have a doubt that in a Synchronous SOAP to RFC/PROXY interface that is it we need to configure the entire Interface and then have to test the Webservice for the response from Altova??
I have configured SOAP at the sender and RFC at the receiver but my Customize BAPI is not yet ready but I want to test the Webservice from Altova,Is it so that i need to configure the whole scenario and test it.
Isnt it enough if I do basic Configuartion??
Thanks & Regards,
R.K

hi,
if u want to test u r WEBSERVICE using altova spy... u need not configure whole scenario.. configure simple soap to file scenario and check u r webservice..
if u want to check syncronous scenario... for the testing use a BAPI which is already existing..
Thanks,
Madhav
Note:Points if useful

Similar Messages

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

Synchronous RFC to SOAP scenario (RFC or XI adapter?)

Hi there,
i have following functional requirement from my customer, SAP is going to send some data (3 fields) to XI and XI has to send them to an appl that will return a status. This status has to be sent back to SAP.
As the appl deals with xml messages, the nonSAP side is going to be integrated via receiver synchronous SOAP CC.
But question is, which of the following is the best integration approach (adapter to use) in the SAP side??
At first i thought sRFC and XI adapters would fit these requirements but i have several doubts:
1)how the RFC is to be implemented to be able to export the data and finally, import the status received from the external appl.???
2)how could we do this with the XI adapter??? Does it support synchronous messages? Is there any step by step guide on the sdn showing ?
Thanks in advance and best regards,
David

Dear,
I have created an interface like the below url.
http://www.****************/Tutorials/XI/RFCtoSOAP/page2.htm
but i am not getting Response, why it is happening.
IR, ID test configuration success. but when i am triggering data. not showing in moni.
please suggest me
Regards,
Kiran Polani

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

Http to RFC or SOAP to RFC (synchronous)

Hi,
I need to connect PHP with RFC via XI/PI
Request will be send from php developed web pages to R/3 (RFC) to get data back to web page.
I think to resolve this scenario 1u2019ve two options
1: SOAP to RFC (synchronous)
2: HTTP to RFC (synchronous)
Can you please suggest me the scenario?
Thanks for you time
Regards,
Farrukh Ghani

Hi Ghani,
The two options you mentioned we can use,but it depends on how PHP web site going to send data,if it is going to send webserive then use SOAP adapter,you are expecting response ,the RFC wil work as synchronous.
If it is not Web Service other option is HTTP,receiver would be RFC only.
How to configure SOAP->XI>RFC or HTTP->XI-->RFC scenarios,simple search in sdn will give many blogs,search in sdn,
if you unable to find right one let me know..
Regards,
Raj

Soap to RFC synchronous scenario

Dear experts,
i am doing a SOAP to RFC(BAPI_INTERNALORDER_GETDETAIL) sync scenario and the rfc returns a structure with the records as well as the BAPIRET2 records .
Do i need to use fault message types here ?
If yes what would be its purpose in this scenario ?
Ravi

Hi,
if you have BAPIRET2 then all the errors will be over there
so I guess there is no need to use a fault message
Regards,
Michal Krawczyk

SOAP to RFC synchronous scenario with File

Hi,
My scenario is
Java application is sending SOAP message to PI and PI should route that message (after converting SOAP message to XI message) to RFC.
2) After receiving the response from RFC PI should send the response to java application. Now here comes the little tweak, we need to map RFC response to File as well apart from sending SOAP response message (which is generated after mapping RFC response message to Java application response structure) back to Java application.
Is it possible without BPM?

Without BPM you can try below approach, but i would recommend you to use BPM.
Develop SOAP---->PI(rfc look up) -
> SOAP/JAVA application
map RFC loop up response to SOAP receiver and JAVA application/.
Regards,
Raj

MAPPING JCO_COMMUNICATION_FAILURE (SOAP to RFC scenario)

Hi,
Our system is PI 7.1 EHP1 and the scenario is to SOAP to RFC (Synchronous). I have imported the RFC into ESR and used it as data type for Outbound interface for SOAP.
Initially i havent created any mapping because all Interface fields are same (name and type) with RFC because i have used RFC as data type. When we have tested the integration via SOAPUI we have seen that the request message wasn't transferred to RFC but the response was transferred from RFC to SOAP response. Could it be a bug? or is it normal behaviour?
Later, i have created a graphical mapping without any data conversion etc.. It is just mapping. This time it transferred the request and response as well.
When we have started stress test on a PI system (6000 SAPS), the PI JAVA stack started to use %100 of CPU. We have processed 100 message per minute. After 20 minutes, Java stack of PI has crashed and restarted.
Our plan is to process message more then this test numbers. Possibly it is approx 400 message per minute.
I have found below errors on RWB (approx 250 message have below errors).
How this high CPU consumption can be resolved?
- <SAP:Error SOAP:mustUnderstand="1" xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="MAPPING">JCO_COMMUNICATION_FAILURE</SAP:Code>
<SAP:P1>Error when opening an RFC connection (CPIC-CALL: 'ThSAPOCMINIT' : cmRc=2 thRc=67</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>"COMMUNICATION FAILURE" during JCo call. Error when opening an RFC connection (CPIC-CALL: 'ThSAPOCMINIT' : cmRc=2 thRc=67</SAP:Stack>
</SAP:Error>
- <SAP:Error SOAP:mustUnderstand="1" xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="MAPPING">JCO_SYSTEM_FAILURE</SAP:Code>
<SAP:P1>connection to partner 'loopback:0' broken / CPIC-CALL: 'ThSAPCMRCV' : cmRc=20 th</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>"SYSTEM FAILURE" during JCo call. connection to partner 'loopback:0' broken / CPIC-CALL: 'ThSAPCMRCV' : cmRc=20 th</SAP:Stack>
</SAP:Error>
Kind regards,
Altuğ Bayram

Hi,
Connection between ABAP and JAVA has been broken...thats the reason for the JCO_COMMUNICATION Error
you need to either restart the java or have a look at the RFC Connection JCO_AI_CONNECTION...
re you making use of AAE for this scenario..which can improve the performance than using classic scenario.
performance depends on the hardware of the server also...
Check the sizing Guide of the PI 7.1 on SDN.
Check the below link it may help you..
http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/f0b96675-87cf-2c10-b489-dee0ac03f782
HTH
Rajesh

SOAP to RFC

Hi,
I am working on SOAP to RFC synchronous interface, apart from developement of IR,ID and BAPI, what are the other configurations need to be done on both PI and SAP.Do we need to create an RFC destination ect? please help
Thanks

Since it's SOAP to RFC , you don't need to create any RFC destinations and all the stuff. Just give your SAP system details in the Receiver RFC Communication channel, that should be fine.
Thanks!

Soap to rfc..dont get a response...

I have pasted below the complete steps for doing a rfc to soap synchronous scenario...i can send a message and update a custom table in r/3 with the data..however i am not getting any response, i have tested the rfc on r/3 and checked the table ..which is getting updated correctly....any ideas on whats wrong .....More important areas are the items in bold.....which is where i think smthing is not ok.
Design..part........
Create data types
1) testScore_dt
2) testScoreResponse_dt.
Create 2 msg types for 1 and 2...
testScore_MT
testScoreResponse_MT
Create Message Interface
MI_TestScore
Outbound Message Interface Synchronous
input Message is testScore_MT
outputMessage is testScoreResponse_MT
Import rfc
ZRfc_testScore
ZRfc_testScoreResponse
Create 2 message mappings
MM_Input_001
Source is testScore_MT
Destination is ZRfc_testScore
MM_Output_001
Source is ZRfc_testScoreResponse
Destinatio is testScoreResponse_MT
Create 1 Interface mapping
Source is MI_testSource
Target is ZRfc_testScore
Request tab...choose mapping as MM_Input_001
Response tab ...choose mapping as MM_Output_001
Configuration...
Create Sender_BService
Create Reciever_BService
Create Communication channels
CC_Sender_Soap
default namespace
interface = MI_TestScore
CC_Reciever_RFC
Do Reciever determination
Sender = Sender_BService
Interface == ?
Do Interface determination
Need Help ?
Sender Agreement
Sender CC
Reciever Agreement
Reciever CC
Regards
Ravi Raman

Ravi,
I believe your scenario is SOAP to RFC, coz the title and your explanation misleading to different scenarios.
>>>>>>>Do Reciever determination
Sender = Sender_BService
Interface == ?
Do Interface determination
Need Help ?
Receiver Determinatio
Sender = Sender_BService
Interface =MI_TestScore
Configured receivers = Receiver_BService
Interface Determinatio
Sender = Sender_BService
Outbound Interface =MI_TestScore
Inbound Interface = RFC
Mapping = Interface mapping.
raj.

SOAP - XI - RFC. XI not perform Adapter call after Technical Routing.

Hi, All!
I have a problem with XI.
My configuration (all calls are synchronous):
SOAP adapter -> XI mapping -> RFC adapter call to R/3
Most of the time it's works correctlly!
But some times XI does not call outbound RFC adapter after "Technical Routing". And there is no error in XI Monitor, but this XML message marked like "scheduled". So the SOAP adapter returns "Timeout error".
I have compared messages in XI monitor for a successful call and a unsuccessful one. There is no difference in "Routings" and "Mapings" they are the same, except for in the unsuccessful message no "Adapter call" at all!
Do you know how to solve such a problem?
Thank you!!

try to register all queues in SXMB_ADM -> Manage queues.
I think that should help you solve the issue.

Synchronous SOAP sender

HI Guys,
I had created a synchronous SOAP sender adapter (Webservice -> RFC), the interface is working and it is updating the records in SAP using RFC but iam not getting the response back from SAP. And the other thing which i noticed is when i change the QOS as Best Effort, Iam not getting any message into SXMB_MONI,but the record is updating in SAP. If is use the QOS as Exactly once the message is showing up in SXMB_MONI. Can anyone let me know regarding the config / design steps for the synchronous response ?
regards,
kittu.

Hi,
please see the below links
Troubleshooting SOAP Message - XI - /people/varadharajan.krishnasamy/blog/2007/01/09/troubleshooting-soap-message--xi
Troubleshooting - RFC and SOAP scenarios-/people/shabarish.vijayakumar/blog/2008/01/08/troubleshooting--rfc-and-soap-scenarios-updated-on-20042009
http://help.sap.com/saphelp_nw04/helpdata/en/c8/e80440a832e369e10000000a155106/frameset.htm
Consuming XI Web Services using Web Dynpro Part II-/people/riyaz.sayyad/blog/2006/05/08/consuming-xi-web-services-using-web-dynpro-150-part-ii
Consuming XI Web Services using Web Dynpro Part I -/people/riyaz.sayyad/blog/2006/05/07/consuming-xi-web-services-using-web-dynpro-150-part-i
SOAP webservice directly to IE - /people/stefan.grube/blog/2006/09/21/using-the-soap-inbound-channel-of-the-integration-engine
Regards
Chilla.

Synchronous SOAP invoked in XML Spy for testing but no reponse recieved

Hello Experts,
I'm have tried to create a synchronous SOAP -> RFC scenario. I already setup my Message Interface as Outbound and Synchronous but when I'm testing it already in XML spy I only successfully sent the soap request and but got no response back. Also in SXMB_MONI I see my message being sent to SAP but it did not return any response. What have I possibly missed out during the setup. Hoping someone could help
Regards,
Alfred

Hi,
Below is my PI objects. Maybe this could help you analyze my problem.
IR Objects
Data Type:
ReqCustomerNo_DT
RespCustDetails_DT
Message Type:
ReqCustomerNo_MT -> using ReqCustomerNo_DT (Data Type)
RespCustDetails_MT -> using ReqCustomerNo_DT (RespCustDetails_DT)
Message Interface:
CDWS_MI -> synchronous/Outbound
Output Message : ReqCustomerNo_MT -> using ReqCustomerNo_DT (Data Type)
Input Message : RespCustDetails_MT -> using ReqCustomerNo_DT (RespCustDetails_DT)
Message Mapping:
Request_MM -> mapped ReqCustomerNo_MT with BAPI_CUSTOMER_GETDETAIL2(RFC)
Response_MM - mapped BAPI_CUSTOMER_GETDETAIL2.response (RFC) with RespCustDetails_MT
Interface Mapping:
CDWS_IM:
Source Interface -> CDWS_MI
Target Interface -> BAPI_CUSTOMER_GETDETAIL2
Messages:
Request: Mapping Program -> Request_MM
Source Message: ReqCustomerNo_MT
Target Message: BAPI_CUSTOMER_GETDETAIL2
Response: Mapping Program -> Response_MM
Source Message: BAPI_CUSTOMER_GETDETAIL2.Response
Target Message: RespCustDetails_MT
ID Objects
Sender Agreement:
Service: ZBSBACKEND
Interface: CDWS_MI
Interface Namespace: http://atp.amkor.co.ph/ppmodule/synch
Receiver Determination:
Service: ZBSBACKEND
Interface: CDWS_MI
Interface Namespace: http://atp.amkor.co.ph/ppmodule/synch
Configured Receivers: ZBSBACKEND
Interface Determination:
Inbound Interface : BAPI_CUSTOMER_GETDETAIL2
Interface Mapping : CDWS_IM
Receiver Agreement:
Sender
Service: ZBSBACKEND
Receiver
Service: ZBSBACKEND
Interface: BAPI_CUSTOMER_GETDETAIL2
Interface namespace: urn:sap-com:document:sap:rfc:functions
Regards,
Alfred

Problem in the scenario SOAP to RFC Syn

Hello All,
i developed one scenario for our client and development is same like below link.
http://www.riyaz.net/blog/xipi-consuming-xi-web-services-using-web-dynpro-part-i/technology/sap/6/
when i test the interface iam getting below error, Please tell me do i need to install any patch in Xi server or do i need to implement any note.
My SAP XI server version 3.0 and Service pack:19
2010-07-19 07:24:57     Operation performed     The message has been received by the mail system. Profile: XI URL: http://xxxxxxxxx:50000/MessagingSystem/receive/AFW/XI credential (User): XIISUSER
2010-07-19 07:24:57     Operation performed     With the connection RFC_http: / / sap.com / xi / XI / System. Attempted placement of the message in the queue of requests.
2010-07-19 07:24:57     Operation performed     Message queued dCaution
2010-07-19 07:24:57     Operation performed     The message has been retrieved from the queue dCaution queries.
2010-07-19 07:24:57     Operation performed     The status of the message has been activated on DLNG
2010-07-19 07:24:58     Operation performed     Paper channel: CC_R_RFC
2010-07-19 07:24:58     Operation performed     MP: entering
2010-07-19 07:24:58     Operation performed     MP: processing local module localejbs/RfcAFBean
2010-07-19 07:24:58     Error     MP: exception caught with cause com.sap.engine.services.ejb.exceptions.BaseEJBException: Exception in method process.
2010-07-19 07:24:58     Error     Exceptions occurred for Adapter Framework: Exception in method process.
2010-07-19 07:24:58     Error     The dissemination of the message to the application via RFC_http: / / sap.com / xi / XI / System failed due to com.sap.aii.af.ra.ms.api.RecoverableException: Exception in method process.:
com.sap.engine.services.ejb.exceptions.BaseEJBException: Exception in method Process .. Enabled message "Failed".
2010-07-19 07:24:58     Error     The status of the message has been activated on FAIL
2010-07-19 07:24:58     Error     Return of the synchronous error message to the calling application: com.sap.aii.af.ra.ms.api.RecoverableException: Exception in method process.: Com.sap.engine.services.ejb.exceptions.BaseEJBException: Exception method in process ..
Thanks and Regards,
Chinna
Edited by: chinnasapxi on Jul 19, 2010 10:55 AM
Edited by: chinnasapxi on Jul 19, 2010 10:56 AM

Hi Cinna,
>just now i checked the RFC it is working
this together with the header "Problem in the scenario SOAP to RFC Syn" is missunderstoobable. But ok, the error is inside RFC adapter: may be it cannot create the DIAG RFC call with the XML what you provided in RTW.
To be shure to have sent the right XML send a message but use a Message Mapping with RFC module as target.
Regards,
Udo

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.

Synchronous SOAP to RFC

Similar Messages

Maybe you are looking for