Using TCP Tunnel to examine SOAP messages to an external web service

I am trying to examine the SOAP communication between my BPEL flow and an external webservice with WSDL at:
http://www.webservicex.net/CurrencyConvertor.asmx?WSDL
How should I modify the deployment descriptor for my flow (bpel.xml), to add a "location" property to override the endpoint of this external service, so I can see the the messages exchanged through the tunnel.
Thanks and Best Regards.
Jaidev

I've changed the port number to 1234 as defaulted in obtunnel in a client program
<?xml version = '1.0' encoding = 'UTF-8'?>
<BPELSuitcase>
<BPELProcess id="worklistClient" src="worklistClient.bpel">
<partnerLinkBindings>
<partnerLinkBinding name="client">
<property name="wsdlLocation">worklistClient.wsdl</property>
</partnerLinkBinding>
<partnerLinkBinding name="PartnerLink_1">
<property name="wsdlLocation">http://wzscqz05.....com:1234/orabpel/test/BPELWorkList/BPELWorkList?wsdl</property>
</partnerLinkBinding>
</partnerLinkBindings>
</BPELProcess>
</BPELSuitcase>

Similar Messages

Consuming an External Web Service using HTTPS and WS Security

Hello everyone,
I'm having a problem setting the security information in a SOAP header using a generated ABAP Client Proxy to consume an external web service that requires a User ID and Password in the Header section of the SOAP message. I need to use HTTPS. I'm on a WAS 7.01 SP08 system so from my readings, SAP is supposed to be able to add the username and password into the header section of the message. I can't seem to get SAP to add this information added to the header.
Here are the steps that I have taken to set the security values.
1) Created the client proxy from the WSDL in SE80. Basic Authentication on the Configuration tab was turned on automatically.
Note, Transport Security is set to None. I cannot change it.
2) Created an outbound set user name profile in transaction WSPROFILE with the appropriate username and password.
3) Added the profile to the default port in transaction LPCONFIG as an outbound under the WS Security section of the screen.
When I called the external Web Service, I got back the following error message:
com.ibm.wsspi.wssecurity.SoapSecurityException: WSEC5509E: A security token whose type is [http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#UsernameToken] is required.
So, after reading through this Forum, I saw that I needed to use the SOAMANAGER. I set up a Proxy in the SOAMANAGER and manually created the Logical Port. This was the only way I could figure out how to set the Authentication Settings in the Logical Port to "User ID / Password". I then entered the User ID and Password.
However, I am still getting the same error message. I feel I am close but missing some small configuration to tell SAP to use WS Security with a Username token.
I'm not sure what I'm doing wrong, so any help would be appreciated.
Thanks,
Stephen

I had this error again so I thought I would post my solution:
The issue is SAP needs to know the certificates being used by the web site being called. These certificates are automatically installed in your browser but need to be manually installed in SAP. This is what I did:
How to find/install new certificates
Make sure you run Internet Explorer as an Administrator so you can export the certificates
Go to the web site that SAP is trying to call in Internet Explorer
Double click on the lock in the address bar
View certificates
Find the certificates that are being used
Tools --> Internet Options --> Content --> Certificates
Click on the “Trusted Root Certification Authorities” tab
Find the certificate identified in step iii
Export as a CER certificate
Click on the “Intermediate Certification Authorities” tab
Find the certificate identified in step iii
Export as a CER certificate
Go to STRUST in SAP
Import the Certificates in the “Anonymous” or “Standard” SSL client
Save
RESTART the ICM via t-code SMICM <-- Critical!!!
Test

MDB receive a message and then call an external web service

Title basically says it all, but I'm looking for suggestions for the best way to have a message driven bean receive a message then process it and call an external web service with the results. This seems like a straightforward problem to solve but I keep getting stuck in the deployment to weblogic when I do it my way so I'm looking for new ideas.
Basically, I have an MDB that gets deployed to WL 10.3 and receives messages just fine. Also, I have a standalone class, that runs from the command line or IDE, that can send messages to the external web service. But when I try to bring the code from the standalone class into the MDB and get it deployed, I can't get all the dependencies to resolve.
So, is there a proper (quick and easy) way to do this? Which wizard should I be using to get Workshop to create web service client so that I can use it in my MDB project? Any suggestions to tutorials?
Thanks,
Matt

Yes BusinessService is the reference point used in OSB to call a backend provider service. So we need to configure the business service based on the external service (they can be http based, jms based, etc ..)
In your case I am assuming it is a http based web service. So below are the steps to be done:
1. Create a business service (if you dont have a wsdl then create it as "Any soap type" else upload the wsdl as a wsdl resource and then use it) and configure the url of the business service with the URL of the external service you want to invoke.
2. From the proxy flow, have a service callout action and select the business service. Then configure the appropriate body and header variables.
3. Then test the proxy service from the test console, you should be able to see the response from the external service as a part of the service callout response.
Let me know if you still have issues.
Thanks,
Patrick

How can make java servlet sent soap message to other java web application

hello,
i want to make simple servlet send soap message to other java web application containing web service????
for example
web application " A " contain web service add two number
java servlet " B " send soap message contain num1 and num2 to A to add them.
how can do this????

I tried that but my problem is that the code is so old. At least what I saw. I don't know how old is too old and I'm trying to do things "right." I saw code from 1998, but I don't know if that's still what you do. It might still work, but that doesn't mean it's correct. There's so much out there on Java that so old that half the time I'm not sure what to do because some other technology in J2EE or the latest Java SDK might have come up with a new way to do things. Thanks.

Using an external web service and local element declarations

I am attempting to use (call) an external web service from workshop
8.1. It seems that if the web service's schema contains local element
declarations with the same name then workshop will generate incorrect
JCX code because it doesn't scope the generated classes.
I think the following simple example will do a better job explaining
than that last paragraph ;). In the following WSDL, the element
"testLocalDec" is used inside two different element types. In XML
Schema this is not a problem because each one is "scoped" by the
element types its included in. However, the generated JCX (listed
second) simply contains the testLocalDec structure twice which causes
problems in Java.
Is there some workaround for this? Note that making this element
declaration in the WSDL will not work because they are different
structures (with different names).
Also see my next email around using XMLBeans with external services
(since that could be a workaround if I knew how to do it).
thanks,
dave
*** sample WSDL ***
<?xml version="1.0" encoding="UTF-8"?>
<wsdl:definitions xmlns:tns="urn:tutorial/hello"
targetNamespace="urn:tutorial/hello"
xmlns:s="http://www.w3.org/2001/XMLSchema"
xmlns="http://schemas.xmlsoap.org/wsdl/"
xmlns:apachesoap="http://xml.apache.org/xml-soap"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<wsdl:types>
<s:schema targetNamespace="urn:tutorial/hello">
     <s:element name="sayHelloResponse" >
