|
|
| |||
![]()
© 1998 CrossWind Technologies,
LLC.
ACCESSING CYBERSCHEDULER CONFIGURING CYBERSCHEDULER Creating User Accounts Managing the Calendar Server and CyberScheduler Agent ADDITIONAL SUPPORT INFORMATION ![]() This guide describes basic configuration of CyberScheduler for Linux from CrossWind Technologies, Inc. It assumes that you have successfully installed CyberScheduler for Linux. If you need additional information regarding the administration of CyberScheduler, please visit CrossWind's online support pages at http://www.crosswind.com/cybsprt2.htm. CyberScheduler for Linux Web servers provides proven thin-client Web technology built on a real-time scheduling engine, bringing effective Internet scheduling to any size group or organization. With CyberScheduler, you can easily set up and deploy an efficient calendaring and scheduling solution for your entire workgroup within minutes. All users enjoy full calendar access through any familiar Internet Web browser, with no additional plug-ins or applications needed. Workgroup features include the ability to schedule meetings and resources, distribute agendas and memos, assign and track tasks, and send out reminders ... in short, everything your group needs to increase productivity and communication. The installation process for CyberScheduler installs two integrated software applications, the CrossWind calendar server (formerly the "Synchronize server"), and the CyberScheduler user interface application (which comprises the "CyberScheduler Web component" and the "CyberScheduler agent"). Both applications are installed on a Linux machine that hosts your Web server. If you've installed CyberScheduler from a tar file, you were allowed to choose the location where the CyberScheduler files were to be installed. For a Red Hat RPM installation, the CyberScheduler Web components are installed in /home/httpd/html/cybersched, with the exception of the cgi method (websync.cgi), which is located in /home/httpd/cgi-bin. For an RPM installation on S.u.S.E. linux, the CyberScheduler Web components are installed in /usr/local/httpd/htdocs, with the exception of the cgi method (websync.cgi), which is located in /usr/local/httpd/cgi-bin. Furthermore, a S.u.S.E. installation uses a symbolic link to access the websync.cgi, so your Apache web server must have symbolic links enabled. Please see Appendix A: Enabling Symbolic Links in Apache. For all installations, the CrossWind calendar server components are
installed in /usr/local/lib/synchronize. An RPM or tar installation
of CyberScheduler will never remove or overwrite an existing CyberScheduler
database, which simplifies the software upgrade process.
ACCESSING CYBERSCHEDULERThis release of CyberScheduler is capable of displaying in either English or German. If the CyberScheduler Web component was installed in a subdirectory called cybersched within the Web server document root (an RPM installation ensures this), to login to CyberScheduler use the HREF: http://localhost/cybersched/login.html. The RPM installation default language is English; the tar installation gives you the freedom to choose either English or German. If you have an English installation but would like to access a German CyberScheduler, use the HREF: http://localhost/cybersched/De/login.html. Similarly, if you have a German installation but would like to access an English CyberScheduler, use the HREF: http://localhost/cybersched/En_US/login.html. Note that in the above examples, remote users should replace "localhost" with the name of the machine that hosts the calendar server.See the Setting Preferences in the login.html
File section for differences between the two versions, besides
the obvious language difference.
If you install CyberScheduler from a tar file, during the installation you will be prompted to enter a user license. However, if you install CyberScheduler from an RPM package, you must apply your CyberScheduler user license to the database after installation. In either case, you'll want to set up user accounts by adding a line to the users file for each user who will access CyberScheduler. You may also choose to configure the additional features listed below.
Applying a License to CyberSchedulerWhen CyberScheduler is installed from a tar file, you are prompted by the installation script for a user license. When CyberScheduler is installed as a RPM package, either a zero-user license or a single-user license is enabled. If a single-user license is installed, users can log in to CyberScheduler as "demo" to evaluate the software. If a zero-user license is installed, the following message will be displayed when users attempt to log in to CyberScheduler:The installed license supports zero users. Please perform a license upgrade. The number of licensed users at a site may be upgraded at any time. This applies to both tar file installations and RPM package installations. Simply contact your CyberScheduler supplier or CrossWind Technologies. A new license can be faxed, e-mailed, or communicated to you over the phone. No re-installation of the software is necessary. The licensing mechanism in CyberScheduler is a static one. If you have an N-user license for your database, then the first N users in the db/users file will be able to use CyberScheduler. The N+1st user will get a complaint from CyberScheduler and the application will then exit. To apply a new license, change directories to /usr/local/lib/synchronize and type the following command (Note: you may need to first set the SYNCHROPATH environment variable to /usr/local/lib/synchronize): linux/bin/synchrod -newLicense license_string If you get the response "Success!", your new license has been installed correctly and will take effect after you stop and restart the calendar server and the CyberScheduler agent (see the sections below about stopping and starting the server and agent). If not, contact your CyberScheduler supplier or CrossWind Technologies. Creating User AccountsA CyberScheduler account with a login of "demo" is provided in the sample database shipped with CyberScheduler. Once you have applied an N-user license, you must edit the usr/local/lib/synchronize/db/users file with a text editor and enter the names of the users who will be using CyberScheduler. User names can be entered in any order and sorted by the Administrator for convenience. The order in which names appear in the users file is the order in which they will be presented to users.Changes to the users file may not take effect immediately since the server updates its state at preset intervals. To force the server to update its state, stop and restart the calendar server and the CyberScheduler agent as described in Managing the Calendar Server and CyberScheduler Agent. Entries to the users file should be added with the following format: CyberScheduler_name +Larry,lsmith,lsmith@mantle, Rhonda, rjones, , Rhonda Jones "Karlsen, Jim", jkarlsen,,Jim Joseph, joe,, Joe Conference Room A, , , Slide Projector Managing the Calendar Server and CyberScheduler Agent
In the directory /etc/rc.d/init.d (or, if you're using Slackware
Linux, in the directory /etc/rc.d), you'll find a shell script called
cybersched. It can be used to start, stop, and restart the CrossWind
calendar server and CyberScheduler agent in the following ways:
Stopping the CrossWind Calendar Server and CyberScheduler Agent
Restarting the CrossWind Calendar Server and CyberScheduler Agent
Setting Preferences in the login.html FileThe login.html file contains four "hidden variables" that control how CyberScheduler is presented to users. The default values for these variables are dependent on the selected language, and may be changed to globally reflect the users' preferences. Edit the login.html file using any text editor.ADDITIONAL SUPPORT INFORMATION For additional support and administration documentation, visit the CyberScheduler Technical Support web site at http://www.crosswind.com/cybsprt2.htm. You'll find helpful system administration information including these topics: APPENDIX A: ENABLING SYMBOLIC LINKS IN APACHE An RPM installation on S.u.S.E. linux uses a symbolic link to access the websync.cgi, so your Apache web server must have symbolic links enabled. Use a text editor to modify /etc/httpd/access.conf so that the Options field below the "<Directory /usr/local/httpd/cgi-bin>" header is set to "FollowSymLinks." Below is an example entry in an access.conf file: <Directory /usr/local/httpd/cgi-bin>
|