CM4D Scheduler must be configured in several areas with multiple users and logins, all requiring different levels of permissions. These areas include:
3. Service User - CM4D Scheduler Settings File
4. Job User(s) - CM4D Scheduler Settings File
5. Service User - CM4D Launcher Settings File
6. CM4D Scheduler Manager User
Although you may choose to use the same user to run all of these, you may also choose more complex combinations of several users depending on the number of servers and how you want to load-balance your Scheduler Jobs. Some of these users are actual Windows Logins, while others only need to exist as CM4D Site Database users.
The following sections detail the requirements of each area to help you to determine which type of user should be used in each instance.
The CM4D Scheduler Service User is the user logged in to the CM4D Scheduler Service. The Scheduler Service connects CM4D Scheduler to the database and assigns jobs to users throughout the system. The user that runs this service is managed at a Windows Administration level.
· Must be a Windows User
· Must have network Share access.
· Must have WRITE access to the Log folder (see the topic Scheduler Folders for more information)
· Must be able to connect to the CM4D Database.
· Must have the Scheduler User Privilege in SiteManager.
· Recommended that the user have Windows Administrator privileges.
· If using Windows Authentication, this user must also added as a user in the SQL Server CM4D database(s).
The CM4D Launcher Service User is the user logged in to the CM4D Launcher Service. The Launcher Service is the service used by the Scheduler Service to run (or "launch") the instances of CM4D that will be used to open documents and print reports. The user that runs this service is managed at a Windows Administration level. The privileges provided to this user by Windows determines the user's access to the rest of the CM4D automation system.
· Must be a Windows User
· Must be able to connect to the CM4D Database
· Must have the Scheduler User Privilege in SiteManager
· Must have READ access to the CM4D Managed Document used to run the job
· Must have READ access to the image file used by the Managed Document
· Must have WRITE access to the Depository that the report(s) will be written to
· Must have WRITE access to the local Scratch folder (see the topic Scheduler Folders for more information)
· If using Windows Authentication, this user must also added as a user in the SQL Server CM4D database(s)
The Service User in the Scheduler Settings file is the user that grants the CM4D Scheduler Service access to the CM4D Site Database.
· Must be able to connect to the CM4D Database
· Must have the Scheduler User privilege in SiteManager
· Does not have to be a Windows User
The Job User is the user that is assigned to run Scheduled jobs, and is the user that uses the CM4D clients started by Launcher to print the reports. There can be more than one job user; add additional lines as needed.
· Must be able to connect to the CM4D Database
· Must have the Scheduler User privilege in SiteManager
· Does not have to be a Windows User
· Can run jobs using any Scheduler Service that is being run by any Service User
The Service User in the Launcher Settings file is the user that grants the CM4D Launcher Service access to the CM4D Site Database.
· Must be able to connect to the CM4D Database
· Must have the Scheduler User privilege in SiteManager
· Does not have to be a Windows User
A Scheduler Manager user is the user who runs the CM4D Scheduler Manager application interface. This user must have Scheduler Manager privilege in Site Manager.
· Must be a logged on Windows User
· Must be able to connect to the CM4D Database
· If using Windows Authentication, this user must also added as a user in the SQL database
· Must have the Scheduler Manager privilege in SiteManager
A user with the Scheduler Manager privilege does not automatically have the Scheduler User privilege. If that user will also be used to run Services or Jobs, they will also need to be assigned the Scheduler User privilege.