GroupWise Monitor consists of two components:
Monitor Agent: The Monitor Agent continuously polls other GroupWise agents (POA, MTA, Internet Agent, WebAccess Agent, as well as the Messenger Agents, and GroupWise gateways), gathers status information from them, and displays the status information at the Monitor Agent server console. The Monitor Agent also services requests for agent status information from the Monitor Application.
NOTE:The Monitor Agent server console is available on Windows, but not on Linux.
Monitor Application: The Monitor Application extends the capability of your Web server so that agent status information can be displayed in your Web browser. Two browser-based consoles are available:
The Monitor Web console, provided by the Monitor Application, takes advantage of your Web server’s capabilities to make agent status information available to you when you are outside your firewall.
The Monitor Agent Web console, provided by the Monitor Agent itself, can be used only behind your firewall but provides capabilities not available in the Monitor Web console. This section focuses on using the full-featured Monitor Agent Web console. Specific differences in functionality between the two Web consoles are summarized in GroupWise 8 Administration Guide.
NOTE:The Monitor browser-based consoles are available on both Windows and Linux.
The Monitor Agent and the Monitor Application can run on the same server or on different servers, depending on the needs of your system.
The Monitor Agent and the Monitor Application can run together on a Linux server or a Windows server, as illustrated below:
Figure 7-1 Monitor Agent and Application Installed on the Same Machine
The server where they run together must be a Web server because the Monitor Application is installed into the Web server installation.
The Monitor Agent and the Monitor Application can also run on different servers. In addition to running on a Linux or Windows server, the Monitor Application can also run on a NetWare server in conjunction with a Web server running on that platform, as illustrated below:
Figure 7-2 Monitor Agent Installed on a Windows Machine with the Monitor Application Installed on a NetWare, Linux, or Windows
Security, discussed in the Monitor Security Requirements, might also determine whether you run the Monitor Agent on the same server as the Web server.
GroupWise Monitor can be configured to support the level of security you have established for your Internet/intranet communication.
If you are not concerned about security issues (for example, you only plan to use Monitor on a secured intranet), you can install the Monitor components to any servers that provide access for your GroupWise administrators and that meet the requirements listed in Section 7.2, Monitor System Requirements.
If you plan to use Monitor to provide GroupWise administrators with access to your GroupWise system from anywhere on the Internet (rather than simply within a secured intranet), and you already have a firewall in place to provide security, you have the following options for configuring Monitor:
Install both Monitor components inside your firewall and use a proxy service. See Configuring Monitor with a Proxy Service. This is the recommended configuration.
Install the Monitor Application on a Web server outside your firewall and the Monitor Agent on a server inside your firewall. See Configuring Monitor without a Proxy Service.
If your firewall includes a proxy service, you can install the Monitor Application to a Web server inside your firewall, and the Monitor Agent to another server inside the firewall, as shown in the following illustration.
Figure 7-3 Monitor Installed inside the Firewall
If desired, the Monitor Agent can also be installed to the Web server rather than a separate server, as discussed in Section 7.1.1, One Monitor Server vs. Two.
If your firewall does not provide a proxy service, you need to install the Monitor Application to a Web server that is outside the firewall. Because the Monitor Agent requires direct access to a GroupWise domain directory, it needs to be installed to a server that is located within the firewall. It should be installed to the same server where a domain directory is located.
Figure 7-4 Monitor Installed outside the Firewall
The firewall must allow inbound IP packets to be sent from the Web server to the IP address and port number of the Monitor Agent (for example, 172.16.5.18:8200).
In addition, the firewall must allow outbound IP packets to be sent from the Monitor Agent to the Web server. This requires all high ports (above 1023) to be open to outbound IP packets.