In addition to the automatic cache refreshing, a typical InterAction environment may have several other automated processes running at various times. For example, an environment might have a schedule like the following:
- Synchronize contacts between the firm list and user lists.
- Synchronize user contacts with Microsoft® Outlook®.
- Transform data with Application Collaboration once a week. This updates the master InterAction database with data from the accounting and HR systems.
- Backup each database twice daily.
- Perform database maintenance once a week.
- Reboot the operating system every Sunday.
If you encounter performance issues during these automated processes, you may want to coordinate the schedules so multiple processes are not running at the same time. Since all these processes use system resources on either the Application Server or the InterAction database server, coordinating the schedules can help improve overall performance.
Reviewing the Existing Schedule
To find the times in which overlapping processes use up too many server resources, use your database and server monitoring tools. Usage peaks discovered during specific times of the day are likely candidates for revising the schedule.
Once you have an idea of potential problem times, review the schedules for all of the automated processes that apply in your environment and write out the schedule.
Review this schedule and the peak times to determine windows of time in which Application Server can refresh the cache without affecting performance. You can set up Application Server sleep windows. Application Server stops automatically refreshing the cache during these windows.
For details about sleep windows, see Preventing Automatic Cache Refreshing.