CorporateTime Server 5.4 Readme

CorporateTime Server 5.4

and

LDAP Connector 1.5 for Critical Path InJoin Directory Server

LDAP Connector 1.5 for Syntegra Global Directory Server

LDAP Connector 1.5 for Netscape Directory Server

LDAP Connector 1.5 for iPlanet Directory Server

This file was last modified 2002-08-12

Thank you for choosing CorporateTime Server. This file contains installation instructions only. Please see the CorporateTime Server Administrator's Guide and Reference Manual for information about configuring, administering and maintaining your calendar server. PDF versions of these manuals are also available (Administrator's Guide | Reference Manual). Please see the release notes for supported platforms, system requirements, a list of included features and a description of known problems.

This product can be used with an internal directory or an external LDAP directory server. Support for the Lightweight Directory Access Protocol (LDAP) is offered through separate connectors: LDAP Connector 1.5 for Critical Path InJoin Directory Server (formerly ISOCOR Global Directory Server), LDAP Connector 1.5 for Syntegra Global Directory Server (formerly Control Data Systems Global Directory Server), LDAP Connector 1.5 for Netscape Directory Server, and LDAP Connector 1.5 for iPlanet Directory Server. If you already use an LDAP Connector of version 1.3, no manual upgrade procedure is necessary.

Contents of this README file

How to report problems
Before you install CorporateTime Server

CorporateTime Server with internal directory

Installing CorporateTime Server with internal directory
Uninstalling CorporateTime Server with internal directory

CorporateTime Server with external LDAP directory server

Preparing your directory server

Critical Path InJoin Directory Server (formerly ISOCOR Global Directory Server)
Syntegra Directory Server (formerly Control Data Global Directory Server)
Netscape Directory Server
iPlanet Directory Server

Installing CorporateTime Server with LDAP Connector
Directory Server terminology
Uninstalling CorporateTime Server with LDAP Connector

If your demo license has expired

CorporateTime Server Administrator (Windows NT Administration GUI)

Calendar Administrator (Web administration interface)

How to report problems

Please contact Oracle's technical support department at support@steltor.com or call (514) 733-8500.

Before you install CorporateTime Server

Before you install your calendar server, ensure that:

You have your server's root password or you have root privileges.
Your server has at least 64 MB of RAM.
Your server has at least 150 MB of free space on the hard drive during installation.
You have removed any extraneous files and subdirectories from the /users/unison/bin directory and any modified reminder files from /users/unison/etc/reminder, as these directories will be overwritten during the installation.

NOTE: Refer to Chapter 2, "Deployment," and Appendices A ("Disk Space and Memory") and B ("Sizing Guidelines") in the CorporateTime Server Administrator's Guide for more detailed instructions on estimating the anticipated calendar server usage within your organization.

NOTE: CorporateTime Server must run as root or unison.

Installing CorporateTime Server with internal directory

Setup:

Open the calendar server package file in a staging directory.

UNIX

Login as root or as a user with root privileges.
Create a UNIX group account called dxoffice.
Create a UNIX user account called unison in the group dxoffice.
Edit /etc/services to include the following entries:
unieng 5730/tcp
unisnc 5731/tcp

NOTE: If using a centralized information service such as NIS, please refer to the operating system documentation for instructions on adding these services.

Run the installation script:
./unisetup
If you are upgrading from a previous version of CorporateTime Server, the presence of a /users/unison directory will be detected. Your old configuration settings (those in /users/unison/misc/unison.ini) will be merged with the new unison.ini and /users/unison/db archived and restored upon installation of the new server. Obsolete parameters will be removed. Other rarely used parameters may also be removed if their values have been left unchanged. This is done in order to simplify the unison.ini file and make it easier to maintain by displaying only those parameters you may need to tune.
For a fresh install you will be prompted to:

enter a new license or accept the default
select a time zone
set the maximum number of concurrent users
enable or disable mail notification
select a node-ID and alias for the creation of a calendar node

Consult the release notes for any additional patches or enhancement packs that may be required.
Refer to the Administrator's Guide for more information concerning the configuration of the calendar server (time zone, logged-on user limit, mail notification, etc.).

See the on-line Administrator's Guide for full configuration, use and maintenance instructions.

NT

