Supporting Forced Mailbox Caching

GroupWise client users have the option to download their GroupWise mailboxes to their workstations so they can work without being continuously connected to the network. This is called Caching mode. For more information, see Caching Mode.

When client users change to Caching mode, the contents of their mailboxes must be copied to their hard drives. This process is called priming the mailbox. If users individually decide to use Caching mode, the POA easily handles the process.

If you force all users in the post office to start using Caching mode, as described in Allowing or Forcing Use of Caching Mode, multiple users might attempt to prime their mailboxes at the same time. This creates a load on the POA that can cause unacceptable response to other users.

To configure the POA to handle multiple requests to prime mailboxes:

  1. In ConsoleOne, browse to and right-click the POA object > click Properties.

  2. Click GroupWise > Agent Settings to display the Agent Settings page.


    Agent Settings property page

  3. Scroll down to the bottom of the list.

  4. Set Max Thread Usage for Priming and Moves as needed.

    By default, the POA allocates only 20% of its TCP handler threads for priming mailboxes. In a default configuration, this would be only one thread. You might want to specify 60 or 80 so that 60% to 80% of POA threads are used for priming mailboxes. You might also want to increase the number of TCP handler threads the POA can start in order to handle the temporarily heavy load while users are priming their mailboxes. See Adjusting the Number of POA Threads and Connections for Client/Server Processing.

  5. Click OK to save the new setting.

    ConsoleOne then notifies the POA to restart so the new setting can be put into effect.

Corresponding Startup Switches
You could also use the /primingmax switch in the POA startup file to configure the POA to handle multiple requests to prime mailboxes.