Od 001370

ON
DEMAND
On Demand
Hyperion Standards &
Implementation Guidelines
1. LastUpdated:April6,2011
2. Version:0.4
3. OracleOnDemandOpsHyperion
OracleOnDemandGlobalOperationsHyperion
Page2of77
1.
TableofContents
1.LastUpdated:April6,2011
........................................................................................
2
2.Version:0.4
.................................................................................................................
2
3.OracleOnDemandOpsHyperion
..........................................................................
2
1.TableofContents
.............................................................................................
3
ocument
............................................................................................................................................
4
DocumentRevisionHistory
.........................................................................................................
4
Audience
......................................................................................................................................
4
Purpose
.......................................................................................................................................
4
Premisses
......................................................................................................................................
4
OnDemandAccessPoliciesfor@Oraclecustomers
.......................................................................
5
CustomerPowerBrokerPoliciesforHyperionOnDemand
.........................................................
5
CustomerActiveDirectoryGroupsforHyperion
........................................................................
5
AccessingOnDemandEnvironments
.........................................................................................
5
2.StepstoAccessingLinux/SolarisHosts
................................................................................
5
3.StepstoAccessingWindowsHosts
......................................................................................
6
HyperionPortStandards
..................................................................................................................
8
PortStandardsforHyperion11.1.1.x
............................................................................................
8
1.Component
.......................................................................................................
8
2.PortStandard
...................................................................................................
8
3.Component
.....................................................................................................

11
4.PortStandard
..................................................................................................

11
PortStandardsforHyperion9.xwithWeblogic
........................................................................

13
Page3of77
5.Component
.....................................................................................................

14
6.PortStandard
..................................................................................................

14
7.Component
.....................................................................................................

14
8.PortStandard
..................................................................................................

14
PortStandardsforHyperion9.xwithOracleApplicationServer
.............................................

16
9.Component
.....................................................................................................

16
10.PortStandard
................................................................................................

16
11.Component
...................................................................................................

16
12.PortStandard
................................................................................................

16
HyperionOnDemandFileStandards
............................................................................................

20
HyperionDatabaseStandards
........................................................................................................

22
HyperionOnDemandSchemaStandards
..................................................................................

22
ReadOnlyDatabaseAccess
......................................................................................................

22
UsageofDatabaseLink
.............................................................................................................

22
DatabaseStatisticsCollection
....................................................................................................

22
SSLOffloading/BIGIP
.................................................................................................................

23
FirewallStandards
..........................................................................................................................

24
EndUserDesktopConfiguration
..................................................................................................

25
TuningtheCPUPower
...............................................................................................................

25
IEBrowserSettings
....................................................................................................................

25
RegistrySettings
........................................................................................................................

26
2.EndUserInternetExplorerTimeout
...........................................................................

26
UsageofRDPServerinOnDemandenvironments
......................................................................

28
ApplicationCreation
......................................................................................................................

29
PlanningApplicationCreation
...................................................................................................

29
4.ConsiderationsforWorkingwithPlanning
........................................................................

29
HFMApplicationCreation
........................................................................................................

29
Page4of77
5.ConsiderationsforWorkingwithHFM
..............................................................................

29
ExtendedAnalyticsCreation
.....................................................................................................

30
FDMApplicationCreation
........................................................................................................

30
ExternalProviderAuthentication
...................................................................................................

31
6.MSADConfigurationstoConsider
............................................................................

31
Auditing
.........................................................................................................................................

33
SharedServicesAuditing
...........................................................................................................

33
PlanningAuditing
.....................................................................................................................

34
HFMAuditing
...........................................................................................................................

34
ManagingProvisioning
..................................................................................................................

36
PerformanceConsiderations
..........................................................................................................

37
HyperionSharedService
...........................................................................................................

37
HyperionEssbase
......................................................................................................................

37
8.Essbase.cfg
..........................................................................................................................

37
9.DataandIndexCache
.........................................................................................................

38
10.RetrievalBufferSize
.........................................................................................................

38
HyperionPlanning
....................................................................................................................

38
11.WebForms
.........................................................................................................................

38
12.OrderingofDimension
.....................................................................................................

38
13.BusinessRules
..................................................................................................................

38
14.Supporting_Detail_Cache_Size
........................................................................................

38
HyperionHFM
...........................................................................................................................

38
15.DataAudit
.........................................................................................................................

38
16.ZerosCalculation
..............................................................................................................

38
17.Attachments
.......................................................................................................................

39
18.MaxnumberofdatarecordsinRAM
...............................................................................

39
19.Consolidationserver
..........................................................................................................

39
20.PerformanceofAdministrativeandBatchoperation
........................................................

39
Page5of77
21.HFMDataandTaskAuditConsideration
.........................................................................

39
OfflinePlanningConsiderations
....................................................................................................

40
22.OfflineDataFormConsiderations
...................................................................................

40
23.OfflineUserConsiderations
.............................................................................................

40
24.BusinessRulesConsiderationsforOfflineCalculations
..................................................

40
NamingRestrictions
.......................................................................................................................

41
NamingRestrictionsforApplications
........................................................................................

41
NamingRestrictionsforDimensions,Members,Aliases,andDataForms
...............................

41
NamingRestrictionsforUsernames
..........................................................................................

42
HyperionEnvironmentBackup
.....................................................................................................

43
OperatingSystem
.......................................................................................................................

43
Database
....................................................................................................................................

43
Essbase
.......................................................................................................................................

43
OpenLDAPBackup
...................................................................................................................

44
HyperionSchemaExport
...........................................................................................................

44
HyperionEnvironmentRestore
.....................................................................................................

45
CompleteRestore
.......................................................................................................................

45
PartialRestore
...........................................................................................................................

45
RestoreaspecificPlanningApplication
....................................................................................

45
RestoreaspecificFDMApplication
..........................................................................................

45
RestoreaspecificHFMApplication
..........................................................................................

46
RestoreaspecificEssbaseApplication
......................................................................................

46
RecoveringNativeDirectoryData
.............................................................................................

47
FTP
.................................................................................................................................................

48
DirectoryStructure
....................................................................................................................

48
FTPUsage
..................................................................................................................................

48
Automation
.................................................................................................................................

49
SMTPServerandEmailAlerts
.....................................................................................................

50
Page6of77
ChangeManagement
......................................................................................................................

51
1.AftertheGoLive:
........................................................................................................

51
2.ExcludedActionsafterGoLive:
..................................................................................

51
Refresh/Migration
..........................................................................................................................

53
HyperionRefreshProcess
..........................................................................................................

53
DataManagement
..........................................................................................................................

55
ProductionAssessment(PA)
..........................................................................................................

56
Appendix
........................................................................................................................................

57
HFMApplicationCopyUtility
..................................................................................................

57
3.RunningtheUtility
.......................................................................................................

57
1.AdvancedOptions
.......................................................................................................

58
2.DataOptions
................................................................................................................

59
3.YearOptions
................................................................................................................

59
4.ScenarioOptions
..........................................................................................................

59
5.DataOptions
................................................................................................................

59
6.InvalidRecordsOptions
..............................................................................................

59
7.DatabaseOptions
.........................................................................................................

59
8.TaskEntryLogScreen
................................................................................................

60
TuningTCP/IP
............................................................................................................................

61
OnDemandHFMDataandTaskAuditExtraction
...................................................................

62
Page7of77
OCUMENT
DocumentRevisionHistory
Date
31-May-10
Version
0.1
03-Jun-10
28-Jun-10
06-Apr-11
0.2
0.3
0.4
Reviewer
Arvind Gupta
Weston Adams
Marcos Couto
Grace Lew
Grace Lew
Status
Initial version
Document review
Addl Updates (e.g. formatting)
Updates to reflect AD role
changes
Audience
Hyperion On Demand Customers/Implementers
Purpose
This document depicts policies, practices, and processes applicable to the access and operation
of Hyperion environments installed at Oracle On Demand. Customers/Implementers of Hyperion
On Demand may use this document as reference. While detailed information is available in other
documents specific to each procedure, this document selectively references Oracle OnDemand
procedures, according to the relevance to each subject area.
Premisses
This document considers that the following resources were previously provisioned:
o Hyperion servers
o Network configurations at Customer site
o Customer workstations
o Individual accounts
Page8of77
ONDEMANDACCESSPOLICIESFOR@ORACLECUSTOMERS
IndividualaccesstoHyperionenvironmentsmustbethroughpersonalaccounts.Along
withdeliveryofanenvironment,mastergenericapplicationaccountsaregiventothe
Customer. These application accounts should be used only for granting access to
administratorusersorforspecificoperationsrequestedbyOracleSupportteams.
CustomerPowerBrokerPoliciesforHyperionOnDemand
PowerBroker Policies are needed for access to Linux Servers in On Demand environments. For
Hyperion, the Oracle Database and Essbase will be installed on a Linux Server. Without
PowerBroker policies, the Customer/Implementation Team will not be able to access the Oracle
Database or Essbase instance.
The Customer/Implementation Team will be given access to Development and Test environments
during the implementation phase. Access to Production environments will be allowed in
preparation for Go-Live, but access will be revoked afterwards.
Below are the PowerBroker Policies available for Hyperion:
HODIMPANALYST This PowerBroker policy will give the Customers implementer analyst ftp
access (inf user access) in all Hyperion environments.
HODIMPDBA This PowerBroker policy will give the customers implementer administrator read/
write/execute privileges to Hyperion and Oracle Home directories in Development and Test
environments.
HODIMPPROD This PowerBroker policy will give the Customers implementer administrator
read/write/execute privileges to Hyperion and Oracle Home directories in the Production
environment. This access will be revoked after Go-Live.
CustomerActiveDirectoryGroupsforHyperion
Active Directory (AD) Accounts are needed for access Windows Server in Oracle On Demand.
Each Hyperion Customer will have a Windows Server where all the Hyperion tools will be
installed. The Customer Administrator will have to access this Windows Server via Remote
Desktop Connection (RDC) in order to use the think client (e.g. FR Studio, EAS Console, HFM
Client, FDM Workbench etc). There will be RDP Servers, one for DEV and TEST instance and
one for Production, in a standard Hyperion deployment in On Demand.
NOTE: The Customer Administrator and Implementation team are advised to use the RDP Server
at Oracle On Demand for thick client access, instead of installing on their local desktop/laptop.
Below is the AD group available for Hyperion:
HODCUSTADMIN AD policy for customer Hyperion Administrators for

Operational Support. This AD policy will allow full access permissions to the
Hyperion software install directory structure on the Windows Server in Non
ProductionenvironmentsandreadonlypermissionsinProduction.
AD Groups are set up to differentiate users and assign them to the proper groups, and to control
Page9of77
file system access. None of the AD groups provide Administrator access on the Windows
Servers. Customer Administrators will be provided local admin access on the RDP Server, but
the admin access to the Hyperion MT Servers will be evaluated and controlled by Oracle On
Demand. There will not be local administrator access provided to Hyperion Production MT
servers.
AccessingOnDemandEnvironments
2. StepstoAccessingLinux/SolarisHosts
BeforeconnectingtoLinuxserversinOnDemandenvironments,pleasemake
surethatyouhavetheappropriatePowerBrokerpolicyassigned.Pleasework
withSDMtomakesureyouhavepolicyassigned.Oncetheaccountiscreated
andthePowerBrokerpolicyassigned,followthestepsbelowtoconnecttoLinux
host(LogintoLinux/UnixboxesrequireanSSHclientlikePutty).
OpenPutty;providethehostname,usernameandthecorrespondingpassword:
Loginwithyourusernameandpasswordcredentials:
For@Oraclecustomers:
Afterlogin,runthepbruncommandtoaccessaparticularinstance.
ThepbrunsyntaxforauserwithHODIMPDBAprivilegeisasfollows(atthe$
prompt):
$ pbrun HODIMPDBA u hySID
(SIDbeingtheinstancename)
Forexample:
[AMD64] arvigupt@auhodcabo01 > pbrun hodimpdba -u hytcabo7
Successful login using -u option.
traffic please use -x option.
If you want to allow X
Page10of77
Usage: /usr/local/bin/pbrun [policy] -x [target user]

su from arvigupt to hytcabo7 at Tue Jun 15 22:34:01 CDT 2010
After running pbrun for user hySID, you will have full access to the software
owned by this user and can execute any change or write operation. Without
pbrun, the customer/implementation team will not have proper access to the
filesystemonLinux.Pleasemakesuretobackupanyfilesbeforechangingthem
sothatanychangescanbereverted,ifneeded.
NOTE:SSHPort22shouldbeopenfromtheOracleOnDemandandCustomer
Firewalls,inordertobeabletoconnecttothehostusingtheSSHProtocol.
3. StepstoAccessingWindowsHosts
In order to access Windows Servers in Oracle On Demand, please have an
ActiveDirectory(AD)accountcreated,withthehelpoftheSDM.OncetheAD
accountissetup,pleasefollowthestepsbelow:
o
o
o
o
Open Remote Desktop Connection from your desktop

