Consultor Eletrônico

Status: Verified

SYMPTOM(s):

After restarting the AdminService, it is not possible to access the OE Explorer browser

"The page cannot be displayed" message when starting OE Explorer

OpenEdge Management remote monitoring has not been enabled with fmconfig -enable

FACT(s) (Environment):

This is the only installation of OE Explorer in the envrionment
AdminServer is running
All Supported Operating Systems
OpenEdge Explorer
OpenEdge 10.1C04
OpenEdge 10.2A01
OpenEdge 10.2B

CAUSE:

The OpenEdge Explorer is not set to autostart with the AdminServer

FIX:

Change the option to start fathom automatically with the AdminServer.

STEPS:

1. Check that the adminserver is still running, if not restart it:
$ proadsv -q

2a. If using OE Explorer 10.2A, first set the environment (this is no longer needed since 10.2B+):

[WINDOWS] proenv > <oee_installdir>\dlc\bin\fathomenv.bat
[UNIX] $DLC/bin/proenv > <oee_installdir>/dlc/bin/fathomenv

2b. Start the fathom components

$ fathom -start

3. Once the OEE Console is open, http://localhost:9090

Select: OPTIONS > Configuration, General
select "Start OpenEdge Explorer automatically"

This action then creates a file: fathom.properties
For OE 10.2B OEE the file is created in: <OE_install_dir>\dlc\properties\fathom.properties
For OE 10.2A OEE the file is created in: <OEE install directory>\dlc\config\fathom.properties
EXAMPLE:
%% Fathom Configuration
%% version 10.2A
%% 28-Jan-2010 14:33:12
[fathom]
autostart=true
fathominitialized=true
resourcesinitialized=false
siteid=pcrcluer3
trenddatabaselocation=local
[remotetrenddatabase]
[webserver]
httpenabled=true
httpport=9090
httpsenabled=false
trustedclients=

Note: The AdminServer will take a bit longer with the additional OpenEdge Explorer architecture that needs to load and initialise, so if you get failure, check with "fathom -query" first and then take the appropriate next actions if necessary.