Content-Length missing in SOAP request

In Oracle Application Server, a SOAP request like :
POST /eai_esn/start.swe?SWEExtSource=WebService&SWEExtCmd=Execute&WSSoap=1 HTTP/1.1
SOAPAction: "document/http://siebel.com/marketing/import:MktgImportServiceInvokeImportJob"
User-Agent: Axis2
Host: 192.168.49.66:8093
Transfer-Encoding: chunked
Content-Type: text/xml; charset=UTF-8
a28
<?xml version='1.0' encoding='UTF-8'?>. . . . </soapenv:Envelope>
0
is rejected with an error like : "Missing body length ..."
However , a SOAP request like :
Content-Type: text/xml;charset=UTF-8
SOAPAction: "document/http://siebel.com/marketing/import:MktgImportServiceInvokeImportJob"
User-Agent: Jakarta Commons-HttpClient/3.1
Host: 192.168.49.58:8093
Content-Length: 2602
<?xml ...... >
is accepted with no error .
Using Microsoft IIS, the first SOAP request without the 'Content-Length' is accepted just fine.
It looks like OAS requires SOAP header to have a "Content-Length" . Is this correct ? Is there a way to change this behavior ?
Thank you
Gabriel Gonzalez

Hi,
The web service we are trying to communicate with is a third-party service that we have no control over. This service requires the name of the attribute to be in the content id field.
See section 3.8 of the following link
http://www.ws-i.org/Profiles/AttachmentsProfile-1.0-2004-08-24.html
I seem to be able to set the name, description, contentType in the SOAP adapter module I have written - but I cannot set the content-Id.
Regards,
Bryan

