Mapping of Web Service SOAP response document

Hi all!
The XI mapping expects a namespace qualified root element of my web service's response SOAP document. Unfortunately my web service (written with AXIS) only provides the "xmlns"-declaration but no namespace-prefix for this element as expected by XI. For this reason the mapping is not working. I am quite desperate and could need some help how to fix that.
All child elements are expected to be non-qualified, only the root element is expected to be qualified. I got this information from the test environment of the message mapping when generating a test XML instance.
Denis

I just had the same problem and solved it like this: I modified the WSDL slightly by removing the prefix from the reference to the element of the response message, as well as the "targetNamespace" in the xsd:schema segment of the WSDL. Like this, SAP is able to parse the response.
Philippe

Similar Messages

Async system - XI BPM Sync - Web service - SOAP response

Dear Experts:
I have the following scenario:
Async Proxy to XI to web service. I use BPM to make this a sync call to the web service. It works fine!
I have a XSLT mapping for the response message from the web service. I use XSLT because the structure of the positive and fault responses are different. Anyway, I could get the positive response post ok back in the XI system.
But the fault response does not get mapped and I get a APPLICATION_ERROR of category UNKNOWN in the SXMB_MONI. I also configured exception handling in the BPM. But it does not catch this error.
Can anyone suggest how to handle the fault response from the web service?
Thank you.

I just had the same problem and solved it like this: I modified the WSDL slightly by removing the prefix from the reference to the element of the response message, as well as the "targetNamespace" in the xsd:schema segment of the WSDL. Like this, SAP is able to parse the response.
Philippe

Web service SOAP response issue

Hi,*
We are upgrading system from ECC 5.0 to ECC 6.0. All of our webservices were created in new system with SOAManager configuration.
When the consumer systsem is trying to consume one of the webservice the XML response is different when compared with the one tested from ECC 5.0.
ECC 6.0 is returning different XML for the same web service. The consuming system "Cold Fusion' is expecting the SOAP XML in different place.
When we tested the same webservice in WS navigator it did gave the response. Also the issue is with this webservice only.
We have re created the webservice again and tested from cold fusion and the same response.
The issue is with only this webservice.
Regards,
Prashanth.

Christoph,
Firstly LiveCycle Designer 8.2 is still not supported to develop forms as per my knowledge. The latest version compatible for SAP Interactive Forms is ALD 8.0.
There is a difference between Acrobat based forms and LiveCycle forms and based on your coding it looks to me that you are trying to create a LiveCycle based form with coding of Acrobat which is not supported in LiveCycle Desginer, which is why you may be getting the error.
I hope that does not confuse you, so may check this [link|http://www.acrobatusers.com/articles/2006/08/designer_or_forms/index.php] for some clear information on what point I was trying to make.
Chintan

Axis Web Service SOAP Response without namespace

Hi folks,
I use the Axis Framework and eclipse to create a Webservice. I wrote a Method which returns a List of customers(complex Element). When I execute the method I get the following result:
<soapenv:Body>
<getAllCustomersResponse>
<ns1:getAllCustomersReturn>
<ns1:email>[email protected]</ns1:email>
<ns1:id>5</ns1:id>
<ns1:name>Hendrik</ns1:name>
</ns1:getAllCustomersReturn>
<ns2:getAllCustomersReturn>
<ns2:email>[email protected]</ns1:email>
<ns2:id>6</ns1:id>
<ns2:name>Masen</ns1:name>
</ns2:getAllCustomersReturn>
</getAllCustomersResponse>
</soapenv:Body>
How can I configure Axis that I get the result without namespace like this: ?
<soapenv:Body>
<getAllCustomersResponse>
<getAllCustomersReturn>
<email>[email protected]</ns1:email>
<id>5</ns1:id>
<name>Hendrik</ns1:name>
</getAllCustomersReturn>
<getAllCustomersReturn>
<email>[email protected]</ns1:email>
<id>6</ns1:id>
<name>Masen</ns1:name>
</getAllCustomersReturn>
</getAllCustomersResponse>
</soapenv:Body>
Thanks for your help
Edited by: Heno on Apr 27, 2009 1:28 AM

I just had the same problem and solved it like this: I modified the WSDL slightly by removing the prefix from the reference to the element of the response message, as well as the "targetNamespace" in the xsd:schema segment of the WSDL. Like this, SAP is able to parse the response.
Philippe

Web Service (SOAP) From Oracle Forms

From the exaples of calling web services (soap) from pl/sql, it seems very poor and troublesome. I've seen a few articles with good points about why not to do this from pl/sql. So, I was hoping someone in the forums could share their opinions and approaches to using web services from forms based applications. I would ideally like to hear reasons people chose not to use pl/sql.

There are some examples of calling web services from forms on the Forms OTN page - works fine although I would encourage the use of the new JVM pooling features as this will aid scalability and performance.
Regards
Grant Ronald
Forms Product Management

File to Web service (SOAP) to File scenario with out BPM in PI 7.1

Hi All,
I have scenario File to Web service (SOAP) to File scenario with out BPM.i am getting the below error:
1) Error MP: unexpected exception caught com.sap.aii.af.service.cpa.impl.exception.CPAObjectKeyException: Value of key must not be null: ObjectId
2) Error ROB: error during processing: com.sap.aii.af.lib.mp.processor.ModuleProcessorException: Processing Error
PI server is 7.1 with SP:8
I have configured the scenario like this
1) 2 File channels - Sender & Receiver ,1 RFC channel - Receiver. We need to note that, the additional Module parameters need to be added only for sender File channel
2) Created Sender Agreement
3)Created Receiver Determination
4)Created Interface Determination
5)Created Receiver Agreement
Regards,
Ramesh

