Legacy Portal Publish
Starting from 10.5, CentraSite allows you to publish mediator published virtual services to API Portal using the Legacy Portal Publish action.
Note:
You cannot publish a native service through the Legacy Portal Publish action.
Doing this involves the following high-level steps:
1. Make sure the virtual service is published to the Mediator, before you initiate the Legacy Publish process.
2. The user initiates the Legacy Portal Publish action and specifies the API Portal to which they are to be published.
3. CentraSite publishes the virtual services to each of the specified API Portals.
4. The publishing process continues even if CentraSite encounters a failure with one of the API Portal.
5. CentraSite logs information about the virtual services that fail at the end of the publish process. If the process of publishing returns specific data about the Service, its metadata is updated as required in the API Portal registry.
Before you execute a Legacy Portal Publish action through the Service Details page, you have to publish the virtual service asset to Mediator gateway. Only then Legacy Portal Publish icon appears on the action bar of the Service Details page. Then you can publish the virtual service to API Portal.
To perform a legacy portal publish
1. In CentraSite Business UI, access the Advanced Search panel in one of the following ways:
Click the
Browse link in the upper-left corner of the menu bar.
Click the
Search icon next to the
Scope list. The default search scope is
Assets.
This displays a list of assets in the Search Results page.
2. In the Additional Search Criteria list, select Asset Types.
3. To search for the assets of type, service, click Choose.
4. In the Choose Asset Types dialog box, select the Assets button, and follow these steps:
a. Click the chevron next to Assets button.
b. In the list of asset types, select any of the following types: Virtual Service, Virtual REST Service, Virtual OData Service.
c. Click OK.
5. Click the service you want to publish to the gateways.
This opens the Service Details page. Also, the actions bar displays a set of actions that are available for working with the displayed service.
6. On the actions bar of the Service Details page, click Publish.
This opens the Publish dialog box.
7. Select Mediator from Gateway type drop-down list.
The default is set to API Gateway.
8. (Optional). In the Sandbox list, select a sandbox categories that classify the endpoint of the service for publishing to Mediator gateways:
The Sandbox list includes:
If you choose... | CentraSite displays... |
Development | Instances of a specific gateway whose endpoints are classified by the Development category. |
Production | Instances of a specific gateway whose endpoints are classified by the Production category. |
Test | Instances of a specific gateway whose endpoints are classified by the Test category. |
All Sandboxes | Instances of a specific gateway whose endpoints are classified by any of the above mentioned categories. |
The default is set to All Sandboxes.
This lists Mediator instances and its corresponding sandbox.
9. In the Name column, select one or more Mediator instances to which you want to publish the virtual services.
10. Click Publish.
A Publish Inprogress popup displays the progress state of publishing the service to selected Mediator gateways.
If the publish process logs failures, identify and correct the failure and then try publishing the service again.
Note:
Once the service gets published to the Mediators , the Legacy Portal Publish icon displays on the action bar of the Service Details page.
11. Click Legacy Portal Publish
This lists API Portal gateways and its corresponding sandbox.
12. In the Name column, select one or more API Portal instances to which you want to publish the virtual services.
13. Click Publish.
A Publish Inprogress popup displays the progress state of publishing the service to selected API Portals.
If the publish process logs failures, identify and correct the failure and then try publishing the service again.