Web services websphere 5.1 encoding character

Hi
i generate a client using the command websphere tool WSDL2java.
Now i would like to change the character encoding ; I want to change to UTF-8.
Any idea ?
thanks
best regards

Hi Paul,
Earlier in this list, Tom Zaranek asked the same question. If you search back there
is a good thread that may be helpful.
In general, having the latest release of an emerging technology is recommended.
HTHs,
Bruce
Paul Martin wrote:
How well do web services work with WLS 5.1? Are there any pitfalls that would be
encountered. Would it be wiser to upgrade to a more recent version of WLS to use
enhanced web services features?

Similar Messages

Web Services and JAXRPC serialization encoding

Hi all.
I have written a Web Service starting from the WSDL using wscompile (NetBeans 5.0 feature). The WSDL defines an operation which returns a complex data type which is wrapped by JAXRPC SI in a suitable class package. What I simply do, is to use these classes to create my complex data content. I don't care about the serialization, because it is automatically performed by my Sun Java System Application Server Platform Edition 8.1_01 (build b04-fcs). The default encoding should be UTF-8.
One colleague of mine has tried to connect to my service creating the stub classes using WSDL2Java by Axis. He gets this problem:
java.io.UTFDataFormatException: Invalid byte 2 of 3-byte UTF-8 sequence.
It looks to be a problem of encoding. I think the output is correctly encoded but I'm not sure an I don't know how verify it or setup the Application Server output since almost everything is automatically performed. I've tried to take a look to the generated code inside the Application Server, but it is a bloody mess!
Note that if I try to consume the service using stub client classes generated with wscompile... everything works! My clients generated using Netbeans 5.0 (which uses wscompile) are fine!
Any suggestion?
Thanks

I upgraded webservices developer pack to 1.0 version (final) and I solved my problems!
Pedro Salazar

MTOM Encoded Web Service Response

Hi,
I am trying to call from APEX some web services that are MTOM encoded and the calls are failing.
Does APEX support MTOM encoding? I am using the apex_web_service.make_request function.
Below is a comparison of 2 service raw responses from soapUI, one that works with APEX and one that doesn’t.
Service 1 Raw Response:
HTTP/1.1 500 Internal Server Error
Date: Fri, 05 Jul 2013 17:06:41 GMT
Server: Apache-Coyote/1.1
X-Powered-By: None
Content-Type: application/soap+xml;charset=UTF-8
Content-Length: 734
Access-Control-Allow-Origin: *
Connection: close
<soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope"><soap:Body>.................</soap:Body></soap:Envelope>
Service 2 Raw Response:
HTTP/1.1 500 Internal Server Error
Date: Fri, 05 Jul 2013 17:05:14 GMT
Server: Apache-Coyote/1.1
X-Powered-By: None
Content-Type: multipart/related; type="application/xop+xml";boundary="uuid:2505d950-8e95-4cd7-a350-a73962f5b748";start="<[email protected]>";start-info="application/soap+xml"
Content-Length: 1175
Access-Control-Allow-Origin: *
Connection: close
--uuid:2505d950-8e95-4cd7-a350-a73962f5b748
Content-Type:application/xop+xml; charset=UTF-8; type="application/soap+xml";
Content-Transfer-Encoding: binary
Content-ID: <[email protected]>
<soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope"><soap:Body>.............</soap:Body></soap:Envelope>
--uuid:2505d950-8e95-4cd7-a350-a73962f5b748—
Service 1 works with APEX, it has a standard “application/soap+xml” content type and XML follows immediately after the header, which APEX expects and is able to parse.
Service 2 does not work with APEX, it has the specific MTOM “multipart/related;type="application/xop+xml"” content type and after the header the uuid reference for the multipart response.
Any idea on how to handle these types of web service calls from APEX?
Thanks!

Hi
Have you found the workaround?
Sorry for refreshing topic. Flag mustUnderstand ='1' in response is unussual thing.
BR

How to disable href/id in the generated response of a web-service

