Mediator Runtime Aliases
Typically you will develop, test, and publish a virtual service in stages (Development stage, Test stage, and Production stage as described in the implementation concepts in Getting Started with CentraSite.) When you promote a virtual service from one stage to the next, you will need to change environment settings such as:
The runtime (routing) endpoint for the virtual service.
The routing endpoint connection properties. For example, connection timeout settings, endpoint client certificates.
Outbound authentication tokens.
You can promote a virtual service from one stage to the next in CentraSite by:
promoting the same virtual service from one stage to the next.
Using this method, you have to export/import the virtual service to the next stage, change its environment settings, and then deploy it. In addition, this method of promotion requires a dedicated CentraSite instance for each stage.
creating a separate virtual service for each stage.
Using this method only requires one instance of CentraSite, but you had to use a unique name for each virtual service.
An easier way to promote a virtual service is to define separate routing runtime aliases to be used in each stage. These aliases are deployed to the runtime gateways along with the virtual services, and are referenced by the virtual services at runtime.
