|Oracle Calendar Server Administrator's Guide
Part Number B10093-01
This chapter describes how to manage your calendar server. All administrative tasks and procedures are executed using command-line utilities, the Admin GUI, the Web GUI, or operating system tools.
Note that all server administration performed through the command-line utilities provided should be carried out on UNIX platforms as the
unison user created by the server installation program. The calendar server daemons should all run under this user name as well. It is not recommended to run the calendar server as the
This chapter documents the following administrative procedures:
If you are using an external LDAP directory server (the
[DAS] enable=TRUE), your directory server must be running before you can start the calendar server. If you have enabled e-mail notification (the
[LIMITS] mail=TRUE), a mail server should be running.
Start the calendar server by using the
unistart utility. Stop it by using the
unistop utility. For full information on use and syntax, see the calendar server Reference Manual, Appendix C, "Utilities."
To start the calendar server (bringing up four daemons if using an internal directory and five daemons if using an external LDAP directory), execute the following command:
For an orderly shutdown of the calendar server, execute the following command:
The number of client connections, the number of processes running, and the volume of network traffic all affect the amount of time that the server takes to stop.
To view the current status of the calendar daemons/services and servers, run the
unistatus utility. For full information on use and syntax, see the calendar server Reference Manual, Appendix C, "Utilities."
To verify the status of the calendar server's daemons/services, run the following command:
% unistatus -d UID PID PPID STIME TIME COMMAND CLASS unison 26512 1 17:18:14 0:00 unilckd daemon unison 26517 1 17:18:16 0:00 uniengd daemon unison 26591 1 17:18:22 0:00 unidasd daemon unison 26669 1 17:18:24 0:00 unisncd daemon unison 26678 1 17:18:26 0:00 unicwsd daemon unistatus: the calendar server is up
To view current logged-on users, run the
uniwho utility. For full information on use and syntax, see the calendar server Reference Manual, Appendix C, "Utilities."
To view a list of current client connections, execute:
PID ADDRESS NODEID XITEMID USER
7721 188.8.131.52 20004 20004,2 CWSOP,na
14668 184.108.40.206 20004 20004,295 Alexander,James
10237 220.127.116.11 20004 20004,142 Addison,Thomas
To change the password of the SYSOP (the administrator of a node) or any other user, run the
unipasswd utility from the command line. For full information on use and syntax, see the calendar server Reference Manual, Appendix C, "Utilities."
To change the password for node 34, execute:
% unipasswd -n 34 Enter old password: Enter new password: Re-enter new password: unipasswd: Password changed successfully
A node created during the installation of the internal-directory version of the calendar server will not have a SYSOP password. The password must be set once the node is created. However, a SYSOP password must be set for a node created as part of the calendar server installation when using a directory server.
Use command-line utilities for a variety of other less frequent tasks. For full information on use and syntax, see the calendar server Reference Manual, Appendix C, "Utilities."
Some of the utilities that you may want to be familiar with once the calendar server is up and running are:
unicheck. Transient files will be removed and permission and ownership settings restored to the default.
See the calendar server Reference Manual, Appendix C, "Utilities," for a description of the function and syntax of all utilities included with the calendar server.