When a process run, in order to be monitored you need:
1- Been able writing to database.
2- Been able to read and display information from database.
We guided you thru the steps to been able to read and display information from database, however maybe the first step is to check if you are been able to WRITE this information to database.
Now in order to WRITE to database you must make sure of the following:
1- In 7.1.2 I faced with an anoying issue, if a JDBC pool is configured to “database” instead of “none” (File), then all pools must be configured to DATABASE. Looks like it does not support to send some to file, and others to database, must be ALL to file, or ALL to database.
Therefore ensure you have all configured pools pointing to database, and of course ProcessAudit and ProcessEngine ( but also ISInternal and ISCore audit ).
2- Edit your process in Designer and , under Runtime tab (QoS) you have NOT selected logging level to “1-None”.
Restart IS as required, or re-deploy process if you need to change any setting.
If this still does not work, go to IS settins → Logging → and enable Monitor and Monitor(Database) facilities. This should give you more detailed information from what is happening.
However my bet is you have some JDBC pools to file and others to database, hitting the anoying “defect”.
#MWS-CAF-Task-Engine#webMethods#webMethods-BPMS