Creating a Version for Virtual API or Service

CentraSite Documentation : Runtime Governance with CentraSite : Virtualized APIs in CentraSite Business UI : Versioning Virtual API or Service : Creating a Version for Virtual API or Service

A service can be versioned when:

a virtual service (v1) is created either from scratch or from native service v1. The subsequent versions of this virtual service ( v1) can be created by versioning v1.

a virtual service (v1) is created from native service (v1) , on versioning, the native service (v2) is created. Virtual service (v2) is created by newly virtualizing native service (v2).

To create a new version for an existing service:

1. In the CentraSite BUI, go to the API or service details page.

2. In the action bar of the API or service, click Version.

3. In the Add a New Version wizard, specify the following fields:

In this field...	Specify...
Namespace	Optional. A namespace for the new versioned virtual service. By default, the URL of the service to be versioned is displayed.
Version	Optional. A version identifier for the virtual service. The version identifier is an optional attribute that you can increment when a service is modified to indicate that the service has been updated. It can contain alphanumeric characters and special characters. If no value is specified, a system generated number is displayed.
Organization	Specify the organization to which this versioned virtual service will be added.
Change Log	Optional. To add a comment for the versioned virtual API or service inorder to keep track of the modifications made (if any).
Version dependent assets	Optional. Select this checkbox if you want to version the assets dependent on the service that is versioned.

Note:

Only the newly versioned API or service can be versioned. For example, if a virtual service V1 having version as 1.0 is versioned to 2.0, virtual service 1.0 cannot be versioned, only the virtual service versioned to 2.0 can be versioned.

4. Click Version.

A new version of the service or the API is created in CentraSite with the version details specified. A copy of the current virtual service which consists of all the details, references, consumers, and local policy definitions is created and linked to the previous version of the service.

Note:

The request can be routed to the oldest version of the deployed versions of the virtual service using the pg.default.enable.oldVersion property. If this property is set to true (the default) and a virtual service is executed without a version, then the request is routed to the oldest version of the deployed versions of the virtual service. If this property is set to false and a virtual service is executed without a version, then the request is routed to the newest version of the deployed versions of the virtual service.

For more information on versioning, refer to the Versioning Support in Mediator section in the Administering webMethods Mediator guide.

Contact Support | Community | Feedback