Supported Platforms

CyberScheduler is available for Micorsoft Windows NT 4.x, Windows 2000, 2003, and Windows XP operating systems

Supported Web Browsers

Web browsers must support HTML version 2.0 or higher, and JavaScript capability is recommended. There are no hardware requirements or other special requirements except as specified by the browser manufacturer.

System Requirements

To use CyberScheduler, you must have both a CrossWind calendar server and CyberScheduler software installed. The following table describes the requirements for the servers that will host the CyberScheduler components.

Installation Overview

The installation process for CyberScheduler involves installing two integrated software applications, the CrossWind calendar server (formerly the "Synchronize server"), and the CyberScheduler user interface application. The procedures for installing these are described in this document.

The CyberScheduler application comprises two components. The "CyberScheduler Web component" is installed on the machine that hosts your Web server, and the "CyberScheduler agent" is installed with your CrossWind calendar server. If the same machine will host both your Web server and your CrossWind calendar server, then you will be able to install the calendar server and both CyberScheduler components at the same time. If the servers are on two different machines, then you must install the CyberScheduler agent on the machine that hosts the calendar server, and then install the CyberScheduler Web component separately on the other machine. You may wish to have your Webmaster install the CyberScheduler Web component for you if you do not have sufficient access to that host.

After installation, you must set up user accounts by adding a line to the users file for each user who will access CyberScheduler.

Installing the CyberScheduler Components

Once you have downloaded the necessary file(s), you will need to determine the sequence of installation. If you plan to install the CrossWind calendar server on the machine that hosts your Web server, then you can run the installation once on that machine to install all of the components. If you plan to install the components separately and/or on different machines, CrossWind recommends that you first install the calendar server (and associated CyberScheduler agent), then install the CyberScheduler Web component. When you run the installation, you choose which components to install. Links to instructions for installing the individual components are provided below:

Starting the installation program.

The installation procedure for CyberScheduler on Windows is executed through a standard graphical interface.

1. Start Windows and log on as an administrator (or a user with administrative privileges).



2. Download the current CyberScheduler self-extracting executable file from CrossWind’s FTP server, or locate the file on the media provided.



3. Double-click the file. (If you are running Windows NT 3.5, select the file from the Program Manager or File Manager, then pull down the File menu, select Run and click OK.) The file will self-extract and the installation process will begin.

The installation program will install the components you specify at the beginning of the installation process.

The service for the CrossWind calendar server can be stopped and started in the Services dialog box accessed from the Windows Control Panel. The server will be listed as "CrossWind Synchronize Server."

The installation procedure will also create a new key in your Windows registry under the pre-defined HKEY_LOCAL_MACHINE\SOFTWARE\ key. The new key will be created as CrossWind Technologies\Synchronize Server\Current Version\. Five value entries are created under this key:

• License: Your license string. You can modify/update your license by editing this entry.



• License Expiration Date: The date your CrossWind calendar server license expires.



• License User Maximum: The number of CyberScheduler users that can access the CrossWind calendar server.



• SYNCHROPATH: The installation location. The CrossWind calendar server for Windows uses the value of this entry to locate the database files.



• Version: The version of the currently installed software. You should not change the value of this entry.

The procedure for upgrading from a previous version of the CrossWind calendar server is similar to that for installing, with the following exceptions:

• The installation program will detect your existing installation and confirm your intent to upgrade.



• You will not be prompted to enter a license; rather it will use your existing one.



• You will not be prompted to specify the startup type for the service. Your previous setting will be used.

The CyberScheduler agent is installed on the same machine that hosts your CrossWind calendar server using the same installation program. The calendar server must already be installed before you install the CyberScheduler agent.

During the installation of the CyberScheduler agent, the following files will be installed:

• websyncd.exe - This is the CyberScheduler agent that is installed in the directory in which your CrossWind calendar server is located.



• websync.exe - This is the CyberScheduler Web component.



• CyberSchedRelNotes.txt, readme.txt - These are text files for the release notes and release contents/contact information, respectively. These documents are installed in the CyberSchedDocs directory within the directory in which your CrossWind calendar server is located (e.g., C:\CrossWind\CalendarServer\CyberSchedDocs).

1. If you have just installed the CrossWind calendar server on your machine and you are already running the installation program, proceed to Step 2.

• Your Web server's document root directory - This is the directory that contains all user-accessible Web documents on your Web server. For example, NCSA/Apache's document root might be located in server_root/htdocs. A Netscape Web server's document root can be determined via the Netscape Administration Server by locating the value of the "Primary Document Directory" under the "Content Mgmt|Primary Document Directory" screen. A Microsoft IIS Web Server’s document root can be determined by accessing your IIS Internet Service Manager.