Provide the Windows hostname and click on Connect
Provide the username and password for Windows login
Ensure Domain A
D1 is selected
NOTE:InordertouseRDPconnectionsforaccesstoWindowshosts,Port3389
shouldbeopenfromtheOracleOnDemandandCustomernetwork.
Page11of77
HYPERIONPORTSTANDARDS
OracleOnDemanddoesnotusedefaultportstoconfigurethecustomerenvironment.
OnDemandhasitsownportstandardstoconfiguretheCustomerNonProductionand
Productionenvironments.BelowliststheportsthatOnDemandusestoconfigurethe
Customerenvironments.
PortStandardsforHyperion11.1.1.x
In the Port Standard column, the following place holders apply:
C=7 for DEV, 5 for TEST and 0 for PROD
B=0 for 1st instance and 1 for 2nd instance of same type
For example, the port for Oracle Database of the first dev instance is: 10710 and second dev
instance will be 11710
1. Com
pone
nt
2. Port
Stan
dard
Oracle Database
1BC10
Oracle Essbase
Agent 1BC23
Application Port
DEV 23768-24600
TEST 22768-23600
PROD 22768-23600
STAGE 24768-25600
1BC45
1BC51
2BC01
2BC02
2BC03
2BC04
2BC05
2BC06
2BC07
2BC08
2BC09
2BC10
2BC11
2BC12
Apache Web Server

IIS Web Server
Shared Services
Essbase Administration Service
EPMA Data Sync Web Service
Hyperion Planning
Essbase Provider Service
FR Web
WebAnalysis
Workspace Web
EPMA Web
Calc Manager
Profitibility & Cost Mgt
ERP Integrator
Page12of77
CMC Console
Stretegic Finance
Planning RMI Port
Workspace Core Services
IR Services
Essbase Integration Server
Essbase Studio Server
FR RMI
FR Server
Planning ADM
Annotation Service
HFM DCOM Range
Data Integration Manager
RDP
SSH
2BC13
2BC14
11333, 1BC53
1BC75-1BC80
1BC81-1BC88
1BC90
1BC24, 1BC25
1BC99
1BC70, 1BC71
1BC72
1BC73
135, 25800-25899
1BC61
3389
22
OnDemanddoesnotopenalltheportsfromthecustomernetwork,sincenotallports
are needed. Customer will access the application using the virtual URL, instead of
accessingtheApacheserverorPlanningServerdirectly.Hence,theApplicationwillbe
accessed using HTTP/HTTPS port 80/443. The above information isshared to help
understandtheOnDemandenvironmentsetup.
ThefollowingPortswillbeopenedfromcustomernetwork,inordertoaccessthe
applicationandmakeuseofsomeHyperiontoolslikeSmartViewandExcelAddinfrom
theEndUserdesktop/laptopcanwork:
3. Com
pone
nt
4. Port
Stan
dard
Oracle Database
1BC10
Oracle Essbase
Agent 1BC23
Application Port
DEV 23768-24600
TEST 22768-23600
PROD 22768-23600
STAGE 24768-25600
1BC45*
2BC02
1BC75-1BC80**
1BC81-1BC88**
Apache Web Server

Workspace Core Services
IR Services
Page13of77

FR RMI
FR Server
Planning ADM
WebAnalysis
HFM DCOM
RDP
SSH
Shared Services
IIS Web Server
Planning RMI Port
HTTP/HTTPS
1BC90**
1BC99**
1BC70, 1BC71**
1BC72**
2BC07*
135, 25800-25899**
3389
22
2BC01*
1BC51*
11333, 1BC53**
80/443
* Ports are opened from customer network in case there are some issues with
applicationaccessoverport80/443
**Someportsareopenedinordertoaccessthethickclientfromthecustomernetwork.
PleasenotethatOnDemanddoesnotrecommenduseofanythickclientslikeFR
Studio, EAS Console etc from a local laptop/desktop, in order to avoid
performance issues over the WAN. Customer/Implementer should use the RDP
Servertoaccessthickclients.(Pleaserefertothe Usage of RDP Server in On Demand
environments section).
Page14of77
PortStandardsforHyperion9.xwithWeblogic
For example, the port for Oracle Database of the first dev instance is 10710 and for second dev
5. Com
pone
nt
6. Port
Stan
dard
Oracle Database
1BC10
Oracle Essbase
Agent 1BC23
Application Port
DEV 23768-24600
TEST 22768-23600
PROD 22768-23600
STAGE 24768-25600
1BC45
1BC51
2BC01
2BC02
2BC03
2BC04
2BC05
2BC06
2BC07
2BC08
2BC09
11333,1BC53
1BC01
1BC02
1BC99
1BC70,1BC71
1BC72
1BC75-1BC81
135, 25800-25899
1BC88
Apache Web Server

IIS Web Server
Shared Services
EPMA Data Sync Web Service
Hyperion Planning
Essbase Provider Service
FR Web
WebAnalysis
Workspace Web
EPMA Web
Planning RMI Port
DIM Repository Server
DIM Repository Agent
FR RMI
FR Server
Planning ADM
BI+ Core Service
HFM DCOM Range
Page15of77
7. Com
pone
nt
8. Port
Stan
dard
Oracle Database
1BC10
Oracle Essbase
Agent 1BC23
Application Port
DEV 23768-24600
TEST 22768-23600
PROD 22768-23600
STAGE 24768-25600
1BC45*
2BC02
1BC75-1BC81**
1BC88**
1BC99**
1BC70, 1BC71**
1BC72**
1BC01**
1BC02**
2BC07*
135, 25800-25899**
3389
22
2BC01*
1BC51*
11333, 1BC53
80/443
Apache Web Server

BI+ Core Service
FR RMI
FR Server
Planning ADM
WebAnalysis
HFM DCOM
RDP
SSH
Shared Services
IIS Web Server
Planning RMI Port
HTTP/HTTPS
Page16of77

Page17of77
PortStandardsforHyperion9.xwithOracleApplicationServer
For example, the port for Oracle Database of the first dev instance is 10710 and for second dev
9. Com
pone
nt
10. Port
Stan
dard
Oracle Database
1BC10
Oracle Essbase
Agent 1BC23
Application Port
DEV 23768-24600
TEST 22768-23600
PROD 22768-23600
STAGE 24768-25600
1BC45
1BC51
1BC88
135,25800-25899
1BC99
1BC70,1BC71
1BC72
1BC01
1BC02
1BC75-1BC81
11333,1BC53
3389
22
80/443
Oracle HTTP Server

IIS Web Server
HFM DCOM
FR RMI
FR Server
Planning ADM
BI+ Core Service
Planning RMI
RDP
SSH
HTTP/HTTPS
11. Com
pone
12. Port
Stan
Page18of77
nt
dard
Oracle Database
1BC10
Oracle Essbase
Agent 1BC23
Application Port
DEV 23768-24600
TEST 22768-23600
PROD 22768-23600
STAGE 24768-25600
1BC45*
1BC51*
1BC75-1BC81**
1BC88**
1BC99**
1BC70, 1BC71**
1BC72**
1BC01**
1BC02**
11333,1BC53**
135, 25800-25899**
3389
22
80/443
Apache Web Server

IIS Web Server
BI+ Core Service
FR RMI
FR Server
Planning ADM
Planing RMI
HFM DCOM
RDP
SSH
HTTP/HTTPS
Page19of77
Page20of77
HYPERIONONDEMANDFILESTANDARDS
OracleOnDemandusesfilestandardsfortheinstallofHyperionsoftwareonbothLinux
andWindows.FollowingarethefilenamingstandardsfortheDatabaseSIDandmount
point:
o
Customer Short Code
This fourcharacter code uniquely identifies a Customers environment. It is

combinedwiththefirstletteroftheenvironmenttypetoformthedatabasesystem
identifier(SID),mountpoints,andusernames.
o
Database SID
This is generated by concatenating the first letter of the environment type,

Customers short code, and the letter 7. However, when a Customer has
additionalNonProductionenvironments,theSIDiscreatedwiththefirstthree
digitsoftheshortcodeplustheenvironmentnumber.
o
Environment type
This can be the Production environment (PROD), the Production Support

