HTTP payload

Hello Y'all,
I would like to know how a sender header HTTP payload would like ? I mean would the Party, sender, namespace need to be setup explicitly as XML tags in the header field so that the http//:<host><port>/xiadapter/....can pick it up?
-AR

Hi,
It would look like normal XML strucutre
<root>
<fields/>
</root>
The Party, sender, namespace will be in the part of the URL and not in payload
Check out the Features part in the following link
http://help.sap.com/saphelp_nw04/helpdata/en/43/64db4daf9f30b4e10000000a11466f/content.htm
Regards,
Prakash

Similar Messages

  • Plain http payload xml format

    Hi,
    Can anyone point me to any documentation/example on the xml layout for the payload. I am using the plain http send to XI and I need to know how to put the data into the right xml format. Thanks..

    Hi Shilton,
    As said already you can get the payload from the "src" of the test tab. But you have to be careful while creating it as a payload. Usually we create the payload as string. And also the XML needs the " compulsorily. for example in <?xml version=<b>"</b>1.0<b>"</b>.
    while creating the string be careful and use '\' character before these quotes.
    something like this.
    var payload = "<?xml version=\"1.0\" encoding=\"UTF-8\"?><ns0:input_mt xmlns:ns0=\"http://com.somenamespace\">
       <val>000000000000001135</val>
    </ns0:input_mt>";
    hope this helps.
    regards
    venkat

  • HTTP payload issue

    Hey all,
    I have an RFC to HTTP scenario, i have managed so far to execute the RFC, pass those values to an XML which is send to an HTTP (Oanda web) and get a response (this last part is the problem)
    i'm trying to map this response from that site to my RFC.Response, but while i see the response in the monitoring  i don't see that this is passing in the format i need which would be:
    <?xml version="1.0" encoding="UTF-8"?>
    <ns0:MT_Response xmlns:ns0="http://test/Fxml">
       <RESPONSE>
          <EXPR/>
          <EXCH/>
          <AMOUNT/>
          <NPRICES/>
          <CONVERSION>
             <DATE/>
             <ASK/>
             <BID/>
          </CONVERSION>
       </RESPONSE>
    </ns0:MT_Response>
    I just see the response in the format send back by the site
    <RESPONSE>
    <EXPR>
    <EXCH>
    <AMOUNT>
    <NPRICES>
    <CONVERSION>
    <DATE>
    <ASK>
    <BID>
    </CONVERSION>
    </RESPONSE>
    - So, as you can see, it seems like the response from the web is making no relation to my Message Type (synchronous), and since my MT is not related, i have an empty response from the RFC
    - How is this possible? what would i need to do in order to create the response in the xml format i created and fill with the correct payload format?
    any help would be apreciated,
    Thanks in advance!

    I tried that but is not working
    if i try to map MT_Response => ZRFC.Response header
    or
    MT_Response/RESPONSE  => ZRFC.Response header
    I get an error (red flag on moni) and i have a mapping exception, my guess is this is because ZRFC.Response is 1.1 and i'm mapping something empty, that's why i was telling that i can't generate the MT_Response file (but in moni i see the RESPONSE format from the web, but is not translating that to my MT)
    of course that if i map a constant to ZRFC.Response i create an empty response, but then again the problem is my MT_Response, maybe im missing a parameter in the HTTP channel that takes the xml payload?
    Edited by: Alexis Alanis on Oct 7, 2008 10:35 AM

  • HTTP Payload contains invalid characters

    Hi all,
    we have a idoc - 2 - http scenario. the idoc xml will be directly routet through to the http receiver as simple payload. The http receiver told us after the successful processing, that the received payload was invalid.
    here is the payload example:
    Header      :
    'HOST' = '10.29.100.74:23005'
    'USER-AGENT' = 'Java/1.4.2_09'
    'CONTENT-TYPE' = 'application/octet-stream'
    'CONTENT-LENGTH' = '3286'
    'CACHE-CONTROL' = 'no-cache'
    'PRAGMA' = 'no-cache'
    'ACCEPT' = 'text/html, image/gif, image/jpeg, *; q=.2, /; q=.2'
    'CONNECTION' = 'keep-alive'
    Content      :
    Content-Length: 3286
    Content-Type: application/octet-stream
    ¼Ý t ¤ ...
    The marked character were added somewhere in the xi system. Any ideas where the problem could be?
    Thanks in advance
    Michael

    The characters before the xml declaration are unicode identifiers which are part of any unicode file.
    It should not lead to errors, but in this case the content-type should be application/xml
    Regards
    Stefan

  • Flat HTTP Payload with HTTP Receiver

    Hello,
    I have the requirement to send a flat structure (no XML) within the Payload of an HTTP POST. The flat structure should be URL-encoded. I already have a combined XSLT/Java Mapping which creates and encodes the desired structure.
    Problem now is that an XML-prolog is added to the message after the mapping step. The rest of the message looks fine, just the prolog cannot be handled of course.
    Is there any way having the XML prolog removed in a simple way? I want to avoid having the URL encoding logic in a module as I  use some parameters in the already existing Java Mapping and the mapping is already working fine.
    Thank you!

    Hi Guppenberger,
    I understand after mapping step XML prolog <?xml version="1.0" encoding="UTF-8" standalone="yes" ?> is getting added to non XML payload. Now, you want to delete it from payload. Please consider below solution as last resort.
    As payload is not XML, graphical and XSLT mapping cannot be used. So to remove prolog, you need to implement below Java Mapping as last mapping in Operational Mapping.
    package com.prolog;
    import com.sap.aii.mapping.api.*;
    import java.io.*;
    public class RemoveProlog_JavaMapping extends AbstractTransformation {
        public void transform(TransformationInput transformationInput, TransformationOutput transformationOutput) throws StreamTransformationException {
            OutputStream outputstream = null;
            try {
                //Read input payload and write the same to output payload after "?>" .
                //Beacuse <?xml version="1.0" encoding="UTF-8" standalone="yes" ?> ends with "?>"
                InputStream inputstream = transformationInput.getInputPayload().getInputStream();
                outputstream = transformationOutput.getOutputPayload().getOutputStream();
                byte[] b = new byte[inputstream.available()];
                inputstream.read(b);
                String inputFileContent = new String(b);
                outputstream.write(inputFileContent.substring(inputFileContent.indexOf("?>")+2).getBytes());
            } catch (Exception exception) {
                exception.printStackTrace();
    Regards,
    Raghu_Vamsee

  • HTTP- XI- SOAP(webservice) - error in outbound mapping

    Scenario is HTTP(request)->XI->SOAP(webservice) ->XI->HTTP(response)
    2 messsage mappings for request and response (syncronous)
    1 interface mapping
    HTTP payload reaches XI from there it appears problem translating request data to webservice external URL "http://webservices.imacination.com/distance/Distance.jws". 
    Message mappings when tested with sample xml in intergration repository results in success. Meaning source populated data gets copied to target in IR testing (both for request and response).
    Here is the log from SXMB_MONI
    - - - - SystemError synchronous 034E60D2-1D22-6B44-B424-E7A4527B7375 54F73912-E6A9-A741-A815-1F623FC79293 2007-01-23T14:50:58Z - vservice4 mi_inb_ws - vservice4 mi_out mi_out - BestEffort - Application <b>EXCEPTION_DURING_EXECUTE</b> com/sap/xi/tf/_mm_ws_ java.lang.NullPointerException During the application mapping com/sap/xi/tf/_mm_ws_ a <b>java.lang.NullPointerException was thrown</b>: N - - HTTP
    server-protocol HTTP/1.1 user-agent Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0) host <xiapp>:8050 content-length 230 remote-addr 10.20.40.120 <b>COMMIT is expected by application</b> !
    SAP_CENTRAL - - - - R E C E I V E R - D E T E R M I N A T I O N Cache Content is up to date - - - - I N T E R F A C E - D E T E R M I N A T I O N Cache Content is up to date - - - - number of receivers: 1 Single-receiver split case - - - - Interface Mapping urn:
    vmyvendor.org\http2webservice im_ws RuntimeException during appliction Java mapping com/sap/xi/tf/_mm_ws_ java.lang.NullPointerException at com.sap.aii.mappingtool.tf3.AMappingProgram.exceptionCaught$(AMappingProgram.java:59)
    Any pointers would be greatly appreciated. Thanks

    From XML request message->SOAP Header->Trace & using XML spy problem is in <b>CL_XMS_MAIN-CALL_PLSRV</b>. The log also talks about message persist processing, is it valid for sync webservice?
      <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Request Message Mapping
      -->
    - <SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30">
    + <Trace level="1" type="B" name="CL_HTTP_PLAIN_INBOUND">
      <Trace level="1" type="T">server-protocol HTTP/1.1</Trace>
      <Trace level="1" type="T">user-agent Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0)</Trace>
      <Trace level="1" type="T">host xiapp:8050</Trace>
      <Trace level="1" type="T">content-length 229</Trace>
      <Trace level="1" type="T">remote-addr 10.20.40.101</Trace>
      </Trace>
      <Trace level="1" type="T">COMMIT is expected by application !</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-ENTER_XMS" />
    - <!--  ************************************
      -->
      <Trace level="1" type="B" name="CL_XMS_MAIN-SET_START_PIPELINE" />
    - <!--  ************************************
      -->
      <Trace level="1" type="B" name="SXMBCONF-SXMB_GET_XMB_USE" />
      <Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV" />
      <Trace level="1" type="T">****************************************************</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_UC_EXECUTE" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">Message-GUID = 69CB2C55A02E1048AC67316A17FD109D</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 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="1" type="T">Corresponding internal pipeline SAP_CENTRAL</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
    + <Trace level="1" type="B" name="PLSRV_RECEIVER_DETERMINATION">
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
    - <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>
      </Trace>
      </Trace>
      </Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
    + <Trace level="1" type="B" name="PLSRV_INTERFACE_DETERMINATION">
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
    - <Trace level="1" type="B" name="CL_ID_PLSRV-ENTER_PLSRV">
      <Trace level="1" type="T">I N T E R F A C E - 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>
      </Trace>
      </Trace>
      </Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
    + <Trace level="1" type="B" name="PLSRV_RECEIVER_MESSAGE_SPLIT">
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
    - <Trace level="1" type="B" name="CL_XMS_PLSRV_RECEIVER_SPLIT-ENTER_PLSRV">
      <Trace level="1" type="T">number of receivers: 1</Trace>
      <Trace level="1" type="T">Single-receiver split case</Trace>
      </Trace>
      </Trace>
      </Trace>
      </Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
      <Trace level="1" type="B" name="PLSRV_MAPPING_REQUEST" />
    - <!--  ************************************
      -->
    + <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
      <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />
    - <!--  ************************************
      -->
      <Trace level="1" type="B" name="CL_MAPPING_XMS_PLSRV3-ENTER_PLSRV" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">Interface Mapping urn:
    vendor\http2webservice im_ws</Trace>
      <Trace level="1" type="T">RuntimeException during appliction Java mapping com/sap/xi/tf/_mm_ws_</Trace>
      <Trace level="1" type="T">java.lang.NullPointerException at com.sap.aii.mappingtool.tf3.AMappingProgram.exceptionCaught$(AMappingProgram.java:59) at com.sap.aii.mappingtool.tf3.Transformer.checkParserException(Transformer.java:182) at com.sap.aii.mappingtool.tf3.Transformer.start(Transformer.java:149) 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 $Proxy176.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.handleRequest(RFCDefaultRequestHandler.java:100) at com.sap.engine.services.rfcengine.RFCJCOServer.handleRequestInternal(RFCJCOServer.java:113) at com.sap.engine.services.rfcengine.RFCJCOServer$ApplicationRunnable.run(RFCJCOServer.java:157) 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/_mm_ws_: java.lang.NullPointerException; null</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/_mm_ws_: java.lang.NullPointerException; null 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 $Proxy176.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.handleRequest(RFCDefaultRequestHandler.java:100) at com.sap.engine.services.rfcengine.RFCJCOServer.handleRequestInternal(RFCJCOServer.java:113) at com.sap.engine.services.rfcengine.RFCJCOServer$ApplicationRunnable.run(RFCJCOServer.java:157) 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: java.lang.NullPointerException at com.sap.aii.mappingtool.tf3.AMappingProgram.exceptionCaught$(AMappingProgram.java:59) at com.sap.aii.mappingtool.tf3.Transformer.checkParserException(Transformer.java:182) at com.sap.aii.mappingtool.tf3.Transformer.start(Transformer.java:149) 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 $Proxy176.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.handleRequest(RFCDefaultRequestHandler.java:100) at com.sap.engine.services.rfcengine.RFCJCOServer.handleRequestInternal(RFCJCOServer.java:113) at com.sap.engine.services.rfcengine.RFCJCOServer$ApplicationRunnable.run(RFCJCOServer.java:157) 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>

  • HTTP adapter - Unable to access the following endpoint(s): REPLACE_WITH_ACTUAL_URL

    Hi All,
    Hope you all doing good.
    I had a simple but a bit unresolved issue.
    I am using soa suite 11.1.1.5 for calling a service which only accepts HTTPS POST requests.
    I used HTTP adapter to call that with required security applied.
    when I tested the process, the calling is not getting successful but the process goes in running state for 2 mins, and then fails with the error: Unable to access the following endpoint(s): REPLACE_WITH_ACTUAL_URL
    End point URL not reachable, and the URL after this.
    But there is 500 error message in the called service server log with the same user.
    I tried changing lot of things without success.
    Can anyone of you guide me, what could be going wrong here.
    Hope I get some solution .,
    Thanks in advance,
    Best Regards

    Hi,
    The process will receive the request as SOAP message. Then the process will call the service which accpets HTTPS POST message.
    I dont know, how to verify whether my service call out to service goes through POST method of HTTP adapter?
    But verb used is POST, http.payload is xml.
    Thanks & Regards
    Chandru

  • Please anyone explain me about HTTP adapter

    Can anyone explain about HTTP Adapter (sender,receiver) End to End implementation with screen shots?

    HI
    HTTP Adapter
    The HTTP Adapter allows connection between the Integration Server and application systems. External systems connect to the Integration Server using the native HTTP interface (HTTP payload without SOAP envelope) which is converted to XI protocol (SOAP with header enhancements). The HTTP Adapter allows synchronous and asynchronous message functionality
    http://help.sap.com/saphelp_erp2005/helpdata/en/69/a6fb3fea9df028e10000000a1550b0/frameset.htm
    http://www.erpgenie.com/netweaver/xi/adapters/index.htm
    Differences between adapters
    You can use the HTTP adapter. Refer to following SDN TV demo of the HHTP adapter for details steps involved into it.
    https://media.sdn.sap.com/SDNTV/main.asp?mediaId=107
    HTTPS using XMLSPY
    http://help.sap.com/saphelp_nw04/helpdata/en/14/ef2940cbf2195de10000000a1550b0/frameset.htm
    The HTTPS configuration data of the Adapter Engines has to be configured in the SLD.
    More Information in the "SAP Security Guide XI"
    http://help.sap.com/saphelp_nw04/helpdata/de/f7/c2953fc405330ee10000000a114084/frameset.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/43/64db4daf9f30b4e10000000a11466f/content.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/14/ef2940cbf2195de10000000a1550b0/frameset.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/fc/5ad93f130f9215e10000000a155106/frameset.htm
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/d23cbe11-0d01-0010-5287-873a22024f79
    http://help.sap.com/saphelp_nw04/helpdata/en/f1/2de3be0382df45a398d3f9fb86a36a/frameset.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/65/6a563cef658a06e10000000a11405a/content.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/f1/2de3be0382df45a398d3f9fb86a36a
    cheers
    Edited by: vemuganti naga phalguna on Jul 24, 2008 12:16 PM

  • Http,idoc adapter

    if we choose the adapter type as idoc,http the channel direction defaults to receiver why?

    Hi Narendra,
    The plain HTTP adapter is generally  used by external systems to connect to the Integration Engine using the native HTTP interface (HTTP payload without SOAP envelope),which is why its default comm channel is receiver
    Also ,a communication channel with a receiver HTTP adapter can be created automatically for business systems that are defined in the System Landscape Directory
    check this http://help.sap.com/saphelp_nw04/helpdata/en/43/64dbb0af9f30b4e10000000a11466f/frameset.htm

  • HTTP sender

    Hi Folks,
       From an external non-sap server I have to send an XML to SAP. I'm using the HTTP adapter as the sender adapter, Please let me know the mechanism how the HTTP sender adapter gets the data from the external server which has to be transmitted. I have to expalin this thing to the client its very urgesnt... Pls help.
    Regards,
       Santosh....

    The plain HTTP adapter gives application systems the option of communicating with the Integration Engine and exchanging business data using a plain HTTP connection.
    The plain HTTP adapter is used by external systems to connect to the Integration Engine using the native HTTP interface (HTTP payload without SOAP envelope). These systems are connected using the Internet communication framework of the SAP Web Application Server. For this purpose, the Integration Engine HTTP inbound channel contains an HTTP service delivered by SAP, called /sap/xi/adapter_plain.
    refer the links that I have given in my previous reply.

  • Sending IDocs to WebAS http port

    Hi,
    Are there any .NET code examples on sending an IDoc to Web AS http port? Is this a simple TCP/IP socket level call? Are there any hand-shaking messages? Does it use http payload (GET, POST)?
    Thank you in advance for your help.
    Pradeep

    Hai ramesh,
                        I am configuring the XML HTTP port and here there is no option telling to define the file path name.
    And its work fine on the local network as the same system with same configuration is put on the public IP .the SAP server is sending idocs but it  is not received in the Webserver side.
    Data is lost somewhere in the middle on the netwrok.
    Thanks,
    jeevan.

  • Error with HTTP binding - 11g

    Hi all ,
    I am getting below error while calling existing RESTful webservice from BPEL SOA composite, using HTTP Binding:
    *“null schema location for ns=null [Cause=null schema location for ns=null] at oracle.sysman.emas.model.wsmgt.WSTestModel.invokeOperation(WSTestModel.java:575)”*
    WSDL file for HTTP service is
    <?xml version="1.0" encoding="UTF-8"?>
    <wsdl:definitions name="CASPaymentService"
    targetNamespace="http://xmlns.oracle.com/pcbpel/adapter/http/HelloWorldServlet/CSGetPaymentProvABCS/CASPaymentService"
    xmlns:tns="http://xmlns.oracle.com/pcbpel/adapter/http/HelloWorldServlet/CSGetPaymentProvABCS/CASPaymentService"
    xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
    xmlns:plt="http://schemas.xmlsoap.org/ws/2003/05/partner-link/"
    xmlns:xsd="http://www.w3.org/2001/XMLSchema">
    <plt:partnerLinkType name="Request_Response_plt">
    <plt:role name="Request-Response_role">
    <plt:portType name="tns:Request_Response_ptt"/>
    </plt:role>
    </plt:partnerLinkType>
    <wsdl:types>
    *<schema xmlns="http://www.w3.org/2001/XMLSchema">*
    *<include schemaLocation="xsd/InputOutputFault.xsd"/>*
    *</schema>*
    </wsdl:types>
    *<wsdl:message name="envelope_msg_in">*
    *<wsdl:part name="input" element="envelope"/>*
    *</wsdl:message>*
    *<wsdl:message name="envelope_msg_out">*
    *<wsdl:part name="envelope" element="envelope"/>*
    *</wsdl:message>*
    <wsdl:portType name="Request_Response_ptt">
    <wsdl:operation name="Request-Response">
    <wsdl:input message="tns:envelope_msg_in"/>
    <wsdl:output message="tns:envelope_msg_out"/>
    </wsdl:operation>
    </wsdl:portType>
    </wsdl:definitions>
    Input schema  ( InputOutputFault.xsd) is like below: Please note it has no namespace
    <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema">
    <xsd:element name="envelope">
    </xsd:element>
    </xsd:schema>
    binding in composite.xml is :
    <reference name="GetPaymentCAS" ui:wsdlLocation="GetPaymentCAS.wsdl">
    <interface.wsdl interface="http://xmlns.oracle.com/pcbpel/adapter/http/HelloWorldServlet/GetPaymentCASServiceCall/GetPaymentCAS#wsdl.interface(Request_Response_ptt)"/>
    <binding.ws port="http://xmlns.oracle.com/pcbpel/adapter/http/HelloWorldServlet/GetPaymentCASServiceCall/GetPaymentCAS#wsdl.endpoint(GetPaymentCAS/Request_Response_pt)"
    location="GetPaymentCAS.wsdl" supports="http">
    <property name="http.verb" type="xs:string" many="false">POST</property>
    <property name="endpointURI" type="xs:string" many="false">http://testaia:9111/CAS/servlets/PaymentServicesServlet</property>
    <property name="http.payload" type="xs:string" many="false">xml</property>
    </binding.ws>
    </reference>
    It seems like HTTP binding in 11g works with XSD with some namespace only. And if we provide the schema details in either <wsdl:types> or via “including schema in wsdl” as shown above, at runtime it still try to look for schema file.
    Any workaround/solution for same is highly appreciated.
    Thanks & Regards
    Pintoo

    hi,
    I depolyd my ProvideABCS into EM here i ubable to invoke the serveses i get below error
    webservices invoikesfail:
    The selected operation ProcessEcoproduct could not be invoked.
    An exception occured while invoking the webservice operation. Please see logs for more details.
    oracle.sysman.emSDK.webservices.wsdlapi.SoapTestException: Client received SOAP Fault from server : oracle.fabric.common.FabricInvocationException: java.lang.NullPointerException
    addtionalinfo:
    java.lang.Exception: oracle.sysman.emSDK.webservices.wsdlapi.SoapTestException: Client received SOAP Fault from server : oracle.fabric.common.FabricInvocationException: java.lang.NullPointerException at oracle.sysman.emas.model.wsmgt.WSTestModel.invokeOperation(WSTestModel.java:808) at oracle.sysman.emas.view.wsmgt.WSView.invokeOperation(WSView.java:384) at oracle.sysman.emas.view.wsmgt.WSView.invokeOperation(WSView.java:301) 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:597) at com.sun.el.parser.AstValue.invoke(Unknown Source) at com.sun.el.MethodExpressionImpl.invoke(Unknown Source) at org.apache.myfaces.trinidadinternal.taglib.util.MethodExpressionMethodBinding.invoke(MethodExpressionMethodBinding.java:53) at org.apache.myfaces.trinidad.component.UIXComponentBase.broadcastToMethodBinding(UIXComponentBase.java:1256) at org.apache.myfaces.trinidad.component.UIXCommand.broadcast(UIXCommand.java:183) at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent$1.run(ContextSwitchingComponent.java:92) at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent._processPhase(ContextSwitchingComponent.java:361) at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent.broadcast(ContextSwitchingComponent.java:96) at oracle.adf.view.rich.component.fragment.UIXInclude.broadcast(UIXInclude.java:102) at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent$1.run(ContextSwitchingComponent.java:92) at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent._processPhase(ContextSwitchingComponent.java:361) at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent.broadcast(ContextSwitchingComponent.java:96) at oracle.adf.view.rich.component.fragment.UIXInclude.broadcast(UIXInclude.java:96) at javax.faces.component.UIViewRoot.broadcastEvents(UIViewRoot.java:475) at javax.faces.component.UIViewRoot.processApplication(UIViewRoot.java:756) at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl._invokeApplication(LifecycleImpl.java:889) at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl._executePhase(LifecycleImpl.java:379) at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:194) at javax.faces.webapp.FacesServlet.service(FacesServlet.java:265) at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227) at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125) at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:300) at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.sysman.emSDK.license.LicenseFilter.doFilter(LicenseFilter.java:101) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.adf.model.servlet.ADFBindingFilter.doFilter(ADFBindingFilter.java:205) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.adfinternal.view.faces.webapp.rich.RegistrationFilter.doFilter(RegistrationFilter.java:106) at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl$FilterListChain.doFilter(TrinidadFilterImpl.java:446) at oracle.adfinternal.view.faces.activedata.AdsFilter.doFilter(AdsFilter.java:60) at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl$FilterListChain.doFilter(TrinidadFilterImpl.java:446) at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl._doFilterImpl(TrinidadFilterImpl.java:271) at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl.doFilter(TrinidadFilterImpl.java:177) at org.apache.myfaces.trinidad.webapp.TrinidadFilter.doFilter(TrinidadFilter.java:92) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.help.web.rich.OHWFilter.doFilter(Unknown Source) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.sysman.emas.fwk.MASConnectionFilter.doFilter(MASConnectionFilter.java:41) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.adf.library.webapp.LibraryFilter.doFilter(LibraryFilter.java:179) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.sysman.eml.app.AuditServletFilter.doFilter(AuditServletFilter.java:179) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.sysman.eml.app.EMRepLoginFilter.doFilter(EMRepLoginFilter.java:203) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.sysman.core.model.targetauth.EMLangPrefFilter.doFilter(EMLangPrefFilter.java:158) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.sysman.core.app.perf.PerfFilter.doFilter(PerfFilter.java:141) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.sysman.eml.app.ContextInitFilter.doFilter(ContextInitFilter.java:542) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:119) at java.security.AccessController.doPrivileged(Native Method) at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:315) at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:442) at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:103) at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:171) at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.dms.servlet.DMSServletFilter.doFilter(DMSServletFilter.java:139) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:27) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3715) at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3681) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321) at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120) at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2277) at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2183) at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1454) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209) at weblogic.work.ExecuteThread.run(ExecuteThread.java:178) Caused by: oracle.sysman.emSDK.webservices.wsdlapi.SoapTestException: Client received SOAP Fault from server : oracle.fabric.common.FabricInvocationException: java.lang.NullPointerException at oracle.sysman.emSDK.webservices.wsdlapi.dispatch.DispatchUtil.invoke(DispatchUtil.java:362) at oracle.sysman.emSDK.webservices.wsdlparser.OperationInfoImpl.invokeWithDispatch(OperationInfoImpl.java:1004) at oracle.sysman.emas.model.wsmgt.PortName.invokeOperation(PortName.java:750) at oracle.sysman.emas.model.wsmgt.WSTestModel.invokeOperation(WSTestModel.java:802) ... 79 more Caused by: oracle.j2ee.ws.client.jaxws.JRFSOAPFaultException: Client received SOAP Fault from server : oracle.fabric.common.FabricInvocationException: java.lang.NullPointerException at oracle.j2ee.ws.client.jaxws.DispatchImpl.throwJAXWSSoapFaultException(DispatchImpl.java:1040) at oracle.j2ee.ws.client.jaxws.DispatchImpl.invoke(DispatchImpl.java:826) at oracle.j2ee.ws.client.jaxws.OracleDispatchImpl.synchronousInvocationWithRetry(OracleDispatchImpl.java:235) at oracle.j2ee.ws.client.jaxws.OracleDispatchImpl.invoke(OracleDispatchImpl.java:106) at oracle.sysman.emSDK.webservices.wsdlapi.dispatch.DispatchUtil.invoke(DispatchUtil.java:358) ... 82 more
    please help on it

  • HTTPS To Retrieve Data

    I have a request to use HTTPS to access a url and "pull" data into our XI instance. I have used HTTP to "push" data to a client url but not to "pull" data. Is this possible and if possible, can a schedule be included in the communication channel to access the client site at a set time period. The client is requesting that we use HTTPS and not FTP.

    >
    Robert Smith wrote:
    > I have a request to use HTTPS to access a url and "pull" data into our XI instance. I have used HTTP to "push" data to a client url but not to "pull" data. Is this possible and if possible, can a schedule be included in the communication channel to access the client site at a set time period. The client is requesting that we use HTTPS and not FTP.
    yes it is possible via the http adapter but scheduling might get tricky.
    I suggest you move to the soap adapter and use the option do not use soap envelop to simulate an HTTP payload. Also using the adapter scheduling you can schedule for the adpater to poll only during specific time.
    /people/shabarish.vijayakumar/blog/2006/11/26/adapter-scheduling--hail-sp-19-

  • About HTTP sync scenario

    Hi all
    It could be a silly question but as we do not use sender agreement in HTTP sender then how do the external system who wants to communicate synch. with XI-PI system know which interface to use .
    and how can we tell XI that this specific http request has to go to RFC or PROXY for exmaple.
    best regards.

    The plain HTTP adapter enables you to receive and send business data from and to external systems, using the plain HTTP inbound/outbound channels of the Integration Engine.
    The standard exchange format for data in the Integration Engine is XML. However, using the plain HTTP adapter you can also send and receive data in HTML and ASCII. In this case you must use a Java mapping.
    Prerequisites
    The HTTP service /sap/xi/adapter_plain supplied by SAP must be assigned to the client in which you run the Integration Engine.
    Process Flow
    An HTTP client sends business documents to the Integration Engine using HTTP. A message is generated from the business document and transferred to the Integration Engine. If, on the other hand, the Integration Engine identifies a plain HTTP receiver, a business document is generated from the message and sent to the receiver. This communication is either synchronous (the client awaits a response to its HTTP request) or asynchronous.
    Integration Engine: HTTP Inbound Channel
    The Integration Engine is called by external systems using HTTP and an HTTP address. For this purpose, the HTTP inbound channel of the Integration Engine contains the HTTP service /sap/xi/adapter_plain, delivered by SAP.
    The class CL_HTTP_PLAIN_INBOUND is provided as a request handler that processes an HTTP request synchronously (client awaits a response) or asynchronously.
    Multi-part documents and HTTP requests with an empty HTTP body are not accepted and receive a response with status code 500 or 204.
    The obligatory parameters of the HTTP address are analyzed and used to construct the message.
    Mandatory Parameters
    Parameter
    Meaning
    service
    Sender service for identifying the sender
    In XI message protocol 2.0, this parameter corresponds to the parameter bs.
    namespace
    Namespace of the sender interface
    interface
    Interface of the HTTP payload
    http://sap-ag.com:8088/sap/xi/adapter_plain?service=sender&namespace=urn%3Asap-ag%2Ecom&interface=%2Fsap%2Forders
    You must code special characters such as forward slash (/), hyphen , period (.), or colon ( with escape characters (for example, %2F for /, %2D for -, %2E for .,and %3A for :).
    The optional parameters of the HTTP address are also analyzed. They affect the runtime response of the message in the Integration Engine.
    Optional Parameters
    Parameter
    Meaning
    party
    Sender party (XI 3.0 only)
    agency
    Issuing agency of the sender (XI 3.0 only)
    scheme
    Identification scheme of the sender (XI 3.0 only)
    qos
    Quality of service of the message:
    Synchronous (BE) or asynchronous (EO, EOIO) processing; the default setting is synchronous processing.
    queueid
    Queue name in EOIO processing (XI 3.0 only)
    msgguid
    32 character message ID; uniquely identifies a message in the Integration Engine. If no message ID is specified, the system generates one internally.
    http://sap-ag.com:8088/sap/xi/adapter_plain?service=sender&namespace=urn%3Asap-ag%2Ecom&interface=%2Fsap%2Forders&qos=EO&msgguid=3C61F6C12F1E2DD1E10000000A1145AB
    You must code special characters such as forward slash (/), hyphen , period (.), or colon ( with escape characters (for example, %2F for /, %2D for -, %2E for .,and %3A for :).
    Optional HTTP header fields are ignored. The payload in the HTTP body is appended to the message as a binary document. The payload must be sent as an XML document with code page UTF-8, so that all services of the Exchange Infrastructure can process the document.
    The instantiated message is transferred to the Integration Engine. In mode BE (synchronous processing) the system waits for the response from the Integration Engine. If processing is successful, the payload of the message is sent as an HTTP response. If not, the system returns an error.
    If processing is successful, the HTTP client has the return code 200. Otherwise, it has the return code 500, or 409. If an error occurs, the error object of the message contains an error message. In the synchronous case, this is placed in the HTTP body of the HTTP response; in the asynchronous case, it is given as the error cause to the HTTP request.
    HTTP Outbound Channel of the Integration Engine (Receiver HTTP Adapter)
    The Integration Engine calls the plain HTTP adapter if technical routing identifies a communication channel for the logical receiver. This communication channel originates from the Integration Directory. It is analyzed and provides the technical information for the HTTP request.
    The main payload of the message is sent as HTTP post to an HTTP address. The technical data for the HTTP post is determined from the communication channel parameters.
    A HTTP client is instantiated for a logical destination, in which the following data are maintained:
    ·        HTTP address
    ·        HTTP proxy data
    ·        Authentication settings
    ·        Security data
    If no destination is specified, the system instantiates an HTTP client using the specified HTTP address and the proxy data. A basic authentication is entered in the HTTP header fields with a user and password in BASE64 code.
    The optional header fields maintained in the communication channel parameters are set in the HTTP header.
    The header fields Content Type (if not already explicitly set), Content Length, and the host are set by default.
    In the HTTP address, the sender party is set as the parameters party, agency, and scheme, the sender service is set as the parameter service, and the interface used is set as the parameters namespace and interface. Depending on the current quality of service (qos) of the message, the parameter qos is also added to the HTTP address. If the quality of service is EOIO, a queue name is also required in the parameter queueid.
    The HTTP body comprises the prolog, message payload, and epilog. The prolog and epilog are optional and enhance the payload for particular servers (for example, CGI servers). If the payload is to be sent as an HTML form using HTTP post, it is URL-escaped beforehand.
    If the specified code page for the HTTP body does not correspond to the default setting UTF 8, the system converts the HTTP body to the corresponding code page; in the XML document, the system replaces the tag encoding=UTF-8 with the corresponding code page tag.
    If the quality of service is set to Best Effort, the system awaits a response from the HTTP server. The system appends this response to the message as a new main payload (with the content type, if necessary), while it deletes the old main payload.
    The system logs any errors that occur in the message.

  • Error when calling simple restful service from SOA 11G

    Hi'
    I have a URL for simple restful service
    http://xxxxx:857/swift/v2/EMPIDChanges/{bookmarkDate}
    GET method
    I am able to invoke this from IE and This URL is also accessible in UNIX server where SOA server is deployed.
    http://xxxxx:857/swift/v2/EMPIDChanges/2012-11-28%2005:57:49
    I am using HTTP Binding adapter,
    This is what goes in the composite.xml
    <reference name="ff" ui:wsdlLocation="ff.wsdl">
    <interface.wsdl interface="http://xmlns.oracle.com/pcbpel/adapter/http/AssetID/Test_AssetID_VL/ff#wsdl.interface(Request_Response_ptt)"/>
    <binding.ws port="http://xmlns.oracle.com/pcbpel/adapter/http/AssetID/Test_AssetID_VL/ff#wsdl.endpoint(ff/Request_Response_pt)"
    location="ff.wsdl" supports="http">
    <property name="http.verb" type="xs:string" many="false">GET</property>
    <property name="endpointURI" type="xs:string" many="false">http://xxxxx:857/swift/v2/EMPIDChanges/{bookmarkDate}</property>
    <property name="http.payload" type="xs:string" many="false">url-encoded</property>
    <property name="oracle.webservices.auth.username" type="xs:string" many="false" override="may">Test1</property>
    <property name="oracle.webservices.auth.password" type="xs:string" many="false" override="may">Test1</property>
    </binding.ws>
    however I am getting error
    <remoteFault xmlns="http://schemas.oracle.com/bpel/extension">
    -<part name="summary">
    <summary>oracle.fabric.common.FabricInvocationException: Unable to access the following endpoint(s): REPLACE_WITH_ACTUAL_URL</summary>
    </part>
    -<part name="detail">
    <detail>Unable to access the following endpoint(s): REPLACE_WITH_ACTUAL_URL</detail>
    </part>
    -<part name="code">
    <code>null</code>
    </reference>
    Please advice,
    Thanks,
    Yatan

    WS Binding: exception durign SOAP invocation: java.util.NoSuchElementException
    Looks like the error is in the data sent to or expected from the service in your composite. Check that audit logs and composite flow to make sure your soap message when using soapui matches what you are working with in soa suite.

Maybe you are looking for