Non WSDL Based Restful Web Services Cannot Be Registered In OAG 11.1.2.3 (Doc ID 2783286.1)

Last updated on APRIL 10, 2024

Applies to:

Oracle API Gateway - Version 11.1.2.3.0 to 11.1.2.4.0 [Release 11gR1]
Information in this document applies to any platform.

Symptoms

On : 11.12.3.0 version, OEG Policy Studio

There is no Service Manager tab in OAG Gateway 11.1.2.3.0 where REST Services can be registered. Is there any other way to register a REST service?
In policy studio when "https://<HOSTNAME>/api/xml/fills" in Static Router was configured, the WSDL for the customized service handler is unable to be opened.

Steps performed:

Registering SOA web service which will send request to the REST Service.
Deleting the service handler, replacing it with Set Web Service Context (Specifying WSDL of the SOA Service).
Static Routing. (Mentioning the HOST PORT of the REST Service)
Connections Filter
Deploy. The deployment is successful but not able to open the WSDL generated for the relative path mentioned.

Is it possible to register REST Service by any other way with Policy Studio?

Cause

	To view full details, sign in with your My Oracle Support account.
	Don't have a My Oracle Support account? Click to get started!

In this Document

Policy Creation

Create a new Policy with “Get TimeZone Information from GEONAMES REST service” as name

Add an "Extract REST Request Attributes" filter using the default values and set this as start point.

In case a proxy is needed, set this up in the Settings tab

Connect the two filters with a success path

Save the next JSON Schema to a file named timezone.json:

Go to the Resources node, select JSON Schemas and Add a new Schema

Add the timezone.json created above

Add a new JSON Schema Validation filter to the canvas

Select the JSON Schema added previously

Connect the last two filters with a success path

Add a JSON Path filter with the next attribute list to get the attributes (Extract JSON attributes):

Connect the last two filters with a success path

Add a Set Message to Echo the JSON Attributes as follows and set the content type as text/xml:

Connect the last two filters with a success path

Create a relative path for the policy

Deploy the configuration

Test the Geonames Timezone REST service using theWeb Browser

If an incorrect username is used, we can get the following response

Now test it using the OAG interface created

Using an invalid username

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.