HYPERION® REPORTING AND ANALYSIS FINANCIAL REPORTING™, INTERACTIVE REPORTING, PRODUCTION REPORTING, WEB ANALYSIS RELEASE 9.2.1
INSTALLATION GUIDE FOR UNIX 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
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 ...... 32 Configuration Procedures ...... 32 RDBMS Considerations ...... 33 Updating the C++ Runtime Environment for AIX ...... 40 SAP Data Source Access and Authentication ...... 40 Creating ODBC Connections ...... 41 Web Environment ...... 41 Security ...... 43 Distributed and Replicated Components ...... 46 Installing Considerations ...... 47 Configuring a Production Reporting Server Installation ...... 48 Considerations ...... 48 Creating a Reporting and Analysis User Account ...... 49
Contents 1 Browser Settings ...... 50 Module-specific Prerequisites ...... 50 Financial Management ...... 50 Financial Reporting ...... 51 Production Reporting ...... 53 Port Numbers ...... 53 Default Port Numbers for Remote Method Invocation (RMI) Servers ...... 54 AJP Connector Ports for Reporting and Analysis ...... 55 Configuring IBM WebSphere ...... 55
CHAPTER 4 Installing Reporting and Analysis ...... 57 Prerequisites ...... 58 Reporting and Analysis Installers ...... 58 Reporting and Analysis Module Installers ...... 59 Using Installation Wizards ...... 59 Hyperion Home ...... 60 Hyperion Home Location ...... 60 Changing the Hyperion Home Location ...... 60 Installing Reporting and Analysis ...... 61
CHAPTER 5 Configuring and Setting Up Reporting and Analysis...... 63 Post Installation Tasks ...... 64 Configuring SAP Data Source Access and Authentication ...... 64 Configuring X11 for UI Services for Financial Reporting and Web Analysis ...... 64 Using the Configuration Utility ...... 67 Prerequisites ...... 68 Task Sequence ...... 68 Configuring Product Upgrades ...... 68 Specifying Application Server Hostnames and HTTP Connector Plug-in Ports ...... 69 Launching the Configuration Utility ...... 69 Registering Reporting and Analysis with Shared Services ...... 70 Deregistering Reporting and Analysis with Shared Services ...... 71 Configuring Relational Storage ...... 71 Deploying Reporting and Analysis to Application Servers ...... 72 Undeploying from an Application Server ...... 75 Enabling the HTTP Server Plug-in ...... 75 Configuration Utility HTTP Server Plug-in Support ...... 75 HTTP Server Plug-in Manual Support ...... 76 Completing Module-Specific Configurations ...... 76 Workspace Configurations ...... 76 Completing Financial Reporting Configurations ...... 78 Completing Configuration Utility ...... 79
2 Contents Configuration Troubleshooting ...... 79 Post Configuration Tasks ...... 80 Verifying Startup Dependencies ...... 80 Starting Shared Services ...... 81 Provision a Reporting and Analysis Administrator User ...... 82 Production Reporting Post Configuration Tasks ...... 83 Adding Drivers for Web Analysis RDBMS Connectivity ...... 84 Launching Reporting and Analysis Modules ...... 84 Changing the Apache HTTP Server Listen Port ...... 84 Reconfiguration ...... 85
CHAPTER 6 Uninstalling Reporting and Analysis...... 87 Prerequisites ...... 88 Uninstalling ...... 88
CHAPTER 7 Upgrading to Reporting and Analysis 9.2.1 ...... 89 Upgrading from 8.x to 9.2.1 ...... 90 Upgrading from 9.x to 9.2.1 ...... 90 Prerequisites ...... 90 Upgrading ...... 90
CHAPTER 8 Installing the Reporting and Analysis Migration Utility ...... 93 Migration Utility ...... 94 Requirements ...... 94 Supported Source Databases ...... 95 Installing the Migration Utility ...... 95 After Installing the Migration Utility ...... 96
APPENDIX A Manually Deploying into Oracle 10g Release 3 (10.1.3.1.0) ...... 97 Prerequisites ...... 98 Deploying Workspace Web Application ...... 98 Creating an OC4J Instance ...... 98 Configuring an OC4J Instance ...... 99 Deploying workspace.war ...... 99 Configuring Workspace ...... 100 Deploying Financial Reporting ...... 103 Creating an OC4J Instance ...... 103 Configuring an OC4J Instance ...... 104 Deploying HReports.ear ...... 105 Deploying Web Analysis ...... 106 Creating an OC4J Instance ...... 106 Configuring an OC4J Instance ...... 107 Deploying WebAnalysis.ear ...... 108
Contents 3 Configuring Oracle HTTP Server for Oracle 10g Release 3 ...... 109 Configuring Oracle Single Sign-on on Oracle 10g Release 3 ...... 111 Prerequisites ...... 111 Configuring the Oracle Application Server ...... 111 Configuring Shared Services ...... 114 Testing Module Availability ...... 115
APPENDIX B Manually Deploying into Sun Java System Application Server Enterprise Edition 8.1...... 117 Prerequisties ...... 118 Creating a Node Agent ...... 118 Creating a New Standalone Server Instance ...... 119 Customizing a Standalone Server Instance ...... 120 Editing Standalone Server Instance JVM Options for Workspace ...... 122 Editing Standalone Server Instance JVM Options for Financial Reporting ...... 122 Financial Reporting Environment Variables ...... 123 Editing Standalone Server Instance JVM Options for Web Analysis ...... 123 Web Analysis Environment Variables ...... 124 Deploying Reporting and Analysis ...... 124 Deploying Workspace Web Applications ...... 124 Deploying Financial Reporting Enterprise Applications ...... 125 Deploying Web Analysis Enterprise Applications ...... 125 Post Configuration Tasks ...... 126 Configuring Workspace Web Applications After Deployment ...... 126 Configuring Web Analysis Enterprise Applications after Deployment ...... 126 Testing Web Applications ...... 127 Generating the JES Load Balancing Plug-in Configuration File ...... 128 Sun Web Server 6.1 Configuration ...... 129 Default Sun Java Enterprise Application Server Locations ...... 132 Testing Module Availability ...... 132
APPENDIX C Manually Deploying into WebLogic 8.1.4 ...... 133 Prerequisites ...... 134 Modifying startWebLogic.sh ...... 134 Deploying Workspace into WebLogic ...... 135 Post Deployment for Workspace ...... 135 Deploying Financial Reporting into WebLogic ...... 136 Post Deployment for Financial Reporting ...... 136 Deploying Web Analysis into WebLogic ...... 137 Pre-Deployment for Web Analysis ...... 137 Deploying Web Analysis ...... 137 Configuring Apache with BEA WebLogic ...... 138 Testing the Connection ...... 144
4 Contents APPENDIX D Manually Deploying into WebLogic 9.2...... 145 Prerequisites ...... 146 Preparing the Environment ...... 146 Preparing a One-Host Environment ...... 146 Preparing a Clustering Environment ...... 147 Deploying Workspace into WebLogic ...... 149 Pre-deployment for Workspace ...... 149 Deploying Workspace ...... 150 Post-deployment for Workspace ...... 152 Deploying Financial Reporting into WebLogic ...... 153 Pre-deployment for Financial Reporting ...... 153 Deploying Financial Reporting ...... 154 Post-deployment for Financial Reporting ...... 156 Deploying Web Analysis into WebLogic ...... 156 Pre-deployment for Web Analysis ...... 156 Verifying Web Analysis Environment Variables ...... 157 Deploying Web Analysis ...... 158 Configuring a Web Server for WebLogic 9.2 ...... 160 Configuring the Apache Web Server Plug-in ...... 160 Testing Module Availability ...... 167
APPENDIX E Manually Deploying into WebSphere 5.1.1.7 ...... 169 Prerequisites ...... 170 Deploying Workspace into WebSphere ...... 170 Deploying Workspace ...... 170 Configuring Workspace Web Application ...... 171 Creating context.properties ...... 172 Starting Workspace Web Application ...... 172 Deploying Financial Reporting into WebSphere ...... 173 Deploying ...... 173 Configuring ...... 175 Deploying Web Analysis into WebSphere ...... 176 Pre-Deployment for Web Analysis ...... 176 Deploying ...... 176 Configuring ...... 178 Configuring Apache or IBM HTTP with WebSphere 5.1 ...... 179 Testing Module Availability ...... 182
APPENDIX F Manually Deploying into WebSphere 6.1 ...... 183 Prerequisites ...... 184 Preparing the WebSphere Environment ...... 184 WebSphere ND ...... 184 WebSphere BASE/Express ...... 184
Contents 5 Add Virtual Host Definitions ...... 185 Deploying Workspace ...... 185 Creating a WebSphere Shared Library for SAP Authentication ...... 186 Creating context.properties ...... 187 Configuring Workspace ...... 187 Deploying Financial Reporting ...... 188 Configuring Financial Reporting ...... 189 Deploying Web Analysis ...... 190 Deploying ...... 190 Environment Variables ...... 190 Creating a WebSphere Shared Library for SAP Authentication and Reporting ...... 191 Configuring Web Analysis ...... 192 Configuring Apache or IBM HTTP with WebSphere 6.1 ...... 192 Testing Module Availability ...... 195
APPENDIX G ActiveX ...... 197 Whitepaper ...... 198 Sample Policy File ...... 199
6 Contents Chapter Reporting and Analysis 1 Architecture Overview
In This Chapter Hyperion ...... 10 Reporting and Analysis Reporting Solution ...... 10 Reporting and Analysis Reporting Solution Architecture...... 11
Reporting and Analysis Architecture Overview 9 Hyperion Hyperion 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 Solution Reporting 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™.
10 Reporting and Analysis Architecture Overview Reporting and Analysis Reporting Solution Architecture The 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 Layer The 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
Reporting and Analysis Reporting Solution Architecture 11 ● 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
12 Reporting and Analysis Architecture Overview ❍ 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 Layer The 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 Tier The 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 Tier The 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.
Reporting and Analysis Reporting Solution Architecture 13 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.
14 Reporting and Analysis Architecture Overview 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
Reporting and Analysis Reporting Solution Architecture 15 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.
16 Reporting and Analysis Architecture Overview 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
Reporting and Analysis Reporting Solution Architecture 17 LSC or RSC Service1 Type Name Instances 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
Note: 1 LSC—Local Service Configurator and RSC—Remote Service Configurator.
Database Layer Architecturally, 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”.
18 Reporting and Analysis Architecture Overview Chapter Installation Sequence 2
In This Chapter High-level Task Flow...... 20 Reporting and Analysis Installation Checklist ...... 21 Configuration Utility Information ...... 23
Installation Sequence 19 High-level Task Flow The 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 .
Step Instruction Product Component Documentation
1 Install Shared Services and configure the Shared Services installer Shared Services Installation Guide Shared Services application server and Hyperion Configuration Utility™ RDBMS.
2 Configure Shared Services to authenticate Shared Services External Shared Services Installation Guide user names that are stored externally in Authentication Configuration Console LDAP, Active Directory, or Windows NT LAN Manager, enabling single sign-on.
Note: You must finish steps 1 and 2 before continuting.
3 Install Hyperion products, such as Hyperion product installers Product installation guides Reporting and Analysis.
4 Activate and configure Hyperion products Hyperion Configuration Utility Product installation guides and register them with Shared Services. You can configure multiple products at one time, if they are installed on the same computer.
5 Create projects, add applications to Shared Services User Management Shared Services User Management projects, and provision users for Console™ Guide applications.
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.
20 Installation Sequence 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- Hyperion Shared Services Installation Guide Delivery site. 3. Install Shared Services and configure the Shared Services Application server and RDBMS.
(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 Hyperion Shared Services Installation Guide 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.
INSTALLATION TASKS REFERENCE
Install Reporting and Analysis: For each machine:
● Run appropriate Reporting and Analysis installers. The Reporting and Analysis Chapter 4, “Installing 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 Chapter 5, “Configuring and Setting Up configuration tasks. Reporting and Analysis”
Reporting and Analysis Installation Checklist 21 Table 3 Reporting and Analysis Installation Checklist (Continued)
POST INSTALLATION TASKS REFERENCE
Configure SAP BW Driver “Configuring SAP Data Source Access and Authentication” on page 64
Configure X11 For UI Services “Configuring X11 for UI Services for Financial Reporting and Web Analysis” on page 64
CONFIGURATION TASKS REFERENCE
1. Activate and register with Shared Services using the Hyperion Configuration “Registering Reporting and Analysis with Utility. Shared Services” on page 70
❍ Activate Reporting and Analysis.
❍ Specify the Shared Services server location. 2. Configure relational databases and repositories. “Configuring Relational Storage” on page 71 3. Auto-deploy Reporting and Analysis modules to application servers “Deploying Reporting and Analysis to (recommended) Application Servers” on page 72 OR If preferred, select the Manual Deployment option to manually configure the deployment. Appendix A, “Manually Deploying into Oracle 10g Release 3 (10.1.3.1.0)” ❍ Manually deploy into Oracle 10g Appendix C, “Manually Deploying into ❍ Manually deploy into WebLogic 8.1 WebLogic 8.1.4” ❍ Manually deploy into WebSphere 5.0.2 or 5.1 Appendix E, “Manually Deploying into Note: Do not select “Deploy as Service” if you have selected “Manual Deployment”. WebSphere 5.1.1.7”
POST-CONFIGURATION TASKS REFERENCE
1. Verify the order of starting Services. “Verifying Startup Dependencies” on page 80 2. Provision a Reporting and Analysis Administrator User. “Provision a Reporting and Analysis Administrator User” on page 82 3. For Production Reporting, set the Environment variables and becreate the executables. “Adding Drivers for Web Analysis RDBMS Connectivity” on page 84 4. For Web Analysis, add drivers for RDBMS connectivity. “Launching Reporting and Analysis Modules” 5. Launch Reporting and Analysis Modules. on page 84
22 Installation Sequence 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 ______
Configuration Utility Information 23 24 Installation Sequence Chapter Planning the Installation 3
In This Chapter Hardware Requirements...... 26 Software Requirements ...... 27 Prerequisites ...... 32 Module-specific Prerequisites...... 50 Port Numbers ...... 53
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.
Planning the Installation 25 Hardware Requirements This 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*
Studios: Web Analysis 1Ghz, 1 GB RAM, 2GB available disk space Financial Reporting Report Server 512 MB Minimum - 1024 MB suggested, 200 MB available disk space Scheduler Server 512 MB Minimum - 1024 MB suggested, 100 MB available disk space Print Server 512 MB Minimum - 1024 MB suggested, 100 MB available disk space Interactive Reporting 1.2 GHz, 256 MB RAM, 350 MB available disk space Interactive Reporting Web Client 1.2 GHz, 220 MB RAM, 30 MB available disk space Production Reporting 4-way 1.0 GHz (or comparable/better), 256 MB RAM, 100 MB available disk space
Machine #1: 4-way 900 MHz (or comparable/better)
Workspace ❍ Solaris—UltraSparcIII
Financial reporting Web App ❍ AIX—POWER3
Web Analysis ❍ HP-UX—PA-RISC
❍ Linux—x86 (2.0 GHz or comparable/better) 8GB RAM 20GB available disk space
Machine #2: 4-way 900 MHz (or comparable/better)
Shared Services ❍ Solaris—UltraSparcIII
Reporting and Analysis Base ❍ AIX—POWER3 Services ❍ HP-UX—PA-RISC Financial Reporting Services ❍ Linux—x86 (2.0 GHz or comparable/better) Interactive Reporting Services 8GB RAM Production Reporting Service 50GB 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.
26 Planning the Installation Software Requirements
Software Support for Apache Tomcat Hyperion 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
Table 1 Software Requirements for Database Layer
Production Web Financial Interactive Component Requirement Reporting Analysis Reporting 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
● SAP BW 3.1 or 3.5 (BAPI connectivity) X X X
● SAP R/3 4.5 or 4.6 X
Hyperion ● Financial Management 4.0.1 or 4.1.x X X Applications
● Planning 4.0.1 or 4.1.x X X
Supported One server: relational repositories
● Microsoft SQL Server 2000 SP 3a X (Enterprise or Standard edition) ● Microsoft SQL Server 2005 X
● Oracle 9i - 9.2.0.5 or 10g - 10.1.0.5 (For X Web Analysis - with Native JDBC drivers, or OCI drivers)
● IBM DB2 Release 8.2 (for Web Analysis - X using JDBC 2.0 with Web Analysis)
Relational data One server: sources
Software Requirements 27 Table 1 Software Requirements for Database Layer (Continued)
Production Web Financial Interactive Component Requirement Reporting Analysis Reporting Reporting Repository
● Microsoft SQL Server 2000 SP 3a XX (Enterprise or Standard edition) ODBC
● Microsoft SQL Server 2000 SP 3a XX (Enterprise or Standard edition) JDBC
● Microsoft SQL Server 2000 SP 3, with MS X SQL Server JDBC drivers
● Microsoft SQL Server 2005 SP1 X 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 XX X Edition ODBC Connectivity
● IBM DB Release 8.2 Enterprise Server X Edition JDBC Connectivity
● IBM DB Release 8.2 Enterprise Server X Edition DB2 Connectivity
● Informix 9.2 and later ODBC X
● 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
1 ● Sybase 12.x ASE ODBC X
28 Planning the Installation Table 1 Software Requirements for Database Layer (Continued)
Production Web Financial Interactive Component Requirement Reporting Analysis Reporting Reporting Repository
● Sybase 12.x ASE JDBC X
1 ● Sybase 12.5.x ASE ODBC XX
● Sybase 12.5.x ASE JDBC X
● Sybase 12.5.x ASE SDK X
● Teradata Version 2 Release 4 and Higher X ODBC
● Teradata Version 2 Release 4 and Higher X Teradata SDK
● Teradata Version 2 Release 5 and Higher X ODBC
● Teradata Version 2 Release 5 and Higher X Teradata SDK
● Teradata 4.1 JDBC X
SQL Grid ● Merant drivers for SQL grid X Relational Connectivity
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 drivers 2JDBC drivers are only required for Virtual Cube connections for relational drill-through.
Software Requirements 29 Middle Layer Components
Table 2 Middle Layer Software Requirements
Production Web Financial Interactive Component Requirement Reporting Analysis Reporting Reporting
Operating System Servers:
● Sun Solaris 9 or 10 X X X X
● IBM AIX 5.2 or 5.3 X X X X
● HP-UX 11i RISC: v1 (specifically 11.11) X X X X
● HP-UX 11i Itanium: v2 (specifically 11.23) X
● Redhat Linux AS 4.0 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
● Java System Application Server Enterprise Edition 8.1 X X X
Runtime clients:
● Financial Management 4.0.x , 4.1.x, or 9.2.0.x. X X
● Planning 4.0.x 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.
● SAP Java Connector 2.1.6 X X
Note: The Financial Management, Analytic Services, and Planning Runtime Client should match the application release number.
30 Planning the Installation Client Layer Components
Table 3 Web Client Software Requirements
Production Web Financial Interactive Component Requirement Reporting Analysis Reporting Reporting
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 X
Note: Must be manually configured
● Sun Java Plug-in 1.4.2_10 X
● Sun Java Plug-in 1.4.2_12 (HP-UX RISC and X Itanium)
● Sun Java Plug-in 1.4.2_15 (Solaris/Linux) X
● Sun Java Plug-in 1.4.2.150 ca142-20070317 X (AIX)
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 4 Third Party Products
Production Web Financial Interactive Component Requirement Reporting Analysis Reporting Reporting
3rd Party Office 2000 X Components Excel 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
Software Requirements 31 Table 4 Third Party Products
Production Web Financial Interactive Component Requirement Reporting Analysis Reporting Reporting
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
Prerequisites The following sections describe the tasks you must complete before installing Reporting and Analysis:
● “Configuration Procedures” on page 32
● “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 Procedures These 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.
32 Planning the Installation RDBMS Considerations Depending 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 41
Backing Up a Repository Hyperion 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 home 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.
● Open odbc.ini file and add for DB2 UDB: Collection= Location=
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.
Prerequisites 33 Configuring Database Software for the Reporting and Analysis Repository Repository 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.
➤ 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.
34 Planning the Installation 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_user GRANT CONNECT ON DATABASE TO USER db2_user GRANT CREATETAB ON DATABASE TO USER db2_user
UPDATE DBM CFG USING DRDA_HEAP_SZ 2048 UPDATE DATABASE CONFIGURATION FOR database_name USING STMTHEAP 8096 UPDATE DATABASE CONFIGURATION FOR database_name USING APPLHEAPSZ 8096 UPDATE DATABASE CONFIGURATION FOR database_name USING APP_CTL_HEAP_SZ 8096
TERMINATE
Prerequisites 35 Where: Variable Name DB2 Description Example
db2_user User who owns the Reporting and biplus Analysis db schema
database_name Database name BIPLUS
bufferpool_name Bufferpool BIPLUS_BP
tablespace_name Tablespace BIPLUS_TS
system_container Container /db2data/BIPLUS_TS
tmp_bufferpool_name Bufferpool TMP_BIPLUS_BP
tmp_tablespace_name Tablespace TMP_BIPLUS_TS
tmp_system_conatainer DB2 container /db2data/TMP_BIPLUS_TS
Note: Do not start _name variables with SYS.
Caution! The default tablespace for the database user that owns the Reporting and Analysis 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. 8 Set all necessary environment variables: Set DB2COMM, DB2INSTANCE, DB2DIR, and:
● Solaris, Linux—LD_LIBRARY_PATH
● AIX—LIBPATH
● HP-UX—SHLIB_PATH
Note: Connectivity to IBM DB2 on AIX 5.2 may fail if the installation is done on a remotely mounted location (a directory location mounted over the network). To resolve this issue, copy recursively the
36 Planning the Installation 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_pages go
2 Create a database in which to store the metadata. CREATE DATABASE biplus ON device_name = size_in_MB go
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 mypassword go
Note: The password for the Microsoft SQL Server repository database should not be null.
5 Create the database user: use biplus go sp_adduser biplus go
Prerequisites 37 6 Grant privileges to the user: use biplus go grant create table to biplus go grant select on sysobjects to biplus go grant create procedure to biplus go grant create view to biplus go grant create functioncreate functioncreate function to biplus go
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 REUSE LOGFILE
GROUP 1 ('diskx:log1.log', 'disky:log1.log') SIZE 50K, GROUP 2 ('diskx:log2.log', 'disky:log2.log') SIZE 50K
MAXLOGFILES 5 MAXLOGHISTORY 100 MAXDATAFILES 10 MAXINSTANCES 2 ARCHIVELOG CHARACTER SET AL32UTF8 NATIONAL CHARACTER SET AL16UTF16 DATAFILE
'disk1:df1.dbf' AUTOEXTEND ON, 'disk2:df2.dbf' AUTOEXTEND ON NEXT 10M MAXSIZE UNLIMITED
38 Planning the Installation DEFAULT TEMPORARY TABLESPACE temp_ts UNDO TABLESPACE undo_ts SET 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.
Prerequisites 39 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 variables:
● ORACLE_HOME
● $ORACLE_HOME identifies the location of the Oracle database software.PATH
● Solaris/Linux—LD_LIBRARY_PATH
● AIX— LIBPATH
● HP—SHLIB_PATH
Updating the C++ Runtime Environment for AIX Financial Reporting and Web Analysis require an updated C++ runtime environment version on AIX 5L.
Note: To determine the current version of your C++ runtime environment, run "lslpp -l | grep xlC.aix50".
➤ To obtain the update: 1 Go to the IBM technical support Web site: https://techsupport.services.ibm.com/server/aix.fdc?toggle=SEARCH 2 Enter the fileset, xlC.aix50.rte.6.0.0.7, or the PTF number, U489780, in the Search string field to locate the patch.
SAP Data Source Access and Authentication To 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 64.
40 Planning the Installation Creating ODBC Connections If 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
Web Environment The 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 42
● “Configuring a Web Environment” on page 42
HTTP Server Requirements The 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 75.
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 76
● Appendix B, “Manually Deploying into Sun Java System Application Server Enterprise Edition 8.1”
● Appendix C, “Manually Deploying into WebLogic 8.1.4”,
● Appendix E, “Manually Deploying into WebSphere 5.1.1.7”.
Application Server Setting All Reporting and Analysis Web applications should have session timeouts set to greater than 10 minutes.
Prerequisites 41 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 Environment Reporting 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 If you are using the IBM WebSphere application server, it is recommended that you use the same account to install, deploy, and execute Hyperion products you use to install WebSphere. Using the same account ensures that the Configuration Utility can successfully deploy Hyperion products to 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/
42 Planning the Installation Extract the archive you downloaded, and install only the GSKit7 package:
➤ To extract and install the GSKit7 package: 1 Extract HTTPServer.aix.2047.tar. 2 Run gskit.sh as the root user.
Security The following topics describe pre-installation security considerations:
● Shared Services
● Firewall and DMZ Support
Shared Services Shared 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 Support All 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
Prerequisites 43 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.
44 Planning the Installation 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).
Prerequisites 45 Distributed and Replicated Components Reporting 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
46 Planning the Installation 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 Considerations The following topics describe pre-installation installing considerations:
● “Satisfying Temporary Space Requirements” on page 47
● “Command Line Processor Considerations” on page 48
Satisfying Temporary Space Requirements The 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:
➤ To specify the directory used to store temporary file created by the install process, pass the argument -is:tempdir. For example, $ ./
where
➤ To perform a GUI installation from a remote X session, you must ensure the launching user's DISPLAY variable is properly initialized, and that the remote X server is accepting connections. It is recommended that this be tested before launching the Reporting and Analysis install, by running xlogo, xclock, or other small X program. For example: On the remote X server machine, enable connectivity from a host: $ xhost +
On the server where you install Reporting and Analysis: $ DISPLAY=
Prerequisites 47 ➤ To perform a console mode installation, pass the argument -console For example: # ./
Command Line Processor Considerations When installing from the Command Line Processor, the InstallShield uses /var as temporary space. However, since most users don’t have a lot of space allocated there, Hyperion recommends redirecting the temporary space to a temporary directory where the installer can uncompress and run, for example:
mkdir /home/user/tmp setup
where
Configuring a Production Reporting Server Installation If 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)
Considerations
● “UNIX Installation Mechanisms” on page 48
● “Fonts” on page 49
UNIX Installation Mechanisms In addition to the Java-based GUI installer, you can use these mechanisms to install Reporting and Analysis on UNIX systems:
● Virtual Network Computing (VNC)—A remote display system which enables you to view a computing desktop environment not only on the computer where it is running, but from anywhere on the Internet and from a wide variety of computer architectures. See this site: http://www.uk.research.att.com/vnc/
48 Planning the Installation ● Exceed®—PC X enterprise connectivity software that enables you to connect Microsoft Windows desktops to UNIX servers and access UNIX applications.
● Command prompt installer —see “Command Line Processor Considerations” on page 48
Fonts Interactive Reporting Service must be configured with appropriate fonts to ensure that BQY documents in Workspace have a consistent look and feel with the Web Client. You must make Type1, TrueType, or OpenType fonts available to Interactive Reporting Service. The configured fonts must support characters for all intended languages. The Reporting and Analysis installer installs Andale WT font in
➤ To make Microsoft’s TrueType Web fonts available to Workspace: 1 Download the Microsoft TrueType Web fonts from: http://sourceforge.net/projects/corefonts/ or some other source. 2 Create a directory to store the font files. 3 If using downloaded Microsoft fonts, extract each file (*.exe) into the newly created directory using the cabextract utility located in INSTALL_HOME/bin/, as below: INSTALL_HOME/bin/cabextract -d directory CAB file
4 If you need a fonts.dir file, create a fonts.dir file in the directory containing the font files using the ttmkfdir utility. The ttmkfdir utility can be dowloaded from the following URL: http://packages.qa.debian.org/t/ttmkfdir.html 5 Add the fonts.dir directory to environment variable FONT_PATH, or add it to BQ_FONT_PATH environment variable inside INSTALL_HOME/bin/services.sh. This directory must contain fonts.dir. 6 Restart Interactive Reporting Service
Creating a Reporting and Analysis User Account For Reporting and Analysis to properly operate, it must be able to run using a user account. For security purposes, Hyperion suggests creating a new, unique user account for Reporting and Analysis named biplus. You may use an existing user account, as long as you use the same one for all installations.
Prerequisites 49 Note: Reporting and Analysis system permissions are the same as those of the user account with which it is associated.
You should not install Reporting and Analysis as a superuser because the services would then run with root privileges, thus creating a potential breach in system security. The Reporting and Analysis user account does not need root privileges.
Browser Settings Reporting 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 G, “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 Prerequisites Prerequisites:
● “Financial Management” on page 50
● “Financial Reporting” on page 51
● “Production Reporting” on page 53
Financial Management Financial 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.
50 Planning the Installation 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 Reporting The Print Server only runs on Microsoft Windows. Refer to the Hyperion Financial Reporting, Interactive Reporting, Production Reporting, and Web Analysis Modules Installation Guide for Windows. The following requisites apply to Financial Reporting:
Cell Attachment Support and Configuration Requirements The 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
Module-specific Prerequisites 51 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.
● 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 Requirements Disable:
● 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.
52 Planning the Installation Environment Variables On UNIX/Linux systems, the following environment variables must be properly initialized in order to run Financial Reporting objects that include metadata containing non-English characters:
● LANG
● LC_ALL
● ESSLANG (if Essbase is used as a data source)
➤ To initialize, use login scripts, or edit:
● LANG, LC_ALL:
● ESSLANG:
Production Reporting The following requisites apply to Production Reporting
Relinking the Hyperion Production Reporting Server Executables A C compiler is required to relink the Production Reporting Server executables for all platforms except Sun Solaris. For the AIX platform, a C++ compiler is required. If you need an installed C++ compiler, you can download the required C++ components from the following locations. For AIX, go to: http://www-1.ibm.com/support/docview.wss?uid=swg24001174 No changes to the Production Reporting Server linking scripts are required.
Port Numbers During 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 77. 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.
Port Numbers 53 If you do not change the default port number, the software is configured with these values:
Shutdown Port for Hyperion Product Listen Port SSL Listen Port 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
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
Default Port Numbers for Remote Method Invocation (RMI) Servers
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
54 Planning the Installation AJP Connector Ports for Reporting and Analysis The Apache JServ Protocol (AJP)
Hyperion Component AJP Connector pORT
Workspace 45002
Financial Reporting 8202
Web Analysis 16002
Configuring IBM WebSphere You must change the wsadmin.sh 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.
Port Numbers 55 56 Planning the Installation Chapter Installing Reporting and 4 Analysis
In This Chapter Prerequisites ...... 58 Reporting and Analysis Installers ...... 58 Using Installation Wizards ...... 59 Hyperion Home ...... 60 Installing Reporting and Analysis ...... 61
Installing Reporting and Analysis 57 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 Installers For 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, services
UIServices Web components related to Workspace, Financial Reporting, Interactive uiservices
Client Modules and components that are needed for the client desktop: Financial clientCD (Windows only) Reporting Studio, Interactive Reporting Studio, Production Reporting Studio, Activator, Remote, and Viewer
SQR Production Production Reporting module and components: Production Reporting DB2, DDO, repservices
Migrator Components that are needed for migrating data from previous Hyperion products migratorCD into the current release
58 Installing Reporting and Analysis Reporting and Analysis Module Installers
Production Web Applications (In Reporting (In UIServicesCD Client (In clientCD Folder, repservicesCD Services (In servicesCD Folder)2 Folder)2 Windows Only)2 Folder)2
Financial -Base Services -Workspace1 -Financial Reporting Studio Not needed Reporting -Financial Reporting Services: -Financial Reporting -Financial Reporting Server -Financial Reporting Print Service -Financial Reporting Scheduler Service
Interactive -Base Services -Workspace1 -Interactive Reporting Studio Needed for Reporting -Impact Management Services -Interactive Reporting -Dashboard Development Production Services Reporting job -Dashboard Development Services output viewing -Interactive Reporting Services: -Interactive Reporting Service -Data Access Service
Web Analysis -Base Services -Workspace1 Not needed Not needed
Production -Base Services -Workspace1 -Production Reporting -Production Reporting -Studio Reporting Server -Activator -DB2 -Remote -DDO -Viewer -Informix -ODBC -Oracle -Sybase -Teradata
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 Wizards With 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.
Using Installation Wizards 59 Hyperion Home When 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), whichThe Hyperion Home location is stored in .hyperion.
Hyperion Home Location If 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 ${Home}/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 Console:
● Only XWindows:
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_
60 Installing Reporting and Analysis 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. See “Reporting and Analysis Installers” on page 58. 3 Set the X display: a. On the remote X server machine, enable connectivity from a host: $ xhost +
b. On the server where you install Reporting and Analysis: $ DISPLAY=
4 Navigate to the directory where you downloaded the Reporting and Analysis files and execute setup
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:\).
10 Select the installation path for Hyperion Home. Common components for Hyperion products are installed to
Installing Reporting and Analysis 61 11 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.
12 Click Next. The Setup Type page is displayed. 13 Select a setup type of Typical or Custom, and click Next. See “Using Installation Wizards” on page 59. 14 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. 15 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. 16 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. 17 See Chapter 5, “Configuring and Setting Up Reporting and Analysis.”
62 Installing Reporting and Analysis Chapter Configuring and Setting Up 5 Reporting and Analysis
In This Chapter Post Installation Tasks ...... 64 Using the Configuration Utility ...... 67 Registering Reporting and Analysis with Shared Services ...... 70 Deregistering Reporting and Analysis with Shared Services ...... 71 Configuring Relational Storage ...... 71 Deploying Reporting and Analysis to Application Servers...... 72 Deploying Reporting and Analysis to Application Servers...... 72 Undeploying from an Application Server ...... 75 Enabling the HTTP Server Plug-in ...... 75 Completing Module-Specific Configurations ...... 76 Completing Configuration Utility ...... 79 Configuration Troubleshooting ...... 79 Post Configuration Tasks ...... 80 Reconfiguration ...... 85
Configuring and Setting Up Reporting and Analysis 63 Post Installation Tasks Post installation tasks include:
● Configuring SAP Data Source Access and Authentication
● Configuring X11 for UI Services for Financial Reporting and Web Analysis
Configuring SAP Data Source Access and Authentication To 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 (shared libraries) in
❍ 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
Configuring X11 for UI Services for Financial Reporting and Web Analysis To perform chart generation, the Reporting and Analysis UI Services require access to a graphics display device, either real or virtual. It is recommended that an X virtual frame buffer (Xvfb) be used instead of a hardware graphics display device, as Xvfb performs all operations in memory and does not require that any screens or input devices be attached to the machine.
64 Configuring and Setting Up Reporting and Analysis AIX 5L
➤ To enable Xvfb for AIX 5L: 1 Log on to the computer that will run the Reporting and Analysis UI Services components as the root user. 2 Determine whether Virtual Frame Buffer support is available on your computer by issuing the following command: lslpp -l X11.vfb
3 If X11.vfb is not installed, install it from your AIX installation media. After installing the package, apply the latest PTF from: http://techsupport.services.ibm.com/rs6k/fixdb.html
Note: See Chapter 6 - The X Virtual Frame Buffer and Softgraphics at: http://www.redbooks.ibm.com/redbooks/SG245130.html.
4 Start Xvfb: /usr/bin/X11/X -force -vfb :1
where :1 is the a display number not already in use.
Solaris 9
➤ To enable Xvfb for Solaris 9: 1 Log on to the computer that will run the Reporting and Analysis UI Services components as the root user. 2 Obtain and compile the X11R6 source distribution from: ftp://ftp.x.org, or obtain and install the binary distribution from ftp://www.ferret.noaa.gov/special_request/xvfb/solaris 3 Start Xvfb: /usr/X11R6/bin/Xvfb :1 -screen 0 1152x900x8 &
where :1 is the a display number not already in use.
Solaris 10
➤ To enable Xvfb for Solaris 10: 1 Log on to the computer that will run the Reporting and Analysis UI Services components as the root user. 2 Determine whether Virtual Frame Buffer support is available on your computer by issuing the following command: pkgchk -l SUNWxwsrv
3 If SUNWxwsrv is not installed, install it from the Solaris installation media.
Post Installation Tasks 65 4 Start Xvfb: /usr/openwin/bin/Xvfb :1 > /dev/null 2>&1 &
where :1 is the a display number not in use.
Red Hat Enterprise Linux Release 4
➤ To enable Red Hat Enterprise Linux Release 4: 1 Log on to the computer that will run the Reporting and Analysis UI Services components as the root user. 2 Determine whether Virtual Frame Buffer support is available on your computer by issuing the following command: rpm -q xorg-x11-Xvfb
3 Start Xvfb: /usr/X11R6/bin/Xvfb :1 -screen 0 1152x900x8 &
where :1 is the a display number not already in use.
HP-UX 11i
➤ To enable HP-UX 11i: 1 Log on to the computer that will run the Reporting and Analysis UI Services components as the root user. 2 Determine whether Virtual Frame Buffer support is available on your computer by issuing the following command: swlist -l product | grep 'Xserver cumulative patch' 3 Ensure that the patch level installed on your system corresponds with HP's recommended level (currently PHSS_31293). 4 Copy /etc/X11/X0screens to /etc/X11/X1screens, where 1 is a disaply number not already in use; for example: cp /etc/X11/X0screens /etc/X11/X1screens
5 Edit /etc/X11/X1screens by adding these lines to the end of the file: ServerOptions ServerMode XVfb
6 Start Xvfb: nohup /usr/bin/X11/Xvfb :10 -screen 0 1024x800x8 \ -pn -fp /usr/lib/X11/fonts/misc -sp /etc/X11/SecurityPolicy &
66 Configuring and Setting Up Reporting and Analysis Setting the DISPLAY variable Prior to starting the Reporting and Analysis UI Services components on UNIX, set the DISPLAY environment variable to an available physical or virtual (Xvfb) graphics device address; for example: DISPLAY=`hostname`:1.0 ; export DISPLAY
For the sake of convenience, it is recommended that DISPLAY be initialized automatically by editing the Reporting and Analysis UI Services start scripts.
Note: Only the Financial Reporting and Web Analysis Reporting and Analysis UI Services components require DISPLAY be set. The Workspace component does not require access to X11.
Tip: Display can be set for Financial Reporting by editing
Using the Configuration Utility The 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 76.) For information on how to launch the Configuration Utility, see “Launching the Configuration Utility” on page 69. 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 70
● 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 71 and “Uninstalling Reporting and Analysis” on page 87
● Relational Storage Configuration— See “Completing Module-Specific Configurations” on page 76
● Application Server Deployment— See “Deploying Reporting and Analysis to Application Servers” on page 72.
● Startup Dependencies Verification—See “Verifying Startup Dependencies” on page 80
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.
Using the Configuration Utility 67 Prerequisites Complete 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 81
Install the application server that you plan to use. Application server documentation
Prepare a database to use for relational storage. Database documentation 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.
Install Hyperion products. Product installation guide
Note: Do not start the product you are configuring.
Task Sequence When 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 Upgrades You 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.
68 Configuring and Setting Up Reporting and Analysis Specifying Application Server Hostnames and HTTP Connector Plug-in Ports When 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 Sun Java System Application Server Enterprise Edition 8.1” on page 117
● “Manually Deploying into WebLogic 8.1.4” on page 133.
● “Middle Layer Components” on page 30 for important file descriptor information.
● “Manually Deploying into WebSphere 5.1.1.7” on page 169
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 Utility You 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: The Configuration Utility requires a minimum of 1024 file descriptors, and does not start if the launching user's limit is less than 1024.
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.
● Command line:
❍ To launch the graphical interface, run configtool.sh from:
Using the Configuration Utility 69 ❍ To launch the console interface, run configtool.sh -console from:
● “Registering Reporting and Analysis with Shared Services” on page 70
● “Deregistering Reporting and Analysis with Shared Services” on page 71
● “Configuring Relational Storage” on page 71
● “Deploying Reporting and Analysis to Application Servers” on page 72
● “Enabling the HTTP Server Plug-in” on page 75
● “Completing Module-Specific Configurations” on page 76
● “Completing Configuration Utility” on page 79
● “Configuration Troubleshooting” on page 79
Registering Reporting and Analysis with Shared Services Shared 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 69. 2 From the list of installed products, select those to configure and click Next. 3 On the task selection page, select Shared Services Registration and click Next. 4 Specify Shared Services server information:
Table 5 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).
70 Configuring and Setting Up Reporting and Analysis 5 Click Next to go to the next configuration task or to finish.
Deregistering Reporting and Analysis with Shared Services If 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: 1 Launch the Configuration Utility. See “Configuring Product Upgrades” on page 68. 2 From the list of installed products, select those to configure and click Next. 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. 4 For Password, enter your password and click Next. 5 Click Next to go to the next configuration task or to finish.
Configuring Relational Storage To 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: 1 Launch the Configuration Utility. See “Launching the Configuration Utility” on page 69. 2 From the list of installed products, select those to configure and click Next. 3 On the task selection page, select Relational Storage Configuration and click Next.
Configuring Relational Storage 71 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 6 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.
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.
6 Click Next to view configuration status. 7 Click Next to go to the next configuration task or to finish.
Deploying Reporting and Analysis to Application Servers The 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”.
Caution! If you are using IBM WebSphere application server, use the same account to install, deploy, and execute Hyperion products that you use to install WebSphere. Using the same account ensures that products are deployed successfully.
72 Configuring and Setting Up Reporting and Analysis ➤ To deploy products to an application server: 1 Launch the Configuration Utility. See “Launching the Configuration Utility” on page 69. 2 From the list of installed products, select those to configure and click Next. 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. 5 Specify application server information:
Table 7 Application Server Configuration Fields
Location Enter the path to the location of the application server directory (for example, /opt/bea/werblogic81), 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— /opt/WebSphere/AppServer
● For WebSphere Express— /opt/IBM/WebSphere/Express51/AppServer
● For WebLogic— /opt/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, /opt/), or browse to and select the location.
Username and Password Enter your WebLogic username and password. (WebLogic only)
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
Note: Window Services are deployed as manual startup.
Deploying Reporting and Analysis to Application Servers 73 Table 7 Application Server Configuration Fields
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 Sun Java System Application Server Enterprise Edition 8.1” ● Appendix C, “Manually Deploying into WebLogic 8.1.4” ● Appendix E, “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 (-).
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 53.
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 53.
Domain (WebLogic only) Enter the name of the domain where you can access the deployed product. You can enter only English alphanumeric characters.
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
6 Click Next to view configuration status. 7 Click Next to go to the next configuration task or to finish.
74 Configuring and Setting Up Reporting and Analysis Undeploying from an Application Server The Configuration Utility enables you to undeploy Reporting and Analysis.
➤ To undeploy: 1 Launch the Configuration Utility. See “Launching the Configuration Utility” on page 69. 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.
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 Support The Reporting and Analysis Configuration Utility supports the following HTTP Server plug- ins: Table 8
Apache IBM IIS
WebSphere Yes Yes
Web Logic Yes
Tomcat Yes
Enabling the HTTP Server Plug-in 75 HTTP Server Plug-in Manual Support For Reporting and Analysis supported manual configurations of HTTP Server plug-ins, see the individual application server appendixes: Table 9
Apache IBM IIS
WebSphere “Manually “Configuring Deploying into Apache or IBM WebSphere HTTP with 5.1.1.7” on WebSphere 5.1” page 169 on page 179
Web Logic “Configuring Apache with BEA WebLogic” on page 138
JES “Manually Deploying into Sun Java System Application Server Enterprise Edition 8.1” on page 117
Completing Module-Specific Configurations You 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 76
● “Completing Financial Reporting Configurations” on page 78
Workspace Configurations Workspace configurations:
● “Customizing the Context Path” on page 77
● “Specifying the GSM Host and Port” on page 77
● “Customizing Service Ports for Reporting and Analysis” on page 77
● “Configuring the Production Reporting Engine for Interactive Reporting” on page 77
76 Configuring and Setting Up Reporting and Analysis 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
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 Analysis The 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 Reporting When 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:
● MS SQL:
● IBM DB2:
Completing Module-Specific Configurations 77 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 78
● “Report Server Configuration” on page 79
● “Workspace, Print Service, and Scheduler Service Configurations” on page 79
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:
● Enable Planning Details
● Enable a Planning Version:
❍ Version 4.1
❍ Version 4.0.1
● Locations of Planning ADM driver and configuration property files. If you enabled:
❍ Version 4.1: The 2 Location fields are enabled, but you do not need to enter them.
❍ Version 4.0.1: Enter two path locations for Planning:
❑ ADM driver
❑ 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,
78 Configuring and Setting Up Reporting and Analysis Workspace, Print Service, and Scheduler Service Configurations To 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 Configuration The 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 Utility Depending on the components selected for configuration, the Configuration Utility may take some time to complete. Progress is logged to
Note: If you experience problems with configuration, as a troubleshooting measure, perform configuration tasks individually for one module at a time.
Configuration Troubleshooting Because 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:
Note: If you experience problems with configuration, as a troubleshooting measure, perform configuration tasks individually for one product at a time.
Configuration Troubleshooting 79 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 See “Starting Shared Services” on page 81. confirmation messages in the server console window or launch User Management Console. See “Verifying Successful Startup of Shared Services” on page 81.
Workspace Service Open the Url: Run startworkspace.sh from: http:/server:port/workspace
Interactive Reporting Core Navigate to: Run Services
Interactive Reporting Navigate to: Run Service
Interactive Reporting Data Navigate to: Run Access Service
80 Configuring and Setting Up Reporting and Analysis Component How to Verify Successful Startup How to Start
Financial Reporting Servers Navigate to
● 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.
Web Analysis Service Open the URL: Run startwebanalysis.sh from: http://server:port/WebAnalysis.
Starting Shared Services
To start the Shared Services server, from a command line, execute the startup file for a server:
Application Server Path to Script
IBM WebSphere
BEA WebLogic
Oracle
Apache Tomcat
Note:
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
Post Configuration Tasks 81 When Shared Services is deployed to the Tomcat application server, these confirmation messages are logged to the following file:
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. 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.
82 Configuring and Setting Up Reporting and Analysis Production Reporting Post Configuration Tasks This section describes the post configuration tasks for Production Reporting:
● Setting the environment variables
● Recreating the executables
Setting up the Environment Variables You run a script to set the environment variables. The scripts are in specified database folders.
➤ To configure the environment variables, locate the environment scripts in the following directories:
where db_name is the name of the database. The following databases are supported: Sybase, Oracle, Informix, DB2, ODBC, DDO, and Teradata.
● For all databases, the following script configures the basic environment variables:
❍ For C Shell: source setenv.csh
❍ For Bourne or Korn Shell: setenv.sh
● For the DDO database, the following script configures additional environment variables:
❍ For C Shell: source setjre.csh
❍ For Bourne or Korn Shell: setjre.sh
Recreating the Executables You must recreate the executables if the version of the operating system or database client software is different from when the original executables were created. You find the versions by using the following command line flag: -id
➤ To recreate the executables, type the following commands from a shell: cd hyperion/BIPlus/bin/SQR/Server/db_name/lib ./sqrmake
where db_name is the name of one of the following database names: Sybase, Oracle, Informix, DB2, ODBC, DDO, or Teradata.
Post Configuration Tasks 83 Adding Drivers for Web Analysis RDBMS Connectivity The 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:
Note: If using WebSphere Application Server, navigate to the following folder:
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://
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://
Changing the Apache HTTP Server Listen Port
➤ To change the Apache Listen Port: 1 Open http.conf and add a Listen directive:
84 Configuring and Setting Up Reporting and Analysis 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.
Reconfiguration The 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.
Reconfiguration 85 86 Configuring and Setting Up Reporting and Analysis Chapter Uninstalling Reporting and 6 Analysis
In This Appendix Prerequisites ...... 88 Uninstalling...... 88
Uninstalling Reporting and Analysis 87 Prerequisites
Before you perform an uninstall, stop Reporting and Analysis.
Uninstalling
Caution! During uninstall, the Reporting and Analysis directory is deleted.
➤ To uninstall Reporting and Analysis: 1 Start the Uninstall wizard by browsing to the following locations and clicking uninstall.bin:
Note: Verify that Reporting and Analysis directories are deleted.
88 Uninstalling Reporting and Analysis Chapter Upgrading to Reporting and 7 Analysis 9.2.1
In This Chapter Upgrading from 8.x to 9.2.1...... 90 Upgrading from 9.x to 9.2.1...... 90
Note: All products in release 9.2.1 (Data Integration Management excepted) support upgrades from 8.x, 9.0.1x and 9.2.
Upgrading to Reporting and Analysis 9.2.1 89 Upgrading from 8.x to 9.2.1 To 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
❍ Backup
● 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 upg rade: 1 Upgrade Reporting and Analysis components: a. Launch services installers which were installed on the previous installation:
❍ ServicesCD
❍ UIServicesCD
❍ 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.
90 Upgrading to Reporting and Analysis 9.2.1 2 After installing: a. Verify that
For example: biplus_1.properties and biplus_1.xml
b. Verify that
❍ value="UPGRADE",
❍ originalVersion="
❍ complete="true"—If complete= "false", the upgrade is incomplete; upgrade all components again and recheck
Upgrading from 9.x to 9.2.1 91 92 Upgrading to Reporting and Analysis 9.2.1 Chapter Installing the Reporting and 8 Analysis Migration Utility
In This Chapter Migration Utility ...... 94 Requirements ...... 94 Installing the Migration Utility...... 95 After Installing the Migration Utility ...... 96
Installing the Reporting and Analysis Migration Utility 93 Migration Utility Migration 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.
Requirements Source and target system requirements:
● Disk space—200 MB
● RAM—256 MB
● Reporting and Analysis Software Requirements. See “Software Requirements” on page 27.
94 Installing the Reporting and Analysis Migration Utility Supported Source Databases Table 10 Supported Source Databases for each Reporting and Analysis Modules:
Reporting Database: 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
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 Untar the UNIX TAR file for your platform. 3 Close all Reporting and Analysis programs. 4 Launch the installation setup file:
● AIX systems—setupAixPlatform.bin
● HPUX systems—setupHpPlatform.bin
● Linux systems—setupLinuxPlatform.bin
● Solaris systems—setupSolarisPlatform.bin 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.
Installing the Migration Utility 95 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. 14 To verify the installation, run the migrator.sh file in the folder where you installed the Migration Utility.
For example:
After Installing the Migration Utility The Hyperion Migration Utility:
● Creates a directory structure, by default:
● 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.
jre Contains the JRE files. AIX includes JRE 1.3.1. All other platforms contains JRE 1.4.1.
96 Installing the Reporting and Analysis Migration Utility APPENDIXZ Manually Deploying into Oracle A 10g Release 3 (10.1.3.1.0)
In This Appendix Prerequisites ...... 98 Deploying Workspace Web Application ...... 98 Deploying Financial Reporting ...... 103 Deploying Web Analysis ...... 106 Configuring Oracle HTTP Server for Oracle 10g Release 3 ...... 109 Configuring Oracle Single Sign-on on Oracle 10g Release 3 ...... 111 Testing Module Availability ...... 115
Manually Deploying into Oracle 10g Release 3 (10.1.3.1.0) 97 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://
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: The operating system user who owns the Oracle Application Server instance should be used to install Reporting and Analysis. If that is not possible, the
Deploying Workspace Web Application To 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://
where
98 Manually Deploying into Oracle 10g Release 3 (10.1.3.1.0) 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.
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=
where
● 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...
Deploying Workspace Web Application 99 and entering:
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 Provider If 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:
where
where
6 Select Append for the PATH definition.
100 Manually Deploying into Oracle 10g Release 3 (10.1.3.1.0) Creating context.properties
➤ To create context.properties: 1 With a text editor, create:
where
2 Add the following values: Set “Y” if components have been installed, “N” if components have not been installed: Reports=Y HPSU=Y HPS=N HMB=N ChangeManagement=Y Analyzer=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 Workspace You need to update the Oracle HTTP Server (OHS) to make static content, online Help, available.
➤ To update OHS Routing for Workspace: 1 Open:
where
Deploying Workspace Web Application 101 2 Check that the following property for Workspace application is added: ohs-routing="false"
For example:
Updating Configuration Files
➤ To update configuration files: 1 Edit:
a. In the line: HYPERION_HOME=$J(HYPERION_HOME)
replace $J(HYPERION_HOME) with your actual HYPERION_HOME location. For example: $HOME/Hyperion
b. In the line: DEPLOYMENT_PATH=$J(servletConfig.deploymentPath)
replace $J(servletConfig.deploymentPath) with the actual location of deployed Workspace The default is:
where
2 Edit:
a. In the line: HYPERION_HOME=$J(HYPERION_HOME)
replace $J(HYPERION_HOME) with your actual HYPERION_HOME location. For example: $HOME/Hyperion
b. In the line: BRIO_LIB=$J(trustedPass.installLib)
replace $J(trustedPass.installLib)with your actual
102 Manually Deploying into Oracle 10g Release 3 (10.1.3.1.0) For example: $HOME/Hyperion/BIPlus/lib
c. In the line: DEPLOYMENT_HOME=$J(trustedPass.deploymentHome)
replace $J(trustedPass.deploymentHome) with the actual location of deployed Workspace application. The default is:
where
Deploying Financial Reporting To 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.
Note: Copy .hyperion-
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 a OC4J instance: 1 Log in to the Oracle Enterprise Manager’s 10g Web console via: http://
where
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.
2 Within Application Server Control instance click on the instance link.
Deploying Financial Reporting 103 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.
Configuring an OC4J Instance
➤ To configure OC4J instance properties: 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 512m Initial 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=
for example: -DHYPERION_HOME=/home/hys9/Hyperion -DBIPLUS_HOME=/home/hys9/Hyperion/BIPlus -DADM_HP_LIB=/home/hys9/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=
104 Manually Deploying into Oracle 10g Release 3 (10.1.3.1.0) 3 Add required library search path Environment Variable: a. Execute the script:
b. Copy the value of one of the following library search paths: LIBPATH SHLIB_PATH LD_LIBRARY_PATH
c. Click Add Environment Variable, and add an appropriate library search path variable: LIBPATH SHLIB_PATH LD_LIBRARY_PATH
using the copied script output for its value; for example: LD_LIBRARY_PATH=
d. Select Append for the variable you define. 4 Under Environment Variables, add the following, substituting values in <> with actual locations: HYPERION_HOME
for example: HYPERION_HOME /home/hys9/Hyperion ESSLANG English_UnitedStates.Latin1@Binary BIPLUS_HOME /home/hys9/Hyperion/BIPlus ARBORPATH /home/hys9/Hyperion/common/EssbaseRTC/9.2.1 DISPLAY
See “Configuring X11 for UI Services for Financial Reporting and Web Analysis” for more information. 5 Click Apply and restart the OC4J instance.
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:
Deploying Financial Reporting 105 by default, keep the Archive type in J2EE Application. For example: /home/BIPlus/InstalledApps/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.
4 Click Next to create a new deployment plan. 5 In Application Name, type FinancialReporting and click Next. 6 Click Deploy. 7 After successful deployment, restart the FinancialReporting OC4J instance.
Deploying Web Analysis To 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.
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://
where
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.
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.
106 Manually Deploying into Oracle 10g Release 3 (10.1.3.1.0) Configuring an OC4J Instance
➤ To configure OC4J instance properties: 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 512m Initial 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=
For example: -DHYPERION_HOME=/home/hys9/Hyperion -DBIPLUS_HOME=/home/hys9/Hyperion/BIPlus -XX:PermSize=64m -XX:MaxPermSize=128m
3 Under Environment Variables, add the following, substituting <> with actual locations: ESSLANG
where
Deploying Web Analysis 107 For example: ESSLANG English_UnitedStates.Latin1@Binary HYPERION_HOME /home/hys9/Hyperion ARBORPATH /home/hys9/Hyperion/common/EssbaseRTC/9.2.1 BIPLUS_HOME /home/hys9/Hyperion/BIPlus DISPLAY
See “Configuring X11 for UI Services for Financial Reporting and Web Analysis” on page 64 for more information.
Note: Select Append for PATH definition.
4 Add one more variable for library path, depending on operating system, where Hyperion Reporting and Analysis is running:
● Linux and Solaris: LD_LIBRARY_PATH=
● HP-UX: SHLIB_PATH=
● IBM AIX: LIBPATH=
Note: Select Append for PATH and LD_LIBRARY_PATH/SHLIB_PATH/LIBPATH definitions.
5 Click Apply and restart the OC4J instance.
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:
by default, in J2EE Application.
108 Manually Deploying into Oracle 10g Release 3 (10.1.3.1.0) 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.
4 Click Next to create a new deployment plan. 5 In Application Name, type WebAnalysis and click Next. 6 Click Deploy.
Tip: For DB connectivity, copy appropriate JDBC drivers into
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
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.
Configuring Oracle HTTP Server for Oracle 10g Release 3 109 3 Add the following aliases, substituting values in <> with actual locations
● Workspace Alias /workspace "
● Web Analysis Alias /WebAnalysis "
4 Open mod_oc4j.conf and create the following Oc4jMount directives for each Reporting and Analysis module you have deployed:
● Workspace Oc4jMount /workspace/cdsrpc Workspace Oc4jMount /workspace/administration/* Workspace Oc4jMount /workspace/browse/* Workspace Oc4jMount /workspace/personalpages/* Workspace Oc4jMount /workspace/viewmanager/* Workspace Oc4jMount /workspace/jobmanager/* Workspace Oc4jMount /workspace/ihtml/* Workspace Oc4jMount /workspace/dataaccess/* Workspace Oc4jMount /workspace/logon Workspace Oc4jMount /workspace/logon/* Workspace Oc4jMount /workspace/js/* Workspace Oc4jMount /workspace/modules/* Workspace Oc4jMount /workspace/resources/* Workspace Oc4jMount /workspace/conf/* Workspace Oc4jMount /workspace/media/* Workspace Oc4jMount /workspace/prefs Workspace Oc4jMount /workspace/BPMContext Workspace Oc4jMount /workspace/wsrp4j/* Workspace Oc4jMount /workspace/ResourceProxy Workspace Oc4jMount /workspace/ Workspace Oc4jMount /workspace/*.jsp Workspace Oc4jMount /workspace/*.jsv Workspace Oc4jMount /workspace/*.jsw Workspace:
● Financial Reporting Oc4jMount /hr FinancialReporting Oc4jMount /hr/* FinancialReporting Oc4jMount /HReports FinancialReporting Oc4jMount /HReports/* FinancialReporting
● Web Analysis Oc4jMount /WebAnalysis/ServerConsole/* WebAnalysis Oc4jMount /WebAnalysis/templates/* WebAnalysis Oc4jMount /WebAnalysis/hfmtemplates/* WebAnalysis Oc4jMount /WebAnalysis/hitemplates/* WebAnalysis Oc4jMount /WebAnalysis/processor WebAnalysis Oc4jMount /WebAnalysis/servlet/* WebAnalysis
110 Manually Deploying into Oracle 10g Release 3 (10.1.3.1.0) Oc4jMount /WebAnalysis/modules/* WebAnalysis Oc4jMount /WebAnalysis/resources/* WebAnalysis Oc4jMount /WebAnalysis/DirectoryServlet WebAnalysis Oc4jMount /WebAnalysis/config WebAnalysis Oc4jMount /WebAnalysis/wa_javadocs/* WebAnalysis Oc4jMount /WebAnalysis/ WebAnalysis Oc4jMount /WebAnalysis/*.jsp WebAnalysis Oc4jMount /WebAnalysis/*.xml WebAnalysis Oc4jMount /WebAnalysis/*.jar WebAnalysis Oc4jMount /WebAnalysis/*.exe WebAnalysis
5 Start the Oracle HTTP Server using opmnctl:
6 Verify that ConfigURL in the following location is referred onto the correct Oracle HTTP Server port:
Configuring Oracle Single Sign-on on Oracle 10g Release 3
Prerequisites Oracle 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.sh
For example: $ORACLE_HOME/sso/bin/ssoreg.sh -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
The resulting configuration file (myosso.conf in this example) is an obfuscated OSSO configuration file. 3 Copy the obfuscated OSSO configuration file to the 10g Release 3 (10.1.3) middle-tier instance.
Configuring Oracle Single Sign-on on Oracle 10g Release 3 111 4 On the middle-tier host, run the following script to complete the registration: ORACLE_HOME/Apache/Apache/bin/osso1013 config_file
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
112 Manually Deploying into Oracle 10g Release 3 (10.1.3.1.0) deny from all allow from
10 Append the following lines to: ORACLE_HOME/Apache/Apache/conf/httpd.conf
11 Update:
a. Uncomment and set UseSecurityAgentTokenWithoutDomain to true. b. Update SSOProviderSessionCookieID and set value to OHS-
Configuring Oracle Single Sign-on on Oracle 10g Release 3 113 14 Setup the Workspace Web Application parameters: a. Start Servlet Configurator:
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:
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:
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:
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://
114 Manually Deploying into Oracle 10g Release 3 (10.1.3.1.0) Testing Module Availability For each of the products used, verify the setup by using the URLs below.
Product URL1 Expected Result
Workspace http://
Financial Reporting http://
Web Analysis http://
Architect http://
Financial Management http://
Planning http://
1URL: Where
Testing Module Availability 115 116 Manually Deploying into Oracle 10g Release 3 (10.1.3.1.0) APPENDIX Manually Deploying into Sun Java System Application Server B Enterprise Edition 8.1
In This Appendix Prerequisties ...... 118 Deploying Reporting and Analysis ...... 124 Post Configuration Tasks ...... 126 Testing Web Applications ...... 127 Generating the JES Load Balancing Plug-in Configuration File ...... 128 Default Sun Java Enterprise Application Server Locations ...... 132 Testing Module Availability ...... 132
Manually Deploying into Sun Java System Application Server Enterprise Edition 8.1 117 Prerequisites
Note: There is no JES option in the Configuration Utility for this release of Reporting and Analysis.
The Application Server Deployment task of the Hyperion Configuration Utility must be run with the “Manual Deployment” option selected for the Tomcat application server.
Tip: The Hyperion Configuration Utility will install and start the Hyperion Apache HTTP Server automatically. If the Sun Web Server will be used, instead, you may safely stop, disable, or remove the Hyperion Apache HTTP Server instance.
The Reporting and Analysis web application archives will be available in these locations:
●
Creating a Node Agent This section describes necessary steps to create a new Node Agent. If you are going to use an existing Node agent instance, skip this section.
➤ To create a Node agent from the command line: 1 If not already started, start the Sun Java System Application Server domain using the asadmin command line tool:
➤ To create a Node agent using the JES Admin Console: 1 Log into the JES Admin Console: https://
118 Manually Deploying into Sun Java System Application Server Enterprise Edition 8.1 3 Specify a Node Agent name and click OK.
Note: Make sure you have enough free space in your default
➤ To start a Node Agent, execute the following command:
Creating a New Standalone Server Instance It is recommended that you create a new Standalone Server instance for each Reporting and Analysis Web module you intend to deploy (Workspace, Financial Reporting, or Web Analysis). This recommendation is based on the assumption that JES administrators do not want all deployed applications to inherit JVM runtime settings that pertain only to Reporting and Analysis. Each Sun Java System Application Server instance has its own J2EE configuration, J2EE resources, application deployment areas, and server configuration settings. Changes to one application server instance have no impact on other application server instances. You can have many application server instances within one domain. If you deploy the Web Application to an existing server instance, skip this section. You can use the JES Admin Console to create new a standalone server instance. The JES Admin Console provides Web-based management tools designed specifically for Sun Java System Application Server. Using the Web Console, you can monitor and configure the components of your Application Server installations.
➤ To create a new standalone Server Instance: 1 If not already started, start the Sun Java System Application Server domain using the asadmin command line tool
Prerequisties 119 5 Select the Node agent from the list of available agents. The selected Node Agent must be started. If no Node Agents are available, create one. See “Creating a Node Agent” on page 118. 6 Select the default-config configuration, and click OK.
Customizing a Standalone Server Instance The default Java security policy must be customized for each Reporting and Analysis module being deployed. ● For Workspace: Copy
to
Append the following lines to workspace_server.policy: grant { permission java.util.PropertyPermission "*", "read,write"; permission java.lang.RuntimePermission "modifyThreadGroup"; permission java.lang.RuntimePermission "setIO"; permission java.security.SecurityPermission "getPolicy"; permission java.util.logging.LoggingPermission "control"; permission java.io.FilePermission "<
● For Financial Reporting: Copy
120 Manually Deploying into Sun Java System Application Server Enterprise Edition 8.1 ● For Web Analysis: Copy
➤ To disable directory browsing: 1 Edit
Prerequisties 121 Editing Standalone Server Instance JVM Options for Workspace
➤ To edit standalone server instance JVM options for Workspace: 1 Log into the JES Admin Console. 2 Navigate to Configurations >
Editing Standalone Server Instance JVM Options for Financial Reporting
➤ To edit standalone server instance JVM options for Financial Reporting: 1 Log into the JES Admin Console. 2 Go to Configurations >
5 Click Save. 6 In the Native Library Path Suffix window, add the following lines:
122 Manually Deploying into Sun Java System Application Server Enterprise Edition 8.1 7 Click Save. 8 Open JVM Options tab. 9 Change the -Djava.security.policy argument to point to fr_server.poilcy created previously. 10 Copy .hyperion-
Financial Reporting Environment Variables You must prepare the JVM environment with the necessary environment variables for Financial Reports to function correctly. Add the following lines to the end of
See “Configuring X11 for UI Services for Financial Reporting and Web Analysis” on page 64.
Note: To define environment variables for specific applications, update
Note: Restart application server components after making the appropriate modifications.
Editing Standalone Server Instance JVM Options for Web Analysis
➤ To edit standalone server instance server JVM options for Web Analysis: 1 Log into the JES Admin Console. 2 Go to Configurations >
where
Prerequisties 123 7 Click Save. 8 Open JVM Options tab. 9 Change the -Djava.security.policy argument to point to wa_server.poilcy created previously.
Note: Restart application server components after making the appropriate modifications.
Web Analysis Environment Variables You must prepare the JVM environment with the necessary environment variables for Web Analysis to function correctly. You can set the Web Analysis environment variables before or after deployment. Restart standalone application server instance after setting the variables. Edit
See “Configuring X11 for UI Services for Financial Reporting and Web Analysis” on page 64.
Note: To define environment variables for specific applications, update
Note: Restart any application server components that are already started when you modify asenv.conf.
Deploying Reporting and Analysis
Deploying Workspace Web Applications
➤ To deploy Workspace Web applications: 1 Log into the JES Admin Console. 2 Select Applications > Web Applications and click Deploy. 3 Provide the server path to the following, and click Next.
4 Specify Workspace as the Web Application Name, and /workspace as its Context Root. 5 Select a target server (For example, WorkspaceServer) for the Web Application and click OK.
Note: You can add one or more server targets.
124 Manually Deploying into Sun Java System Application Server Enterprise Edition 8.1 Note: Ensure that you have write permission and enough free space in your
Deploying Financial Reporting Enterprise Applications
➤ To deploy Financial Reporting Enterprise Applications: 1 Log into the JES Admin Console. 2 Select Applications > Enterprise Applications and click Deploy. 3 Provide the server path to
Note: You can add one or more server targets.
Note: Ensure you have write permission and enough free space in your
Deploying Web Analysis Enterprise Applications
➤ To deploy Web Analysis Enterprise Applications: 1 Run the Sun Java System Application Server domain if it isn’t running yet. 2 Log into the JES Admin Console. 3 Select Applications > Enterprise Applications and click Deploy. 4 Provide the server path to
Note: You can add one or more server targets.
Note: Ensure you have write permission and enough free space in your
Deploying Reporting and Analysis 125 Post Configuration Tasks
● “Configuring Workspace Web Applications After Deployment” on page 126
● “Configuring Web Analysis Enterprise Applications after Deployment” on page 126
Configuring Workspace Web Applications After Deployment
➤ After deploying, perform these tasks: 1 Edit
with
Note: This ensures you will be able to access the Web Application by a short URL http://
3 Create a file named context.properties in
5 Copy context.properties into:
Configuring Web Analysis Enterprise Applications after Deployment
➤ After deployment, perform these tasks: 1 Edit sun-web.xml:
126 Manually Deploying into Sun Java System Application Server Enterprise Edition 8.1 a. Open
2 Edit
3 Create
Testing Web Applications The new standalone server instance is initially in a stopped state. Before testing the deployed and configured application, you should start it via Admin Console.
➤ To test the Web applications: 1 Log into the JES Admin Console. 2 Select the Stand-Alone Instances tab and select an option:
● WorkspaceServer
● FinancialreportingServer
● WebanalysisServer 3 Click Start.
You can access the Web Application directly from a browser by entering: http://
Testing Web Applications 127 where
Note: For Financial Reporting, accessing http://
Generating the JES Load Balancing Plug-in Configuration File For each server (Workspace, WebAnalysis and Financial Reporting) you must generate a load balancer plug-in configuration file.
➤ To generate a load balancer plug-in configuration file: 1 Open the asadmin utility located in:
2 Generate a load balancer configuration file: asadmin> create-http-lb-config --user
3 Create references for each server in newly created load balancer configuration file: asadmin> create-http-lb-ref --user
4 Enable each server: asadmin> enable-http-lb-server --user
128 Manually Deploying into Sun Java System Application Server Enterprise Edition 8.1 5 Enable each web application: asadmin> enable-http-lb-application --user
6 Create health checker for each server: asadmin> create-http-health-checker --user
7 Export resulting configuration to XML file: asadmin> export-http-lb-config --user
8 Update exported
Sun Web Server 6.1 Configuration
Automatically Installing the Load Balancing Plugin The recommended procedure for configuring Sun Web Server 6.1 for use with Sun JES 8.1 is as follows:
● Launch the Sun JES install program
● Select the Sun Web Server 6.1 component
● Select the Sun JES Load Balancing Plugin component
● Select Configure Now
The Sun JES install program will automatically copy the required load balancing plugin files and modify Sun Web Server's configurations files (obj.conf and magnus.conf). See http://docs.sun.com for more information.
Generating the JES Load Balancing Plug-in Configuration File 129 Manually Installing the Load Balancing Plug-in In the following procedures, substitute <> denoted values with actual install locations. For example, on Solaris,
❍ sun-loadbalancer_1_0.dtd
❍ sun-loadbalancer_1_1.dtd g 2 Create these directories:
Configuring the Load Balancing Plug-in
➤ To configure if the Load Balancing Plug-in was installed automatically by the JES install program: 1 Copy:
change the value of the config-file= parameter so that it refers to
4 Restart Sun Web Server 6.1.
130 Manually Deploying into Sun Java System Application Server Enterprise Edition 8.1 ➤ To configure if the Load Balancing Plug-in was installed manually: 1 Open
4 Save and close obj.conf 5 Open
7 Save and close magnus.conf. 8 Restart Sun Web Server 6.1.
Create NameTrans Entries for Static Workspace Content The Reporting and Analysis Workspace module contains static HTML content that can be served by Sun Web Server 6.1, instead of JES, for improved performance.
➤ To create nameTrans entries for static Workspace content: 1 Open
Generating the JES Load Balancing Plug-in Configuration File 131 NameTrans fn="pfx2dir" from="/workspace/themes/" dir="
3 Save and close obj.conf. 4 Restart Sun Web Server 6.1.
Default Sun Java Enterprise Application Server Locations Sun Java Enterprise System default installations:
● Solaris™-/opt/SUNWappserver/appserver
● Linux:-/opt/sun/appserver/
● Windows-SystemDrive:\Sun\AppServer
Testing Module Availability
➤ To directly access the Web Application: http://localhost:
132 Manually Deploying into Sun Java System Application Server Enterprise Edition 8.1 APPENDIX Manually Deploying into C WebLogic 8.1.4
In This Appendix Prerequisites ...... 134 Deploying Workspace into WebLogic...... 135 Deploying Financial Reporting into WebLogic ...... 136 Deploying Web Analysis into WebLogic ...... 137 Configuring Apache with BEA WebLogic ...... 138 Testing the Connection...... 144
Manually Deploying into WebLogic 8.1.4 133 Prerequisites
● Hyperion Shared Services
❍ Install Hyperion Shared Services.
❍ Verify that it is up and running.
❍ Test the installation and make sure that you can log into Shared Services. http://
For example: http://localhost:58080/interop/index.jsp
● 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. You need at least 1 GB available disk space in the temporary path before deploying.
Modifying startWebLogic.sh
➤ To modify startWebLogic.sh: 1 Open startWeblogic.sh. For example: /opt/bea/user_projects/domains/mydomain/startWeblogic.sh.
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.sh script: LIB_DIR=
5 Save startWeblogic.sh. IMPORTANT! The Workspace Reporting and Analysis component requires a 2000 file descriptors minimum. The installing user's file descriptor limit must be greater than 2000. Refer to the ulimit man page for your operating system for details on setting this value.
Note: WebLogic changes the user's descriptor limit to 1024/1025 in ${BEA_HOME}/weblogic81/common/bin/commEnv.sh. You must manually comment the last line in that file by inserting a hash (#). For example: Change resetFd to #resetFd.
134 Manually Deploying into WebLogic 8.1.4 Deploying Workspace into WebLogic
➤ To deploy : 1 Extract
where
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 144.
Post Deployment for Workspace After you have deployed Workspace, create context.properties.
➤ To create context.properties: 1 With a text editor, create:
Deploying Workspace into WebLogic 135 2 Add the following values: 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: Reports=Y HPSU=Y HPS=N HMB=N ChangeManagement=Y Analyzer=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 installed:
● Financial Reporting (Reports)
● Interactive Reporting (HPSU)
● Performance Scorecard (HPS)
● Dashboard Development Services (ChangeManagement)
● Web Analysis (Analyzer)
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:
Note: See “Testing the Connection” on page 144.
Post Deployment for Financial Reporting
➤ After you have deployed Financial Reporting: 1 Execute:
136 Manually Deploying into WebLogic 8.1.4 2 Copy the output, and set the library search path variable in the script used to start Weblogic. For example: LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:/home/hyperion/Hyperion/common/Essbas eRTC/9.2.1/bin:/home/hyperion/Hyperion/common/ADM/9.2.0/Essbase/9.2.0/bi n; export LD_LIBRARY_PATH
Deploying Web Analysis into WebLogic
Pre-Deployment for Web Analysis Manually create
with the following contents: HYPERION_HOME=
ARBORPATH=$HYPERION_HOME/common/EssbaseRTC/9.2.1 export ARBORPATH
PATH=$HYPERION_HOME/common/ADM/9.2.0/lib:$HYPERION_HOME/common/SAP/bin:$ PATH export PATH
Note: In the following lines, use LD_LIBRARY_PATH for Solaris/Linux, LIBPATH for AIX, and SHLIB_PATH for HP-UX. The code in the following lines would be for Solaris/Linux, since it uses LD_LIBRARY_PATH.
LD_LIBRARY_PATH=$HYPERION_HOME/common/EssbaseRTC/9.2.1/bin: $HYPERION_HOME/common/ADM/9.2.0/Essbase/9.2.0/bin:$HYPERION_HOME/common/ SAP/lib:$LD_LIBRARY_PATH
export LD_LIBRARY_PATH
ICU_DATA=
Ensure
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.
Deploying Web Analysis into WebLogic 137 3 Select one as the archive to deploy:
Note: See “Testing the Connection” on page 144.
Configuring Apache with BEA WebLogic The 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:
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
138 Manually Deploying into WebLogic 8.1.4 KeepAliveSecs 20 WeblogicCluster
Configuring Apache with BEA WebLogic 139
140 Manually Deploying into WebLogic 8.1.4
Configuring Apache with BEA WebLogic 141 PathTrim / KeepAliveEnabled ON KeepAliveSecs 20 WeblogicCluster
142 Manually Deploying into WebLogic 8.1.4 KeepAliveSecs 20 WeblogicCluster
c. Open:
and add the following lines, replacing
3 Restart the Apache HTTP server. 4 Test the plug-in by using a URL:
● Financial Reporting—http://
● Web Analysis—http://
● Workspace—http://
Configuring Apache with BEA WebLogic 143 Testing the Connection Test the connectivity to your newly deployed Reporting and Analysis application by opening the following URLs: http://
where
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://
which returns the Financial Reporting internal build number.
144 Manually Deploying into WebLogic 8.1.4 APPENDIX Manually Deploying into D WebLogic 9.2
In This Appendix Prerequisites ...... 146 Preparing the Environment ...... 146 Deploying Workspace into WebLogic...... 149 Deploying Financial Reporting into WebLogic ...... 153 Deploying Web Analysis into WebLogic ...... 156 Configuring a Web Server for WebLogic 9.2...... 160 Testing Module Availability ...... 167
Manually Deploying into WebLogic 9.2 145 Prerequisites
● Shared Services
❍ Install Shared Services
❍ Verify that it is up and running
❍ Test the installation and make sure that you can log into : http://
● Install Reporting and Analysis 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. You need at least 1 GB available disk space in the temporary path before deploying.
Preparing the Environment Review the following sections for information on:
● Preparing a One-Host Environment
● Preparing a Clustering Environment
Preparing a One-Host Environment Preparing a one-host environment involves creating a WebLogic domain for the environment.
➤ To create a WebLogic domain: 1 Run BEA WebLogic Configuration Wizard:
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.
146 Manually Deploying into WebLogic 9.2 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 Environment Preparing 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:
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.
Preparing the Environment 147 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:
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:
148 Manually Deploying into WebLogic 9.2 e. Click New, enter the server name (for example:
Starting Servers
➤ To start servers, do one:
● Navigate to Environment > Clusters >
● Using the command line, enter: %DOMAIN_DIR%\bin\startManagedWebLogic.sh
Deploying Application Servers in a Cluster Follow 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:
with the following content, replacing
Deploying Workspace into WebLogic 149 JAVA_OPTIONS="- Djavax.xml.parsers.SAXParserFactory=org.apache.xerces.jaxp.SAXParserFacto ryImpl ${JAVA_OPTIONS}"; export JAVA_OPTIONS cd
Note: All parent folders should be created manually.
For example: LIB_DIR=/home/hyperion/Hyperion/BIPlus/lib; export LIB_DIR EXT_PRE_CLASSPATH=${LIB_DIR}/iona63.jar:${LIB_DIR}:${EXT_PRE_CLASSPATH}; export EXT_PRE_CLASSPATH JAVA_OPTIONS="- Djavax.xml.parsers.SAXParserFactory=org.apache.xerces.jaxp.SAXParserFacto ryImpl ${JAVA_OPTIONS}"; export JAVA_OPTIONS cd /home/hyperion/bea/user_projects/domains/BIPlus_domain/bin ./startManagedWebLogic.sh workspace http://localhost:7001
2 Create the following shutdown script:
with the followng content, replacing
Deploying Workspace
➤ To deploy Workspace: 1 Create following file with execute permissions and set environment variables:
150 Manually Deploying into WebLogic 9.2 2 Run the following script: #!/bin/sh JAVA_HOME=
if [[ ! -d "${BIPLUS_HOME}/InstallableApps" ]]; then print "ERROR: BIPLUS_HOME environment variable isn't set or it points to an invalid BIPlus home directory name" exit 1 else if [[ ! -x "${JAVA_HOME}/bin/jar" ]]; then print "ERROR: JAVA_HOME environment variable isn't set or it points to an invalid JDK directory name" exit 1 else if [ -r "${BIPLUS_HOME}/InstallableApps/workspace.war" ]; then printf "ERROR: Can't locate workspace.war file in the ${BIPLUS_HOME}/InstallableApps directory" else echo "Unpacking workspace.war...\n" WAR_HOME=${BIPLUS_HOME}/InstallableApps
WEBAPP_DIR=${BIPLUS_HOME}/AppServer/InstalledApps/WebLogic/9.2/Workspace /applications/workspace mkdir -p ${WEBAPP_DIR}
cd ${WEBAPP_DIR} ${JAVA_HOME}/bin/jar -xf ${WAR_HOME}/workspace.war echo "Done" fi fi fi
Note: Replace
3 Use the following script to start the WebLogic Server Administration Console:
4 Start the workspace server using the startup script created in pre-deployment. For example:
5 In a Web browser, enter the following URL: http://
where
Deploying Workspace into WebLogic 151 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.
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-root b.+/app c.+/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 Workspace Post-deployment for Workspace involves creating context.properties.
➤ To create context.properties: 1 With a text editor, create:
152 Manually Deploying into WebLogic 9.2 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
● Post-deployment for Financial Reporting
Pre-deployment for Financial Reporting
➤ To pre-deploy Financial Reporting: 1 Create the following startup script:
with the following content, replacing
Note: All parent folders should be created manually.
For example: cd /home/hyperion/Hyperion/BIPlus/InstallableApps . /home/hyperion/Hyperion/BIPlus/InstallableApps/freporting_web.env cd /home/hyperion/bea/user_projects/domains/biplus_domain/bin ./startManagedWebLogic.sh FinancialReporting http://localhost:7001
Deploying Financial Reporting into WebLogic 153 2 Create the following shutdown script:
with the following content, replacing
Deploying Financial Reporting
➤ To deploy the Financial Reporting Web application: 1 Create following file with execute permissions and set environment variables:
2 Run the following script: #!/bin/sh
JAVA_HOME=
if [[ ! -d "${BIPLUS_HOME}/InstallableApps" ]]; then print "ERROR: BIPLUS_HOME environment variable isn't set or it contains an invalid BIPlus home directory name" exit 1 else if [[ ! -x "${JAVA_HOME}/bin/jar" ]]; then print "ERROR: JAVA_HOME environment variable isn't set or it contains an invalid JDK directory name" exit 1 else if [ -r "${BIPLUS_HOME}/InstallableApps /HReports.ear" ]; then printf "ERROR: Can't locate HReports.ear file in the ${BIPLUS_HOME}/InstallableApps directory" else echo "Unpacking HReports.ear..." EAR_HOME=${BIPLUS_HOME}/InstallableApps TMP_DIR=${EAR_HOME}/tmp/fr
154 Manually Deploying into WebLogic 9.2
WEBAPP_DIR=${BIPLUS_HOME}/AppServer/InstalledApps/WebLogic/9.2/Financial Reporting/applications/HReports.ear
mkdir -p ${TMP_DIR} mkdir -p ${WEBAPP_DIR}
cd ${WEBAPP_DIR} ${JAVA_HOME}/bin/jar -xf ${EAR_HOME}/HReports.ear META-INF
cd ${TMP_DIR} ${JAVA_HOME}/bin/jar -xf ${EAR_HOME}/HReports.ear HReports.war hr.war
mkdir -p ${WEBAPP_DIR}/HReports.war mkdir -p ${WEBAPP_DIR}/hr.war
cd ${WEBAPP_DIR}/HReports.war ${JAVA_HOME}/bin/jar -xf ${TMP_DIR}/HReports.war cd ${WEBAPP_DIR}/hr.war ${JAVA_HOME}/bin/jar -xf ${TMP_DIR}/hr.war
rm -rf ${TMP_DIR} echo "Done" fi fi fi
Note: Replace
3 Copy the files listed below to:
From
From
4 Start the FinancialReporting server using the startup script created during pre-deployment. For example:
5 Login in to your WebLogic Admin Console using the following URL: http://
where
Deploying Financial Reporting into WebLogic 155 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 When 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. 13 Select I will make the deployment accessible from the following location. 14 Click Finish. 15 Click Activate changes. 16 Start the application (turn application state from Prepared to Active).
Post-deployment for Financial Reporting
➤ To post-deploy Financial Reporting: 1 Copy .hyperion-
Deploying Web Analysis into WebLogic Deploying 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: 1 Create the following startup script:
156 Manually Deploying into WebLogic 9.2 with the following content, replacing
Note: All parent folders should be created manually.
For example: . /home/hyperion/Hyperion/BIPlus/InstallableApps/config/wa_env.sh cd /home/hyperion/bea/user_projects/domains/BIPlus_domain/bin ./startManagedWebLogic.sh WebAnalysis http://localhost:7001
2 Create the following shutdown script:
replacing
Verifying Web Analysis Environment Variables Verify that
ARBORPATH=
PATH=
ICU_DATA=
EXT_PRE_CLASSPATH=
Deploying Web Analysis into WebLogic 157 One of the following:
● Linux and Solaris: LD_LIBRARY_PATH=
● HP-UX: SHLIB_PATH=
● IBM-AIX: LIBPATH=
Deploying Web Analysis
➤ To deploy the Web Analysis Web application: 1 Create following file with execute permissions and set environment variables:
2 Run the following script: #!/bin/sh
JAVA_HOME=
if [[ ! -d "${BIPLUS_HOME}/InstallableApps" ]]; then print "ERROR: BIPLUS_HOME environment variable isn't set or it contains an invalid BIPlus home directory name" exit 1 else if [[ ! -x "${JAVA_HOME}/bin/jar" ]]; then print "ERROR: JAVA_HOME environment variable isn't set or it contains an invalid JDK directory name" exit 1 else if [ -r "${BIPLUS_HOME}/InstallableApps/WebAnalysis.ear" ]; then printf "ERROR: Can't locate WebAnalysis.ear file in the ${BIPLUS_HOME}/InstallableApps directory" else echo "Unpacking WebAnalysis.ear..." EAR_HOME=${BIPLUS_HOME}/InstallableApps TMP_DIR=${EAR_HOME}/tmp/wa
WEBAPP_DIR=${BIPLUS_HOME}/AppServer/InstalledApps/WebLogic/9.2/WebAnalys is/applications/WebAnalysis.ear
mkdir -p ${TMP_DIR} mkdir -p ${WEBAPP_DIR}
158 Manually Deploying into WebLogic 9.2 cd ${WEBAPP_DIR} ${JAVA_HOME}/bin/jar -xf ${EAR_HOME}/WebAnalysis.ear META-INF
cd ${TMP_DIR} ${JAVA_HOME}/bin/jar -xf ${EAR_HOME}/WebAnalysis.ear WebAnalysis.war
mkdir -p ${WEBAPP_DIR}/WebAnalysis.war cd ${WEBAPP_DIR}/WebAnalysis.war ${JAVA_HOME}/bin/jar -xf ${TMP_DIR}/WebAnalysis.war
rm -rf ${TMP_DIR} echo "Done" fi fi fi
Note: Replace
3 Start the WebAnalysis server using the startup script created during pre-deployment. For example:
4 Log on to your WebLogic Admin Console using the following URL: http://
where
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. 12 Select I will make the deployment accessible from the following location. 13 Click Finish. 14 Click Activate changes. 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.
Deploying Web Analysis into WebLogic 159 Note:
Configuring a Web Server for WebLogic 9.2 Hyperion 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-in The 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:
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:
to the
❍ 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:
replacing
160 Manually Deploying into WebLogic 9.2 LoadModule weblogic_module modules/mod_wl_20.so
Configuring a Web Server for WebLogic 9.2 161 PathTrim / KeepAliveEnabled ON KeepAliveSecs 20 WeblogicCluster
162 Manually Deploying into WebLogic 9.2 KeepAliveSecs 20 WeblogicCluster
Configuring a Web Server for WebLogic 9.2 163
164 Manually Deploying into WebLogic 9.2
Configuring a Web Server for WebLogic 9.2 165 KeepAliveSecs 20 WeblogicCluster
c. Open:
and add the following lines, replacing
3 Restart the Apache Web Server. 4 Test the plug-in by using a URL:
● Financial Reporting—http://
● WebAnalysis—http://
166 Manually Deploying into WebLogic 9.2 ● Workspace—http://
Testing Module Availability For each of the products used, verify the setup by using the URLs below.
Product URL1 Expected Result
Workspace http://
Financial Reporting http://
Web Analysis http://
1URL: Where
Testing Module Availability 167 168 Manually Deploying into WebLogic 9.2 APPENDIX Manually Deploying into E WebSphere 5.1.1.7
In This Appendix Prerequisites ...... 170 Deploying Workspace into WebSphere ...... 170 Deploying Financial Reporting into WebSphere ...... 173 Deploying Web Analysis into WebSphere ...... 176 Configuring Apache or IBM HTTP with WebSphere 5.1 ...... 179 Testing Module Availability ...... 182
Manually Deploying into WebSphere 5.1.1.7 169 Prerequisites
● Hyperion Shared Services
❍ Install Hyperion Shared Services.
❍ Verify that it is up and running.
❍ Test the installation and make sure that you can log into Shared Services. http://
For example: http://localhost:58080/interop/index.jsp
● 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 was not selected, you must re-run Hyperion Configuration Utility for the Application Server Deployment task. You need at least 1 GB available disk space in the temporary path before deploying.
Deploying Workspace into WebSphere
Deploying Workspace
➤ To deploy the Workspace Web Application: 1 Run your WebSphere Server. For example: /IBM/AppServer/bin/startServer.sh server1
2 Login into WebSphere Administrative Console by using the URL: http://
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.
170 Manually Deploying into WebSphere 5.1.1.7 5 Create a new application: a. Click Applications > Install New Application. b. Choose Server path and enter the path and file name:
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. 10 Navigate to Servers > Application Servers. 11 In the Message window, click Save. 12 In the Save to Master Configuration window, click Save.
Deploying Workspace into WebSphere 171 Creating context.properties
➤ To create context.properties: 1 With a text editor, create:
2 Add the following values: 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: Reports=Y HPSU=Y HPS=N HMB=N ChangeManagement=Y Analyzer=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)
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:
172 Manually Deploying into WebSphere 5.1.1.7 Deploying Financial Reporting into WebSphere
Deploying
➤ To deploy the Financial Reporting Web application: 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. 3 Navigate to Servers > Application Servers. 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. 8 Navigate to Servers > Application Servers. 9 Click FinancialReporting. 10 Click Web Container. 11 Optional: Click on Thread Pool and adjust the settings for your user base. For example, for many concurrent users, increase the Maximum Size. 12 Click OK. 13 Click HTTP transports. 14 Verify the Port assignments for this application server. 15 Navigate to Servers > Application Servers. 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 170. 20 Click Host Aliases. 21 Click New.
Deploying Financial Reporting into WebSphere 173 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
29 Click Next. 30 Select the Virtual Host created when deploying Workspace, step 4 on page 170. 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.
174 Manually Deploying into WebSphere 5.1.1.7 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: /usr/WebSphere/AppServer/Bin/startServer.sh FinancialReporting
Configuring
● “Changing the Default Cookie Path” on page 175
● “Enabling UTF-8 Encoding” on page 175
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 Encoding After 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 Financial Reporting into WebSphere 175 Deploying Web Analysis into WebSphere
Pre-Deployment for Web Analysis Manually create
with the following contents: HYPERION_HOME=
ARBORPATH=$HYPERION_HOME/common/EssbaseRTC/9.2.1 export ARBORPATH
PATH=$HYPERION_HOME/common/ADM/9.2.0/lib:$HYPERION_HOME/common/SAP/bin: $ARBORPATH/bin:
Note: In the following lines, use LD_LIBRARY_PATH for Solaris/Linux, LIBPATH for AIX, and SHLIB_PATH for HP-UX. The code in the following lines would be for Solaris/Linux, since it uses LD_LIBRARY_PATH.
LD_LIBRARY_PATH=HYPERION_HOME/common/EssbaseRTC/9.2.1/bin:$HYPERION_HOM E/common/ADM/9.2.0/Essbase/9.2.0/bin:$HYPERION_HOME/common/SAP/lib export LD_LIBRARY_PATH
ICU_DATA=$HYPERION_HOME/common/ADM/9.2.0/Essbase/9.2.0/bin/HssEssDriver/ export ICU_DATA
Ensure
Deploying
➤ To deploy the Web Analysis Web application: 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. 3 Navigate to Servers > Application Servers. 4 Click New. 5 For Server Name, enter WebAnalysis. Leave other options with their default values, or modify to suit your WebSphere infrastructure.
176 Manually Deploying into WebSphere 5.1.1.7 6 Click Next. 7 Click Finish. 8 Navigate to Servers > Application Servers. 9 Click WebAnalysis. 10 Click Web Container. 11 Optional: Click on Thread Pool and adjust the settings for your user base. For example, for many concurrent users, increase the Maximum Size. 12 Click OK. 13 Click HTTP transports. 14 Verify the Port assignments for this application server. 15 Navigate to Servers > Application Servers. 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 170. 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
Deploying Web Analysis into WebSphere 177 29 Click Next. 30 Select the Virtual Host created when deploying Workspace, step 4 on page 170. 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: /usr/WebSphere/WebSphere/AppServer/bin/startServer.shWebAnalysis
Configuring
● “Changing the Default Cookie Path” on page 175
● “Setting OS Library Search Path for Financial Reporting” on page 179
Changing the Default Cookie Path
➤ 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.
178 Manually Deploying into WebSphere 5.1.1.7 Setting OS Library Search Path for Financial Reporting
➤ To set the operating system library search path: 1 Navigate to Application Servers > FinancialReporting > Process Definition > Environment Entries. 2 Create a new OS library search path entry (for example: LIBPATH on AIX, LD_LIBRARY_PATH on Solaris), and populate with the
Configuring Apache or IBM HTTP with WebSphere 5.1 This 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:
To:
Configuring Apache or IBM HTTP with WebSphere 5.1 179
To: 180 Manually Deploying into WebSphere 5.1.1.7 Name="/WebAnalysis/hfmtemplates/*" /> 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: 6 Copy 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 Apache or IBM HTTP with WebSphere 5.1 181 Testing Module Availability Test the modules availability: http:// where 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:// which returns the Financial Reporting internal build number. 182 Manually Deploying into WebSphere 5.1.1.7 APPENDIX Manually Deploying into F WebSphere 6.1 In This Appendix Prerequisites ...... 184 Preparing the WebSphere Environment ...... 184 Deploying Workspace...... 185 Deploying Financial Reporting ...... 188 Deploying Web Analysis ...... 190 Configuring Apache or IBM HTTP with WebSphere 6.1 ...... 192 Testing Module Availability ...... 195 Manually Deploying into WebSphere 6.1 183 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:// For example: http://localhost:58080/interop/index.jsp ● Install Reporting and Analysis 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. You need at least 1 GB available disk space in the temporary path before deploying. Note: On UNIX systems, Reporting and Analysis should not be installed as root. Preparing the WebSphere Environment You must have a configured Web server before proceeding. See IBM's document: http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/topic/com.ibm.webs phere.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. 184 Manually Deploying into WebSphere 6.1 2 Create a new application server for each module that will be deployed (freporting, webanalysis, workspace) by running the wsadmin.sh 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 Definitions If 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 > Deploying Workspace ➤ To deploy : 1 Log in to the WebSphere console for the profile containing your application servers. 2 Navigate to Applications > Install New Application. Deploying Workspace 185 3 Supply the full server path to workspace.war; by default: 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 Authentication If 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: substituting substituting 186 Manually Deploying into WebSphere 6.1 Creating context.properties ➤ To create context.properties: 1 With a text editor, create: Note: In the same directory, you can start with context.properties.sample. Uncomment and set the value for each property. 2 Add the following values: Set “Y” if components are installed, “N” if components are not installed: Reports=Y HPSU=Y HPS=N HMB=N ChangeManagement=Y Analyzer=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 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. Deploying Workspace 187 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 replace $J(HYPERION_HOME) with your actual HYPERION_HOME location. In the line: DEPLOYMENT_PATH=$J(servletConfig.deploymentPath) replace $J(servletConfig.deploymentPath) with the actual location of deployed Workspace application. The default is: Deploying Financial Reporting ➤ To deploy Financial Reporting: 1 Log in to the WebSphere console for the profile containing your application servers. 2 Navigate to Applications > Install New Application. 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. 188 Manually Deploying into WebSphere 6.1 Configuring Financial Reporting ➤ To configure Financial Reporting : 1 Log in to the WebSphere Administrative Console. 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 Perform the following: a. If the Reporting and Analysis installation is owned by a different operating system user than owns WebSphere, copy ${HOME}/.hyperion_ e. Paste the value returned for the appropriate variable as returned by the Note: These values may not be optimal for your user load, and may need to be adjusted. 8 Add the additional Generic JVM argument: -Djava.awt.headless=false 9 Copy the files listed below to: Where Deploying Financial Reporting 189 From From 10 Click OK, then save all changes. 11 Start or restart the freporting application server. Deploying Web Analysis Deploying ➤ To deploy Web Analysis: 1 Log in to the WebSphere Administrative Console for the profile containing your application servers. 2 Navigate to Applications > Install New Application. 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 Variables ➤ To create Env ironment var iables: 1 Log in to the WebSphere Administrative Console. 190 Manually Deploying into WebSphere 6.1 2 In the left pane, navigate to Servers > Application Servers > Your WebAnalysis server. 3 In the right pane click Java and Process Management > Process Definition > Environment Entries. 4 Create the following Environment Variables by clicking New in the right pane: HYPERION_HOME= BIPLUS_HOME= ARBORPATH= One of the following: ● Linux and Solaris: LD_LIBRARY_PATH= ● HP-UX: SHLIB_PATH= ● IBM AIX: LIBPATH= 5 Click New and enter DISPLAY in the Name field. Specify the Xvfb address configured for the Reporting and Analysis host machine. 6 Click OK and then save all changes. Creating a WebSphere Shared Library for SAP Authentication and Reporting If 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: 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 WebAnalysis. 4 Click Apply. 5 Click New. Deploying Web Analysis 191 6 Specify Name as: SAP_LIBRARY. 7 Specify Classpath as: where where 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. 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 Enter the following in Classpath, replacing 8 Click OK, then save all changes. 9 Start or restart the application server. Configuring Apache or IBM HTTP with WebSphere 6.1 This 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. 192 Manually Deploying into WebSphere 6.1 3 Select your Web server, and click Generate Plug-in. 4 Copy: into: 5 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: To: Configuring Apache or IBM HTTP with WebSphere 6.1 193 Web Analysis: Change the URI group definition which contains this single line: To: 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 194 Manually Deploying into WebSphere 6.1 Workspace: Alias /workspace " Alias /wsmedia " Alias /InsightInstaller " Web Analysis: Alias /WebAnalysis " b. Insert the following lines at the end of file: LoadModule was_ap20_module " where Testing Module Availability For each of the products used, verify the setup by using the URLs below. Product URL1 Expected Result Workspace http:// Financial Reporting http:// Web Analysis http:// 1URL: Where Testing Module Availability 195 196 Manually Deploying into WebSphere 6.1 APPENDIX G G ActiveX In This Appendix Whitepaper ...... 198 Sample Policy File ...... 199 ActiveX 197 Whitepaper Hyperion 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 198 ActiveX 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 File The components enable the XML parsing routines in Internet Explorer. Sample policy file: CLASS USER CATEGORY "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} Sample Policy File 199 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 Explorer END CATEGORY ;; WindowsComponents 200 ActiveX Index A launching, 69 ADM driver, enabling the, 78 log file, 79 AJAX, 198 order of tasks, 68 Apache, configuring with WebSphere, 179 ports for application servers, 72 Application Layer, 13 post configuration tasks, ?? to 85 Services Tier, 13 prerequisites, 23, 68 Web Tier, 13 reconfiguration, 85 application server host names, specifying, 69 Shared Services registration, 70 troubleshooting, 79 B upgrades, 68 configuring backing up repositories, 33 Apache, 179 browsers Apache with Weblogic, 138 settings, 50 completing module-specific configurations, 76 Web requirements, 42 database software for the Repository, 34 Financial Reporting, 78 C IBM DB2, 34 C++, updating, 40 IBM Websphere, 55 cell documents, print, 51 installation, 32 Client Layer, 11 Microsoft SQL Server, 37 command line installer, 49 Oracle, 38 Common Administration Services, 16 Production Reporting engine for Interactive components Reporting, 77 client tier, 31 relational databases, 72 clustered, 46 Web environment, 42 database tier, 27 Workspace, 76 distributed, 46 configuring Sharedd Services, 114 middle tier, 30 connections, ODBC, creating, 41 replicated, 46 considerations, RDBMS, 33 configuration files, 102 context.properties for WebSphere 6.1, 187 Configuration Utility context.properties, forWebLogic 9.1, manual deployment, about, 71 152 application server deployment, 72 cookie path, 189 database configuration, 71 cookie path, changing, 175, 178 database user rights, 68 creating Index A 1 user accounts, 49 Financial Reporting Servers, 15 custom install, 62 Financial Reporting, customizing service ports for Reporting and Analysis, 77 deploying Financial Reporting, 103 firewalls D configurations, 44 DMZ, 43 databases Web server installation and, 42 creating users, 37 functional services, 15 layer, 18 repository size recommendations, 34 supported in Migration Utility, 95 G to store metadata, 37 GSM host and port, specifying, 77 DB2COMM, 36 DB2DIR, 36 H DB2INSTANCE, 36 hardware, requirements, 26 default cookie path, changing, 175, 178 heap size, adjusting, 173, 177 deploying high-level task flow, 20 Financial Reporting into Websphere, 173, 176 host name, logical values, 174, 177 Web Analysis into Websphere, 173, 176 HTTP connector plug-in ports, specifying, 69 Workspace Web Application with WebSphere, 170 HTTP Server plug-in deregistering Reporting and Analysis from Shared Services, Configuration Utility support, 75 71 enabling, 75 distributed components, 46 manual support, 76 DMZ support, firewall, 43 requirements, 41 Hyperion Home E changing the location, 60 enabling defining a location, 60 HTTP Server plug-in, 75 overview, 60 Planning ADM driver, 78 Hyperion License Server, 20, 58 UTF-8 encoding, 175 Hyperion System 9 BI+ environment variables, 83 Reporting Solution Architecture, 11 UNIX, 40 Hyperion System 9, about, 10 Web Analysis, 157 error messages, 39 I IBM DB2 F configuring, 34 Financial Reporting, 103, 188 to 189 troubleshooting, 34 completing configurations, 78 Version 7.2 configuration tasks, 33 deploying into WebLogic, 136 to 137 Impact Manager Services, 16 enabling the Planning ADM driver, 78 installation HReports.ear, 105 UNIX, 48 manual deployment installation wizards, using, 59 WebLogic, 153, 156 installer, command line, 49 Report Server, configuring, 79 installers for Reporting and Analysis, 59 workspace, print service, and scheduler, 79 Interactive Reporting Services, 15 2 Index D J planning client-tier components, 31 JDBC driver, and IBM DB2, 36 database tier components, 27 installation, ?? to 55 L middle-tier components, 30 launching Reporting and Analysis modules, 84 port number, changing, 84 LD_LIBRARY_PATH, 40 prepare WebSphere environment, 184 LIBPATH, 40 prerequisites, 32, 184 License Server, 20, 58 print limitations, to distributing and replicating components, 47 cell documents, 51 login testing, shared services provisioning, 82 requirements, 51 to 52 privileges, granting, 38 M Production Reporting installing, 48 maintenance, service packs, 50 management services, 14 post Configuration tasks, 83 manual deployment, 100 to 103, 105, 108 to 109, 111, recreating the executables, 83 184 to 185, 187 to 189, 191 to 192 Service, 16 Microsoft SQL Server setting up the environment variables, 83 configuring, 37 provision the native Shared Services, 82 login, 37 provisioning an administrator, 82 Migration Utility after installing, 96 R installing, ?? to 96 RDBMS, considerations, 33 overview, 94 replicated components, 46 migration, repository, 33 Report Server, configuring, 79 module installers, overview, 59 Reporting, 10 repository N backup, 33 network computing, virtual, 48 databases, size recommendations, 34 migration, 33 O requirements hardware, 26 OC4J instance, 103, 106 HTTP Server, 41 ODBC connections, creating, 41 print, 51 to 52 OHS routing for Workspace, 101 software, 27 operating system, setting search path, 179 temporary space, 47 Oracle configuring, 38 third party, 31 error messages, 39 Web browsers, 42 Oracle 10g Release 3, 99 to 103, 105 to 106, 108 to 109, 111, web client, 31 114 reviewing selected components, 62 P S Performance Scorecard Services, 16 sample policy file, 199 PHYSNAME, 37 SAP as an authentication provider, 100 Index J 3 SAP authentication T shared library for, 191 temporary space, requirements, 47 scheduler, configuring testing configuration, 79 Workspace Web application, 172 secure sockets-capable servers, 42 testing module availability, 115, 167 security third party requirements, 31 Interactive Reporting, 45 overview, 43 Servers, 72 U services UNIX Common Administration, 16 installation mechanisms, 48 Financial Reporting, 15 updating Impact Manager, 16 C++, 40 Interactive Reporting, 15 updating configuration files, 102 management, 14 Upgrading, 90 Upgrading, prerequisites, 90 Performance Scorecard, 16 user accounts, creating, 49 Production Reporting, 16 user provisioning, 43 starting up, 80 Migration Utility, 94 tier summary, 17 setting OS library search path, 179 V setting up virtual host definitions, 185 environment variables, 83 virtual network computing, 48 shared pool size, Oracle and, 39 VNC, 48 Shared Services provisioning an administrator, 82 W Single Sign-on, 111 Web Analysis, 106, 190 to 192 single sign-on, 114 single sing-on configuring WebLogic, 136 to 137 Oracle, 114 deploying into WebLogic, 136 to 137 Smart View Services, 17 environment variables, 173, 176 software requirements, 27 Web Analysis.ear, 108 space requirements, temporary, 47 WebLogic 9.2, manual deployment, 158 specifying Web browsers requirements, 42 application server host names, 69 Web browsers, requirements, 42 GSM host and port, 77 web client requirements, 31 HTTP connector plug-in ports, 69 Web server, 109 SQL Server, configuring, 37 WebLogic Sun Java System Application Server configuring manually deploying, ?? to 132 Apache, 138 system permissions, 50 Financial Reporting, 136 to 137 system requirements production mode, 134 Migration Utility, 94 Web Analysis, 136 to 137 testing connections, 144 WebLogic 9.2 manual deployment, 149 4 Index T WebLogic 9.2, manual deployment Financial Reporting, 153, 156 Web Analysis, 156 to 158 web-server plug-in, enabling, 75 WebSphere, 179 configuration requirements prior to installation, 42 configuring Apache configuring Apache with Websphere Application Server, 179 deploying workspace, 170 enabling UTF-8 encoding, 175 testing connections, 182 Web Analysis environment variables, 176 WebSphere 6.1, 184 to 185, 187 to 189, 191 to 192 WebSphere 6.1, manual deployment, 184, 190 Whitepaper, 198 Windows user accounts, creating, 49 wizards, 59 Workspace, 185, 187 completing configurations, 76 configuring Production Reporting engine for Interactive Reporting, 77 creating context.properties, 101 customizing context path, 76 service ports, 77 deploying into WebSphere, 170 deployment, 149 specifying the GSM host and port, 77 starting after deploying with WebSphere, 172 Web application, 170 WorkspaceOC4J instance, 99 Index W 5