Task Engine 10.11 | Task Engine Webhelp | webMethods Task Engine User's Guide | Configuring the Task Engine Environment | Configuring the WmTaskClient Package | Specifying a User Account for the WmTaskClient Package
Specifying a User Account for the WmTaskClient Package
The My webMethods Server user account you specify for the WmTaskClient package must conform to the following requirements:
*Must be a member of an existing My webMethods Server role.
*Must be assigned the My webMethods Server functional permission, "Impersonate Users for Remote Clients." This is normally done by a making the user a member of a group or role that grants this permission, although this permission can be granted directly to the user if necessary. For additional information, see Remote Session Timeout Values. For general information about granting permissions, see Configuring Task Access Permissions.
*Must be granted permissions to the appropriate tasks, and permissions for all actions that you want to apply to the task using WmTaskClient (again, through group or role membership, or directly).
*Must be included as a group member in an Integration Server ACL that provides execution access to the services in the WmTaskClient package. If you have central user management enabled for your installation, you can add both My webMethods Server groups and roles to the ACL as an ACL group.
For example, if you are running instances of a task type named OrderApproval on My webMethods Server and you want to access these instances using WmTaskClient, the user name you specify must have been granted all permissions for the OrderApproval task type, and must be granted the "Impersonate Users for Remote Client" privilege.
Furthermore, you must ensure that the specified user is a member of a group that is included in an ACL that enables execution of the services in the WmTaskClient package. For more information about working with ACLs, see webMethods Integration Server Administrator’s Guide.