Ensure that the gateways for the aliases have already been created. For example, you might have three gateways: Development, Testing, and Production.Ensure that the gateways for the aliases have 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.Field | Description | ||
Runtime alias type | Select the type of runtime alias: Simple Alias: A simple routing URL or host and port name.webMethods Integration Server Alias: Contains the webMethods Integration Server service 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.Transformation Alias: Accepts the XSLT style sheet to be used for the request or response transformation.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 AuthenticationNTLMOAuth2 | ||
Name | Assign a name to the alias. | ||
Description | (Optional) Write a description for the alias. |
Field | Description | ||
Default Value | The value used by default when no stage-specific values are entered. This default value is overwritten at deployment time by stage-specific values, if they exist. For Simple or Endpoint Alias , type a default URL or components of the URL such as service name. For webMethods Integration ServerAlias, type the webMethods Integration Server service name. For Transformation Alias, choose an XSLT style sheet which is considered as a default value. | ||
Stage-specific Values | Stage specific values are used to define the values that are specific to a particular Mediator. You can select an instance of Mediator and enter the value to be used for that Mediator. | ||
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.
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 (that is, even if Mediator processes the header according to the virtual service's security run-time policy).
Remove processed security header from request before routing: Removes the security header if it is processed by Mediator (that is, 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). |
Endpoint Type | Field Values |
Alias | Name: ProdSandboxDefault Value: http://myhost:5555 |
webMethods Integration Server Alias | Name: ProdServiceDefault Value: fault:postProcess |
Secure Alias | Name: ProdAuthTokenPassword: ****Domain: mysever.sag |
Transformation Alias | Name: ProdTransDefault Value: sample.xsl |
Endpoint Alias | Name: SearchServiceProductionEndpointDescription: The clustered production endpoint for the search service.Default Value: http://prodcluster:6666/SearchEndpoint Properties:Connection Timeout: 5Read Timeout: 15 |
