Reporting and Analysis Installers

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 U N I X

Reporting and Analysis Installation Guide for UNIX, 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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

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

Database Storage Parameters for Oracle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

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

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

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

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

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

Configuring X11 for UI Services for Financial Reporting and Web Analysis . . . . . . . . 34

AIX 5L . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Solaris 9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Solaris 10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Red Hat Enterprise Linux Release 4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

HP-UX 11i . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Contents iii

Setting the DISPLAY Variable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Web Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Application Server Setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Web Browser Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Configuring a Web Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

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

Financial Management Web Server Environment . . . . . . . . . . . . . . . . . . . . . . . . 38

Browser Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Module-specific Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Configuring a Production Reporting Server Installation . . . . . . . . . . . . . . . . . . . . . . 39

Financial Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Financial Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Financial Reporting Print Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Environment Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Production Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Relinking the Hyperion Production Reporting Server Executables . . . . . . . . . . . . 40

Installing Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Satisfying Stack Size Limit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Satisfying Temporary Space Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Command Line Processor Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

UNIX Installation Mechanisms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Fonts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Updating the C++ Runtime Environment for AIX . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Creating a Reporting and Analysis User Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Port Numbers Used by Hyperion Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Chapter 3. Installing Reporting and Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Reporting and Analysis Installers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Reporting and Analysis Module Installers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

About Hyperion Home . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Hyperion Home Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Files Installed in the HYPERION_HOME Directory . . . . . . . . . . . . . . . . . . . . . . . . . 48

Changing the Hyperion Home Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Installing Reporting and Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Running Silent Installations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Chapter 4. Configuring Reporting and Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Hyperion Configuration Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Task Sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

iv Contents

Restricted Characters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Satisfying Initial Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Configuring Product Upgrades . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Configuring Reporting and Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Registering With Shared Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Configuring Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Specifying Application Server Hostnames and Web Server Connector Plug-in Ports . . 58

Deploying to the Application Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

What Happens During Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

WebSphere and WebLogic 9.1.x . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

WebLogic 8.1.x . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

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

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

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

Completing Module-Specific Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Workspace Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Customizing the Context Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Specifying the GSM Host and Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

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

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

Interactive Reporting Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

Financial Reporting Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Enabling the Planning ADM Driver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Enabling the Analytic Provider Services Driver . . . . . . . . . . . . . . . . . . . . . . . . . . 66

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

Report Server Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

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

SQR Production Reporting Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

Reconfiguring Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

Testing Module Availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

Post Configuration Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

Error Messages When Testing Module Availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

Post Configuration Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

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

Installing OpenJMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Configuring OpenJMS Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Configuring and Starting OpenJMS Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

Configuring Web Analysis to use OpenJMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

Contents v

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

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

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

Verifying Startup Dependencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Starting Shared Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Verifying Successful Startup of Shared Services . . . . . . . . . . . . . . . . . . . . . . . . . . 76

Stopping Shared Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Reporting and Analysis Administrator User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

Configuring Production Reporting Post Configuration Tasks . . . . . . . . . . . . . . . . . . 78

Setting up the Environment Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

Recreating the Executables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

Launching Reporting and Analysis Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

Adding Content Expiration Headers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

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

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

Guidelines for Changing Port Ranges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

Service Types Used in irmconfig.xml . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

Sample irmconfig.xml . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

Setting up SiteMinder with Transparent Logon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

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

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

Configuring the SiteMinder Policy Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

Setting up Workspace Web Application Parameters . . . . . . . . . . . . . . . . . . . . . . 88

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

Configuring Shared Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

Restarting Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

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

Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

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

Uninstalling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

Reinstalling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

Reinstalling Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

Reinstalling UIServices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

Reinstalling Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

vi Contents

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

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

Upgrading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

Migrating Users and Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

About SyncCSSIdentity_BI Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

Running SyncCSSIdentity_BI utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

Using Most Provider Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

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

Upgrading Manually Deployed Web Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

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

