XML message without encoding type

Hi,
Is there any possibility to generate the XML file without encoding?
Should convert <?xml version="1.0"; encoding="UTF-8"?> to <?xml version="1.0";?>. I have checked the blog and the answer was either Java mapping or XSLT mapping. Is it possible to handle in graphical mapping?
I am using the AS2 adapter to send the file to customer and External defination for the target message. Below are few information on the AS2 configuration:
Signing Algorithm: SHA-1
Encryption: 3DES
Your suggestion is highly appreciated.
Regards,
Vasantha

HI Vasantha,
It is not possible with Graphical Mapping you need to go either with JAVA or XSLT mapping.
/people/stefan.grube/blog/2007/02/02/remove-namespace-prefix-or-change-xml-encoding-with-the-xmlanonymizerbean
Cheers!!!
Naveen

Similar Messages

Sending non-SOAP XML message without using JMS

Hi, I would like to build application to exchange non-SOAP XML message without using JSM. Could you please tell me which Java Technology that can help doing this? Thanks in advance

to be more specific, could you please tell me any open source jaxm-like that support non-SOAP XML?

PI 7.1 XML messages are not getting archived.

Hi Experts,
Currently I am wotking with PI 7.1. I am trying to archive PI messages from PI Production server,and also maintianed the following parameters in SXMB_ADM.
ARCHIVE PERSIST_DURATION ASYNC 1 1
DELETION PERSIST_DURATION ASYNC 1 1
DELETION PERSIST_DURATION HISTORY 7 30
DELETION PERSIST_DURATION SYNC 2 0
DELETION PERSIST_DURATION_ERROR SYNC 3 1
Retention period
Retention Period for Asynchronous XML message in the Database
XML Messages Without Errors Awaiting Deletion 1
XML Messages Without Errors Awaiting Archiving 1
Retention Period for Synchronous XML message in the Database
XML Messages with Errors Awaiting Deletion 3
XML Messages Without Errors Awaiting Deletion 2
Retention Period for History Entries in the Database
History Entries for Deleted XML Messages 7
Messages are not getting archived.
When I execute the report "RSXMB_SHOW_REORG_STATUS"
I am geting the following output.
Msgs not in retention period (can be archived): 0
Msgs in retention period (cannot be archived): 88
Kindly suggest me what changes can be done so that PI messages will get archived from PI production server.
Regards
Naveen

Hi,
Please refer this thread.
[Deleting XML messages, database growing|Deleting XML messages, database growing]
Suresh

Error deserializing arguments, xml tag without a recognized type

