Oracle E-Business Suite Integrated SOA Gateway (ISG) introduced PL/SQL as RESTful webservices in EBS 12.2.3.  EBS 12.2.4 expands that functionality further, allowing Plain Old Java Objects (POJO) / Java Beans to be published as RESTful web services using ISG. This new Java API REST service provides support for both GET and POST verbs.

What is POJO?

POJO stands for Plain Old Java Object. It is a Java object which does not implement any framework-specific interfaces such as Spring, Hibernate, JDO, or EJB. POJOs allow applications to be decoupled from infrastructure frameworks.

Prerequisites for Using Custom Java API as REST service in ISG

The following tasks needs to be performed to use custom Java API as REST services:

Custom Java API steps

Custom Java APIs are configured and deployed on the application tier.  For more information, see Section 5, “Deploying Custom Application Tier Objects” in this document:

Java REST API Lifecycle

Java REST API lifecycle

Java API REST services follow the same lifecycle as PLSQL rest services. Once the custom classes and ILDT loader files are uploaded, you are ready to use Java APIs as REST services from the Integration Repository.

You can find the newly uploaded Java API in the Integration Repository using the new “Java Bean Services” Interface Subtype :

 

Java Bean Services Interface Subtype

Select GET, POST, or both based on your requirements. Provide a service alias and deploy the service.

Voila! the service is ready to be used.

Java Web Service Details

What’s more in a Java API rest services?

Java API REST services support GET and POST methods. GET requests can be invoked as Uniform Resource Identifiers (URI) from any browser.  The invocation process is simple, user-friendly and quick.

URI Format:

http://<host>:<port>/webservices/rest/<Service Alias>/<rest method name>/[<key-param>]?queryParam=paramValue[&....

Example :

Get all employees reporting “Mark ”, location “CA”

http://<host:port>/webservices/rest/empSvc/getEmployees/Mark/?location=CA

Key Features of GET

  • GET requests can be cached
  • GET requests can be bookmarked
  • GET requests remain in the browser history

GET requests should not be used when dealing with sensitive data.

Related Articles