Runtime Versioning Support in Mediator

Mediator supports deployment of versioned virtual APIs or services. You can deploy one or more versions of a virtual API or service to Mediator. The deployed versions of virtual API or service can be used simultaneously. You can provide a unique version to a particular virtual service or an API in CentraSite and publish a specified version of an API or a service to Mediator.

Each version is a unique service and the deployed versions are displayed in the Services page under the CentraSite navigation panel. Each version is unique and you must use an appropriate WSDL to generate the requests.

On creating a new virtual alias in Mediator, you can enter an endpoint prefix for the alias to be invoked in the Endpoint prefix for invocation alias field. The endpoint prefix provided in this field is displayed in the URL field of the VSD .

The information entered in the Endpoint prefix for invocation alias field is also available in the WSDL file.

Note:

While generating the request, the content in the requests can be different for different versions. Hence, ensure that you select an appropriate WSDL of the version used to generate the request.

The version can be system defined version, for example, 1.0, 2.0, or 3.0. Optionally, you can also define the user version of a versioned service, for example, u1, u2, or u3. These system or user defined versions are displayed in the URLs for endpoints as follows:

If the system defined version is 1.0 and if no user version is defined, then this system defined version is appended after the service name in the URL. For example,

http://127.0.0.1:5555/ws/<service name>/<system defined version>
http://127.0.0.1:5555/ws/TestVS1/1.0

If you have defined the version of a versioned service, for example, ver2, then the version defined by you is appended after the service name in the URL. For example,

http://127.0.0.1:5555/ws/<service name>/<user defined version>
http://127.0.0.1:5555/ws/TestVS1/ver2

If you have provided a prefix for the alias in the Endpoint prefix for invocation alias field, for example, /testing/EPprefix, then this endpoint prefix for invocation alias is appended before the service name in the URL. For example,

http://127.0.0.1:5555/ws/<endpoint prefix for invocation alias>/<service name>/
<system or user defined version>
http://127.0.0.1:5555/ws/testing/EPprefix/TestVS1/ver2