Highlighted
Absent Member.
Absent Member.
1737 views

Configuring the Monitor Agent to Be Independent from a Domain Database

We have 2012 installed and running, since WebAccess changed in 2012 the
GW domain that the Monitor Agent was using was removed.

Since GW Monitor is only supposed to need the domain during
installation, I modified the monitor.xml file to connect over tcpip.

If you want the Monitor Agent to fail over independently from the domain
that it initially accessed to gather information about agents to
monitor, delete the following line in monitor.xml:

HOME_PATH path=“/domain”

and replace it with the following line:

HOME_MTA address=“IP_address” port=“port_number”

where IP_address and port_number are the MTA IP address and port number.


When I do this, GW Monitor does not load.
From the monitor.xml file:
<HOME_MTA address="10.10.19.7" port="7100" />^M
<BIND_ADDRESS address="10.10.19.6" />^M

IP 10.10.19.6 is pingable and a Cluster Address. This is where the
agent is running.
10.10.19.7 is also pingable and has a MTA agent on port 7100.

At the moment, I'm suspicious that the HOME_MTA address is not being
read and connecting to the MTA at that IP.

I've not found a log file that tells me why the agent does not load.

Does anyone else have their GWmonitor connecting to an MTA on a
different IP Address?




Labels (2)
0 Likes
2 Replies
Highlighted
Absent Member.
Absent Member.

Re: Configuring the Monitor Agent to Be Independent from a DomainDatabase

On 5/15/2012 3:39 PM, Brad Beckenhauer wrote:
> We have 2012 installed and running, since WebAccess changed in 2012 the
> GW domain that the Monitor Agent was using was removed.
>
> Since GW Monitor is only supposed to need the domain during
> installation, I modified the monitor.xml file to connect over tcpip.
>
> If you want the Monitor Agent to fail over independently from the domain
> that it initially accessed to gather information about agents to
> monitor, delete the following line in monitor.xml:
>
> HOME_PATH path=“/domain”
>
> and replace it with the following line:
>
> HOME_MTA address=“IP_address” port=“port_number”
>
> where IP_address and port_number are the MTA IP address and port number.
>
>
> When I do this, GW Monitor does not load.
> From the monitor.xml file:
> <HOME_MTA address="10.10.19.7" port="7100" />^M
> <BIND_ADDRESS address="10.10.19.6" />^M
>
> IP 10.10.19.6 is pingable and a Cluster Address. This is where the agent
> is running.
> 10.10.19.7 is also pingable and has a MTA agent on port 7100.
>
> At the moment, I'm suspicious that the HOME_MTA address is not being
> read and connecting to the MTA at that IP.
>
> I've not found a log file that tells me why the agent does not load.
>
> Does anyone else have their GWmonitor connecting to an MTA on a
> different IP Address?
>
>
>
>


I just started Monitor from the command line and it works
ie.. (username and password removed)
/opt/novell/groupwise/agents/bin/gwmon /ipa-10.10.19.6
-httpagentuser-XXXXX -httpagentpassword-XXXX

If I run the same command and specify using the monitor.xml file, it
errors out as shown below.

/opt/novell/groupwise/agents/bin/gwmon
@/mnt/mail/webdom/groupwise/agents/share/monitor.xml
GWMON: Unable to connect to the MTA at 10.10.19.6:7100


Now I would be suspicious that the monitor.xml file is corrupt. But if I
change monitor.xml and point HOME_PATH to a local domain, it works so
the monitor.xml file is good, it just does not work when I remove the
HOME_PATH and use the HOME_MTA address of either a local or remote MTA.

Does anyone else have this working?

0 Likes
Absent Member.
Absent Member.

Re: Configuring the Monitor Agent to Be Independent from a D

I've had same experiences on this. Though I've just installed a new GWMonitor 2012 for a customer and it now worked fine 🙂

My config is now:
<HOME_MTA address="10.147.47.31" port="7100" />

Though I also had to remove the line with HOME_PATH completely (could not just remark it)

Patrick Frontéri # GroupWiseR of Norway # Active part of the OpenHorizons and NetworkPartners.no Collaboration
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.