RDE: Using an external ODATA service

Hi,
I'm trying to use an external oData service in a RDE "SAP Fiori Start application" Project.
I've added the service to the HCP Destinations page as well as giving it the additional property "RDEEnabled=true" but it still doesn't appear in the RDE: Data Connection screen in the catalog.
Any tips?
Thanks,
Dick

Hello Richard,
then this environment would have to provide an OData service /IWFND/CATALOGSERVICE with a collection ServiceCollection that has the same structure as the one provided by NetWeaver Gateway, because this is what the River RDE "SAP Fiori Start application" template uses to find applicable services.
Best regards
Frank

Similar Messages

Consuming External OData services from SAP

Hi All,
I am trying to sync up SAP to an external system. Using the SAP Netweaver Gateway I am able to expose the SAP Objects as OData service so that the external system can sync with SAP data.
Now when SAP needs to consume the OData services of the external system can it do through Netweaver gateway ?
How do we build a bi-directional interface keeping both the systems in sync.
Thanks
Ravijeet

NW Gateway cannot do that. But you can do it with simple ABAP.
check here.
Implementing the REST Client - Connectivity - SAP Library

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>

Create a record using SAPUI5 and ODATA Service

Hi there,
since SPS6, SAP HANA should allow CRUD operations using an ODATA Service.
That sounds nice and so I wanted to give it a try.
I've started by creating a simple table and set up a tiny application that displays the data in a grid (using a JSON Model) and allows to insert new records by entering data into two textfields and save them as a new record to the databse. That works well, the grid shows the records which I have created using the SAP HANA Studio.
So I wanted to create new records, and the documentation says very clearly how to create a new record.
I've tried it this way, but when the request is send I get an 501 Not Implemented error.
Thats the code I'm using in my SAVE-Button:
btnSave.attachPress(function() {
   var entry = {};
   entry.id = tfUserId.getValue();
   entry.username = tfUserName.getValue();
   oData.create('/tbl_user', entry, null,
   function() {
      alert("Create successful");
   function() {
      alert("Create failed");
After that I've tried to create a record using the POSTMAN extension for Chrome browser as mentioned in this cool video by Thomas Jung.
Unfortunately, this also doesn't work for me. After sending the request I get as respone a sap hana xs login window with Status Code 200 instead of a status code "201 created".
Here's a screenshot:
I'm using SAP HANA Cloud Trial.
Anybody got an idea what I'm doing wrong? Or does ODATA CRUD not work an SAP HANA Cloud Trial?
Many thanks,
ben

Hi Jason,
exactly, it's the logon page returned that is opened when I open the service URL in the browser. After logging on I can see the results of the ODATA service call.
The URL must be correctly defined, the grid shows up the data from the ODATA Service.
And yes, the URL looks OK when expecting in Chrome developer tools...
Thanks,
ben

Using an external web service and XMLBeans

I have an external document/literal web service that I want to use
(call) from inside workshop. I have listed a small example at the end
of this email.
I am wondering if there is a way to call and receive from the web
service using XMLBeans. In the tutorial examples XMLBeans are only
used by marshaling and unmarshaling the xml structure into a string
which is what is actually passed according to the WSDL. However, in
this case (and I personally think in most cases) the schema is
explicitly described in the WSDL and passed as the message. I might
add the structures for my real service are much more complex and so
the value of XMLBeans is certainly applicable to them.
Clearly I can somehow save off the schema and generate XMLBeans from
it. The next step is much less clear, how do I tell my JCX to use the
beans instead of generating private classes to represent the
structures?
To be honest I am a little surprised that for 8.1 the WSDL->JCX stuff
doesn't just leverage XMLBeans by default instead of generating basic
classes. This would give the power of XMLBeans to all web service
calls.
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:sequence>
</s:complexType>
</s:element>
<s:element name="sayHello" >
<s:complexType>
<s:sequence>
<s:element name="caller" type="s:string" />
</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>

FYI, there is a XMLBeans newsgroup; w/ good feedback from the
developers:
http://newsgroups.bea.com/cgi-bin/dnewsweb?cmd=xover&group=weblogic.developer.interest.xmlbeans
Bruce Stephens wrote:
>
Hi David,
We are on the road, headed in that direction; pedal to the metal, etc.
just not there...yet.
We appreciate and value your input.
Thanks,
Bruce
David Rees wrote:
I have an external document/literal web service that I want to use
(call) from inside workshop. I have listed a small example at the end
of this email.
I am wondering if there is a way to call and receive from the web
service using XMLBeans. In the tutorial examples XMLBeans are only
used by marshaling and unmarshaling the xml structure into a string
which is what is actually passed according to the WSDL. However, in
this case (and I personally think in most cases) the schema is
explicitly described in the WSDL and passed as the message. I might
add the structures for my real service are much more complex and so
the value of XMLBeans is certainly applicable to them.
Clearly I can somehow save off the schema and generate XMLBeans from
it. The next step is much less clear, how do I tell my JCX to use the
beans instead of generating private classes to represent the
structures?
To be honest I am a little surprised that for 8.1 the WSDL->JCX stuff
doesn't just leverage XMLBeans by default instead of generating basic
classes. This would give the power of XMLBeans to all web service
calls.
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:sequence>
</s:complexType>
</s:element>
<s:element name="sayHello" >
<s:complexType>
<s:sequence>
<s:element name="caller" type="s:string" />
</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>

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 External Web Service

Hello All,
I need to get data from External Web Service.
for example from :
http://www.w3schools.com/webservices/ws_use.asp
I need to use it from SERVER side method for example from any Context Node SET_XXX() method.
Thanks In Advance
Eli

Hi Eli,
You can create a proxy using the external web services. Go to transation SE 80->Edit Object on the application tool bar. Select the Enterprise Services tab and select the client proxy and click create.
select URL/HTTP Destination and just follow the menu path. The external web service will be created as a proxy(class) in SAP. you will be able to use this in your coding.
Hope this helps.
Sudha.

Employee Photo - External HTTP service

Hi all,
currently I trying to setup the Employee photo dysplay in the portal Iview photo and in PA20/30 transaction. My problem is that I have the requirement to use an external http service that doesn't supports SAP Content Server HTTP Interface and it requires Basic authentication.
The access to the picture can be done by a direct url http://hostname/path/pernr.jpg ou using a dll service, http://hostname/path/service.dll?docid=pernr.
Does anyone ever face a similar problem, is there a way to implement this using "standard" features?
For example put the access logic to the picture in a function module or other object, and setup the z* object has the content server implementation.
Thanks and best regards,
Paulo Ruivo

Hello
Where are you trying to store the photos? In an external storage system or in the database?
If you are using an external storage system, please note that you must use either a different content server installation for each system, or at least a different content repository.
In case you are using the database storage, then make sure you have followed all the instructions from the note 595563 to do this. In case everything is fine, please go to OAC0 and test the connection to your content repository.
Additionaly please ensure that you have the lastest version of SAPHTTP installed on your system. Please review the SAP note 615354 for more information on this.
Thanks and Kind Regards
Ramana

External Web services in WebDynpro

hi,
We have a requirement of developing an application which uses external web services in web dynpro.
Does anybody have any document or link as how to go about.
we tried working on that but when creating a Adaptive Web Sertvice Model and giving the external WSDL url we are getting an error as
error in loading the WSDL file.
Are there any prerequisites in order to use an External Web Service.
PLease help.
Thanks and regards,
Kris

Hi gopi krishna ,
check the following link , it gives step by step procedure to use an external webservice in webdynpro.
U need to configure the HTTP proxy not to get that error , all details will be available in that link , hope it will be useful check it,
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/98347a90-0201-0010-d1a6-cc4d80917d81
Regards,
Sam Charles J.

Internal vs. external directory services best practices

Hello everyone,
We have two distinct directory services here where I work, one that supports 'internal' needs, and one that is used for external clients, the people who use our web-facing applications. We are limited by the separation of the directory services. E.g., our internal users cannot use the external directory service to look up email addresses.
I have been asked to look into design options and best practises. Is it common to have distinct services like this? Or are those external users usually part of the same service as the internal users? Is my online banking account information in the same directory service (assuming it is in a directory service at all) as the employees at my bank? Does it make sense to run separate services like this? What are some alternatives?
Part of the integration problem is AD vs. Sun Directory Server. The external service is in Sun Directory Server and predates AD. The AD service is obviously here for the Windows environment. Some organizations I have worked with in the past used Sun LDAP as the authoritative source of data, and synced in one way or another into AD.
Any feedback is appreciated,
Mark

No, what I am looking for is architectural input regarding the use of AD and a separate LDAP server. In my case I am talking about AD and the SJS Directory Server, but this would apply to any environment that has AD plus some other LDAP server.
I need to be able to reasonably answer the general question: Why should we keep the SJS Directory Server, when we could just put all our LDAP data into AD?
I also need to answer the more specific question: Given our LDAP data is external users only (customer, partners), does it make sense to keep them there? Again, why not just put these "external" entities into AD?
I'm not trying to figure out how to get AD and LDAP to work together. I'm trying to figure out why I have two directories, and why I should or should not keep two directories. I've found nothing online dealing with what should be a very common scenario.
Mark

External Report Service

Hi,
I am using the External Report Service to run and extract some custom data.
I have the process working fine in SOAP UI, which returns XML, with the report contents as BASE64 string in the <reportBytes> tag.
The problem comes when I try to parse the response in PL/SQL instead of SOAP UI.
I am using a fairly standard approach UTL_HTTP, then deal with the response.
Problem is the response seems to be in an odd format that makes no sense. I am guessing it is due to the content type of
Content-Type
application/soap+xml; charset=UTF-8;action=""
I want to do what I have done previously, fetch the response, read it into a VARCHAR2 or CLOB, convert to XML, then parse it.
However the response is unreadable.
Any suggestions?
Also, are there any plans for Oracle to put some standards on the web services. The differing content types and response tags make building anything generic nearly impossible.
Thanks

Thinking it's probably a character set issue?
Any assistance greatly received, thanks

[OSB and OWSM] - External Web service stacks and frameworks

Hi everyone ! I'm starting to read about OSB and OWSM and I'm having some doubts. I've some developments of Web services with external Stacks like CXF, JBossWS, Metro and I'd like to ask some questions:
1- Will I be able to productively leverage all features of OSB and OWSM like creating a proxy service to add WS-* standards policies and features (WS-Security, for instance) even with these web services implemented in different stacks other than Weblogic's ?
2- If it is possible, do these web services need to be deployed at the Weblogic server to enable the OWSM and OSB to work effectively ?
3- Even if it is possible to use the OSB and OWSM nicely with webservices developed at external stacks and deployed at other application servers is there any reason to quit using these external web service stacks in favor of Weblogic's (like features only enabled on OSB/OWSM when the services use the Weblogic stack) ?
I suppose that if I ignore the JAX-WS stack from Weblogic and use an external framework (like CXF) I'll lose most of the application server administration capabilities since the Weblogic server won't be able to recognize the CXF stack as it does with its own.But, the main doubt I'm in is, since OSB and OWSM might be used with external providers I probably won't need to develop my web services using the Weblogic implementation (which my team does not yet know) since there will be no features of the OSB and OWSM which can only be used with the Weblogic's stack. I would like, please, to know your oppinions about these considerations. Sorry about the long post and possible errors (I just started learning).
Thank you!

Hi Lupan,
I can speak mostly to OWSM as my experience with OSB is small thus far.
+1- Will I be able to productively leverage all features of OSB and OWSM like creating a proxy service to add WS-* standards policies and features (WS-Security, for instance) even with these web services implemented in different stacks other than Weblogic's ?+
OWSM (10gR3) has two types of policy enforcement point (PEP) -- Gateway and Agent. The Gateway acts as a remote proxy and is neutral to the service implementation technology as long as it adheres to SOAP 1.1. In this regard you can use OWSM freely with CXF, MS implementations, etc. Agents run in-process with the service and thus have far greater restrictions on what service implementation frameworks and containers that are supported. There is some certification for AXIS 1.x running in OAS and Tomcat; but practically speaking, my recommendation for Agents is to only use within OAS 10gR3 where it is built in (and using OC4J Web Services through JAX-RPC).
OWSM 11gR1 initially supports only agent-style (in process) PEP and is built-in to Fusion Middleware and WLS. It is only for Fusion and WLS Web Service implementations.
OWSM is quite full-featured for WS-*.
+2- If it is possible, do these web services need to be deployed at the Weblogic server to enable the OWSM and OSB to work effectively ?+
"No" if using OWSM Gateway PEP. A qualified "Yes" if using OWSM Agent PEP.
+3- Even if it is possible to use the OSB and OWSM nicely with webservices developed at external stacks and deployed at other application servers is there any reason to quit using these external web service stacks in favor of Weblogic's (like features only enabled on OSB/OWSM when the services use the Weblogic stack) ?+
There is the manageability that you mention, but also there is the identity propagation scenario and tight security integration. Both OAS and WLS hosted services in the native stacks (JAX-RPC and JAX-WS) allow sophisticated and secure passing of identity in the request -- for instance, via SAML Assertions in the WS-Sec header -- and built-in capabilities to map the passed identity into the running service's Subject (i.e. enabling JAAS security etc.).
In my experience this type of identity propagation functionality has either been absent or less complete in other typical implementation frameworks not closely aligned with the container security mechanisms.
Hope this helps,
Todd

Listview and details with Appbuilder (OData Service)

Hi,
I try to create an app with appbuilder, which shows me a list of items, and if i click one item in the list, i get to a new site and see the details.
For this i created an OData service, which works and is available in my browser.
Then I startet to create the app in the appbuilder. I followed the steps in this tutorial http://www.youtube.com/watch?v=iC3x7P5Cu1g
I added the ODataService in the DataSource, and added a ODataQuery for the details. After this I created a new SuperList with two sites, one for the complete list, and one for the detailed view. It all seems to work. I see the list with all my items and i can click on one item, to get to the detailed view. But there I see nothing. The fields of the detailview are empty, and I don't know why.
If I confirm my ODataQuery (with the button in the DataSource section) i get all the data i want, but the view is empty.
The only differents between my app and the app in the video is, that in the video the query uses the filter function (<url>...?$filter=...). This returns a table with one entry. I use an own OData service with the parameter. The service returns a structure, no table. Could this be the problem?
How can I fix this (hopefully without changing the OData Service..)
Thanks and Regards
Jens

Its quarterly billing, and on direct debit, so the whole point there is it takes care of itself.
It aso didnt hurt that as I said, I had no communication from BT in that year, no calls, emails, texts, letters nothing. They sent me no letter to say that there had been a missed payment, they took no action due to this, still something at this point that no one has been able to explain how that happened. Also the direct debit was set up by someon from their executive level complaints deaprtment, so you would think it would work ok. But apparantly 3 months later they didnt take a payment, and kept not taking payments or getting in touch with me about it, they just did notning. Then after a year, again without any warning or notification restricted my line, which as it turnds out was an automatic process, no one had any clue about what had been going on. Hence why the first manager I spoke to about it said she was going to have to investigate how this happened and obviously work out a repaymnt package. Though as par for the course from that point on I never received a callback from BT at any point, I called them often enough, but they never could be bothered it seemed to get back in touch.
Also my bills arent exaclty large, as I say the only reason I even have a landline is for my internet access for work so its not as if its a huge amount and its every 3 months so not something really on your radar. Again thats the point of DD and what you assume is a professional and capapble company.

Authentication : accessing an LDAP via an external web service ?

Hi,
I know it is possible to use an external web service to authenticate a user on a portal.
But I would like to know it is possible for a user to :
- open hiw browser and navigate to the Enterprise Portal
- the portal is asking a user and password
- then the portal call a web service giving the user/password
- the web service (enternal and already existing) check the authentication through the LDAP
- the web service reply OK/NOK to the portal with a SAP USER ID (or another information)
- the portal if authentication ok send a logon ticket to the user
I didn't find any clear information telling it is possible.
So if someone can help on this matter ...
Many thanks.
Naguy C.
Edited by: NAGUY CAILLAVET on Feb 13, 2009 2:28 PM

Hello,
First, thank you Sandor for your answer.
I understand that it is possible to create a BPEL process that exposes multiple operations/messages. This would be exactly what I need: a single process (web service) that will expose many operations. Could anyone, please, point me to such an example?
So far I thought that there is possible to have only one operation exposed with a BPEL process, what is delimited between the receive/reply blocks (in the synchronous case).
Regards,
Marinel

Calling the odata service from UI

Hi Everyone,
From the below document I have executed all operations of the odata service
Let’s code CRUDQ and Function Import operations in OData service!
But I want that from an UI I will provide the data which will create or update or get deleted. Is it possible? If yes, then How to do that and if No, then what is the use of this odata service which I created? How to create an odata service which can be called from a browser? For that RFCs and BAPIs are required?
Regards,
Soumya

Hi Chandra,
Following I am giving the code where I got stuck. When I am pressing the create button the dialog is opening but during fetching and getting the request it is showing the alert of the 1st err function which I have made bold. But why the code is going there I am not able to uderstand.Please help.
Code:
OData.request
                                        requestUri:      "http://server:host/sap/opu/odata/sap/ZGW638785_EMPLOYEE_TEST_SRV/EmployeeCollection/",
                                              method: "GET",
                                              headers: {
                                                "X-Requested-With": "XMLHttpRequest",
                                                "Content-Type": "application/atom+xml",
                                                "DataServiceVersion": "2.0",
                                                "X-CSRF-Token":"Fetch"                                 }
                                           function (data, response)
                                           alert("1st func     "+mandt_var+"      "+employeeID_var +"       "+ address_var+"       " + datejoining_var + "        " + yearexp_var);
                                            header_xcsrf_token = response.headers['X-CSRF-TOKEN'];
                                            OData.request
                                                 requestUri: "http://server:host/sap/opu/odata/sap/ZGW638785_EMPLOYEE_TEST_SRV/",
                                                 method: "POST",
                                                 headers: {
                                                  "X-Requested-With": "XMLHttpRequest",
                                                  "Content-Type": "application/atom+xml",
                                                  "DataServiceVersion": "2.0",
                                                  "Accept": "application/atom+xml,application/atomsvc+xml,application/xml",
                                                  "X-CSRF-Token": header_xcsrf_token
                                                     data:
                                                    mandt: mandt_var,
                                                       employeeID:employeeID_var,
                                                       address:address_var,
                                                       dateOfJoining: datejoining_var,
                                                       yearOfExp: yearexp_var,
                                                    function (data, response)
                                                   alert("2nd Func     "+mandt_var+"      "+employeeID_var+"        "+address_var+"       "
                                         + datejoining_var+"        "+yearexp_var);
                                                       document.location.reload(true);
                                                              $("<div>Returned data " + window.JSON.stringify(data) + "</div>").appendTo($("#MessageDiv"));
                                                    function (err)
                                                   alert("1st err func     "+mandt_var+"      "+employeeID_var+"        "+address_var+"       "
                                         + datejoining_var+"        "+yearexp_var);
                                                              $("<div>Returned error " + window.JSON.stringify(err.response) + "</div>").appendTo($("#MessageDiv"));
                                  function (err)
                                       alert("2nd err func    "+mandt_var+"      "+employeeID_var+"        "+address_var+"       "
                                         + datejoining_var+"        "+yearexp_var);
                                                      var request = err.request; // the request that was sent.
                                                      var response = err.response; // the response that was received.
                                                      alert("Error in Get -- Request "+request+" Response "+response);

RDE: Using an external ODATA service

Similar Messages

Maybe you are looking for