START:
EPM System Installer provides us a single start script under EPM_ORACLE_INSTANCE/bin which is called start.bat depending on the operating system.
To start the system, we start from foundation server, and run the start.bat under the "E:\Oracle\Middleware\user_projects\epmsystem1\bin". Then we pass on to the application server and run the start.bat which also under this or a similar path "E:\Oracle\Middleware\user_projects\epmsystem2\bin".
To check if we have succeeded on starting the application, we could run EPM System Diagnostics.
STOP:
Stoping procedure is quite similar to starting procedure. To stop we could start from the application server then stop the foundation server.
What is EPM System Diagnostics?
Epm System Diagnostics is a tool that makes the essantial checks on a system and produces a report in which it shows its analysis. EPM System Diagnostics can be found on both of the servers(Applciation and Foundation). After the analysis, reports are created int the following path which may change according to the installation "E:\Oracle\Middleware\user_projects\epmsystem2\diagnostics\reports\"
Example:"E:\Oracle\Middleware\user_projects\epmsystem1\diagnostics\reports\instance_report_20140813_034231.html"
These reports can be used to for historical evalution. For example to estimate a time period where we have last succeeded on running some module or when some module just crashed, we could always check these things.
System Diagnostics exe can be found in the EPM_ORACLE_INSTANCE/bin
EXE's and URL's
Oracle Hyperion Shared Services Console: http://machine_name:Port/interop. This is found on the Foundation Server. Example: http://machine_name:28080/interop
EPM Workspace: Http://machine:port/workspace. Workspace URL's can be also found on foundation services.
Example. http://machine_name:19000workspace
Hiç yorum yok:
Yorum Gönder