The GroupWise 6.x Windows client and the GroupWise 6.5 Cross-Platform client both use client/server access mode to the post office. This requires a TCP/IP connection between the GroupWise clients and the POA in order for users to access their mailboxes. Benefits of client/server access include:
Load Balancing: The workload is split between the client workstation and the POA on another server. The POA can perform a processor-intensive request while the client is doing something else.
Database Integrity: The GroupWise client does not need write access to databases in the post office. Therefore, client failures cannot damage databases.
Reduced Network Traffic: Requests are processed on the POA server and only the results are sent back across the network to the client workstation.
Tighter Security: Client users do not need to log in to the server where the post office is located. This eliminates the need for users to have write access to the post office directory.
Scalability: More concurrent users can be supported in a single post office.
Platform Independence: The GroupWise client on any platform can access the post office by way of TCP/IP communication with the POA.
Simplified Client Connections: The GroupWise client can communicate with any POA in the GroupWise system. Any POA can then redirect the client to connect to the correct POA for the users' post office.
Historical Note: In GroupWise 5.x, the GroupWise client allowed the user to enter a path to the post office directory to facilitate direct access mode. The GroupWise 6.x client no longer offers the user that option. However, you can force the GroupWise 6.x client to use direct access by starting it with the /ps switch and providing the path to the post office directory. For information about alternatives to client/server access mode, see the GroupWise 5.5 Agent Setup Guide.