Agenda

• Wednesday am:• Overview• What’s new in install and config

• Wednesday pm:• What’s new in shared services/LCM

• Thursday:• Hands-on install-config, standard deployment

• Friday am:• Hands-on LCM

• Friday pm:• Hands-on scale-out, remove instance• wrapup

<Insert Picture Here>

EPM System Installation and ConfigurationWhat’s new in release 11.1.2.3

Dave Babicz, EngineeringKathryn Gestri – Info Development

Topics

• Embedded Components• New Applications• Certification Changes• Install Changes• Configuration Changes• Diagnostic Tool Changes• Deployment Report Changes• Start Menu Changes• Windows Service Changes• Documentation Changes

Embedded Fusion Components

• EPM System 11.1.2 PS3 (11.1.2.3) is synchronized with FMW 11gR1 PS6 (11.1.1.7)• WebLogic• OHS• AppDev (ADF, JRF, oracle_common)• OCM• OPMN• ODI

New Applications

• None

Certification Changes

• New Certifications• WebSphere Support 7.0.0.23+ (including AS version)• MS Office 2010 64bit• Browser JRE Plug In 1.7.0_07+• FireFox 17.x+ and IE9

• Direct upgrade Path from 11.1.1.4 only• For 11.1.1.0.x to 11.1.1.3.x, apply maintenance release to

11.1.1.4 and then upgrade to 11.1.2.3• For 9.3.3, upgrade to 11.1.2.2 and then apply maintenance

release 11.1.2.3

• Maintenance Paths from 11.1.2.X

 

Install-time Changes

• MSIs

• FDM

• PR

• Samples

• DB client

• ODI

• Deployment Wizard

MSIs

• We completed the migration to MSIs for• Interactive Reporting, Production Reporting (Remote piece), EPMA generator, and

HSF (64bit)

• Note well:

• Other PR clients (developer, viewer, activator) install with server

• EIS console client only installs with server now

• EPMA batch client only installs with webapp now

• Essbase client (unix) only installs with Essbase server

• Nothing was done for FDM because it is at EOL

MSIs – PR in HIT installer

MSIs – EPMA in HIT installer

Dropped Generator

MSIs – Interactive Reporting in HIT installer

Dropped studio

Essbase Integration Services in HIT installer (note new Samples too)

Dropped console

Comes with server only

Profitability Samples in HIT installer

FDM Enterprise Edition in HIT installer

Also get ODI now

HFM ADM Driver in HIT installer

Available now on unix but…

Database client(s)

Database Clients

• Install to• MWH/dbclient32• MWH/dbclient64•

We set an env variable on the system called TNS_ADMIN• That points by default to: MWH\user_projects\config\dbclient

• Tnsnames.ora

Deployment Wizard

• Rapid HFM• Rapid Planning• Rapid Essbase

• Run wizard.cmd(.sh)

• Place zips on system, including database ones, unzip installer zip, and we do the rest all the way through starting and validating

Deployment Wizard

Deployment Wizard - Essbase

Deployment Wizard - Planning

Deployment Wizard - HFM

Deployment Wizard – Check panel

Upgrades (Generally no change)

• General process and strategy same as in PS1• Activities on pre-PS2 box:

• HSS migration• In same migration zip for HSS migration script you’ll

find:• HSF migration script• HFM migration script

• Essbase staging• Data folders

• Essbase rehosting

Upgrades (more)

• Tasks in configuration tool• Foundation: Import migration data zip• Perform before any other product

• WA: update registry (Hidden and always run)• HPCM: re-register applications (Hidden and always

run)• EAS: Import data• Essbase studio: reference old data folder and run

upgrade utility• HFM: run upgrade utility

Configuration Changes• Product DB panel change• New Planning RMI port panel, new RMI task introduced• New EPMA Dimension Server port panel, new Dimension Server task

