hyperion® reporting and analysis – system 9€¦ · hyperion® reporting and analysis – system...

H Y P E R I O N ® R E P O R T I N G A N D A N A L Y S I S – S Y S T E M 9

R E L E A S E 9 . 3 . 1

I N S T A L L A T I O N G U I D E F O R W I N D O W S

Reporting and Analysis Installation Guide for Windows, 9.3.1

Copyright © 1989, 2008, Oracle and/or its affiliates. All rights reserved.

Authors: Marilyn Ghilardi

The Programs (which include both the software and documentation) contain proprietary information; they are providedunder a license agreement containing restrictions on use and disclosure and are also protected by copyright, patent, andother intellectual and industrial property laws. Reverse engineering, disassembly, or decompilation of the Programs, exceptto the extent required to obtain interoperability with other independently created software or as specified by law, isprohibited.

The information contained in this document is subject to change without notice. If you find any problems in thedocumentation, please report them to us in writing. This document is not warranted to be error-free. Except as may beexpressly permitted in your license agreement for these Programs, no part of these Programs may be reproduced ortransmitted in any form or by any means, electronic or mechanical, for any purpose.

If the Programs are delivered to the United States Government or anyone licensing or using the Programs on behalf of theUnited States Government, the following notice is applicable:

U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered toU.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to theapplicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication,disclosure, modification, and adaptation of the Programs, including documentation and technical data, shall be subjectto the licensing restrictions set forth in the applicable Oracle license agreement, and, to the extent applicable, the additionalrights set forth in FAR 52.227-19, Commercial Computer Software--Restricted Rights (June 1987). Oracle USA, Inc., 500Oracle Parkway, Redwood City, CA 94065.

The Programs are not intended for use in any nuclear, aviation, mass transit, medical, or other inherently dangerousapplications. It shall be the licensee's responsibility to take all appropriate fail-safe, backup, redundancy and other measuresto ensure the safe use of such applications if the Programs are used for such purposes, and we disclaim liability for anydamages caused by such use of the Programs.

Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of theirrespective owners.

The Programs may provide links to Web sites and access to content, products, and services from third parties. Oracle isnot responsible for the availability of, or any content provided on, third-party Web sites. You bear all risks associated withthe use of such content. If you choose to purchase any products or services from a third party, the relationship is directlybetween you and the third party. Oracle is not responsible for: (a) the quality of third-party products or services; or (b)fulfilling any of the terms of the agreement with the third party, including delivery of products or services and warrantyobligations related to purchased products or services. Oracle is not responsible for any loss or damage of any sort that youmay incur from dealing with any third party.

Contents

Chapter 1. Reporting and Analysis Architecture Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Hyperion and Enterprise Performance Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

About Reporting and Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Reporting and Analysis Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Client Layer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Application Layer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Application Layer Web Tier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Web Server Use in Hyperion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Application Layer Services Tier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Database Layer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Chapter 2. Planning the Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Preparing an RDBMS for the Reporting and Analysis Repository . . . . . . . . . . . . . . . . . . . 23

Backing Up a Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Configuring Database Software for the Reporting and Analysis Repository . . . . . . . . . 24

Configuring IBM DB2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

IBM DB2 with Web Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Configuring Microsoft SQL Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Configuring Oracle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Manually Creating Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Database Storage Parameters for Oracle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Creating ODBC Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Microsoft SQL Server Analysis Services (SSAS) Connections . . . . . . . . . . . . . . . . . . . 32

SSAS 2005 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

SSAS 2000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Obtaining and Preparing Pre-requisite Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

SAP Data Source Access and Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Configuring SAP Data Source Access and Authentication . . . . . . . . . . . . . . . . . . . . . 34

Installing the IBM Global Security Kit for WebSphere Express . . . . . . . . . . . . . . . . . . 34

Web Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Application Server Setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Web Browser Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Contents iii

Configuring a Web Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Financial Reporting and Web Analysis Web Server Environment . . . . . . . . . . . . . 35

Financial Management Web Server Environment . . . . . . . . . . . . . . . . . . . . . . . . 36

Browser Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Module-specific Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Configuring a Production Reporting Server Installation . . . . . . . . . . . . . . . . . . . . . . 37

Financial Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Financial Reporting Print Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Importing Financial Reporting Content into Microsoft Word and Powerpoint . . . 37

Cell Attachment Support and Configuration Requirements . . . . . . . . . . . . . . . . . 37

Print Server Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Installing Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Satisfying Temporary Space Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Command Line Processor Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Port Numbers Used by Hyperion Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Chapter 3. Installing Reporting and Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Terminal Services Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Reporting and Analysis Installers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Reporting and Analysis Module Installers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

About Hyperion Home . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Hyperion Home Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Files Installed in the HYPERION_HOME Directory . . . . . . . . . . . . . . . . . . . . . . . . . 44

Changing the Hyperion Home Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Installing Reporting and Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Running Silent Installations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Chapter 4. Configuring Reporting and Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Hyperion Configuration Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Task Sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Restricted Characters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Satisfying Initial Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Configuring Product Upgrades . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Configuring Reporting and Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Registering With Shared Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Configuring Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Microsoft SQL Server Windows Authentication . . . . . . . . . . . . . . . . . . . . . . . . . 54

iv Contents

Specifying Application Server Hostnames and Web Server Connector Plug-inPorts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Deploying to the Application Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

What Happens During Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

WebSphere and WebLogic 9.1.x . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

WebLogic 8.1.x . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Enabling the Web Server Plug-in . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Hyperion Configuration Utility Web Server Plug-in Support . . . . . . . . . . . . . . . . 58

Web Server Plug-in Manual Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Completing Module-Specific Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Workspace Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Customizing the Context Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Specifying the GSM Host and Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Customizing Service Ports for Reporting and Analysis . . . . . . . . . . . . . . . . . . . . 60

Configuring the SQR Production Reporting Engine for Interactive Reporting . . . . 60

Interactive Reporting Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Financial Reporting Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Enabling the Planning ADM Driver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Enabling the Analytic Provider Services Driver . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Print Server Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Workspace, Print Server, and Scheduler Server Configurations . . . . . . . . . . . . . . 63

Report Server Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Web Analysis Configuration - Enabling the Analytic Provider Services Driver . . . . . . . 63

SQR Production Reporting Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

Reconfiguring Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

Testing Module Availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

Post Configuration Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Error Messages When Testing Module Availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Post Configuration Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

Configuring WebLogic 9.x OpenJMS for Web Analysis . . . . . . . . . . . . . . . . . . . . . . . 66

Installing OpenJMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

Configuring OpenJMS Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

Configuring and Starting OpenJMS Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

Configuring Web Analysis to use OpenJMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