I am trying to run a webservice created using Weblogic Workshop 8.1sp2 that communicates
with an ejb control. When I test in debug mode, I get the above error, specifically:
<detail>
<jwErr:jwErrorDetail xmlns:jwErr="http://www.bea.com/2002/04/jwErrorDetail/">
com.bea.wlw.runtime.core.request.RequestValidationException: Error deserializing
arguments.
Encountered an xml tag without a recognized type: the type must be declared with
an xsi:type attribute.
Caused by: com.bea.xml.marshal.XmlEncodingException: Encountered an xml tag with
out a recognized type: the type must be declared with an xsi:type attribute.
</detail>
I am passing a Request object to the jws method (to the ejb) that has a Collection
as an instance member. This Collection references objects of another type, Param
(code for both objects below). Before passing the object, I convert the Collection
to an array of objects. When I call the operation via a java client, I get the
above message.
In Workshop, I've included the Request and Param classes as the parameter xml
and the soap style is rpc. I've tested the ejb by itself and it is working fine.
Request.java:
import java.util.*;
public class Request implements java.io.Serializable
protected Collection params=null;
public Collection getParams()
{ return params; }
public void setParams(Collection data)
{ params=data; }
Param.java:
public class Param implements java.io.Serializable
private String name=null;
private Object value=null;
public String getName()
{ return name; }
public void setName(String data)
{ name = data; }
public Object getValue()
{ return value; }
public void setValue(Object data)
{ value=data; }
Here's the code from the jws:
public class MyWS implements com.bea.jws.WebService
* @common:control
private control.PSEjbControl psEJB;
static final long serialVersionUID = 1L;
* @common:operation
* @jws:parameter-xml
* include-java-types="mypackage.Request mypackage.Param"
* @jws:protocol soap-style="rpc"
public void addData(mypackage.Request arg0) throws java.rmi.RemoteException
System.out.println("arg0 : " + arg0);
psEJB.addData(arg0);
*Note: in the server console, arg0 comes through as null when called from my client.
Here's the bit from my client:
import weblogic.jws.proxies.*;
import org.openuri.www.encodedTypes.Request;
import org.openuri.www.encodedTypes.Param;
public void go(String wsdl) throws Exception {
MyWSSoap mw = null;
mw = new MyWS_Impl().getMyWSSoap();
Request req = new Request();
Collection reqColl = new ArrayList();
Param param1 = new Param();
param1.setName("NAME");
param1.setValue("Joe Tester");
Param param2 = new Param();
param2.setName("ADDRESS");
param2.setValue("345 Test Drive");
reqColl.add(param1);
reqColl.add(param2);
Object[] obs = reqColl.toArray();
req.setParams(obs);
mw.addData(req);
Not sure if this enough to go by. Please let me know if you need more information.
Any help is really appreciated. Thanks.

Hi Keith,
My only suggestion is to factor out the java.util.Collection (see the
docs here [1]) with either primitive types or XMLBeans [2].
Sorry, not much help. You might also ask your question in the workshop
[3] newsgroup.
Bruce
[1]
http://e-docs.bea.com/workshop/docs81/doc/en/integration/reference/refJavaClassConversion.html
[2]
http://e-docs.bea.com/workshop/docs81/doc/en/workshop/guide/xmlbeans/conXMLBeansSupportBuiltInSchemaTypes.html
[3]
http://newsgroups.bea.com/cgi-bin/dnewsweb?cmd=xover&group=weblogic.developer.interest.workshop
Keith wrote:
>
Hi Bruce, thanks for the reply. I set the operation for document-style soap and
still get the deserialization exception as mentioned in my original note. Below
is the wsdl. Note: in my original note, the problematic operation was addData()
which is now named addBusinessLocation(). As always, your help is greatly appreciated.
Keith
<?xml version="1.0" encoding="utf-8"?>

<definitions xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:conv="http://www.openuri.org/2002/04/soap/conversation/"
xmlns:cw="http://www.openuri.org/2002/04/wsdl/conversation/" xmlns:http="http://schemas.xmlsoap.org/wsdl/http/"
xmlns:jms="http://www.openuri.org/2002/04/wsdl/jms/" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/"
xmlns:s="http://www.w3.org/2001/XMLSchema" xmlns:s0="http://www.openuri.org/"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
targetNamespace="http://www.openuri.org/">
<types>
<s:schema elementFormDefault="qualified" targetNamespace="http://www.openuri.org/"
xmlns:s="http://www.w3.org/2001/XMLSchema" xmlns:ope="http://www.openuri.org/">
<s:element name="addBusinessLocation">
<s:complexType>
<s:sequence>
<s:element name="arg0" type="ope:Request" minOccurs="0"/>
</s:sequence>
</s:complexType>
</s:element>
<s:element name="addBusinessLocationResponse">
<s:complexType>
<s:sequence/>
</s:complexType>
</s:element>
<s:element name="getBusinessLocation">
<s:complexType>
<s:sequence/>
</s:complexType>
</s:element>
<s:element name="getBusinessLocationResponse">
<s:complexType>
<s:sequence>
<s:element name="getBusinessLocationResult" type="ope:Response" minOccurs="0"/>
</s:sequence>
</s:complexType>
</s:element>
<s:element name="Response" nillable="true" type="ope:Response"/>
<s:element name="repeat">
<s:complexType>
<s:sequence>
<s:element name="in" type="s:string" minOccurs="0"/>
</s:sequence>
</s:complexType>
</s:element>
<s:element name="repeatResponse">
<s:complexType>
<s:sequence>
<s:element name="repeatResult" type="s:string" minOccurs="0"/>
</s:sequence>
</s:complexType>
</s:element>
<s:element name="string" nillable="true" type="s:string"/>
<s:complexType name="Request">
<s:sequence>
<s:element name="Params" type="ope:Collection" minOccurs="0"/>
</s:sequence>
</s:complexType>
<s:complexType name="Collection">
<s:sequence>
<s:element name="item" type="s:anyType" nillable="true" minOccurs="0"
maxOccurs="unbounded"/>
</s:sequence>
</s:complexType>
<s:complexType name="Param">
<s:sequence>
<s:element name="Name" type="s:string" minOccurs="0"/>
<s:element name="Value" type="s:anyType" minOccurs="0"/>
</s:sequence>
</s:complexType>
<s:complexType name="Response">
<s:complexContent>
<s:extension base="ope:Request">
<s:sequence/>
</s:extension>
</s:complexContent>
</s:complexType>
</s:schema>
</types>
<message name="addBusinessLocationSoapIn">
<part name="parameters" element="s0:addBusinessLocation"/>
</message>
<message name="addBusinessLocationSoapOut">
<part name="parameters" element="s0:addBusinessLocationResponse"/>
</message>
<message name="getBusinessLocationSoapIn">
<part name="parameters" element="s0:getBusinessLocation"/>
</message>
<message name="getBusinessLocationSoapOut">
<part name="parameters" element="s0:getBusinessLocationResponse"/>
</message>
<message name="repeatSoapIn">
<part name="parameters" element="s0:repeat"/>
</message>
<message name="repeatSoapOut">
<part name="parameters" element="s0:repeatResponse"/>
</message>
<message name="getBusinessLocationHttpGetIn"/>
<message name="getBusinessLocationHttpGetOut">
<part name="Body" element="s0:Response"/>
</message>
<message name="repeatHttpGetIn">
<part name="in" type="s:string"/>
</message>
<message name="repeatHttpGetOut">
<part name="Body" element="s0:string"/>
</message>
<message name="getBusinessLocationHttpPostIn"/>
<message name="getBusinessLocationHttpPostOut">
<part name="Body" element="s0:Response"/>
</message>
<message name="repeatHttpPostIn">
<part name="in" type="s:string"/>
</message>
<message name="repeatHttpPostOut">
<part name="Body" element="s0:string"/>
</message>
<portType name="PublicServiceWSSoap">
<operation name="addBusinessLocation">
<input message="s0:addBusinessLocationSoapIn"/>
<output message="s0:addBusinessLocationSoapOut"/>
</operation>
<operation name="getBusinessLocation">
<input message="s0:getBusinessLocationSoapIn"/>
<output message="s0:getBusinessLocationSoapOut"/>
</operation>
<operation name="repeat">
<input message="s0:repeatSoapIn"/>
<output message="s0:repeatSoapOut"/>
</operation>
</portType>
<portType name="PublicServiceWSHttpGet">
<operation name="getBusinessLocation">
<input message="s0:getBusinessLocationHttpGetIn"/>
<output message="s0:getBusinessLocationHttpGetOut"/>
</operation>
<operation name="repeat">
<input message="s0:repeatHttpGetIn"/>
<output message="s0:repeatHttpGetOut"/>
</operation>
</portType>
<portType name="PublicServiceWSHttpPost">
<operation name="getBusinessLocation">
<input message="s0:getBusinessLocationHttpPostIn"/>
<output message="s0:getBusinessLocationHttpPostOut"/>
</operation>
<operation name="repeat">
<input message="s0:repeatHttpPostIn"/>
<output message="s0:repeatHttpPostOut"/>
</operation>
</portType>
<binding name="PublicServiceWSSoap" type="s0:PublicServiceWSSoap">
<soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="document"/>
<operation name="addBusinessLocation">
<soap:operation soapAction="http://www.openuri.org/addBusinessLocation"
style="document"/>
<input>
<soap:body use="literal"/>
</input>
<output>
<soap:body use="literal"/>
</output>
</operation>
<operation name="getBusinessLocation">
<soap:operation soapAction="http://www.openuri.org/getBusinessLocation"
style="document"/>
<input>
<soap:body use="literal"/>
</input>
<output>
<soap:body use="literal"/>
</output>
</operation>
<operation name="repeat">
<soap:operation soapAction="http://www.openuri.org/repeat" style="document"/>
<input>
<soap:body use="literal"/>
</input>
<output>
<soap:body use="literal"/>
</output>
</operation>
</binding>
<binding name="PublicServiceWSHttpGet" type="s0:PublicServiceWSHttpGet">
<http:binding verb="GET"/>
<operation name="getBusinessLocation">
<http:operation location="/getBusinessLocation"/>
<input>
<http:urlEncoded/>
</input>
<output>
<mime:mimeXml part="Body"/>
</output>
</operation>
<operation name="repeat">
<http:operation location="/repeat"/>
<input>
<http:urlEncoded/>
</input>
<output>
<mime:mimeXml part="Body"/>
</output>
</operation>
</binding>
<binding name="PublicServiceWSHttpPost" type="s0:PublicServiceWSHttpPost">
<http:binding verb="POST"/>
<operation name="getBusinessLocation">
<http:operation location="/getBusinessLocation"/>
<input>
<mime:content type="application/x-www-form-urlencoded"/>
</input>
<output>
<mime:mimeXml part="Body"/>
</output>
</operation>
<operation name="repeat">
<http:operation location="/repeat"/>
<input>
<mime:content type="application/x-www-form-urlencoded"/>
</input>
<output>
<mime:mimeXml part="Body"/>
</output>
</operation>
</binding>
<service name="PublicServiceWS">
<port name="PublicServiceWSSoap" binding="s0:PublicServiceWSSoap">
<soap:address location="http://localhost:8010/WebService/PublicServiceWS.jws"/>
</port>
<port name="PublicServiceWSHttpGet" binding="s0:PublicServiceWSHttpGet">
<http:address location="http://localhost:8010/WebService/PublicServiceWS.jws"/>
</port>
<port name="PublicServiceWSHttpPost" binding="s0:PublicServiceWSHttpPost">
<http:address location="http://localhost:8010/WebService/PublicServiceWS.jws"/>
</port>
</service>
</definitions>
Bruce Stephens <[email protected]> wrote:
Hi Keith,
As a quick test, you might try changing the protocol style to use
doc/lit (@jws:protocol soap-style="document") to see if this provides
another view on the real issue.
Could you post the generated WSDL?
Thanks,
Bruce
Keith wrote:
I am trying to run a webservice created using Weblogic Workshop 8.1sp2that communicates
with an ejb control. When I test in debug mode, I get the above error,specifically:
<detail>
<jwErr:jwErrorDetail xmlns:jwErr="http://www.bea.com/2002/04/jwErrorDetail/">
com.bea.wlw.runtime.core.request.RequestValidationException: Errordeserializing
arguments.
Encountered an xml tag without a recognized type: the type must bedeclared with
an xsi:type attribute.
Caused by: com.bea.xml.marshal.XmlEncodingException: Encountered anxml tag with
out a recognized type: the type must be declared with an xsi:type attribute.
</detail>
I am passing a Request object to the jws method (to the ejb) that hasa Collection
as an instance member. This Collection references objects of anothertype, Param
(code for both objects below). Before passing the object, I convertthe Collection
to an array of objects. When I call the operation via a java client,I get the
above message.
In Workshop, I've included the Request and Param classes as the parameterxml
and the soap style is rpc. I've tested the ejb by itself and it isworking fine.
Request.java:
import java.util.*;
public class Request implements java.io.Serializable
protected Collection params=null;
public Collection getParams()
{ return params; }
public void setParams(Collection data)
{ params=data; }
Param.java:
public class Param implements java.io.Serializable
private String name=null;
private Object value=null;
public String getName()
{ return name; }
public void setName(String data)
{ name = data; }
public Object getValue()
{ return value; }
public void setValue(Object data)
{ value=data; }
Here's the code from the jws:
public class MyWS implements com.bea.jws.WebService
* @common:control
private control.PSEjbControl psEJB;
static final long serialVersionUID = 1L;
* @common:operation
* @jws:parameter-xml
* include-java-types="mypackage.Request mypackage.Param"
* @jws:protocol soap-style="rpc"
public void addData(mypackage.Request arg0) throws java.rmi.RemoteException
System.out.println("arg0 : " + arg0);
psEJB.addData(arg0);
*Note: in the server console, arg0 comes through as null when calledfrom my client.
Here's the bit from my client:
import weblogic.jws.proxies.*;
import org.openuri.www.encodedTypes.Request;
import org.openuri.www.encodedTypes.Param;
public void go(String wsdl) throws Exception {
MyWSSoap mw = null;
mw = new MyWS_Impl().getMyWSSoap();
Request req = new Request();
Collection reqColl = new ArrayList();
Param param1 = new Param();
param1.setName("NAME");
param1.setValue("Joe Tester");
Param param2 = new Param();
param2.setName("ADDRESS");
param2.setValue("345 Test Drive");
reqColl.add(param1);
reqColl.add(param2);
Object[] obs = reqColl.toArray();
req.setParams(obs);
mw.addData(req);
Not sure if this enough to go by. Please let me know if you need moreinformation.
Any help is really appreciated. Thanks.

How to change the Encoding type of a XML

Hi all,
I'm having a XML(generated at run time) with UTF-8 Encoding. If I'm going to parse it, getting an error saying "*Document root element is missing*".
If I change the encoding to ANSI, it parses without error.
How can I change the encoding type of a documnet ?
Any comment welcome.
Kaushalya

There's no such thing as the "encoding of a String". If you produced a String from a sequence of bytes using the wrong encoding, you may not be able to repair that problem by hacking about in your code. You're better off to produce the String using the correct encoding in the first place. Read this for more information about XML and encodings as you appear to be misunderstanding basic concepts:
[http://skew.org/xml/tutorial/]

What is inbound XML message type and idoc type in Purchase Order response

Hi ,
We are on SRM 7 ECS , support pack SAPKIBKV08.
We have a process in which vendor will send a Purchase Order response which will be
converted to XML format by a middleware. This XML message will come to
SRM and post a POR. I want to do the EDI mapping for this XML message,
but there is no message type and idoc type in SRM for Purchase Order
response. How do I map my message type in SRM to the vendor sent fields
in middleware .
Please advise
Rgds
Sumendra

Hi,
You can process with XML without IDoc.
Vendor-> (XML) -> PI -> (XML) -> SRM.
Please check PurchaseOrderConfirmation_In in namespace "http://sap.com/xi/SRM/Procurement/Global".
http://esworkplace.sap.com
Regards,
Masa

Handling multiple XML message types in a webservice

My below scenario is
I have a webservice that receives XML messages from third party. The webservice populates 3 database tables through Mediator and DBAdapter from these XML files. Data for each table comes in a single XML file. How will I design the single werbservice to receive all the three different types of messages. eg: Customer, Order, OrderItem.
My WSDL is given below:
<?xml version= '1.0' encoding= 'UTF-8' ?>
<wsdl:definitions
name="receiveData"
targetNamespace="http://xmlns.oracle.com/sca/soapservice/receiveData"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
xmlns:inp1="http://xmlns.oracle.com/pcbpel/adapter/db/top/Order"
xmlns:tns="http://xmlns.oracle.com/sca/soapservice/ESTAProcessing/receiveData" >
<wsdl:types>
<schema xmlns="http://www.w3.org/2001/XMLSchema" >
<import namespace="http://xmlns.oracle.com/pcbpel/adapter/db/top/Order" schemaLocation="xsd/Order.xsd" />
</schema>
</wsdl:types>
<wsdl:message name="requestMessage">
<wsdl:part name="request" element="inp1:Order"/>
</wsdl:message>
<wsdl:portType name="execute_ptt">
<wsdl:operation name="execute">
<wsdl:input message="tns:requestMessage"/>
</wsdl:operation>
</wsdl:portType>
</wsdl:definitions>
Any similar example will be really good. Let me know if it does make sense. Here what I am looking for is whether a single operation can handle all three types of XML schema defintions and if yes how to put that in the WSDL

Technically you can do with XSD switch option however you should rethink towards your design of accepting three different message in single web service. specially the case you have taken customer and order.

File adapter - change of encoding in the header of the xml message

Hello!
I would like to change the encoding in the header of an xml message (sent to a a receiver file adapter)
from <?xml version="1.0" encoding="UTF-8" ?>
to <?xml version="1.0" encoding="ISO-8859-1" ?>
We have XI 3.0 with SP15.
Can anybody help me please?
Kind regards
Chris

Hi Chris,
An XSLT map can convert the encoding for you.
<?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
<xsl:output method='xml' encoding="ISO-8859-1"/>
<xsl:template match="@*|node()">
    <xsl:copy>
      <xsl:apply-templates select="@*|node()"/>
    </xsl:copy>
</xsl:template>
</xsl:stylesheet>
Thanks,
-Russ

Adding Encoding in XML header without mapping

Hi Gurus,
I am stuck in a situation where in a pass through scenario, I need to add encoding type in XML header.
Below is example -
Current Situation - <?xml version="1.0"?>
Expected result - <?xml version="1.0" encoding="UTF-8"?>
Can anybody help me in this regard? how to achieve this?
Regards
Vidhi S

Hi Vidhi
Use it in the below way in the receiver adapter.
Module name: AF_Modules/XMLAnonymizerBean
Parameter name: anonymizer.encoding
This will work. I have tested already.

How to define message without parts in WSDL?

Hi all,
I don't know if it is possible, but I would like to create a message without defining part/type.
Really what I want to accomplish is to avoid the part definition below in my .wsdl file.
<message name="RCMR_IN000002NR01Input">
<part name="param0" type="xsd:string"/>
</message>
<message name="RCMR_IN000002NR01Output">
<part name="param0" type="xsd:string"/>
</message>
So I would like to something akind to
<message name="RCMR_IN000002NR01Input">
</message>
<message name="RCMR_IN000002NR01Output">
</message>
I try to assign a string to RCMR_IN000002NR01Input (I am using rpc literal). At the moment the partnerlink receiving my message gets confused by the param0 part of the XML.
I hope that description of my issue was not to cryptic to be understandable. Please feel free to ask clarifying questions.
Any help is appreciated.
Regards,
Aagaard
Edited by: Aagaard on Oct 8, 2008 8:42 AM
Maybe I should try to elaborate on my use case.
I pick up a SOAP message from a JMS queue (well, topic really). The message is a domain specific type. I get the content of the message as a string and assign it to a variable with a param0 of type string.
I then use the contains function to determine which partnerlink to invoke for a given message.
The invokation is succesful seen from BPEL.
However, the receiving systems receives my message including the original SOAP envelope - AND including a new BPEL generated SOAP envelope :-(
This is addition to the following code which was the concern of my original post:
<part xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" name="param0">
<param0 xmlns="" xmlns:def="http://www.w3.org/2001/XMLSchema" xsi:type="def:string" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
So anybody have any ideas as to how to get rid of unnecessary SOAP envelope and that irritating param0?

Hi again,
Srin, you were right. I did have a namespace issue. Getting that resolved however, introduced a new error.
My BPEL process invokes the remote partner, delivers the payload, the remote partner sends back a meaningful response, but no BPEL instance is shown in the BPEL console.
In the <oracle home>/opmn/logs I find the following errors:
ORABPEL-05002
Message handle error.
An exception occurred while attempting to process the message "com.collaxa.cube.engine.dispatch.message.invoke.InvokeInstanceMessage"; the exception is: Exception not handled by the Collaxa Cube system.
An unhandled exception has been thrown in the Collaxa Cube system. The exception reported is: "java.lang.NullPointerException
And
Exception: java.lang.NullPointerException
Handled As: com.collaxa.cube.CubeException
+] -> [java.lang.NullPointerException: null]+
ORABPEL-00000
Exception not handled by the Collaxa Cube system.
An unhandled exception has been thrown in the Collaxa Cube system. The exception reported is: "java.lang.NullPointerException
This seems strange to me. It seems that even if the meaningfull answer from the partner link is lost enroute I should still get a response in BPEL (maybe just null). My next step will be to try and set up a TCP Monitor between the partnerlink server and the BPEL server.
Any thoughts, hints, ideas and solutions are very welcome.
Will report on progress
Regard,
Aagaard
Edited by: Aagaard on Oct 10, 2008 10:18 AM
Update:
My current thinking is that I have a problem with my message types. The problem is definitely in the way BPEL handles the response from the partnerlink. The nullpointer exception may suggest that I am trying to assign the return payload to an incompatible type. I don't know if it could be an issue if the partnerlink response is some specific type while I excpect a string?
Anyway here's what my wsdl looks like now:
<?xml version="1.0" encoding="UTF-8"?>
<definitions name="RCMR_AR000002NR01"
targetNamespace="http://com.scandihealth.ccs.webservices.messaging.common/CCSMessageServiceRemote.wsdl"
xmlns="http://schemas.xmlsoap.org/wsdl/"
xmlns:tns="http://com.scandihealth.ccs.webservices.messaging.common/CCSMessageServiceRemote.wsdl"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" >
<documentation>
WSDL for Service: CCSMessageServiceRemote, generated by Oracle WSDL toolkit (version: 1.1)
</documentation>
<types>
<schema targetNamespace="http://schemas.xmlsoap.org/wsdl/" xmlns:tns="http://com.scandihealth.ccs.webservices.messaging.common/CCSMessageServiceRemote.xsd" xmlns="http://www.w3.org/2001/XMLSchema" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<element name="msgInputOutput" type="xsd:string"/>
</schema>
</types>
<message name="RCMR_IN000002NR01InputOutput">
<part name="param0" element="msgInputOutput"/>
</message>
<portType name="CCSMessageServiceRemotePortType">
<operation name="RCMR_IN000002NR01">
<input message="tns:RCMR_IN000002NR01InputOutput"/>
<output message="tns:RCMR_IN000002NR01InputOutput"/>
</operation>
</portType>
<binding name="CCSMessageServiceRemoteBinding" type="tns:CCSMessageServiceRemotePortType">
<soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="rpc"/>
<operation name="RCMR_IN000002NR01">
<soap:operation soapAction="urn:com-scandihealth-ccs-webservices-messaging-common-CCSMessageServiceRemote/RCMR_IN000002NR01"/>
<input>
<soap:body use="literal" encodingStyle="http://schemas.xmlsoap.org/soap/literal/" namespace="urn:com-scandihealth-ccs-webservices-messaging-common-CCSMessageServiceRemote" />
</input>
<output>
<soap:body use="literal" encodingStyle="http://schemas.xmlsoap.org/soap/literal/" namespace="urn:com-scandihealth-ccs-webservices-messaging-common-CCSMessageServiceRemote"/>
</output>
</operation>
</binding>
<service name="CCSMessageServiceRemote">
<port name="CCSMessageServiceRemotePort" binding="tns:CCSMessageServiceRemoteBinding">
<soap:address location="http://.../HL7Receive_servlet_WS/WS"/>
</port>
</service>
</definitions>
My assignment / invokation looks like this:
<assign name="CreateInputParamGenerateMessage">
<copy>
<from variable="getContentAsString"/>
<to variable="RCMR_IN000002NR01Input" part="param0"/>
</copy>
</assign>
<invoke name="InsertOperation"
partnerLink="RCMR_AR000002NR01"
portType="ns6:CCSMessageServiceRemotePortType"
operation="RCMR_IN000002NR01"
inputVariable="RCMR_IN000002NR01Input"
outputVariable="RCMR_IN000002NR01Output"/>

Read XML message from a CLOB

We are currently receiving XML messages from a business partner that goes
through a transformation/parser first to make sure the xml document was
in MISMO form (Mortgage Industry Standard Message Organization). Then the
document is stored in a clob in a table. The document is stored Without
the tags. We are storing these XML messages into a CLOB datatype for
later processing. I want to read the CLOB and then parse out the
individual fields to store into a table. What is the best way to
accomplish this in PL/SQL? Here is one sample record:
<MORTGAGEDATA>
<APPLICATION LoanPurposeType="OTHER">
<LenderCaseIdentifier>3631681</LenderCaseIdentifier>
<LendersBranchIdentifier>2966448</LendersBranchIdentifier>
</APPLICATION>
<PROPERTY PropertyUsageType="Primary">
<Address1>1335 test</Address1>
<City>las cruces</City>
<State>NM</State>
<PostalCode>88001</PostalCode>
</PROPERTY>
<SUBJECTPROPERTY>
<SubjectPropertyEstimatedValueAmount>69000</SubjectPropertyEstimatedValueAmount>
</SUBJECTPROPERTY>
<BORROWERRECONCILEDLIABILITY LiabilityType="HelocSubjectProperty">
<LiabilityUnpaidBalanceAmount>0</LiabilityUnpaidBalanceAmount>
<LiabilityMonthlyPaymentAmount>0</LiabilityMonthlyPaymentAmount>
</BORROWERRECONCILEDLIABILITY>
<BORROWERRECONCILEDLIABILITY LiabilityType="MortgageLoanSubjectProperty">
<LiabilityUnpaidBalanceAmount>0</LiabilityUnpaidBalanceAmount>
</BORROWERRECONCILEDLIABILITY>
<BORROWER>
<FirstName>scooby</FirstName>
<MiddleName/>
<LastName>doo</LastName>
<NameSuffix/>
<MothersMaidenName>velma</MothersMaidenName>
</BORROWER>
</MORTGAGEDATA>
NOTE: I have tried to use DBMS_XMLQUERY and it comes out like this using a
stored procedure called printclob: When I do this the data is put into
one field called xml_app_msg. The problem is how do I reference the
individual fields like FirstName and so on to store in another table? Can
I apply a stylesheet and if so, how?
Or do I create an object type called xml_app_msg with the fields lastname
and so on?
-- The table is raw_xml_msg_tbl and the field with the stored infomation is
xml_app_msg.
set serveroutput on size 50000
declare
queryCtx DBMS_XMLquery.ctxType;
result CLOB;
begin
queryCtx := DBMS_XMLQuery.newContext('select xml_app_msg from raw_xml_msg_tbl where app_id = :APP_ID');
-- DBMS_XMLQuery.clearBindValue(queryCtx);
DBMS_XMLQuery.setBindValue(queryCtx,'APP_ID','LT1001');
-- get the result..!
result := DBMS_XMLQuery.getXML(queryCtx);
-- Now you can use the result to put it in tables/send as messages..
printClobOut(result);
DBMS_XMLQuery.closeContext(queryCtx); -- you must close the query handle..
end;
OUTPUT:
<?xml version = '1.0'?>
<ROWSET>
<ROW num="1">
<XML_APP_MSG><MORTGAGEDATA>
<BORROWER>
<FirstName>Falls</FirstName>
<MiddleName/>
<LastName>Water</LastName>
<NameSuffix/>
<SSN>123-45-6789</SSN>
</BORROWER>
</MORTGAGEDATA>
</XML_APP_MSG>
</ROW>
</ROWSET>
null

I parse the XML doc into a domdocument and then loop through using xpath.valueof to pull the individual values from the nodes and then build a generic insert. It works quite well with a small number of columns. I'm not sure how it would work with a lot of columns. You can get code examples from Steve Muench's book "Developing Oracle XML Applications".

XML message as input for webservice gives deserialization error

Hi,
jDeveloper 10.1.3
BPEL PM 10.1.2.0.2
Carrental example
Problem:
For the Business Rule Engine I did the Carrental XML example. Based on the java application that connects to the BR engine, I created a webservice in jDeveloper and deployed it to my localhost AS 10.1.3. The webservice has a testRule method that accepts a String buf as input. For now, the only thing the webservice does is return a 'do nothing' string. This works fine:
When deployed the testpage generates the following SOAP message:
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Body xmlns:ns1="http://carrental/types/">
<ns1:testRuleElement>
<ns1:buf>my xml message</ns1:buf>
</ns1:testRuleElement>
</soap:Body>
</soap:Envelope>
The SOAP response is:
<?xml version="1.0" encoding="UTF-8"?>
<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:ns0="http://carrental/types/"><env:Body><ns0:testRuleResponseElement><ns0:result>do nothing...</ns0:result></ns0:testRuleResponseElement></env:Body></env:Envelope>
In BPEL Designer I create a new asynchronous process ValidateBR, with a partnerlink for the webservice, based on the following WSDL file:
<definitions
name="Rent"
targetNamespace="http://carrental/"
xmlns="http://schemas.xmlsoap.org/wsdl/"
xmlns:tns="http://carrental/"
xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/"
xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/"
xmlns:tns0="http://carrental/types/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
>
<types>
<schema xmlns="http://www.w3.org/2001/XMLSchema" targetNamespace="http://carrental/types/"
elementFormDefault="qualified" xmlns:tns="http://carrental/types/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:soap11-enc="http://schemas.xmlsoap.org/soap/encoding/">
<complexType name="testRule">
<sequence>
<element name="buf" type="string" nillable="true"/>
</sequence>
</complexType>
<complexType name="testRuleResponse">
<sequence>
<element name="result" type="string" nillable="true"/>
</sequence>
</complexType>
<complexType name="version">
<sequence/>
</complexType>
<complexType name="versionResponse">
<sequence>
<element name="result" type="string" nillable="true"/>
</sequence>
</complexType>
<element name="testRuleElement" type="tns:testRule"/>
<element name="testRuleResponseElement" type="tns:testRuleResponse"/>
<element name="versionElement" type="tns:version"/>
<element name="versionResponseElement" type="tns:versionResponse"/>
</schema>
</types>
<message name="Rent_testRule">
<part name="parameters" element="tns0:testRuleElement"/>
</message>
<message name="Rent_testRuleResponse">
<part name="parameters" element="tns0:testRuleResponseElement"/>
</message>
<message name="Rent_version">
<part name="parameters" element="tns0:versionElement"/>
</message>
<message name="Rent_versionResponse">
<part name="parameters" element="tns0:versionResponseElement"/>
</message>
<portType name="Rent">
<operation name="testRule">
<input message="tns:Rent_testRule"/>
<output message="tns:Rent_testRuleResponse"/>
</operation>
<operation name="version">
<input message="tns:Rent_version"/>
<output message="tns:Rent_versionResponse"/>
</operation>
</portType>
<binding name="RentSoapHttp" type="tns:Rent">
<soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
<operation name="testRule">
<soap:operation soapAction="http://carrental//testRule"/>
<input>
<soap:body use="literal" parts="parameters"/>
</input>
<output>
<soap:body use="literal" parts="parameters"/>
</output>
</operation>
<operation name="version">
<soap:operation soapAction="http://carrental//version"/>
<input>
<soap:body use="literal" parts="parameters"/>
</input>
<output>
<soap:body use="literal" parts="parameters"/>
</output>
</operation>
</binding>
<service name="Rent">
<port name="RentSoapHttpPort" binding="tns:RentSoapHttp">
<soap:address location="http://localhost:7780/Rules-rent-context-root/RentSoapHttpPort"/>
</port>
</service>
</definitions>
I defined the process variable inputVariable to be defined based on the carrental.xsd schema. I assign the inputVariable to the 'buf' parameter of the webservice as shown below in the ValidateBR.bpel

<process name="ValidateBR" targetNamespace="http://xmlns.oracle.com/ValidateBR" xmlns="http://schemas.xmlsoap.org/ws/2003/03/business-process/" xmlns:xp20="http://www.oracle.com/XSL/Transform/java/oracle.tip.pc.services.functions.Xpath20" xmlns:bpws="http://schemas.xmlsoap.org/ws/2003/03/business-process/" xmlns:ns1="http://rules.oracle.com/carrental" xmlns:ldap="http://schemas.oracle.com/xpath/extension/ldap" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:ns3="http://carrental/types/" xmlns:ns2="http://carrental/" xmlns:client="http://xmlns.oracle.com/ValidateBR" xmlns:bpelx="http://schemas.oracle.com/bpel/extension" xmlns:ora="http://schemas.oracle.com/xpath/extension" xmlns:orcl="http://www.oracle.com/XSL/Transform/java/oracle.tip.pc.services.functions.ExtFunc">
<partnerLinks>
<partnerLink name="client" partnerLinkType="client:ValidateBR" myRole="ValidateBRProvider" partnerRole="ValidateBRRequester"/>
<partnerLink name="CheckBR" partnerRole="Rent_Role" partnerLinkType="ns2:Rent_PL"/>
</partnerLinks>
<variables>
<variable name="inputVariable" messageType="client:ValidateBRRequestMessage"/>
<variable name="outputVariable" messageType="client:ValidateBRResponseMessage"/>
<variable name="InvokeValidateBR_testRule_InputVariable" messageType="ns2:Rent_testRule"/>
<variable name="InvokeValidateBR_testRule_OutputVariable" messageType="ns2:Rent_testRuleResponse"/>
</variables>
<sequence name="main">
<receive name="receiveInput" partnerLink="client" portType="client:ValidateBR" operation="initiate" variable="inputVariable" createInstance="yes"/>
<assign name="Assign_1">
<copy>
<from variable="inputVariable" part="payload" query="/ns1:repository"/>
<to variable="InvokeValidateBR_testRule_InputVariable" part="parameters" query="/ns3:testRuleElement/ns3:buf"/>
</copy>
</assign>
<invoke name="InvokeValidateBR" partnerLink="CheckBR" portType="ns2:Rent" operation="testRule" inputVariable="InvokeValidateBR_testRule_InputVariable" outputVariable="InvokeValidateBR_testRule_OutputVariable"/>
<invoke name="callbackClient" partnerLink="client" portType="client:ValidateBRCallback" operation="onResult" inputVariable="outputVariable"/>
</sequence>
</process>
When I deploy the process and initiate a testinstance from the BPEL console, the assign looks as follows:
<InvokeValidateBR_testRule_InputVariable>
<part name="parameters" >
<testRuleElement>
<buf>
<driver>
<driver-license-number>15-PS-FZ</driver-license-number>
<name>Rob de Haan</name>
<age>39</age>
<vehicle-type>Saab</vehicle-type>
<license-type>B</license-type>
<pre-convictions>0</pre-convictions>
<pre-accidents>0</pre-accidents>
<able-to-drive>true</able-to-drive>
</driver>
</buf>
</testRuleElement>
</part>
</InvokeValidateBR_testRule_InputVariable>
The InvokeValidateBR shows the following error:
<remoteFault>
<part name="code" >
<code>Client</code>
</part>
<part name="summary" >
<summary>when invoking endpointAddress 'http://localhost:7780/Rules-rent-context-root/RentSoapHttpPort', caught exception while handling request: deserialization error: unexpected XML reader state. expected: END but found: START: {http://rules.oracle.com/carrental}driver</summary>
</part>
<part name="detail" >
<detail>AxisFault faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Client faultSubcode: faultString: caught exception while handling request: deserialization error: unexpected XML reader state. expected: END but found: START: {http://rules.oracle.com/carrental}driver faultActor: faultNode: faultDetail: {http://xml.apache.org/axis/}stackTrace:caught exception while handling request: deserialization error: unexpected XML reader state. expected: END but found: START: {http://rules.oracle.com/carrental}driver at org.collaxa.thirdparty.apache.axis.message.SOAPFaultBuilder.createFault(SOAPFaultBuilder.java:221) at org.collaxa.thirdparty.apache.axis.message.SOAPFaultBuilder.endElement(SOAPFaultBuilder.java:128) at org.collaxa.thirdparty.apache.axis.encoding.DeserializationContext.endElement(DeserializationContext.java:1083) at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown Source) at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanEndElement(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source) at javax.xml.parsers.SAXParser.parse(Unknown Source) at org.collaxa.thirdparty.apache.axis.encoding.DeserializationContext.parse(DeserializationContext.java:226) at org.collaxa.thirdparty.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:645) at org.collaxa.thirdparty.apache.axis.Message.getSOAPEnvelope(Message.java:424) at org.collaxa.thirdparty.apache.axis.client.Call.invokeEngine(Call.java:2754) at org.collaxa.thirdparty.apache.axis.client.Call.invoke(Call.java:2715) at org.collaxa.thirdparty.apache.axis.client.Call.invoke(Call.java:1737) at com.collaxa.cube.ws.wsif.providers.axis.WSIFOperation_ApacheAxis.invokeAXISMessaging(WSIFOperation_ApacheAxis.java:2113) at com.collaxa.cube.ws.wsif.providers.axis.WSIFOperation_ApacheAxis.invokeRequestResponseOperation(WSIFOperation_ApacheAxis.java:1611) at com.collaxa.cube.ws.wsif.providers.axis.WSIFOperation_ApacheAxis.executeRequestResponseOperation(WSIFOperation_ApacheAxis.java:1083) at com.collaxa.cube.ws.WSIFInvocationHandler.invoke(WSIFInvocationHandler.java:452) at com.collaxa.cube.ws.WSInvocationManager.invoke2(WSInvocationManager.java:327) at com.collaxa.cube.ws.WSInvocationManager.invoke(WSInvocationManager.java:189) at com.collaxa.cube.engine.ext.wmp.BPELInvokeWMP.__invoke(BPELInvokeWMP.java:601) at com.collaxa.cube.engine.ext.wmp.BPELInvokeWMP.__executeStatements(BPELInvokeWMP.java:317) at com.collaxa.cube.engine.ext.wmp.BPELActivityWMP.perform(BPELActivityWMP.java:188) at com.collaxa.cube.engine.CubeEngine.performActivity(CubeEngine.java:3408) at com.collaxa.cube.engine.CubeEngine.handleWorkItem(CubeEngine.java:1836) at com.collaxa.cube.engine.dispatch.message.instance.PerformMessageHandler.handleLocal(PerformMessageHandler.java:75) at com.collaxa.cube.engine.dispatch.DispatchHelper.handleLocalMessage(DispatchHelper.java:166) at com.collaxa.cube.engine.dispatch.DispatchHelper.sendMemory(DispatchHelper.java:252) at com.collaxa.cube.engine.CubeEngine.endRequest(CubeEngine.java:5438) at com.collaxa.cube.engine.CubeEngine.createAndInvoke(CubeEngine.java:1217) at com.collaxa.cube.engine.delivery.DeliveryService.handleInvoke(DeliveryService.java:511) at com.collaxa.cube.engine.ejb.impl.CubeDeliveryBean.handleInvoke(CubeDeliveryBean.java:335) at ICubeDeliveryLocalBean_StatelessSessionBeanWrapper16.handleInvoke(ICubeDeliveryLocalBean_StatelessSessionBeanWrapper16.java:1796) at com.collaxa.cube.engine.dispatch.message.invoke.InvokeInstanceMessageHandler.handle(InvokeInstanceMessageHandler.java:37) at com.collaxa.cube.engine.dispatch.DispatchHelper.handleMessage(DispatchHelper.java:125) at com.collaxa.cube.engine.dispatch.BaseScheduledWorker.process(BaseScheduledWorker.java:70) at com.collaxa.cube.engine.ejb.impl.WorkerBean.onMessage(WorkerBean.java:86) at com.evermind.server.ejb.MessageDrivenBeanInvocation.run(MessageDrivenBeanInvocation.java:123) at com.evermind.server.ejb.MessageDrivenHome.onMessage(MessageDrivenHome.java:755) at com.evermind.server.ejb.MessageDrivenHome.run(MessageDrivenHome.java:928) at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:186) at java.lang.Thread.run(Thread.java:534) {http://xml.apache.org/axis/}hostname:NL-GRH-L120981 </detail>
</part>
</remoteFault>
FYI: the webservice only contains a return "do nothing"
Question:
What is the proper way to assign an XML message to the web service?
Any help would be appreciated.
Rob
Message was edited by:
[email protected]

Hi,
Reading only is not possible..
I will be still more clear in my question this time..
I have deployed my bpel. My receiveInputVariable is of type xsd:string.
So when i run the bpel in my console, i will be asked to give input as string data.
So when i go to the XMLView, it will be like this.
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
     <soap:Body xmlns:ns1="http://xmlns.oracle.com/Sabari_POC_Appln/DOM_Parser/ConvertToBLOB">
          <ns1:process>
               <ns1:input></ns1:input>
</ns1:process>
</soap:Body>
</soap:Envelope>
Now, i am going to give my input like this. --- which leads to error.
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
     <soap:Body xmlns:ns1="http://xmlns.oracle.com/Sabari_POC_Appln/DOM_Parser/ConvertToBLOB">
          <ns1:process>
               <ns1:input>
*<?xml version="1.0" encoding="UTF-8"?>*
*<projects>*
*<project id = "BP001">*
*<name>Banking Project</name>*
*<start-date>Jan 10 1999</start-date>*
*<end-date>Jan 10 2003</end-date>*
*</project>*
*<project id = "TP001">*
*<name>Telecommunication Project</name>*
*<start-date>March 20 1999</start-date>*
*<end-date>July 30 2004</end-date>*
*</project>*
*<project id = "PP001">*
*<name>Portal Project</name>*
*<start-date>Dec 10 1998</start-date>*
*<end-date>March 10 2006</end-date>*
*</project>*
*</projects>*
</ns1:input>
</ns1:process>
</soap:Body>
</soap:Envelope>
This xml is not accepted as string input.. so kindly suggest me some other solution.
I also tried.. like.. making my receiveInputVariable of type xsd:anyType, it also dint help. same error occurred.
Thanks,
Sabarisri. N
Edited by: Sabarisri N on Jul 20, 2011 1:03 PM

XML message mapping considering idoc message variant

Dear Experts,
I am very new to PI. I am working on a scenario where I need to map VGON_OUT xml message from SNC system to ORDRSP.ORDERS05 inbound idoc of ECC 6.0 system.
The issue is :
In the inbound partner profile in ECC there are two ordersp message types. one with message variant SMI and another without any message variant.
Both of them are using different process codes for processing.
So my question is how to map the VGON_out xml message in PI?
Please note: the key difference is the idoc message variant.
There is no way to merge both of these message types as their function is serving two different purposes.
I have attached the xml file and the screenshot of the partner profile here.
Any suggestion or reference link or document would be deeply appreciated.
Thanks in advance.
Praty

Hi Pratyusa,
Did you try with different partner profiles for each ORDRSP?
Regards,
Krupa

Send XML Message via HTTP and Receive Response

Hello,
We have a scenario where we need to update Currency Exchange Rates in R/3 via a 3rd party called Oanda. I'd like to use XI for this Interface, if possible.
Basically, we need to send XML over HTTP. Here's the URL and the XML we need to use for our POST (I'll need to perform the look-up for about 15 currency codes - I plan on using a BPM process to loop through each currency code specified in a flat file):
http://www.oanda.com/cgi-bin/fxml/fxml?fxmlrequest=<CONVERT><CLIENT_ID>TestAccount1</CLIENT_ID><EXCH>USD</EXCH><EXPR>CAD</EXPR><DATE>03/25/2008</DATE></CONVERT>
And the reponse looks like this:
<RESPONSE>
<EXPR>CAD</EXPR>
<EXCH>USD</EXCH>
<AMOUNT>1</AMOUNT>
<NPRICES>1</NPRICES>
<CONVERSION>
    <DATE>Mon, 24 Mar 2008 20:00:00 GMT</DATE>
    <ASK>1.0257</ASK>
    <BID>1.0251</BID>
</CONVERSION>
</RESPONSE>
I plan on mapping each reponse to BAPI_EXCHRATE_CREATEMULTIPLE, using BPM.
So my question is this: Should I use the HTTP adapter for the out going POST to Oanda? If so, would the HTTP adapter be consider the sender or the receiver? Also, how would the XML message be automatically appended to the end of the URL (i.e., after the fxmlrequest parameter)? I guess I'm a little confused on how to use the HTTP adapter... Are there any blogs that discuss this type of scenario?
Thanks,
Matt

Hi guys,
I have few concerns for setting up this scenario.
1). I have created a data type for request mapping, and teste the mapping.
The output looks like below:
<?xml version="1.0" encoding="UTF-8" ?>
<ns1:MT_CONVERT xmlns:ns1="http://test.com/ExchngRate">
   <CONVERT>
     <CLIENT_ID>test</CLIENT_ID>
     <EXPR>CAD</EXPR>
     <EXCH>USD</EXCH>
     <DATE>10/21/2009</DATE>
     <AMOUNT>1</AMOUNT>
   </CONVERT>
</ns1:MT_CONVERT>
How to pass only
<CONVERT>
     <CLIENT_ID>test</CLIENT_ID>
     <EXPR>CAD</EXPR>
     <EXCH>USD</EXCH>
     <DATE>10/21/2009</DATE>
     <AMOUNT>1</AMOUNT>
   </CONVERT>
to the receiver HTTP adapter.
2) I am using URL address in the receiver HTTP adapter.
Target Host: www.oanda.com
Path Prefix: cgi-bin/fxml/fxml?fxmlrequest=
What is will be Service Number?
Looking forward for you help. Your help is greatly appreciated.
Thanks,
Namadev
Edited by: Namadev Chillal on Oct 21, 2009 5:35 PM

How to map a complex XML message onto a flattened XSD for multi line insert

Hi Experts.
I have a webservice in my composite that takes an xml message that contains repeating complex type elements. The XSD is as follows:
<?xml version= '1.0' encoding= 'UTF-8' ?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:XxInt003Stg="http://www.somewhere.co.uk/xxx/integration/int003Stage"
targetNamespace="http://www.somewhere.co.uk/xxx/integration/int003Stage" elementFormDefault="qualified">
<xsd:complexType name="InterfaceFileType">
<xsd:sequence>
<xsd:element name="FileName" type="xsd:string"/>
<xsd:element name="FileSource" type="xsd:string"/>
<xsd:element name="FileIdentifier" type="xsd:integer"/>
<xsd:element name="InterfaceInvoices" type="XxInt003Stg:InterfaceInvoicesType"/>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="InterfaceInvoicesType">
<xsd:sequence>
<xsd:element name="InterfaceInvoice" type="XxInt003Stg:InterfaceInvoiceType"
maxOccurs="unbounded"/>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="InterfaceInvoiceType">
<xsd:sequence>
<xsd:element name="SupplierNumber" type="xsd:string"/>
<xsd:element name="SupplierSite" type="xsd:string"/>
<xsd:element name="InvoiceNumber" type="xsd:string"/>
<xsd:element name="InterfaceInvoiceLines">
<xsd:complexType>
<xsd:complexContent>
<xsd:extension base="XxInt003Stg:InterfaceInvoiceLinesType">
<xsd:sequence>
<xsd:element name="InterfaceInvoiceLine"
type="XxInt003Stg:InterfaceInvoiceLineType"
maxOccurs="unbounded"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="InterfaceInvoiceLinesType"/>
<xsd:complexType name="InterfaceInvoiceLineType">
<xsd:sequence>
<xsd:element name="LineAmount" type="xsd:decimal" nillable="false"/>
<xsd:element name="TaxAmount" type="xsd:decimal"/>
<xsd:element name="BusinessEntityReference" type="xsd:string"/>
<xsd:element name="AccountNumber" type="xsd:string"/>
</xsd:sequence>
</xsd:complexType>
<xsd:element name="InterfacePayload">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="InterfaceFiles" type="XxInt003Stg:InterfaceFileType"
maxOccurs="unbounded"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:schema>
When I try to push this through the database adapter after mapping the fields it inserts multiple rows but they are all the same values. I have put a for-each XSLT construct based on the lowest element in the XSD (Invoice Line) and allocated that at various places on the target tree structure but with no success.
The XSLT is as follows:
<xsl:template match="/">
<top:XxInt003InterfaceInvoiceStgCollection>
<top:XxInt003InterfaceInvoiceStg>
<top:fileName>
<xsl:value-of select="/inp1:InterfacePayload/inp1:InterfaceFiles/inp1:FileName"/>
</top:fileName>
<top:fileSource>
<xsl:value-of select="/inp1:InterfacePayload/inp1:InterfaceFiles/inp1:FileSource"/>
</top:fileSource>
<top:fileIdentifier>
<xsl:value-of select="/inp1:InterfacePayload/inp1:InterfaceFiles/inp1:FileIdentifier"/>
</top:fileIdentifier>
<top:supplierNumber>
<xsl:value-of select="/inp1:InterfacePayload/inp1:InterfaceFiles/inp1:InterfaceInvoices/inp1:InterfaceInvoice/inp1:SupplierNumber"/>
</top:supplierNumber>
<top:supplierSite>
<xsl:value-of select="/inp1:InterfacePayload/inp1:InterfaceFiles/inp1:InterfaceInvoices/inp1:InterfaceInvoice/inp1:SupplierSite"/>
</top:supplierSite>
<top:invoiceNumber>
<xsl:value-of select="/inp1:InterfacePayload/inp1:InterfaceFiles/inp1:InterfaceInvoices/inp1:InterfaceInvoice/inp1:InvoiceNumber"/>
</top:invoiceNumber>
<xsl:for-each select="/inp1:InterfacePayload/inp1:InterfaceFiles/inp1:InterfaceInvoices/inp1:InterfaceInvoice/inp1:InterfaceInvoiceLines/inp1:InterfaceInvoiceLine">
<top:lineAmount>
<xsl:value-of select="/inp1:InterfacePayload/inp1:InterfaceFiles/inp1:InterfaceInvoices/inp1:InterfaceInvoice/inp1:InterfaceInvoiceLines/inp1:InterfaceInvoiceLine/inp1:LineAmount"/>
</top:lineAmount>
</xsl:for-each>
<top:taxAmount>
<xsl:value-of select="/inp1:InterfacePayload/inp1:InterfaceFiles/inp1:InterfaceInvoices/inp1:InterfaceInvoice/inp1:InterfaceInvoiceLines/inp1:InterfaceInvoiceLine/inp1:TaxAmount"/>
</top:taxAmount>
<top:businessEntityReference>
<xsl:value-of select="/inp1:InterfacePayload/inp1:InterfaceFiles/inp1:InterfaceInvoices/inp1:InterfaceInvoice/inp1:InterfaceInvoiceLines/inp1:InterfaceInvoiceLine/inp1:BusinessEntityReference"/>
</top:businessEntityReference>
<top:accountNumber>
<xsl:value-of select="/inp1:InterfacePayload/inp1:InterfaceFiles/inp1:InterfaceInvoices/inp1:InterfaceInvoice/inp1:InterfaceInvoiceLines/inp1:InterfaceInvoiceLine/inp1:AccountNumber"/>
</top:accountNumber>
</top:XxInt003InterfaceInvoiceStg>
</top:XxInt003InterfaceInvoiceStgCollection>
</xsl:template>
I am sure this is just something fundemantal I am doing, is it something to do with the inp1 bit of the XSLT? I get the feeling this should be looping somehow?
Thanks
Keith

Hi,
as I understand you try to transform 'InterfacePayload' (your XSD - just easier to read here)
InterfacePayload (1:1)
-- InterfaceFiles (1:N)
---- FileName (1:1)
---- FileSource (1:1)
---- FileIdentifier (1:1)
---- InterfaceInvoices (1:1)
------ InterfaceInvoice (1:N)
-------- SupplierNumber (1:1)
-------- SupplierSite (1:1)
-------- InvoiceNumber (1:1)
-------- InterfaceInvoiceLines (1:1)
---------- InterfaceInvoiceLine (1:N)
------------ LineAmount (1:1)
------------ TaxAmount (1:1)
------------ BusinessEntityReference (1:1)
------------ AccountNumber (1:1)
to 'XxInt003InterfaceInvoiceStgCollection' (extracted from your XSLT)
XxInt003InterfaceInvoiceStgCollection (1:1)
-- XxInt003InterfaceInvoiceStg (1:1)
---- fileName (1:1)
---- fileSource (1:1)
---- fileIdentifier (1:1)
---- supplierNumber (1:1)
---- supplierSite (1:1)
---- invoiceNumber (1:1)
---- lineAmount (1:N)
---- taxAmount (1:1)
---- businessEntityReference (1:1)
---- accountNumber (1:1)
In the 'xsl:for-each' construct
+<xsl:for-each select="/inp1:InterfacePayload/inp1:InterfaceFiles/inp1:InterfaceInvoices/inp1:InterfaceInvoice/inp1:InterfaceInvoiceLines/inp1:InterfaceInvoiceLine">+
+<top:lineAmount>+
+<xsl:value-of select="/inp1:InterfacePayload/inp1:InterfaceFiles/inp1:InterfaceInvoices/inp1:InterfaceInvoice/inp1:InterfaceInvoiceLines/inp1:InterfaceInvoiceLine/inp1:LineAmount" />+
+</top:lineAmount>+
+</xsl:for-each>+
- you are asking to iterate through all available 'inp1:InterfaceInvoiceLine' elements in the input XML document
- the value of the element 'top:lineAmount' (for each iteration) is being calculated as all values of available 'inp1:LineAmount' elements in the input XML document together
So, if you have ... lets say
- 4x 'inp1:InterfaceInvoiceLine' element in the input XML document, each containing one 'inp1:LineAmount' element ... with values {1, 2, 3, 4} respectively
- the output will be something like this
<top:lineAmount>1234</top:lineAmount>
<top:lineAmount>1234</top:lineAmount>
<top:lineAmount>1234</top:lineAmount>
<top:lineAmount>1234</top:lineAmount>
Why are you always querying from +/inp1:InterfacePayload/inp1:InterfaceFiles/...+ ?
I think ... all Xpath queries in your XSLT are wrong (they query something else than you think).
e.g.
- putting all file names together into one element (+/inp1:InterfacePayload/inp1:InterfaceFiles/inp1:FileName+)
- putting all file sources together into one element (+/inp1:InterfacePayload/inp1:InterfaceFiles/inp1:FileSource+)
- putting all invoice numbers together into one element (+/inp1:InterfacePayload/inp1:InterfaceFiles/inp1:InterfaceInvoices/inp1:InterfaceInvoice/inp1:InvoiceNumber+)
Best regards,
Martin.

XML message without encoding type

Similar Messages

Maybe you are looking for