Deployment Process in CentraSite Business UI

The API management platform of CentraSite Business UI allows you to publish Service assets (also, termed as API assets) and Virtual Service assets (also, termed as Virtual API assets) to and from the webMethods Mediator and webMethods API Portal gateways.

Axis Free Mediation and WSStack are used to process REST services. The advantage of using Axis Free Mediation is that it supports HTTP patch. However, by default, WSStack is used.

Axis Free Mediation is specified by selecting the VSD format. When a new REST service is published, CentraSite publishes the service to the Axis Free Mediation. When a service is republished, CentraSite considers the mediation stack that the service has been published to. Therefore, republishing a service does not modify the mediation stack of a service.

Note:

The republished services do not show any different behavior because of switching between the mediation stack. However, if CentraSite is publishing a service to Mediator 9.10 or earlier versions, it publishes and republishes the REST services to the WSStack Mediation stack.

To change the deployment method for REST services, the restServiceStack configuration parameter in the centrasite.xml customization file has to be set. By default the configuration parameter is set to wsstack. When changing it to Axis-free, any newly published REST service goes to Axis Free Mediation. Redeploying a REST service is not sufficient to change the mediation stack. To change the mediation stack for an already deployed service, it has to be unpublished first and then republished.

Publishing a Service to Mediator gateway refers to the process you use to deploy Virtual Services to Mediator where they are exposed to consuming clients.

The process of publishing a Service asset to a Mediator gateway is carried out by a synchronous mechanism between CentraSite and Mediator.

The process of publishing a Service asset to Mediator gateway includes the following steps:

A user initiates the publish process by selecting the Virtual Services that are to be published, and specifies in which Mediators they are to be published.

The publishing process continues even if CentraSite encounters a failure with one of the Mediator gateway.

CentraSite logs information about the Services that fail at the end of the publish process. If the process of publishing returned specific data about the Services, the Services's metadata is updated as needed in the CentraSite Registry Repository.

Publishing a Service to API Portal gateway refers to the process you use to deploy native and Virtual Services to API Portal on which they are to be exposed for testing and user consumption.

The process of publishing a Service asset to an API Portal gateway is initiated from CentraSite and is carried out on the API Portal server.

The process of publishing a Service asset to API Portal gateway includes the following steps:

A user initiates the publish process by selecting the Virtual Services that are to be published, and specifies in which API Portals they are to be published.

The publishing process continues even if CentraSite encounters a failure with one of the API Portal gateway.