Setting up WebSphere 6.0 OpenJMS and Web Analysis . . . . . . . . . . . . . . . . . . . . . . . 70

Configuring WebSphere 6.0 Embedded Messaging and Web Analysis Cluster(Reporting and Analysis ) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

Configure Web Analysis to use WebSphere JMS . . . . . . . . . . . . . . . . . . . . . . . . . 71

Verifying Startup Dependencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

Contents v

Starting Shared Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

Verifying Successful Startup of Shared Services . . . . . . . . . . . . . . . . . . . . . . . . . . 73

Stopping Shared Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

Reporting and Analysis Administrator User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Launching Reporting and Analysis Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Adding Content Expiration Headers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

Changing the Apache Web Server Listen Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Customizing Ports Used by Interactive Reporting Service, Interactive Reporting JobService and Interactive Reporting Data Access Service . . . . . . . . . . . . . . . . . . . . . . . 77

Guidelines for Changing Port Ranges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

Service Types Used in irmconfig.xml . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

Sample irmconfig.xml . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

Setting up SiteMinder with Transparent Logon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

Enabling the SiteMinder Web Agent for Microsoft IIS . . . . . . . . . . . . . . . . . . . . . 81

Creating the IBM HTTP Server/Apache Web Agent Configuration File . . . . . . . . 81

Configuring IBM HTTP Server/Apache SiteMinder Modules . . . . . . . . . . . . . . . . 81

Configuring the SiteMinder Policy Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

Setting up Workspace Web Application Parameters . . . . . . . . . . . . . . . . . . . . . . 83

Setting the Trusted Password on the Authentication Service . . . . . . . . . . . . . . . . 84

Configuring Shared Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

Restarting Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

Chapter 5. Uninstalling and Reinstalling Reporting and Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

Deregistering Reporting and Analysis with Shared Services . . . . . . . . . . . . . . . . . . . . . . . 87

Uninstalling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

Reinstalling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

Reinstalling Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

Reinstalling UIServices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

Reinstalling Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

Chapter 6. Upgrading Reporting and Analysis from 9.x to 9.3.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

Upgrading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

Migrating Users and Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

About SyncCSSIdentity_BI Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

Running SyncCSSIdentity_BI utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

Using Most Provider Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

vi Contents

Using Provider Type Sun One LDAP Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

Upgrading Manually Deployed Web Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

Chapter 7. Installing the Reporting and Analysis Migration Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

Migration Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100

Supported Source Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100

Installing the Migration Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

After Installing the Migration Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102

Chapter 8. Configuring a Web Server with Apache Tomcat . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

Configuring Apache . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

Copy Required Files to the Apache Machine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

Create the Tomcat Web Server Plug-in Configuration Files . . . . . . . . . . . . . . . . . . . 104

Enable the Tomcat Web Server Plug-in in httpd.conf . . . . . . . . . . . . . . . . . . . . . 105

Create Aliases for Workspace and Web Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

Restart Apache and Test the Tomcat Web Server Plug-in . . . . . . . . . . . . . . . . . . . . . 106

Configuring IIS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

Copy Required Files to the IIS Machine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

Create the Tomcat HTTP Plug-in Configuration Files . . . . . . . . . . . . . . . . . . . . . . . 107

Create a Virtual Directory for the Tomcat HTTP Plug-in . . . . . . . . . . . . . . . . . . . . . 109

Register the Tomcat HTTP Plug-in as an ISAPI Filter . . . . . . . . . . . . . . . . . . . . . . . 109

Create Virtual Directory Aliases for Workspace and Web Analysis . . . . . . . . . . . . . . 110

Restart IIS and Test the Tomcat HTTP Plug-in . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

Chapter 9. Manually Deploying into Oracle 10g Release 3 (10.1.3.1.0) Application Server . . . . . . . . . . . . . . 113

Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

Deploying Workspace Web Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114

Creating an OC4J Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114

Configuring the Workspace OC4J Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114

Deploying workspace.war . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115

Configuring Workspace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115

Enabling SAP as an Authentication Provider . . . . . . . . . . . . . . . . . . . . . . . . . . . 115

Creating context.properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116

Modifying portlet.xml . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

Update Oracle HTTP Server Routing for Workspace . . . . . . . . . . . . . . . . . . . . . 118

Updating Configuration Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118

Deploying Financial Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119


Configuring the FinancialReporting OC4J Instance . . . . . . . . . . . . . . . . . . . . . . . . . 120

Contents vii

Deploying HReports.ear . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

Deploying Web Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122


Configuring the WebAnalysis OC4J Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122

Deploying WebAnalysis.ear . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124

Configuring Oracle HTTP Server for Oracle 10g Release 3 . . . . . . . . . . . . . . . . . . . . . . . 125

Configuring Reporting and Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125

Configuring Financial Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127

Configuring Oracle Single Sign-on on Oracle 10g Release 3 . . . . . . . . . . . . . . . . . . . . . . 127

Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127

Configuring the Oracle Application Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127

Configuring Shared Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131

Testing Module Availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131

Post Configuration Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132

Chapter 10. Manually Deploying into Oracle 10g Release 2 (10.1.2.0.2) Application Server . . . . . . . . . . . . . 133

Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133

Deploying Workspace Web Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134


Configuring an OC4J Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134

Deploying workspace.war . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135

Using Oracle Enterprise Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135

Using Oracle Distributed Configuration Management Command Line Utility . . . . . 136


Enabling SAP as an Authentication Provider . . . . . . . . . . . . . . . . . . . . . . . . . . 136

Creating context.properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137

Updating Configuration Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138




Configuring a FinancialReporting OC4J Instance . . . . . . . . . . . . . . . . . . . . . . . . . . 140

Deploying HReports.ear . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142

Using Oracle Enterprise Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142

Using Oracle Distributed Configuration Management Command LineUtility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142



Configuring the WebAnalysis OC4J Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144

Environment Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144

Deploying WebAnalysis.ear . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145

viii Contents

Using Oracle Enterprise Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145

Using Oracle Distributed Configuration Management Command Line Utility . . . . . 145

Configuring Oracle HTTP Server for Oracle 10g Release 2 . . . . . . . . . . . . . . . . . . . . . . . 146

Configuring Reporting and Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146

Configuring Performance Management Architect or Planning . . . . . . . . . . . . . . . . . 147

Configuring Financial Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148

Defining Additional Parameters for Workspace . . . . . . . . . . . . . . . . . . . . . . . . . . . 148

Configuring Oracle Single Sign-On on Oracle 10g Release 2 . . . . . . . . . . . . . . . . . . . . . . 149

Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149

Configuring the Oracle Application Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149

Configuring Shared Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152



Chapter 11. Manually Deploying into WebLogic 9.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155

Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155

Preparing the Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155