Run the CorporateTime Server self-extracting executable and follow the instructions on the screen.

If you are upgrading from a previous version of CorporateTime Server, the presence of a \users\unison directory will be detected. Your old configuration settings (those in \users\unison\misc\unison.ini) will be merged with the new unison.ini and \users\unison\db archived and restored upon installation of the new server. Obsolete parameters will be removed. Other rarely used parameters may also be removed if their values have been left unchanged. This is done in order to simplify the unison.ini file and make it easier to maintain by displaying only those parameters you may need to tune.

For a fresh install you will be prompted to:

enter a new license or accept the default
select a time zone
set the maximum number of concurrent users
enable or disable mail notification
select a node-ID and alias for the creation of a CorporateTime node

Consult the release notes for any additional patches or enhancement packs that may be required.
Refer to the Administrator's Guide for more information concerning the configuration of the calendar server (time zone, logged-on user limit, mail notification, etc.).

See the on-line Administrator's Guide for full configuration, use and maintenance instructions.

Uninstalling CorporateTime Server with internal directory

UNIX

Stop the calendar server using the unistop utility.
Delete the <calendar server path>.
Delete the /users directory.
Remove the UNIX user account unison.
Remove the UNIX group account dxoffice.
Remove the unieng and unisnc entries from /etc/services.

NT

Select Start | Settings | Control Panel | Add/Remove Programs, select CorporateTime Server, and follow the operating system instructions.

If you are unable to remove your calendar server using the method above, complete the following

procedure:

Stop the calendar server using one of the following methods:

Select Services | Properties... from the CorporateTime Server Administrator and follow the on-line instructions;
Select Start | Settings | Control Panel | Services to open the service control tool provided with the operating system;
Use the unistop utility.

Remove the \users\unison directory.
Using regedit, find and remove the entry under

HKEY_LOCAL_MACHINE/SOFTWARE/Oracle/calendar server/CurrentVersion

Reboot.

Preparing your directory server

Critical Path InJoin Directory Server (formerly ISOCOR Global Directory Server)

Note: the home directory of the InJoin Directory Server is assumed to be /usr/x500ds in the following instructions. If you have installed the product to another directory, adjust the absolute path for the InJoin files accordingly.

Unpack the contents of the LDAP Connector package file in a staging directory. The directory should contain the following files:
corptime_acsp
corptime_admin_aci
corptime_default_aci
corptime_esp
corptime_esp_acsp
corptime_local
corptime_macros
corptime_schema
ct-oidnames.cfg
ct-oidtable.at
ct-oidtable.gen
ct-oidtable.oc
ct-x500web.at
ct-oidslocal
Copy the following calendar server configuration files to the targeted directories:
ct-oidslocal to /usr/x500ds/scripts
ct-oidnames.cfg to /usr/x500ds/scripts
ct-oidtable.gen to /usr/x500ds/ldap/etc
ct-oidtable.at to /usr/x500ds/ldap/etc
ct-oidtable.oc to /usr/x500ds/ldap/etc
ct-x500web.at to /usr/x500ds/wg
Append ct-oidnames.cfg to /usr/x500ds/scripts/db/oidnames.cfg. Insert "CorporateTime" immediately before "MISCELLANEOUS" in the OidOrder key [Settings] section. Also, if this file is duplicated under /usr/x500ds/ldap/etc and the ~/dib directory, these files should also be updated.
Make the calendar server attributes known to odsadmin & odsdua:

append ct-oidslocal to /usr/x500ds/scripts/oidslocal

Make the calendar server prefixes known to the Directory Server:

append ct-oidtable.gen to /usr/x500ds/ldap/etc/oidtable.gen

Make the calendar server attributes known to the Directory Server:

append ct-oidtable.at to /usr/x500ds/ldap/etc/oidtable.at

Make the calendar server object classes known to the Directory Server:

append ct-oidtable.oc to /usr/x500ds/ldap/etc/oidtable.oc

Make the calendar server attributes known to the ISOCOR web interface:

append ct-x500web.at to /usr/x500ds/wg/x500web.at