Migration Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102

Supported Source Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102

Installing the Migration Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

After Installing the Migration Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

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

Configuring Apache . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

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

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

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

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

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

Configuring IIS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

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

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

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

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

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

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

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

Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115

Deploying Workspace Web Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116

Creating an OC4J Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116

Configuring the Workspace OC4J Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116

Deploying workspace.war . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

Configuring Workspace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118

Contents vii

Enabling SAP as an Authentication Provider . . . . . . . . . . . . . . . . . . . . . . . . . . . 118

Creating context.properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118

Modifying portlet.xml . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

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

Updating Configuration Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120

Deploying Financial Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121


Configuring the FinancialReporting OC4J Instance . . . . . . . . . . . . . . . . . . . . . . . . . 122

Deploying HReports.ear . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124

Deploying Web Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124


Configuring the WebAnalysis OC4J Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125

Deploying WebAnalysis.ear . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127

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

Configuring Reporting and Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128

Configuring Financial Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130

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

Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130

Configuring the Oracle Application Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131

Configuring Shared Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134

Testing Module Availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134

Post Configuration Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135

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

Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137

Deploying Workspace Web Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138


Configuring an OC4J Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138

Deploying workspace.war . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139

Using Oracle Enterprise Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139

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


Enabling SAP as an Authentication Provider . . . . . . . . . . . . . . . . . . . . . . . . . . 140

Creating context.properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141

Updating Configuration Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142




Configuring a FinancialReporting OC4J Instance . . . . . . . . . . . . . . . . . . . . . . . . . . 144

viii Contents

Deploying HReports.ear . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146

Using Oracle Enterprise Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146

Using Oracle Distributed Configuration Management Command Line Utility . . 147



Configuring the WebAnalysis OC4J Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148

Environment Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149

Deploying WebAnalysis.ear . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150

Using Oracle Enterprise Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150

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

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

Configuring Reporting and Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151

Configuring Performance Management Architect or Planning . . . . . . . . . . . . . . . . . 152

Configuring Financial Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153

Defining Additional Parameters for Workspace . . . . . . . . . . . . . . . . . . . . . . . . . . . 153

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

Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154

Configuring the Oracle Application Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154

Configuring Shared Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157



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

Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159

Preparing the Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159

Deploying Workspace into WebLogic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160

Creating a New Domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160

Modifying setDomainEnv.sh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160

Deploying Workspace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161

Modifying portlets.xml . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162

Post Deployment for Workspace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163

Creating context.properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163

Deploying Financial Reporting into WebLogic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163

Post Deployment for Financial Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164

Deploying Web Analysis into WebLogic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164

Verifying Web Analysis Environment Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . 164

Modifying setDomainEnv.sh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165

Deploying Web Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166

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

Contents ix

Configuring Apache HTTP Plug-in . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167

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

Configuring for Performance Management Architect . . . . . . . . . . . . . . . . . . . . 174

Configuring for Financial Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174

Configuring for Performance Scorecard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175

Configuring for Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176



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

Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179

Creating WebLogic Domains . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179

Deploying Workspace into WebLogic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180

Modifying startWebLogic.sh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180

Deploying Workspace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181


Post Deployment for Workspace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183

Compiling JSP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183

Creating context.properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183

Deploying Financial Reporting into WebLogic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184

Deploying Web Analysis into WebLogic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185

Web Analysis Environment Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185

Deploying Web Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186

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

Configuring Apache . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186

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

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

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

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

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



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

Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199

Preparing the WebSphere Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200

WebSphere ND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200

WebSphere BASE/Express . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200

Add Virtual Host Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201

x Contents

Deploying Workspace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201

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

Assigning SAP_LIBRARY to Workspace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202

Creating context.properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203




Configuring Financial Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206


Deploying . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207


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

Configuring Web Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209

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

Configuring Apache Server or IBM HTTP Server . . . . . . . . . . . . . . . . . . . . . . . . . . 210

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

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



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

Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215

Preparing the WebSphere Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216

WebSphere ND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216

WebSphere BASE/Express . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216

Add Virtual Host Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217

Deploying Workspace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217

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

Assigning SAP_LIBRARY to Workspace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219

Creating context.properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219



Deploying and Configuring Financial Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221


Deploying . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223


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

Configuring Web Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226

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

Contents xi

Configuring Apache Server or IBM HTTP Server . . . . . . . . . . . . . . . . . . . . . . . . . . 227

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

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



Chapter 15. Manually Deploying into Sun Java System Application Server Enterprise Edition 8.1 05Q4 . . . . . 231

Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231

Creating a Node Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231

Creating a New Standalone Server Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232

Customizing a Standalone Server Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233

Editing Standalone Server Instance JVM Options for Workspace . . . . . . . . . . . . . . . 235

Editing Standalone Server Instance JVM Options for Financial Reporting . . . . . . . . . 236

Financial Reporting Environment Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236

Editing Standalone Server Instance JVM Options for Web Analysis . . . . . . . . . . . . . 237

Web Analysis Environment Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238

Deploying the Workspace Web Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238

Creating context.properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239

Deploying the Financial Reporting Web Application . . . . . . . . . . . . . . . . . . . . . . . . . . . 240

Deploying the Web Analysis Web Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240

Post Deployment for Web Analysis Enterprise Applications . . . . . . . . . . . . . . . . . . . 241

Testing Web Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241

Generating the JES Load Balancing Plug-in Configuration File . . . . . . . . . . . . . . . . . . . . 242

SunOne Web Server 6.1 Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243

Automatically Installing the Load Balancing Plugin . . . . . . . . . . . . . . . . . . . . . . 243

Manually Installing the Load Balancing Plug-in . . . . . . . . . . . . . . . . . . . . . . . . 244

Configuring the Load Balancing Plug-in . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244

Create NameTrans Entries for Static Workspace Content . . . . . . . . . . . . . . . . . 245

Default Sun Java Enterprise Application Server Locations . . . . . . . . . . . . . . . . . . . . . . . 246



Appendix A. ActiveX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249

Whitepaper . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249

Sample Policy File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253

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 9Management reporting includingquery and analysis in one coordinated environment

Oracle's Hyperion ApplicationsCoordinated planning, consolidation, and scorecardingapplications

Oracle's Hyperion Foundation ServicesUsed 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 WorkspaceWeb-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 9High performance multidimensionalmodeling, analysis, and reporting

Oracle's Hyperion Financial Reporting System 9Highly formatted financialreporting

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

Oracle's Hyperion SQR Production Reporting System 9High volume enterpriseproduction reporting

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

Authoring Studios

Oracle's Hyperion Interactive Reporting StudioHighly 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 ClientRead-only Web plug-in forviewing Interactive Reporting documents.

Oracle's Hyperion Financial Reporting StudioWindows 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 StudioJava 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 StudioWindows 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 ServicesEnables creation ofdashboards:

Dashboard StudioWindows client that utilizes extensible and customizabletemplates to create interactive, analytical dashboards without the need to codeprogramming logic.

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

Performance ScorecardWeb-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 indicatorsIndicate good, acceptable, or poor performance ofaccountability teams and employees

Strategy mapsRelate high-level mission and vision statements to lower-levelactionable strategy elements

Accountability mapsIdentify those responsible for actionable objectives

Cause and Effect mapsDepict interrelationships of strategy elements andmeasure the impact of changing strategies and performance

Oracle's Hyperion Smart View for OfficeHyperion-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 layera middle tier that retrieves requested information and manages security,communication, and integrationcontains 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:

WorkspaceDeployed to Apache Tomcat on Machine A, and is configured to acceptrequests on TCP port 45000

Financial Reporting Web componentDeployed to Apache Tomcat on MachineB, and isconfigured to accept requests on TCP port 8200

Web serverMicrosoft 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 page128

Oracle 10g Release 2:Configuring Oracle HTTP Server for Oracle 10g Release 2 on page151

SUN Java System Application Server Enterprise Edition: Chapter 15, Manually Deployinginto Sun Java System Application Server Enterprise Edition 8.1 05Q4

WebLogic 9.1: Configuring a Web Server for WebLogic 9.1 on page 166

WebLogic 8.1: Configuring a Web Server for WebLogic 8.1 on page 186

WebSphere 6.1: Configuring a Web Server with WebSphere 6.1 Application Server onpage 210

WebSphere 6.0.2: Configuring a Web Server with WebSphere 6.0.2 Application Server onpage 226

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 servicesServices in the local Install Home that are configured using the Local ServiceConfigurator (LSC). Referred to as LSC services.

Remote servicesServices 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 ServiceStores 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 ServiceHandles 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 ServiceChecks 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 ServiceProvides 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 ServiceMonitors 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 BrokerSupports GSM and LSMs by routing client requests and managing loadbalancing for RSC services. A system can have multiple Service Brokers.

Name ServiceMonitors 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 servicesCore Services that collect and distribute system messages and eventsfor troubleshooting and usage analysis:

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

Usage ServiceRecords the number and nature of processes addressed by HyperionInteractive Reporting Service, which enables administrators to review usage statistics


such 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 servicesCore Services that are specific to various functional modules:

Job ServiceExecutes 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 ServiceManages 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 ServicesCore 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) ServiceHarvests metadata from published InteractiveReporting repository documents.

Update (Transformer) ServiceUpdates 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 ServiceRuns 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 ServiceProvides 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 ServiceEnables users to jointlyanalyze multidimensional and relational sources in one document. It retrieves flattenedOLAP results from Web Analysis documents, SQR Production Reporting job output, or


Financial 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 ServerGenerates 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 replicablethe 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 ServerProvides a Java RMI Registry towhich other Financial Reporting servers are bound.

Hyperion Financial Reporting Print ServerEnables 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 ServerResponds 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 ServicesSupport Performance Scorecard client functionality usedin conjunction with Reporting and Analysis.

Oracle's Hyperion Shared ServicesSupports authentication and user provisioning forall Hyperion products. See the Shared Services documentation set.

Smart View ServicesProvide 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

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 repositoryHyperion system data in supported relational database tables

Shared ServicesUser, 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 .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37

Browser Settings ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .39

Module-specific Prerequisites .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .39

Installing Considerations ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .40

Port Numbers Used by Hyperion Products.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43

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 HyperionConfiguration 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 users home 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 29

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: DB2DIR\java\db2java.zip.

8 Set all necessary environment variables:

Set DB2COMM, DB2INSTANCE, DB2DIR, and:

Solaris, LinuxLD_LIBRARY_PATH

AIXLIBPATH

HP-UXSHLIB_PATH

Note:

Connectivity to IBM DB2 on AIX 5.2 may fail if the installation is done on a remotelymounted location (a directory location mounted over the network). To resolve this issue,copy recursively the /common/ODBC/Merant/5.1 (this directoryshould be on a local hard disk )

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.

Open odbc.ini file and add for DB2 UDB:

Collection= Location=

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 go


grant 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 variables:

ORACLE_HOME

PATH

Solaris/LinuxLD_LIBRARY_PATH

AIX LIBPATH

HPSHLIB_PATH

ORACLE_HOME identifies the location of the Oracle database software.

Note:

Core ServicesHyperion 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 Databaseson page 57.

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/10Oracle

IBM DB2DB2

MS SQL ServerMSSQLServer

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 60stor

Reporting and Analysis Installers

Documents

Transcript of Reporting and Analysis Installers