GroupWise 8 Best Practices

From MicroFocusInternationalWiki
Revision as of 16:42, 23 June 2010 by Timscotland (Talk | contribs) (Frequently Asked Questions)

Jump to: navigation, search


This guide serves as a set of considerations and guidelines for Novell® GroupWise® administrators.

It is not a comprehensive instruction set and is not intended to replace product manuals. Administrators using this guide should consult product documentation, technical information documents (TIDs), and online help for further instruction regarding each of the guidelines offered here.

It is intended that this will be a “living document”; additional content will be added as it becomes available and content will be modified as necessary.

Please click on the links below for further information about each section.

GroupWise 8 Design

This section contains best practice information on the underlying architecture, system design and service design to assist GroupWise system administrators and consultants to deploy new systems or redesign existing system in the most efficient manner.

GroupWise 8 System Administration

GroupWise system administration is all done through ConsoleOne. Please ensure that you only use the latest version of the ConsoleOne snapins with 1.3h. However, client file caching should be disabled on all platforms. This setting can be found in the Protocol section of the System Settings of the Novell Client.

Within the administration section you will find the optimised settings for Agents, Gateways and servers that should be employed to ensure maximum efficiency and operational stability.

GroupWise 8 Security

GroupWise is and has always been the collaboration system of choice for security conscience organisations. With the passing of time, security protocols and deployment methods change. With these changes, keeping up with the latest security configuration becomes ever more important.

This Security section contains best practices for the optimal settings that ensure that a GroupWise system remains secure.

GroupWise 8 Good and Bad Habits

The real meat of this best practices wiki.

GroupWise 8 Moving GroupWise Users

Moving users used to be a problematic task within GroupWise, however since the release of GroupWise 6.5 this process has been dramatically improved.

GroupWise 8 Troubleshooting

There are numerous tools available for the management, troubleshooting and reporting available

Common issues and problem resolution.

Frequently Asked Questions

How many users can I have in a Post Office?
Discussed in the Architecture & Sesign Section
What hardware does Novell recommend?
The Design System section discusses this and Virtualisation
How many messages can a post office and domain handle in an hour?
Depends upon your hardware... Discussed here
Why should I deploy GroupWise services on Linux?
Platform options
How many users can one WebAccess server handle?
In the past where NetWare was prevalent, the limitation placed on a WebAccess system was the number of threads that a NetWare server could host and the number of concurrent users per thread. In the real world this proved to be 2-3 users per thread and 250 threads maximum (?).
Both Apache and Tomcat come from the Linux world and have proven that scalability on Linux is considerably better than NetWare with 100 concurrent users per thread regularly seen in the real world. That would imply that the maximum would be 25,000 per WebAccess server; By that point there may be other factors to consider such as high availability, load balancing and security coming into play. A maximum of 5,000 concurrent users per Agent or Application (Half that if both on the same server) would be a good working number.


How to enter a new Enhancement Request

GroupWise 8 Active Partners

This page contains an incomplete list of third party application vendors for GroupWise 8