3. In the Home column, click 
for the WmTaskClient package.
for the WmTaskClient package. for the WmTaskClient package. Field | Description |
Task Server URL | The host name and port number of the My webMethods Server instance that contains the Task Engine to which you want to connect. The default value is http://localhost:8585. |
Task Server Username | The My webMethods Server user account that you want to use to connect to Task Engine. The default value is Administrator. For more information about the requirements that apply to the user account, see Specifying a User Account for the
WmTaskClient Package. |
Task Server Password | The password for the specified user account. Type a password or accept the default value. |
Socket Timeout (milliseconds) | The timeout period in milliseconds that all services will wait for a response on the WmTaskClient package Home page. The default value is 60000. The value applies to all WmTaskClient IS services and cannot be overridden for individual service invocations. |
Number of Retries on Service Failure | The number of times to attempt to invoke a service if the initial attempt fails. The default value is 0. The value applies to all WmTaskClient IS services, but can be overridden for individual service invocations by specifying the retryOnFailureCount parameter when invoking a service. |
Delay Between Service Retries (milliseconds) | The number of milliseconds to wait between attempts. The default is 1000. The value applies to all WmTaskClient IS services, but can be overridden for individual service invocations by specifying the retryDelay parameter when invoking a service. This field is ignored if the value for Number of Retries on Service Failure is 0. |
Integration Server ACL containing users allowed to impersonate | The Integration Server Access Control List (ACL) that controls execution access for services in WmTaskClient. By default, this is the Internal ACL. The ACL must include a group that contains the specified user. For more information about working with ACLs, see webMethods Integration Server Administrator’s Guide. |
Use JMS | The protocol that WmTaskClient uses to communicate with My webMethods Server. Values are:  true - WmTaskClient uses Universal Messaging as a Java Message Service (JMS) provider to communicate with My webMethods Server. You can use this option only when Universal Messaging is configured as a JMS provider on the My webMethods Server cluster configuration page. For more information about using Universal Messaging as a JMS provider in a My webMethods Server cluster, see Administering My webMethods Server.false - WmTaskClient uses SOAP calls to communicate with My webMethods Server. This is the default value. |
