Consuming a WebService using OSR (uddi) endpoint

Hey folks,
I'm trying to consume a WebService declaratively in my ADF taskflow, using a WebService Proxy connection in my model project, as the guides/tutorials told me to. However, I don't have the final endpoint of the service as it is registered in the OSR (Oracle Service Registry) and all I have is its UDDI key.
So, in fact, my application must connect to OSR to get the service endpoint based on the uddi key and then resolve the port binding based on that.
Any ideas on how I can perform this?
Thanks in advance!

This article helped me out! So if you came here with the same problem, here's some light!
http://biemond.blogspot.co.uk/2009_12_01_archive.html

Similar Messages

How to consume REST WebService using Axis2 in Adobe CQ5.5

Hi All,
    How to consume REST WebService using Axis2 in Adobe CQ5.5 ?
Please help me with this.Thanks very much for your help.
Thanks & Regards,
Kumar

We had enough trouble getting the "osgi compliant" Axis2 library to run in OSGI without spooky failures that we ended up re-writing everything utilizng JAX-WS. JAX-WS is present in the underlying JDK, you just need to create an OSGI fragment bundle that exposes these classes from the JDK. So basically a bundle that just exports:
com.sun.xml.ws,
                                com.sun.xml.ws.addressing,
                                com.sun.xml.ws.addressing.model,
                                com.sun.xml.ws.addressing.v200408,
                                com.sun.xml.ws.api,
                                com.sun.xml.ws.api.addressing,
                                com.sun.xml.ws.api.client,
                                com.sun.xml.ws.api.fastinfoset,
                                com.sun.xml.ws.api.handler,
                                com.sun.xml.ws.api.message,
                                com.sun.xml.ws.api.message.stream,
                                com.sun.xml.ws.api.model,
                                com.sun.xml.ws.api.model.soap,
                                com.sun.xml.ws.api.model.wsdl,
                                com.sun.xml.ws.api.pipe,
                                com.sun.xml.ws.api.pipe.helper,
                                com.sun.xml.ws.api.server,
                                com.sun.xml.ws.api.streaming,
                                com.sun.xml.ws.api.wsdl.parser,
                                com.sun.xml.ws.api.wsdl.writer,
                                com.sun.xml.ws.binding,
                                com.sun.xml.ws.client,
                                com.sun.xml.ws.client.dispatch,
                                com.sun.xml.ws.client.sei,
                                com.sun.xml.ws.developer,
                                com.sun.xml.ws.developer.servlet,
                                com.sun.xml.ws.encoding,
                                com.sun.xml.ws.encoding.fastinfoset,
                                com.sun.xml.ws.encoding.soap,
                                com.sun.xml.ws.encoding.soap.streaming,
                                com.sun.xml.ws.encoding.xml,
                                com.sun.xml.ws.fault,
                                com.sun.xml.ws.handler,
                                com.sun.xml.ws.message,
                                com.sun.xml.ws.message.jaxb,
                                com.sun.xml.ws.message.saaj,
                                com.sun.xml.ws.message.source,
                                com.sun.xml.ws.message.stream,
                                com.sun.xml.ws.model,
                                com.sun.xml.ws.model.soap,
                                com.sun.xml.ws.model.wsdl,
                                com.sun.xml.ws.org.objectweb.asm,
                                com.sun.xml.ws.protocol.soap,
                                com.sun.xml.ws.protocol.xml,
                                com.sun.xml.ws.resources,
                                com.sun.xml.ws.server,
                                com.sun.xml.ws.server.provider,
                                com.sun.xml.ws.server.sei,
                                com.sun.xml.ws.server.servlet,
                                com.sun.xml.ws.spi,
                                com.sun.xml.ws.streaming,
                                com.sun.xml.ws.transport,
                                com.sun.xml.ws.transport.http,
                                com.sun.xml.ws.transport.http.client,
                                com.sun.xml.ws.transport.http.server,
                                com.sun.xml.ws.transport.http.servlet,
                                com.sun.xml.ws.util,
                                com.sun.xml.ws.util.exception,
                                com.sun.xml.ws.util.localization,
                                com.sun.xml.ws.util.pipe,
                                com.sun.xml.ws.util.xml,
                                com.sun.xml.ws.wsdl.parser,
                                com.sun.xml.ws.wsdl.writer,
                                com.sun.xml.ws.wsdl.writer.document,
                                com.sun.xml.ws.wsdl.writer.document.http,
                                com.sun.xml.ws.wsdl.writer.document.soap,
                                com.sun.xml.ws.wsdl.writer.document.soap12,
                                com.sun.xml.ws.wsdl.writer.document.xsd,
                                com.sun.xml.internal.bind,
                                com.sun.xml.internal.bind.v2,
                                com.sun.xml.internal.ws,
                                com.sun.xml.internal.ws.addressing,
                                com.sun.xml.internal.ws.addressing.model,
                                com.sun.xml.internal.ws.addressing.v200408,
                                com.sun.xml.internal.ws.api,
                                com.sun.xml.internal.ws.api.addressing,
                                com.sun.xml.internal.ws.api.client,
                                com.sun.xml.internal.ws.api.fastinfoset,
                                com.sun.xml.internal.ws.api.handler,
                                com.sun.xml.internal.ws.api.message,
                                com.sun.xml.internal.ws.api.message.stream,
                                com.sun.xml.internal.ws.api.model,
                                com.sun.xml.internal.ws.api.model.soap,
                                com.sun.xml.internal.ws.api.model.wsdl,
                                com.sun.xml.internal.ws.api.pipe,
                                com.sun.xml.internal.ws.api.pipe.helper,
                                com.sun.xml.internal.ws.api.server,
                                com.sun.xml.internal.ws.api.streaming,
                                com.sun.xml.internal.ws.api.wsdl.parser,
                                com.sun.xml.internal.ws.api.wsdl.writer,
                                com.sun.xml.internal.ws.binding,
                                com.sun.xml.internal.ws.client,
                                com.sun.xml.internal.ws.client.dispatch,
                                com.sun.xml.internal.ws.client.sei,
                                com.sun.xml.internal.ws.developer,
                                com.sun.xml.internal.ws.encoding,
                                com.sun.xml.internal.ws.encoding.fastinfoset,
                                com.sun.xml.internal.ws.encoding.soap,
                                com.sun.xml.internal.ws.encoding.soap.streaming,
                                com.sun.xml.internal.ws.encoding.xml,
                                com.sun.xml.internal.ws.fault,
                                com.sun.xml.internal.ws.handler,
                                com.sun.xml.internal.ws.message,
                                com.sun.xml.internal.ws.message.jaxb,
                                com.sun.xml.internal.ws.message.saaj,
                                com.sun.xml.internal.ws.message.source,
                                com.sun.xml.internal.ws.message.stream,
                                com.sun.xml.internal.ws.model,
                                com.sun.xml.internal.ws.model.soap,
                                com.sun.xml.internal.ws.model.wsdl,
                                com.sun.xml.internal.ws.org.objectweb.asm,
                                com.sun.xml.internal.ws.protocol.soap,
                                com.sun.xml.internal.ws.protocol.xml,
                                com.sun.xml.internal.ws.resources,
                                com.sun.xml.internal.ws.server,
                                com.sun.xml.internal.ws.server.provider,
                                com.sun.xml.internal.ws.server.sei,
                                com.sun.xml.internal.ws.spi,
                                com.sun.xml.internal.ws.streaming,
                                com.sun.xml.internal.ws.transport,
                                com.sun.xml.internal.ws.transport.http,
                                com.sun.xml.internal.ws.transport.http.client,
                                com.sun.xml.internal.ws.transport.http.server,
                                com.sun.xml.internal.ws.util,
                                com.sun.xml.internal.ws.util.exception,
                                com.sun.xml.internal.ws.util.localization,
                                com.sun.xml.internal.ws.util.pipe,
                                com.sun.xml.internal.ws.util.xml,
                                com.sun.xml.internal.ws.wsdl.parser,
                                com.sun.xml.internal.ws.wsdl.writer,
                                com.sun.xml.internal.ws.wsdl.writer.document,
                                com.sun.xml.internal.ws.wsdl.writer.document.http,
                                com.sun.xml.internal.ws.wsdl.writer.document,
                                com.sun.xml.internal.ws.wsdl.writer.document.soap,
                                com.sun.xml.internal.ws.wsdl.writer.document.soap12,
                                com.sun.xml.internal.ws.wsdl.writer.document.xsd,
                                com.sun.xml.internal.messaging.saaj.soap

