Oracle eMail Server Administrator's Guide Release 5.2 A86653-01 |
|
If you have a multinode system you can define communities to let eMail Server know which nodes can communicate directly with each other. This means that eMail Server can select the best routes for transferring messages and system information.
Use the following tasks discussed in this chapter to manage communities:
You can create a new community if you need to add one or more nodes that do not use the same networking protocol as your existing node(s).
This task can be performed through either the Administration Tool GUI, or the OOMGR command-line interface.
"Parameters for Creating a Community" for more information about the parameters in this dialog box
See Also:
IOFCMGR>insert community name=<community_name> 2>description=<description>;
See Also:
"Parameters for Creating a Community" for more information about the parameters available with this command |
If you are creating a connect node, make sure it is a member of each community to which it connects and that it uses the communications protocol of each community that it connects.
You must subscribe at least one node to a community to connect the community to your eMail Server system.
This task can be performed through either the Administration Tool GUI, or the OOMGR command-line interface.
See Also:
"Guidelines for Subscribing a Node to a Community" for more information about performing this task |
IOFCMGR>subscribe community node=<node_name> 2>DBconnect=<connect_string> 3>community=<community_name>;
If you are creating a connect node, make sure it is a member of each community to which it connects and that it uses the networking protocols of each community to which it connects.
Message delivery routes (commroutes) specify how information travels from one community to another. If you do not add message delivery routes to and from a community, messages and replicator packages cannot be delivered to or sent from the community.
This task can be performed through either the Administration Tool GUI, or the OOMGR command-line interface.
See Also:
"Guidelines for Creating a Message Delivery Route for a Community" for more information about performing this task |
"Parameters for Creating a Message Delivery Route for a Community" for more information about the parameters in this dialog box
See Also:
IOFCMGR>insert commroute 2>sourcecomm=<source_community_name> 3>targetcomm=<target_community_name> 4>connectcomm=<connect_community_name> 5>cost=<cost>;
See Also:
"Parameters for Creating a Message Delivery Route for a Community" for more information about the parameters available with this command |
You can display message delivery route information to verify message delivery route settings. This command displays the source community, destination community, connect community, and cost.
This task can be performed through either the Administration Tool GUI, or the OOMGR command-line interface.
The message delivery route information appears in the right pane.
IOFCMGR>fetch commroute community=<community_name>;
You can change the name of a community, if necessary.
This task can be performed through either the Administration Tool GUI, or the OOMGR command-line interface.
IOFCMGR>update community name=<community_name> to name=<new_community_name>;
You can unsubscribe a node from a community if you want to change the community to which a node is subscribed, or if you are deleting a community.
Before you unsubscribe a node from a community, determine the services this node provides to the community and assign these services to other nodes.
For example, if the node is a connect node for two or more communities, you must change the message delivery routes so that previously-connected communities remain connected. If you do not change message delivery routes, a community can be disconnected, preventing communication with the rest of the system.
Use the Administration Tool to view the nodes subscribed to a community and to determine the services that a node provides. See the online help in the Administration Tool for more information.
This task can be performed through either the Administration Tool GUI, or the OOMGR command-line interface.
See Also:
"Guidelines for Unsubscribing a Node from a Community" for more information about performing this task |
IOFCMGR>unsubscribe community node=<node_name> 2>community=<community_name>;
Make sure that the node you are unsubscribing from the community is a member of at least one other community. A node must be subscribed to at least one community at all times.
There are two reasons to delete communities:
When you delete a community, you remove it from the eMail Server system.
Before you delete a community, unsubscribe all nodes subscribing to this community. Otherwise, you will receive a message that there are still nodes subscribing to this community and the Delete operation will be abandoned. Refer to "Unsubscribing a Node from a Community" for instructions.
This task can be performed through either the Administration Tool GUI, or the OOMGR command-line interface.
IOFCMGR>delete community name=<community_name>;
To merge communities, you must delete one community after subscribing the nodes of the deleted community to the other.
This task can be performed through the Administration Tool GUI, the Administration Tool command-line, and the OOMGR command-line.
You can only merge communities if the nodes that subscribe to those communities use the same network protocol.
Like message delivery routes, nodes have an associated cost that determines which connect node is used when more than one is available. eMail Server automatically chooses the lowest cost node. Therefore, if there are multiple connect nodes between two communities, you can control the connect node chosen by setting the node costs appropriately.
You assign node cost while installing the node. See the Oracle eMail Server Installation Guide for more information.
|
Copyright © 2001 Oracle Corporation. All Rights Reserved. |
|