Hi,
Thanks for your reply!!
My Scenario is File to SOAP to File.
Configred modules in Sender channal below:
Prcessing sequence:
Number       Module Name                                        Module Key
1..........       AF_Modules/RequestResponseBean.......1
2..........       CallSapAdapter..........................................2
3..........       AF_Modules/ResponseOnewayBean.......3
Module Configuration:
Module Key                                       Parameter Name                                       ParameterValue
1                                                        passThrough                                            true
3                                                        receiverChannel                                       receiverChannel name
3                                                        receiverService                                        receiverService name
please tell any more confiration requered.
Regards,
Ramesh

How to install and consume GroupWise Web Service (SOAP)

Hello! I'm Razvan, programmer from Romnia, and I am new to GroupWise development.
I am asking if anyone could help me with a C# Visual Studio 2010 example of how to install and consume GroupWise Web Service (SOAP).
The documentation from novell site didn't help me, i didn't understant much of it.
All I need is either a link to a documented GroupWise C# developer step-by-step tutorial, or some code examples.
Can you please show me some code examples in C# with:
1)loging in using a username and a password,
2)retrieving contact list,
3)retrieving appointment list,
4)sending a mail,
5)setting an appointment
I don't know how to use "groupwise.wsdl" and customise it so that it points to our GroupWise server.
Please, I really need this because I am working at a project right now which involves GroupWise integration.
I hope I haven't disturbed anyone with my simple question.
I know this might be a very simple question given the complexity of the other posts here, but that's why I really hope I will get an answer soon.
Thank you very much!
Signature:
How old is the Orthodox faith?
How old is the orthodox faith?

