Publishing APIs to Service Registries
Publishing an API to a service registry enables applications to dynamically locate an API Gateway instance that can process that API.
When publishing an API to a service registry, keep the following points in mind:
Before you publish an API to a service registry destination, you must add the service registry to the API Gateway instance from where you want to publish.
You must have the
Publish API to service registry functional privilege to publish APIs to a service registry.
You can publish only active APIs. You cannot publish APIs that are in the inactive state.
An API that is published to a service registry:
Is automatically de-registered from the service registry if the API is deactivated in API Gateway. When the API is activated again, it is automatically registered on the same service registry.
Is automatically de-registered from the service registry if the API Gateway instance from where it was registered goes down. When the API Gateway instance comes up again, the API is registered on the same service registry.
In a cluster of API Gateway nodes, only the API Gateway instance from where you publish an API is added to the service registry. You have to separately publish the API from each API Gateway instance that the service registry can use for an API.
Note:
Similarly, you have to separately unpublish the API from each API Gateway instance from where you want to unpublish the API.
If a load balancer has been configured for the API Gateway cluster, APIs from all instances are registered using the load balancer URL.