Installing the Linux Monitor Agent

1. Make sure that LDAP is running on your eDirectory server and that it is configured to accept login from the Monitor Agent Installation program (worksheet item 15)

   The Installation Advisor requires eDirectory access in order to create the Monitor objects in eDirectory. The Installation Advisor uses LDAP to gain the required access.

2. At the Linux server where you want to install Monitor, open a new terminal window, then enter the following command:

   xhost + localhost

   If you cannot execute this command because the X Window System is not running on the Linux server, see Installing the GroupWise Agents Using the Text-Based Installation Advisor, which describes the process for the POA and the MTA.

3. Become root by entering su and the root password.

4. Change to the root of the GroupWise 6.5 for Linux Administrator CD.

5. Start the GroupWise Installation Advisor.

   ./install

6. Select the language in which you want to run the Installation Advisor and install software, then click OK.

7. Click Install Products > GroupWise Monitor > Install GroupWise Monitor.

   The Monitor Agent software is installed to the bin and lib subdirectories of /opt/novell/groupwise/agents.

8. When the file copy is complete, click OK.

9. Continue with Configuring the Linux Monitor Agent.

Configuring the Linux Monitor Agent

1. After the Monitor Agent files have been installed, click Configure Monitor.

   The Monitor Agent installation and configuration steps are separate so that you can install updated agent software without needing to repeat the agent configuration steps.

   
   

2. Review the Introduction, then click Next.

3. Accept the License Agreement, then click Next.

4. Browse to and select a domain directory (worksheet item 5) where the Monitor Installation program can access a domain database, then click Next.

   This allows the Monitor Agent to automatically discover all agents in your GroupWise system and start monitoring them.

5. Click Exit to complete the installation.

6. Continue with Installing and Configuring the Monitor Application.

Installing and Configuring the Monitor Application

1. After installing and configuring the Monitor Agent, click Install Monitor Application with Apache and Tomcat.

   This installs a version of Apache and Tomcat specifically for use with GroupWise. Apache files are installed under /var/opt/novell/http and /etc/opt/novell/http. Tomcat files are installed under /var/opt/novell/tomcat4 and /etc/opt/novell/tomcat4.

   or

   If you want to use an existing Apache/Tomcat installation, click Install Monitor Application.

2. Accept the License Agreement, then click Next.

3. Specify the IP address or DNS hostname of the Linux server where you are installing the Monitor Application (worksheet item 4), then click Next.

   The default port number of 8200 is typically acceptable, unless another program is already using that port.

4. Click Next to accept the default Apache and Tomcat locations that were established in Step 1.

   or

   Specify the locations of Apache and Tomcat installations on your system, then click Next.

5. Fill in the LDAP information (worksheet item 15), then click Next.

6. Browse to and select the eDirectory context where you want the Monitor Application objects to be created (worksheet item 19), then click Next.

   The GroupWise Monitor Application objects are GroupWiseMonitor and MonitorProvider.

7. Click Exit to complete the configuration.

8. Continue with Starting the Web Server.

Starting the Web Server

If you installed Apache and Tomcat along with the Monitor Application, follow the instructions below to start your Web server. If you did not install Apache and Tomcat along with the Monitor Application, restart Apache and Tomcat on your system.

1. Make sure you are logged in as root.

2. If you have other instances of Apache and Tomcat running on this server, bring them down before you start the new versions you just installed.

3. Change to the /etc/init.d directory.

4. Start Tomcat.

   ./novell-tomcat4 start

5. Wait until Tomcat is all the way up.

6. Start Apache.

   ./novell-httpd start

7. Continue with Starting the Linux Monitor Agent for the First Time.

Starting the Linux Monitor Agent for the First Time

1. Make sure you are logged in as root.

2. Make sure you know the path to a domain directory where a domain database (domain.db) is located or the IP address of a server where the MTA is running.

3. Change to the GroupWise agent bin directory.

   cd /opt/novell/groupwise/agents/bin

4. Use one of the following commands to start the Monitor Agent:

   ./gwmon --home /domain_directory &
   ./gwmon --ipa IP_address --ipp port_number &

   The --home startup switch specifies a domain directory where the Monitor Agent can access a domain database.

   The --ipa startup switch specifies the IP address of a server where an MTA is running, which is another way for the Monitor Agent to obtain information from a domain database. The --ipp startup switch specifies the port number on which the Monitor Agent listens for incoming service requests.

   The ampersand (&) causes the Monitor Agent to run in the background, so that the terminal window you started it in is again available for use.

   A message indicates that the Monitor Agent is polling the domain you specified.

   You can also start the Monitor Agent using its startup script (/etc/initd/grpwise-ma).

   The Monitor Agent does not have a --show switch. The Monitor log file (mmddmon.nnn) for status messages is located in the /var/log/novell/groupwise/gwmon directory. The log file name includes the month and day when it was created, along with an incrementing extension to accommodate multiple log files on the same day. The Monitor Agent can also be monitored from your Web browser.

