Calendaring and Scheduling Software
   calendaring and scheduling software scheduling software   support for calendaring and scheduling software  Force Accounting FAQs demo calendaring and scheduling  software purchase calendaring and scheduling software sitemap for calendaring and scheduling software




for Linux

 

 

Configuration Guide
CyberScheduler 2.1 for Linux

 

 

 

 

 

 

 

 

CrossWind Technologies, LLC.
http://www.crosswind.com

 

 

 

 

 

 

© 1998 CrossWind Technologies, LLC.
CyberScheduler and Synchronize are trademarks of CrossWind Technologies, LLC.
All other brand and product names are either trademarks or registered trademarks of their respective companies.
Rev. 6/98.11

 

Table of Contents

 

INTRODUCTION
ACCESSING CYBERSCHEDULER
CONFIGURING CYBERSCHEDULER Applying a License to CyberScheduler
Creating User Accounts
Managing the Calendar Server and CyberScheduler Agent Starting the CrossWind Calendar Server and CyberScheduler Agent Stopping the CrossWind Calendar Server and CyberScheduler Agent Restarting the CrossWind Calendar Server and CyberScheduler Agent Setting Preferences in the login.html File
ADDITIONAL SUPPORT INFORMATION
CyberScheduler Technical Support: http://www.crosswind.com/cybsprt2.htm APPENDIX A: ENABLING SYMBOLIC LINKS IN APACHE  
 



for Linux
Configuration Guide
 
INTRODUCTION

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 CYBERSCHEDULER

This 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.
 
CONFIGURING CYBERSCHEDULER

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.

Please go to the CyberScheduler online support pages at http://www.crosswind.com/cybsprt2.htm for details about even more CyberScheduler configuration and administration topics listed in the Additional Support Information section at the end of this document.

Applying a License to CyberScheduler

When 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 Accounts

A 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, login_name, e-mail_address, CyberScheduler_alias The above fields are defined as follows:

CyberScheduler_name

This field is the user's CyberScheduler name. It is mandatory and must also be unique within the database. Once entered and used, this field must never change. If it changes, CyberScheduler will not be able to find the calendar items for that user and all entries for that user will have been lost. Use the optional CyberScheduler_alias field (see below) to change a CyberScheduler user's name once it has been established. login_name For all CyberScheduler users this field must contain the user's login name and should be unique within the local database. It can be changed at any time to reflect a new login. This field must be left blank for "non-human" resources like conference rooms. e-mail_address This field is optional, and is used to designate an e-mail address for the user. If this field is omitted, then the login_name will be used by default as the e-mail address. This field is typically necessary when the e-mail system needs more information than just the login_name to route e-mail correctly. Upon installation, e-mail notification is not enabled. For more information about configuring e-mail, please be sure to see the "E-Mail" section of the online support pages at http://www.crosswind.com/cybsprt2.htm. CyberScheduler_alias This field is optional, and determines how the user's name will be displayed within CyberScheduler. If this field is omitted, then the CyberScheduler_name is used by default. This field can be used or modified, for example, when a user's name changes due to marriage. To avoid confusion, it is suggested that you not use a name that conflicts with another local CyberScheduler_name or CyberScheduler_alias, although this is not strictly required. Commas must separate fields, including blank fields. Any extra white space before or after a comma is optional and will be ignored. If a particular field contains a comma, then you must surround the entire field with double quotation marks so that the comma will not be interpreted as a field separator. You should take care to hit Return or Enter at the end of the last line in the file. Most of the time it will not be a problem, but some text editors fail to automatically include an end-of-line character before the end-of-file, thereby causing the last line to be ignored. Here is an example of entries in the db/users file: Joe, jclark, , Joey
+Larry,lsmith,lsmith@mantle,
Rhonda, rjones, , Rhonda Jones
"Karlsen, Jim", jkarlsen,,Jim
Joseph, joe,, Joe
Conference Room A, , ,
Slide Projector
Note: The leading "+" for Larry indicates that he is a CyberScheduler administrator. See the Additional Support Information section below for instructions to get more information about CyberScheduler administrators.
 

Managing the Calendar Server and CyberScheduler Agent

Both the RPM and tar installation process starts the calendar server (synchrod) and the CyberScheduler agent (websyncd) automatically. The following instructions are provided should you need to manually start and stop them.

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:
 

Starting the CrossWind Calendar Server and CyberScheduler Agent
  • To start the CrossWind calendar server and CyberScheduler agent, enter
  • sh ./cybersched start
    This will start the processes for both the CrossWind calendar server and the CyberScheduler agent.
     
    Stopping the CrossWind Calendar Server and CyberScheduler Agent
  • To stop the CrossWind calendar server and CyberScheduler agent, enter
  • sh ./cybersched stop
    This will stop the processes for both the CrossWind calendar server and the CyberScheduler agent.
     
    Restarting the CrossWind Calendar Server and CyberScheduler Agent
  • To restart the CrossWind calendar server and CyberScheduler agent, enter
  • sh ./cybersched restart
    This will first stop and then start the processes for both the CrossWind calendar server and the CyberScheduler agent.

    Setting Preferences in the login.html File

    The 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.
  • "dow" - The setting of this variable determines the first calendar day of the week. The default for this variable is "sun" (Sunday) in the English login.html, and "mon" (Monday) in the German login.html.
  • "dmy" - If set to "On", dates will be displayed in the dd/mm/yy format; if set to "Off", dates will be displayed in the mm/dd/yy format. The default for this variable is "Off" in the English login.html and "On" in the German login.html.
  • "tfh" - If set to "On", time will be displayed as 0:00 to 23:59; if set to "Off", time will be displayed as 12:00am to 11:59pm. The default for this variable is "Off" in the English login.html and "On" in the German login.html.
  • "lan" - This variable determines the language displayed. The default for this variable is "En_US" in the English login.html and "De" in the German login.html.
  •  

    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:

  • Designating Non-Human Resources (such as conference rooms and equipment)
  • User Account Administration
  • Designating a CyberScheduler Administrator
  • CyberScheduler Passwords
  • Obtaining License Information
  • Hierarchical User Groups
  • Editing the Holidays File
  • E-mail Administration
  • Database Maintenance
  •  

    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>
    AllowOverride None
    Options FollowSymLinks
    </Directory>






    BACK