Set Web Service Context

Contents

Overview

The Set Web Service Context filter is used in a policy to determine the service to obtain resources from in the Web Service Repository. For example, by pointing this filter at a pre-configured getQuote service in the Web Service Repository, the policy knows to return the WSDL for this particular service when a WSDL request is received. The Return WSDL filter is used in conjunction with this filter to achieve this.

The Set Web Service Context filter is configured automatically when auto-generating a policy from a WSDL file and is not normally manually configured. For a detailed example, see the Web Services Repository tutorial.

Configuration

Name:
Enter a name for the filter in the Name: field.

Service WSDL:
Click the button on the right, and select a service definition (WSDL file) currently registered in the Web Service Repository from the tree. To register a Web Service, right-click the default Web Services node, and select Register Web Service. For more details on adding services to the Web Services Repository, see the Web Services Repository tutorial.

Monitoring:
The fields on this tab enable you to configure whether this Web Service stores usage metrics data to a database. This information can be used by Service Monitor to produce reports showing how and who is calling this Web Service. The following monitoring options are available on this tab:

  • Monitor service usage:
    Select this option if you want to store message metrics for this Web Service.
  • Monitor service usage per client:
    Select this option if you want to generate reports monitoring which authenticated clients are calling which Web Services.
  • Monitor client usage:
    If you want to generate reports on authenticated clients, but are not interested in what Web Services they are calling, select this option and unselect the Monitoring service usage per client checkbox.
  • Which attribute is used to identify the client?:
    Enter the message attribute to use to identify authenticated clients. The default is authentication.subject.id, which stores the identifier of the authenticated user (for example, the username or user's X.509 Distinguished Name).
  • Composite Context:
    Multiple service contexts may be set during the processing of a message. For example, the Enterprise Gateway receives a message, and sends it to serviceA first, and then serviceB. Monitoring is performed for each service. A composite service context may also be set before service A and service B, which includes serviceA and serviceB. This composite service passes if both serviceA and serviceB complete successfully. Monitoring is also performed on the composite. This setting enables you to mark a service context as a composite context, and is not selected by default.