Performance Considerations

Watchlists are designed with the goal of reducing the load on the web server. Running a Watchlist with a query requires less overhead than opening the associated application to get that same information. If users can get the information they need from the Watchlist menu without opening an application, this produces a net reduction in web server load and a net gain in productivity.

Having a Watchlist defined with a refresh interval of five minutes does not mean that the Watchlist will run every five minutes. A user action (for example, clicking on the Watchlist dropdown menu) causes the Watchlist to check the refresh interval to see if it should be updated. So Watchlists do not run without user action.

There are multiple configuration settings that help ensure that users cannot set up Watchlists that would adversely affect web server performance. These settings can be found in the Web Runtime section of Server Manager under the Web Objects Settings heading.

Web Objects Setting	Value
Watchlists: Default Max Records to Return	Specify the default value for the "Max Records to Return" field in the Watchlist Management tab. This is used when creating Watchlists.
Watchlists: Upper Limit on Max Records to Return	Specify the largest value a user is allowed to enter in the "Max Records to Return" field for a Watchlist. The user receives an error if he exceeds this value when creating or editing a Watchlist.
Watchlists: Default Refresh Interval	Specify the default value in minutes for the "Refresh Interval" field in the Watchlist Management tab. This is used when creating Watchlists.
Watchlists: Lower Limit on Refresh Interval	Specify the smallest value in minutes that a user is allowed to enter in the "Refresh Interval" field for a Watchlist.
Watchlists: Number of Threads	Specify the maximum number of Watchlists per user that can update simultaneously.

For more information on creating Watchlists, see the JD Edwards EnterpriseOne Applications One View Watchlists Implemenation Guide.