• The HTML files installation directory - This is the directory on your Web server that will contain the CyberScheduler HTML files. The installation process will place a login.html file in this directory that corresponds to your choice of the English or German version of CyberScheduler.

• The CGI executables installation directory - Most Web server configurations have options that allow or deny execution of CGI executables based on their location or MIME type (i.e., filename suffix, such as .exe, .cgi or .pl). If your Web server configuration only allows CGI executables to reside in a particular directory, then you must specify that location during installation when asked for the location of the CyberScheduler CGI executable.

A CyberScheduler account with a login of "demo" is provided in the sample database shipped with CyberScheduler. If a user does not have an entry in users file, then the user can log in as "demo" to use a sample CyberScheduler calendar.

Once the CrossWind calendar server is installed, you should edit the 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. Entries should be added with the following format:

The above fields are defined as follows:

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:

Help on Microsoft IIS Web Server Configuration

Follow these instructions if you choose to create aliases on your Microsoft IIS Web Server:

1. To create an alias that corresponds to a document directory that CyberScheduler will use to store various resources:



1. Access your IIS Internet Service Manager. Highlight (i.e., click once on...) the Web Site that you’d like the CyberScheduler Web component to belong to. For example, you might highlight the "Default Web Site" that IIS automatically installs if you haven’t created a different one yet.



2. Click the "Action" button, and then point to "New," and select "Virtual Directory." This brings up the "New Virtual Directory Wizard."



3. Enter an alias for the document directory into which the CyberScheduler agent will install its html documents and resources. The alias can be essentially any name you choose; it’s merely a way to reference an actual directory. Click on "Next."



4. Now enter the physical path of the directory to which you want your alias to correspond. Write down the alias that you’ve created as well as the directory it’s associated with, as you’ll need both pieces of information when installing CyberScheduler.



5. Finally, click on "Next" again and make sure that the "Allow Read Access" permission is set, then click on "Finish."



2. To create an alias that corresponds to an application directory that CyberScheduler will use to store its CGI method:



1. Once again, access your IIS Internet Service Manager. Highlight (i.e., click once on...) the same Web Site that you highlighted in step 1a. above.



2. Again, click the "Action" button, and then point to "New," and select "Virtual Directory." This brings up the "New Virtual Directory Wizard" once again.



3. Enter an alias for the application directory into which the CyberScheduler agent will install its CGI method. As before, the alias can be essentially any name you choose. Click on "Next."



4. Enter the physical path of the directory to which you want your alias to correspond. As before, write down the alias that you’ve created as well as the directory it’s associated with, as you’ll also need those two pieces of information when installing CyberScheduler.



5. Finally, click on "Next" again. This time make sure that the "Allow Execute Access" permission is set, then click on "Finish."

Help On Netscape FastTrack Web Server Configuration

Follow these instructions if you choose to create aliases on your Netscape FastTrack Web Server:

1. To create an alias that corresponds to a document directory that CyberScheduler will use to store various resources:



1. Access your FastTrack Administrator Server. Under the "SERVERS SUPPORTING GENERAL ADMINISTRATION" heading, click on the gray button labeled with the appropriate server host name. Next click on "Content Management" and "Additional Document Directories." Map a URL prefix to a directory that you've already created. This URL prefix will be the "installation directory alias" that the CyberScheduler installation program refers to, so write it down! For example, if I have created a subdirectory called "CyberSched" under my Primary Document Directory "C:\Netscape\SuiteSpot\docs," then I would enter "CyberSched" in the "URL prefix" entry slot and "C:\Netscape\SuiteSpot\docs\CyberSched" in the "Map To Directory" slot. Click "OK."



2. Click "Save and Apply."



2. To create an alias that corresponds to an application directory that CyberScheduler will use to store its CGI method:



1. Again in your FastTrack Administrator Server, click on "Programs" and "CGI Directory" to map a URL prefix to a CGI directory where the CyberScheduler Web component will be located. This URL prefix will be the "CGI directory’s alias" to which the CyberScheduler installation program refers, so write it down, too! Continuing the example above, if I have created a subdirectory "cgi-bin" under my "C:\Netscape\Server" directory, then I would enter "cgi" in the "URL prefix" entry slot and "C:\Netscape\Server\cgi-bin" in the "CGI directory slot. Then click "OK."



2. Click "Save and Apply" as before.