environment(TEST),theNonProductionenvironment(DEV),oradditionalNon
Productionenvironments(DEV).Eachenvironmentusesdifferentportnumbers.
o
Mount point
Themountpointfortheapplicationsenvironmentisthesameasthedatabase
SIDname.Themountpointisalwaysenteredinlowercase.
Forexample,belowwouldbethemountpointsfortheOracleDatabaseforthe
DEVinstance,pertheabovenamingconvention:
/dxxxx7/Oracle
/dxxxx7/oradata
/dxxxx7/backup
/dxxxx7/log
/dxxxx7/arch
(wheredisfortheDEVinstance,andxxxxwillbefourcharactercustomercode)
Page21of77
TheHyperionEssbasemountpointwouldbe:
/dxxxx7/essbase
OntheWindowstier,Hyperionsoftwareisinstalledon:
D:\dxxxx7\Hyperion
Ifthereisaneedtosavecustomerspecificfiles,itisrecommendedtousethe
followingstandard(thereshouldbeacustomdirectoryonLinuxandWindows
tostorecustomerspecificfiles):
OntheOracleDBnode:
/dxxxx7/oracle/custom
OntheEssbasenode:
/dxxxx7/essbase/custom
OnWindowsTier:
D:\dxxxx7\custom
NOTE:Itisrecommendedtostorecustomerspecificfilesinacustomlocationso
thatitiseasytodifferentiatecustomercustomscripts,data,oranyotherfiles
fromSoftwaretechstack. Iftherearedataloadscripts,theseshouldalsobe
located under the custom directory. Customer may create as many sub
directories as needed under custom. In Production environment, if any
permissionwouldhavetobegiven,itwillbegivetothecustomdirectoryonlyso
thatcustomercanmanagetheircustomfiles,loadscriptetc.
Page22of77
HYPERIONDATABASESTANDARDS
HyperionOnDemandSchemaStandards
On Demand has certain schema standards in the Oracle Database for
configuringtheHyperionproduct.Belowisthesummaryoftheschemausedto
configurethedifferentHyperioncomponents:
o HSSHyperionSharedServices
o BIPLUSHyperionReporting&Analysis
o PLANSYSPlanningSystemSchema
o HFMHyperionHFMApplication
o EPMAEnterprisePerformanceArchitect
o SNPMODIMasterRepository
o SNPWODIWorkRepository
o DIMDataIntegrationManager
o EISEssbaseIntegrationServer
For each custom Planning and FDM application, the Implementation team is
advisedtoraiseaServiceRequestviaMOStosetupthecustomschema.Each
PlanningandFDMapplicationshouldhaveitsowncustomschema.OracleOn
DemandwillsetuptheschemabasedonOnDemandstandards.
ReadOnlyDatabaseAccess
During the implementation phase or after GoLive, there may be a need to
provide readonly access to Customer/Implementation Team to troubleshoot
functionalordataintegrityissues.
OnDemandwillsetupauserlikeCUSTADMINwithSELECTONLYprivileges,
so that Customer can use this Database account to connect to the Oracle
DatabaseandrunSQLstotroubleshootanyfunctionalordataintegrityissues.
ThisaccountwillallowtheimplementationteamtoqueryanyHyperionschema.
Page23of77
UsageofDatabaseLink
CustomersmayneedtomigratedatatotheHyperionEnvironmentfromother
data sources. To accommodate this, database links are allowed during the
implementationphasetoperformbulkdatamovesfromasourcedatabasetothe
targetdatabasewithintheCustomersenvironment.Customersshouldusethe
OracleDataIntegrator(ODI),DataIntegrationManagement(DIM),orFinancial
DataQualityManagement(FDQM)toolstoloadbulkdatafromtheirtransactional
database(OLTP)toHyperion.
DuringtheProductionAssessmentprocess,OraclewillassessDBlinksinthe
Production environment, and if any DB links exist, will advise the customer
accordingly. AnydataloadprocessusingDBlinksshouldbeconvertedtouse
OnDemandstandarddataloadingtools.
Database links with endpoints located within the Data Center are allowed.
DatabaselinksdefinedintooroutoftheDataCenterarenotallowed.
DatabaseStatisticsCollection
OPTIMIZER_MODE of Oracle Database establishes the default behavior for
choosing an optimization approach for the Oracle instance. Hyperion Oracle
DatabaseinstancehavetheOPTIMIZER_MODEsettoALL_ROWS.Thismode
usesacostbasedapproachforallSQLstatementsinthesessionandoptimize
withagoalofbestthroughput.Inordertomakesureoptimizerispickingthebest
executionplan,Databasestatisticsshouldbeuptodate.
OnDemandsetupacustomjobtogatherthestatisticsofHyperionSchemas
everyweektomakesurestatisticsisuptodate.
Page24of77
SSLOFFLOADING/BIGIP
On Demand use F5 BIGIP as the Load Balancer in Hyperion environment
configurations.BIGIPisnotonlyusedasaLoadBalancerbutalsoforSSLOffloading
as well. So, even with a single server install, BIGIP will be used to configure the
customerenvironment.WithSSLOffloading,OnDemanddoesnotconfiguretheWeb
Server with SSL; BIGIP terminates the SSL, and sends the HTTP request to the
Apache/IISWebServer.
SSLOffloadingoffersfollowingbenefits:
o NoneedtoinstallSSLcertificateoneachWebServer
o EasyMaintenance,ifcertificateexpires,itonlyneedstobereplacedon
theBIGIP
o AvoidsSSLperformanceoverheadonWebServer,butratherallowsH/W
totakecareofSSLprocessing
o Muchfasterprocessing,asallinternalcommunicationbetweenHyperion
componentswillbeHTTPonly.SSLcommunicationwillbeonlybetween
theclientandtheBIGIP
o Noneedforseparateloadbalancer,asBIGIPcanperformloadbalancing
andSSLoffloading
o BIGIPreceivestheclientHTTPSrequestandforwardstheHTTPrequest
totheWebServerbasedontheroutingrules.RoutingRuleswillbesetup
on the BIGIP based on the Customer instance configuration, and
Hyperioncomponentsdeployed
o BIGIPmaintainsthesessionpersistenceviacookies.BIGIPsendsthe
cookiestotheclientbrowser.Cookietimeoutis8hours
OnDemandusesOneConnectprofileattheBIGIP.
Page25of77
FIREWALLSTANDARDS
OnDemandHyperionarchitectureincludemixofLinuxandWindowsServer.Oracle
Database and Essbase running on Linux and HFM/FDM Components running on
WindowsServer.OtherHyperionComponentslikeSharedService,Planning,Essbase
ProviderService,AdminServicewillbedeployedonLinuxorWindowsasperSolution
developedforthecustomer.
ThereisfirewallbetweentheLinuxandWindowstierorbetweenDBtierandWindows
MT.ThisisastandardpracticeinOracleOnDemandtohavefirewallbetweenDBtier
andMTsforsecurityreason.
DefaultFirewalltimeoutforalltheportsis30minute.Defaulttimeoutworkswellinmost
ofthesenerios.OnDemandwillevaluateanyexceptioncasewheretimeoutmayneed
tobeincreased.
DuetoSecurityreasons,OnDemanddoesnotopentheProductionServerportsfrom
nonproduction server. Customer should use tools in Production just to connect to
Productioninstance,nottoNonProductionenvironmentunlesstoolsareneededbyOn
DemandforsomeMigrationorRefreshactivities.
Page26of77
ENDUSERDESKTOPCONFIGURATION
The Hyperion application is very sensitive to EndUser desktop configurations and
generalperformanceovertheWAN.ItishighlyrecommendedthatEndUserdesktop
configurationsfollowproductrecommendations.PleaserefertotheClientCertification
matrixofthecertificationreleaseat:
Certification Release
TheEndUserDesktopshouldadheretoproductrequirementsintermsofRAM,Disk
Space,CPUspeed,andBrowsersettings. Anydeviationfromproductrequirements
mayresultinadverseperformance.
TuningtheCPUPower
When accessing webforms, part of the time elapsed is due to the PC CPU processing
the network receive process, the browser UI and embedded client processing. The older
the PC is, the more likely it is that a significant part of the response time is originating
from the local CPU.
A benchmark was measured on a Pentium class PC (5 years old). This yielded 8
seconds response time in a 150ms-300ms latency situation. The same benchmark on
the same network connection, this time on a quad-core CPU of the Core Duo
generation, the result became 4 seconds.
In the majority of cases, the CPU power is not tunable as such, apart from ensuring
adequate memory. Using contemporary PCs ensures that local processing doesnt
become a bottleneck, so PC exchange isnt to be ruled out. The sweet-spot offerings
(one or 2 generations behind the latest and ultimate designs) will be sufficient.
IEBrowserSettings
There are some recommendations for IE Browser settings. Without these in
place,therecouldbeanegativeimpactontheapplication.Thesesettingsare
specifictoIE7.
Force IE 7 to check for new version every time user visit a page:
o OpenIE7
o GotoTools>Internetoptions>General
Page27of77
o Inbrowsinghistorysectionselectsettings
o InTemporaryInternetfilesselectSettings
o Makesuretheoption"Checkfornewerversionsofstoredpages"hasbeen
setto"Everyvisittothepage".
o PressOkthenpressapply.
Make sure you disable IE default pop up blocking:
o OpenIE7
o GotoTools>Internetoptions>Privacy
o MakesureTurnonPopupBlockerisnotenabled
Add workspace URL to trusted sites:
o OpenIE7
o GotoTools>Internetoptions>Security
o SelectTrustsitesfromSelectazonetovieworchangesecuritysettings
o Type your workspace URL in form https://workspaceserver:portnumber in
Addthiswebsitetothezone:
UnselectRequireserververification(https:)forallsitesinthiszone
Pressaddthenpressclose
o PressOkthenpressApply
Minimize security setting for trusted sites:
o OpenIE7
o GotoTools>Internetoptions>Security
o Select Trusted Sites from select a zone to view or change security
settings
o Presscustomlevel
o FromResettolistselectLow
o Pressok
o Pressapplythenok
Page28of77
Enable cookies:
o OpenIE7>Tools>Internetoptions>PrivacyTab>Advanced>
Checkthe"Overrideautomaticcookiehandling"andacceptthefirstand
thirdpartycookiesandcheckthe"Alwaysallowsessioncookies"option
Enable Drawing options:
o OpenIE7>Tools>Internetoptions>AdvancedTab>Uncheckthe
option"EnableNativeXMLHTTP"
o OpenIE7>Tools>Internetoptions>SecurityTab>CustomLevel
> Miscellaneous > Enable the option "Allow scriptinitiated windows
withoutsizeorpositionconstraints"
RegistrySettings
2. EndUserInternetExplorerTimeout
TheHyperionapplicationisverysensitivetoInternetExplorertimeouts.Thereis
functionality in the application where it may take much longer to process the
requestontheserver.Forexample,theremaybeaBusinessRuleinPlanning
thatcouldtakeupto10minutestofinish,oraSmartViewretrievalthattakesa
much longer time. These would have dependencies on Internet Explorer
timeouts.
ItisadvisablefortheimplementationteamnottodesignBusinessRulestotake
morethanoneortwominutesatthemax,fromthePlanningWeb.Ifthereare
longrunningBusinessRules,itisadvisabletorunthemfromtheAdminConsole,
insteadofthePlanningWeborruntheminthebackground.
In order to avoid IE timeouts for longrunning processes, it is advisable to
considerthefollowingIEtimeouts:
o HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Int
ernetSettings
o KeepAliveTimeout
o ServerInfoTimeout
o ReceiveTimeout
Detailedconsiderationsfortheabovesettingsmaybefoundat:
Page29of77
o http://support.microsoft.com/kb/813827
o http://support.microsoft.com/kb/181050
ThereisnoonesetofvaluesthatcanmeetallCustomerrequirements.Please
testthesetimeoutsbasedonlongrunningprocesses.Iftherearebusinessrules
in Planning Web that may take up to 10 minutes, consider setting
ReceiveTimeoutto10min,sothatIEdoesnottimeoutandthrowtheConnection
ErrororPagenotfounderror.
Page30of77
USAGEOFRDPSERVERINONDEMANDENVIRONMENTS
TheHyperionapplicationhasmanythickclientsthatacustomeradministratorcanuse
tomanagetheHyperionapplications.Someofthethickclientsareasfollows:
o
o
o
o
o
Financial Reporting Studio

Essbase Administrative Service (EAS)
Financial Management Client (HFM)
FDM Workbench
Data Integration Manager client (DIM)
ThesethickclientareverysensitivetoperformanceovertheWAN.Inordertoalleviate
performanceissueswiththesethickclients,thereisaWindowsServer,provisionedwith
theCustomerHyperionenvironment,thatwillhaveallthethickclientsneededforthe
Customer environment. This Windows Server will be accessed by the Customer
AdministratorsorImplementationTeamusingtheRemoteDesktopConnection(RDC).
There will be one such Windows Server for NonProduction environments shared
between DEV and TEST, and one for the Production environment. Customer can
licensedformoreRDPServerifneeded.
Customers/ImplementersareadvisedtousethisRDPServerforthickclients,insteadof
installing on their desktop/laptop. Following are the advantages of using the RDP
Server:
o
Performance issues alleviated with thick client, since communication between client and
server component will be much faster due to no latency.
o
No maintenance needed on the End-User desktop when Server components are
upgraded. RDP Server Software component can be upgraded with the new version at the same
time.
o
Less overhead for Customer administrator as they do not have to support End-User thick
clients issues and install and maintain them
o
End-User only needs the Essbase Excel Add-in and SmartView client. Customer
Administrator will use RDP Server for FR Studio and other thick clients.
Note:MakesureADaccountissetupbeforeloggingintotheRDPServer.
ItisnotadvisabletousethethickclientinstalledonnonproductionRDPServertouse
Production instance or Vice Versa. For example, Using the Essbase Administration
Server console in nonProduction RDP Server to access the Production Essbase
Server.Asastandardpractice,OnDemanddoesnotopenProductionServerports
fromnonproductionserverduetosecurityreasons.
Page31of77
APPLICATIONCREATION
During the Implementation phase, the Implementation Team will create the custom
Planning,HFMandFDMapplication. Thefollowinginformationwillhelpinsettingup
thecustomplanningandFDMapplicationintheOnDemandenvironment.
PlanningApplicationCreation
Application creation is typically performed by the Implementation Team as
needed;butduetoconstraintsonaccesstotheDBserverandlimitedknowledge
ofOracleDatabasedetailsandstandards,theHyperionOnDemandteamneeds
tobeinvolvedincreatingtheinitialframeworkfornewHyperionPlanning.
Each Planning application needs a custom schema in the Oracle Database.
ImplementationTeamneedstoinitiatearequesttotheHyperionOnDemand
teamtosetupcustomschemasforeachPlanningapplication.Oncetherequest
isreceivedviaServiceRequestinMOS,theHyperionOnDemandteamwillset
up the custom schema per On Demand standards, and the Planning DSN.
Implementation team will then use the Planning DSN to set up the custom
planningapplication.
4. ConsiderationsforWorkingwithPlanning
o
o
o
o
o
o
o
Creating and refreshing on the Manage Database page affects data in the Essbase
database. When you click Create, data is erased, and Planning plan types are rebuilt. When
you click Refresh, data might be replaced. Customer should be careful when selecting Create
v/s Refresh. Oracle On Demand recommends backing up the database before a refresh.
Modifying Essbase outlines directly through Oracle Essbase Administration Services is not
supported.
The Refresh outline process in the new version of Planning has changed, where the process
is not incremental. This means that any changes done directly to the Essbase outline will not
be retained after a refresh. During the Refresh process, if a member does not exist in the
Planning relational database, those members and associated properties will not be retained
in Essbase during a refresh.
Do not change dense/sparse Dimension settings or order of Dimension in Essbase directly. It
needs to be done in Planning.
If you upgrade an application created in the Classic application administration to Performance
Management Architect, you cannot return to working with that application in Classic
application administration
Do not alter the planning properties directly in the HSPSYS_PROPERTIES table; rather use
the Manage Properties option in Planning Administration.
Planning uses the JDBC connection pools to access the Oracle Database. Never reduce the
JDBC_MAX_CONNECTIONS to less than 2, since planning does not function well if
Page32of77
o
o
o
o
JDBC_MAX_CONNECTIONS is set to less than 2. The Implementation team should set the
JDBC_MIN_CONNECTIONS and JDBC_MAX_CONNECTIONS to appropriate values based
on the number of concurrent users for Planning.
If you use a different release of SmartView and Planning, SmartView will display a Warning
message at user login. To prevent the warning message, you can set the
SMART_VIEW_DISPLAY_WARNING system property to No .
Implementation team should set/configure background processing for the Business Rules and
Calc Rules automatically after a threshold. It is not advisable to run the Business Rules and
Calc Rules in the foreground when rules take more than 3 min. Default and Min value for
HBR_MAX_WAIT_FOR_RULE is 180000.
The Planning application does not support use of non-ASCII characters in passwords. If a
password contains non-ASCII character, authentication will fail.
Calc Script size should be less than 64K, otherwise you will receive the error The length of
the calc script exceeds the maximum allowed length .
HFMApplicationCreation
Customer/Implementation team can set up the HFM application using HFM
Win32ClientorfromHFMWeb,whichisintegratedwithWorkspace.Thereisno
needtosetupanyseparateschemasforeachHFMapplication.AlltheHFM
applicationscreatedwillresideinthecommonHFMschemanamedHFMinthe
Oracle database. Customer/Implementation team can setup as many
applicationsasneeded,basedoncustomerrequirements;butitisnotadvisable
toleavetheunusedapplicationsintheProductionenvironment.TheProduction
environmentshouldonlyhavetheapplicationsthatareneededbythecustomer.
Each application will consume memory so delete the unwanted application in
HFM.
5. ConsiderationsforWorkingwithHFM
o
o
o
o
o
If you upgrade an application created in Classic application administration to Performance