introduced• R&A Agents port configuration• Database config actions consolidated for R&A• DME Listener port configurable• Essbase Studio configuration change• FR RMI Port change• ERPI Configuration change• Set LWA values in 1st pass of configuration• HTTP shared drive• Lock registry• COMPACT server heap size• Maintenance• Vertical Scaling• Remove an Instance

Product DB Panel Now Has a Grid

• One pass configuration and all DBs can be different.• For new config, maintenance, or upgrade• Advanced options changed a bit

• Now we don’t compare the URL you enter in advanced mode against the values in the grid; grid values aren’t used if you use an advanced URL.

• We support LDAP URL for DB configuration, where LDAP contains DB parameters like SID/SERVICE-NAME, HOST, and port.• User just enters user, password

Product DB Panel Now Has a Grid

Product DB Panel (with Advanced open)

New Planning RMI task – separated from DB Config

New Planning RMI port panel

Stored in HSS registry and

service gets its port from registry, not property file

New Dimension Server Task

Dimension Server logic, prior to PS2,

was executed as part of DB Config

New Dimension Server Port Panel

Stored in HSS registry and

service gets its port from registry,

not windows registry

R&A Agent Ports Configuration

Merge DB config for R&A Framework, IR, FR and WA

• Why ?• DB Config for R&A, FR & WA are controlled via a single task

in configtool but depends on what is installed. So, if WA is not installed, WA tables does not get populated.

• So now all DB tables for R&A get populate at one time.

This solves issues we had with distributed configs.

DME Listener Port

Essbase Studio Configurations Changes

• Became a webapp at one point in the dev cycle; and was pulled

• Takes server.properties entries from HSS registry node (under ESSBASE_STUDIO_SERVER node); server.properties starts blank and is an override file.

• Altered default port for HTTP component to 12080

Essbase Studio Configurations Changes

FR RMI Port Configuration

• It is a range and actually, the range is large enough for 10 instances of FR.

• Each FR webapp instance uses two ports:• One for RMI• One for ADM driver (no longer controlled by ADM.properties)

FR RMI Port Configuration

ERPI Configuration Changes

• During DB config we configure ERPI tables and ODI tables

• During application deployment, we configure ERPI webapp and ODI agent and console.

• ODI Agent and console run in the same JVM as ERPI (no choice for the user)

PR and EIS Configuration

• You do need to run configuration for these products now

• For PR, you just have to select product node in task panel and preconfiguration gets run

FCM/ARM Configuration

• We support SOA clustered now• We use LWA, not Physical host, port , when doing

Deploy to SOA• Out of the box, we have increased the stuck thread

max time• Out of the box, we have increased FCM/ARM

datasource connection pool sizes to 150

Mixed mode Configuration for FCM/ARM

• HITSF#1 (16666316)• Please apply it for all configurations involving FCM/ARM• Enables FCM/ARM configurations like

• #1• FCM/ARM on windows with HFM/FR/Discman• Foundation Services on unix

• #2• FCM/ARM on windows with

HFM/FR/Discman/Foundation Services• Foundation Services on unix, along with say Calc,

Planning, HPCM

Ability to set LWA during first pass of the configtool

• Enable LWA to be set during the first run of the configtool

Enable

HTTP Config Supports Shared Drive

• What does that do for me ?• Enables you to keep one set of conf files for OHS on a

shared drive.

• Hence, when you have more than 1 OHS, and make a change like add an application, you don’t have to reconfig web server config

• Simply restart the OHS servers to re-read the confi files

HTTP Config Supports Shared Drive

Shown when Web Server Type is OHS

HTTP Config Supports Shared Drive

Advanced Option for HTTP Config Behavior details

• We do not support two OHS nodes configured to separate Shared folders; when second box is being configured, the shared location is set and grey’d using that entered on 1st box.

• We do not support a mix of local and shared OHS set ups; user can do multiple local or multiple shared setups

