4
Managing Nodes

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:

Manually Initializing a Node

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.

Caution:
After manually initializing a node, wait until the replicator process propagates the change to all other nodes before beginning another configuration task. The replicator log file will return the message "transfer complete" when it is finished replicating.

See Also:
"Using Server Process Logs" for more information about the replicator log file

Steps for Manually Initializing a Node

This task can only be performed through the OOMGR command-line interface.

In OOMGR

Start OOMGR on the DCN of the parent domain.

Enter one of the following commands at the OOMGR prompt:

If the new node is to be: Enter the following command:

A member node

IOFCMGR>boot node node=<node_name>
2>DBconnect=<database_connect_string>
3>DBpassword=<database_password>
4>community=<initial_community>;

This causes eMail Server to automatically set the member node status to initializing. When the installation is complete, the status changes to initialized.

A DCN

IOFCMGR>boot domain QualifiedName=<qualified_ name>
2>node=<node_name>
3>DBconnect=<database_connect_string>
4>DBpassword=<database_password>
5>community=<initial_community>;

This causes eMail Server to automatically enter the new DCN name as the ConfigNode attribute of the new domain.

Start OOMGR on the sponsor node.
On the sponsor node, check that the new node record has been replicated. To do this, enter the following command at the OOMGR prompt:
```
IOFCMGR>fetch node name=<node_name>;
```
If the results of the fetch command in step 4 indicate that the database does contain the new node information, run the Configuration Assistant on the computer where the new node will reside.

See Also:
Oracle eMail Server Installation Guide for more information

During the automatic configuration process, you will be asked to select automatic or manual node definition. Select Manual Node Definition.

If the new node is to be:	Enter the following command:
A member node	IOFCMGR>boot node node=<`node_name`> 2>DBconnect=<`database_connect_string`> 3>DBpassword=<`database_password`> 4>community=<`initial_community`>; This causes eMail Server to automatically set the member node status to initializing. When the installation is complete, the status changes to initialized.
A DCN	IOFCMGR>boot domain QualifiedName=<`qualified_ name`> 2>node=<`node_name`> 3>DBconnect=<`database_connect_string`> 4>DBpassword=<`database_password`> 5>community=<`initial_community`>; This causes eMail Server to automatically enter the new DCN name as the ConfigNode attribute of the new domain.

Renaming a Node

You can rename a node if you decide to change your node naming conventions.

Caution:
After renaming a node, wait until the replicator process propagates the change to all other nodes before beginning another configuration task. The replicator log file will return the message "transfer complete" when it is finished replicating.

See Also:
"Using Server Process Logs" for more information about the replicator log file

Steps for Renaming a Node

This task can only be performed through the OOMGR command-line interface.

In OOMGR

Start OOMGR on the DCN containing the node that you want to rename.

Enter the following command at the OOMGR prompt:

IOFCMGR>update node name=<node_name> to name=<new_node_name>;

Deleting a Node

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.

Prerequisites to Deleting a Node

Before deleting a node, back up the system so that you can restore it in case of difficulty.
Export data, such as user accounts, from the node that you are deleting to another node. Refer to "Migrating Directory Accounts to Another Node or Domain" for instructions.

Determine the role the node performs in your system and assign that role to another node using the following guidelines:

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.

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.

Steps for Deleting a Node

This task can be performed through either the Administration Tool GUI, or the OOMGR command-line interface.

In the Administration Tool GUI

Start the Administration Tool GUI.
In the navigation tree, select Messaging System > Nodes > node_name.
In the toolbar, click (Remove).

In OOMGR

Start OOMGR on the DCN containing the node you want to delete.
Enter the following command at the OOMGR prompt:
```
IOFCMGR>delete node name=<node_name>;
```

Moving the SCN

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.

Caution:
After moving the SCN, wait until the replicator process propagates the change to all other nodes before beginning another configuration task. The replicator log file will return the message "transfer complete" when it is finished replicating.

See Also:
"Using Server Process Logs" for more information about the replicator log file

Steps for Moving the SCN

This task can only be performed through the OOMGR command-line interface.

In OOMGR

Start OOMGR on the current SCN.
Enter the following command at the OOMGR prompt:
```
IOFCMGR>move SCN name=<new_SCN_node_name>;
```

Moving a DCN

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.

Prerequisites to Moving a DCN

Replicate domain information from the current DCN to the new DCN. Refer to "Manually Replicating Directory Data" for instructions.

Caution:
After moving a DCN, wait until the replicator process propagates the change to all other nodes before beginning another configuration task. The replicator log file will return the message "transfer complete" when it is finished replicating.

See Also:
"Using Server Process Logs" for more information about the replicator log file

Steps for Moving a DCN

This task can only be performed through the OOMGR command-line interface.

In OOMGR

Start OOMGR on the current DCN.
Enter the following command at the OOMGR prompt:
```
IOFCMGR>move DCN name=<new_DCN_node_name>;
```

Displaying Local Node Information

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:

Node name
Node state
Version number of eMail Server
Default quota (disk space assigned to local accounts)
Time zone (offset from Greenwich Mean Time)
Patch version level (through OOMGR only)
Mail version (through OOMGR only)

Steps for Displaying Local Node Information

This task can be performed through either the Administration Tool GUI, or the OOMGR command-line interface.

In the Administration Tool GUI

Start the Administration Tool GUI.
In the navigation tree, select Messaging System > Nodes > node_name.
In the right pane, select the Local Info tab.

In OOMGR