Management Architect, you cannot return to working with that application in Classic
application administration
HFM Application Name can have a maximum of 10 alphanumeric characters, but cannot start
with a number or contain spaces or special characters. Application names are not casesensitive. HFM, HSV and HSX are reserved names and cannot be used for application name.
Do not create applications with the same name even if they are on different financial
management application servers. Applications of the same name but from different financial
management application servers cannot coexist on one Shared-service Server.
It is important to use the Virtual URL to set up the Financial Management Web Server URL
for Security Administration while creating the application. Use of Host and Port combination
may result in HTTP protocol instead of HTTPS while navigating within the application.
On Demand enables the DCOM on the HFM Server and uses the custom ports for DCOM
Range. This range is open from the customer network. Please refer to the Hyperion Port
Standards section for the port numbers. It is advisable for the Customer/Implementation
Page33of77
o
o
o
o
Team to use the RDP Server to access the HFM application via Win32 client.
Before copying an HFM application, either using HFMCopyApplication.exe or by other means,
make sure all users are disconnected from the application that is being copied and all
processing is stopped. Otherwise the copied application may contain incorrect data.
Customer administrator should use the task audit feature that is available in HFM Web to
review the activities performed by the users. Implementation team should work with On
Demand to set up a scheduled process to extract and purge the task audit on a regular basis,
so that HFM performance would not be downgraded.
Customer administrator should use the data audit feature to review data changes performed
by users. Since the HFM application data is sensitive, it is advisable to turn on the data audit
by setting the EnableDataAudit metadata attribute to Y . Implementation team should work
with On Demand to set up a scheduled process to extract and purge the audit data on a
regular basis, so that HFM performance would not downgraded.
Customer should scan the HFM application to find the invalid records and then delete them.
Scan process is very Database and Network intensive, so it should be performed during a
maintenance window.
Implementation team should fine tune the HFM Registry parameters to find the best possible
values so that the HFM Web and Consolidation would perform better under load. Default
values of HFM Registry parameters may not be suitable. Please refer to the Application
Design Guidelines document for more information about HFM registry parameters.
Oracle On Demand recommends that you add Hyperion Product VIP to the exceptions for the
Web pop-up blocker. When you perform some HFM tasks such as loading data on the Web, a
status Window pops up showing the status. If you have the pop-up blocker enabled on the
browser, the status window will not be displayed.
Extract and back up the Application before doing any major changes. Oracle On Demand
backs up the HFM schema as a standard backup process. Customer and Implementation
team should be extracing and backing up individual application metadata before major
changes to the application.
ExtendedAnalyticsCreation
ExtendedAnalyticsStarSchemaenablestheuseofEssbasetoanalyzedata
andproduceReports.ThisStarschemacanbeusedfrom3rdpartyproductsas
well.TheExtendedAnalyticsmoduleenablescreationofmultiplestarschemas
perapplication.Tablenamesineachstarschemabeginwithaprefixthatyou
specify.
Touse Extended Analyticsmodule,thereisaneed tosetupan OLAPData
Source Name (DSN) for the database that will store star schemas, and then
configuretheDSNwiththeFinancialManagementConfigurationutility.
In order to use Extended Analytics Module, Customer/Implementation Team
shouldlogarequestwithOracleOnDemandtosetupDataSourceperOracle
OnDemandstandardsintheOracledatabase,andthenconfigureDSNwiththe
FinancialManagementConfigurationutility.
Page34of77
NOTE: ItisnotadvisableforCustomer/ImplementationTeamtoruntheEPM
Configuration utility to configure any product hosted in an On Demand
environment. Running the EPM Configurator may cause the disruption of
applicationconfigurationandapplicationmaybeunusable.
FDMApplicationCreation
EachFDMapplicationneedsacustomschemaintheOracleDatabase.Thereis
noneedforDSNforFDMapplication,similartoPlanning,sooncetheschemais
setupforFDM,Implementationteamcanusetheschematosetupthecustom
FDMapplication. EachFDMapplication willneed the filesystem tostore the
FDMapplicationspecificfiles.
FDM application should be set up using the UNC path, instead of drive
letter.OnDemandstandardistosetuptheFDMapplicationfilestructureunder
FDMAPPSfolderunderCUSTOMfolder,thatwillholdalltheFDMapplications:
D:\<SID>\CUSTOM\FDMAPPS
EachFDMapplicationwillhaveitsownfolderunderFDMAPPS.Thiswillhelpto
isolateallthecustomerspecificfiles,datafilesfromtheHyperionfilesystem.
With these file standards, FDM application will be setup using UNC path
\\<machinename>\custom\fdmapps\<appname>.Customfolderwillbeshared
withthecorrectpermissionsothatitcanbereferencedintheUNCpathandwill
beaccessiblefromalltheFDMApplicationServers,includingRDP,sothatthe
applicationcanbeaccessedfromWorkbenchontheRDPServer.
Page35of77
EXTERNALPROVIDERAUTHENTICATION
In an outofthebox deployment, On Demand environment is set up to use native
authenticationusingOpenLDAP.ThisisthestandardconfigurationforanOnDemand
environment.Customermayhaverequirementtousea3 rdpartyauthenticationsystem
forHyperionproducts.
Hyperion Shared Services allow integration with MSAD, LDAP, SAP, and Oracle
Databaseasthe3rdpartyauthenticationprovider.Mostcommonly,Customerstendto
integratetheHyperionproductwiththeircorporateMSADorLDAPServer.
In the On Demand environment, Customer/Implementation Team can integrate their
HyperioninstancewiththeircorporateMSADorLDAPdirectoryserver. Tointegrate
HyperionSharedServiceswithMSADorLDAPServer:
Oracle Responsibilities:
o Help Customer/Implementation Team set up the infrastructure and network, so that
Hyperion product can connect to the customer MSAD or LDAP Server
o Help troubleshoot any connectivity issues between Oracle Servers and Customer MSAD/
LDAP Server
o Deploy root certificate in the JDK certstore if communication with MSAD/LDAP is over
SSL
o Once Customer provides the NATed IP and Port, Oracle On Demand Firewall team will
open the port from all the Hyperion servers including Essbase in each environment
Customer Responsibilities:
o Provide Oracle NATed IP and Port of the MSAD/LDAP Server to integrate with
o Provide Oracle root certificate of MSAD/LDAP if communication is over SSL
o Configure Hyperion Shared Services with external Provider
o Optimize the search in MSAD or LDAP by using the proper filters
o Troubleshoot any configuration issues related with MSAD/LDAP Server
o Troubleshoot any performance issue with external provider
o Provide documentation to Oracle regarding configuration, in order to troubleshoot, in
Production, any issues related to the MSAD/LDAP server
o Be aware that there is a risk of single point-of-failure for Hyperion if MSAD/LDAP down
o Let On Demand know when any changes are happening on MSAD/LDAP Server that
might have an impact on the Hyperion application
6. MSADConfigurationstoConsider
You can configure MSAD so that Shared Services can perform a static hostname lookup or a
DNS lookup to identify MSAD. Static hostname lookup does not support MSAD failover
without updating the MSAD configuration in Shared Services. Using the DNS lookup ensures
high availability of MSAD in scenarios where MSAD is configured on multiple domain controllers.
When configured to perform a DNS lookup, Shared Services query the DNS server to identify
registered domain controllers, and connect to the domain controller with the greatest weight.
Page36of77
ForHighAvailabilityenvironments,makesureyouareusingDNSLookupinstead
ofHostName.
If you are using the global catalog, use one of these methods to configure your MSAD user
directories:
o Configure the global catalog server as the external user directory (recommended)
o Configure each MSAD domain as a separate external user directory
The customer must provide a unique attribute that will be used as the login
attributeforallHyperionproducts.Allgivenattributevaluesmustbecompletely
unique. Noduplicatevaluescanexistortherewillbeproblemsauthenticating
theusers.
Theattributevaluescannotcontainspecialcharacters(likethe@symbol)and
cannotexceed30characters,orsomeoftheproductswillnotrecognizethelogin
and/orrejectthelogin.
Essbasehasalimitationof30charactersintheloginattribute.
Theattributecanbeastandardattribute(likesAMAccountNameforMSAD),or,it
canbeanycustomerdefinedattribute,aslongastheabovecriteriaaremet.
Loginattributeshouldbesinglevalued,notmultivalued.
Search order of the user directory should be set correctly. Shared Services terminates the search
for the user or group when it encounters the specified account. Oracle OnDemand recommends
that the corporate directory that contains most of the EPM System users be placed at the top of
the search order. If a user has multiple accounts within a user directory, Shared Services
retrieves the account that the search first encounters.
Use of self-signed certificates on the MSAD Server if communicate is over SSL is not
recommended, since it adds maintenance on the Hyperion components hosted at Oracle On
Demand. With the use of self-signed certificate, Java Keystore on all the Hyperion servers need
to be updated with the root certificate. If the SSL certificate deployed on the MSAD Server is
using VeriSign or any other trusted authority, no maintenance is needed on the Hyperion servers.
The external user directory configuration in Shared Services may use an identity attribute that
reflects the location of users and groups (for example, DN). In such cases, moving users and
groups across organizational units can cause stale data within Native Directory because EPM
Page37of77
System security is not synchronized to be aware of such changes. When the following actions
take place in an LDAP-based user directory including MSAD, the links that the Native Directory
maintains with the user directory are broken, creating stale data in the Native Directory and
causing loss of access to EPM System applications.
Users and groups are moved across organizational units.
Multiple users or groups are assigned identical common name (CN). CN of provisioned
users or groups are modified.
The Oracle On Demand recommendation is to run the Update Native Directory Utility to
synchronize Native Directory data with the data in configured LDAP-based user directories.
Running this utility makes the stale provisioning data usable.
When the users and groups are moved across organizational units, please work with the Oracle
On Demand team to run the update Native directory utility. Oracle On Demand will take the
backup of the OpenLDAP and then run the Update Native directory. It is not advisable for
Customer/Implementation Team to run it by themselve, for, if proper backup is not taken, it may
interrupt the environment availability. We need to run the UpdateUsers.cmd to synchronize the
identities in Planning from Shared Service as well. UpdateUsers.cmd will update the SID in
planning with changes in Shared Services.
Note: If customer plan to use the SSL for MSAD/LDAP authentication, and use self signed
certificate, customer need to make sure to notify On Demand for any changes on the SSL
certificate, otherwise MSAD/LDAP users will not be able to login to the application once SSL
certificate change on the MSAD/LDAP Server. Oracle On Demand will not be resposible for
interuption of service caused by changes on the certificate on the directory server.
7.
Page38of77
AUDITING
Auditingisveryimportantfeatureoftheapplicationandcustomershoulduseitwith
careful.OneimportantthingtoconsiderisIfAuditismandatoryforthecustomerandif
yes,whattoauditandhowmuchdatatoretainintheaudittablessothatperformanceis
notimpacted.
Please note that On Demand does not enable the auditing at the Database level.
ApplicationAuditfeaturesshouldbeusedifauditingneedtobeenabled.
SharedServicesAuditing
Shared Services allow the auditing of provisioning and life-cycle management activities to track
changes to security objects and artifacts that are exported or imported using the Lifecycle
Management Utility.
Auditing can be configured at three levels:
o Global
o Application Group
o Application
At the global level, you can audit security and artifacts handled by Shared Services. Application
group-level and application-level auditing allow you to audit security activities related to an
application group or application performed through Shared Services. Application group and
application security activities that are performed outside Shared Services, for example, assigning
calculation scripts in Essbase, cannot be audited.
By default, Shared Service auditing is disabled. Oracle On Demand recommends enabling
auditing to allow Shared Services Administrators, Directory Managers, and LCM Managers to
view audit reports to track the changes that have occurred in the environment. Since it is a hosted
environment, it is necessary to audit the changes in the environment.
Customer/Implementation Team should purge the audit data on regular basis, otherwise it may
impact overall performance of the Shared Service.
Page39of77
PlanningAuditing
Planning Administrators can select aspects of the application for change tracking. For example,
you can track changes to Metadata, such as when users change a member property or add a
currency. You can also track changes in data forms, business rules, users, or access
permissions. To select Planning audit: Administration -> Reporting -> Auditing.
NOTE: To avoid affecting performance, be selective on which application elements you audit.
Planning records auditing changes in the Planning database table HSP_AUDIT_RECORDS.
Customer/Implementer should use Oracle DB SQL to pull the Report based on this table. To clear
Audit Records, run the SQL DELETE to purge the table once the records have been reviewed and
extracted.
HFMAuditing
HFMapplicationprovideDataAuditandTaskAuditfeaturethatcanusedtoauditthe
dataandtaskwithintheHFMapplication.
YoucanuseDataAuditfeaturetoviewthedatachangesperformedbytheusers.You
canfilterthedatachangesbydatarange,applicationserver,userandthedimension
membersofthecells.YoucanauditScenarioandAccountmembersbysettingthe
EnableDataAuditmetadataattributetoYforthescenariosandaccountstoaudit.Toturn
offauditingofscenarioandAccountmembers,changetheEnableDataAuditattribueto
N.OnlyusersassignedtotheAdministratorrolecanperformadataaudit.DataAudit
Recordsarestoredin<appname>_Data_Audittable.DataAuditfeatureisavailableonly
fromWebInterface.CustomerAdministratororImplementationteamshouldmonitorthe
DataAuditlog,extractthedataandthenpurgeitsothatlargedataaudithavenoimpact
ontheHFMperformance.
YoucanuseTaskAuditFeaturetoviewthetasksperformedbyusers.Youcanfilter
auditedtasksbydaterange,applicationserver,userandtaskperformed.Onlyusers
Page40of77
assgined the administrator role can perform the task audit. Task audit feature is
available onlyin Financial Management Web interface. Taskaudit log information is
storedin<appname>_TASK_AUDITtable.CustomerAdministratororImplementation
teamshouldmonitorthetaskauditandextractandpurgethedatasothatperformance
isnotimpactedduetohugetable.
Note:OnDemandcansetuptheautomatedprocesstoextractandpurgetheDataAudit
andTaskAudittablesinthecustomerenvironment.Btdefault,thisprocesswillbesetup
in Production enviornment. If there is need to setp the automated process in non
production,pleaseworkwithOnDemandteam.Processwillmonitortherecordcount
intheaudittablesandbasedonthethresholddefined,tableswillbeextractedandthen
purged. Automated job make use of HFMAuditExtractCmdLine utility. Please refer
Appexdixformoreinformationonthisjob.
Page41of77
MANAGINGPROVISIONING
ProvisioningistheprocessofassigningusersandgroupsinSharedServiceaccessto
theapplication,basedontherolesintheorganization.Eachorganizationhasaunique
provisioning requirement. Customer/Implementation Team should adhere to the
followingbestpracticesfortheProvisioningofusersandgroups:
o
o
o
o
o
o
o
o
o
o
o
o
o
All the Shared Service provisioning activity will be performed by the Shared Service
Administrator or Provisioning Manager. Customer should limit assigning the Shared Service
Administrator or Provisioning Manager roles to only the super users in the organization.
Accidentally assigning the Shared Service Administrator or Provisioning Manager roles to
users may disrupt the application avaiability if users perform some destructive operation in
Shared Service.
Built-in Admin Account should not be used for connection or access to the application.
Customer SuperUser should not share the Admin user password with the End-Users.
None of the Planning Datasource connections should be established using the built-in admin
account.
None of the connection setups in Data Integration Manager (DIM), Oracle Data Integrator
(ODI) or Hyperion Financial Data Quality Management (FDQM) should use the Admin user.
End-Users should not be given Shared Service roles. They would just need functional access
to the application.
Users or Groups should only be provisioned access to the application they would need
access to for their work. Unneccessary access should not be given to the users or groups.
Customer should use Artifact level access to further restrict access to the users. Artifact level
access restricts the access given by the roles. Artifact level access can be provided using the
Product Administration screen within the Shared Service Console. This screen can be
accessed by right clicking on the application and select Assign Access Control option.
To facilate administration, Oracle On Demand recommends that you provision groups rather
than users and that you use aggregated roles. Group level provisioning is not supported for
Financial Management Taskflow.
During the installation of Hyperion instance in On Demand, On Demand sets up hypadmin
user. This is an administrator user who will have access to all the applications.
Customer/Implementation Team is advised to use the h ypadmin user to set up the Planning
Data Source and connections in data management tools.
Each user, including customer SuperUsers, should use their own Account instead of using the
admin or hypadmin user.
Provisioning reports enable administrators to review the access rights and permissions
granted to users across EPM System applications, making them useful to track user access
for compliance reporting. Oracle On Demand runs the Provisioning Report during the
Production Assessment (PA) process to be sure that there are a very limited number of
SuperUsers (One or Two) in the application and Admin access of the application is given to a
limited number of users on the customer side. Any discrepancies will be reported to the
Customer and SDM.
It is not advisable to refresh the security/provisioning from a Non-Production to Production
environment, as users might have more priviedges in Non-Production than in Production.
Once the user/groups are deprovisioned or deleted in Shared Service, it is advisable to
update the Planning as well so that unwanted users/groups can be removed from planning to
Page42of77
conserve disk space. To remove deprovisioned users and groups from the Planning database
tables:
Select Administration, then Dimensions and select a dimension member.
Select Administration, then Manage Data Forms and select a data form folder or data
form.
If using Calculation Manager:
o Select Administration, then Business Rule Security and select a business rule folder
or business rule.
o Select Administration, then Manage Task Lists and select a task list.
o Click Assign Access.
o Click Remove Non-provisioned Users/Groups.
Page43of77
PERFORMANCECONSIDERATIONS
TheHyperionapplicationisverysensitivewithrespecttothedesignoftheEssbase
Cube,EssbaseCachesettings,HFMapplicationdesign,Calc,andHBRdesign. An
incorrectly designed Calc Script, HBR, or Planning Web Forms can cause severe
performanceissuewiththeapplication.
ImplementationTeamneedstoconsiderallaspectstoensurethatapplicationperforms
wellfromtheCustomernetwork.ThereisnoonesetofparametersthatOnDemandcan
recommend,soImplementationTeamneedtoconsidertheapplicationtuning,andset
uptheapplicationandparameterscorrectlybasedontesting.Enoughtestingshouldbe
done with multiple users to be sure that Web Forms performs well in a multiuser
environment.
PleasereferApplicationDesignGuidelinesdocumentformoreinformationabout
tuningforeachHyperioncomponent.
HyperionSharedService
Shared Services does not automatically remove audit data from the Shared Services database.
Retaining large amounts of data can degrade performance while generating an audit report.
Shared Services Administrators must purge the data based on your company's audit data
retention policies. Before purging data, be sure to request On Demand to back up the Shared
Service database.
HyperionEssbase
On Demand deploys 64bit Essbase on Linux 64bit in Hyperion 11.1.x. We
should take the advantage of 64bit Essbase when tuning the Essbase
application,Essbase.cfgparameter,andDataandIndexCachefortheEssbase
database. PleasereferApplicationDesignGuidelinesformoreinformation
aboutapplicationdesignandparameterstoconsider.
8. Essbase.cfg
ThefollowingEssbase.cfgparametersshouldbeconsideredandtunedforthe
64bitplatform,duringtheimplementationphase(sincethereisnoonefitforall,
Page44of77
Customer/Implementation Team is advised to tune them based on application

requirements):
o SERVERTHREADS
o CALCCACHE
o CALCCACHEHIGH
o CALCCACHEDEFAULT
o CALCCACHELOW
o CALCLOCKBLOCKHIGH
o CALCLOCKBLOCKDEFAULT
o CALCLOCKBLOCKLOW
o PARCALCMULTIPLEBITMAPMEMOPT
o DLTHREADSPREPARE
o DLTHREADSWRITE
o DYNCALCACHEMAXSIZE
o MULTIPLEBITMAPMEMCHECK
o NETDELAY
o NETRETRYCOUNT
9. DataandIndexCache
Whentherearemillionsofmembers,tryhighervaluesthanthedefault,e.g.
1024(on32bit)or2048Mb(on64bit),ratherthanstayingwith32Mb.Monitor
thecachehitratios(shouldbecloseto1)intheEssbaseAdministrationConsole
andadjustcachesizeaccordingly.
10.RetrievalBufferSize
SetRetrievalBufferSizeto100KBfor32bitplatformand500KBfor64bit
Platform.Thedefaultbuffersizeis10KBfor32bitplatformsand20KBfor64bit
platforms. Implementation team should start with the default value, and then
increaseitgraduallytofindthebestmatch.
Page45of77
HyperionPlanning
HyperionPlanningperformanceisdirectlyrelatedtothePlanningWebForms
andBusinessRulesdesign.IncorrectlydesignedPlanningformsandBusiness
Rulescanseverelyimpactperformanceofoverallapplication.
11. WebForms
PlanningWebformsshouldbedesignedinsuchawaythatformsdoesnottake
morethanaminuteovertheWebtoopen.IfthePlanningWebformstakemore
than a minute, these forms are not suitable for a multiuser environment. A
singlelargeformshouldbesplitintomultiplesmallerformswithfewerrowsand
column.
12.OrderingofDimension
The order of dimensions is critical for the structure and performance of Essbase databases.
Optimize performance by ordering dimensions according to these guidelines:
o Make Period and Account dense, and order dense dimensions from most to least dense.
The most dense is usually Period, followed by Account. Dense dimensions calculate
faster than sparse dimensions.
o Separate sparse dimensions into aggregating and non-aggregating dimensions. Place
aggregating dimensions before non-aggregating dimensions. Order sparse dimensions
from most to least dense. Aggregating dimensions, such as Account, aggregate, or
consolidate, children into the parent to create new data. Non-aggregating dimensions,
such as Scenario, do not consolidate children to create data.
13.BusinessRules
BusinessRulesshouldbedesignedinsuchawaythatrulesdoesnottakemore
thanoneminutetoexecutetoavoidInternetExplorerconnectiontimeout.Ifthe
businessrulestakemorethanoneminute,thoserulesshouldberunfromthe
EASconsole. Browserbasedapplicationsarenotdesignedtorunprocesses
thattakeawhile.PleaseadjustIEtimeoutsettingsasindicatedintheEnd-User
Desktop Configurationsection.YoushouldconsiderrunningtheBusinessRules
in the background if they take more than three minutes. Consider setting
HBR_MAX_WAIT_FOR_RULE as Planning Property, to set the threshold to run
the HBR in background. If this property is not set, HBR will run in the foreground.
Page46of77
14.Supporting_Detail_Cache_Size
Allocate memory for supporting detail cache. You can specify the amount of
memoryforthesupportingdetailcache.Thisimprovesperformancewhenusers
change theplanning unitstatus.Tochange the default memoryallocation for
supporting detail cache, change the SUPPORTING_DETAIL_CACHE_SIZE
property.Thedefaultis20.ImplementationteamshouldmonitortheSupporting
DetailDetectionCacheandifitreachesthat75%orhigher,considertoincrease
thesupporting_detail_cache_size.
HyperionHFM
Customer/ImplementationTeamshouldconsiderthefollowingpointstoimprove
the performance of the HFM application. For more details, please refer
ApplicationDesignGuidelinesdocument.
15.DataAudit
IfDataAuditfeaturenotpartofbusinessrequirements,youshouldturnoffthe
DataAudit.ToTurnofftheDataAudit,settheEnableDataAuditattributetoNfor
allthemembersinthemetadatafile.
16.ZerosCalculation
LoadingandCalculatingzerosinHFMisnotrecommended.Zerosisstoredas
data,andwillincreasethesizeofthedatabase,hencewillimpactperformance.
17. Attachments
For attaching multiple documents to a data grid/process unit, Oracle
recommendsthatyoudonotattachmorethanthreedocumentstoacell.Each
documentshouldbesmallerthan100Kinsize.
18.MaxnumberofdatarecordsinRAM
ConsiderHFMParameterMaxNumDataRecordsinRAMfromdefault1000000to
2000000 on 32bit HFM to improve the performance of consolidation and
SmartViewperformance.
Page47of77
19.Consolidationserver
Consider deploying a dedicated consolidation server when there are big
consolidationsduringpeakhours.
20.
PerformanceofAdministrativeandBatchoperation
UsetheWindowsRDPServerforFRStudioorotherthickclient,insteadofusing
itfromlocallaptop/desktop
AvoidusingFDMWebtoloadhugedatafiles,instead,useBatchscheduleto
processhugefilestoavoidanytimeoutsduetofirewall,networketc.WebBased
applicationsarenotdesignedtowaitalongtimeforaresponsetocomeback
fromtheserver.
21. HFMDataandTaskAuditConsideration
IfDataauditisnotpartofbusinessrequirements,thenitshouldbeturnedoff.
Huge data audit tables will result in severe performance issues in the HFM
application.Toturnoffdataaudit,setEnableDataAuditattributetoNforallthe
membersintheMetadatafile.
InordertomakesureHFMapplicationperformanceisnotimpactedbyhugedata
auditandtaskaudit,OracleOnDemandwillsetupaprocessinProductionto
monitorthe<APPNAME>_DATA_AUDITand<APPNAME>_TASK_AUDITtables.
Theprocessmonitorsthetablesforathresholdof200,000records.Ifthetables
havemorethan200,000records,theprocessdoesthefollowing:
o
o
o
Extract the Data to .csv file using HFMAuditExtractUtility and save the .csv on the HFM
Windows Server
Move the records of Data and Task audit table to the _HIST table
Truncate the Data and Task audit
Sincethe.csvfileisavailableontheWindowsServer,Customerscanretrieve
thefiletotheirlocallaptop/desktopforfutureauditing.Customer/Implementation
TeamisadvisedtoworkwiththeOracleOnDemandteamtomakesuredata
extractisavailableontheserverbeforeitcanbepurgedontheserver.
Page48of77
OFFLINEPLANNINGCONSIDERATIONS
OfflinePlanningallowsuserstotakedataformsofflineandworkwhiledisconnected
fromtheserver.CustomercandownloadtheofflineclientusingtheURLhttps://<VIP>/
HyperionPlanning/SmartView.ThereisnoneedtocopytheofflineclientfromHyperion
PlanningServeranddistributetoEndUsers.Rather,distributetheURLtoEndUsersto
downloadtheclient.
IftheEndUserswhoaretakingdataformsofflinearenonadministrators,makesure
that users have read/write access to
hyperion\offline\myanalytics,
hyperion\offline\offlinedata,andwindows\system32\msvcr71.dllatminimum.
WithIE7andIE8defaultbrowsersettings,EndUsersmayreceiveerrorRevocation
informationforthesecuritycertificateforthissiteisnotavailable.Doyouwantto
proceed? withinSmartViewandOfflinePlanning.Thiserrormayoccurwhileusing
HTTPSprotocol.Tofixtheerror,unchecktheCheckforservercertificaterevocation
underSecurity,tools>InternetOptions>Advanced.
22.
OfflineDataFormConsiderations
Data forms used offline should be self-contained. To ensure that values calculated offline are
correct, all necessary depedencies pertinent to data forms taken offline must be available offline.
Data not downloaded from the server is not available offline.
Dependent data required for business rules to run offline must be taken offline.
23.
OfflineUserConsiderations
Although offline users can select Sync back to Server, offline users must have write permission
for a cell to save the changed cell value to the server.
If a data form member is deleted on the server while a user is working with that data form and
member offline, the offline users changes to that member are not saved to the server when sync
back to server is selected.
If more than one user modified the same data, the last values synchronized back are saved. To
prevent data load issues or miscalculation, use planning units and process management on the
server to control data access.
Offline users can enter data in multiple currencies just as online users can. But Currency
conversion is not supported when working offline.
Set the Data form property Enable Offline Usage when a data form is used offline, which allows
users to save data changed offline back to the server.
Use Planning units to prevent two users from working with a data form simultaneously.
SmartView does not currently support hidden data forms; they are not downloaded when users
take data forms offline that are associated with hidden forms.
Page49of77
24.BusinessRulesConsiderationsforOfflineCalculations
o
o
o
Business Rule calculations can use only data and objects taken offline. Rules do not
have access to data or objects stored on the server.
Runtime prompts are not supported for business rules with Run on Load property set.
Business rules set to Run on Save that require user input for a runtime prompt are
not supported when synchronizing back to server.
Page50of77
NAMINGRESTRICTIONS
The Hyperion product has limitations when creating names for Applications,
Dimensions,CalcScript,orUsernamesinSharedServices.
NamingRestrictionsforApplications
When naming Applications, follow these rules:
o For non-Unicode mode applications, use no more than 8 bytes; for Unicode mode
applications, use no more than 30 characters
o Do not use spaces
o Do not use these special characters:
Asterisks, backslashes, brackets, colons, commas
Equal signs, greater than signs,less than signs
Period, plus signs,question marks, quotation marks(single and double)
Semicolons, slashes,tabs, vertical bars
o For Planning Application names in relational database environments, do not use extended
characters
o For ASO, do not use DEFAULT, LOG, METADATA or TEMP as application names
o Enter names in the Preferred case- Application names are created exactly as entered
NamingRestrictionsforDimensions,Members,Aliases,andDataForms
When naming Dimensions, Members, and Aliases, follow these rules:
o For non-Unicode mode Dimensions, Members or Aliases, use no more than 80 bytes. For
Unicode mode Dimensions, Members or Aliases, use no more than 80 characters
o Distinguish between upper and lower case only if case sensitivity is enabled
o Do not use HTML tags in Member names, Dimension names, Aliases, and Descriptions
o Do not use quotation marks, brackets, backslashes or tabs. Brackets are permitted but not
recommended in block storage outlines. They cause errors when converting to aggregate
storage outlines
o To begin Dimension or Member names, do not use these characters:
@ signs, backslashes, brackets, commas
Dashes, hyphens or minus signs
Equal signs, periods
Less than, parentheses, plus signs
Quotation marks, underscores, vertical bars
o Do not place spaces at the beginning or end of names. Essbase ignores such spaces
o Do not use forward slashes in Member names
o Do not use these words as Dimension or Member names:
Calculation script commands, operator and keywords
Report write commands
Function names and function arguments
Names of other Dimensions and Members, and Generaton names, Level names and
Aliases in the database.
Page51of77
Note: ItisnotadvisabletouseanyspecialcharactersintheFormsNameasuseof
LCMtomigratetheDataFormswillhaveimpact.LCMhavethelimitationofusageof
special characters in data forms, where forms cannot be migrated if LCM used for
Refresh.
NamingRestrictionsforUsernames
User Names in Essbase must be under 30 characters. If third party authentication system
is used, make sure Login Attribute is under 30 characters, otherwise users will not be able to login
to Planning and Essbase.
Page52of77
HYPERIONENVIRONMENTBACKUP
HyperiondeploymentsinOnDemandincludethefollowingSoftwarecomponents:
o
o
o
o
Oracle Database
Essbase Database
OpenLDAP
Windows OS for Hyperion tech stack
The Oracle Database hosts the HFM application, Metadata for Planning and other
Hyperion components data/Metadata. The Essbase Database hosts the Planning
application data and other BSO, ASO Cubes. Hyperion Software including the
WeblogicApplicationServerareinstalledonWindowsOS.
OracleOnDemandtakesdailyHotBackupofHyperioncomponentssothatthereisno
needtoshutdowntheservicesandhaveusersunabletoaccesstheapplication.Hot
BackupsincludethebackupoftheOracleDB,Essbase,andWindowsOS, including
theHyperionfilesystem.
OracleOnDemandtakestheHotBackupoftheOracleDBandEssbaseat22:00CDT.
ThisistheBackupWindowforUScustomers.TherearetwootherBackupWindows,
15:00CDTand8:00CDT,totakecareofEMEAandAPACcustomers.OnDemandwill
not be able to schedule any Backups aside from these three Backup Windows.
Customer is advised to pick one Backup Window based on their Business
Requirements. On Demand takes backups of Production and NonProduction
environments.
OracleOnDemandusesdifferenttypesofbackups,eachtargetingadifferentpartof
theserverthatisbeingbackedup.
OperatingSystem
The core Operating System is backed up separately from the Applications or
Databases.TheOperatingSystemisbackeduptoanalternateonlinedisk.This
backupoccursdailyandduplicatestheserversrootdiskforUNIX.Thisallows
theservertosimplybebootedusingthealternatecopyifnecessary.TheUNIX
backupprocessduplicatestheserversrootdisktoasparephysicaldiskinthe
server.WindowsservershavetheirrootdiskbackeduptoaNetworkAttached
Page53of77
Storagedeviceeveryday.Wetakeincrementalbackupssixtimesaweek,and
onefullbackup.Thisbackupiswrittentotapetwiceaweek.Beforethetapeis
shipped,allTapeBackupsareencryptedusingDecru.
Database
Databases are backed up using hot backups, which allow a database to be
backedupwhileitisstillinuse.Fulldatabasebackupsarewrittentodiskdaily,
andcopiedtotapetwiceaweek.
Archivelogmanagementisatwofoldprocess:
Archivelogsarecontinuouslymanaged.Oncethedatabaseonlinearchive(redo
log)iswrittentodiskasan(offline)logarchive,ascriptcopiesthemtoabackup
serverandtwocopiesofthetapearemade.Oneofthetwotapesissentoffsite
duringthenexttapevaultingpickup.Offsitetapesareretainedforfiveweeks.
Thesecondtapeiskeptonsiteforfiveweeksincaserecoveryisneededfor
nondisaster recovery purposes. So technically, On Demand can restore an
environmentasoldas5weeksandrollforwardbyapplyingarchives
Essbase
OracleOnDemandtakesHotBackupsoftheEssbasefilesystem.EssbaseHot
Backuparecomprisedofthefollowingsequenceofsteps:
o Logoffalltheusersfromthesystem
o DisableLogins
o PuttheEssbaseDatabaseintoArchiveMode
o TaketheEssbasefilesystembackup
o PuttheEssbaseDatabaseintoWriteMode
o EnableLogins
EssbaseBackupstake25minutes,dependingonthesizeoftheDatabase.This
time will vary when the size of Essbase file system increase. Customers are
advised to devise an internal process for their EndUsers not to log into the
systemasitcaninterruptthebackupprocess.Customersarealsoadvisedto
communicatetheBackupscheduletotheirUserCommunity.
Page54of77
OracleOnDemanddoesnotexportLevel0orAllDataforeachdatabaseaspart
ofthestandardEssbaseBackupprocess.IfthereisaneedtoexportLevel0or
AllDataregularly,Customer/Implementerisadvisedtosetupcustomjobsfor
this.OnDemandwillworkwiththeCustomer/ImplementertosetuptheJobifit
needstobescheduledonUNIXorWindowsOS.
OpenLDAPBackup
OpenLDAP is backed up at the same time when Oracle Database and Essbase is
backed up so that all the data is synchronized if Restore is needed. OpenLDAP is
backedusingtheOpenLDAPbackup.batfilethatrunsasascheduledjobontheShared
ServiceServer.
HyperionSchemaExport
InordertohavetheabilitytorestoreaspecificHyperioncomponentorCustomer
application,OracleOnDemandtakesdailySchemaexportsforalltheHyperion
Schemas. This will enable the Customer to be able to request a specific
Applicationrestoreinthecaseofanydatalossorcorruption,insteadofhavingto
restore the complete Oracle DB, which would impact the complete Hyperion
Application.
WhatOracleOnDemanddoesnotperformasapartofthestandardBackupprocess
are:
o BackingupLevel0orallDataforeachEssbaseCube
o BackingupindividualHFMApplicationMetadataorData
o Backing up any custom interface setup and its related files, it will be
backedupasapartofOSbackup
Page55of77
HYPERIONENVIRONMENTRESTORE
SystemRestoremaybeneededeitherbyOracleOnDemandwhileperformingsome
maintenanceintheCustomersenvironment,orrequestedbyCustomerinthecaseof
anydatalossorcorruptioninProductionorNonProductionenvironments.Theremay
beaneedtoRestorethecompletesystemorjusttodoaPartialRestore.
CompleteRestore
A Complete Restore would include the Oracle DB Hot/Cold Backup, Essbase, and Windows OS
containing the Hyperion Filesystem.
PartialRestore
Only a specific Application or Hyperion component is restored. Customer to provide the name of
the Application or schema to Restore.
RestoreaspecificPlanningApplication
Inordertorestoreaspecificplanningapplication,
Customer will:
o Provide name of the Planning Application to Restore
o Provide details on whether corresponding Essbase applications need to be Restored or
just the Planing RDBMS schema
o Validate the Planning Application forms after Restore
o Validate Essbase Data after Restore
Oracle will:
o Find if Backup is available for the requested Restore date
o Restore the Planning Schema from Backup
o Restore the Essbase application folder on Linux from Backup if requested
o Start Essbase application after Restore
RestoreaspecificFDMApplication
InordertorestoreaspecificFDMapplication,
Customer will:
o Provide name of the FDM application to Restore
o Validate the FDM application after restore
o Validate FDM Data after the restore
Oracle will:
o Find if Backup available for the requested Restore date
o Restore the FDM Schema from Backup
o Restore the FDM application folder on Windows Server from Backup
Page56of77
Start FDM services after Restore
RestoreaspecificHFMApplication
AlltheHFMapplicationsarestoredinasingleHFMSchema.Ifthereisaneedto
restorethespecificHFMapplication,thecompleteHFMSchemawillberestored,
hencealltheHFMapplicationsintheHFMschemawillberestored.Customer
shouldextractMetadataandDataifthereareanymajorchangesarehappingfor
theHFMapplicationsothatifthereisaneedtorestore,extractedMetadataand
Datacaneasilybeimported.InordertorestoreHFMapplication,
Customer will:
o Provide name of the HFM application
o Validate all the HFM application after restore
o Validate HFM Data after the restore
Oracle will:
o Find if backup available for the date for which restore requested
o Restore the HFM Schema from the backup
o Start HFM services after restore
RestoreaspecificEssbaseApplication
InordertorestoreaspecificEssbaseapplication,
Customer will:
o Provide name of Essbase application to Restore
o Provide details on whether all the calc scripts, rules files, etc. need to be Restore
o Validate the Essbase application after Restore
o Validate Essbase Data after Restore
Oracle will:
o Find if Backup available for the requested Restore date
o Restore the Essbase APP folder specific to the application from Backup
o Start Essbase application after Restore
RecoveringNativeDirectoryData
The Shared Services database stores information related to product registration while the Native
Directory database contains provisioning data for all products. These databases work in tandem
to support EPM System products. Data inconsistencies between these databases impact normal
operations. Inconsistencies could occur during manual database update or database upgrades.
When there is need to recover the Native Directory, Oracle On Demand will:
o Back up the Native Directory
o Run the Recover Native Directory from Shared Services. This will sync up the Native
Directory with the Shared Services database. It does the following:
Create missing registered applications in Native Directory
Remove, from Native Directory, stale application entries for which data is not present
Page57of77
in the Shared Services database

