Get Started with Fusion Web Services Integration


This document aims at helping to understand how Fusion web services documented in Oracle Enterprise Repository (OER) can be invoked by third party applications from different platforms. Fusion web services are also referred as ADF services because web services are developed in Fusion using ADF business components. OER is accessible at: I assume that readers have gone through the OER cookbook before reading this paper. To find the cookbook in OER, please follow these steps:

  • Go to OER (Login will require a account. To access OER guest can be used).
  • In left side search enter search term Opportunity, type -> ADF Service
  • In the search results select Opportunity Service. This will open opportunity service details and the lower region with few tabs like detail, documentation etc.
  • In the documentation tab, select the top link with title ‘Service Invocation Details- Opportunity Service’
Please note that in the similar manner you can open a service specific cookbook for any of the documented web services in OER.

Use Case

Fusion web services can be invoked by another 3rd party fusion application, using other integration technologies like Oracle Data Integrator (ODI), a ADF Mobile application etc. This blog post discusses on how to invoke a Fusion Applications web service from a third party ADF or any other Java EE application.

Invoking from an ADF/Java EE Application

Any third party ADF application can invoke an ADF web service from various places like the application module impl, entity object impl, from a managed bean code in the UI etc. If it’s a non ADF Java though EE compliant application then a ADF web service can be called from a java code as well.

Service Invocation Approaches

A Fusion web service can be invoked as a synchronous service using a service-based entity object and a view object, Java API for XML Web Services (JAX-WS) client, or from SOA. The 3 primary approaches are:

  1. Using web service client proxy
  2. Using BPEL
  3. Using connection architecture

Examples for all the 3 approaches are provided in the OER cookbook. This blog post discusses the various aspects of web service invocation using web service client proxy approach. A Fusion Applications web service documented on OER can be invoked by creating a web service proxy client in the JDeveloper by just providing the WSDL URL.

Invoking Services

All ADF business components have synchronous and asynchronous versions for the same method. A service method can be invoked synchronously if all of the following conditions are met:
  • The invoked method takes a simple payload, such as a single document or a fixed number of documents, (including parent and children).
  • The invoked method is expected to be finished in real time and takes no longer than a few seconds.

Security Aspect

Fusion Applications web services are secured using Oracle Web Service Manager (OWSM) using the WS-security 1.1 standard. Web service clients need to send SOAP requests with either the username and password, or a Security Assertion Markup Language (SAML) token for authenticating with Fusion Applications. The web service provider decides what policies can be applied to secure a web service. The method of invocation depends on the policy applied on the service. The applied policies on a service could be find out by looking into the WSDL file. The policies to be applied on a web service are usually decided by the producer team based on the intended usage for the service. In general, more than one policy is applied to a web service to suit different calling mechanisms based on client environment. To use username/password based security, web service clients must use the wss11_username_token_with_message_protection_client_policy policy which provides message protection (integrity and confidentiality) and authentication for outbound SOAP requests. Both plain text and digest mechanisms are supported. The web service consumer inserts username and password credentials, and signs and encrypts the outgoing SOAP message, which is decrypted and verified by the web service provider. To prevent replay attacks, the policy assertion provides the option to include time stamps and verification by the web service provider. The message can be protected with ciphers of different strengths. This policy uses the symmetric key technology for signing and encryption, and the WS-Security’s Basic 128 suite of asymmetric key technology for endorsing signatures. To use SAML based security, web service clients must use the  wss11_saml_token_with_message_protection_client_policy policy which enables message protection (integrity and confidentiality) and SAML token population for outbound SOAP requests. A SAML token in the SOAP message provides identity propagation for use in SAML-based authentication. This policy provides message protection (integrity and confidentiality) and uses the symmetric key technology for signing and encryption, and the WS-Security’s Basic 128 suite of asymmetric key technology for endorsing signatures. For more information on the available policies refer to this documentation.

How Policies are Enforced

OWSM policies define how identity is propagated from the client to the service. Based on the policy defined the service authenticates the identity using  the token provided by the client. The server side first authenticates the user. ADF Business Components web services will check whether the user is authorized to invoke the service. More information on how authorization is handled is documented here. The client side can invoke the service through a SOAP service invocation, where the client can be a JAX-WS proxy. Before passing the service to the server side, the client side will either propagate the current user credential or switch identity, based on the client side authentication policy. The following example is provided to show how to call a synchronous web service using client proxy method with security policy oracle/wss_username_token_over_ssl_client_policy.


