BPEL partnerlink SOAP encodingStyle

I am getting error calling a partnerlink WebMethod Glue web service. I think Glue requires encodingStyle set for either SOAP Envelope or SOAP Body. It is not clear how BPEL is constructing the call to partnerlink. I need to figure out how can I make sure the encodingStyle attribute is added to SOAP Body or Envelope.
Anybody has any idea how it is done. I know I could modify SOAP header in BPEL process. How do I modify SOAP Body or Envelope? I want the soap call to partnerlink look like this: (the key thing is soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/")
<soapenv:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:x="x">
<soapenv:Header/>
<soapenv:Body>
<x:getOperation soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
<arg0 xsi:type="xsd:string">000000010</arg0>
</x:getOperation>
</soapenv:Body>
</soapenv:Envelope>
I played with property setting in bpel.xml, but didn't seem to have any effect:
<partnerLinkBinding name="SomeWebService">
<property name="wsdlLocation">SomeWebServiceRef.wsdl</property>
<property name="encodingStyle">http://schemas.xmlsoap.org/soap/encoding/</property>
<property name="optSoapShortcut">false</property>
<property name="sendXSIType">true</property>
</partnerLinkBinding>
Edited by: user636556 on Sep 24, 2008 3:01 PM

Settting property in property tab of partnerlink is same as putting those values directly in bpel.xml like I showed in my previous post. That didn't make any difference.

Similar Messages

  • XI 2.0 Standalone J2SE SOAP Adapter as client - SOAP:encodingStyle

    Hi,
    We're setting up the J2SE SOAP Adapter of XI 2.0 to talk to a synchronous web service provided by a webmethods platform.
    When we generate the Request message using the WSDL and post it directly via the HTTP test tool the message is understood and a response message is returned.
    Here is the Request:
    <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">
         <SOAP-ENV:Body>
              <m:callFP091 xmlns:m="http://destserver/FP091.flows" SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
                   <iw1_RECTPE xsi:type="xsd:string">String</iw1_RECTPE>
                   <iw1_DLRCODE xsi:type="xsd:string">String</iw1_DLRCODE>
                   <iw1_FRNCODE xsi:type="xsd:string">String</iw1_FRNCODE>
                   <iw1_JOBNUM xsi:type="xsd:string">String</iw1_JOBNUM>
                   <iw1_CHASIS xsi:type="xsd:string">String</iw1_CHASIS>
                   <iw1_COLOUR xsi:type="xsd:string">String</iw1_COLOUR>
                   <iw1_DESCRIP xsi:type="xsd:string">String</iw1_DESCRIP>
                   <iw1_INVNUM xsi:type="xsd:string">String</iw1_INVNUM>
                   <iw1_CAPAMT xsi:type="xsd:string">String</iw1_CAPAMT>
                   <iw1_INTFRE xsi:type="xsd:string">String</iw1_INTFRE>
                   <iw1_LOC_IND xsi:type="xsd:string">String</iw1_LOC_IND>
                   <iw1_REGISTRATION xsi:type="xsd:string">String</iw1_REGISTRATION>
                   <iw1_ENGINE_NUM xsi:type="xsd:string">String</iw1_ENGINE_NUM>
                   <iw1_VIN_NUM xsi:type="xsd:string">String</iw1_VIN_NUM>
              </m:callFP091>
         </SOAP-ENV:Body>
    </SOAP-ENV:Envelope>
    When we try to use the SOAP Adapter and pass it the following message from XI:
    <m:callFP091 xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/"
    xmlns:m="http://destserver/FP091.flows"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/"
    SOAP:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" >
              <iw1_RECTPE xsi:type="xsd:string">E1</iw1_RECTPE>
              <iw1_DLRCODE xsi:type="xsd:string">3009838</iw1_DLRCODE>
              <iw1_FRNCODE xsi:type="xsd:string">333</iw1_FRNCODE>
              <iw1_JOBNUM xsi:type="xsd:string">123</iw1_JOBNUM>
              <iw1_CHASIS xsi:type="xsd:string">2</iw1_CHASIS>
              <iw1_COLOUR xsi:type="xsd:string">3</iw1_COLOUR>
              <iw1_DESCRIP xsi:type="xsd:string">4</iw1_DESCRIP>
              <iw1_INVNUM xsi:type="xsd:string">5</iw1_INVNUM>
              <iw1_CAPAMT xsi:type="xsd:string">6</iw1_CAPAMT>
              <iw1_INTFRE xsi:type="xsd:string">7</iw1_INTFRE>
              <iw1_LOC_IND xsi:type="xsd:string">8</iw1_LOC_IND>
              <iw1_REGISTRATION xsi:type="xsd:string">9</iw1_REGISTRATION>
              <iw1_ENGINE_NUM xsi:type="xsd:string">1</iw1_ENGINE_NUM>
              <iw1_VIN_NUM xsi:type="xsd:string">2</iw1_VIN_NUM>
    </m:callFP091>
    The SOAP adapter wraps the envelope and body around this message, provides an empty header but changes the SOAP:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" attribute to SOAP:actor='http://schemas.xmlsoap.org/soap/encoding/'.
    The generated SOAP message is:
    <SOAP:Envelope xmlns:SOAP='http://schemas.xmlsoap.org/soap/envelope/'>
    <SOAP:Header/>
    <SOAP:Body>
    <m:callFP091 xmlns:m='http://196.11.134.83/FP091.flows'
    SOAP:actor='http://schemas.xmlsoap.org/soap/encoding/'
    xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance'
    xmlns:xsd='http://www.w3.org/2001/XMLSchema'>
              <iw1_RECTPE xsi:type='xsd:string'>E1</iw1_RECTPE>
              <iw1_DLRCODE xsi:type='xsd:string'>3009838</iw1_DLRCODE>
              <iw1_FRNCODE xsi:type='xsd:string'>333</iw1_FRNCODE>
              <iw1_JOBNUM xsi:type='xsd:string'>123</iw1_JOBNUM>
              <iw1_CHASIS xsi:type='xsd:string'>2</iw1_CHASIS>
              <iw1_COLOUR xsi:type='xsd:string'>3</iw1_COLOUR>
              <iw1_DESCRIP xsi:type='xsd:string'>4</iw1_DESCRIP>
              <iw1_INVNUM xsi:type='xsd:string'>5</iw1_INVNUM>
              <iw1_CAPAMT xsi:type='xsd:string'>6</iw1_CAPAMT>
              <iw1_INTFRE xsi:type='xsd:string'>7</iw1_INTFRE>
              <iw1_LOC_IND xsi:type='xsd:string'>8</iw1_LOC_IND>
              <iw1_REGISTRATION xsi:type='xsd:string'>9</iw1_REGISTRATION>
              <iw1_ENGINE_NUM xsi:type='xsd:string'>1</iw1_ENGINE_NUM>
              <iw1_VIN_NUM xsi:type='xsd:string'>2</iw1_VIN_NUM>
    </m:callFP091>
    </SOAP:Body>
    </SOAP:Envelope>
    This message has no SOAP:encodingStyle attribute and is therefore not understood by the WebMethods web service. Here is the error message from the web service:
    [B2BCORE.0076.9201] SOAP Message Coder cannot decode message; no encoding style is specified
    How do I configure the outbound SOAP adapter within the XI 2.0 J2SE adapter engine to add the SOAP:encodingStyle attribute to the outbound message?
    I have tried playing around with the XMBWS.* parameters outlined in the adapter engine documentation but these don't seem to have any influence on the way the SOAP request message is formed.
    Any suggestions would be appreciated.
    Regards,
    -Derek

    Hi,
    You could use the webMethods XI adapter to create the connection.
    Best Regards,
    Sander

  • BPEL 11g SOAP with Attachments

    Does anyone have any examples utilizing SOAP with Attachments with BPEL 11g?
    I have previously worked with SwA in BPEL 10g, but I have not been able to successfully port my BPEL projects to 11g. I am able to send in an attachment without error, but the outgoing requests and/or responses do not contain the attachment as they should.
    Note: I am trying to use traditional SOAP with Attachments (hrefs) and not MTOM

    Hi ,
    Even we too have same requirement where soap with attachment (swa) has to pass through bpel process(11g).You hava mentioned that ur able to attach file to req..please can u share your sample for reference.
    Thanks for suggestions.

  • BPEL service(SOAP) expose as RESTFul Service through OSB

    I am trying to invoke simple HelloWorld BPEL process exposed as SOAP Web Service through OSB as RESTFul service but always getting XML parsing exception in response action.
    Could any body give me steps how to implement it?
    Thanks
    Edited by: user10475179 on Dec 4, 2011 9:44 PM

    Thanks for your reply. I was able to manage to get xml, is there a simple way with simple steps to use JSON? If you have any steps/screenshots I would appreciate.
    Thanks
    Edited by: user10475179 on Dec 6, 2011 2:24 PM

  • Bpel cluster, soap adress in wsdl, soapSeverUrl, load balance - problem

    Hello,
    I've installed bpel into cluster of two nodes with RAC repository db behind.
    I have followind problem ...
    I want to loadbalance incomming requests.
    Configuration description:
    One public IP > load balancer > ( node1) or (node2) with private IPs.
    My expectation was that parameter soapServerUrl ( set to loadbalancer address)
    ensures that the address of load balancer will be inside wsdl in soap:address.
    The real world situation is other :-(
    In bpel console > processes > process WSDL sheet, WSDL location - here is the correct soapServerUrl
    but inside the wsdl there isn't. There is node address inside wsdl.
    So, was my expectation wrong?
    If my expectation was wrong, is there any other solution?
    How can I ensure that the address of loadbalancer will be inside the wsdl.
    Karel

    selfreply:
    you have to re-deploy processes after you change soapServerUrl for a domain.
    Karel

  • Invoking BPEL partnerlink each for one child node

    Hi
    I have a requirement for invoking partnerlink (DB Adapter) for each child node of input message of BPEL service! E.g. I have to update or insert an employee! I received list of of employees in input message like below.
    <employee_list>
         <employee>
              <name> Ram </name>
              <Age> 21 </Age>
              <dept> IT </dept>
              <isNew>N</isNew>
         </employee>
         <employee>
              <name> Hari </name>
              <Age> 21 </Age>
              <dept> IT </dept>
              <isNew>Y</isNew>
         </employee>
    </employee_list>
    So the requirement is to call DB_Call partnerlink for each employee node in above!
    Is this possible in BPEL? If yes, how?
    Thanks In Advance
    Priyadarshi

    Yes you can, use a fo reach loop in bpel, loop for the count of employee, then have an if condition to check whether you want to update or insert for and use invoke node to call the appropriate operation.I hope you have gone through the upsert operation in database adpater which automatically supports insert or update. If a record is present it updates else inserts a new one.

  • BPEL partnerlink services not deployed

    Hi,
    Deploying a BPEL process via JDeveloper required a manual copy of class files (packages) to be put them under ~/bpel/system/classes on the OAS.
    Does this have to manually configured in JDev before deployment?
    Thank you for any comment.
    Mark

    Just as normal application development. You shoul have a version control system, like subversion, to keep track on the processes you developed. With a version-control-tool, you define the versions of the application you deployed in you OTAP environment.
    Changing a process means that a new version of this process is deployed. For a new process, the default 1.0, version of the process is deployed.
    But again; you should have a version-control-system, and a build system to keep track/control on your whole OTAP process.

  • Asynch replies from bpel partnerlink not making it back??

    Anyone seen this behaviour ? After a restart of OAS3/BPEL we have an asynch call that says it's returned BUT the parent says it hasn't. It looks very of on the tree-finder! This is BPEL to BPEL partner link...

    Delving through the logs on OAS revealed the following, which I guess explains it:
    "<2006-07-06 08:19:24,632> <ERROR> <default.collaxa.cube.engine.dispatch> <BaseScheduledWorker::process> Failed to handle dispatch message
    ... exception ORABPEL-05002
    Message handle error.
    An exception occurred while attempting to process the message "com.collaxa.cube.engine.dispatch.message.instance.CallbackDeliveryMessage";
    the exception is: Cannot update document.
    The process domain was unable to update/insert the document "2601-168" into the datastore. The exception reported is: ORA-01653: unable
    to extend table ORABPEL.DOCUMENT by 8 in tablespace ORABPEL
    ORA-06512: at "ORABPEL.COLLAXA", line 152 "

  • BPEL - not generating correct SOAP packet for complex types

    Hi,
    Below is a snippet from wsdl, correct SOAP request and reply packet (generated using a SOAP test tool) and finally BPEL generated SOAP request and error response (captured using TCP packet monitor)
    The problem is with element 'XActivationPackageArray', which is getting enclosed
    by itself again from Oracle BPEL PM.
    ------------------------W S D L S T A R T----------------------------------------------------
    <definitions xmlns="http://schemas.xmlsoap.org/wsdl/" .......>
         <types>
              <schema>
                   <complexType name="XActivationPackageArray">
                        <sequence>
                             <element name="XActivationPackage" type="tns2:XActivationPackage" maxOccurs="unbounded"/>
                        </sequence>
                   </complexType>
                   <element name="XActivationPackageArray" type="tns2:XActivationPackageArray"/>
                   <complexType name="XActivationPackage">
                        <sequence>
                             <element name="activationPackage" nillable="true" type="xsd:string"/>
                        </sequence>
                   </complexType>
                   <complexType name="XActivationResponse">
                        <sequence>
                             <element name="unitId" nillable="true" type="xsd:string"/>
                             <element name="serviceId" nillable="true" type="xsd:string"/>
                        </sequence>
                   </complexType>
                   <element name="XActivationResponse" type="tns2:XActivationResponse"/>
              </schema>
         </types>
         <message name="activateServiceRequest">
              <part name="userId" type="xsd:string"/>
              <part name="companyCd" type="xsd:string"/>
              <part name="customerCd" type="xsd:string"/>
              <part name="stockAccountId" type="xsd:string"/>
              <part name="orderNumber" type="xsd:string"/>
              <part name="serviceType" type="xsd:string"/>
              <part name="location" type="xsd:string"/>
              <part name="unitId" type="xsd:string"/>
              <part name="serviceIdPool" type="xsd:string"/>
              <part name="serviceId" type="xsd:string"/>
              <part name="XActivationPackageArray" element="tns2:XActivationPackageArray"/>
         </message>
         <message name="activateServiceResponse">
              <part name="XActivationResponse" element="tns2:XActivationResponse"/>
         </message>
    </definitions>
    ------------------------W S D L E N D----------------------------------------------------
    ------------------------Correct SOAP packet ----------------------------------------------------
    <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:urn="urn:sf2pwrapper.ws.sf2.p1.com">
    <soapenv:Body>
    <urn:activateService>
    <userId>XYZ</userId>
    <companyCd>999</companyCd>
    <customerCd>ABCDE</customerCd>
    <stockAccountId>FGHIJ</stockAccountId>
    <orderNumber>888999</orderNumber>
    <serviceType>AA</serviceType>
    <location>A</location>
    <unitId/>
    <serviceIdPool>XXX</serviceIdPool>
    <serviceId/>
    <XActivationPackageArray>
                   <XActivationPackage>
                        <activationPackage>MMGG</activationPackage>
                   </XActivationPackage>
    </XActivationPackageArray>
    </urn:activateService>
    </soapenv:Body>
    </soapenv:Envelope>
    ------------------------Correct reply ----------------------------------------------------
    <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>
    <activateServiceResponse xmlns="urn:sf2pwrapper.ws.sf2.p1.com">
    <ns1:XActivationResponse xmlns:ns1="urn:model.sf2pwrapper.ws.sf2.p1.com">
    <unitId xmlns="">0642342</unitId>
    <serviceId xmlns="">83753710</serviceId>
    </ns1:XActivationResponse>
    </activateServiceResponse>
    </soapenv:Body>
    </soapenv:Envelope>
    ------------------------BPEL generated SOAP packet--------------------------------------------------
    <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:activateService soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns1="urn:sf2pwrapper.ws.sf2.p1.com">
    <userId xmlns:def="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="def:string">XYZ</userId>
    <companyCd xmlns:def="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="def:string">999</companyCd>
    <customerCd xmlns:def="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="def:string">ABCDE</customerCd>
    <stockAccountId xmlns:def="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="def:string">FGHIJ</stockAccountId>
    <orderNumber xmlns:def="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="def:string">888999</orderNumber>
    <serviceType xmlns:def="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="def:string">AA</serviceType>
    <location xmlns:def="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="def:string">A</location>
    <unitId xmlns:def="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="def:string"></unitId>
    <serviceIdPool xmlns:def="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="def:string">XXX</serviceIdPool>
    <serviceId xmlns:def="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="def:string"></serviceId>
    <XActivationPackageArray>
    <XActivationPackageArray xmlns="urn:model.sf2pwrapper.ws.sf2.p1.com">
    <XActivationPackage xmlns="">
    <activationPackage>MMGG</activationPackage>
    </XActivationPackage>
    </XActivationPackageArray>
    </XActivationPackageArray>
    </ns1:activateService>
    </soapenv:Body>
    </soapenv:Envelope>
    ------------------------BPEL error--------------------------------------------------
    <?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>
    <soapenv:Fault>
    <faultcode>soapenv:Server.userException</faultcode>
    <faultstring>org.xml.sax.SAXException: Invalid element in com.p1.sf2.ws.sf2pwrapper.model.XActivationPackage - XActivationPackage</faultstring>
    <detail>
    <ns1:hostname xmlns:ns1="http://xml.apache.org/axis/">c7g7mrs</ns1:hostname>
    </detail>
    </soapenv:Fault>
    </soapenv:Body>
    </soapenv:Envelope>

    t

  • SOAP Envelope encodingStyle

    Hi experts,
    I have a PI SOAP Receiver, sending to a Java Powerbuilder app. I am getting an HTTP 200, but with an error message in SXMB_MONI:
    <SAP:Category>XIAdapterFramework</SAP:Category>
    <SAP:Code area="MESSAGE">GENERAL</SAP:Code>
    <SAP:AdditionalText>com.sap.aii.af.ra.ms.api.DeliveryException: java.lang.NullPointerException; HTTP 200 OK</SAP:AdditionalText>
    When I execute the same scenario using soapUI instead of PI, using the same SOAP Payload, I get no SOAP body, only this HTTP Response (HTTP 200 OK as well):
    " No mapping found for 'class java.lang.String' using encoding style 'http://xml.apache.org/xml-soap/literalxml'  "
    When I change the Payload slightly in soapUI, ie. adding an encodingStyle attribute to the SOAP Envelope, I get the expected response message ("Test OK").
    To summarize:
    PI sends this SOAP Envelope, which the remote app cannot accept (no mapping found):
    <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
    When the SOAP Envelope is modified like below, the test is ok:
    <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/"        
                   SOAP:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
    Any ideas how I can add an encodingStyle attribute ?
    kr,
    Peter Glas

    An sdn search gave me this thread to create custom SOAP envelop
    Generating SOAP Envelope when DO NOT USE ENVELOPE option is marked

  • Sending SOAP Attachments through BPEL--Urgent

    Hi All,
    we are calling one external web service from bpel.webservice expecting 2 attachments as part of request. here is the sample soap request.
    *<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:imp="http://www.agile.com/2004/01/ais/import">*
    *<soapenv:Header/>*
    *<soapenv:Body>*
    *<imp:importDataRequest>*
    *<imp:dataSource>*
    *<imp:attachmentRef href="cid:12266262222"/>*
    *<imp:type>aXML</imp:type>*
    *</imp:dataSource>*
    *<imp:mapping>*
    *<imp:attachmentRef href="cid:9876553333"/>*
    *</imp:mapping>*
    *</imp:importDataRequest>*
    *</soapenv:Body>*
    *</soapenv:Envelope>*
    1.how can we attach file throgh bpel in SOAP request and then how to provide reference number to href field..
    2. is there any alternative to achive this?
    if anyone have the working example or link please send me to [email protected]
    Thanks,
    Sudhakar.M

    You could create a variable base64Binary and assign the content of the ora:getAttachmentContent() return value. And then write to a file using the option "Native format translation is not required (Schema is opaque)" from the file adapter and assign to the opaque element.

  • Invoke WS from BPEL 'exception on JaxRpc invoke'

    I am trying to call a standard Java web service from a BPEL workflow, and randomly get the following error:
    exception on JaxRpc invoke: HTTP transport error: javax.xml.soap.SOAPException: java.security.PrivilegedActionException: javax.xml.soap.SOAPException: Message send failed: Connection refused
    The web service in question is deployed on the local machine, and the BPEL partnerLinks point to "localhost". It doesn't appear to matter whether or not the application server(s) are clustered.
    Because it seems to happen randomly, regardless of load, I am thoroughly stumped. Does anyone have any ideas on what could be causing this problem?
    Thanks,
    Dan

    Dan,
    I wonder if you can write a simple Java client and try to call this WS. Do you get this error also? Was the WS deployed to the same application server as the BPEL? Can you try the actual IP address of the server or the hostname rather than localhost? Would that make any difference?
    Mustafa

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

  • Error invoking bpel partner link from bpel process

    hello,
    i try to invoke a bpel web service (deployed correctly) from another bpel process.
    I've this error:
    Cannot find resource. Context:
    http://orcldemo.localdomain:9700/orabpel/xmllib/ws-addressing.xsd
    I've tried to add my wsdl to:
    \\orcldemo\orabpel\system\xmllib\
    In this way I can invoke bpel web service (http://orcldemo:9700/orabpel/xmllib/WebServiceName.wsdl)and deploy my bpel process without compilation error, but when I start my bpel process the instance isn't created.
    I've pm server on linux machine with oc4j
    ThankYou
    Andrea

    Resolved!! Edwin, was a name resolution problem, as you say!
    My problem also was that bpel server is on a remote linux machine, so soap server url with localhost (and similar) is not accepted by designer
    The better solution for Bpel server soap is:
    http://MachineIP:9700
    So I can invoke bpel process, and also JDev WS (deployed on oc4j) with endpoint as http://machineName:9700 and http://localhost:9700
    Thank you
    Andrea

  • Response not coming back to ESB when calling BPEL process

    Hi,
    I am doing some demo,
    the actual process is, in ESB, I am reading a file and passing thsoe fiel contents to BPEL as SOAP service. In BPEL proecess, I processed the message and sending the response back to the ESB. When I deployed and check the process flow in the BPEL console, everything looks fine, I mena, it sending the response back to the ESB, where as in ESB process, I am not able to see the response.
    Is there any thing that I am missing?
    Thanks.

    Is the BPEL process a synchronous process?
    Also for performance reasons it it best to call BPEL process via the direct jca connector not SOAP.
    You do this by just selecting the BPEL process in the routing service going through the wizard. There is no need to creat a SOAP service. The good this about this is that in the ESB process it provides a link to the BPEL process.
    cheers
    James

Maybe you are looking for