Technical references : Installation : New installation : Post-installation : The Scheduler : Creating a Planon Software Suite account
Creating a Planon Software Suite account
A special user account in Planon Software Suite is used to find the corresponding accounts of users to be notified.
In Accounts > User Groups > Users, add a user as specified in the following table.
Field
Description
Name
SCHEDULERENGINEADMIN
* 
Use this exact name (case sensitive, without spaces). A special client on the application server – planonschedulerengine.ear - will use this user to look for users/accounts to be notified and to check alarms and notifications definitions.
Password
Enter a password - you are free to select you own password.
Start date
Specify the date as of which this account is allowed to log on to Planon Software Suite.
Property set
The scheduler is property-set-independent. The SCHEDULERENGINEADMIN account can switch property sets and work in multiple property sets simultaneously.
Time zone
In order to be able to analyze log files, this account must be in the same time zone as the server running the planonschedulerengine.ear.
The SCHEDULERENGINEADMIN account needs to be authorized to execute the tasks it is used for, e.g. Alerts, Connect for Outlook and so on. So if you use authorization, we advise to provide the Scheduler with all rights.
When using the application locking and the SCHEDULERENGINEADMIN is not linked to the Admin group, this user is also locked and cannot perform the appointed tasks (notification, alarms, synchronizing meeting requests etc).
In addition, make sure that the SCHEDULERENGINEADMIN account is linked to a user group to which the Scheduler product definition is assigned: Planon ProCenter Planned Services Scheduler.
* 
Keep in mind that when configuring the SCHEDULERENGINEADMIN account, the scheduler might already try to log on to the application, which might result in a locked account. The server log will display the locked account name. By default, accounts are locked for five minutes, but customers may use a different (longer) time window. The Scheduler however will not retry anymore, you need to restart the application server to make the scheduler login again.
For more information on the locking mechanism, see the chapter on Planon login module security (Administrator’s Guide).
After changing authorization for the SCHEDULERENGINEADMIN account, a cache refresh of the application server is required to make the scheduler aware of these changes.