When a client invokes a service via an HTTP request, Integration Server checks the credentials and user group membership of the client against the Execute ACL assigned to the service. Integration Server performs this check to make sure the client is allowed to invoke that service. In a publish-and-subscribe situation, however, Integration Server invokes the service when it receives a document rather than as a result of a client request. Because Integration Server does not associate user credentials with a published document, you can specify the user account for Integration Server to use when invoking services associated with webMethods messaging triggers.

You can instruct Integration Server to invoke a service using the credentials of one of the predefined user accounts (Administrator, Central, Default, Developer, Replicator). You can also specify a user account that you or another server administrator defined. When Integration Server receives a document that satisfies a trigger condition, Integration Server uses the credentials for the specified user account to invoke the service specified in the trigger condition.

Make sure that the user account you select includes the credentials required by the execute ACLs assigned to the services associated with triggers. For example, suppose that you specify "Developer" as the user account for invoking services in triggers. The receiveCustomerInfo trigger contains a condition that associates a publishable document type with the service addCustomer. The addCustomer service specifies "Replicator" for the Execute ACL. When the trigger condition is met, the addCustomer service will not execute because the user setting you selected (Developer) does not have the necessary credentials to invoke the service (Replicator).

How you specify a user account for a webMethods messaging trigger service depends on the messaging provider used by the trigger.