Novell GROUPWISE 7 - INTEROPERABILITY GUIDE, Руководство пользователя

Страница: 52 / 485

52 GroupWise 7 Interoperability Guide
n
ov
do
cx (e
n)
11
Ju
ly 20
08
5 If you need to install the agents to
sys:\system
on multiple nodes in the cluster:
5a Repeat Step 4 , mapping new drives as needed.
5b If you marked Yes for Consolidate Multiple Startup Files on GroupWise Volume? (under
Agent Clustering Worksheet item 1 ), copy one complete set of agent startup files and the
grpwise.ncf
file to the planned location, then delete all agent startup files, as well as
the
grpwise.ncf
file, from the
sys:\system
directories to avoid future confusion.
The
grpwise.ncf
file includes a
load
command for each instance of each agent. You
will use this information later when you create the load and unload scripts for the volume
resources.
6 Continue with Editing Clustered Agent Startup Files .
3.5.2 Editing Clustered Agent Startup Files
By default, the Agent Installation program creates agent startup files in the agent installation
directory. Each MTA startup file is named after the domain it services, with a
.mta
extension. Each
POA startup file is named after the post office it services, with a
.poa
extension.
Because you selected Configure GroupWise Agents for Clustering during installation, the Agent
Installation program set the MTA
/home startup switch and the POA /home startup switch using the
format:
volume :\ directory
so that the startup files are valid no matter which node the agents are currently running on.
The Agent Installation program also adds a /cluster startup switch to POA startup files to ensure that
GroupWise clients detect the clustering environment and try more persistently to reconnect in a
failover, failback, or migration situation.
One additional manual modification of POA startup files is required for robust functionality in a
clustering environment. Uncomment the
/ip startup switch and provide the secondary IP address of
the GroupWise volume where the post office is located ( Agent Clustering Worksheet item 7 ). This
information is available to the POA in its eDirectory object properties. However, in some failover
situations, reconnection to the MTA is improved when the information is immediately available to
the POA in its startup file.
If you are running the POA in protected memory and your version of NetWare requires it, add the /
user and /password startup switches (under Agent Clustering Worksheet item 8 ) in order to provide a
user name and password that the POA can use to access its post office volume.
If the POA needs to access a remote document storage area, add the /user and /password startup
switches (under System Clustering Worksheet item 12 ) in order to provide a user name and
password that the POA can use to access the volume where the document storage area resides. As an
alternative to startup switches, you can assign the POA object all rights except Supervisor and
Access control, as long as the remote document storage area is located in the same tree with the post
office.
If you have connection problems between the MTA and the POA, you can use the /user and /
password startup switches in the MTA startup file as well.