Netscape Calendar Server 4.0 - README
Netscape Calendar Server 4.0
This file was last updated on March 8, 2000
Thank you for choosing Netscape Calendar Server. This file contains
installation instructions only. Please see the Netscape Calendar Server
Administrator's
Guide for information about administering your Netscape Calendar
Server. Please see the release
notes for a description of new features and known problems, and other
information about this release.
A web browser, such as Netscape
Navigator , is required to install and administer the Calendar Server.
A calendar client is required to access the Netscape Calendar Server. Netscape
Calendar, a component of Netscape
Communicator with Enterprise Calendaring , is used as a calendar client.
An LDAP directory server, such as Netscape
Directory Server, is required. An SMTP messaging server, such
as Netscape Messaging Server,
is required for mail notification of calendar entries.
This version of Netscape Calendar Server is available for Windows NT
4.0 (Service Pack 4), Solaris 2.5.1/2.6, HPUX 10.20/11.0 and AIX 4.21/4.32
NOTE: Under Solaris 2.5.1, in order
to run the Administration Server component of Calendar Server, you will
need the libresolv.so.2 library, which is part of Sun patch #103663. To
obtain this patch from the Sun website, click here.
Contents of this README file
How to report problems
Search the available resources at Netscape
Business Technical Support or post problems or questions to the Netscape
Calendar user group snews://secnews.netscape.com/netscape.server.calendar.
How to get more information
For complete instructions on deploying, configuring, and administering
your Calendar Server, consult the Administrator's Guide. An on-line
version of the Administrator's
Guide is provided with the Calendar Server software under <Netscape
Server root>/manual/calendar/cs. Click the Help button on any
Calendar Server or Administration Server form to access the on-line help.
Search our on-line
database for answers to your questions or view the release
notes for a description of new features and known problems of this
release.
Before installing Calendar Server
Before you install the Calendar Server, ensure that:
-
You have your server's root password
-
Your server has at least 64 MB of RAM
-
Your server has at least 150 MB of free space on the hard drive
-
An LDAP directory server such as Netscape Directory Server 3.x or 4.x is
successfully installed
-
You have a web browser such as Netscape Communicator to install and administer
the Calendar Server
-
You have Netscape Calendar client installed. This is a component
of Netscape Communicator with Enterprise Calendaring
-
If you require mail notification, you will need an SMPT mail server such
as Netscape Messaging Server 4.x
NOTE: Refer to Chapter 1 "Deployment and Installation" and
Appendices A "Disk Space and Memory" and B "Sizing Guidelines" in the Administrator's
Guide for more detailed instructions on estimating the anticipated
calendar usage within your organization.
During installation of Netscape Directory Server 3.x:
-
Note where you installed this server; this will be used for Calendar Server
installation
-
You must select Configure Directory for SuiteSpot
-
Note your SuiteSpot Administrator's ID and Password; this
will be used for Calendar Server installation and administration
-
Note the URL to access this server:
ldap://<directory server host>:<directory server port>/<base
DN>
During installation of Netscape Directory Server 4.x:
-
Note where you installed this server; this will be used for Calendar Server
installation
-
Note your Administrator's ID and Password; this will be used
for Calendar Server installation and administration
-
Note the URL to access this server:
ldap://<directory server host>:<directory server port>/<base
DN>
-
Execute the following ldapmodify function on the server so that it is able
to run with Admin Server 3.5:
# cd <server_root>/server4/shared/bin
# ./ldapmodify -D "cn=directory manager"
-w password -f
<server-root>/slapd-hostname/ldif/suitespot3x.ldif
or see Technote
#19981217-3.
-
Do not install Calendar Server 4.0 and Directory Server 4.0 under the
same server root, as they each use a different version of the Admin server.
Calendar uses Admin server 3.5.
NOTE: Under UNIX, the Calendar Server must
run as the root or unison user. If you install Calendar Server in the same
server root as other SuiteSpot servers, all the SuiteSpot servers must
be run as the same user.
Installing Calendar Server -- UNIX
Clean (first time) Install
1. Preparing for installation:
-
Login as root
-
Create a group account called dxoffice with an ID of less than
60000
-
Create a user account called unison with an ID of less than 60000
in the group dxoffice
-
Edit /etc/services to include the following entries:
unieng 5730/tcp
unisnc 5731/tcp
unidas 5732/tcp
2. Running the installation script:
-
Run ns-setup
Follow the installation script instructions. Use all defaults except
as noted below:
-
For SuiteSpot user and group enter:
-
SuiteSpot User [nobody]: unison or root
-
SuiteSpot Group [nobody]: dxoffice or sys
-
For the URL to access the Directory Server enter:
-
ldap://<directory server host>:<directory server port>/<base
DN>
-
Enter the SuiteSpot 4.0 user ID and password set during installation
of the directory server
-
If prompted to create a /users directory, answer "yes"
-
If prompted to create or replace the /users/unison directory,
answer "yes"
Refer to the Troubleshooting section: Disabling
anonymous binds if you selected this option during the installation
-
Refer to the "Deployment and Installation" chapter of the Administrator's
Guide for more information concerning the configuration of Calendar
Server (time zone, logged-on user limit and mail notification)
3. Creating the Calendar Server instance:
-
Use a web browser to open URL <calendar server host>:<calendar
server administration port>
NOTE: If you cannot connect to the Administration Server, ensure
that the Hosts and Addresses entries in <Netscape SuiteSpot root>/admin-serv/config/ns-admin.conf
includes the host and address you are connecting from. If you change these
parameters, stop and start the Administration Server using <Netscape
SuiteSpot root>/start-admin and <Netscape SuiteSpot root>/stop-admin.
-
Click Create New Netscape Calendar Server 4.0
-
Use defaults except as noted below:
-
Enter a value between 10000 and 20000 for Node-ID
-
Change the Node Alias to a more descriptive name if desired
-
Alter the Node Time Zone if required; this value cannot be changed
later
-
Enter and record (for later use) a SYSOP password
-
Click Submit
-
Monitor the status display for error messages
4. Adding users to the Calendar Server:
-
If the user(s) do not exist on the Directory Server:
-
Return to the Netscape Server Administration page
-
Select Users and Groups | New User from General Administration to
open the New User form
-
Complete this form according to the instructions in the context sensitive
on-line help
-
Click Create And Edit User
-
Click the Calendar tab
-
Enter a Node-ID and related SYSOP Password and click Add
-
If the user(s) do exist in the Directory Server:
-
Select User Management | Add Users to Node from the Netscape Calendar
Server 4.0 page
-
In the user list on the Add Users to Node form, you will see displayed
up to 100 users who are not configured calendar users. To select users
to add, click on an entry to select a single user, <Ctrl> click on each
desired entry to create a subset of the displayed users, or click Select
All to activate the complete list. If you have more than 100 users
to add, this procedure must be repeated until the user list is empty.
-
Select the Node-ID for the node that you wish to add the selected
users
-
Enter the SYSOP password
-
Click Add
-
See "Creating Calendar users" in theAdministrator's
Guide for more detailed instructions.
A Netscape Calendar client can now connect to this Netscape Calendar
Server.
Installing Calendar Server -- Windows NT
Note: Calendar server can be installed on either an NTFS or FAT partition.
Clean (first time) Install
-
Run a40eiu.exe
-
Follow the InstallShield instructions
-
Enable LDAP-based authentication and enter values for:
-
Server Name
-
Server Port
-
Base Distinguished Name
-
For Administration Server authentication enter:
-
Change the randomly selected administration server port if desired (not
possible for 3.x installation). You will connect to this port to access
the Netscape Administration Server. Note the displayed URL for later use.
-
If you choose to disable anonymous binds, you must follow the instructions
in Disabling anonymous binds after you have
completed installation
-
Enter a value between 10000 and 20000 for Node-ID
-
Use a descriptive Node Alias that is one word and up to 32 characters
in length
-
Select the desired Node Time Zone; this value cannot be changed
later
-
Enter and record (for later use) a SYSOP password
-
Follow the instructions under Adding users to the
Calendar Server
Upgrade/Migration from Calendar Server
3.5x (UNIX/NT)
A note about Netscape Calendar Server - As
the contract with our NCS supplier has been abruptly terminated,
the Alliance is legally unable to sell the NCS product family, including
additional seats. To our existing NCS 3.5 customers with a valid maintenance
subscription, you can still upgrade to NCS 4.0 without additional cost.
This upgrade does not include any additional seats.
Please contact technical support for information on getting this upgrade.
To find the alternative solution and more information about Enterprise
Calendaring and Netscape Calendar Server click here.
Once you complete the upgrade from Calendar Server 3.5 to 4.0, review
the parameters (preserved from the 3.5 installation) in the /users/unison/misc/unison.ini
file to ensure that the settings are correct.
UNIX Upgrade (from Netscape Calendar Server 3.5x)
If you are already using Calendar Server 3.5, follow the instructions in
this section before installing Calendar Server 4.0. Ignore the Migrate
from previous version link on the Administration Server page.
-
Back up the LDAP directory.
-
Stop and back up each Calendar Server. Ensure that the backup has a unique
file name and is not saved under the Calendar Server root.
-
On the Calendar Server that is to be migrated:
-
Stop the Administration Server.
-
Run ns-setup
-
Ensure that the Calendar Server backup is not in the /users/unison
directory
-
Install Calendar Server 4.0 with the following directions
(see installation instruction) and caveats:
-
Use the same server root and Administration Server configuration
-
When prompted to overwrite the /users/unison directory, answer
"yes"
-
When prompted to migrate from a previous version, answer "yes"
-
Ensure <Netscape SuiteSpot root>/admin-serv/config/dsgw.conf
has the line:
include ../../../../admin-serv/config/dsgw-calendar.conf
-
The steps to create the Calendar Server instance are not required; it will
be created automatically.
-
Start the Calendar Server
Note: If you abort once the /users/unison directory has been backed
up, you must untar the archived directory and relink to /users/unison
before attempting the migration procedure again.
NT Upgrade (from Netscape Calendar Server 3.51)
Before migrating from CS 3.51 on NT, with an existing
configuration of more than 9 nodes on a single server, migrate the number
of nodes over 9 to another 3.51 server. Calendar 4.0 does not support
more than 9 nodes on a server, on the NT platform. See the release
notes and this Technical
Note for more information.
-
Run a40eiu.exe
-
Follow the InstallShield instructions
-
Install to the same directory as the current 3.5 installation
-
Enable LDAP-based authentication and enter values for:
-
Server Name
-
Server Port
-
Base Distinguished Name
-
For Administration Server authentication enter:
-
Change the randomly selected administration server port if desired. You
will connect to this port to access the Netscape Administration Server.
Note the displayed URL for later use.
Uninstalling Calendar Server -- UNIX
-
Stop the Calendar Server.
-
Using your web browser, open URL: <calendar server host>:<calendar
server administration port>
-
Select Server Preferences | Server On/Off from the Calendar Server
Manager
-
Click Stop Server
-
If your server does not stop, execute unistop
-
Remove all calendar objects and attributes in the Directory Server
-
Using ldapsearch and ldapmodify, remove all nsCalUser
attributes from the users that were in this Calendar Server
-
Using ldapsearch and ldapmodify, remove
the nsCalAdmin members for the calendar nodes that were
in this Calendar Server, from the Calendar Server
Admins group. If this is the last member of this group, also remove
this group and the associated aci object for this group
-
Using ldapsearch and ldapmodify, remove all nsCalAdmin
objects for the calendar nodes that were in this Calendar Server
-
Refer to your Directory Server Administrator's
Guide for information on how to use these LDAP tools
-
Remove the Administration Server if you are not sharing the Administration
Server with other SuiteSpot servers
-
Return to the Netscape Server Administration Page
-
Select Admin Preferences | Shut Down and click on Shut down the
administration server!
-
If your server does not stop, use the kill command against
all the "ns" daemons that are running your Calendar Server
-
Remove the Calendar Server. If you are sharing the Administration Server
with other SuiteSpot servers, follow these steps to remove Calendar Server
specific information:
-
Remove <calendar server path>/admin-serv/config/dsgw-calendar.conf
-
Remove <calendar server path>/admin-serv/config/dsgw-calendar-defs.conf
-
Remove <calendar server path>/bin/admin/admin/bin/addcaluser
-
Remove <calendar server path>/bin/admin/admin/html/display-cal-resource.html
-
Remove <calendar server path>/bin/admin/admin/html/display-cal-user.html
-
Remove <calendar server path>/bin/admin/admin/html/dscrresource.html
-
Remove <calendar server path>/bin/admin/admin/html/dslsresource.html
-
Remove <calendar server path>/bin/admin/admin/html/list-Resource.html
-
Remove <calendar server path>/bin/calendar
-
Remove <calendar server path>/calendar-<host>
-
Remove <calendar server path>/manual/calendar
-
Remove <calendar server path>/unison
-
In <calendar server path>/admin-serv/config/dsgw.conf, remove
the line include dsgw-calendar.conf
-
In <calendar server path>/admin-serv/config/dsgwfilter.conf,
remove the "dsgw-resource" section
-
In <calendar server path>/admin-serv/config/dsgwsearchprefs.conf,
remove the Resource section
-
In <calendar server path>/admin-serv/config/servers.lst, remove
the line calendar:Netscape Calendar Server
-
Remove the /users directory
-
Remove the unison user account
-
Remove the dxoffice group account
-
Remove the unieng, unisnc, and unidas entries
from /etc/services
Uninstalling Calendar Server -- Windows
NT
-
Stop the Calendar Server
-
Using your web browser, open URL: <calendar server host>:<calendar
server administration port>
-
Select Server Preferences | Server On/Off from the Calendar Server
Manager
-
Click Stop Server
-
If your server does not stop, refer to the Administrator's
Guide for how to use unistop or use Control
Panel | Services to stop all the calendar services
-
Remove all calendar objects and attributes in the Directory Server
-
Using ldapsearch and ldapmodify, remove all nsCalUser
attributes from the users that were in this Calendar Server
-
Using ldapsearch and ldapmodify, remove
the nsCalAdmin members for the calendar nodes that were
in this Calendar Server, from the Calendar Server
Admins group. If this is the last member of this group, also remove
this group and the associated aci object for this group.
-
Using ldapsearch and ldapmodify, remove all nsCalAdmin
objects for the calendar nodes that were in this Calendar Server
-
Refer to the Netscape Directory Server Administrator's Guide for
information on how to use these LDAP tools
-
Remove the Administration Server if you are not sharing the Administration
Server with other SuiteSpot servers
-
Return to the Netscape Server Administration Page
-
Select Admin Preferences | Shut Down and click Shut down the
administration server!
-
If your server does not stop, use Control Panel
| Services to stop the Administration Server
-
Run <calendar server path>\uninst.exe
-
Remove the Calendar Server. If you are sharing the Administration Server
with other SuiteSpot servers, follow these steps to remove Calendar Server
specific information:
-
Remove <calendar server path>\admin-serv\config\dsgw-calendar.conf
-
Remove <calendar server path>\admin-serv\config\dsgw-calendar-defs.conf
-
Remove <calendar server path>\bin\admin\admin\bin\addcaluser.exe
-
Remove <calendar server path>\bin\admin\admin\html\display-cal-resource.html
-
Remove <calendar server path>\bin\admin\admin\html\display-cal-user.html
-
Remove <calendar server path>\bin\admin\admin\html\dscrresource.html
-
Remove <calendar server path>\bin\admin\admin\html\dslsresource.html
-
Remove <calendar server path>\bin\admin\admin\html\list-Resource.html
-
Remove <calendar server path>\bin\calendar
-
Remove <calendar server path>\calendar-<host>
-
Remove <calendar server path>\manual\calendar
-
In <calendar server path>\admin-serv\config\dsgw.conf, remove
the line include dsgw-calendar.conf
-
In <calendar server path>\admin-serv\config\dsgwfilter.conf,
remove the "dsgw-resource" section
-
In <calendar server path>\admin-serv\config\dsgwsearchprefs.conf,
remove the Resource section
-
In <calendar server path>\admin-serv\config\servers.lst, remove
the line calendar:Netscape Calendar Server
-
Select Control Panel | Add/Remove Programs | Netscape Calendar Server
4.0
-
Remove the \users directory
-
Using regedit, find and remove HKEY_LOCAL_MACHINE/SOFTWARE/NETSCAPE/CALENDAR
SERVER
-
Using regedit, find and remove the unicwsd, uniengd,
unilckd,
unisncd,
and unidasd entries under
HKEY_LOCAL_MACHINE/SYSTEM/CURRENT
CONTROL SET/SERVICES.
-
Reboot the machine
Troubleshooting
Disabling anonymous binds
If you chose to disable anonymous binds during installation of your
Calendar Server, you must manually enter a value in the /users/unison/misc/unison.ini,
in UTF-8 format, for the binddn parameter. To complete this step:
-
Run /users/unison/bin/unistrconv with no arguments/options to
determine the current terminal character set
-
Run ./unistrconv -from <current terminal character set> <binddn
value> to convert your binddn value to UTF-8
-
Copy and paste the value output in step #2 to the [LDAP] section of the
/users/unison/misc/unison.ini
file. The completed entry should follow the format "binddn = <binddn
value output in step #2>"
Finding Documentation
You can use your web browser to examine the documentation for this
release of the directory server. The following manuals and release
notes are available at the following locations:
-
Calendar Server 4.0 Release Notes:
http://developer.iplanet.com/docs/manuals/calendar.html#40
http://developer.iplanet.com/docs/manuals/calendar.html#40