| Oracle® Calendar Administrator's Guide 10g Release 1 (10.1.2) Part Number B25485-05 |
|
|
View PDF |
| Oracle® Calendar Administrator's Guide 10g Release 1 (10.1.2) Part Number B25485-05 |
|
|
View PDF |
This chapter is an introduction to managing the calendar server. All administrative tasks and procedures are executed using command-line utilities or the Calendar Administrator.
This chapter contains the following sections:
Administration concerns for Oracle Calendar fall into four broad categories:
Initial deployment planning, including sizing estimates and operating system configuration. Throughout this guide you will find a variety of information to aid you in designing a deployment that will meet your needs efficiently and effectively, including common deployment scenarios, recommended sizing guidelines, recommended kernel parameter settings for UNIX platforms and more.
Installing the Oracle Calendar software and performing basic initial configuration. This information can be found in the Oracle Collaboration Suite Installation Guide.
Performing ongoing system maintenance, such as tuning calendar configuration parameters according to anticipated and observed usage, backing up the calendar database and monitoring the system. Most of these tasks can be performed using a variety of command-line administration tools provided with the calendar server.
Managing the information in the calendar database, such as adding and modifying calendar users, resources, event calendars, holidays, groups. Most of these tasks can be performed using either command-line utilities or the Oracle Calendar administrator.
The Oracle Calendar administrator is an web-based server management tool that enables users and administrators to manage user accounts, resources, event calendars, groups and holidays in the calendar server database. In addition, the Oracle Calendar administrator provides easy access to basic system administration tasks such as viewing the status of calendar nodes and databases, and starting or stopping nodes and servers.
A majority of the administration tasks can be performed using the Oracle Calendar administrator. 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 lets the user manage users, resources, event calendars, and groups. The Server Administration tab lets the administrator start and stop individual nodes and calendar servers, configure nodes and calendar servers, and organize holiday management.
For more information about all tunable parameters available to configure your Oracle Calendar Administrator in the $ORACLE_HOME/ocad/bin/ocad.ini configuration file, see "Calendar Administrator Parameters" in Chapter 5 of Oracle Calendar Reference Manual.
Certain Calendar server administration tasks can be accomplished with the Oracle Enterprise Manager. For more information about Oracle Enterprise Manager, see "Introduction to Oracle Enterprise Manager 10g Application Server Control for Collaboration Suite" in Chapter 3 of Oracle Collaboration Suite Administrator's Guide.
The Oracle Calendar server comes with a number of command-line utilities that provide scriptable control over a wide range of calendar server information and features. These command-line utilities are installed in the $ORACLE_HOME/ocal/bin of your Calendar server's installation directory.
Note that all server administration performed with 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.
For a complete list of the utilities included with your calendar server and full details on their operation, see "Calendar Server Utilities" in Chapter 6 of Oracle Calendar Reference Manual.
If you have deployed Oracle Calendar in standalone mode with 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 these utilities, see "Calendar Server Utilities" in Chapter 6 of 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 from the $ORACLE_HOME/ocal/bin directory:
% unistart
Example For an orderly shutdown of the calendar server, execute the following command from the $ORACLE_HOME/ocal/bin directory:
% 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. |
Using OPMN to Stop and Start the Calendar Server
When deployed with Oracle Collaboration Suite, Oracle Calendar server can also be started and stopped using the Oracle Process Management and Notification (OPMN) opmnctl utility. This utility is located in the $ORACLE_HOME/opmn/bin directory.
Example To start the Calendar server, bringing up six daemons, execute the following command from the $ORACLE_HOME/opmn/bin directory:
% opmnctl startproc ias-component=CalendarServer
Example For an orderly shutdown of the calendar server, execute the following command from the $ORACLE_HOME/opmn/bin directory:
% opmnctl stopproc ias-component=CalendarServer
To view the current status of the calendar daemons/services and servers, run the unistatus utility. For full information about use and syntax of this utility, see "Calendar Server Utilities" in Chapter 6 of Oracle Calendar Reference Manual.
Example To verify the status of the calendar server's daemons/services, run the following command:
% unistatus -d
UID PID PPID STIME TIME COMMAND CLASS INFORMATION oracle 4739 2570 May31 00:00:03 unisncd Listener oracle 4632 2570 May31 00:00:00 unidasd Listener oracle 4262 2570 May31 00:00:00 unicsmd Listener oracle 1629 4444 Jun03 00:00:11 uniengd Listener 2/25 sess oracle 2366 4444 Jun15 00:00:00 uniengd Listener 0/25 sess oracle 4444 2570 May31 00:00:00 uniengd Controller 5 lstn oracle 4525 4444 May31 00:00:03 uniengd Listener 2/25 sess oracle 7084 4444 Jun15 00:00:00 uniengd Listener 0/25 sess oracle 7417 4444 Jun15 00:00:00 uniengd Listener 0/25 sess oracle 4858 2570 May31 00:00:00 unicwsd Controller 2 tasks oracle 28607 4858 Jun15 00:00:05 unicwsd Task Messaging,SSR,Snooze,EventSync,DirSync,GALSync,Calendar store consistency scan,EventCalUpdate,DirProv,LogRotation oracle 28929 4858 Jun15 00:00:00 unicwsd Task Replication oracle 4250 2570 May31 00:00:00 unilckd Controller 1 lstn oracle 4298 4250 May31 00:00:02 unilckd Listener 7 DB sess
Using OPMN to Check the Calendar Server Status
When deployed with Oracle Collaboration Suite, Oracle Calendar server's status can also be checked using the Oracle Process Management and Notification (OPMN) opmnctl utility. This utility is located in the $ORACLE_HOME/opmn/bin directory.
Example To verify the status of the calendar server's daemons/services, run the following command from the $ORACLE_HOME/opmn/bin directory:
% opmnctl status ias-component=CalendarServer Processes in Instance: cal.visioncorp.com -------------------+--------------------+---------+--------- ias-component | process-type | pid | status -------------------+--------------------+---------+--------- CalendarServer | Calendar_CSM | 13305 | Alive CalendarServer | Calendar_CWS | 13454 | Alive CalendarServer | Calendar_DAS | 13387 | Alive CalendarServer | Calendar_SNC | 13413 | Alive CalendarServer | Calendar_ENG | 13356 | Alive CalendarServer | Calendar_LCK | 13306 | Alive
To view current logged-on users, run the uniwho utility. For full information about use and syntax, see "Calendar Server Utilities" in Chapter 6 of 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
To change the password of the SYSOP (the administrator) run the unioidconf utility from the command line with the -setsysoppassword option. This utility is also useful in cases where the administrator password is forgotten. In this case, you will be asked for the Directory Manager's password, and then prompted for the new calendar administrator's password. For more information about use and syntax of this utility, see "Calendar Server Utilities" in Chapter 6 of Oracle Calendar Reference Manual.
Example To change the password, execute:
% unioidconf -setsysoppassword -D cn=orcladmin Enter a bind password: Enter new administrator password: Re-enter new administrator password:
|
Note: unioidconf can only be used when Calendar is deployed with Oracle Collaboration Suite. Use the unipasswd utility to change the sysop password when using Oracle Calendar in a standalone environment. For more information on unipasswd, see "Calendar Server Utilities" in Chapter 6 of Oracle Calendar Reference Manual. |
Calendar server can be populated using command-line utilities or by using the Oracle Calendar administrator. Additionally, when Oracle Calendar server is deployed with Oracle Collaboration Suite, automatic provisioning features for users can be configured. For all information about populating the Calendar server, see the following chapters:
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:
uniaccessrights — to manage user and resource access rights.
uniadmrights — to grant, modify or remove administration rights.
unicheck (UNIX only) — to verify the presence of all necessary files and directories, and check the settings for permissions, owner, and group information.
uniclean (UNIX only) — to remove or correct any problems found running unicheck. Transient files will be removed and permission and ownership settings restored to the default.
unidsdiff — to report differences between the Calendar server and the directory server.
unidssync — to synchronize the information in the Calendar server with that in the directory server.
unilogons — to display calendar server signon/signoff statistics.
unireqdump — to view and delete requests in the Corporate-Wide Services (CWS) queue.
unirmold — to remove old data from the calendar server database.
uniuser — to manage user, resource and event calendar accounts.
uniwho — to display information about signed-on calendar users.
For more information on use and syntax of these utilities see "Calendar Server Utilities" in Chapter 6 of Oracle Calendar Reference Manual.
