If you’ve used GroupWise 5.5 for groupware on your network, you know how fast and reliable it is. To keep it that way, however, you need to take care of it. In this Daily Feature, I’ll show you a few things you can do to keep GroupWise humming along.

Tuning the GroupWise database
For all of its e-mail, scheduling, and groupware capabilities, GroupWise is basically a huge database that resides on your NetWare server volumes. Like any database, it needs to be checked and optimized regularly for best performance. The easiest way to do this is to use the Scheduled Event in the Post Office Agent that runs Mailbox/Library Maintenance. If you have not disabled this event, it will keep your user and message databases in good working condition.

Before running the Mailbox/Library Maintenance agent, make sure you have a current backup of the entire GroupWise system. The best way to back it up is to shut down all of the agents, Post Office Agent (POA) and Message Transfer Agent (MTA), locally and any other servers accessing the GroupWise database. You don’t need to back up the whole volume—just the domain and post office directories.

After you’ve backed up your GroupWise database, you’re ready to begin. The first thing you should do is rebuild the primary domain and any secondary domains. To do so, open NetWare Administrator and select the Domain object. Next, select GroupWise Utilities from the Tools menu and click System Maintenance. Finally, select Rebuild Database and click Run.

Next, you need to rebuild all the post offices in each domain. To do so, select the Post Office object in NetWare Administrator. Next, select GroupWise Utilities from the Tools menu and click System Maintenance. Then, select Rebuild Database and click Run. At this point, you can start the GroupWise Agents and allow users to log in to GroupWise.

Two ways to optimize your Message Store
There are two ways to tune your GroupWise server’s Message Store. First, you can have the server do the work. To begin, select all of the user objects in a post office in the NDS View. Next, select GroupWise Utilities from the Tools menu and click Mailbox/Library Maintenance. Select Structural Rebuild from the Action pull-down menu, then select Run.

The second way you can optimize your Message Store is to use the GWCheck utility, which you’ll find in the GroupWise software distribution directory. When you use GWCheck, your workstation performs operations to server files. This approach can work well if you have a fast workstation because it doesn’t tax the server resources as much.

Purging GroupWise files and directories
GroupWise creates, deletes, stores, and updates a lot of files when you have many users. Because it does, running a purge regularly on the GroupWise MTA and POA directories is a good idea. The best way is to change the directory attributes on all the folders and subfolders to Purge Immediate.

To purge files, open a command prompt on your workstation and change directories to the GRPWISE.POA directory on your server’s SYSTEM volume. Then, type FLAG *.* P /do /sub and press [Enter].

Making GroupWise run on dual processors
If you have NetWare 4.11 with SP6 or later, or any version of NetWare 5 and fairly current support packs, you can make GroupWise use the secondary processor. The easiest way to do this is by editing the domain MTA configuration file (DOMAIN.MTA) and the post office configuration file (POSTOFFICE.POA).

Scroll down to the section for Symmetric Multiprocessing (SMP). By default, the /NOSMP switch is set. Remark this line out or just change it to read /SMP. Then, save and restart MTA and POA. You will notice the POA and MTA threads running on the secondary processor.

You can verify this by looking at your server’s console monitor. On the monitor screen saver, you’ll see both the red worm you normally see and a blue worm.

To protect all of the information you have in your GroupWise System, perform maintenance to make sure your system stays healthy. You’ll also gain speed and reliability.
The authors and editors have taken care in preparation of the content contained herein but make no expressed or implied warranty of any kind and assume no responsibility for errors or omissions. No liability is assumed for any damages. Always have a verified backup before making any changes.