Referencing the Runtime Aliases in Virtual Services

CentraSite Documentation : Working with the CentraSite Business UI : Managing Governance Rules : Mediator Runtime Aliases : Referencing the Runtime Aliases in Virtual Services

After you have defined the runtime (routing) aliases, you need to reference them in the virtual services. Before you do this, the following prerequisites must be met:

Ensure that the gateways to which the virtual service will be deployed has already been created. For example, you might have three gateways: Development, Testing, and Production.

Ensure that you have the API Run-time Provider role for creating an alias.

Ensure that you have the Mediator Publisher role or Publishing permissions on the Mediator gateway for publishing the aliases to Mediator.

To reference an alias in a virtual service

1. In CentraSite Business UI, open the virtual alias.

2. Click Virtualize in the action bar.

3. Select Create New Virtual Alias and specify a name for the virtual alias and click Next.

You may also reconfigure an existing virtual alias.

4. For Simple and Endpoint aliases In the Policy Actions window, Policy Enforcement > Routing section, select one of the following routing actions and use ${<aliasname>} (<aliasname> is the name of the alias specified in the previous step) in Route to, to form the complete routing URL:

Routing Action	Description
Straight Through Routing	Routes the requests directly to a native endpoint that you specify.
Content Based Routing	Route requests to different endpoints based on specific criteria that you specify.
Load Balancing and Failover Routing	Routes the requests across multiple endpoints
Context Based Routing	Route requests to different endpoints based on specific values that appear in the request message.

5. For Secure alias only In the Policy Actions window, Policy Enforcement > Outbound Authentication,

a. Select one of the following authentication actions:

Authentication Action	Description
HTTP Basic Authentication	Uses HTTP basic authentication to verify the client's authentication credentials contained in the request's Authorization header against the Integration Server's user account.
NTLM Authentication	Uses NTLM authentication to verify the client's authentication credentials contained in the request's Authorization header against the Integration Server's user account.
OAuth2 Authentication	Uses OAuth2 authentication to verify the client's authentication credentials contained in the request's Authorization header against the Integration Server's user account.

b. For Authenticate Using, select Secure Alias.

c. Enter the Alias name.

6. For webMethods Integration Server only, in the Policy Actions > Request Handling or Response Processing window, select Invoke webMethods Integration Server.

To configure Invoke webMethods Integration Server:

a. Select webMethods IS Service Alias in the Select Type option.

b. Type the alias name (already created) in the webMethods IS Service Alias field.

7. For Transformation Alias only, select one of the following:

Policy Actions > Request Handling > Request Transformation

Policy Actions > Response Processing > Response Transformation

To configure Request or Response Transformation:

a. Select Tranformation Alias in the Select Type option.

b. Type the alias name (already created) in the Transformation Alias field.

8. Click Virtualize.

Contact Support | Community | Feedback