Bring the Directory Server down and back up again. (During InJoin DS installation, a default DSA is generated in ~/dib directory, see dib/odsgen.inf for pertinent information. If your DSA is in dib0, then adjust the commands below accordingly.)
su - dsamgr
cd dib
odsstop
odsstart
Ensure that no errors occurred:
odselog -a
Copy the following calendar server command files to your DSA directory (~/dib)
corptime_acsp
corptime_admin_aci
corptime_default_aci
corptime_esp
corptime_esp_acsp
corptime_local
corptime_macros
corptime_schema
Add the calendar server schema to the Directory Server:
Edit the file corptime_local to insert the required Directory Server parameters for your installation
Start the ISOCOR GDS command line shell:
odsadmin
Bind as the Directory Server manager
bman

NOTE: if your manager or password is not the default you should use:
admin> bind -n N(Rcn(<SuperUserDN>)) -p <SuperUserDN password>

Apply the calendar server schema definition to the Directory Server. Note that the '~' causes the command file to be processed without prompting.
admin> run corptime_schema ~
Initialize the Directory Server (OPTIONAL - some steps may be skipped if your site is already set up)

Create an Entry Starting Point (ESP) if none has been initialized. An Access Control Specific Point (ACSP) will also be created:
admin> run corptime_esp_acsp ~

or

If an ESP exists without an ACSP, create an ACSP only:
admin> run corptime_acsp ~

If the default Access Control Information (ACI) has not been initialized, this command file will set ACI to permit anonymous read only access and to allow authenticated users the right to modify their own entry. Be aware of how this will modify your Directory Server's security. For more information on the default ACIs used by the calendar server, please see the Calendar Server Access Control Requirements.
admin> run corptime_default_aci ~

Create the CorporateTime SYSOPs ACIs
admin> run corptime_admin_aci ~
Type "." (a period) to quit the GDS command line shell
admin> .
To verify your success, enter the following URL in a browser to display the entries under the BaseDN:
ldap://<directory server host>:<odsldap port>/<base DN>??sub

Upgrading from pre-1.3 versions of the LDAP connector:
Copy the new ct-oidnames.cfg to <Installation directory>/scripts/db
Open the file ct-oidnames.cfg
Edit the file <Installation directory>/scripts/db/oidnames.cfg. Replace the calendar server section with the content of ct-oidnames.cfg
The beginning of the calendar server section is marked by:
############################################################ 
# @ (#) Id: <filename>  .... 
############################################################ 
The end of the calendar server section is marked by:
# End of file `<filename>'
Copy the new ct-oidnames.cfg to every working directory of the directory server instance (DIB, DIB0, DIB1, ...) and to <Installation directory>/ldap/etc

Edit the file oidnames.cfg
Follow the same procedure described in step 1 for oidnames.cfg

Copy the new ct-oidslocal to <Installation directory>/scripts

Edit the file <Installation directory>/scripts/oidslocal
Follow the same procedure described in step 1 for oidslocal

Copy the new ct-oidtable.at to <Installation directory>/ldap/etc

Edit the file <Installation directory>/ldap/etc/oidtable.at
Follow the same procedure described in step 1 for oidtable.at

Copy the new ct-oidtable.oc to <Installation directory>/ldap/etc

Edit the file <Installation directory>/ldap/etc/oidtable.oc
Follow the same procedure described in step 1 for oidtable.oc

Copy the new ct-x500web.at to <Installation directory>/wg

Edit the file <Installation directory>/wg/x500web.at
Follow the same procedure described in step 1 for x500web.at

Copy the file corptime_schema to every working directory of the directory server instance (DIB, DIB0, DIB1, ...). For each instance:

Run odsadmin
Bind as directory manager by typing bman, or if the manager and password is not the default, by typing bind -n N(rcn(<SuperUserDN>)) -p <password>
Run corptime_schema ~
Type "." alone to quit. Some errors will be reported. This is expected; the errors are caused by adding existing atttibutes to the directory server
Run odsstop and odsstart to restart the directory server.

Apply the schema changes through the navigator. The following steps must be completed for each instance of the directory server.

