Understanding the Architecture Behind the Client Options Interface


As Chapter 3, "Understanding the GroupWise Directory," noted, the GroupWise administration snap-ins write changes directly to the GroupWise domain database to which the snap-ins are connected. For client options to take effect, however, the changes must propagate all the way down to the GroupWise user database, USERxxx.DB. Here is the flow of events:

  1. The administrator makes a change to client options.

    For example, imagine that you have unchecked the box labeled Allow Shared Folder Creation, and then locked that setting. Assume that the post office object was selected at the time you made the change. This means that the setting will apply to the entire post office.

  2. The GroupWise administrator snap-ins write the change to the GroupWise domain database and create an administration update file to propagate this change to the post office.

  3. The MTA transmits this file to the POA.

  4. The POA administration thread writes this change to the post office database.

  5. A POA writes (or merges) the change to the preferences capsule of the user database, or to the user databases that are affected by the changes in client options.

Note

The GroupWise client reads the preferences capsule of the user database when the client initially logs in. This means that if you make a client option change, the users will not normally see this change until they have logged out and back in with the GroupWise client.




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