Hello All,
Do I have any possibility to disbale href/id on the generated response of a web-service that use RPC-encoded format? My generated soap body looks like this:
<env:Body env:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
<m:Response xmlns:m="http://www.myTest.com">
<result xmlns:n1="java:com.myTest" xsi:type="n1:Response">
<ResultObject xsi:type="n1:ResultObject">
<firstString href="#ID_6" />
<integerObject href="#ID_13" />
<secondString href="#ID_6" />
</ResultObject>
<ResultObject xsi:type="n1:ResultObject">
<firstString href="#ID_6" />
<integerObject href="#ID_13" />
<secondString href="#ID_6" />
</ResultObject>
<ResultObject xsi:type="n1:ResultObject">
<firstString href="#ID_6" />
<integerObject href="#ID_13" />
<secondString href="#ID_6" />
</ResultObject>
</result>
</m:Response>
<xsd:int xsi:type="xsd:int" id="ID_13">10</xsd:int>
<xsd:string xsi:type="xsd:string" id="ID_6">EUR</xsd:string>
</env:Body>
Do I have any possibility to instruct the serialization process so that the result to conform with an XML schema and to keep the RPC-Encoded format? In other words to get rid of href/id:s? Href/id:s are used only for objects having the same reference.
This issue is now even more problematic since JDK 5 when for integers boxing is not necessarily and thus, the compiler translates an Integer assignment using the method:
public static Integer valueOf(int i)
which returns cached Integer objects for any integer between -128 and 127.
Please give some hints (others than using boxing for integers or changing the soap format to document-literal).
Thanks

Hello All,
Do I have any possibility to disbale href/id on the generated response of a web-service that use RPC-encoded format? My generated soap body looks like this:
<env:Body env:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
<m:Response xmlns:m="http://www.myTest.com">
<result xmlns:n1="java:com.myTest" xsi:type="n1:Response">
<ResultObject xsi:type="n1:ResultObject">
<firstString href="#ID_6" />
<integerObject href="#ID_13" />
<secondString href="#ID_6" />
</ResultObject>
<ResultObject xsi:type="n1:ResultObject">
<firstString href="#ID_6" />
<integerObject href="#ID_13" />
<secondString href="#ID_6" />
</ResultObject>
<ResultObject xsi:type="n1:ResultObject">
<firstString href="#ID_6" />
<integerObject href="#ID_13" />
<secondString href="#ID_6" />
</ResultObject>
</result>
</m:Response>
<xsd:int xsi:type="xsd:int" id="ID_13">10</xsd:int>
<xsd:string xsi:type="xsd:string" id="ID_6">EUR</xsd:string>
</env:Body>
Do I have any possibility to instruct the serialization process so that the result to conform with an XML schema and to keep the RPC-Encoded format? In other words to get rid of href/id:s? Href/id:s are used only for objects having the same reference.
This issue is now even more problematic since JDK 5 when for integers boxing is not necessarily and thus, the compiler translates an Integer assignment using the method:
public static Integer valueOf(int i)
which returns cached Integer objects for any integer between -128 and 127.
Please give some hints (others than using boxing for integers or changing the soap format to document-literal).
Thanks

Creating a web service using websphere integration developer

Hi! all, Iam trying to create a web service in websphere integration developer, of IBM,
While creating a wsdl file, it asks for literals, there we need to check the corresponding literal based upon the requiremnet.
I came to know that document literal is used for document inputs and outputs,where as rpc literal/rpc encoded is used when dealing with the primitive data types.
I created a simple addition operation with rpc encoded its working,
but i tried out with the rpc encoded , which is causing an error
the err is :
IWAB0135E An unexpected error has occurred.
SOAPException
Operation timed out: connect:could be due to invalid address
Iam not getting how to resolve this error,
Please let me know , if any has faced this kind of error , n knows how to solve.
And also let me know exactly , the difference between the literals.
Fine then,
Thanks & Regards,
D.Swetha.