Deploying Workspace into WebLogic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156

Creating a New Domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156

Modifying setDomainEnv.cmd . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156

Deploying Workspace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157

Modifying portlets.xml . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158

Post Deployment for Workspace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159

Creating context.properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159

Deploying Financial Reporting into WebLogic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159

Deploying Web Analysis into WebLogic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160

Verifying Web Analysis Environment Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . 160

Deploying Web Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160

Configuring a Web Server for WebLogic 9.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161

Configuring Apache HTTP Plug-in . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161

Configuring for Reporting and Analysis and Hyperion Applications . . . . . . . . . . 162

Configuring for Performance Management Architect . . . . . . . . . . . . . . . . . . . . 169

Configuring for Financial Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169

Configuring for Performance Scorecard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170

Configuring for Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170

Configuring Microsoft IIS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171

Configure Proxying by Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171

Register iisforward.dll with IIS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172

Configure Proxy by File Extension . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173

Contents ix

Restart IIS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178



Chapter 12. Manually Deploying into WebLogic 8.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181

Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181

Creating WebLogic Domains . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181

Deploying Workspace into WebLogic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182

Modifying startWebLogic.bat . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182

Deploying Workspace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183


Post Deployment for Workspace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185

Compiling JSP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185

Creating context.properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185

Deploying Financial Reporting into WebLogic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186

Deploying Web Analysis into WebLogic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186

Web Analysis Environment Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186

Deploying Web Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187

Configuring a Web Server for WebLogic 8.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187

Configuring Apache . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187

Configuring with Reporting and Analysis and Hyperion Applications . . . . . . . . . 188

Configuring with Performance Management Architect with Apache WebServer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195

Configuring with Financial Management with Apache Web Server . . . . . . . . . . 195

Configuring with Performance Scorecard with Apache Web Server . . . . . . . . . . 196

Configuring with Planning with Apache Web Server . . . . . . . . . . . . . . . . . . . . . 196

Configuring Microsoft IIS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197

Configure Proxying by Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197

Register iisforward.dll with IIS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198

Configure Proxy by File Extension . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199

Restart IIS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204



Chapter 13. Manually Deploying into WebSphere 6.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207

Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207

Preparing the WebSphere Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207

WebSphere ND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208

WebSphere BASE/Express . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208

Add Virtual Host Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208

x Contents

Deploying Workspace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209

Creating a WebSphere Shared Library for SAP Authentication . . . . . . . . . . . . . . . . . 210

Assigning SAP_LIBRARY to Workspace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210

Creating context.properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210




Configuring Financial Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214


Deploying . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214


Creating a WebSphere Shared Library for SAP Authentication and Reporting . . . . . . 215

Configuring Web Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216

Configuring a Web Server with WebSphere 6.1 Application Server . . . . . . . . . . . . . . . . . 217

Configuring Apache Server or IBM HTTP Server . . . . . . . . . . . . . . . . . . . . . . . . . . 217

Configuring IIS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219

Configuring Financial Management with a Web Server . . . . . . . . . . . . . . . . . . . . . . 224

Configuring Financial Management with Apache Web Server or IBM HTTPServer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224

Using Only IIS with Financial Management . . . . . . . . . . . . . . . . . . . . . . . . . . . 225



Chapter 14. Manually Deploying into WebSphere 6.0.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227

Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227

Preparing the WebSphere Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227

WebSphere ND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228

WebSphere BASE/Express . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228

Add Virtual Host Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228

Deploying Workspace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229

Creating a WebSphere Shared Library for SAP Authentication . . . . . . . . . . . . . . . . . 230

Assigning SAP_LIBRARY to Workspace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231

Creating context.properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231



Deploying and Configuring Financial Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233


Deploying . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234


Creating a WebSphere Shared Library for SAP Authentication and Reporting . . . . . . 236

Contents xi

Configuring Web Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237

Configuring a Web Server with WebSphere 6.0.2 Application Server . . . . . . . . . . . . . . . 237

Configuring Apache Server or IBM HTTP Server . . . . . . . . . . . . . . . . . . . . . . . . . . 237

Configuring IIS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240

Configuring Financial Management with a Web Server . . . . . . . . . . . . . . . . . . . . . . 245

Configuring Financial Management with Apache Web Server or IBM HTTPServer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245

Using Only IIS with Financial Management . . . . . . . . . . . . . . . . . . . . . . . . . . . 245



Appendix A. ActiveX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247

Whitepaper . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247

Sample Policy File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251

xii Contents

1Reporting and AnalysisArchitecture Overview

In This Chapter

Hyperion and Enterprise Performance Management .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13

About Reporting and Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13

Reporting and Analysis Architecture ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14

Hyperion and Enterprise Performance ManagementHyperion offers a comprehensive Enterprise Performance Management (EPM) system thatconsists of these products:

● Oracle's Hyperion® Reporting and Analysis – System 9—Management reporting includingquery and analysis in one coordinated environment

● Oracle's Hyperion Applications—Coordinated planning, consolidation, and scorecardingapplications

● Oracle's Hyperion® Foundation Services—Used to ease installation and configuration,provide metadata management, and support a common Microsoft Office interface

About Reporting and AnalysisReporting and Analysis is a modular business intelligence platform that provides managementreporting, query, and analysis capabilities for a wide variety of data sources in one coordinatedenvironment.

One zero-footprint Web-based thin client provides users with access to content:

● Financial reporting for scheduled or on-demand highly formatted financial and operationalreporting from most data sources including Oracle's Hyperion® Planning – System 9 andOracle's Hyperion® Financial Management – System 9

● Interactive reporting for ad hoc relational queries, self-service reporting and dashboardsagainst ODBC data sources

● Production reporting for high volume enterprise-wide production reporting

● Web analysis for interactive ad hoc analysis, presentation, and reporting ofmultidimensional data

Hyperion and Enterprise Performance Management 13

Reporting and Analysis, which includes Oracle's Hyperion® Essbase® – System 9, is part of acomprehensive EPM system that integrates this business intelligence platform with Oracle'sHyperion financial applications and Oracle's Hyperion® Performance Scorecard – System 9.

Reporting and Analysis ArchitectureThe Reporting and Analysis environment is organized into three layers:

● “Client Layer” on page 14

● “Application Layer” on page 15

● “Database Layer” on page 22

Client LayerThe client layer refers to local interfaces used to author, model, analyze, present, report, anddistribute diverse content, and third-party clients, such as Microsoft Office:

● Oracle's Hyperion® Workspace—Web-based DHTML zero-footprint client that providesthe user interface for viewing and interacting with content created by the authoring studios,and enables users to create queries against relational and multidimensional data sources:

