Configuring Your System to Better Support GroupWise Monitor

The GroupWise Monitor Agent cannot be configured from ConsoleOne. However, the information that GroupWise Monitor uses to monitor your GroupWise system is spread all throughout your system. To make all the features of GroupWise Monitor work, you must enable three components:

• HTTP monitoring of GroupWise agents

• SNMP monitoring of GroupWise agents

• Message logging on GroupWise message transfer agents (MTAs)

Enabling HTTP Monitoring

The chapters in this book regarding the GroupWise post office agent (POA), MTA, GroupWise Internet Agent (GWIA), and WebAccess components all tell how to enable HTTP monitoring. To review, see each of those chapters. But in short, here's how you enable HTTP monitoring on all GroupWise agents.

Following are the steps for enabling HTTP monitoring of GroupWise agents:

1.	Start ConsoleOne.
2.	Go to the Properties of the agent (MTA, POA, WebAccess, or GWIA) you want to enable HTTP monitoring on, and go to the Network Address option under the GroupWise tab.
3.	Enter the HTTP port value.

Note

Make sure that the HTTP port value is in fact the HTTP port on which your agent is listening. If you are using the /HTTP* switches in the startup files of your agents, you might not be using the same values as are specified in ConsoleOne. If a GroupWise agent has /HTTP* switches in its startup file, those switches take precedence over the HTTP values in ConsoleOne. The GWIA keeps the /HTTP* switches in its GWIA.CFG file; that's where they should be for the GWIA. For all other agents, though, it is not recommended that you use the /HTTP* startup switches in your agent's startup files, because managing them is more difficult than doing the job through ConsoleOne.

After you have completed adding HTTP monitoring support, you will need to restart the GroupWise agents for which you enabled HTTP monitoring.

Enabling SNMP Monitoring

All the GroupWise agents can be monitored via SNMPin fact, SNMP monitoring is a default on all GroupWise agents. The GroupWise POA can be configured to disable SNMP monitoring, though, so here's how to enable SNMP monitoring on the GroupWise POA.

Follow these steps to enable SNMP support for a GroupWise POA:

1.	Run ConsoleOne.
2.	Go to the Properties of the POA object.
3.	Go to the Agent Settings property page.
4.	Slide down to the bottom of the Agent Settings property page and check the Enable SNMP check box, as shown in Figure 18.4. Figure 18.4. Enable SNMP by checking the Enable SNMP check box and entering the GET string
5.	Enter the word public (case-sensitive) in the SNMP Community "Get" String field below the Enable SNMP check box.

Note

A discussion of SNMP community get strings is outside the scope of this book. You are welcome to change the SNMP Community "Get" String field according to your organization's SNMP guidelines.

Enabling MTA Message Logging

To enable MTA message logging, follow these steps:

1.	Run ConsoleOne.
2.	Edit the properties of the MTA object.
3.	Go to the Message Log Settings property page.
4.	Change the Message Logging Level field so that it says Full.
5.	Don't fill in the Message Log File Path field unless you want to change the message logging path. By default, the MTA will place the message log files in the DOMAIN\MSLOCAL\MSGLOG directory.
6.	Check all check boxes except Track Administrative Messages. Rarely will you need to track ADMIN-type messages through the system.
7.	Set a value, such as 30 days, for the Delete Report After field.

Figure 18.5 shows MTA message logging enabled.

Figure 18.5. Enabling MTA message logging is accomplished from the Message Log Settings property page

Now the MTA is logging information that is very useful when tracking message flow. These logs are separate from the typical MTA logs.