Unfortunately, OUT parameters are not supported in 9.0.3 as per this doc:
http://otn.oracle.com/docs/products/ias/doc_library/903doc_otn/generic.903/b10004/plsqlservices.htm#1030066
JDeveloper's PL/SQL Web service support is built on top of the Oracle9iAS support so is subject to the same constraints. Support for OUT arguments is planned in future releases of Oracle9iAS and Oracle9i JDev.
You may be able to construct a workaround using an approach described in this new DB Web services paper:
http://otn.oracle.com/tech/webservices/htdocs/dbwebservices/Database_Web_Services.pdf
where you use JPublisher/SQLJ to do the work and then another wrapper/sub class as the actual class that is published as a Web service. See the section that covers a strategy for publishing result sets which are an unsupported type but through a bit of extra work can be used within Web services. This loses the point-and-click tooling approach in JDeveloper but may solve the issue if it is a hard requirement.
Mike.

How to deploy web service/client on websphere

Hi,
I have developed a web service client on Jdeveloper 10.1.3.1.0 and I deployed it on the embeded OC4J and OAS and it worked fine. BUT when I packaged it as EAR file and deployed it on websphere 6.0 {the production enviroment at the client side} It gave me NoClassForService00.
And in websphere application server it didn't recognize it as Web service client.
Any one faced this problem b4. PLZ advice.
Thnx

Hi Amol,
Thank you very much for replying my question. The contents in my application.xml are:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE application PUBLIC "-//Sun Microsystems, Inc.//DTD J2EE Application 1.3//EN" "http://java.sun.com/dtd/application_1_3.dtd">
<application>
<display-name>testwsapp</display-name>
<description>J2EE Application testwsapp</description>
<module>
<web>
<web-uri>testws_War.war</web-uri>
<context-root>testws</context-root>
</web>
<alt-dd>testws_War.xml</alt-dd>
</module>
</application>
The contents in jaxrpc-ri-runtime.xml are:
<?xml version="1.0" encoding="UTF-8"?>
<endpoints xmlns='http://java.sun.com/xml/ns/jax-rpc/ri/runtime' version='1.0'>
<endpoint
name='testws'
interface='contactws.testwsGenServer.testwsRPC'
implementation='contactws.testwsGenServer.testwsRPCBean'
tie='contactws.testwsGenServer.testwsRPC_Tie'
model='null'
wsdl='/WEB-INF/testws.wsdl'
service='{urn:testws/wsdl}Testws'
port='{urn:testws/wsdl}testwsRPCPort'
urlpattern='/testws'
</endpoint></endpoints>
I tried to access and check the web service using:
http://servername:port/testws/testws
The first testws is contextroot named and the second testws is url pattern, which was exactly like what you mentioned but I got "404 Not Found" error.
By the way, using the same ear to deploy to Windows Sun ONE App. Server 7 env. and then using the same url, I can access the web service. I am wondering if there is any special for deploying Web Service on Unix Sun ONE app. Server 7 env. or I missed something?
I hope I can hear from you soon.
Thank you again,
Jackie

Deploying a Web Service developed for WebSphere to Oracle App Server

I have an EAR file containing a web service (exposed as a servlet) that was developed using WebSphere Studio and originally deployed to a WebSphere application server. It should be J2EE 1.4 compliant. I now want to deploy it as a web service on Oracle Application Server.
Is it as simple as just deploying the EAR to OAS? Or do I need to (re-)assemble the EAR using the Web Service Assembler tool and then deploy it? What is the best practices approach for this scenario? My goal is to develop a web service that is deployable to both WebSphere and OAS with as little fuss as possible.
Thanks

using Ant.
check apache.org project there they have the ant section.
Regards

Get user name - web services throws error if a name has special character

