My scenario soap to soap scenario

i am new in pi, Can u explain how to create the multiple operations at receiver side.

HI,
For this, we have to fill the TargetURL and the SOAPAction in Receiver Communication channel dynamically.
So, we need to write UDF in Message Mappings using DynamicConfiguration to fill the TargetURL and the SOAPAction Dynamically.
DynamicConfigurationKey keyURL = DynamicConfigurationKey.create("http://sap.com/xi/XI/System/SOAP","THeaderSOAPACTION");
DynamicConfigurationKey targetURL=DynamicConfigurationKey.create("http://sap.com/xi/XI/System/SOAP","TServerLocation");
// access dynamic configuration
DynamicConfiguration conf = (DynamicConfiguration) container
.getTransformationParameters()
.get(StreamTransformationConstants.DYNAMIC_CONFIGURATION);
conf.put(keyURL,"Soap action");
conf.put(targetURL,"target url");
return "";
In this UDF, we are filling the TargetURL in u201CTServerLocationu201D message attribute and SOAPAction in u201CTHeaderSOAPActionu201D message attribute.
So, whenever we execute this corresponding operation these values will be filled in receiver communication channel at runtime.
TargetURL- Give some dummy URL or http://
SOAPAction - *
regards,
ganesh.

Similar Messages

  • Mapping related errors in SOAP Adapter scenario

    Hello Friends
    I have done this several times and in this particular case I am getting some errors.
    Here is the scenario
    External  --- (SOAP) ---  XI  -
    (RFC) -
    SAP TABLE.
    Program
    I have created an XSD (External definition) to get the data to XI using SOAP Adapter.
    I have done the mapping and everything looks Ok to me. I even restarted my XI server. All other scenarios are working except for this particular scenario in question.
    When I looked at <SXMB_MONI> I see the xml string coming in correctly with proper tags and data as expected.
    However, it is failing with some mapping errors.
    Here is the error message I got in SXMB_MONI
    Any help will be greatly appreciated.
      <Trace level="1" type="T">Interface Mapping http://cincom.com/config AddConfigDNA</Trace>
      <Trace level="1" type="T">RuntimeException during appliction Java mapping com/sap/xi/tf/_AddConfigDNARequest_</Trace>
      <Trace level="1" type="T">com.sap.aii.utilxi.misc.api.BaseRuntimeException: RuntimeException in Message-Mapping transformation: Cannot produce target element /ns1:ZBAPI_ADD_CONFIG_DNA. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd at com.sap.aii.mappingtool.tf3.AMappingProgram.start(AMappingProgram.java:403) at com.sap.aii.mappingtool.tf3.Transformer.start(Transformer.java:141) at com.sap.aii.mappingtool.tf3.AMappingProgram.execute(AMappingProgram.java:102) at com.sap.aii.ibrun.server.mapping.JavaMapping.executeStep(JavaMapping.java:64) at com.sap.aii.ibrun.server.mapping.Mapping.execute(Mapping.java:91) at com.sap.aii.ibrun.server.mapping.MappingHandler.run(MappingHandler.java:90) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest(MappingRequestHandler.java:95) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleRequest(MappingRequestHandler.java:68) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceImpl.processFunction(MappingServiceImpl.java:79) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceObjectImpl0.processFunction(MappingServiceObjectImpl0.java:131) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java:187) at $Proxy177.processFunction(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.call(RFCDefaultRequestHandler.java:219) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:169) at com.sap.engine.services.rfcengine.RFCJCOServer.handleRequest(RFCJCOServer.java:156) at com.sap.mw.jco.JCO$Server.dispatchRequest(JCO.java:7701) at com.sap.mw.jco.MiddlewareJRfc$Server.dispatchRequest(MiddlewareJRfc.java:2376) at com.sap.mw.jco.MiddlewareJRfc$Server.listen(MiddlewareJRfc.java:1700) at com.sap.mw.jco.JCO$Server.listen(JCO.java:8061) at com.sap.mw.jco.JCO$Server.work(JCO.java:8181) at com.sap.mw.jco.JCO$Server.loop(JCO.java:8128) at com.sap.mw.jco.JCO$Server.run(JCO.java:8044) 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) Root Cause: com.sap.aii.mappingtool.tf3.IllegalInstanceException: Cannot produce target element /ns1:ZBAPI_ADD_CONFIG_DNA. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd at com.sap.aii.mappingtool.tf3.AMappingProgram.processNode(AMappingProgram.java:283) at com.sap.aii.mappingtool.tf3.AMappingProgram.start(AMappingProgram.java:398) at com.sap.aii.mappingtool.tf3.Transformer.start(Transformer.java:141) at com.sap.aii.mappingtool.tf3.AMappingProgram.execute(AMappingProgram.java:102) at com.sap.aii.ibrun.server.mapping.JavaMapping.executeStep(JavaMapping.java:64) at com.sap.aii.ibrun.server.mapping.Mapping.execute(Mapping.java:91) at com.sap.aii.ibrun.server.mapping.MappingHandler.run(MappingHandler.java:90) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest(MappingRequestHandler.java:95) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleRequest(MappingRequestHandler.java:68) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceImpl.processFunction(MappingServiceImpl.java:79) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceObjectImpl0.processFunction(MappingServiceObjectImpl0.java:131) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java:187) at $Proxy177.processFunction(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.call(RFCDefaultRequestHandler.java:219) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:169) at com.sap.engine.services.rfcengine.RFCJCOServer.handleRequest(RFCJCOServer.java:156) at com.sap.mw.jco.JCO$Server.dispatchRequest(JCO.java:7701) at com.sap.mw.jco.MiddlewareJRfc$Server.dispatchRequest(MiddlewareJRfc.java:2376) at com.sap.mw.jco.MiddlewareJRfc$Server.listen(MiddlewareJRfc.java:1700) at com.sap.mw.jco.JCO$Server.listen(JCO.java:8061) at com.sap.mw.jco.JCO$Server.work(JCO.java:8181) at com.sap.mw.jco.JCO$Server.loop(JCO.java:8128) at com.sap.mw.jco.JCO$Server.run(JCO.java:8044) 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)</Trace>
      <Trace level="1" type="T">Runtime exception occurred during execution of application mapping program com/sap/xi/tf/_AddConfigDNARequest_: com.sap.aii.utilxi.misc.api.BaseRuntimeException; RuntimeException in Message-Mapping transformation: Cannot produce target element /ns1:ZBAPI_ADD_CONFIG_DNA. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd</Trace>
      <Trace level="1" type="T">com.sap.aii.ibrun.server.mapping.MappingRuntimeException: Runtime exception occurred during execution of application mapping program com/sap/xi/tf/_AddConfigDNARequest_: com.sap.aii.utilxi.misc.api.BaseRuntimeException; RuntimeException in Message-Mapping transformation: Cannot produce target element /ns1:ZBAPI_ADD_CONFIG_DNA. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd at com.sap.aii.ibrun.server.mapping.JavaMapping.executeStep(JavaMapping.java:73) at com.sap.aii.ibrun.server.mapping.Mapping.execute(Mapping.java:91) at com.sap.aii.ibrun.server.mapping.MappingHandler.run(MappingHandler.java:90) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest(MappingRequestHandler.java:95) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleRequest(MappingRequestHandler.java:68) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceImpl.processFunction(MappingServiceImpl.java:79) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceObjectImpl0.processFunction(MappingServiceObjectImpl0.java:131) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java:187) at $Proxy177.processFunction(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.call(RFCDefaultRequestHandler.java:219) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:169) at com.sap.engine.services.rfcengine.RFCJCOServer.handleRequest(RFCJCOServer.java:156) at com.sap.mw.jco.JCO$Server.dispatchRequest(JCO.java:7701) at com.sap.mw.jco.MiddlewareJRfc$Server.dispatchRequest(MiddlewareJRfc.java:2376) at com.sap.mw.jco.MiddlewareJRfc$Server.listen(MiddlewareJRfc.java:1700) at com.sap.mw.jco.JCO$Server.listen(JCO.java:8061) at com.sap.mw.jco.JCO$Server.work(JCO.java:8181) at com.sap.mw.jco.JCO$Server.loop(JCO.java:8128) at com.sap.mw.jco.JCO$Server.run(JCO.java:8044) 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) Root Cause: com.sap.aii.utilxi.misc.api.BaseRuntimeException: RuntimeException in Message-Mapping transformation: Cannot produce target element /ns1:ZBAPI_ADD_CONFIG_DNA. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd at com.sap.aii.mappingtool.tf3.AMappingProgram.start(AMappingProgram.java:403) at com.sap.aii.mappingtool.tf3.Transformer.start(Transformer.java:141) at com.sap.aii.mappingtool.tf3.AMappingProgram.execute(AMappingProgram.java:102) at com.sap.aii.ibrun.server.mapping.JavaMapping.executeStep(JavaMapping.java:64) at com.sap.aii.ibrun.server.mapping.Mapping.execute(Mapping.java:91) at com.sap.aii.ibrun.server.mapping.MappingHandler.run(MappingHandler.java:90) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest(MappingRequestHandler.java:95) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleRequest(MappingRequestHandler.java:68) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceImpl.processFunction(MappingServiceImpl.java:79) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceObjectImpl0.processFunction(MappingServiceObjectImpl0.java:131) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java:187) at $Proxy177.processFunction(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.call(RFCDefaultRequestHandler.java:219) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:169) at com.sap.engine.services.rfcengine.RFCJCOServer.handleRequest(RFCJCOServer.java:156) at com.sap.mw.jco.JCO$Server.dispatchRequest(JCO.java:7701) at com.sap.mw.jco.MiddlewareJRfc$Server.dispatchRequest(MiddlewareJRfc.java:2376) at com.sap.mw.jco.MiddlewareJRfc$Server.listen(MiddlewareJRfc.java:1700) at com.sap.mw.jco.JCO$Server.listen(JCO.java:8061) at com.sap.mw.jco.JCO$Server.work(JCO.java:8181) at com.sap.mw.jco.JCO$Server.loop(JCO.java:8128) at com.sap.mw.jco.JCO$Server.run(JCO.java:8044) 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) Root Cause: com.sap.aii.mappingtool.tf3.IllegalInstanceException: Cannot produce target element /ns1:ZBAPI_ADD_CONFIG_DNA. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd at com.sap.aii.mappingtool.tf3.AMappingProgram.processNode(AMappingProgram.java:283) at com.sap.aii.mappingtool.tf3.AMappingProgram.start(AMappingProgram.java:398) at com.sap.aii.mappingtool.tf3.Transformer.start(Transformer.java:141) at com.sap.aii.mappingtool.tf3.AMappingProgram.execute(AMappingProgram.java:102) at com.sap.aii.ibrun.server.mapping.JavaMapping.executeStep(JavaMapping.java:64) at com.sap.aii.ibrun.server.mapping.Mapping.execute(Mapping.java:91) at com.sap.aii.ibrun.server.mapping.MappingHandler.run(MappingHandler.java:90) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest(MappingRequestHandler.java:95) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleRequest(MappingRequestHandler.java:68) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceImpl.processFunction(MappingServiceImpl.java:79) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceObjectImpl0.processFunction(MappingServiceObjectImpl0.java:131) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java:187) at $Proxy177.processFunction(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.call(RFCDefaultRequestHandler.java:219) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:169) at com.sap.engine.services.rfcengine.RFCJCOServer.handleRequest(RFCJCOServer.java:156) at com.sap.mw.jco.JCO$Server.dispatchRequest(JCO.java:7701) at com.sap.mw.jco.MiddlewareJRfc$Server.dispatchRequest(MiddlewareJRfc.java:2376) at com.sap.mw.jco.MiddlewareJRfc$Server.listen(MiddlewareJRfc.java:1700) at com.sap.mw.jco.JCO$Server.listen(JCO.java:8061) at com.sap.mw.jco.JCO$Server.work(JCO.java:8181) at com.sap.mw.jco.JCO$Server.loop(JCO.java:8128) at com.sap.mw.jco.JCO$Server.run(JCO.java:8044) 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)</Trace>
      <Trace level="1" type="E">CL_XMS_PLSRV_MAPPING~ENTER_PLSRV</Trace>
      </Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
    - <!--  ************************************
      -->
      </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:[email protected]">
      <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>

    Hi Ram,
    This error is due to error in message mapping.The map rules you have specified for the Node: "ZBAPI_ADD_CONFIG_DNA" is not getting satisfies due to which it is unable to create the Node who occurance is mandatory.Check if map rule specified for this particular Node.
    Thanks,
    Bhargav.
    Note:Award Points if found useful

  • ABAP.INTERFACE_REGISTRATION_ERROR while run SOAP - PI - RFC - R3 scenario.

    Hi all,
    My scenario is a third party send a request (through SOAP message) to PI, then PI will made RFC call to R3 system to retrieve data.  (call BAPI_CUSTOMER_DISPLAY).
    At IR i've created.
    Namespace: http://send
    1.  Data type: DT_request (which include customer number )
         Data type: DT_response
    2.  Message type for 2 data types above.
    3.  Message Mapping for request: MT_request  => BAPI_CUSTOMER_DISPLAY and for response: BAPI_CUSTOMER_DISPLAY.response => MT_response.
    4. Service Interface: SI_BAPI_CUSTOMER_DISPLAY_REQUEST: Outbound, stateless and synchronous.
        Operator Mapping: which mapping SI_BAPI_CUSTOMER_DISPLAY_REQUEST and SI_CUSTOMER_DISPLAY_RESPONSE (please see 6).
    At business system B (on R3 WS ABAP).
    Namespace: http://rec
    5. Importing BAPI_CUSTOMER_DISPLAY rfc.
    6. Inbound Service Interface: SI_BAPI_CUSTOMER_DISPAY_RESPONSE: Inbout, statelss and synchronous (corresponding to  4.)
    And then, at ID I've created:
    7. SOAP communication channel (cc) for business system A. This cc is sender.
    8. RFC communication channel for business system B. This cc is receiver.
    9. Sender agreement, receiver determination...
    10. Generate WSDL and got the ws url is: http://sapsrv:50100/sap/xi/engine?type=entry&version=3.0&Sender.Service=BVI&Interface=http%3A%2F%2Fsend%5ESI_BAPI_CUSTOMER_DISPLAY_REQUEST
    Then,  I tried to test with XML spy but get this error:
    <s:SystemError xmlns:s="http://sap.com/xi/WebService/xi2.0">
                             <context/>
                             <code>ABAP.INTERFACE_REGISTRATION_ERROR</code>
                             <text>No implementing class registered for the interface (ABAP interface, request message SI_BAPI_CUSTOMER_DISPLAY_REQUEST, request message, namespace http://send)</text>
    PS: - I've generated all proxy at r3 system. (via tcode Sproxy)
             - And Sxmb_adm I've set Business System is Application System.
    Please help me to fix this error.
    Many thanks.

    >>ABAP.INTERFACE_REGISTRATION_ERROR
    You did not complete proxy objects coding yet.

  • System Error in Message Monitoring -Proxy to SOAP async scenario

    Hi All,
    My scenario is ABAP Proxy---> SAP PI 7.1 ---> WEbService(Asynchronous SOAP ).
    In Moni message is showing successful Flag, but message has got stuck in "system Error" at message monitoring.I can't see any Audit log in Message monitoring .
    but in related Soap Receiver communication channel i can see the below Error 
    "2010-08-11 09:54:15 Error SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Server was unable to process request. ---> Retrieving the COM class factory for component with CLSID {00226D6E-6A57-44DB-9DDC-66FDCB2869B3} failed due to the following error: 80070005.
    2010-08-11 09:54:15 Information SOAP: sending a delivery error ack ...
    2010-08-11 09:54:15 Information SOAP: sent a delivery error ack
    2010-08-11 09:54:15 Error Adapter Framework caught exception: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Server was unable to process request. ---> Retrieving the COM class factory for component with CLSID {00226D6E-6A57-44DB-9DDC-66FDCB2869B3} failed due to the following error: 80070005.
    2010-08-11 09:54:15 Error Delivering the message to the application using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Server was unable to process request. ---> Retrieving the COM class factory for component with CLSID {00226D6E-6A57-44DB-9DDC-66FDCB2869B3} failed due to the following error: 80070005. "
    Please help , what could be the problem.
    Thanks in Advance.
    Jyoti

    Hi Jyoti,
    >Is there any specific setup required at Provide side while moving to Acceptance system
    I dont think so.
    Please compare EXACTLY the settings of the two Comunication Channels, especially the server path. Please assure that you ve sent exactly the same message content from Acceptance system.
    Regards,
    Udo

  • Error while testing SOAP scenario

    I have done SOAP(Sender)--SAP-PI- SOAP(RECEIVER) Scenario. It is in synchorous mode..
    It works fine in Altove XML Spy.. and getting the response fron webservice..
    but when i;m testing it PI (RWB->Comp Monit>Integration engine-->Test Messge ) it gives me error
    " Error While Testing: Method Not implemented "
    Can anyone please help me on this.. What acould be the reason.. for this..
    Regards,
    deep

    Sunil, Thanks For your Reply...
    Payload is correct.. and mapping is also fine. I'm getting reponse from Webservices using XML SPY..
    But i have seen one warning about Integation Engine : Is Websecurity Available : Communication error Proxy calls are not permitted on sender or receiver side on the IS (client)  in Component monitoring..
    Does this warning cause this error  anyway.. ?  Because i'm getting error even in XML SPY when i defined business system as Sender and Receiver as Business Service. But if i define both are as Business Serivces.. it works fine.. (in XML SPY)
    But in both cases i'm failing in RWB(INtegration engine-:>Test message)
    Is there any relation to above mentioned warning " Is Websecurity Available : Communication error Proxy calls are not permitted on sender or receiver side on the IS (client)  in Component monitoring.. "
    Regards,
    Deep

  • Error while executing the SOAP-XI-JDBC(syn) scenario

    Dear Forum,
    We have done SOAP-XI-JDBC(synch) scenario with out BPM.
    When we sent the request data from EP to Oracle database through XI, we got an error,Runtime in Message-Mapping transformation~.
    com.sap.aii.utilxi.misc.api.BaseRuntimeException: Runtime in Message-Mapping transformation: Cannot produce target element /ns:Customer/customers. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd at com.sap.aii.mappingtool.tf3.AMappingProgram.start(AMappingProgram.java:291)
    Exception message says that it is a mapping issue. But we got the responce data from database along with this message.In message monitoring we got the message processed successfully.
    Now i am not able to understanding why it throughs an error Runtime in Message-Mapping transformatio~ first time ?
    Pls revert me to fulfill this task successfully.
    Points will be rewarded.
    Regards,
    Naresh

    Dear Friends,
    Sorry for the delay,and Thank you for your quick responce.
    Yes I got that message under trace option in SXMB_MONI,
    Pls find the following msg structures and if any error please let me know status...
    Soap request structure:
    <?xml version="1.0" encoding="ISO-8859-1"?>
    <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://soap2dbns" targetNamespace="http://soap2dbns">
    <xsd:element name="soap_reqmt" type="soap_reqdt" />
    <xsd:complexType name="soap_reqdt">
    <xsd:annotation>
    <xsd:appinfo source="http://sap.com/xi/TextID">
    5b474a34c8a511dc8d8e001a4bf038d4
    </xsd:appinfo>
    </xsd:annotation>
    <xsd:sequence>
    <xsd:element name="Request" maxOccurs="unbounded">
    <xsd:annotation>
    <xsd:appinfo source="http://sap.com/xi/TextID">
    49b1ae20c81211dcce03001b78afb958
    </xsd:appinfo>
    </xsd:annotation>
    <xsd:complexType>
    <xsd:sequence>
    <xsd:element name="ORDERID" type="xsd:string">
    <xsd:annotation>
    <xsd:appinfo source="http://sap.com/xi/TextID">
    49b1ae21c81211dcc20d001b78afb958
    </xsd:appinfo>
    </xsd:annotation>
    </xsd:element>
    <xsd:element name="Operation" type="xsd:string">
    <xsd:annotation>
    <xsd:appinfo source="http://sap.com/xi/TextID">
    49b1ae22c81211dc858a001b78afb958
    </xsd:appinfo>
    </xsd:annotation>
    </xsd:element>
    </xsd:sequence>
    </xsd:complexType>
    </xsd:element>
    </xsd:sequence>
    </xsd:complexType>
    </xsd:schema>
    Data base request structure:
    <?xml version="1.0" encoding="ISO-8859-1"?>
    <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://soap2dbns" targetNamespace="http://soap2dbns">
    <xsd:element name="db_reqmt" type="db_reqdt" />
    <xsd:complexType name="db_reqdt">
    <xsd:annotation>
    <xsd:appinfo source="http://sap.com/xi/TextID">
    5b4e7620c8a511dcc4fe001a4bf038d4
    </xsd:appinfo>
    </xsd:annotation>
    <xsd:sequence>
    <xsd:element name="STATEMENTNAME" maxOccurs="unbounded">
    <xsd:annotation>
    <xsd:appinfo source="http://sap.com/xi/TextID">
    fa204eb0bceb11dcbb54001b78b0798a
    </xsd:appinfo>
    </xsd:annotation>
    <xsd:complexType>
    <xsd:sequence>
    <xsd:element name="FETCHDATA">
    <xsd:annotation>
    <xsd:appinfo source="http://sap.com/xi/TextID">
    fa204eb1bceb11dc9750001b78b0798a
    </xsd:appinfo>
    </xsd:annotation>
    <xsd:complexType>
    <xsd:sequence>
    <xsd:element name="TABLE" type="xsd:string">
    <xsd:annotation>
    <xsd:appinfo source="http://sap.com/xi/TextID">
    fa204eb3bceb11dccc94001b78b0798a
    </xsd:appinfo>
    </xsd:annotation>
    </xsd:element>
    <xsd:element name="access">
    <xsd:annotation>
    <xsd:appinfo source="http://sap.com/xi/TextID">
    fa204eb4bceb11dc9b35001b78b0798a
    </xsd:appinfo>
    </xsd:annotation>
    <xsd:complexType>
    <xsd:sequence>
    <xsd:element name="ORDERID" type="xsd:string">
    <xsd:annotation>
    <xsd:appinfo source="http://sap.com/xi/TextID">
    fa204eb5bceb11dca20a001b78b0798a
    </xsd:appinfo>
    </xsd:annotation>
    </xsd:element>
    <xsd:element name="ITEM" type="xsd:string">
    <xsd:annotation>
    <xsd:appinfo source="http://sap.com/xi/TextID">
    d0279840c81011dc8e4e001b78afb958
    </xsd:appinfo>
    </xsd:annotation>
    </xsd:element>
    <xsd:element name="QUANTITY" type="xsd:string">
    <xsd:annotation>
    <xsd:appinfo source="http://sap.com/xi/TextID">
    d0279841c81011dcb8f4001b78afb958
    </xsd:appinfo>
    </xsd:annotation>
    </xsd:element>
    <xsd:element name="PRICE" type="xsd:string">
    <xsd:annotation>
    <xsd:appinfo source="http://sap.com/xi/TextID">
    d0279842c81011dc832f001b78afb958
    </xsd:appinfo>
    </xsd:annotation>
    </xsd:element>
    </xsd:sequence>
    </xsd:complexType>
    </xsd:element>
    <xsd:element name="key">
    <xsd:annotation>
    <xsd:appinfo source="http://sap.com/xi/TextID">
    89f43170c81611dcc8fa001b78afb958
    </xsd:appinfo>
    </xsd:annotation>
    <xsd:complexType>
    <xsd:sequence>
    <xsd:element name="ORDERID">
    <xsd:annotation>
    <xsd:appinfo source="http://sap.com/xi/TextID">
    89f43171c81611dcb6e3001b78afb958
    </xsd:appinfo>
    </xsd:annotation>
    <xsd:complexType>
    <xsd:simpleContent>
    <xsd:extension base="xsd:string">
    <xsd:attribute name="compareOperation" type="xsd:string">
    <xsd:annotation>
    <xsd:appinfo source="http://sap.com/xi/TextID">
    89f43172c81611dccba5001b78afb958
    </xsd:appinfo>
    </xsd:annotation>
    </xsd:attribute>
    </xsd:extension>
    </xsd:simpleContent>
    </xsd:complexType>
    </xsd:element>
    </xsd:sequence>
    </xsd:complexType>
    </xsd:element>
    </xsd:sequence>
    <xsd:attribute name="action" type="xsd:string">
    <xsd:annotation>
    <xsd:appinfo source="http://sap.com/xi/TextID">
    fa204eb2bceb11dca298001b78b0798a
    </xsd:appinfo>
    </xsd:annotation>
    </xsd:attribute>
    </xsd:complexType>
    </xsd:element>
    </xsd:sequence>
    </xsd:complexType>
    </xsd:element>
    </xsd:sequence>
    </xsd:complexType>
    </xsd:schema>
    Soap Responce Structure:
    <?xml version="1.0" encoding="ISO-8859-1"?>
    <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://soap2dbns" targetNamespace="http://soap2dbns">
    <xsd:element name="soap_resmt" type="soap_resdt" />
    <xsd:complexType name="soap_resdt">
    <xsd:annotation>
    <xsd:appinfo source="http://sap.com/xi/TextID">
    8d49d494c8a411dc81f5001a4bf038d4
    </xsd:appinfo>
    </xsd:annotation>
    <xsd:sequence>
    <xsd:element name="response" minOccurs="0" maxOccurs="unbounded">
    <xsd:annotation>
    <xsd:appinfo source="http://sap.com/xi/TextID">
    491ccd30bd0611dcb29d001b78b0798a
    </xsd:appinfo>
    </xsd:annotation>
    <xsd:complexType>
    <xsd:sequence>
    <xsd:element name="row" minOccurs="0" maxOccurs="unbounded">
    <xsd:annotation>
    <xsd:appinfo source="http://sap.com/xi/TextID">
    491ccd31bd0611dca3d7001b78b0798a
    </xsd:appinfo>
    </xsd:annotation>
    <xsd:complexType>
    <xsd:sequence>
    <xsd:element name="ORDERID" type="xsd:string">
    <xsd:annotation>
    <xsd:appinfo source="http://sap.com/xi/TextID">
    491ccd32bd0611dcc7d1001b78b0798a
    </xsd:appinfo>
    </xsd:annotation>
    </xsd:element>
    <xsd:element name="ITEM" type="xsd:string">
    <xsd:annotation>
    <xsd:appinfo source="http://sap.com/xi/TextID">
    491ccd33bd0611dca6ad001b78b0798a
    </xsd:appinfo>
    </xsd:annotation>
    </xsd:element>
    <xsd:element name="QUANTITY" type="xsd:string">
    <xsd:annotation>
    <xsd:appinfo source="http://sap.com/xi/TextID">
    491ccd34bd0611dc95a8001b78b0798a
    </xsd:appinfo>
    </xsd:annotation>
    </xsd:element>
    <xsd:element name="PRICE" type="xsd:string">
    <xsd:annotation>
    <xsd:appinfo source="http://sap.com/xi/TextID">
    491ccd35bd0611dcc034001b78b0798a
    </xsd:appinfo>
    </xsd:annotation>
    </xsd:element>
    </xsd:sequence>
    </xsd:complexType>
    </xsd:element>
    </xsd:sequence>
    </xsd:complexType>
    </xsd:element>
    </xsd:sequence>
    </xsd:complexType>
    </xsd:schema>
    Database responce Structure:
    <?xml version="1.0" encoding="ISO-8859-1"?>
    <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://soap2dbns" targetNamespace="http://soap2dbns">
    <xsd:element name="db_resmt" type="db_resdt" />
    <xsd:complexType name="db_resdt">
    <xsd:annotation>
    <xsd:appinfo source="http://sap.com/xi/TextID">
    8d3b7cb1c8a411dcb1d6001a4bf038d4
    </xsd:appinfo>
    </xsd:annotation>
    <xsd:sequence>
    <xsd:element name="STATEMENTNAME_response" maxOccurs="unbounded">
    <xsd:annotation>
    <xsd:appinfo source="http://sap.com/xi/TextID">
    adca3410bcfd11dcaf4c001b78b0798a
    </xsd:appinfo>
    </xsd:annotation>
    <xsd:complexType>
    <xsd:sequence>
    <xsd:element name="row" minOccurs="0" maxOccurs="unbounded">
    <xsd:annotation>
    <xsd:appinfo source="http://sap.com/xi/TextID">
    adca3411bcfd11dc92d6001b78b0798a
    </xsd:appinfo>
    </xsd:annotation>
    <xsd:complexType>
    <xsd:sequence>
    <xsd:element name="ORDERID" type="xsd:string">
    <xsd:annotation>
    <xsd:appinfo source="http://sap.com/xi/TextID">
    adca3412bcfd11dc92e8001b78b0798a
    </xsd:appinfo>
    </xsd:annotation>
    </xsd:element>
    <xsd:element name="ITEM" type="xsd:string">
    <xsd:annotation>
    <xsd:appinfo source="http://sap.com/xi/TextID">
    adca3413bcfd11dc9f7a001b78b0798a
    </xsd:appinfo>
    </xsd:annotation>
    </xsd:element>
    <xsd:element name="QUANTITY" type="xsd:string">
    <xsd:annotation>
    <xsd:appinfo source="http://sap.com/xi/TextID">
    adca3414bcfd11dcc6c4001b78b0798a
    </xsd:appinfo>
    </xsd:annotation>
    </xsd:element>
    <xsd:element name="PRICE" type="xsd:string">
    <xsd:annotation>
    <xsd:appinfo source="http://sap.com/xi/TextID">
    adca3415bcfd11dca54c001b78b0798a
    </xsd:appinfo>
    </xsd:annotation>
    </xsd:element>
    </xsd:sequence>
    </xsd:complexType>
    </xsd:element>
    </xsd:sequence>
    </xsd:complexType>
    </xsd:element>
    </xsd:sequence>
    </xsd:complexType>
    </xsd:schema>
    Regards,
    Naresh

  • Error while testing sender SOAP scenario from XMLSpy-but can test from RWB

    HI,
    I developed one scenario with sender SOAP adapter and Receiver side ABAP proxy.
    Now I want to test my scenario.
    I tested my scenario  successfully from RWB-->Integration server &#61664;Integration Engine. ( it posted successfully and I can see checked flag in SXMB_MONI)
    But when I tried to test the scenario fro XML spy it is throwing HTTP error 500.
    When I type my URL in internet explores it is giving “Message Servlet is in Status OK”.
    I am not sure what is the difference between there two type of testing.
    What does it mean by successful from RWB and fails from XMLSpy?
    Why I am getting this error from XMLSpy?

    Dear Ashok,
    if RWB showing you successful then message in not in error.
    XML Spy giving error HTTP 500 not it is just server error.This might be due to large payload.
    here is the description of all error related with 500+
    5xx Server Error
    The server failed to fulfill an apparently valid request.
    Response status codes beginning with the digit "5" indicate cases in which the server is aware that it has erred or is incapable of performing the request. Except when responding to a HEAD request, the server SHOULD include an entity containing an explanation of the error situation, and whether it is a temporary or permanent condition. User agents SHOULD display any included entity to the user. These response codes are applicable to any request method.
    500 Internal Server Error
    501 Not Implemented
    502 Bad Gateway
    503 Service Unavailable
    504 Gateway Timeout
    505 HTTP Version Not Supported
    506 Variant Also Negotiates (RFC 2295)
    507 Insufficient Storage (WebDAV) (RFC 4918)
    509 Bandwidth Limit Exceeded
    This status code, while used by many servers, is not an official HTTP status code.
    510 Not Extended (RFC 2774)
    first ping your server
    Tcode for this is SM49>ping
    Then in additional parameter put the server IP and execute it will show you its reachability.
    if it is not reachable then contact the server vendor,
    Else if it is timeout problemthen
    you run Tcode SXMB_ADM>intregration engine configuration
    put category RUNTIME
    then click specific configuration
    Then change/increase HTTP timeout
    **PS: Reward points if useful**
    Regards,
    Sumit Gupta

  • When will we go for Altova xml spy testing in case of soap scenario ??

    Hi
    suppose I have a scenario like this: rfc-xi-soap. In this scenario if somebody say's testing the scenario using Altova xml spy means Altova xml spy will be acting as webservice ?? what is the ( or is there) significance of below URL in testing ??
    http://<host>:<j2ee-port>/XISOAPAdapter/MessageServlet?
    channel=<party>:<service>:<channel>
    thanks
    kumar

    Hi Kumar
    I am using XmlSpy for following reasons ::
    *) To check & confirm the Request/Response/Fault Structure of the WebService.
    *) To check the whether the WebService is UP or not, in case someone has reported an issue.
    *) To develop the xsd structure for the WebServices, in case I am getting different structure after importing the WSDL in XI. Like in the case of this Weblog -->
    /people/shabarish.vijayakumar/blog/2006/03/23/rfc--xi--webservice--a-complete-walkthrough-part-1
    In this response structure is created, you can also use other tools for creating xsd.
    - Lalit -

  • SOAP to IDocs Scenario...IDocs getting locked at SAP

    Dear Experts
    We are sending measuring point details to SAP system from 3rd Party. Scenario is working fine for small amount of load. If more number of messages triggered (say 100) IDocs at SAP are getting stuck u201CMeasPoint 10000211 currently locked -> document processing not possibleu201D.
    I tried configuring Sender SOAP adapter as EOIO and specified the Queue name as Test Queue. Still IDocs are getting stuck at SAP ECC. Now one more issues messages are getting stuck in queue SMQ2. We can control the flow by using BPM in PI. I donu2019t want to use BPM for this. Can we control this from SAP or using Trigger by background program in Partner profiles?
    Please suggest. Thank You.
    SAP Error Details:-MeasPoint 10000211 currently locked -> document processing not possible
    Message no. IR007
    Diagnosis
    The object you want to access is locked, either
    u2022     By yourself in another session, or
    u2022     By another user
    u2022     or by the system, which is still processing data for this object
    System Response
    The system cannot access the object.
    Procedure
    u2022     If you are locking the object yourself in another session, exit processing in the other session and continue processing in this session.
    u2022     If the object is locked by another user, you can
    o     contact the other user
    o     wait until the other user has finished processing the object
    u2022     If the object is locked because the system is still processing its data, wait a while, and then call up the object again.

    1. Create a new process code "Z" and check the enque state of the objects before passing back to standard processing modules. Id also change to process immediate as part of this change
    or
    2. I think assuming RBDAPP01 is still used you may be able to make use of an exit there to do the same thing .. check and wait before processing.
    or
    3. In message mapping place a UDF that has some kind of wait timer in it (this is random and wont always work cause you wont know when the lock is dropped) but should work.
    or
    4. Dont use IDOC's create an abap proxy to do the work as a sync process. Processing will need to finish in the proxy and return to the PI stack before the next message is processed in the EOIO queue - this would be the prefered option as far as im concerned, it guarenteed to work and as long as your proxy sticks to the standard rouintes it should be upgrade friendly.
    or
    5. Use a proxy as above but dont do any processing, just use the proxy to build the IDOC and post it - then check the status of the locks until you are ready then rinse and repeat ..... but like scratching your right ear with your left hand .. but it will work.

  • '500 Connection timed out' Error in Sender SOAP Scenario

    Hi mates,
    I exposed o/b synch MI as a webservice. This webservice is received by a BPM and it triggers an IDOC generation program on R/3. BPM waits & collects the IDOCs and cosntructs the response from these IDOCs and returns it to the webservice caller.
    I'm making the SOAP call from a client program and I get the correct response in some cases where the data requested is not huge...normally with in 30 sec.
    But in some cases I get the error '500 Connection timed out' after 60 sec. The detailed message is as follows.
    <i>500 Connection timed out
    Connection timed out (-5)
    Error: -5
    Version: 6040
    Component: ICM
    Date/Time: Thu Jun 15 17:06:10 2006 
    Module: icxxthr_mt.c
    Line: 2551
    Server: hcidx1_DX1_03
    Detail: Connection to partner timed out after 60s</i>
    My BPM waits for 10 minutes and I set the parameter XI.Timeout to 600000 (i.e. 10 minutes) in module parameter table for the sender SOAP adapter as per the note 856597. And in SXMB_ADM, I set the parameter CHECK_FOR_ASYNC_RESPONSE_TIMEOUT of category SA_COMM to 600. In my client program, I set the timeout as 1 hour. All these config params are supposed to make sure that all the components involved wait for atleast 10 mins before they timeout.
    But I get timeout after 60 sec. Whats wrong/missing?
    I highly appreciate your inputs.
    thx in adv
    praveen

    Hey Praveen,
    <i>I'm making the SOAP call from a client program and I get the correct response in some cases where the data requested is not huge...normally with in 30 sec.
    But in some cases I get the error '500 Connection timed out' after 60 sec. The detailed message is as follows.</i>
    does this mean you are getting some response in some cases where u r payload is small , and if its large ur getting some timeout like this? Also is ur scenario Sync / Async?
    Assuming i understood correctly , i came a similar situation but that has to do some thing with Paging file / memory issues when the files are too huge and no. of users are high please let me know if this is the case.
    best regards
    Vara
    [PLEASE REWARD FOR POSTING]

  • Creating Custom SOAP header in the Sender soap scenario

    Hello Experts,
    Currently i have a SOAP to RFC scenario . In which in the request parameter i have single input parameter. But as per the requirement we need to have some xml parameters in the soap header .
    So i want the soap request looks like below,
    <?xml version="1.0"?>
    -<SOAP-ENV:Envelope xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
    -<SOAP-ENV:Header>
    -<ns0:TestHeader xmlns:ns0="http://testcustomer.com">
    -<MessageDetails>
    <ServiceType/>
    <ServiceAction>String</ServiceAction>
    <MessageRole rtype=""/>
    -<MessageSource>
    <SourceName/>
    <SourceID idtype=""/>
    </MessageSource>
    -<MessageDestinations>
    -<MessageDestination>
    <DestinationID idtype=""/>
    <DestinationName/>
    </MessageDestination>
    </MessageDestinations>
    <Property Name=""/>
    </MessageDetails>
    </ns0:TestHeader>
    </SOAP-ENV:Header>
    -<SOAP-ENV:Body>
    -<m:MT_CERT_IP xmlns:m="http://mydzit.gov.sa/zakat">
    <INPUT1>102140000007</INPUT1>
    </m:MT_CERT_IP>
    </SOAP-ENV:Body>
    </SOAP-ENV:Envelope>
    Kindly let me know the steps, how can i achieve this ??
    I have referred the AddSOAPHeaderBean  module but still not received the needed output.
    Best Regards,
    Amit

    Hi Amit,
    My few cents.
    You have an example in Dimitri Sannen's blog Read SOAP header information doing the mapping with XSLT.
    Also, you have an other example like Dev Noronha suggestion, in William Li's blog How to Read SOAP Header Information
    Regards.

  • How do I test Sender SOAP scenario?

    Hi
    Soap - IDOC.
    The authorizations on the WS to send data is not yet provided to me.
    thus, I m trying to send a sample data from Altova XML spy.
    For this purpose I have created a WSDL from ID (Tools -> create WS)
    in Receiver NS, receiver MI, I have given receiver side details only
    but in sender side NS and MI and Sender service, I have given the Sender service that I have created in ID and the XI's local NS and receiver MI
    For URL, I have selected on "Propose URL". Now will I be able to send data to the R3 server with this link?
    (R3 is production server in my network)
    now with that WSDL, I coudlnt validate in XML SPY.
    have I provided the correct details?
    Please suggest me is there any other way of testing Sender WS to IDOC?
    Thanks and Regards,
    Venkat.

    oops I guess I have confused u
    let me detail it again
    Scenario : SOAP - XI - IDOC
    The scenario is finished.
    I dont have authorizations on WS to logon n send the data
    Thus, I have created WSDL from ID (in XI)
    now I want to send data to XI which inturn will post the data to R3 and create a IDOC
    when I try to validate the WSDL created through XI using SPY, it couldnt validate and I couldnt send the request
    I want to send the data from outside XI and I want to generate a IDOC with the test data I have specified.
    how do I do it?
    Hope I made it clear this time
    Thanks,
    Nikhil.

  • Fault message in sender SOAP scenario

    Hi mates,
    I've a o/b synch MI which is exposed as a web service. I've specified the fault message with faultcode, faultstring, faultactor and detail. I've a BPM as the receiver for this synch infterface. This BPM implements synch-asynch bridge.
    Now the question is...How can I specify that a particular fault message needs to be returned to the SOAP caller. I can send the response for the SOAP caller using the send step with mode 'Closes S/A bridge'.
    I appreciate you inputs.
    thx in adv
    praveen

    Moorthy,
    I've the FM in my BPM. But...how can I append this to Response message as these have two different MTs?
    Do you mean to say my response message should have a node for fault message data?
    I'm trying to implement sth like in this blog <a href="/people/sap.user72/blog/2006/01/16/xi-propagation-of-meaningful-error-information-to-soap-client">Propagation of meaningful error information to SOAP Client</a>
    To achieve FM in SOAP scenario, should I be using <b>only</b> a non-BPM receiver like a R/3 system using FM with exception as the receiver? Can this be not possible if I use BPM as receiver?
    thx in adv
    praveen

  • Sender Soap scenario HTTP/1.1 404 Not Found error

    Hello All,
    I created SOAP to  IDOC scenario, generated the WSDL file from Sender agreement and while testing the interface using SOAPUI tool iam getting HTTP/1.1 404 Not Found error.
    i gave login authorization details in the SOAPUI tool.
    Update: when i generated the WSDL file from sender agrement, in the URL the port number was 443.
    when i check the port numer in SMICM transaction it show 50000.
    Now when i test with port numer 443 iam getting Connction refused error.
    Regards,
    Chinna
    Edited by: chinnasapxi on Mar 4, 2011 6:44 AM

    i created the URl and when i tested the from SOAP UI below is the error detials.
    Fri Mar 04 11:32:08 IST 2011:ERROR:com.eviware.soapui.model.iface.Request$SubmitException: com.eviware.soapui.impl.wsdl.submit.RequestTransportRegistry$MissingTransportException: Missing transport for protocol [ http]
       com.eviware.soapui.model.iface.Request$SubmitException: com.eviware.soapui.impl.wsdl.submit.RequestTransportRegistry$MissingTransportException: Missing transport for protocol [ http]
            at com.eviware.soapui.impl.wsdl.WsdlRequest.submit(WsdlRequest.java:241)
            at com.eviware.soapui.impl.wsdl.panels.request.AbstractWsdlRequestDesktopPanel.doSubmit(AbstractWsdlRequestDesktopPanel.java:146)
            at com.eviware.soapui.impl.support.panels.AbstractHttpRequestDesktopPanel.onSubmit(AbstractHttpRequestDesktopPanel.java:777)
            at com.eviware.soapui.impl.support.panels.AbstractHttpRequestDesktopPanel$SubmitAction.actionPerformed(AbstractHttpRequestDesktopPanel.java:488)
            at javax.swing.AbstractButton.fireActionPerformed(Unknown Source)
            at javax.swing.AbstractButton$Handler.actionPerformed(Unknown Source)
            at javax.swing.DefaultButtonModel.fireActionPerformed(Unknown Source)
            at javax.swing.DefaultButtonModel.setPressed(Unknown Source)
            at javax.swing.plaf.basic.BasicButtonListener.mouseReleased(Unknown Source)
            at java.awt.AWTEventMulticaster.mouseReleased(Unknown Source)
            at java.awt.Component.processMouseEvent(Unknown Source)
            at javax.swing.JComponent.processMouseEvent(Unknown Source)
            at java.awt.Component.processEvent(Unknown Source)
            at java.awt.Container.processEvent(Unknown Source)
            at java.awt.Component.dispatchEventImpl(Unknown Source)
            at java.awt.Container.dispatchEventImpl(Unknown Source)
            at java.awt.Component.dispatchEvent(Unknown Source)
            at java.awt.LightweightDispatcher.retargetMouseEvent(Unknown Source)
            at java.awt.LightweightDispatcher.processMouseEvent(Unknown Source)
            at java.awt.LightweightDispatcher.dispatchEvent(Unknown Source)
            at java.awt.Container.dispatchEventImpl(Unknown Source)
            at java.awt.Window.dispatchEventImpl(Unknown Source)
            at java.awt.Component.dispatchEvent(Unknown Source)
            at java.awt.EventQueue.dispatchEvent(Unknown Source)
            at java.awt.EventDispatchThread.pumpOneEventForFilters(Unknown Source)
            at java.awt.EventDispatchThread.pumpEventsForFilter(Unknown Source)
            at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
            at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
            at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
            at java.awt.EventDispatchThread.run(Unknown Source)

  • Sender SOAP (Scenario)

    Hi Guys,
    Here is my scenario where client has a Java Web Aplication to get connected to my Backend System using RFC.This happens through XI.
    I produce the Outbound Interface in the Form of WebService (By generating WSDL file)
    Here we use Sender SOAP Adapter. I want to implement security level using key / certificates.
    Now important thing here is the people who are going to login donot have username on PI box.
    Now how can assign the certificate to the users who are external in my visual admin.
    Hope my scenario is clear . Kindly post u r views on this.
    With regards
    Srini

    Hi,
    I guess the Service user which you would have created will be in XI abap stack only.You need to provide the url and the userId, pwd to the web service client so that they will be bale to invoke your webservice.. you don't have to give the service user details in Soap Sender Adapter. It is just for ypur web client to acesss your webservice.
    The url will be like this:
    http://<serverhost>:<port>/XISOAPAdapter/MessageServlet?channel=<party>:<ServiceName>:<Channel Name>
    I hope it clears your doubt.
    Thanks
    Amit
    Edited by: Craig Cmehil on Jul 3, 2008 3:30 PM

  • Error in SOAP receiver channel in Synchronous Proxy to SOAP scenario

    Hi all,
    We are experiencing an issue with a synchronous Proxy to SOAP scenario. Getting below error message in the SOAP receiver communication channel for the response message.
    SOAP: Response message contains an errorXIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 500 Internal Server Error
    Returning to application. Exception: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Error encountered while executing mapping: com.sap.aii.af.service.mapping.MappingException: com.sap.aii.utilxi.misc.api.ResourceException: Could not determine mapping steps for message 1364b76e-ecbf-11e4-85f4-000023acfde6.
    We are running PI 7.4.
    Any help is appreciated.
    Thanks,
    Pushpa

    Hi,
    Seems the Receiver Webservice is not reachable. Did you try to test it using SOAP UI tool.
    1. Test a fresh message from local SOAP UI tool.
    2. Pick 3rd party WSDL file and Import in SOAP UI tool.
    3. Put some dummy data for mandatory fields
    4. Trigger it msg and ckh if you get successful / response msg.
    5. Check if firewall is open and that URL is not blocked.
    Hope it helps
    Regards,
    Azhar