NOTE: It is not advisable for the Customer administrator or Implementation Team to run the
Recover Native Directory since OD will do this after taking the appropriate backup.
Page58of77
FTP
Oracle will provide SSH File Transfer Protocol (Secure FTP or SFTP) access to a
dedicated SFTP server (ftps01.oracle.com) that will facilitate file transfer in Non
ProductionandProductionenvironments.
There are multiple ways to Transfer the files from customer Desktop to Linux and
WindowsServerinADC.InordertoTransferthefilefromcustomerDesktoptoLinux
server,customercanuseSSHSecureFileTransferthatisbuiltintoSSHSecureShell.
In order to transfer the files from customer Desktop to Windows Server in ADC,
customer can use RDC Connection and share the local disk so that local disk are
availablefromtheWindowsServerandfilecanbeshared.
SSHFileTransferorRDPconnectioncanbeusedtocopythefileswhenfilesneedto
betransferonetimeandfilesaresmallsize.RDPConnectionisnotefficienttoTransfer
largefiles.
Inordertotransferlargefilesorfilesneedtobetransferonregularbasisinorderto
processthemusingdatamanagementtools,customershoulduseOracleSFTPServer
ftps01.oracle.comtouploadthefiles.
DirectoryStructure
Directory structure of the FTP Server on the Linux Server would be as follows:
/interface/<infuser>/<instance>/incoming
/interface/<infuser>/<instance>/outgoing
/interface/<infuser>/<instance>/archive
/interface/<infuser>/<instance>/src
where <instance> will be instance name (D<custid>7, T<custid>7 or P<custid>7). If
Page59of77
the above directory structure is not available on the Linux Server (Oracle DB, Essbase), please
raise a request with Oracle On Demand to set it up. Once the directory structure is setup for each
instance on the FTP Server, customer can upload the files for each instance. Files will be
uploaded to the incoming folder when files need to be processed by Hyperion software. Outgoing
folder is to move the file so that customer can download them.
FTPUsage
Customer/Implementer will use SFTP Protocol to upload files that should be
processed by Hyperion components. Oracle SFTP Server filesystem will be
mountedontheLinuxServers,sofilesuploadedontheOracleFTPServer,will
beavailableontheLinuxServerforprocessing.
Customer/ImplementationTeamwilluseSFTPclients,likeFileZillaorCoreFtp,to
uploadordownloadfilesontheOracleSFTPServer.OracleOnDemandwillnot
providesupportonusageofFTPclientsoftware.
Customer/ImplementationTeamwilluploadthefilesinthe/incomingfolderin
ordertoprocessthosefilesbytheHyperionSoftware.Customer/Implementation
Team will move the files to the outgoing folder in order to have those files
availabletodownloadfromSFTPServer.
Automation
Thereisnoautomatedprocesstomovethefilesfromthe/incomingfolderto
theHyperionfilesystemonLinuxorWindowstoprocessthem.Aprocesswould
need to be set up. The Oracle On Demand team will work with the
Customer/Implementer to set up the process to transfer the files from the
/incomingfoldertotheWindowsserver,sothatfilescanbeprocessedbythe
custominterfaceprocesssetupbyCustomer/Implementer.
TheOracleOnDemandstandardistomovethefilesfromthe/incomingfolder
tothe /custom folderontheEssbaseorWindowsserver,sothatfilescanbe
differentiatedfromtheHyperiontechstack. Custominterfaceprogramsshould
readthefilesfromthe /custom folderonWindows D:\<sid>\custom oron
Linux /SID/essbase/custom. There may be some limitation with Data
ManagementtoolslikeFDQM,whereitismandatorytoreadthefilesfromthe
specific folder instead of /custom. On Demand team will work with
Page60of77
Customer/Implementer, taking those product limitations into consideration, to

