Configuring a JDBC Data Source
To enable the
Task Engine to provide log events for
webMethods Monitor, a JDBC data source must be specified as a JDBC pool existing on the
Integration Server specified in
Configuring Task Engine in My
webMethods. Otherwise, it will not be possible to view task-related information when browsing process instances with
webMethods Monitor.
The name of the pool must be ProcessAudit and it must point to the process audit database used by webMethods Monitor. If this JDBC pool is not already defined locally on the My webMethods Server, the Task Engine automatically checks to see if this pool exists on the configured Integration Server. If the pool is defined there, the Task Engine creates an identical pool in My webMethods Server.
Note:
The Task Engine checks for the presence of an existing pool on the configured Integration Server only after the first task is queued from a business process following a start-up of My webMethods Server. During the interval between start-up and the queuing of the first task from a business process, the JDBC pool may not exist on My webMethods Server.
In general, 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 follows:
To reconfigure a
Task Engine JDBC data source
1. In My webMethods: Navigate > Applications > Administration > My webMethods > Data Sources. This panel displays all available data sources. Note that the default data source cannot be deleted or modified.
2. On the Data Source panel, click
for the
ProcessAudit data source and choose
Modify from the menu.
3. On the Data Source Properties panel, modify the display name and database server type from list if required.
4. Click Next.
5. Modify the required database connection information as needed:
Server host name
Server port number
Database name
User name
Password
6. Click Submit.