• If doing a mix of windows and unix components, and putting OHS on BOTH, local setup has to be used since shared reference cannot be same across two OHS on unlike systems.

Lock Registry

• The intent of the usage is to prevent attempts at parallel configuration

• A user that tries to start a second configuration session should see a popup message:• A configuration tool session is open on this or another

system, you cannot proceed. Restart the tool after closing other session. (User sees only OK button and tool closes after the OK)

• Deployment report audit record:• I should see trace of start, stop for the box that sees the popup

COMPACT Server Heap Size Setting

• 12 GB or more on machine – set heap at 8 GB

• 6GB or more, up to but not including 12 GB, set heap at 4 GB

• Under 6 GB on machine• 32 bit machine – 750 MB• 64 bit machine – 1.536 MB

Maintenance Process

• Generate a deployment report• Does the configuration reported match expectations ?• If yes, proceed with maintenance• If no, run

• Epmsys_registry.bat (.sh) preview for HSS registry issues• If any, run epmsys_registry.bat(.sh) repair

• Generate deployment report, now does it match your configuration ?

• If no call Support• If yes, proceed with maintenance

Vertical Scaling Support

• Any EPM products on unix

• For windows, we will support Vertical Scaling for Java web applications for the following only:

• Planning domain set of products (HSS, WS, Ra Framework, Calc, EAS, APS, FR, EPMA java webapps)

• HPCM• ERPI• PLUS Essbase server

• Note: this leaves out EPMA dimension server, HFM service-web tiers, FCM, ARM, Discman

• Start menus organized by instance now• Windows services names have instance in them

Vertical Scaling Support (Gotchas)

• Don’t go thinking the windows-based components can be separated in separate vertical instances • HFM Web services and Webapp must be same instance• EPMA dimension server is a singleton in EPM system• EIS service cannot be replicated into separate vertical

instances

Some Actions Moved from Install to Configuration

• Install/Setup .Net• Install/Setup VC Redistributables (we use VC 2010 exclusively

now except for legacy components nearing EOL, e.g. FDM)• Install MSXML• COM registrations• DLL registrations• Service creation• Start menu creation

Work done in goal to support shared binaries, e.g. install once, configure n boxes.

Instance Removal

• Why ?• Want to start over configuration for the components in a single instance

• No granularity for doing part of an instance.

• When FCM/ARM in the instance be sure SOA server is up

• If removing an instance on a box remote from the admin server, then start admin server

• Does NOT• Remove data, nor remove database objects in product

repositories

Instance Removal

• How ?• EPM_ORACLE_INSTANCE/bin/Configtool.bat (.sh) –remove

• No UI, just command line output

Websphere Configuration Changes

• Still manual

• We now support AS and ND

• AS is for single box only

Registry Structure Changes of Note

• We have introduced an Essbase_Studio_product node• We have introduced an Essbase_Administration Services

product node• We have introduced an Essbase Integration Services product

and service node• We have introduced an RMI registry node (for Planning)

Essbase Studio Product Node

Essbase Admin Services Product Node

Essbase Integr. Services Node

Planning RMI Registry Node

Deployment Report Updates

• Upper section worked on extensively.

• Audit section not really enhanced.

• Review example

<Insert Picture Here>

Documentation Changes for 11.1.2.3

Documentation Changes for 11.1.2.3

Documentation has been updated to reflect Oracle’s recommended deployment methodologies.

Documentation Changes for 11.1.2.3

• Installation Start Here shows the deployment paths and guides to choose based on your path.

• Standard Deployment Guide includes more products (Studio, Profitability, FDMEE, Strategic Finance)

• Installation and Configuration Guide has separate sections for new deployment, maintenance, and upgrades.

• Deployment Options Guide (new) includes optional deployment tasks you can perform after a standard deployment, new install, maintenance, or ugprade.

11.1.2.3 Documentation on OTN

http://docs.oracle.com/cd/E40248_01/nav/portal_1.htm