Configuring Task Client in Integration Server or Microservices Runtime Containers
The WmTaskClient package stores all configurations you make in the taskclient.properties file, which resides in the Integration Server_directory /pacakges/WmTaskClient/config/ directory. When running in a Integration Server or Microservices Runtime container, you can modify the WmTaskClient package configuration at containers startup, by providing a taskclient.properties file in a volume or host directory, mounted to the following path in the container: /opt/softwareag/IntegrationServer/pacakges/WmTaskClient/config/taskclient.properties.
The following sample describes the syntax of the taskclient.properties file:
#wmtaskclient
#Mon Sep 07 18:55:47 EEST 2020
taskclientretries=0
taskclientusejms=false
taskclientimpersonateacl=Admins
taskclientuser=Administrator
taskclientpassword=PASS
taskclienttimeout=60000
taskserver=REMOTE_MWS
taskclienturl=http\://MWS_HOST\:8585
taskclientretries=5
taskclientretrydelay=1000
where the WmTaskClient properties correspond to the following user interface fields:
taskclientusejms -
Use JMStaskclientimpersonateacl -
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.