Use the Server Manager to configure the Scheduling Server on each machine where it is installed. Each machine can then run time-based activities (such as backups, database maintenance, data imports, etc.) that have been previously set up. When configuring the Scheduling Server, define:
To configure the Scheduling Server:
The Scheduling Server Configuration window opens.
Note: To use this feature, Windows must be a supported login mode (Open CSM Administrator>Security>Edit security settings, select the Desktop Client, Browser Client, or Browser Portal, and in the Supported login modes section, select Windows). This CSM Server logs in to CSM using the account associated with the Windows credentials used by the Windows server.
Note: This is usually an administrative account with broad system access, such as CSDAdmin.
Note: When this setting is not selected, this CSM Server uses a system default Role. However, control the behavior of Field properties in a View, based on the Role of the logged in User, by making this selection. In other words, based on a custom View for the Role of the person logging in (ex: IT Manager), the behavior of the Fields for a Business Object can be different when a record is created or modified.
The Choose Schedule Group window opens.
Note: The actions for scheduled items are selected and configured in CSM Administrator (CSM Administrator>Scheduling>Edit Schedule). Most Users will use the (Default) group, however if additional items need to be run at different times or for different purposes, these can be placed in separate groups, and run by different servers (ex: A SaaS customer may need to import Users into Active Directory at their company, which cannot be done in the SaaS environment. They could use one scheduling server to import to Active Directory at the company, and another SaaS scheduling server to run Default actions).
Important: A single Scheduling Server will only run scheduled events for a single group. Normally, this will be the (Default) group, unless multiple services are configured.
Note: There are two different methods that allow the service to be stopped. The first is to actually stop the service from running in the Service control panel applet, or by using the Stop button in the Server Manager. While this works, it requires direct access to the machine/image on which the service is running.
The second method is to pause/resume processing. This can be done from the CSM Administrator by any user with sufficient security rights. In this case, the service is still running, but it will not process any records. The advantage of this approach is that it does not require access to the machine/image on which the service is running.
For items to be processed, the service must be running, and must not be paused. You can resume processing from the CSM Administrator, or as a convenience, from the Pause/Resume Processing button in the Server Manager.