Updating Tasks Applying Optional Settings
Several optional Task Engine settings apply when you update tasks with the available Web and built-in services:
Note:
In addition to the following options, you are advised to review all of the available options described in the PDF publication webMethods Task Engine User’s Guide.
-Dtask.update.sync. Cluster synchronization is not enabled by default. This option helps to solve the problem that when a task is updated, there is a small (up to 2 second) delay until other nodes in the cluster reflect the change. This is normally not an issue for standard task interfaces, but it can present a problem for remote Task Engine Web service APIs, as well as services in the WmTaskClient package. For more information, see the PDF publication
webMethods Task Engine User’s Guide.
-Dtask.lock.wait.timeout and -Dtask.lock.valid.time. These two options specify both the time that the Task Engine will wait to obtain a lock on a task instance (default=10 seconds), as well as the duration of the lock (default=60 seconds). For more information, see the PDF publication
webMethods Task Engine User’s Guide.
-Dupdate.completed.task. This option enables a remote service to update tasks regardless of task status. By default, you can update only tasks in Active, Error, and Suspended state. For more information, see the topic “Task Update Behavior” in the PDF publication
webMethods Task Engine User’s Guide.
Related Topics