Hs Windows Install

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

FINANCIAL REPORTING™, INTERACTIVE REPORTING, PRODUCTION REPORTING, WEB ANALYSIS

R E L E A S E 9 . 2 . 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

Hyperion Reporting and Analysis Release 9.2.1 Installation Guide

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

Authors: Reporting and Analysis Documentation Team

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

The information contained in this document is subject to change without notice. If you find any problems in the documentation, please report them to us in writing. This document is not warranted to be error-free. Except as may be expressly permitted in your license agreement for these Programs, no part of these Programs may be reproduced or transmitted 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 the United States Government, the following notice is applicable:

U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are “commercial computer software” or “commercial technical data” pursuant to the applicable 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 subject to the licensing restrictions set forth in the applicable Oracle license agreement, and, to the extent applicable, the additional rights set forth in FAR 52.227-19, Commercial Computer Software--Restricted Rights (June 1987). Oracle USA, Inc., 500 Oracle Parkway, Redwood City, CA 94065.

The Programs are not intended for use in any nuclear, aviation, mass transit, medical, or other inherently dangerous applications. It shall be the licensee's responsibility to take all appropriate fail-safe, backup, redundancy and other measures to ensure the safe use of such applications if the Programs are used for such purposes, and we disclaim liability for any damages 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 their respective owners.

The Programs may provide links to Web sites and access to content, products, and services from third parties. Oracle is not responsible for the availability of, or any content provided on, third-party Web sites. You bear all risks associated with the use of such content. If you choose to purchase any products or services from a third party, the relationship is directly between 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 warranty obligations related to purchased products or services. Oracle is not responsible for any loss or damage of any sort that you may incur from dealing with any third party.

Contents 1

Contents

CHAPTER 1 Reporting and Analysis Architecture Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Hyperion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Reporting and Analysis Reporting Solution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Reporting and Analysis Reporting Solution Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Client Layer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Application Layer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Database Layer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

CHAPTER 2 Installation Sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

High-level Task Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Reporting and Analysis Installation Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Configuration Utility Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

CHAPTER 3 Planning the Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Hardware Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Software Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Software Support for Apache Tomcat . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Database Layer Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Middle Layer Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Client Layer Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Configuration Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

RDBMS Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

SAP Data Source Access and Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Creating ODBC Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Web Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Distributed and Replicated Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Installing Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Configuring a Production Reporting Server Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Browser Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Module-specific Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Financial Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

2 Contents

Financial Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Port Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Default Port Numbers for Remote Method Invocation (RMI) Servers . . . . . . . . . . . . . . . 52

AJP Connector Ports for Reporting and Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Configuring IBM WebSphere . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

CHAPTER 4 Installing Reporting and Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Reporting and Analysis Installers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Reporting and Analysis Module Installers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Using Installation Wizards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Hyperion Home . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Hyperion Home Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Changing the Hyperion Home Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Installing Reporting and Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

CHAPTER 5 Configuring and Setting Up Reporting and Analysis. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Post Installation Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

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

Using the Configuration Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Task Sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

Configuring Product Upgrades . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

Specifying Application Server Hostnames and HTTP Connector Plug-in Ports . . . . . . . 64

Launching the Configuration Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Registering Reporting and Analysis with Shared Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

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

Configuring Relational Storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

Deploying Reporting and Analysis to Application Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

Undeploying from an Application Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

Enabling the HTTP Server Plug-in . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

Configuration Utility HTTP Server Plug-in Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

HTTP Server Plug-in Manual Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

Completing Module-Specific Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

Workspace Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

Completing Financial Reporting Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

Completing Configuration Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Configuration Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Post Configuration Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

Verifying Startup Dependencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

Starting Shared Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Provision a Reporting and Analysis Administrator User . . . . . . . . . . . . . . . . . . . . . . . . . . 78

Contents 3

Adding Drivers for Web Analysis RDBMS Connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

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

Changing the Apache HTTP Server Listen Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

Reconfiguration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

CHAPTER 6 Uninstalling Reporting and Analysis. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

Uninstalling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

CHAPTER 7 Upgrading to Reporting and Analysis 9.2.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

Upgrading from 8.x to 9.2.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

Upgrading from 9.x to 9.2.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

Upgrading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

CHAPTER 8 Installing the Reporting and Analysis Migration Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

Migration Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

Supported Source Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

Installing the Migration Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

After Installing the Migration Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

APPENDIX A Manually Deploying into Oracle 10g Release 3 (10.1.3.1.0) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

Deploying Workspace Web Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

Creating an OC4J Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

Configuring an OC4J Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

Deploying workspace.war . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

Configuring Workspace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

Deploying Financial Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

Creating an OC4J Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

Configuring an OC4J Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

Deploying HReports.ear . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

Deploying Web Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

Creating an OC4J Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

Configuring an OC4J Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102

Deploying WebAnalysis.ear . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

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

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

Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

Configuring the Oracle Application Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

Configuring Shared Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

Testing Module Availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110

4 Contents

APPENDIX B Manually Deploying into WebLogic 8.1.4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

Modifying startWebLogic.cmd . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

Deploying Workspace into WebLogic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

Post Deployment for Workspace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

Deploying Financial Reporting into WebLogic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114

Deploying Web Analysis into WebLogic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115

Pre-Deployment for Web Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115

Deploying Web Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115

Configuring Apache with BEA WebLogic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116

Configuring Microsoft IIS 5/6 with WebLogic 8/9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

Configure Proxying by Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122

Register iisforward.dll with IIS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123

Configure Proxy by File Extension . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123

Testing Module Availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128

Testing the Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129

APPENDIX C Manually Deploying into WebLogic 9.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131

Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132

Preparing the Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132

Preparing a One-Host Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132

Preparing a Clustering Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133

Deploying Workspace into WebLogic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135

Pre-deployment for Workspace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135

Deploying Workspace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136

Post-deployment for Workspace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138

Deploying Financial Reporting into WebLogic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139

Pre-deployment for Financial Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139

Deploying Financial Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140

Deploying Web Analysis into WebLogic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142

Pre-deployment for Web Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142

Verifying Web Analysis Environment Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142

Deploying Web Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143

Configuring a Web Server for WebLogic 9.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145

Configuring the Apache Web Server Plug-in . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145

Configuring Microsoft IIS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152

Configure Proxying by Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152

Register iisforward.dll with IIS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153

Configure Proxy by File Extension . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153

Restart IIS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158

Testing Module Availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159

Contents 5

APPENDIX D Manually Deploying into WebSphere 5.1.1.7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161

Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162

Deploying Workspace into WebSphere . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162

Deploying Workspace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162

Configuring Workspace Web Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163

Creating context.properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164

Starting Workspace Web Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164

Deploying Financial Reporting into WebSphere . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165

Deploying . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165

Configuring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167

Deploying Web Analysis into WebSphere . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168

Pre-Deployment for Web Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168

Deploying . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169

Configuring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171

Configuring Apache or IBM HTTP with WebSphere 5.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171

Configuring Microsoft IIS with WebSphere 5.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174


APPENDIX E Manually Deploying into WebSphere 6.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179

Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180

Preparing the WebSphere Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180

WebSphere ND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180

WebSphere BASE/Express . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180

Add Virtual Host Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181

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

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

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

Configuring Workspace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183

Deploying Financial Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184

Configuring Financial Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184

Deploying Web Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185

Deploying . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185

Environment Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186

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

Configuring Web Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187

Configuring Apache or IBM HTTP with WebSphere 6.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187

Configuring Microsoft IIS with WebSphere 6.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190


APPENDIX F ActiveX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195

Whitepaper . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196

Sample Policy File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197

6 Contents

Reporting and Analysis Architecture Overview 9

C h a p t e r

1Reporting and Analysis Architecture Overview

In This Chapter Hyperion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Reporting and Analysis Reporting Solution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Reporting and Analysis Reporting Solution Architecture. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

10 Reporting and Analysis Architecture Overview

HyperionHyperion is a comprehensive Business Performance Management (BPM) system that consists of these products:

● Hyperion—Management reporting including query and analysis in one coordinated environment

● Hyperion Applications+™—Coordinated planning, consolidation, and scorecarding applications

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

Reporting and Analysis Reporting SolutionReporting and Analysis is a modular business intelligence platform that provides management reporting, query, and analysis capabilities for a wide variety of data sources in one coordinated environment.

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

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

● Interactive reporting for ad hoc relational query, self-service reporting and dashboards against ODBC data sources

● Production reporting for high volume enterprise-wide production reporting

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

Reporting and Analysis, which includes Oracle’s Hyperion® Essbase® – System 9™, is part of a comprehensive BPM system that integrates this business intelligence platform with Hyperion financial applications and Oracle’s Hyperion® Performance Scorecard – System 9™.

Reporting and Analysis Reporting Solution Architecture 11

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

● “Client Layer” on page 11

● “Application Layer” on page 13

● “Database Layer” on page 18

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

● Workspace—DHTML based, zero-footprint client that provides the 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:

❍ Essbase—High performance multidimensional modeling, analysis, and reporting

❍ Oracle’s Hyperion® Financial Reporting – System 9—Highly formatted financial reporting

❍ Oracle’s Hyperion® Interactive Reporting – System 9™—Ad hoc query, analysis, and reporting including dashboards

❍ Oracle’s Hyperion® SQR® Production Reporting – System 9™—High volume enterprise production reporting

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


● Oracle’s Hyperion® Interactive Reporting Studio™—Highly intuitive and easy-to-navigate environment for data exploration and decision making. With a consistent design paradigm for query, pivot, charting, and reporting, all levels of users move fluidly through cascading dashboards—finding answers fast. Trends and anomalies are automatically highlighted, 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 for viewing Interactive Reporting Studio reports.

● Oracle’s Hyperion® Financial Reporting Studio™—Windows client for authoring highly formatted financial reports from multidimensional data sources, which features easy, drag and drop, reusable components to build and distribute HTML, PDF, and hardcopy output.

● Oracle’s Hyperion® Web Analysis Studio™—Java applet that enables you to create, analyze, present, and report multidimensional content. The studio offers the complete Web Analysis feature set to designers creating content, including dashboards for information consumers.

● Oracle’s Hyperion® SQR® Production Reporting Studio™—Windows client that provides 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 form templates that prompt dynamic user input.

● Oracle’s Hyperion® Dashboard Development Services™—Enables creation of dashboards:

❍ Dashboard Studio—Windows client that utilizes extensible and customizable templates to create interactive, analytical dashboards without the need to code programming logic.

❍ Dashboard Architect—Windows-based integrated development environment that enables programmers to swiftly code, test, and debug components utilized by Dashboard Studio.

● Oracle’s Hyperion® Smart View for Office™—Hyperion-specific Microsoft add-in and toolbar from which users can query Hyperion data sources including Analytic Services, Financial Management, and Planning. Users can use this environment to interact with Financial Management and Planning forms for data input, and can browse the Reporting and Analysis repository and embed documents in the office environment. Documents are updated by user request.

● Oracle’s Hyperion® Performance Scorecard – System 9™—Web-based solution for setting goals and monitoring business performance using recognized scorecarding methodologies. Provides tools that enable users to formulate and communicate organizational strategy and accountability structures:

❍ Key Performance Indicators (KPIs)—Create tasks and achievements that indicate progress toward key goals

❍ Performance indicators—Indicate good, acceptable, or poor performance of accountability teams and employees

❍ Strategy maps—Relate high-level mission and vision statements to lower-level actionable strategy elements


❍ Accountability maps—Identify those responsible for actionable objectives

❍ Cause and Effect maps—Depict interrelationships of strategy elements and measure the impact of changing strategies and performance

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 13

● “Application Layer Services Tier” on page 13

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

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

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

For a complete description of supported Web tier hardware and software, see Chapter 3, “Planning the Installation”.

Application Layer Services TierThe application layer services tier contains services and servers that control functionality of various Web applications and clients. 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 Service Configurator (LSC). Referred to as LSC services.

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

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


Core Services

Core Services are mandatory for authorization, session management, and document publication:

● Repository Service—Stores Hyperion system data in supported relational database tables, known collectively as the repository. A system can have only one Repository Service.

● Publisher Service—Handles repository communication for other LSC services and some Web application requests; forwards repository requests to Repository Service and passes replies back to initiating services. A system can have only one Publisher Service.

● Global Service Manager (GSM)—Tracks system configuration information and monitors registered 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 configuration information with GSM, which supplies and maintains references to all other registered services.

● Authentication Service—Checks user credentials at logon time and determines whether they can connect; determines group memberships, which, along with roles, affects what content and other system objects (resources) users can view and modify. Authentication Service is replicable and does not have to be co-located with other services.

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

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

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

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

Management Services

Management services are Core Services that collect and distribute system messages and events for troubleshooting and usage analysis:

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

● Usage Service—Records the number and nature of processes addressed by Hyperion Interactive 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 MIME types are, and what happens to system output. Systems can have multiple Usage Services.


Functional Services

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

● Job Service—Executes scripts that create reports, which can be prompted by users with permissions or by Event Service. Report output is returned to initiating users or published to the repository. Job Services can be created and configured for every executable.

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

Interactive Reporting Services

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

● Hyperion Interactive Reporting Service—Runs Interactive Reporting jobs and delivers interactive HTML content for Interactive Reporting files. When actions involving Interactive Reporting documents are requested, Hyperion Interactive Reporting Service fulfills such requests by obtaining and processing the documents and delivering HTML for display.

● Hyperion Interactive Reporting Data Access Service—Provides access to relational and multidimensional databases, and carries out database queries for the plug-in, Hyperion Interactive Reporting Service, and Interactive Reporting jobs. Each Hyperion Interactive Reporting Data Access Service supports connectivity to multiple data sources, using the connection information in one or more Interactive Reporting database connection files, so that one Hyperion Interactive Reporting Data Access Service can process a document whose sections require multiple data sources. Hyperion Interactive Reporting Data Access Service maintains a connection pool for database connections.

● Extended Access for Hyperion Interactive Reporting Service—Enables users to jointly analyze multidimensional and relational sources in one document. It retrieves flattened OLAP results from Web Analysis documents, Production Reporting job output, or Financial Reporting Batch reports in the Reporting and Analysis repository and imports data into Interactive Reporting documents (.bqy) as Results sections.

● Hyperion Interactive Reporting Base Service—Starts all LSC and RSC services in one Install Home.

Financial Reporting Services

Financial Reporting services support Financial Reporting functionality by processing batch requests, generating output, and distributing Financial Reporting client content:

● Hyperion Financial Reporting Server—Generates and formats dynamic report or book results, including specified calculations. Hyperion Financial Reporting Server can handle numerous simultaneous requests for report execution from multiple clients, because each


request is run on its own execution thread. Hyperion Financial Reporting Server caches data source 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 number of 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 to which other Financial Reporting servers are bound.

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

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

Production Reporting Service

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

Impact Manager Services

Impact Manager services enable you to harvest, update, and publish new Interactive Reporting content from old Interactive Reporting repository resources. These services must be used in conjunction with Interactive Reporting services. Both services perform automatic load balancing and fault tolerance when multiple instances are running:

● Assessment (Harvester) Service—Harvests metadata from published Interactive Reporting repository documents.

● Update (Transformer) Service—Updates published and harvested Interactive Reporting documents or publishes new versions to the repository.

Performance Scorecard Services

Scorecard Module services support Performance Scorecard client functionality used in conjunction with Reporting and Analysis.

Common Administration Services

Common Administration services include Oracle’s Hyperion® Shared Services™ that support authentication and user provisioning for all Hyperion products. See the Shared Services documentation set.


Oracle’s Hyperion® Shared Services

Hyperion Hub functionality is now part of Oracle’s Hyperion® Shared Services™.

Features enabled by Shared Services:

● User provisioning

● External authentication definition

● Metadata synchronization

● Data synchronization

● Task flow management

The Hyperion Shared Services User Management Guide (on the Oracle® E-Delivery site) describes user-provisioning functionality. The Oracle’s Hyperion® Shared Services Installation Guide (on the Oracle® E-Delivery site) describes external authentication definition. All other Shared Services functionality is described in the administrator's and user's guides for the products that implement Shared Services.

Smart View Services

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

Services Tier Summary

LSC or RSC Service1 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 1 per system

Core Session Manager Multiple

Impact Management Services Assessment (Harvester) Service Multiple

Impact Management Services Update (Transformer) Service Multiple

Interactive Reporting Extended Access for Interactive Reporting Service Multiple

Interactive Reporting Hyperion Interactive Reporting Base 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


Note: 1 LSC—Local Service Configurator and RSC—Remote Service Configurator.

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

There are three 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

Database layer components:

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

● Multidimensional data sources, for example, Essbase

● Hyperion applications, for example, Financial Management and Planning

● Data warehouses

● ODBC data sources

For a complete description of supported data sources, see Chapter 3, “Planning the Installation”.

RSC Core Name Service 1 per system

Core Repository Service 1 per system

Core Service Broker Multiple

Functional Event Service 1 per system

Functional Job Service Multiple

N/A Common Administration Services Shared Services 1 per system

Financial Reporting Servers Hyperion Financial Reporting Communication Server 1 per system

Financial Reporting Servers Hyperion Financial Reporting Print Server Multiple

Financial Reporting Servers Hyperion Financial Reporting Scheduler Server 1 per system

Financial Reporting Servers Hyperion Financial Reporting Server Multiple

Performance Scorecard Services Scorecard Module Services Multiple

Production Reporting Service Production Reporting Service Multiple

Smart View Services Smart View Services Multiple

LSC or RSC Service1 Type Name Instances

Installation Sequence 19

C h a p t e r

2Installation Sequence

In This Chapter High-level Task Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Reporting and Analysis Installation Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Configuration Utility Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

20 Installation Sequence

High-level Task FlowThe following table lists the high-level steps required to install and configure multiple Hyperion products. Review these steps first before you begin the installation process. For detailed information, refer to the component user interface and related documentation listed next to each step. Following these steps in the sequence listed will help to ensure trouble-free installation of all Hyperion products.

Note: Beginning with this release, Hyperion® License Server™ and standalone license files are not used for license management. Instead, administrators need to audit product use. To ensure compliance with your license agreement, you need to edit a properties file to activate or deactivate features in accordance with what you have purchased.

For more information about license compliance, see the Hyperion License Compliance Readme (hyp_license_compliance_readme_921.pdf), which you can find on the Oracle® E-Delivery site or the product DVD .

Note: If installing SQR Production Reporting or Interactive Reporting Studio as a stand-alone product, copy the Hyperion back-office supplied license file to your product server computer and specify the full path to the license file during product activation during installation.

Step Instruction Product Component Documentation

1 Install Shared Services and configure the Shared Services application server and RDBMS.

Shared Services installer

Hyperion Configuration Utility™

Shared Services Installation Guide

2 Configure Shared Services to authenticate user names that are stored externally in LDAP, Active Directory, or Windows NT LAN Manager, enabling single sign-on.

Shared Services External Authentication Configuration Console

Shared Services Installation Guide

Note: You must finish steps 1 and 2 before continuting.

3 Install Hyperion products, such as Reporting and Analysis.

Hyperion product installers Product installation guides

4 Activate and configure Hyperion products and register them with Shared Services. You can configure multiple products at one time, if they are installed on the same computer.

Hyperion Configuration Utility Product installation guides

5 Create projects, add applications to projects, and provision users for applications.

Shared Services User Management Console™

Shared Services User Management Guide

http://edelivery.oracle.com/

Reporting and Analysis Installation Checklist 21

Reporting and Analysis Installation Checklist This checklist contains steps required for a successful Reporting and Analysis installation. Page numbers refer to the Reporting and Analysis Installation Guide unless otherwise noted.

If you are migrating from prior Hyperion releases, see Chapter 8, “Installing the Reporting and Analysis Migration Utility”

Before you begin the installation process, make sure you meet the hardware and software system requirements contained in Chapter 3, “Planning the Installation”.

Table 3 Reporting and Analysis Installation Checklist

INSTALL SHARED SERVICES AND CONFIGURE THE SHARED SERVICES APPLICATION SERVER AND RDBMS REFERENCE

1. Ensure that the database you are using for Shared Services is installed and operational before installing Shared Services.

2. Download Shared Services software and documentation from the Oracle® E-Delivery site.

3. Install Shared Services and configure the Shared Services Application server and RDBMS.

Hyperion Shared Services Installation Guide

(OPTIONAL) CONFIGURE THE SHARED SERVICES EXTERNAL AUTHENTICATION PROVIDER REFERENCE

1. Shared Services server is running.

2. Using Shared Services, configure the External Authentication Provider:

❍ Windows NT LAN Manager (NTLM)

❍ Lightweight Directory Access Protocol (LDAP)

❍ Microsoft Active Directory (MSAD)

Shared Services writes your configuration information to a central XML-based security configuration file that is generated by Shared Services. Reporting and Analysis references the security configuration file for external and remote users single sign-on.

3. Set up the environment and user rights for NT LAN Manager support.

4. Optionally, configure the environment for Netegrity Single Sign-on, configure Shared Services to use Single Socket Layers, and install the Hyperion Remote Authentication Module.

Hyperion Shared Services Installation Guide

INSTALLATION TASKS REFERENCE

Install Reporting and Analysis:

For each machine:

● Run appropriate Reporting and Analysis installers. The Reporting and Analysis installers create folders and copy the files onto the machine.

● After completing the last installer, run the Configuration Utility to perform the configuration tasks.

Chapter 4, “Installing Reporting and Analysis”

Chapter 5, “Configuring and Setting Up Reporting and Analysis”


POST INSTALLATION TASKS REFERENCE

Configure SAP BW Driver “Configuring SAP Data Source Access and Authentication” on page 62

CONFIGURATION TASKS REFERENCE

1. Activate and register with Shared Services using the Hyperion Configuration Utility.

❍ Activate Reporting and Analysis.

❍ Specify the Shared Services server location.

2. Configure relational databases and repositories.

3. Auto-deploy Reporting and Analysis modules to application servers (recommended)

OR

If preferred, select the Manual Deployment option to manually configure the deployment.

❍ Manually deploy into Oracle 10g

❍ Manually deploy into WebLogic 8.1

❍ Manually deploy into WebSphere 5.0.2 or 5.1

Note: Do not select “Deploy as Service” if you have selected “Manual Deployment”.

“Registering Reporting and Analysis with Shared Services” on page 66

“Configuring Relational Storage” on page 67

“Deploying Reporting and Analysis to Application Servers” on page 68

Appendix A, “Manually Deploying into Oracle 10g Release 3 (10.1.3.1.0)”

Appendix B, “Manually Deploying into WebLogic 8.1.4”

Appendix D, “Manually Deploying into WebSphere 5.1.1.7”

POST-CONFIGURATION TASKS REFERENCE

1. Verify the order of starting Services

2. Provision a Reporting and Analysis Administrator User

3. For Web Analysis, add drivers for Web Analysis RDBMS connectivity

4. Launch Reporting and Analysis Modules

“Verifying Startup Dependencies” on page 76

“Provision a Reporting and Analysis Administrator User” on page 78

“Adding Drivers for Web Analysis RDBMS Connectivity” on page 79

“Launching Reporting and Analysis Modules” on page 79

Table 3 Reporting and Analysis Installation Checklist (Continued)

Configuration Utility Information 23

Configuration Utility Information Fill in the information needed before running the Configuration Utility:

Component Information Needed

Shared Services:

● Server name

● Port number

● Administrator user name and password

___________________________________________

___________________________________________

___________________________________________

Relational database:

● Server name

● Port number

● Name (or SID for Oracle)

● Owner user name and password

___________________________________________

___________________________________________

___________________________________________

___________________________________________

Application server:

● Location (directory)

● BEA: home

● Weblogic: user name and password

● Weblogic: Domain name

● Name

● Port number

___________________________________________

___________________________________________

___________________________________________

___________________________________________

___________________________________________

___________________________________________

___________________________________________


Planning the Installation 25

C h a p t e r

3Planning the Installation

In This Chapter Hardware Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Software Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Module-specific Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Port Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Note: Reporting and Analysis is supported on the platforms specified in the tables included in this chapter. Subsequent maintenance releases and service packs may be used where the vendor asserts backward compatibility. Please be aware that while these assertions are made in good faith, certain incompatibilities may exist. In the event that an incompatibility is identified, there may be a delay in reproducing and fixing resultant issues for the affected versions.

26 Planning the Installation

Hardware RequirementsThis following table contains guidance for a general purpose deployment for a user population of up to 125 users. This guidance should be considered a starting point for deployments of this size, recognizing that many site specific factors and usage patterns will determine the appropriate hardware solution.

For larger deployments, we recommend consulting with Hyperion Consulting Services or a qualified Hyperion implementation partner to determine the appropriate hardware topology for your specific usage patterns and needs.

Hardware Guidance with User Population up to 125*

Machine #1:

Workspace

Financial Reporting Web Application

Web Analysis

4-way 2.0 GHz (or comparable/better), 8GB RAM, 20GB available disk space

Machine #2:

Shared Services

Repoting and Analysis Base Services

Financial Reporting Services

Interactive Reporting Services

Production Reporting Service

4-way 2.0 GHz (or comparable/better), 8GB RAM, 50GB available disk space

Studios:

Web Analysis

Financial Reporting

Report Server

Scheduler Server

Print Server

Interactive Reporting

Interactive Reporting Web Client

Production Reporting

1Ghz, 1 GB RAM, 2GB available disk space

512 MB Minimum - 1024 MB suggested, 200 MB available disk space



1.2 GHz, 256 MB RAM, 350 MB available disk space

1.2 GHz, 220 MB RAM, 30 MB available disk space

4-way 1.0 GHz (or comparable/better), 256 MB RAM, 100 MB available disk space

Alternate topologies of more machines of lower requirements, for example, 2-way machines, are viable. Contact Hyperion Consulting or a Hyperion implementation partner for discussions on alternatives.

Adequate load and performance testing should be integrated into the implementation testing phase to validate your production environment hardware sizing and assess the overall technical readiness before implementing in Production.

Software Requirements 27

Software Requirements

Software Support for Apache TomcatHyperion provides Apache Tomcat as part of the Reporting and Analysis installation, should its use suit the needs of your deployment strategy. Hyperion does not own or maintain the Apache Tomcat application server and is not responsible for problems that you may encounter with its functionality. Hyperion, however, does fully support the use of Apache Tomcat in its products. In deployments where customers require high availability or failover, Hyperion recommends that you deploy a commercially supported application server where these capabilities are supported.

Database Layer Components

Note: You must be a local Administrator group member to install Reporting and Analysis.

Table 1 Software Requirements for Database Layer

Component RequirementProduction Reporting

Web Analysis

Financial Reporting


Repository

OLAP data sources One server:

● Hyperion Essbase 7.1.x or 9.2.1 X X X X

● IBM DB2 OLAP Server 7.1 SP 11 X

● IBM DB2 OLAP Server 8.1 SP 3 or 8.2 X X

● Microsoft Analysis Services 8 X

● SAP BW 3.1 or 3.5 (BAPI connectivity) X X X

● SAP BW 3.1 or 3.5 (ODBO connectivity) X

● SAP R/3 4.5 or 4.6 X

Hyperion Applications

● Financial Management 4.0.1 or 4.1.x X X

● Planning 4.0.1 or 4.1.x X X

Supported relational repositories

One server:

● Microsoft SQL Server 2000 SP 3a (Enterprise or Standard edition)

● Microsoft SQL Server 2005

X

X


● Oracle 9i - 9.2.0.5 or 10g - 10.1.0.5 (For Web Analysis - with Native JDBC drivers, or OCI drivers)

X

● IBM DB2 Release 8.2 (for Web Analysis - using JDBC 2.0 with Web Analysis)

X

Relational data sources

One server:

● Microsoft SQL Server 2000 SP 3a (Enterprise or Standard edition) ODBC

X X

● Microsoft SQL Server 2000 SP 3a (Enterprise or Standard edition) JDBC

X X

● Microsoft SQL Server 2000 SP 3, with MS SQL Server JDBC drivers

X

● Microsoft SQL Server 2005 SP1 X X X

● Microsoft SQL Server 2005 SP1 Analysis Services

X X

● Oracle 9i - 9.2.0.5 OCI Connectivity X X

● Oracle 9i - 9.2.0.5 ODBC Connectivity X X

● Oracle 9i - 9.2.0.5 JDBC Connectivity X X

● Oracle 10g 10.1.0.5 OCI Connectivity X X

● Oracle 10g 10.1.0.5 ODBC Connectivity X X

● Oracle 10g 10.1.0.5 JDBC Connectivity X

● Oracle 10g r2 10.2.0.2 OCI Connectivity X X X

● Oracle 10g r2 10.2.0.2 ODBC Connectivity X X

● Oracle 10g r2 10.2.0.2 JDBC Connectivity X X

● Oracle 11g (beta) OCI Connectivity

● Oracle 11g (beta) ODBC Connectivity

● Oracle 11g (beta) JDBC Connectivity

● IBM DB Release 8.2 Enterprise Server Edition ODBC Connectivity

X X X

● IBM DB Release 8.2 Enterprise Server Edition JDBC Connectivity

X

● IBM DB Release 8.2 Enterprise Server Edition DB2 Connectivity

X

● Informix 9.2 and later ODBC X

Table 1 Software Requirements for Database Layer (Continued)


Web Analysis

Financial Reporting


Repository


● Informix 9.2 and later JDBC X

● Informix 9.4 and later ODBC X X

● Informix 9.4 and later JDBC X

● Informix 9.4 and later SDK 2.81 and later X

● ODBC 3.x ODBC connectivity X

● Redbrick 6.30 ODBC X X

● Sybase 12.x ASE ODBC1 X

● Sybase 12.x ASE JDBC X

● Sybase 12.5.x ASE ODBC1 X X

● Sybase 12.5.x ASE JDBC X

● Sybase 12.5.x ASE SDK X

● Sybase 12.x IQ ODBC X

● Sybase 12.6 IQ ODBC X

● Teradata Version 2 Release 4 and Higher ODBC

X

● Teradata Version 2 Release 5 and Higher ODBC

X

● Teradata 4.1 JDBC X

SQL Grid Relational Connectivity

● Merant drivers for SQL grid X

JDBC drivers2 One JDBC Driver:

● JDBC SQL Server 2000 SP 3 X

● For Oracle 9i - 9.2.0.5, Type 2 and Type 4 X

● For DB2 8.2 FP2, Type 2 and Type 4 X

1Only supported using Data Direct ODBC drivers2JDBC drivers are only required for Virtual Cube connections for relational drill-through.

Table 1 Software Requirements for Database Layer (Continued)


Web Analysis

Financial Reporting


Repository


Middle Layer Components

1 Only supported if running Reporting and Analysis as a 32-bit application.

Table 2 Middle Layer Software Requirements


Web Analysis

Financial Reporting


Operating System Processors: Servers:

X86

EM64T1

AMD 641

● Microsoft Windows 2000 Server SP 4

● Microsoft Windows 2003 Server SP 1 (includes support for R2)

X X X X

Application Servers Servers:

● BEA WebLogic 8.1.4 X X X

● BEA WebLogic 9.2 MP1 X X X

● IBM WebSphere 5.1.1.7 X X X

● IBM WebSphere 6.1 X X X

● Oracle 10g Release 3 (10.1.3.1.0) X X X

Runtime clients:

● Financial Management 4.0.x , 4.1.x, or 9.2.0.x. X X

● Planning 4.0.x

Note: The required Runtime components are included for Planning 4.1 and Analytic Services and do not need to be installed as a prerequisite.

X

● SAP Java Connector 2.1.6 X X

Note: The Financial Management, Analytic Services, and Planning Runtime Client should match the application release number.


Client Layer Components

Table 3 Standalone Client Software Requirements


Web Analysis

Financial Reporting


Operating System

Processers: Clients:

x86

EM64T

AMD 64

● Microsoft Windows 2000 Pro

● Microsoft Windows XP Pro

● Microsoft Windows Vista (all editions above “Home series”)

X X X X

Runtime Client for Windows stand-alone client

Runtime Clients:

● Financial Management Runtime Client Release 4.0.x or 4.1.x.

X

● Planning 4.0.x

Note: The required runtime components are included for Planning Release 4.1 and Essbase and do not need to be installed as a prerequisite.

X

● SAP BW Java Connector 2.1.6

Note: For Production Reporting, you only need the SAP JCo drivers if you are installing SQR/DDO.

X X

Other ● Adobe Acrobat Reader 6.0 or later X X X X

Table 4 Web Client Software Requirements


Web Analysis

Financial Reporting


Operating system Operating systems:

● Microsoft Windows 2000 Professional X X X

● Microsoft Windows XP Professional X X X

● Microsoft Windows Vista X X X

Web browser Web browsers:

● Microsoft Internet Explorer 6.0 X X X X

● Microsoft Internet Explorer 7.0 X X X X

● Mozilla Firefox 2.0.0.3 X X X X

Java plug-ins Server Plug-ins:


● Sun Java Plug-in 1.3.1_17 or later

Note: Must be manually configured

X

● Sun Java Plug-in 1.4.2_10 X

● Sun Java Plug-in 1.4.2_15 X

Browser Plug-ins:

● JVM Plug-in 1.3.1_19 X

● JVM Plug-in 1.4.2_15 X

Note: A JRE is downloaded to the client when a user logs onto Web Analysis Studio. The Web Analysis.properties file contains the settings for the correct version. See the Hyperion Workspace Administrator’s Guide.

Table 5 Third Party Products


Web Analysis

Financial Reporting


3rd Party Components

Office 2000

Excel X X

X

Office XP 2002 X X X

Office 2003 X X X

Adobe Acrobat Reader 6.0 or higher X X X X

Adobe Distiller Server 6.0 X

AFPL Ghostscript 8.51 X X

GNU Ghostscript 7.06 X X

Apache Tomcat 5.0.28 X X X

JDBC Data Direct 3.6 (build 24) X X X X

JDBC MySQL 3.0.8 X X X

Log4J 1.2.8 X

ODBC Data Direct 5.1 X

ODBC Data Direct 5.2 X X

SVG Viewer 3.0, or higher X

JCE 1.2.2 X X X

Table 4 Web Client Software Requirements(Continued)


Web Analysis

Financial Reporting


Prerequisites 33

PrerequisitesThe following sections describe the tasks you must complete before installing Reporting and Analysis:

● “Configuration Procedures” on page 33

● “RDBMS Considerations” on page 33

● “Web Environment” on page 41

● “Security” on page 43

Caution! For essential prerequisite tasks such as installing and configuring Shared Services see the Hyperion Installation Roadmap.

Configuration ProceduresThese sections detail how to configure your system before installing Reporting and Analysis:

● Install, configure, and run theShared Services. See the Hyperion Shared Services Installation Guide.

These procedures differ according to the RDBMS used for metadata storage.

RDBMS ConsiderationsDepending on which relational database management system you use as the relational repository, you might perform database configuration tasks before installing Shared Services.

The following topics describe pre-installation RDBMS considerations:

● “Backing Up a Repository” on page 33

● “Configuring Database Software for the Reporting and Analysis Repository” on page 34

● “Creating ODBC Connections” on page 40

Backing Up a RepositoryHyperion recommends you back up the following directories, files, and repository before upgrading, migrating, or reinstalling.

● RDBMS, all tables in the repository

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

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

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


IBM DB2 Version 8.2

When using IBM DB2 8.2 for Web Analysis, you must configure DB2 to use JDBC 2.0 drivers and ensure that the following types comply as required:

● Ensure that the IBM DB2 Client Application Enabler is installed.

● Make sure to create the required regular and system temporary tablespace.

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

● When specifying locations and path for a tablespace definition, the path reference on Unix is case sensitive, and do not use localhost for the server name reference.

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

Oracle

● You must be a database administrator with “Create” privileges to create tables in Oracle.

● Use the global database server name when specifying locations and paths. “Localhost” is not a recommended server name.

● Tablespaces can be shared with other applications.

Configuring Database Software for the Reporting and Analysis RepositoryRepository databases are the relational databases that Reporting and Analysis uses to store and manage the application metadata. See “Software Requirements” on page 27 to review the supported repository and data source databases.

Note: The amount needed space depends on the repository size you plan to build. Hyperion suggests starting with at least 250 MB, which provides room to grow the Reporting and Analysis repository without having to increase the datafile or tablespace.

Reporting and Analysis requires a repository database to store its persistent data. You must configure the database before configuring Reporting and Analysis. See:

● “Configuring IBM DB2” on page 34

● “Configuring Microsoft SQL Server” on page 37

● “Configuring Oracle” on page 38

● “SAP Data Source Access and Authentication” on page 40

Configuring IBM DB2

After installing IBM DB2, record the IBM DB2 database host name, port number, and service name for use when you install the Product Title Variable products.

Note: A database administrator should perform the following procedures.

Prerequisites 35

➤ To configure your system for use with IBM DB2:

1 Create an operating system user account.

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 database using UTF-8 encoding for the best compatibility with non-ascii character sets. To create the database, run the DB2 Command Line Processor or Command Center as the DB2 instance owner and 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 provides for a larger repository without increasing the datafile/tablespace. Also, performance is enhanced if you initially create a larger data file.

3 Log on to the DB2 Control Center as the DB2 administrator and add the Reporting and Analysis user you created in Step 1 to the DB2 database.

This provides Reporting and Analysis access to your database. The Reporting and Analysis user owns the Reporting and Analysis database tables that are built and populated and objects that are 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 Create a DB2 database with the following:

● A bufferpool and a tablespace with an 8 KB pagesize

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

● Tablespace access, database connect, and create table privileges for the Reporting and Analysis 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 8 K EXTENDED STORAGE

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

CREATE BUFFERPOOL tmp_bufferpool_name SIZE 512 PAGESIZE 12K

CREATE SYSTEM TEMPORARY TABLESPACE tmp_tablespace_name PAGESIZE 12K MANAGED BY SYSTEM USING ('tmp_system_conatainer') EXTENTSIZE 16 OVERHEAD 10.5 PREFETCHSIZE 16 TRANSFERRATE 0.33 BUFFERPOOL tmp_bufferpool_name


GRANT USE OF TABLESPACE tablespace_name TO USER db2_userGRANT CONNECT ON DATABASE TO USER db2_userGRANT CREATETAB ON DATABASE TO USER db2_user

UPDATE 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 8096

TERMINATE

Where:

Note: Do not start _name variables with SYS.

Caution! The default tablespace for the database user that owns the Reporting and Analysis repository must not be partitioned.

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

6 If you use an IBM DB2 RDBMS and Reporting and Analysis services are on separate machines, create a client connection to the Reporting and Analysis database using the Client Application Enabler.

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

Variable Name DB2 Description Example

db2_user User who owns the Reporting and Analysis db schema

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

Prerequisites 37

8 Set all necessary environment variables:

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

Configuring Microsoft SQL Server

After you install Microsoft SQL Server, record the Microsoft SQL database host name, port number, and server for use when you install the Reporting and Analysis products. Microsoft SQL Server is not case-sensitive.

The default tablespace for the database user who owns the Reporting and Analysis repository must 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 objects that are built and populated during this installation. The user created here is also the user that Reporting and Analysis services use to connect to the database. Hyperion suggests naming the user biplus.

Note: The Reporting and Analysis repository database user cannot be an administrator, nor can it be a 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 biplusgo grant create table to biplusgo grant select on sysobjects to biplusgo grant create procedure to biplusgo grant create view to biplus gogrant create functioncreate functioncreate function to biplusgo

Configuring Oracle

After you install Oracle, record the Oracle database host name, port number, and Oracle SID (or Service Name) for use when you install the Product Title Variable 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 table space should have UTF-8 as its 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 2

Prerequisites 39

ARCHIVELOGCHARACTER 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 this user. To improve performance, these should not be shared with other applications. Do not use the SYSTEM tablespace. To list the tablespaces, enter the following SQL statement from SQL*Plus:

select * from sys.dba_tablespaces;

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

Note: This action requires CREATE TABLESPACE system privileges.

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

create tablespace tablespace_name datafile 'filespec';

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

create tablespace tablespace_name datafile 'filespec' size nnM;

where nn is the megabyte count.

Plan the repository size. Hyperion suggests starting with 250 MB minimum, 500 MB for a production environment, which provides for a larger repository without increasing the datafile/tablespace. Also, performance is enhanced if you initially create a larger data file.

The sizing of the shared pool is also important, because it determines whether the installer can create all of the necessary repository tables. If the shared pool size on the database is set too small, you receive an error. Hyperion recommends that a shared pool size of 60 MB be used during the installation.

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 objects that are built and populated during this installation. The user created here is also the user that Reporting and Analysis services use to connect to the database. Hyperion suggests naming the user biplus.


Database privileges are required to perform the following actions. The tablespaces created or identified in the previous step are used as the default and temporary tablespaces. To create the user, 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:

grant connect, create table, create view, create sequence to biplus;

4 Set the NLS_LENGTH_SEMANTICS parameter to char:

nls_length_semantics=char

5 Set the necessary environment variable:

Use the System option in Control Panel or the Set command from the Windows command prompt to set the LIBPATH environment variable to the location of the Oracle Client libraries.

SAP Data Source Access and AuthenticationTo configure Reporting and Analysis to access SAP JAVA Connector (SAP JCo) data sources and optionally to authenticate users against an SAP server, you must install the SAP JCo files to each Reporting and Analysis component machine.

Obtain the SAP JCo from:

● Your SAP distribution

● Download it from the SAP web site

● Download it from the SAP web site as a registered user at https://service.sap.com/connectors.

Configure the SAP data source access and authentication after installation, when Reporting and Analysis creates the correct SAP directories. See “Configuring SAP Data Source Access and Authentication” on page 62.

Creating ODBC ConnectionsIf you are going to use ODBC to access your data source, you must create an ODBC connection. For information on installing and configuring the DataDirect ODBC drivers supplied with Product Title Variable, go to the following Web address:

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

Prerequisites 41

Web EnvironmentThe following topics describe pre-installation Web environment considerations:

● “HTTP Server Requirements” on page 41

● “Application Server Setting” on page 41

● “Web Browser Requirements” on page 41

● “Configuring a Web Environment” on page 42

HTTP Server RequirementsThe Web environment requirements are based on support for the World Wide Web Consortium (W3C) standards for servlets (Servlet 2.3) and JSP (JSP 1.1). The Web environment consists of an HTTP server and a servlet container.

For this release, it is recommended that the Apache HTTP Server that is automatically installed and configured be used.

Note: Microsoft IIS and IBM HTTP Server can be configured automatically for use with some application servers. See “Configuration Utility HTTP Server Plug-in Support” on page 71.

Note: To start Apache as a root user, to run a port < 1024, modify httpd.conf by changing Group #-1 to Group nobody.

For information on manually configuring a HTTP Server, see:

● “HTTP Server Plug-in Manual Support” on page 72

● Appendix A, “Manually Deploying into Oracle 10g Release 3 (10.1.3.1.0)”

● Appendix B, “Manually Deploying into WebLogic 8.1.4”,

● Appendix D, “Manually Deploying into WebSphere 5.1.1.7”.

Application Server SettingAll Reporting and Analysis Web applications should have session timeouts set to greater than 10 minutes.

Web Browser Requirements You must have Internet Explorer or Mozilla Firefox to access the Reporting and Analysis user interface.See “Software Requirements” on page 27 for supported version numbers.


Configuring a Web EnvironmentReporting and Analysis requires a servlet engine and a stand-alone HTTP Server.

Note: By default, the Reporting and Analysis installation automatically configures Jakarta Tomcat and Apache HTTP Server.

A servlet is a Java program that runs as part of a network service, typically an HTTP server and responds to requests from clients.

To automatically configure Reporting and Analysis, your own servlet engine must be installed

before you run the Hyperion Configuration Utility™.

If you opt not to deploy Reporting and Analysis to the Jakarta Tomcat Web application server and Apache HTTP Server bundled with the installer, you must manually install a supported application server and HTTP server before configuring Reporting and Analysis.

Hyperion recommends a secure sockets-capable server in a production environment, or where the local network is not protected by some other means (such as a firewall) or where public users are able to access the HTTP server.

After the HTTP server/servlet engine is installed, follow the procedure to configure your Web environment for use with Reporting and Analysis before installing Reporting and Analysis.

Configuring IBM WebSphere

Note: When accessing Essbase, the Financial Reporting or Web Analysis user who starts the Hyperion Web Applications needs to have read and write access to the Essbase.id file. The Essbase.id file is created in the home directory of the user owning the application server process(es). For information on the Essbase.id file, see the Hyperion Enterprise Analytics documentation.

Requirement for WebSphere Apache Plug-in

The IBM Global Security Kit 7 (GSKit7) is required for WebSphere Apache Plug-in, and is included with WebSphere (base) and higher. WebSphere Express users must download and install it manually:

Download the latest version of IBM HTTP Server 2.0 (2.0.47.1 at the time of this writing) for your platform from: http://www.ibm.com/software/webservers/httpservers/

Extract the archive you downloaded, and install only the GSKit7 package:

➤ To extract and install the GSKit7 package:

1 Extract HTTPServer.win.2047.zip.

2 Open a command prompt in the skit subdirectory of your extracted files location.

3 Run the command: setup.exe gsk7bas.

4 Complete the setup Wizard.

Prerequisites 43

SecurityThe following topics describe pre-installation security considerations:

● Shared Services

● Firewall and DMZ Support

Shared ServicesShared Services functionality is programmed into products, such as Planning, Financial Management, and Business Modeling. Shared Services integrates the products to provide the following functionalities:

● User provisioning

● External authentication definition

● Metadata synchronization

● Data synchronization

● Task flow management

User provisioning functionality is described in the Hyperion Shared Services User Management Guide. External authentication definition is described in the Hyperion Shared Services Installation Guide. All other Shared Services functionality is described in the administrator's and user's guides for the products that implement Shared Services. Products that implement Shared Services functionality require access to a Shared Services server running Shared Services client and server software, and to a database dedicated to Shared Services.

Firewall and DMZ SupportAll elements of Reporting and Analysis work within configurations where one or more firewalls are deployed, and that communicate through HTTP and HTTPS (at 56- and 128-bit encryption levels). The supported firewall configurations are:

● No firewalls present

● Browser | Firewall | HTTP server with Product Title Variable servlets | Reporting and Analysis server components

● Browser | Firewall | HTTP server | Firewall | Application server with Reporting and Analysis servlets | Reporting and Analysis server components


Figure 1 Supported Firewall Configurations

Workspace and Financial Reporting Web Applications

➤ To support Browser | Firewall | HTTP server + Web application server with Workspace and Financial Reporting Web Applications | Firewall | Reporting and Analysis server components:

1 For Financial Management ADM driver, fix DCOM dynamic ports in a range and open RPC port 135 to the Financial Management Application servers. The specified range should have 11 ports minimum (5000-5010 for instance). To configure the DCOM port range, refer to http://support.microsoft.com/kb/300083.

Note: Specify the 135 port as well as the range in the Properties for COM Internet Services.

2 Disable the streaming option in the Servlet configurator on the Workspace Web Application server: To modify ws.conf located in the config folder, select Properties > Internal > Transfer and deselect Pass data using streams instead of files.

Note: If you deployed your Web application manually, you may have to open the batch that launches the servlet configurator to correctly set the deployment_path folder.

Prerequisites 45

The modification to ws.conf done by the configurator is:

WebClient.Internal.Transfer.PassDCByStream=false

3 Open the Interactive Reporting base services ports in the firewall, with the ports listed in the installer.

CS: 1800 and 1801

Service broker:1497

Reporting and Analysis/DAS: Configure a range of ports by adding a line into common/fif/default-domain.cfg.

For example:

policies:iiop:server_address_mode_policy:port_range = "1805:1812";

A total of 8 ports are needed for both Reporting and Analysis / DAS: each Reporting and Analysis/DAS uses 2 ports and with active standby, each need 4 ports.

4 Open the ports to connect from the Web Application server to the external authentication providers.

This is different from previous Reports versions. The Web Application is getting the CSS file from Shared Services, but then opens connection to the authentication provider (MSAD port 389, Open ldap 58089,…).

5 Open Shared Services http port (depends on which machine calls Shared Services, IIS, or WebLogic).

6 Assigning a fixed value to the ports in Reports services box (fr_...properties in lib biplus/lib folder -> set HrPrintSvrPort, HrRepServerPort1 and2, HrSchdSvrPort, HrHtmlSvrPort) and open these ports.

Note: In the Web Application, Financial Reporting Studio must be installed.

7 Modify the Licence Server HYSLD agent port by changing the VENDOR HYSLD line to:

VENDOR HYSLD PORT=yournewport

This is not the 27000, but the HYSLD one. With this fixed port open in the firewall, the components can register with the Licence Server through the firewall and communicate with the HYSLD process.

8 To test if a port is open, type:

telnet servername port

If an empty window opens, the port is open in the firewall. Otherwise, the host will be unreachable.

Interactive Reporting Row-level Security

Note: Row-level security setting in Release 7.x cannot migrate to 8.x; Release 8.x can migrate to 9.x.

Note: The win32 Financial Reporting Studio client needs to be able to access the Foundation server machine (Interactive Reporting Base Service 1).


Distributed and Replicated ComponentsReporting and Analysis server components are designed to work in a distributed and replicated manner. Distributed components make it possible to install components on separate computers. Replicated components make it possible to install multiple instances of the same component on separate computers where Reporting and Analysis automatically routes work across the components.

It is important to note that performance characteristics are not the same for all implementation configurations. Capacity planning and configuration planning information is not covered by this document.

This release of Reporting and Analysis has services that run standalone as self-contained server processes, and others that run inside a servlet container. The core services run standalone and provide basic functionality for authentication, authorization, session management, load balancing, job service, Interactive Reporting and Data Access services, logging and usage tracking. The Financial Reporting Report Server, Print Server, and Schedule Server also run as standalone processes.

This release of Reporting and Analysis supports the following configurations of distributed and replicated components:

● Distributed Configurations

❍ All components on same computer

❍ All Web components on one computer; all other components on a second computer

❍ Base services on a separate computer; business services on a separate computer

❍ All components fully distributed

● Replicated Configurations

❍ No replication; single implementation of all components

❍ Servlets (as a unit) replicated

❍ Authentication Service replicated

❍ Data Access Service replicated

❍ Workspace replicated

❍ Job Service replicated

❍ Service Broker replicated

❍ Session Manage replicated

❍ Usage tracking, Assessment, and Update service replicated

❍ Authorization Service replicated

❍ Analytical Bridge Service replicated

❍ Web Analysis UI Services

❍ Financial Reporting UI Services

❍ Financial Reporting Report Server - requires Financial Reporting UI Services be replicated to balance load

❍ Financial Reporting Print Server

Prerequisites 47

The following limitations apply to distribution and replication:

● Publisher, Event, Repository, and Logging Services cannot be replicated

● LSM is not directly installed; it comes with other services. You can have one LSM per process space

● Publisher, Authorization, and Repository Services are required in one process space

● Workspace requires Job Service

● Financial Reporting Scheduler Server

Installing ConsiderationsThe following topics describe pre-installation installing considerations:

● “Satisfying Temporary Space Requirements” on page 47

● “Command Line Processor Considerations” on page 47

Satisfying Temporary Space RequirementsThe Reporting and Analysis installer requires 1 GB of temporary space.

➤ To redirect temporary space for the installation to somewhere else, take one of the following actions:

● Use this command:

setupWinPlatform.exe -is:tempdir directory_name

where directory_name is a directory on your system with space.

● Alternately, you can change the TEMP environment variable (Start > Setting > Control Panel > System, Advanced tab, Environment Variables)

Command Line Processor ConsiderationsTo run the installer from the Command Line Processor, you must designate a temporary directory where the installer can uncompress and run, for example:

mkdir D:\Temp

setupWinPlatform.exe -is:tempdir D:\Temp -is:javaconsole -console

Note: -is:javaconsole activates DOS where you can see debug messages while installing. User only after experiencing problems for collecting more debug information for support. -console is used for running a command-line installation. Since most users use the GUI, this is optional for specific users.


Configuring a Production Reporting Server InstallationIf you intend to use Production Reporting iServer to run Production Reporting jobs, you must have a Production Reporting Server license before running the Reporting and Analysis installer. During services configuration, the configuration tool prompts for the following production reporting information:

● Root directory for the database client software for Job Service

● Connect string for Job Service (the string utilized by the Job Service to connect to a database when a connection is required during the execution of Production Reporting jobs)

● Location of Production Reporting Server sqr.ini file (only required if the installer cannot find it in the standard location, or if the environment variable Production Reporting SQRDIR is not set)

Browser SettingsReporting and Analysis supports Internet Explorer, and Mozilla Firefox. Make sure that browser preferences and options are enabled as follows:

● For Internet Explorer and Mozilla Firefox:

❍ Enable JavaScript.

❍ Enable cookies. The preferred setting is to allow cookies to be stored on your computer. Minimum requirement is per session level cookies set.

❍ Allow pop-up windows for the Reporting and Analysis Web Application server.

● For Internet Explorer

❍ Enable ActiveX to support Bindows. For supplemental information on ActiveX, see Appendix F, “ActiveX.”.

❍ Add the Reporting and Analysis Web site to the trusted zone. For example, for Internet Explorer this is done through the Internet Options by selecting Tools > Internet Options > Security Tab > Trusted Sites, and clicking Sites.

❍ Change browser cache settings so that pages are checked for changes with every visit. This is a required setting for Financial Reporting to view PDF documents. This is done by selecting Tools > Internet Options. On the General tab, select Settings from the Temporary Internet files group. Then select Every visit to the page on Settings.

Module-specific PrerequisitesPrerequisites:

● “Financial Management” on page 49

● “Financial Reporting” on page 49

Module-specific Prerequisites 49

Financial ManagementFinancial Management currently runs on Microsoft Windows. For best performance when accessing Financial Management, Financial Management requires you install the Financial Reporting Services and Web Analysis and Financial Reporting UI Services on a Windows operating system.

Since data access interface for Financial Management resides only in Windows, when running Reporting and Analysis on UNIX, the data access layer is split between components that run on UNIX and components that run on Windows. Internal tests indicate that Reporting and Analysis server components installed on UNIX, while fully functional, can be significantly slower than Reporting and Analysis server components installed on Windows only.

Financial ReportingThe following requisites apply to Financial Reporting:

Selecting the Server Components Java Virtual Machine for Financial ReportingReporting and Analysis uses Sun Microsystem's Java Virtual machine (JVM) for all Server Components: Report Server, Print Server, Scheduler Server, and UI Services.

You can optionally use a another JVM vendor during installation; for example, BEA JRockit 1.4.2. See: http://www.bea.com/jrockit.

For Tomcat, you must select JDK. Otherwise, a JRE installation is sufficient.

➤ To specify a JVM for use by the Server Components:

1 Create a User or System environment variable called HR.server.java.dll on the Server Component(s) machine.

2 Assign the full path to the jvm.dll that is included with the JVM implementation.

Note: You must select a JDK if using Tomcat. Otherwise, a JRE installation is sufficient.

Cell Attachment Support and Configuration RequirementsThe following Microsoft Office 2000, 2002, or 2003 documents can be printed to PDF:

● Microsoft Word files (*.doc, *.rtf)

● Microsoft Excel files (*.xls, *.xlc)

● Microsoft PowerPoint files (*.ppt)

Note: All file types can be accessed from the HTML client.


Printing Cell Documents

In order to print cell documents, the corresponding “print” applications (Microsoft Word, Excel and PowerPoint) on the Print Server machine must:

● Be properly installed

● Be properly registered for printing in the computer’s registry

● Be available to the “SYSTEM” account

● Have access to, and be able to print from, the printers installed by Financial Reporting (HRPrinter1-5). The SYSTEM account issues all print requests, so it is important that the applications can print using the Print Server’s printers.

An easy way to test running a program using the SYSTEM account, is to use the at command at a command prompt. While the at command is meant primarily for scheduling a task (also known as the Windows Task Scheduler), another result is that all scheduled tasks run under the SYSTEM account. The parameters for the at accounts are as follows:

at time/interactive “command”

where:

at—task scheduler program

time—time, in 24-hour notation (00:00 through 23:59) when program should run

The time parameter must be indicated. To print immediately, it can be set to one minute past the current time. For example, if the current time is 10:29 AM, you can launch Excel under the SYSTEM account by using the following from a command prompt: at 10:30:

For Office 2003: /interactive “C\Program Files\Microsoft Office\OFFICE11\Excel.exe”

For Office 2002:/interactive “C\Program Files\Microsoft Office\OFFICE10\Excel.exe”

For Office 2000:/interactive “C\Program Files\Microsoft Office\OFFICE\Excel.exe” The command prompt displays something similar to: Added a job with job ID = 1

At 10:30, Excel launches (under the SYSTEM account). Once Excel is launched, you can test whether you can use the printers by issuing a print command (File - Print) and making sure the printers list contains the HRPRinters.

/interactive—allows the program to interact with the desktop of the user who is logged on at job run time

“command”—full program path

Additional considerations when working with cell attachments:

● Include the correct supported extensions for files (*.doc, *.rtf, *.xls, *.xlc, *.ppt).

● Files that are corrupt or improperly uploaded to the ADM provider (through Financial Management client or Essbase Add-in for Excel) do not print.

Port Numbers 51

● Microsoft files containing macros or that trigger UI components requiring user input are not supported. Some MS files with macros perform operations when the file is opened which include the dialog launching requiring user input. Files that display dialogs or UI components requiring user input are not be available for printing. Additionally, such files halt the PDF generation process, requiring the server’s administrator to restart the Print Server machine to resume printing activities.

● Documents that contain file extensions that are not properly registered to print, fail.

Print Server RequirementsDisable:

● All add-ins (including Hyperion add-ins) from all Microsoft Office applications—To enhance application launch time and consume system resources. If enabled, it may display UI components that require user input.

● SmartTags (Office 2002+)—To enhance performance.

● “Office Assistant”—Office Assistant prompts the user for input which halts the printing process.

Tip: Dedicate a machine for use as a Print Server, ensuring that add-ins are not used.

Port NumbersDuring Reporting and Analysis product installation, the default port number for application servers is automatically populated and can be changed during the configuration process. See “Customizing Service Ports for Reporting and Analysis” on page 73.

Each application port number must be unique. After modifying the default port number, if your application does not launch, or if an error message is displayed similar to “port already in use” or “bind error,” there may be a port number conflict.

If you do not change the default port number, the software is configured with these values:

Hyperion Product Listen Port SSL Listen Port

Shutdown Port for

Apache Tomcat

Shared Services 58080 58090 58005

Application Builder J2EE 21080 21090 21005

Analytic Administration Services 10080 10090 10005

Analytic High Availability Services 11080 11090 11005

Planning 8300 8300 8301

Hyperion Translation Manager™ 14080 14090 14005


Default Port Numbers for Remote Method Invocation (RMI) Servers

AJP Connector Ports for Reporting and AnalysisThe Apache JServ Protocol (AJP)

Financial Reporting 8200 8201

Web Analysis 16000 16001

Hyperion Business Modeling™ 17080 17090 17005

Performance Scorecard 18080 18090 18005

Performance Scorecard Alerting 18081 18091 18006

Essbase Smart View Provider 13080 13090 13005

Workspace 19000 45001

Hyperion component RMI PORT

Hyperion Remote Authentication Module 58000

Financial Reporting 1099

Planning 11333

Strategic Finance 1493 and 1495

Hyperion Performance Suite Legacy 1494 - 1498

Hyperion Performance Suite GSM 1800

Hyperion Performance Suite Services 1801-1803

OpenLDAP 58081

Hyperion Component AJP Connector pORT

Workspace 45002

Financial Reporting 8202

Web Analysis 16002

Hyperion Product Listen Port SSL Listen Port

Shutdown Port for

Apache Tomcat

Port Numbers 53

Configuring IBM WebSphereYou must change the wsadmin.bat script (the last line that executes com.ibm.ws.bootstrap.WSLauncher) and add -Xmx512M for Java there. During servlet deployment on WebSphere, deployment may fail if the WebSphere administrator application (wsadmin.bat) is set to use less than 512 MB of memory. In case of deployment problems, set a higher heap value and retry.


Installing Reporting and Analysis 55

C h a p t e r

4Installing Reporting and

Analysis

In This Chapter Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Reporting and Analysis Installers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Using Installation Wizards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Hyperion Home . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Installing Reporting and Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

56 Installing Reporting and Analysis

Prerequisites● Use database configuration tools to create a database. See “Configuring Database Software

for the Reporting and Analysis Repository” on page 34.

● Install and configure Shared Services, and have a CSS configuration file available. See Hyperion Shared Services Installation Guide and Hyperion Shared Services Readme.

● Read the Hyperion Reporting and Analysis Readme.

Note: Beginning with this release, Hyperion® License Server™ and standalone license files are not used for license management. Instead, administrators need to audit product use. To ensure compliance with your license agreement, you need to edit a properties file to activate or deactivate features in accordance with what you have purchased.

For more information about license compliance, see the Hyperion License Compliance Readme (hyp_license_compliance_readme_921.pdf), which you can find on the Oracle® E-Delivery site or the product DVD .

Reporting and Analysis InstallersFor each computer, run one or more of the installers associated with the computer:

Installer Installer Description Executable Folder

Services Workspace base services, and services for the Reporting and Analysis modules, and Financial Reporting standalone servers: Report Server, Print Server, Scheduler Server; for example, GSM Name Services, Authentication Service, Repository Service, Job Utilities, and Interactive Reporting SDK.

services<OS>CD

UIServices Web components related to Workspace, Financial Reporting, Interactive Reporting, and Web Analysis Studio, and Interactive Reporting Plug-ins; installs the component to view Production Reporting job output

uiservices<OS>CD

Client

(Windows only)

Modules and components that are needed for the client desktop: Financial Reporting Studio, Interactive Reporting Studio, Production Reporting Studio, Activator, Remote, and Viewer

clientCD

SQR Production Reporting

Production Reporting module and components: Production Reporting DB2, DDO, Informix, ODBC, Oracle, Sybase, and Teradata

repservices<OS>CD

Migrator Components that are needed for migrating data from previous Hyperion products into the current release

migratorCD

http://edelivery.oracle.com/

Using Installation Wizards 57

Reporting and Analysis Module Installers

Note: 1 Workspace is a Web application common to Financial Reporting, Interactive Reporting, Production Reporting, and Web Analysis. Workspace, Interactive Reporting, and Production Reporting are installed together.

Note: 2Each installer contains the documentation pertaining to the installer components.

Using Installation WizardsWith each installer wizard, you perform a typical or custom installation:

● Typical—Installs commonly required modules

● Custom—Installs selected Reporting and Analysis modules

Two chapters guide you through Reporting and Analysis installation and configuration:

● This chapter guides you through the installer process.

● Chapter 5, “Configuring and Setting Up Reporting and Analysis” guides you through the Configuration Utility and descriibes the steps to launch Reporting and Analysis.

Services (In servicesCD Folder)2

Web Applications (In UIServicesCD Folder)2

Client (In clientCD Folder, Windows Only)2

Production Reporting (In repservicesCD Folder)2

Financial Reporting

-Base Services

-Financial Reporting Services:

-Financial Reporting Server

-Financial Reporting Print Service

-Financial Reporting Scheduler Service

-Workspace1

-Financial Reporting

-Financial Reporting Studio Not needed


-Base Services

-Impact Management Services

-Dashboard Development Services

-Interactive Reporting Services:

-Interactive Reporting Service

-Data Access Service

-Workspace1

-Interactive Reporting

-Interactive Reporting Studio

-Dashboard Development Services

Needed for Production Reporting job output viewing

Web Analysis -Base Services -Workspace1 Not needed Not needed


-Base Services -Workspace1 -Production Reporting

-Studio

-Activator

-Remote

-Viewer

-Production Reporting Server

-DB2

-DDO

-Informix

-ODBC

-Oracle

-Sybase

-Teradata


Hyperion HomeWhen multiple Hyperion products are installed on the same computer, common internal and third-party components used by the products are installed to a central location, (Hyperion Home), which is defined in the system environment variable HYPERION_HOME.

Hyperion Home LocationIf the current installation is the first Hyperion installation on the computer, the Reporting and Analysis installer prompts you to define the location for Hyperion Home. The default location is C:\Hyperion. If Hyperion Home was previously defined, the current installation uses the defined location.

Changing the Hyperion Home Location

Note: It is recommended that you retain the initial Hyperion Home location.

After a product installation defines Hyperion Home, you must run a migration utility to change the Hyperion Home location. The utility moves the files installed in Hyperion Home to the new location.

➤ To change the Hyperion Home location:

1 Launch the migration utility by performing an action:

● From the Start Menu:

<HYPERION_HOME>\common\utilities\HyperionHomeTool\1.0.1\bin\run.exe

● From Console:

<HYPERION_HOME>\common\utilities\HyperionHomeTool\1.0.1\bin\run.exe -console

2 Step through the screens, and when prompted, enter the new Hyperion Home location or click Browse to navigate to the desired location.

The migration utility copies the Hyperion Home directory to the new location and replaces the current HYPERION_HOME environment variable value.

The utility updates the HYPERION_HOME environment variable.

Installing Reporting and Analysis 59

Installing Reporting and Analysis

Note: If install SQR Production Reporting or Interactive Reporting Studio as a stand-alone product, copy the Hyperion back-office supplied license file to your product server computer and specify the full path to the license file during product activation during installation.

➤ To install Reporting and Analysis:

1 Download the software from the Oracle® E-Delivery site.

2 Shut down all processes and services related to previous component releases.

3 Execute the installers by launching from a command line processor or navigating to the directory in which the Reporting and Analysis file was downloaded.

See “Reporting and Analysis Installers” on page 56.

4 When the Reporting and Analysis splash screen is displayed, click Next.

The Country Location is displayed.

5 Select the country where you are installing the software.

The setup program displays a license based on the selection.

6 Click Next.

7 Read the License Agreement, select I ACCEPT, and click Next.

8 When the directory path for the installation displays, click Next to accept the default Reporting and Analysis directory or click Browse to select another directory.

The new installation default path is C:\Hyperion\BIPlus.

Note: When running several installers, make sure that you install components into the same installation directory.

Note: You can enter only English alphanumeric characters and these special characters: dash ( - ), underscore ( _ ), plus sign ( + ), backslash ( \ ), forward slash ( / ), dot (.), colon ( : ). The colon character ( : ) is supported only for Windows platforms to specify the drive (for example, c:\).

9 Select the installation path for Hyperion Home.

Common components for Hyperion products are installed to <HYPERION_HOME>\common. See “Hyperion Home” on page 58.

10 Click Next to accept the default installation, or click Browse to select another location, and click Next.

Note: If the installation program detects a directory for Hyperion Home, Directory Name and Browse are disabled.

11 Click Next.

The Setup Type page is displayed.


12 Select a setup type of Typical or Custom, and click Next.

See “Using Installation Wizards” on page 57.

13 If you selected Custom , select the features for Reporting and Analysis.

● For Production Reporting, or client installers, when the license information dialog box is displayed, enter the license file directory and Deployment ID.

● For Financial Reporting alone, the license file dialog box is not displayed.

14 From the Summary screen,review the components selected for the install and click Next to proceed with the install or Back to change selections.

The wizard installs the Reporting and Analysis components.

15 After the installation is complete, the installation wizard may, under certain circumstances, prompt you to launch the Configuration Utility.

If you run multiple installers on the same machine, choose one option:

● If you are not on the last installer, click Finish.

● If you run the last installer, click Run the Configuration Utility.

● If you run the Client or Production Reporting installers, click Finish.

● In the Client installer, if you install the Financial Reporting Studio and chose the Typical install, perform the product activation in the configuration tool.

16 See Chapter 5, “Configuring and Setting Up Reporting and Analysis.”

Configuring and Setting Up Reporting and Analysis 61

C h a p t e r

5Configuring and Setting Up

Reporting and Analysis

In This Chapter Post Installation Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Using the Configuration Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Registering Reporting and Analysis with Shared Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

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

Configuring Relational Storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

Deploying Reporting and Analysis to Application Servers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

Deploying Reporting and Analysis to Application Servers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

Undeploying from an Application Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

Enabling the HTTP Server Plug-in . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

Completing Module-Specific Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

Completing Configuration Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Configuration Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Post Configuration Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

Reconfiguration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

62 Configuring and Setting Up Reporting and Analysis

Post Installation TasksPost installation tasks include:

● Configuring SAP Data Source Access and Authentication

Configuring SAP Data Source Access and AuthenticationTo configure Reporting and Analysis to access SAP JAVA Connector (SAP JCo) data sources and optionally to authenticate users against an SAP server, you must obtain the SAP JCo and extract the files to each Reporting and Analysis component machine.

➤ To configure Reporting and Analysis to use SAP as a data source and optionally to use SAP as an authentication provider:

1 Obtain the SAP JCo files from:

● Your SAP distribution

● Download from the SAP web site

● Download from the SAP web site as a registered user at https://service.sap.com/connectors

2 After Reporting and Analysis installation, place the SAP JCo binaries (DLL files) in <HYPERION_HOME>/common/SAP/bin.

3 Optional: To configure Reporting and Analysis to use SAP as an authentication provider:

a. Download these files from the SAP Enterprise Portal EP60 SP2 or higher:

❍ com.sap.security.core.jar

❍ com.sap.security.api.jar

❍ sap.logging.jar

❍ iaik_jce.jar

❍ iaik_jce_export.jar (if using the export version of the IAIK-JCE libraries)

into <HYPERION_HOME>\common\SAP\lib

b. After installation, expand the JAR files, using the convenience utility, explodejar.bat, in <HYPERION_HOME>\common\SAP\lib or winzip.

Using the Configuration UtilityThe Configuration Utility is a centralized tool for configuring Shared Services and Reporting and Analysis. If your module has unique configuration requirements, the Configuration Utility provides additional options to enable you to complete all necessary configuration tasks. (See “Completing Module-Specific Configurations” on page 72.) For information on how to launch the Configuration Utility, see “Launching the Configuration Utility” on page 65.

Using the Configuration Utility 63

The Configuration Utility guides you through a series of pages to perform the following configuration tasks:

● Shared Services Registration—Required for all products. See“Registering Reporting and Analysis with Shared Services” on page 66

● Shared Services Deregistration—Required to deregister Reporting and Analysis from Shared Services. If you need to uninstall Reporting and Analysis and if Reporting and Analysis is registered with Shared Services, perform this step first to deregister the product before uninstalling it. See “Deregistering Reporting and Analysis with Shared Services” on page 66 and “Uninstalling Reporting and Analysis” on page 81

● Relational Storage Configuration— See “Completing Module-Specific Configurations” on page 72

● Application Server Deployment— See “Deploying Reporting and Analysis to Application Servers” on page 68.

● Startup Dependencies Verification—See “Verifying Startup Dependencies” on page 76

You can use the Configuration Utility to perform configuration tasks sequentially for multiple products in one session. The sequence of Configuration Utility pages depends on your product and task selections. As a troubleshooting measure, perform configuration tasks individually for one product at a time.

You can reconfigure products after the initial configuration, following the same procedures.

Note: Do not select “Registering” and “Deregistering” products with Shared Services”, nor “Deploying” and “Undeploying” products on an application server at the same time.

PrerequisitesComplete these tasks before using the Configuration Utility:

Task Documentation

Obtain a valid license for each product. Shared Services Installation Guide

Install, configure, and start the Shared Services server. Shared Services Installation Guide

“Starting Shared Services” on page 77

Install the application server that you plan to use. Application server documentation

Prepare a database to use for relational storage.

The database user that you specify during configuration should have the following user rights for the database: inserting seeded data and creating, deleting, and updating tables.

Database documentation

Install Hyperion products.

Note: Do not start the product you are configuring.

Product installation guide


Task SequenceWhen performing multiple configuration tasks in one session, the Configuration Utility orders the tasks for you. When performing tasks individually, follow this order:

● Product activation

● Shared Services registration

● Database configuration

● Application server deployment

Configuring Product UpgradesYou can use the Configuration Utility to configure products that are upgraded from previous System 9 release (for example, 9.0.0 or 4.0.0). The Configuration Utility determines whether the products installed on the machine are new or upgraded. The product selection page indicates which products were specified as upgrades during the product installation process.

All configuration tasks are available for upgraded products; however, if an upgraded product is configured for a relational database, the database configuration page is read-only except for the password. You can configure only one upgraded product at a time because each product may be configured for a different database. Similarly, you cannot configure new products and upgraded products simultaneously.

If you are upgrading Shared Services and products, upgrade Shared Services first. You must activate upgraded products and reregister them with Shared Services.

Note: The Configuration Utility is backward compatible with the previous releases and can be used to configure products for that release.

Specifying Application Server Hostnames and HTTP Connector Plug-in PortsWhen Reporting and Analysis UI Services are distributed among 2 or more machines, or when configuring an HTTP server on a machine other than where the Application Server(s) are installed, you must provide the following:

● Correct Application Server hostnames—Specify the machine name and port as part of the Configuration Utility.

● HTTP plug-in ports—Manually enter the information in the HTTP plug-in configuration file(s).

See:

● “Manually Deploying into Oracle 10g Release 3 (10.1.3.1.0)” on page 93

● “Manually Deploying into WebLogic 8.1.4” on page 111.

● “Middle Layer Components” on page 30 for important file descriptor information.

● “Manually Deploying into WebSphere 5.1.1.7” on page 161

Using the Configuration Utility 65

Tip: When deploying to Tomcat, the port(s) you must specify are the AJP3 ports, not HTTP listen ports. For example, 8202, 16002, and 45002 for Financial Reporting, Web Analysis, and Workspace, respectively. For WebLogic and WebSphere, the connector ports and the HTTP listen ports are identical. For example, 8200, 16000, and 45000.

Launching the Configuration UtilityYou must run the Configuration Utility on each machine to which a product is installed. The utility can be launched from a product installer or independently.

Note: Before beginning the configuration process, ensure you have installed the application server you plan to use and you have installed and configured an empty database. Also, ensure that Shared Services server is up and running to enable registration of Reporting and Analysis with Shared Services.

➤ To launch the Configuration Utility:

1 Choose a method:

● After running the applicable installers for a computer, on the final screen of the last installer, click Launch Configuration Utility.

● Choose a method:

❍ From the Start menu, select Programs -> Hyperion System 9 Foundation -> -> Configuration Utility

❍ Double click the configtool.bat file from:

<HYPERION_HOME>\common\config\

❍ From a console, run configtool.bat -console: from:

<HYPERION_HOME>\common\config

2 On the welcome page, click Next.

3 From the list of installed products, select those to configure and click Next.

A list of configuration tasks is displayed.

4 Follow the instructions for configuration tasks:

● “Registering Reporting and Analysis with Shared Services” on page 66

● “Deregistering Reporting and Analysis with Shared Services” on page 66

● “Configuring Relational Storage” on page 67

● “Deploying Reporting and Analysis to Application Servers” on page 68

● “Enabling the HTTP Server Plug-in” on page 71

● “Completing Module-Specific Configurations” on page 72

● “Completing Configuration Utility” on page 75

● “Configuration Troubleshooting” on page 75


Registering Reporting and Analysis with Shared ServicesShared Services functionality is programmed into Hyperion products to enable user provisioning, single-sign on, and metadata management.

Products that implement Shared Services functionality require access to the Shared Services server and to a database dedicated to Shared Services. Registering with Shared Services enables a product to implement the required information in the Shared Services server by creating a registration file under its corresponding product directory in Shared Services.

➤ To register the selected modules with Shared Services:

1 Launch the Configuration Utility.

See “Launching the Configuration Utility” on page 65.


3 On the task selection page, select Shared Services Registration and click Next.

4 Specify Shared Services server information:

5 Click Next to go to the next configuration task or to finish.

Deregistering Reporting and Analysis with Shared ServicesIf you uninstall Reporting and Analysis after configuration and Reporting and Analysis is registered with Shared Services, perform this step first to deregister Reporting and Analysis before uninstalling it.

➤ To deregister Reporting and Analysis with Shared Services:


See “Configuring Product Upgrades” on page 64.


3 On the task selection page, select Shared Services Deregistration and click Next.

On the Shared Services location page, the Server, Port, and User fields display the information that was specified when the product was registered with Shared Services.

Table 6 Shared Services Server Fields

Server Enter the computer name (host name) where Shared Services server is installed.

Port Enter the Shared Services server port number, or accept the default (58080).

User Enter the username of Shared Services Administrator.

Password Enter the password for Shared Services Administrator.

SSL Select this checkbox if you are using Secure Sockets Layer (SSL).

Configuring Relational Storage 67

4 For Password, enter your password and click Next.


Configuring Relational StorageTo enable database configuration, the database must not contain tables that were created as part of a previously configured instance of Reporting and Analysis.

Note: You must have a properly configured database before proceeding with the next section. A test connection is made to the database to ensure the information entered is correct.

When you configure products to use a database, the Configuration Utility checks for connectivity to the database and ensures that the database is a supported database type.

If errors occur during a multiple-product configuration, terminating configuration for a particular product does not terminate the entire process. Configuration continues for the other products. The Configuration Utility displays error messages on a summary page after the configuration process completes.

For a list of supported databases for this release, see Chapter 3, “Planning the Installation”.

➤ To configure a database:




3 On the task selection page, select Relational Storage Configuration and click Next.

4 From the list of supported databases, select the database and click Next.

The relational storage configuration details page is displayed.

Note: If you are configuring a product upgrade, the fields on this page are read-only except for the password.

5 Specify database information:

Table 7 Database Configuration Fields

Server Enter the computer name of the server hosting the database.

Port Specify the server port number on which the database listens, or accept the default port:

● DB2—50000

● Oracle—1521

● SQL Server—1433

Product Displays the name of each product being configured and its install location. This field cannot be changed.


6 Click Next to view configuration status.


Deploying Reporting and Analysis to Application ServersThe Configuration Utility enables you to deploy multiple Reporting and Analysis modules to an application server. The application server must be installed on the same machine as the products you are deploying.

To view the list of supported application servers for this release, see Chapter 3, “Planning the Installation”.

➤ To deploy products to an application server:




3 On the task selection page, select Application Server Deployment and click Next.

4 From the list of supported application servers, select the application server and click Next.

A page is displayed that is specific to the selected application server.

Database or SID (Oracle only) Enter the database name or the Oracle System Identification (database instance). You can enter only English alphanumeric characters and the dash character (-).

Username Enter the name of the database owner.

Password Enter the password of the database owner.

Table 7 Database Configuration Fields

Deploying Reporting and Analysis to Application Servers 69

5 Specify application server information:

Table 8 Application Server Configuration Fields

Location Enter the path to the location of the application server directory (for example, c:\WebLogic\Appserver), or browse to and select the location.

Enter the path to the application server directory, or browse to the directory.

For example:

● For WebSphere Base—

c:\WebSphere\AppServer

● For WebSphere Express—

c:\IBM\WebSphere\Express51\AppServer

● For WebLogic—

c:\bea\weblogic81

Note: For WebSphere, the Configuration Utility verifies that the specified WebSphere directory and the WebSphere temporary directory are set with Write permission. Write permission must be assigned before running the Configuration Utility.

BEA Home (WebLogic only) For WebLogic, enter the path to the BEA Home directory (for example, c:\), or browse to and select the location.

Username and Password (WebLogic only)

Enter your WebLogic username and password.

Deploy as service Select this checkbox if you want to deploy as a Windows service.

In the Windows service control panel, the service name is listed as:

Hyperion <Product> <AppServer><Version#>

For example, for WebSphere:

Hyperion SharedServices9 WAS51

Note: Do not select “Deploy as Service” if you select “Manual Deployment”.

Note: Window Services are deployed as manual startup.

Manual Deployment Select this checkbox to manually deploy products to the application server. The Configuration Utility creates the necessary Web archives (EAR or WAR) to enable manual deployment at a future time. For more information, see

● Appendix A, “Manually Deploying into Oracle 10g Release 3 (10.1.3.1.0)”

●

● Appendix B, “Manually Deploying into WebLogic 8.1.4”

● Appendix D, “Manually Deploying into WebSphere 5.1.1.7”

Component Displays the name of each product or component being configured. This field cannot be changed. For example, if you are configuring Reporting and Analysis, then Intelligence and Web Analysis components may appear in this column.

ServerName Enter the name of the server where you can access the deployed product.

You can enter only English alphanumeric characters and the dash character (-).


Note: For all application servers, if you chose to deploy products automatically rather than manually, the Configuration Utility checks server disk space when starting deployment to ensure that the size of the EAR or WAR file (as specified in the product configuration file) is available for deployment. The Configuration Utility notifies you if inadequate space is available. If this occurs, in the product configuration file, you must specify a different location for storage of the EAR or WAR files and then repeat the automatic deployment process. On WebSphere, if you chose to deploy products automatically rather than manually, the Configuration Utility checks server disk space for the java.io.tempdir folder when starting deployment to ensure that at least four times the size of the EAR or WAR file (as specified in your product configuration file) is available for deployment. If inadequate space is available on the server, the Configuration Utility relocates java.io.tempdir to <HYPERION_HOME>\temp. After deployment is completed, the folder is automatically deleted.

6 Click Next to view configuration status.


Undeploying from an Application ServerThe Configuration Utility enables you to undeploy Reporting and Analysis.

➤ To undeploy:



2 From the list of installed products, select Reporting and Analysis and click Next.

3 On the task selection page, select Application Server Undeployment and click Next.

4 From the list of supported application servers, select an application server and click Next.

Port If you want to change the default port number that was set during installation, specify a different port number here. Otherwise, accept the default port number.

Each application port number must be unique. For a list of default port numbers, see “Port Numbers” on page 51.

If you want to change the default port number that was set during installation, specify a different port number here. Otherwise, accept the default port number. The port number must not exceed 65535. Hyperion recommends using a port number greater than 1025 to avoid conflicts with third-party port assignments.

Each application port number must be unique. For a list of default port numbers, see “Port Numbers” on page 51.

Domain (WebLogic only) Enter the name of the domain where you can access the deployed product. You can enter only English alphanumeric characters.

Table 8 Application Server Configuration Fields

Enabling the HTTP Server Plug-in 71

Enabling the HTTP Server Plug-in If you enable the HTTP Server plug-ins, on the HTTP server plug-in configuration dialog, select Enable module and enter the host and port number for one or more of the following modules:

Note: NOTE: The HTTP Server Plug-in is not an optional component, and must be installed and configured on at least one machine.

● Financial Reporting

● Web Analysis

● Performance Scorecard

Note: To add a component after finishing the configuration, you must execute the Configuration Utility to configure the application deployment and add the additional HTTP Server plug-in information.

Configuration Utility HTTP Server Plug-in SupportThe Reporting and Analysis Configuration Utility supports the following HTTP Server plug-ins:

Note: 1If IIS is chosen as the HTTP server during Configuration, and IIS version is 6.0; for example: OS=Windows 2003, you must allow all unknown ISAPI extensions via the Internet Information Services Manager.

Table 9

Apache IBM IIS1

WebSphere Yes Yes

Web Logic Yes

Tomcat Yes Yes


HTTP Server Plug-in Manual SupportFor Reporting and Analysis supported manual configurations of HTTP Server plug-ins, see the individual application server appendixes:

Completing Module-Specific ConfigurationsYou can use the Configuration Utility to perform configuration tasks for a module. These tasks are displayed on the Configuration Utility task list. For example, Configuring the Production Reporting engine is a configuration task that must be performed for deploying Production Reporting.

Module-specific configuration windows:

● “Workspace Configurations” on page 72

● “Completing Financial Reporting Configurations” on page 73

Workspace Configurations Workspace configurations:

● “Customizing the Context Path” on page 72

● “Specifying the GSM Host and Port” on page 73

● “Customizing Service Ports for Reporting and Analysis” on page 73

● “Configuring the Production Reporting Engine for Interactive Reporting” on page 73

Customizing the Context Path The Context Path configuration dialog displays when installing the Interactive Reporting services in a separate home directory from UIServices.

The context path for Interactive Reporting, which is the part of the URL that accesses the deployed Web application. For example in the following URL, /workspace is the context path:

http://localhost:8080/workspace

Table 10

Apache IBM IIS

WebSphere “Manually Deploying into WebSphere 5.1.1.7” on page 161

“Manually Deploying into WebSphere 5.1.1.7” on page 161

Web Logic “Configuring Apache with BEA WebLogic” on page 116

“Configuring Microsoft IIS 5/6 with WebLogic 8/9” on page 121

Oracle 10g

Completing Module-Specific Configurations 73

Specifying the GSM Host and Port GSM and LSM track the services of the system and, when a client makes a request, they provide the client with a service. They perform load-balancing when dispatching services to clients. The GSM also holds the system configuration information and periodically checks all registered services to see if they are running. The system must have one and only one GSM. Every server process in the system must have one LSM (including the server process running the GSM); a server processor cannot have multiple LSMs.

The Global Service Manager (GSM) Host and Port Configuration displays when you run the UIservices installer.

Customizing Service Ports for Reporting and AnalysisThe Customizing Service Ports for Configuration dialog affords you the ability to view and modify the ports used by all installed Reporting and Analysis components.

Configuring the Production Reporting Engine for Interactive ReportingWhen you run Configuration Utility for the services CD, the Configure Production Reporting Engine dialog box displays.

➤ To configure Production Reporting engine for Interactive Reporting:

1 To configure Production Reporting engine for Interactive Reporting enable Select whether you want to configure Production Reporting engine.

2 In the Enter Production Reporting binary folder according to the chosen repository type field, enter one of the following Production Reporting binary folders:

● Oracle: <ProdReport_HOME>/Server/Oracle/bin

● MS SQL: <ProdReport_HOME>/Server/ODBC/bin

● IBM DB2: <ProdReport_HOME>/Server/DB2/bin

where <ProdReport_HOME> is the default location for Production Reporting. For example:

...<BIPLUS_HOME>\bin\SQR

3 For MS SQL: Enter MS SQL client home.

4 In Enter repository connection string, enter one of the following repository connection strings used to establish database connection by the native database client:

● Oracle: TNS name

● MS SQL: ODBC

● IBM DB2: Database alias registered by Client Configuration Assistant

Completing Financial Reporting Configurations● “Enabling the Planning ADM Driver” on page 74

● “Report Server Configuration” on page 75


● “Print Service Configuration” on page 74

● “Workspace, Print Service, and Scheduler Service Configurations” on page 75

Enabling the Planning ADM Driver The Planning ADM Driver displays when you run the Configuration Utility for the following installers:

● ServicesCD to configure the Financial Reporting server

● UIServicesCD to configure Financial Reporting

To enable Hyperion Planning Details:

● If version 4.0.1 of the Planning ADM Driver is not found on the system, the Planning Details displays with the following text field:

Enable Planning Details, which will configure version 4.1, automatically

● If the version 4.0.1 of the Planning ADM Driver is found on the system, the following fields are displayed:

Enable Planning Details:

Version 4.1

Version 4.0.1

If Version 4.0.1 is used, then enter the following:

Location of Planning Configuration Property file

Caution! The Planning ADM driver does not automatically download the HspJSHome.properties file. To work around this, download the properties file using the Shared Services Configuration Tool or manually copy the properties file to the classpath location on the local server, <BIPLUS_HOME>\lib folder.

Print Service ConfigurationThe Financial Reporting Print Server Configuration displays when you run the Configuration Utility on a machine where the Financial Reporting Print Service component is installed.

Select a Print Service configurations:

● Adobe Acrobat Distiller

● GNU Ghostscript or AFPL Ghostscript

● None of the above. Do not generate PDFs

Configuration Troubleshooting 75

Workspace, Print Service, and Scheduler Service ConfigurationsTo configure the Financial Reporting Workspace Web application, Print service, and Scheduler service, enter the following locations:

● Workspace Web Applications

● Financial Reporting Print Service Location(s)

● Financial Reporting Scheduler Service

Note: To enter multiple Print Service locations, enter the machines, separated by commas.

Report Server ConfigurationThe Financial Reporting Server Configuration displays when you run the UIservices Configuration Utility to configure the Financial Reporting Web component.

Enter the location of the Financial Reporting Server Location.

Completing Configuration UtilityDepending on the components selected for configuration, the Configuration Utility may take some time to complete. Progress is logged to <HYPERION_HOME>\common\config\logs\configtool.log

When the deployment process finishes, a summary displays the completed tasks with a finished status.

Note: If you experience problems with configuration, as a troubleshooting measure, perform configuration tasks individually for one module at a time.

Configuration TroubleshootingBecause the Configuration Utility separates configuration from product installation, the task of tracking and correcting configuration errors is simplified. The Configuration Utility logs configuration errors and warning messages to a log file, configtool.log, in a central location:

<HYPERION_HOME>\common\config\logs

Note: If you experience problems with configuration, as a troubleshooting measure, perform configuration tasks individually for one product at a time.


Post Configuration Tasks

Verifying Startup Dependencies

Note: Before performing these steps you should have registered with the Shared Services Server during the Reporting and Analysis configuration process.

Reporting and Analysis services are installed by default as manual services, with an optional automatic setting. Before starting Reporting and Analysis, you must verify that these dependent software components are running:

Note: These software components must be started in this order. Each must be running prior to starting the subsequent component.

Component How to Verify Successful Startup How to Start

Shared Services server On the Shared Services server computer, look for confirmation messages in the server console window or launch User Management Console. See “Verifying Successful Startup of Shared Services” on page 78.

See “Starting Shared Services” on page 77.

Workspace Service Open the Url:

http:/server:port/workspace

Use the services panel orRun startworkspace.bat from: <BIPlus_Home>\AppServer\InstalledApps\Appserver>\<VERSION>\Workspace\bin\

Interactive Reporting Core Services

Navigate to:

<BIPLUS_HOME>\logs.

Check in stdout_console.log for the message: “Giving control to the ORB to process the requests.”

Start > Programs > Hyperion System 9 BI + > Core Services Utilities and Administration >Start Reporting and Analysis or

Run

<BIPLUS_HOME>\bin\startCommonServices.bat

Interactive Reporting Service

Navigate to:

<BIPLUS_HOME>\logs.

Check BI_PM1_BIProcessMonitor.log for the message: “The service’s current status is AVAILABLE”.

Start > Programs > Hyperion System 9 BI + > Utilities and Administration > Start Interactive Reporting Service, or

Run

<BIPLUS_HOME>\bin\startIntelligenceService.bat

Interactive Reporting Data Access Service

Navigate to:

<BIPLUS_HOME>\logs.

Check DAS-server_messages_DASProcessMonitor.log

for the message: “The service’s current status is AVAILABLE”.

Start > Programs > Hyperion System 9 BI + > Utilities and Administration > Start Interactive Reporting DAS Service, or

Run

<BIPLUS_HOME>\bin\startDataAccessService.bat

Post Configuration Tasks 77

Starting Shared ServicesThis section describes how to start Shared Services if you did not deploy the Shared Services application server as a Windows service. If you deployed the Shared Services application server as a service, start the service manually from Windows control panel.

To start the Shared Services server, take one of the following actions:

● Select Start > Programs > Hyperion System 9 Foundation > Start Shared Services.

● Execute the startup script for a server:

Financial Reporting Servers Navigate to <BIPLUS_HOME>\logs and check for the “Started successfully...” messages:

● Financial Reporting Communication Server-FRCommSrv.log

● Financial Reporting Print Server-FRPrintSrv.log

● Financial Reporting Server-FRReportSrv.log

● Financial Reporting Scheduler Server–FRSchedSrv.log

● Financial Reporting Web-FRWebApp.log

If present and no error messages exist, the services are started.

Use the services panel, or

Bring up Financial Reporting services:

<BIPLUS_HOME>\bin\freporting {start|stop|restart} for the RMI components(Report Server, Scheduler Server, Communication Server).

Web Analysis Service Open the URL:

http://server:port/WebAnalysis.

Use the services panel orRun startwebanalysis.bat from: <BIPlus_Home>\AppServer\InstalledApps\Appserver>\<VERSION>\WebAnalysis\bin

Application Server Path to Script

IBM WebSphere <HSS_HOME>\AppServer\InstalledApps\<AppServName>\<version>\SharedServices9\bin\startSharedServices9.bat

BEA WebLogic <HSS_HOME>\AppServer\InstalledApps\<AppServName>\<version>\SharedServices9\startSharedServices.bat

Oracle <OracleInstallDir>\bin\emctl start iasconsole

<OracleInstallDir>\opmn\bin\opmnctl startall

Apache Tomcat <HSS_HOME>\AppServer\InstalledApps\<AppServName>\<version>\SharedServices9\

bin\startSharedServices9.bat

Note: <HSS_HOME> is the directory where Shared Services is installed; for example, c:\hyperion\SharedServices\9.2.

Component How to Verify Successful Startup How to Start


Verifying Successful Startup of Shared Services

➤ To verify successful startup and configuration of Shared Services:

1 Look for the following confirmation messages in the Share Services console window during startup:

● Database Configuration Test Passed

● Security System Initialized Successfully

● Shared Services Initialized Successfully

When Shared Services is deployed to WebSphere, these confirmation messages are logged to the following file:

<WebSphereInstallDir>\AppServer\logs\SharedServices9\SystemOut.log

When Shared Services is deployed to WebLogic, these confirmation messages are logged to the following file, unless the log level is set to WARN:

<HSS_HOME>\AppServer\InstalledApps\WebLogic\8.1vSharedServices9\ logs\SharedServices_Metadata.log

2 On the Shared Services server computer, launch the User Management Console login page using one of these methods:

● Select Start > Programs > Hyperion System 9 Foundation > User Management Console.

● Open a browser and enter this URL:

http://server:port/interop/

where server is the name of the computer where the Shared Services Server is installed and port is the Shared Services Server port number. The default port number is 58080; if Shared Services Server is installed to a non-default port, specify that value. For example, using the default port:

http://jdoe:58080/interop/

Note: As a best practice when accessing User Management Console on the machine where the Shared Services Server is running, the URL to access the console should always use an IP address or a fully qualified machine name that includes the domain name. If the IP address is dynamic, use the fully qualified machine name.

If the User Management Console login page is displayed, Shared Services server is started successfully.

Provision a Reporting and Analysis Administrator User

➤ To provision a Reporting and Analysis Administrator for login testing:

1 Log on to Shared Services. For example:

http://server:port/interop/

Enter the username and password. The default is admin and password.

Post Configuration Tasks 79

2 Select a user or create one.

3 Right-click on the user and select Provision.

4 Expand Roles for Reporting and Analysis.

5 Select Reporting and Analysis Global Administrator and Reporting and Analysis Administrator.

6 Click Save.

Adding Drivers for Web Analysis RDBMS ConnectivityThe support drivers for the Web Analysis' relational data source connectivity are the native RDBMS drivers. For example: Microsoft's JDBC driver, Oracle's JDBC driver and IBM's DB2 JDBC driver. This native driver must be manually added to the Web Analysis WEB_INF\lib folder.

➤ To configure the application server to use SQL grid connectivity drivers, navigate to the following folder:

<BIPLUS_HOME>\BIPlus\InstallableApps\WebAnalysis.war\WEB-INF\lib

and add the JDBC driver. For example: Microsoft, Oracle, IBM DB2.

Note: If using WebSphere Application Server, navigate to the following folder: <WAS_HOME>\installedApps\<HOST>\WebAnalaysis.ear\WebAnalysis.war\WEB-INF\lib

Launching Reporting and Analysis Modules

➤ To start the Reporting and Analysis Web Components:

1 Start the Shared Services before launching one of the Reporting and Analysis modules:

Enter the Shared Services URL:

http://<server>:<port>/interop/

where < server> is the name of your Shared Services server.

The default username and password are: Admin and password.

2 Test the connectivity to your newly deployed Reporting and Analysis application(s) by opening the following URLs:

http://<server>:<port>/workspace/—main logon URL where the default port is 19000.http://<server>:<port>/hr/—for verifying successful startup,where the default port is 8200http://<server>:<port>/WebAnalysis/—for verifying a successful startup


Changing the Apache HTTP Server Listen Port

➤ To change the Apache Listen Port:

1 Open http.conf and add a Listen directive: <HYPERION_HOME>/common/httpServers/Apache/2.0.52/conf/httpd.conf.

2 Locate:

Listen 19000

3 Do one of the following:

● To make Reporting and Analysis accessible on another port, change the port number.

● To make Reporting and Analysis accessible on 2 ports, add a second Listen directive. For example:

Listen 19000 Listen 80

After configuration, see Hyperion Workspace Administrator’s Guide.

ReconfigurationThe Configuration Utility enables you to reconfigure Hyperion products multiple times. Reconfiguration procedures are identical to the initial configuration procedures. Launch the Configuration Utility, select the products to reconfigure, and repeat the procedures. Select the options that you want to change and follow the prompts to enter the required information.

Product activation is not required when you reconfigure.

Uninstalling Reporting and Analysis 81

C h a p t e r

6Uninstalling Reporting and

Analysis

In This Appendix Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

Uninstalling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

82 Uninstalling Reporting and Analysis

PrerequisitesBefore you perform an uninstall:

● Stop Reporting and Analysis.

● Manually stop all services either by the control panel, closing the DOS window, or running a stop script. Services include: Open Ldap, Apache, Shared Services, Reporting and Analysis Web applications, Workspace, Financial Reporting, and Interactive Reporting.

Uninstalling

Caution! During uninstall, the Reporting and Analysis directory is deleted.

➤ To uninstall Reporting and Analysis:

1 Start the Uninstall wizard by one of the following means:

● Use the Start menu:

i. Select Start > Setting > Control Panel > Add or Remove Programs.

ii. Click Change/Remove to initiate the uninstall for:

❑ Hyperion System 9 Reporting and Analysis Services

❑ Hyperion System 9 Reporting and Analysis UIServices

❑ Hyperion System 9 Reporting and Analysis RepServices

❑ Hyperion System 9 Reporting and Analysis Migration Utility

❑ Hyperion System 9 Reporting and Analysis Client

● Run uninstall.exe, by browsing to the following locations:

Note: When you run the UIServices uninstall, Application Servers will undeploy.

<BIPLUS_HOME>\uninstallClient\

<BIPLUS_HOME>\uninstallServices\

<BIPLUS_HOME>\uninstallUIServices\

<BIPLUS_HOME>\uninstallRepServices\

<HYPERION_HOME>\Migration Utility\uninstall\

The wizard Language screen displays.

2 Select the country where you are uninstalling the software, and click Next.

3 When the Welcome screen displays, click Next.

The Summary screen displays.

Uninstalling 83

4 Verify programs you want uninstalled, and click Next.

5 When the wizard finishes the uninstall, click Finish.

6 Verify that Reporting and Analysis directories are deleted.

7 If uninstalling all Hyperion products, rename C:\WINDOWS\vpd.properties.

8 Remove files from the registry:

a. Start the Registry Editor up by clicking Start > Run.

b. Type regedit.

9 Optionally, remove the following Registry entries:

Keys\ Sub-keys Remove values

HKEY_CURRENT_USER\

Software\ Folders:

● Brio Software

● Interactive brioqry

● SQR Developer entries

Software\Microsoft\WindowsNT

\CurrentVersion\PrinterPorts

HR*

HKEY_LOCAL_MACHINE\

SOFTWARE\Brio Software Entries pertaining to:

● Interactive Reporting Studio

● SQR Developer

SOFTWARE\Hyperion Solutions Financial Reporting (HR) server install items:

● Hyperion Reports\HRCommSrv

● Hyperion Reports\HReports

● Hyperion Reports\HReports\JVM

● HRPrintSrv

● Hyperion Reports\HRReportSrv

● Hyperion Reports\HRSchedSrv

All entries pertaining to:

● Dashboard Development Services

● Hyperion Intelligence Architect

● Hyperion Intelligence Dashboard builder

● Hyperion Reports

● Interactive Reporting Studio

SOFTWARE\Hyperion Solutions\InstalledComponents HR*

SOFTWARE\Microsoft\Windows\CurrentVersion Selectively remove unused SharedDLL entries related to ADM

SOFTWARE\Microsoft\Windows\CurrentVersion

\Uninstall\Hyperion System 9 Hyperion

84 Uninstalling Reporting and Analysis

10 Reboot your machine.

Note: Rebooting will remove ControlSet01 entries.

SOFTWARE\Microsoft\WindowsNT

\CurrentVersion\Print\Printers HR*

SYSTEM\CurrentControlSet\Control\Print

\Environments\Windows NT x86\Drivers\Version-3 Hyperion PS entries

SYSTEM\CurrentControlSet\Control\Print\Printers HR*

SYSTEM\CurrentControlSet\Services ● HR*

● Hyperion Interactive Reporting*

● Hyperion Financial Reporting*

● Hyperion WebAnalysis*

HKEY_USERS\

.DEFAULT\Software\Microsoft\WindowsNT\CurrentVersion

\Devices HR*

Keys\ Sub-keys Remove values

Upgrading to Reporting and Analysis 9.2.1 85

C h a p t e r

7Upgrading to Reporting and

Analysis 9.2.1

In This Chapter Upgrading from 8.x to 9.2.1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

Upgrading from 9.x to 9.2.1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

Note: All products in release 9.2.1 (Data Integration Management excepted) support upgrades from 8.x, 9.0.1x and 9.2.

86 Upgrading to Reporting and Analysis 9.2.1

Upgrading from 8.x to 9.2.1To upgrade from 8.x to 9.2.1, use the Hyperion Reporting and Analysis Migration Utility. For detailed information, see the Hyperion Reporting and Analysis Migration Utility Guide.

Upgrading from 9.x to 9.2.1

Note: The steps in this section cover upgrades from both 9.0.1.x and 9.2.

Prerequisites● Stop the following components:

❍ Reporting and Analysis

❍ Application server and HTTP server

● Delete JSP class files from previous Application Server deployments

● Perform a full backup of your installation:

❍ Backup Interactive Reporting and Shared Services database repositories

❍ Make a copy of C:\windows\vpd.properties

❍ Backup <HPERION_HOME> and <BIPLUS_HOME> folders.

● Upgrade Shared Services - Install in the same location as the previous release. In order not to recreate database repository click Reuse the existing repository during Shared Services Relational Storage configuration task.

Upgrading

➤ To upgrade:

1 Upgrade Reporting and Analysis components:

a. Launch services installers which were installed on the previous installation:

❍ ServicesCD

❍ UIServicesCD

❍ ClientCD

❍ RepServicesCD

Note: Be sure that during installing services you select items under the existing list (not new installation)

Each installer displays the Summary window with a list of components to upgrade.

b. Complete the installation by clicking Finish.

Upgrading from 9.x to 9.2.1 87

2 After installing:

a. Verify that <HYPERION_HOME>\common\config\product\biplus\9.2.0.3 contains:

<product_name>_<product_number>.properties <product_name>_<product_number>.xml

For example:

biplus_1.properties and biplus_1.xml

b. Verify that <product_name>_<product_number>.xml (for example: biplus_1.xml) contains installType with the following properties:

❍ value="UPGRADE",

❍ originalVersion="<full_product_version>"

❍ complete="true"—If complete= "false", the upgrade is incomplete; upgrade all components again and recheck <product_name>_<product_number>.xml.

3 Launch the Configuration Utility to configure upgraded Reporting and Analysis modules:

You can use the Configuration Utility to configure modules from this release or from the previous release (9.0.0). The Configuration Utility determines whether the products installed on the machine are new or upgraded. The product selection page indicates which modules are upgraded.

Configure upgraded modules one at a time because each product may be configured for a different database. Likewise, you cannot configure new products and upgraded products simultaneously.

Perform all configuration tasks.

4 In the Database Configuration window, enter the database password.

88 Upgrading to Reporting and Analysis 9.2.1

Installing the Reporting and Analysis Migration Utility 89

C h a p t e r

8Installing the Reporting and

Analysis Migration Utility

In This Chapter Migration Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

Installing the Migration Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

After Installing the Migration Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

90 Installing the Reporting and Analysis Migration Utility

Migration UtilityMigration is conducted after the Reporting and Analysis installation is completed and the file system and repository contents have been backed up but before new content is added into the repository. The Migration Utility is installed on a machine that has visibility to the source and target systems, including source and target repository databases.

The Migration Utility is a wizard-based utility that guides Hyperion Reports, Hyperion Analyzer, and Hyperion Performance Suite customers to migrate to the Reporting and Analysis. The Migration Utility supports:

● Migration from:

❍ Hyperion Intelligence 6.6.4 (OnDemand Server 6.6.4 or later and Broadcast Server 6.6.4 or later)

❍ Brio Portal 7.0.5

❍ BrioONE (Brio POrtal 7.0.5 or later and OnDemand 6.6.4 or later)

❍ Hyperion Reports 7.0, 7.0.1, 7.2, 7.2.1

❍ Hyperion Analyzer 6.5, 7.0, 7.0.1, 7.2, 7.2.1

❍ Hyperion Performance Suite 8.x

❍ Localized environments. Migrating legacy version from non-US (United States) operating systems. (Log messages are not localized.)

● Transition to User Provisioning as part of Migration

● Phased migration (migrating groups first, followed by users, folders, etc.)

● Cross platform and cross database migration

Note: For non-supported deployments, you must upgrade to the versions above.

When migration to the to Reporting and Analysis release is completed, user / group / role information is seamlessly migrated through a Provisioning module.

RequirementsSource and target system requirements:

● Disk space—200 MB

● RAM—256 MB

● Reporting and Analysis Software Requirements. See “Software Requirements” on page 27.

Installing the Migration Utility 91

Supported Source Databases

Installing the Migration Utility

➤ To install the Hyperion Migration Utility:

1 Download the Hyperion Migration Utility file for your platform from the Oracle® E-Delivery site to a temporary directory.

2 Double-click the ZIP file to decompress it.

3 Close all Reporting and Analysis programs.

4 Launch the installation setup file setupwinPlatform.exe.

5 The Reporting and Analysis splash screen is displayed.

6 Click Next.

The Country Location is displayed.

7 Select the country’s location describing where the Migration Utility is, and click Next.

8 Read the License Agreement, select I ACCEPT, and click Next.

9 The directory path for the installation is displayed. Click Next to accept the location, or click Browse to select a new location.

10 The installer searches for the Hyperion Home setting and displays the directory name, if detected. Click Next to accept the location, or click Browse to select a new Hyperion Home location.

11 The Summary displays the installation location and size. Click Next. A progress box is displayed.

12 When the installation is complete, the Install Shield informs you whether the installation was successful.

13 Click Finish.

Table 11 Supported Source Databases for each Reporting and Analysis Modules:

Database:Reporting and Analysis Brio Portal Reports Analyzer HPSu SQR

SQL Server X X X X X X

Oracle X X X X X X

DB2 X X X X X X

Sybase X X X

Informix X X X

Redbrick X X

Teradata X X X X

SAP BW X X X X X

SAP R/3 X X X

92 Installing the Reporting and Analysis Migration Utility

14 To verify the installation:

● Run the migrator.bat file in the folder where you installed the Migration Utility.

For example: <HYPERION_HOME>\migrator\bin.

● Select Start > Hyperion System 9 Reporting and Analysis > Utilities and Administration > Migration Utility.

After Installing the Migration UtilityThe Hyperion Migration Utility:

● Creates a directory structure, by default:

<HYPERION_HOME>\Migration Utility

● Adds migration utility entries to the Windows Registry.

● Copies program files, scripts, and documentation to:

Directory Structure Description

bin Contains INI files and executables for the Migration Utility

conf Contains the db_defaults.properties and Migration.properties files

help Contains help files

lib Contains the Migration JAR files

log Contains the file generated by installing the Migration Utility. Also describe each change that made for migration.

uninstall Contains the uninstall.exe file.

Manually Deploying into Oracle 10g Release 3 (10.1.3.1.0) 93

A P P E N D I X Z

AManually Deploying into Oracle

10g Release 3 (10.1.3.1.0)

In This Appendix Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

Deploying Workspace Web Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

Deploying Financial Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

Deploying Web Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

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

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

Testing Module Availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110

94 Manually Deploying into Oracle 10g Release 3 (10.1.3.1.0)

Prerequisites● Shared Services

❍ Install Shared Services.

❍ Verify that it is up and running.

❍ Test the installation and make sure that you can log into Shared Services:

http://<server>:<port>/interop/index.jsp

For example:

http://localhost:58080/interop/index.jsp

● Install Reporting and Analysis UI Services.

It is required that you run the Hyperion Configuration Utility and select both the Deploy to Application Server and Configure Web Server tasks. If these options are not selected, you must re-run Hyperion Configuration Utility.

You need at least 1 GB available disk space in the temporary path before deploying.

Note: Enterprise Manager Web Console of Oracle Application Server will be used for deployment. Be sure to select “Configure this as an Administrator OC4J instance” during OAS installation – otherwise the Enterprise Manager Web Console will be unavailable.

Deploying Workspace Web ApplicationTo prevent all deployed applications from inheriting JVM runtime settings that pertain only to Workspace, it is recommended that a new OC4J instance be created.

Creating an OC4J Instance

Note: If you choose to deploy the Web Application to an existing OC4J instance, skip this section.

To create an OC4J instance, use Oracle Enterprise Manager Web console, which provides Web-based management tools for Oracle 10g Application Server.

➤ To create an OC4J instance:

1 Log in to the Oracle Enterprise Manager’s 10g Web console via:

http://<servername>:<port>/em

where <servername> is the hostname or IP address of the machine where the Oracle 10g Application Server Management Service is running, and <port> is the Management Service listen port provided after the Application Server installation.

Note: The default login ID is oc4jadmin. The password is specified during the Oracle 10g Application Server installation. Contact your Oracle Administrator for more information.

Deploying Workspace Web Application 95

2 Within the Application Server Control instance, click the instance link.

3 Click the Create OC4J instance.

4 In the Create OC4J Instance Page, in the OC4J Instance, type Workspace, then do one of the following:

● Select Add to a new group... and enter the group name; for example: BIPlus.

● Select which group of OC4J instances it will join; for example, BIPlus.

5 Select Start this OC4J instance after creation check and click Create.

Configuring an OC4J Instance

➤ To configure OC4J instance properties:

1 On the Oracle Enterprise Manager’s 10g Web site, navigate to OC4J > Workspace > Administration and select Server Properties.

Note: The Workspace OC4J instance must be started before it can be configured.

2 In Server Properties, under Command Line Options:

● Append the following Java Option:

-DHYPERION_HOME=<HYPERION_HOME>

where <HYPERION_HOME> is the directory the Hyperion common files were installed.

● Change maximum heap size to 512m, and initial heap size to 256m to accommodate your server.

Note: The size of the OC4J instance heap must be increased in order to successfully deploy the Workspace application.

3 Click Apply and restart the OC4J instance.

Deploying workspace.war

➤ To deploy:

1 On the Oracle Enterprise Manager’s 10g Web console, navigate to Workspace > Applications and click Deploy.

2 Supply the absolute location to workspace.war to Archive Location by selecting one of the following:

● Archive is present on the local machine...

● Archive is on the same machine...

and entering:

<BIPLUS_HOME>\InstallableApps\workspace.war

by default, in J2EE Application.


Note: If the Web browser used to deploy the workspace.war archive is not on the same machine where Reporting and Analysis was installed, you must copy Location on Server.

3 Click Next to create a new deployment plan.

4 In Application Name, type Workspace and change the context-root value to workspace.

5 Click Next.

6 Click Deploy.

7 After successful deployment, click Return.

8 Select the Workspace OC4J instance and then click Restart.

Configuring Workspace

Enabling SAP as an Authentication ProviderIf Shared Services is configured to provide SAP authentication, Workspace must have the SAP Java and Native libraries added to its OC4J environment.

➤ To add SAP to Workspace OC4J environment:

1 With a text editor, open:

<DEPLOYED_LOCATION>\Workspace\application-deployments\Workspace\ workspace\orion-web.xml

where <DEPLOYED_LOCATION> is the file-system path to where the Web archive was expanded; for example <ORACLE_HOME>/j2ee

2 Add the following entry before the last line (</orion-web-app>), substituting <HYPERION_HOME> with the actual file-system directory:

<classpath path="<HYPERION_HOME>/common/SAP/lib"/>

where <HYPERION_HOME> is the directory the Hyperion common files were installed.

3 Save and close the file.

4 On the Oracle Enterprise Manager 10g Web site, navigate to Workspace > Administration and drill down to Server Properties.

5 Add an Environment Variable called PATH and assign the value, substituting <HYPERION_HOME> with the actual file-system directory:

<HYPERION_HOME>\common\SAP\bin

6 Select Append for the PATH definition.

Deploying Workspace Web Application 97

Creating context.properties

➤ To create context.properties:

1 With a text editor, create:

<DEPLOYED_LOCATION>\Workspace\applications\Workspace\workspace\conf \context.properties

where <Deployed_Location> is the default OAS home. For example:

<OAS_Home>\10.1.3.1\OracleAS_1\j2ee\Workspace\applications\Workspace \workspace

2 Add the following values:

Set “Y” if components have been installed, “N” if components have not been installed:

Reports=YHPSU=YHPS=NHMB=NChangeManagement=YAnalyzer=Y

Note: Leave both HPSU and ChangeManagement entry values as ‘Y’.

Assign an appropriate Y or N to each value in accordance with the Reporting and Analysis modules you have installed:

● Financial Reporting (Reports)

● Interactive Reporting (HPSU)

● Performance Scorecard (HPS)

● Dashboard Development Services (ChangeManagement)

● Web Analysis (Analyzer)

3 Click Start or Restart Workspace OC4J instance.

Update Oracle HTTP Server Routing for WorkspaceYou need to update the Oracle HTTP Server (OHS) to make static content, online Help, available.

➤ To update OHS Routing for Workspace:

1 Open:

<DEPLOYED_LOCATION>\Workspace\config\default-web-site.xml

where <Deployed_Location> is the default OAS home.

For example:

<OAS_Home>\10.1.3.1\OracleAS_1\j2ee\


2 Check that the following property for Workspace application is added:

ohs-routing="false"

For example:

<web-app application="Workspace" name="workspace" load-on-startup="true" root="/workspace" ohs-routing="false" />

Updating Configuration Files

➤ To update configuration files:

1 Edit:

<BIPLUS_HOME>\bin\config.bat

a. In the line:

DEPLOYMENT_PATH=$J(servletConfig.deploymentPath)

replace $J(servletConfig.deploymentPath) with the actual location of deployed Workspace

The default is:

<DEPLOYED_LOCATION>\Workspace\applications\Workspace\workspace


For example:


2 Edit:

<BIPLUS_HOME>\bin\settrustedpass.bat

a. In the line:

BRIO_LIB=$J(trustedPass.installLib)

replace $J(trustedPass.installLib)with your actual <BIPLUS_HOME>\lib location.

For example:

c:\Hyperion\BIPlus\lib

b. In the line:

DEPLOYMENT_HOME=$J(trustedPass.deploymentHome)

replace $J(trustedPass.deploymentHome) with the actual location of deployed Workspace application.

The default is:

<DEPLOYED_LOCATION>\Workspace\applications\Workspace\workspace


For example:


Deploying Financial Reporting 99

Deploying Financial ReportingTo prevent all deployed applications from inheriting JVM runtime settings that pertain only to Financial Reporting, it is recommended that a new OC4J instance be created.




➤ To create a OC4J instance:


http://<servername>:<port>/em



2 Within Application Server Control instance click on the instance link.

3 Click Create OC4J Instance.

4 In the Create OC4J Instance Page, in OC4J Instance, type FinancialReporting, then determine which group of OC4J instances it will join; for example, BIPlus.

5 Select Start this OC4J instance after creation and click Create.



1 In the Oracle Enterprise Manager’s 10g Web site, navigate to OC4J > Financial Reporting > Administration and click Server Properties.

Note: The FinancialReporting OC4J instance must be started before it can be configured.


2 In Server Properties:

a. Under Command Line Options, change:

Maximum heap size to 512mInitial heap size to 256m

Note: The size of the OC4J instance heap must be increased in order to successfully deploy the Financial Reporting application.

b. Remove the -Djava.awt.headless=true property in two places:

❍ Options

❍ Stop-parameters:Java Options

c. Under Options, add the following properties, substituting values in <> with actual locations:

-DHYPERION_HOME=<HYPERION_HOME>-DBIPLUS_HOME=<BIPLUS_HOME>-DADM_HP_LIB=<PLANNING_ADM_LOCATION>-XX:PermSize=64m-XX:MaxPermSize=128m

for example:

-DHYPERION_HOME=C:\Hyperion-DBIPLUS_HOME=C:\Hyperion\BIPlus-DADM_HP_LIB=C:\Hyperion\ADM\Planning\9.2.0\lib-XX:PermSize=64m-XX:MaxPermSize=128m

Note: Define -DADM_HP_LIB entries, even if Planning is absent in your environment; for example: -DADM_HP_LIB=

3 Under Environment Variables, add the following, substituting values in <> with actual locations:

HYPERION_HOME <HYPERION_HOME>ESSLANG <ESSLANG>BIPLUS_HOME <BIPLUS_HOME>ARBORPATH <HYPERION_HOME>\common\EssbaseRTC\9.2.1PATH <HYPERION_HOME>\common\ADM\Planning\9.2.0\bin; <HYPERION_HOME>\common\ADM\9.2.0\Essbase\9.2.0\bin; <HYPERION_HOME>\common\EssbaseRTC\9.2.1\bin; <HYPERION_HOME>\common\SAP\bin

for example:

HYPERION_HOME C:\HyperionESSLANG English_UnitedStates.Latin1@BinaryBIPLUS_HOME C:\Hyperion\BIPlusARBORPATH C:\Hyperion\common\EssbaseRTC\9.2.1ESS_ES_HOME C:\Hyperion\BIPlus\bin\EssbaseJAPIPATH C:\Hyperion\common\ADM\Planning\9.2.0\bin; C:\Hyperion\common\ADM\9.2.0\Essbase\9.2.0\bin; C:\Hyperion\common\EssbaseRTC\9.2.1\bin; C:\Hyperion\common\SAP\bin


Deploying Web Analysis 101

Deploying HReports.ear

➤ To deploy HReports.ear:

1 On the Oracle Enterprise Manager's 10g Web Console, navigate to OC4J > FinancialReporting > Applications.

2 Click Deploy.

3 Supply the absolute location to HReports.ear to Archive Location:

<BIPLUS_HOME>\InstallableApps\HReports.ear

by default, keep the Archive type in J2EE Application.

For example:

c:\Hyperion\BIPlus\InstallableApps\HReports.ear

Note: If the Web browser used to deploy the HReports.ear archive is not on the same machine where Reporting and Analysis was installed, you must use copy Location on Server.


5 In Application Name, type FinancialReporting and click Next.

6 Click Deploy.

7 After successful deployment, restart the FinancialReporting OC4J instance.

Deploying Web AnalysisTo prevent all deployed applications from inheriting JVM runtime settings that pertain only to Web Analysis, it is recommended that a new OC4J instance be created.




➤ To create an OC4J instance:


http://<servername>:<port>




2 Within Application Server Control instance, click the instance link.

3 Click Create OC4J instance.

4 In the Create OC4J Instance page, in OC4J Instance, type WebAnalysis, then determine which group of OC4J instances it will join; for example, BIPlus.

5 Select Start this OC4J instance after creation and click Create.



1 On the Oracle Enterprise Manager’s 10g Web console, navigate to OC4J > WebAnalysis > Administration and select Server Properties.

Note: The WebAnalysis OC4J instance must be started before it can be configured.

2 In Server Properties:

a. Under Command Line Options, change:

Maximum heap size to 512mInitial heap size to 256m

Note: The size of the OC4J instance heap must be increased in order to successfully deploy the Web Analysis application.

b. Remove the -Djava.awt.headless=true property in two places:

❍ Options

❍ Stop-parameters:Java Options

c. Under Options, add the following properties, substituting values in <> with actual locations:

-DHYPERION_HOME=<HYPERION_HOME>-DBIPLUS_HOME=<BIPLUS_HOME>-XX:PermSize=64m-XX:MaxPermSize=128m

For example:

-DHYPERION_HOME=C:\Hyperion-DBIPLUS_HOME=C:\Hyperion\BIPlus-XX:PermSize=64m-XX:MaxPermSize=128m


3 Under Environment Variables, add the following, substituting <> with actual locations:

ESSLANG <ESSLANG>HYPERION_HOME <HYPERION_HOME>ARBORPATH <HYPERION_HOME>\common\EssbaseRTC\9.2.1BIPLUS_HOME <BIPLUS_HOME>ICU_DATA <HYPERION_HOME>\common\ADM\9.2.0\Essbase\9.2.0\bin\ HssEssDriverPATH <HYPERION_HOME>\common\ADM\9.2.0\Essbase\9.2.0 \bin;<HYPERION_HOME>\common\EssbaseRTC\9.2.1\bin; <HYPERION_HOME>\common\SAP\bin

where <HYPERION_HOME> and <BIPLUS_HOME> are real path values.

For example:

ESSLANG English_UnitedStates.Latin1@BinaryHYPERION_HOME C:\HyperionARBORPATH C:\Hyperion\common\EssbaseRTC\9.2.1BIPLUS_HOME C:\Hyperion\BIPlusICU_DATA C:\Hyperion\common\ADM\9.2.0\Essbase\9.2.0\bin\ HssEssDriverPATH C:\Hyperion\common\ADM\9.2.1\Essbase\9.2.0\bin; C:\Hyperion\common\EssbaseRTC\9.2.1\bin; C:\Hyperion\common\SAP\bin

Note: Select Append for PATH definition.


Deploying WebAnalysis.ear

➤ To deploy WebAnalysis.ear:

1 On the Oracle Enterprise Manager’s 10g Web console, navigate to OC4J > WebAnalysis > Applications.

2 Click Deploy.

3 Supply the absolute location to WebAnalysis.ear to Archive Location:

<BIPLUS_HOME>\InstallableApps\WebAnalysis.ear

by default, in J2EE Application.

Note: If the Web browser used to deploy the WebAnalysis.ear archive is not on the same machine where Reporting and Analysis was installed, you must use copy Location on Server.


5 In Application Name, type WebAnalysis and click Next.

6 Click Deploy.


Tip: For DB connectivity, copy appropriate JDBC drivers into <DEPLOYED_LOCATION>\WebAnalysis\applications\WebAnalysis\WebAnalysis\ WEB-INF\lib

Examples of JDBC drivers:

● DB2: db2java.zip, db2jcc.jar, db2jcc_license_cisuz.jar, db2jcc_license_cu.jarMS

● SQL: msbase.jar, mssqlserver.jar, msutil.jar

● Oracle: ojdbc14.jar

7 Click Apply.

8 After successful deployment, restart the WebAnalysis OC4J instance.

Configuring Oracle HTTP Server for Oracle 10g Release 3

➤ To properly route requests from Oracle HTTP Server to the OC4J instances created for Reporting and Analysis:

1 Stop HTTP_Server from Oracle Enterprise Manager 10g Web console.

2 Edit <OAS_HOME>\Apache\Apache\http.conf:

a. Modify Port and Listen directives with port number will be used for Reporting and Analysis ; 19000 by default.

Note: After this operation your Oracle Enterprise Manager 10g Web console will use new port settings too; for example, http://localhost:19000/em.

b. If browser clients using short hostname or hostname aliases will access your product, consider changing the value of UseCanonicalName to Off.

If you log on using a server name like:

http://becks:19000/workspace/

Oracle HTTP Server forces the URL to:

http://becks.hyperion.com:19000/workspace/

which causes JavaScript permission denied errors.

For more information on UseCanonicalName, see:

http://httpd.apache.org/docs/2.0/mod/core.html#usecanonicalname.

3 Add the following aliases, substituting values in <> with actual locations

● Workspace

Alias /workspace "<BIPLUS_HOME>\AppServer\InstalledApps\workspace_static"Alias /wsmedia "<BIPLUS_HOME>\AppServer\InstalledApps\workspace_static\wsmedia"

Configuring Oracle HTTP Server for Oracle 10g Release 3 105

Alias /InsightInstaller"<BIPLUS_HOME>\AppServer\InstalledApps\workspace_static\zeroadmin\component\Insight"

● Web Analysis

Alias /WebAnalysis "<BIPLUS_HOME>\AppServer\InstalledApps\WebAnalysis_static"

4 Open mod_oc4j.conf and create the following Oc4jMount directives for each Reporting and Analysis module you have deployed:

● Workspace

Oc4jMount /workspace/cdsrpc WorkspaceOc4jMount /workspace/administration/* WorkspaceOc4jMount /workspace/browse/* WorkspaceOc4jMount /workspace/personalpages/* WorkspaceOc4jMount /workspace/viewmanager/* WorkspaceOc4jMount /workspace/jobmanager/* WorkspaceOc4jMount /workspace/ihtml/* WorkspaceOc4jMount /workspace/dataaccess/* WorkspaceOc4jMount /workspace/logon WorkspaceOc4jMount /workspace/logon/* WorkspaceOc4jMount /workspace/js/* WorkspaceOc4jMount /workspace/modules/* WorkspaceOc4jMount /workspace/resources/* WorkspaceOc4jMount /workspace/conf/* WorkspaceOc4jMount /workspace/media/* WorkspaceOc4jMount /workspace/prefs WorkspaceOc4jMount /workspace/BPMContext WorkspaceOc4jMount /workspace/wsrp4j/* WorkspaceOc4jMount /workspace/ResourceProxy WorkspaceOc4jMount /workspace/ WorkspaceOc4jMount /workspace/*.jsp WorkspaceOc4jMount /workspace/*.jsv WorkspaceOc4jMount /workspace/*.jsw Workspace:


Oc4jMount /hr FinancialReportingOc4jMount /hr/* FinancialReportingOc4jMount /HReports FinancialReportingOc4jMount /HReports/* FinancialReporting

● Web Analysis

Oc4jMount /WebAnalysis/ServerConsole/* WebAnalysisOc4jMount /WebAnalysis/templates/* WebAnalysisOc4jMount /WebAnalysis/hfmtemplates/* WebAnalysisOc4jMount /WebAnalysis/hitemplates/* WebAnalysisOc4jMount /WebAnalysis/processor WebAnalysisOc4jMount /WebAnalysis/servlet/* WebAnalysisOc4jMount /WebAnalysis/modules/* WebAnalysisOc4jMount /WebAnalysis/resources/* WebAnalysisOc4jMount /WebAnalysis/DirectoryServlet WebAnalysisOc4jMount /WebAnalysis/config WebAnalysisOc4jMount /WebAnalysis/wa_javadocs/* WebAnalysisOc4jMount /WebAnalysis/ WebAnalysisOc4jMount /WebAnalysis/*.jsp WebAnalysisOc4jMount /WebAnalysis/*.xml WebAnalysisOc4jMount /WebAnalysis/*.jar WebAnalysisOc4jMount /WebAnalysis/*.exe WebAnalysis


5 Start the Oracle HTTP Server using opmnctl:

<OAS_HOME>\opmn\bin\opmnctl.exe startproc process-type=HTTP_Server

6 Verify that ConfigURL in the following location is referred onto the correct Oracle HTTP Server port:

<BIPLUS_HOME>\InstallableApps\config\WebAnalysis.properties

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

PrerequisitesOracle Application Server Infrastructure > Identity Management and Metadata Repository (OID, SSO, and metadata repository) should be installed.

Configuring the Oracle Application Server

➤ To configure Oracle Single Sign-On on Oracle 10g Release 3:

1 On the Identity Management host (where 10.1.3.1.0 is installed), set the ORACLE_HOME and ORACLE_SID environment variables.

2 On the Identity Management host, run the ssoreg script, using the -remote_midtier option. The file is located at:

ORACLE_HOME\sso\bin\ssoreg.bat

For example:

%ORACLE_HOME%\sso\bin\ssoreg.bat -oracle_home_path %ORACLE_HOME% -config_mod_osso TRUE -site_name BIPlus -remote_midtier -config_file %ORACLE_HOME%\Apache\Apache\conf\osso\myosso.conf -mod_osso_url http://myhost.domain.com:19000

3 Copy the obfuscated OSSO configuration file to the 10g Release 3 (10.1.3) middle-tier instance.

4 On the middle-tier host, run one of the following script to complete the registration:

● If you have Perl:

ORACLE_HOME\Apache\Apache\bin\osso1013 config_file

● If you do not have Perl:

a. Copy config_file into \ORACLE_HOME\Apache\Apache\conf\osso\osso.conf

b. Uncomment the following line in httpd.conf:

include '<ORACLE_HOME>\Apache\Apache\conf\mod_osso.conf'

c. Add the OssoConfigFile entry into mod_osso.conf file. Insert the following line into <IfModule mod_osso.c> directive:

OssoConfigFile "<ORACLE_HOME>\Apache\Apache\conf\osso\osso.conf"

Configuring Oracle Single Sign-on on Oracle 10g Release 3 107

For example:

OssoConfigFile 'C:\Oracle\Apache\Apache\conf\osso\osso.conf'

5 Update Identity Management properties for Workspace:

a. On the Oracle Enterprise Manager’s 10g Web site, navigate to OC4J > Workspace > Administration.

b. Select Identity Management Properties, and click Configure.

c. Enter the following information and click Next.

User: Fully qualified domain name of the OID host, cn=orcladmin

Password: User password

Port: Port value, by default: non-SSL 389.

d. Select Use Oracle Identity Management Security Provider, and click Next.

e. Select Use OID Security Provider and Enable SSO Authentication for Workspace and click Configure.

f. Restart Workspace.

6 Change Global Security Provider properties:

a. At the bottom of the Administration Console, select Global Setup.

b. Under Security Providers, select Change Security Provider.

c. In the Oracle Identity Management Security Provider, select Created and click OK.

7 Update Security Providers properties for Web Analysis:

a. On the Oracle Enterprise Manager’s 10g Web site, select OC4J > WebAnalysis > Administration, and select Security Providers Properties.

b. Select Edit for WebAnalysis Application Name.

c. Click Change Security Provider and select OIM Security Provider.

d. Select Enable SSO Authentication and click OK.

8 Update Security Providers properties for Financial Reporting:

a. On the Oracle Enterprise Manager’s 10g Web site, navigate to OC4J > Financial Reporting: > Administration and select Security Providers Properties.

b. Select Edit for FinancialReporting Application Name.

c. Click Change Security Provider and select OIM Security Provider.

d. Select Enable SSO Authentication and click OK.

9 Update:

ORACLE_HOME\Apache\Apache\conf\mod_osso.conf

and insert the following lines into <IfModule mod_osso.c>:

<Location /workspace> Require valid-user AuthType Basic order deny,allow


deny from all allow from <localhost>, < Identity Management host > satisfy any </Location> <Location /workspace/browse/configURL> Require valid-user AuthType Basic allow from all </Location> <Location /hr> Require valid-user AuthType Basic </Location> <Location /HReports> Require valid-user AuthType Basic </Location> <Location /WebAnalysis> Require valid-user AuthType Basic order deny,allow deny from all allow from <localhost>, <Identity Management host> satisfy any </Location>

10 Append the following lines to:

ORACLE_HOME\Apache\Apache\conf\httpd.conf

<Location /WebAnalysis/>OssoSendCacheHeaders off </Location> <Location /workspace/>OssoSendCacheHeaders off </Location> <Location /hr/>OssoSendCacheHeaders off </Location> <Location /HReports/>OssoSendCacheHeaders off </Location>

11 Update:

<BIPLUS_HOME>\InstallableApps\config\WebAnalysis.properties

a. Uncomment and set UseSecurityAgentTokenWithoutDomain to true.

b. Update SSOProviderSessionCookieID and set value to OHS-<hostname.domain.com>-<ora_http_port>

c. Uncomment and set UseRemoteUser to true.

12 Restart Hyperion Core Services.

13 Restart the Middle-Tier and Application Server instances:

ORACLE_HOME\opmn\bin\opmnctl stopallORACLE_HOME\opmn\bin\opmnctl startall

Configuring Oracle Single Sign-on on Oracle 10g Release 3 109

14 Setup the Workspace Web Application parameters:

a. Start Servlet Configurator:

<BIPLUS_HOME>\bin\config.bat

b. Navigate to Properties > User Interface > Login.

c. Set:

❍ Property Custom username policy to $REMOTE_USER$

❍ Custom password policy to $TRUSTEDPASS$

then select File > Save and File > E xit.

d. To change settrusted password value, run:

<BIPLUS_HOME>\bin\settrustedpass.bat

When prompted, supply default password 123456, then specify a new trusted password. This script will create a file called tp.conf containing the trusted password in the encrypted format. The file should be automatically copied to:

<WORKSPACE_DEPLOYMENT_DIRECTORY>\WEB_INF\config

e. To set the Trusted Password on the Authentication Service:

i. Set the same password as in the previous step for the Authentication Service.

ii. Log on to the Local Service Configurator under:

<BIPLUS_HOME>\bin\ServiceConfig.bat

Note: You must have Global Administrator role assigned to perform these changes.

iii. Click Show host properties.

iv. Click the Authentication tab and set the password.

v. Click OK.

Configuring Shared Services

➤ To configure Shared Services:

1 Log on to Shared Services Configuration Console: http://<server>:58080/interop/framework/

2 Select Support Security Agent for Single Sign-on.

3 Click Save.

4 Select Requisite Provider (Oracle Internet Directory) and click Edit.

5 Select Trusted.

6 Click Save.

7 Restart all components.


Testing Module AvailabilityFor each of the products used, verify the setup by using the URLs below.

1URL: Where <Web server> is the Web server machine hostname and <port> is the Web Server listen port. For example, 19000 for Apache, IBM HTTP Server, and 80 for Oracle HTTP Server and IIS.

Product URL1 Expected Result

Workspace http://<Web server>:<port>/workspace/

Workspace splash screen and a new browser window should open.

Financial Reporting http://<Web server>:<port>/hr/status.jsp

Text: Hyperion Financial Reporting is available.

Web Analysis http://<Web server>:<port>/WebAnalysis

The browser should redirect to /WebAnalysis/WebAnalysis.jsp, the Web Analysis splash screen, and a new browser window should open.

Architect http://<Web server>:<port>/awb/appinfo.jsp

You should see an XML document showing the version number for Architect.

Financial Management http://<Web server>:<port>/hfm/Home/AboutHFM.asp?workspace=true

You should see an XML document showing the version number for Financial Management.

Planning http://<Web server>:<port>/HyperionPlanning/appinfo.jsp

You should see an XML document showing the version number for Planning.

Manually Deploying into WebLogic 8.1.4 111

A P P E N D I X

BManually Deploying into

WebLogic 8.1.4

In This Appendix Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

Deploying Workspace into WebLogic. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

Deploying Financial Reporting into WebLogic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114

Deploying Web Analysis into WebLogic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115

Configuring Apache with BEA WebLogic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116

Configuring Microsoft IIS 5/6 with WebLogic 8/9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

Testing the Connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129

112 Manually Deploying into WebLogic 8.1.4

Prerequisites● Hyperion Shared Services

❍ Install Hyperion Shared Services.


❍ Test the installation and make sure that you can log into Shared Services.


For example:


● Install Reporting and Analysis

It is required that the Application Server Deployment task of Hyperion Configuration Utility be run with the Manual Deployment option selected. If this option is not selected, you must re-run Hyperion Configuration Utility for the Application Server Deployment task.


Modifying startWebLogic.cmd

➤ To modify startWebLogic.cmd:

1 Open startWeblogic.cmd. For example:

C:\bea\user_porjects\domains\mydomain\startWebLogic.cmd;

2 Enter values for the JAVA_HOME location and the WL_HOME variables.

Note: These values may have been set by the WebLogic installer.

3 Set PRODUCTION_MODE=true. This starts the WebLogic Application Server in production mode.

4 Set the environment variables in the startWeblogic.cmd script:

SET LIB_DIR=<BIPLUS_HOME>\libSET CLASSPATH=%LIB_DIR%\iona63.jar;%LIB_DIR%;%CLASSPATH%SETJAVA_OPTIONS=-Dorg.omg.CORBA.ORBClass=com.iona.corba.art.artimpl.ORBImpl-Dorg.omg.CORBA.ORBSingletonClass=com.iona.corba.art.artimpl.ORBSingletonSET MEM_ARGS=-Xms256m -Xmx512m

5 Save startWeblogic.cmd.

Deploying Workspace into WebLogic 113

Deploying Workspace into WebLogic

➤ To deploy:

1 Extract <BIPLUS_HOME>\InstallableApps\workspace.war contents into <BIPLUS_HOME>\AppServer\InstalledApps\WebLogic\8.1\Workspace\

applications\workspace

2 Use startWebLogic.cmd to start the WebLogic Server Administration Console.

3 In a Web browser, enter the URL:

http://<server>:<port>/console

where <server> is the machine where WebLogic is running and <port> is the WebLogic standard port. The default port for a typical WebLogic installation is 7001.

4 Enter a username and password, then click Sign In.

5 In the left Navigation frame, select Deployments > Web Applications Modules, then select Deploy a new Web Application Module.

6 Select the following directory as the deployment location:

<BIPLUS_HOME>\AppServer\InstalledApps\WebLogic\8.1\Workspace\ applications\workspace

7 Select the Workspace Web application module and click Target Module.

Note: Do not select the workspace.war.

8 Review your choices, then click Deploy.

The Workspace Web application is deployed.

Note: See “Testing the Connection” on page 129.

Post Deployment for WorkspaceAfter you have deployed Workspace, create context.properties.



<BIPLUS_HOME>\AppServer\InstalledApps\WebLogic\8.1\Workspace\applications\Workspace\workspace\conf\context.properties



Set “Y” if components are installed, “N” if components are not installed. For example, if Financial Reporting, Interactive Reporting, WebAnalysis, and Dashboard Development Services are installed:


Note: Leave both HPSU and ChangeManagement entry values as Y.

Assign an appropriate Y or N to each value in accordance with the Reporting and Analysis modules installed:






Deploying Financial Reporting into WebLogic

➤ To deploy the Financial Reporting Web application:

1 Sign in to your WebLogic Admin Console.

2 In the left Navigation frame, select Deployments > Applications and select Deploy a new Application.

3 Select one as the archive to deploy:


4 Click Continue.



Deploying Web Analysis into WebLogic 115

Deploying Web Analysis into WebLogic

Pre-Deployment for Web AnalysisYou must prepare the JVM environment with the necessary environment variables for Web Analysis to function correctly. Reporting and Analysis creates WebAnalysis.env, which sets required environment variables at runtime. The file is located in:

<BIPLUS_HOME>\InstallableApps\config\

You may set the Web Analysis environment variables before or after deployment. Restart WebLogic after setting the variables.

The following example sets the environment variables in WebAnalysis.env:

envloader.path=<BIPLUS_HOME>\bin\EnvLoader.dllHYPERION_HOME=<HYPERION_HOME>BIPLUS_HOME=<BIPLUS_HOME>ARBORPATH=%HYPERION_HOME%\common\EssbaseRTC\9.2.1PATH=%ARBORPATH%\bin;%HYPERION_HOME%\common\ADM\9.2.0\Essbase\9.2.0\bin; %HYPERION HOME%\common\SAP\bin;%BIPLLUS_HOME%\bin;%PATH%LoadLibrarypath=%HYPERION_HOME%\common\ADM\9.2.0\Essbase\9.2.0\binLoadLibraryPath=%HYPERION_HOME%\common\ADM\9.2.0\libLoadLibraryPath=%HYPERION_HOME%\common\SAP\LoadClasspath=%HYPERION_HOME%/common/SAP/libLoadClasspath=%HYPERION_HOME%/common/CLS/9.2.1.0/lib/cls-9_2_0.jarLoadClasspath=%HYPERION_HOME%/common/JDBC/DataDirect/3.6/lib/hyjdbc.jar

Deploying Web Analysis

➤ To deploy the Web Analysis Web application:

1 Sign in to your WebLogic Admin Console.

2 In the left Navigation frame, select Deployments > Applications and select Deploy a new Application.

3 Select one as the archive to deploy:


4 Click Continue.




Configuring Apache with BEA WebLogicThe Apache HTTP Server Plug-in proxies requests from an Apache HTTP Server to a WebLogic Server. You target a non-clustered servers group using the WebLogicCluster parameter in the plug-in configuration file. The Apache HTTP Server Plug-in operates as a module within an Apache HTTP Server.

➤ To configure Apache HTTP Server:

1 Install Apache HTTP Server 2.0 and verify that the mod_so.c module is enabled by executing:

<APACHE_HOME>\bin\Apache.exe -1

Note: The mod_so.c module is required for loading Apache plug-in module for WebLogic.

This command lists all enabled modules. Verify that module mod_so.c is listed.

2 Install the Apache HTTP Server Plug-in module:

a. Copy the mod_wl_20.so file located in one of the following locations to the <APACHE_HOME>/modules directory:

<BEA_HOME>\weblogic81\server\bin

b. With a text editor, create <APACHE_HOME>/conf/HYSL-WebLogic.conf with the following contents, replacing the Workspace, Web Analysis, and Financial Reporting hosts and ports to be real values:

<LocationMatch /workspace/cdsrpc$> SetHandler weblogic-handler PathTrim / KeepAliveEnabled ON KeepAliveSecs 20 WeblogicCluster <workspace host>:<workspace port></LocationMatch><LocationMatch /workspace/administration> SetHandler weblogic-handler PathTrim / KeepAliveEnabled ON KeepAliveSecs 20 WeblogicCluster <workspace host>:<workspace port></LocationMatch><LocationMatch /workspace/browse> SetHandler weblogic-handler PathTrim / KeepAliveEnabled ON KeepAliveSecs 20 WeblogicCluster <workspace host>:<workspace port></LocationMatch><LocationMatch /workspace/personalpages> SetHandler weblogic-handler PathTrim / KeepAliveEnabled ON KeepAliveSecs 20 WeblogicCluster <workspace host>:<workspace port></LocationMatch>

Configuring Apache with BEA WebLogic 117

<LocationMatch /workspace/viewmanager> SetHandler weblogic-handler PathTrim / KeepAliveEnabled ON KeepAliveSecs 20 WeblogicCluster <workspace host>:<workspace port></LocationMatch><LocationMatch /workspace/jobmanager> SetHandler weblogic-handler PathTrim / KeepAliveEnabled ON KeepAliveSecs 20 WeblogicCluster <workspace host>:<workspace port></LocationMatch><LocationMatch /workspace/ihtml> SetHandler weblogic-handler PathTrim / KeepAliveEnabled ON KeepAliveSecs 20 WeblogicCluster <workspace host>:<workspace port></LocationMatch><LocationMatch /workspace/dataaccess> SetHandler weblogic-handler PathTrim / KeepAliveEnabled ON KeepAliveSecs 20 WeblogicCluster <workspace host>:<workspace port></LocationMatch><LocationMatch /workspace/logon$> SetHandler weblogic-handler PathTrim / KeepAliveEnabled ON KeepAliveSecs 20 WeblogicCluster <workspace host>:<workspace port></LocationMatch><LocationMatch /workspace/logon> SetHandler weblogic-handler PathTrim / KeepAliveEnabled ON KeepAliveSecs 20 WeblogicCluster <workspace host>:<workspace port></LocationMatch><LocationMatch /workspace/prefs$> SetHandler weblogic-handler PathTrim / KeepAliveEnabled ON KeepAliveSecs 20 WeblogicCluster <workspace host>:<workspace port></LocationMatch><LocationMatch /workspace/js> SetHandler weblogic-handler PathTrim / KeepAliveEnabled ON KeepAliveSecs 20 WeblogicCluster <workspace host>:<workspace port></LocationMatch><LocationMatch /workspace/modules> SetHandler weblogic-handler


PathTrim / KeepAliveEnabled ON KeepAliveSecs 20 WeblogicCluster <workspace host>:<workspace port></LocationMatch><LocationMatch /workspace/resources> SetHandler weblogic-handler PathTrim / KeepAliveEnabled ON KeepAliveSecs 20 WeblogicCluster <workspace host>:<workspace port></LocationMatch><LocationMatch /workspace/conf> SetHandler weblogic-handler PathTrim / KeepAliveEnabled ON KeepAliveSecs 20 WeblogicCluster <workspace host>:<workspace port></LocationMatch><LocationMatch /workspace/media> SetHandler weblogic-handler PathTrim / KeepAliveEnabled ON KeepAliveSecs 20 WeblogicCluster <workspace host>:<workspace port></LocationMatch><LocationMatch /workspace/BMPContext$>SetHandler weblogic-handler PathTrim / KeepAliveEnabled ON KeepAliveSecs 20 WeblogicCluster <workspace host>:<workspace port></LocationMatch><LocationMatch /workspace/$> SetHandler weblogic-handler PathTrim / KeepAliveEnabled ON KeepAliveSecs 20 WeblogicCluster <workspace host>:<workspace port></LocationMatch><LocationMatch /workspace/(.*)\.jsp$> SetHandler weblogic-handler PathTrim / KeepAliveEnabled ON KeepAliveSecs 20 WeblogicCluster <workspace host>:<workspace port></LocationMatch><LocationMatch /workspace/(.*)\.jsv$> SetHandler weblogic-handler PathTrim / KeepAliveEnabled ON KeepAliveSecs 20 WeblogicCluster <workspace host>:<workspace port></LocationMatch><LocationMatch /workspace/(.*)\.jsw$> SetHandler weblogic-handler PathTrim / KeepAliveEnabled ON

Configuring Apache with BEA WebLogic 119

KeepAliveSecs 20 WeblogicCluster <workspace host>:<workspace port></LocationMatch><LocationMatch /hr> SetHandler weblogic-handler PathTrim / KeepAliveEnabled ON KeepAliveSecs 20 WeblogicCluster <fr host>:<fr port></LocationMatch><LocationMatch /hr/*> SetHandler weblogic-handler PathTrim / KeepAliveEnabled ON KeepAliveSecs 20 WeblogicCluster <fr host>:<fr port></LocationMatch><LocationMatch /WebAnalysis/ServerConsole> SetHandler weblogic-handler PathTrim / KeepAliveEnabled ON KeepAliveSecs 20 WeblogicCluster <hostname>:<WebAnalysis_port></LocationMatch><LocationMatch /WebAnalysis/templates> SetHandler weblogic-handler PathTrim / KeepAliveEnabled ON KeepAliveSecs 20 WeblogicCluster <hostname>:<WebAnalysis_port></LocationMatch><LocationMatch /WebAnalysis/hfmtemplates> SetHandler weblogic-handler PathTrim / KeepAliveEnabled ON KeepAliveSecs 20 WeblogicCluster <hostname>:<WebAnalysis_port></LocationMatch><LocationMatch /WebAnalysis/hitemplates> SetHandler weblogic-handler PathTrim / KeepAliveEnabled ON KeepAliveSecs 20 WeblogicCluster <hostname>:<WebAnalysis_port></LocationMatch><LocationMatch /WebAnalysis/processor$> SetHandler weblogic-handler PathTrim / KeepAliveEnabled ON KeepAliveSecs 20 WeblogicCluster <hostname>:<WebAnalysis_port></LocationMatch><LocationMatch /WebAnalysis/servlet> SetHandler weblogic-handler PathTrim / KeepAliveEnabled ON KeepAliveSecs 20 WeblogicCluster <hostname>:<WebAnalysis_port>


</LocationMatch><LocationMatch /WebAnalysis/modules> SetHandler weblogic-handler PathTrim / KeepAliveEnabled ON KeepAliveSecs 20 WeblogicCluster <hostname>:<WebAnalysis_port></LocationMatch><LocationMatch /WebAnalysis/resources> SetHandler weblogic-handler PathTrim / KeepAliveEnabled ON KeepAliveSecs 20 WeblogicCluster <hostname>:<WebAnalysis_port></LocationMatch><LocationMatch /WebAnalysis/DirectoryServlet$> SetHandler weblogic-handler PathTrim / KeepAliveEnabled ON KeepAliveSecs 20 WeblogicCluster <hostname>:<WebAnalysis_port></LocationMatch><LocationMatch /WebAnalysis/config$> SetHandler weblogic-handler PathTrim / KeepAliveEnabled ON KeepAliveSecs 20 WeblogicCluster <hostname>:<WebAnalysis_port></LocationMatch><LocationMatch /WebAnalysis/wa_javadocs$> SetHandler weblogic-handler PathTrim / KeepAliveEnabled ON KeepAliveSecs 20 WeblogicCluster <hostname>:<WebAnalysis_port></LocationMatch><LocationMatch /WebAnalysis/$> SetHandler weblogic-handler PathTrim / KeepAliveEnabled ON KeepAliveSecs 20 WeblogicCluster <hostname>:<WebAnalysis_port></LocationMatch><LocationMatch /WebAnalysis/(.*)\.jsp$> SetHandler weblogic-handler PathTrim / KeepAliveEnabled ON KeepAliveSecs 20 WeblogicCluster <hostname>:<WebAnalysis_port></LocationMatch><LocationMatch /WebAnalysis/(.*)\.xml$> SetHandler weblogic-handler PathTrim / KeepAliveEnabled ON KeepAliveSecs 20 WeblogicCluster <hostname>:<WebAnalysis_port></LocationMatch>

Configuring Microsoft IIS 5/6 with WebLogic 8/9 121

<LocationMatch /WebAnalysis/(.*)\.jar$> SetHandler weblogic-handler PathTrim / KeepAliveEnabled ON KeepAliveSecs 20 WeblogicCluster <hostname>:<WebAnalysis_port></LocationMatch><LocationMatch /WebAnalysis/(.*)\.exe$> SetHandler weblogic-handler PathTrim / KeepAliveEnabled ON KeepAliveSecs 20 WeblogicCluster <hostname>:<WebAnalysis_port>

</LocationMatch>

c. Open:

<APACHE_HOME>\conf\httpd.conf

and add the following lines, replacing <BIPLUS_HOME> with an actual BIPlus installation path:

RedirectMatch 301 ^/WebAnalysis$ /WebAnalysis/ RedirectMatch 301 ^/workspace$ /workspace/ LoadModule weblogic_module modules\mod_wl_20.so Include conf/HYSL-WebLogic.conf

Alias /wsmedia "<BIPLUS_HOME>\AppServer\InstalledApps\workspace_static\wsmedia"Alias /workspace "<BIPLUS_HOME>\AppServer\InstalledApps\workspace_static"Alias /InsightInstaller "<BIPLUS_HOME>\AppServer\InstalledApps\workspace_static\zeroadmin\component\Insight" Alias /WebAnalysis "<BIPLUS_HOME>\AppServer\InstalledApps\WebAnalysis_static"

3 Restart the Apache HTTP server.

4 Test the plug-in by using a URL:

● Financial Reporting—http://<APACHE SERVER>:<port>/hr/version.jsp

● Web Analysis—http://<APACHE SERVER>:<port>/WebAnalysis

● Workspace—http://<APACHE SERVER>:<port>/workspace

Configuring Microsoft IIS 5/6 with WebLogic 8/9Configuring Microsoft ISS 5/6 with WebLogic 8/9 involves the following steps:

● Configure Proxying by Path

● Register iisforward.dll with IIS

● Configure Proxy by File Extension

● Testing Module Availability


Configure Proxying by Path

➤ To configure proxying by path:

1 Create a directory to store the configuration files needed to configure proxying by path. For example:

C:\Hyperion\WebLogicVHosts

2 Copy <WLS_HOME>\server\bin\iisforward.dll to the new directory.

3 Using a text editor, create a file called iisproxy.ini in the new directory.

4 Add the property WlForwardPath to iisproxy.ini, and specify a comma delimited list of paths to be proxied.

Only Workspace and Web Analysis paths need be included for this release, as they are the only applications that include static content. Other modules, such as Financial Reporting, include only dynamic content, and do not need to be included in WlForwardPath.

● Workspace dynamic content forward paths:

/workspace/cdsrpc,/workspace/administration,/workspace/browse,/ workspace/personalpages,/workspace/viewmanager,/workspace/ jobmanager,/workspace/ihtml,/workspace/dataaccess,/workspace/ logon,/workspace/prefs,/workspace/js,/workspace/modules,/workspace/ resources,/workspace/conf,/workpace/media,/workspace/BPMContext,/ workspace/*.jsp,/workspace/ * jsv,/workspace/*.jsw

● Web Analysis dynamic content forward paths:

/WebAnalysis/ServerConsole,/WebAnalysis/templates,/WebAnalysis/ hfmtemplates,/WebAnalysis/hitemplates,/WebAnalysis/portlettemplates,/ WebAnalysis/servlet,/WebAnalysis/modules,/WebAnalysis/resources,/ WebAnalysis/processor,/WebAnalysis/DirectoryServlet,/WebAnalysis/ config,/WebAnalysis/Conig,/WebAnalysis/wa_javadocs/*,/WebAnalysis/ *.jsp,/ WebAnalysis/*.xml,/WebAnalyis/*.jar,/WebAnalysis/*.exe

● iisproxi.ini that includes both Workspace and Web Analysis:

WlForwardPath=/workspace/cdsrpc,/workspace/administration,/workspace/ browse,/workspace/personalpages,/workspace/viewmanager,/workspace/ jobmanager,/workspace/ihtml,/workspace/dataaccess,/workspace/logon,/ workpace/prefs,/workspace/js,/workspace/modules,/workspace/ resources,/workpace/conf,/workspace/media,/workspace/BPMContext,/ workspace/*.jsp,/workpace/*.jsv,/workspace/*.jsw,/WebAnalysis/ ServerConsole,/WebAnalysis/templates,/WebAnalysis/hfmtemplates,/ WebAnalysis/hitemplates,/WebAnalysis/portlettemlates,/WebAnalysis/ servlet,/WebAnalysis/modules,/WebAnalysis/resources,/WebAnalysis/ processor,/WebAnalysis/DirectoryServlet,/WebAnalysis/config,/ WebAnalysis/Config,/WebAnalysis/wa_javadocs/*,/WebAnalysis/*.jsp,/ WebAnalyis/*.xml,/WebAnalysis/*.jar,/ WebAnalysis/*.exe


Register iisforward.dll with IISYou must register iisforward.dll with the IIS website used to proxy request to WebLogic.

➤ To register:

1 Open the Internet Information Service Manager and expand Web Sites.

2 Right click the Web Site used to proxy requests. For example, Default Web Site.

3 Select Properties from the context menu, and select ISAPI Filters.

4 Click Add, and enter WLFilter in Filter Name.

5 Provide the full path to iisforward.dll. For example:

C:\Hyperion\WebLogicVHosts\iisforward.dll

6 Click OK.

7 If you are configuring IIS 6.0 (Windows 2003), do the following:

a. Click Web Service Extensions.

b. In the right pane, click Add a new Web service extension.

c. In Extension Name, enter WLFilter.

d. Add the full path to iisforward.dll to Required Files by clicking Add. For example:


e. Check Set extension status to Allowed.

f. Click OK.

Configure Proxy by File ExtensionTo configure proxy by file extension:

● Create File-system Directories and Configuration Files

● Create Application Pools (IIS 6.0)

● Create IIS Virtual Directories

● Add IIS Application Extension Maps

Create File-system Directories and Configuration FilesA file-system directory must be created for Workspace and each Workspace module for which IIS will act as a proxy.

➤ To create and configure:

1 Create a directory to store the configuration files needed to configure proxying by extension for Workspace. For example:

C:\Hyperion\WebLogicVHosts\workspace


2 Repeat this process, creating a directory for each Workspace module you have installed. For example:

C:\Hyperion\WebLogicVHosts\WebAnalysisC:\Hyperion\WebLogicVHosts\FinancialReporting

3 Copy <WLS_HOME>\server\bin\iisproxy.dll to each new directory.

4 Using a text editor, create a file called iisproxy.ini in each new directory.

5 To each copy of iisproxy.ini, add the following:

WebLogicHost=weblogichost.example.comWebLogicPort=<WebLogic Server listen port>KeepAliveEnabled=trueKeepAliveSecs=20

6 For other modules, such as Financial Reporting, which include only dynamic content also add:

WlForwardPath=/context_path

Example iisproxy.ini for Workspace:

WebLogicHost=somehost.example.comWebLogicPort=45000KeepAliveEnabled=trueKeepAliveSecs=20

Example iisproxy.ini for Financial Reporting:

WlForwardPath=/hrWebLogicHost=somehost.example.comWebLogicPort=8200KeepAliveEnabled=trueKeepAliveSecs=20

Create Application Pools (IIS 6.0)If you are configuring IIS 6.0 (Windows 2003), perform this procedure for each file-system directory.

➤ To create application pools:

1 Open the Internet Information Service Manager.

2 Right click Application Pools.

3 Select New > Application Pool from the context menu.

4 Assign the same name given to your file-system directory in Application pool ID. For example, Workspace.

5 Click OK.

Create IIS Virtual DirectoriesIIS Virtual Directories must be created for Workspace and each Workspace module for which IIS will act as a proxy.


For Workspace

➤ To create IIS virtual directories for Workspace:



3 Select New > Virtual Directory from the context menu.

4 Click Next and specify workspace in the Alias field.

Aliases are case-sensitive. Enter aliases exactly as documented.

5 Provide the full path to the workspace_static directory in Path. For example:

C:\Hyperion\BIPlus\AppServer\InstalledApps\workspace_static

6 Click Next.

7 Select Read, Run scripts, Execute in the Virtual Directory Access Permissions dialog.

8 Click Next, then Finish.

9 Repeat the process to create a Virtual Directory called wsmedia that uses the full path to workspace_static\wsmedia. For example:

C:\Hyperion\BIPlus\AppServer\InstalledApps\workspace_static\wsmedia

10 Repeat the process again, to create a Virtual Directory called InsightInstaller that uses the full path to workspace_static\zeroadmin\component\Insight. For example:

C:\Hyperion\BIPlus\AppServer\InstalledApps\workspace_static\zeroadmin\ component\Insight

For Web Analysis

➤ To create IIS virtual directories for Web Analysis:




4 Click Next, and specify WebAnlysis in the Alias field.


5 In Path, provide the full path to the WebAnalysis_static directory. For example:

C:\Hyperion\BIPlus\AppServer\InstalledApps\WebAnalysis_static

6 Click Next.




For Financial Reporting and Products that do Not Include Static Content

➤ To create IIS virtual directories for Financial Reporting and products that do no include static content:




4 Click Next, then specify an appropriate value from the table above in the Alias field. For example, hr.


5 In Path, provide the full path to the files-system directory that contains iisproxy.ini and iisproxy.dll for this proxy definition. For example:

C:\Hyperion\WebLogicVHosts\FinancialReporting

6 Click Next.



9 Repeat this process for each additional application for which IIS will act as a proxy.

Add IIS Application Extension Maps

For Workspace and Web Analysis

➤ To add IIS application extension maps for Workspace and Web Analysis:


2 Expand the Web Site used to proxy requests. For example Default Web Site.

3 Right click the Virtual Directory called workspace, then select Properties.


● IIS 5.0-From Application Protection, select High (Isolated).

● IIS 6.0-Select the Application Pool you created for this Virtual Host during Create Application Pools (IIS 6.0). For example, Workspace.

5 Click Configuration.

6 Under Application extensions, click Add.

7 In Executable, provide the full path to the copy of iisproxy.dll that resides in the file-system directory created for this Virtual Host. For example:

C:\Hyperion\WebLogicVHosts\Workspace\iisproxy.dll

8 In Extension, enter .wlforward.

9 Clear Verify that file exists.


10 Click OK.

11 Repeat this process for the Web Analysis Virtual Host.


➤ To add IIS application extension maps for Financial Reporting and products that do not include static content:


2 Expand the Web Site used to proxy requests. For example, Default Web Site.

3 Right click the Virtual Directory to be configured; for example: hr, then select Properties.


● IIS 5.0-From Application Protection, select High (Isolated).

● IIS 6.0-Select the Application Pool you created for this Virtual Host during Create Application Pools (IIS 6.0). For example, hr.configuration.

5 Under Wildcard application maps, click Insert.

6 Provide the full path to the copy of iisproxy.dll that resides in the file-system directory created for this Virtual Host. For example:

C:\Hyperion\WebLogicVHosts\FinancialReporting\iisproxy.dll

7 Clear Verify that file exists.

8 Click OK.


Allow ISAPI Extensions (IIS 6.0)If you are configuring IIS 6.0 (Windows 2003), you need to allow ISAPI Extensions.

Do one of the following security models:

● Allow all Unknown ISAPI Extensions

● Add a New Web Service Extension for Each Copy of iisproxy.dll

Allow all Unknown ISAPI Extensions

➤ To configure:


2 Click Web Service Extensions.

3 In the right side pane, click All unknown ISAPI Extensions.


4 Click Allow.

5 Click OK.

Add a New Web Service Extension for Each Copy of iisproxy.dll

➤ To configure:



3 In the right side pane, click Add a new Web service extension.

4 In Extension Name, enter a unique name that reflects the role of the extension. For example, workspace-wls-proxy.

5 Add the full path to iisforward.dll to Required Files by clicking Add. For example:


6 Check Set extension status to Allowed.

7 Click OK.

8 Repeat process for each copy of iisproxy.dll.

Restart IISRestart IIS to enable the Microsoft Internet Information Server (IIS) Plug-in for WebLogic.

After restarting:

1. Open the Internet Information Service Manager and expand Web Sites.

2. Right click the Web Site used to proxy requests. For example, Default Web Site.

3. Select Properties from the context menu, and then click the ISAPI Filters tab.

4. Ensure the WLFilter ISAPI Filter is loaded.

Testing Module AvailabilityFor each of the productss used, verify the setup by using the URLs below:



You should see the Workspace splash screen and a new browser window should open.


You should see this text: Hyperion Financial Reporting is available.

Testing the Connection 129

1URL: Where <Web server> is the Web server machine hostname and <port> is the WebServer listen port. For example, 19000 for Apache, IBM HTTP Server, and 80 for Oracle HTTP Server and IIS.

Testing the ConnectionTest the connectivity to your newly deployed Reporting and Analysis application by opening the following URLs:

http://<server>:<port>/workspace/http://<server>:<port>/hr/http://<server>:<port>/WebAnalysis/

where <server> is the machine hostname where the Apache http server is running, and <port> is the port specified by the Listen directive in Apache’s httpd.conf file. For default port numbers, see “Port Numbers” on page 51.

Accessing http://<server>:<port>/hr/ redirects your browser to:

http://<server>:<port>/workspace/index.jsp

You must start the Workspace application first. If Workspace hasn’t been deployed yet, or is not started, you receive an error. As a workaround, verify the Financial Reporting application has deployed successfully by accessing

http://<server>:<port>/hr/version.jsp

which returns the Financial Reporting internal build number.


The browser should redirect to /WebAnalysis/WebAnalysis.jsp, the Web Analysis splash screen, and a new browser window should open. Where <Web server> is the Web server machine hostname and <port> is the Web Server listen port; for example, 19000 for Apache, IBM HTTP Server, and Oracle HTTP Server, and 80 for IIS. For a list of default ports, see Ports in the Hyperion System 9 Installation Start Here.



Manually Deploying into WebLogic 9.2 131

A P P E N D I X

CManually Deploying into

WebLogic 9.2


Preparing the Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132

Deploying Workspace into WebLogic. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135

Deploying Financial Reporting into WebLogic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139

Deploying Web Analysis into WebLogic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142

Configuring a Web Server for WebLogic 9.2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145

Configuring Microsoft IIS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152


132 Manually Deploying into WebLogic 9.2


❍ Install Shared Services

❍ Verify that it is up and running

❍ Test the installation and make sure that you can log into : http://<server>:<port>/interop/index.jsp

For example:



It is required thatyou run the and select both the Deploy to Application Server and Configure Web Server tasks. If these options were not selected, you must re-run Hyperion Configuration Utility.


Preparing the EnvironmentReview the following sections for information on:

● Preparing a One-Host Environment

● Preparing a Clustering Environment

Preparing a One-Host EnvironmentPreparing a one-host environment involves creating a WebLogic domain for the environment.

➤ To create a WebLogic domain:

1 Run BEA WebLogic Configuration Wizard:

<WL_HOME>\common\bin\config.cmd

2 Select Create a new WebLogic domain and click Next.

3 On Select Domain Source, click Next.

4 On Configure Administrator Username and Password, enter an administrator username and password, and click Next.

5 On Configure Sever Start Mode and JDK, select Production Mode, and click Next.

6 On Customize Environment and Services Settings, select Yes and click Next.

7 On Configure the Administration Server, enter an Administration Servlet Name and port. For example, AdminServer - 7001.

8 Configure SSL if necessary and click Next.

Preparing the Environment 133

9 On Configure Managed Servers, add the following servers:

● workspace - 45000

● WebAnalysis - 16000

● FinancialReporting - 8200

10 On Configure Clusters, click Next.

11 On Configure Machines, click Next.

12 On Review WebLogic Domain, click Next.

13 Enter a Domain name (for example, BIPlus_domain) and change the domain location if necessary. Click Create.

Preparing a Clustering EnvironmentPreparing a clustering environment involves:

● Creating a WebLogic Domain

● Creating a Cluster

● Starting Servers

● Deploying Application Servers in a Cluster

Creating a WebLogic Domain

➤ To create a WebLogic domain:

1 Run BEA WebLogic Configuration Wizard:

<WL_HOME>\common\bin\config.cmd

2 Select Create a new WebLogic domain and click Next.

3 On Select Domain Source, click Next.

4 On Configure Administrator Username and Password, enter an administrator username and password, and click Next.

5 On Configure Sever Start Mode and JDK, select Production Mode, and click Next.

6 On Customize Environment and Services Settings, select Yes and click Next.

7 On Configure the Administration Server, click Next.

8 Configure SSL if necessary and click Next.

9 On Configure Managed Servers, click Next.

10 On Configure Machines, click Next.

11 On Review WebLogic Domain, click Next.

12 Enter a Domain name (BIPlus_domain) and change the domain location if necessary. Click Create.


13 Check Start AdminConsole and press Done.

14 Login into AdminConsole and create three servers for Workspace, Web Analysis, and Financial Reporting.

a. Select Environment > Servers, then click Lock & Edit.

b. Click New and enter Server Name: <host>-ws for example, update Server Listen Port.

c. Click Next, then click Finish.

d. Click New and enter Server Name: <host>-fr for example, update Server Listen Port.

e. Click Next, then click Finish.

f. Click New and enter Server Name: <host>-wa for example, update Server Listen Port.

g. Click Next, then click Finish.

h. C lick Activate Changes.

15 Repeat steps 1-14 for every machine except host where a cluster will be configured.

Creating a Cluster

➤ To create a cluster:

1 Login into Admin console where cluster will be configured as Admin User.

2 Navivate to Environment > Machines, and click Lock & Edit.

a. Click New, enter the machine name, select OS, and click OK.

b. Repeat step a for all machines and click Activate Changes.

3 Navigate to Environment > Clusters, and click Lock & Edit.

a. Click New, enter the cluster name (for example: ws-cluster.), update the port value, and click OK.

b. Click New, enter the cluster name (for example: wa-cluster.), update the port value, and click OK.

c. Click New, enter the cluster name (for example: fr-cluster.), update the port value, and click OK.

4 Navigate to Environment > Servers and click Lock & Edit.

a. Click New, enter the server name (for example:<host>-ws), and update the port value. Select “Yes, make this server a member of an existing cluster” and select ws-cluster. Click Finish.

b. Click on the created server, select the correct machine, and click Save.

c. Click New, enter the server name (for example: <host>-wa), and update the port value. Select “Yes, make this server a member of an existing cluster” and select wa-cluster. Click Finish.

d. Click on the created server, select the correct machine, and click Save.


e. Click New, enter the server name (for example: <host>-fr), and update the port value. Select “Yes, make this server a member of an existing cluster” and select fr-cluster. Click Finish.

f. Click on the created server, select tbe correct machine, and click Save.

g. Repeat step a through step f for every host, and click Activate Changes.

Starting Servers

➤ To start servers, do one:

● Navigate to Environment > Clusters > <Cluster Name> > Control. Select all servers in the cluster and click Start. Click Yes to continue.

● Using the command line, enter:

%DOMAIN_DIR%\bin\startManagedWebLogic.cmd <server-name> http://<cluster_host>:<port>

For example:

startManagedWebLogic.cmd bi-win21-ws http://bi-win21:7002

Deploying Application Servers in a ClusterFollow manual deployment instructions in the following sections. Deploy on all hosts in the cluster and create property files for every machine.

Deploying Workspace into WebLogic● Pre-deployment for Workspace

● Deploying Workspace

● Post-deployment for Workspace

Pre-deployment for Workspace

➤ To pre-deploy Workspace:

1 Create the following startup script:

<BIPLUS_HOME>\AppServer\InstalledApps\WebLogic\9.2\Workspace\startWorkspace.cmd

with the following content, replacing <BIPLUS_HOME>, <BIPlus_domain>, <admin server>, and <port> with real values:

set LIB_DIR=<BIPLUS_HOME>\libset EXT_PRE_CLASSPATH=%LIB_DIR%\iona63.jar;%LIB_DIR%;%EXT_PRE_CLASSPATH%


set JAVA_OPTIONS="-Djavax.xml.parsers.SAXParserFactory=org.apache.xerces.jaxp.SAXParserFactoryImpl"cd <BIPlus_domain>\binstartManagedWebLogic.cmd workspace http://<admin server>:<port>

Note: All parent folders should be created manually.

For example:

set LIB_DIR=C:\Hyperion\BIPlus\libset EXT_PRE_CLASSPATH=%LIB_DIR%\iona63.jar;%LIB_DIR;%EXT_PRE_CLASSPATH%set JAVA_OPTIONS="-Djavax.xml.parsers.SAXParserFactory=org.apache.xerces.jaxp.SAXParserFactoryImpl"cd C:\bea\user_projects\domains\BIPlus_domain\binstartManagedWebLogic.cmd workspace http://localhost:7001

2 Create the following shutdown script:

<BIPLUS_HOME>\AppServer\InstalledApps\WebLogic\9.2\Workspace\stopWorkspace.cmd

with the followng content, replacing <BIPlus_domain>, <admin server>, and <port> with real values:

cd <BIPlus_domain>\binstopManagedWebLogic.cmd workspace t3://<admin server>:<port> %1 %2

Deploying Workspace

➤ To deploy Workspace:

1 Create following file and set environment variables:

<BIPLUS_HOME>\InstallableApps\unpack_workspace.cmd

2 Run the following script:

@ECHO OFF

SET BIPLUS_HOME=<BIPLUS_HOME>SET JAVA_HOME=<JAVA_HOME>SET TEMP_EAR=%BIPLUS_HOME%\InstallableApps\tmp\wsSET WEB_APP=%BIPLUS_HOME%\InstallableApps\workspace.warSET WEB_APP_DIR=%BIPLUS_HOME%\AppServer\InstalledApps\WebLogic\9.2\Workspace\applications\workspace

IF EXIST %WEB_APP% GOTO CHECK_JAVA GOTO INVALID_DIR :CHECK_JAVAif "%JAVA_HOME%" == "" GOTO NO_JAVAIF NOT EXIST "%JAVA_HOME%\bin\jar.exe" GOTO NO_JAVA


IF NOT EXIST %TEMP_EAR% GOTO CREATE_DIRRD /s/q %TEMP_EAR%

:CREATE_DIRMKDIR %TEMP_EAR%MKDIR %WEB_APP_DIR%

ECHO Unpacking workspace.war...

CD "%WEB_APP_DIR%" "%JAVA_HOME%\bin\jar.exe" -xf %WEB_APP%RD /s/q %TEMP_EAR%

ECHO DoneGOTO END

:NO_JAVAECHO The JAVA_HOME environment variable is not set to a suitable JDK home.GOTO END :INVALID_DIRECHO Unable to find %WEB_APP%. Check the value of the BIPLUS_HOME variable.GOTO END

:END PAUSE

Note: Replace <BIPLUS_HOME> and <JAVA_HOME> with an actual BIPlus home and JDK home directory paths.

3 Use the following script to start the WebLogic Server Administration Console:

<BIPLUS_DOMAIN>\bin\startWebLogic.cmd

4 Start the workspace server using the startup script created in pre-deployment. For example:

<BIPLUS_HOME>\AppServer\InstalledApps\WebLogic\9.2\Workspace\startWorkspace.cmd

5 In a Web browser, enter the following URL:


where <server> is the machine where WebLogic is running and <port> is the domain port (7001 according to point 7 in Preparing a One-Host Environment).

6 Enter a username and password, then click Sign In.

7 If you have not already done so, in the Change Center of the Administration Console, click Lock & Edit.

8 In the left pane of the Administration Consolec click Deployments.

9 In the right pane, click Install.


10 Using the Install Application Assistant, locate the following directory the corresponds to the Web application you want to intsall.

<BIPLUS_HOME>\AppServer\InstalledApps\WebLogic\9.2\Workspace\applications\workspace

11 When you locate the directory to install, click Next.

12 Select Install this deployment as an application and click Next.

13 Select workspace as the target server to deploy the Web application and click Next.

14 Select I will make the deployment accessible from the following location.

15 Click Next.

16 Review the configuration settings, and click Finish to complete the installation.

If you install an application that follows the below directory structure and there is no deployment plan in the /plan/plan directory, WebLogic server automatically creates a deployment plan for you.

a.+app-rootb.+/appc.+/plan

Choose one:

● If you chose to immediately go to the deployment's configuration screen, click the tabs to set additional configuration settings for the Web application.

● If you chose to change this information later, the Administration Console returns you to the Deployments table, which should now include your newly-installed Web application.

17 Click Activate changes.

18 Start the application, and turn the application state from Prepared to Active.

Post-deployment for WorkspacePost-deployment for Workspace involves creating context.properties.



<BIPLUS_HOME>\AppServer\InstalledApps\WebLogic\9.2\Workspace\applications\workspace\conf\context.properties


Set “Y” if components have been installed, “N” if components have not been installed:


Deploying Financial Reporting into WebLogic 139

Note: Leave both HPSU and ChangeManagement entry values as ‘Y’.

3 Assign an appropriate Yor N to each value in accordance with the modules you have installed:

Financial Reporting (Reports)

Interactive Reporting (HPSU)

Performance Scorecard (HPS)

Dashboard Development Services (ChangeManagement)

Web Analysis (Analyzer)

4 Start or restart the workspace server using the scripts created during pre-deployment.

Deploying Financial Reporting into WebLogic● Pre-deployment for Financial Reporting

● Deploying Financial Reporting

Pre-deployment for Financial Reporting

➤ To pre-deploy Financial Reporting:


<BIPLUS_HOME>\AppServer\InstalledApps\WebLogic\9.2\FinancialReporting\startFinancialReporting.cmd

with the following content, replacing <BIPLUS_HOME>, <BIPlus_domain>, <admin server> and <port> with real values:

cd <BIPlus_domain>\binstartManagedWebLogic.cmd FinancialReporting http://<admin server>:<port>.


For example:

cd C:\bea\user_projects\domains\biplus_domain\binstartManagedWebLogic.cmd FinancialReporting http://localhost:7001


<BIPLUS_HOME>\AppServer\InstalledApps\WebLogic\9.2\FinancialReporting\stopFinancialReporting.cmd

with the following content, replacing <BIPlus_domain>, <admin server>, and <port> with real values:

cd <BIPlus_domain>\binstopManagedWebLogic.cmd FinancialReporting t3://<admin server>:<port> %1 %2


Deploying Financial Reporting



<BIPLUS_HOME>\InstallableApps\unpack_freporting.cmd


@ECHO OFF

SET BIPLUS_HOME=<BIPLUS_HOME>SET JAVA_HOME=<JAVA_HOME>SET TEMP_EAR=%BIPLUS_HOME%\InstallableApps\tmp\frSET WEB_APP=%BIPLUS_HOME%\InstallableApps\HReports.earSET WEB_APP_DIR=%BIPLUS_HOME%\AppServer\InstalledApps\WebLogic\9.2\FinancialReporting\applications\HReports.ear

IF EXIST %WEB_APP% GOTO CHECK_JAVA GOTO INVALID_DIR :CHECK_JAVAif "%JAVA_HOME%" == "" GOTO NO_JAVAIF NOT EXIST "%JAVA_HOME%\bin\jar.exe" GOTO NO_JAVA IF NOT EXIST %TEMP_EAR% GOTO CREATE_DIRRD /s/q %TEMP_EAR%

:CREATE_DIRMKDIR %TEMP_EAR%MKDIR %WEB_APP_DIR%MKDIR %WEB_APP_DIR%\hr.warMKDIR %WEB_APP_DIR%\HReports.war

ECHO Unpacking HReports.ear...

CD %TEMP_EAR%"%JAVA_HOME%\bin\jar.exe" -xf %WEB_APP% HReports.war hr.war

CD "%WEB_APP_DIR%" "%JAVA_HOME%\bin\jar.exe" -xf %WEB_APP% META-INFCD "%WEB_APP_DIR%"\hr.war"%JAVA_HOME%\bin\jar.exe" -xf %TEMP_EAR%\hr.war

CD "%WEB_APP_DIR%"\HReports.war"%JAVA_HOME%\bin\jar.exe" -xf %TEMP_EAR%\HReports.war

RD /s/q %TEMP_EAR%

ECHO DoneGOTO END

:NO_JAVAECHO The JAVA_HOME environment variable is not set to a suitable JDK home.GOTO END

Deploying Financial Reporting into WebLogic 141

:INVALID_DIRECHO Unable to find %WEB_APP%. Check the value of the BIPLUS_HOME variable.GOTO END

:END PAUSE


3 Copy the files listed below to:

<BIPLUS_HOME>\AppServer\InstalledApps\WebLogic\9.2\FinancialReproting\applications\HReports.ear\hr.war\WEB-INF\lib

From <BIPLUS_HOME>:

<BIPLUS_HOME>\lib\HReports.jar<BIPLUS_HOME>\lib\NetCharts.jar<BIPLUS_HOME>\lib\HyperionADMWidgets.jar<BIPLUS_HOME>\lib\commons-fileupload-1.0.jar

From <HYPERION_HOME>:

<HYPERION_HOME>\common\loggers\Log4j\1.2.8\lib\log4j-1.2.8.jar<HYPERION_HOME>\common\ADM\9.2.0\lib\adm.jar<HYPERION_HOME>\common\ADM\9.2.0\lib\ap.jar

4 Start the FinancialReporting server using the startup script created during pre-deployment. For example:

<BIPLUS_HOME>\AppServer\InstalledApps\WebLogic\9.2\FinancialReporting\startFinancialReporting.cmd

5 Login in to your WebLogic Admin Console using the following URL:



6 Click Deployments.

7 Click Lock and Edit.

8 Click Install.

9 Using the Install Application Assistant, locate the directory that corresponds to the Web application you want to install.

10 <BIPLUS_HOME>\AppServer\InstalledApps\WebLogic\9.2\FinancialReporting\applications\

HReports.earWhen you locate the directory to install, click Next.

11 Select Install this deployment as an applicatio and click Next.

12 Select FinancialReporting as the target server, then click Next.


14 Click Finish.



16 Start the application (turn application state from Prepared to Active).

17 Start or restart the FinancialReporting server using the scripts created during pre-deployment.

Deploying Web Analysis into WebLogicDeploying Web Analysis into WebLogic involves:

● Pre-deployment for Web Analysis

● Verifying Web Analysis Environment Variables

● Deploying Web Analysis

Pre-deployment for Web Analysis

➤ To pre-deploy Web Analysis:


<BIPLUS_HOME>\AppServer\InstalledApps\WebLogic\9.2\WebAnalysis\startWebAnalysis.cmd

with the following content, replacing <BIPLUS_HOME>, <BIPlus_domain>, <admin server>, and <port> with real values:

cd <BIPlus_domain>\binstartManagedWebLogic.cmd WebAnalysis http://<admin server>:<port>


For example:

cd C:\bea\user_projects\domains\BIPlus_domain\binstartManagedWebLogic.cmd WebAnalysis http://localhost:7001


<BIPLUS_HOME>\AppServer\InstalledApps\WebLogic\9.2\WebAnalysis\stopWebAnalysis.cmd

replacing <BIPlus_domain>, <admin server>, and <port> with real values:

cd <BIPlus_domain>\binstopManagedWebLogic.cmd WebAnalysis t3://<admin server>:<port> %1 %2

Verifying Web Analysis Environment VariablesThe Hyperion Configuration Utility prepares the JVM environment with the necessary environment variables for WebAnalysis to function correctly. Reporting and Analysis creates WebAnalysis.env which sets required environment variables at runtime. The file is located in:

<BIPLUS_HOME>\InstallableApps\config

Deploying Web Analysis into WebLogic 143




<BIPLUS_HOME>\InstallableApps\unpack_webanalysis.cmd


@ECHO OFF

SET BIPLUS_HOME=<BIPLUS_HOME>SET JAVA_HOME=<JAVA_HOME>SET TEMP_EAR=%BIPLUS_HOME%\InstallableApps\tmp\waSET WEB_APP=%BIPLUS_HOME%\InstallableApps\WebAnalysis.earSET WEB_APP_DIR=%BIPLUS_HOME%\AppServer\InstalledApps\WebLogic\9.2\WebAnalysis\applications\WebAnalysis.ear

IF EXIST %WEB_APP% GOTO CHECK_JAVA GOTO INVALID_DIR :CHECK_JAVAif "%JAVA_HOME%" == "" GOTO NO_JAVAIF NOT EXIST "%JAVA_HOME%\bin\jar.exe" GOTO NO_JAVA IF NOT EXIST %TEMP_EAR% GOTO CREATE_DIRRD /s/q %TEMP_EAR%

:CREATE_DIRMKDIR %TEMP_EAR%MKDIR %WEB_APP_DIR%MKDIR %WEB_APP_DIR%\WebAnalysis.war

ECHO Unpacking WebAnalysis.ear...

CD %TEMP_EAR%"%JAVA_HOME%\bin\jar.exe" -xf %WEB_APP% WebAnalysis.war

CD "%WEB_APP_DIR%" "%JAVA_HOME%\bin\jar.exe" -xf %WEB_APP% META-INFCD "%WEB_APP_DIR%"\WebAnalysis.war"%JAVA_HOME%\bin\jar.exe" -xf %TEMP_EAR%\WebAnalysis.war

RD /s/q %TEMP_EAR%

ECHO DoneGOTO END

:NO_JAVAECHO The JAVA_HOME environment variable is not set to a suitable JDK home.GOTO END


:INVALID_DIRECHO Unable to find %WEB_APP%. Check the value of the BIPLUS_HOME variable.GOTO END

:END PAUSE


3 Start the WebAnalysis server using the startup script created during pre-deployment. For example:

<BIPLUS_HOME>\AppServer\InstalledApps\WebLogic\9.2\WebAnalysis\startWebAnalysis.cmd

4 Log on to your WebLogic Admin Console using the following URL:



5 Click Deployments.

6 Click Lock and Edit.

7 Click Install.

8 Using the Install Application Assistant, locate the following directory that corresponds to the Web application you want to install:

<BIPLUS_HOME>\AppServer\InstalledApps\WebLogic\9.2\WebAnalysis\applications\WebAnalysis.ear

9 When you locate the directory to install, click Next.

10 Select Install this deployment as an application and click Next.

11 Select WebAnalysis as the target server, and click Next.


13 Click Finish.


15 Start the application (turn the application state from Prepared to Active).

16 Start or restart the target WebAnalysis server using the scripts created during pre-deployment.

Note: <BPLUS_HOME>\InstallableApps\config\WebAnalysis.properties contains the ConfigURL parameter which is set to the WebServer port value. Configure WebServer and start Workspace before running Web Analysis.

Configuring a Web Server for WebLogic 9.2 145

Configuring a Web Server for WebLogic 9.2Hyperion components often are distributed across physical hardware resources, and are always distributed among multiple application server instances. All Hyperion components accessed through the Workspace must share the Web server hostname and port. A Web server is used to fulfill this requirement.

Configuring the Apache Web Server Plug-inThe Apache Web Server Plug-in proxies requests from an Apache Web Server to a WebLogic Server. You target a non-clustered servers group using the WebLogicCluster parameter in the plug-in configuration file. The Apache Web Server Plug-in operates as a module within an Apache Web Server.

➤ To configure the Apache Web Server plug-in:

1 Install Apache Web Server 2.0 and verify that mod_so.c module is enabled by executing:

<APACHE_HOME>\bin\apache.exe -l

mod_so.c module is required for loading Apache plug-in module for WebLogic. This command lists all enabled modules. Verify that module mod_so.c is listed.

Note: mod_so.c enables loadable module support and is usually installed by default. If not, rebuild Apache using the --enable-so configuration option.

2 Install the Apache HTTP Plug-in module:

a. Copy the mod_wl_20.so file located in:

<WL_HOME>\server\plugin\<OS_name>\<OS_bit>

to the <APACHE_HOME>\modules directory.

If you did not install WebLogic with the Apache HTTP Plug-in module, the mod_wl_20.so file and directory are not there. If this is the case:

❍ Re-run the WebLogic 9.2 installation, select custom, and select the Web Server Plugins component.

❍ Copy mod_wl_20.so from another WebLogic 9.2 installation that has plug-ins.

b. With a text editor, create:

<APACHE_HOME>\conf\HYSL-WebLogic.conf

replacing<hostname>, <ws_port>, <fr_port> and <wa_port> by their values:

RedirectMatch 301 ^/WebAnalysis$ /WebAnalysis/RedirectMatch 301 ^/workspace$ /workspace/LoadModule weblogic_module modules/mod_wl_20.so<LocationMatch /workspace/cdsrpc$>SetHandler weblogic-handlerPathTrim /KeepAliveEnabled ONKeepAliveSecs 20


WeblogicCluster <hostname>:<ws_port></LocationMatch>

<LocationMatch /workspace/administration>SetHandler weblogic-handlerPathTrim /KeepAliveEnabled ONKeepAliveSecs 20WeblogicCluster <hostname>:<ws_port></LocationMatch>

<LocationMatch /workspace/browse>SetHandler weblogic-handlerPathTrim /KeepAliveEnabled ONKeepAliveSecs 20WeblogicCluster <hostname>:<ws_port></LocationMatch>

<LocationMatch /workspace/personalpages>SetHandler weblogic-handlerPathTrim /KeepAliveEnabled ONKeepAliveSecs 20WeblogicCluster <hostname>:<ws_port></LocationMatch>

<LocationMatch /workspace/viewmanager>SetHandler weblogic-handlerPathTrim /KeepAliveEnabled ONKeepAliveSecs 20WeblogicCluster <hostname>:<ws_port></LocationMatch>

<LocationMatch /workspace/jobmanager>SetHandler weblogic-handlerPathTrim /KeepAliveEnabled ONKeepAliveSecs 20WeblogicCluster <hostname>:<ws_port></LocationMatch>

<LocationMatch /workspace/ihtml>SetHandler weblogic-handlerPathTrim /KeepAliveEnabled ONKeepAliveSecs 20WeblogicCluster <hostname>:<ws_port></LocationMatch>

<LocationMatch /workspace/dataaccess>SetHandler weblogic-handlerPathTrim /KeepAliveEnabled ONKeepAliveSecs 20WeblogicCluster <hostname>:<ws_port></LocationMatch>


<LocationMatch /workspace/logon$>SetHandler weblogic-handlerPathTrim /KeepAliveEnabled ONKeepAliveSecs 20WeblogicCluster <hostname>:<ws_port></LocationMatch>

<LocationMatch /workspace/logon>SetHandler weblogic-handlerPathTrim /KeepAliveEnabled ONKeepAliveSecs 20WeblogicCluster <hostname>:<ws_port></LocationMatch>

<LocationMatch /workspace/prefs$>SetHandler weblogic-handlerPathTrim /KeepAliveEnabled ONKeepAliveSecs 20WeblogicCluster <hostname>:<ws_port></LocationMatch>

<LocationMatch /workspace/js>SetHandler weblogic-handlerPathTrim /KeepAliveEnabled ONKeepAliveSecs 20WeblogicCluster <hostname>:<ws_port></LocationMatch>

<LocationMatch /workspace/modules>SetHandler weblogic-handlerPathTrim /KeepAliveEnabled ONKeepAliveSecs 20WeblogicCluster <hostname>:<ws_port></LocationMatch>

<LocationMatch /workspace/resources>SetHandler weblogic-handlerPathTrim /KeepAliveEnabled ONKeepAliveSecs 20WeblogicCluster <hostname>:<ws_port></LocationMatch>

<LocationMatch /workspace/conf>SetHandler weblogic-handlerPathTrim /KeepAliveEnabled ONKeepAliveSecs 20WeblogicCluster <hostname>:<ws_port></LocationMatch>

<LocationMatch /workspace/media>SetHandler weblogic-handlerPathTrim /


KeepAliveEnabled ONKeepAliveSecs 20WeblogicCluster <hostname>:<ws_port></LocationMatch>

<LocationMatch /workspace/BPMContext$>SetHandler weblogic-handlerPathTrim /KeepAliveEnabled ONKeepAliveSecs 20WeblogicCluster <hostname>:<ws_port></LocationMatch>

<LocationMatch /workspace/wsrp4j>SetHandler weblogic-handlerPathTrim /KeepAliveEnabled ONKeepAliveSecs 20WeblogicCluster <hostname>:<ws_port></LocationMatch>

<LocationMatch /workspace/ResourceProxy>SetHandler weblogic-handlerPathTrim /KeepAliveEnabled ONKeepAliveSecs 20WeblogicCluster <hostname>:<ws_port></LocationMatch>

<LocationMatch /workspace/$>SetHandler weblogic-handlerPathTrim /KeepAliveEnabled ONKeepAliveSecs 20WeblogicCluster <hostname>:<ws_port></LocationMatch>

<LocationMatch /workspace/(.*)\.jsp$>SetHandler weblogic-handlerPathTrim /KeepAliveEnabled ONKeepAliveSecs 20WeblogicCluster <hostname>:<ws_port></LocationMatch>

<LocationMatch /workspace/(.*)\.jsv$>SetHandler weblogic-handlerPathTrim /KeepAliveEnabled ONKeepAliveSecs 20WeblogicCluster <hostname>:<ws_port></LocationMatch>

<LocationMatch /workspace/(.*)\.jsw$>SetHandler weblogic-handlerPathTrim /KeepAliveEnabled ONKeepAliveSecs 20


WeblogicCluster <hostname>:<ws_port></LocationMatch>

<LocationMatch /hr>SetHandler weblogic-handlerPathTrim /KeepAliveEnabled ONKeepAliveSecs 20WeblogicCluster <hostname>:<fr_port></LocationMatch>

<LocationMatch /hr/*>SetHandler weblogic-handlerPathTrim /KeepAliveEnabled ONKeepAliveSecs 20WeblogicCluster <hostname>:<fr_port></LocationMatch>

<LocationMatch /WebAnalysis/ServerConsole>SetHandler weblogic-handlerPathTrim /KeepAliveEnabled ONKeepAliveSecs 20WeblogicCluster <hostname>:<wa_port></LocationMatch>

<LocationMatch /WebAnalysis/templates>SetHandler weblogic-handlerPathTrim /KeepAliveEnabled ONKeepAliveSecs 20WeblogicCluster <hostname>:<wa_port></LocationMatch>

<LocationMatch /WebAnalysis/hfmtemplates>SetHandler weblogic-handlerPathTrim /KeepAliveEnabled ONKeepAliveSecs 20WeblogicCluster <hostname>:<wa_port></LocationMatch>

<LocationMatch /WebAnalysis/hitemplates>SetHandler weblogic-handlerPathTrim /KeepAliveEnabled ONKeepAliveSecs 20WeblogicCluster <hostname>:<wa_port></LocationMatch>

<LocationMatch /WebAnalysis/processor$>SetHandler weblogic-handlerPathTrim /KeepAliveEnabled ONKeepAliveSecs 20WeblogicCluster <hostname>:<wa_port></LocationMatch>


<LocationMatch /WebAnalysis/servlet>SetHandler weblogic-handlerPathTrim /KeepAliveEnabled ONKeepAliveSecs 20WeblogicCluster <hostname>:<wa_port></LocationMatch>

<LocationMatch /WebAnalysis/modules>SetHandler weblogic-handlerPathTrim /KeepAliveEnabled ONKeepAliveSecs 20WeblogicCluster <hostname>:<wa_port></LocationMatch>

<LocationMatch /WebAnalysis/resources>SetHandler weblogic-handlerPathTrim /KeepAliveEnabled ONKeepAliveSecs 20WeblogicCluster <hostname>:<wa_port></LocationMatch>

<LocationMatch /WebAnalysis/DirectoryServlet$>SetHandler weblogic-handlerPathTrim /KeepAliveEnabled ONKeepAliveSecs 20WeblogicCluster <hostname>:<wa_port></LocationMatch>

<LocationMatch /WebAnalysis/config$>SetHandler weblogic-handlerPathTrim /KeepAliveEnabled ONKeepAliveSecs 20WeblogicCluster <hostname>:<wa_port></LocationMatch>

<LocationMatch /WebAnalysis/wa_javadocs$>SetHandler weblogic-handlerPathTrim /KeepAliveEnabled ONKeepAliveSecs 20WeblogicCluster <hostname>:<wa_port></LocationMatch>

<LocationMatch /WebAnalysis/$>SetHandler weblogic-handlerPathTrim /KeepAliveEnabled ONKeepAliveSecs 20WeblogicCluster <hostname>:<wa_port></LocationMatch>

<LocationMatch /WebAnalysis/(.*)\.jsp$>SetHandler weblogic-handlerPathTrim /


KeepAliveEnabled ONKeepAliveSecs 20WeblogicCluster <hostname>:<wa_port></LocationMatch>

<LocationMatch /WebAnalysis/(.*)\.xml$>SetHandler weblogic-handlerPathTrim /KeepAliveEnabled ONKeepAliveSecs 20WeblogicCluster <hostname>:<wa_port></LocationMatch>

<LocationMatch /WebAnalysis/(.*)\.jar$>SetHandler weblogic-handlerPathTrim /KeepAliveEnabled ONKeepAliveSecs 20WeblogicCluster <hostname>:<wa_port></LocationMatch>

<LocationMatch /WebAnalysis/(.*)\.exe$>SetHandler weblogic-handlerPathTrim /KeepAliveEnabled ONKeepAliveSecs 20WeblogicCluster <hostname>:<wa_port></LocationMatch>

c. Open:

<APACHE_HOME>\conf\httpd.conf

and add the following lines, replacing <BIPLUS_HOME> with an actual BIPlus installation path:

Include conf/HYSL-WebLogic.confAlias /wsmedia"<BIPLUS_HOME>\AppServer\InstalledApps\workspace_static\wsmedia"Alias /workspace"<BIPLUS_HOME>\AppServer\InstalledApps\workspace_static"Alias /InsightInstaller"<BIPLUS_HOME>\AppServer\InstalledApps\workspace_static\zeroadmin\component\Insight"Alias /WebAnalysis"<BIPLUS_HOME>\AppServer\InstalledApps\WebAnalysis_static"

3 Restart the Apache Web Server.

4 Test the plug-in by using a URL:

● Financial Reporting—http://<APACHE SERVER>:<port>/hr/status.jsp

● WebAnalysis—http://<APACHE SERVER>:<port>/WebAnalysis

● Workspace—http://<APACHESERVER>:<port>/workspace

where <APACHE SERVER> is the Apache server host machine and <port> is the default port, 19000.


Configuring Microsoft IISThe Microsoft Internet Information Server (IIS) Plug-in for WebLogic proxies requests from IIS to WebLogic. The web applications that comprise the Application Layer Web Tier of are distributed among more than one WebLogic server instance, which include the Workspace, and one or more of the following Workspace modules:


● Web Analysis

● Architect

● Planning

● Performance Scorecard

All Hyperion products that are accessed through Architect must share the same Web server hostname and port.

The following procedures describe configuring Microsoft IIS and the IIS plug-in for WebLogic to fulfill this requirement.

Configure Proxying by Path

➤ To configure proxying by path:

1 Create a directory to store the configuration files needed to configure proxying by path. For example:

C:\Hyperion\WebLogicVHosts.

2 Copy <WLS_HOME>\server\bin\iisforward.dll to your new directory.

3 Using a text editor, create a file called iisproxy.ini in your new directory.

4 Add the property WlForwardPath to iisproxy.ini, and specify a comma delimited list of paths to be proxied.

Only Workspace and Web Analysis paths need to be included, for this release, as they are the only applications that include static content. Other modules, such as Financial Reporting, include only dynamic content, and do not need to be included in WlForwardPath.

● Workspace dynamic content forward paths:

/workspace/cdsrpc,/workspace/administration,/workspace/browse,/workspace/personalpages,/workspace/viewmanager,/workspace/jobmanager,/workspace/ihtml,/workspace/dataaccess,/workspace/logon,/workspace/prefs,/workspace/js,/workspace/modules,/workspace/resources,/workspace/conf,/workspace/media,/workspace/BPMContext,/workspace/*.jsp,/workspace/*.jsv,/workspace/*.jsw,/workspace/wsrp4j/*, /workspace/ResourceProxy

● Web Analysis dynamic content forward paths:

/WebAnalysis/ServerConsole,/WebAnalysis/templates,/WebAnalysis/hfmtemplates,/WebAnalysis/hitemplates,/WebAnalysis/portlettemplates,/WebAnalysis/servlet,/WebAnalysis/modules,/WebAnalysis/resources,/WebAnalysis/processor,/WebAnalysis/DirectoryServlet,/WebAnalysis/config,/WebAnalysis/Config,/WebAnalysis/wa_javadocs/*,/WebAnalysis/*.jsp,/WebAnalysis/*.xml,/WebAnalysis/*.jar,/WebAnalysis/*.exe

Configuring Microsoft IIS 153

● iisproxi.ini that include both Workspace and Web Analysis:

WlForwardPath=/workspace/cdsrpc,/workspace/administration,/workspace/browse,/workspace/personalpages,/workspace/viewmanager,/workspace/jobmanager,/workspace/ihtml,/workspace/dataaccess,/workspace/logon,/workspace/prefs,/workspace/js,/workspace/modules,/workspace/resources,/workspace/conf,/workspace/media,/workspace/BPMContext,/workspace/*.jsp,/workspace/*.jsv,/workspace/*.jsw,/workspace/wsrp4j/*,/workspace/ResourceProxy,/WebAnalysis/ServerConsole,/WebAnalysis/templates,/WebAnalysis/hfmtemplates,/WebAnalysis/hitemplates,/WebAnalysis/portlettemplates,/WebAnalysis/servlet,/WebAnalysis/modules,/WebAnalysis/resources,/WebAnalysis/processor,/WebAnalysis/DirectoryServlet,/WebAnalysis/config,/WebAnalysis/Config,/WebAnalysis/wa_javadocs/*,/WebAnalysis/*.jsp,/WebAnalysis/*.xml,/WebAnalysis/*.jar,/WebAnalysis/*.exe

Register iisforward.dll with IISYou must register iisforward.dll with the IIS website that will be used to proxy request to WebLogic.

➤ To register:

1 Open the Internet Information Service Manager, and expand Web Sites.

2 Right click the Web Site that will be used to proxy requests. For example: Default Web Site.

3 Select Properties from the context menu, and click ISAPI Filters.

4 Click Add, and enter WLFilter in Filter Name.

5 Provide the full path to iisforward.dll. For example: C:\Hyperion\WebLogicVHosts\iisforward.dll

6 Click OK.

7 If you are configuring IIS 6.0 (Windows 2003), do the following:

a. Click Web Service Extensions.

b. In the right side pane, click Add a new Web service extension.

c. In Extension Name, enter WLFilter.

d. Add the full path to iisforward.dll to Required Files by clicking Add. For example: C:\Hyperion\WebLogicVHosts\iisforward.dll

e. Check Set extension status to Allowed.

f. Click OK.

Configure Proxy by File Extension● Create File-system Directories and Configuration Files

● Create Application Pools (IIS 6.0)

● Create IIS Virtual Directories

● Add IIS Application Extension Maps

● Allow ISAPI Extensions (IIS 6.0)


Create File-system Directories and Configuration FilesA file-system directory must be created for Workspace and each Workspace module for which IIS will act as a proxy.

➤ To create and configure:

1 Create a directory to store the configuration files needed to configure proxying by extension for Workspace. For example: C:\Hyperion\WebLogicVHosts\workspace

2 Repeat this process, creating a directory for each Workspace module you have installed. For example:

C:\Hyperion\WebLogicVHosts\WebAnalysis

C:\Hyperion\WebLogicVHosts\FinancialReporting

C:\Hyperion\WebLogicVHosts\BPMA

3 Copy <WLS_HOME>\server\bin\iisproxy.dll to each new directory.

4 Using a text editor, create a file called iisproxy.ini in each new directory.

5 To each copy of iisproxy.ini, add the following:

WebLogicHost=weblogichost.example.comWebLogicPort=<WebLogic Server listen port>

If proxying to a WebLogic cluster, substitute WebLogicHost with WebLogicCluster, and do not include WebLogicPort. For example:

WebLogicCluster=host1.example.com:<port>,host2.example.com:<port>

For a full list of supported plug-in parameters, see BEA documentation.

Example iisproxy.ini for Workspace:

WebLogicHost=somehost.example.comWebLogicPort=45000KeepAliveEnabled=trueKeepAliveSecs=20

Create Application Pools (IIS 6.0) If you are configuring IIS 6.0 (Windows 2003), perform this procedure for each file-system directory you created.

➤ To create application pools:


2 Right click Application Pools.

3 Select New > Application Pool from the context menu.

4 Assign the same name given to your file-system directory in Application pool ID. For example Workspace.

5 Click OK.


Create IIS Virtual DirectoriesIIS Virtual Directories must be created for and each module for which IIS will act as a proxy.

For Workspace

➤ To create IIS virtual directories for Workspace:




4 Click Next, then specify workspace in the Alias field.


5 Provide the full path to the workspace_static directory in Path. For example: <BIPLUS_HOME>\AppServer\InstalledApps\workspace_static

6 Click Next.



9 Repeat the process to create a Virtual Directory called wsmedia that uses the full path to:

workspace_static\wsmedia

For example:

<BIPLUS_HOME>\AppServer\InstalledApps\workspace_static\wsmedia

10 Repeat the process, again, to create a Virtual Directory called InsightInstaller that uses the full path to:

workspace_static\zeroadmin\component\Insight

For example:

<BIPLUS_HOME>\AppServer\InstalledApps\workspace_static\zeroadmin\component\Insight

For Web Analysis

➤ To create IIS virtual directories for Web Analysis:


2 Right click the Web Site used to proxy requests. For example , Default Web Site.


4 Click Next, then specify Web Analysis in the Alias field.



5 In Path, provide the full path to the WebAnalysis_static directory. For example, <BIPLUS_HOME>\AppServer\InstalledApps\WebAnalysis_static.

6 Click Next.




For Workspace modules that do not include static content, such as Financial Reporting, create one virtual directory for each file-system directory. The Virtual Directory Aliases used must match the context root of the web application for which IIS will act as a proxy. For example:

➤ For Financial Reporting and any products that do not include static content:


2 Right click the Web Site used to proxy requests. For example Default Web Site.


4 Click Next, then specify an appropriate value from the table above in the Alias field. For example, hr.


5 In Path, provide the full path to the file-system directory that contains iisproxy.ini and iisproxy.dll for this proxy definition. For example, C:\Hyperion\WebLogicVHosts\FinancialReporting.

6 Click Next.




Application Workspace Module Application Context Root Virtual DirectoryAlias

Financial Reporting /hr hr

Architect /awb awb

Performance Scorecard /HPSWebReports HPSWebReports

Planning /HyperionPlanning HyperionPlanning


Add IIS Application Extension Maps

For Workspace and Web Analysis

➤ To add IIS application extension maps:


2 Expand the Web Site used to proxy requests. For example Default Web Site.

3 Right click on the Virtual Directory called workspace, then select Properties.


● IIS 5.0 —From Application Protection, select High (Isolated).

● IIS 6.0—Select the Application Pool that you created for this Virtual Host. For example, Workspace.


6 Under Application extensions, click Add.

7 In Executable, provide the full path to the copy of iisproxy.dll that resides in the file-system directory for this Virtual Host. For example: C:\Hyperion\WebLogicVHosts\Workspace\iisproxy.dll

8 In Extension, enter .wlforward.

9 Clear Verify that file exists and click OK.

10 Repeat this process for the Virtual Host.


➤ For Financial Reporting and any products that do not include static content:


2 Expand the Web Site used to proxy requests. For example, Default Web Site.

3 Right click on the Virtual Directory to be configured. For example: hr, then select Properties.


● IIS 5.0 (Windows 2000)—From Application Protection, select High (Isolated).

● IIS 6.0 (Windows 2003)—Select the Application Pool that you created for this Virtual Host. For example, hr.


6 Under Wildcard application maps, click Insert.

7 Provide the full path to the copy of iisproxy.dll that resides in the file-system directory for this Virtual Host. For example: C:\Hyperion\WebLogicVHosts\FinancialReporting\iisproxy.dll


8 Clear Verify that file exists and click OK.


Allow ISAPI Extensions (IIS 6.0)If you are configuring IIS 6.0 (Windows 2003), you need to allow ISAPI Extensions. Do the one of the following security models:

Allow all unknown ISAPI Extensions

➤ To configure:



3 In the right side pane, click All unknown ISAPI Extensions.

4 Click Allow.

5 Click OK.

Add a new Web service extension for each copy of iisproxy.dll

➤ To configure:



3 In the right side pane, click Add a new Web service extension.

4 In Extension Name, enter a unique name that reflects the role of the extension. For example workspace-wls-proxy.

5 Add the full path to iisforward.dll to Required Files by clicking Add. For example, C:\Hyperion\WebLogicVHosts\iisforward.dll

6 Check Set extension status to Allowed and click OK.

7 Repeat process for each copy of iisproxy.dll.

Restart IIS Restart IIS to enable the Microsoft Internet Information Server (IIS) Plug-in for WebLogic. After restarting:

1. Open the Internet Information Service Manager, and expand Web Sites.

2. Right click the Web Site used to proxy requests. For example Default Web Site.

3. Select Properties from the context menu, and then click the ISAPI Filters tab.

4. Ensure the WLFilter ISAPI Filter is loaded.

Testing Module Availability 159


1URL: Where <Web server> is the Web server machine hostname and <port> is the Web Server listen port. For example, 19000 for Apache, IBM HTTP Server, and 80 for Oracle HTTP Server and IIS.





Text:Hyperion Financial Reporting is available.




Manually Deploying into WebSphere 5.1.1.7 161

A P P E N D I X

DManually Deploying into

WebSphere 5.1.1.7


Deploying Workspace into WebSphere . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162

Deploying Financial Reporting into WebSphere . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165

Deploying Web Analysis into WebSphere . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168

Configuring Apache or IBM HTTP with WebSphere 5.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171

Configuring Microsoft IIS with WebSphere 5.1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174


162 Manually Deploying into WebSphere 5.1.1.7

Prerequisites● Hyperion Shared Services

❍ Install Hyperion Shared Services.


❍ Test the installation and make sure that you can log into Shared Services.


For example:



It is required that the Application Server Deployment task of Hyperion Configuration Utility be run with the Manual Deployment option selected. If this option was not selected, you must re-run Hyperion Configuration Utility for the Application Server Deployment task.


Deploying Workspace into WebSphere

Deploying Workspace

➤ To deploy the Workspace Web Application:

1 Run your WebSphere Server. For example:

C:\IBM\AppServer\bin\startServer.bat server1

2 Login into WebSphere Administrative Console by using the URL:

http://<server>:<port>/admin

Enter the username and password: admin and blank for the password.

3 Create a Workspace server:

a. Click Servers > Application Servers.

b. Click New.

c. Enter the Server name (for example, workspace) and click Next.

d. Click Finish.

4 Create a virtual host:

a. Click Environment > Virtual Hosts.

b. Click New.

c. Enter the virtual host name and click OK.

Deploying Workspace into WebSphere 163

5 Create a new application:

a. Click Applications > Install New Application.

b. Choose Server path and enter the path and file name:

<BIPLUS_HOME>\AppServer\InstallabelApps\workspace.war

Enter /workspace into the context root.

c. Click Next.

d. Select Generate Default Bindings.

e. Select Do not default virtual host name for Web modules.

f. Click Next.

g. On the next screen click Continue.

h. To pre-compile the JSPs on the Provide options to perform the installation screen, select Pre-compile JSP.

i. Click Next.

j. On Map Virtual Hosts for Web Modules, select the Web module and the Virtual Host, and click Next.

k. On Map modules to application servers, select the Web module and cell, node, and server, and click Apply. Click Next.

l. Click Finish.

m. After the deployment process finishes, click Save to Master Configuration.

Configuring Workspace Web Application

➤ To configure Workspace Web Application:

1 Navigate to Servers > Application Servers.

2 Click Workspace.

3 Click Web Container.

4 Navigate to Session Management > Enable Cookies.

5 Change the cookie path from / to /workspace, then click OK.

6 Optional: Click on Thread Pool and adjust the settings for your user base. For example, for many concurrent users, increase the Maximum Size.

7 Click OK.

8 Click HTTP transports.

9 Verify the Port assignments for this application server.


11 In the Message window, click Save.

12 In the Save to Master Configuration window, click Save.





<WAS_HOME>\AppServer\InstalledApps\<NODE_NAME>\workspace_war.ear\ workspace.war\conf\context.properties


Set “Y” if components are installed, “N” if components are not installed. For example, if Financial Reporting, Interactive Reporting, WebAnalysis, and Dashboard Development Services are installed:









Starting Workspace Web Application

➤ To start the Workspace ND web application:

1 Start the workspace web application.

2 Click Enterprise Applications.

3 Select Enable Workspace_war application.

4 Click Start at the top.

➤ To start the Workspace Base:

<WAS_HOME>/bin/startServer.bat/<Workspace_Server_Name>

Deploying Financial Reporting into WebSphere 165

Deploying Financial Reporting into WebSphere

Deploying


1 If you have implemented WebSphere Network Deployment (ND), start the network manager through the StartManager command. Otherwise, use the StartServer command to start the application server where WebSphere's Administration Console application is installed. For example: ./startServer.sh server1.

2 Log on to the WebSphere Administrative Console.


4 Click New.

5 For Server Name, enter FinancialReporting. Leave other options with their default values, or modify to suit your WebSphere infrastructure.

6 Click Next.

7 Click Finish.


9 Click FinancialReporting.



12 Click OK.




16 Optional: Navigate to FinancialReporting > Process Definition > Java Virtual Machine.

17 Optional: Adjust the minimum and maximum heap size to suit your hardware and average load. Refer to the Java memory tuning tips section in the WebSphere InfoCenter for guidelines on setting the JVM heap size. The URL:

http://publib.boulder.ibm.com/infocenter/wasinfo/v5r1//index.jsp?topic=/com.ibm.websphere.base.doc/info/aes/ae/rprf_javamemory.html

18 Navigate to Environment > Virtual Hosts.

19 In the right pane, click the virtual host created in step 4 under “Deploying Workspace” on page 162.

20 Click Host Aliases.

21 Click New.


22 Assign a value to Host Name that makes sense for your infrastructure. For example:

● To allow a host to connect to the http transports noted in step 10 - step 14, enter an asterisk (*) in this field.

● To limit access to a host, such as your HTTP Server machine, enter that host's name or IP address.

● Change the Port assignment to the non-SSL port noted in step 13.

23 Click OK.

24 Optional: If your site uses SSL, repeat step 13, and assign the correct Secure Socket Layer (SSL) Port, noted in step 14.

25 Click Save in the main toolbar.

26 Click Save in the right pane.

27 In the left pane, navigate to Applications > Install New Application.

28 If you are working on the WebSphere Application Server machine where the Financial Reporting Web Application is installed, browse to the HReports.ear location, using Local path. Otherwise, use the Server path.

Tip: The HReports.ear default location is <BIPLUS_HOME>\InstallableApps\

29 Click Next.

30 Select the Virtual Host created when deploying Workspace, step 4 on page 162.

31 Click Next in Preparing for the Application Installation.

32 Optional: In Provide Options to Perform the Installation, specify the directory where you deploy the application, or click Next.

33 Click Next in Map Virtual Hosts for Web Modules.

34 In Map Modules to Application Servers:

a. Highlight the cell containing the FinancialReporting application server.

b. Select HReports.war and hr.war, and click Apply.

Note: If the check box is not selected, deployment runs on the default server.

35 Click Next.

36 In Summary, click Finish.

37 In the main toolbar, click Save.

38 In the right pane, click Save.

Deploying Financial Reporting into WebSphere 167

39 To start the Financial Reporting application server:

● If you have implemented WebSphere Network Deployment (ND), navigate to Servers > Application Servers in the left pane, and select FinancialReporting in the right pane, then click Start.

● If you have not implemented WebSphere ND, use the WebSphere startServer command. For example:

C:\WebSphere\AppServer\Bin\startServer.bat FinancialReporting

40 Optional: Create an NT/2000 service to start the Financial Reporting automatically when the system starts. For example:

C:\IBM\AppServer\bin\WASService -add "desired_service_display_name"-serverName "name_of_WebSphere_Server"

where desired_service_display_name is the name displayed in the Windows Services applet, such as “Hyperion Financial Reporting Web” and name_of_WebSphere_Server is the WebSphere server name where you deployed the application.

Configuring● “Changing the Default Cookie Path” on page 167

● “Enabling UTF-8 Encoding” on page 168

Changing the Default Cookie Path

➤ To change the default cookie path:

1 Navigate to WebSphere Application Server.

2 Click FinancialReporting.

3 Navigate to Web Container - Session Management.

4 Select Enable Cookie.

5 Click Enable Cookie and change the Cookie path from / to /hr.

6 Save the changes in Master Configuration and restart the Financial Reporting Application Server.


Enabling UTF-8 EncodingAfter deploying Financial Reporting, enable UTF-8 URL encoding for the Application Server.

➤ To enable UTF-8 encoding:

1 Start the WebSphere Administrator's Console.

2 Navigate to Servers > Application Servers > FinancialReporting.

3 In the Additional Properties section, click Process Definition.

4 In the Process Definition's Additional Properties section, click Java Virtual Machine.

5 Set the Generic JVM Argument Property:

-Dclient.encoding.override=UTF-8

6 Select Apply.

7 Save changes in Master Configuration and restart the FinancialReporting Application Server.

Deploying Web Analysis into WebSphere

Pre-Deployment for Web Analysis You must prepare the JVM environment with the necessary environment variables for Web Analysis to function correctly. Reporting and Analysis creates WebAnalysis.env, which sets required environment variables at runtime. The file is located in:

<BIPLUS_HOME>\InstallableApps\config\

You can set the Web Analysis environment variables before or after deployment. Restart WebSphere after setting the variables.

The following example sets the environment variables in WebAnalysis.env:

envloader.path=<BIPLUS_HOME>/bin/EnvLoader.dllHYPERION_HOME=<HYPERION_HOME>BIPLUS_HOME=<BIPLUS_HOME>ARBORPATH=%HYPERION_HOME%/common/EssbaseRTC/9.2.1PATH=%ARBORPATH%/bin;%HYPERION_HOME%/common/ADM/9.2.0/Essbase/9.2.0/bin;%HYPERION_HOME%/common/SAP/bin;%BIPLUS_HOME%/bin;%PATH%LoadLibrarypath=%HYPERION_HOME%/common/ADM/9.2.0/Essbase/9.2.0/binLoadLibraryPath=%HYPERION_HOME%/common/ADM/9.2.0/libLoadLibraryPath=%HYPERION_HOME%/common/SAP/binLoadClasspath=%HYPERION_HOME%/common/SAP/libLoadClasspath=%HYPERION_HOME%/common/CLS/9.2.1.0/lib/cls-9_2_0.jarLoadClasspath=%HYPERION_HOME%/common/JDBC/DataDirect/3.6/lib/hyjdbc.jar

Deploying Web Analysis into WebSphere 169

Deploying


1 If you have implemented WebSphere Network Deployment (ND), start the network manager through the StartManager command. Otherwise, use the StartServer command to start the application server where WebSphere's Administration Console application is installed. For example: ./startServer.sh server1.

2 Log on to the WebSphere Administrative Console.


4 Click New.

5 For Server Name, enter WebAnalysis. Leave other options with their default values, or modify to suit your WebSphere infrastructure.

6 Click Next.

7 Click Finish.


9 Click WebAnalysis.



12 Click OK.




16 Optional: Navigate to WebAnalysis > Process Definition > Java Virtual Machine.

17 Optional: Adjust the minimum and maximum heap size to suit your hardware and average load. Refer to the Java memory tuning tips section in the WebSphere InfoCenter for guidelines on setting the JVM heap size. The URL:

http://publib.boulder.ibm.com/infocenter/wasinfo/v5r1//index.jsp?topic=/com.ibm.websphere.base.doc/info/aes/ae/rprf_javamemory.html

18 Navigate to Environment > Virtual Hosts.

19 In the right pane, click the virtual host created in step 4 under “Deploying Workspace” on page 162.

20 Click Host Aliases.

21 Click New.

22 Assign a value to Host Name that makes sense for your infrastructure. For example:

● To allow a host to connect to the http transports noted in step 10 - step 14, enter an asterisk (*) in this field.


● To limit access to a host, such as your HTTP Server machine, enter that host's name or IP address.

● Change the Port assignment to the non-SSL port noted in step 13.

23 Click OK.

24 Optional: If your site uses SSL, repeat step 13, and assign the correct Secure Socket Layer (SSL) Port, noted in step 14.

25 Click Save in the main toolbar.

26 Click Save in the right pane.

27 In the left pane, navigate to Applications > Install New Application.

28 If you are working on the WebSphere Application Server machine where the Web Analysis Web Application is installed, browse to the WebAnalysis.ear location, using Local path. Otherwise, use the Server path.

Tip: The WebAnalysis.ear default location is <BIPLUS_HOME>\InstallableApps\

29 Click Next.

30 Select the Virtual Host created when deploying Workspace, step 4 on page 162.

31 Click Next in Preparing for the Application Installation.

32 Optional: In Provide Options to Perform the Installation, specify the directory where you deploy the application, or click Next.

33 Click Next in Map Virtual Hosts for Web Modules.

34 In Map Modules to Application Servers:

a. Highlight the cell containing the WebAnalysis application server.

b. Select WebAnalysis.ear, and click Apply.

Note: If the check box is not selected, deployment runs on the default server.

35 Click Next.

36 In Summary, click Finish.

37 In the main toolbar, click Save.

38 In the right pane, click Save.

39 To start the Web Analysis application server:

● If you have implemented WebSphere Network Deployment (ND), navigate to Servers > Application Servers in the left pane, and select WebAnalysis in the right pane, then click Start.

● If you have not implemented WebSphere ND, use the WebSphere startServer command; for example:

C:\WebSphere\WebSphere\AppServer\bin\startServer.batWebAnalysis

Configuring Apache or IBM HTTP with WebSphere 5.1 171

40 Optional: Create an NT/2000 service to start the Web Analysis automatically when the system starts; for example:

C:\IBM\AppServer\bin\WASService -add "desired_service_display_name"-serverName "name_of_WebSphere_Server"

where desired_service_display_name is the name displayed in the Windows Services applet, such as “Hyperion Web Analysis Web” and name_of_WebSphere_Server is the WebSphere server name where you deployed the application.

Configuring

➤ To change the default cookie path:

1 Navigate to WebSphere Application Server.

2 Click WebAnalysis.

3 Navigate to Web Container - Session Management.

4 Select Enable Cookie.

5 Click Enable Cookie and change the Cookie path from / to /WebAnalysis.

6 Save the changes in Master Configuration and restart the Web Analysis Application Server.

Configuring Apache or IBM HTTP with WebSphere 5.1This section describes the configuring of either Apache 2.x or IBM HTTP Server. Before configuring, close the WebSphere Application Server and the HTTP server.

➤ To configure an HTTP Server with WebSphere:

1 Configure virtual hosts:

a. Click Environment > Virtual Hosts.

b. Click on a virtual host. For example, default_host.

c. In Additional Properties, click Host Aliases.

d. Click New.

e. In the Host Name, type asterisk (*).

f. In the Port field, enter the HTTP port.

g. Click OK.

h. On the top of the window, click Save.

2 Regenerate HTTP server plug-in configuration file:

a. Click Environment > Update Web Server Plugin.

b. Click OK.

c. In the left pane, navigate to Environment > Update Web Server Plug-in.


3 Right-click on the link View or download the current web server plug-in configuration file and click Save As. Save the file to a location on your HTTP Server machine.

4 Manually modify the plugin-cfg.xml file created by the process above by adding instructions to serve Workspace and Web Analysis static content from the Web server, rather than from the application server. This improves performance.

Workspace:

Change the URI group definition which contains this single line:

<Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid" Name="/workspace/*"/>

To:

<Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid"Name="/workspace/cdsrpc"/><Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid"Name="/workspace/administration/*"/><Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid"Name="/workspace/browse/*"/><Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid"Name="/workspace/personalpages/*"/><Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid"Name="/workspace/viewmanager/*"/><Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid"Name="/workspace/jobmanager/*"/><Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid"Name="/workspace/ihtml/*"/><Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid"Name="/workspace/dataaccess/*"/><Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid"Name="/workspace/logon"/><Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid"Name="/workspace/logon/*"/><Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid"Name="/workspace/prefs"/><Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid"Name="/workspace/js/*"/><Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid"Name="/workspace/modules/*"/><Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid"Name="/workspace/resources/*"/><Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid"Name="/workspace/conf/*"/><Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid"Name="/workspace/media/*"/><Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid"Name="/workspace/BPMContext"/><Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid"Name="/workspace/wsrp4j/*"/><Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid"Name="/workspace/ResourceProxy"/><Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid"Name="/workspace/"/><Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid"Name="/workspace/*.jsp"/><Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid"


Name="/workspace/*.jsv"/><Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid"Name="/workspace/*.jsw"/>

Web Analysis:


<Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid" Name="/WebAnalysis/*"/>

To:

<Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid"Name="/WebAnalysis/ServerConsole/*" /><Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid"Name="/WebAnalysis/templates/*" /><Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid"Name="/WebAnalysis/hfmtemplates/*" /><Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid"Name="/WebAnalysis/hitemplates/*" /><Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid"Name="/WebAnalysis/processor" /><Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid"Name="/WebAnalysis/servlet/*" /><Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid"Name="/WebAnalysis/modules/*" /><Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid"Name="/WebAnalysis/resources/*" /><Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid"Name="/WebAnalysis/DirectoryServlet" /><Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid"Name="/WebAnalysis/config" /><Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid"Name="/WebAnalysis/wa_javadocs" /><Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid"Name="/WebAnalysis/" /><Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid"Name="/WebAnalysis/*.jsp" /><Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid"Name="/WebAnalysis/*.xml" /><Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid"Name="/WebAnalysis/*.jar" />

5 If your HTTP Server is not running on the same machine as your Application Server, copy the following folders to your HTTP Server machine:

<BIPLUS_HOME>\AppServer\InstalledApps\workspace_static<BIPLUS_HOME>\AppServer\InstalledApps\WebAnalysis_static

6 Copy <WAS_HOME>\bin\mod_was_ap20_http.dll to <HTTP_SERVER_ROOT>\modules\

7 Open httpd.conf on your HTTP server and add the following, replacing <BIPLUS_HOME> with an actual BIPlus installation path:

LoadModule was_ap20_module modules\mod_was_ap20_http.dllWebSpherePluginConfig "<PLUGIN-CFG-LOCATION>\plugin-cfg.xml"Alias /workspace" <BIPLUS_HOME>\AppServer\InstalledApps\workspace_static"


Alias /wsmedia "<BIPLUS_HOME>\AppServer\InstalledApps\workspace_static\wsmedia"Alias /InsightInstaller "<BIPLUS_HOME>\AppServer\InstalledApps\workspace_static\zeroadmin\component\Insight"Alias /WebAnalysis "<BIPLUS_HOME>\AppServer\InstalledApps\WebAnalysis_static"

Note: If your HTTP Server is not running on the same machine as your Application Server, update the workspace_static and WebAnalysis_static folder paths according to step 5.

8 Restart the WebSphere Application Server(s) which run the Workspace, WebAnalysis, and Financial Reporting web applications.

9 Restart the HTTP server.

Configuring Microsoft IIS with WebSphere 5.1

➤ To configure:

1 Start the IIS application.

2 Create a new virtual directory for the Web site instance that will work with WebSphere Application Server. These instructions assume that you are using the Default Web Site.

a. On the left navigation pane expand to Default Web Site. Right-click Default Web Site and select New > Virtual Directory to create the directory with a default installation.

b. In the Adding a virtual directory wizard, perform the following steps:

i. Type sePlugins in the Virtual Directory Alias screen.

ii. Browse to the WebSphere Application Server <WAS_PLUGINS_INSTALL_ROOT>\bin directory in the Web Site Content Directory screen.

iii. Select Execute (such as ISAPI application or CGI) in the Virtual Directory Access Permissions screen.

iv. Click Finish to add the sePlugins virtual directory to your default Web site.

3 Add the Internet Services Application Programming Interface (ISAPI) filter into the IIS configuration:

a. Right-click Default Web Site in the tree on the left and click Properties.

b. In the Properties dialog, perform the following steps:

i. Go to the ISAPI Filters tab.

ii. Click Add to open the Filter properties window.

iii. In Filter Name, type iisWASPlugin.

iv. In Executable, click Browse.

v. Browse to the <WAS_PLUGINS_ROOT>\bin directory.

vi. Click iisWASPlugin_http.dll.

vii. Click OK until all open windows close.

Configuring Microsoft IIS with WebSphere 5.1 175

4 Enable the Web server to run WebSphere Application Server extensions (IIS 6.0):

a. Expand the navigation pane to Web service extensions.

b. Click Web Service Extensions.

c. In the right side pane, click Add a new Web service extension.

d. Specify Extension name. For example, iisWASPlugin.

e. Add the full path to <WAS_PLUGINS_ROOT>\bin\iisWASPlugin_http.dll to Required Files by clicking Add.

f. Check Set extension status to Allowed.

g. Click OK.

5 Create IIS Virtual Directories for Workspace:

a. Open the Internet Information Service Manager and expand Web Sites.

b. Right click the Web Site used to proxy requests. For example Default Web Site.

c. Select New > Virtual Directory from the context menu.

d. Click Next, then specify workspace in the Alias field.


e. Provide the full path to the workspace_static directory in Path; for example:

<BIPLUS_HOME>\AppServer\InstalledApps\workspace_static

f. Click Next.

g. Select Read, Run scripts, Execute in the Virtual Directory Access Permissions dialog.

h. Click Next, then Finish.

i. Repeat the process to create a Virtual Directory called wsmedia that uses the full path to workspace_static\wsmedia. For example:

<BIPLUS_HOME>AppServer\InstalledApps\\workspace_static\wsmedia

j. Repeat the process, again, to create a Virtual Directory called InsightInstaller that uses the full path to workspace_static\zeroadmin\component\Insight. For example:

<BIPLUS_HOME>\AppServer\InstalledApps\\workspace_static\zeroadmin\component\Insight

k. Configure MIME types for InsightInstaller virtual directory:

❍ Right click the InsightInstaller virtual directory and select Properties.

❍ Select HTTP Headers tab and click MIME Types.

❍ Add following Extension / MIME types pairs:

.bat / application/octet-stream

.exe / application/octet-stream

.ex_ / application/octet-stream

.msi / application/octet-stream

.boot / application/octet-stream

.hdr / application/octet-stream

.ini / application/octet-stream

.xpi / application/octet-stream


6 Create IIS Virtual Directories for Web Analysis:

a. Open the Internet Information Service Manager and expand Web Sites.

b. Right click the Web Site used to proxy requests. For example Default Web Site.


d. Click Next, then specify WebAnalysis in the Alias field.


e. In Path, provide the full path to the WebAnalysis_static directory. For example:

<BIPLUS_HOME>\AppServer\InstalledApps\\WebAnalysis_static

f. Click Next.



7 Generate the Web server plug-in:

a. Log in to the WebSphere Administrative Console for the profile containing your application servers.

b. Navigate to Servers > Web Servers and click OK.

c. Download/save generated plugin using View or download the current web server plugin configuration file link.


Workspace:


<Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid"Name="/workspace/*"/>

To:

<Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid"Name="/workspace/cdsrpc"/><Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid"Name="/workspace/administration/*"/><Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid"Name="/workspace/browse/*"/><Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid"Name="/workspace/personalpages/*"/><Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid"Name="/workspace/viewmanager/*"/><Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid"Name="/workspace/jobmanager/*"/><Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid"Name="/workspace/ihtml/*"/><Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid"Name="/workspace/dataaccess/*"/><Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid"Name="/workspace/logon"/>


<Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid"Name="/workspace/logon/*"/><Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid"Name="/workspace/prefs"/><Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid"Name="/workspace/js/*"/><Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid"Name="/workspace/modules/*"/><Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid"Name="/workspace/resources/*"/><Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid"Name="/workspace/conf/*"/><Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid"Name="/workspace/media/*"/><Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid"Name="/workspace/BPMContext"/><Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid"Name="/workspace/wsrp4j/*"/><Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid"Name="/workspace/ResourceProxy"/><Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid"Name="/workspace/"/><Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid"Name="/workspace/*.jsp"/><Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid"Name="/workspace/*.jsv"/><Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid"Name="/workspace/*.jsw"/>

Web Analysis


<Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid"Name="/WebAnalysis/*"/>

To:

<Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid"Name="/WebAnalysis/ServerConsole/*" /><Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid"Name="/WebAnalysis/templates/*" /><Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid"Name="/WebAnalysis/hfmtemplates/*" /><Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid"Name="/WebAnalysis/hitemplates/*" /><Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid"Name="/WebAnalysis/processor" /><Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid"Name="/WebAnalysis/servlet/*" /><Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid" Name="/WebAnalysis/modules/*" /><Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid"Name="/WebAnalysis/resources/*" /><Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid"Name="/WebAnalysis/DirectoryServlet" /><Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid"Name="/WebAnalysis/config" />


<Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid"Name="/WebAnalysis/wa_javadocs/*" /><Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid"Name="/WebAnalysis/" /><Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid"Name="/WebAnalysis/*.jsp" /><Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid"Name="/WebAnalysis/*.xml" /><Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid"Name="/WebAnalysis/*.jar" />

9 Add the Plugin Config variable to the registry under the path HKEY_LOCAL_MACHINE > SOFTWARE > IBM > WebSphere Application Server > 5.x.0.0 where x designates the version.

Set the value of the Plugin Config variable to the location of the configuration file. For example:<WAS_INSTALL_ROOT>\config\cells\plugin-cfg.xml

10 Restart all IIS services.

Testing Module AvailabilityTest the modules availability:

http://<server>:<port>/workspace/http://<server>:<port>/hr/http://<server>:<port>/WebAnalysis/

where <server> is the Apache http server machine hostname and <port> is the port specified by the Listen directive in Apache’s httpd.conf file. For default port numbers, see “Port Numbers” on page 51.

Accessing http://<server>:<port>/hr/ redirects your browser to:

http://<server>:<port>/workspace/index.jsp

You must start the Workspace application first. If Workspace is not yet deployed, or is not started, you receive an error. As a workaround, verify the Financial Reporting application has deployed successfully by accessing

http://<server>:<port>/hr/version.jsp

which returns the Financial Reporting internal build number.

Manually Deploying into WebSphere 6.1 179

A P P E N D I X

EManually Deploying into

WebSphere 6.1


Preparing the WebSphere Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180

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

Deploying Financial Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184

Deploying Web Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185

Configuring Apache or IBM HTTP with WebSphere 6.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187

Configuring Microsoft IIS with WebSphere 6.1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190


180 Manually Deploying into WebSphere 6.1


❍ Install Shared Services.


❍ Test the installation and make sure that you can log into Shared Services:


For example:



It is required that you run the Hyperion Configuration Utility and select both the Deploy to Application Server and Configure Web Server tasks. If these options were not selected, you must re-run Hyperion Configuration Utility.


Note: On UNIX systems, Reporting and Analysis should not be installed as root.

Preparing the WebSphere EnvironmentYou must have a configured Web server before proceeding. See IBM's document:

http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/topic/com.ibm.websphere.express.doc/info/exp/ae/tihs_localsetup.html WebSphere

WebSphere ND

➤ To prepare WebSphere ND:

1 Log in to the WebSphere Administrative Console for the profile that will host the Reporting and Analysis application servers.

2 Navigate to Application Servers.

3 Create a new application server for each module that will be deployed (freporting, webanalysis, workspace)

4 Start the new application server(s).

WebSphere BASE/Express

➤ To prepare Host WebSphere BASE/Express:

1 Start the default application server for the profile in which you wish to deploy Reporting and Analysis. For example, server1.

Deploying Workspace 181

2 Create a new application server for each module that will be deployed (freporting, webanalysis, workspace) by running the wsadmin.bat to get to the wsadmin prompt and enter a command. For example:

$AdminTask createApplicationServer myhostNode01 {-name freporting -templateName default }

Tip: You can use the wsadmin scripting host to interactively create a new server by passing the createApplicationServer task –interactive

3 Save changes using the wsadmin scripting client.

For example, $AdminConfig save

4 Restart the default application server.

For example, server1.

5 Start the new application server(s).

For example, freporting, webanalysis, workspace.

Add Virtual Host DefinitionsIf client machines will access Reporting and Analysis using a non-default HTTP port, such as 19000, the Reporting and Analysis default, the following procedure must be performed. Definitions must also be added for each application server transport.

➤ To add virtual definitions:

1 Log in to the WebSphere console for the profile containing your application servers.

2 Navigate to Environment > Virtual Hosts and click on default_host.

3 Click Host Aliases > New.

4 Specify the hostname or IP address of your Web server in Host Name, or * to allow access from any host.

5 Specify the HTTP port client machines will use to access Reporting and Analysis. For example, 19000.

6 Repeat the process to add each application server transport chain. For example, 9081, 9082, 9083.

Tip: Navigate to Application Servers > <Server Name> > Web Container Settings > Web container transport chains in the WebSphere console for the profile containing your application servers to view transport chain port definitions.

Deploying Workspace

➤ To deploy:


2 Navigate to Applications > Install New Application.


3 Supply the full server path to workspace.war; by default:

<BIPLUS_HOME>\InstallableApps\workspace.war

4 Specify /workspace as the context root, then click Next.

5 Select Pre-compile JSP and click Next.

6 Select the appropriate module to server mapping by highlighting the workspace application server, the desired web server instance, such as webserver1, and enabling the check-box next to the available module. Click Apply, then Next.

Note: Be sure to map the module to both an application server and web server.

7 Acknowledge the summary of actions to be performed, then click Finish to proceed with deployment.

Note: Due to the large size of the Workspace application, it is expected that deployment may take several minutes to complete. Do not interrupt the deployment process.

8 Click Save to Master Configuration after deployment completes.

Creating a WebSphere Shared Library for SAP AuthenticationIf Shared Services is configured to provide SAP authentication, Workspace must have the SAP Java and Native libraries added to its runtime environment.

➤ To create a WebSphere Shared Library:

1 Log in to the WebSphere Administrative Console.

2 In the left pane, navigate to Environment > Shared Libraries.

3 In the right pane choose the Server scope for Shared Libraries by clicking Browse Servers, and selecting Workspace.

4 Click Apply.

5 Click New.

6 Specify Name: SAP_LIBRARY.

7 Specify Classpath:

<HYPERION_HOME>\common\SAP\lib

substituting <HYPERION_HOME> with your actual install location.

8 Specify native library path:


substituting <HYPERION_HOME> with your actual install location.

9 Save changes to the Master Configuration.

Deploying Workspace 183




<WAS_PROFILE>\installedApps\<Cell_Node>\workspace_war\workspace.war\conf\context.properties

Note: In the same directory, you can start with context.properties.sample. Uncomment and set the value for each property.


Set “Y” if components are installed, “N” if components are not installed:




Financial Reporting (Reports)Interactive Reporting (HPSU)Performance Scorecard (HPS)Dashboard Development Services (ChangeManagement)Web Analysis (Analyzer)

3 Start or restart the Workspace application server.

Configuring Workspace

➤ To configure Workspace :

1 Navigate to Session Management > Enable Cookies for the application server instance where Workspace is deployed.

2 Change the Cookie Path from / to /workspace, then click OK.

3 Navigate to Java and Process Management > Process Definition > Java Virtual Machine for the application server instance where is deployed.

4 In Initial Heap Size, enter 256.

5 In Maximum Heap Size, enter 512.

Note: These values may not be optimal for your user load, and may need to be adjusted.


6 Add additional Generic JVM argument:

-Djava.awt.headless=false

7 Click OK, then save all changes.

8 Start or restart the application server.

9 Edit <BIPLUS_HOME>\bin\config.bat:

In the line:

DEPLOYMENT_PATH=$J(servletConfig.deploymentPath)

replace $J(servletConfig.deploymentPath) with the actual location of deployed Workspace application. The default is:

<WAS_PROFILE>\config\cells\<CELL>\nodes\<NODE>\servers\workspace_war.ear\workspace.war

Deploying Financial Reporting

➤ To deploy Financial Reporting:



3 Supply the full server path to HReports.ear and click Next. By default:


4 On Select installation options, verify that Precompile JavaServer Pages files is clear and click Next.

5 Select the appropriate module to server mapping by highlighting the freporting application server, the desired web server instance, such as webserver1, and enabling the check-box next to the two available Financial Reporting modules.

6 Click Apply, then Next.

Note: Be sure to map the modules to the correct application server and web server. The Web Server should be the same as selected during Workspace deployment.

7 Map virtual hosts for Web modules.

8 Acknowledge the summary of action to be performed, then click Finish to proceed with deployment.

9 Click Save to Master Configuration after deployment completes.

Configuring Financial Reporting

➤ To configure Financial Reporting :



2 Navigate to Session Management > Enable cookies for the application server instance where Financial Reporting is deployed.

3 Change the Cookie Path from / to /hr, then click OK.

4 Navigate to Java and Process Management > Process Definition > Java Virtual Machine for the application server instance where Financial Reporting is deployed.




7 Add the additional Generic JVM argument:


8 Copy the files listed below to:

<DEPLOYMENT_LOCATION>/WEB-INF/lib

Where <DEPLOYMENT_LOCATION> is the file-system path where the Financial Reporting Web Application (HReports.ear) was deployed.

From <BIPLUS_HOME>:

<BIPLUS_HOME>/lib/HReports.jar <BIPLUS_HOME>/lib/NetCharts.jar <BIPLUS_HOME>/lib/HyperionADMWidgets.jar <BIPLUS_HOME>/lib/commons-fileupload-1.0.jar

From <HYPERION_HOME>:

<HYPERION_HOME>/common/loggers/Log4j/1.2.8/lib/log4j-1.2.8.jar <HYPERION_HOME>/common/ADM/9.2.0/lib/adm.jar <HYPERION_HOME>/common/ADM/9.2.0/lib/ap.jar


10 Start or restart the freporting application server.


Deploying

➤ To deploy Web Analysis:

1 Log in to the WebSphere Administrative Console for the profile containing your application servers.


3 Supply the full server path to WebAnalysis.ear and click Next. By default:



4 Select Precompile JavaServer Pages files and click Next.

5 Select the appropriate module to server mapping by highlighting the webanalysis application server, the desired web server instance, such as webserver1, and enabling the check-box next to the available WebAnalysis module.

6 Click Apply, then Next.

Note: Be sure to map the modules to the correct application server and web server. The web server should be the same as selected during Workspace deployment.

7 Acknowledge the summary of actions to be performed, then click Finish to proceed with deployment.

8 Click Save to Master Configuration.

Environment VariablesThe Hyperion Configuration Utility prepares the JVM environment with the necessary environment variables for WebAnalysis to function correctly. Reporting and Analysis creates WebAnalysis.env which sets required environment variables at runtime. The file is located in:

<BIPLUS_HOME>\InstallableApps\config

Creating a WebSphere Shared Library for SAP Authentication and ReportingIf Shared Services is configured to provide SAP authentication, or if Web Analysis will report against SAP data sources, the SAP Java and Native libraries added to the Web Analysis runtime environment.

➤ To create a WebSphere Shared Library:


2 In the left pane, navigate to Environment > Shared Libraries.

3 In the right pane choose the Server scope for Shared Libraries by clicking Browse Servers, and selecting WebAnalysis.

4 Click Apply.

5 Click New.

6 Specify Name as: SAP_LIBRARY.

7 Specify Classpath as:

<HYPERION_HOME>\common\SAP\lib

where <HYPERION_HOME> is your actual install location.


8 Specify the native library path:


where <HYPERION_HOME> is your actual install location.

9 Save changes to the Master Configuration.

Configuring Web Analysis

➤ To configure Web Analysis:

1 Navigate to Session Management > Enable Cookies for the application server instance where Web Analysis is deployed.

2 Change the Cookie Path from / to /WebAnalysis, then click OK.

3 Navigate to Java and Process Management > Process Definition > Java Virtual Machine for the application server instance where Web Analysis is deployed.




6 Add additional Generic JVM argument:


7 Enter the following in Classpath, replacing <HYPERION_HOME> with your actual installed location:

<HYPERION_HOME>\common\JDBC\DataDirect\3.6\lib\hyjdbc.jar


9 Start or restart the application server.

Configuring Apache or IBM HTTP with WebSphere 6.1This section describes the configuring of Apache Server or IBM HTTP Server.

➤ To regenerate the Web server plug-in:

1 Log in to the WebSphere Administrative Console for the profile containing your application servers.

2 Navigate to Servers > Web servers.

3 Select your Web server, and click Generate Plug-in.

4 Copy:

<WAS_PROFILE>\config\cells\<CELL>\nodes\<NODE>\servers\<WEBSERVER>\plugin-cfg.xml


into:

<HTTP_HOME>\conf


Workspace:


<Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid" Name="/workspace/*"/>

To:

<Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid" Name="/workspace/cdsrpc"/><Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid" Name="/workspace/administration/*"/><Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid" Name="/workspace/browse/*"/><Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid" Name="/workspace/personalpages/*"/><Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid" Name="/workspace/viewmanager/*"/><Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid" Name="/workspace/jobmanager/*"/><Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid" Name="/workspace/ihtml/*"/><Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid" Name="/workspace/dataaccess/*"/><Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid" Name="/workspace/logon"/><Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid" Name="/workspace/logon/*"/><Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid" Name="/workspace/prefs"/><Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid" Name="/workspace/js/*"/><Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid" Name="/workspace/modules/*"/><Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid" Name="/workspace/resources/*"/><Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid" Name="/workspace/conf/*"/><Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid" Name="/workspace/media/*"/><Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid" Name="/workspace/BPMContext"/><Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid" Name="/workspace/wsrp4j/*"/><Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid" Name="/workspace/ResourceProxy"/><Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid" Name="/workspace/"/><Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid" Name="/workspace/*.jsp"/>


<Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid" Name="/workspace/*.jsv"/><Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid" Name="/workspace/*.jsw"/>

Web Analysis:


<Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid" Name="/WebAnalysis/*"/>

To:

<Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid" Name="/WebAnalysis/ServerConsole/*" /><Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid" Name="/WebAnalysis/templates/*" /><Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid" Name="/WebAnalysis/hfmtemplates/*" /><Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid" Name="/WebAnalysis/hitemplates/*" /><Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid" Name="/WebAnalysis/processor" /><Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid" Name="/WebAnalysis/servlet/*" /><Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid" Name="/WebAnalysis/modules/*" /><Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid" Name="/WebAnalysis/resources/*" /><Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid" Name="/WebAnalysis/DirectoryServlet" /><Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid" Name="/WebAnalysis/config" /><Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid" Name="/WebAnalysis/wa_javadocs/*" /><Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid" Name="/WebAnalysis/" /><Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid" Name="/WebAnalysis/*.jsp" /><Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid" Name="/WebAnalysis/*.xml" /><Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid" Name="/WebAnalysis/*.jar" />

6 Update httpd.conf:

a. Add the following Aliases to your Web server (IBM HTTP Server or Apache) httpd.conf for Workspace and Web Analysis static content, replacing <BIPLUS_HOME> with an actual BIPlus installation path:

Workspace:

Alias /workspace "<BIPLUS_HOME>\AppServer\InstalledApps\workspace_static"

Alias /wsmedia"<BIPLUS_HOME>\AppServer\InstalledApps\workspace_static\wsmedia"


Alias /InsightInstaller"<BIPLUS_HOME>\AppServer\InstalledApps\workspace_static\zeroadmin\component\Insight"

Web Analysis:

Alias /WebAnalysis"<BIPLUS_HOME>\AppServer\InstalledApps\WebAnalysis_static"

b. Insert the following lines at the end of file:

LoadModule was_ap20_module "<PLUG_IN_HOME>\bin\mod_was_ap20_http.dll"WebSpherePluginConfig "<HTTP_HOME>\conf\plugin-cfg.xml"

where <PLUG-IN_HOME> and <HTTP_HOME> are the real locations.

Configuring Microsoft IIS with WebSphere 6.1

➤ To configure:

1 Start the IIS application.

2 Create a new virtual directory for the Web site instance that you intend to work with WebSphere Application Server. These instructions assume that you are using the Default Web Site.

a. On the left navigation pane expand to Default Web Site. Right-click Default Web Site and select New > Virtual Directory to create the directory with a default installation.

b. In Adding a virtual directory wizard, perform the following steps:

i. Type sePlugins in the Virtual Directory Alias screen.

ii. Browse to the WebSphere Application Server <WAS_PLUGINS_INSTALL_ROOT>\bin directory in the Web Site Content Directory screen.

iii. Select Execute (such as ISAPI application or CGI) in the Virtual Directory Access Permissions screen.

iv. Click Finish to add the sePlugins virtual directory to your default Web site.

3 Add the Internet Services Application Programming Interface (ISAPI) filter into the IIS configuration:

a. Right-click Default Web Site in the tree on the left and click Properties.

b. In the Properties dialog, perform the following steps:

i. Go to the Internet Information Services tab.

ii. Go to the ISAPI Filters tab.

iii. Click Add to open the Filter properties window.

iv. In Filter Name, type iisWASPlugin.

v. In Executable, click Browse.

vi. Browse to the <WAS_PLUGINS_ROOT>\bin directory.

vii. Click iisWASPlugin_http.dll.

viii. Click OK until all open windows close.


4 Enable the Web server to run WebSphere Application Server extensions (IIS 6.0):

a. Expand the navigation pane to Web service extensions.

b. Click Web Service Extensions.

c. In the right side pane, click Add a new Web service extension.

d. Specify Extension name, for example, iisWASPlugin.

e. Add the full path to <WAS_PLUGINS_ROOT>\bin\iisWASPlugin_http.dll to Required Files by clicking Add.

f. Check Set extension status to Allowed.

g. Click OK.

5 Create IIS Virtual Directories for Workspace:

a. Open the Internet Information Service Manager, and expand Web Sites.

b. Right click the Web Site that will be used to proxy requests; for example Default Web Site.


d. Click Next, then specify workspace in the Alias field.


e. Provide the full path to the workspace_static directory in Path; for example: <BIPLUS_HOME>\AppServer\InstalledApps\workspace_static

f. Click Next.



i. Repeat the process to create a Virtual Directory called wsmedia that uses the full path to workspace_static\wsmedia. For example:

<BIPLUS_HOME>AppServer\InstalledApps\\workspace_static\wsmedia

j. Repeat the process, again, to create a Virtual Directory called InsightInstaller that uses the full path to workspace_static\zeroadmin\component\Insight. For example:

<BIPLUS_HOME>\AppServer\InstalledApps\\workspace_static\zeroadmin\ component\Insight

k. Configure MIME types for InsightInstaller virtual directory:

❍ Right click the InsightInstaller virtual directory and select Properties.

❍ Select HTTP Headers tab and click MIME Types.

❍ Add following Extension / MIME types pairs:

.bat / application/octet-stream

.exe / application/octet-stream

.ex_ / application/octet-stream

.msi / application/octet-stream

.boot / application/octet-stream

.hdr / application/octet-stream

.ini / application/octet-stream

.xpi / application/octet-stream


6 Create IIS Virtual Directories for Web Analysis:

a. Open the Internet Information Service Manager, and expand Web Sites.

b. Right click the Web Site that will be used to proxy requests. For example, Default Web Site.


d. Click Next, then specify WebAnalysis in the Alias field.


e. In Path, provide the full path to the WebAnalysis_static directory; for example:<BIPLUS_HOME>\AppServer\InstalledApps\\WebAnalysis_static

f. Click Next.



7 Generate the Web server plug-in:

a. Log in to the WebSphere Administrative Console for the profile containing your application servers.

b. Navigate to Servers > Web Servers.

c. If the IIS server you want to use with WebSphere is not in the list, add it to list:

i. Click New.

ii. Specify the Server Name; for example, IIS.

iii. Select Microsoft Internet Information Services (IIS) in the Type field.

iv. Specify the Host Name, where IIS installed.

v. Click Next two times.

vi. Specify the Web server Port client machines will use to access Reporting and Analysis; for example, 19000.

vii. Specify the WebSphere Plug-in installation location.

viii. Click Next, then Finish.

d. Select your Web server, and click Generate Plug-in.


Workspace:


<Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid"Name="/workspace/*"/>

To:

<Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid"Name="/workspace/cdsrpc"/><Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid"Name="/workspace/administration/*"/>


<Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid"Name="/workspace/browse/*"/><Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid"Name="/workspace/personalpages/*"/><Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid"Name="/workspace/viewmanager/*"/><Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid"Name="/workspace/jobmanager/*"/><Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid"Name="/workspace/ihtml/*"/><Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid"Name="/workspace/dataaccess/*"/><Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid"Name="/workspace/logon"/><Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid"Name="/workspace/logon/*"/><Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid"Name="/workspace/prefs"/><Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid"Name="/workspace/js/*"/><Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid"Name="/workspace/modules/*"/><Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid"Name="/workspace/resources/*"/><Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid"Name="/workspace/conf/*"/><Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid"Name="/workspace/media/*"/><Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid"Name="/workspace/BPMContext"/><Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid"Name="/workspace/wsrp4j/*"/><Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid"Name="/workspace/ResourceProxy"/><Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid"Name="/workspace/"/><Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid"Name="/workspace/*.jsp"/><Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid"Name="/workspace/*.jsv"/><Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid"Name="/workspace/*.jsw"/>

Web Analysis:


<Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid"Name="/WebAnalysis/*"/>

To:

<Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid"Name="/WebAnalysis/ServerConsole/*" /><Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid"Name="/WebAnalysis/templates/*" /><Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid"Name="/WebAnalysis/hfmtemplates/*" />


<Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid"Name="/WebAnalysis/hitemplates/*" /><Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid"Name="/WebAnalysis/processor" /><Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid"Name="/WebAnalysis/servlet/*" /><Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid" Name="/WebAnalysis/modules/*" /><Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid"Name="/WebAnalysis/resources/*" /><Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid"Name="/WebAnalysis/DirectoryServlet" /><Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid"Name="/WebAnalysis/config" /><Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid"Name="/WebAnalysis/wa_javadocs" /><Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid"Name="/WebAnalysis/" /><Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid"Name="/WebAnalysis/*.jsp" /><Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid"Name="/WebAnalysis/*.xml" /><Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid"Name="/WebAnalysis/*.jar" />

9 Create a text file named plugin-cfg.loc in the <WAS_PLUGINS_INSTALL_ROOT>\bin directory. The first line of the plugin-cfg.loc file identifies the location of plugin-cfg.xml.

For example:

C:\WebSphere\config\plugin-cfg.xml.

Note: The last line of the .loc file should be a blank line (carriage return).

10 Restart all IIS services.


1URL: Where <Web server> is the Web server machine hostname and <port> is the WebServer listen port; for example, 19000 for Apache, IBM HTTP Server, and 80 for Oracle HTTP Server and IIS.





Text: Hyperion Financial Reporting is available



ActiveX 195

A P P E N D I X

F FActiveX

In This Appendix Whitepaper . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196

Sample Policy File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197

196 ActiveX

WhitepaperHyperion delivers a Web-based, highly interactive user interface, which the Gartner Group calls Rich Internet Applications.

The goals:

● High interactivity

● Ease-of-use to end users

● Benefits of thin-client computing

● Minimization of round-trips to the server, to provide an application-like experience

The technology side of the industry uses Asynchronous JavaScript and XML (AJAX), to describe Rich Internet Applications. AJAX, the most commonly used approach to Web application development, is a set of technologies that can be used to develop rich Web applications.

Web applications implementations:

● Google maps

● Google GMail

● Flickr

● Amazon A9.com

● Reporting and Analysis

Technologies encompassed by AJAX:

● DHTML

● CSS

● DOM (Document Object Model) browser

● XML (Extensible Markup Language)

● CommunicatiXMLHttpRequest—a communication technique supported by newer browsers —joined with JavaScript on the client

AJAX technologies:

● Are browser-independent

● Are platform-independent

● Use W3C open standards

● Run in the native Web browser environment

● Do not require additional software be installed or configured on the client machine

Sample Policy File 197

Microsoft was a leader in establishing the DOM and XML object model and offered one of the first browser implementations of the technologies. When these capabilities were introduced, Microsoft elected to implement their support of XML and the XMLHttpRequest object through ActiveX technologies.

For Hyperion, and other applications built using these open standards technologies, to function properly, Internet Explorer must be configured to enable support for ActiveX technologies.

Hyperion does not download ActiveX components to the browser. Instead, only HTML, JavaScript, and XML are sent to and by the client browser.

Guidelines to enable XML components:

● Generally enable the ActiveX controls and plug-in execution by, in the browser security settings, setting "Run ActiveX controls and plug-ins" to Enable.

● Enable ActiveX controls and plug-in execution by adding the Project Reporting and Analysis site as a trusted site and changing the custom security settings for trusted sites.

● Provide group policies that define the controls required for handling XML (the MS XML parser and XMLHTTPRequest controls) and enable these administrator approved controls for all sites or for select trusted sites.

Note: Hyperion can provide guidance on how to add and implement these policies.

● All other ActiveX controls and plug-ins remain disabled. Group policies can be implemented by zone by enabling the controls for sites in the trusted zone.

● For Active X enabled controls, enable the setting "Script ActiveX controls marked safe for scripting".

Sample Policy FileThe components enable the XML parsing routines in Internet Explorer.

Sample policy file:

CLASS USERCATEGORY "Windows Components" CATEGORY "Internet Explorer" CATEGORY "Administrator Approved Controls" KEYNAME "Software\Policies\Microsoft\Windows\CurrentVersion\Internet Settings\AllowedControls"

POLICY "MS XML Parser" EXPLAIN "Enable the MSXML Parser for HTTP Requests" PART "MS XML 2" CHECKBOX VALUENAME {079AA557-4A18-424A-8EEE-E39F0A8D41B9} VALUEON NUMERIC 0 VALUEOFF NUMERIC 1 END PART PART "MS XML 3" CHECKBOX VALUENAME {2933BF90-7B36-11D2-B20E-00C04F983E60}

198 ActiveX

VALUEON NUMERIC 0 VALUEOFF NUMERIC 1 END PART PART "WinHttpRequest Component version 5.1" CHECKBOX VALUENAME {2087C2F4-2CEF-4953-A8AB-66779B670495} VALUEON NUMERIC 0 VALUEOFF NUMERIC 1 END PART PART "Microsoft.XMLHTTP and Microsoft.XMLHTTP.1.0" CHECKBOX VALUENAME {ED8C108E-4349-11D2-91A4-00C04F7969E8} VALUEON NUMERIC 0 VALUEOFF NUMERIC 1 END PART PART "Msxml2.XMLHTTP" CHECKBOX VALUENAME {F6D90F16-9C73-11D3-B32E-00C04F990BB4} VALUEON NUMERIC 0 VALUEOFF NUMERIC 1 END PART PART "Msxml2.XMLHTTP.2.6 and .3.0" CHECKBOX VALUENAME {F5078F1E-C551-11D3-89B9-0000F81FE221} VALUEON NUMERIC 0 VALUEOFF NUMERIC 1 END PART PART "Microsoft.XMLParser.1.0" CHECKBOX VALUENAME {D2423620-51A0-11D2-9CAF-0060B0EC3D39} VALUEON NUMERIC 0 VALUEOFF NUMERIC 1 END PART

;; Microsoft.XMLParser.1.0 {D2423620-51A0-11D2-9CAF-0060B0EC3D39};; Microsoft.XMLHTTP {ED8C108E-4349-11D2-91A4-00C04F7969E8};; Microsoft.XMLHTTP.1.0 {ED8C108E-4349-11D2-91A4-00C04F7969E8};; Msxml2.XMLHTTP {F6D90F16-9C73-11D3-B32E-00C04F990BB4};; Msxml2.XMLHTTP.2.6 {F5078F1E-C551-11D3-89B9-0000F81FE221};; Msxml2.XMLHTTP.3.0 {F5078F35-C551-11D3-89B9-0000F81FE221} ;; same as 2.6 above

END POLICY

END CATEGORY ;; AdminApproved END CATEGORY ;; Internet ExplorerEND CATEGORY ;; WindowsComponents

Index A 1

Index

AADM driver, enabling the, 74

AJAX, 196

Apache, configuring with WebSphere, 171

Application Layer, 13

Services Tier, 13

Web Tier, 13

application server host names, specifying, 64

Bbacking up repositories, 33

browsers

settings, 48

Web requirements, 41

Ccell documents, print, 50

Client Layer, 11

Common Administration Services, 16

components

client tier, 31

clustered, 46

database tier, 27

distributed, 46

middle tier, 30

replicated, 46

configuration files, 98

Configuration Utility

about, 67

application server deployment, 68

database configuration, 67

database user rights, 63

launching, 65

log file, 75

order of tasks, 64

ports for application servers, 68

post configuration tasks, ?? to 80

prerequisites, 23, 63

reconfiguration, 80

Shared Services registration, 66

troubleshooting, 75

upgrades, 64

configuring

Apache, 171

Apache with Weblogic, 116

completing module-specific configurations, 72

database software for the Repository, 34

Financial Reporting, 73

IBM DB2, 34

IBM Websphere, 53

installation, 33

Microsoft SQL Server, 37

Oracle, 38

Production Reporting engine for Interactive Reporting, 73

relational databases, 68

Web environment, 42

Workspace, 72

configuring Sharedd Services, 109

connections, ODBC, creating, 40

considerations, RDBMS, 33

context.properties for WebSphere 6.1, 183

context.properties, forWebLogic 9.1, manual deployment, 138

cookie path, 184

cookie path, changing, 167

custom install, 60

customizing service ports for Reporting and Analysis, 72

2 Index D

Ddatabases

creating users, 38

layer, 18

repository size recommendations, 34

supported in Migration Utility, 91

to store metadata, 37

default cookie path, changing, 167

deploying

Financial Reporting into Websphere, 165, 168

Web Analysis into Websphere, 165, 168

Workspace Web Application with WebSphere, 162

deregistering Reporting and Analysis from Shared Services, 66

distributed components, 46

DMZ support, firewall, 43

Eenabling

HTTP Server plug-in, 71

Planning ADM driver, 74

UTF-8 encoding, 168

environment variables

TEMP, 47

Web Analysis, 142

Windows, 37, 40

error messages, 39

FFinancial Reporting, 99, 184

completing configurations, 73

deploying into WebLogic, 114 to 115

enabling the Planning ADM driver, 74

HReports.ear, 101

manual deployment

WebLogic, 139

print service configuration, 74

Report Server, configuring, 75

workspace, print service, and scheduler, 75

Financial Reporting Servers, 15

Financial Reporting,

deploying Financial Reporting, 99

firewalls

configurations, 44

DMZ, 43

Web server installation and, 42

functional services, 15

GGSM host and port, specifying, 73

Hhardware, requirements, 26

heap size, adjusting, 165, 169

high-level task flow, 20

host name, logical values, 166, 169

HTTP connector plug-in ports, specifying, 64

HTTP Server plug-in

Configuration Utility support, 71

enabling, 71

manual support, 72

requirements, 41

Hyperion Home

changing the location, 58

defining a location, 58

overview, 58

Hyperion License Server, 20, 56

Hyperion System 9 BI+

Reporting Solution Architecture, 11

Hyperion System 9, about, 10

IIBM DB2

configuring, 34

troubleshooting, 34

Version 7.2 configuration tasks, 34

Impact Manager Services, 16

installation wizards, using, 57

installers for Reporting and Analysis, 57

Interactive Reporting Services, 15

JJava Virtual Machine, 49

JDBC driver, and IBM DB2, 36

Llaunching Reporting and Analysis modules, 79

Index M 3

LIBPATH, 40

License Server, 20, 56

limitations, to distributing and replicating components, 47

login testing, shared services provisioning, 78

Mmaintenance, service packs, 48

management services, 14

manual deployment, 96 to 99, 101, 103 to 104, 106, 180 to 181, 183 to 184, 186 to 187

Microsoft SQL Server

configuring, 37

login, 37

Migration Utility

after installing, 92

installing, ?? to 92

overview, 90

migration, repository, 33

module installers, overview, 57

OOC4J instance, 99, 101

ODBC connections, creating, 40

OHS routing for Workspace, 97

Oracle

configuring, 38

error messages, 39

Oracle 10g Release 3, 95 to 99, 101, 103 to 104, 106, 109

PPerformance Scorecard Services, 16

PHYSNAME, 37

planning

client-tier components, 31

database tier components, 27

installation, ?? to 53

middle-tier components, 30

port number, changing, 80

prepare WebSphere environment, 180

prerequisites, 33, 180

print

cell documents, 50

requirements, 50 to 51

print service configuration, 74

privileges, granting, 38


installing, 48

Service, 16

provision the native Shared Services, 78

provisioning an administrator, 78

RRDBMS, considerations, 33

replicated components, 46

Report Server, configuring, 75

Reporting, 10

repository

backup, 33

databases, size recommendations, 34

migration, 33

requirements

hardware, 26

HTTP Server, 41

print, 50 to 51

software, 27

temporary space, 47

third party, 32

Web browsers, 41

web client, 31

reviewing selected components, 60

Ssample policy file, 197

SAP as an authentication provider, 96

SAP authentication

shared library for, 186

scheduler, configuring

configuration, 75

secure sockets-capable servers, 42

security

Interactive Reporting, 45

overview, 43

server

Java Virtual Machine, 49

Servers, 68

services

Common Administration, 16


Impact Manager, 16

4 Index T

Interactive Reporting, 15

management, 14

Performance Scorecard, 16

Production Reporting, 16

starting up, 76

tier summary, 17

shared pool size, Oracle and, 39

Shared Services

provisioning an administrator, 78

Single Sign-on, 106

single sign-on, 109

single sing-on

Oracle, 109

Smart View Services, 17

software requirements, 27

space requirements, temporary, 47

specifying

application server host names, 64

GSM host and port, 73

HTTP connector plug-in ports, 64

SQL Server, configuring, 37

system requirements

Migration Utility, 90

Ttemporary space, requirements, 47

testing

Workspace Web application, 164

testing module availability, 110, 159

third party requirements, 32

Uuninstalling

prerequisites, 82

updating configuration files, 98

Upgrading, 86

Upgrading, prerequisites, 86

user provisioning, 43

Migration Utility, 90

Vvirtual host definitions, 181

WWeb Analysis, 101, 185 to 187

configuring WebLogic, 114 to 115

deploying into WebLogic, 114 to 115

environment variables, 165, 168

Web Analysis.ear, 103

WebLogic 9.2, manual deployment, 143

Web browsers requirements, 41

Web browsers, requirements, 41

web client requirements, 31

Web server, 104

WebLogic

configuring

Apache, 116

Financial Reporting, 114 to 115

production mode, 112

Web Analysis, 114 to 115

testing connections, 129

WebLogic 9.2

manual deployment, 135

WebLogic 9.2, manual deployment


Web Analysis, 142 to 143

web-server plug-in, enabling, 71

WebSphere, 171

configuration requirements prior to installation, 42

configuring Apache configuring

Apache with Websphere Application Server, 171

deploying workspace, 162

enabling UTF-8 encoding, 168

testing connections, 178

Web Analysis environment variables, 168

WebSphere 6.1, 180 to 181, 183 to 184, 186 to 187

WebSphere 6.1, manual deployment, 180, 185

Whitepaper, 196

wizards, 57

Workspace, 181, 183

completing configurations, 72

configuring

Production Reporting engine for Interactive Reporting, 73

creating context.properties, 97

customizing

context path, 72

service ports, 73

Index W 5

deploying into

WebSphere, 162

deployment, 135

specifying the GSM host and port, 73

starting after deploying with WebSphere, 164

Web application, 162

WorkspaceOC4J instance, 95