IBM BPM, V8.0.1, All platforms > Administer the IT infrastructure > Administer Business Process Choreographer > Use the administrative console to administer Business Process Choreographer

Refreshing people query results, using the refresh daemon

Use this method if you want to change how often the people query results are refreshed, or if you want to disable the automatic refreshing.

People queries are resolved by the specified people directory provider. The result is stored in the Business Process Choreographer database. To optimize the authorization performance, the retrieved query results are cached. The cache content is checked for currency when the people query refresh daemon is invoked.

In order to keep people query results up to date, a daemon is provided that refreshes expired people query results on a regular schedule. The daemon refreshes all cached people query results that have expired.


Procedure

  1. Open the custom properties page for the Human Task Manager:

    1. Click either Servers > Clusters > WebSphere application server clusters > cluster_name or Servers > Server Types > WebSphere application servers > server_name, then on the Configuration tab, in the Business Integration section, expand Business Process Choreographer, and click Human Task Manager.

    2. Choose one of the following options:

      • To change settings without having to restart the server, select the Runtime tab.

      • To make changes that will only have an effect after the server is restarted, select the Configuration tab.

  2. In the field People query refresh schedule enter the schedule using the syntax as supported by the WebSphere CRON calendar. This value determines when the daemon will refresh any expired people query results. The default value is " 0 0 1 * * ?", which causes a refresh every day at 1 am. If you want to disable the daemon, delete the value. If you disable the daemon, you should use administrative scripts to refresh the queries.

  3. In the field Timeout for people query result enter a new value in seconds. This value determines how long a people query result is considered to be valid. After this time period, the people query result is considered to be no longer valid, and the people query will be refreshed the next time that the daemon runs. The default is one hour.

  4. If you want any changes made on the Runtime tab to remain in effect after the next server restart, select Save runtime changes to configuration.

  5. Click OK.
  6. Save the changes. To make your changes made on the Configuration tab effective, restart the application server.

    The new expiration time value applies only to new people queries, it does not apply to existing people queries.

Use the administrative console to administer Business Process Choreographer


Related tasks:
Refreshing people query results, using administrative scripts


Related information:

Options for maintaining an optimal Business Process Choreographer database size