Just a comment.
The value for the version element should be "1.02"
not "1.2".
Preston
>>> On Tuesday, March 01, 2011 at 8:06 AM,
TheRomanian<[email protected]> wrote:
> I have great news! After strong documentation yesterday and today, I've
> just made a successfull example that actually connects to our GroupWise
> server.
>
> I made it in PHP.
>
> I need an ASP.NET + C# application, but now is very simple to convert
> it. I post the PHP code here for other people who in future might be
> interested in finding out.
>
> So a simple PHP GroupWise Login code using "groupwise.wsdl" web
> service:
>
>
> require_once('./GWService/GroupwiseService.php');
> require_once('FB.class.php');
>
> $classmap = array(
> 'Authenication' => 'Authenication',
> 'PlainText' => 'PlainText',
> 'loginRequest' => 'loginRequest',
> 'loginResponse' => 'loginResponse',
> 'logoutRequest' => 'logoutRequest',
> 'logoutResponse' => 'logoutResponse',
> 'UserInfo' => 'UserInfo',
> );
>
> $gwservice = new GroupwiseService(
> "./WSDL/groupwise.wsdl",
> array(
> "location" => "http://11.150.40.78:8756/soap",
> *Your GroupWise server IP:
> and PORT*
> "classmap" => $classmap,
> "trace" => true)
> );
>
> // do login
> $pt = new PlainText();
> $pt‑>username = *"YOUR GROUPWISE USERNAME"*;
> $pt‑>password = *"YOUR GROUPWISE PASSWORD"*;
>
> $lr = new loginRequest();
> $lr‑>auth = $pt;
> $lr‑>language = "en";
> $lr‑>version = "1.2";
> $lr‑>application = "phpClient";
>
> $lres = $gwservice‑>loginRequest($lr);
> //print_r($lres);
>
>
> I Hope this will help others.
>
> ‑‑
> Signature:
>
> How old is the Orthodox Faith?
> 'How old is the orthodox faith?'
> (http://www.orthodoxphotos.com/history.shtml)

Web Service SOAP Sender Authorization

Hi all
I have been implementing a Web Service (SOAP Sender CC) that should be consumed by an external party. I have been testing it successfully using XMLSpy with the drawback of the authentication box coming up even though I have added sap-user and sap-password to the URL as following:
http://<host>:50000/XISOAPAdapter/MessageServlet?channel=:SOAP_Service:CC_SOAP_Sender&sap-user=<name>&sap-password=<pass>
The user that I have created for this has the profile SAP_XI_APPL_SERV_USER assigned.The request is successfully executed when I enter <name> and <pass> in the box. My understanding of it would be that the box does not show up if the login parameters are provided with the URL. Do I have to do any additional settings so that the login information will be taken from the URL parameters automatically instead bringing up the authoritzation box?
My CC settings are as following:
Adapter Type: SOAP (SAP BASIS 7.00)
Sender
Transport Protocol: HTTP
Message Protocol: SOAP 1.1
Adapter Engine: Integration Server
HTTP Security Level: HTTP
Conversion Parameters: Keep Headers
Quality of Service: Best Effort
Any feedback would be appreciated.
Thank you,
Daniel

Hello Daniel,
1. You can add username and password to the SOAP URL and expose your XI Interface as a webservice. Just that the URL is different than the one you are using and you do not need a Sender SOAP adapter but the blog I have listed above.
2. You can turn of Basic authentication on Sender SOAP adapter's but it is not recommended as it would turn off all authentication for SOAP scenarios and it can lead to security risks.
I have seen a few forum threads describing how to turn of Basic authentication for SOAP adapters but from what I have heard from SAP, they do not recommend using this option.
Regards
Bhavesh

Web Services, SOAP, 8.6 RT Target

Hello,
I have an application where I want to access information "served" on a standalone, networked, instrument. For this particular instrument you can get all the information I am looking for through a normal web browser or through a defined a set of web services using SOAP (Simple Object Access Protocol).
Using the web services approach is remarkably easy from LabVIEW on a PC - simply use tools>>Import>>Web Service... From here you can simply point to the Web Service Definition file (WSDL File) on the instrument and the import wizard creates a set of wrapper files that do all the work.
www.xmethods.net has a bunch of services listed - there is a (free) weather service that will give you a report and/or forecast for any city - I had fun playing with this! (In reality I cannot tell what protocol LV has chosen to use with this example - suffice to say that it works from the PC)
However, this operation is definitely not-so-easy from a RT Target - in fact, I simply don't know how to make it work at all!
My understanding is that 8.6 and RT lost support for some protocols (SOAP, etc.) to focus on RESTful. However, I'm unclear if this is just for services from a RT Target (server) rather than when a RT Target is acting as a client. In any case, in the above example the VI's created on the PC using the import wizard are based in .NET and not supported on a RT Target.
Now, it would seem to me that it would not be unreasonable to go low-level and create the desired communication with more basic building blocks - especially since for my particular application all I want to do is "get value X". Unfortunately, I'm totally new to this level of network protocol and am a little daunted...
Has anybody run into this before? I know there other instruments out there that use this kind of "server" approach - has anybody had to create their own interface to the HTML? Is there an example I'm just not finding? Are there SOAP workarounds for RT Targets?
Any suggests/examples very much appreciated!

Yes this can be done on a RT target, because it supoort TCP/IP and string functions. That is all you need. For devices that publish a webpage you would have to send a HTTP request to the device requesting the published page. the response can then be parsed for the required values. Have a look at the following document. Try "www.carya.nl" and path "/index.php" with HTTP GET and you'll get a response from the webserver.
Message Edited by andre.buurman@carya on 04-09-2009 09:52 PM
Regards,
André
Using whatever version of LV the customer requires. (LV5.1-LV2012) (www.carya.nl)

Update key mapping via web service

Hi ,
I have a question about edit key mapping. The problem is that we create vendors in MDM and syndicate them to different ERP systems. To decide which system a new vendor/changes must be send to, I need the Edit Key Mapping, but the users do not want to enter this information manually and I do not see how I can create key mapping automatically.
We are working on a new solution where vendors are entered in sharepoint and updated in MDM via web services. I would like to know if one of you know if key mapping can be maintained via a web service.
Kind regards
Jonna

Hello,
You may use the document,
[MDM PI via Web Service Key Mapping|http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/e0812356-e62f-2c10-76aa-9a02d038ba81]
Hope this helps your scenario
Regards,
Abhishek

Invoking a web service with multi document WSDL

Hi,
I'm trying to call a web service from BPEL using the partner link button. The WSDL I have is in two parts, the first document includes the endpoint and a wsdl:import statement which points to the second document containing types and definitions. I can create a client to the service using JDeveloper but BPEL doesn't seem to register the WSDL as valid.
I have included the wsdls below for information. I would appreciate any help or suggestions.
Thanks in advance
John
Document One:
<?xml version="1.0" encoding="utf-8"?>
<wsdl:definitions xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" name="RADCalcWSWsd" targetNamespace="urn:RADCalcWSWsd" xmlns:bns0="urn:RADCalcWSWsd/Config1/rpc" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/">
<wsdl:documentation>RAD Calculator Service description.</wsdl:documentation>
<wsdl:import location="./bindings/Config1_rpc.wsdl" namespace="urn:RADCalcWSWsd/Config1/rpc"/>
<wsdl:service name="RADCalcWS">
<wsdl:port name="Config1Port_Rpc" binding="bns0:Config1Binding">
<soap:address location="http://ermprot1:50000/RADCalcWS/Config1?style=rpc"/>
</wsdl:port>
</wsdl:service>
</wsdl:definitions>
Document Two
<?xml version="1.0" encoding="utf-8"?>
<wsdl:definitions xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" targetNamespace="urn:RADCalcWSWsd/Config1/rpc" xmlns:prt0="urn:RADCalcWSWsd/RADCalcWSVi/rpc" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/">
<wsdl:import location="../porttypes/Config1_RADCalcWSVi_rpc.wsdl" namespace="urn:RADCalcWSWsd/RADCalcWSVi/rpc"/>
<wsdl:binding name="Config1Binding" type="prt0:RADCalcWSVi_Rpc">
<soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="rpc"/>
<wsdl:operation name="add">
<soap:operation soapAction=""/>
<wsdl:input>
<soap:body use="literal" namespace="urn:RADCalcWSVi" parts="f1 f2 "/>
</wsdl:input>
<wsdl:output>
<soap:body use="literal" namespace="urn:RADCalcWSVi"/>
</wsdl:output>
</wsdl:operation>
<wsdl:operation name="divide">
<soap:operation soapAction=""/>
<wsdl:input>
<soap:body use="literal" namespace="urn:RADCalcWSVi" parts="f1 f2 "/>
</wsdl:input>
<wsdl:output>
<soap:body use="literal" namespace="urn:RADCalcWSVi"/>
</wsdl:output>
</wsdl:operation>
<wsdl:operation name="getDateTime">
<soap:operation soapAction=""/>
<wsdl:input>
<soap:body use="literal" namespace="urn:RADCalcWSVi"/>
</wsdl:input>
<wsdl:output>
<soap:body use="literal" namespace="urn:RADCalcWSVi"/>
</wsdl:output>
</wsdl:operation>
<wsdl:operation name="multiply">
<soap:operation soapAction=""/>
<wsdl:input>
<soap:body use="literal" namespace="urn:RADCalcWSVi" parts="f1 f2 "/>
</wsdl:input>
<wsdl:output>
<soap:body use="literal" namespace="urn:RADCalcWSVi"/>
</wsdl:output>
</wsdl:operation>
<wsdl:operation name="subtract">
<soap:operation soapAction=""/>
<wsdl:input>
<soap:body use="literal" namespace="urn:RADCalcWSVi" parts="f1 f2 "/>
</wsdl:input>
<wsdl:output>
<soap:body use="literal" namespace="urn:RADCalcWSVi"/>
</wsdl:output>
</wsdl:operation>
<wsdl:operation name="test">
<soap:operation soapAction=""/>
<wsdl:input>
<soap:body use="literal" namespace="urn:RADCalcWSVi"/>
</wsdl:input>
<wsdl:output>
<soap:body use="literal" namespace="urn:RADCalcWSVi"/>
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
</wsdl:definitions>

I've noticed that JDeveloper [edit:]doesn't[:edit] recursively look for schema type infomation and things in sub wsdl files, could you have a similar issue? (BPEL engine don't have an issue though)
BTW, your second wsdl file imports a third wsdl file -> I presume this defines the portType?
Message was edited by:
taylor_tails

Web Service encoding response improperly using the plugin and ssl

We are having a problem with the response from a document style web service. The response is xml but the elements come back as "&lt element &gt" instead of <element>. The return variable is of type String.
Our setup is Iplanet(6.1) frontend using the wl-proxy plugin
to Weblogic 8.1. The webservice is using https. If we use port 7001 (not https) instead of https 443 it works fine.
It appears to me that the plugin when used with ssl has a bug.
In help would be greatly appreciated. This situation did not occur using wls6.1. When we migrated to 8.1 that is when it started happening.
Other screnarios tested: When going right at weblogic 8.1 using ssl no problem.

Hi
When you have generated the client proxy classes from NW DS you can then include the .jar file into your applets code. Then, to actually execute the web service you can use the following code (for example)
String logicalPort = "<logical port defined in WSDL>";
<generate service interface> service = new <generated service implementation>();
<generated proxy class> port = (<generated proxy class>)service.getLogicalPort(logicalPort, <generated proxy class>.class);
String param = "myval";
String result = port.<method>(param);
where everything in the <> represents the relevant client classes that have been generated by NW DS. Bear in mind that you can either create deployed proxies or standalone proxies. Deployed proxies get deplyed to the J2EE server and need to be looked up via JNDI. The implementation classes are not included as part of the proxy generation.
Standalone proxies are created with the implementation classes included and can therefore be included in ANY java application.
I hope this helps
Darrell

How to pass .txt file as an attachment to the web service (SOAP Attachment)

Hi,
I am creating web service using NetBeans 6.5 IDE and JAX-WS. I create a web application and then create web service using provided interface. I want to add .txt file as an attachment/parameter to the web service operation using "Add operation" interface. Don't want to add as an attachment to the SOAP message by creating it explicitly. IDE generates SOAP request and response automatically when the service is tested using "Test Web service" option. How can I add attcahment when I add operation so that it will appear in the generated SOAP message ?
TIA.

Hi AnitaDP,
Attachment doesn't work in web service. You have to pass the content of the text file as a String or as an array of bytes to a method of your web service. From there, you may save the passed data in a file.

Problem in writing a client web service from WSDL document

Hi,
I wrote a web service using .Net and a WSDL document. I tried after that to generate a client web service using Jdeveloper. but, the methode generated by Jdeveloper (in the stub) does not represente the original methode.
<?xml version = '1.0' encoding = 'windows-1252'?>


<definitions
name="CreditCard"
targetNamespace="http://tempuri.org/jdeveloper/generated/CreditCard/CreditCard"
xmlns="http://schemas.xmlsoap.org/wsdl/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:tns="http://tempuri.org/jdeveloper/generated/CreditCard/CreditCard"
xmlns:ns1="http://tempuri.org/jdeveloper/generated/CreditCard/CreditCard/schema">
<types>
<schema
targetNamespace="http://tempuri.org/jdeveloper/generated/CreditCard/CreditCard/schema"
xmlns="http://www.w3.org/2001/XMLSchema"
xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/"/>
</types>
<message name="Validate0Request">
<part name="cardNumber" type="xsd:string"/>
<part name="lngDate" type="xsd:long"/>
</message>
<message name="Validate0Response">
<part name="return" type="xsd:boolean"/>
</message>
<portType name="CreditCardPortType">
<operation name="Validate">
<input name="Validate0Request" message="tns:Validate0Request"/>
<output name="Validate0Response" message="tns:Validate0Response"/>
</operation>
</portType>
<binding name="CreditCardBinding" type="tns:CreditCardPortType">
<soap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http"/>
<operation name="Validate">
<soap:operation soapAction="" style="rpc"/>
<input name="Validate0Request">
<soap:body use="encoded" namespace="CreditCard.CreditCard" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>
</input>
<output name="Validate0Response">
<soap:body use="encoded" namespace="CreditCard.CreditCard" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>
</output>
</operation>
</binding>
<service name="CreditCard">
<port name="CreditCardPort" binding="tns:CreditCardBinding">
<soap:address location="http://localhost:8888/FirstSample-CreditCard-context-root/CreditCard.CreditCard"/>
</port>
</service>
</definitions>
Here The methode Validate consume two parameters : string and long
the generated stub look like :
public Vector Validate(Element requestElem) throws Exception
There is some one who have a solution ?
---------------------------------------

My guess is that it is because .NET defaults to generating a document style interface whereas JDeveloper defaults to generating an RPC style interface. The end result is that JDeveloper wraps the document interface in something that looks document like - thus your client. To see how to handle this right now, check out this sample - you have to parse the XML:
http://otn.oracle.com/tech/webservices/htdocs/series/net/content.html
In the preview of JDeveloper 9.0.3 which is due quite soon - next few weeks roughly (crossing my fingers) - JDeveloper will wrap .NET document based Web services in a much more elegant wrapper - giving you exactly what you are looking for - a method called Validate rather than a vector of Elements.
What I don't understand in your sample, however, is that you have WSDL generated from JDeveloper versus WSDL generated from .NET. Did you also do an implementation of the validate method in Java too?
Mike.

Support on 'Base64 encoding in XML gateway Web service SOAP content'

Hi Experts,
IHAC who's requirement is as follows:
They are currently using Web service protocol to send order information from Oracle Applications to their trading partner.
But need to encode the payload in base64 encoding in the SOAP request.
Further details:
=====================================================================
Current SOAP request is,
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:bac="http://backend.ws.gtas.gridnode.com">
<soapenv:Header/>
<soapenv:Body>
<bac:backendImport4>
<bac:username>?</bac:username>
<bac:password>?</bac:password>
<bac:recipient>?</bac:recipient>
<bac:contentFileName>?</bac:contentFileName>
<bac:content>
<EMPLOYEE>
<EMPLOYEE_DATA>
<EMAIL_ADDRESS/>
<EMPLOYEE_ID>81</EMPLOYEE_ID>
<EMPLOYEE_NUM>2</EMPLOYEE_NUM>
<FIRST_NAME/>
<FULL_NAME>Eddi.S,</FULL_NAME>
<LAST_NAME>Eddi.S</LAST_NAME>
<MIDDLE_NAME/>
</EMPLOYEE_DATA>
</EMPLOYEE>
</bac:content>
<bac:docType>?</bac:docType>
</bac:backendImport4>
</soapenv:Body>
</soapenv:Envelope>
Required SOAP request with base64 encoding is:
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:bac="http://backend.ws.gtas.gridnode.com">
<soapenv:Header/>
<soapenv:Body>
<bac:backendImport4>
<bac:username>?</bac:username>
<bac:password>?</bac:password>
<bac:recipient>?</bac:recipient>
<bac:contentFileName>?</bac:contentFileName>
<bac:content>
PD94bWwgdmVyc2lvbj0iMS4wIiBlbmNvZGluZz0iVVRGLTgiIHN0YW5kYWxvbmU9J25vJz8+DQo8IURPQ1RZUEUgRU1QTE9ZRUU+DQo8IS0tIE9yYWNsZSBlWHRlbnNpYmxlIE1hcmt1cCBMYW5ndWFnZSBHYXRld2F5IFNlcnZlciAgLS0+DQo8RU1QTE9ZRUU+DQogIDxFTVBMT1lFRV9EQVRBPg0KICAgIDxFTUFJTF9BRERSRVNTLz4NCiAgICA8RU1QTE9ZRUVfSUQ+ODE8L0VNUExPWUVFX0lEPg0KICAgIDxFTVBMT1lFRV9OVU0+MjwvRU1QTE9ZRUVfTlVNPg0KICAgIDxGSVJTVF9OQU1FLz4NCiAgICA8RlVMTF9OQU1FPkVkZGkuUyw8L0ZVTExfTkFNRT4NCiAgICA8TEFTVF9OQU1FPkVkZGkuUzwvTEFTVF9OQU1FPg0KICAgIDxNSURETEVfTkFNRS8+DQogIDwvRU1QTE9ZRUVfREFUQT4NCjwvRU1QTE9ZRUU+DQo=
</bac:content>
<bac:docType>?</bac:docType>
</bac:backendImport4>
</soapenv:Body>
</soapenv:Envelope>
The issue in question is the content within the element <bac:content>.
Base64 encoding of the payload
<EMPLOYEE>
<EMPLOYEE_DATA>
<EMAIL_ADDRESS/>
<EMPLOYEE_ID>81</EMPLOYEE_ID>
<EMPLOYEE_NUM>2</EMPLOYEE_NUM>
<FIRST_NAME/>
<FULL_NAME>Eddi.S,</FULL_NAME>
<LAST_NAME>Eddi.S</LAST_NAME>
<MIDDLE_NAME/>
</EMPLOYEE_DATA>
</EMPLOYEE>
is
PD94bWwgdmVyc2lvbj0iMS4wIiBlbmNvZGluZz0iVVRGLTgiIHN0YW5kYWxvbmU9J25vJz8+DQo8IURPQ1RZUEUgRU1QTE9ZRUU+DQo8IS0tIE9yYWNsZSBlWHRlbnNpYmxlIE1hcmt1cCBMYW5ndWFnZSBHYXRld2F5IFNlcnZlciAgLS0+DQo8RU1QTE9ZRUU+DQogIDxFTVBMT1lFRV9EQVRBPg0KICAgIDxFTUFJTF9BRERSRVNTLz4NCiAgICA8RU1QTE9ZRUVfSUQ+ODE8L0VNUExPWUVFX0lEPg0KICAgIDxFTVBMT1lFRV9OVU0+MjwvRU1QTE9ZRUVfTlVNPg0KICAgIDxGSVJTVF9OQU1FLz4NCiAgICA8RlVMTF9OQU1FPkVkZGkuUyw8L0ZVTExfTkFNRT4NCiAgICA8TEFTVF9OQU1FPkVkZGkuUzwvTEFTVF9OQU1FPg0KICAgIDxNSURETEVfTkFNRS8+DQogIDwvRU1QTE9ZRUVfREFUQT4NCjwvRU1QTE9ZRUU+DQo=
========================================================================
Is there a way in XML gateway to encode the payload automatically to base64 encoding so that it can accommodate the unicode
Is there any way to encode the order information from EBS tables to base64 format in the outbound SOAP request ? Is this supported . If yes, how.?
Does this involve customization. Is it possible to use encoder/decoder provided in sites such as XSL on top of XML : http://gandhimukul.tripod.com/xslt/base64-xslt.html
Basically, They are trying to use XML Gateway to send and receive messages to a Trading Partner via SOAP. The issues is
1. Outbound: The TP web service can only receive xml content that is encoded in base 64 binary format. How do we configure to encode content using base64
2. Inbound: They want to receive messages using the SOAP architecture into XML gateway.
Please let us know if you have any detailed configuration document for this purpose. Please advise and share relevant details.
regards,
Ajith

Hi Gurvinder,
Thanks for looking into this. Just to clarify again.
example XML content:
<?xml version="1.0" encoding="UTF-8" standalone='no'?>
<!DOCTYPE EMPLOYEE>

<EMPLOYEE>
<EMPLOYEE_DATA>
<EMAIL_ADDRESS/>
<EMPLOYEE_ID>81</EMPLOYEE_ID>
<EMPLOYEE_NUM>2</EMPLOYEE_NUM>
<FIRST_NAME/>
<FULL_NAME>Eddi.S,</FULL_NAME>
<LAST_NAME>Eddi.S</LAST_NAME>
<MIDDLE_NAME/>
</EMPLOYEE_DATA>
</EMPLOYEE>
Sample Soap message that needs to be sent to our service provider is as follows
<?xml version="1.0" encoding="UTF-8" ?>
- <soapenv:Envelope xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope">
- <soapenv:Body>
- <ns5:backendImport5 xmlns:ns5="http://backend.ws.gtas.gridnode.com">
<ns5:username>admin</ns5:username>
<ns5:password>admin1</ns5:password>
<ns5:recipient>GT424</ns5:recipient>
<ns5:contentFileName>cabotTest.xml</ns5:contentFileName>
<ns5:content>PD94bWwgdmVyc2lvbj0iMS4wIiBlbmNvZGluZz0iVVRGLTgiIHN0YW5kYWxvbmU9J25vJz8+DQo8IURPQ1RZUEUgRU1QTE9ZRUU+DQo8IS0tIE9yYWNsZSBlWHRlbnNpYmxlIE1hcmt1cCBMYW5ndWFnZSBHYXRld2F5IFNlcnZlciAgLS0+DQo8RU1QTE9ZRUU+DQogIDxFTVBMT1lFRV9EQVRBPg0KICAgIDxFTUFJTF9BRERSRVNTLz4NCiAgICA8RU1QTE9ZRUVfSUQ+ODE8L0VNUExPWUVFX0lEPg0KICAgIDxFTVBMT1lFRV9OVU0+MjwvRU1QTE9ZRUVfTlVNPg0KICAgIDxGSVJTVF9OQU1FLz4NCiAgICA8RlVMTF9OQU1FPkVkZGkuUyw8L0ZVTExfTkFNRT4NCiAgICA8TEFTVF9OQU1FPkVkZGkuUzwvTEFTVF9OQU1FPg0KICAgIDxNSURETEVfTkFNRS8+DQogIDwvRU1QTE9ZRUVfREFUQT4NCjwvRU1QTE9ZRUU+DQo=</ns5:content>
<ns5:docType>3C3RN</ns5:docType>
</ns5:backendImport5>
</soapenv:Body>
</soapenv:Envelope>
. The xml content provided need to be encoded as base 64 encoding. The following is the equivalent of above xml content.
<ns5:content>PD94bWwgdmVyc2lvbj0iMS4wIiBlbmNvZGluZz0iVVRGLTgiIHN0YW5kYWxvbmU9J25vJz8+DQo8IURPQ1RZUEUgRU1QTE9ZRUU+DQo8IS0tIE9yYWNsZSBlWHRlbnNpYmxlIE1hcmt1cCBMYW5ndWFnZSBHYXRld2F5IFNlcnZlciAgLS0+DQo8RU1QTE9ZRUU+DQogIDxFTVBMT1lFRV9EQVRBPg0KICAgIDxFTUFJTF9BRERSRVNTLz4NCiAgICA8RU1QTE9ZRUVfSUQ+ODE8L0VNUExPWUVFX0lEPg0KICAgIDxFTVBMT1lFRV9OVU0+MjwvRU1QTE9ZRUVfTlVNPg0KICAgIDxGSVJTVF9OQU1FLz4NCiAgICA8RlVMTF9OQU1FPkVkZGkuUyw8L0ZVTExfTkFNRT4NCiAgICA8TEFTVF9OQU1FPkVkZGkuUzwvTEFTVF9OQU1FPg0KICAgIDxNSURETEVfTkFNRS8+DQogIDwvRU1QTE9ZRUVfREFUQT4NCjwvRU1QTE9ZRUU+DQo=</ns5:content>
See that the content is encoded using the base64 format.
Please help us to know how we can configure XML gateway to achieve this.
Regards,
Ajith

Mapping of Web Service SOAP response document

Similar Messages

Maybe you are looking for