webMethods Task Engine 10.2 | Configuring the Task Engine Environment | About Task Engine Configuration
 
About Task Engine Configuration
webMethods Task Engine interacts with several other webMethods components, including the Process Engine and Integration Server. To enable proper operation, you must specify information about these components as follows:
*You must configure a connection to the Process Engine you want to work with to enable the Task Engine in My webMethods Server to provide results from completed tasks to the Process Engine. You do this by specifying the location of the Integration Server where the Process Engine is running.
*You must a configure a connection between the Process Engine and the Task Engine that it is to work with. You do this with the Integration Server Administrator.
Important: If you are working in a clustered My webMethods Server environment, you must also apply the Task Engine server role to each server node in the cluster when you set up clustered operation, as described in Administering My webMethods Server. This role must be applied to all nodes of the cluster where Task Engine operations are performed; for example, tasks being worked on (either from an inbox or Task List Management) or queued from the Process Engine. If there are nodes in the cluster where these operations would never happen, this role can be omitted from these nodes.
The Task Engine also requires a connection to a JDBC data source on Integration Server to enable the Task Engine to provide log events for webMethods Monitor. When the Task Engine first requires this connection, it queries the specified Integration Server to determine the name of this JDBC pool, and configures a connection automatically.
Therefore, no manual configuration is required. However, in the event the name or location of the JDBC pool on Integration Server changes, you can redefine the configuration as described in Configuring a JDBC Data Source.

Copyright © 2007-2018 | Software AG, Darmstadt, Germany and/or Software AG USA, Inc., Reston, VA, USA, and/or its subsidiaries and/or its affiliates and/or their licensors.
Innovation Release