New Features in Release 11.1.2.0
EPM System Installer now installs these items:
o WebLogic Server (replaces Apache Tomcat as the embedded Java container)
o Oracle HTTP Server (replaces Apache Web server as the embedded Web server)
Most EPM System products have adopted Oracle Diagnostic Logging (ODL) as the logging mechanism. The ODL framework provides uniform support for managing log files, including log file rotation, maximum log file size, and the maximum log directory size. For more information, see the “Using EPM System Logs” chapter of the Oracle Hyperion Enterprise Performance Management System Installation and Configuration Troubleshooting Guide.
Oracle Configuration Manager (OCM) integrates with My Oracle Support and provides configuration information for Oracle software. It assists in the troubleshooting, maintenance, and diagnostics of your EPM System deployment. For more information about Oracle Configuration Manager, see the Oracle Hyperion Enterprise Performance Management System Installation and Configuration Guide.
This release allows the system administrator to reconfigure logical references to existing, deployed Web applications without redeploying them.
With this release, many EPM System products support host names that resolve to IPv6 addresses. See the Oracle Hyperion Enterprise Performance Management System Certification Matrix. IPv4 support (both host name and IP address) remains unchanged from earlier releases.
EPM supports the following types of SSL configuration:
o Full SSL Deployment (including data access)
o SSL Terminating at the Web Server
o SSL Accelerators (off-loading)
o Two-way SSL
For more information on the SSL configurations, see the Oracle Hyperion Enterprise Performance Management System Security Administration Guide.
EPM System Configurator now requires the Shared Services “admin” password to be changed during system configuration. Once deployed, subsequent password changes are done through Shared Services. For more information, see the Oracle Hyperion Enterprise Performance Management System Installation and Configuration Guide.
Essbase now supports active-passive failover without Oracle Clusterware.
Primary families of EPM System products 11.1.2.1.0:
l Oracle's Hyperion® Foundation Services
l Oracle Essbase
l Oracle's Hyperion Reporting and Analysis
l Oracle's Hyperion Financial Performance Management Applications
l Oracle's Data Management
Download Oracle EPM (Hyperion) 11.1.2.1.0 from here
After download, unzip the entire content in a folder. It will create the installer files, and other assemblies required for the installation to complete. Assemblies will be having the directory structure of product/version and assembly.dat.
Installation procedure:
Install Oracle Database if you need the database to be used as database for the fusion edition. I installed oracle Database 11.2.0.1 for the purpose.
Most part of the installation is just an easy. Once the pre-requisite is completed, there will be no issues in completion of the installation.
Start the installation using the setup installer zip file
./installTool.sh
After the pre-requisites testing finished, we will be able to see the launch screen.
Configuration of the Shared Services, Web server and other connections and ports:
The EPM_ORACLE_INSTANCE location to be given in the following screen shot.
Provide the database details for the first-time configuration of shared services database.
Epm_admin is the domain to be created for Weblogic. We can skip this and we can add a new domain once the installation is completed.
Hyperion uses both Weblogic as well as Oracle HTTP Server for the user interface.
In this blog, we can describe the available option for deployment of weblogic too.
Specify the location of the datafile for Essbase studio.
Oracle HTTP Server port as 19000 by default.
Configuration is completed.
You can try login the hyperion EPM page as
Login to shared services using
http://machine:port/interop/index.jsp
EPM System Installer installs a single start script in EPM_ORACLE_INSTANCE/bin, called
start.sh. Running the single start script on a machine in your EPM System deployment
starts all EPM System services installed on that machine.
The following EPM System product services and processes are listed below in their recommended startup order.
1. Databases for repositories.
2. Any corporate user directories that you plan to configure for use with Shared Services.
3. Foundation Services Managed Server application server, which includes Shared Services,
and EPM Workspace.
4. Reporting and Analysis Framework — Agent Service (if required for your environment)
5. Reporting and Analysis Framework Application Server (if required for your environment)
6. Web server
The remaining services and processes can be started in any order:
1. Performance Management Architect Services
2. Performance Management Architect application server
3. Performance Management Architect Data Synchronizer application server
4. Essbase Server
5. Administration Services application server
6. Integration Services Server
7. Essbase Studio Server
8. Provider Services application server
9. Financial Reporting Services
10. Financial Reporting application server
11. Web Analysis application server
12. Calculation Manager application server
13. Planning application server and the Hyperion RMI Registry
14. Financial Management service
15. Financial Management Web application server
16. Strategic Finance service
17. Performance Scorecard application server
18. Performance Scorecard Alerter application server
19. Profitability and Cost Management application server
20. Disclosure Management application server
21. Financial Close Management application server.
22. Data Relationship Management services
23. FDM Task Manager service
24. ERP Integrator - Web Application
Validating the Installation:
EPM System Diagnostics tests the connectivity of installed and configured EPM System components. Run EPM System Diagnostics on each machine in the deployment. The results of the tests are saved in HTML format.
Run validate.sh from /EPM_ORACLE_BASE/bin
It will create a report at the location of
/EPM_ORACLE_INSTANCE/diagnostics/reports and find out the validation_report_date_time.html
Validate the failed status and rerun the configuration when required.
To logon to administrative services:
Once you click the launch, the application will store a java file in the name easconsole.
Double-click the easconsole and it will deploy the java application on your machine.
Provide the admin password you assigned during the installation.
To logon to administrative services:
Once you click the launch, the application will store a java file in the name easconsole.
Double-click the easconsole and it will deploy the java application on your machine.
Provide the admin password you assigned during the installation.
To create datasource,
please do the following:
From the admin login page
Navigate->Administer->classic Application Administration -> Planning administration
Click to manage workspace, then create new datasource.
The datasource (Database) inputs are
Then click validate database connection.
For Essbase connection
SERVER_NAME:administrator_username : password given during install
Later you validate the essbase connection and click finish
Later you can create your own applications with options. Once done, you can give the privileges on the applications for the users.