Maybe you are looking for

  • How to remove (all) footnotes in Indesign CS5.5?

    I'm still having that trouble where Indesign crashes the moment you try to export it to HTML. See the associated post on this genuinely terrifying, workflow breaking problem here -> http://forums.adobe.com/message/4022421#4022421 . This appears to ha

  • Register-SPWorkflowService : The underlying connection was closed: An unexpected error occurred on a receive

    My Fellow SharePoint 2013 Engineers, For the past two days I have been struggling to setup the SharePoint 2013 Workflow Manager. After following the detailed steps provided by Harbar.net when I reach the final step to register the workflow service fo

  • How do I get rid of Ask?

    How do I uninstall Ask?

  • Win 7 64 bit vs Desktop OS 6.2.2 and my Centro

    I am a Volunteer here, not employed by HP. You too can become an HP Expert! Details HERE! If my post has helped you, click the Kudos Thumbs up! If it solved your issue, Click the "Accept as Solution" button so others can benefit from the question you

  • Complexe percentage calculation

    hi, I would like to compute percentage based on this table between ticket and CA based on BUV and ID parameters: ID BUV Ticket CA 103 BUV31 2 274 € 32 662 € 103 BUV2 1 979 € 32 662 € 103 BUV35 1 788 € 32 662 € 104 BUV31 2 492 € 40 900 € 104 BUV2 2 31