|
|
 
 | |||
Users and Groups Designating Non-Human Resources Modifying User Accounts Disabling User Accounts Deleting User Accounts Designating a CyberScheduler Administrator CyberScheduler Passwords Hierarchical User Groups Database Administration
Calendar Server Configuration
Users and Groups Designating Non-Human Resources Resources such as conference rooms and slide projectors can be listed in the db\users file. Users running CyberScheduler can then specify not only which users they would like to attend a meeting, but what resources they would like to reserve as well. Note that resource entries do not include a login_name. These entries are designated by the lack of a login_name. They are treated by CyberScheduler in much the same manner as other users, with the following exceptions:
Modifying User Accounts There will commonly be times when a user’s entry in db/users must be modified. Any of the last three fields for an entry can be modified without loss of data for that account. Please remember, the first field for a user’s entry CyberScheduler_name must not be changed unless you wish to remove the data for the original entry. For example, if a user changes his or her name, or is replaced by a different person, this change can be applied to the CyberScheduler_alias field in that user’s entry. If a user’s login_name must be changed, simply change that field. The e-mail_address field can be also be changed in this fashion. If you need to have a new user inherit data from another user’s calendar, consider simply changing all fields except the CyberScheduler_name. Disabling User Accounts You can disable a CyberScheduler account without removing the calendar data associated with it. You can use any of the following techniques depending on your needs:
Deleting User Accounts To delete a user account, you can either remove the user’s entry from the db\users file or change the CyberScheduler_name field. Please note: Deleting an account will automatically delete all calendar items originated by that user and removes that user from the invitee list of all calendar items to which he/she was invited. Extreme caution should be used when performing this type of maintenance. Designating a CyberScheduler Administrator CyberScheduler administrators can be designated by an optional "+" entered
just before the CyberScheduler_name (see example above). The "+"
is not part of the user’s name. One or more administrators may be designated
for a database. Administrative capabilities apply only to the local database,
not to remote ones. Administrators have the following capabilities:
CyberScheduler Passwords In some cases, it may be necessary to reset a password if, for example, a user forgets his or her password. To reset a password, the user’s password entry must be deleted from the db\database\userinfo file. There may be more than one line corresponding to the same user in this file. Only the line containing the encrypted password entry should be deleted. The entire line must be deleted. Hierarchical User Groups As the number of CyberScheduler users grows, a linear set of names becomes insufficient to allow quick access to users. To deal with this issue, the ability to display a hierarchy of user groups is provided. The db\groups subdirectory can contain files and directories that define the group structure. Files are used to designate group names and directories are used to designate group hierarchies. Group names must be unique within a particular database. This applies to both file and directory names. For example, you cannot have a group named "staff" under both Engineering and Administration (rather you could use "Engineering_staff" and "Administrative_staff"). Behavior is unpredictable if this rule is not met. The following example shows a possible layout for a groups hierarchy under db\groups: Building-1 (subdirectory)
A group file lists either the CyberScheduler_alias or CyberScheduler_name of users in the group, one per line. For example, consider the following lines from a db\users file: Joe, jclark, , Joey
If Joe, Jim and Rhonda work in the Manufacturing group in Building-1, then the file db\groups\Building-1\Manufacturing might contain the following entries: Joe
Note that it is not necessary to surround Jim’s name by double quotation marks as in the users file. Also note that a group file entry will always refer to a matching CyberScheduler_alias before a matching CyberScheduler_name. For example, "Joe" in the above group file refers to the user whose login is "joe", not "jclark".
Database Administration Backing Up the Database CrossWind recommends that you back up your CyberScheduler database on a daily basis. Only the db subdirectory and its contents need to be backed up. Under Windows, any backup software can be used including the built-in system backup facility. Whichever tool you decide to use, make sure that it saves all files and directories including empty directories and zero-length files. You do not need to stop the calendar server when backing up the database. When deciding what time the backup should occur, keep in mind that the calendar server propagates unfinished to-dos to the next day around midnight. The amount of time required to do this depends on the size of the database and the speed of your system. For this reason, when scheduling your backup, it’s probably a good idea to avoid the time between 12:00 a.m. and 1:00 a.m. Restoring the Database A full restore will reset the state of the database to the time of the last backup. When performing a full restore, you should carefully follow these steps:
Configuring E-mail Delivery If your mail server is on a different machine than your calendar server,
use a text editor to add a line to your calendar server's db\database\server\server.opts
file that reads
Enabling/Disabling E-mail Notification During the installation of CyberScheduler for Windows, you have the opportunity to enable e-mail notification for all users. In order to enable e-mail notification after installation you must edit the db\database\notify.mail file (create it first, if it does not already exist) to contain the following single line: #R (tab) _ _ALL_ _ ( Note: two underbars with no spaces between them, before and after the ALL.) To disable e-mail notification for all users, remove the above line, or simply rename the db\database\notify.mail file to db\database\notify.mail.sav. During the CyberScheduler installation, a sample holidays file is installed as db\database\holidays. This file is used by CyberScheduler to display holiday names on each user’s calendar. The sample file includes entries for common holidays in the United States. Using any text editor such as Notepad or WordPad, you can edit the holidays file to contain the holidays that are appropriate for your CyberScheduler users. The format of the holidays file is: holiday_name*{workday|nonworkday}:(tab) start_date - end_date We recommend that you maintain your holidays in chronological order, with a blank line separating each year. Some entry examples from the file are: Christmas Eve*workday: 12/24/1998
- 12/24/1998
New Year’s Day*nonworkday: 1/1/1999 - 1/1/1999
Notice that the date format is M/D/YYYY. Holidays that are designated as “nonworkday” are seen as time that is not free to anyone who uses “Find Free Time” when scheduling a meeting on CyberScheduler. After installation, you can determine the amount of users your CyberScheduler license supports by using any text editor to view db\database\server\server.log. Under the heading "License information" you will see the number of users supported. Following is an example server.log entry that shows support for 5 users: License information:
|
