Forum Stats

  • 3,874,250 Users
  • 2,266,709 Discussions
  • 7,911,783 Comments

Discussions

Accessing a secure web service from ADF Mobile Application

Rapid Value Solutions
Rapid Value Solutions Member Posts: 147
edited Mar 17, 2014 12:05PM in JDeveloper and ADF

Hi,

We are trying to create an ADF Mobile application that uses a secure web service that is in the Oracle EBS (with SOA Suite).

We are using JDeveloper 11g 11.1.2.4.0

Initially we created a Web Service Data Control(SOAP/REST) from the gallery and provided the WSDL. We tried running it on a simulator but was not getting anything. We couldn't also find a way to provide the username and password. So we left it there.

Then we tried creating a Java Desktop Application to check if it was a problem with our server. In the desktop application, we created a 'Web Service Client and Proxy' from the new gallery and then followed the steps and used oracle/wss_username_token_client_policy, added the code below for putting username and password and was able to call the service and retrieve data.

(reqContext.put(BindingProvider.USERNAME_PROPERTY,"DBAKER");

reqContext.put(BindingProvider.PASSWORD_PROPERTY,"xxxxx");

Then we thought of going back to the ADF Mobile application and creating a 'Web Service Client and Proxy' there but when we built the project, we got the "annotations are not supported in -source 1.4 " & "generics are not supported in -source 1.4 " errors and found that ADF Mobile doesn't support beyond Java 1.4.(Is that right?)

We then found the video "Accessing Secured Web Services from ADF Mobile" by Shay (https://www.youtube.com/watch?v=rk5om3o3Pas) and saw that he was using a Login server.

We wanted to confirm if using a Login server is the right way to access a secure web service from an Oracle ADF Mobile application?

Are there other ways to do it?

If we have to create a Login server, can you provide links that will put us on the right track in creating a Login server that can connect to EBS?

Thank you.

Tagged:

Best Answer

Answers

This discussion has been closed.