Start OOMGR on the local node.
Enter the following command at the OOMGR prompt:
```
IOFCMGR>show local all;
```

Changing a Node's Time Zone Value (GMT Offset)

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.

Steps for Changing a Node's Time Zone Value (GMT Offset)

This task can be performed through either the Administration Tool GUI, or the OOMGR command-line interface.

In the Administration Tool GUI

Start the Administration Tool GUI.
In the navigation tree, select Messaging System > Nodes > node_name.
In the right pane, select the Local Info tab.
In the Local Info tab, select the appropriate time zone from the Time Zone list box.

See Also:
"GMT Deviations" for more information about the values to enter
Click Apply.

In OOMGR

Start OOMGR on the local node in question.
Enter the following command at the OOMGR prompt:
```
IOFCMGR>modify local node=<node_name> to timezone=<GMT_offset>;
```
See Also:
"GMT Deviations" for more information about the values to enter

GMT Deviations

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.

City Country Standard GMT Deviation with DST Adjustment

Honolulu

USA

-10

None

San Francisco

USA

-8

-7 (April - October)

Mazatlan

Mexico

-7

None

Winnipeg

Canada

-6

-5 (April - October)

New York

USA

-5

-4 (April - October)

Santiago

Chile

-4

-3 (October - April)

Rio De Janeiro

Brazil

-3

-2 (October - April)

Greenwich

England

0

0

Rome

Italy

+1

+2 (April - October)

Cairo

Egypt

+2

+3 (April - October)

Dubai

UAE

+4

None

Bombay

India

+5.5

None

Dhaka

Bangladesh

+6

None

Saigon

Vietnam

+7

None

Shanghai

China

+8

None

Seoul

South Korea

+9

None

Auckland

New Zealand

+12

+13 (October - April)

City	Country	Standard GMT Deviation	with DST Adjustment
Honolulu	USA	-10	None
San Francisco	USA	-8	-7 (April - October)
Mazatlan	Mexico	-7	None
Winnipeg	Canada	-6	-5 (April - October)
New York	USA	-5	-4 (April - October)
Santiago	Chile	-4	-3 (October - April)
Rio De Janeiro	Brazil	-3	-2 (October - April)
Greenwich	England	0	0
Rome	Italy	+1	+2 (April - October)
Cairo	Egypt	+2	+3 (April - October)
Dubai	UAE	+4	None
Bombay	India	+5.5	None
Dhaka	Bangladesh	+6	None
Saigon	Vietnam	+7	None
Shanghai	China	+8	None
Seoul	South Korea	+9	None
Auckland	New Zealand	+12	+13 (October - April)

Changing a Node's Default Quota

You can change the default disk space quota for storing messages in local accounts on a node. For example, if you need to increase the number of users in your system, you may want to decrease the default quota to have room for more user accounts on a node.

Steps for Changing a Node's Default Quota

This task can be performed through either the Administration Tool GUI, or the OOMGR command-line interface.

In the Administration Tool GUI

Start the Administration Tool GUI.
In the navigation tree, select Messaging System > Nodes > node_name.
In the right pane, select the Local Info tab.
In the Local Info tab, enter the new number of disk space (bytes) in the Default Quota text box.
Click Apply.

In OOMGR

Start OOMGR on the local node.

Enter the following command at the OOMGR prompt:

IOFCMGR>modify local defaultquota=<old_bytes> to defaultquota=<new_bytes>;

Changing a Node's Debug Value

You can change the default debug value for an entire node.

Steps for Changing a Node's Debug Value

This task can be only performed through the OOMGR command-line interface.

In OOMGR

Start OOMGR on the local node.

Enter the following command at the OOMGR prompt:

IOFCMGR>modify local debug=<old_value> to debug=<new_value>;

Changing a Node's State

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).

Steps for Changing a Node's State

This task can be performed through either the Administration Tool GUI, or the OOMGR command-line interface.

In the Administration Tool GUI

Start the Administration Tool GUI.
In the navigation tree, select Messaging System > Nodes > node_name.
In the right pane, select the Local Info tab.
In the Local Info tab, choose a state from the Node State list box.
Click Apply.

In OOMGR

Start OOMGR on the local node.

Enter the following command at the OOMGR prompt:

IOFCMGR>modify local <node_name> to state=["servers only" | open];

4Managing Nodes

Manually Initializing a Node

Steps for Manually Initializing a Node

In OOMGR

Renaming a Node

Steps for Renaming a Node

In OOMGR

Deleting a Node

Prerequisites to Deleting a Node

Steps for Deleting a Node

In the Administration Tool GUI

In OOMGR

Moving the SCN

Steps for Moving the SCN

In OOMGR

Moving a DCN

Prerequisites to Moving a DCN

Steps for Moving a DCN

In OOMGR

Displaying Local Node Information

Steps for Displaying Local Node Information

In the Administration Tool GUI

In OOMGR

Changing a Node's Time Zone Value (GMT Offset)

Steps for Changing a Node's Time Zone Value (GMT Offset)

In the Administration Tool GUI

In OOMGR

GMT Deviations

Changing a Node's Default Quota

You can change the default disk space quota for storing messages in local accounts on a node. For example, if you need to increase the number of users in your system, you may want to decrease the default quota to have room for more user accounts on a node.

Steps for Changing a Node's Default Quota

In the Administration Tool GUI

In OOMGR

Changing a Node's Debug Value

Steps for Changing a Node's Debug Value

In OOMGR

Changing a Node's State

Steps for Changing a Node's State

In the Administration Tool GUI

In OOMGR

4
Managing Nodes