Consume webservice using option UDDI or url

hi
can any one help me how to consume webservice
through option UDDI or url
is there is any configuration need to be made
to register UDDI as iam consuming webservice from RFC
can any one help me out ?

Hi Kishore,
Following links would guide you:
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/c2188ae5-0601-0010-dd93-c23e381ef41e
Re: WebService Tutorials
http://help.sap.com/saphelp_nw04s/helpdata/en/43/733b956d596fcee10000000a1553f6/frameset.htm
Regards,
Anagha

Consume ABAP Webservice using AJAX javascript

Hi,
We created webservice for ABAP BAPI. And I want to consume this using AJAX javascript.
But I am getting "Access Denied" javascript error.
Please let me know how to pass the credentials while trying to consume this webservice
I tried below code, but its NOT workng
var URL ="http://hostname/sap/bc/srt/rfc/sap/servicename?sap-client=400&sap-user=testuser&sap-password=testpassword";
xmlhttprequest.open("POST", URL, true);
Please let me know your thoughts ...
Thanks
Edited by: sona p on Feb 27, 2010 12:18 AM

Hi,
Thanks for your response. I did the same as mentioned in the link provided by you. But it is not working . I am still getting "Access denied" javascript error in the second line ( xmlhttprequest.open) . Below is my code.
var auth = make_base_auth('userid','password');
xmlhttprequest.open("POST", URL, true);
xmlhttprequest.setRequestHeader('Authorization', auth);
xmlhttprequest.setRequestHeader ("Content-Type", "text/xml");
xmlhttprequest.onreadystatechange = getDataList;
xmlhttprequest.send(SOAPEnvelope);
Please let me know your thoughts. Thanks again for your response.

