About the Task Engine Configuration
In a typical production environment webMethods Task Engine interacts with other webMethods components, such as Process Engine and webMethods Monitor. To enable proper operation, you must configure the connection between Task Engine and the other webMethods components. The configuration settings are specific to the runtime on which Task Engine is installed.
For Task Engine on My webMethods Server, you must configure the following:
In
My webMethods, a connection to the
Integration Server on which
Process Engine is installed to enable
Task Engine to provide results from completed tasks to the
Process Engine. You do this by specifying the location of the
Integration Server on which the
Process Engine is running.
In
Integration Server Administrator, a connection between the
Process Engine and
Task Engine that it is to work with. You do this by specifying the location of the
My webMethods Server on which
Task Engine is running on the configuration page of the wmTaskClient package.
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. If 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.
For Task Engine on Integration Server, you must configure the location of the Integration Server on which Task Engine is installed. You do this on the configuration page of the wmTaskClient package, by specifying the location of the Integration Server, or selecting in-process communication when Task Engine and Process Engine are installed on the same Integration Server.