<s:complexType>
<s:sequence>
<s:element name="sayHelloReturn" type="s:string" />
<s:element name="testLocalDec" >
<s:complexType />
</s:element>
</s:sequence>
</s:complexType>
</s:element>
     <s:element name="sayHello" >
<s:complexType>
<s:sequence>
<s:element name="caller" type="s:string" />
<s:element name="testLocalDec" >
<s:complexType >
<s:sequence>
<s:element name="different" type="s:string" />
</s:sequence>
</s:complexType>
</s:element>
</s:sequence>
</s:complexType>
</s:element>
</s:schema>
</wsdl:types>
<wsdl:message name="sayHelloRequestMsg">
<wsdl:part name="message" element="tns:sayHello"/>
</wsdl:message>
<wsdl:message name="sayHelloResponseMsg">
<wsdl:part name="sayHelloReturn" element="tns:sayHelloResponse"/>
</wsdl:message>
<wsdl:portType name="HelloWorld">
<wsdl:operation name="sayHello" >
<wsdl:input message="tns:sayHelloRequestMsg" />
<wsdl:output message="tns:sayHelloResponseMsg" />
</wsdl:operation>
</wsdl:portType>
<wsdl:binding name="HelloWorldServiceSoapBinding"
type="tns:HelloWorld">
<wsdlsoap:binding style="document"
transport="http://schemas.xmlsoap.org/soap/http"/>
<wsdl:operation name="sayHello">
<wsdlsoap:operation soapAction=""/>
<wsdl:input name="sayHelloRequestMsg">
<wsdlsoap:body use="literal"/>
</wsdl:input>
<wsdl:output name="sayHelloResponseMsg">
<wsdlsoap:body use="literal"/>
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
<wsdl:service name="HelloWorldService">
<wsdl:port binding="tns:HelloWorldServiceSoapBinding"
name="HelloWorldService">
<wsdlsoap:address
location="http://localhost:18080/tutorial/HelloWorldService"/>
</wsdl:port>
</wsdl:service>
</wsdl:definitions>
*** generated JCX ***
package helloTest;
* @jc:location
http-url="http://localhost:18080/tutorial/HelloWorldService"
* @jc:wsdl file="#HelloWorldServiceWsdl"
* @editor-info:link source="HelloWorldService.wsdl" autogen="true"
public interface HelloWorldServiceControl extends
com.bea.control.ControlExtension, com.bea.control.ServiceControl
public static class testLocalDec
implements java.io.Serializable
public static class sayHelloResponse
implements java.io.Serializable
public java.lang.String sayHelloReturn;
public testLocalDec testLocalDec;
public static class testLocalDec
implements java.io.Serializable
public java.lang.String different;
* @jc:protocol form-post="false" form-get="false"
public sayHelloResponse sayHello (java.lang.String caller,
testLocalDec testLocalDec);
static final long serialVersionUID = 1L;
/** @common:define name="HelloWorldServiceWsdl" value::
<?xml version="1.0" encoding="UTF-8"?>
<wsdl:definitions xmlns:tns="urn:tutorial/hello"
targetNamespace="urn:tutorial/hello"
xmlns:s="http://www.w3.org/2001/XMLSchema"
xmlns="http://schemas.xmlsoap.org/wsdl/"
xmlns:apachesoap="http://xml.apache.org/xml-soap"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<wsdl:types>
<s:schema targetNamespace="urn:tutorial/hello">
     <s:element name="sayHelloResponse" >
<s:complexType>
<s:sequence>
<s:element name="sayHelloReturn" type="s:string" />
<s:element name="testLocalDec" >
<s:complexType />
</s:element>
</s:sequence>
</s:complexType>
</s:element>
     <s:element name="sayHello" >
<s:complexType>
<s:sequence>
<s:element name="caller" type="s:string" />
<s:element name="testLocalDec" >
<s:complexType >
<s:sequence>
<s:element name="different" type="s:string" />
</s:sequence>
</s:complexType>
</s:element>
</s:sequence>
</s:complexType>
</s:element>
</s:schema>
</wsdl:types>
<wsdl:message name="sayHelloRequestMsg">
<wsdl:part name="message" element="tns:sayHello"/>
</wsdl:message>
<wsdl:message name="sayHelloResponseMsg">
<wsdl:part name="sayHelloReturn"
element="tns:sayHelloResponse"/>
</wsdl:message>
<wsdl:portType name="HelloWorld">
<wsdl:operation name="sayHello" >
<wsdl:input message="tns:sayHelloRequestMsg" />
<wsdl:output message="tns:sayHelloResponseMsg" />
</wsdl:operation>
</wsdl:portType>
<wsdl:binding name="HelloWorldServiceSoapBinding"
type="tns:HelloWorld">
<wsdlsoap:binding style="document"
transport="http://schemas.xmlsoap.org/soap/http"/>
<wsdl:operation name="sayHello">
<wsdlsoap:operation soapAction=""/>
<wsdl:input name="sayHelloRequestMsg">
<wsdlsoap:body use="literal"/>
</wsdl:input>
<wsdl:output name="sayHelloResponseMsg">
<wsdlsoap:body use="literal"/>
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
<wsdl:service name="HelloWorldService">
<wsdl:port binding="tns:HelloWorldServiceSoapBinding"
name="HelloWorldService">
<wsdlsoap:address
location="http://localhost:18080/tutorial/HelloWorldService"/>
</wsdl:port>
</wsdl:service>
</wsdl:definitions>

Hi David,
The folks in the workshop newgroup may have a suggestion, if you could
try your post there:
http://newsgroups.bea.com/cgi-bin/dnewsweb?cmd=xover&group=weblogic.developer.interest.workshop
Thanks,
Bruce
David Rees wrote:
>
I am attempting to use (call) an external web service from workshop
8.1. It seems that if the web service's schema contains local element
declarations with the same name then workshop will generate incorrect
JCX code because it doesn't scope the generated classes.
I think the following simple example will do a better job explaining
than that last paragraph ;). In the following WSDL, the element
"testLocalDec" is used inside two different element types. In XML
Schema this is not a problem because each one is "scoped" by the
element types its included in. However, the generated JCX (listed
second) simply contains the testLocalDec structure twice which causes
problems in Java.
Is there some workaround for this? Note that making this element
declaration in the WSDL will not work because they are different
structures (with different names).
Also see my next email around using XMLBeans with external services
(since that could be a workaround if I knew how to do it).
thanks,
dave
*** sample WSDL ***
<?xml version="1.0" encoding="UTF-8"?>
<wsdl:definitions xmlns:tns="urn:tutorial/hello"
targetNamespace="urn:tutorial/hello"
xmlns:s="http://www.w3.org/2001/XMLSchema"
xmlns="http://schemas.xmlsoap.org/wsdl/"
xmlns:apachesoap="http://xml.apache.org/xml-soap"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<wsdl:types>
<s:schema targetNamespace="urn:tutorial/hello">
<s:element name="sayHelloResponse" >
<s:complexType>
<s:sequence>
<s:element name="sayHelloReturn" type="s:string" />
<s:element name="testLocalDec" >
<s:complexType />
</s:element>
</s:sequence>
</s:complexType>
</s:element>
<s:element name="sayHello" >
<s:complexType>
<s:sequence>
<s:element name="caller" type="s:string" />
<s:element name="testLocalDec" >
<s:complexType >
<s:sequence>
<s:element name="different" type="s:string" />
</s:sequence>
</s:complexType>
</s:element>
</s:sequence>
</s:complexType>
</s:element>
</s:schema>
</wsdl:types>
<wsdl:message name="sayHelloRequestMsg">
<wsdl:part name="message" element="tns:sayHello"/>
</wsdl:message>
<wsdl:message name="sayHelloResponseMsg">
<wsdl:part name="sayHelloReturn" element="tns:sayHelloResponse"/>
</wsdl:message>
<wsdl:portType name="HelloWorld">
<wsdl:operation name="sayHello" >
<wsdl:input message="tns:sayHelloRequestMsg" />
<wsdl:output message="tns:sayHelloResponseMsg" />
</wsdl:operation>
</wsdl:portType>
<wsdl:binding name="HelloWorldServiceSoapBinding"
type="tns:HelloWorld">
<wsdlsoap:binding style="document"
transport="http://schemas.xmlsoap.org/soap/http"/>
<wsdl:operation name="sayHello">
<wsdlsoap:operation soapAction=""/>
<wsdl:input name="sayHelloRequestMsg">
<wsdlsoap:body use="literal"/>
</wsdl:input>
<wsdl:output name="sayHelloResponseMsg">
<wsdlsoap:body use="literal"/>
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
<wsdl:service name="HelloWorldService">
<wsdl:port binding="tns:HelloWorldServiceSoapBinding"
name="HelloWorldService">
<wsdlsoap:address
location="http://localhost:18080/tutorial/HelloWorldService"/>
</wsdl:port>
</wsdl:service>
</wsdl:definitions>
*** generated JCX ***
package helloTest;
* @jc:location
http-url="http://localhost:18080/tutorial/HelloWorldService"
* @jc:wsdl file="#HelloWorldServiceWsdl"
* @editor-info:link source="HelloWorldService.wsdl" autogen="true"
public interface HelloWorldServiceControl extends
com.bea.control.ControlExtension, com.bea.control.ServiceControl
public static class testLocalDec
implements java.io.Serializable
public static class sayHelloResponse
implements java.io.Serializable
public java.lang.String sayHelloReturn;
public testLocalDec testLocalDec;
public static class testLocalDec
implements java.io.Serializable
public java.lang.String different;
* @jc:protocol form-post="false" form-get="false"
public sayHelloResponse sayHello (java.lang.String caller,
testLocalDec testLocalDec);
static final long serialVersionUID = 1L;
/** @common:define name="HelloWorldServiceWsdl" value::
<?xml version="1.0" encoding="UTF-8"?>
<wsdl:definitions xmlns:tns="urn:tutorial/hello"
targetNamespace="urn:tutorial/hello"
xmlns:s="http://www.w3.org/2001/XMLSchema"
xmlns="http://schemas.xmlsoap.org/wsdl/"
xmlns:apachesoap="http://xml.apache.org/xml-soap"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<wsdl:types>
<s:schema targetNamespace="urn:tutorial/hello">
<s:element name="sayHelloResponse" >
<s:complexType>
<s:sequence>
<s:element name="sayHelloReturn" type="s:string" />
<s:element name="testLocalDec" >
<s:complexType />
</s:element>
</s:sequence>
</s:complexType>
</s:element>
<s:element name="sayHello" >
<s:complexType>
<s:sequence>
<s:element name="caller" type="s:string" />
<s:element name="testLocalDec" >
<s:complexType >
<s:sequence>
<s:element name="different" type="s:string" />
</s:sequence>
</s:complexType>
</s:element>
</s:sequence>
</s:complexType>
</s:element>
</s:schema>
</wsdl:types>
<wsdl:message name="sayHelloRequestMsg">
<wsdl:part name="message" element="tns:sayHello"/>
</wsdl:message>
<wsdl:message name="sayHelloResponseMsg">
<wsdl:part name="sayHelloReturn"
element="tns:sayHelloResponse"/>
</wsdl:message>
<wsdl:portType name="HelloWorld">
<wsdl:operation name="sayHello" >
<wsdl:input message="tns:sayHelloRequestMsg" />
<wsdl:output message="tns:sayHelloResponseMsg" />
</wsdl:operation>
</wsdl:portType>
<wsdl:binding name="HelloWorldServiceSoapBinding"
type="tns:HelloWorld">
<wsdlsoap:binding style="document"
transport="http://schemas.xmlsoap.org/soap/http"/>
<wsdl:operation name="sayHello">
<wsdlsoap:operation soapAction=""/>
<wsdl:input name="sayHelloRequestMsg">
<wsdlsoap:body use="literal"/>
</wsdl:input>
<wsdl:output name="sayHelloResponseMsg">
<wsdlsoap:body use="literal"/>
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
<wsdl:service name="HelloWorldService">
<wsdl:port binding="tns:HelloWorldServiceSoapBinding"
name="HelloWorldService">
<wsdlsoap:address
location="http://localhost:18080/tutorial/HelloWorldService"/>
</wsdl:port>
</wsdl:service>
</wsdl:definitions>

Issue with calling an external web service using web service proxy

Hi,
I've created several web services using JDeveloper succesfully in the past, however I'm getting an issue with one that was working ok previously. Have spoken to the developers of the external web service and they say they haven't changed anything. Also if I test the external web service through soapUI for example it seems fine so it would seem that the issue is with the autogenerated code created by JDeveloper.
Basically I get the following exception as it sends the request to the external service:
java.security.PrivilegedActionException: javax.xml.soap.SOAPException: Message send failed: Bad Authentication header format: 'Basic realm="Integration Server" encoding="UTF-8"'
Expected "," at position 33
The user name/password appear correct.
JDev version 10.1.3.42.70
Any ideas?
Many Thanks
Gary
Edited by: user10916721 on 08-May-2012 09:54

Found the answer. Basically I had one proxy web service working and one not both linking to a middle tier written in web methods. THe issue actually ended up being with the web methods code in that the one web service (that was not working) was put together using a backwards compatability mode. Once this was switched back then started working again in JDev.

HELP Using Oracle9i database to consume external Web Service

Hi all,
I am trying to make use Oracle9i db to call an external .Net Web Service from a JAva Stored Procedure.
I created the .Net Web Service and use JDeveloper 9.0.3.4Build(1247) to create the Client Stub Java class(ie: serviceClientStub.java).
Following the instruction from the article"Calling External Web Service from Java Stored Procedure, http://otn.oracle.com/sample_code/tech/java/jsp/samples/wsclient/Readme.html, I connected to the database using SQL Navigator4.3 tried to load the required jar files(with Create public synonym and Resolve option checked) into Oracle9i database(ver 9.2.0.1.0). They are loaded in the following order:
[OC4J_HOME]/soap/lib/soap.jar
[OC4J_HOME]/lib/dms.jar
[OC4J_HOME]/jlib/javax-ssl-1_1.jar
[ORACLE_HOME]/lib/servlet.jar
[OC4J_HOME]/jdk/jre/lib/ext/mail.jar
Where [OC4J_HOME] refers to Oc4j_extended that I downloaded from Oracle website.
[ORACLE_HOME] refers to oracle/ora90
However, most of the java classes failed to compiled. When I loaded the Client Stub class, it failed to compile as well.
This is the error message that I got:
ORA-29521: referenced name javax/mail/Flags could not be found
ORA-29521: referenced name javax/mail/MessageException could not be found
ORA-29521: referenced name javax/mail/MethodNotSupportedException could not be found
Any ideas how to resolve these issues?
Also, besides using the Client Soap stack library(above method), is there another way to be able to load the Client Stub class in the database, have it compiled successfully?
Your assistance will be highly appreciated!

As far as I can see, you're at least missing activation.jar. Without this library you won't be able to successfully load the mail.jar library.

Error when calling an external web service (blank soap action)

I did a lot of searching on this message and did not find an answer. Most of the issues i found related to XI/PI, which we are not using.
There is a web service created outside of SAP for which i generated (from the WSDL) a proxy class in my DEV system, client 050, a few years ago. This was subsequently moved to QA and production, and all is working fine.
Now, i want the same web service to work in client 100. I created the logical port, and the RFC destination, but when i try to call the web service, i get the following error
Server did not recognize the value of HTTP Header SOAPAction
Since only the basis group around here can access the logical port definition,and rfc destination, i have no idea where this information should be set up. I should not have to reimport the WSDL, since the proxy was imported from DEV to QA and it is working in QA client 050. There is something i need to set up, specific to client 100, and i am missing it. I looked in SOAMANAGER, and i didnt see anything even set up there for client 050, so i did set up anything for client 100.
Any help would be appreciated.

I tried adding the web reference in a console app and works fine. In the plugins this can't be done, because the plugins are deploy in database.
I tried another basic test using ChannelFactory. Only want to retrieve some entity through the external web services:
IPluginExecutionContext context = localContext.PluginExecutionContext;
IOrganizationService service = localContext.OrganizationService;
ITracingService tracer = localContext.TracingService;
try
BasicHttpBinding binding = new BasicHttpBinding();
binding.Name = "BasicHttpBinding_IAxxisWcfServices";
binding.Security.Mode = BasicHttpSecurityMode.None;
binding.Security.Transport.ProxyCredentialType = HttpProxyCredentialType.None;
binding.Security.Transport.ClientCredentialType = HttpClientCredentialType.None;
EndpointAddress endpoint = new EndpointAddress(@"http://*****.svc");
ChannelFactory<IAxxisWcfServices> factory = new ChannelFactory<IAxxisWcfServices>(binding, endpoint);
IAxxisWcfServices channel = factory.CreateChannel();
var entity = channel.FindByEntities(new CRM.Application.Context.Dtos.Asegurado( { CrmGuid = "7C3E96C6-C3BC-E411-80DF-0A736AE14667" }, null, new CRM.Framework.Session() { User = "***", Password = "***" });
catch (Exception ex)
throw new InvalidPluginExecutionException(ex.Message);
That test threw the following exception on the GenericParameterAttributes of channelType of factory object:
http://s27.postimg.org/4wf3er8up/Error.png

Use BizTalk 2006 as a proxy for an external Web Service

Hi
We have a solution that is going to work just as a proxy for an external Web Service.
It works like this:
1. We have a Request-Response receive port that receives the calls for the WS.
2. Different Static Solicit-Response ports that have filters for each method in the WS receive the requests and then send them to the external WS.
3. The response from the external WS is then sendt back to the caller via the Request-Response port in point 1.
This generally works like it should. The only problem i have is when the external WS returns a Fault message. I get this fault from the external WS:
<s:Fault xmlns:s="http://schemas.xmlsoap.org/soap/envelope/"><faultcode>s:Client</faultcode><faultstring xml:lang="nb-NO">Some error message the caller should see.</faultstring><detail><GenericFault
xmlns="http://register.test.com/Common" xmlns:i="http://www.w3.org/2001/XMLSchema-instance"><ErrorCode>SomthingWentWrong</ErrorCode><Message>Some error message the caller should see.</Message></GenericFault></detail></s:Fault>
This message then failes on BizTalk and BizTalk returns this Fault message to the caller:
<SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"><SOAP:Body><SOAP:Fault><faultcode>Microsoft BizTalk Server Negative Acknowledgment
</faultcode><faultstring>An error occurred while processing the message, refer to the details section for more information </faultstring><faultactor>/Hemit.BizTalk.NHN.Position.ws/IPositionService.asmx</faultactor><detail><ns0:NACK
Type="NACK" xmlns:ns0="http://schema.microsoft.com/BizTalk/2003/NACKMessage.xsd"><NAckID>{7AC314FE-2CA3-44AE-8208-180495500481}</NAckID><ErrorCode>0xc0c016b7</ErrorCode><ErrorCategory>0</ErrorCategory><ErrorDescription>There
is an error in XML document (1, 2).</ErrorDescription><ErrorDetail><Fault xmlns='http://schemas.xmlsoap.org/soap/envelope/'> was not expected.</ErrorDetail></ns0:NACK></detail></SOAP:Fault></SOAP:Body></SOAP:Envelope>
So the problem seems to be that the Request-Response port in point one will ONLY accept the real response that is specified in the response schema for that particular method, and not a Fault. And when it receives a fault, it generates its own Fault saying
a Fault message was not expected.
Does anyone know how i can be able to send the actual fault from the external WS all the way back to the caller on the inside?
I know how to do it with an orchestration, but can not figure out how to get it done just with the ports.
Kind regars
John Viggo

Hi John,
Enable Propagate fault message
on the WCF solict –response port.
For the two-way send port, you can choose whether to forward
SOAP fault messages on to the original caller over a solicit-response send port by selecting
Propagate fault message. If this option is not selected, BizTalk Server will generate a NACK. What you see is the NACK.
If it is selected, BizTalk Server will treat the message as a valid WCF response message from the external service and the response message will not be suspended because it is propagated.
Then you need to map the fault message to the actual response in the map. Set this Fault-Message to Caller-Response map in the outbound map of the Requeust-Response port.
In this case of messaging-only scenario, this method shall help in handling the fault message and passing fault details back to the caller. Refer the following articles for more details.
Synchronous web services calls and Faults
BizTalk and
SOAPFault
version issues
If this answers your question please mark it accordingly. If this post is helpful, please vote as helpful.

How to retrieve error message(s) after failed web service call

Hi!
I tried to create an item using the web service ego_item_pub.process_item and it worked ok (version 12.1.1). Sending the same request again, I got an error which should be ok since the item id already exists. The thing is, that I only get an "E" as return status:
<X_RETURN_STATUS>E</X_RETURN_STATUS>
<X_MSG_COUNT>1</X_MSG_COUNT>
As described in the integration repository, there should be a parameter called msg_data which should contain the message if there is exactly 1 message, but I cannot find it.
So, I tried to get the message using fnd_message.get, but the response of my web service call is:
AuthorizationFailure : User not authorized to execute service. (I use sysadmin/sysadmin as ws security user).
I use the following grant details:
All Users Direct GLOBAL Revoke Action Enabled
SYSADMIN SYSADMIN Direct USER
What else can I do or how can I retrieve error messages for a failed web service call?
Thanks a lot,
Konrad

Hi Konrad,
As we've found out, search the Integration Repository for internal name ERROR_HANDLER and use that. Letting the general public know the answer for this one!
Regards,
Gareth
http://garethroberts.blogspot.com

Problems using external web service

I am trying to access an external web service running on tomcat 4.1. have created
a service control from the WSDL of the web service. when i run it with the test
form/xmlbrowser it comes up with this error.
Exception in createInteraction
com.bea.control.ServiceControlException: env:ServerInternal Server Error (unexpected
encoding style: expected=http://schemas.xmlsoap.org/soap/encoding/, actual=)
It has the url as seen in the header below:
<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">
Is there some incompatability problems between weblogic8.1 and tomcat4.1

Keith,
can you attach the WSDL you are trying to connect to ?
Regards,
Raj Alagumalai
Backline Workshop Support
"Keith Marshall" <[email protected]> wrote in message
news:3f79558a$[email protected]..
>
I am trying to access an external web service running on tomcat 4.1. havecreated
a service control from the WSDL of the web service. when i run it withthe test
form/xmlbrowser it comes up with this error.
Exception in createInteraction
com.bea.control.ServiceControlException: env:ServerInternal Server Error(unexpected
encoding style: expected=http://schemas.xmlsoap.org/soap/encoding/,
actual=)
>
It has the url as seen in the header below:
<SOAP-ENV:Envelopexmlns: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">
Is there some incompatability problems between weblogic8.1 and tomcat4.1

SOAP Response from PL/SQL Web Service

My returned SOAP xml from PL/SQL web service has totally rearranged element order, which defined in WSDL and oracle database. It also changed all element name from mixed upper/lower case to pure lower case and makes them hard to read. Why is that? Is there any way to avoid these to happen?
My PL/SQL web service was generated by Oracle9i JDeveloper 9.0.3.
Thanks for any help.
Yi

Hi,
we need more details
- it seems like you have both Return and OUT arguments; which SOAP stack are you using?
- which tools?
- What is the naming convention of your PL/SQL arguments?
Kuassi
Mike,
1. The SOAP is the result of publishing a stored procedure/function as a Web service.
2. The elements for returned data are re-ordered. The function returns no complex type.
3. The element tags containing returned data are all changed to lower case.
Here are what I expected for returning SOAP:
<return xmlns:ns2="http://oracle817/IDemogprofilews.xsd" xsi:type="ns2:oracle817_ODemog">
<OFipsCode xsi:type="xsd:string">51059</ OFipsCode >
<TotalPopulation xsi:type="xsd:double">818584.0</ TotalPopulation >
<PercentMinority xsi:type="xsd:double">22.5</ PercentMinority >
<PersonsBelowPovertyLevel xsi:type="xsd:double">28210.0</ PersonsBelowPovertyLevel >
<HouseholdsInArea xsi:type="xsd:double">292943.0</ HouseholdsInArea >
<HousingUnitsBuiltBefore1950 xsi:type="xsd:double">5.2</ HousingUnitsBuiltBefore1950 >
<White xsi:type="xsd:double">666349.0</ White >
<HispanicOrigin xsi:type="xsd:double">50526.0</ HispanicOrigin >
<AmericanIndian xsi:type="xsd:double">2318.0</ AmericanIndian >
<HighSchoolDiploma xsi:type="xsd:double">91675.0</ HighSchoolDiploma >
<BachelorAndHigher xsi:type="xsd:double">264673.0</ BachelorAndHigher >
<Adults18yearsAndOlder xsi:type="xsd:double">618989.0</ Adults18yearsAndOlder >
<Seniors65yearsAndOlder xsi:type="xsd:double">52977.0</ Seniors65yearsAndOlder >
Instead I get following back:
<return xmlns:ns2="http://oracle817/IDemogprofilews.xsd" xsi:type="ns2:oracle817_ODemog">
<totalpopulation xsi:type="xsd:double">818584.0</totalpopulation>
<americanindian xsi:type="xsd:double">2318.0</americanindian>
<housingunitsbuiltbefore1950 xsi:type="xsd:double">5.2</housingunitsbuiltbefore1950>
<hispanicorigin xsi:type="xsd:double">50526.0</hispanicorigin>
<highschooldiploma xsi:type="xsd:double">91675.0</highschooldiploma>
<adults18yearsandolder xsi:type="xsd:double">618989.0</adults18yearsandolder>
<seniors65yearsandolder xsi:type="xsd:double">52977.0</seniors65yearsandolder>
<householdsinarea xsi:type="xsd:double">292943.0</householdsinarea>
<personsbelowpovertylevel xsi:type="xsd:double">28210.0</personsbelowpovertylevel>
<ofipscode xsi:type="xsd:string">51059</ofipscode>
<bachelorandhigher xsi:type="xsd:double">264673.0</bachelorandhigher>
<white xsi:type="xsd:double">666349.0</white>
<percentminority xsi:type="xsd:double">22.5</percentminority>
You can see the element tag names are in different order/sequence and cases.
Thanks.
Yi

Is it possible to call an external web service using ABAP?

Hi~~
I wonder that is possible to use an external web service in SAPGUI using ABAP without PI ( Process Integraion ).
The external web service means the service that is developed by web-language like ASP.NET.
Thank you.

hi,
i'm trying to study on how to use the oracle bi publisher using another client application aside from oracle. the client application is custom and uses a .Net framework. unfortunately, i am not familiar with how .Net sends requests to oracle bi publisher so i was thinking that may be i can just create oracle pl/sql stored procedures that can send this requests over to bi publisher.
p.s. when you said concurrent manager, i'm not sure if you are referring to oracle apps concurrent manager but if you are, unfortunately i won't be using oracle apps with bi publisher.
thanks
allen

Using Client Side Extensions (SWF) to call external Web Service

Hi,
I'm using .swf files to extend my CRMOD application, and one of my requirements is to be able to show information on a custom applet using the Client Side Extensions. This information is coming from an external system, so i'm trying to call this external web service using .swf.
When i create my swf application and i run it locally, i can access the web service and receive the results into my browser, but when i do the same call from the custom web applet in CRMOD i don't get any results.
Can someone tell me if this is possible? And if so, how to do it?
Best Regards,
NF

Post Author: luke
CA Forum: Data Integration
Yes. I have figured out the way to do it.
Luke.

Not able to use external Web service

Hi All,
I am facing an issue where in I am not able to access the external web service through webi rich client.
Error is Provided URL is not valid WIS 10853
It works fine for QAAWS and the external web service opens fine through Browser ( it opens an XML page ).
Additionally I have xcelcius installed and the external web service works fine on it.
What can be the problem??
Regards
KP

i want to expose data from share point through a webservice and use that webservice as a data source in Bi Publisher. But i am not able to use the webservice directly since it is a external web service.
But i am not able to use the webservice directly since it is a external web service.
why?
look at "Creating a BI Publisher Report Based on External Web Services" ExternalWebServices
For that i made below config changes. But it is causing weblogic server starting issues.
why do you want to change some weblogic server settings?

Using TCP Tunnel to examine SOAP messages to an external web service

Similar Messages

Maybe you are looking for