movethefilestothefolderneededonanexceptionbasis.
Inordertosetupanautomatedprocesstotransferthefilesfromthe/incoming
to/customfolder:
Customer will:
o Set up process to upload the files on the Oracle SFTP Server
o Open a request with Oracle On Demand requesting setup of the Transfer process
o Validate the Transfer process
o Process the file
o Make sure archive of file is maintained if needed
o Make sure file uploaded does not start with _, -,$, /,\,<.> and |. Also file name should not
have spaces or () in between
o Troubleshoot the Interface process when it is not able to process the file
Oracle will:
o Set up the Transfer process to move the files from /incoming to /custom folder or
folder requested as per customer interface requirement
o Work with Implementation Team to validate the Transfer process
o Work with Implementation Team to fix the transfer process when broken
Page61of77
SMTPSERVERANDEMAILALERTS
TheHyperionproducthasoutboundEmailcapabilitywhereitcansendemailtoEnd
Users.Forexample,youcansetupbatchburstinginFinancialReportingtosendthe
scheduledreportstoEndUsersviaEmail,oryoucansetupEmailalertsinHFMfor
Intercompany and Process Management. Email alert usage will vary for each
implementation.
ThereisaSMTPServerinOnDemandwhichcanbeusedtosendoutboundemails
from the Hyperion instance. During the installation of the Product, On Demand
configurestheHyperionproducttousetheSMTPServerauohssmtp.oracle.com.All
theHyperionServershaveSMTPport25opentothisServer.OnDemandwillmake
sureconnectivityisinplacebetweenHyperionServersandtheSMTPServer.SMTP
configurationisavailableduringconfigurationoftheSharedServicesinSystem11.
Since Email alert usage varies from Customer to Customer, On Demand does not
configure each Email functionality in the Hyperion product. Implementation Team
should configure each feature, such as intercompany Email alerts, process
managementalerts,orFRschedulerbasedonCustomerrequirements.OnDemandwill
makesuretherearenoissuessendingoutboundemailsfromOraclenetwork,butif
thereareissueswiththeCustomerEmailserver,itshouldbeaddressedbyCustomer
network/exchange administrators. They need to make sure their Email server is not
treatingEmailalertsasjunkEmails.IftheImplementationTeamneedshelpconfiguring
functionalityintheapplicationforeMailalerts,theyshouldworkwithHyperionProduct
Support.
HyperionProductdoesnothaveinboundemailcapability.Anybouncedemailoroutof
officereturncannotbeprocessedbytheapplication.
Page62of77
CHANGEMANAGEMENT
Duringtheimplementationphase,Customer/ImplementationTeamwillhaveaccessto
all three Hyperion environments (i.e. Development, Production Support, and
Production). There is no difference between Production and NonProduction
environmentsbeforeGoLive.Customer/ImplementationTeammayneedaccesstothe
Production environment in preparation for GoLive. After GoLive, the Production
environmentwillbelockeddown,andchangestotheProductionenvironmentwillgo
throughtheOnDemandChangeManagementprocess.
The On Demand Change Management process enforces that changes will be first
migrated to the Production Support (TEST) environment where
Customer/Implementation Team will do thorough testing. Once the testing has
completedandchangesaresignedoffbytheCustomerauthorizedapprover,changes
willbemigratedtotheProductionenvironment.Anyconfigurationchangeswillnotbe
directly promoted to Production unless an exception has been approved by the
CustomerandOracleOnDemand.
1. AftertheGoLive:
Customer/Implementation Team will:
o Design new planning applications in Development environment
o Design new HFM applications in Development environment
o Design new Reports in Development environment
o Design new custom interfaces for ODI, DIM and FDQM in Development environment
o Design new Essbase cubes, HBR, and Calc scripts in Development environment
o Conduct performance testing and ensure design is per product best practices
o Once Tested in Development environment, request Oracle On Demand to migrate to
Production Support environment
o Once UAT is completed and changes are signed-off from Customer-authorized approvers,
request Oracle On Demand to migrate to Production environment
Oracle will:
o Migrate new Planning applications to Production Support and Production environments
o Migrate new HFM applications to Production Support and Production environments
o Migration new Reports to Production Support and Production environments
o Migrate new custom interface setups in ODI, DIM and FDM to Production Support and
Production environments
o Migrate new Essbase Cubes, HBR, and Calc Scripts to Production Support and
Production environments
2. ExcludedActionsafterGoLive:
Customer/Implementation Team is advised not to perform the actions below directly in
Production after Go-Live, because they may cause system stability issues:
Page63of77
o
o
o
o
o
o
o
o
o
o
o
o
Setup of new Planning applications

