The precise definition of service invocation for your system depends on your Pegasystems license and the Data-Admin-License instance identified in the System instance, and may not match the definition provided here. For official documentation, contact Global Customer Support.

A service invocation is a call from any external system to execute a Rule-Service-* rule in your application that creates, updates, or operates on a work object. Ordinarily, a service request that only reads information (rather than performs update processing) does not count as a service invocation. When counting service invocations, it does not matter whether the application sends a response to the service request.

For example, a License Compliance facility can count a service invocation when all the following occur:

• A service request is received from an external system.
• The service request requires authentication.
• The License Type field on the Security tab of the Operator ID instance used for authentication is set to Invocation.
• The Method is read-only checkbox on the Service tab of the service rule form is not checked.

Service BPEL rules and Service Portlet rules can be exceptions; these are not counted as service invocations. Special rules apply to counting service invocations from Service File rule executions. BURND 4/20/07

To see a chart of period-by-period counts of service invocations on your system, select> System > Tools > Usage Metrics> Services Invocation Chart. BYRNB 2/25/10

	SOA
	Working with the License Compliance facility About License Compliance data instances License Compliance facility — Reports and charts

Definitions — S