Login as the directory server manager.
Select the Administration | Schema menu.
Select the "Defined Attributes" tab and make sure that ctCalPublishedType is in the list of attributes.
Select the "Object Classes" tab.
Double click the "ctCalUser" object class.You should be in the "Configure Object Class" window.
Select the right pane: "May Contain these attributes".
Click the Add button.
Select "ctCalPublishedType" and "ctCalSMSTimeRange" from the list of attributes.
Click OK repeatedly until you see the "Configure Schema" window.
Select the check box "Synchronize local schema on OK".
Click OK repeatedly until all dialog boxes are closed.
Exit the navigator application (critical step).
Run the navigator application and follow the above steps for other instances.
Syntegra Directory Server (formerly Control Data Global Directory Server)

( UNIX | NT )

UNIX

Login as root or as a user with root privileges.
Create a UNIX group account called dxoffice with an ID of less than 60000.
Create a UNIX user account called unison with an ID of more than 100 and less than 60000 in the group dxoffice.
Edit /etc/services to include the following entries:

unieng 5730/tcp
unisnc 5731/tcp
unidas 5732/tcp
NOTE: If using a centralized information service such as NIS, please refer to the operating system documentation for instructions on adding these services.

Untar the contents of the LDAP Connector package file to a temporary directory (hereafter referred to as <Temp Directory>).
The directory should contain:
cds/oidtable.gen_cst
cds/oidtable.oc_cst
cds/oidtable.at_cst
To prepare the directory server, you will need to install files to configure ctCal directory objects.

