Automating GroupWise Monitor on Windows and NetWare
Novell Cool Solutions: Feature
By Martin Zinaich
Digg This -
Posted: 8 Dec 2005
Unfortunately, the GroupWise Monitor Agent requires Windows or Linux and cannot be run as a NLM. Setting up GroupWise Monitor to be online automatically, all the time, is not as easy as one might think. The good news is, it is doable. In this configuration the "Agent" is running on a Windows server and the "Application" (Web) piece is running under NetWare Apache. Here are the quick setup steps:
You will find the Installation under the GroupWise distribution \Admin\Monitor directory. Run setup and in the first step just install the Agent:
This needs to be done on the Windows Server itself. The server needs to have the NetWare Client installed (at least to create the NDS Objects). Point the install to a local directory on the server, such as "C:\gwmon". The install will put down the files and create the needed NDS objects.
Now you need to make the changes needed to automate the agent to run on server boot. Since the agent was not written as a Windows service you have to use some extra programs to get it to run as a service. You also want to make a batch file that runs the agent so you can setup and make changes to the Monitor configuration.
- In the Monitor directory (C:\GWMON) create a batch file called Mon.bat with the following line:
- gwmon.exe /ipa-xxx.xxx.xxx.xxx /ipp-7180 /home- /httpuser-httpuserid /httppassword-httppassword
- Where xxx.xxx.xxx.xxx is the IP address of one of your MTA's
- Where 7180 equals the port assigned on the MTA's HTTP access
- Where httpuserid equals the UserID configured for the HTTP access to that MTA
- Where httppassword equals the Password for the HTTP UserID
- Note: you must include the /home- or the Monitor Agent will try to attach to the domain via a mapped drive (and you don't want to do it that way)
- Make sure you use the same UserID and Password for all HTTP agent access
- All of these settings are configured under a MTA?s GroupWise/Agent Settings and GroupWise/Network Address tabs.
Make any other changes under Notification, HTTP and Threshold.
Next select Exit from the Configuration pull down and WAIT until the DOS Batch window closes (this may take a few seconds). Run the batch program again and see if there are any error messages or user input required. Continue this process until the agent starts on its own and requires no user interaction.
Srvany will be used to run the agent as a Windows service. You can read about SrvAny here: http://support.microsoft.com/kb/q137890/
You can get a copy of the two programs here: http://www.electrasoft.com/srvany/srvany.htm
Put the programs in the Windows directory and follow these steps:
- Go to the Windows directory and type: INSTSRV GWMON
- Note here you are installing a service to run SRVANY. We want it called GWMON so we can easily see it under services.
- Under Parameters create two String Values called "Application" and "AppParameters".
- In the Application value enter the complete path to run gwmon.exe:
- Under the AppParameters value enter the parameter values that are used in the mon.bat file:
Go to the Windows Services tool (Control Panel/Admin Tools/Services) and double click gwmon and pick the Log On tab:
Make sure "Allow Service to interact with desktop" is unchecked. You should also be able to check the use local system account.
Click OK and when you are back to the Services screen, Right Click gwmon and pick Start. If all goes well the service should be running. To tell for sure we need to install the Application (Web) portion.
Go back to the Monitor install program and pick the GroupWise Monitor Application:
Enter the IP Address (or DNS name) of the server where you just installed the Agent above:
You will then need to pick a location and type of Web server where you want the Monitor Application to run. In this case the M: drive is mapped to a Novell 6.5 server running Apache and Tomcat:
Chose the defaults for both Apache and Tomcat. Let the install program unload and restart both Apache and Tomcat. You may elect to not change the default home page on the server (most likely because the server may be running other web application) in which case the page you'll need to hit is http://webserver/novell.htm.
From your browser go to http://webserver/novell.htm and see if you get a login screen. If you do you can login with your NDS user ID. If you get the following screen instead, your Monitor Agent isn't running properly on the Windows server:
There are two steps to configuring the Monitor agent on a Windows server:
- Stop the Monitor Agent
- Start the Monitor Agent via the mon.bat batch file
Since not all configuration options are available from the Application (Web) interface, you will need to come to the server to configure certain items.
- Go to Control Panel / Admin Tools / Services
- Find GWMON, right click and pick Stop
- Go to the C:\gwmon directory
- Run the mon.bat file created above
- Make any required changes and check for any startup problems
- When finished pick Exit from the Configuration menu
- Always Wait until the batch file window closes!
- Make sure the mon.bat file has closed and there is no interactive Agent on the screen
- Go to Control Panel / Admin Tools / Services
- Find GWMON, right click and pick Start
Novell Cool Solutions (corporate web communities) are produced by WebWise Solutions. www.webwiseone.com