Consuming peoplesoft webservices using JSF application gives error

Hi,
I am using Jdeveloper 11g to consume a peoplesoft webservice which does the basic datbase operations.
I have been successful in creating a proxy using the wsdl file and using JAX-WS approach to achieve the same.
I can connect to the webservice using the proxy client.
But when i package the proxy( create a jar) and import in my web application (JSF application), i am running into following error.
<ActionListenerImpl><processAction> com.sun.xml.ws.streaming.XMLStreamReaderException: unexpected XML tag. expected: {http://peoplesoft.com/KCM_WEB_CASE_CI}Get__CompIntfc__KCM_WEB_CASE_CIResponse but found: {http://schemas.xmlsoap.org/ws/2002/xx/secext}Get__CompIntfc__KCM_WEB_CASE_CIResponse
javax.faces.el.EvaluationException: com.sun.xml.ws.streaming.XMLStreamReaderException: unexpected XML tag. expected: {http://peoplesoft.com/KCM_WEB_CASE_CI}Get__CompIntfc__KCM_WEB_CASE_CIResponse but found: {http://schemas.xmlsoap.org/ws/2002/xx/secext}Get__CompIntfc__KCM_WEB_CASE_CIResponse
     at javax.faces.component.MethodBindingMethodExpressionAdapter.invoke(MethodBindingMethodExpressionAdapter.java:102)
     at com.sun.faces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:102)
     at javax.faces.component.UICommand.broadcast(UICommand.java:387)
     at javax.faces.component.UIViewRoot.broadcastEvents(UIViewRoot.java:475)
     at javax.faces.component.UIViewRoot.processApplication(UIViewRoot.java:756)
     at com.sun.faces.lifecycle.InvokeApplicationPhase.execute(InvokeApplicationPhase.java:82)
     at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:100)
     at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:118)
     at javax.faces.webapp.FacesServlet.service(FacesServlet.java:265)
     at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
     at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
     at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:300)
     at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at oracle.dms.wls.DMSServletFilter.doFilter(DMSServletFilter.java:330)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:27)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.doIt(WebAppServletContext.java:3684)
     at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3650)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
     at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2268)
     at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2174)
     at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1446)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused by: com.sun.xml.ws.streaming.XMLStreamReaderException: unexpected XML tag. expected: {http://peoplesoft.com/KCM_WEB_CASE_CI}Get__CompIntfc__KCM_WEB_CASE_CIResponse but found: {http://schemas.xmlsoap.org/ws/2002/xx/secext}Get__CompIntfc__KCM_WEB_CASE_CIResponse
     at com.sun.xml.ws.streaming.XMLStreamReaderUtil.verifyTag(XMLStreamReaderUtil.java:214)
     at com.sun.xml.ws.streaming.XMLStreamReaderUtil.verifyTag(XMLStreamReaderUtil.java:222)
     at com.sun.xml.ws.client.sei.ResponseBuilder$DocLit.readResponse(ResponseBuilder.java:531)
     at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:127)
     at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:95)
     at com.sun.xml.ws.client.sei.SEIStub.invoke(SEIStub.java:135)
     at $Proxy135.getCompIntfcKCMWEBCASECI(Unknown Source)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:597)
     at weblogic.wsee.jaxws.spi.ClientInstance$ClientInstanceInvocationHandler.invoke(ClientInstance.java:363)
     at $Proxy136.getCompIntfcKCMWEBCASECI(Unknown Source)
     at project1.proxy.KCM_WEB_CASE_CISoapClient.getKCMMethod_final(KCM_WEB_CASE_CISoapClient.java:618)
     at login.view.Handler.CRMSearchHandler.getSearchResults(CRMSearchHandler.java:18)
     at login.view.backing.Login.search(Login.java:54)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:597)
     at com.sun.el.parser.AstValue.invoke(AstValue.java:157)
     at com.sun.el.MethodExpressionImpl.invoke(MethodExpressionImpl.java:283)
     at javax.faces.component.MethodBindingMethodExpressionAdapter.invoke(MethodBindingMethodExpressionAdapter.java:88)