❍ Oracle's Hyperion Essbase — System 9—High performance multidimensionalmodeling, analysis, and reporting

❍ Oracle's Hyperion® Financial Reporting – System 9—Highly formatted financialreporting

❍ Oracle's Hyperion® Interactive Reporting – System 9—Ad hoc query, analysis, andreporting including dashboards

❍ Oracle's Hyperion® SQR® Production Reporting – System 9—High volume enterpriseproduction reporting

❍ Oracle's Hyperion® Web Analysis – System 9—Advanced interactive ad hoc analysis,presentation, and reporting against multidimensional data sources

● Authoring Studios

❍ Oracle's Hyperion® Interactive Reporting Studio—Highly intuitive and easy-to-navigate environment for data exploration and decision making. A consistent designparadigm and robust formatting tools enable users to easily build free-form,presentation-quality reports for broad-scale publishing across their organization.

❍ Oracle's Hyperion® Interactive Reporting Web Client—Read-only Web plug-in forviewing Interactive Reporting documents.

❍ Oracle's Hyperion® Financial Reporting Studio—Windows client for authoring highlyformatted financial reports from multidimensional data sources, which features easy,drag and drop, reusable components to build and distribute HTML, PDF, and hardcopyoutput.

14 Reporting and Analysis Architecture Overview

❍ Oracle's Hyperion® Web Analysis Studio—Java applet that enables you to create,analyze, present, and report multidimensional content. The studio offers the completeWeb Analysis feature set to designers creating content, including dashboards forinformation consumers.

❍ Oracle's Hyperion® SQR® Production Reporting Studio—Windows client thatprovides the design environment for creating reports from a wide variety of data sources.Reports can be processed in one pass to produce a diverse array of pixel-perfect output.Processing can be scheduled and independently automated, or designed to use formtemplates that prompt dynamic user input.

❍ Oracle's Hyperion® Dashboard Development Services—Enables creation ofdashboards:

❏ Dashboard Studio—Windows client that utilizes extensible and customizabletemplates to create interactive, analytical dashboards without the need to codeprogramming logic.

❏ Windows-based integrated—Windows-based integrated developmentenvironment that enables programmers to swiftly code, test, and debug componentsutilized by Dashboard Studio.

❏ Performance Scorecard—Web-based solution for setting goals and monitoringbusiness performance using recognized scorecarding methodologies. Provides toolsthat enable users to formulate and communicate organizational strategy andaccountability structures:

● Key Performance Indicators (KPIs)—Create tasks and achievements thatindicate progress toward key goals

● Performance indicators—Indicate good, acceptable, or poor performance ofaccountability teams and employees

● Strategy maps—Relate high-level mission and vision statements to lower-levelactionable strategy elements

● Accountability maps—Identify those responsible for actionable objectives

● Cause and Effect maps—Depict interrelationships of strategy elements andmeasure the impact of changing strategies and performance

● Oracle's Hyperion® Smart View for Office—Hyperion-specific Microsoft add-in andtoolbar from which users can query Hyperion data sources including Essbase, FinancialManagement, and Planning. Users can use this environment to interact with FinancialManagement and Planning forms for data input, and can browse the Reporting and Analysisrepository and embed documents in the office environment. Documents are updated byuser request.

Application LayerThe application layer—a middle tier that retrieves requested information and manages security,communication, and integration—contains two components:

● “Application Layer Web Tier” on page 16

Reporting and Analysis Architecture 15

● “Application Layer Services Tier” on page 17

Because the business intelligence platform is modular, it may consist of various combinationsof components, configured in numerous ways. The end result is a comprehensive, flexiblearchitecture that accommodates implementation and business needs.

Application Layer Web TierThe application layer relies upon a J2EE application server and Web server to send and receivecontent from Web clients. An HTTP connector is required to link the Web server and theapplication server.

The Web tier hosts the Workspace, Interactive Reporting, Financial Reporting, and Web AnalysisWeb applications.

For a complete description of supported Web tier hardware and software, see the HyperionInstallation Start Here.

Web Server Use in HyperionHyperion components often are distributed across physical hardware resources, and are alwaysdistributed among multiple application server instances. All Hyperion components accessedthrough the Workspace must share the Web server hostname and port. A Web server is used tofulfill this requirement.

Using vendor provided Web server plug-ins, the Web server used by Hyperion acts as a reverseproxy to route client requests. Requests may be handled in part by the Web server itself, such asrequests for static images that exist on the same machine as the Web server, or routed to theappropriate Hyperion application server instance for processing.

Workspace utilizes Uniform Resource Identifiers (URIs) to contact other Hyperion componentsusing the http(s) protocol. The hostname and port used in the URI is taken from the HyperionURI, as supplied by the client.

Consider the following example, which illustrates the relationship between:

● Workspace—Deployed to Apache Tomcat on Machine A, and is configured to acceptrequests on TCP port 45000

● Financial Reporting Web component—Deployed to Apache Tomcat on MachineB, and isconfigured to accept requests on TCP port 8200

● Web server—Microsoft IIS Web server is installed on Machine C, and configured to acceptincoming requests on TCP port 19000

In the above configuration, the Apache Tomcat Web Server plug-in is configured for IIS. It willroute dynamic content requests to the /workspace context to MachineA:45000/workspace, andwill route all requests to the /hr context to MachineB:8200/hr. Static content requests, such asimages, to /workspace will be served directly by IIS from a directory local to Machine C.

Users of this system will access Workspace using the URI:

http://MachineC:19000/workspace/.


When users request a Financial Reporting document, the Workspace will process the requestusing the URI

http://MachineC:19000/hr.

If a user attempted to access Workspace using

http://MachineA:45000/workspace/

retrieval of Financial Reporting documents would fail, as the Workspace would construct URIsusing

http://machineA:45000/hr.

You must use proper Web server and Web server plug-in configurations:

● Tomcat: Chapter 8, “Configuring a Web Server with Apache Tomcat”

● Oracle 10g Release 3: “Configuring Oracle HTTP Server for Oracle 10g Release 3” on page125

● Oracle 10g Release 2:“Configuring Oracle HTTP Server for Oracle 10g Release 2” on page146

● WebLogic 9.1: “Configuring a Web Server for WebLogic 9.1” on page 161

● WebLogic 8.1: “Configuring a Web Server for WebLogic 8.1” on page 187

● WebSphere 6.1: “Configuring a Web Server with WebSphere 6.1 Application Server” onpage 217

● WebSphere 6.0.2: “Configuring a Web Server with WebSphere 6.0.2 Application Server” onpage 237