Setup of new BI+ Reports
Setup of new HFM applications
Setup of new Essbase cubes
Setup of new HBR, Calc Scripts
Setup of new custom interfaces for data loading
Setup of external authentication systems
Configuration changes for Essbase in Essbase.cfg
Configuration changes for Hyperion Financial Management with respect to tuning of HFM
Parameters
Configuration Changes in Planning and Data Forms in exising Planning application
Redesign existing BI+ Reports
Any other configuration changes that may interrupt the functionality of the Hyperion
application
Page64of77
REFRESH/MIGRATION
InOracleOnDemand,RefreshistheprocessofbuildingtheTargetinstancefromthe
Sourceinstance.ForeBusinessSuite(EBS),theTargetenvironmentisbuiltasis,from
the Source instance including the Oracle database and Tech stack. All the
configurations, Techstack patches, and CPU patches are carried over as a part of
Refreshprocess.Incontrast,theHyperionRefreshprocessisdifferentfromtheEBS
refresh process.In Hyperion,the Refreshprocess meansMigrating the Applications
fromtheSourceenvironmenttoTargetenvironment,wheretheTargetenvironmentis
alreadyupandrunningandfullyfunctional.
HyperionRefreshProcess
The Hyperion Refresh process includes:
o MigratingPlanningapplicationfromSourcetoTargetenvironment
o MigratingHFMapplicationfromSourcetoTargetenvironment
o MigratingBI+ReportsfromSourcetoTargetenvironment
o MigratingSharedServicesecurityfromSourcetoTargetenvironment
o MigratingFDMapplicationfromSourcetoTargetenvironment
o MigratingDIMRepositoryfromSourcetoTargetenvironment
o MigratingDRMschemafromSourcetoTargetenvironment
o MigratingBusinessRules,CalcScripts,RulesandEssbaseCubes
o Migratingcustominterfaces
Once the Implementation Team has done the development in the DEV instance, Implementation
Team can request a Refresh of TEST from DEV, in order for the same set of applications and data
to be available in the TEST instance. Once UAT is done and signed-off, another Refresh can be
scheduled from TEST to PROD to have the applications and data available in Production for GoLive.
On Demand makes use of Hyperion product tools/utilities to migrate the Applications. For
example, the HFMCopyApplication utility is used to copy the Classic HFM application;
CSSExportImport to migrate the Shared Services security; and Life Cycle Management (LCM) to
Migrate Planning and EPMA artifacts, etc. During the Refresh process, there may be some
product issues, where either these tools/utilities do not work, or data is not migrated correctly by
these utilities. In those cases, Oracle On Demand will closely work with Hyperion Product
Support to fix issues and ensure Target instance matches with the Source instance.
On Demand standard Refresh SLA is 55 hours, but the time will vary based on the Modules
Page65of77
involved and number of Applications to be migrated. If there are multiple Planning, HFM, FDM,
and Essbase Applications, this time may get extended. Customer/Implementation Team will
submit the Refresh request via RFC in MOS, and include the completed Hyperion Refresh
template . In the Hyperion Refresh template, Customer/Implementation Team would need to
specify the Applications that need to be migrated, data (level 0 or all), Shared Services security,
Reports to be migrated etc. Each artifact that needs to be migrated should be listed clearly in this
Hyperion Refresh template. The Oracle On Demand team will this list when performing
Application migrations.
In order to perform the Refresh or migrate the Applications, On Demand will run exports of the
artifacts first, from the Source environment. It is advisable for Customer/Implementation Team not
to use the environment when the export process running. Having the users in the system and
running the process may result in inconsistent data on the Target. On Demand does not shut
down the Source environment for the Refresh, but advises the customer not to use it when the
export is running. The RFC will be updated once the exports are done, so that the Customer can
start using the source environment.
After the application and data is migrated, Oracle On Demand go through

complete Health Check process and make sure source and target instance
matches.Checksperformedare:
o
o
o
o
o
o
o
Essbase Data Blocks comparison

Shared Service User, Group and Provisioning comparison
Random check of the Data Forms, Data Grid to be sure Data Match
Count of Data Forms, Data Grid
Count of BI+ Reports
Count of Business Rules and Validate them
Dimension Library to be sure Dimension and Member matches
1.
Page66of77
DATAMANAGEMENT
In order to load data into Hyperion Planning, HFM, and Essbase cube,
Customer/ImplementationTeamwillusedataintegrationtoolslikeFDQM,DIM,ODI,or
EIS as solutioned and architected for the Customer. Customer will use the data
integrationtoolstodesigntheinterfacetoloadthedataintoHyperionmodules.For
custominterfaces,theremaybeaneedtotransferfilesfromtheSourcesystemonthe
HyperionServersothatfilescanbeprocessedusingthecustominterface.
Customer will:
o Design the custom interface using Hyperion integration tools according to product best
practices
o Design the script to load the files on the Oracle FTP Server
o Archive the file if needed after processing
o Validate the data
o Monitor the custom interface and if interface/job fails, re-fire it again
o Work with Oracle On Demand to troubleshoot failed job/interface if issue is related to
infrastructure
o Troubleshoot issue with Data Load with respect to load performance
Oracle will:
o Set up custom file transfer process to transfer the file from Oracle FTP Server to the
Hyperion Server in order for custom interface to process the files
o Troubleshoot any issues related to File Transfer process
o Monitor Data Integration tools
Page67of77
PRODUCTIONASSESSMENT(PA)
ProductionAssessmentistheprocessthatOracleOnDemandgoesthroughbeforeGo
LivetoensurethattheProductionenvironmentistunedandallthecriticalpatchesare
inplace,inordertoalleviatesystemstabilityissuesatGoLive.DuringthePAprocess,
On Demand makes sure that all lessons learned have been incorporated into the
Productionenvironment,sothatthesameissuesthatoccurredforothercustomerswill
notoccur.
DuringtheProductionAssessment,OnDemandperformsthefollowing:
o
o
o
o
o
o
o
o
Check and perform performance tuning of Web Server and Application Server
Check and perform performance tuning of Oracle Database
Check and perform performance tuning of individual Hyperion products
Check and introduce critical Hyperion patches for Bug fixes that may cause stability
issues
Revoke the HODIMPPROD Power Broker policy
Revoke Administrator access on Windows servers
Ensure System Monitoring is in place
Ensure the Backups are running for Production
It is advisable for Customer/Implementation Team to schedule the Production

