Publishing Service Assets to API Portal Gateway

When you execute a Publish action through the Service Details page, the exact rendering of user interface depends on whether or not the native service has an immediate virtual service.

If the native service does not have an immediate virtual service, you are allowed to directly publish the native service to API Portal gateway.

If the native service has an immediate virtual service, you are directed to select one or more virtual services (in addition to the native service), and then publish the selected services to API Portal gateway.

To publish a Service asset to API Portal gateway

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: Service, REST Service, 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.

CentraSite directs you to an intermediate Publish Virtual Services dialog box, if the displayed service has a virtual service. A list of the defined virtual services that are available for publishing to the gateways is displayed.

CentraSite directs you to the Publish to Gateway dialog box, if the displayed service does not have an immediate virtual service.

7. In the Publish Virtual Services dialog box, select one or multiple virtual services you want to publish to the gateways, and then click Next.

This opens the Publish to Gateway dialog box.

8. In the Gateway list, select one or more API Portal gateways to that you want to publish the virtual services.

The Gateway list only displays the gateways for which you have the Modify permission.

The Gateway list provides the following information about each gateway:

Column	Description
Name	Name of the gateway.
Type	API Portal
Sandbox	The category to classify deployment endpoint of the gateway.
Settings	The Configure icon displays the API Portal Settings dialog box that allows you to configure a set of sandbox categories for the specified API Portal individually. The dialog box also lists the set of API communities available for the specified API Portal. You can assign a service to one or more API communities.

9. (Optional). In the Sandbox list, do the following:

a. Click the Configure icon next to the field labeled Sandbox.

This opens the API Portal Settings dialog box.

b. Select one or multiple sandbox categories that classify the endpoint of the service for publishing to API Portal 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.

c. Select one or multiple communities available for a particular API Portal gateway.

The default is set to Public Community. Any new community assigned to the service overwrites the existing community assignments.

d. Click OK.

10. Click Publish.

A Publish Inprogress popup displays the progress state of publishing the service to selected API Portal gateways.

If the publish process logs failures, identify and correct the failure and then try publishing the service again.