I am calling UserProfileService.asmx web service and using GetUserPropertyByAccountName. The method works for almost everyone except for those who has special characters in the Preferred Name. How do I fix this? We are having serious production issues and
would like to know how to fix the issue.
User: domain\aberg returns name as the name does not have any special characters. Arthur Berg
User: domain\jobill returns following error because this use has a dash in the last name. Joe O-Bill
User: domain\mobrien returns following error because this use has a dash in the last name. Mark O'Brien
<?xml version="1.0" encoding="utf-16"?>
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<soap:Body>
<soap:Fault>
<faultcode>soap:Client</faultcode>
<faultstring>A user with the account name DOMAIN\jobill could not be found. ---> An error was encountered while retrieving the user profile.</faultstring>
<detail>
<ErrorCode xmlns="http://microsoft.com/webservices/SharePointPortalServer/UserProfileService">UserCannotBeFound</ErrorCode>
<ErrorMessage xmlns="http://microsoft.com/webservices/SharePointPortalServer/UserProfileService">An error was encountered while retrieving the user profile.</ErrorMessage>
</detail>
</soap:Fault>
</soap:Body>
</soap:Envelope>
I am using codeplex tool "web service studio 2.0" to verify this.

I have NO clue what is going on. When I go to user profile from Central Admin the user account is domainxp.net\username. But when I pull up the user using address bar (say in edit form) I see domain\usename. Could this be confusing the workflow which is
calling the web services?
I ran the following powershell and after few minutes it starting to resolve the user name without any errors. I like to know what is going on here. Problem is solved for now but I wont be surprise if I see the same problem after doing a Full AD sync.
$adUser = "domain\user"
$siteCollection = "http://local.site/sales"
Set-SPUser -Identity $adUser -Web $siteCollection -SyncFromAD
Thanks
Brooke

How can I invoke the web service manually in websphere?

Hi
I've developed a webservice application using Rational Application Developer (RAD). I deployed it in a websphere 6.1 application server, using the administration console to import the war file that I had previously exported with RAD.
My webservice application is listed in the "Enterprise Applications" section of websphere's administration console as started.
My question is: how can I invoke the web service manually? Is there some kind of websphere generated webpage that I can use to call it manually?
I tried http://<server:port>/<contextroot> and http://<server:port>/<contextroot>/<servicename> in a webbrowser, but it doesn't work. Is it possible to invoke the web service manually, or do I need to develop a client?
Thanks in advance
Pedro

Hi Bo Wang,
    Go to the Portal -> System Administration -> System Configuration
                           -> Portal Content folder
                           -> Open Visual Composer folder
    There you can see the Webservice Systems you have created through VC.
You can delete the unwanted system here.
Regards,
Shemim

Xml encoding on web service request in flex 3

The encoding of xml on the <mx:request> tag has changed
as of flex 3 build 185179. In prior builds I could bind a variable
that contained an XML fragment and it was left untouched. As of
build 185179 the "<" and">" characters are encoded as
< and > respectively. This breaks web services that
expect XML fragements as parameters, i.e. Microsoft SharePoint Web
Services. See attached code that used to work. Variables v and q
are determined at runtime. They are XML fragments set in
actionscript prior to calling the web service.

How are you calling the WebService from Flex??
I was seeing a very similar error when I tried to use the Generated Web Service classes to call my web service. But it didn't happen with the MXML approach.
Sorry I don't have an answer as to what causes this, I have been searching the web, posted here....
I'll follow up if I find anything.

WebServiceException When invoking secured ADF-BC web services on WebSphere

