CentraSite Documentation : Runtime Governance with CentraSite : Virtualized Services in CentraSite : Viewing REST/XML-based Virtual Services : The Routing Protocols Step (REST/XML) : The “Content-based” Routing Protocol Step (REST or XML)
The “Content-based” Routing Protocol Step (REST or XML)
Perform the following steps to examine the “Content-Based” routing of a virtual REST or XML service:
To examine “Content-Based” routing
1. In CentraSite Control, display the details page of REST/XML virtual service. For procedures for this step, see Viewing or Editing Virtualized Services.
2. Open the Processing Steps profile.
3. Select the Routing Protocols tab. On this tab, examine the following fields:
Field
Description
Service Type
Specifies XML (for a native REST or XML service).
Routing Type
Specifies the routing type Content-Based.
Routing Rules
Specifies one or more routing rules.
Click the Configure Endpoint Properties icon (next to the Endpoint button) for an endpoint.
This icon displays a dialog box that enables you to examine the properties defined for an endpoint as follows:
*HTTP 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: Enables SSL client authentication for the endpoint.
*Client Certificate Alias: The client's private key used for performing SSL client authentication.
*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) is used for performing SSL client authentication.
HTTP Method
Specifies the HTTP method to pass to the native service.
Default To
Specifies the URL of the native service to route the request to.
HTTP Authentication
Authentication Scheme: Specifies the mode of authentication: Basic Authentication (default), NTLM, OAuth2 or None.
Basic Authentication.
*Use credentials from incoming request: (default): Authenticates requests based on the credentials specified in the HTTP header. Mediator passes the “Authorization” header present in the original client request to the native service.
*Use specified credentials: Authenticates requests according to the values you specify in the User, Password, and Domain fields.
NTLM. Note that if Mediator is used to access a native service protected by NTLM (which is typically hosted in IIS), then the native service in IIS should be configured to use NTLM as the authentication scheme. If the authentication scheme is configured as “Windows”, then “NTLM” should be in its list. The “Negotiate” handshake will be supported in the near future. This note applies to all three of the following options for NTLM:
*Use credentials from incoming request: Default. Mediator uses the user credentials passed in the request header for an NTLM handshake with the server.
*Use specified credentials: Mediator uses the values specifies in the User, Password, and Domain fields for an NTLM handshake with the server.
*Transparent: If the property watt.pg.disableNtlmAuthHandler is set to false (the default), then Mediator will behave in "pass by" mode, allowing an NTLM handshake to occur between the client and server. If the property watt.pg.disableNtlmAuthHandler is set to true, then Mediator performs the Kerberos Windows authentication (and not NTLM Windows authentication). This property is located in Integration Server_directory\instances\instance_name\config\server.cnf. Note: If the client is a WCF application, then the client should be configured with clientCredentialType set to NTLM.
OAuth2.
*Use credentials from incoming request: Default. This is known as “pass through” mode, in which the consumer includes an OAuth2 access token (a “Bearer” type token) in the request. Mediator then passes the access token unchanged to the native OAuth server.
*Use specified token: In this mode, the consumer does not include an OAuth2 access token in the request. Instead, the provider generates an OAuth2 access token for each consumer, and Mediator stores the access tokens in Passman. When consumers send requests, Mediator obtains the OAuth2 access tokens from Passman and uses them to access the native services. Specify an OAuth access token to be deployed by Mediator. If you select this option, the consumer need not pass the OAuth token during service invocation. Click the Show Token button to view the OAuth access token. Users who do not have the permissions to create and manage virtual services will not see this button.
None. Select the following option:
*Invoke Service Anonymously: Does not authenticate requests.
HTTP Headers
Specifies the HTTP headers used to authenticate the requests.
*Use Existing: Uses the HTTP headers that are contained in the requests.
*Customize: Uses the HTTP headers that are specified in the Name and Value columns below.
Copyright © 2005-2016 Software AG, Darmstadt, Germany.

Product LogoContact Support   |   Community   |   Feedback