CentraSite Documentation : Working with the CentraSite Business UI : Managing Governance Rules : Mediator Runtime Aliases : Defining the Runtime Aliases
Defining the Runtime Aliases
Before you define the runtime (routing) endpoint aliases, the following prerequisites must be met:
*Ensure that the targets for the aliases have already been created. For example, you might have three targets: Development, Testing, and Production.
*Ensure that you have the necessary permissions to deploy the endpoint aliases. If no target-level user credentials are provided, CentraSite uses the credentials of the user who is logged in.
To define runtime endpoint aliases
1. In CentraSite Business UI, click Manage Governance Rules.
2. Click the Add Runtime Alias action and complete the following fields in the runtime alias wizard:
Field
Description
Runtime alias type
Select the type of runtime alias:
*Simple Alias: A simple routing URL or host and port name.
*Secure Alias: Contains username, password, and domain values. The password is hashed and put into secure storage so that it is not visible in clear text.
*Endpoint Alias: A name and value pair which can also contain endpoint properties such as Connection Timeout, Read Timeout, etc.
Authentication Scheme
For the Secure Alias type only. Select one of the following:
*HTTP Basic Authentication
*NTLM
*OAuth2
Name
Assign a name to the alias.
Description
(Optional) Write a description for the alias.
3. Click Next.
4. Complete the following fields:
Field
Description
Default Value
Enter a default URL or components of the URL such as service name to use when no stage-specific values are entered. This default value is overwritten at deployment time by stage-specific values, if they exist.
Stage-specific Values
Select an instance of Mediator. The stage-specific targets and their URLs are displayed below this field.
Endpoint Properties
For the Endpoint Alias type only. Click the endpoint properties icon next to Stage-specific Values to configure endpoint properties.
*SOAP Optimization Method: Optional, This setting is not applicable for REST services. Mediator can accept the following methods to optimize the payloads of SOAP requests:
*MTOM: Indicates that Mediator expects to receive a request with a Message Transmission Optimization Mechanism (MTOM) attachment, and will forward the attachment to the native service.
*SwA: Indicates that Mediator expects to receive a “SOAP with Attachment” (SwA) request, and will forward the attachment to the native service.
*None (the default).
*Connection Timeout: The time interval (in seconds) after which a connection attempt will timeout. If a value is not specified (or if the value 0 is specified), Mediator will use the value of the global property pg.endpoint.connectionTimeout located in the file Integration Server_directory\packages\WmMediator\config\resources\pg-config.properties. The default of that property is 30 seconds.
*Read Timeout: The time interval (in seconds) after which a socket read attempt will timeout. If a value is not specified (or if the value 0 is specified), Mediator will use the value of the global property pg.endpoint.readTimeout located in the file Integration Server_directory\packages\WmMediator\config\resources\pg-config.properties. The default of that property is 30 seconds.
SSL Options: To enable SSL client authentication for the endpoint, you must specify values for both the Client Certificate Alias field and the IS Keystore Alias field. If you specify a value for only one of these fields, a deployment error will occur.
Note:  
SSL client authentication is optional; you may leave both fields blank.
*Client Certificate Alias: The client's private key to be used for performing SSL client authentication. If you specify a client certificate alias, you must also include in the virtual service's policy the “Require SSL” action and select that action's “Client Certificate Required” option. The “Client Certificate Required” option specifies whether client certificates are required for the purposes of: 1) Verifying the signature of signed SOAP requests or decrypting encrypted SOAP requests, and 2) Signing SOAP responses or encrypting SOAP responses.
*IS Keystore Alias: The keystore alias of the instance of Integration Server on which Mediator is running. This value (along with the value of Client Certificate Alias) will be used for performing SSL client authentication.
WSS Header Customization: Indicates whether Mediator should pass the WS-Security headers of the incoming requests to the native service.
*Pass all security headers: Passes the security header, even if it is processed by Mediator (i.e., even if Mediator processes the header according to the virtual service's security run-time policy).
Note:  
If the virtual service does not contain a security run-time policy, and the mustUnderstand attribute of the security header is 0/false, then Mediator will always forward the security header to the native service.
*Remove processed security header from request before routing: Removes the security header if it is processed by Mediator (i.e., if Mediator processes the header according to the virtual service's security run-time policy). Note that Mediator will not remove the security header if both of the following conditions are true: 1) Mediator did not process the security header, and 2) the mustUnderstand attribute of the security header is 0/false).
Examples:
Endpoint Type
Field Values
Alias
*Name: ProdSandbox
*Default Value: http://myhost:5555
Secure Alias
*Name: ProdAuthToken
*Password: ****
*Domain: mysever.sag
Endpoint Alias
*Name: SearchServiceProductionEndpoint
*Description: The clustered production endpoint for the search service.
*Default Value: http://prodcluster:6666/Search
*Endpoint Properties:
*Connection Timeout: 5
*Read Timeout: 15
5. Click Publish.
Next, you need to reference the alias in the virtual service, as described in Referencing the Runtime Aliases in Virtual Services.
Copyright © Software AG, Darmstadt, Germany.
Product LogoContact Support   |   Community   |   Feedback