We built web services using ADF 11.1.1.7 RC1, and deployed to WebSphere ND 7.0.0.23
The web services are secured using OWSM policy:
@SecurityPolicy( { "oracle/wss11_saml_or_username_token_with_message_protection_service_policy" })
And we have a client java program which invokes the web services as follows:
MTOMFeature mtom = new MTOMFeature();
SecurityPolicyFeature sec_policy = new SecurityPolicyFeature("oracle/wss11_saml_token_with_message_protection_client_policy");
if (lCMAMService == null) {
generateFCMWebserviceUrl();
URL url = new URL(fcmUrl);
LCMAMService_Service lCMAMService_Service = null;
try {
lCMAMService_Service = new LCMAMService_Service(url);
} catch (WebServiceException wse) {
generateFCMWebserviceUrl(true);
URL physicalURL = new URL(fcmUrl);
lCMAMService_Service = new LCMAMService_Service(physicalURL);
lCMAMService = lCMAMService_Service.getLCMAMServiceSoapHttpPort(mtom, sec_policy);
Everything works fine in WebLogic. However, when running on WebSphere ND 7.0.0.23, the following exception were thrown:
javax.xml.ws.WebServiceException: Invalid or unsupported WebServiceFeature feature http://www.w3.org/ns/ws-policy
     at org.apache.axis2.jaxws.ExceptionFactory.createWebServiceException(ExceptionFactory.java:173)
     at org.apache.axis2.jaxws.ExceptionFactory.makeWebServiceException(ExceptionFactory.java:70)
     at org.apache.axis2.jaxws.ExceptionFactory.makeWebServiceException(ExceptionFactory.java:118)
     at org.apache.axis2.jaxws.feature.ClientFramework.addFeature(ClientFramework.java:56)
     at org.apache.axis2.jaxws.binding.BindingImpl.setFeatures(BindingImpl.java:138)
     at org.apache.axis2.jaxws.BindingProvider.initialize(BindingProvider.java:167)
     at org.apache.axis2.jaxws.BindingProvider.<init>(BindingProvider.java:73)
     at org.apache.axis2.jaxws.client.proxy.JAXWSProxyHandler.<init>(JAXWSProxyHandler.java:123)
     at org.apache.axis2.jaxws.client.proxy.JAXWSProxyHandler.<init>(JAXWSProxyHandler.java:114)
     at org.apache.axis2.jaxws.spi.ServiceDelegate.getPort(ServiceDelegate.java:615)
     at javax.xml.ws.Service.getPort(Service.java:133)
     at oracle.apps.epm.fcc.lcm.proxy.LCMAMService_Service.getLCMAMServiceSoapHttpPort(LCMAMService_Service.java:59)
     at oracle.apps.epm.fcc.lcm.common.FCMExportImportHandler.instantiateFCMService(FCMExportImportHandler.java:703)
It seems that in WebSphere, the security policy are not supported. Any idea what needs to be changed for the client code to work in WebSphere?
Thanks.

Hi,
as you are from Oracle, can you reach out to internal forums and mailing lists? JDeveloper 11.1.1.7 RC1 is not available outside of Oracle and therefore should not have questions posted on this public forum.
Frank

Bypass Adapter URI Endpoint with Escape Character for Web Service

Dear All,
I would like to apply by pass adapter URI Endpoint for XI webservice, the default format is
http://<host>:<port>/sap/xi/engine?type=entry&version=3.0&Sender.Service=<BusinessService>&Interface=<namespace>^<Outbound Interface name>
If I am using format using with carat () character then there has no problem to the service, but consumer doesn't support carat () character. I instead the carat (^) with URL Escape Character (%5E)
http://<host>:<port>/sap/xi/engine?type=entry&version=3.0&Sender.Service=<BusinessService>&Interface=<namespace>%5E<Outbound Interface name>
Then error occurred
<SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
   <SOAP:Body>
      <SOAP:Fault>
         <faultcode>SOAP:Server</faultcode>
         <faultstring>System Error</faultstring>
         <detail>
            <s:SystemError xmlns:s="http://sap.com/xi/WebService/xi2.0">
               <context/>
               <code>RCVR_DETERMINATION.MESSAGE_INCOMPLETE</code>
               <text>Message is incomplete. No Sender found</text>
            </s:SystemError>
         </detail>
      </SOAP:Fault>
   </SOAP:Body>
</SOAP:Envelope>
How to resolve this error...
Thank you.
Regards,
Weng

Hi ,
as per my knowledge.....................
When you create a WSDL with the help of a wizard. In the Integration Directory, choose Tools -> Define Web Service to enter the wizard.
On Propose URL button, as this genertated URL default Point to Entegration Engine.. SO already proformance wise Good.
If You want to Point your URL to adapter engine , use below given URL this will point ur incoming soap message to SOAPadapter sender channel
http://<host>:<j2ee-port>/XISOAPAdapter/MessageServlet?channel=:<service>:<channel>.
Regards
Prabhat Sharma.

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

RPC/SOAP-Encoded Web Service with Workshop

Is there anyway to create a RPC/SOAP-Encoded Web Service with Workshop ? There is an "encoding" attribute in the autotype ant task but no corresponding properties in Workshop.

Hi,
Thanks for the reference.
I have checked both in the wsdl and the Soap message,
rpc property effectively means rpc/encoded. Now that
would say that RPC/Literal is not supported ?
Here are what the messages looks like with rpc and
document properties
Thanks all for making this clear.
document wlw property = Document/Literal
<SOAP-ENV:Envelope xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<SOAP-ENV:Body SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
<ns:getEmployeeResponse xmlns:ns="http://www.openuri.org/">
<ns:getEmployeeResult xmlns:ns="http://www.openuri.org/">
<ns:Address xmlns:ns="http://www.openuri.org/">
<ns:City xmlns:ns="http://www.openuri.org/">Luxembourg</ns:City>
<ns:Country xmlns:ns="http://www.openuri.org/">LU</ns:Country>
<ns:Number xmlns:ns="http://www.openuri.org/">2</ns:Number>
<ns:PostCode xmlns:ns="http://www.openuri.org/">1000</ns:PostCode>
<ns:Street xmlns:ns="http://www.openuri.org/">Bld. Royal</ns:Street>
</ns:Address>
<ns:Age xmlns:ns="http://www.openuri.org/">20</ns:Age>
<ns:Name xmlns:ns="http://www.openuri.org/">Dupont</ns:Name>
<ns:FirstNames xmlns:ns="http://www.openuri.org/">
<ns:String xmlns:ns="http://www.openuri.org/">Jean</ns:String>
<ns:String xmlns:ns="http://www.openuri.org/">Jacques</ns:String>
</ns:FirstNames>
</ns:getEmployeeResult>
</ns:getEmployeeResponse>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
rpc wlw property = RPC/Soap-Encoded
<SOAP-ENV:Envelope xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<SOAP-ENV:Body SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
<ns:getEmployeeResponse xmlns:ns="http://www.openuri.org/">
<getEmployeeResult xmlns:s="http://www.openuri.org/encodedTypes" xsi:type="s:Employee">
<Address xsi:type="s:Address">
<City xsi:type="xsd:string">Luxembourg</City>
<Country xsi:type="xsd:string">LU</Country>
<Number xsi:type="xsd:int">2</Number>
<PostCode xsi:type="xsd:string">1000</PostCode>
<Street xsi:type="xsd:string">Bld. Royal</Street>
</Address>
<Age xsi:type="xsd:int">20</Age>
<Name xsi:type="xsd:string">Dupont</Name>
<FirstNames SOAP-ENC:arrayType="xsd:string[2]" xsi:type="SOAP-ENC:Array">
<String xsi:type="xsd:string">Jean</String>
<String xsi:type="xsd:string">Jacques</String>
</FirstNames>
</getEmployeeResult>
</ns:getEmployeeResponse>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
Message was edited by phcollignon at Aug 27, 2004 2:54 AM

How to use Flash Media Live Encoder as a web Service

Coud we use the Flash Media Live Encoder as a Web Service installed on another Server (Preferebaly on the Flash Media Server Itself).

FMLE is typically used on the client side, and it doesn't have any sort of API that you would use to run it as a service. That said, unless you wanted to publish a camera that is connected to the server, I'm not sure why you'd want to run FMLE as a service.
Perhaps if you explain what is is you want to accomplish....

Web services websphere 5.1 encoding character

Similar Messages

Maybe you are looking for