SOA Suite to accept non-SOAP HTTPs Post

Is it possible to configure BPEL or ESB to accept an old fashion HTTPs post? I looked at the Bindings samples, but unless I'm missing some files they appear to be posts rather than accepting a post. Thanks in advance.

Meant to reply to this in the recent post, my apologies. Unless my directory is corrupt, those examples are limited to BPEL files. I extracted the jar files and they are .bpel and .jpr files as well.

Similar Messages

  • SOA Suite : Status as NONE for Home process-type.

    Hi,
    I am unable to restart the process-type home in SOA Suite.
    After I found the status it shows as NONE. Please see below
    Even though the status is NONE. I am able to work on application deployed under Home. But what if i have to redeploy the application or change the database.
    bash-3.2# ./opmnctl status
    ./opmnctl[20]: unlimited: 0403-009 The specified number is not valid for this command.
    Processes in Instance: FCCAS.ubsapp01
    ----------------------------------------------------      ----------+---------
    ias-component | process-type | pid | status
    ----------------------------------------------------- ---------+---------
    ASG | ASG | N/A | Down
    OC4JGroup:default_group | OC4J: BRSTEST | 635032 | Alive
    OC4JGroup:default_group | OC4J: home | 0 | NONE
    Kindly help to correct it.
    Please see the opmn log.
    09/10/03 06:30:49 [pm-process] Starting Process: default_group~home~default_group~1 (39002256:0)
    09/10/03 06:30:49 [libopmnoc4j] Attempt to obtain port of type: default-web-site failed for an OC4J process
    09/10/03 06:30:49 [libopmnoc4j] Attempt to get ports for proc: 39002256 failed
    09/10/03 06:30:49 [libopmnoc4j] Process Start Error: default_group~home~default_group~1 (39002256:0)
    09/10/03 06:30:49 [libopmnoc4j] An error occurred while building the start command
    09/10/03 06:30:49 [pm-workers] Job 0 483053 result:
    FCCAS.ubsapp01~default_group~home~default_group~39002256:0
    Status: Stopped
    Operation: internal (no port available from the port range)
    ErrFile:
    09/10/03 06:30:49 [pm-process] Starting Process: default_group~home~default_group~1 (39002256:0)
    09/10/03 06:30:49 [libopmnoc4j] Attempt to obtain port of type: default-web-site failed for an OC4J process
    09/10/03 06:30:49 [libopmnoc4j] Attempt to get ports for proc: 39002256 failed
    09/10/03 06:30:49 [libopmnoc4j] Process Start Error: default_group~home~default_group~1 (39002256:0)
    09/10/03 06:30:49 [libopmnoc4j] An error occurred while building the start command
    09/10/03 06:30:49 [pm-workers] Job 0 483054 result:
    FCCAS.ubsapp01~default_group~home~default_group~39002256:0
    Status: Stopped
    Operation: internal (no port available from the port range)
    ErrFile:
    09/10/03 06:33:40 [pm-process] Starting Process: default_group~home~default_group~1 (39002294:0)
    09/10/03 06:33:40 [libopmnoc4j] Attempt to obtain port of type: default-web-site failed for an OC4J process
    09/10/03 06:33:40 [libopmnoc4j] Attempt to get ports for proc: 39002294 failed
    09/10/03 06:33:40 [libopmnoc4j] Process Start Error: default_group~home~default_group~1 (39002294:0)
    09/10/03 06:33:40 [libopmnoc4j] An error occurred while building the start command
    09/10/03 06:33:40 [pm-workers] Job 0 471537 result:
    FCCAS.ubsapp01~default_group~home~default_group~39002294:0
    Status: NONE
    Operation: internal (no port available from the port range)
    ErrFile:
    09/10/03 06:33:40 [pm-process] Starting Process: default_group~home~default_group~1 (39002294:0)
    09/10/03 06:33:40 [libopmnoc4j] Attempt to obtain port of type: default-web-site failed for an OC4J process
    09/10/03 06:33:40 [libopmnoc4j] Attempt to get ports for proc: 39002294 failed
    09/10/03 06:33:40 [libopmnoc4j] Process Start Error: default_group~home~default_group~1 (39002294:0)
    09/10/03 06:33:40 [libopmnoc4j] An error occurred while building the start command
    09/10/03 06:33:40 [pm-workers] Job 0 471542 result:
    FCCAS.ubsapp01~default_group~home~default_group~39002294:0
    Status: Stopped
    Operation: internal (no port available from the port range)
    ErrFile:
    09/10/03 06:33:40 [pm-process] Starting Process: default_group~home~default_group~1 (39002294:0)
    09/10/03 06:33:40 [libopmnoc4j] Attempt to obtain port of type: default-web-site failed for an OC4J process
    09/10/03 06:33:40 [libopmnoc4j] Attempt to get ports for proc: 39002294 failed
    09/10/03 06:33:40 [libopmnoc4j] Process Start Error: default_group~home~default_group~1 (39002294:0)
    09/10/03 06:33:40 [libopmnoc4j] An error occurred while building the start command
    09/10/03 06:33:40 [pm-workers] Job 0 471543 result:
    FCCAS.ubsapp01~default_group~home~default_group~39002294:0
    Status: Stopped
    Operation: internal (no port available from the port range)
    ErrFile:
    Thanks
    RAM
    Edited by: user10310778 on Oct 2, 2009 9:15 AM

    It seems like your server ports are occupied.
    Type the command,
    netstat -an | grep portnumber
    and see whether the port is listening. You can also get the list of processes using the port using '-ap' option. If any processes are running, kill those processes and start your SOA server.

  • Performance tuning of BPEL processes in SOA Suite 11g

    Hi,
      We are working with a customer for performance tuning of SOA Suite 11g, one of the areas is to tune the BPEL processes. I am new to this and started out with stress testing Hello World process using SOAPUI tool. I would like help with the below topics -
    1. How do I interpret the statistics collected during stress testing? Do we have any benchmark set that can indicate that the performance is ok.
    2. Do we need to run stress tests for every BPEL process deployed?
    2. Is there any performance tuning strategy documentation available? Or can anybody share his/her experiences to guide me?
    Thanks in advance!
    Sritama

    1. How do I interpret the statistics collected during stress testing? Do we have any benchmark set that can indicate that the performance is ok.
    You need
    pay attention to:
    java heap usage vs java heap capacity
    java eden usage vs java eden capacity
    JDBC pool initial connections vs JDBC pool capacity connections
    if you are using linux: top
    if you are using aix: topas
    2. Do we need to run stress tests for every BPEL process deployed?
    yes, you need test each BPEL. You can use "Jmeter" tool.
    Download Jmeter from here: Apache JMeter - Apache JMeter™
    Other tools:
    jstat
    jstack
    jps -v
    Enterprise Manager
    WebLogic Console
    VisualVM
    JRockit Mission Control
    3. Is there any performance tuning strategy documentation available? Or can anybody share his/her experiences to guide me?
    I recommend "Oracle SOA Suite 11g Performance Tuning Cookbook" http://www.amazon.com/Oracle-Suite-Performance-Tuning-Cookbook/dp/1849688842/ref=sr_1_1?ie=UTF8&qid=1378482031&sr=8-1&keywords=oracle+soa+suite+11g+performance+tuning+cookbook

  • Upgrading SOA Suite 10.3.1.0 to 10.3.1.5

    I'm trying to updgrade the SOA AS 10.3.1.0 installed on my machine to 10.3.1.5. I have done a basic installation of SOA AS 10.3.1.0. While applying the patch 10.3.1.5 it gets hanged at 77%. Check the below log file:
    Setting variable 's_backup_file_list' to 'C:\product\10.1.3.1\OracleAS_1\j2ee\home\config\oc4j.properties
    C:\product\10.1.3.1\OracleAS_1\j2ee\home\config\server.xml
    C:\product\10.1.3.1\OracleAS_1\opmn\conf\opmn.xml
    '. Received the value from a code block.
    Calling Query SpawnQueries1.1.4 Spawn
    command = C:\product\10.1.3.1\OracleAS_1\perl\5.8.3\bin\MSWin32-x86-multi-thread\perl.exe -IC:\product\10.1.3.1\OracleAS_1\perl\5.8.3\lib -IC:\product\10.1.3.1\OracleAS_1\perl\5.8.3\lib\MSWin32-x86 C:\product\10.1.3.1\OracleAS_1\config\opmn_bpel.pl
    Query Returned: 0
    Setting variable 'nReturn' to '0'. Received the value from a code block.
    Calling Query fileQueries10.1.0.3.0 exists
    filename = C:\product\10.1.3.1\OracleAS_1\bin\win_touch.exe
    Query Returned: true
    Calling Query fileQueries10.1.0.3.0 exists
    filename = C:\product\10.1.3.1\OracleAS_1\j2ee\home\connectors\OracleASjms\OracleASjms.rar
    Query Returned: true
    Calling Action SpawnActions10.1.0.3.2 Spawn
         installcommand = C:\product\10.1.3.1\OracleAS_1\bin\win_touch.exe C:\product\10.1.3.1\OracleAS_1\j2ee\home\connectors\OracleASjms\OracleASjms.rar
         deinstallcommand = null
         WaitForCompletion = null
    Start output from spawned process:
    End output from spawned process.
    Calling Query fileQueries10.1.0.3.0 exists
    filename = C:\product\10.1.3.1\OracleAS_1\j2ee\home\applications\BC4J.ear
    Query Returned: false
    Calling Query fileQueries10.1.0.3.0 exists
    filename = C:\product\10.1.3.1\OracleAS_1\j2ee\home\applications\datatags.ear
    Query Returned: true
    Calling Action SpawnActions10.1.0.3.2 Spawn
         installcommand = C:\product\10.1.3.1\OracleAS_1\bin\win_touch.exe C:\product\10.1.3.1\OracleAS_1\j2ee\home\applications\datatags.ear
         deinstallcommand = null
         WaitForCompletion = null
    Start output from spawned process:
    End output from spawned process.
    Calling Query fileQueries10.1.0.3.0 exists
    filename = C:\product\10.1.3.1\OracleAS_1\j2ee\home\applications\admin_web.war
    Query Returned: true
    Calling Action SpawnActions10.1.0.3.2 Spawn
         installcommand = C:\product\10.1.3.1\OracleAS_1\bin\win_touch.exe C:\product\10.1.3.1\OracleAS_1\j2ee\home\applications\admin_web.war
         deinstallcommand = null
         WaitForCompletion = null
    Start output from spawned process:
    End output from spawned process.
    Calling Query fileQueries10.1.0.3.0 exists
    filename = C:\product\10.1.3.1\OracleAS_1\j2ee\home\applications\dms.war
    Query Returned: true
    Calling Action SpawnActions10.1.0.3.2 Spawn
         installcommand = C:\product\10.1.3.1\OracleAS_1\bin\win_touch.exe C:\product\10.1.3.1\OracleAS_1\j2ee\home\applications\dms.war
         deinstallcommand = null
         WaitForCompletion = null
    Start output from spawned process:
    End output from spawned process.
    Calling Query fileQueries10.1.0.3.0 exists
    filename = C:\product\10.1.3.1\OracleAS_1\j2ee\home\applications\jmsrouter.war
    Query Returned: true
    Calling Action SpawnActions10.1.0.3.2 Spawn
         installcommand = C:\product\10.1.3.1\OracleAS_1\bin\win_touch.exe C:\product\10.1.3.1\OracleAS_1\j2ee\home\applications\jmsrouter.war
         deinstallcommand = null
         WaitForCompletion = null
    Start output from spawned process:
    End output from spawned process.
    Calling Query fileQueries10.1.0.3.0 exists
    filename = C:\product\10.1.3.1\OracleAS_1\j2ee\home\applications\ascontrol.ear
    Query Returned: true
    Calling Action SpawnActions10.1.0.3.2 Spawn
         installcommand = C:\product\10.1.3.1\OracleAS_1\bin\win_touch.exe C:\product\10.1.3.1\OracleAS_1\j2ee\home\applications\ascontrol.ear
         deinstallcommand = null
         WaitForCompletion = null
    Start output from spawned process:
    End output from spawned process.
    Calling Action fileActions10.1.0.3.0 copyFile
         selectedNodes = null
         source = C:\product\10.1.3.1\OracleAS_1\j2ee\home\config\default-web-site.xml
         destination = C:\product\10.1.3.1\OracleAS_1\j2ee\home\config\default-web-site.xml.pre10135
         permissions = null
         owner = null
         group = null
    Setting variable 's_backup_file_list' to 'C:\product\10.1.3.1\OracleAS_1\j2ee\home\config\oc4j.properties
    C:\product\10.1.3.1\OracleAS_1\j2ee\home\config\server.xml
    C:\product\10.1.3.1\OracleAS_1\opmn\conf\opmn.xml
    C:\product\10.1.3.1\OracleAS_1\j2ee\home\config\default-web-site.xml
    '. Received the value from a code block.
    Calling Action SpawnActions10.1.0.3.2 Spawn
         installcommand = C:\product\10.1.3.1\OracleAS_1\opmn\bin\opmnctlw startall
         deinstallcommand = null
         WaitForCompletion = null
    Start output from spawned process:
    opmnctl: starting opmn and all managed processes...
    Let me know if there is a workaround. Please I'm desperately trying to install AIA 2.4 Media pack on Windows 7 OS.

    Hello,
    The latest version of Oracle AS B2B is 10.1.2.0.2. Please download B2B from OTN Download site under Application server + Application Server 10g (10.1.2.0.2) + Application Server Integration(10.1.2.0.2).
    Please let us know if you have any questions.
    Also, you may be interested in taking a look at the Installation Best practices document for B2B and SOA suite in the following URL.
    http://www.oracle.com/technology/products/integration/b2b/pdf/B2B_SOA_Suite_Installation.pdf
    Rgds,Ramesh

  • Oracle WebLogic Integration's Custom Control and SOA Suite Spring Component

    I crated this thread to inform users about some issues with the
    Oracle WebLogic Integration's Custom Control and SOA Suite Spring Component
    tutorial from
    http://www.oracle.com/technology/architect/soa-suite-series/wli_custom_control_spring_component.html
    - Fig. 6 doesn't agree with what's just above. This step isn't necessary because it can be create automatically when you make a class.
    - Fig. 11 shows the package
    sample.oracle.otn.soaessentials.javainteg
    and the class should be placed in
    sample.oracle.otn.soaessentials.javainteg.impl
    - The Business Tier -> Spring 2.5 might not be available. Extensions steps steps should be given.
    - Fig. 15 When lgger-context is created in Jdev 11.1.1.3.0 the Spring context is created in
    /mywork/SOASuiteWLIEssentials/JavaIntegration/src/META-INF
    while in the sample project it is in
    /mywork/SOASuiteWLIEssentials/JavaIntegration
    - Fig 18 has incorrect class name.
    - Fig 19 is incorrect: there is no Spring 2.5 SCA in Jdev 11.1.1.3.0; there is only WebLogic SCA. Where is the canvas mentioned above?
    - Fig 28 logger-context.xml is not where it is displayed in the fig. It is /src/Meta-Inf/.
    - Most of the fig from the deployment are not up to date.
    - I don't understand the need for the portion:
    "Implementing the use case in WLI" up to
    "Implementing the use case in SOA Suite"
    It confused me when I tried to follow the tutorial.

    I am also looking for the same .... Please share the CLoning script for SOA Suite from Prod to staging Env...
    Thanks.

  • SOA Suite components

    Hello everyone.
    I'm currently in the process of evaluating the Oracle SOA Suite. I have problems to find out the components that are really part of the suite---there seems to be a lot of contradicting information around. In the datasheet, as well as on the SOA Suite homepage, I read that Oracle BAM was included in the package. But after installing the current version (10.1.3.3 + patchset): no BAM to be found. Same with Registry. What's going on? I find this rather frustrating. What does one get buying the SOA Suite?!
    Thanks and greets,
    Jan.

    Hi Marc, thanks for your hint.
    But I cannot find specific information about the suite's components in the pricelist (http://www.oracle.com/corporate/pricing/technology-price-list.pdf), it justs lists SOA Suite and BAM seperately. So I assume that it ain't part of the suite and has to be purchased independently. I think Oracle should remove it from the suite's product sheet and the "SOA Suite Components" list (shown at http://www.oracle.com/technologies/soa/soa-suite.html) as this is rather misleading ;-)
    Thanks,
    Jan.

  • Latest version of SOA Suite released for customer

    What is the latest version of SOA Suite released for customer? Where I can find the documentation of the release?

    The latest release is SOA Suite 10.1.3.4.
    http://www.oracle.com/technology/software/tech/soa/index.html
    You should use the latest MLR#5 with it.
    http://www.oracle.com/technology/products/ias/bpel/htdocs/bpel_release_archive.html

  • Installing B2B with SOA suite 10.3.1

    I have installed SOA suite 10.3.1 and Oracle XE as DB. Now, I want to install B2B, could anyone give me pointers as to where to download it from and how to go about the installation process. Thanks in advance

    Hello,
    The latest version of Oracle AS B2B is 10.1.2.0.2. Please download B2B from OTN Download site under Application server + Application Server 10g (10.1.2.0.2) + Application Server Integration(10.1.2.0.2).
    Please let us know if you have any questions.
    Also, you may be interested in taking a look at the Installation Best practices document for B2B and SOA suite in the following URL.
    http://www.oracle.com/technology/products/integration/b2b/pdf/B2B_SOA_Suite_Installation.pdf
    Rgds,Ramesh

  • SOAP version for B2B HTTP inbound message in SOA Suite 11.1.1.7

    Is there a way to find out the SOAP version supported by B2B HTTP inbound message in SOA Suite 11.1.1.7? Has there been a upgrade of SOAP version to SOAP 1.2?
    The reason behind this assumption is because we are facing following error when an external service posts an XML message enclosed in SOAP envelope (SOAP 1.1) to B2B Sync Receiver Servlet:
    Mime Header Content-Type: text/xml requires SOAP envelope namespace
    Since SOAP headers are already added in the message we are not expecing to face such issue. As per my understanding this issue maybe seen when there is a SOAP version mismatch.
    Moreover, this issue is not seen when this external service posts the same SOAP message to B2B Sync Receiver of SOA suite 11.1.1.6.
    Any help would be highly appreciated.
    Thanks,

    I resolved the issue by myself, The connection factory which I was referring was duplicated. Hence messages were not dequeueing.
    I would be able to found the issues by creating a similar test case scenario.
    Cheers,
    B

  • Http post issue in soa suite 11g  with 10g wsdl

    I have 10g process that has http post wsdl as below. When I'm trying to create a project in 11g 11.1.1.4 with same wsdl, getting the following error at building the project. "Error(12,61): Parse of component type files failed, check the adf-config.xml file : "Error at line 34 char 64: Malformed WS Binding port. Missing # between namespace URI and service/port names."
    I'm sure that http post mechanism is changed in 11g, but can you please help what exactly is wrong ?
    <?xml version="1.0"?>
    <definitions name="HTTPPostService"
    targetNamespace="http://services.otn.com"
    xmlns:tns="http://services.otn.com"
    xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    xmlns:plnk="http://schemas.xmlsoap.org/ws/2003/05/partner-link/"
    xmlns="http://schemas.xmlsoap.org/wsdl/"
              xmlns:http="http://schemas.xmlsoap.org/wsdl/http/"
              xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/"
    >
    <!-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    TYPE DEFINITION - List of types participating in this BPEL process
    The BPEL Designer will generate default request and response types
    but you can define or import any XML Schema type and use them as part
    of the message types.
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -->
    <types>
    <schema attributeFormDefault="qualified" elementFormDefault="qualified"
    targetNamespace="http://services.otn.com"
    xmlns="http://www.w3.org/2001/XMLSchema">
    <element name="Postreq">
    <complexType>
    <sequence>
    <element name="Order_Update_Request">
    <complexType>
    <sequence>
    <element name="ORD_ID" type="string"/>
    <element name="E_MAIL" type="string"/>
    </sequence>
    </complexType>
    </element>
    </sequence>
    </complexType>
    </element>
    <element name="Postresp">
    <complexType>
    <sequence>
    <element name="Order_Update_Response">
    <complexType>
    <sequence>
    <element name="RETURN_STATUS" type="string"/>
    <element name="MESSAGE_TEXT" type="string"/>
    </sequence>
    </complexType>
    </element>
    </sequence>
    </complexType>
    </element>
    </schema>
    </types>
    <!-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    MESSAGE TYPE DEFINITION - Definition of the message types used as
    part of the port type defintions
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -->
    <message name="HTTPPostServiceRequestMessage">
    <part name="payload" element="tns:Postreq"/>
    </message>
    <message name="HTTPPostServiceResponseMessage">
    <part name="payload" element="tns:Postresp"/>
    </message>
    <!-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    PORT TYPE DEFINITION - A port type groups a set of operations into
    a logical service unit.
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -->
    <!-- portType implemented by the HTTPPostService BPEL process -->
    <portType name="HTTPPostService">
    <operation name="IScript_Update_Order">
    <input message="tns:HTTPPostServiceRequestMessage" />
    <output message="tns:HTTPPostServiceResponseMessage"/>
    </operation>
    </portType>
    <binding name="HTTPPost" type="tns:HTTPPostService">
    <http:binding verb="POST"/>
    <operation name="IScript_Update_Order">
    <http:operation location="/PSIG/HttpConnector?From=PSFT_XINBOUND&amp;MessageName=ABC_ORD_UPDORDER&amp;MessageType=sync&amp;MessageVersion=v1"/>
    <input>
    <mime:mimeXml part="payload"/>
    <mime:content type="text/xml"/>
    </input>
    <output>
    <mime:mimeXml part="payload"/>
              <mime:content type="text/xml"/>
    </output>
    </operation>
    </binding>
    <service name="HTTPPostService">
    <port name="HTTPPost" binding="tns:HTTPPost">
    <http:address location="http://myserver.mycompany.com"/>
    </port>
    </service>
    <!-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    PARTNER LINK TYPE DEFINITION
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -->
    <plnk:partnerLinkType name="HTTPPostService">
    <plnk:role name="HTTPPostServiceProvider">
    <plnk:portType name="tns:HTTPPostService"/>
    </plnk:role>
    </plnk:partnerLinkType>
    </definitions>

    Can you make sure your helloworld is using adf bindings as mentioned in thread Re: Urgent :: 11g Invoking Composite from Java/From Webservice Proxy

  • SOAP over HTTP/POST

    Hi everyone,
    I'd be eternally grateful if someone could provide me with a quick + easy solution to the following (basic?) task.
    I have a user form with the required parameters and a submit button. I have an XML schema which specifies the format for the soap requests and responses. How do I accept user input, wrap it into a soap request, send it via HTTP/POST to a server ( http://localhost:9999/xyz/xyz), wait for a soap response and display the response in a readable format to the user when they press the submit button? Not that hard is it?!
    Please try to be a specific as possible because I'm no Java expert. I'm just so confused with all the tutorials about wsdl, bpel, tomcat, jax ws, glassfish etc etc etc!
    I use netbeans and java app server 9, though I'm open to other IDEs/servers.
    Any help will be greatly appreciated,
    Ruth

    https://saaj.dev.java.net/source/browse/*checkout*/saSAAJ: aj/saaj-ri/docs/index.html
    The Java Web Services Tutorial:
    http://java.sun.com/webservices/docs/1.6/tutorial/doc/index.html
    (Chapter 5)
    SOAP Tutorial: http://www.w3schools.com/soap/default.asp

  • 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>

  • Error loading wsdl from the OSB in the SOA Suite over https

    Hi,
    We are running SOA Suite 11G R1 PS2. I have created a webservice in the OSB which runs on https://soa-test.myfirm.com/schedule/service/v1. This service works fine. I can test it in the OSB and using SoapUI. Now I want to make use of it in a bpel proces in the SOA Suite so I added the webservice as external reference and pointed it to the the above url. This works...it sees the porttype and all the bindings. But when I want to deploy it, it doesnt compiles and i get the following issue:
    Error(19,30): Load of wsdl "https://soa-test.myfirm.com/schedule/service/v1?wsdl" failed
    Error(29,89): Cannot find Port Type "{http://www.myfirm.com/wsdl/schedule/service}ScheduleServicePortType" for "ScheduleService" in WSDL Manager
    So it seems it cannot load the wsdl. I saw it might be a proxy issue but I dont use a proxy. I can see the wsdl using my browser without proxy settings.
    Does anyone know why it cannot load my wsdl?
    best regards,
    H
    Edited by: 860367 on 20-May-2011 05:32

    The issue changed to an certificate issue now.
    I get the error:
    javax.xml.soap.SOAPException: javax.xml.soap.SOAPException: Message send failed: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
         at oracle.j2ee.ws.client.jaxws.DispatchImpl.invoke(DispatchImpl.java:784)
         at oracle.j2ee.ws.client.jaxws.OracleDispatchImpl.synchronousInvocationWithRetry(OracleDispatchImpl.java:234)
         at oracle.j2ee.ws.client.jaxws.OracleDispatchImpl.invoke(OracleDispatchImpl.java:105)
         at oracle.integration.platform.blocks.soap.AbstractWebServiceBindingComponent.dispatchRequest(AbstractWebServiceBindingComponent.java:464)
         ... 156 more
    Caused by: javax.xml.soap.SOAPException: javax.xml.soap.SOAPException: Message send failed: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
         at oracle.j2ee.ws.saaj.client.p2p.HttpSOAPConnection.call2(HttpSOAPConnection.java:227)
         at oracle.j2ee.ws.common.transport.HttpTransport.transmit(HttpTransport.java:75)
         at oracle.j2ee.ws.common.async.MessageSender.call(MessageSender.java:64)
         at oracle.j2ee.ws.common.async.Transmitter.transmitSync(Transmitter.java:134)
         at oracle.j2ee.ws.common.async.Transmitter.transmit(Transmitter.java:90)
         at oracle.j2ee.ws.common.async.RequestorImpl.transmit(RequestorImpl.java:273)
         at oracle.j2ee.ws.common.async.RequestorImpl.invoke(RequestorImpl.java:94)
         at oracle.j2ee.ws.client.jaxws.DispatchImpl.invoke(DispatchImpl.java:741)
    I looked in the forum and this could be solved by adding the root CA to the trust keystore of the server. My OSB Managed Server and SOA Managed Server are on the same machine (https://sontprs201.myfirm.com:8888). This machine has a certificate of GoDaddy so i have added the GoDaddy-root and GoDaddy-intermediate as trusted certificates to my certs.jks
    In the weblogic console I set both the managed servers to point to my certs.jks with the correct password and in OSB managed server i setup the SSL with the correct private key alias.
    When i call the OSB service from SoapUI i get the correct 3 certificates back (GD-root, GD-intermediate, sontprs201.myfirm.com), but when I call the OSB service from BPEL I still get the error: Unable to access the following endpoint(s): https://sontprs201.myfirm.com:8888/schedule/service/v1. Unable to find valid certification path.
    Does anybody know what I'm missing or how I can debug this?
    Thanks in advance!

  • HTTPS post using SOAP

    All,
    I have to make a HTTPS post to an URL https://.......
    Can I do it using SOAP receiver adapter - using - "Dont Use SOAP envelope" option.
    Please advice...
    reg

    Bhavesh,
    Could you please share your thoughts on the following....
    1. Enabled SSL on JAVA engine. - can access https://server:httpsprot(50001)/index.html - but gives a warning that cerficate expired.
    2. We have messages coming from a vendor - outside our firewall. - We have not exchanged any certs or keys.
    I have configured a sender SOAP with -
    Transprot Protocol - HTTP
    Message Protocol - SOAP 1.1
    HTTPS security Level - HTTPS Without Client Authentication.
    I have generated a webservice, used SOAP UI - to send a SOAP request to XI. I can see the message in moni. The end point in the SOAP UI is -
    https://<SERVER>:<HTTPS Port>/XISOAPAdapter/MessageServlet?channel=party:service:channel
    Is there anything that I will have to do to accept the messages from the vendor.
    I am trying to skip the ssl enablement on ABAP engine - so using SOAP adapter.
    When tried to post some data from a webmethods server, it is giving error for some SSL certificatie. As a part of SSL enablement on JAVA, I dont think basis team did install any certificate.
    reg

  • Oracle SOA Suite - SOAP Fault content not being returned

    It starts with a fairly standard scenario: from within a BPEL process in Oracle SOA Suite, I’m making a call to an external web service. The not-so-standard part: the owner of the external web service has decided to return all errors in the form of a SOAP fault. Unfortunately, this error schema is not included in the WSDL. If we call the external web service directly (via SOAPUI, for example), we get the following, including a nice explanation of why it errored out:
    <soapenv:Fault xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:err="error.xml.common">
    <faultcode>soapenv:Server</faultcode>
    <faultstring>Undefined</faultstring>
    <detail>
    <err:ErrorList>
    <err:Error>
    <err:Application>CIA</err:Application>
    <err:Code>1031</err:Code>
    <err:Description>Field value is invalid Credit Card Number V failed mod10 check</err:Description>
    <err:ServerTime>2010-02-25T17:37:38.472-05:00</err:ServerTime>
    </err:Error>
    <err:StackTrace>subscription.memberservices.common.exception.ServiceInvocationException: 1031~Field value is invalid Credit Card Number V failed mod10 check
    at subscription.memberservices.common.client.http.CiaHttpClient.checkForErrors(CiaHttpClient.java:120)
    at subscription.memberservices.common.client.http.CiaHttpClient.enroll(CiaHttpClient.java:50)
    at subscription.memberservices.na.processes.enroll.EnrollProcess.callCiaEnroll(EnrollProcess.jpd:1003)
    at subscription.memberservices.na.processes.enroll.EnrollProcess_wf$ImplControlSend14.invoke(EnrollProcess_wf.java:145)
    at com.bea.wli.bpm.runtime.Perform.execute(Perform.java:32)
    ... 38 more</err:StackTrace>
    </err:ErrorList>
    </detail>
    </soapenv:Fault>
    No matter what I try, however, I can’t fetch the information in the “detail” element above. When examining the audit trail in SOA Suite, I can only see this:
    <fault>
    <faultType>0</faultType>
    <remoteFault>
    <part name="summary">
    <summary>Undefined</summary>
    </part>
    <part name="detail">
    <detail>javax.xml.ws.soap.SOAPFaultException: Undefined</detail>
    </part>
    <part name="code">
    <code>null</code>
    </part>
    </remoteFault>
    </fault>
    It seems SOA Suite is “protecting” my service from the other SOAP fault elements instead of passing everything back, only passing the faultstring element. I even tried adding an ErrorList schema to match theirs but to no avail. Anyone out there have any experience, luck or ideas with this problem?
    Thanks for the assistance,
    Rob

    Re: Oracle SOA suite server does not startBut I can see that server has got started -
    <21-Jul-2010 12:04:47 o'clock BST> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>em application gets deployed on admin server and not on SOA server. You may access em console on - http://<hostName>:<admin_server_port>/em
    By default admin server port is 7001.
    Regards,
    Anuj

Maybe you are looking for

  • Differences between old & new version

    Hello folks, I got the new version of iMovie but can't find all the functions that I had with the old one version. For example how is it possible to add the "rallenty" function? How to modify audio settings to the mic (example: echo, cathedral...)? H

  • Exempt amount is not considering in IT 195

    Hi, SAP has provided an scenario where in IT 195 after adding non exempt rule,we can exempt the amount which need to be garnished by way of clicking the exempt radio button given in the bottom of IT 195 and here you can give how much money to be exem

  • WEBI working in Rich Client but giving error opendocument' api. (error err_wis_30270) in launch pad

    Hi, I transported webi documents + universe from a development server (BI 4.1. SP2) to a test server (same release). I can open the documents with the WEBI rich client, but I am unable to open them with the launch pad (error ...opendocument' api. (er

  • RME 4.0.6 - Archive Purge not working

    Hi, I have noticed that our archive purge job is failing completely, for all devices, and it appears to have been failing for some time now. Looking at the meesage apeparing in the Job Details for one of the devices I get: *** Device Details for myde

  • Trying to use cut function in finder

    I'm new to the mac so this may be a silly question but why can't I cut a file and then paste it somewhere else? I can only copy an item. The edit>cut function is grayed out. Please help!