Since OpenEdge 11.7, 12.x a new system property
fathomRestrictedMode, provides the ability to
disable OEM features and use only
OEE functionality when an
OE Enterprise Advanced RDBMS or
OpenEdge Management license is installed. This feature does not unbind the fathom plugin from the current OpenEdge install, nor does it stop the fathom plugin from starting as without it the Web Server doesn't start.
OpenEdge 11.7: To disable OEM functionality and make Fathom run as OEE:
1. Stop the AdminServer, it is not sufficient to only stop the fathom webserver
$ fathom -stop
$ proadsv -stop -keepservers
2. Dump the configuration database which holds customised jobs/reports/Shared Collection and views/resource configuration offline, with an Admin privileged user
$ fathom -dump fathom.xml -user admin -password admin
3. Disable OpenEdge Management functionality
Edit: {DLC}/fathom.init.params
fathomRestrictedMode=true
4. Restart the AdminServer / Fathom and access the OE Console
OpenEdge 12.x: To disable OEM functionality and make Fathom run as OEE:In OpenEdge 12, OEM is a separate independent process from the AdminServer running on as a PASOE instance webapp.
1. Open proenv and change directory
$ proenv> cd %OEM%\bin\
2. Stop the fathom webapp:
$ proenv> fathom -stop
3. Enable the fathomRestrictedMode property in {OEM}\conf\jvm.properties, add the line:
-DfathomRestrictedMode=true
Save the file
3a. This step only needs to be performed when registered as a Service which is the default for Windows installations.
$ proenv> tcman service unregister
$ proenv> tcman service fathom_12.2 register
4. Start the fathom web app
$ proenv> fathom -start
When the fathom plugin starts up after restricting fathom features:
- The following message is written to the admserv.log :
Fathom is running in restricted mode. OpenEdge Management functionality is disabled.
- The fathomRestrictedMode option explicitly disables all OEM functionality and makes the OE Console behave as if it were OpenEdge Explorer in the web console. This includes, but not exclusively:
- Jobs are disabled and the Jobs menu is hidden
- Reports are disabled and the Reports menu is hidden
- Alerts are disabled and the Alerts menu is hidden
- Library menu is hidden
- Collections menu is hidden
- Trending is disabled
- Polling is disabled
- Alerting is disabled
- System resource types such as network, file, memory, cpu are hidden
- SNMP adapter won't be loaded
- Third party web applications will not be loaded
- Resource status will report "Running" instead of "Passed|Failed"
To re-enable OEM functionality
This Enhancement was engineered specifically for customers who requested the ability to disable OEM and only use OEE. It is not recommended to switch between OEE/OEM functionality. Set the required license feature as needed and leave it.
Removing this switch or setting it to fathomRestrictedMode=false, will not automatically re-enable any resources.
Re-enabling OEM functionality will require either:
- Manually editing all the options that re-enable this functionality.
- Loading the dump of the configuration database taken with 'fathom -dump' before OEM functionality was disabled.
- Delete the content of <OEM>\config\configdb\*.* to clear out the configuration, then restart the AdminServer which will create a new configdb database . For further information refer to Article How to reclaim space used by the graph/activity database
