Oracle® Calendar Administrator's Guide Release 2 (9.0.4) Part Number B10892-02 |
|
|
View PDF |
A node is a database containing agendas and information for users, resources and event calendars. A node network is a set of two or more connected nodes. More than one node can exist on a single calendar host. This situation commonly occurs where a group of users requires a different time zone, or when there is a logical division that the administrator wishes to maintain within a group of users in the same time zone.
This chapter covers the following topics:
Each node is identified by a unique numeric key called the node-ID. Most administrators set one or more descriptive node aliases that may also be used when connecting to the calendar server. A SYSOP (node administrator) password restricts access to the calendar account used for all node management tasks. Each node has a default time zone.
To create a node, you will need the following information:
-r
flag can be used to "reset" a node (delete it and recreate it with the same node-ID). A warning will be issued before this action is taken. Node-IDs are unique locally and across the node network. Two nodes with the same node-ID cannot be connected in a network.[LDAP]mgrdn
parameter. In Oracle Collaboration Suite, all nodes of an instance share the SYSOP password, which is actually the password of the Calendar instance administrator, an entity stored in OiD for use by the whole server instance. Its password is set when Calendar is installed with Oracle Collaboration Suite.unistop
utility introduced in Chapter 5, "Calendar Server Administration", to bring down the calendar server. Please note that the server must be down in order to create a node successfully.uniaddnode
utility. For full information on use and syntax of unistop
and uniaddnode
, see Appendix E, "Utilities" in the Oracle Calendar Reference Manual.unistart
utility introduced in Chapter 5, "Calendar Server Administration", to restart the calendar server. For full information on use and syntax of unistart
, see Appendix E, "Utilities" in the Oracle Calendar Reference Manual.To create a node with a node-ID of 144 and alias "Publications":
% uniaddnode -n 144 -a publications -w dmpasw uniaddnode: Database initialization done uniaddnode: node [144] has been successfully initialized
An entry similar to the following would now exist in the $ORACLE_HOME/ocal/misc/unison.ini
file. Note that the name and version fields are for internal use and are automatically generated during node creation. The values in these fields must not be modified.
[144] aliases = publications name = N2 version = A.02.61 timezone = EST5EDT
Deleting a node manually requires an advanced knowledge of the calendar server. Before attempting to remove a node, familiarize yourself with the contents of the chapters referenced in the following procedure.
$ORACLE_HOME/ocal/misc/nodes.ini
file and applying the change. Understand the contents of Chapter 7, "Calendar Node Networks", before attempting to do this.uniuser -ex
).$ORACLE_HOME/ocal/db/nodes/<Nx>
directory, where <Nx>
is the value of the name
parameter in the appropriate node section of the $ORACLE_HOME/ocal/misc/unison.ini
file. For example, if you are deleting the node with node-ID 144, <Nx>
is the value of the name
parameter in the [144]
section of the unison.ini
file. For details on unison.ini
parameters, see Appendix C, "Server Parameters" in the Oracle Calendar Reference Manual.$ORACLE_HOME/ocal/misc/unison.ini
file. For example, if you are deleting the node with node-ID 144, delete the [144]
section of unison.ini
.