Skip Headers

Oracle® Calendar Administrator's Guide
Release 2 (9.0.4)

Part Number B10892-02
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Master Index
Master Index
Go to Feedback page
Feedback

Go to previous page
Previous
Go to next page
Next
View PDF

5
Calendar Server Administration

This chapter describes how to manage your calendar server. All administrative tasks and procedures are executed using command-line utilities or the Calendar Administrator.

Note that all server administration performed through the command-line utilities provided must be carried out on UNIX platforms as the instance owner. The instance owner is the UNIX user account used to install and run the server. The calendar server daemons should all run under this user name as well. It is not recommended to run the calendar server as the root user.

This chapter documents the following administrative tasks:

Using the Calendar Administrator

A majority of the administration tasks can be performed using the Calendar Administrator WEB interface. This WEB application is normally installed in the $ORACLE_HOME/ocad directory. The Calendar Administrator can be used by the administrator (SYSOP) or calendar users who have administration rights.

The Calendar administrator interface is divided into two sections, accessible through tabs appearing on the top right of the page. Access to specific commands and functionality is determined by the user's assigned calendar administrative rights. The Calendar Management tab allows the user to manage users, resources, event calendars, and groups. The Server Administration tab lets the administrator start and stop individual nodes and calendar servers, and organize holiday management.

For more information on all tunable parameters available to configure your Oracle Calendar Administrator, see appendix D, "Calendar Administrator Parameters" which lists all parameters located in the initialization file $ORACLE_HOME/ocad/bin/ocad.ini.

Starting and Stopping the Calendar Server

If you are using an external LDAP directory server (the unison.ini parameter [DAS] enable=TRUE), your directory server must be running before you can start the calendar server. If you have enabled e-mail notification in the clients (the unison.ini parameter [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 of this utility, see Appendix E, "Utilities" in the Oracle Calendar Reference Manual.

Example

To start the calendar server (bringing up five daemons if using an internal directory and six daemons if using an external LDAP directory), execute the following command:

% unistart 
Example

For an orderly shutdown of the calendar server, execute the following command:

% unistop


Note::

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.


Checking Server Status

To view the current status of the calendar daemons/services and servers, run the unistatus utility. For full information on use and syntax of this utility, see Appendix E, "Utilities" in the Oracle Calendar Reference Manual.

Example

To verify the status of the calendar server's daemons/services, run the following command:

% unistatus -d

<pre>UID   PID  PPID STIME   TIME      COMMAND CLASS INFORMATION 
tin   6772 228  1:41:21 0:0:0.156 unisncd Listener  
tin   4368 228  2:32:23 0:0:0.187 unicwsd Controller  3 task(s) 
tin   6756 4368 2:32:27 0:0:0.125 unicwsd Task  SSR 
tin   7680 4368 2:32:27 0:0:0.203 unicwsd Task  Messaging 
tin   7196 228  1:41:28 0:0:0.46  unicsmd Listener 
tin   6712 228  1:41:17 0:0:0.78  unilckd Listener  0 DB sess 
tin   6692 228  1:41:18 0:0:1.875 uniengd Listener  3/100 sess
unistatus: the calendar server is up

Viewing Current User Activity

To view current logged-on users, run the uniwho utility. For full information on use and syntax, see Appendix E, "Utilities" in the Oracle Calendar Reference Manual.

Example

To view a list of current client connections, execute:

% uniwho
    PID           ADDRESS  NODEID      XITEMID  USER
   7721     193.77.49.162   20004      20004,2  CWSOP,na 
  14668     193.77.49.223   20004    20004,295  Alexander,James 
  10237      193.77.49.44   20004    20004,142  Addison,Thomas 
  TOTAL STANDARD SHARED CONNECTIVITY
      3        2      0            1

Changing the SYSOP (Node) Password

Cmd line

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 of this utility, see Appendix E, "Utilities" in the Oracle Calendar Reference Manual.

Example

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


Note::

In an Calendar installation with no LDAP directory, nodes are created with no SYSOP password. The password must be set after the node is created. However, a SYSOP password is set for a node created where the calendar server installation is using a directory server.


Other Administrative Tasks

Use command-line utilities for a variety of other less frequent tasks. Some of the utilities that you may want to be familiar with once the calendar server is up and running are:

See Appendix E, "Utilities" in the Oracle Calendar Reference Manual for a description of the function and syntax of all utilities included with the calendar server.