Assessment as soon as possible before GoLive, so that there is sufficient time to
incorporatethepatchesandperformancetuningconfigurations withoutimpactingthe
GoLiveschedule.UntilProductionAssessmentiscomplete,Customerwillnotreceive
ProductionReady(PR)status.
Page68of77
APPENDIX
HFMApplicationCopyUtility
The Financial Management Application Copy Utility is a standalone utility and can be run from
any machine that has valid UDL file(s) to access the Source and Target RDBMS environments.
This utility is used to be copy the classic HFM application within the same environment or
across the environments.
The HFMCopyAplication utility will be used when Customer requests refresh of the
classicHFMapplicationfromoneenvironmenttoanother.OnDemandteamwillrunthe
utility to fulfil the customer request. During the implementation phase,
Customer/Implementation Team may prefer to do the copy themselves to meet
deadlines when the refresh SLA is not acceptable. This section will help the
implementationteamtoruntheHFMCopyApplicationutility.Thisutilitycanberunfrom
the RDP Server. If this utility is not available on the RDP Server,
Customer/ImplementationTeamcanrequestOnDemandtocopytheutilityfromthe
HFMServertotheRDPServer. ItisnotadvisabletorunthisutilityfromCustomer
laptop/desktop due to the performance over WAN. This utility spawns a number of
workerthreads,eachthreadcopiesonetable,androwsareprocessedonebyone.
RunningthisutilityfromCustomernetworkwillconsumelotsofnetworkbandwidthand
overalloperationwillbeslow.
3. RunningtheUtility
The Financial Management Application Copy Utility is installed on the Financial Management
Application server by default in the %Hyperion_Home%\FinancialManagement\Server folder and
is named HfmCopyApplication.exe. This will be copied to the RDP Server so that
Customer/Implementation Team can access it without access to the HFM Windows Server.
The following shows the screens presented when this utility is run:
Select the >> button to navigate to the proper UDL file for the Source environment
Page69of77
The list of Applications is retrieved from the Hsx_DataSources table in the Source environment
Select the >> button to browse to the UDL file configured to access the Target environment. This
UDL file can be the same as the Source UDL or it can point to a different UDL
For the Target destination, the utility will read the Windows registry and populate the drop-down
with names of Applications that were previously copied. If this is the first time running the utility,
then it will show only the Source Application name. The registry key read is user-specific,
HKEY_CURRENT_USER\Software\Hyperion Solutions\HfmCopyApplication\Settings, and the
values read to populate the drop-down are DestApp00 DestAppXX. You may select an existing
Application name from the drop down or manually type a new Application name. The Target
Application name must adhere to the naming conventions in the Financial Management
Administrators guide.
Copy Application Data: This box is typically checked to generate an identical copy of the Source
Application. Clear this check box to create a shell Application. Application metadata tables will
be copied and populated while data tables are only created but are not populated.
Copy Audit data: This box can be cleared if Task and Data audit trails are not required to be
maintained in the Target environment. Often the Task and Data audit tables are very large tables
and should not be copied unless required.
Copy Cluster Settings: This check box should normally not be checked. This will copy the
Financial Management Cluster related tables only if the Source environment has a cluster
defined. Copying this information between Production and Test can cause crossover connections,
where Test environments connecting to a cluster actually connect to the Production application
servers
Overwrite existing Application (if it exists): In general always select Drop All Application
tables prior to copy . It is possible for the Target application to have Scenario and Year data
populated that the Source application does not have, and not dropping these tables would
introduce variances in the newly copied Application compared to the Source Application. The
circumstances in which Only drop tables that are being copied would be a valid option would be
rare.
NOTE: The HFM_Errorlog table is not copied by this utility regardless of the options selected.
Page70of77
25.
1. AdvancedOptions
The Advanced Options dialog is broken up into three pages. Typically, it would not be required to
make any changes to any selections on these tabs, unless directed by Support to address a
specific situation.
Use Client-Side Cursors: This option will bring all row data to the client from the RDBMS server.
The server does not cache any data. All caching will occur on the client, meaning the client will
require more memory and the server requires less. Reduce the number of threads to 2 x Number
of CPUs if this option is selected. Use this option if Server-Side cursors fail.
Use Server-Side Cursors: This option will run faster and require less memory on the client. The
data set will be cached on the server (requiring more resources on the server). This is the default
option.
SQL Binding: This option specifies how the SQL statement is executed on the server. The
default is to use SQL binding. Change this option to not use SQL binding if excessive errors occur
or Multi-Step OLE DB Errors occur. It is best to leave this option on and then restart any failed
processes with this option disabled (if the error is a Multi-Step error).
Thread Usage: This option allows the user to specify the number of processing threads. The
minimum is one and the maximum is twenty. The default is the number of processors times 4.
This option basically controls how many current tables are being processed and has an impact on
the amount of network traffic and the load placed on Source and Target RDBMS servers.
Log SQL Errors: This option specifies whether to output every SQL error to the log file. Please
note, some errors are expected. You may see errors for the attempt to drop tables that do not
exist or the defaulting of sequence values. This is acceptable. Do not use the presence of SQL
errors in the log to gauge whether the processing succeeded. This option is not checked by
default to reduce confusion when reviewing the log
Number of Task retries: This option specifies the number of times a query should be reexecuted in the event of a failure. This is to resolve possible deadlock issues when inserting data
in the database.
2. DataOptions
The Data Options tab allows you to control what data is actually copied. The Copy Application
Data check box must be checked on the Options screen before any data will be copied. The
screen shot below shows non-default selections where the utility would only copy data in years
2006 and 2007 for the Actual Scenario:
3. YearOptions
Limit Data to one or more Years: Select this option when you need to copy a subset of historical
data. Be careful to consider the impact Rules may have when previous Year data is not copied.
4. ScenarioOptions
Page71of77
Limit data to one or more Scenarios: Select this option to copy only a subset of the overall
application. Be care to consider the impact Rules may have when Scenarios are not copied
5. DataOptions
Do not export Numeric Data: When this option is selected the numeric data is not copied but
cell text and line item detail information is copied.
Do not export User data (grids, forms, reports, etc): This is information maintained in the
USERPARAMS.
6. InvalidRecordsOptions
Note the warning that these options will impact performance and require more database sort
area. The utility does a join on the DCN and DCE tables with the Metadata ITEM tables.
Filter invalid Calc Status Records: Invalid Calc status records are the result of Metadata
changes. This option selects only the rows for which the entity and value exist in the database.
Filter invalid Data Records: Invalid Data status records are the result of Metadata changes. This
option selects only the rows where the entity, account, ICP, custom1-4 exist.
Filter Zero value data records: Zeros in the application can impact application performance.
The utility does not copy rows found to have zeros for all periods
7. DatabaseOptions
The Database Options tab allows for control over where the data is stored in the
database.Multipletablespacescanbeconfiguredbasedondatabasetabletypes
Data Table: consists of all Scenario/Year tables (DCN, DCE, CSN, CSE, LID, TXT, RTD, etc).
These tables are generally written to and read from quite frequently. They generally have large
amounts of relatively small rows.
Metadata Tables: consist of all of the Metadata based tables (DESC, LAYOUT, HEADER, ITEM).
These tables are read from and written to fairly infrequently. They have small numbers of small
rows.
System Tables: are read from rather frequently (HSV, HSX, HFM). Excluding the
HFM_ERRORLOG table (which is not read or written to by the Copy App utility), these tables
have small row counts
Audit Tables: generally have large numbers of rows of medium sized data. They are written to
rather frequently and read from infrequently.
BLOB Tables: have BLOB columns that are broken up to 2Kb chunks (Note: The current option
shows LOB tables, but will be changed to read BLOB in the next release). These tables are read
from more frequently than written to.
Data Tablespace: Allows you to control where data objects are created by copy utility. Change
from <Default> is only needed in environments where DBA wants to separate data and index
objects. Note that the HFM application server(s) should also be configured to use the same
tablespace options so new tables are created in the expected location. When the Target database
is MS SQL Server, you will see all File groups configured for the specific database configured in
the Target UDL. When the Target database is Oracle, you will see a list of all tablespaces that the
user has quota to create objects.
Page72of77
Index Tablespace: Allows you to control where index objects are created by copy utility. Change
from <Default> is only needed in environments where DBA wants to separate data and index
objects. Note that the HFM application server(s) should also be configured to use the same
tablespace options so new indexes are created in the expected location. When the Target
database is MS SQL Server, you will see all File groups configured for the specific database
configured in the Target UDL. When the Target database is Oracle, you will see a list of all
tablespaces that the user has quota to create objects.
This screen allows you to verify all settings before selecting Next to start the copy process
The processing status screen displays the current status of each task. To see the log entries for
any given task at any time during processing, simply double-click on the task row to display the
Task Entry Log screen.
NOTE: When the Source and Target are the same database and the same schema (user) the
utility does not process each table row by row, instead an INSERT INTO SELECT FROM
statement is used. As a result of this, the utility will not display a row count showing the number of
rows that have been processed but the log still will show the number of rows copied.
8. TaskEntryLogScreen
Completed Tasks:
Failed Tasks:
To see the log entries for any task, running or completed, double click on the entry in the Task
Status window. If the Display SQL Errors option has been selected, the error generated by the
RDBMS will also be displayed in the log.
If the Task Entry Log screen is displayed after all processing has completed, you will have the
option of restarting the task.
Restart Task screen:
Once all processing has completed, you can go to any task in the list, double-click on the entry
and activate the Restart Task page. From this page you can change task options and select the
Page73of77
Restart Task button. The task will then be re-executed with the new options (if any). The task
entry in the Processing Status screen will be updated with current Task progress.
If all tables have successfully copied then select OK to see the Finish screen
From the Finished screen, you can review the log file
TuningTCP/IP
The WINDOWS operating system uses default settings that work well on
average situations. These settings are not catering for latency situations
on a WAN and moving large data sets.
In most cases, significant improvements can be achieved by tuning the
TCP/IP settings in Windows. To do so, some basic data needs to be
acquired about the network connection to qualify it.
1. In case the Internet is used as the connection, the tooling to qualify and change
the settings is publicly available on www.speedguide.net and www.speedtest.net .
2. If the connection is MPLS based, settings must be adjusted in collaboration with
the network provider.
Example:
A benchmark was measured as before on a Pentium class PC in a 150300ms situation, this yielded 8seconds response time. The connection
bandwidth was 100Mbits/second and the effective sustained transfer rate
was approx. 2-7Mbits/second.
The TCP/IP settings were optimized based on the above values to
MTU=1500 and RWIN=512kb (default is 65kB). After the tuning, the
response time dropped to 5 seconds
The same tuning operation performed on a quad-core PC on the same
network conditions reduced the response time from 4 seconds down to 2.5
seconds
Page74of77
Guidance:
The reduction in response time originates from a reduction in the return
messages in the TCP/IP link, but also by an increase in efficiency in the
client software from the larger chunks of data available to the client layer.
The tuning also has a positive effect on browsing in general, so it is not
constrained to Hyperion and can be left in place when done.
Recommendations:
Most user PCs will benefit from TCP/IP tuning. The threshold of benefit is
as low as 30-50milliseconds of latency. Even on fast contemporary PCs
the improvement is noticeable and improves user perception.
OnDemandHFMDataandTaskAuditExtraction
Customer can use Data and Task audit feature in the HFM application to track
the changes in the application for auditing purpose, since it could be security
requirement in the company or to back track the changes if data have changed in
the
application
for
some
reason.
Data
Audit
is
stored
in
<APPNAME>_DATA_AUDIT
table
and
Task
audit
is
stored
in
<APPNAME>_TASK_AUDIT table. Each HFM application will have its own Data
Audit and Task audit tables.
Huge Data and Task tables can severely impact the HFM application
performance. It is a good practice to monitor these tables and purge them on a
regular basis. On Demand will set up this job during Production Assessment.
This same job can be set up in the Non-Production environment if tables are
growing too much and causing performance issues.
On Demand will set up a Scheduled Task on HFM Windows Server to run this job
that will monitor the Data Audit and Task Audit for a threshold and extract the
records into CSV format before purging the tables. The job will perform the
following:
o Monitor the <APPNAME>_DATA_AUDIT, <APPNAME_TASK_AUDIT> and
HFM_ERRORLOG
o Monitor
the
Tables
for
the
Record
limit
MAXIMUM_ALLOWED_RECORDS in the configuration file
defined
in
o When the Tables reach the limit, do the following:
Page75of77
Extract the Records using the HFMAuditExtract command line utility in

CSV format and save the file on the HFM Windows Server
Move the Records to the _HIST table so that records are available
before purge in case customer need them
Purge the Data Audit, Task Audit and Error Log Tables.
The utility allows the configuration file purge.ini to be customized per Customer
requirements. Some of the parameters that are configurable are: Application to
be monitored and Threshold to be monitored.
Purge.ini
[GLOBAL]
# List of applications that needs to be verified. The application names to be delimited by semi-colon(;)
# For example:# APPLICATIONS=APPS1;APPS2;APPS3....
APPLICATIONS=SAMPLE
# For specific tables, addd table names seperted by semicolon

TABLENAME=HFM_ERRORLOG
# Path of the HFMAuditExtractUtility.exe

AUDIT_EXTARCT_UTILITY=D:\od_stage\HFMAuditExtractUtility\CommandLine
Utility\x86\HFMAuditExtractCmdLine.exe
# The maximum allowed records in the hfm data/task audit tables.

MAXIMUM_ALLOWED_RECORDS=100000
# Path to the udl file

UDLFILE=D:\od_stage\Purge\ORACLE_hfm.udl
#Modify the below details for the data source(HOST,SID, PORT, USERNAME/PWD and Schema)
[DATASOURCE]
Page76of77
HOST=auhodtest01.oracle.com
SID=THYPW7
PORT=10510
USERNAME=hfm
PASSWORD=xxxxx
SCHEMA=hfm
Page77of77

Od 001370

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Od 001370

Caricato da

Copyright:

Formati disponibili

ON

HODCUSTADMIN AD policy for customer Hyperion Administrators for

If you want to allow X

Usage: /usr/local/bin/pbrun [policy] -x [target user]

Open Remote Desktop Connection from your desktop

Apache Web Server

Apache Web Server

Essbase Integration Server

Apache Web Server

Apache Web Server

Servertoaccessthickclients.(Pleaserefertothe Usage of RDP Server in On Demand

Oracle HTTP Server

Apache Web Server

Customer Short Code

This fourcharacter code uniquely identifies a Customers environment. It is

This is generated by concatenating the first letter of the environment type,

This can be the Production environment (PROD), the Production Support

Financial Reporting Studio

If you upgrade an application created in Classic application administration to Performance

Customer/Implementation Team is advised to tune them based on application

Start FDM services after Restore

in the Shared Services database

Customer/Implementer, taking those product limitations into consideration, to

Setup of new Planning applications

After the application and data is migrated, Oracle On Demand go through

Essbase Data Blocks comparison

It is advisable for Customer/Implementation Team to schedule the Production

o When the Tables reach the limit, do the following:

Extract the Records using the HFMAuditExtract command line utility in

# For specific tables, addd table names seperted by semicolon

# Path of the HFMAuditExtractUtility.exe

# The maximum allowed records in the hfm data/task audit tables.

# Path to the udl file

Potrebbero piacerti anche