In this example, we are using OpportunityService from OER and using its findOppotunity method to get an opportunity. Steps:

  1. In your project click on New → Business Tier → Web Services → Web Service Client and Proxy.
  2. Provide WSDL URL and next. To obtain WSDL url you can login to OER and navigate to required ADF service to invoke. On the bottom of the documentation page the reference WSDL will be available. You will need to replace the host and port name with actual values.
  3. Leave default in next screen and uncheck “Generate as Async” option. Click next → next.
  4. Choose “don’t generate asynchronous methods” and next
  5. Chose oracle/wss_username_token_over_ssl_client_policy and next → next → finish. Please note that this is not the only policy that will work with this case. You may use another policy applicable to the web service.

The above steps will generate required code and files for invoking the OpportunityService web service via client proxy using the selected policy. In this example you will need to open the OpportunityBean class to add the code specific to set parameters for the method being called.  The portion of the code that is required to be added is marked in bold. Now, the place where this is required to be invoked use the following code:

import java.util.List;
import java.util.Map;
import javax.faces.event.ActionEvent;
import weblogic.wsee.jws.jaxws.owsm.SecurityPoliciesFeature;
public class OpportunityBean {
//This would be the WSDL url used by removing the ?WSDL part from the url
private static String endpointUrl =
"https://<server name>/opptyMgmtOpportunities/OpportunityService";
public OpportunityBean() { }
public void findOpportunity(ActionEvent actionEvent) {
ViewCriteriaItem item = new ViewCriteriaItem();
ViewCriteriaRow condition = new ViewCriteriaRow();
ViewCriteria viewCriteria = new ViewCriteria();
int fetchStart = 0;
int fetchSize = 100;
FindCriteria findCriteria = new FindCriteria();
FindControl findControl = new FindControl();
OpportunityService_Service opportunityService_Service = 
    new OpportunityService_Service();
// Configure security feature
SecurityPoliciesFeature securityFeatures =
new SecurityPoliciesFeature(new String[] 
     { "oracle/wss_username_token_over_ssl_client_policy" });
OpportunityService opportunityService =
Map requestContext = ((BindingProvider)opportunityService).getRequestContext();
try {
} catch (Exception e) {
List contacts;
try {
contacts = opportunityService.findOpportunity(findCriteria, findControl);
System.out.println("number of items:" + contacts.size());
Opportunity opp = (Opportunity)contacts.get(0);
System.out.println("Des:" + opp.getOptyId().longValue());
} catch (ServiceException e) {
public static void setPortCredentialProviderList(Map requestContext)
   throws Exception {
String username = "Sales_Representative";
/*Please note that for the sake of simplicity the password is hardcoded. 
You should always use credential manager to store passwords. More details at
String password = "Welcome1";
requestContext.put(BindingProvider.USERNAME_PROPERTY, username);
requestContext.put(BindingProvider.PASSWORD_PROPERTY, password);
requestContext.put(BindingProvider.ENDPOINT_ADDRESS_PROPERTY, endpointUrl);

Considerations while specifying WSDL Location

If you encounter the error on running your app in integrated WLS as: [Security:090504]Certificate chain received from <some server name/>- XXXXX –> <another server name> failed hostname verification check. Certificate contained <some server name> but check expected <some server name> Cause: If you use HTTPS to get the Web service from the WSDL, and the hostname definition in the WebLogic Server SSL certificate does not equal the hostname of the peer HTTPS server or is not one of the following, the action fails with a hostname verification error: ■ localhost ■ ■ hostname of localhost ■ IP address of localhost Solution: Turn off the host name verification by weblogic server by adding to the java options in the project properties (run/debug jvm options) as follows:

Please note that this for local development testing etc.  You should not be making such changes to the production server’s setDomain.env. In production scenario this exception should be resolved by adding the required target certificate to the calling server.

Best Practices for Fusion Application Web Services

Below are some tips and best practices for invoking Fusion Applications web services. These are generic best practices and are not specific to any given application web service.

  • Guaranteed message delivery: consider use of a messaging infrastructure, such as EDN  or native JMS (if the client does not use Fusion Middleware). Using such an infrastructure, with the ability to retry using an exponential back-off, can result in a robust infrastructure resilient to any unplanned downtime.
  • Using JDeveloper: Fusion web services are organized in a granular fashion with schema information abstracted from the methods/operations of the Web Service. Instead of manually downloading each XSD file referenced in the WSDL, obtain the WSDL URL for the service from OER and use JDeveloper to import it, which will resolve references to the schema files and download them.
  • Managing Large Applications: To effectively manage service metadata (WSDL/XSD/EDL) in large scale integration projects, use the Centralized Asset pattern, in which all integration metadata across all projects are stored in a centralized location for easy access. This centralized location could be a shared network drive, a development Fusion Applications instance (using concrete URL) or its Metadata Services (MDS). The metadata is still accessed via the concrete WSDL obtained from the OER and is referenced using HTTP protocol e.g. http://<host>:<port>/<path_to_asset>. If the integrations are developed using Fusion Middleware, you can also access the metadata directly from MDS of the development Fusion Applications instance using the ORAMDS protocol e.g. oramds://<path_to_asset>. At deployment time, config plans should replace any references to the development instance with the appropriate URLs for the production instance. This is the approach used within Fusion Applications development.


hi ,
how to call a web-service using ADF Mobile(Android/iOS). for the leave apply system.what is web service names will be used.

Posted by guest on September 08, 2013 at 11:22 AM PDT #

To call a web service using ADF Mobile you can refer

By leave apply system I am guessing you mean HCM Employee Absence service. If yes then you can refer it at http://<HostName:PortNumber>/hcmEmploymentAbsencesAbsenceCaseService/AbsenceCaseService?WSDL

You can search about such services in OER

Posted by Vik on September 09, 2013 at 01:44 PM PDT #


How could I schedule the LoaderIntegration Service Invocation?


Posted by Ricardo Cheachire on January 20, 2014 at 04:49 AM PST #

can i achieve this in SAAS environment, also i tried to access the WSDL but it says

We're sorry, the page you requested was not found.

https://<My Environment>

am I missing anything?

Posted by guest on May 19, 2014 at 10:55 PM PDT #

Hello guest,

you need to replace <My environment> with the actual server name of your SaaS environment.

Something like

Hope this helps,

Posted by Oliver Steinmeier on May 22, 2014 at 12:02 PM PDT #

Hi VIk,
How to invoke wss11_saml_token_with_message_protection_client_policy policy enabled webservice and how to keystore if keystore is needed. I am trying to consume using https. Please point me some pointers to refer.


Posted by shyam on May 23, 2014 at 04:18 AM PDT #

i did dude...I just didn't wanted to share my environment details, so that is why I user <my environment>

so on SAAS environmnet I am getting this error:

We're sorry, the page you requested was not found.

Posted by guest on May 23, 2014 at 04:35 AM PDT #

Hi Vik,

I am getting this error when I ran app from integrated weblogic server,
I even set the java options for project to

Still getting below error, please help me on this

Caused By: [Security:090504]Certificate chain received from - failed hostname verification check. Certificate contained * but check expected

Thanks & Regards
Apoorv Jain

Posted by apoorv Jain on June 24, 2014 at 07:03 AM PDT #

Thanks for this tutorial, I am facing one problem at the time of calling a web service,

Suppose my web service is running over a cluster port & IP x.x.x.x:8888/XYZ/abx?wsdl

If i am using this web service in oracle soa with that IP & port i am able to got response from web service, Same service is exposed over a domain name like which is SSL based so with that domain name my web service URL is something like.
When i am trying to calling this web service i am not able to got any response from web service.

I already imported the certificate in the trust store and had been cross verified that certificate is exist in the trust store.

I had tried with all the way but the web service is not giving response.

I am stuck in my development please help me.


Posted by Sandeep Pachauri on August 18, 2014 at 11:33 PM PDT #

Apoorv: setting the "" should hide the issue, it has worked on test cases I have used. Can you confirm how you set the property ? Also you can try setting "oracle.jdeveloper.ssl.trusteverybody=true"..

Jani Rautiainen
Fusion Applications Developer Relations

Posted by Jani Rautiainen on August 19, 2014 at 10:27 PM PDT #

Sandeep: Are you able to access the URL using a browser ?

Jani Rautiainen
Fusion Applications Developer Relations

Posted by Jani Rautiainen on August 19, 2014 at 10:31 PM PDT #

Hi ,
I want to create contact using PersonService fusion wsdl take from OER. So far i consumed this webservice in my local. When am invoking createPerson method for creating contact it ask send a parameter as JAXBElement object.


i dont know how to set the value for JAXBElement. If any one knows please send me the code.


Posted by Govindh on October 16, 2014 at 05:32 AM PDT #

You would need to do something like: personFactory =
PersonName personName = personFactory.createPersonName();

Just change the factory path and method names to match your service as needed.
Jani Rautiainen
Fusion Applications Developer Relations

Posted by Jani Rautiainen on October 16, 2014 at 11:56 PM PDT #

Hi jani,
Thanks for your input. I tried with your code

ObjectFactory personFactory =new ObjectFactory();
Person personName = personFactory.createPerson();

PersonResult ps=createPerson(personName);
List<Person> perList = ps.getValue();
System.out.print("=====>>>>" + perList.size());

but i got below error. can you send me your full code for my reference.

Exception in thread "main" JBO-27008: Attribute PersonFirstName in view object PersonParty cannot be set.
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)


Posted by Govindh on October 17, 2014 at 12:17 AM PDT #

I am not an expert on your specific service, however based on a quick search seems the call may be wrong. See:
WebService Sample Payload for Creating a Person (Doc ID 1335004.1)

Not able to created contact using web service

Jani Rautiainen
Fusion Applications Developer Relations

Posted by Jani Rautiainen on October 17, 2014 at 01:09 AM PDT #

Hi Jani,
I have solved above issue using Object factory class as u said . Now i want to fetch fusion custom fields using java code.


DateofBirth_c, These are custom fields in fusion application. How to fetch these custom fileds?. if you any sample code for this please share with me.


Posted by Govindh on October 27, 2014 at 03:07 AM PDT #

Govind can you elaborate on the requirement. If I understood correctly you want to customize a Fusion Applications web service to include custom fields added by the customer ? If so, then unfortunately I do not think that is possible, see:
/Start quote/
It is important to note that you cannot modify the web service interface for a service-enabled application module. You can, for example, add an attribute in a view object that is included in a service-enabled application module, but that attribute cannot be added to the web service interface.
/End quote/
If that is the requirement I think the only viable option would be to create a custom web service that matches the requirement.
Jani Rautiainen
Fusion Applications Developer Relations

Posted by Jani Rautiainen on October 28, 2014 at 07:11 AM PDT #

Hi Jani,

I have regenerated webservice in my local and that problem was solved


Posted by Govindh on November 20, 2014 at 02:24 AM PST #

Hi Jani,

I am having some success with calling Fusion web services from 3rd party applications.

However, I note that every WSDL seems to state that all fields are optional, which some are not.

Is there a simple way to find out what values are considered valid by Fusion i.e. The createWorker servive from workerService2 requires an Action List to be passed in, what does this refer to and where can valid values be found?


Posted by David on December 17, 2014 at 03:26 AM PST #

Not sure if this can be considered simple, but in OER you can click the link in the "type" column which takes you to the XSD:

Where the attribute description states:
<oer:attribute description="Foreign key to PER_ACTIONS_B table." name="ActionId"/>
<oer:attribute description="Foreign key to PER_ACTION_REASONS_B table." name="ActionReasonId"/>

if you have access to those tables then you could query the values from there.

Posted by Jani Rautiainen on December 18, 2014 at 12:33 AM PST #

Thanks, I should be able to access through fusion BI.

Posted by David on December 18, 2014 at 12:53 AM PST #

Thanks for the valuable info.
If we want to call a particular web service(For ex: updatePersonEmail ), where can we get the necessary WSDL file for that? Do we need tom open an Oracle SR and gt it from Oracle?


Posted by guest on March 06, 2015 at 02:54 AM PST #

Thanks for the valuable info.
If we want to call a particular web service(For ex: updatePersonEmail ), where can we get the necessary WSDL file for that? Do we need tom open an Oracle SR and gt it from Oracle?


Hi Raj,

If you go to
Find the web service that you need
Under the details tab of the documentation at the very bottom, you will find the WSDL URL.


Posted by David on March 06, 2015 at 03:15 AM PST #

You should be able to access it directly in your target environment. You can get the path of the WSDL from OER:

Query your service and under the "Detail" tab there is a "Service Path" that will be something like:

Replace the HostName and PortNumber with server details for your instance.

Posted by Jani Rautiainen on March 06, 2015 at 03:18 AM PST #

I did verify that.
But when I am trying to access the URL, I am getting 'Page Not Found' error from Oracle Public Cloud.


Posted by guest on March 06, 2015 at 03:50 AM PST #

As for the host and port information I would not know the values for your instance. If the host and port are known does the problem reproduce for all services or only some ? Can you confirm whether your service is externally available, in OER under the "Taxonomy" tab the external services have "Keyword" column with value "EXTERNAL".
Jani Rautiainen
Fusion Applications Developer Relations

Posted by Jani Rautiainen on March 09, 2015 at 06:11 AM PDT #

Post a Comment:
  • HTML Syntax: NOT allowed

Follow us on twitter Fusion Applications Extensibility, Customizations and Integration forum Fusion Applications Dev Relations YouTube Channel
This blog offers news, tips and information for developers building extensions, customizations and integrations for Oracle Fusion Applications.


« March 2015