Best Practices for Working with the GroupWise Directory


For a large GroupWise system, here are some good rules to follow:

  • If you perform a large number of operations, such as grafting or modifying multiple users on a domain, GroupWise administrator should be connected to the domain that owns the objects being modified. If you do not do this, you will generate about 50% more administration traffic between domains than you need to. We therefore suggest connecting to the proper owning domain and not doing administration while connected to the primary domain.

  • If your system has a lot of administration messages flowing through it, implement the 2nd Mail Priority Router on the primary domain MTA. To do this, edit the MTA object, go to the Agents Settings page, and check the box named 2nd High Priority Router. This will provide an additional thread for processing admin messages, making bottlenecks at the MTA less likely.

  • Design your GroupWise system so that your primary domain is only doing administrative work. If the primary domain is housing the GroupWise Internet Agent (GWIA), or is a routing hub for all other domains, it might not be efficient enough in servicing GroupWise administration changes. It is ideal to see to it that the primary domain does not own any post offices.

These best practices should be more closely adhered to in systems with a few thousand or more users.



NOVELL GroupWise 7 Administrator Solutions Guide
Novell GroupWise 7 Administrator Solutions Guide
ISBN: 0672327880
EAN: 2147483647
Year: 2003
Pages: 320
Authors: Tay Kratzer

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net