Application Layer Services TierThe application layer services tier contains services and servers that control functionality ofvarious Web applications and clients:

● “Core Services” on page 18

● “Interactive Reporting Services” on page 19

● “Financial Reporting Servers” on page 20

● “SQR Production Reporting Service” on page 20

● “Assistive Hyperion Services” on page 20

Most services fall into two main groups, depending on the tool used to configure their properties:

● Local services–Services in the local Install Home that are configured using the Local ServiceConfigurator (LSC). Referred to as LSC services.

● Remote services–Services on a local or remote host that are configured using the RemoteService Configurator (RSC). Referred to as RSC services.

Because most of these services are replicable, you may encounter multiple instances of a servicein a system.


Core Services

Core Services are mandatory for authorization, session management, and documentpublication:

● Repository Service—Stores Hyperion system data in supported relational database tables,known collectively as the repository. Repository Service is replicable; if replicated, it mustbe replicated and co-located with Publisher Service.

● Publisher Service—Handles repository communication for other LSC services and someWeb application requests; forwards repository requests to Repository Service and passesreplies back to initiating services. Publisher Service is replicable; if replicated, it must bereplicated and co-located with Repository Service.

● Global Service Manager (GSM)—Tracks system configuration information and monitorsregistered services in the system. A system can have only one GSM.

● Local Service Manager (LSM)—Created for every instance of an LSC or RSC service,including GSM. When system servers start, they register their services and configurationinformation with GSM, which supplies and maintains references to all other registeredservices.

● Authentication Service—Checks user credentials at logon time and determines whetherthey can connect; determines group memberships, which, along with roles, affects whatcontent and other system artifacts (resources) users can view and modify. AuthenticationService is replicable and does not need to be co-located with other services.

● Authorization Service—Provides security at the level of resources and actions; managesroles and their associations with operations, users, groups, and other roles. A system musthave at least one Authorization Service.

● Session Manager Service—Monitors and maintains the number of simultaneous systemusers. Monitors all current sessions and terminates sessions that are idle for more than aspecified time period. While Session Manager is replicable, each instance independentlymanages a set of sessions.

● Service Broker—Supports GSM and LSMs by routing client requests and managing loadbalancing for RSC services. A system can have multiple Service Brokers.

● Name Service—Monitors registered RSC services in the system, and provides them withsystem configuration information from server.xml. Works in conjunction with ServiceBroker to route client requests to RSC services. A system can have only one Name Service.

● Management services—Core Services that collect and distribute system messages and eventsfor troubleshooting and usage analysis:

❍ Logging Service—Centralized service for recording system messages to log files. Asystem can have only one Logging Service.

❍ Usage Service—Records the number and nature of processes addressed by HyperionInteractive Reporting Service, which enables administrators to review usage statisticssuch as the number of logons, what the most used files are, what the most selected MIMEtypes are, and what happens to system output. Systems can have multiple Usage Services.

● Functional services—Core Services that are specific to various functional modules:


❍ Job Service—Executes scripts that create reports, which can be prompted by users withpermissions or by Event Service. Report output is returned to initiating users orpublished to the repository. Job Services can be created and configured for everyexecutable.

❍ Event Service—Manages subscriptions to system resources. Tracks user subscriptions,job parameters, events and exceptions, and prompts Job Service to execute scheduledjobs. Event Service is configured to distribute content through e-mail and FTP sites, andto notify users with subscriptions about changing resources. A system can have only oneEvent Service.

● Oracle's Hyperion® Impact Management Services—Core Services that enable you toharvest, update, and publish new Interactive Reporting content from old InteractiveReporting repository resources. These services must be used in conjunction with InteractiveReporting services. Both services perform automatic load balancing and fault tolerance whenmultiple instances are running:

❍ Assessment (Harvester) Service—Harvests metadata from published InteractiveReporting repository documents.

❍ Update (Transformer) Service—Updates published and harvested InteractiveReporting documents or publishes new versions to the repository.

Interactive Reporting Services

Interactive Reporting services are Core Services that support Interactive Reporting functionalityby communicating with data sources, starting RSC services, and distributing InteractiveReporting client content:

● Hyperion Interactive Reporting Service—Runs Interactive Reporting jobs and deliversinteractive HTML content for Interactive Reporting files. When actions involvingInteractive Reporting documents are requested, Hyperion Interactive Reporting Servicefulfills such requests by obtaining and processing the documents and delivering HTML fordisplay.

● Hyperion Interactive Reporting Data Access Service—Provides access to relational andmultidimensional databases, and carries out database queries for the plug-in, HyperionInteractive Reporting Service, and Interactive Reporting jobs. Each Hyperion InteractiveReporting Data Access Service supports connectivity to multiple data sources, using theconnection information in one or more Interactive Reporting database connection files, sothat one Hyperion Interactive Reporting Data Access Service can process a document whosesections require multiple data sources. Hyperion Interactive Reporting Data Access Servicemaintains a connection pool for database connections.

● Extended Access for Hyperion Interactive Reporting Service—Enables users to jointlyanalyze multidimensional and relational sources in one document. It retrieves flattenedOLAP results from Web Analysis documents, SQR Production Reporting job output, orFinancial Reporting Batch reports in the Reporting and Analysis repository and importsdata into Interactive Reporting documents (.bqy) as Results sections.


Financial Reporting Servers

Financial Reporting servers support Financial Reporting functionality by processing batchrequests, generating output, and distributing Financial Reporting client content:

● Hyperion Financial Reporting Server—Generates and formats dynamic report or bookresults, including specified calculations. Hyperion Financial Reporting Server can handlenumerous simultaneous requests for report execution from multiple clients, because eachrequest is run on its own execution thread. Hyperion Financial Reporting Server caches datasource connections, so multiple requests by the same user do not require a re-connection.Financial Reporting servers are replicable—the number necessary depends on the numberof concurrent users who want to execute reports simultaneously through the clients.Multiple Financial Reporting servers can be configured to report against one repository.

● Hyperion Financial Reporting Communication Server—Provides a Java RMI Registry towhich other Financial Reporting servers are bound.

● Hyperion Financial Reporting Print Server—Enables Financial Reporting content to becompiled as PDF output. Runs only on supported Windows platforms, but is replicable toprovide scalability for PDF generation.

● Hyperion Financial Reporting Scheduler Server—Responds to Financial Reportingscheduled batch requests. At the specified time, Hyperion Financial Reporting SchedulerServer prompts the other Financial Reporting servers to fulfill the request.

SQR Production Reporting Service

