Software AG Products 10.7 | Using CentraSite | Runtime Governance | Run-Time Alias Management
 
Run-Time Alias Management
 
Defining the Runtime Aliases
Referencing the Runtime Aliases in Virtual Services
Publishing a Virtual Service with Runtime Alias
Note:
This section is not applicable if the CentraSite run-time aspects are not enabled. By default, run-time aspects configured from CentraSite are disabled. However, you can enable them if required. To enable the CentraSite run-time aspects, see Enabling CentraSite Run-Time Aspects.
Mediator Runtime Aliases
You develop, test, and publish a virtual service in Development stage, Test stage, and Production stage respectively. When you promote a virtual service from one stage to the next, you have to change environment settings such as:
*The runtime (routing) endpoint for the virtual service.
*The routing endpoint connection properties. For example, connection timeout settings and endpoint client certificates.
*Outbound authentication tokens.
You can promote a virtual service in CentraSite from one stage to the next by:
*Promoting the same virtual service from one stage to the next.
Using this method, you have to export or 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, however, you have 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.