Similar Messages

  • Content-length in HTTP Post request

    Hi all,
    I have a problem with a Http request. I send data in a POST to a servlet, but the KVM doesn't set the Content-Length correctly. How can I do ?
    The code :
    conn = (HttpConnection) Connector.open(m_strServer);
    conn.setRequestMethod(HttpConnection.POST);
    conn.setRequestProperty("Content-Type", "application/x-www-form-urlencoded");
    String requestData = "from=" + m_strOriginator + "&to=" + m_strDestinator + "&message=" + m_strMessage;
    out = conn.openDataOutputStream();
    out.write(requestData.getBytes());
    out.flush();
    in = conn.openDataInputStream();
    if (conn.getResponseCode() == 200)
         response = true;the request sended :
    POST /my_directory/test.xml HTTP/1.1
    Content-Type: application/x-www-form-urlencoded
    Transfer-Encoding: chunked
    Host: my_pc
    15
    from=8&to=9&message=J
    0
    I think that the KVM doesn't put "Content-Length:" before "15".
    Perhaps it's a bug.
    St�phane

    Maby u try to force it with:
    conn.setRequestProperty ( "Content-Length" ,
                   Integer.toString (requestData.getBytes()));
    for me it does also not work...but u never know
    lemme know if it works
    Fabian

  • HELP content  length always -1!!!!!

    Im developing a MIDlet to upload data to a servlet but my content length is always -1
    here is my code
    HttpConnection c = null;
        InputStream is = null;
        DataOutputStream dos = null;
        OutputStream os = null;
    try
           c = (HttpConnection)Connector.open(url2, Connector.READ_WRITE, true);
        c.setRequestMethod(HttpConnection.POST);
       c.setRequestProperty("IF-Modified-Since", "20 Jan 2001 16:19:14 GMT");
       c.setRequestProperty("User-Agent", "Profile/MIDP-2.0 Configuration/CLDC-1.0");
       c.setRequestProperty("Content-type", "multipart/form-data; " );
        c.setRequestProperty("Connection", "close" );
        c.setRequestProperty("Content-Length",Long.toString( size ) );
               dos = new DataOutputStream(c.openDataOutputStream());
        dos.writeLong(size);  
        dos.write(photo);  
        dos.flush();  
        dos.close();
        finally
          if(is!= null) {
            is.close();
          if(os != null) {
            dos.close();
          if(c != null) {
            c.close();
          }what am I doing wrong
    Thanks in advance!!

    It depends on what implementation you are running on, but WTK 2.2, for example, always seem to use the chunked transfer encoding when doing a POST and there is no Content-Length header in the request headers, and if the server reply is also sent using the chunked transfer encoding there will be no Content-Length header in the reply headers either
    regards
    simon

  • Missing Content-Length in HTTP response

    Hi All,
    I am experimenting with developing websevices using Sun Java Application Server. I have a working webservice using BEA Weblogic and I would like to have it ported to SUN. The application works like this: A client (Tuxedo application program) sends an XML document to the webservice, in response the websevice parse this document and based on certain fields it send back another document.
    The problem is that the SUN application does not return the content-length in its response and hence the requesting client rejects the message. Can anyone help?? Below is the response from both SUN and Weblogic:
    Weblogic
    HTTP/1.1 200 OK
    Date: Sat, 22 Oct 2005 11:42:53 GMT
    Pragma: no-cache
    Server: WebLogic Server 8.1 SP2 Fri Dec 5 15:01:51 PST 2003 316284 WebLogic Server 8.1 SP2 Fri Dec 5 15:01:51 PST 2003 316284 WebLogic Server 8.1 SP2 Fri Dec 5 15:01:51 PST 2003 316284 with CR174524
    Content-Length: 2025
    Content-Type: text/xml; charset=UTF-8
    Expires: Thur, 01 Jan 1970 00:00:00 GMT
    Cache-Control: no-cache
    Connection: Close
    <?xml version="1.0" encoding="utf-8"?>
    <SOAP-ENV:Envelope
    SUN
    HTTP /1.1 200 OK
    X-Powered-By: Servlet/2.4
    SOAPAction: ""
    Content-Type: text/xml;charset=utf-8
    Date: Sat, 22 Oct 2005 11:42:53 GMT
    Server: Sun-Java-System/Application-Server
    Connection: close
    <?xml version="1.0" encoding="UTF-8"?>
    env:Envalope xmls:env="http://schemas.xmlsoap.org/soap/envelope/"
    As can be seen the Content-Length is missing.
    Thanks for your help.
    Ransford

    Is there an option in Sun Java Application Server to include Content-Length in response to a client request? If not is it possible to generate this information from the service code?
    Thanks.

  • HTTP PUT Request for File Uploads is returning a response header with content-length = 0

    After upgrading from CF9 to Coldfusion 10, I'm running into an odd issue, with `cURL` calls to a webservice that used to work.
    We are using an HTTP PUT Request with multipart="no" so that the request header content is the file itself, now the data is being sent properly in the content but it has a ~8k limit. This is fine for smaller files but some files are 60kb etc.
    Errors are odd too, near the 8KB limit we get a bad gateway error 502, and above that the webpage errors with a connection reset.
    It works fine with multipart="yes", but in a PUT request the file's data isn't even sent since it's looking for `httpparam formField` , the content-length from the target page's Headers show a content-length of 0 which causes `cURL` to fail with an error (56): http://curl.haxx.se/docs/manpage.html
    Here's example code to reproduce:
    <cfset sFilename = "C:\999\test4.txt">
    <cffile action="readBinary" file="#sFilename#" variable="fileRead">
    <cfset oFileInfo = GetFileInfo("#sFilename#")>
    <cfhttp           url="localhost/Clarence/diff_elt_test_output.cfm"
                                  method="PUT"
                                  username="******"
                                  password="******"
                                  multipart="yes"
                                  result="oHttp">
              <cfhttpparam type="header" name="Content-Type" value="text/plain" />
              <cfhttpparam type="header" name="Content-Length" value="#oFileInfo.Size#" />
              <cfhttpparam type="body" value="#fileRead#"/>
    </cfhttp>
    <cfdump var="#oHttp#">
    Dumping the response via GetHttpRequestData() shows that the header's content-length = 0 and content is blank.
    Whereas POST requests work fine, cURL has a -F form option which is our fallback but a solution to this would be great.
    Here's what I've tried:
    1. Changing CF post request limit sizes (64MB+)
    2. Changing IIS config web/webserver http runtime and security.request filtering request limits to much higher values
    3. AJP Connector between IIS and Tomcat has a default 8KB header limit, I changed that to 64k on both sides, still nothing
    Also am I missing something fundamental here? I thought at the network layer a packet is split up and rejoined, so large content in a http request body should work, what's wrong with Coldfusion 10?

    I am familiar with java.net package and know how to
    Read and Write Streams.
    However, what I do not know is what string
    represntation of PUT or POST resquests is?It's HttpURLConnection.setRequestMethod("PUT") or ("POST").
    Also you have to setDoOutput(true).
    Then you set the content type, possibly encode the input, set the content length, and write the file data to the stream.
    Using a Jakarta package may be easier, however.

  • PO 7.4: NW BPM: HTTP Error response for SOAP request or invalid content-type.HTTP 200 OK

    Hi Experts
    I am trying to call NW BPM scenario(File to BPM) from PI, and using below adapter config.
    I am getting below error.
    Failed to call the endpoint: Error in call over HTTP: HTTP 200 OK
    SOAP: Call failed: java.io.IOException: HTTP Error response for SOAP request or invalid content-type.; HTTP 200 OK
    SOAP: Error occurred: com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.io.IOException: HTTP Error response for SOAP request or invalid content-type.; HTTP 200 OK
    MP: exception caught with cause com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.io.IOException: HTTP Error response for SOAP request or invalid content-type.; HTTP 200 OK
    Transmitting the message to endpoint <local> using connection File_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.io.IOException: HTTP Error response for SOAP request or invalid content-type.; HTTP 200 OK
    Any idea how to fix this issue?
    Thanks,
    Sandeep Maurya.

    Hi Sandeep,
    Test the URL from your browser and check the proxy settings as well.
    Refer the below links
    SOAP: call failed: java.io.IOException: invalid content type for SOAP: TEXT
    SOAP: Call failed: java.io.IOException: Failed to get the input stream from socket: java.net.SocketException: Connection…
    Regards
    Bhargava Krishna

  • OSB - Content length http header missing from business service out message

    Hi all,
    I am having some diffuclty with a business service in OSB. I created the business service from the wsdl and created a regular proxy service that just routes to the business service. When i run the test console i get the below fault.
    <faultcode>soapenv:Server</faultcode>
    <faultstring>BEA-380000: Length Required</faultstring>
    <detail>
    After some debugging i find that the content length http header is missing from the outbound message the business process creates and sends to the acutal web service which sends back the http 411 fault.
    Does anyone know how to configure the message flow of my proxy service to ensure that the outbound message sent from the business service contains that content length http header or any suggestions on how to fix this issue will be appreciated.
    Thanks

    Disable the "Use Chunked Streaming Mode" property in HTTP Transport Configuration of your business service. By default it remains enabled.
    Regards,
    Anuj

  • Content-Length Header Missing in Http Response

    Hi folks,
    Our application uses JSPs and Servlets. To solve a TCP level probelm, we would like to ensure that each response sent from the WebLogic Server includes a content-length header. All the pages are dynamic and therefore we cannot explicitly set the content-length.
    To ensure that WebLogic has the opportunity to set this header, we have increased the response buffer size by adding a <%@ page buffer="nK" %> header to our JSPs and a response.setBufferSize call to our Servlets. The responses still do not contain a content-length header.
    Is there anything else we can do to get WebLogic to set this header?
    Thanks in advance,
    Santosh

    Anybody?

  • Safri browser 3.1.2 SOAP Request HTTP 400 Error

    Hi,
    I have a simple html making ajax calls (XMLHttpRequest) to our webservice on a button click. The code works fine with major browsers like FireFox, IE and Opera. But if i load the html in Safari and send the SOAP request to the webservice using XMLHttpRequest, i get an HTTP 400 - Bad Request Error from the server.
    Why is it failing just for the safari browser? Do i need to set any extra HTTP headers? When i see the WireShark captured packets for Firefox and Safari, i see the content length is different. And also Safari is missing a lot of headers.
    Could you please help troubleshoot the issue?
    PS: The webserver is running IIS 6.0 on windows server 2003.
    regards
    srividhya

    I'm not sure how to help you. No link found.
    Try this to see how Safari performs XMLHttpRequests:
    http://www.mnot.net/javascript/xmlhttprequest/
    Every browser is different...

  • Error with SOAP Request to calendar web service

    Hi
    I'm sending the following SOAP request to a calendar web service to create an appointment in the calendar. The response returns what seems to be a syntax error ("The Create method did not have a proper element in the request") but I can't see the cause of the fault. Any suggestions on what it may be? It's an 11g DB.
    Many thanks
    -x-POST-x-
    POST /ocws-bin/ocas.fcgi HTTP/1.0
    Content-Type: text/xml; charset="utf-8"
    Content-Length: 993
    SOAPAction: SOAPAction: "http://www.oracle.com/WebServices/Calendaring/1.0/Create"
    Connection: close
    <SOAP-ENV:Envelope
    xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
    <SOAP-ENV:Header><auth:BasicAuth xmlns:auth="http://soap-authentication.org/2002/01/">
    <Name>CalendarName</Name><Password>CalendarPassword</Password>
    </auth:BasicAuth> </SOAP-ENV:Header>
    <SOAP-ENV:Body><cwsl:Create xmlns:cwsl="http://www.oracle.com/WebServices/Calendaring/1.0/"><CmdId>ITS APPOINTMENT</CmdId><iCalendar>
    <vcalendar prodid="-//Oracle//Calendaring//Calendarlet//EN" version="2.0">
    <vevent><class>PUBLIC</class>
    <description>Calendar Body</description>
    <dtstart value="DATE-TIME">20102905T120000</dtstart>
    <duration>P00DT0H30M00S</duration>
    <location>Location of user</location>
    <summary>Incident ID - (name of user])</summary>
    <uid>XGjRVnpReQALNsILlBlvcyXGCoUyXF</uid>
    <x-oracle-eventtype>APPOINTMENT</x-oracle-eventtype>
    <priority>5</priority>
    </vevent>
    </vcalendar>
    </iCalendar></cwsl:Create></SOAP-ENV:Body></SOAP-ENV:Envelope>
    -x-RESPONSE-x-
    HTTP/1.1 500 Internal Server Error
    Date: Thu, 27 May 2010 08:22:16 GMT
    Server: Apache/2.2.4 (Unix) mod_ssl/2.2.4 OpenSSL/0.9.7a mod_fastcgi/2.4.6
    OCAS-ProcTime: 407
    Connection: close
    Content-Type: text/xml; charset=utf-8
    <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" soap:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
    <soap:Body>
    <soap:Fault>
    <faultcode>soap:Server.Error::System::SOAPRequest</faultcode>
    <faultstring>The Create method did not have a proper element in the request</faultstring>
    <detail>
    <cwsl:Error xmlns:cwsl="http://www.oracle.com/WebServices/Calendaring/1.0/">
    <Class>Error::System::SOAPRequest</Class>
    <Code>0020-00-00-00000034</Code>
    <Line>3180</Line>
    <FileName>SOAPRequestHandler.cpp,v</FileName>
    <Version>1.57</Version>
    <LastMod>2007/05/30 21:13:25</LastMod>
    <Author>pscattol</Author>
    <Date>Thu May 27 09:22:16 2010</Date>
    <PID>26152</PID>
    <TID>3044838304</TID>
    <Level>Error</Level>
    </cwsl:Error>
    </detail>
    </soap:Fault>
    </soap:Body>
    </soap:Envelope>

    Hi,
    I am having problem using dii client, while sending a
    request to c# webservice. error follows
    QName QNAME_TYPE_STRING = new QName(NS_XSD,
    "string");
    call.setReturnType(QNAME_TYPE_STRING);
    call.setOperationName(new QName(BODY_NAMESPACE_VALUE,
    "GetDetails"));
    call.addParameter("String_1", QNAME_TYPE_STRING,
    ParameterMode.IN);Do you need another call to addParameter here?
    String[] params = { "02", "2004" };
    String result = (String)call.invoke(params);

  • Call web service (multipart MIME soap request) using pl/sql (utl_http)

    I've the following header and http request.
    POST http://deab/DexNETWebServices_4_0_0_4/LoginService.svc HTTP/1.1
    MIME-Version: 1.0
    Content-Type: multipart/related; type="application/xop+xml";start="<http://tempuri.org/0>";boundary="uuid:e4c19840-745d-45b2-90ca-12d71be4cfd9+id=1";start-info="application/soap+xml"
    VsDebuggerCausalityData: uIDPo5F/qXRc4YJImqB6Ard30cQAAAAAAjIXinpIVUulXLJOsSG7yyv7Lf2yHgpHlIxvc6oeqaAACQAA
    Host: deab
    Content-Length: 1017
    Expect: 100-continue
    Accept-Encoding: gzip, deflate
    Connection: Keep-Alive
    --uuid:e4c19840-745d-45b2-90ca-12d71be4cfd9+id=1
    Content-ID: <http://tempuri.org/0>
    Content-Transfer-Encoding: 8bit
    Content-Type: application/xop+xml;charset=utf-8;type="application/soap+xml"
    <s:Envelope xmlns:s="http://www.w3.org/2003/05/soap-envelope" xmlns:a="http://www.w3.org/2005/08/addressing"><s:Header><a:Action s:mustUnderstand="1">http://tempuri.org/ILoginService/LoginByUserName</a:Action><a:MessageID>urn:uuid:cf410a05-23d4-4b92-a22c-329cbc19fbe7</a:MessageID><a:ReplyTo><a:Address>http://www.w3.org/2005/08/addressing/anonymous</a:Address></a:ReplyTo><a:To s:mustUnderstand="1">http://deab/DexNETWebServices_4_0_0_4/LoginService.svc</a:To></s:Header><s:Body><LoginByUserName xmlns="http://tempuri.org/"><systemId>19e0ddb4-5fa5-41ee-b624-aea762865a6c</systemId><strName>FirmwareUpdateLogQueryWorker</strName><productId>0af39a3e-6549-485b-872f-b73413203998</productId><password>abc</password></LoginByUserName></s:Body></s:Envelope>
    --uuid:e4c19840-745d-45b2-90ca-12d71be4cfd9+id=1--
    I'm using the following code to set the header from PL/SQL and call the request. But UTL_HTTP.get_response returns the error 400 Bad Request.
    DECLARE
       l_request         CLOB;
       l_http_req        UTL_HTTP.req;
       l_http_resp       UTL_HTTP.resp;
       v_buffer          VARCHAR2 (32767);
       p_status_code     NUMBER (9);
       p_error_message   VARCHAR2 (32767);
       p_response        CLOB;
    BEGIN
      l_request :=
                '--uuid:e4c19840-745d-45b2-90ca-12d71be4cfd9+id=1'
             || CHR (13)
             || 'Content-ID: <http://tempuri.org/0>'
             || CHR (13)
             || 'Content-Transfer-Encoding: 8bit'
             || CHR (13)
             || 'Content-Type: application/xop+xml;charset=utf-8;type="application/soap+xml"'
             || CHR (13)
             || CHR (13)
             || '<s:Envelope xmlns:s="http://www.w3.org/2003/05/soap-envelope" xmlns:a="http://www.w3.org/2005/08/addressing"><s:Header><a:Action s:mustUnderstand="1">http://tempuri.org/ILoginService/LoginByUserName</a:Action><a:MessageID>urn:uuid:cf410a05-23d4-4b92-a22c-329cbc19fbe7</a:MessageID><a:ReplyTo><a:Address>http://www.w3.org/2005/08/addressing/anonymous</a:Address></a:ReplyTo><a:To s:mustUnderstand="1">http://deab/DexNETWebServices_4_0_0_4/LoginService.svc</a:To></s:Header><s:Body><LoginByUserName xmlns="http://tempuri.org/"><systemId>'
             || '19e0ddb4-5fa5-41ee-b624-aea762865a6c'
             || '</systemId><strName>'
             || 'FirmwareUpdateLogQueryWorker'
             || '</strName><productId>'
             || '0af39a3e-6549-485b-872f-b73413203998'
             || '</productId><password>'
             || 'abc'
             || '</password></LoginByUserName></s:Body></s:Envelope>'
             || CHR (13)
             || '--uuid:e4c19840-745d-45b2-90ca-12d71be4cfd9+id=1--';
          DBMS_OUTPUT.put_line ('request ' || l_request);
          l_http_req := UTL_HTTP.begin_request ('http://deab/DexNETWebServices_4_0_0_4/LoginService.svc', 'POST', 'HTTP/1.1');
          UTL_HTTP.set_header (l_http_req, 'MIME-Version', '1.0');
          UTL_HTTP.set_header (
             l_http_req,
             'Content-Type',
             'multipart/related; type="application/xop+xml";start="<http://tempuri.org/0>";boundary="uuid:e4c19840-745d-45b2-90ca-12d71be4cfd9+id=1";start-info="application/soap+xml"');
          --      UTL_HTTP.set_header (l_http_req, 'Content-ID', '<http://tempuri.org/0>');
          --      UTL_HTTP.set_header (l_http_req, 'Content-Transfer-Encoding', '8bit');
          UTL_HTTP.set_header (
             l_http_req,
             'VsDebuggerCausalityData',
             'uIDPo5F/qXRc4YJImqB6Ard30cQAAAAAAjIXinpIVUulXLJOsSG7yyv7Lf2yHgpHlIxvc6oeqaAACQAA');
          UTL_HTTP.set_header (l_http_req, 'Content-Length', LENGTH (l_request));
          --                  UTL_HTTP.set_header (l_http_req,
          --                                       'SOAPAction',
          --                                       'http://tempuri.org/ILoginService/LoginByUserName');
          UTL_HTTP.write_text (l_http_req, l_request);
          DBMS_LOB.createtemporary (p_response, FALSE);
          l_http_resp := UTL_HTTP.get_response (l_http_req);
       BEGIN
          LOOP
             UTL_HTTP.read_text (l_http_resp, v_buffer, 32767);
             DBMS_OUTPUT.put_line (v_buffer);
             DBMS_LOB.writeappend (p_response, LENGTH (v_buffer), v_buffer);
          END LOOP;
       EXCEPTION
          WHEN UTL_HTTP.end_of_body
          THEN
             NULL;
       END;
       UTL_HTTP.end_response (l_http_resp);
       p_status_code := l_http_resp.status_code;
       p_error_message := l_http_resp.reason_phrase;
       p_response := REPLACE (p_response, '&lt;', '<');
       p_response := REPLACE (p_response, '&gt;', '>');
       DBMS_OUTPUT.put_line (
          'Status: ' || p_status_code || '-' || p_error_message || ': ' || p_response);
    END;
    Thank you for your help on this.

    HI Michiel
    I am also trying to achieve something similar to that. I am trying to call a web service that sends an xml attachment over MTOM? Kindly, let me know if this was achievable from your end? I mean how did the issue got resolved.
    thanks
    vijay

  • Posting XML via HTTP post returns "Envelope missing in SOAP message header"

    Hi,
    I am trying to post a simple XML message directly to the integration server using an html document, where the form that contains the XML message is a simple
    <b><FORM action="http://servername:8000/sap/xi/engine?type=entry" method="post"></b>
    So, I add my xml message like this:
    <?xml version="1.0" encoding="UTF-8">
    <ns:PlantMaintenanceMessageType xmlns:ns="http://sap.com/demo/plantmaintenance">
          <EquipmentID>SLIEQUIP5</EquipmentID>
          <FunctionalLocation>KB</FunctionalLocation>
          <Date/>
          <Time/>
    </ns:PlantMaintenanceMessageType>
    but I get a message back from the Integration Server as:
    <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
      <SAP:Category>XIProtocol</SAP:Category>
      <SAP:Code area="PARSER">ITEM_MISSING</SAP:Code>
      <SAP:P1>Envelope</SAP:P1>
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <b><SAP:Stack>XML tag Envelope missing in SOAP message header (SAP XI Extension)</SAP:Stack></b>
      </SAP:Error>
    Seems like I am missing the Envelope so my Integration Server can understand my post. What does the Envelope look like or should conatain so that the Integration Server accepts my XML file ?
    Thanks !

    This is the trace
      <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Call Adapter
      -->
    - <SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30">
      <Trace level="1" type="T">Party normalization: sender</Trace>
      <Trace level="1" type="T">Sender scheme external =</Trace>
      <Trace level="1" type="T">Sender agency external =</Trace>
      <Trace level="1" type="T">Sender party external =</Trace>
      <Trace level="1" type="T">Sender party normalized =</Trace>
      <Trace level="1" type="B" name="CL_XMS_HTTP_HANDLER-HANDLE_REQUEST" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">XMB was called with URL /sap/xi/engine?type=entry</Trace>
      <Trace level="2" type="T">Request Line = POST /sap/xi/engine?type=entry HTTP/1.1</Trace>
      <Trace level="2" type="T">Host = sapqxh:8020</Trace>
      <Trace level="2" type="T">Server protocol = HTTP/1.1</Trace>
      <Trace level="2" type="T">Remote address = 10.228.137.106</Trace>
      <Trace level="1" type="T">COMMIT is done by XMB !</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="3" type="T">XMB was called with external pipeline PID = ENTRY</Trace>
      <Trace level="3" type="T">Getting type of XMB...</Trace>
      <Trace level="1" type="B" name="SXMBCONF-SXMB_GET_XMB_USE" />
      <Trace level="2" type="T">XMB kind = CENTRAL</Trace>
      <Trace level="3" type="T">Start pipeline found</Trace>
      <Trace level="2" type="T">Switch to external start pipeline PID = CENTRAL</Trace>
    - <Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV">
      <Trace level="3" type="T">No triggers found. OK.</Trace>
      </Trace>
      <Trace level="1" type="T">****************************************************</Trace>
      <Trace level="1" type="T">* *</Trace>
      <Trace level="1" type="T">* *</Trace>
      <Trace level="1" type="T">XMB entry processing</Trace>
      <Trace level="3" type="T">system-ID = QXH</Trace>
      <Trace level="3" type="T">client = 220</Trace>
      <Trace level="3" type="T">language = E</Trace>
      <Trace level="3" type="T">user = PISUPER</Trace>
      <Trace level="1" type="Timestamp">2008-07-18T14:19:04Z CET</Trace>
      <Trace level="1" type="T">* *</Trace>
      <Trace level="1" type="T">* *</Trace>
      <Trace level="1" type="T">****************************************************</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_UC_EXECUTE" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">Message-GUID = 4880474945AE67E2E10000000AE4896A</Trace>
      <Trace level="1" type="T">PLNAME = CENTRAL</Trace>
      <Trace level="1" type="T">QOS = EO</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_ASYNC" />
    - <!--  ************************************
      -->
      <Trace level="3" type="T">QOS = EO</Trace>
      <Trace level="3" type="T">Message-GUID = 4880474945AE67E2E10000000AE4896A</Trace>
      <Trace level="1" type="T">Get definition of external pipeline = CENTRAL</Trace>
    - <Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID">
      <Trace level="3" type="T">External PLID = CENTRAL</Trace>
      <Trace level="3" type="T">Internal PLID = SAP_CENTRAL</Trace>
      </Trace>
      <Trace level="1" type="T">Get definition of internal pipeline = SAP_CENTRAL</Trace>
      <Trace level="3" type="T">Generate prefixed queue name</Trace>
      <Trace level="1" type="T">Queue name : XBTL0000</Trace>
      <Trace level="1" type="T">Generated prefixed queue name = XBTL0000</Trace>
      <Trace level="1" type="T">Schedule message in qRFC environment</Trace>
      <Trace level="3" type="T">Setup qRFC Scheduler</Trace>
      <Trace level="1" type="T">Setup qRFC Scheduler OK!</Trace>
      <Trace level="3" type="T">Call qRFC .... MsgGuid = 4880474945AE67E2E10000000AE4896A</Trace>
      <Trace level="3" type="T">Call qRFC .... Version = 000</Trace>
      <Trace level="3" type="T">Call qRFC .... Pipeline = CENTRAL</Trace>
      <Trace level="3" type="T">OK.</Trace>
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="1" type="T">Going to persist message</Trace>
      <Trace level="1" type="T">NOTE: The following trace entries are always lacking</Trace>
      <Trace level="1" type="T">- Exit WRITE_MESSAGE_TO_PERSIST</Trace>
      <Trace level="1" type="T">- Exit CALL_PIPELINE_ASYNC</Trace>
      <Trace level="1" type="T">Async barrier reached. Bye-bye !</Trace>
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="3" type="T">Version number = 000</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
    - <!--  ************************************
      -->
      <Trace level="3" type="T">Persisting message Status = 001</Trace>
      <Trace level="3" type="T">Message version 000</Trace>
      <Trace level="3" type="T">Pipeline CENTRAL</Trace>
      <Trace level="1" type="T">--start sender interface action determination</Trace>
      <Trace level="1" type="T">select interface MIOA_US139_EmployeeData*</Trace>
      <Trace level="1" type="T">select interface namespace urn:abbott-com:US139</Trace>
      <Trace level="1" type="T">found interface MIOA_US139_EmployeeData</Trace>
      <Trace level="1" type="T">found action ARCH</Trace>
      <Trace level="1" type="T">set interface action to ARCH</Trace>
    - <Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE">
      <Trace level="3" type="T">Trace object available again now. OK.</Trace>
      <Trace level="3" type="T">Message was read from persist layer. OK.</Trace>
      <Trace level="3" type="T">Message properties in XMB object were setup. OK.</Trace>
      <Trace level="3" type="ToDo">Make sure we catch exceptions in persist read</Trace>
      <Trace level="3" type="ToDo">Tracing obj. not avail. before return of CL_XMS_MAIN-PERSIST_READ_MESSAGE</Trace>
      </Trace>
      <Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>
      <Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />
    - <!--  ************************************
      -->
      <Trace level="3" type="T">message version successfully read from persist version= 000</Trace>
      <Trace level="2" type="T">Increment log sequence to 001</Trace>
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="1" type="T">Starting async processing with pipeline CENTRAL</Trace>
      <Trace level="3" type="T">system-ID = QXH</Trace>
      <Trace level="3" type="T">client = 220</Trace>
      <Trace level="3" type="T">language = E</Trace>
      <Trace level="3" type="T">user = PISUPER</Trace>
      <Trace level="1" type="Timestamp">2008-07-18T14:19:08Z CET</Trace>
      <Trace level="1" type="T">----
    </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="3" type="T">External PLID = CENTRAL</Trace>
      <Trace level="3" type="T">Internal PLID = SAP_CENTRAL</Trace>
      </Trace>
      <Trace level="1" type="T">Corresponding internal pipeline SAP_CENTRAL</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T">Pipeline attributes</Trace>
      <Trace level="3" type="T">PID = SAP_CENTRAL</Trace>
      <Trace level="3" type="T">ENABLE = 1</Trace>
      <Trace level="3" type="T">TRACELEVEL = 0</Trace>
      <Trace level="3" type="T">EXEMODE = A</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T" />
      <Trace level="3" type="T">Pipeline elements</Trace>
      <Trace level="3" type="T">ELEMPOS = 0001</Trace>
      <Trace level="3" type="T">PLSRVID = PLSRV_RECEIVER_DETERMINATION</Trace>
      <Trace level="3" type="T">PLSRVTYPE =</Trace>
      <Trace level="3" type="T">FL_DUMMY = 0</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T">ELEMPOS = 0002</Trace>
      <Trace level="3" type="T">PLSRVID = PLSRV_INTERFACE_DETERMINATION</Trace>
      <Trace level="3" type="T">PLSRVTYPE =</Trace>
      <Trace level="3" type="T">FL_DUMMY =</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T">ELEMPOS = 0003</Trace>
      <Trace level="3" type="T">PLSRVID = PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
      <Trace level="3" type="T">PLSRVTYPE =</Trace>
      <Trace level="3" type="T">FL_DUMMY =</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T">ELEMPOS = 0004</Trace>
      <Trace level="3" type="T">PLSRVID = PLSRV_MAPPING_REQUEST</Trace>
      <Trace level="3" type="T">PLSRVTYPE =</Trace>
      <Trace level="3" type="T">FL_DUMMY =</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T">ELEMPOS = 0007</Trace>
      <Trace level="3" type="T">PLSRVID = PLSRV_OUTBOUND_BINDING</Trace>
      <Trace level="3" type="T">PLSRVTYPE =</Trace>
      <Trace level="3" type="T">FL_DUMMY =</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T">ELEMPOS = 0008</Trace>
      <Trace level="3" type="T">PLSRVID = PLSRV_CALL_ADAPTER</Trace>
      <Trace level="3" type="T">PLSRVTYPE = =SWITCH=</Trace>
      <Trace level="3" type="T">FL_DUMMY =</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T">ELEMPOS = 0009</Trace>
      <Trace level="3" type="T">PLSRVID = PLSRV_MAPPING_RESPONSE</Trace>
      <Trace level="3" type="T">PLSRVTYPE =</Trace>
      <Trace level="3" type="T">FL_DUMMY =</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T" />
      <Trace level="1" type="Timestamp">2008-07-18T14:19:08Z CET Begin of pipeline processing PLSRVID = CENTRAL</Trace>
    - <Trace level="1" type="B" name="PLSRV_RECEIVER_DETERMINATION">
      <Trace level="1" type="Timestamp">2008-07-18T14:19:08Z CET Start of pipeline service processing PLSRVID= PLSRV_RECEIVER_DETERMINATION</Trace>
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
      <Trace level="3" type="T">Calling pipeline service: PLSRV_RECEIVER_DETERMINATION</Trace>
      <Trace level="3" type="T">Reading Pipeline-Service specification...</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
      <Trace level="3" type="T">PLSRVID = PLSRV_RECEIVER_DETERMINATION</Trace>
      <Trace level="3" type="T">PLSRVTYPE =</Trace>
      <Trace level="3" type="T">ADRESSMOD = LOCAL</Trace>
      <Trace level="3" type="T">P_CLASS = CL_RD_PLSRV</Trace>
      <Trace level="3" type="T">P_IFNAME = IF_XMS_PLSRV</Trace>
      <Trace level="3" type="T">P_METHOD = ENTER_PLSRV</Trace>
      <Trace level="3" type="T">FL_LOG =</Trace>
      <Trace level="3" type="T">FL_DUMMY = 0</Trace>
      <Trace level="3" type="T" />
    - <Trace 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 level="2" type="T">Start without given receiver</Trace>
      <Trace level="2" type="T">Classic Receiver Determination via Rules.</Trace>
      <Trace level="2" type="T">Check conditions for rule line no. 1</Trace>
      <Trace level="2" type="T">...valid Receiver w/o Condition: - BS_AIMS</Trace>
      <Trace level="2" type="T">No Receiver found behaviour: 0</Trace>
      <Trace level="2" type="T">Number of Receivers:1</Trace>
      </Trace>
      </Trace>
      </Trace>
      <Trace level="1" type="Timestamp">2008-07-18T14:19:08Z CET End of pipeline service processing PLSRVID= PLSRV_RECEIVER_DETERMINATION</Trace>
      </Trace>
    - <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
      <Trace level="3" type="T">Persisting message after plsrv call</Trace>
      <Trace level="3" type="T">Message-Version = 001</Trace>
      <Trace level="3" type="T">Message version 001</Trace>
      <Trace level="3" type="T">Pipeline CENTRAL</Trace>
      </Trace>
    - <Trace level="1" type="B" name="PLSRV_INTERFACE_DETERMINATION">
      <Trace level="1" type="Timestamp">2008-07-18T14:19:11Z CET Start of pipeline service processing PLSRVID= PLSRV_INTERFACE_DETERMINATION</Trace>
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
      <Trace level="3" type="T">Calling pipeline service: PLSRV_INTERFACE_DETERMINATION</Trace>
      <Trace level="3" type="T">Reading Pipeline-Service specification...</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
      <Trace level="3" type="T">PLSRVID = PLSRV_INTERFACE_DETERMINATION</Trace>
      <Trace level="3" type="T">PLSRVTYPE =</Trace>
      <Trace level="3" type="T">ADRESSMOD = LOCAL</Trace>
      <Trace level="3" type="T">P_CLASS = CL_ID_PLSRV</Trace>
      <Trace level="3" type="T">P_IFNAME = IF_XMS_PLSRV</Trace>
      <Trace level="3" type="T">P_METHOD = ENTER_PLSRV</Trace>
      <Trace level="3" type="T">FL_LOG =</Trace>
      <Trace level="3" type="T">FL_DUMMY = 0</Trace>
      <Trace level="3" type="T" />
    - <Trace 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 level="2" type="T">Check conditions for (Inb: Party Srvc If) BS_AIMS MIIA_US139_EmployeeData</Trace>
      <Trace level="2" type="T">...valid InbIf without Condition: MIIA_US139_EmployeeData</Trace>
      <Trace level="2" type="T">Number of receiving Interfaces:1</Trace>
      </Trace>
      </Trace>
      </Trace>
      <Trace level="1" type="Timestamp">2008-07-18T14:19:11Z CET End of pipeline service processing PLSRVID= PLSRV_INTERFACE_DETERMINATION</Trace>
      </Trace>
    - <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
      <Trace level="3" type="T">Persisting message after plsrv call</Trace>
      <Trace level="3" type="T">Message-Version = 002</Trace>
      <Trace level="3" type="T">Message version 002</Trace>
      <Trace level="3" type="T">Pipeline CENTRAL</Trace>
      </Trace>
      <Trace level="1" type="B" name="PLSRV_RECEIVER_MESSAGE_SPLIT" />
    - <!--  ************************************
      -->
      <Trace level="1" type="Timestamp">2008-07-18T14:19:14Z CET Start of pipeline service processing PLSRVID= PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
      <Trace level="3" type="T">Calling pipeline service: PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
      <Trace level="3" type="T">Reading Pipeline-Service specification...</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
      <Trace level="3" type="T">PLSRVID = PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
      <Trace level="3" type="T">PLSRVTYPE =</Trace>
      <Trace level="3" type="T">ADRESSMOD = LOCAL</Trace>
      <Trace level="3" type="T">P_CLASS = CL_XMS_PLSRV_RECEIVER_SPLIT</Trace>
      <Trace level="3" type="T">P_IFNAME = IF_XMS_PLSRV</Trace>
      <Trace level="3" type="T">P_METHOD = ENTER_PLSRV</Trace>
      <Trace level="3" type="T">FL_LOG =</Trace>
      <Trace level="3" type="T">FL_DUMMY = 0</Trace>
      <Trace level="3" type="T" />
    - <Trace 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="3" type="T">Case handling for different plsrv_ids PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
      <Trace level="2" type="T">got property produced by receiver determination</Trace>
      <Trace level="1" type="T">number of receivers: 1</Trace>
      <Trace level="1" type="T">Single-receiver split case</Trace>
      <Trace level="1" type="T">Post-split internal queue name = XBTM0000</Trace>
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="1" type="T">Persisting single message for post-split handling</Trace>
      <Trace level="1" type="T" />
      <Trace level="1" type="T">Going to persist message + call qRFC now...</Trace>
      <Trace level="1" type="T">NOTE: The following trace entries are always lacking</Trace>
      <Trace level="1" type="T">- Exit WRITE_MESSAGE_TO_PERSIST</Trace>
      <Trace level="1" type="T">Async barrier reached. Bye-bye !</Trace>
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
    - <!--  ************************************
      -->
      <Trace level="3" type="T">Persisting message Status = 012</Trace>
      <Trace level="3" type="T">Message version 003</Trace>
      <Trace level="3" type="T">Pipeline CENTRAL</Trace>
    - <Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE">
      <Trace level="3" type="T">Trace object available again now. OK.</Trace>
      <Trace level="3" type="T">Message was read from persist layer. OK.</Trace>
      <Trace level="3" type="T">Message properties in XMB object were setup. OK.</Trace>
      <Trace level="3" type="ToDo">Make sure we catch exceptions in persist read</Trace>
      <Trace level="3" type="ToDo">Tracing obj. not avail. before return of CL_XMS_MAIN-PERSIST_READ_MESSAGE</Trace>
      </Trace>
      <Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>
      <Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />
    - <!--  ************************************
      -->
      <Trace level="3" type="T">message version successfully read from persist version= 004</Trace>
      <Trace level="2" type="T">Increment log sequence to 005</Trace>
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="1" type="T">Starting async processing with pipeline CENTRAL</Trace>
      <Trace level="3" type="T">system-ID = QXH</Trace>
      <Trace level="3" type="T">client = 220</Trace>
      <Trace level="3" type="T">language = E</Trace>
      <Trace level="3" type="T">user = PISUPER</Trace>
      <Trace level="1" type="Timestamp">2008-07-18T14:19:20Z CET</Trace>
      <Trace level="1" type="T">----
    </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="3" type="T">External PLID = CENTRAL</Trace>
      <Trace level="3" type="T">Internal PLID = SAP_CENTRAL</Trace>
      </Trace>
      <Trace level="1" type="T">Corresponding internal pipeline SAP_CENTRAL</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T">Pipeline attributes</Trace>
      <Trace level="3" type="T">PID = SAP_CENTRAL</Trace>
      <Trace level="3" type="T">ENABLE = 1</Trace>
      <Trace level="3" type="T">TRACELEVEL = 0</Trace>
      <Trace level="3" type="T">EXEMODE = A</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T" />
      <Trace level="3" type="T">Pipeline elements</Trace>
      <Trace level="3" type="T">ELEMPOS = 0001</Trace>
      <Trace level="3" type="T">PLSRVID = PLSRV_RECEIVER_DETERMINATION</Trace>
      <Trace level="3" type="T">PLSRVTYPE =</Trace>
      <Trace level="3" type="T">FL_DUMMY = 0</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T">ELEMPOS = 0002</Trace>
      <Trace level="3" type="T">PLSRVID = PLSRV_INTERFACE_DETERMINATION</Trace>
      <Trace level="3" type="T">PLSRVTYPE =</Trace>
      <Trace level="3" type="T">FL_DUMMY =</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T">ELEMPOS = 0003</Trace>
      <Trace level="3" type="T">PLSRVID = PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
      <Trace level="3" type="T">PLSRVTYPE =</Trace>
      <Trace level="3" type="T">FL_DUMMY =</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T">ELEMPOS = 0004</Trace>
      <Trace level="3" type="T">PLSRVID = PLSRV_MAPPING_REQUEST</Trace>
      <Trace level="3" type="T">PLSRVTYPE =</Trace>
      <Trace level="3" type="T">FL_DUMMY =</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T">ELEMPOS = 0007</Trace>
      <Trace level="3" type="T">PLSRVID = PLSRV_OUTBOUND_BINDING</Trace>
      <Trace level="3" type="T">PLSRVTYPE =</Trace>
      <Trace level="3" type="T">FL_DUMMY =</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T">ELEMPOS = 0008</Trace>
      <Trace level="3" type="T">PLSRVID = PLSRV_CALL_ADAPTER</Trace>
      <Trace level="3" type="T">PLSRVTYPE = =SWITCH=</Trace>
      <Trace level="3" type="T">FL_DUMMY =</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T">ELEMPOS = 0009</Trace>
      <Trace level="3" type="T">PLSRVID = PLSRV_MAPPING_RESPONSE</Trace>
      <Trace level="3" type="T">PLSRVTYPE =</Trace>
      <Trace level="3" type="T">FL_DUMMY =</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T" />
      <Trace level="1" type="Timestamp">2008-07-18T14:19:20Z CET Begin of pipeline processing PLSRVID = CENTRAL</Trace>
      <Trace level="1" type="T">Start with pipeline element PLEL= 5EC3C53B4BB7B62DE10000000A1148F5</Trace>
    - <Trace level="1" type="B" name="PLSRV_MAPPING_REQUEST">
      <Trace level="1" type="Timestamp">2008-07-18T14:19:20Z CET Start of pipeline service processing PLSRVID= PLSRV_MAPPING_REQUEST</Trace>
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
      <Trace level="3" type="T">Calling pipeline service: PLSRV_MAPPING_REQUEST</Trace>
      <Trace level="3" type="T">Reading Pipeline-Service specification...</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
      <Trace level="3" type="T">PLSRVID = PLSRV_MAPPING_REQUEST</Trace>
      <Trace level="3" type="T">PLSRVTYPE =</Trace>
      <Trace level="3" type="T">ADRESSMOD = LOCAL</Trace>
      <Trace level="3" type="T">P_CLASS = CL_MAPPING_XMS_PLSRV3</Trace>
      <Trace level="3" type="T">P_IFNAME = IF_XMS_PLSRV</Trace>
      <Trace level="3" type="T">P_METHOD = ENTER_PLSRV</Trace>
      <Trace level="3" type="T">FL_LOG =</Trace>
      <Trace level="3" type="T">FL_DUMMY = 0</Trace>
      <Trace level="3" type="T" />
    - <Trace 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="2" type="T">......attachment XI_Context not found</Trace>
      <Trace level="3" type="T">Mapping already defined in interface determination</Trace>
      <Trace level="3" type="T">Object ID of Interface Mapping 3CCA7AE76D3F33F19F8D7A8DAD494E65</Trace>
      <Trace level="3" type="T">Version ID of Interface Mapping C387A5F00F8B11DCAB84C751AAE12E82</Trace>
      <Trace level="1" type="T">Interface Mapping urn:abbott-com:US139 IM_US139_EmployeeData</Trace>
      <Trace level="3" type="T">Mapping Steps 1 JAVA com/sap/xi/tf/_MM_US139_EmployeeData_</Trace>
      <Trace level="3" type="T">Dynamic Configuration Is Empty</Trace>
      <Trace level="2" type="T">Mode 0</Trace>
      <Trace level="3" type="T">Creating Java mapping com/sap/xi/tf/_MM_US139_EmployeeData_.</Trace>
      <Trace level="3" type="T">Load c387a5f0-0f8b-11dc-ab84-c751aae12e82, urn:abbott-com:US139, -1, com/sap/xi/tf/_MM_US139_EmployeeData_.class.</Trace>
      <Trace level="3" type="T">Search com/sap/xi/tf/_MM_US139_EmployeeData_.class (urn:abbott-com:US139, -1) in swcv c387a5f0-0f8b-11dc-ab84-c751aae12e82.</Trace>
      <Trace level="3" type="T">Loaded class com.sap.xi.tf._MM_US139_EmployeeData_</Trace>
      <Trace level="2" type="T">Call method execute of the application Java mapping com.sap.xi.tf._MM_US139_EmployeeData_</Trace>
      <Trace level="2" type="T">Java mapping com/sap/xi/tf/_MM_US139_EmployeeData_ completed. (executeStep() of com.sap.xi.tf._MM_US139_EmployeeData_</Trace>
      <Trace level="3" type="T">Dynamic Configuration Is Empty</Trace>
      </Trace>
      </Trace>
      </Trace>
      <Trace level="1" type="Timestamp">2008-07-18T14:22:07Z CET End of pipeline service processing PLSRVID= PLSRV_MAPPING_REQUEST</Trace>
      </Trace>
    - <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
      <Trace level="3" type="T">Persisting message after plsrv call</Trace>
      <Trace level="3" type="T">Message-Version = 005</Trace>
      <Trace level="3" type="T">Message version 005</Trace>
      <Trace level="3" type="T">Pipeline CENTRAL</Trace>
      </Trace>
    - <Trace level="1" type="B" name="PLSRV_OUTBOUND_BINDING">
      <Trace level="1" type="Timestamp">2008-07-18T14:22:12Z CET Start of pipeline service processing PLSRVID= PLSRV_OUTBOUND_BINDING</Trace>
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
      <Trace level="3" type="T">Calling pipeline service: PLSRV_OUTBOUND_BINDING</Trace>
      <Trace level="3" type="T">Reading Pipeline-Service specification...</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
      <Trace level="3" type="T">PLSRVID = PLSRV_OUTBOUND_BINDING</Trace>
      <Trace level="3" type="T">PLSRVTYPE =</Trace>
      <Trace level="3" type="T">ADRESSMOD = LOCAL</Trace>
      <Trace level="3" type="T">P_CLASS = CL_XMS_PLSRV_OUTBINDING</Trace>
      <Trace level="3" type="T">P_IFNAME = IF_XMS_PLSRV</Trace>
      <Trace level="3" type="T">P_METHOD = ENTER_PLSRV</Trace>
      <Trace level="3" type="T">FL_LOG =</Trace>
      <Trace level="3" type="T">FL_DUMMY = 0</Trace>
      <Trace level="3" type="T" />
      <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />
    - <!--  ************************************
      -->
    - <Trace level="1" type="B" name="CL_XMS_PLSRV_OUTBINDING-ENTER_PLSRV">
      <Trace level="2" type="T">O U T B O U N D - B I N D I N G</Trace>
      <Trace level="2" type="T">Cache Content is up to date</Trace>
      <Trace level="2" type="T">determine OUTBOUND BINDING for:</Trace>
      <Trace level="2" type="T">-QEHCLNT230</Trace>
      <Trace level="2" type="T">-BS_AIMS</Trace>
      <Trace level="2" type="T">urn:abbott-com:US139.MIIA_US139_EmployeeData</Trace>
      <Trace level="2" type="T">Channel found: - BS_AIMS - CC_BS_AIMS_File_Out_09</Trace>
      <Trace level="2" type="T">no header mapping defined</Trace>
      </Trace>
      </Trace>
      </Trace>
      <Trace level="1" type="Timestamp">2008-07-18T14:22:12Z CET End of pipeline service processing PLSRVID= PLSRV_OUTBOUND_BINDING</Trace>
      </Trace>
    - <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
      <Trace level="3" type="T">Persisting message after plsrv call</Trace>
      <Trace level="3" type="T">Message-Version = 006</Trace>
      <Trace level="3" type="T">Message version 006</Trace>
      <Trace level="3" type="T">Pipeline CENTRAL</Trace>
      </Trace>
      <Trace level="1" type="B" name="PLSRV_CALL_ADAPTER" />
    - <!--  ************************************
      -->
      <Trace level="1" type="Timestamp">2008-07-18T14:22:18Z CET Start of pipeline service processing PLSRVID= PLSRV_CALL_ADAPTER</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV" />
    - <!--  ************************************
      -->
      <Trace level="3" type="T">Calling pipeline service: PLSRV_CALL_ADAPTER</Trace>
      <Trace level="3" type="T">Reading Pipeline-Service specification...</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
      <Trace level="3" type="T">PLSRVID = PLSRV_CALL_ADAPTER</Trace>
      <Trace level="3" type="T">PLSRVTYPE = =SWITCH=</Trace>
      <Trace level="3" type="T">ADRESSMOD = SD</Trace>
      <Trace level="3" type="T">P_CLASS =</Trace>
      <Trace level="3" type="T">P_IFNAME =</Trace>
      <Trace level="3" type="T">P_METHOD =</Trace>
      <Trace level="3" type="T">FL_LOG =</Trace>
      <Trace level="3" type="T">FL_DUMMY = 0</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T">Unknown channel type: File</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
      <Trace level="3" type="T">PLSRVID = PLSRV_CALL_ADAPTER</Trace>
      <Trace level="3" type="T">PLSRVTYPE = AENGINE</Trace>
      <Trace level="3" type="T">ADRESSMOD = SD</Trace>
      <Trace level="3" type="T">P_CLASS = CL_XMS_PLSRV_IE_ADAPTER</Trace>
      <Trace level="3" type="T">P_IFNAME = IF_XMS_PLSRV</Trace>
      <Trace level="3" type="T">P_METHOD = ENTER_PLSRV</Trace>
      <Trace level="3" type="T">FL_LOG =</Trace>
      <Trace level="3" type="T">FL_DUMMY = 0</Trace>
      <Trace level="3" type="T" />
      <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />
    - <!--  ************************************
      -->
    - <Trace level="1" type="B" name="CL_XMS_PLSRV_IE_ADAPTER-ENTER_PLSRV">
      <Trace level="3" type="T">Channel for adapter engine: File</Trace>
    - <Trace level="1" type="B" name="CL_XMS_PLSRV_CALL_XMB-CALL_XMS_HTTP">
      <Trace level="2" type="T">old values in cache (no lock found) - start reading from SLD</Trace>
      <Trace level="1" type="T">error reading SAP_XIAdapterFramework from SLD</Trace>
      <Trace level="2" type="T">Adapter Framework(s) found</Trace>
      <Trace level="2" type="T">Service Port(s) found - take first one</Trace>
      <Trace level="2" type="T">URL found</Trace>
      <Trace level="2" type="T">Get logon data for adapter engine (SAI_AE_DETAILS_GET):</Trace>
      <Trace level="3" type="T">URL = http://sapqxh:52000/MessagingSystem/receive/AFW/XI</Trace>
      <Trace level="3" type="T">User = PIISUSER</Trace>
      <Trace level="3" type="T">Cached =</Trace>
      <Trace level="3" type="T">Creating HTTP-client</Trace>
      <Trace level="3" type="T">HTTP-client: creation finished</Trace>
      <Trace level="3" type="T">Security: Basic authentication</Trace>
      <Trace level="3" type="T">Serializing message object...</Trace>
      <Trace level="3" type="T">HTTP-client: sending http-request...</Trace>
      <Trace level="3" type="T">HTTP-client: request sent</Trace>
      <Trace level="3" type="T">HTTP-client: Receiving http-response...</Trace>
      <Trace level="3" type="T">HTTP-client: response received</Trace>
      <Trace level="3" type="T">HTTP-client: checking status code...</Trace>
      <Trace level="3" type="T">HTTP-client: status code = 200</Trace>
      <Trace level="3" type="T">Deserializing message object...</Trace>
      <Trace level="1" type="T">Empty response received!</Trace>
      <Trace level="3" type="System_Error">HTTP-client: error response=</Trace>
      <Trace level="3" type="T">HTTP-client: closing...</Trace>
      </Trace>
      </Trace>
      </Trace>
    - <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
      <Trace level="3" type="T">Persisting message after plsrv call</Trace>
      <Trace level="3" type="T">Message-Version = 007</Trace>
      <Trace level="3" type="T">Message version 007</Trace>
      <Trace level="3" type="T">Pipeline CENTRAL</Trace>
      </Trace>
      <Trace level="3" type="System_Error">Error exception return from pipeline processing!</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
    - <!--  ************************************
      -->
      <Trace level="3" type="T">Persisting message Status = 014</Trace>
      <Trace level="3" type="T">Message version 008</Trace>
      <Trace level="3" type="T">Pipeline CENTRAL</Trace>
      </SAP:Trace>

  • Issue in soap request SAP Host Control

    Hi. I use SAP NW 7.4  SP2 and have issue in next request
    POST / HTTP/1.1
    SOAPAction: ""
    Content-Type: text/xml; charset=UTF-8
    Content-Length: 559
    <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
    xmlns:ns0="urn:SAPHostControl">
      <SOAP-ENV:Header/>
      <SOAP-ENV:Body>
        <ns0:MoveIpAddress>
          <aInterfaceName/>
          <aAddress>IP</aAddress>
          <aAddressFamily/>
          <aTargetHost>IP</aTargetHost>
          <aTargetUser/>
          <aTargetPassword/>
          <aTargetInterfaceName>???</aTargetInterfaceName>
          <aConnectionToTarget>???</aConnectionToTarget>
        </ns0:MoveIpAddress>
      </SOAP-ENV:Body>
    </SOAP-ENV:Envelope>
    maybe does anyone used this request, what I need write in aTargetInterfaceName && aConnectionToTarget  aConnectionToTarget - http, tcp or https don't work
    Thank you

    Hi,
    Run the program 'RSTXTRAN' using transaction SE38 and attach the Text object to your TR.
    Last time I faced the same problem.
    Everything gets transported except Text object.
    Hope it will be useful to u.
    Revert if not resolved.
    Regards
    Amit
    Edited by: Amit Gupta on May 14, 2009 7:31 AM

  • SOAP request has multiref/soapenc:Array elements

    Hi there - I am receiving a request that is structured using multiref elements. When I examine the SOAP request in the diagnostic log, I see all of the data, but when it gets to the mediator, only the elements in id0 are populated and the rest of the elements are empty. I have seen a few posts that OSB does not handle multirefs, but wanted to see if anyone has solved the problem in another way.
    I am currently using jDev 11.1.1.2 but moving soon to 11.1.1.5. Here is the associated wsdl, an example of the raw SOAP request (which has all of the data) and then the input to my mediator (with the empty elements):
    The problem is occurring with the "Keys" type which is a soapenc:Array. In this case I get the id0 Keys element but the rest of the Keys elements (id1, id2, id3 and id4) are empty when it gets to my mediator.
    WSDL_
         <s:complexType name="Document">
              <s:sequence>
              <s:element name="Keys" type="tns:Keys" />
              <s:element name="IdentifierDisplay" type="s:string" minOccurs="0" maxOccurs="1" />
              <s:element name="contextType" type="s:string" minOccurs="0" maxOccurs="1" />
              <s:element name="autodownload" type="s:boolean" minOccurs="0" maxOccurs="1" />
              <s:element name="ObjectId" type="tns:ObjectId" />
              <s:element name="Type" type="tns:Type" minOccurs="0" maxOccurs="1" />
              <s:element name="EditURL" type="s:string" minOccurs="0" maxOccurs="1" />
              <s:element name="Description" type="s:string" minOccurs="0" maxOccurs="1" />
              <s:element name="Date" type="s:date" minOccurs="0" maxOccurs="1" />
              <s:element name="Time" type="s:time" minOccurs="0" maxOccurs="1" />
              <s:element name="Status" type="tns:Status" minOccurs="0" maxOccurs="1" />
              <s:element name="DocumentLocators" type="tns:DocumentLocators" minOccurs="0" maxOccurs="1" />
    <s:element name="content" type="s:base64Binary" minOccurs="0" maxOccurs="1" />
              </s:sequence>
         </s:complexType>
         <s:complexType name="Type">
              <s:sequence>
              <s:element name="Keys" type="tns:Keys" />
              <s:element name="IdentifierDisplay" type="s:string" minOccurs="0" maxOccurs="1" />
              </s:sequence>
         </s:complexType>
         <s:complexType name="Status">
                   <s:sequence>
                   <s:element name="Keys" type="tns:Keys" minOccurs="0" maxOccurs="1" />
              <s:element name="Name" type="s:string" minOccurs="0" maxOccurs="1" />
              <s:element name="Value" type="s:string" minOccurs="0" maxOccurs="1" />
              <s:element name="Date" type="s:date" minOccurs="0" maxOccurs="1" />
              <s:element name="Time" type="s:time" minOccurs="0" maxOccurs="1" />
                   </s:sequence>
         </s:complexType>
         <s:complexType name="ElectronicFileLocator">
                   <s:sequence>
                   <s:element name="Keys" type="tns:Keys" minOccurs="0" maxOccurs="1" />
              <s:element name="IdentifierDisplay" type="s:string" minOccurs="0" maxOccurs="1" />
              <s:element name="contextType" type="s:string" minOccurs="0" maxOccurs="1" />
              <s:element name="filename" type="s:string" minOccurs="0" maxOccurs="1" />
              <s:element name="fileDateTime" type="s:string" minOccurs="1" maxOccurs="1" />
              <s:element name="fileLocation" type="s:string" minOccurs="0" maxOccurs="1" />
              <s:element name="fileSize" type="s:string" minOccurs="0" maxOccurs="1" />
              <s:element name="serverAddress" type="s:string" minOccurs="0" maxOccurs="1" />
              <s:element name="serverDescription" type="s:string" minOccurs="1" maxOccurs="1" />
              <s:element name="serverType" type="s:string" minOccurs="0" maxOccurs="1" />
              <s:element name="serverPlatform" type="s:string" minOccurs="0" maxOccurs="1" />
              <s:element name="serverVendor" type="s:string" minOccurs="0" maxOccurs="1" />
                   </s:sequence>
         </s:complexType>
         <s:complexType name="PhysicalDocumentLocator">
                   <s:sequence>
                   <s:element name="Keys" type="tns:Keys" minOccurs="0" maxOccurs="1" />
              <s:element name="IdentifierDisplay" type="s:string" minOccurs="0" maxOccurs="1" />
              <s:element name="contextType" type="s:string" minOccurs="0" maxOccurs="1" />
              <s:element name="location" type="s:string" minOccurs="0" maxOccurs="1" />
              <s:element name="Date" type="s:date" minOccurs="1" maxOccurs="1" />
                   </s:sequence>
         </s:complexType>
    <s:complexType name="DocumentLocators">
         <s:sequence>
              <s:element name="ElectronicFileLocator" type="tns:ElectronicFileLocator" minOccurs="0" maxOccurs="1" />
              <s:element name="PhysicalDocumentLocator" type="tns:PhysicalDocumentLocator" minOccurs="0" maxOccurs="1" />
              </s:sequence>
    </s:complexType>
         <s:complexType name="Keys">
              <s:complexContent mixed="false">
                   <s:restriction base="soapenc:Array">
                        <s:attribute wsdl:arrayType="s:string[]" ref="soapenc:arrayType" />
                   </s:restriction>
              </s:complexContent>
         </s:complexType>
    XML input from diagnostic.log Note: bold elements are missing once it gets to my mediator_
    <?xml version = '1.0' encoding = 'UTF-8'?>
    <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <soapenv:Body>
    <ns1:create xmlns:ns1="http://www.replaced.com/edms" soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
    <Document href="#id0"/>
    </ns1:create>
    <multiRef xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns2="http://www.replaced.com/edms/types" id="id0" soapenc:root="0" soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xsi:type="ns2:Document">
    <Keys soapenc:arrayType="xsd:string[3]" xsi:type="soapenc:Array">
    <Keys xsi:type="xsd:string">DENVER</Keys>
    <Keys xsi:type="xsd:string">CAP</Keys>
    <Keys xsi:type="xsd:string" xsi:nil="true"/>
    </Keys>
    <IdentifierDisplay xsi:type="xsd:string">2011-SITE-000011</IdentifierDisplay>
    <contextType xsi:type="xsd:string">application/xml</contextType>
    <autodownload xsi:type="xsd:boolean">false</autodownload>
    <ObjectId href="#id1"/>
    <Type href="#id2"/>
    <Description xsi:type="xsd:string">skipper7</Description>
    <EditURL xsi:type="xsd:string" xsi:nil="true"/>
    <Date xsi:type="xsd:date">2011-11-03</Date>
    <Time xsi:type="xsd:time" xsi:nil="true"/>
    <Status xsi:type="ns2:Status" xsi:nil="true"/>
    <DocumentLocators href="#id3"/>
    </multiRef>
    <multiRef xmlns:ns3="http://www.replaced.com/edms/types" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" id="id3" soapenc:root="0" soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xsi:type="ns3:DocumentLocators">
    <ElectronicFileLocator href="#id4"/>
    <PhysicalDocumentLocator xsi:type="ns3:PhysicalDocumentLocator" xsi:nil="true"/>
    </multiRef>
    *<multiRef xmlns:ns4="http://www.replaced.com/edms/types" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" id="id2" soapenc:root="0" soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xsi:type="ns4:Type">*
    *<Keys soapenc:arrayType="xsd:string[3]" xsi:type="soapenc:Array">*
    *<Keys xsi:type="xsd:string">DENVER</Keys>*
    *<Keys xsi:type="xsd:string">CAP</Keys>*
    *<Keys xsi:type="xsd:string" xsi:nil="true"/>*
    *</Keys>*
    *<IdentifierDisplay xsi:type="xsd:string">Inspection Notice</IdentifierDisplay>*
    *</multiRef>*
    *<multiRef xmlns:ns5="http://www.replaced.com/edms/types" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" id="id1" soapenc:root="0" soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xsi:type="ns5:ObjectId">*
    *<Keys soapenc:arrayType="xsd:string[3]" xsi:type="soapenc:Array">*
    *<Keys xsi:type="xsd:string">DENVER</Keys>*
    *<Keys xsi:type="xsd:string">CAP</Keys>*
    *<Keys xsi:type="xsd:string" xsi:nil="true"/>*
    *</Keys>*
    *<IdentifierDisplay xsi:type="xsd:string">2011-SITE-000011</IdentifierDisplay>*
    *<Value xsi:type="xsd:string"/>*
    *<contextType xsi:type="xsd:string">application/xml</contextType>*
    *</multiRef>*
    *<multiRef xmlns:ns6="http://www.replaced.com/edms/types" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" id="id4" soapenc:root="0" soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xsi:type="ns6:ElectronicFileLocator">*
    *<Keys soapenc:arrayType="xsd:string[3]" xsi:type="soapenc:Array">*
    *<Keys xsi:type="xsd:string">DENVER</Keys>*
    *<Keys xsi:type="xsd:string">CAP</Keys>*
    *<Keys xsi:type="xsd:string" xsi:nil="true"/>*
    *</Keys>*
    *<IdentifierDisplay xsi:type="xsd:string" xsi:nil="true"/>*
    *<contextType xsi:type="xsd:string">application/xml</contextType>*
    *<filename xsi:type="xsd:string">ExternalAPOService.wsdl</filename>*
    *<fileDateTime xsi:type="xsd:string">2011-11-03T16:20:46</fileDateTime>*
    *<fileLocation xsi:type="xsd:string">ExternalAPOService.wsdl</fileLocation>*
    *<fileSize xsi:type="xsd:string">24084</fileSize>*
    *<serverAddress xsi:type="xsd:string" xsi:nil="true"/>*
    *<serverDescription xsi:type="xsd:string">skipper7</serverDescription>*
    *<serverType xsi:type="xsd:string" xsi:nil="true"/>*
    *<serverPlatform xsi:type="xsd:string" xsi:nil="true"/>*
    *<serverVendor xsi:type="xsd:string" xsi:nil="true"/>*
    *</multiRef>* </soapenv:Body>
    </soapenv:Envelope>
    XML input when looking at the input to my mediator in em_
    <Document>
         <Keys soapenc:arrayType="xsd:string[3]" xsi:type="soapenc:Array" xmlns:ns1="http://www.replaced.com/edms" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">
              <Keys xsi:type="xsd:string">DENVER</Keys>
              <Keys xsi:type="xsd:string">CAP</Keys>
              <Keys xsi:type="xsd:string" xsi:nil="true"/>
         </Keys>
         <IdentifierDisplay xsi:type="xsd:string" xmlns:ns1="http://www.replaced.com/edms" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">2011-SITE-000011</IdentifierDisplay>
         <contextType xsi:type="xsd:string" xmlns:ns1="http://www.replaced.com/edms" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">application/xml</contextType>
         <autodownload xsi:type="xsd:boolean" xmlns:ns1="http://www.replaced.com/edms" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">false</autodownload>
         <ObjectId href="#id1" xmlns:ns1="http://www.replaced.com/edms" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
         <Type href="#id2" xmlns:ns1="http://www.replaced.com/edms" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
         <Description xsi:type="xsd:string" xmlns:ns1="http://www.replaced.com/edms" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
         <EditURL xsi:type="xsd:string" xsi:nil="true" xmlns:ns1="http://www.replaced.com/edms" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
         <Date xsi:type="xsd:date" xmlns:ns1="http://www.replaced.com/edms" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">2011-11-03</Date>
         <Time xsi:type="xsd:time" xsi:nil="true" xmlns:ns1="http://www.replaced.com/edms" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
         <Status xsi:type="ns2:Status" xsi:nil="true" xmlns:ns1="http://www.replaced.com/edms" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
         <DocumentLocators href="#id3" xmlns:ns1="http://www.replaced.com/edms" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
    </Document>
    Edited by: mi**** on Nov 4, 2011 7:24 AM

    Hi PeterFL,
    Well Done!
    Thank you very much for sharing the solution to us.
    Best Regards,
    Amy Peng
    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click
    HERE to participate the survey.

  • GWWS_CAT:1022: SOAP Error: Invalid SOAP Body While processing Valid Soap Request

    Hi,
    I Following tuxedo version on AIX 6.1 Power 7 64 bit.
    INFO: Oracle Tuxedo, Version 10.3.0.0, 64-bit, Patch Level 095
    Service Meta Information is :
    service=StockQuote
    export=y
    servicetype=service
    tuxservice=STOCKQUOTE
    svcdescription=This service is used to demo security and xml buffer interop.
    inbuf=XML
    outbuf=XML
    param=XMLBuffer
    type=xml
    access=inout
    size=1000
    this is actually picked from salt sample packaged with version 10.3.
    Request Message:
    <?xml version="1.0" encoding="UTF-8"?>
    <SOAP-ENV:Envelope
    xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
    xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    xmlns:ns1="urn:salt.samples.wsdl"
    xmlns:ns2="urn:pack.samples_typedef.salt11">
    <SOAP-ENV:Body>
    <ns2:StockQuote>
    <ns2:inbuf>
    </ns2:inbuf>
    </ns2:StockQuote>
    </SOAP-ENV:Body>
    </SOAP-ENV:Envelope>
    I put GWWS under tracing and found following.
    Response Messag:
    150237.uaix4070!GWWS.5767178.1046.0: TRACE:ms:SCO[4095] FSM State Transition: --WAKEUP-->Created
    150237.uaix4070!GWWS.5767178.1046.0: TRACE:ms:SCO[4095] FSM State Transition: --Inbound-->Receive
    150237.uaix4070!GWWS.5767178.1046.0: TRACE:ms:SCO[4095] FSM State Transition: --Found-->ParseHTTP
    150237.uaix4070!GWWS.5767178.1046.0: TRACE:ms:HTTP Parsing: Buffer length 1140 -- POST /secsapp HTTP/1.1^M
    Host: uaix4070.unix.rabobank.nl:8070^M
    User-Agent: gSOAP/2.7^M
    Content-Type: text/xml; charset=utf-8^M
    Content-Length: 437^M
    Connection: close^M
    SOAPAction: "StockQuote"^M
    ^M
    <?xml version="1.0" encoding="UTF-8"?>
    <SOAP-ENV:Envelope
    xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
    xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xmlns:xsd="http://www.w3.org/2001/XMLS
    150237.uaix4070!GWWS.5767178.1046.0: TRACE:ms:chema"
    xmlns:ns1="urn:salt.samples.wsdl"
    xmlns:ns2="urn:pack.samples_typedef.salt11">
    <SOAP-ENV:Body>
    <ns2:StockQuote>
    <ns2:inbuf>
    </ns2:inbuf>
    </ns2:StockQuote>
    </SOAP-ENV:Body>
    </SOAP-ENV:Envelope>
    150237.uaix4070!GWWS.5767178.1046.0: TRACE:ms:parse_header_field() return 6
    150237.uaix4070!GWWS.5767178.1046.0: TRACE:ms:SCO[4095] FSM State Transition: --OK-->HTTPDispatch
    150237.uaix4070!GWWS.5767178.1046.0: TRACE:ms:A HTTP message is received, SCO index=4095
    150237.uaix4070!GWWS.5767178.1046.0: TRACE:ms:Finding endpoint, soap->path is /secsapp, request_uri is /secsapp
    150237.uaix4070!GWWS.5767178.1046.0: TRACE:ms:SCO[4095] FSM State Transition: --Post-->ParseSOAPHeader
    150237.uaix4070!GWWS.5767178.1046.0: TRACE:ms:SCO[4095] FSM State Transition: --Default-->ParseHeaderRoot
    150237.uaix4070!GWWS.5767178.1046.0: TRACE:ms:A SOAP message is received, SCO index=4095
    150237.uaix4070!GWWS.5767178.1046.0: TRACE:ms:SCO[4095] FSM State Transition: --None-->ParseSOAPBody
    150237.uaix4070!GWWS.5767178.1046.0: TRACE:ms:SCO[4095] FSM State Transition: --Default-->ParseBodyRoot
    150237.uaix4070!GWWS.5767178.1046.0: TRACE:ms:SCO[4095] FSM State Transition: --OK-->ParseBodyElement
    150237.uaix4070!GWWS.5767178.1046.0: TRACE:ms:Begin data transformation of request message, buffer type = XML, SCO index=4095
    150237.uaix4070!GWWS.5767178.1046.0: TRACE:ms:SCO[4095] FSM State Transition: --Fail-->SOAPFault
    150237.uaix4070!GWWS.5767178.1046.0: TRACE:ms:SCO[4095] FSM State Transition: --OK-->PackSOAPBody
    150237.uaix4070!GWWS.5767178.1046.0: TRACE:ms:SCO[4095] FSM State Transition: --OK-->PackSOAPHeader
    150237.uaix4070!GWWS.5767178.1046.0: TRACE:ms:SCO[4095] FSM State Transition: --Default-->WSRMHandle3
    150237.uaix4070!GWWS.5767178.1046.0: TRACE:ms:SCO[4095] FSM State Transition: --OK-->PackHTTP
    150237.uaix4070!GWWS.5767178.1046.0: TRACE:ms:SCO[4095] FSM State Transition: --Default-->Send
    150237.uaix4070!GWWS.5767178.1046.0: TRACE:ms:Sending HTTP Header: HTTP/1.1 500 Internal Server Error^M
    Server: gSOAP/2.7^M
    Content-Type: text/xml; charset=utf-8^M
    Content-Length: 311^M
    Connection: close^M
    ^M
    150237.uaix4070!GWWS.5767178.1046.0: TRACE:ms:Sending SOAP Message: <?xml version="1.0" encoding="UTF-8"?>
    <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"><SOAP-ENV:Body><SOAP-ENV:Fault><faultcode>SOAP-ENV:Client</faultcode><faultstring>GWWS_CAT:1022: SOAP Error: Invalid SOAP Body.</faultstring></SOAP-ENV:Fault><
    /SOAP-ENV:Body></SOAP-ENV:Envelope>
    Is there something wrong with the request ? Are there known bugs with handling of Soap request in this version ?
    Thanks & Regards,
    Ajeet Tewari

    Ajeet,
    I believe that may be caused by the fact that the payload is empty (<inbuf></inbuf>). The gateway is very strict on that...
    Regards,
    Maurice

Maybe you are looking for

  • How do I export a counter from a task with multiple counters

    Hi All, I have a quadrature output VI that works 100%, outputting the frequency on the default pins (I'm using a NI-6284, so the default CTR0 and CTR1 pins are PFI12 and PFI13). During my development, I made a silly mistake and routed the encoder pin

  • Dynamic photo gallery script?

    Can anyone suggest a good photo gallery script? My client is a photographer and needs a user-friendly system where he can create galleries, upload images. He also needs to assign usernames/passwords to each gallery. I was going to use Coppermine, but

  • Materialized views on prebuilt tables - query rewrite

    Hi Everyone, I am currently counting on implementing the query rewrite functionality via materialized views to leverage existing aggregated tables. Goal*: to use aggregate-awareness for our queries How*: by creating views on existing aggregates loade

  • Buffer table not up to date  while changing contr

    Hi , While changing contracts in SRM we are getting a message  " Buffer table not up to date "  and when we click on this message we get a dump with the below information : This error is occuring in the program SAPLBBP_PDH ,saying : The exception 'CX

  • Java exception when opening a bundle

    Hi, Any ideas why ZENworks 11.2.0.0 throws an exception when opening a bundle (see below) from ZENworks' bundle management view? So far it has been working smoothly for a long time. I have tried to restart services again and even the whole server, bu