Configuration of ADM instance to monitor remote Agate instances

[Former Member]

I will be installing ITS version 6.20 Patch Level 20 on Windows 2000 Service Pack 4. I am using Apache version 1.3.26.2 (IBM's version). Web Browser is IE 6.0 SP1.

The confiuration we have is this:

We have 4 Servers: A, B, C ,D

A=Wgate

B=Agate

C=Wgate

D=Agate

We have 3 instances installed on all servers (for failover purposes). The instance names are ADM, IT1, IT2, IT3. On the Wgate servers I have instances ADM, IT1, IT2, IT3. On the Agate servers I have admin AGate intance ADM, IT1, IT2, and IT3 (all but ADM regular instances).

I will do what I read in this post:

After I install my Wgate instances, I edit my registry.xml as in the above link and add my remote agates to the instances. Do I have to manually modify the ItsRegistryWGATE.xml (Wgate WGATE_APACHE_ADM section) to add the Urls for the instances to be monitored? I think adding the remote agates via "Proxy ADM" feature as in note 811339 gives me local performance info, but I need to be able to configure SNC, etc. If I don't manually add the URLs, do the Instances show up under ITS Administration?

I'm getting ready to do this (in a real short period of time starting soon!), so any help someone can give is greatly appreciated.

Message was edited by: Girish Patel

[Former Member]

Hi Girish,

You do not have to add URLs. Adding URLs is for monitoring other unrelated instances.

Just add the agates to the instances and make sure they become visible in the left-hand-side pane of the ADM (on both machines).

This will enable you to go to the other ADM (on the other machine) with the link "Go to Native ADM"

Now if you want to display the instances of the other machines in your overview also, you have to add a Proxy ADM.

On both machines, add a proxy-ADM. This proxy-ADM points to the ADM on the other machine.

[Former Member]

Thanks Tony. I've always added the URLs for the local instances. Are you saying it is only for an instance on another system?

[Former Member]

In a wgate configuration you need the local URLS, otherwise wgate won't catch requests.

In the wgate config file, local Urls are linked to instances through the agate name.

The instances are declared in the instances section.

If you put some foreign URL into the wgate config, then the ADM will display that instance as a remote instance and provide a "Go to native" link, which enables you to link straight to the remote ADM (however, currently, this does not work).