Manage Service Resolution

When the gateway receives a message, it must determine the target service—this process is known as service resolution. The Service Resolution Settings dialog allows you to configure resolution behavior.
When the
Layer7 API Gateway
receives a message, it must determine the target service—this process is known as service resolution. The Service Resolution Settings dialog allows you to configure resolution behavior.
To learn more about the
Layer7 API Gateway
service resolution logic, see Gateway Service Resolution Process.
Before you change any of the resolution settings, be aware of the following ramifications:
  • Changing service resolution settings may cause services that previously resolved to no longer resolve. For example, you have two services that share the same custom resolution path but are capitalized differently. If you change the resolution to be case insensitive, those services will conflict.
To configure service resolution
:
  1. In the Policy Manager, select
    [Tasks] > Transports > Manage Service Resolution
    from the Main Menu (on the browser client, from the Manage menu). The Service Resolution Settings dialog appears. You can also access this dialog from the Manage Listen Ports task.
    Configure the dialog as follows:
    Setting
    Description
    HTTP/FTP Resolution
    Only Services with a resolution path are accessible
    Select this check box to prevent access to any service that was not assigned a resolution path via HTTP/FTP listeners. This is useful when you have services associated with a JMS or Email listener and you wish to prevent any other access.
    Clear this check box to allow all services to be resolved as described under Gateway Service Resolution Process. This setting is the default.
    Resolution paths are case sensitive
    Select this box to enforce case sensitivity of resolution paths. This setting is the default.
    Clear this check box to ignore case when comparing a request to a services custom resolution path. Relaxing the case allows services to be more readily matched.
    Switching to case insensitive comparisons may cause services that previously resolved to no longer resolve. For example, there are two services that have the same custom resolution path differentiated only by case. In the default behavior, these two paths are unique, but when case sensitivity is removed, those resolution paths are now the same and the services will conflict.
    Other Areas Affected by Case Sensitivity Changes
    Changing the case sensitivity for resolution paths also affects how other areas of the
    Layer7 API Gateway
    resolve services:
    • WSDL Proxy
      : A path can be used in the WSDL proxy to identify from which service the WSDL should be download. When case sensitivity is disabled, the WSDL proxy matches the services accordingly.
    For more information, see Download a WSDL in the WSDL Proxy & Policy Downloads.
    • WSDM Services
      : A path can be used to identify a WSDM service. When case sensitivity is disabled, the WSDM services matches the services accordingly.
    For more information, see Working with Internal Services.
    Allow resolution by "L7-Original-URL" header
    Select this check box to allow a service to be resolved using a path supplied in an HTTP header. This setting is the default.
    For more information, see "Step 2: Determine service based on URI" under Gateway Service Resolution Process.
    Allow resolution by Service GOID/OID in URLs
    Select this check box to permit services to be resolved by URLs that contain the service GOID (i.e., entity ID) or OID. This setting is the default.
    Clear this check box to not permit resolution by service GOID or OID.
    For more information, see "Step 1: Determine service based on service entity ID" under Gateway Service Resolution Process.
    SOAP Message Resolution
    Use SOAP action
    Select this check box to permit services to be resolved based on the SOAP action in the incoming message. This setting is the default.
    Clear this check box to not consider the SOAP action when resolving the service.
    For more information, see "Step 3: Determine service based on SOAPAction" under Gateway Service Resolution Process.
    Use SOAP body child namespace
    Select this check box to permit services to be resolved based on the SOAP payload namespace of the message body. This setting is the default.
    Clear this check box to not consider the namespace in the SOAP payload when resolving the service.
    For more information, see "Step 4: Determine service based on SOAP payload namespace" under Gateway Service Resolution Process.     
  2. Click [
    OK
    ] when done.