SQR Production Reporting Service responds to scheduled and on-demand requests by JobService to run jobs, process data, and generate reports. SQR Production Reporting Service isoptimized for high volume reporting through the use of native drivers, array processing for largedata sets, and cursor management. It processes time-saving data manipulation operations in onepass of the data source and produces large quantities of reports in online and printed formats.SQR Production Reporting Service is a replicable service.

Assistive Hyperion Services

● Performance Scorecard Services—Support Performance Scorecard client functionality usedin conjunction with Reporting and Analysis.

● Oracle's Hyperion® Shared Services—Supports authentication and user provisioning forall Hyperion products. See the Shared Services documentation set.

● Smart View Services—Provide a common Microsoft Office interface for Hyperion products.See the Smart View documentation set.

Services Tier Summary

LSC or RSC Service Type Name Instances

LSC Core Authentication Service Multiple


LSC or RSC Service Type Name Instances

Core Authorization Service Multiple

Core Global Service Manager 1 per system

Core Local Service Manager Multiple

Core Publisher Service Multiple

Core Session Manager Multiple

Impact Management Assessment (Harvester) Service Multiple

Impact Management Update (Transformer) Service Multiple

Interactive Reporting Extended Access for Hyperion Interactive Reporting Service Multiple

Interactive Reporting Extended Access for Hyperion Interactive Reporting Service Multiple

Interactive Reporting Hyperion Interactive Reporting Data Access Service Multiple

Interactive Reporting Hyperion Interactive Reporting Service Multiple

Management Logging Service 1 per system

Management Usage Service Multiple

RSC Core Name Service 1 per system

Core Repository Service Multiple

Core Service Broker Multiple

Functional Event Service 1 per system

Functional Job Service Multiple

Assistive Hyperion Common Administration Services Shared Services 1 per system

Financial Reporting Servers Financial Reporting Communication Server

Financial Reporting Servers Financial Reporting Print Server Multiple

Financial Reporting Servers Financial Reporting Scheduler Server

Financial Reporting Servers Financial Reporting Server Multiple

Performance Scorecard Services Scorecard Module Services

SQR Production Reporting Service SQR Production Reporting Service Multiple

Smart View Services Oracle's Hyperion® Smart View for Office Services Multiple


Database LayerArchitecturally, databases fall into two fundamental groups: repositories that store Hyperionsystem data; and data sources that are the subject of analysis, presentation, and reporting.

There are two important repositories for information storage:

● Common repository—Hyperion system data in supported relational database tables

● Shared Services—User, security, and project data that can be used across Hyperion products

Data Sources:

● Relational data sources, for example, Oracle, IBM DB2, and Microsoft SQL Server

● Multidimensional data sources, for example, Essbase

● Oracle's Hyperion applications, for example, Financial Management and Planning

● Data warehouses

● ODBC data sources

For a complete description of supported data sources, see the Hyperion Installation Start Here.


2Planning the Installation

In This Chapter

Preparing an RDBMS for the Reporting and Analysis Repository.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23

Obtaining and Preparing Pre-requisite Software ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33

Web Environment .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35

Browser Settings ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .36

Module-specific Prerequisites .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37

Installing Considerations ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .39

Port Numbers Used by Hyperion Products.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .40

Hyperion no longer ships or requires Oracle's Hyperion® License Server™ (or standalone licensefiles) for use with Hyperion products.

To ensure compliance with your license agreement, Hyperion recommends that you implementan auditing process. In addition, during product configuration with Oracle's Hyperion®Configuration Utility™, you activate only the features you purchased. For more information,see “Hyperion License Compliance” in Hyperion Installation Start Here.

Note:

Reporting and Analysis is supported on the platforms specified in the tables included in thischapter. Subsequent maintenance releases and service packs may be used where the vendorasserts backward compatibility. Please be aware that while these assertions are made in goodfaith, certain incompatibilities may exist. In the event that an incompatibility is identified,Hyperion may experience a delay in reproducing and fixing resultant issues for the affectedversions.

Preparing an RDBMS for the Reporting and Analysis Repository

Backing Up a RepositoryIf you are performing an upgrade from a previous release of Reporting and Analysis, Hyperionrecommends you back up the following directories, files, and repository before upgrading,migrating, or reinstalling.

● RDBMS, all tables in the repository

Preparing an RDBMS for the Reporting and Analysis Repository 23

● File system, all installation homes on all machines which includes the physical files in therepository that are maintained on disk

● Back up the repository (full database dump after the instance is shut down, before theupdates to the instance or migration).

● Back up vpd.properties in the installing user’s %SystemRoot% directory.

Configuring Database Software for the Reporting andAnalysis RepositoryRepository databases are the relational databases that Reporting and Analysis uses to store andmanage the application metadata. See Hyperion Installation Start Here to review the supportedrepository and data source databases.

Note:

The amount of space needed depends on the aggregate size of the objects you plan to store inthe repository. Hyperion suggests starting with at least 250 MB, which provides room to growthe Reporting and Analysis repository without having to increase the data file or tablespace.

Reporting and Analysis requires a repository database to store its persistent data. You mustconfigure your system for use with a database Reporting and Analysis. See:

● “Configuring IBM DB2” on page 24

● “IBM DB2 with Web Analysis” on page 27

● “Configuring Microsoft SQL Server” on page 27

● “Configuring Oracle” on page 28

Configuring IBM DB2After installing IBM DB2, record the IBM DB2 database host name, port number, and servicename for use when you install the Reporting and Analysis products.

Note:

A database administrator should perform the following procedures.

➤ To configure your system for use with IBM DB2:

1 Create an operating system user account for DB2.

Hyperion suggests you name the database user biplus

2 Create a database within a DB2 instance for Reporting and Analysis.

Create a Database for Reporting and Analysis. Hyperion recommends you create the databaseusing UTF-8 encoding for the best compatibility with non-ASCII character sets. To create the

24 Planning the Installation

database, run the DB2 Command Line Processor or Command Center as the DB2 instance ownerand enter the following commands:

CREATE DATABASE database_name USING CODESET UTF-8 TERRITORY US

TERMINATE

Plan the repository size. Hyperion suggests starting with 250 MB minimum, which providesroom to grow the Reporting and Analysis repository without having to increase the data file ortablespace.

3 Log on to the DB2 Control Center as the DB2 administrator and add the operating system user you createdin Step 1 to the DB2 database.

This provides Reporting and Analysis access to your database. The Reporting and Analysis userowns the Reporting and Analysis database tables that are built and populated and objects thatare created during installation. Reporting and Analysis services use one database-connection,user account.

Note:

By default, the case-sensitive settings for all data bases is set to OFF.

4 Modify the DB2 database:

● Increase the following:

