CentraSite Documentation : Working with the CentraSite Business UI : Managing Governance Rules : Mediator Runtime Aliases : Referencing the Runtime Aliases in Virtual Services
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.
Context Based Routing
Route requests to different endpoints based on specific values that appear in the request message.
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.
Dynamic Routing
Route requests to a dynamic URL based on specific criteria that you specify.
5. For Secure alias only In the Policy Actions window, Policy Enforcement > Outbound Authentication,
a. Select one of the following authentication actions:
Routing Action
Description
HTTP Basic Authentication
Used when native API enforces basic authentication. Based on the modes selected, Mediator either uses configured basic authentication credentials to invoke a native service or it uses credentials from the authorization header of the incoming request to access the native API.
NTLM Authentication
Used when native API enforces NTLM authentication. Based on the modes selected, Mediator either uses configured authentication credentials to obtain the NTLM token to invoke the native service or it uses credentials from the authorization header of the incoming request to obtain the NTLM token to access the native API.
OAuth2 Authentication
Used when native API enforces OAuth authorization. Based on the modes selected, Mediator either uses configured OAauth token to invoke the native service or it uses the OAauth token of the incoming request to access native service.
Kerberos Authentication
Used when a service provider wants a web service client that does not have the ability to generate the Kerberos token to access a service enforced with the Kerberos policy. It is also used when service provider wants a web service client to access a service enforced with the Kerberos policy.
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.
Copyright © 2005-2016 Software AG, Darmstadt, Germany.
Product LogoContact Support   |   Community   |   Feedback