Oracle eMail Server Administrator's Guide Release 5.2 A86653-01 |
|
Nodes, or instances, of the eMail Server installation, are the basic building blocks of your eMail Server system. Each node can perform a different role in your system. You assign roles to nodes to optimize your system's performance.
When you first install eMail Server, you create the initial node, called the System Configuration Node (SCN). The SCN stores information about the other system components. The first node is also the Domain Configuration Node (DCN), the node that stores and replicates information about the messaging objects in a domain.
Managing nodes includes the following tasks discussed in this chapter:
If the automatic initialization of a node is disabled for the domain to which you want to add a node, then you must manually initialize the node to create its node record in the database.
This task can only be performed through the OOMGR command-line interface.
IOFCMGR>fetch node name=<node_name
>;
During the automatic configuration process, you will be asked to select automatic or manual node definition. Select Manual Node Definition.
You can rename a node if you decide to change your node naming conventions.
This task can only be performed through the OOMGR command-line interface.
IOFCMGR>update node name=<node_name
> to name=<new_node_name
>;
You can delete a node if you no longer need it, or if you have moved the node information to another host machine. Deleting a node removes its configuration information from the database, but it does not uninstall the eMail Server software.
Service Node Provides | Action |
---|---|
Node is a DCN |
Move the DCN information to another node in the domain. Refer to "Moving a DCN" for instructions. |
Node is an SCN |
Move the SCN information to another node in the community. Refer to "Moving the SCN" for instructions. |
Node is a connect node for two or more communities |
Either make another node the connect node, or change the message delivery routes so that previously connected communities will remain connected. If you do not make one of these changes, a community may be disconnected, preventing communication with the rest of the system. |
This task can be performed through either the Administration Tool GUI, or the OOMGR command-line interface.
IOFCMGR>delete node name=<node_name
>;
You can move the System Configuration Node (SCN) to another node that is on a more powerful host machine or one that is in a different location. Moving the SCN reassigns the SCN capabilities to another node, and the node that was the original SCN becomes a member node.
This task can only be performed through the OOMGR command-line interface.
IOFCMGR>move SCN name=<new_SCN_node_name
>;
You can move a Domain Configuration Node (DCN) to another node in the same domain, if you want to change the node that stores the domain information.
Replicate domain information from the current DCN to the new DCN. Refer to "Manually Replicating Directory Data" for instructions.
This task can only be performed through the OOMGR command-line interface.
IOFCMGR>move DCN name=<new_DCN_node_name
>;
You can display information about your local node to see how the node is currently configured, and to determine whether you need to reconfigure the node. The following information is displayed:
This task can be performed through either the Administration Tool GUI, or the OOMGR command-line interface.
IOFCMGR>show local all;
You may have to change a node's time zone offset from Greenwich Mean Time (GMT) if your time zone changes for any reason. Daylight Savings Time is automatically adjusted by the guardian.
This task can be performed through either the Administration Tool GUI, or the OOMGR command-line interface.
IOFCMGR>modify local node=<node_name
> to timezone=<GMT_offset
>;
Use the following information to help determine your location's Greenwich Mean Time (GMT) deviation. Make a note of your GMT offset for use during installation.
This task can be performed through either the Administration Tool GUI, or the OOMGR command-line interface.
IOFCMGR>modify local defaultquota=<old_bytes
> to defaultquota=<new_bytes
>;
You can change the default debug value for an entire node.
This task can be only performed through the OOMGR command-line interface.
IOFCMGR>modify local debug=<old_value
> to debug=<new_value
>;
You can change the state of a node to servers only if you want to prevent additional users from logging on during times of system maintenance such as backing up the database or upgrading the software. Changing the node state does not disconnect users already logged on. When the system maintenance is finished, you can return the state to open (running).
This task can be performed through either the Administration Tool GUI, or the OOMGR command-line interface.
|
Copyright © 2001 Oracle Corporation. All Rights Reserved. |
|