Append the content of the following files (containing the calendar server schema's object identifier numbers, the object classes and the attributes):
<Temp Directory>/cds/oidtable.gen_cst
<Temp Directory>/cds/oidtable.oc_cst
<Temp Directory>/cds/oidtable.at_cst
to the corresponding OID (object identifier) table files:
/usr/var/osi/oidtable.gen
/usr/var/osi/oidtable.oc
/usr/var/osi/oidtable.at

Restart the directory server to allow the configuration changes to take effect.

NT

Login as a user with administrator privileges.
Extract the contents of the LDAP Connector package file to a temporary directory (hereafter referred to as <Temp Directory>).
The directory should contain:
oidtable.gen_cst
oidtable.oc_cst
oidtable.at_cst
To prepare the directory server, you will need to install files to configure ctCal directory objects.

Append the content of the following files (containing the calendar server schema's object identifier numbers, the object classes and the attributes):
<Temp Directory>\oidtable.gen_cst
<Temp Directory>\oidtable.oc_cst
<Temp Directory>\oidtable.at_cst
to the corresponding OID (object identifier) table files:
\usr\var\osi\oidtable.gen
\usr\var\osi\oidtable.oc
\usr\var\osi\oidtable.at

Restart the Directory Server to allow the configuration changes to take effect.

Upgrading from pre-1.3 versions of the LDAP connector
Copy the new oidtable.oc_cst to <Installation directory>/var/osi
Copy the new oidtable.at_cst to <Installation directory>/var/osi
Open the file oidtable.oc_cst
Edit the file <Installation directory>/var/osi. Replace the calendar server section with the content of oidtable.oc_cst.
The beginning of the calendar server section is marked by:
################################################################## 
# @ (#) Id: <filename> .... 
################################################################## 
The end of the calendar server section is marked by
# End of file <filename> 
Follow the same step for the file oidtable.at_cst
Restart the directory server
Netscape Directory Server

( UNIX | NT )

UNIX
Login as root or as a user with root privileges.
Create a UNIX group account called dxoffice with an ID of less than 60000.
Create a UNIX user account called unison with an ID of more than 100 and less than 60000 in the group dxoffice.
Edit /etc/services to include the following entries:

unieng 5730/tcp
unisnc 5731/tcp
unidas 5732/tcp
NOTE: If using a centralized information service such as NIS, please refer to the operating system documentation for instructions on adding these services.

Extract the contents of the LDAP Connector package file to a temporary directory (hereafter referred to as <Temp Directory>).
The directory should contain:
ns-slapd30/oracle-calendar-globopt.conf
ns-slapd30/oracle-calendar-schema.conf
To prepare the directory server, you will need to install files to configure ctCal directory objects.
Copy the files:
<Temp Directory>/oracle-calendar-globopt.conf
<Temp Directory>/oracle-calendar-schema.conf
to:
<Directory Server Root>/slapd-<Server Name>/config
For Netscape Directory Server 3.x:
Edit the <Directory Server Root>/slapd-<Server Name>/config/slapd.conf file to include the following files in the indicated sequence:
: 
include <Directory Server Root>/slapd-<Server Name>/config/ns-schema.conf 
include <Directory Server Root>/slapd-<ServerName>/config/oracle-calendar-schema.conf 
: 
include <Directory Server Root>/slapd-<Server Name>/config/ns-globopt.conf 
include <Directory Server Root>/slapd-<ServerName>/config/oracle-calendar-globopt.conf 
:
For Netscape Directory Server 4.x:
Edit the <Directory Server Root>/slapd-<Server Name>/config/slapd.conf file to include the following file in the indicated sequence:
: 
include <Directory Server Root>/slapd-<Server Name>/config/ns-schema.conf 
include <Directory Server Root>/slapd-<ServerName>/config/oracle-calendar-schema.conf
:
Edit the <Directory Server Root>/slapd-<Server Name>/config/slapd.ldbm.conf file to include the following file at the bottom of the file:
include <Directory Server Root>/slapd-<ServerName>/config/oracle-calendar-globopt.conf
Restart the directory server to allow the configuration changes to take effect.
NT
Login as a user with administrator privileges.
Extract the contents of the LDAP Connector package file to a temporary directory (hereafter referred to as <Temp Directory>).
The directory should contain:
oracle-calendar-globopt.conf
oracle-calendar-schema.conf
To prepare the directory server, you will need to install files to configure ctCal directory objects.
Copy the files:
<Temp Directory>\oracle-calendar-globopt.conf
<Temp Directory>\oracle-calendar-schema.conf
to:
<Directory Server Root>\slapd-<Server Name>\config
For Netscape Directory Server 3.x:
Edit the <Directory Server Root>\slapd-<Server Name>\config\slapd.conf file to include the following files in the indicated sequence:
: 
include <Directory Server Root>\slapd-<Server Name>\config\ns-schema.conf 
include <Directory Server Root>\slapd-<ServerName>\config\oracle-calendar-schema.conf 
: 
include <Directory Server Root>\slapd-<Server Name>\config\ns-globopt.conf 
include <Directory Server Root>\slapd-<ServerName>\config\oracle-calendar-globopt.conf 
:
For Netscape Directory Server 4.x:
Edit the <Directory Server Root>\slapd-<Server Name>\config\slapd.conf file to include the following files in the indicated sequence:
: 
include <Directory Server Root>\slapd-<Server Name>\config\ns-schema.conf 
include <Directory Server Root>\slapd-<ServerName>\config\oracle-calendar-schema.conf
:
Edit the <Directory Server Root>\slapd-<Server Name>\config\slapd-ldbm.conf file to include the following file at the bottom of the file:
:
include <Directory Server Root>\slapd-<ServerName>\config\oracle-calendar-globopt.conf
:
Restart the directory server to allow the configuration changes to take effect.
Upgrading from pre-1.3 versions of the LDAP connector

3.x:

Copy the new ct-calendar-schema.conf file to <Directory Server Root>/slapd-<Server Name>/config
Go to the administration page
Select the directory server instance
Click the blinking admin button on the top of the page
Click "Apply manual change"
Restart the directory server

4.x:

Copy the new oracle-calendar-schema.conf file to <Directory Server Root>/slapd-<Server Name>/config
Restart the directory server

iPlanet Directory Server

Extract the contents of the LDAP Connector package file to a temporary staging directory. The directory should contain:
ns-slapd50/oracle-calendar-schema.ldif
Apply the schema by running:
% ldapmodify -h <host> -p <port> -D <ManagerDN> -w <ManagerDNPassword> -f oracle-calendar-schema.ldif

Installing CorporateTime Server with LDAP Connector

( UNIX | NT)

UNIX

Ensure that your directory server is installed and configured correctly, and that you have followed the steps outlined above to prepare your directory server.
Open the calendar server package in a staging directory.
Place your LDAP Connector package file in the same directory.
Run unisetup. For a first-time install, this script will create a /users/unison tree, install the CorporateTime Server package, and create an initial node.

For an upgrade from a previous installation, this script will install the new version, restore the archived databases and will add the existing nodes to the directory server. The presence of a /users/unison directory will be detected. Your old configuration settings (those in /users/unison/misc/unison.ini) will be merged with the new unison.ini and /users/unison/db archived and restored upon installation of the new server. Obsolete parameters will be removed. Other rarely used parameters may also be removed if their values have been left unchanged. This is done in order to simplify the unison.ini file and make it easier to maintain by displaying only those parameters you may need to tune.
Follow the installation script instructions:

When prompted to specify the URL to access the LDAP-based Directory Server, enter:
ldap://<LDAP host>:<LDAP port>/<base DN>

The unisetup script will ask for a DN to group the SYSOP users under. This DN will be appended to the previously specified root DN, and will be used as the calendar server administrators' Parent DN. For example:

If you enter "ldap://your.host.com:389/o=Company X,c=US" as the LDAP base URL,

The base DN is "o=Company X,c=US".

If you enter "ou=Server Admins" as the relative DN,

The calendar server administrators' Parent DN is then "ou=Server Admins,o=Company X,c=US".
If you specify a DN other than the default (none), you must ensure that this DN exists before running unisetup.
The unisetup script will ask for a calendar server administrators' Group DN. This DN will be appended to the previously specified base DN. For example:

If you enter "ldap://your.host.com:389/o=Company X,c=US" as the LDAP base URL,

The base DN is then "o=Company X,c=US".

If you enter "cn=Calendar Server Admins" as the group DN,

The calendar server administrators' Group DN is then "cn=Calendar Server Admins,o=Company X,c=US".
If you want the group to be under the same DN as the calendar server administrators, you must specify the DN as part of the group DN. For example:

If you enter "cn=Calendar Server Admins,ou=Server Admins",

The group DN is then "cn=Calendar Server Admins,ou=Server Admins,o=Company X,c=US".

Run /users/unison/bin/unidsacisetup to create the directory server access control information (ACI). For more information on the default ACIs used by the calendar server, please see the Calendar Server Access Control Requirements.

NOTE: You must complete this step in order to run your calendar server with your directory server, unless using LDAP Connector 1.5 for Critical Path InJoin Directory Server.

Consult the release notes for any additional patches or enhancement packs that may be required.

See the on-line Administrator's Guide for full configuration, use and maintenance instructions.

NT

Ensure that your directory server is installed and configured correctly, and that you have followed the steps outlined above to prepare your directory server.
Run the CorporateTime Server self-extracting executable. Follow the instructions displayed and refer to the Directory Server terminology table to ensure that you enter the correct values where required.

If you are upgrading from a previous version of CorporateTime Server, the presence of a \users\unison directory will be detected. Your old configuration settings (those in \users\unison\misc\unison.ini) will be merged with the new unison.ini and \users\unison\db archived and restored upon installation of the new server. Obsolete parameters will be removed. Other rarely used parameters may also be removed if their values have been left unchanged. This is done in order to simplify the unison.ini file and make it easier to maintain by displaying only those parameters you may need to tune.

If using Netscape Directory Server or Control Data Global Directory Server, run \users\unison\bin\unidsacisetup to create the directory server access control information (ACI).
Consult the release notes for any additional patches or enhancement packs that may be required.

See the on-line Administrator's Guide for full configuration, use and maintenance instructions.

Directory Server terminology

Use the following table to determine the correlation between the directory server parameters required during installation and the terminology used for each separate product.

Table 1: Calendar server / directory server concordance
Definition of concept CorporateTime Server Netscape Directory Server and iPlanet Directory Server Syntegra Global Directory Server Critical Path InJoin Directory Server

Computer on which Directory Server is installed LDAP Host Directory Server host
Directory Server host

Port number for Directory Server (LDAP) connections LDAP Port Directory Server port number LDAP Daemon Port Directory Server address port number

The point in the directory hierarchy from which searches are performed Base DN BaseDN / Directory suffix / search root DN located beneath context prefix Entry Starting Point / context prefix

"Superuser" for teh directory, i.e. user with unrestricted access SuperUserDN RootDN or Unrestricted user Manager DN Directory Administrator's DN

Password for unrestricted access SuperUserDNPassword RootDN or Unrestricted user password Manager DN Password Directory Administrator's Password

The "parent" entry, offset from the baseDN, for the 6 reserved calendar users Calendar Server Administrators' Parent DN n/a n/a n/a

A new group, offset from the baseDN, for the 6 reserved calendar users Calendar Server Administrators' Group DN n/a n/a n/a

Uninstalling CorporateTime Server with LDAP Connector

( UNIX | NT )

UNIX

Stop the calendar server using the unistop command.
In the Directory Server, remove the calendar server attributes from your calendar users. This is done by using LDIF update commands.
In the Directory Server, remove all ctCal objects for the calendar server nodes that were on this server.

Use the ldapsearch and ldapdelete commands and refer to your Directory Server Administrator's Guide for proper syntax.

In the Directory Server remove all the relevant calendar server administrative groups and ACLs from the database.

Clean up your LDIF file with a manual edit LDIF or use LDIF update statements.

Delete the <calendar server path>.
Delete the /users directory.
Remove the UNIX user account unison.
Remove the UNIX group account dxoffice.
Remove the unieng, unisnc, and unidas entries from /etc/services.

NT

Select Start | Settings | Control Panel | Add/Remove Programs and follow the operating system instructions to remove the calendar server.

If you are unable to remove the calendar server using the method above:

Stop the calendar server using one of the following methods:

Select Services | Properties... from the CorporateTime Server Administrator and follow the on-line instructions
Select Start | Settings | Control Panel | Services to open the service control tool provided with the operating system
Use the unistop command

In the Directory Server, remove the calendar server attributes from your calendar users. This is done by using LDIF update commands.
In the Directory Server, remove all ctCal objects for the calendar server nodes that were on this server.

Use the ldapsearch and ldapdelete commands and refer to your Directory Server Administrator's Guide for proper syntax.

In the Directory Server remove all the relevant calendar server administrative groups and ACLs from the database.

Clean up your LDIF file with a manual edit LDIF or use LDIF update statements.

Remove the \users\unison directory.
Using regedit, find and remove the entry under
HKEY_LOCAL_MACHINE\SOFTWARE\Oracle\calendar server\CurrentVersion
Reboot the machine.

If your demo license has expired

Contact Oracle support at (514) 733-8500 and request a new license key.
Stop your calendar server using the unistop utility.
Open the /users/unison/misc/unison.ini file and replace the value of the [LIC] license parameter with the key supplied to you.
Restart your calendar server using the unistart utility.

CorporateTime Server Administrator

The CorporateTime Server Administrator is an NT-based GUI used to manage the CorporateTime Server. Many administrative tasks and procedures may be performed using this tool, although some functionality is available only through command-line utilities. See the Administrator's Guide for a more complete description of when and how the Admin GUI can be used. The CorporateTime Server Administrator is included as part of the installed package for the NT version of CorporateTime Server.

Calendar Administrator

The Calendar Administrator is a CGI- or FastCGI-based Web administration tool for your calendar server. Use it to manage users, resources, holidays, and event calendars. The Calendar Administrator requires a Web server and a Web browser compatible with HTML 3.2 (Microsoft Internet Explorer 4.0 or greater, Netscape Navigator 4.0 or greater). For installation instructions, see the Calendar Administrator readme file.

***Table 1: Calendar server / directory server concordance***
Definition of concept	CorporateTime Server	Netscape Directory Server and iPlanet Directory Server	Syntegra Global Directory Server	Critical Path InJoin Directory Server
Computer on which Directory Server is installed	LDAP Host	Directory Server host		Directory Server host
Port number for Directory Server (LDAP) connections	LDAP Port	Directory Server port number	LDAP Daemon Port	Directory Server address port number
The point in the directory hierarchy from which searches are performed	Base DN	BaseDN / Directory suffix / search root	DN located beneath context prefix	Entry Starting Point / context prefix
"Superuser" for teh directory, i.e. user with unrestricted access	SuperUserDN	RootDN or Unrestricted user	Manager DN	Directory Administrator's DN
Password for unrestricted access	SuperUserDNPassword	RootDN or Unrestricted user password	Manager DN Password	Directory Administrator's Password
The "parent" entry, offset from the baseDN, for the 6 reserved calendar users	Calendar Server Administrators' Parent DN	n/a	n/a	n/a
A new group, offset from the baseDN, for the 6 reserved calendar users	Calendar Server Administrators' Group DN	n/a	n/a	n/a

Copyright © 1993, 2002, Oracle Corporation. All rights reserved.