Field | Description | |
HTTP or JMS | Select HTTP. | |
Routing Type | Select Straight Through. | |
Default To | Click Endpoint, and select the URL of the Native Service to route the request to. Alternatively, Mediator offers Local Optimization capability if the Native Service and the Virtual Service (in Mediator) are located on the same machine. With local optimization, service invocation happens in-memory and not through a network hop. In the Default To field, specify the Native Service in either of the following forms: local://<service_full_path> OR local://<server>:<port>/ws/<service_full_path> For example: local://MediatorTestServices:New MediatorTestServices_Port which points to the endpoint service NewMediatorTestServices_Port which is present under the folder MediatorTestServices in Integration Server. This works for HTTP endpoints only, for all types of Routing Protocols. | |
Configure Endpoint Properties (icon) | The Configure Endpoint Properties icon displays a dialog box that enables you to configure a set of properties for the endpoint as follows: ![]() ![]() ![]() ![]() 1. Bridging between SwA and MTOM is not supported. If a consumer sends an SwA request, Mediator can only forward SwA to the native provider. The same is true for MTOM, and applies to responses received from the native provider. That is, an SwA or MTOM response received by Mediator from a native provider will be forwarded to the caller using the same format it received. 2. When sending SOAP requests that do not contain a MTOM or SWA attachment to a Virtual Service for a native provider endpoint that returns an MTOM or SWA response, the request 'Accept' header must be set to multipart/related (or the Virtual Service's Request Processing Step should include an
Virtual Service that sets the BUILDER_TYPE context variable to multipart/related). This is necessary so Mediator knows how to parse the response properly. ![]() ![]() Note: If the Virtual Service does not contain a security run-time policy, and the mustUnderstand attribute of the security header is 0 or false, then Mediator will always forward the security header to the Native Service. ![]() ![]() ![]() Note: If the Virtual Service does not contain a security run-time policy, and the mustUnderstand attribute of the security header is 0 or false, then Mediator will always forward the security header to the Native Service. ![]() ![]() ![]() The precedence of the Read Timeout configuration is as follows: 1. If a value is specified for the Read Timeout field in the routing endpoint alias, Mediator will use the value specified in the Runtime Alias > Endpoint Alias > Endpoint Properties > Read Timeout field. The read timeout value defined at an alias level takes precedence over the timeout values defined at an API level and the global configuration. 2. If a value 0 is specified (or if the value is not specified) for the Read Timeout field in the routing endpoint alias, then Mediator will use the value specified in the Read Timeout field of this step. The read timeout value defined at an API level takes precedence over the global configuration. 3. If a value 0 is specified (or if the value is not specified) for the Read Timeout field in this step (at an API level), then 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 (in the Mediator Administration console, go to > Settings > Extended Settings > pg.endpoint.readTimeout property.). Note: If a value for the Read Timeout configuration is not specified in any of the above configuration parameters, then Mediator will use the default 30 seconds. ![]() Note: SSL client authentication is optional; you may leave both fields blank. ![]() ![]() | |
HTTP Authentication | Authentication Scheme: Specify the mode of authentication: Basic Authentication (default), NTLM, OAuth2, or None. Basic Authentication. Select one of the following options: ![]() ![]() ![]() ![]() 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: ![]() ![]() ![]() OAuth2. Select one of the following options: ![]() ![]() Specify an OAuth access token to be deployed by Mediator by clicking Show Token and selecting an OAuth access token. Users who do not have the permissions to create and manage Virtual Services will not see this button. Note: Here are some general guidelines: ![]() ![]() None. Select the following option: ![]() | |
HTTP Headers | The HTTP headers that you want to use to authenticate the requests. ![]() ![]() |