My Oracle Support Banner

Virtualizing A New Restful Service Endpoint On API Gateway Removes Existing Listener And Endpoints (Doc ID 1997940.1)

Last updated on OCTOBER 20, 2022

Applies to:

Oracle API Gateway - Version 11.1.2.1.0 and later
Information in this document applies to any platform.

Symptoms

Existing Listener and endpoints and virtualized soap services are inadvertently removed when virtualizing a new Restful Service Endpoint on API Gateway. When adding a new Restful service endpoint through the API Service Manager tab on the API gateway manager console, a Listener and all the existing endpoints (SOAP service endpoints) that had been added previously get removed.
It also seems like all the API services get added even though only 1 was selected to be deployed from the API Service Manager

There is no error. Just the functionality is abnormal. Virtualizing a new Restful Service Endpoint on API Gateway Manager seems to cause the listener to be removed from Policy Studio.

As workaround, it is necessary to add the restful API service and then re-add the listener and all the virtualized soap services.

ENVIRONMENT
OAG 11.1.2.2
Rest Service in API Gateway Manager

STEPS

  1. Go into the API gateway manager console
  2. Click on API Service Manager tab
  3. Click on New API Service
  4. IN the NEW API SERVICE WIZARD
    (Step#1 of wizard) Add the name of the service and the destination URL
    Name: <SERVICE NAME>
    Destination: https://<HOST>:<PORT>/<URI>
    Click Next

  5. (Step#2) Service Exposure
    Service Name is <SERVICE NAME>
    Listening on HTTP
    Note: the Listener is not an available option in drop down of the listeners.
    Select Default Services and path
    Click Next

  6. (Step#3 Request Processing)
    Click Next

  7. (Step#4 Routing)
    Click Next

  8. (Step#5 Response Processing)
    Click Next

  9. (Step#6 Monitoring)
    Click Next

  10. (Step#7 Tags)
    Click Finish

  11. Takes you to a List of all the API Services.
    Click Deploy

  12. Takes you to Deployment Wizard
  13. Specify the gateway
    Click next

  14. Step#2
    No comment was added

  15. Click Deploy
  16. Deployment Summary shows successful
  17. Click Finish
  18. Go back into Policy Studio and you will no longer see the Listener

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
Symptoms
Cause
Solution
References


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