5. Continue with Accessing the Monitor Web Console on Linux.

Accessing the Monitor Web Console on Linux

1. In your Web browser, view the following URL:

   http://network_address/gwmon/gwmonitor

   
   

   For instructions on protecting the Monitor Agent Web console with a password, see "Configuring Authentication and Intruder Lockout for the Monitor Web Console" in "Monitor" in the GroupWise 6.5 Administration Guide.

Starting the Linux Monitor Agent on System Startup

If you selected Launch Monitor Agent on System Startup in the Monitor Agent Installation program, your system was configured so that the Monitor Agent would start automatically. The Monitor Installation program always creates a grpwise-m a startup script in /etc/init.d for starting the Monitor Agent. To enable automatic startup, the Monitor Installation program creates symbolic links named S99grpwise-ma in the rc3.d and rc5.d directories so that the Monitor Agent can load on startup into runlevel 3 or 5, depending on the configuration of your Linux system.

When the grpwise-ma script runs and starts the Monitor Agent, it reads the Monitor Agent configuration file (monitor.xml) in /opt/novell/groupwise/agents/share to check for configuration information.

Stopping the Linux Monitor Agent

When you start the Monitor Agent with the grpwise-ma startup script, you can also use the script to stop it.

1. Make sure you are logged in as root.

2. Change to the /etc/init.d directory.

3. To stop the Monitor Agent, enter the following command:

   ./grpwise-ma stop

4. To confirm that the Monitor Agent has stopped, enter the following command:

   ps -eaf | grep gwmon

   The only gwmon process ID you should see listed is the one for the grep command.

When you start the Monitor Agent manually (without using the grpwise-ma script), use the standard Linux kill command to stop it.

1. Make sure you are logged in as root.

2. Determine the process ID of the Monitor Agent.

   ps -eaf | grep gwmon

   The PIDs for all gwmon processes are listed.

3. Kill the first gwmon process in the list.

   kill first_process_ID

   It might take a few seconds for all gwmon processes to terminate.

4. Repeat the ps command to verify that the Monitor Agent stopped.

Completing the Monitor Installation on a UNIX Apache Web Server

The Monitor Installation program copies the following files to the location you specified: gwmonitor.tar, gwmonitordocs.tar, gwmonitorjars.tar, gwmonitorservlets.tar, index.html, and servlets.properties. It also creates a palm subdirectory for the Palm Query Application (PQA) file it creates.

To complete the installation and configuration process:

1. Using the tar -xvf command, extract the following tar files to the specified locations:

   • gwmonitor.tar: Extract to the root of the UNIX server. A /novell directory is created for the files.

   • gwmonitordocs.tar: Extract to the Apache document root directory (for example, /usr/local/apache/htdocs).

   • gwmonitorservlets.tar: Extract to the Tomcat ROOT/WEB-INF/classes directory (for example, /usr/local/tomcat/webapps/ROOT/WEB-INF/classes).

   • gwmonitorjars.tar: Extract to the Tomcat ROOT/WEB-INF/lib directory (for example, /usr/local/tomcat/webapps/ROOT/WEB-INF/lib).

2. Modify the Tomcat web.xml file to include the following information. The web.xml file is in the Tomcat ROOT/WEB-INF directory.

   <web-app> 
    
   <servlet> 
   <servlet-name>gwmonitor</servlet-name> 
   <servlet-class>com.novell.gwmonitor.MonitorServlet</servlet-class> 
   <init-param> 
   <param-name>Config</param-name> 
   <param-value>/novell/gwmonitor/gwmonitor.cfg</param-value> 
   </init-param> 
   <load-on-startup> </load-on-startup> 
   </servlet> 
    
   </web-app>

3. Modify the gwmonitor.cfg file, located in the /novell/gwmonitor directory at the root of the UNIX server, to change the Templates.path setting to point to the templates.

   For example, change the following line in webacc.cfg:

   Templates.path=/java/servlets/com/novell/gwmonitor/templates

   to

   Templates.path=/usr/local/tomcat/webapps/ROOT/WEB-INF/classes/com/novell/gwmonitor/templates

4. In the gwmonitor.cfg file, verify that the paths for the following settings point to valid directories. Typically, these directories reside in the /novell/gwmonitor directory, but you can relocate them if desired. Refer to the comments in the gwmonitor.cfg file for explanations of each of these settings.

   Log.path=/novell/gwmonitor/logs 
   Security.Timeout.path=/novell/gwmonitor/users

5. Copy the index.html file to the Apache document root directory (for example, /usr/local/apache/htdocs). You can replace your Web server's current default home page with this file, or you can rename the file and link to it from your current default home page.