Important Considerations When Publishing and Unpublishing APIs
The following are some aspects of runtime you may need to consider when you publish and unpublish APIs to gateways:
You will only be able to publish APIs to the gateways for which you have the required roles or the Modify instance-level permission.
You can publish a native API to an instance of
API-Portal. However, you cannot publish a native API to an instance of
Mediator.
You can publish virtualized APIs to both
Mediator and
API-Portal gateways.
When publishing a virtualized API to both
Mediator and
API-Portal gateways in a single step, only if publishing to at least one
Mediator instance was successful,
CentraSite will publish the API to
API-Portal instance.
When publishing an API to one or more gateways, if
CentraSite encounters a publish failure with one of the gateway, it immediately ignores the failure gateway and proceeds with the next gateway. Any gateway that encountered failure during the publish process is displayed in the
Publish Log.
When trying to publish an API to a set of gateways, if the API is already published to a selected gateway, then that API is republished to that particular gateway.
When unpublishing an API from the
API-Portal gateway, the access tokens associated with the unpublished API are revoked from the
API-Portal registry. These revoked access tokens will continue to reside in the
CentraSite's repository.
When republishing an API (which is already unpublished) to the
API-Portal gateway, the access tokens associated with the API and which already exist in the
CentraSite's repository are once again published to the
API-Portal registry.
When
CentraSite version 9.12 is configured with
Mediator version 9.10 or earlier, publishing and republishing a Virtual REST Service with HTTP Patch method fails in the
Mediator instance. This is because,
Mediator version 9.10 and earlier do not support the Axis Free Mediation stack. Instead, the
Mediator versions 9.10 and earlier support the WSStack Mediation stack. In order to publish a REST Service with HTTP Patch operation, it is mandatory that the
Mediator instance must be configured for the Axis Free Mediation stack. Also, the
Mediator instance must be of version 9.12 or above.