I am not sure what else i need to import or rather how to package the proxy classes to get it working.
Any help will be highly appreciated.
I even tried creating a webservice proxy in the JSF project instead of importing the jar, yet i am getting the same error, but the irony is that when i run just the proxy class(standalone with main method) i can get access to the webservice.
Thanks
Ash
Edited by: [email protected] on Jun 8, 2010 2:38 PM

Well,
There is a issue with analyzer capturing SOAP traffic when using with secure proxies, so that is why you are not seeing any data there.
And I think if you will try your jax-rpc code again, it might work as there was nothing incorrect in your code, so might be that the whole config was corrupt which was throwing out incorrect error(s).
About a web service with credentials, you can quickly create one.
Have a java class like the following:
import javax.jws.WebService;
import weblogic.jws.Policy;
@WebService
@Policy(uri = "policy:Wssp1.2-2007-Https-UsernameToken-Plain.xml")
public class Class1 {
public Class1() {
super();
public String sayHello() {
return "Hi";
The procy code for this will be something like:
private static Class1Service class1Service;
public static void main(String[] args) {
try {
class1Service = new Class1Service();
Class1 class1 = class1Service.getClass1Port();
Map<String, Object> requestContext = ((BindingProvider) class1).getRequestContext();
setPortCredentialProviderList(requestContext);
// Add your code to call the desired methods.
System.out.println(class1.sayHello());
} catch (Exception ex) {
ex.printStackTrace();
public static void setPortCredentialProviderList(Map<String, Object> requestContext) throws Exception {
// TODO - Provide the required values
String username = "weblogic";
String password = "weblogic1";
List<CredentialProvider> credList = new ArrayList<CredentialProvider>();
// Add the necessary credential providers to the list
credList.add(getUNTCredentialProvider(username, password));
//credList.add(getBSTCredentialProvider(clientKeyStore, clientKeyStorePassword, clientKeyAlias, clientKeyPassword, serverKeyStore, serverKeyStorePassword, serverKeyAlias, requestContext));
//credList.add(getSAMLTrustCredentialProvider());
requestContext.put(WSSecurityContext.CREDENTIAL_PROVIDER_LIST, credList);
Thanks,
Vishal

Consuming WCF-Webservices using XI/PI

Hello,
I'am trying to consume a WCF-Webservice with the XI/PI. First I imported the WSDL of this webservice as an external definition - so far so good. But when I try to create a message-mapping, no fields are available and the XI/PI says something like "null-pointer exception". I suppose it's because there are no field definitions in the WSDL (seems, that the fields I'am missing are downloaded in the background when using anything other to test the webservice, eg. SoapUI).
Can someone give me a hint how to comsume WCF-Services with the XI? Maybe it's a problem with the WSDL, but how can I put the fields/parameters into the WSDL?
Thank in advance
Thomas

1.Once you import the WSDL under External Definition then you should be able to see the messages under the message tab which indicates input/output message types of your Web service
2.If you are not sending any request and not expecting any response from web service then this message tab will be empty
if web service contains reference to input and output strucuteres then PI editor can not refer them
in that case do a copy the structure of messages into WSLD and reimport agian
HTH
Rajesh

Consuming a webservice using Webservice model in Webdynpro

Hi all,
I am working on a scenario where in XI is used for calling Remote Function Module of R3 system using SOAP
My XI Consultant has implemented SOAP to RFC scenario in XI succesfully and generated the WSDL file in XI.
I got that WSDL file and saved locally on my desktop.
I created a Webservice model based on the local WSDL file and then gave necessary inputs and also included the following code for the SOAP call to happen
wdContext.currentRequest_Soap2Rfc_Ob_MiElement().modelObject().execute();
wdContext.nodeResponse().invalidate();
wdContext.nodeRes_Mt().invalidate();
When I tried to give input data and click on submit it is calling the model object execute method and is throwing the following exception
Exception on execution of web service with WSDL URL 'C:\Documents and Settings\aljsed01\Desktop\soap2rfc_ob_mi.wsdl' with operation 'soap2rfc_ob_mi' in interface 'soap2rfc_ob_mi'
Does any have any idea about this?
Should I require some more steps to do?
Anyhelp in this regard is highly appreciated
Regards,
Santhosh

Hi Anil and Rahul,
Thanks a lot for your help and time.
I have created destinations one for metadata and the other for Execution.
But I am not sure of what URL to be given
I have my WSDL file locally on the system.If I give that path,it says wrong protocol.
And if I give XI URL,it does not pick up metada shows some other error.
What URL should I need to give for locally saved WSDL??Please suggest
And Rahul,here is the WSDL file which my XI consultant gave
Let me know if it is ok.
<?xml version="1.0" encoding="UTF-8"?>
<wsdl:definitions xmlns:p1="http://soap2rfcns" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" name="soap2rfc_ob_mi" targetNamespace="http://soap2rfcns">
+     <wsdl:types>+
+          <xsd:schema targetNamespace="http://soap2rfcns" xmlns="http://soap2rfcns" xmlns:xsd="http://www.w3.org/2001/XMLSchema">+
+               <xsd:element name="res_mt" type="res_dt"/>+
+               <xsd:element name="req_mt" type="req_dt"/>+
+               <xsd:complexType name="req_dt">+
+                    <xsd:annotation>+
+                         <xsd:appinfo source="http://sap.com/xi/TextID">0f2ee199b2ce11dca877001a4bf038d4</xsd:appinfo>+
+                    </xsd:annotation>+
+                    <xsd:sequence>+
+                         <xsd:element name="airlineid" type="xsd:string">+
+                              <xsd:annotation>+
+                                   <xsd:appinfo source="http://sap.com/xi/TextID">f17dde30b2cd11dcb5f6001b78b0798a</xsd:appinfo>+
+                              </xsd:annotation>+
+                         </xsd:element>+
+                         <xsd:element name="connectid" type="xsd:string">+
+                              <xsd:annotation>+
+                                   <xsd:appinfo source="http://sap.com/xi/TextID">f17dde31b2cd11dcbcd8001b78b0798a</xsd:appinfo>+
+                              </xsd:annotation>+
+                         </xsd:element>+
+                         <xsd:element name="fldate" type="xsd:date">+
+                              <xsd:annotation>+
+                                   <xsd:appinfo source="http://sap.com/xi/TextID">f17dde32b2cd11dc986c001b78b0798a</xsd:appinfo>+
+                              </xsd:annotation>+
+                         </xsd:element>+
+                    </xsd:sequence>+
+               </xsd:complexType>+
+               <xsd:complexType name="res_dt">+
+                    <xsd:sequence>+
+                         <xsd:element name="econofree" type="xsd:integer">+
+                              <xsd:annotation>+
+                                   <xsd:appinfo source="http://sap.com/xi/TextID">6906c250b2ce11dca99e001b78b0798a</xsd:appinfo>+
+                              </xsd:annotation>+
+                         </xsd:element>+
+                         <xsd:element name="bussfree" type="xsd:integer">+
+                              <xsd:annotation>+
+                                   <xsd:appinfo source="http://sap.com/xi/TextID">6906c251b2ce11dc9996001b78b0798a</xsd:appinfo>+
+                              </xsd:annotation>+
+                         </xsd:element>+
+                         <xsd:element name="firstfree" type="xsd:integer">+
+                              <xsd:annotation>+
+                                   <xsd:appinfo source="http://sap.com/xi/TextID">6906c252b2ce11dc9c70001b78b0798a</xsd:appinfo>+
+                              </xsd:annotation>+
+                         </xsd:element>+
+                    </xsd:sequence>+
+               </xsd:complexType>+
+          </xsd:schema>+
+     </wsdl:types>+
+     <wsdl:message name="req_mt">+
+          <wsdl:part name="req_mt" element="p1:req_mt" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"/>+
+     </wsdl:message>+
+     <wsdl:message name="res_mt">+
+          <wsdl:part name="res_mt" element="p1:res_mt" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"/>+
+     </wsdl:message>+
+     <wsdl:portType name="soap2rfc_ob_mi">+
+          <wsdl:operation name="soap2rfc_ob_mi">+
+               <wsdl:input message="p1:req_mt"/>+
+               <wsdl:output message="p1:res_mt"/>+
+          </wsdl:operation>+
+     </wsdl:portType>+
+     <wsdl:binding name="soap2rfc_ob_miBinding" type="p1:soap2rfc_ob_mi" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">+
+          <soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"/>+
+          <wsdl:operation name="soap2rfc_ob_mi">+
+               <soap:operation soapAction="http://sap.com/xi/WebService/soap1.1" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"/>+
+               <wsdl:input>+
+                    <soap:body use="literal" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"/>+
+               </wsdl:input>+
+               <wsdl:output>+
+                    <soap:body use="literal" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"/>+
+               </wsdl:output>+
+          </wsdl:operation>+
+     </wsdl:binding>+
+     <wsdl:service name="soap2rfc_ob_miService">+
+          <wsdl:port name="soap2rfc_ob_miPort" binding="p1:soap2rfc_ob_miBinding" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">+
+               <soap:address location="http://sapxidev:50000/XISOAPAdapter/MessageServlet?channel=:BS_SS:req_cc&version=3.0&Sender.Service=BS_SS&Interface=http%3A%2F%2Fsoap2rfcns%5Esoap2rfc_ob_mi" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"/>+
+          </wsdl:port>+
+     </wsdl:service>+
</wsdl:definitions>
Rgds,
Santhosh

Consume webservice using HTTP adapter

Hi PI Experts,
Can we consume a webservice using a HTTP adapter?
If yes can anyone share some knowledge, how to do so?
Thanks & REgards,
Krishna

Hi Krishna,
I think this can be done using FLEX.(not sure).
Ref: http://wiki.sdn.sap.com/wiki/display/EmTech/ConsumingABAPWebServicesusing+Flex
Thanks,

Consuming external webservice in an automated activity

hi,
i am consuming a bapi based webservice in an automated activity. i have checked this in wsnavigator using WSDL, it is working fine. when i consume this in my process dc , it asks me to create aService group. i have created one and now deployed dc to server. it doesn't work and in log error it shows that thsi service group is not assigned to any physical system.
now i tried to create a business scenario communication, for this i created provider systems (it was created and pinged sucessfully, showed all the web services lying in its service registry). when i was creating business scenario, under first step credentials of service group and provider systems are provided. unser second step when i tried to add the services it didn't showed the services which it showed me while i pinged.
please tell me how to sucessfully consume an external web service (bapi based).This is lying on SR but when i tried to access it through single service administration, it was not there. please guide me how can i sucessfully consume this webservice (using service group or logical destination).
Thanks In Advance.

Hi Rohit,
try with Application Communication Configuration instead of Business Scenario (should be easier for single service). Make sure you have entered the correct credentials for the backend system (both for metadata retrieval and for runtime invocation).
Instead of Service Registry you can also try with WSIL when creating the provider system. The WSIL URL for the ABAP system should look like this: http://host:port/sap/bc/srt/wsil.
Please also check the SOA config guide by Alexander Zubev:
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/40dabb46-dd66-2b10-1a9a-81aa620098b3
Hope this helps,
Christian
Edited by: Christian Loos on Dec 29, 2009 10:28 AM

How to call webservice using jdev9i

Hi gurus and experts,
i need to consume a webservice using oaf. with great effort finally i created stub using axis s/w.
now i dont know how to use the stub in jdev.where to write the code and what to write.iam strucked :-( .
since there were no sample tutorial about how to call webservice from jdev9i, iam struggling to make.iam jus a starter.
and while googling i came to know that stubs can be created using jdev9i .but when i see new-->webservices--web service stub it is greyed out.
i have 2 questions now:
1)if stub created using axis can it be used in jdev9i? if yes ,please tell me how? any tutorial links also helps me.
2)if the stubs should be created only by jdev9i so that webservices can be called using jdev,then please guide me how to make it.
i need some helping hands from u guys.
Thanks a lot
Edited by: 881533 on Oct 25, 2011 2:34 AM
Edited by: 881533 on Oct 25, 2011 2:37 AM

Hello sir,
i got following reply:
<returnRecordResponse xmlns="http://xyz" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<returnResult>Error_request</returnResult>
</returnRecordResponse>
but correct response is
<returnRecordResponse xmlns="http://xyz" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<returnResult>Success</returnResult>
</returnRecordResponse>
can you tell me correction in the code which i have put on the forum?or tell me other way to call webservice?

How to use webservice using Jdev

Hi All,
Could some one please point me to a tutorial and let me know how to consume a webservice using Jdev.
Scenario is, I want to extract data from Webserice which will be given by other department using Jdev.
This will have basic authentication as well.
I have created a Webservice client and Proxy and provided the WS URL, it is creating several files using Jax-WS Style.
Now I want to test this webservice client, if its working fine and able to send us the data.
Thanks

Hi,
see:
http://www.oracle.com/technetwork/developer-tools/adf/learnmore/73-handson-wsdc-321927.pdf
http://www.oracle.com/technetwork/developer-tools/adf/learnmore/72-wsprxyclient-pojodc-hands-on-321228.pdf
Frank

SOURCING10: Passing parameters to a Query Based webservice using JAVA

Hi Experts,
I have been working on consuming a Query based webservice published in Souricng10 in a simple JAVA class. The query has a filter parameter which is not mandatory. I am able to consume the webservice using the GET method and display the content of the webservice. But when i try to POST a value to the filter parameter of the query i am getting the following error:
java.io.IOException : Server returned HTTP response code: 415 for URL: http://sapcild9.web.bc:55000/sourcing/ngservices/rest/query/Z_TEST_WS_QUERY/execute/
at sun.net.www.protocol.http.HttpURLConnection.getInputStream(Unknown Source)
Following is the code which i have used:
   URL url = new URL("http://sapcild9.web.bc:55000/sourcing/ngservices/rest/query/Z_TEST_WS_QUERY/execute/");
   HttpURLConnection connection = (HttpURLConnection)url.openConnection();
   connection.setRequestProperty("Authorization", "Basic " + authStringEnc);
   connection.setRequestProperty("Content-Type","application/x-www-form-urlencoded; charset=UTF-8");
   connection.setRequestProperty("Content-Length", "" +Integer.toString(urlParameters.getBytes().length));
   connection.setRequestProperty("Content-Language", "en-US");
   connection.setUseCaches (false);
   connection.setDoInput(true);
   connection.setDoOutput(true);
   connection.setAllowUserInteraction(true);
   connection.setInstanceFollowRedirects(false);
   connection.setRequestMethod("POST");
   connection.connect();
   //Send request
   OutputStream out = connection.getOutputStream();
   OutputStreamWriter wr= new OutputStreamWriter(out, "UTF-8");
   wr.write("EXTERNAL_ID");
   wr.write("=");
   wr.write(URLEncoder.encode("temp","UTF-8"));
   wr.close();
   out.close();
   is = connection.getInputStream();
   isr =new InputStreamReader(is);
   BufferedReader bufferReader = new BufferedReader(isr);
   String str; StringBuffer stringBuffer = new StringBuffer();
   while ((str = bufferReader.readLine()) != null) {
   stringBuffer.append(str);
   stringBuffer.append("\n");
   System.out.println(stringBuffer.toString());
   connection.disconnect();
   is.close();
Please Advise how to proceed on this isssue?
Thanks in advance.
Srikanth Emani

Hi Gael,
your URL is made up of :
[ProcedureName]?[parameter1]=[value1]&[parameter2]=[value2]
creating URLs like this can have problems especially with spaces and punctuation.
the answer is a FORM
the following will create a hidden form :
FORM ACTION="[ProcedureName]" METHOD="POST" name="F1"
INPUT type="HIDDEN" name="[parameter1]" value="[value1]"
INPUT type="HIDDEN" name="[parameter2]" value="[value2]"
/FORM
you can set the values in the form using:
document.F1.[parameter1].value="abc123%%&&$$!";
document.F1.submit();
will submit the form and the PL/SQL procedure should receive the text as it was contained in the form.
the only characters that can now cause problems are :
" as it delimits the field.
' as it may cause problems in PL/SQL.
\ as it is a special character.
Regards Michael

Exposing and Consuming web service using NWDS

Hi all,
I want to expose and consume a webservice using NWDS.
My java application will interact with the SAP web service to create materials in r3.
I just want to know how to create a EJB project that contains the Web service and deploy on the SAP WAS.
and from the java application how would I access the same.
do I need to AXIS jar ?
How would get The WSDL corrosponding java files ?
I will be very thank ful if you can provide me with the some study materials also.
Warm regards

Hi
Refer these links
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/media/uuid/60dbd7ac-4788-2910-539b-b3599c64be12
http://help.sap.com/saphelp_nw04s/helpdata/en/d6/f9bc3d52f39d33e10000000a11405a/frameset.htm
Regards
Abhishek

Consuming a webservice in ABAP ECC 6.0 without using XI/ PI

Hi Experts,
I wanted to consume an external webservice without using XI / PI.After doing my homework and search on sdn I came to know that we can consume webservices in ABAP using proxies using SE80(Enterprise Services).
I am trying to create a client proxy with the URL of webservice.It asks me the option to choose between URL or HTTP.
I am selecting URL and in the second screen it asks about the package details and after that it finishes.Later I get an error message stating "NO VENDOR SPECIFIED".Its not allowing me to create a proxy.
So, here are my questions.
Does anyone faced the same kind of problem?
Can we really consume a webservice without using XI / PI or any other middleware?
Is it possible to consume the webservice only with URL or WSDL file ?
Please let me know the exact process.
Thanks in Advance.
Shanker Pandey.

Hi Martin,
Please check these following links. Though you have reported already, these may help
Proxy Object generation error using Wizard for Web Service Consumption
Also, please have a look @ /people/thomas.jung/blog/2006/03/13/develop-a-web-service-that-sends-an-email--in-abap-netweaver-04s
Hope this helps,
Karthik

Error in consuming webservices using ABAP

Dear Gurus,
I am trying to consume webservices using ABAP. We dont have XI installed and no java instance installed.
I created a customer proxy through SE80 and generated a proxy class by giving a WSDL link and also defined logical port. Traditionally followed the steps. But while testing webservices , I get a ICF error.
The error is as follows:
SOAP : 1:023 SRT : Processing error in internet communication framework ("ICF error when recieving the response ICM_HTTP_CONNECTION_FAILED)
Please let me know the cause of this error and solution to be provided.
I also tried to call the method from an abap program, But I get CX_AI_SYSTEM_FAULT exception.
Awaiting your replies.
Thanks in advance for your support and valuable time.
Thanks
Gurushanthi

Hi Gurushanthi,
It could one of several problems, examples:
- A firewall setting
- http communication out disabled by Basis team or
- The logical port wasn't configured correctly.
Try the suggestions in this thread to narrow down the reason (particularly the telnet test from the server):
[Re: Error testing external web service ICM_HTTP_CONNECTION_FAILED;
Regards, Trevor

Consuming a WebService using OSR (uddi) endpoint

Similar Messages

Maybe you are looking for