Status: Verified
GOAL:
How to configure Fathom for remote monitoring
GOAL:
How to enable remote monitoring using Fathom Managemet
GOAL:
How to enable remote monitoring using OpenEdge management
GOAL:
How to use OE Management across multiple different platforms
FACT(s) (Environment):
All Supported Operating Systems
OpenEdge Management 3.1x
OpenEdge Management 3.2x
Fathom Management 2.1A
Fathom Management 3.x
FIX:
Remote monitoring requires, at a minimum, two different machines? one with both a Progress and a Fathom installation, and one with only a Progress installation.
Not limited to monitoring only one remote machine at a time; It is possible to monitor more than one machine, provided that the setup each remote container (Progress-only machine) was done properly.
To set up these machines it is important to have the machine with the OpenEdge/Fathom Management installation up and running with remote monitoring in place before setup the required configuration on any other machine that is running only Progress (and no OpenEdge/Fathom Management).
To set up the first machine:
1) Install OpenEdge 10 or Progress 9.1D or later and the latest service pack.
2) Install OpenEdge Management or Fathom Version 2.1A or higher.
3) When the installation completes, start AdminServer/Fathom.
4) Run the following command in a Proenv prompt:
proenv>fmconfig -enable
Steps in the setup process are listed (as they occur) in the Progress Proenv window, until the setup is complete.
As noted in the Proenv window, the jaas.jar file is copied to the <Progress-install-dir>\<JRE-home-dir>\lib\ext directory.
Additionally, a new directory is installed: <fathom-install-dir>/SonicMQ.
Note that the following actions occur: The Fathom1.FathomAdminServer1.log file is created in the same directory as the AdminServer log file (admserv.log).
The last line of the Fathom1.FathomAdminServer1.log file includes the following text: ?...reconciling complete.?
The admserv.log completes as usual, with the starting of the Fathom probe.
Fathom is now ready to monitor remote systems.
5) To verify that remote monitoring has been set up properly, run the following command in the Proenv window:
proenv>fmconfig -query
The followinng is a sample screen of the results of "fmconfig -query"
=========================================
Fathom remote monitoring properties.
=========================================
Type: Fathom
Status: Enabled
Domain: Fathom1
Container: FathomAdminserver1
Host: hostname
Port: 6835
=========================================
6) Restart the Progress AdminServer. Setting up the remote contaiiner (also known as Progress-only machine) 1) Install OpenEdge 10 or Progress 9.1D or later and the latest service pack
2) Start AdminServer.
3) Run the following command in a Proenv prompt:
proenv>fmconfig -host <fathom-machine-hostname> -enable
in which <fathom-machine-hostname> is the name of the host where OpenEdge/Fathom Management is running.
Steps in the setup process are listed (as they occur) in the Progress Proenv window, until setup is complete.
Additionally, required files are created in the $DLC/java/ext directory.
The following events occur:
The Fathom1.<container-name>.log file is created.
The container name is generated by the Remote Monitoring Configuration Utility; the format of the name is hostname+number?for example, PCTEST1.
The last line of the adminserver log file confirms that startup is complete.
The admserv.log completes as usual with the following text: ?...!+0099completed.?
4) To verify that the remote monitoring has been set up properly, run the following command in the Progress Proenv window:
proenv>fmconfig -query
The followinng is a sample screen of the results of "fmconfig -query"
=========================================
Fathom remote monitoring properties.
=========================================
Type: &.nbsp; Remote
Status: Enabled
Domain: Fathom1
Container: <Remote container server name>
Host: <OpenEdge/Fathom hostname>
Port: 6835
=========================================
5) Restart the AdminServer. .