Enterprise Manager in EPM 11.1.2.x...a game of hide and seek!
By Torben Hein -Oracle on Mar 20, 2012
guest article: Maurice Bauhahn:
Users of Oracle Hyperion Enterprise Performance Management 18.104.22.168 and 22.214.171.124 may puzzle why the URL http://<servername>:7001/em may not conjure up Enterprise Manager Fusion Middleware Control. This powerful tool has been installed by default...but WebLogic may not have been 'Extended' to allow you to call it up (we are hopeful this ‘Extend’ step will not be needed with 126.96.36.199). The explanation is on pages 425 and following of the following document:
look at the screen dumps in that section reveals a somewhat scary prospect,
however: the non-AdminServer servlets had all failed (see the red down-arrow
icons to the right of their names) after the configuration! Of course you would
want to avoid that scenario!
A rephrasing of the instructions might help:
the WebLogic AdminServer is not running (in a default scenario that would mean
port 7001 is not active).
- Ensure you have logged into the computer as the
installing owner of EPM. Since Enterprise Manager uses a LOT of resources, be
sure that there is adequate free RAM to accommodate the added load.
- On the
machine where WebLogic AdminServer is set up (typically the Foundation Services
machine), run \Oracle\Middleware\wlserver_10.3\common\bin\config (config.sh on
the 'Extend an existing WebLogic domain' option, and click the 'Next' button.
- Select the
domain being used by EPM System.
- Typically, the default domain is created under /Oracle/Middleware/user_projects/domains and is named EPMSystem.
- Click 'Next'. Under 'Extend my domain automatically to support the following added products'
- place a check mark before 'Oracle Enterprise Manager - 188.8.131.52 [oracle_common]' to select it.
- Continue accepting the defaults by clicking 'Next' on each page until
- on the last page you click 'Extend'.
- The system will grind for a few minutes while it configures (deploys?) EM.
- Start the AdminServer.
- Sometimes there is contention in the startup order of the various servlets
(resulting in some not coming up). To avoid that problem on Microsoft Windows
machines you may start and stop services via the following analogous command line
commands to those run on Linux/Unix (these more carefully space out timings of
- Ensure EPM
WebLogic is up:
- Shut down
- Shut down
- Ensure EPM is up:
Now you should be able to more successfully troubleshoot with the EM tool: