Hi,
In this page we are going to see how we used to validate the Hyperion components using an URL
We should able to access all the components w.r.t the URL and its respective port number,If we are unable to access the Web URL we should check the Hyperion services status in services.msc
Logs Location :
Daignostics logs : " Oracle/middleware/user projects/epmsystem1/bin/diagnostics/logs"
Server Logs : " Oracle/Middleware/user_projects/domains/EPMSystem/servers "
Below are
the software’s needed to perform this Health check
Java Version : Java
6 or less
Browser : IE 9 or less
MS Office : Office 2013 or less
Smart view : 11.1.2.5.610 or less
This test validates that users can log into the Workspace
and Reporting and shared services, this would indicate that all critical
services are running. This should be the first test to determine if the
application is functioning. If any errors occur here more diagnostics are
needed to determine what is wrong.
Environment
|
URL
|
Training Envt
|
http://servername:19000/workspace/
|
Log into the
Workspace application with your corporate credentials
Navigate ->Administer ->Reporting and Analysis ->Services (Green mark indicates in below screen services are up and running)
Navigate ->Explore
Navigate ->Administer
->Shared Services Console
Environment
|
URL
|
DEV
|
http://servername:10080/easconsole/console.html
|
Click on Launch and login with your user details
Here we are using "admin" details
Validating the Applications and its databases by expanding the
Essbase server a below
Environment
|
URL
|
DEV
|
http://servername:13080/aps/SmartView
|
Url to
connect to the Hyperion Applications using Smart View :
"http://servername:19000/workspace/SmartViewProviders"
Environment
|
URL
|
DEV
|
http://servername:8200/hr/status.jsp
|
Validating the FR Services
No comments:
Post a Comment