Configuring Task Client in Integration Server or Microservices Runtime Containers

When running Integration Server or Microservices Runtime as Docker containers, you can modify the WmTaskClient package configuration on container startup using the application.properties file for the Integration Server or Microservices Runtime container.

The following sample lists the configuration properties, that the WmTaskClient package supports and the syntax to use when including WmTaskClient settings in the application.properties file for an Integration Server or Microservices Runtime container:

taskclientproperty.taskclientretries=0
taskclientproperty.taskclientusejms=false
taskclientproperty.taskclientimpersonateacl=Admins
taskclientproperty.taskclientuser=Administrator
taskclientproperty.taskclientpassword=PASS
taskclientproperty.taskclienttimeout=60000
taskclientproperty.taskserver=REMOTE_MWS
taskclientproperty.taskclienturl=http\://MWS_HOST\:8585
taskclientproperty.taskclientretries=5
taskclientproperty.taskclientretrydelay=1000

The WmTaskClient properties correspond to the following user interface fields:

taskclientusejms - Use JMS

taskclientimpersonateacl - Integration Server ACL containing users allowed to impersonate

taskclientuser - Task Server Username

taskclientpassword - Task Server Password

taskclienttimeout - Socket Timeout (milliseconds)

taskserver - Task Server

taskclienturl - Task Server URL

taskclientretries - Number of Retries on Service Failure

taskclientretrydelay - Delay Between Service Retries (milliseconds)

For more information about the WmTaskClient configuration options, see Configuring the WmTaskClient Package. For more information about using Integration Server and Microservices Runtime packages with Docker, see webMethods Integration Server Administrator’s Guide.