Disabling the OpenEdge Explorer (OEE) or Management (OEM) fathom.plugin from
autostarting with the AdminServer can be achieved using either of the following Methods:
Option 1: In the OpenEdge Console go to
Options -> General. Uncheck the check-box to have OpenEdge Explorer auto start.
This action updates the
fathom.properties, autostart value to false (See Option 2 below)
Option 2: Manually, edit the
fathom.properties file and set
autostart to
false under the
[Fathom] section.
For
OpenEdge 10.2B and later, the file is created in:
<OE_install_dir>\dlc\properties\fathom.propertiesFor
OpenEdge 10.2A and earlier, the file is created in:
<OEE install directory>\dlc\config\fathom.properties
[fathom]
autostart=false
fathominitialized=true # just means it went through the initial setup page in the OE Console
Additionally, edit the
<OE_install_dir>/fathom.init.params property file, ensure that
fathomEnabled is
true. Otherwise when
fathomEnabled=
false:
- The fathom plugin will not be able to be started after the AdminServer has started with: $ fathom -start
- As a result, the Jetty WebServer is disabled and will result in the loss of OpenEdge Console functionality, leaving only command line utilities for managing database and ubroker components (unless this is the intention)
SET fathomEnabled=true
The Fathom plugin can then be manually started once the AdminServer has started:
$ proadsv -query -port 20931
$ fathom -start -port 20931
$ fathom -query -port 20931
Where: port
20931 is the default AdminServer listening port.
Since OpenEdge 11.7, a
fathomRestrictedMode system property was added to the the product in order to provide the ability to disable OEM and use only OEE functionality when the OE Enterprise Advanced RDBMS or OpenEdge Management license are installed. For further details refer to Article:
