Content Management (CM) services, like index management and content exchange, regularly generate tasks. In an Application Server Java (AS Java) cluster, you must assign these tasks to a CM instance otherwise they will not be executed. You assign each task to a single CM instance, making sure that there is an even distribution of tasks to all the available instances.
You can influence the distribution of the workload to different CM instances by adapting the times at which tasks are scheduled to run. By ensuring that long-running tasks or tasks with a high load are triggered at different times, you can distribute the load more evenly.
For more information about the purpose of the tasks, see Scheduler Tasks .
File System Repository in a ClusterIf after the installation of a cluster you plan to set up a file system repository, make sure that it is set to read only. The file system repository does not support simultaneous editing of files by multiple servers in a cluster.
The file system repository must point to one central share in a file system. That is, all Java instances must access one unified central share on the Java central instance.
More information: File System Repository Manager
A list of scheduler classes is displayed.
To assign a task to a system:
Some tasks like the Polling Scheduler Task are comprised of subtasks. Make sure that you select each subtask before assigning a CM system.
If you cannot find an appropriate time, you can add an entry to the Time Table under System Administration → System Configuration → Knowledge Management → Content Management →Global Services (Show Advanced Options) → Scheduler Time Table. Once you have created a new entry, it will be available for selection when you schedule a task.