Slow GroupWise Performance

  • 3394208
  • 02-Apr-2008
  • 26-Apr-2012


Novell GroupWise 6.5
Novell GroupWise 7


How to create a second POA for one Post Office on the same server to resolve slow performance issue
Slow GroupWise Performance
GroupWise performance is really slow
TCP/IP threads and Message Handling threads are maxing out
Users not able to login in timely fashion


Corrective Actions:
Our goal is to distribute load between two POA agents so that the overall performance of the Post Offices increases.

1. Follow the steps listed below to configure the existing POA to do Message Processing. This POA will only be responsible to process messages for the Post Office and it will not accept any TCP/IP Client/Server request

  • Launch ConsoleOne
  • Right Click on the POA Object and select Properties
  • Click the GroupWise | Agent Settings
  • Uncheck "Enable TCP/IP (for Client/Server)
  • Also uncheck "Enable IMAP" and "Enable SOAP" if they are checked
  • Make sure "Message File Processing" is set to All
  • Click Apply and Close
2. Follow the steps listed below to Configure a new POA to handle the TCP/IP Client/Server requests. This POA will serve only Client/Server requests and will not be responsible for Message Processing

  • Launch ConsoleOne
  • Right Click on the Post Office object and click New | POA
  • Specify the name as POA1
  • Put a check mark on"Define additional properties"
  • Click OK
  • Click GroupWise | Agent Settings
  • Change the "Message File Processing" to Off
  • Make sure Enable Client/Server is selected
  • If needed, put a check mark on "Enable IMAP" and "Enable SOAP"
  • Click GroupWise | Network Address
  • In the Network Address tab, specify the same IP Address that is been used by the first POA i.e the ip address of the server. Make sure that the "Message Transfer" is 0
  • In the QuickFinder tab, disable the "Enable QuickFinder Indexing”. We would like to disable this task as it is assigned to the first POA
  • In the Maintenance tab, disable "Enable Automatic Database Recovery”, "Perform User Upkeep” &"Generate Address Book for Remote”
  • In the Schedule Task tab, keep the default schedule task unselected as those are been performed by the first POA
3. Installing additional Post Office Agent on the server.
NetWare Server
  • Make a copy of the existing POA startup file and save it with a different name
  • Edit the first POA startup file and put a "/name-POA" without quotes at the end of the file
  • Edit the second POA startup file (that was just created) and put a "/name-POA1" without quotes at the end of the file
  • Edit GRPWISE.NCF file and put a load statement for the new POA as mentioned below
Load"pathToPOA.NLM" @"pathToNewPOAFile"
eg Load sys:\system\gwpoa.nlm @sys:\system\xyz.poa
Note- xyz.poa is the startup file for the new POA.
Windows Server
  • From the Software Distribution Directory à Agents à Install.exe
  • Specify the Post Office name as something different than the original name. But the path to the Post Office database will be the same as the original..
  • Edit the new POA file that gets created after running the above install and put a"/name-POA1" without quotes at the end of the file
  • Edit the second POA startup file (that was just created) and uncomment the /nomtp switch

  • Edit the original POA file and put a "/name-POA" without quotes at the end of the file