❍ bufferpool from 1000 (default) to 32000 (about the size of thelargest audit table and indexes)

❍ IBMDEFAULTBP bufferpool from 1000(default) to 100000

❍ bufferpool from 1000(default) to 8000 (temporary spacebufferpool)

❍ DBHEAP from 1200(default) to 33000

❍ SORTHEAP from 256(default) to 2000

❍ LOGBFSIZ from 16(default) to 128

● A bufferpool and a tablespace with a 16 KB pagesize

● A system temporary bufferpool and a system temporary tablespace with an 16 KB pagesize

● Tablespace access, database connect, and create table privileges for the Reporting andAnalysis user

● drda_heap_sz parameter set to 2048 or higher

● stmtheap, applheapsz, and app_ctl_heap_sz parameters set to 8096

For example:

CREATE DATABASE database_name USING CODESET UTF-8 TERRITORY US CREATE BUFFERPOOL bufferpool_name SIZE 256 PAGESIZE 16 K EXTENDED STORAGE

CREATE REGULAR TABLESPACE tablespace_name PAGESIZE 16 K MANAGED BY SYSTEM USING ('system_container') EXTENTSIZE 16 OVERHEAD 10.5 PREFETCHSIZE 16 TRANSFERRATE 0.33 BUFFERPOOL bufferpool_name DROPPED


TABLE RECOVERY ONCREATE BUFFERPOOL tmp_bufferpool_name SIZE 512 PAGESIZE 16KCREATE SYSTEM TEMPORARY TABLESPACE tmp_tablespace_name PAGESIZE 16K MANAGED BY SYSTEM USING ('tmp_system_conatainer') EXTENTSIZE 16 OVERHEAD 10.5 PREFETCHSIZE 16 TRANSFERRATE 0.33 BUFFERPOOL tmp_bufferpool_nameGRANT USE OF TABLESPACE tablespace_name TO USER db2_userGRANT CONNECT ON DATABASE TO USER db2_userGRANT CREATETAB ON DATABASE TO USER db2_userUPDATE DBM CFG USING DRDA_HEAP_SZ 2048UPDATE DATABASE CONFIGURATION FOR database_name USING STMTHEAP 8096UPDATE DATABASE CONFIGURATION FOR database_name USING APPLHEAPSZ 8096UPDATE DATABASE CONFIGURATION FOR database_name USING APP_CTL_HEAP_SZ 8096UPDATE DATABASE CONFIGURATION FOR database_name USING SORTHEAP 2000TERMINATE

Where:

Variable Name DB2 Description Example

db2_user User who owns the Reporting and Analysis DBschema

biplus

database_name Database name BIPLUS

bufferpool_name Bufferpool BIPLUS_BP

tablespace_name Tablespace BIPLUS_TS

system_container Container \db2data\BIPLUS_TS

tmp_bufferpool_name Bufferpool TMP_BIPLUS_BP

tmp_tablespace_name Tablespace TMP_BIPLUS_TS

tmp_system_conatainer DB2 container \db2data\TMP_BIPLUS_TS

Note:

Do not start _name variables with SYS.

Caution!

The default tablespace for the database user that owns the Reporting and Analysis repositorymust not be partitioned.

5 Ensure that the IBM DB2 Client Application Enabler is installed on the computers on which you installReporting and Analysis services.

6 For Core Services and Job Factory Service— if you use an IBM DB2 RDBMS and Reporting and AnalysisServices are on separate machines, create a client connection to the Reporting and Analysis database usingthe Client Application Enabler.


7 The application Client Configuration Assistant feature requires you enter the host name, port number, andservice name used in your database server installation. Driver full path: \java\db2java.zip.

8 Set all necessary environment variables:

Set the PATH environment variable to the DB2 libraries location. Use the System option inControl Panel or the Set command from the Windows command prompt.

IBM DB2 with Web AnalysisWhen using IBM DB2 for Web Analysis, you must ensure that the following conditions are met:

● Configure DB2 to use JDBC 2.0 drivers. Ensure that the IBM DB2 Client Application Enableris installed.

● Create required tablespace.

● Ensure that the default tablespace for the database user who owns the Reporting and Analysisrepository is not partitioned.

● Do not use localhost for the server name.

● Ensure that usernames are granted connection privileges to the database.

Configuring Microsoft SQL ServerAfter you install Microsoft SQL Server, record the Microsoft SQL database host name, portnumber, and server for use when you install the Reporting and Analysis products. MicrosoftSQL Server is not case-sensitive.

The default tablespace for the database user who owns the Reporting and Analysis repositorymust not be partitioned.

Note:

A database administrator should perform the following procedures.

➤ To configure Microsoft SQL Server for use with Reporting and Analysis:

1 Set up the database within your RDBMS.

If a database device lacks sufficient disk space to store the Reporting and Analysis metadata,create a database device, using a command line or Enterprise Manager:

DISK INIT NAME = 'logical_name',PHYSNAME = 'absolute_dir_path_and_file_name',VDEVNO = virtual_device_number,SIZE = size_in_2k_pagesgo

2 Create a database in which to store the metadata.


CREATE DATABASE biplusON device_name = size_in_MBgo

3 Create a database user account for Reporting and Analysis.

A user must be created. This user owns the Reporting and Analysis database tables and objectsthat are built and populated during this installation. The user created here is also the user thatReporting and Analysis services use to connect to the database. Hyperion suggests naming theuser biplus.

Note:

The Reporting and Analysis repository database user cannot be an administrator, nor can it bea user who is assigned the System Administrators role.

4 Create the Microsoft SQL Server login:

sp_addlogin biplus, password mypasswordgo

Note:

The password for the Microsoft SQL Server repository database should not be null.

5 Create the database user:

use biplusgosp_adduser biplusgo

6 Grant privileges to the user:

use biplusgogrant create table to biplusgogrant select on sysobjects to biplusgogrant create procedure to biplusgogrant create view to biplus gogrant create function to biplusgo

Configuring Oracle● Adequate privileges must be granted to the Oracle user.

● Use the global database server name when specifying locations and paths. Do not uselocalhost as a server name.

● Tablespaces can be shared with other applications.

After you install Oracle, record the Oracle database host name, port number, and Oracle SID(or Service Name) for use when you install the Reporting and Analysis products.


Note that when you install Oracle, SQL*Net is needed to run Production Reporting for Oracle.

Note:

A database administrator should perform these procedures.

The Oracle database that contains the Reporting and Analysis tablespace should have UTF-8 asits character set. Oracle supports the following three character sets with UTF-8 encoding:

● AL32UTF8 (UTF-8 encoding for ASCII platforms)

● UTF8 (backward compatible encoding for Oracle)

