Installation and Configuration of Hyperion EPM System V11.1.2.2

The current HFM application resides on V11.1.1.3 in production environment. And we are in process of upgrading to V11.1.2.2.

Though production environment is distributed, we have got one development environment consisting only one server. So, I am going to try installing and configuring Hyperion EPM system V11.1.2.2 on this single server environment.

As the server was already used before for Hyperion EPM system, I did not care much about pre-requisites. Otherwise, before starting installation and configuration of Hyperion EPM system, we should really follow the pre-requisite checklist. I will cover this pre-requisite checklist soon in this blog.

Once required installers from the bundle of EPM system V11.1.2.2 installers from Oracle Edelivery site are extracted in one folder, run installTool.cmd as an administrator

Before proceeding further, let us take a brief overview about the environment used. I am here interested in single server HFM-FDM application environment. To give the exact idea, refer to following architecture.

So, we are interested in installing HFM and FDM on our server. Please refer following post of this blog to get the exact idea of required installers.

 http://evolvewithhyperion.blogspot.com/2013/06/epm-system-v11122-installers.html

As per our requirement, I selected only Foundation Services, HFM and FDM components from the installation list.

Once the installation is successful, we can either start for configuration or we can finish up the installation process and select to configure later.

Selected configure to complete the configuration process.

Before starting installation of Hyperion EPM System V11.1.2.2, we need to create DB schemas for required components. The topic will be covered in details in a separate post about pre-requisite checklist.

Right now, I am giving a list of DB schemas I created on Oracle 11g DB residing on Unix server.

Shared Services	Hyp11_hss
HFM	Hyp11_hfm
FDM	Hyp11_fdm3
	Hyp11_fdm4
	Hyp11_fdm5

Referring to above table, give DB schema details.

I decided to go step by step for configuration. First configured only common settings of Shared Services and configured Shared Services DB.

After that, I selected to deploy foundation services to application server.

 The default application web server is Weblogic which gets installed along with EPM system. I am using this default application web server.

We have got two options either to deploy to single managed server which is referred as compact deployment or we can choose to deploy to separate managed servers.

These managed servers are created on weblogic admin server.

Compact Deployment

 Separate Managed Servers:

I selected deployment on separate managed servers; deployment takes several minutes and almost checks our patience. The only good thing is to see changing messages like deploying shared services, creating server for shared services while configuration.

We are now remaining to configure Foundation services web server. This will be the last option we will be doing after completing whole configuration.

Now, we will be configuring HFM components.

Select to start IIS features.

Refering to our DB schema table, please give proper schema details created for HFM.

As weblogic domain is already created while configuring Foundation Services, select option to deploy to existing weblogic doman.

As I am going to deploy on separate managed servers, another managed server HFMWeb0 will be created on weblogic admin server.

 Configure DCOM. Enter user in format "DomainName/Username"

 Configure application Server and cluster.

 

Configure  HFM Web server

Provide application web directory and directory name.

 Configure Provider services which enables SmartView

Configure HFMLCM service which enables Life Cycle management

Enable Web Services.

 

During this first attempt, DCOM configuration was failed.

While investigation, found that, the user “hyperionepm” which I was using for installation and configuration of Hyperion EPM system V11.1.2.2 is connected to secondary domain controller but the during configuration, only primary domain controller was hit for DCOM configuration.

We are connected to following domain controller.

For this issue, a new dll file was provided by Oracle as a temporary solution so that if the user does not exist on primary domain controller, it checks if the user exists on secondary domain controller.

A patch will be provided later for production environment.

After HFM, FDM is configured.