|
Name:
Enter an appropriate name for the filter to be displayed in a circuit.
Service Name:
Enter an appropriate name for this service to be displayed on the
Service Monitor interface when generating reports for this service.
Monitoring Options:
The fields in this group enable you to configure whether this 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 fields are available:
-
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 which 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.
|