● UTFE (UTF-8 encoding for EBCDIC platforms)

The following is a sample script that creates a sample database with AL32UTF8

encoding:

CREATE DATABASE sample

CONTROLFILE REUSELOGFILE

GROUP 1 ('diskx:log1.log', 'disky:log1.log') SIZE 50K,GROUP 2 ('diskx:log2.log', 'disky:log2.log') SIZE 50K

MAXLOGFILES 5MAXLOGHISTORY 100MAXDATAFILES 10MAXINSTANCES 2ARCHIVELOGCHARACTER SET AL32UTF8NATIONAL CHARACTER SET AL16UTF16DATAFILE

'disk1:df1.dbf' AUTOEXTEND ON,'disk2:df2.dbf' AUTOEXTEND ON NEXT 10M MAXSIZE UNLIMITED

DEFAULT TEMPORARY TABLESPACE temp_tsUNDO TABLESPACE undo_tsSET TIME_ZONE = '+02:00';

For more information refer to the Oracle Documentation.

➤ To configure Oracle for use with Reporting and Analysis:

1 Dedicate a tablespace to Reporting and Analysis.

Determine the tablespaces to be used as the default tablespace and temporary tablespace for thisuser. Do not use the SYSTEM tablespace. To list the tablespaces, enter the following SQLstatement from SQL*Plus:

select * from sys.dba_tablespaces;

If a user cannot use a default or temporary tablespace, then create a tablespace by entering anSQL statement from the SQL*Plus utility:


Tip:

Create a separate tablespace for indexes to improve performance.

Note:

This action requires CREATE TABLESPACE system privileges.

● If the database instance or file name (filespec) exists:

create tablespace tablespace_name datafile 'filespec' SEGMENT SPACE MANAGEMENT AUTO ;

● If the database instance or file name (filespec) does not exist:

create tablespace tablespace_name datafile 'filespec' size nnM SEGMENT SPACE MANAGEMENT AUTO ;

where nn is the megabyte count.

Plan the repository size. Hyperion suggests starting with 250 MB minimum, which providesroom to grow the Reporting and Analysis repository without having to increase the datafileor tablespace.

The sizing of the shared pool is important, to ensure that the Hyperion Configuration Utilitycan create all of the necessary repository tables. If the shared pool size on the database is settoo small, you receive an error. Hyperion recommends that a shared pool size of 60 MB beused during the Hyperion Configuration Utility.

Make sure that SEGMENT SPACE MANAGEMENT parameter is set to AUTO when you createtablespace. This parameter is needed for better performance.

2 Create an Oracle user account for Reporting and Analysis.

A user must be created. This user owns the Reporting and Analysis database tables and objectsthat are built and populated during this installation. The user created here is also the user thatReporting and Analysis services use to connect to the database. Hyperion suggests naming theuser biplus.

Database privileges are required to perform the following actions. The tablespaces created oridentified in the previous step are used as the default and temporary tablespaces. To create theuser, enter the following commands from within the Oracle SQL*Plus utility:

create user biplus identified by mypassword default tablespace tablespace1 temporary tablespace tablespace2;

where tablespace1 and tablespace2 are the tablespaces previously created or identified.

3 Give the user database connection privileges:

Oracle 9: grant connect, resource to biplus;

Oracle 10: grant connect, resource, create view to biplus;

4 Set the NLS_LENGTH_SEMANTICS parameter to char:

nls_length_semantics=char


5 Set the necessary environment variable:

For Core Services and Job Factory Service—Use the System option in Control Panel or the Setcommand from the Windows command prompt to set the LIBPATH environment variable tothe location of the Oracle Client libraries.

Note:

Core Services—Hyperion recommends enabling the parallel query option to allow parallel queryactivity for faster row retrieval.

Manually Creating TablesThe Hyperion Configuration Utility creates the repository tables. See “Configuring Databases”on page 53.

You also have the option to create the repository tables before installing and configuringReporting and Analysis.

To manually create database tables, run the following scripts in the configured database:

\database\portalsql\\Create.sql\database\portalsql\\CreateDSS.sql\database\\CreateAA.sql\database\\CreateUT.sql\database\\CreateUTViews.sql\database\\CreateChangeMgmt.sql\database\\CreateRLS.sql\database\\database-internal-schema.sql\database\\database-atf-schema.sql\database\\database-analyzer-schema.sql

where :

● Oracle 9/10—Oracle

● IBM DB2—DB2

● MS SQL Server—MSSQLServer

Database Storage Parameters for OracleThe Oracle DDLs now contain storage parameters. If the database will be large, alter storageparameters after install and before relational storage configuration.

create table V8_ACCESS_CTRL ( RESOURCE_ID VARCHAR2(64) not null, ACCESSOR_ID VARCHAR2(64) not null, ACCESSOR_TYPE NUMBER(1) not null, GRANT_ID VARCHAR2(64) not null, GRANT_TYPE NUMBER(1) not null, LAST_UPDATE_DATE DATE, constraint PK_V8_ACCESS_CTRL primary key (RESOURCE_ID, ACCESSOR_ID, GRANT_ID)


)pctfree 8pctused 60storage( initial 2M next 1M)

There are now small, medium, and large table sizes:

● Large tables are allocated 2M initial extents

● Medium tables 300K

● Small tables are left with the default values

pctfree and pctused are set based on the expected insert, update activity on the table; forexample, if high insert, update activity pctfree is higher.

Creating ODBC ConnectionsInteractive Reporting and SQR Production Reporting uses ODBC to access a data source, andmust create an ODBC connection.

Prerequisite

You must have Microsoft 4.0 XML Parser installed before using the ODBC drivers. To downloadand install XML Parser, go to:

http://www.microsoft.com/downloads/details.aspx?FamilyID=3144b72b-b4f2-46da-b4b6-c5d7485f2b42&DisplayLang=en

Installing

For information on installing and configuring the DataDirect ODBC drivers supplied withReporting and Analysis, go to:

http://www.datadirect.com/download/docs/dochome/index.ssp

In Reporting and Analysis, use the HELP to see the parameters.

Microsoft SQL Server Analysis Services (SSAS) Connections

SSAS 2005 To connect to Microsoft SSAS 2005 databases, you must install SSAS Connectivity Client on anyFinancial Reporting Client or Financial Reporting server or Web Analysis Web Applicationmachine.

When you choose the Client component during the install there are 6 types of subcomponentsto choose from. You must expand Client Components and select the Client Connectivitycomponent that is required by Financial Reporting and Web Analysis to connect.


http://www.microsoft.com/downloads/details.aspx?FamilyID=3144