HYPERION® REPORTING AND ANALYSIS – SYSTEM 9 RELEASE 9.3.1
INSTALLATION GUIDE FOR WINDOWS Reporting and Analysis Installation Guide for Windows, 9.3.1 Copyright © 1989, 2008, Oracle and/or its affiliates. All rights reserved. Authors: Marilyn Ghilardi The Programs (which include both the software and documentation) contain proprietary information; they are 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 ...... 13 Hyperion and Enterprise Performance Management ...... 13 About Reporting and Analysis ...... 13 Reporting and Analysis Architecture ...... 14 Client Layer ...... 14 Application Layer ...... 15 Application Layer Web Tier ...... 16 Web Server Use in Hyperion ...... 16 Application Layer Services Tier ...... 17 Database Layer ...... 22
Chapter 2. Planning the Installation ...... 23 Preparing an RDBMS for the Reporting and Analysis Repository ...... 23 Backing Up a Repository ...... 23 Configuring Database Software for the Reporting and Analysis Repository ...... 24 Configuring IBM DB2 ...... 24 IBM DB2 with Web Analysis ...... 27 Configuring Microsoft SQL Server ...... 27 Configuring Oracle ...... 28 Manually Creating Tables ...... 31 Database Storage Parameters for Oracle ...... 31 Creating ODBC Connections ...... 32 Microsoft SQL Server Analysis Services (SSAS) Connections ...... 32 SSAS 2005 ...... 32 SSAS 2000 ...... 33 Obtaining and Preparing Pre-requisite Software ...... 33 SAP Data Source Access and Authentication ...... 33 Configuring SAP Data Source Access and Authentication ...... 34 Installing the IBM Global Security Kit for WebSphere Express ...... 34 Web Environment ...... 35 Application Server Setting ...... 35 Web Browser Requirements ...... 35
Contents iii Configuring a Web Environment ...... 35 Financial Reporting and Web Analysis Web Server Environment ...... 35 Financial Management Web Server Environment ...... 36 Browser Settings ...... 36 Module-specific Prerequisites ...... 37 Configuring a Production Reporting Server Installation ...... 37 Financial Management ...... 37 Financial Reporting Print Server ...... 37 Importing Financial Reporting Content into Microsoft Word and Powerpoint . . . 37 Cell Attachment Support and Configuration Requirements ...... 37 Print Server Requirements ...... 39 Installing Considerations ...... 39 Satisfying Temporary Space Requirements ...... 39 Command Line Processor Considerations ...... 40 Port Numbers Used by Hyperion Products ...... 40
Chapter 3. Installing Reporting and Analysis ...... 41 Prerequisites ...... 41 Terminal Services Configuration ...... 41 Reporting and Analysis Installers ...... 42 Reporting and Analysis Module Installers ...... 42 About Hyperion Home ...... 44 Hyperion Home Location ...... 44 Files Installed in the HYPERION_HOME Directory ...... 44 Changing the Hyperion Home Location ...... 45 Installing Reporting and Analysis ...... 46 Running Silent Installations ...... 48
Chapter 4. Configuring Reporting and Analysis ...... 49 Hyperion Configuration Utility ...... 49 Task Sequence ...... 50 Restricted Characters ...... 50 Troubleshooting ...... 50 Satisfying Initial Requirements ...... 50 Configuring Product Upgrades ...... 50 Configuring Reporting and Analysis ...... 51 Registering With Shared Services ...... 52 Configuring Databases ...... 53 Microsoft SQL Server Windows Authentication ...... 54
iv Contents Specifying Application Server Hostnames and Web Server Connector Plug-in Ports ...... 54 Deploying to the Application Server ...... 55 What Happens During Deployment ...... 56 WebSphere and WebLogic 9.1.x ...... 56 WebLogic 8.1.x ...... 57 Enabling the Web Server Plug-in ...... 57 Hyperion Configuration Utility Web Server Plug-in Support ...... 58 Web Server Plug-in Manual Support ...... 58 Completing Module-Specific Configurations ...... 59 Workspace Configurations ...... 59 Customizing the Context Path ...... 60 Specifying the GSM Host and Port ...... 60 Customizing Service Ports for Reporting and Analysis ...... 60 Configuring the SQR Production Reporting Engine for Interactive Reporting .... 60 Interactive Reporting Configuration ...... 61 Financial Reporting Configurations ...... 61 Enabling the Planning ADM Driver ...... 61 Enabling the Analytic Provider Services Driver ...... 62 Print Server Configuration ...... 62 Workspace, Print Server, and Scheduler Server Configurations ...... 63 Report Server Configuration ...... 63 Web Analysis Configuration - Enabling the Analytic Provider Services Driver ...... 63 SQR Production Reporting Configurations ...... 64 Reconfiguring Products ...... 64 Testing Module Availability ...... 64 Post Configuration Tasks ...... 65 Error Messages When Testing Module Availability ...... 65 Post Configuration Tasks ...... 66 Configuring WebLogic 9.x OpenJMS for Web Analysis ...... 66 Installing OpenJMS ...... 66 Configuring OpenJMS Databases ...... 66 Configuring and Starting OpenJMS Server ...... 68 Configuring Web Analysis to use OpenJMS ...... 68 Setting up WebSphere 6.0 OpenJMS and Web Analysis ...... 70 Configuring WebSphere 6.0 Embedded Messaging and Web Analysis Cluster (Reporting and Analysis ) ...... 70 Configure Web Analysis to use WebSphere JMS ...... 71 Verifying Startup Dependencies ...... 71
Contents v Starting Shared Services ...... 72 Verifying Successful Startup of Shared Services ...... 73 Stopping Shared Services ...... 74 Reporting and Analysis Administrator User ...... 75 Launching Reporting and Analysis Modules ...... 75 Adding Content Expiration Headers ...... 76 Changing the Apache Web Server Listen Port ...... 77 Customizing Ports Used by Interactive Reporting Service, Interactive Reporting Job Service and Interactive Reporting Data Access Service ...... 77 Guidelines for Changing Port Ranges ...... 78 Service Types Used in irmconfig.xml ...... 78 Sample irmconfig.xml ...... 78 Setting up SiteMinder with Transparent Logon ...... 80 Prerequisites ...... 80 Enabling the SiteMinder Web Agent for Microsoft IIS ...... 81 Creating the IBM HTTP Server/Apache Web Agent Configuration File ...... 81 Configuring IBM HTTP Server/Apache SiteMinder Modules ...... 81 Configuring the SiteMinder Policy Server ...... 81 Setting up Workspace Web Application Parameters ...... 83 Setting the Trusted Password on the Authentication Service ...... 84 Configuring Shared Services ...... 84 Restarting Components ...... 84
Chapter 5. Uninstalling and Reinstalling Reporting and Analysis ...... 87 Prerequisites ...... 87 Deregistering Reporting and Analysis with Shared Services ...... 87 Uninstalling ...... 88 Reinstalling ...... 90 Reinstalling Services ...... 90 Reinstalling UIServices ...... 90 Reinstalling Client ...... 91
Chapter 6. Upgrading Reporting and Analysis from 9.x to 9.3.1 ...... 93 Prerequisites ...... 93 Upgrading ...... 94 Migrating Users and Groups ...... 95 Prerequisites ...... 95 About SyncCSSIdentity_BI Utility ...... 96 Running SyncCSSIdentity_BI utility ...... 96 Using Most Provider Types ...... 96
vi Contents Using Provider Type Sun One LDAP Server ...... 97 Upgrading Manually Deployed Web Applications ...... 97
Chapter 7. Installing the Reporting and Analysis Migration Utility ...... 99 Migration Utility ...... 99 Requirements ...... 100 Supported Source Databases ...... 100 Installing the Migration Utility ...... 101 After Installing the Migration Utility ...... 102
Chapter 8. Configuring a Web Server with Apache Tomcat ...... 103 Configuring Apache ...... 103 Copy Required Files to the Apache Machine ...... 103 Create the Tomcat Web Server Plug-in Configuration Files ...... 104 Enable the Tomcat Web Server Plug-in in httpd.conf ...... 105 Create Aliases for Workspace and Web Analysis ...... 106 Restart Apache and Test the Tomcat Web Server Plug-in ...... 106 Configuring IIS ...... 107 Copy Required Files to the IIS Machine ...... 107 Create the Tomcat HTTP Plug-in Configuration Files ...... 107 Create a Virtual Directory for the Tomcat HTTP Plug-in ...... 109 Register the Tomcat HTTP Plug-in as an ISAPI Filter ...... 109 Create Virtual Directory Aliases for Workspace and Web Analysis ...... 110 Restart IIS and Test the Tomcat HTTP Plug-in ...... 111
Chapter 9. Manually Deploying into Oracle 10g Release 3 (10.1.3.1.0) Application Server ...... 113 Prerequisites ...... 113 Deploying Workspace Web Application ...... 114 Creating an OC4J Instance ...... 114 Configuring the Workspace OC4J Instance ...... 114 Deploying workspace.war ...... 115 Configuring Workspace ...... 115 Enabling SAP as an Authentication Provider ...... 115 Creating context.properties ...... 116 Modifying portlet.xml ...... 117 Update Oracle HTTP Server Routing for Workspace ...... 118 Updating Configuration Files ...... 118 Deploying Financial Reporting ...... 119 Creating an OC4J Instance ...... 119 Configuring the FinancialReporting OC4J Instance ...... 120
Contents vii Deploying HReports.ear ...... 121 Deploying Web Analysis ...... 122 Creating an OC4J Instance ...... 122 Configuring the WebAnalysis OC4J Instance ...... 122 Deploying WebAnalysis.ear ...... 124 Configuring Oracle HTTP Server for Oracle 10g Release 3 ...... 125 Configuring Reporting and Analysis ...... 125 Configuring Financial Management ...... 127 Configuring Oracle Single Sign-on on Oracle 10g Release 3 ...... 127 Prerequisites ...... 127 Configuring the Oracle Application Server ...... 127 Configuring Shared Services ...... 131 Testing Module Availability ...... 131 Post Configuration Tasks ...... 132
Chapter 10. Manually Deploying into Oracle 10g Release 2 (10.1.2.0.2) Application Server ...... 133 Prerequisites ...... 133 Deploying Workspace Web Application ...... 134 Creating an OC4J Instance ...... 134 Configuring an OC4J Instance ...... 134 Deploying workspace.war ...... 135 Using Oracle Enterprise Manager ...... 135 Using Oracle Distributed Configuration Management Command Line Utility ..... 136 Configuring Workspace ...... 136 Enabling SAP as an Authentication Provider ...... 136 Creating context.properties ...... 137 Updating Configuration Files ...... 138 Modifying portlet.xml ...... 139 Deploying Financial Reporting ...... 139 Creating an OC4J Instance ...... 139 Configuring a FinancialReporting OC4J Instance ...... 140 Deploying HReports.ear ...... 142 Using Oracle Enterprise Manager ...... 142 Using Oracle Distributed Configuration Management Command Line Utility ...... 142 Deploying Web Analysis ...... 143 Creating an OC4J Instance ...... 143 Configuring the WebAnalysis OC4J Instance ...... 144 Environment Variables ...... 144 Deploying WebAnalysis.ear ...... 145 viii Contents Using Oracle Enterprise Manager ...... 145 Using Oracle Distributed Configuration Management Command Line Utility ..... 145 Configuring Oracle HTTP Server for Oracle 10g Release 2 ...... 146 Configuring Reporting and Analysis ...... 146 Configuring Performance Management Architect or Planning ...... 147 Configuring Financial Management ...... 148 Defining Additional Parameters for Workspace ...... 148 Configuring Oracle Single Sign-On on Oracle 10g Release 2 ...... 149 Prerequisites ...... 149 Configuring the Oracle Application Server ...... 149 Configuring Shared Services ...... 152 Testing Module Availability ...... 152 Post Configuration Tasks ...... 153
Chapter 11. Manually Deploying into WebLogic 9.1 ...... 155 Prerequisites ...... 155 Preparing the Environment ...... 155 Deploying Workspace into WebLogic ...... 156 Creating a New Domain ...... 156 Modifying setDomainEnv.cmd ...... 156 Deploying Workspace ...... 157 Modifying portlets.xml ...... 158 Post Deployment for Workspace ...... 159 Creating context.properties ...... 159 Deploying Financial Reporting into WebLogic ...... 159 Deploying Web Analysis into WebLogic ...... 160 Verifying Web Analysis Environment Variables ...... 160 Deploying Web Analysis ...... 160 Configuring a Web Server for WebLogic 9.1 ...... 161 Configuring Apache HTTP Plug-in ...... 161 Configuring for Reporting and Analysis and Hyperion Applications ...... 162 Configuring for Performance Management Architect ...... 169 Configuring for Financial Management ...... 169 Configuring for Performance Scorecard ...... 170 Configuring for Planning ...... 170 Configuring Microsoft IIS ...... 171 Configure Proxying by Path ...... 171 Register iisforward.dll with IIS ...... 172 Configure Proxy by File Extension ...... 173
Contents ix Restart IIS ...... 178 Testing Module Availability ...... 178 Post Configuration Tasks ...... 179
Chapter 12. Manually Deploying into WebLogic 8.1 ...... 181 Prerequisites ...... 181 Creating WebLogic Domains ...... 181 Deploying Workspace into WebLogic ...... 182 Modifying startWebLogic.bat ...... 182 Deploying Workspace ...... 183 Modifying portlets.xml ...... 184 Post Deployment for Workspace ...... 185 Compiling JSP ...... 185 Creating context.properties ...... 185 Deploying Financial Reporting into WebLogic ...... 186 Deploying Web Analysis into WebLogic ...... 186 Web Analysis Environment Variables ...... 186 Deploying Web Analysis ...... 187 Configuring a Web Server for WebLogic 8.1 ...... 187 Configuring Apache ...... 187 Configuring with Reporting and Analysis and Hyperion Applications ...... 188 Configuring with Performance Management Architect with Apache Web Server ...... 195 Configuring with Financial Management with Apache Web Server ...... 195 Configuring with Performance Scorecard with Apache Web Server ...... 196 Configuring with Planning with Apache Web Server ...... 196 Configuring Microsoft IIS ...... 197 Configure Proxying by Path ...... 197 Register iisforward.dll with IIS ...... 198 Configure Proxy by File Extension ...... 199 Restart IIS ...... 204 Testing Module Availability ...... 204 Post Configuration Tasks ...... 205
Chapter 13. Manually Deploying into WebSphere 6.1 ...... 207 Prerequisites ...... 207 Preparing the WebSphere Environment ...... 207 WebSphere ND ...... 208 WebSphere BASE/Express ...... 208 Add Virtual Host Definitions ...... 208
x Contents Deploying Workspace ...... 209 Creating a WebSphere Shared Library for SAP Authentication ...... 210 Assigning SAP_LIBRARY to Workspace ...... 210 Creating context.properties ...... 210 Modifying portlets.xml ...... 211 Configuring Workspace ...... 212 Deploying Financial Reporting ...... 213 Configuring Financial Reporting ...... 214 Deploying Web Analysis ...... 214 Deploying ...... 214 Environment Variables ...... 215 Creating a WebSphere Shared Library for SAP Authentication and Reporting ...... 215 Configuring Web Analysis ...... 216 Configuring a Web Server with WebSphere 6.1 Application Server ...... 217 Configuring Apache Server or IBM HTTP Server ...... 217 Configuring IIS ...... 219 Configuring Financial Management with a Web Server ...... 224 Configuring Financial Management with Apache Web Server or IBM HTTP Server ...... 224 Using Only IIS with Financial Management ...... 225 Testing Module Availability ...... 225 Post Configuration Tasks ...... 226
Chapter 14. Manually Deploying into WebSphere 6.0.2 ...... 227 Prerequisites ...... 227 Preparing the WebSphere Environment ...... 227 WebSphere ND ...... 228 WebSphere BASE/Express ...... 228 Add Virtual Host Definitions ...... 228 Deploying Workspace ...... 229 Creating a WebSphere Shared Library for SAP Authentication ...... 230 Assigning SAP_LIBRARY to Workspace ...... 231 Creating context.properties ...... 231 Modifying portlet.xml ...... 232 Configuring Workspace ...... 233 Deploying and Configuring Financial Reporting ...... 233 Deploying Web Analysis ...... 234 Deploying ...... 234 Environment Variables ...... 236 Creating a WebSphere Shared Library for SAP Authentication and Reporting ...... 236
Contents xi Configuring Web Analysis ...... 237 Configuring a Web Server with WebSphere 6.0.2 Application Server ...... 237 Configuring Apache Server or IBM HTTP Server ...... 237 Configuring IIS ...... 240 Configuring Financial Management with a Web Server ...... 245 Configuring Financial Management with Apache Web Server or IBM HTTP Server ...... 245 Using Only IIS with Financial Management ...... 245 Testing Module Availability ...... 245 Post Configuration Tasks ...... 246
Appendix A. ActiveX ...... 247 Whitepaper ...... 247 Sample Policy File ...... 248
Index ...... 251
xii Contents Reporting and Analysis 1 Architecture Overview
In This Chapter Hyperion and Enterprise Performance Management ...... 13 About Reporting and Analysis ...... 13 Reporting and Analysis Architecture ...... 14
Hyperion and Enterprise Performance Management Hyperion offers a comprehensive Enterprise Performance Management (EPM) system that consists of these products:
● Oracle's Hyperion® Reporting and Analysis – System 9—Management reporting including query and analysis in one coordinated environment
● Oracle's Hyperion Applications—Coordinated planning, consolidation, and scorecarding applications
● Oracle's Hyperion® Foundation Services—Used to ease installation and configuration, provide metadata management, and support a common Microsoft Office interface
About Reporting and Analysis 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 Web-based 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 queries, 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
Hyperion and Enterprise Performance Management 13 Reporting and Analysis, which includes Oracle's Hyperion® Essbase® – System 9, is part of a comprehensive EPM system that integrates this business intelligence platform with Oracle's Hyperion financial applications and Oracle's Hyperion® Performance Scorecard – System 9.
Reporting and Analysis Architecture The Reporting and Analysis environment is organized into three layers:
● “Client Layer” on page 14
● “Application Layer” on page 15
● “Database Layer” on page 22
Client 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:
● Oracle's Hyperion® Workspace—Web-based DHTML 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:
❍ Oracle's Hyperion Essbase — System 9—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
● Authoring Studios
❍ Oracle's Hyperion® Interactive Reporting Studio—Highly intuitive and easy-to- navigate environment for data exploration and decision making. A consistent design paradigm 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 documents.
❍ 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.
14 Reporting and Analysis Architecture Overview ❍ Oracle's Hyperion® Web Analysis Studio—Java applet that enables you to create, analyze, present, and report multidimensional content. The studio offers the 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.
❏ Windows-based integrated—Windows-based integrated development environment that enables programmers to swiftly code, test, and debug components utilized by Dashboard Studio.
❏ Performance Scorecard—Web-based solution for setting goals and monitoring business performance using recognized scorecarding methodologies. Provides tools that enable users to formulate and communicate organizational strategy and accountability structures:
● Key Performance Indicators (KPIs)—Create tasks and achievements that indicate progress toward key goals
● Performance indicators—Indicate good, acceptable, or poor performance of accountability teams and employees
● Strategy maps—Relate high-level mission and vision statements to lower-level actionable strategy elements
● Accountability maps—Identify those responsible for actionable objectives
● Cause and Effect maps—Depict interrelationships of strategy elements and measure the impact of changing strategies and performance
● Oracle's Hyperion® Smart View for Office—Hyperion-specific Microsoft add-in and toolbar from which users can query Hyperion data sources including Essbase, 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.
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 16
Reporting and Analysis Architecture 15 ● “Application Layer Services Tier” on page 17 Because the business intelligence platform is modular, it may consist of various 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 the Hyperion Installation Start Here.
Web Server Use in Hyperion 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. Using vendor provided Web server plug-ins, the Web server used by Hyperion acts as a reverse proxy to route client requests. Requests may be handled in part by the Web server itself, such as requests for static images that exist on the same machine as the Web server, or routed to the appropriate Hyperion application server instance for processing. Workspace utilizes Uniform Resource Identifiers (URIs) to contact other Hyperion components using the http(s) protocol. The hostname and port used in the URI is taken from the Hyperion URI, as supplied by the client. Consider the following example, which illustrates the relationship between:
● Workspace—Deployed to Apache Tomcat on Machine A, and is configured to accept requests on TCP port 45000
● Financial Reporting Web component—Deployed to Apache Tomcat on MachineB, and is configured to accept requests on TCP port 8200
● Web server—Microsoft IIS Web server is installed on Machine C, and configured to accept incoming requests on TCP port 19000 In the above configuration, the Apache Tomcat Web Server plug-in is configured for IIS. It will route dynamic content requests to the /workspace context to MachineA:45000/workspace, and will route all requests to the /hr context to MachineB:8200/hr. Static content requests, such as images, to /workspace will be served directly by IIS from a directory local to Machine C. Users of this system will access Workspace using the URI: http://MachineC:19000/workspace/.
16 Reporting and Analysis Architecture Overview When users request a Financial Reporting document, the Workspace will process the request using the URI http://MachineC:19000/hr. If a user attempted to access Workspace using http://MachineA:45000/workspace/ retrieval of Financial Reporting documents would fail, as the Workspace would construct URIs using http://machineA:45000/hr. You must use proper Web server and Web server plug-in configurations:
● Tomcat: Chapter 8, “Configuring a Web Server with Apache Tomcat”
● Oracle 10g Release 3: “Configuring Oracle HTTP Server for Oracle 10g Release 3” on page 125
● Oracle 10g Release 2:“Configuring Oracle HTTP Server for Oracle 10g Release 2” on page 146
● WebLogic 9.1: “Configuring a Web Server for WebLogic 9.1” on page 161
● WebLogic 8.1: “Configuring a Web Server for WebLogic 8.1” on page 187
● WebSphere 6.1: “Configuring a Web Server with WebSphere 6.1 Application Server” on page 217
● WebSphere 6.0.2: “Configuring a Web Server with WebSphere 6.0.2 Application Server” on page 237
Application Layer Services Tier The application layer services tier contains services and servers that control functionality of various Web applications and clients:
● “Core Services” on page 18
● “Interactive Reporting Services” on page 19
● “Financial Reporting Servers” on page 20
● “SQR Production Reporting Service” on page 20
● “Assistive Hyperion Services” on page 20 Most services fall into two main groups, depending on the tool used to configure their properties:
● Local services–Services in the local Install Home that are configured using the Local 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 Architecture 17 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. Repository Service is replicable; if replicated, it must be replicated and co-located with Publisher 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. Publisher Service is replicable; if replicated, it must be replicated and co-located with Repository 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 artifacts (resources) users can view and modify. Authentication Service is replicable and does not need 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—Core Services that collect and distribute system messages and events for troubleshooting and usage analysis:
❍ Logging Service—Centralized service for recording system messages to log files. A system can have only one Logging Service.
❍ Usage Service—Records the number and nature of processes addressed by Hyperion Interactive Reporting Service, which enables administrators to review usage statistics such as the number of logons, what the most used files are, what the most selected MIME types are, and what happens to system output. Systems can have multiple Usage Services.
● Functional services—Core Services that are specific to various functional modules:
18 Reporting and Analysis Architecture Overview ❍ 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.
● Oracle's Hyperion® Impact Management Services—Core Services that 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.
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, SQR 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.
Reporting and Analysis Architecture 19 Financial Reporting Servers Financial Reporting servers support Financial Reporting functionality by processing batch requests, generating output, and distributing Financial Reporting client content:
● Hyperion Financial Reporting Server—Generates and formats dynamic report or book results, including specified calculations. Hyperion Financial Reporting Server can handle numerous simultaneous requests for report execution from multiple clients, because each request is run on its own execution thread. Hyperion Financial Reporting Server caches data source connections, so multiple requests by the same user do not require a re-connection. Financial Reporting servers are replicable—the number necessary depends on the number of concurrent users who want to execute reports simultaneously through the clients. Multiple Financial Reporting servers can be configured to report against one repository.
● Hyperion Financial Reporting Communication Server—Provides a Java RMI Registry to which other Financial Reporting servers are bound.
● Hyperion Financial Reporting Print Server—Enables Financial Reporting content to be compiled as PDF output. Runs only on supported Windows platforms, but is replicable to provide scalability for PDF generation.
● Hyperion Financial Reporting Scheduler Server—Responds to Financial Reporting scheduled batch requests. At the specified time, Hyperion Financial Reporting Scheduler Server prompts the other Financial Reporting servers to fulfill the request.
SQR Production Reporting Service SQR Production Reporting Service responds to scheduled and on-demand requests by Job Service to run jobs, process data, and generate reports. SQR 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. SQR Production Reporting Service is a replicable service.
Assistive Hyperion Services
● Performance Scorecard Services—Support Performance Scorecard client functionality used in conjunction with Reporting and Analysis.
● Oracle's Hyperion® Shared Services—Supports authentication and user provisioning for all Hyperion products. See the Shared Services documentation set.
● Smart View Services—Provide a common Microsoft Office interface for Hyperion products. See the Smart View documentation set.
Services Tier Summary
LSC or RSC Service Type Name Instances
LSC Core Authentication Service Multiple
20 Reporting and Analysis Architecture Overview LSC or RSC Service Type Name Instances
Core Authorization Service Multiple
Core Global Service Manager 1 per system
Core Local Service Manager Multiple
Core Publisher Service Multiple
Core Session Manager Multiple
Impact Management Assessment (Harvester) Service Multiple
Impact Management Update (Transformer) Service Multiple
Interactive Reporting Extended Access for Hyperion Interactive Reporting Service Multiple
Interactive Reporting Extended Access for Hyperion Interactive Reporting Service Multiple
Interactive Reporting Hyperion Interactive Reporting Data Access Service Multiple
Interactive Reporting Hyperion Interactive Reporting Service Multiple
Management Logging Service 1 per system
Management Usage Service Multiple
RSC Core Name Service 1 per system
Core Repository Service Multiple
Core Service Broker Multiple
Functional Event Service 1 per system
Functional Job Service Multiple
Assistive Hyperion Common Administration Services Shared Services 1 per system
Financial Reporting Servers Financial Reporting Communication Server
Financial Reporting Servers Financial Reporting Print Server Multiple
Financial Reporting Servers Financial Reporting Scheduler Server
Financial Reporting Servers Financial Reporting Server Multiple
Performance Scorecard Services Scorecard Module Services
SQR Production Reporting Service SQR Production Reporting Service Multiple
Smart View Services Oracle's Hyperion® Smart View for Office Services Multiple
Reporting and Analysis Architecture 21 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 two important repositories for information storage:
● Common repository—Hyperion system data in supported relational database tables
● Shared Services—User, security, and project data that can be used across Hyperion products
Data Sources:
● Relational data sources, for example, Oracle, IBM DB2, and Microsoft SQL Server
● Multidimensional data sources, for example, Essbase
● Oracle's Hyperion applications, for example, Financial Management and Planning
● Data warehouses
● ODBC data sources For a complete description of supported data sources, see the Hyperion Installation Start Here.
22 Reporting and Analysis Architecture Overview 2 Planning the Installation
In This Chapter Preparing an RDBMS for the Reporting and Analysis Repository...... 23 Obtaining and Preparing Pre-requisite Software ...... 33 Web Environment ...... 35 Browser Settings ...... 36 Module-specific Prerequisites ...... 37 Installing Considerations ...... 39 Port Numbers Used by Hyperion Products...... 40
Hyperion no longer ships or requires Oracle's Hyperion® License Server™ (or standalone license files) for use with Hyperion products. To ensure compliance with your license agreement, Hyperion recommends that you implement an auditing process. In addition, during product configuration with Oracle's Hyperion® Configuration Utility™, you activate only the features you purchased. For more information, see “Hyperion License Compliance” in Hyperion Installation Start Here.
Note: Reporting and Analysis is supported on the platforms specified in the tables included in 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, Hyperion may experience a delay in reproducing and fixing resultant issues for the affected versions.
Preparing an RDBMS for the Reporting and Analysis Repository
Backing Up a Repository If you are performing an upgrade from a previous release of Reporting and Analysis, Hyperion recommends you back up the following directories, files, and repository before upgrading, migrating, or reinstalling.
● RDBMS, all tables in the repository
Preparing an RDBMS for the Reporting and Analysis Repository 23 ● File system, all installation homes on all machines which includes the physical files in the repository that are maintained on disk
● Back up the repository (full database dump after the instance is shut down, before the updates to the instance or migration).
● Back up vpd.properties in the installing user’s %SystemRoot% directory.
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 Hyperion Installation Start Here to review the supported repository and data source databases.
Note: The amount of space needed depends on the aggregate size of the objects you plan to store in the repository. Hyperion suggests starting with at least 250 MB, which provides room to grow the Reporting and Analysis repository without having to increase the data file or tablespace.
Reporting and Analysis requires a repository database to store its persistent data. You must configure your system for use with a database Reporting and Analysis. See:
● “Configuring IBM DB2” on page 24
● “IBM DB2 with Web Analysis” on page 27
● “Configuring Microsoft SQL Server” on page 27
● “Configuring Oracle” on page 28
Configuring IBM DB2 After installing IBM DB2, record the IBM DB2 database host name, port number, and service name for use when you install the Reporting and Analysis products.
Note: A database administrator should perform the following procedures.
➤ To configure your system for use with IBM DB2: 1 Create an operating system user account for DB2. Hyperion suggests you name the database user biplus 2 Create a database within a DB2 instance for Reporting and Analysis. Create a Database for Reporting and Analysis. Hyperion recommends you create the database using UTF-8 encoding for the best compatibility with non-ASCII character sets. To create the
24 Planning the Installation database, run the DB2 Command Line Processor or Command Center as the DB2 instance 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 room to grow the Reporting and Analysis repository without having to increase the data file or tablespace. 3 Log on to the DB2 Control Center as the DB2 administrator and add the operating system 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 Modify the DB2 database:
● Increase the following:
❍
❍ IBMDEFAULTBP bufferpool from 1000(default) to 100000
❍
❍ DBHEAP from 1200(default) to 33000
❍ SORTHEAP from 256(default) to 2000
❍ LOGBFSIZ from 16(default) to 128
● A bufferpool and a tablespace with a 16 KB pagesize
● A system temporary bufferpool and a system temporary tablespace with an 16 KB pagesize
● Tablespace access, database connect, and create table privileges for the Reporting 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 16 K EXTENDED STORAGE
CREATE REGULAR TABLESPACE tablespace_name PAGESIZE 16 K MANAGED BY SYSTEM USING ('system_container') EXTENTSIZE 16 OVERHEAD 10.5 PREFETCHSIZE 16 TRANSFERRATE 0.33 BUFFERPOOL bufferpool_name DROPPED
Preparing an RDBMS for the Reporting and Analysis Repository 25 TABLE RECOVERY ON CREATE BUFFERPOOL tmp_bufferpool_name SIZE 512 PAGESIZE 16K CREATE SYSTEM TEMPORARY TABLESPACE tmp_tablespace_name PAGESIZE 16K MANAGED BY SYSTEM USING ('tmp_system_conatainer') EXTENTSIZE 16 OVERHEAD 10.5 PREFETCHSIZE 16 TRANSFERRATE 0.33 BUFFERPOOL tmp_bufferpool_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 UPDATE DATABASE CONFIGURATION FOR database_name USING SORTHEAP 2000 TERMINATE
Where:
Variable Name DB2 Description Example
db2_user User who owns the Reporting and Analysis DB biplus 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 For Core Services and Job Factory Service— 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.
26 Planning the Installation 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:
IBM DB2 with Web Analysis When using IBM DB2 for Web Analysis, you must ensure that the following conditions are met:
● Configure DB2 to use JDBC 2.0 drivers. Ensure that the IBM DB2 Client Application Enabler is installed.
● Create required tablespace.
● Ensure that the default tablespace for the database user who owns the Reporting and Analysis repository is not partitioned.
● Do not use localhost for the server name.
● Ensure that usernames are granted connection privileges to the database.
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.
Preparing an RDBMS for the Reporting and Analysis Repository 27 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 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 function to biplus go
Configuring Oracle
● Adequate privileges must be granted to the Oracle user.
● Use the global database server name when specifying locations and paths. Do not use localhost as a server name.
● Tablespaces can be shared with other applications. After you install Oracle, record the Oracle database host name, port number, and Oracle SID (or Service Name) for use when you install the Reporting and Analysis products.
28 Planning the Installation Note that when you install Oracle, SQL*Net is needed to run Production Reporting for Oracle.
Note: A database administrator should perform these procedures.
The Oracle database that contains the Reporting and Analysis tablespace should have UTF-8 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
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. 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:
Preparing an RDBMS for the Reporting and Analysis Repository 29 Tip: Create a separate tablespace for indexes to improve performance.
Note: This action requires CREATE TABLESPACE system privileges.
● If the database instance or file name (filespec) exists: create tablespace tablespace_name datafile 'filespec' SEGMENT SPACE MANAGEMENT AUTO ;
● If the database instance or file name (filespec) does not exist: create tablespace tablespace_name datafile 'filespec' size nnM SEGMENT SPACE MANAGEMENT AUTO ;
where nn is the megabyte count. Plan the repository size. Hyperion suggests starting with 250 MB minimum, which provides room to grow the Reporting and Analysis repository without having to increase the datafile or tablespace. The sizing of the shared pool is important, to ensure that the Hyperion Configuration Utility 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 Hyperion Configuration Utility. Make sure that SEGMENT SPACE MANAGEMENT parameter is set to AUTO when you create tablespace. This parameter is needed for better performance. 2 Create an Oracle user account for Reporting and Analysis. A user must be created. This user owns the Reporting and Analysis database tables and objects that are built and populated during this installation. The user created here is also the user that Reporting and Analysis services use to connect to the database. Hyperion suggests naming the user biplus. Database privileges are required to perform the following actions. The tablespaces created or identified in the previous step are used as the default and temporary tablespaces. To create the user, enter the following commands from within the Oracle SQL*Plus utility: create user biplus identified by mypassword default tablespace tablespace1 temporary tablespace tablespace2;
where tablespace1 and tablespace2 are the tablespaces previously created or identified. 3 Give the user database connection privileges: Oracle 9: grant connect, resource to biplus; Oracle 10: grant connect, resource, create view to biplus; 4 Set the NLS_LENGTH_SEMANTICS parameter to char: nls_length_semantics=char
30 Planning the Installation 5 Set the necessary environment variable: For Core Services and Job Factory Service—Use the System option in Control Panel or the Set command from the Windows command prompt to set the LIBPATH environment variable to the location of the Oracle Client libraries.
Note: Core Services—Hyperion recommends enabling the parallel query option to allow parallel query activity for faster row retrieval.
Manually Creating Tables The Hyperion Configuration Utility creates the repository tables. See “Configuring Databases” on page 53. You also have the option to create the repository tables before installing and configuring Reporting and Analysis. To manually create database tables, run the following scripts in the configured database:
where
● Oracle 9/10—Oracle
● IBM DB2—DB2
● MS SQL Server—MSSQLServer
Database Storage Parameters for Oracle The Oracle DDLs now contain storage parameters. If the database will be large, alter storage parameters after install and before relational storage configuration. create table V8_ACCESS_CTRL ( RESOURCE_ID VARCHAR2(64) not null, ACCESSOR_ID VARCHAR2(64) not null, ACCESSOR_TYPE NUMBER(1) not null, GRANT_ID VARCHAR2(64) not null, GRANT_TYPE NUMBER(1) not null, LAST_UPDATE_DATE DATE, constraint PK_V8_ACCESS_CTRL primary key (RESOURCE_ID, ACCESSOR_ID, GRANT_ID)
Preparing an RDBMS for the Reporting and Analysis Repository 31 ) pctfree 8 pctused 60 storage ( initial 2M next 1M)
There are now small, medium, and large table sizes:
● Large tables are allocated 2M initial extents
● Medium tables 300K
● Small tables are left with the default values pctfree and pctused are set based on the expected insert, update activity on the table; for example, if high insert, update activity pctfree is higher.
Creating ODBC Connections Interactive Reporting and SQR Production Reporting uses ODBC to access a data source, and must create an ODBC connection.
Prerequisite You must have Microsoft 4.0 XML Parser installed before using the ODBC drivers. To download and install XML Parser, go to: http://www.microsoft.com/downloads/details.aspx?FamilyID=3144b72b-b4f2-46da-b4b6- c5d7485f2b42&DisplayLang=en
Installing For information on installing and configuring the DataDirect ODBC drivers supplied with Reporting and Analysis, go to: http://www.datadirect.com/download/docs/dochome/index.ssp In Reporting and Analysis, use the HELP to see the parameters.
Microsoft SQL Server Analysis Services (SSAS) Connections
SSAS 2005 To connect to Microsoft SSAS 2005 databases, you must install SSAS Connectivity Client on any Financial Reporting Client or Financial Reporting server or Web Analysis Web Application machine. When you choose the Client component during the install there are 6 types of subcomponents to choose from. You must expand Client Components and select the Client Connectivity component that is required by Financial Reporting and Web Analysis to connect.
32 Planning the Installation Verifying the Client Connectivity Component Locate: \Program Files\Common Files\System\Ole DB\msolap90.dll
to verify that you have the Client Connectivity Component.
Correcting the Client Connectivity Component Selection If you did not drill down to select the client Connectivity component, the following procedure will correct it.
➤ To correctly select the Client Connectivity component: 1 Click Start >Settings, Control Panel and select Change or Remove Programs. 2 Select Microsoft SQL Server 2005 and click Change or Remove Programs. 3 Select the Workstation Components option and click Next and click Next. 4 Click Change Installed Components. 5 Expand the Connectivity Components option and choose either of the two options to install it to the local shared drive:
● Will be installed on local hard drive
● Entire feature will be installed on local hard drive 6 Click Next. 7 Click Install, then Next, then Finish.
SSAS 2000 To connect to SSAS 2000 databases, you must install SSAS 2000 Connectivity Client on any Financial Reporting Client or Financial Reporting server or Web Analysis Web Application machine. When you choose the Client component during the install, expand Client Components and select the Client Connectivity component that is required by Financial Reporting and Web Analysis to connect.
Obtaining and Preparing Pre-requisite Software
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:
Obtaining and Preparing Pre-requisite Software 33 ● Your SAP distribution
● 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.
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 as a registered user at https://service.sap.com/connectors 2 After Reporting and Analysis installation: a. Place the SAP JCo binaries 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
Installing the IBM Global Security Kit for WebSphere Express The IBM Global Security Kit 7 (GSKit7) is required for the WebSphere Web server plug-in, and is included with WebSphere (base) and higher. WebSphere Express users must download and install it manually:
34 Planning the Installation Download the latest version of IBM HTTP Server 2.0 (2.0.47.1 at the time of this writing) for your platform from: http://www.ibm.com/software/webservers/httpservers/ Extract the archive you downloaded, and install only the GSKit7 package:
➤ To extract and install the GSKit7 package: 1 Extract HTTPServer.win.2047.zip. 2 Open a command prompt in the skit subdirectory of your extracted files location. 3 Run the command: setup.exe gsk7bas. 4 Complete the setup Wizard.
Web Environment The following topics describe pre-installation Web environment considerations:
● “Application Server Setting” on page 35
● “Configuring a Web Environment” on page 35
Application Server Setting By default, session timeout is set to 60 minutes, and is defined in WEB-INF\web.xml.
Note: Hyperion recommends that all Reporting and Analysis Web applications should have session timeouts set to greater than 10 minutes.
Web Browser Requirements You must have Internet Explorer or Mozilla Firefox to access the Reporting and Analysis user interface. See Hyperion Installation Start Here for supported version numbers.
Configuring a Web Environment
Financial Reporting and Web Analysis Web Server Environment Reporting and Analysis requires both an Application server and a stand-alone Web server.
Note: The Reporting and Analysis installation can automatically configure Apache Tomcat and Apache Web Server.
Web Environment 35 A servlet is a Java program that runs as part of a network service, typically a Web server and responds to requests from clients. If you opt not to deploy Reporting and Analysis to the Tomcat application server and Apache Web Server bundled with the installer, you must manually install a supported application server and Web 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 Web server.
Financial Management Web Server Environment
● For Workspace configuration of Financial Management, you must use the machine name or actual IP address for the IIS Web server machine. Do not use localhost as the machine name for Financial Management.
● To set timeout in Apache for Financial Management Web servers, add the following to C:\hyperion\common\httpservers\apache\2.0.52\conf dir\hfm.conf:
ProxyTimeout
where
● For using only IIS (for example, if Apache is not used at all ): You must configure the IIS used by Financial Management as the front-end Web server for Workspace. You can have the Workspace Web application server running on a separate machine, but you must install the Workspace code onto the machine running IIS. The Workspace installation includes files that are served by the Web server, such as the help files. To install the Workspace code onto the IIS machine, after installing Workspace on the IIS machine, run the Hyperion Configuration Utility Web server configuration. When the task prompts for the Workspace web server, another host name can be entered.
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 server.
● For Internet Explorer
❍ Enable ActiveX. For supplemental information regarding this requirement, see Active X.
36 Planning the Installation ❍ 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.
Module-specific Prerequisites Prerequisites:
● “Configuring a Production Reporting Server Installation” on page 37
● “Financial Reporting Print Server” on page 37
Configuring a Production Reporting Server Installation 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 Oracle's Hyperion® SQR® Production Reporting Server sqr.ini file (only required if the installer cannot find it in the standard location, or if the Production Reporting environment variable SQRDIR is not set).
Financial Management Financial Management currently runs on Microsoft Windows. For best performance when accessing Financial Management , Financial Management requires you install all Financial Reporting and Web Analysis components on a computer running a Windows operating system.
Financial Reporting Print Server The following requisites apply to Financial Reporting:
Importing Financial Reporting Content into Microsoft Word and Powerpoint You must use Ghostscript and not Distiller to import content into Microsoft Word and PowerPoint. When you run the Hyperion Configuration Utility, you need to choose Ghostscript. See “Print Server Configuration” on page 62.
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)
Module-specific Prerequisites 37 ● Microsoft Excel files (*.xls, *.xlc)
● Microsoft PowerPoint files (*.ppt)
Note: All file types can be accessed from the HTML client.
Printing Cell Documents In order to print cell documents, the corresponding “print” applications (Microsoft Word, Excel and PowerPoint) on the Print Server machine must:
● Be properly installed
● Be properly registered for printing in the computer’s registry
● Be available to the “SYSTEM” account
● Have access to, and be able to print from, the printers installed by Financial Reporting (HRPrinter1-5). The SYSTEM account issues all print requests, so it is important that the applications can print using the Print Server’s printers. An easy way to test running a program using the SYSTEM account is to use the at command at a command prompt. While the at command is meant primarily for scheduling a task (also known as the Windows Task Scheduler), another result is that all scheduled tasks run under the SYSTEM account. The parameters for the at accounts are as follows: at time/interactive “command” where: at—task scheduler program time—time, in 24-hour notation (00:00 through 23:59) when program should run The time parameter must be indicated. To print immediately, it can be set to one minute past the current time. For example, if the current time is 10:29 AM, you can launch Excel under the SYSTEM account by using the following from a command prompt: at 10:30: For Office 2003: /interactive “C\Program Files\Microsoft Office \OFFICE11\Excel.exe” For Office 2002:/interactive “C\Program Files\Microsoft Office \OFFICE10\Excel.exe” For Office 2000:/interactive “C\Program Files\Microsoft Office\OFFICE \Excel.exe” The command prompt displays something similar to: Added a job with job ID = 1 At 10:30, Excel launches (under the SYSTEM account). Once Excel is launched, you can test whether you can use the printers by issuing a print command (File - Print) and making sure the printers list contains the HRPRinters. /interactive—Allows the program to interact with the desktop of the user who is logged on at job run time
38 Planning the Installation “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 Analytic Services 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.
Installing Considerations The following topics describe pre-installation installing considerations:
● “Satisfying Temporary Space Requirements” on page 39
● “Command Line Processor Considerations” on page 40
Satisfying Temporary Space Requirements The Reporting and Analysis installer requires 1 GB of temporary space.
➤ To instruct the installer to use a specific location to store temporary files, rather than use the Operating System defined location for temporary files, use this command: setupWinPlatform.exe -is:tempdir directory_name
where directory_name is a directory on your system with space.
Installing Considerations 39 Command Line Processor Considerations To install from the Command Line processor, you must pass the argument -console. You can also, optionally, pass the arguments -is:tempdir and/or -is:javaconsole. For example: mkdir D:\Temp
setupWinPlatform.exe -is:tempdir D:\Temp -is:javaconsole -console
Note: -is:javaconsole activates a new window where you can see debug messages while installing. Use this option only if experiencing problems to collect debug information for Hyperion Support.
Port Numbers Used by Hyperion Products For a listing of default port numbers for Hyperion Applications, see the Hyperion Installation Start Here. During Hyperion product installations, the default port numbers for application servers are automatically populated. You can change the defaults during the configuration process. Each application port number must be unique. If a default port number is modified and the application does not launch or an error message similar to “port already in use” or “bind error” is displayed, a port number conflict may exist.
40 Planning the Installation Installing Reporting and 3 Analysis
In This Chapter Prerequisites...... 41 Terminal Services Configuration ...... 41 Reporting and Analysis Installers...... 42 Reporting and Analysis Module Installers ...... 42 About Hyperion Home...... 44 Installing Reporting and Analysis...... 46 Running Silent Installations...... 48
Prerequisites
● Use database configuration tools to create a database. See Configuring Database Software for the Reporting and Analysis Repository .
● Install and configure Shared Services. See Hyperion Shared Services Installation Guide and Hyperion Shared Services Readme.
● Read the Hyperion Reporting and Analysis – System 9 Readme.
● If you are installing Hyperion applications; for example, Planning or Financial Management, install and configure the applications before installing Reporting and Analysis.
Terminal Services Configuration
Note: You must be a local Administrator group member to install Reporting and Analysis.
If you are installing Reporting and Analysis components in a Terminal Services Application Server Mode session, it must be switched to Install Mode.
➤ To switch your current Terminal Server session to Install Mode: 1 Click Start, and then click Run. 2 In the Open box, type cmd, and then click OK.
Prerequisites 41 3 At the command prompt, type change user / install, and then press ENTER. The following message appears: User session is ready to install applications. 4 Type Exit, and then press ENTER.
Reporting and Analysis Installers For each machine, run one or more of the five installers associated with the machine. For directions for installing, see “Installing Reporting and Analysis” on page 46.
Installer Installer Description Executable Folder
Reporting and Analysis Services1 * Workspace Core Services, and services for the Reporting and services Analysis modules; for example, for Workspace: GSM Name Services, Authentication Service, Repository Service, Job Utilities. for Interactive Reporting: Services and Interactive Reporting SDK. For Financial Reporting standalone servers: Financial Reporting Server, Financial Reporting Print Server, Financial Reporting Scheduler Server
Reporting and Analysis UIServices Web components related to Workspace (includes Interactive uiservices Reporting and Interactive Reporting Plug-ins, and installs the component to view Production Reporting job output), Financial Reporting, and Web Analysis Studio.
Reporting and Analysis Client Modules and components that are needed for the client desktop: client Interactive Reporting Studio, Financial Reporting Studio, SQR (Windows only) Production Reporting: Studio, Activator, Remote, and Viewer, and Dashboard Development Services.
Reporting and Analysis Production Reporting Production Reporting module and components: Production repservices
Reporting and Analysis Migrator Components that are needed for migrating data from previous migrator Hyperion products into the current release. See Chapter 7, “Installing the Reporting and Analysis Migration Utility ”.
*For Interactive Reporting content only: If you use webservices to access some of Hyperion repository content: select Custom install, and under the Core Services, select the Web Services feature.
Reporting and Analysis Module Installers
Web Applications (In Client (In client EXE, Production Reporting Services (In services EXE)2 UIServices EXE)2 Windows Only)2 (In repservices EXE)2
Financial Reporting -Core Services -Workspace1 -Oracle's Hyperion® Not needed Financial Reporting -Financial Reporting -Financial Reporting Studio Services: -Reporting and Analysis servicesReporting and
42 Installing Reporting and Analysis Web Applications (In Client (In client EXE, Production Reporting Services (In services EXE)2 UIServices EXE)2 Windows Only)2 (In repservices EXE)2 Analysis services Financial Reporting Report Server -Reporting and Analysis servicesReporting and Analysis servicesFinancial Reporting Print Service -Financial Reporting Scheduler Service
Interactive Reporting -Core Services -Workspace1 -Oracle's Hyperion® Needed for SQR Interactive Reporting Production Reporting -Impact Management -Interactive Reporting3 Studio job output viewing Services -Dashboard -Dashboard Development Development Services Services -Interactive Reporting Services: -Interactive Reporting Service -Data Access Service
Web Analysis -Core Services -Workspace1 Not needed Not needed -Web Analysis
SQR Production -Core Services -Workspace1 -Oracle's Hyperion® -Production Reporting Reporting SQR® Production Server Reporting -DB2 -Studio -DDO -Activator -Informix -Remote -ODBC -Viewer -Oracle -Sybase
Note: 1Workspace is a Web application common to Financial Reporting, Interactive Reporting, SQR Production Reporting, and Web Analysis and Reporting and Analysis Apps. Workspace, Interactive Reporting, and Production Reporting are installed together. 2Each installer contains the documentation pertaining to the installer components. 3For Interactive Reporting content only: If you use webservices to access some of Hyperion repository content: select Custom install, and under the Core Services, select the Web Services feature.
Reporting and Analysis Module Installers 43 About Hyperion Home When multiple Hyperion products are installed on one computer, common internal and third- party components are installed to a central location, called Hyperion Home. The Hyperion Home location is defined in the system environment variable called HYPERION_HOME.
Hyperion Home Location The default location for Hyperion Home is C:\Hyperion. When you install, the installer searches for the HYPERION_HOME environment variable on the computer to which you are installing. If the Hyperion Home location was previously defined for another Hyperion product, the installation uses the previously defined location. The location cannot be changed through the installer. If the current installation is the first Hyperion installation on the computer, you can specify the location during installation.
Files Installed in the HYPERION_HOME Directory Various files are installed in the
Table 1 Common-Component Folders Created in the Common Directory
Folder Contents
appServers Application server files
CLS License services APIs
config Hyperion Configuration Utility files
CSS Files to support Hyperion external authentication
Docs Product documentation files
EssbaseJavaAPI Java driver used when embedding Essbase in other applications
EssbaseRTC Essbase runtime client used when embedding Essbase in other applications
httpServers Apache web server files for batteries included installation
HyperionLookAndFeel Installer user interface files
JakartaCommons Common development library files
JavaMail Files to support sending e-mail via Java
JCE JCE files for encryption, key generation and agreement, and MAC
44 Installing Reporting and Analysis Folder Contents
JDBC JDBC files
JRE Java Runtime Environment files
lib common internal library files
loggers Files for external authentication logging
ODBC ODBC drivers
Opatch Oracle patching tool files; for future use
PERL Scripting language files
SAP SAP files
SharedServices Supporting files for Shared Services
utilities Utilities to change the location of Hyperion Home and export, import, or validate provisioning data
validation Not used in this release
velocity Not used in this release
XML Common XML components
Changing the Hyperion Home Location After Hyperion Home is defined through the product installation, you can run a migration utility to change the Hyperion Home location. The migration utility moves the files installed in Hyperion Home to the new location and updates the value of the HYPERION_HOME environment variable. Hyperion Home Migration Utility is provided with the Shared Services installation.
Note: For an Apache Tomcat 5.0.28 Windows installation, you can install the Shared Services server as a Windows service. If you select this option, the Shared Services server is launched automatically by the service and runs in the background. However, if you change the HYPERION_HOME location, the Windows service does not automatically start. This problem occurs because the registry entries for the Windows service retain the old path information. To solve this problem, you must manually update the location of the Windows service.
➤ To change the Hyperion Home location: 1 Launch the migration utility:
● Choose a method:
About Hyperion Home 45 ❍ Select Start > Programs > Hyperion > Foundation Services > Home Migration Utility.
❍ Double-click the run.exe file from:
❍ From a Windows console, change to:
Then type run.exe -console. 2 Step through the screens, and when prompted, enter the Hyperion Home location or click Browse to navigate to the preferred location. Do not choose a HYPERION_HOME location that contains a space character. For example, C: \Program Files is not acceptable.
Installing Reporting and Analysis
Note: The server on which Financial Reporting runs must be configured with only one Network Interface Controller (NIC) card.
➤ To install Reporting and Analysis: 1 Download the software from the Oracle® E-Delivery site. 2 Shut down all processes and services related to previous component releases. 3 Execute the desired installer: services, uiservices, client, repservices
● For installer descriptions, see “Reporting and Analysis Installers” on page 42
● For functionality descriptions, see “Reporting and Analysis Module Installers” on page 42.
● For Migration Utility, see Chapter 7, “Installing the Reporting and Analysis Migration Utility ”. 4 Select a language to be used for the installation wizard. 5 On some of the installers, for example: client installer, a target language dialog displays. Select the country where you are installing the software. The setup program displays a license based on the selection. Select the Country Location, click Next. 6 Read the License Agreement, select I AGREE, and click Next. 7 Click Next. 8 When the directory path for the installation displays, click Next to accept the default Reporting and Analysis directory or click Browse to select another directory. The new installation default path is C:\Hyperion\BIPlus.
46 Installing Reporting and Analysis Note: When running several installers on the same machine, make sure that you install components into the same installation directory.
Note: Do not specify installation directories that contain spaces or non-alphanumeric characters.
The Hyperion Home selection page is displayed. 9 Select the installation path for Hyperion Home. The common components for Hyperion products are installed to
Note: If the installation program detects a directory for Hyperion Home, Directory Name and Browse are disabled. 11 Click Next. The Setup Type page is displayed. 12 Select a setup type of Typical or Custom, and click Next.
● Typical—Installs commonly required modules
● Custom—Installs selected Reporting and Analysis modules To see the functionality in each installer, see “Reporting and Analysis Installers” on page 42. To see the installers needed for each module, see Hyperion Reporting and Analysis Module Installers. 13 From the Summary screen, review the components selected for the install and click Next. The wizard installs the Reporting and Analysis components. 14 After the installation is complete, the installation wizard may, under certain circumstances, prompt you to launch the Hyperion 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 Hyperion Configuration Utility.
❍ If you run the Client or Production Reporting installers, click Finish.
Installing Reporting and Analysis 47 Running Silent Installations To install Reporting and Analysis on multiple computers and duplicate installation options, you can record your installation settings and run a silent installation from the command line. Silent installations automate the installation process so you can install Reporting and Analysis without repeating installation-setting specifications. To record your installation settings, you create a response file and run the installation to record the settings in the response file. Then, when you run a silent installation, the response file is used to set the installation options of the nonsilent installation.
➤ To record installation settings and run a silent installation: 1 Navigate to the directory that contains the product installer. 2 From a command line, run a command: setup.exe -options-record
where
The installation runs in the background. If you specify it, the installation can run in the background. Information is logged into the log file the same way it is during the GUI install.
Note: Sample response files are available from the Oracle® E-Delivery site.
48 Installing Reporting and Analysis Configuring Reporting and 4 Analysis
In This Chapter Hyperion Configuration Utility...... 49 Satisfying Initial Requirements ...... 50 Configuring Product Upgrades...... 50 Configuring Reporting and Analysis ...... 51 Completing Module-Specific Configurations ...... 59 Reconfiguring Products ...... 64 Testing Module Availability...... 64 Post Configuration Tasks...... 65 Error Messages When Testing Module Availability ...... 65 Post Configuration Tasks...... 66
Hyperion Configuration Utility Hyperion Configuration Utility is a common tool that installs automatically with Hyperion products. Although you must use it to set up new products that you install, it also enables you to reconfigure existing products and upgraded products. Configuration involves these tasks:
● Product option selection—To comply with your license agreement, select the product features that you are authorized to use.
● Shared Services registration—To use Shared Services to provision and share users among Hyperion product applications.
● Relational database configuration—To store and retrieve application data in a database repository.
● Application server deployment—To deploy the application automatically, or partially, to an application server.
● Shared Services deregistration—To deregister products from with Shared Services before upgrading or uninstalling these products. For information about the order of configuration tasks, acceptable characters, and resolving configuration issues, see:
● “Task Sequence ” on page 50
● “Restricted Characters” on page 50
● “Troubleshooting” on page 50
Hyperion Configuration Utility 49 Task Sequence Hyperion recommends that you configure products separately and perform all configuration tasks. However, you can configure products simultaneously performing all, or specific, configuration tasks.
Restricted Characters Only enter alphanumeric, dash (-), dot (.) , underscores (_), and tildes (~) during configuration. Tildes are only supported on Microsoft Windows. All other characters are not supported.
Troubleshooting Terminating configuration for one product does not stop the configuration of other products. All configuration warnings and errors are logged as follows: Microsoft Windows —
● Configure products individually.
● See the Hyperion Installation and Configuration Troubleshooting Guide for information about configuration checks, debugging using logs, troubleshooting methodology, and solutions to common configuration issues.
Satisfying Initial Requirements If you are using Hyperion Configuration Utility for the first time, perform these tasks:
Table 2 Configuration Requirements
Task Reference
Satisfy system and product-specific requirements. “System Requirements” and “Planning Hyperion Installations” in the Hyperion Installation Start Here
Gather the information you need to configure products. “Hyperion Configuration Utility Worksheets” in the Hyperion Installation Start Here
Install, configure, and start the Shared Services server. Hyperion Shared Services Installation Guide
Configuring Product Upgrades You can use Hyperion Configuration Utility to configure and reconfigure supported product upgrades. Note the following:
● If you upgraded Shared Services, configure it before configuring other products.
● Configure upgraded products individually.
50 Configuring Reporting and Analysis ● Deploy to the same database you used when you configured the previous product release. If you do not want to use Shared Services with the products you are upgrading, select Shared Services Deregistration during configuration.
Configuring Reporting and Analysis Run Hyperion Configuration Utility on the computer hosting the products to configure or reconfigure.
➤ To configure Reporting and Analysis: 1 Launch Hyperion Configuration Utility as follows:
● At the end of installation by selecting Launch Hyperion Configuration Utility on the last panel.
● Using a method:
❍ Select Start > Programs > Hyperion > Foundation Services > Configuration Utility.
❍ Double-click configtool.bat in:
❍ Change to
Table 3 Configuration Tasks
Selection Task
Product Options Select the product features that you are authorized to use based on your purchase and licensing agreement. See “Hyperion License Compliance” in the Hyperion Installation Start Here. During product configuration, Hyperion Configuration Utility copies registry.properties to
Shared Services Registration Enter the information in “Registering With Shared Services” on page 52.
Configure Database a. Start the database. b. Select the database type. c. Enter the information in “Configuring Databases” on page 53.
Deploy to Application Server a. Start the application server.
Configuring Reporting and Analysis 51 Selection Task b. Select the application server, then an option:
● Automatic—Hyperion Configuration Utility deploys all files to the application server, resulting in no or minimal post-deployment tasks:
❍ WebLogic: If disk space is inadequate, specify another location for the WAR file and redeploy. ❍ WebSphere: If disk space is inadequate, Hyperion Configuration Utility places java.io.tempdir in
WebLogic 8.1.x—
Completing Module Specific Configurations See “Completing Module-Specific Configurations” on page 59
6 Click Finish. Configuration time depends on the products and tasks you selected. Progress is recorded in configtool.log as follows:
● Configure products individually and perform tasks separately.
● See the Hyperion Installation and Configuration Troubleshooting Guide for information about resolving configuration issues. 7 Important: After you configure each product, you must open registry.properties—in
Registering With Shared Services By default, the user you specify during registration is pre-provisioned as admin. This enables you to log on to Shared Services after configuration using admin/password, to create and provision users.
52 Configuring Reporting and Analysis Table 4 Shared Services Registration
Field Description
Server Name The name of the computer where the Shared Services server is installed. Caution! Do not specify an IP address, especially in DHCP environments, or enter restricted characters.
Port The default or custom Shared Services server port number.
User The username of the Shared Services Administrator.
Password the password of the Shared Services Administrator.
SSL Select to use Secure Sockets Layer for encryption. See the Hyperion Product SSL Configuration Guide.
Configuring Databases You can use Windows Authentication for SQL Server connections if you use Microsoft SQL Server database. See “Microsoft SQL Server Windows Authentication” on page 54. The Hyperion Configuration Utility enables Reporting and Analysis to detect an existing database and supports options for over-writing or not over-writing tables.
Table 5 Database Configuration
Field Description
Server Name of the computer or server hosting the database.
Port Server port number on which the database listens.
Product Name of each product and its installation location.
Database or SID (Oracle only) Database name or the Oracle system identification (database instance). Do not use restricted characters.
Username The name of the database owner.
Password The password of the database owner. Note: If this changes, reconfigure as described in the Hyperion Installation Start Here.
Data Tablespace (Oracle) Name of an existing tablespace used to create tables. The data tablespace is the logical portion of the database used to allocate storage for table data.
Index Tablespace (Oracle) Name of an existing tablespace used to create database indexes. The index tablespace is the logical portion of the database used to allocate storage for index data.
Configuring Reporting and Analysis 53 Microsoft SQL Server Windows Authentication
➤ To set up Windows authentication for a SQL Server connection: 1 Set up SQL Server with your NT login user: 2 Ensure that your NT domain user is assigned to the SQL Server database (for example, hub). 3 Grant the NT domain user full access permissions to the database. 4 From the configuration task list, select Configure Database. 5 From the database list, select SQL Server. 6 Specify all database information except for Username and Password.
Specifying Application Server Hostnames and Web Server Connector Plug-in Ports When Reporting and Analysis UI Services are distributed among 2 or more machines, or when configuring a Web Server on a machine other than where the Application Server(s) are installed, you must provide the following:
● The correct Application Server hostnames—specify the machine name and port as part of the Hyperion Configuration Utility.
● Web Server plug-in ports—manually enter the information in the Web server plug-in configuration file(s). See:
● Chapter 9, “Manually Deploying into Oracle 10g Release 3 (10.1.3.1.0) Application Server”
● Chapter 10, “Manually Deploying into Oracle 10g Release 2 (10.1.2.0.2) Application Server”
● Chapter 11, “Manually Deploying into WebLogic 9.1”
● Chapter 12, “Manually Deploying into WebLogic 8.1”
● Chapter 13, “Manually Deploying into WebSphere 6.1”
● Chapter 14, “Manually Deploying into WebSphere 6.0.2”
Note: Use fully qualified hostnames for all entries. For example, somehost.example.com
Tip: When deploying to Tomcat, the port(s) you must specify are the AJP3 ports, not Web server listen ports. For example, 45002 for Workspace, 8202 for Financial Reporting, and 16002 for Web Analysis. For WebLogic and WebSphere, the connector ports and the Web server listen ports are identical. For example: 45000, 8200, and 16000.
54 Configuring Reporting and Analysis Deploying to the Application Server To prevent the Web application being deployed from inheriting unwanted runtime settings, you must create and use one of the following:
● Oracle OC4J instance
● WebLogic server
● WebSphere application server Deploying more than one Web application to the same OC4J instance, WebLogic server, or WebSphere application server may yield unsuccessful results. If you are deploying your product to a single application server, decide between these deployment options:
● Automatic—Select the Deploy to Application Server task and the Automatic deployment type in Hyperion Configuration Utility to have Hyperion Configuration Utility deploy all files to the application server. In most cases, no other deployment tasks are required.
● Manual—Select the Deploy to Application Server task and the Manual deployment type in Hyperion Configuration Utility to have Hyperion Configuration Utility place the necessary Web archives (EAR or WAR) in the /AppServer/InstallableApps/ common directory to enable manual deployment at a future time. Manual Deployment procedures: For WebSphere 6.0, Hyperion recommends using the same profile for all EPM System Web applications. For WebLogic, Hyperion recommends using the same domain for all EPM System Web applications. After configuration, perform the deployment tasks for your application server in one of these chapters:
❍ Chapter 9, “Manually Deploying into Oracle 10g Release 3 (10.1.3.1.0) Application Server”
❍ Chapter 10, “Manually Deploying into Oracle 10g Release 2 (10.1.2.0.2) Application Server”
❍ Chapter 11, “Manually Deploying into WebLogic 9.1”
❍ Chapter 12, “Manually Deploying into WebLogic 8.1”
❍ Chapter 13, “Manually Deploying into WebSphere 6.1”
❍ Chapter 14, “Manually Deploying into WebSphere 6.0.2”
Table 6 Automatic Deployment Parameters
Field Description
Location Path to the application server installation directory and examples:
● WebSphere Base:
c:\WebSphere\AppServer
● WebSphere Express:
Configuring Reporting and Analysis 55 Field Description
c:\IBM\WebSphere\Express51\AppServer
● WebLogic 8.1.x:
c:\bea\weblogic81
● WebLogic 9.1.x:
c:\bea\weblogic91
Deploy as a service Selected by default to register the web application as a Windows service listed in Windows Control Panel. See “Startup Dependencies” in the Hyperion Installation Start Here.
Profile (WebSphere) Name of the profile where you access the application. By default, all applications deploy to the same profile. To change the profile name, see “What Happens During Deployment ” on page 56.
Domain (WebLogic) Default name of the domain where you access the application. For WebLogic 9.1.x, all applications deploy to the same domain. To change the domain name, see “What Happens During Deployment ” on page 56.
BEA Home (WebLogic) Path to the BEA Home directory (e.g.,c:\)
Component Products being deployed. Some products display as components.
Server Name Enter the name of the server where you will access the product. Do not include spaces. This name is used as the product directory name in
Port To change the default port, enter a unique port number that does not exceed 1025 to avoid conflicts with third-party port assignments. See “Ports” in the Hyperion Installation Start Here.
What Happens During Deployment
WebSphere and WebLogic 9.1.x Hyperion Configuration Utility deploys each application to the same WebSphere profile or WebLogic domain. The profile or domain is created when the first application is deployed. Each application runs in a separate JVM. Hyperion Configuration Utility deploys the application to:
56 Configuring Reporting and Analysis Note: It is not recommended to change other parameters in this file.
WebLogic 8.1.x Deploying to a single domain for WebLogic 8.1.x is not supported. For WebLogic 8.1.x, Hyperion Configuration Utility deploys the application to:
Enabling the Web Server Plug-in Notes:
● Financial Management 9.2, 4.0.2 and Planning 9.2.x, 4.0.5 are not integrated into Workspace. When running the Web Server plug-in for these releases, clear Enable Financial Management and Enable Planning check boxes.
● The Web Server plug-in is not an optional component, and must be installed and configured on at least one machine.
● The Web Server plug-in and Application Server must be installed on the same machine where Workspace is installed.
➤ To enable the Web server plug-in: 1 Launch Hyperion Configuration Utility. See “Configuring Reporting and Analysis” on page 51. 2 From the list of configuration tasks, select Deploy to Application Server and Configure Web Server, and click Next. 3 On the Web server plug-in configuration dialog, select the Web Server. See “Hyperion Configuration Utility Web Server Plug-in Support” on page 58 4 On the Web Server plug-in configuration for the product dialog, enable the check box adjacent to each module that will integrate with the Workspace. For each enabled module, supply the hostname and port to which this Web server will proxy requests. If this installation of the Web server will proxy requests by way of a load balancer, DNS alias, or other means of redirection, supply that address here. Accept or change the port number for one or more of the following modules or products:
● Financial Reporting
● Web Analysis
● Performance Scorecard
● Planning
● Financial Management
● Oracle's Enterprise Performance Management Architect
Configuring Reporting and Analysis 57 Note: To add a component after finishing the configuration, you must execute the Hyperion Configuration Utility to configure the application deployment and add the additional Web server plug-in information. 5 Click Next. 6 Enter the location of the Web server and click Next. 7 Accept the default or enter the Web server port to be used for accessing your Web application via Workspace.
Hyperion Configuration Utility Web Server Plug-in Support Reporting and Analysis Hyperion Configuration Utility supports the following Web server plug- ins:
Table 7 Web server Plug-in Automatic:
Apache IBM IIS1
WebLogic 9.1 Yes Yes
WebLogic 8.1 Yes Yes
WebSphere 6.1 Yes Yes Yes
WebSphere 6.0 Yes Yes Yes
Tomcat Yes Yes
Note: 1If IIS is chosen as the Web server during Configuration, and IIS version is 6.0; for example: OS=Windows 2003, you must allow all unknown ISAPI extensions via the Internet Information Services Manager.
Web Server Plug-in Manual Support For Reporting and Analysis supported manual configurations of Web server plug-ins, see the individual application server appendixes:
Table 8 Web server Plug-in Automatic:
Apache IBM IIS Oracle HTTP Server
Oracle Release 3 “Configuring Oracle HTTP Server for Oracle 10g Release 3” on page 125
Oracle Release 2 “Configuring Oracle HTTP Server for
58 Configuring Reporting and Analysis Apache IBM IIS Oracle HTTP Server Oracle 10g Release 2” on page 146
Tomcat “Configuring Apache” “Configuring IIS” on on page 103 page 107
WebLogic 9.1 “Configuring Apache “Configuring HTTP Plug-in” on page Microsoft IIS” on 161 page 171
WebLogic 8.1 “Configuring with “Configuring Reporting and Analysis Microsoft IIS” on and Hyperion page 197 Applications” on page 188
WebSphere 6.1 “Configuring Apache “Configuring Apache “Configuring IIS” on Server or IBM HTTP Server or IBM HTTP page 219 Server” on page 217 Server” on page 217
WebSphere 6.0 “Configuring Apache “Configuring Apache “Configuring IIS” on Server or IBM HTTP Server or IBM HTTP page 240 Server” on page 237 Server” on page 237
Completing Module-Specific Configurations You can use the Hyperion Configuration Utility to perform configuration tasks for a module. These tasks are displayed on the Hyperion Configuration Utility task list.
Note: The following configuration tasks may not appear on the task list in the order below because components can be installed on several machines.
Workspace Configurations Workspace configurations:
● “Customizing the Context Path ” on page 60
● “Specifying the GSM Host and Port ” on page 60
● “Customizing Service Ports for Reporting and Analysis ” on page 60
● “Configuring the SQR Production Reporting Engine for Interactive Reporting” on page 60
Completing Module-Specific Configurations 59 Customizing the Context Path The Context Path configuration dialog displays when installing the Workspace Web Application. The context path is the part of the URL that accesses the deployed Web application. For example in the following URL, workspace is the context path: http://somehost.example.com:19000/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 process 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. For each of the ports listed, keep or enter another port. For a listing of the default ports, see Hyperion Installation Start Here, Chapter 5: “Ports”, under Reporting and Analysis, see Foundation Ports.
Configuring the SQR Production Reporting Engine for Interactive Reporting When you run Hyperion Configuration Utility for the services, the Configure SQR Production Reporting Engine dialog box displays.
➤ To configure SQR Production Reporting engine for Interactive Reporting: 1 To configure SQR 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:
60 Configuring Reporting and Analysis 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
Interactive Reporting Configuration The Default formatting locale for Interactive Reporting displays when you run the Hyperion Configuration Utility for the Repository Configuration. Enter the Default user's language and the default locale for Interactive Reporting.
Financial Reporting Configurations
● “Enabling the Planning ADM Driver” on page 61
● “Print Server Configuration” on page 62
● “Workspace, Print Server, and Scheduler Server Configurations” on page 63
● “Report Server Configuration” on page 63
Enabling the Planning ADM Driver
● “Enabling Planning 9.3.1” on page 61
● “Enabling Planning Details 9.2.0.x / 9.3.0.x” on page 61
Enabling Planning 9.3.1
● The Reporting and Analysis installer automatically enables Planning.
● The PlanningSystemDB.properties is downloaded.
● The installer does not lay down the Planning ADM files. You must run the Planning Installer and select the Custom option. The next screen will allow you to select only the Planning ADM option to be installed. This should be installed on the Financial Reporting Report Server and the Financial Reporting Web Application Server.
● The installation of the Planning ADM can be done either before or after the Reporting and Analysis install.
Enabling Planning Details 9.2.0.x / 9.3.0.x
➤ To enable Planning: 1 You must install the corresponding versions of the Planning ADM driver and Oracle's Hyperion® Essbase® – System 9 Runtime Client (RTC) on the Reporting and Analysis machines. Refer to the Hyperion Planning Installation Guide.
Completing Module-Specific Configurations 61 2 You must manually update config.properties found in
to reflect the location of the Planning ADM install. For example, from: FR_PLANNINGADMDIR=
to: FR_PLANNINGADMDIR=
Enabling the Analytic Provider Services Driver To enable High Availability (HA) using Oracle's Hyperion® Provider Services (APS), you must enable APS driver support for Financial Reporting. For Financial Reporting: On each computer where one or more of the following are installed:
● Financial Reporting Report Server
● Financial Reporting Scheduler
● Financial Reporting Web application
● Financial Reporting Studio Do the following: 1. Edit
Print Server Configuration The Financial Reporting Print Server Configuration task displays when you run the Hyperion Configuration Utility on a machine where the Financial Reporting Print Server component is installed.
Note: To import Financial Reporting content into Word and PowerPoint, Ghostscript is needed.
Select a Print Server configuration:
● Adobe Acrobat Distiller 6.0 or higher
● GNU Ghostscript 7.0.6 or AFPL Ghostscript 8.5.1
● None of the above. Do not generate PDFs
62 Configuring Reporting and Analysis Workspace, Print Server, and Scheduler Server Configurations To configure the Financial Reporting Workspace Web application, Print server, and Scheduler server, enter the following locations:
● Workspace Web Application URL
● Financial Reporting Print Server Location(s)
● Financial Reporting Scheduler Server
Note: To specify multiple Print Service locations, enter the machine names, separated by commas.
Report Server Configuration The Financial Reporting Report Server Configuration displays when you run the UIservices Hyperion Configuration Utility to configure the Financial Reporting Reports Server and the Financial Reporting Web Application is on another machine. Enter the hostname of the Financial Reporting Report Server machine.
Web Analysis Configuration - Enabling the Analytic Provider Services Driver To enable High Availability (HA) using Oracle's Hyperion® Provider Services (APS), you must enable APS driver support for Web Analysis.
➤ To enable the Analytic Provider Services Driver: 1 Edit:
set EESPlugInSupported property value to true set EESServerName=
into the folder corresponding to Web Analysis classpath. For example: if WA is deployed on Tomcat, copy these files into:
Completing Module-Specific Configurations 63 SQR Production Reporting Configurations When you run Hyperion Configuration Utility for the services, the Configure SQR Production Reporting Engine dialog box displays. Enter:
● Select whether you want to configure Production Reporting engine
● SQR Production Reporting binary folder according to the chosen repository type
● Database client home
● Repository connection string.
Reconfiguring Products Hyperion Configuration Utility enables you to reconfigure products to incorporate changes in your environment such as a different application server. To reconfigure, launch Hyperion Configuration Utility on the computer hosting the product, and follow the procedures in this chapter.
Note: If you reconfigure a database, restart the application server afterward.
Testing Module Availability For each of the products used, verify the setup by using the URLs below. If you have changed the web server configuration, restart the web server before running these tests.
Product URL* Expected Result
Workspace http://
Financial Reporting http://
Web Analysis http://
Performance Management Architect http://
64 Configuring Reporting and Analysis Product URL* Expected Result
Financial Management http://
Planning http://
*URL: Where
Post Configuration Tasks To finish the configuration, see “Post Configuration Tasks” on page 66.
Error Messages When Testing Module Availability When testing the Reporting and Analysis Modules availability using Internet Explorer, if an error message is received, disable friendly HTTP error messages.
➤ To disable the friendly HTTP error messages Internet Explorer feature: 1 In Internet Explorer, click Tools > Internet Options. 2 Click the Advanced tab. 3 Clear Show friendly HTTP error messages. HTTP Errors from the Web server:
● 404—The Web server or the plug-in is not proxying requests to the application server. Check http://
● 500—The Web server plug-in is attempting to proxy requests to the application server, but the application server is not responding. Ensure the application server is started, and verify the plug-in configuration is correct.
Post Configuration Tasks 65 Post Configuration Tasks
Configuring WebLogic 9.x OpenJMS for Web Analysis This section assumes that you have Reporting and Analysis components installed and configured in clustered environment.
Installing OpenJMS
➤ To install OpenJMS: 1 Download latest version of OpenJMS server from http://openjms.sourceforge.net/ 2 Unpack the created archive to the desired host. 3 Open system environment variables editor: Start > Settings > Control Panel > System > Advanced > Environment Variables. 4 Click New on the System variables pane and enter OPENJMS_HOME as the variable name and folder with unpacked OpenJMS; for example: D:\openjms-0.7.7-alpha-3. Click OK to add variable. 5 Click New on the System variables pane and enter JAVA_HOME as the variable name:
Configuring OpenJMS Databases OpenJMS is provided with preconfigured Derby database engine, so this procedure is not mandatory. But, if you wish to gain a better performance in production, you should configure OpenJMS to use a commercial database engine.
Microsoft SQL Server 2000 SP3/ Microsoft SQL Server 2003
➤ To configure: 1 Download JDBC drivers from Microsoft: http://www.microsoft.com/downloads/details.aspx?FamilyID=07287b11-0502-461a- b138-2aa54bfdc03a&DisplayLang=en 2 Create MS SQL Database and user for OpenJMS. User must have permissions to create tables. Select from sysobjects table, create procedures, views and functions. 3 Edit %OPENJMS_HOME%\bin\setenv.bat: rem Configures the JDBC driver set JDBC_PATH=
where
66 Configuring Reporting and Analysis 4 The JDBC driver connection properties needs to be set in the OpenJMS configuration file: %OPENJMS_HOME%\config\openjms.xml:
Wait for dbtool.bat to finish with a “Successfully created tables” message.
Oracle Database Server 9i/10g
➤ To configure Oracle Database 9i or 10g: 1 Copy Oracle JDBC drivers archive:
from database server to host, which will be running OpenJMS server. 2 Create Oracle database user for OpenJMS. User must have CONNECT and RESOURCE permissions. 3 Edit %OPENJMS_HOME%\bin\setenv.bat: rem Configures the JDBC driver set JDBC_PATH=
where
Post Configuration Tasks 67
Wait for dbtool.bat to finish with a “Successfully created tables” message.
Configuring and Starting OpenJMS Server
➤ To configure and start OpenJMS server: 1 Set correct host name in %OPENJMS_HOME%\config\openjms.xml. Line:
and disable TCP connector by removing
and disable security by adding the following element to Configuration section:
Configuring Web Analysis to use OpenJMS
➤ To configure Web Analysis: 1 Open:
and add the following properties on all servers in the cluster running Web Analysis Web applications: Cluster=true atf.messaging.provider-url=rmi://
68 Configuring Reporting and Analysis Configuring WebLogic 9.x JMS Server for Web Analysis
➤ To configure JMS Server Web Analysis cluster for WebLogic 9.x: 1 Navigate to Services -> Persistent Stores, click Lock & Edit: a. Click New, select File or JDBC Store. b. Enter Store name; for example: biplus_store, Target (one of the migratable Web Analysis server), and Directory or Data Source. c. Click Finish and Activate Changes. 2 Navigate to Services > Messaging > JMS Modules and click Lock & Edit. a. Click New and enter Name. b. Click Next and select wa-cluster with all servers as targets. c. Click Next, select “Would you like to add resources to this JMS system module?”, and click Finish. 3 Create Connection factory and Distributed destination: a. Click New, and select Connection factory. b. Click Next, and enter Name, Factory and JNDI name as JmsTopicConnectionFactory.
Note: The name can not be changed. c. Click Next, wa-cluster, with all servers, is selected. d. Click Finish. e. Click New, and select Distributed Topic, Click Next. f. Specify atf_naming_sync as the distributed destination and JNDI name (name can’t be changed). Load balancing policy is Round-robin. g. Click Next, wa-cluster (with all servers) is selected. h. Click Finish and Activate Changes. 4 Navigate to Services > Messaging-> JMS Servers, and click Lock & Edit. a. Click New, and enter Server name. b. Select your persistent store which was created in the 1st step. c. Click Next, and select Target, which was selected in step 3.b. d. Click Finish and Activate Changes. 5 Open WebAnalysis.properties, and append the following lines: Cluster=true atf.event.broker.idle-time=1001 atf.messaging.provider-url=t3://
where
Post Configuration Tasks 69 a. Click on the earlier created JMS Server > Monitoring > Active destinations. b. Check that during testing Web Analysis; for example: report changes, “Messages Received” is increased.
Setting up WebSphere 6.0 OpenJMS and Web Analysis This section assumes that you already have Reporting and Analysis components installed and configured in a clustered environment. WebSphere Embedded Messaging component must be installed as well.
Configuring WebSphere 6.0 Embedded Messaging and Web Analysis Cluster (Reporting and Analysis )
Configure Service Integration Bus
➤ To configure service integration bus: 1 Log into WebSphere Administrative Console. 2 Navigate to Service integration > Buses. 3 Click New to create a new service integration bus. 4 Specify bus name; for example: hyperion-jms-bus. 5 Clear Secure to disable bus security. 6 Click OK to save changes to the master configuration. 7 Click on newly created bus and navigate to Bus members on Topology widget. 8 Select the server which will be running JMS server. 9 Click Next and Finish to add a new bus member. 10 Save changes to the master configuration.
Configure WebSphere ORB Port
➤ To configure WebSphere ORB port: 1 Log into the WebSphere Administrative Console. 2 Navigate to Servers•Application servers. 3 Select server from list – this must be the same server, which was assigned as a bus member in previous step. 4 Click on Ports link. 5 Assign a valid port number to ORB_LISTENER_ADDRESS: a. Click on the corresponding link and enter the desired port; for example: 6888. b. Click OK.
70 Configuring Reporting and Analysis 6 Save changes to the master configuration.
Define WebAnalysis topic Connection Factory and Topic Destination
➤ To define topic connection factory and topic destination:Web Analysis 1 Log into the WebSphere Administrative Console. 2 Navigate to Resources > JMS Providers > Default messaging. 3 Enter JMS server node and name in Scope setting and click Apply. 4 To create a new topic connection factory, click on the JMS topic connection factory link and then New. 5 Specify JmsTopicConnectionFactory for both Name and JNDI name. 6 Select previously created bus from bus list and click OK. 7 Navigate to Resources > JMS Providers > Default messaging. 8 To create a new topic destination, click on JMS topic link and then New. 9 Specify atf_naming_sync for both Name and JNDI name. 10 Select previously created bus from bus list and click OK. 11 Save changes to the master configuration.
Configure Web Analysis to use WebSphere JMS
➤ To configure Web Analysis to use WebSphere JMS: 1 Open:
and add the following properties on all servers in the cluster running Web Analysis Web applications: Cluster=true atf.event.broker.idle-time=1001 atf.messaging.context- factory=com.ibm.websphere.naming.WsnInitialContextFactory atf.messaging.provider-url=iiop://
where
Verifying Startup Dependencies Before starting Reporting and Analysis, verify that Shared Services server is running. For instructions to start Shared Services server, see “Starting Shared Services” on page 72.
Post Configuration Tasks 71 Note: After you configure each product, you must open registry.properties—in
Note: Before performing these steps you should have registered with the Shared Services Server during the Reporting and Analysis configuration process.
To start all installed Reporting and Analysis components, run the consolidated start script
Starting Shared Services If you deployed the Shared Services application server as a Windows service, to start Shared Services manually, from the Windows control panel, select Administrative Tools > Services.
➤ If you did not deploy Shared Services application server as a Windows service, to start the Shared Services server: 1 Select Start > Programs > Hyperion > Foundation Services > Start Shared Services. 2 If the menu item does not indicate the application server to which the Shared Services server is deployed, you must start Shared Services server manually.
➤ To start Shared Services server manually, execute the startup script:
Application Server Path to Script
IBM WebSphere
BEA WebLogic 8.1.x
BEA WebLogic 9.1.x
Oracle To start Oracle Enterprise Manager:
72 Configuring Reporting and Analysis Application Server Path to Script
Apache Tomcat
Note:
Verifying Successful Startup of Shared Services
➤ To verify successful startup and configuration of Shared Services: 1 During startup, look for the following confirmation messages in the Shared Services console window:
● Database Configuration Test Passed
● Security System Initialized Successfully
Note: This message will not display for Tomcat.
● Shared Services Initialized Successfully When Shared Services is deployed to WebSphere, the confirmation message is logged to
Post Configuration Tasks 73 Note: As a best practice, the URL should 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.
Optionally, on Windows, you can select Start > Programs > Hyperion > Foundation Services > User Management Console. Display of the Oracle's Hyperion® Shared Services User Management Console login page indicates that the Shared Services server started successfully.
Stopping Shared Services If you installed the Shared Services application server as a Windows service, to stop Shared Services server, use the Windows control panel.
➤ To stop Shared Services server manually: 1 Execute the stop script:
Application Server Path to Script
IBM WebSphere
BEA WebLogic 8.1.x
BEA WebLogic 9.1.x
Oracle To stop Oracle Enterprise Manager:
where Shared Services has been deployed to instance “
Apache Tomcat
Note: On Windows systems, you can optionally select Start > Programs > Hyperion > Foundation Services > Stop Shared Services. 2 On WebLogic, if a message that suggests using the FORCESHUTDOWN command is displayed, use the FORCESHUTDOWN command to stop Shared Services server:
74 Configuring Reporting and Analysis a. In a text editor, open the stop script. See the table under Step 1 for the stop script location. b. In the file, find SHUTDOWN, and replace it with FORCESHUTDOWN. c. Save and execute the file.
Reporting and Analysis Administrator User
➤ To provision a Reporting and Analysis Administrator for login testing, see the Hyperion System 9 Security Guide.
Launching Reporting and Analysis Modules
➤ To access 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 For each of the products used, verify the setup by using the URLs below.
Post Configuration Tasks 75 Product URL* Expected Result
Workspace http://
Financial Reporting http://
Web Analysis http://
Performance Management Architect http://
Financial Management http://
Planning http://
*URL: Where
Adding Content Expiration Headers You add content expiration headers for any of the following reasons:
● http compression is on
● SSL is used
● Multiple versions of the product are being used. The older version required that the browser be configured to check for new files on every visit to the page. This is not necessary and hurts performance on new versions of the product. Adding content expiration headers to files served by the new product improves performance by overriding the browser's settings and forcing the files to be cached.
76 Configuring Reporting and Analysis ➤ To add content expiration headers, add the following lines to httpd.conf for Workspace and Web Analysis static content: LoadModule expires_module modules/mod_expires.so
Changing the Apache Web Server Listen Port
➤ To change the Apache Web server Listen Port: 1 Open http.conf and add a Listen directive:
● 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.
Customizing Ports Used by Interactive Reporting Service, Interactive Reporting Job Service and Interactive Reporting Data Access Service Ports used by Interactive Reporting services can be customized in:
which defines these default port ranges:
● Interactive Reporting Data Access Service—6811, 6812
● Interactive Reporting Service—6813, 6814
● Interactive Reporting Job Processor—6815
● Interactive Reporting Logging Utility—6810
Post Configuration Tasks 77 Guidelines for Changing Port Ranges
● Port range should be a comma-separated list of ports in the PORT_RANGE property for each service type. For example, for Data Access Service, change the PORT_RANGE property values under the
● Number of ports to be configured should match the MAX_NUMBER_OF_MANAGED_SERVICES property value. For example, when MAX_NUMBER_OF_MANAGER_SERVICES property value is 3, three separate ports must be specified in the PORT_RANGE property value.
Service Types Used in irmconfig.xml
● Interactive Reporting Data Access Service—
● Interactive Reporting Service—
● Interactive Reporting Job Processor—
● Interactive Reporting Logging Utility—
Sample irmconfig.xml The following is a Windows sample of irmconfig.xml:
78 Configuring Reporting and Analysis
Post Configuration Tasks 79
where
Setting up SiteMinder with Transparent Logon The ability to transparently log on to Reporting and Analysis using SiteMinder is supported. The following sections detail the Reporting and Analysis configuration steps required for SiteMinder integration.
Prerequisites The following components should be already installed and configured according to corresponding product’s documentation:
● Reporting and Analysis Services and UI Services must be installed and configured
● SiteMinder Policy Server 6.0 must be installed and configured
● IBM HTTP Server 2.x (2.0.47.1 recommended), or Apache Web Server 2.x (2.0.52 recommended), must be installed
● SiteMinder Web Agent 6 must be installed on the Web server host
80 Configuring Reporting and Analysis Enabling the SiteMinder Web Agent for Microsoft IIS Open
Creating the IBM HTTP Server/Apache Web Agent Configuration File
➤ To create the configuration file: 1 Execute
and enable the Web agent by changing the default of NO to YES: enableWebAgent=”YES”
Configuring IBM HTTP Server/Apache SiteMinder Modules
➤ To configure IBM HTTP Server/Apache SiteMinder Modules: 1 Open
and verify the following lines, adding them if needed: LoadModule sm_module "
Configuring the SiteMinder Policy Server
➤ To configure the SiteMinder Policy Server: 1 Log on to Policy Server Administration console. 2 Right-click on Agents->Create Agent.
● In Agent Properties, enter the agent name as was specified in Web Agent configuration file on the Web server host.
Post Configuration Tasks 81 ● Optional: Enter a description of a new agent.
● Click OK. 3 In the left tree view select Agent Conf Objects. 4 Right-click on IISDefaultSettings or ApacheDefaultSettings, depending on the Web server software you have installed, and select Duplicate Configuration Object in context menu. 5 On Agent Configuration Object Properties, give a name to a new configuration object: a. Double-click on #DefaultAgentName. b. In the Edit Parameter Dialog, in Parameter Name, remove the comment (#) character from the property name and for Value, and assign the same name as specified for the Agent. c. Double-click on #BadUrlChars and remove “//” from BadUrlChars value. d. Uncomment #BadCssChars and leave Value blank. e. Double-click on #IgnoreExt. f. Uncomment #IgnoreExt and, for Value, remove the following extensions: .gif, .jpg,.jpeg,.png. g. Uncomment #LogFileName and, for Value, enter a log file name and location. h. Set Logfile property to yes if you want to enable agent logging. i. Click OK. 6 In the left tree view select Domains and expand your domain. 7 Right-click on realms and select Create realm in context menu. a. Assign Workspace as the realm name, and then select the previously created Web Agent using the Lookup button. b. Set Resource Filter to /workspace. c. Click OK. 8 Right-click on realms and select Create realm in context menu. a. Assign Web Analysis as the realm name, then select the previously created Web Agent using the Lookup button. b. Set Resource Filter to /WebAnalysis. c. Click OK 9 Right click on realms and select Create realm in context menu. a. Assign Financial Reporting as the realm name, then select the previously created Web Agent using the Lookup. b. Set Resource Filter to /hr. c. Click OK. 10 Right-click on the Workspace context realm created in step 7a and select Create realm under realm. a. Enter realm Name: configUrl. b. For Resource Filter: /browse/configURL.
82 Configuring Reporting and Analysis c. Select Unprotected radio button. d. Click OK. 11 Under the WebAnalysis realm, create the unprotected realm for: /com/hyperion/plaf/images subcontext 12 Under the WebAnalysis realm, create another unprotected realm for /servlet/com/hyperion/plaf/images subcontext 13 Under the WebAnalysis realm, create another unprotected realm for /processor sub-context 14 Right-click on Workspace realm and select Create Rule under realm. 15 Assign a name to the rule, then, while holding down the Ctrl key, select Get, Post and Put from the actions list. Click OK. 16 Create the same rule for Web Analysis realm. 17 Create the same rule for the Financial Reporting realm. 18 In the domain tree right click on Responses and select Create Response. 19 Assign a Name to a new Response and click Create to create a new Attribute. 20 Navigate to theAdvanced tab and enter ‘hyplogin=<%userattr="SM_USERLOGINNAME"%>’ to Script (without single quotes) and click OK to save a new Attribute. 21 Click OK to save the Response. 22 Right-click on Policies in Domains tree and select Create Policy. 23 Assign a policy name, then set up directory access. 24 On the Rules tab, click Add/Remove. 25 Move rules created for Reporting and Analysis to the Current Members list. 26 Click OK. 27 In the Policy Dialog, select all the Reporting and Analysis rules that were created and click the Set Response button. 28 For each Reporting and Analysis module, select the Response created in the previous steps then click OK. 29 Click OK to save the policy.
Setting up Workspace Web Application Parameters
➤ To setup Workspace Web Application parameters: 1 Start Servlet Configurator:
2 Navigate to Properties > User Interface > Login. 3 Set property Custom username policy to $SECURITY_AGENT$ and Custom password policy to $TRUSTEDPASS$: Click File->Save and File->Exit.
Post Configuration Tasks 83 4 Run settrustedpass.batlocated in the
Setting the Trusted Password on the Authentication Service Set the same password as in the previous step for the Authentication Service.
➤ To set the trusted password on the Authentication Service: 1 Log on to the Local Service Configurator under:
Note: User must have Global Administrator role assigned to perform these changes. 2 Click Show host properties. 3 Click the Authentication tab and set the password. 4 Click OK.
Configuring Shared Services
➤ To configure Shared Services: 1 Log on to Shared Services. 2 Navigate to Administration->Configure User Directories. 3 Select Support Security Agent for Single Sign-on. 4 Click Save. 5 Select Requisite Provider and click Edit. 6 Select Trusted. 7 Click Save.
Restarting Components
➤ To restart components: 1 Stop all Reporting and Analysis components. 2 Stop the SiteMinder configured Web server. 3 Restart the Shared Services application.
84 Configuring Reporting and Analysis 4 Start Reporting and Analysis common services, BI and DAS service. 5 Start the Financial Reporting services. 6 Start the Workspace Web application. 7 Start the SiteMinder enabled Web server. 8 Start the WebAnalysis and Financial Reporting Web applications.
Post Configuration Tasks 85 86 Configuring Reporting and Analysis Uninstalling and Reinstalling 5 Reporting and Analysis
In This Chapter Prerequisites...... 87 Deregistering Reporting and Analysis with Shared Services...... 87 Uninstalling ...... 88 Reinstalling...... 90
Prerequisites Before you perform an uninstall:
● Optional: Backup Installation, Hyperion Home, and repository directories. See the Hyperion Workspace Administrator's Guide.
● Stop Reporting and Analysis.
● Manually stop all services either by the control panel, closing the DOS window, or running a stop script. Services include: Open Ldap, Apache, Shared Services, Reporting and Analysis Web applications, Workspace, Financial Reporting, and Interactive Reporting.
● Deregister from Shared Services.
Deregistering Reporting and Analysis with Shared Services
➤ To deregister products with Shared Services: 1 Launch Hyperion Configuration Utility. See “Configuring Reporting and Analysis” on page 51. 2 From the list of installed products, select those to configure, and click Next. 3 From the list of configuration tasks, select Deregister from Shared Services, 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 In the Password text box, enter the password for the specified Shared Services user. 5 Click Next.
Prerequisites 87 Uninstalling
Caution! During uninstall, the Reporting and Analysis directory is deleted.
➤ To uninstall Reporting and Analysis: 1 Start the Uninstall wizard by one of the following means:
● Use the Start menu: a. Select Start > Setting > Control Panel > Add or Remove Programs. b. Click Change/Remove to initiate the uninstall for:
● Hyperion Reporting and Analysis Services
● Hyperion Reporting and Analysis UIServices
● SQR Production Reporting
● Migration Utility
● Client
Note: When you run the UIServices uninstall, Application Servers will undeploy.
● Run uninstall.exe, by browsing to the following locations:
The wizard Language screen displays. 2 Select the country where you are uninstalling the software, and click Next. 3 When the Welcome screen displays, click Next. 4 The Summary screen displays. 5 Verify programs you want uninstalled, and click Next. 6 When the wizard finishes the uninstall, click Finish. 7 Verify that Reporting and Analysis directories are deleted. 8 If uninstalling all Hyperion products, rename C:\WINDOWS\vpd.properties. 9 Remove files from the registry: a. Start the Registry Editor up by clicking Start > Run. b. Type regedit. 10 Optionally, remove the following Registry entries:
88 Uninstalling and Reinstalling Reporting and Analysis Keys\ Sub-keys Remove values
HKEY_CURRENT_USER\
Software\ Folders:
● Brio Software ● Interactive brioqry ● SQR Developer entries
Software\Microsoft\WindowsNT HR* \CurrentVersion\PrinterPorts
HKEY_LOCAL_MACHINE\
SOFTWARE\Brio Software Entries pertaining to:
● Interactive Reporting Studio ● SQR Developer
SOFTWARE\Hyperion Solutions Financial Reporting (HR) server install items:
● Hyperion Reports\HRCommSrv ● Hyperion Reports\HReports ● Hyperion Reports\HReports\JVM ● HRPrintSrv ● Hyperion Reports\HRReportSrv ● Hyperion Reports\HRSchedSrv All entries pertaining to:
● Dashboard Development Services ● Hyperion Intelligence Architect ● Hyperion Intelligence Dashboard builder ● Hyperion Reports ● Interactive Reporting Studio
.....SOFTWARE\Hyperion Solutions\InstalledComponents HR*
SOFTWARE\Microsoft\Windows\CurrentVersion Selectively remove unused SharedDLL entries related to ADM
SOFTWARE\Microsoft\Windows\CurrentVersion Hyperion System 9* \Uninstall\Hyperion System 9
SOFTWARE\Microsoft\WindowsNT HR* \CurrentVersion\Print\Printers
SYSTEM\CurrentControlSet\Control\Print Hyperion PS entries \Environments\Windows NT x86\Drivers\Version-3
SYSTEM\CurrentControlSet\Control\Print\Printers HR*
SYSTEM\CurrentControlSet\Services ● HR*
Uninstalling 89 Keys\ Sub-keys Remove values
● Hyperion Interactive Reporting* ● Hyperion Financial Reporting* ● Hyperion WebAnalysis*
HKEY_USERS\
.DEFAULT\Software\Microsoft\WindowsNT\CurrentVersion HR* \Devices
11 Reboot your machine.
Note: Rebooting will remove ControlSet01 entries.
Reinstalling Reinstall applies only when you are installing the same version of software a 2nd time.
Reinstalling Services
➤ To reinstall Services: 1 Stop all services. 2 Backup the current installation folder. 3 Run the Services installer, selecting the existing installation folder. 4 Run the Hyperion Configuration Utility and select Database configuration and Financial Reporting configuration. 5 Restart services.
Note: If you previously customized server.xml, config.dat, you must manually restore your edits. For more information, see the Hyperion Workspace Administrator's Guide.
Reinstalling UIServices
➤ To reinstall the same version of UIServices: 1 Stop the application server instance, which is running Workspace, Web Analysis, and Financial Reporting. 2 Stop the Web server. 3 Backup the deployed Web Application directory; for example:
90 Uninstalling and Reinstalling Reporting and Analysis
● Shared Services registration
● Financial Reporting configuration
Reinstalling Client
➤ To reinstall the Client: 1 Stop the client software on the machine. 2 Backup the installation folder. 3 Run the Client installer, selecting the existing installation folder. 4 If Financial Reporting Client is installed, then run the Hyperion Configuration Utility and execute Financial Reporting configuration task.
Reinstalling 91 92 Uninstalling and Reinstalling Reporting and Analysis Upgrading Reporting and 6 Analysis from 9.x to 9.3.1
In This Chapter Prerequisites...... 93 Upgrading...... 94 Migrating Users and Groups ...... 95 Upgrading Manually Deployed Web Applications...... 97
The following procedure describes upgrading a System 9.x release to 9.3.1. If you are upgrading from a previous release of Hyperion products, note the following supported upgrade paths:
● 9.2.0.3 to 9.3.1
● 9.3.0.x to 9.3.1 If you are using a release prior to 9.2.0.3, you must first upgrade to one of the versions noted above, and then upgrade to 9.3.1. Upgrading from 9.2 releases prior to 9.2.0.3 will be supported in an upcoming service pack.
Prerequisites
● Backup Installation, Hyperion Home, and repository directories. See the Hyperion Workspace Administrator's Guide.
● Stop the following components:
❍ Reporting and Analysis
❍ Application server and Web server
● 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. Registering for an upgrade with the same Shared Services keeps the same provisioning.
● Optional—If you have WebLogic 8.1.6 Application Server (auto-deployment) or manually deployed applications of all Application Server types, delete JSP class files from previous Application Server deployments. Locations of the precompiled JSPs for the Application Servers:
❍ Oracle
Prerequisites 93
❍ Tomcat
❍ WebSphere 6 0.2.11 and WebSphere 6.1:
❍ WebLogic 8.1
❍ WebLogic 9.1
Upgrading When you upgrade, you need to perform the same tasks with the Hyperion Configuration Utility as with a new install; for example: you need to configure Web application and Web server configurations again.
➤ To upgrade: 1 Upgrade Reporting and Analysis components: a. Launch services installers which were installed on the previous installation:
● Services
● UIServices
● Client
● Repservices
94 Upgrading Reporting and Analysis from 9.x to 9.3.1 Note: Be sure that during the installation of the upgrades, you select an existing installation folder (not the new installation option).
Each installer displays the Summary window with a list of components to upgrade. b. Complete the installation by clicking Finish. 2 Launch the Hyperion Configuration Utility to configure upgraded Reporting and Analysis modules: You can use the Hyperion Configuration Utility to configure modules from this release. The Hyperion Configuration Utility determines whether the products installed on the machine are new or upgraded. The product selection page indicates which modules are upgraded. Perform all configuration tasks. As a troubleshooting measure, configure upgraded modules one at a time because each product may be configured for a different database. Likewise, you cannot configure new products and upgraded products simultaneously. 3 In the Database Configuration window, enter the password. 4 Install and run the Migration Utility. See “Migration Utility” on page 99.
Migrating Users and Groups This section describes the steps you must perform to migrate users and groups to support the move Organizational Unit (OU) feature. It needs to run ONLY ONCE for cleaning up an upgraded system with external providers (LDAP/MSAD) in which users/groups have been moved across multiple OUs. Any future movement of users/groups will be automatically taken care of by Shared Services if configured appropriately.
Prerequisites
● Before starting the migration of users and groups, see the Hyperion Security Administration Guide for complete information about the OU feature.
● Hyperion recommends that you back up the user and group data in OpenLDAP and Reporting and Analysis before starting the migration process. After migrating users and groups to use the new identity attribute, you cannot revert to the previously used identity attribute. To revert, restore user and group data in OpenLDAP and Reporting and Analysis repository from the backups.
● After upgrading Reporting and Analysis, migrate users and groups to the new identity attribute before performing any other operation such as loading security or changing existing security settings. Such changes may be lost during the migration.
Migrating Users and Groups 95 About SyncCSSIdentity_BI Utility Reporting and Analysis uses the SyncCSSIdentity_BI utility to synchronize user and group identities stored in its relational database to reflect the identity attribute set in Shared Services. Run the SyncCSSIdentity_BI utility only if Shared Services was upgraded to use the new identity attribute. This utility performs the following tasks: 1. Updates the CSSidentities in Reporting and Analysis (database) tables for users and groups from external providers if users and group happen to change their Organizational Units (OUs). 2. Updates the access control and ownership information in Reporting and Analysis database tables for the objects having some association with these users and groups. Run the utility if these two conditions are met:
● Shared Services uses the new identity attribute
● If you have data resulting from inter-OU moves in the user directories.
Running SyncCSSIdentity_BI utility Run the SyncCSSIdentity_BI utility for:
● “Using Most Provider Types” on page 96
● “Using Provider Type Sun One LDAP Server” on page 97
Using Most Provider Types
➤ To run the SyncCSSIdentity_BI utility for most provider types: 1 Execute the utility after upgrading Shared Services and Reporting and Analysis but before starting Reporting and Analysis services. This utility needs to be run only once 2 Verify that Shared Services is running. 3 Stop Reporting and Analysis Services. 4 The SyncCSSIdentity_BI utility comes as a part of 9.3.1 installation of Reporting and Analysis Services and is installed in:
for this utility. The default level is set to WARN. You can use your own log4j config.xml file by specifying it as a JVM system property as: -Dlog4j_config=
Runtime information from SyncCSSIdentity_BI utility is written into:
96 Upgrading Reporting and Analysis from 9.x to 9.3.1
Using Provider Type Sun One LDAP Server For provider type Sun ONE LDAP Server, you need to run the utility each time you move a user or group from one OU to another.
➤ To run the SyncCSSIdentity_BI utility for type Sun ONE LDAP Server: 1 Run the updateNativeDir utility before moving the a user or group.
Note: Ask Support for the updateNativeDir utility. 2 Move the user or group. 3 Run SyncCSSIdentity_BI utility. See “Using Most Provider Types” on page 96. 4 Run updateNativeDir utility again.
Upgrading Manually Deployed Web Applications The following procedure upgrades manually deployed Web Applications from releases 9.0.1, 9.2, and 9.3 to the current release:
➤ To upgrade manually deployed Web Applications: 1 Stop the application server instance, which is running Workspace, Web Analysis, and Financial Reporting. 2 Stop the Web server. 3 Backup the current deployed Application folder structure by copying the root deployment folder to another folder. 4 Backup the existing Web server configuration files; for example: httpd.conf and HYSLWorkers.properties for Apache.
Upgrading Manually Deployed Web Applications 97 5 Run the latest installer for uiservices, selecting the existing installation folder for uiservices. 6 Run the Hyperion Configuration Utility and select Deploy to Application Server and Configure Web Server. 7 On the Select the Application Server and Deployment Type window, for Oracle 10g or JES 8.x, you must select manual. 8 Deploy the WAR file. See the current deployment instructions:
● Chapter 8, “Configuring a Web Server with Apache Tomcat”
● Chapter 9, “Manually Deploying into Oracle 10g Release 3 (10.1.3.1.0) Application Server”
● Chapter 10, “Manually Deploying into Oracle 10g Release 2 (10.1.2.0.2) Application Server”
● Chapter 11, “Manually Deploying into WebLogic 9.1”
● Chapter 12, “Manually Deploying into WebLogic 8.1”
● Chapter 13, “Manually Deploying into WebSphere 6.1”
● Chapter 14, “Manually Deploying into WebSphere 6.0.2” 9 Execute post-deploy tasks, using the current deployment instructions. 10 To preserve some existing configuration, like ws.conf settings, copy ws.conf from the backup folder created in step 3 to WEB-INF\config under the newly deployed workspace deployment structure. 11 If some httpd.conf settings have been customized for Apache, copy the httpd.conf from the backup folder in step 4 to the current Apache folder, replacing the existing file. Do the same for IIS configuration settings.
98 Upgrading Reporting and Analysis from 9.x to 9.3.1 Installing the Reporting and 7 Analysis Migration Utility
In This Chapter Migration Utility ...... 99 Requirements...... 100 Supported Source Databases ...... 100 Installing the Migration Utility...... 101 After Installing the Migration Utility...... 102
This chapter includes a brief overview of the Hyperion Migration Utility and procedure to install it on your system. You use the following manuals to migrate:
● Hyperion Reporting and Analysis Migration Utility Guide
● Hyperion Reporting and Analysis Migration Utility Planning Guidelines
● Hyperion Reporting and Analysis – System 9 Readme
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 guides Hyperion Reports, Hyperion Analyzer, Hyperion Performance Suite and Brio Systems customers to migrate to Reporting and Analysis. The Migration Utility supports:
● Migration from:
❍ Brio Intelligence Server 6.6.4 (Brio OnDemand Server 6.6.4 or later and Brio Broadcast Server 6.6.4 or later)
❍ Brio Portal 7.0.5
❍ BrioONE (Brio Portal 7.0.5 or later and Brio OnDemand Server 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
Migration Utility 99 ❍ 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 Hyperion Installation Start Here.
Supported Source Databases
Table 9 Supported Source Databases:
Oracle's Oracle's Hyperion® Hyperion® SQR® Interactive Production Reporting Brio Financial Web Reporting – Reporting – Database: and Analysis Portal Reporting Analysis System 9 System 9
IBM DB2 X X X X X X
Informix X X X
Microsoft SQL X X X X X X Server
OpenEdge X
Oracle X X X X X X
Progress X
Redbrick X X
SAP BW X X X X X
100 Installing the Reporting and Analysis Migration Utility Oracle's Oracle's Hyperion® Hyperion® SQR® Interactive Production Reporting Brio Financial Web Reporting – Reporting – Database: and Analysis Portal Reporting Analysis System 9 System 9
SAP R/3 X X X
Sybase X X X
Teradata X 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 Double-click the ZIP file to decompress it. 3 Close all Reporting and Analysis programs. 4 Launch the installation setup file setupWinPlatform.exe.
5 The Reporting and Analysis Welcome screen is displayed. 6 Click Next. The Country Location is displayed. 7 Select the country’s location describing where the Migration Utility is, and click Next. 8 Read the License Agreement, select I ACCEPT, and click Next. 9 The directory path for the installation is displayed. Click Next to accept the location, or click Browse to select a new location. 10 Select the installation path for Hyperion Home. The common components for Hyperion products are installed to
Note: If the installation program detects a directory for Hyperion Home, Directory Name and Browse are disabled. 12 The Summary displays the installation location and size. Click Next. A progress box is displayed. 13 When the installation is complete, Install Shield informs you whether the installation was successful. 14 Click Finish.
Installing the Migration Utility 101 15 To verify the installation:
● Run the migrator.bat file in the folder where you installed the Migration Utility. For example:
● Select Start > Programs >Hyperion Reporting and Analysis > Utilities and Administration > Migration Utility.
After Installing the Migration Utility The Hyperion Migration Utility:
● Creates a Migration Utility installation log:
Directory Structure Description of Contents
bin INI files and executables for the Migration Utility
conf product specific property files
help Help files
install Installation files
lib Migration JAR files
log Migration Utility log
uninstall Uninstall files
● Adds migration utility entries to the Windows Registry.
● Migration logs are placed in:
102 Installing the Reporting and Analysis Migration Utility Configuring a Web Server with 8 Apache Tomcat
In This Chapter Configuring Apache...... 103 Configuring IIS...... 107
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. See “Web Server Use in Hyperion” on page 16. The Hyperion Configuration Utility will automatically deploy Hyperion components on Apache Tomcat. It will also automatically configure Web server plug-ins for the Apache Web Server or Microsoft IIS, provided the designated Web server machine is also used to host Workspace. Configuration of a Web server on a machine separate from Workspace is a manual process.
Note: All of the commercial-grade Application Servers supported by Hyperion have extensive documentation regarding Web server plug-in configuration. Hyperion specific requirements are documented in each manual deployment section of this guide, and should be considered supplemental information to the vendor provided documentation.
Configuring Apache The following procedures use Apache 2.0.52. Other versions may require that you obtain an appropriate version of the Tomcat-Apache plug-in binary (mod_jk) from: http://tomcat.apache.org/connectors-doc/webserver_howto/apache.html
Copy Required Files to the Apache Machine
➤ To copy the required files: 1 On the Apache machine, copy the Apache-Tomcat plug-in binary:
Configuring Apache 103 to:
to a location accessible to Apache, such as
to the same location.
Create the Tomcat Web Server Plug-in Configuration Files Perform the following procedure on the Apache machine.
➤ To create the configuration files: 1 Using a text editor, create the file:
with the following line: worker.list=Workspace worker.Workspace.type=ajp13 worker.Workspace.host=hostname.example.com worker.Workspace.port=45002
Note: If you have more than one System 9 Workspace module installed,worker.list can contain a comma delimited list of workers. For each worker defined in worker.list, you must define type, host, and port. The values assigned must match those entered in the Hyperion Configuration Utility during the application server Deployment task.
Example workers.properties for an installation that contains Workspace, Financial Reporting, and Web Analysis, each on its own machine: worker.list=Workspace,Financial_Reporting,Web_Analysis worker.Workspace.type=ajp13 worker.Workspace.host=hostname.example.com worker.Workspace.port=45002 worker.Financial_Reporting.type=ajp13 worker.Financial_Reporting.host=hostname.example.com worker.Financial_Reporting.port=8202 worker.Web_Analysis.type=ajp13 worker.Web_Analysis.host=hostname.example.com worker.Web_Analysis.port=16002 2 Create the file:
104 Configuring a Web Server with Apache Tomcat
The following example applies to an installation that contains Workspace, Financial Reporting, and Web Analysis: JkMount /workspace/cdsrpc Workspace JkMount /workspace/administration/* Workspace JkMount /workspace/browse/* Workspace JkMount /workspace/personalpages/* Workspace JkMount /workspace/viewmanager/* Workspace JkMount /workspace/jobmanager/* Workspace JkMount /workspace/ihtml/* Workspace JkMount /workspace/dataaccess/* Workspace JkMount /workspace/logon Workspace JkMount /workspace/logon/* Workspace JkMount /workspace/prefs Workspace JkMount /workspace/js/* Workspace JkMount /workspace/modules/* Workspace JkMount /workspace/resources/* Workspace JkMount /workspace/conf/* Workspace JkMount /workspace/media/* Workspace JkMount /workspace/BPMContext Workspace JkMount /workspace/wsrp4j/* Workspace JkMount /workspace/ResourceProxy Workspace JkMount /workspace/ Workspace JkMount /workspace/*.jsp Workspace JkMount /workspace/*.jsv Workspace JkMount /workspace/*.jsw Workspace JkMount /hr Financial_Reporting JkMount /hr/* Financial_Reporting JkMount /WebAnalysis/ServerConsole/* Web_Analysis JkMount /WebAnalysis/templates/* Web_Analysis JkMount /WebAnalysis/hfmtemplates/* Web_Analysis JkMount /WebAnalysis/hitemplates/* Web_Analysis JkMount /WebAnalysis/portlettemplates/* Web_Analysis JkMount /WebAnalysis/processor Web_Analysis JkMount /WebAnalysis/servlet/* Web_Analysis JkMount /WebAnalysis/modules/* Web_Analysis JkMount /WebAnalysis/resources/* Web_Analysis JkMount /WebAnalysis/DirectoryServlet Web_Analysis JkMount /WebAnalysis/config Web_Analysis JkMount /WebAnalysis/Config Web_Analysis JkMount /WebAnalysis/wa_javadocs/* Web_Analysis JkMount /WebAnalysis/ Web_Analysis JkMount /WebAnalysis/*.jsp Web_Analysis JkMount /WebAnalysis/*.xml Web_Analysis JkMount /WebAnalysis/*.jar Web_Analysis JkMount /WebAnalysis/*.exe Web_Analysis
Enable the Tomcat Web Server Plug-in in httpd.conf To enable, open the following file in a text editor:
Configuring Apache 105 LoadModule jk_module modules/mod_jk-1.2.8-apache-2.0.52.so
# Set the jk log level [debug/error/info] JkLogLevel info
# Select the log format JkLogStampFormat "[%a %b %d %H:%M:%S %Y] "
# JkOptions indicate to send SSL KEY SIZE, JkOptions +ForwardKeySize +ForwardURICompat -ForwardDirectories
Include conf/jkmount.conf
Create Aliases for Workspace and Web Analysis While not required, it is highly recommended that Apache be configured to serve static content for Workspace and Web Analysis. Doing so will improve performance. To create aliases, in a text editor, open:
Add the following alias directives: Alias /wsmedia "
where
Restart Apache and Test the Tomcat Web Server Plug-in Restart Apache, then test the plug-in by accessing one or more of the URLs below, depending on which modules you have deployed: Workspace: http://
where
106 Configuring a Web Server with Apache Tomcat Configuring IIS
Copy Required Files to the IIS Machine
➤ To copy the required files to the IIS machine 1 On the IIS machine, create a directory to store the Tomcat HTTP plug-in binary and configuration files; for example: C:\Inetpub\jakarta-tomcat 2 From the machine where Workspace is installed, copy the following file to the newly created directory on the IIS machine:
from the WebAnalysis machine to the same location.
Note: The isapi_redirect-1.2.14.dll shipped with Hyperion is not compatible with Windows x64 (64-bit) editions of IIS.
Create the Tomcat HTTP Plug-in Configuration Files Perform the following operations on the IIS machine.
➤ To create Tomcat HTTP plug-in on the IIS machine: 1 Using a text editor, create a file called jakarta.reg with the following contents, substituting directory paths as needed to suit your installation: REGEDIT4 [HKEY_LOCAL_MACHINE\SOFTWARE\Apache Software Foundation\Jakarta Isapi Redirector\1.0] "extension_uri"="/jakarta-tomcat/isapi_redirect-1.2.14.dll" "log_file"="C:\\Inetpub\\jakarta-tomcat\\isapi.log" "log_level"="error" "worker_file"="C:\\Inetpub\\jakarta-tomcat\\workers.properties" "worker_mount_file"="C:\\Inetpub\\jakarta-tomcat\\uriworkermap.properties" 2 Double-click jakarta.reg to import its contents to the Windows registry, or use regedit.exe. 3 Create: C:\Inetpub\jakarta-tomcat\workers.properties
Configuring IIS 107 substituting C:\Inetpub\jakarta-tomcat as needed: worker.list=Workspace worker.Workspace.type=ajp13 worker.Workspace.host=hostname.example.com worker.Workspace.port=45002
If there is more than one Workspace module installed, worker.list can contain a comma delimited list of workers. For each worker defined in worker.list, you must define type, host, and port. The values assigned must match those entered in the Hyperion Configuration Utility during the application server Deployment task. Example workers.properties for an installation that contains Workspace, Financial Reporting, and Web Analysis, each on its own machine: worker.list=Workspace,Financial_Reporting,Web_Analysis worker.Workspace.type=ajp13 worker.Workspace.host=hostname.example.com worker.Workspace.port=45002
worker.Financial_Reporting.type=ajp13 worker.Financial_Reporting.host=hostname.example.com worker.Financial_Reporting.port=8202
worker.Web_Analysis.type=ajp13 worker.Web_Analysis.host=hostname.example.com worker.Web_Analysis.port=16002 4 Create: C:\Inetpub\jakarta-tomcat\uriworkermap.properties
substituting C:\Inetpub\jakarta-tomcat as needed. The following example applies to an installation that contains Workspace, Financial Reporting, and Web Analysis: /workspace/=Workspace /workspace/*.jsp=Workspace /workspace/*.jsw=Workspace /workspace/*.jsv=Workspace /workspace/browse/*=Workspace /workspace/ihtml/*=Workspace /workspace/viewmanager/*=Workspace /workspace/logon=Workspace /workspace/dataaccess/*=Workspace /workspace/personalpages/*=Workspace /workspace/prefs=Workspace /workspace/media/*=Workspace /workspace/modules/*=Workspace /workspace/resources/*=Workspace /workspace/js/*=Workspace /workspace/BPMContext=Workspace /workspace/wsrp4j/*=Workspace /workspace/ResourceProxy=Workspace /workspace/administration/*=Workspace /workspace/cdsrpc=Workspace /workspace/logon/*=Workspace /workspace/jobmanager/*=Workspace
108 Configuring a Web Server with Apache Tomcat /workspace/conf/*=Workspace
/hr=Financial_Reporting /hr/*=Financial_Reporting
/WebAnalysis/=Web_Analysis /WebAnalysis/*.jar=Web_Analysis /WebAnalysis/*.exe=Web_Analysis /WebAnalysis/*.jsp=Web_Analysis /WebAnalysis/*.xml=Web_Analysis /WebAnalysis/templates/*=Web_Analysis /WebAnalysis/wa_javadocs/*=Web_Analysis /WebAnalysis/ServerConsole/*=Web_Analysis /WebAnalysis/config=Web_Analysis /WebAnalysis/resources/*=Web_Analysis /WebAnalysis/portlettemplates/*=Web_Analysis /WebAnalysis/hfmtemplates/*=Web_Analysis /WebAnalysis/modules/*=Web_Analysis /WebAnalysis/hitemplates/*=Web_Analysis /WebAnalysis/servlet/*=Web_Analysis /WebAnalysis/Config=Web_Analysis /WebAnalysis/processor=Web_Analysis /WebAnalysis/DirectoryServlet=Web_Analysis
Create a Virtual Directory for the Tomcat HTTP Plug-in
➤ To create a virtual directory of the Tomcat HTTP plug-in: 1 Open the Windows Control Panel. 2 Open Administrative Tools. 3 Open Internet Information Services (IIS) Manager. 4 Expand your local computer’s Web sites until Default Web Site is visible. 5 Right-click Default Web Site, then select New > Virtual Directory. 6 Click Next, then specify jakarta-tomcat in the Alias text field. 7 Click Next, then browse to the location where you copied the Tomcat HTTP plug-in binary; for example: C:\Inetpub\jakarta-tomcat 8 Click Next, then select Read, Run, Execute from the list of available permissions. 9 Click Next then Finish.
Register the Tomcat HTTP Plug-in as an ISAPI Filter
➤ To register: 1 From the Internet Information Services (IIS) Manager, expand your local computer’s web sites until Default Web Site is visible. 2 Right-click Default Web Site, then select Properties.
Configuring IIS 109 3 Click the ISAPI Filters tab. 4 Click Add. 5 In Filter Name, specify jakarta-tomcat. 6 In Executable, browse to the Tomcat HTTP plug-in binary; for example: C:\Inetpub\jakarta-tomcat\isapi_redirect-1.2.14.dll 7 Optional: If you are configuring IIS on Windows 2003 or later (IIS 6.0), you must register the Tomcat HTTP plug-in as a new Web Service Extension. The following procedure does not apply to Windows 2000 (IIS 5.0): a. From the Internet Information Services (IIS) Manager, right click Web Service Extensions and select Add a new Web service extension. b. In the Extension name text field, specify jakarta-tomcat. c. Click Add to add a Required File. d. Browse to the Tomcat HTTP plug-in binary; for example: C:\Inetpub\jakarta-tomcat\isapi_redirect-1.2.14.dll e. Enable the Set extension status to Allowed check box, then click OK.
Create Virtual Directory Aliases for Workspace and Web Analysis While not required, it is highly recommended that IIS be configured to serve static content for Workspace and Web Analysis. Doing so will improve performance.
➤ To create virtual directory aliases: 1 Open Internet Information Services (IIS) Manager, then expand your local computer’s web sites until Default Web Site is visible. 2 Right-click Default Web Site, then select New > Virtual Directory. 3 Click Next, then specify workspace in Alias. 4 Click Next, then browse to the location where you copied the workspace_static folder; for example: C:\Inetpub\workspace_static. 5 Click Next, then select Read from the list of available permissions. 6 Click Next then Finish. 7 Repeat this process to create three more Virtual Directories, substituting these values for Alias and location: InsightInstaller ...\workspace_static\zeroadmin\component\Insight wsmedia ...\workspace_static\wsmedia WebAnalysis ...\WebAnalysis_static
110 Configuring a Web Server with Apache Tomcat Restart IIS and Test the Tomcat HTTP Plug-in Restart IIS, then test the plug-in by accessing once or more of the URLs below, depending on which modules you have deployed: Workspace: http://
Configuring IIS 111 112 Configuring a Web Server with Apache Tomcat Manually Deploying into Oracle 9 10g Release 3 (10.1.3.1.0) Application Server
In This Chapter Prerequisites...... 113 Deploying Workspace Web Application...... 114 Deploying Financial Reporting...... 119 Deploying Web Analysis...... 122 Configuring Oracle HTTP Server for Oracle 10g Release 3 ...... 125 Configuring Oracle Single Sign-on on Oracle 10g Release 3...... 127 Testing Module Availability...... 131 Post Configuration Tasks...... 132
Prerequisites
● Shared Services
❍ Install Shared Services
❍ Verify that it is up and running.
❍ Test the installation and make sure they 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 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: Enterprise Manager Web Console of Oracle Application Server will be used for deployment. Be sure to check “Configure this as an Administrator OC4J instance” check box during OAS installation – otherwise the Enterprise Manager Web Console will be unavailable.
Prerequisites 113 Deploying Workspace Web Application
Creating an OC4J Instance To prevent the Web application being deployed from inheriting unwanted runtime settings, you must create and use a new OC4J instance. Deploying more than one Web application to the same OC4J instance may yield unsuccessful results. Workspace does not require modifications to Oracle HTTP Server listen port(s). However, if you wish to modify these ports, it is recommended that you do so before continuing. Refer to the appropriate Oracle® Application Server guide for details on changing port numbers.
➤ To create an OC4J instance called Workspace, follow the instructions in the Oracle® Containers for J2EE Configuration and Administration Guide.
Note: OC4J group administrative settings such as environment variables are shared by all group members. The OC4J instance you create for the Web application being deployed should be assigned to a group created specifically for that application. (When an application is deployed to more than one OC4J instance, those instances can be assigned to the same group.) For example, when deploying Shared Services and Workspace, the OC4J instance created for Shared Services should be assigned to a different group than the instance created for Workspace. Refer to the Oracle® Process Manager and Notification Server Administrator's Guide for more information about groups.
Configuring the Workspace OC4J Instance
➤ To configure the Workspace OC4J instance: 1 Log on to Oracle® Enterprise Manager 10g Application Server Control. 2 Start the Workspace OC4J instance if it is not running. 3 From the Cluster Topology page in Application Server Control Console, navigate to Application Server:instance name. 4 Click the Workspace OC4J instance link, then the Administration link, and finally the Server Properties link. 5 Under Command Line Options, 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. 6 Add a row for the following Java Option: -DHYPERION_HOME=
114 Manually Deploying into Oracle 10g Release 3 (10.1.3.1.0) Application Server where
Deploying workspace.war
➤ To deploy: 1 Navigate to the Workspace > Applications page of the Oracle Enterprise Manager’s 10g Web console. 2 Click Deploy. 3 Supply the absolute location to workspace.war to Archive Location:by selecting one of the following:
● Archive is present on the local machine...
● Archive is on the same machine... and entering:
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. 4 Click Next to create a new deployment plan. 5 In Application Name, type Workspace. 6 Click Next. 7 Click Deploy. 8 After successful deployment, click Return. 9 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.
Deploying Workspace Web Application 115 ➤ To add SAP to Workspace OC4J environment: 1 With a text editor, open:
where
where
Creating context.properties
➤ To create context.properties: 1 With a text editor, create:
Where
Note: Keep HPSU and ChangeMangement as Y. b. Assign an appropriate Y or N to each value in accordance with the Reporting and Analysis modules you have installed:
116 Manually Deploying into Oracle 10g Release 3 (10.1.3.1.0) Application Server ● Financial Reporting (Reports)
● Web Analysis (Analyzer)
● Planning (HP)
● Performance Management Architect (BPMA)—Used with Financial Management or Planning
● Financial Management (HFM)
● Performance Scorecard (HPS) 3 Click Start or Restart Workspace OC4J instance.
Modifying portlet.xml
➤ To modify portlet.xml to support portlets: 1 With a text editor, open:
where
Preference Change value to:
pr_wsrp_producer_url http://
ir_wsrp_producer_url http://
fr_wsrp_producer_url http://
wa_wsrp_producer_url http://
workspace_url
● Apache—19000 ● IBM HTTP Server—19000 ● Oracle HTTP Server—19000 ● IIS—80
foundation_port
Deploying Workspace Web Application 117 Preference Change value to:
● Apache—19000 ● IBM HTTP Server—19000 ● Oracle HTTP Server—19000 ● IIS—80
foundation_host
3 Start or restart the Workspace OC4J instance.
Update Oracle HTTP Server Routing for Workspace You need to update the Oracle HTTP Server (OHS) to make static content and online Help, available.
➤ To update OHS Routing for Workspace: 1 Open:
Where
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: c:\Hyperion b. In the line: DEPLOYMENT_PATH=$J(servletConfig.deploymentPath)
replace $J(servletConfig.deploymentPath) with the actual location of deployed Workspace
118 Manually Deploying into Oracle 10g Release 3 (10.1.3.1.0) Application Server The default is:
Where
a. In the line: HYPERION_HOME=$J(HYPERION_HOME)
replace $J(HYPERION_HOME) with your actual HYPERION_HOME location. For example: c:\Hyperion b. In the line: BRIO_LIB=$J(trustedPass.installLib)
replace $J(trustedPass.installLib) with your actual
replace $J(trustedPass.deploymentHome) with the actual location of deployed Workspace application. The default is:
Where
Deploying Financial Reporting
Creating an OC4J Instance To prevent the Web application being deployed from inheriting unwanted runtime settings, you must create and use a new OC4J instance. Deploying more than one Web application to the same OC4J instance may yield unsuccessful results. Financial Reporting does not require modifications to Oracle HTTP Server listen port(s). However, if you wish to modify these ports, it is recommended that you do so before continuing. Refer to the appropriate Oracle® Application Server guide for details on changing port numbers.
Deploying Financial Reporting 119 ➤ To create an OC4J instance called FinancialReporting, follow the instructions in the Oracle® Containers for J2EE Configuration and Administration Guide.
Note: OC4J group administrative settings such as environment variables are shared by all group members. The OC4J instance you create for the Web application being deployed should be assigned to a group created specifically for that application. (When an application is deployed to more than one OC4J instance, those instances can be assigned to the same group.) For example, when deploying Shared Services and Workspace, the OC4J instance created for Shared Services should be assigned to a different group than the instance created for Workspace. Refer to the Oracle® Process Manager and Notification Server Administrator's Guide for more information about groups.
Configuring the FinancialReporting OC4J Instance
➤ To configure the FinancialReporting OC4J instance: 1 Log on to Oracle® Enterprise Manager 10g Application Server Control. 2 Start the FinancialReporting OC4J instance if it is not running. 3 From the Cluster Topology page in Application Server Control Console, navigate to Application Server:FinancialReporting. 4 In Server Properties, 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. 5 Remove the -Djava.awt.headless=true property in two places: 1.Options 2.Stop-parameters:Java Options 6 Under Options, add the following properties, substituting values in <> with actual locations: -DHYPERION_HOME=
for example: -DHYPERION_HOME=C:\Hyperion -DBIPLUS_HOME=C:\Hyperion\BIPlus -DADM_HP_LIB=C:\Hyperion\ADM\Planning\9.3.1\lib
120 Manually Deploying into Oracle 10g Release 3 (10.1.3.1.0) Application Server Note: Define -DADM_HP_LIB entries, even if Planning is absent in your environment; for example: - DADM_HP_LIB= 7 If Oracle Application Server is running on Windows, Linux, Solaris, or HP-UX, add the following Java options: -XX:PermSize=64m -XX:MaxPermSize=128m 8 If Oracle Application Server is running on Solaris 10 for SPARC, add the following Java option, as in Metalink 431167.1: -Djava.nio.channels.spi.SelectorProvider=sun.nio.ch.PollSelectorProvider 9 Under Environment Variables, add the following, substituting values in <> with actual locations: HYPERION_HOME
for example: HYPERION_HOME C:\Hyperion ESSLANG English_UnitedStates.Latin1@Binary BIPLUS_HOME C:\Hyperion\BIPlus ARBORPATH C:\Hyperion\common\EssbaseRTC\9.3.1 ESS_ES_HOME C:\Hyperion\BIPlus\bin\EssbaseJAPI PATH C:\Hyperion\common\ADM\Planning\9.3.1\bin;C:\Hyperion\common\ADM\9. 3.1\Essbase\9.3.1\bin;C:\Hyperion\common\ADM\9.3.1\ODBO\9.3.1;C:\Hyperion \common\EssbaseRTC\9.3.1\bin;C:\Hyperion\common\SAP\bin;C:\Hyperion \FinancialManagement\Common;C:\Hyperion\FinancialManagement\Server;C: \Hyperion\FinancialManagement\Client 10 Click Apply. 11 Restart the FinancialReporting OC4J instance.
Deploying HReports.ear
➤ To deploy HReports.ear: 1 Navigate to the OC4J > FinancialReporting > Applications page of the Oracle Enterprise Manager's 10g Web Console. 2 Click Deploy. 3 Supply the absolute location to HReports.ear to Archive Location:
by default, keep the Archive type in J2EE Application. For example:
Deploying Financial Reporting 121 c:\Hyperion\BIPlus\InstallableApps\HReports.ear
Note: If the Web browser used to deploy the HReports.ear archive is not on the same machine where Reporting and Analysis was installed, you must use copy Location on Server. 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
Creating an OC4J Instance To prevent the Web application being deployed from inheriting unwanted runtime settings, you must create and use a new OC4J instance. Deploying more than one Web application to the same OC4J instance may yield unsuccessful results. Web Analysis does not require modifications to Oracle HTTP Server listen port(s). However, if you wish to modify these ports, it is recommended that you do so before continuing. Refer to the appropriate Oracle® Application Server guide for details on changing port numbers.
➤ To create an OC4J instance called WebAnalysis, follow the instructions in the Oracle® Containers for J2EE Configuration and Administration Guide.
Note: OC4J group administrative settings such as environment variables are shared by all group members. The OC4J instance you create for the Web application being deployed should be assigned to a group created specifically for that application. (When an application is deployed to more than one OC4J instance, those instances can be assigned to the same group.) For example, when deploying Shared Services and Workspace, the OC4J instance created for Shared Services should be assigned to a different group than the instance created for Workspace. Refer to the Oracle® Process Manager and Notification Server Administrator's Guide for more information about groups.
Configuring the WebAnalysis OC4J Instance
➤ To configure the WebAnalyis OC4J instance: 1 Log on to Oracle® Enterprise Manager 10g Application Server Control. 2 Start the WebAnalysis OC4J instance if it is not running.
122 Manually Deploying into Oracle 10g Release 3 (10.1.3.1.0) Application Server 3 From the Cluster Topology page in Application Server Control Console, navigate to Application Server:WebAnalysis. 4 In Server Properties: 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.
In Server Properties, remove the -Djava.awt.headless=true property in two places: 1. Options 2. Stop-parameters:Java Options 5 In Server Properties, add the following Java Option: -Ddeployment.mode=true
Note: The additional JVM argument (-Ddeployment.mode=true) is required at the first deployment time only and should be removed after successful application deployment. 6 Under Options, add the following properties, substituting values in <> with actual locations: -DHYPERION_HOME=
for example: -DHYPERION_HOME=C\Hyperion -DBIPLUS_HOME=C:\Hyperion\BIPlus 7 If Oracle Application Server is running on Windows, Linux, Solaris, or HP-UX, add the following Java options: -XX:PermSize=64m -XX:MaxPermSize=128m 8 If Oracle Application Server is running on Solaris 10 for SPARC, add the following Java option, as in Metalink 431167.1: -Djava.nio.channels.spi.SelectorProvider=sun.nio.ch.PollSelectorProvider 9 Under Environment Variables, add the following, substituting <> with actual locations: ESSLANG English_UnitedStates.Latin1@Binary HYPERION_HOME
Deploying Web Analysis 123 where
Deploying WebAnalysis.ear
➤ To deploy WebAnalysis.ear: 1 Navigate to the OC4J > WebAnalysis > Applications page of the Oracle Enterprise Manager’s 10g Web console. 2 Click Deploy. 3 Supply the absolute location to WebAnalysis.ear to Archive Location:
by default, in J2EE Application.
Note: If the Web browser used to deploy the WebAnalysis.ear archive is not on the same machine where Reporting and Analysis was installed, you must use copy Location on Server. 4 Click Next to create a new deployment plan. 5 In Application Name, type WebAnalysis and click Next. 6 Click Deploy. 7 For Web Analysis Drill-through feature, add the JDBC drivers to the following directory for any database which can be used as a target for relational drill-through:
Examples of JDBC drivers:
● DB2: db2java.zip, db2jcc.jar, db2jcc_license_cisuz.jar, db2jcc_license_cu.jar
● MS SQL: msbase.jar, mssqlserver.jar, msutil.jar
● Oracle: ojdbc14.jar 8 Remove the deployment mode option:
124 Manually Deploying into Oracle 10g Release 3 (10.1.3.1.0) Application Server a. Navigate to WebAnalysis: > Administration page of the Oracle Enterprise Manager 10g Web site. b. Select Server Properties. c. In Server Properties, under Options, remove following argument: -Ddeployment.mode=true 9 Click Apply. 10 The WebAnlysis OC4J instance must be restarted, but you should do so only after completing the Oracle HTTP Server configuration for Workspace steps. See “Configuring Oracle HTTP Server for Oracle 10g Release 3” on page 125.
Note: If the WebAnlysis OC4J instance is restarted before the Oracle HTTP Server configuration for Workspace, starting Web Analysis may take several minutes.
Configuring Oracle HTTP Server for Oracle 10g Release 3
● “Configuring Reporting and Analysis” on page 125
● “Configuring Financial Management” on page 127
Configuring Reporting and Analysis
➤ To properly route requests from Oracle HTTP Server to the OC4J instances created for Reporting and Analysis: 1 If browser clients using short hostname or hostname aliases will access your product, consider changing the value of UseCanonicalName to Off in httpd.conf. For example, if you log on using a URL like: http://
Oracle HTTP Server, by default, changes the URL to http://
which will cause JavaScript errors. For more information on UseCanonicalName, see: http://httpd.apache.org/docs/2.0/mod/core.html#usecanonicalname. 2 Edit
Configuring Oracle HTTP Server for Oracle 10g Release 3 125 "
Alias /WebAnalysis "
and create the following Oc4jMount directives for each Reporting and Analysis module you have deployed, where Workspace, FinancialReporting and WebAnalysis matches the name(case sensitive) of the OC4J Container where you deployed the application: 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 Oc4jMount /hr FinancialReporting Oc4jMount /hr/* FinancialReporting Oc4jMount /HReports FinancialReporting Oc4jMount /HReports/* FinancialReporting Oc4jMount /WebAnalysis/ServerConsole/* WebAnalysis Oc4jMount /WebAnalysis/templates/* WebAnalysis Oc4jMount /WebAnalysis/hfmtemplates/* WebAnalysis Oc4jMount /WebAnalysis/hitemplates/* WebAnalysis Oc4jMount /WebAnalysis/processor WebAnalysis Oc4jMount /WebAnalysis/servlet/* WebAnalysis 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 4 Restart the Oracle HTTP Server using opmnctl:
126 Manually Deploying into Oracle 10g Release 3 (10.1.3.1.0) Application Server
Configuring Financial Management
➤ To route requests through Oracle HTTP Server to the Web server used by Financial Management: 1 With a text editor, create or update:
so that it contains:
where
and add the line: Include conf\hfm.conf
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.bat
Configuring Oracle Single Sign-on on Oracle 10g Release 3 127 For example: %ORACLE_HOME%\sso\bin\ssoreg.bat -oracle_home_path %ORACLE_HOME% - config_mod_osso TRUE -site_name BIPlus -remote_midtier -config_file % ORACLE_HOME%\Apache\Apache\conf\osso\myosso.conf -mod_osso_url http:// myhost.domain.com:19000 3 Copy the obfuscated OSSO configuration file to the 10g Release 3 (10.1.3) middle-tier instance. 4 On the middle-tier host, run one of the following script to complete the registration:
● If you have Perl: ORACLE_HOME\Apache\Apache\bin\osso1013 config_file
● If you do not have Perl: a. Copy config_file into ORACLE_HOME\Apache\Apache\conf\osso\osso.conf b. Uncomment the following line in httpd.conf: include '
For example: OssoConfigFile 'C:\Oracle\Apache\Apache\conf\osso\osso.conf' 5 Update Identity Management properties for Workspace: a. Navigate to the OC4J > Workspace > Administration page of the Oracle Enterprise Manager’s 10g Web site. b. Select Identity Management Properties, and click Configure. c. Enter:
● User: Fully qualified domain name of the OID host, cn=orcladmin
● Password: User password
● Port: Port value, by default: non-SSL 389. Click Next. 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:
128 Manually Deploying into Oracle 10g Release 3 (10.1.3.1.0) Application Server 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, 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 Authenticationand click OK. 9 Update: ORACLE_HOME\Apache\Apache\conf\mod_osso.conf
and insert the following lines into
Configuring Oracle Single Sign-on on Oracle 10g Release 3 129
as follows: a. Uncomment and set UseSecurityAgentTokenWithoutDomain to true. b. Update SSOProviderSessionCookieID and set value: OHS-
● Property Custom username policy to $REMOTE_USER$
● Custom password policy to $TRUSTEDPASS$ then click File->Save and File->Exit. 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:
130 Manually Deploying into Oracle 10g Release 3 (10.1.3.1.0) Application Server 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. 2 Navigate to Administration->Configure User Directories. 3 Select Support Security Agent for Single Sign-on. 4 Click Save. 5 Select Requisite Provider (Oracle Internet Directory) and click Edit. 6 Select Trusted. 7 Click Save. 8 Restart all components.
Testing Module Availability For each of the products used, verify the setup by using the URLs below. If you have changed the web server configuration, restart the web server before running these tests.
Product URL* Expected Result
Workspace http://
Financial Reporting http://
Web Analysis http://
Performance Management Architect http://
Testing Module Availability 131 Product URL* Expected Result
Financial Management http://
Planning http://
*URL: Where
Post Configuration Tasks To finish the configuration, see “Post Configuration Tasks” on page 66.
132 Manually Deploying into Oracle 10g Release 3 (10.1.3.1.0) Application Server Manually Deploying into Oracle 10 10g Release 2 (10.1.2.0.2) Application Server
In This Chapter Prerequisites...... 133 Deploying Workspace Web Application...... 134 Deploying Financial Reporting...... 139 Deploying Web Analysis...... 143 Configuring Oracle HTTP Server for Oracle 10g Release 2 ...... 146 Configuring Oracle Single Sign-On on Oracle 10g Release 2...... 149 Testing Module Availability...... 152 Post Configuration Tasks...... 153
Prerequisites
● Shared Services
❍ Install Shared Services
❍ Verify that it is up and running.
❍ Test the installation and make sure they 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 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: The Hyperion Configuration Utility will install and start the Hyperion Apache Web Server automatically. If the Oracle HTTP Server will be used, you may safely stop, disable, or remove the Hyperion Apache Web Server instance.
Prerequisites 133 Deploying Workspace Web Application
Creating an OC4J Instance To prevent the Web application being deployed from inheriting unwanted runtime settings, you must create and use a new OC4J instance. Deploying more than one Web application to the same OC4J instance may yield unsuccessful results. Workspace does not require modifications to Oracle HTTP Server listen port(s). However, if you wish to modify these ports, it is recommended that you do so before continuing. Refer to the appropriate Oracle® Application Server guide for details on changing port numbers.
➤ 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 ias_admin. The password is specified during the Oracle 10g Application Server installation. Contact your Oracle Administrator for more information. 2 On the home page for the Oracle Application Server Enterprise Manager, under System Components, click Create OC4J Instance. 3 In the Create OC4J Instance Page, in OC4J Instance, type Workspace, then click Create.
Configuring an OC4J Instance The size of the OC4J instance heap must be increased in order to successfully deploy the Workspace application, and the default deployment directory must be changed.
➤ To configure OC4J instance properties: 1 Navigate to OC4J > Workspace: > Administration page of the Oracle Enterprise Manager’s 10g Web site and select Server Properties. 2 Optional: In Server Properties, under General, provide the following paths for Application Directory and Deployment Directory:
where
134 Manually Deploying into Oracle 10g Release 2 (10.1.2.0.2) Application Server The Application Directory and Deployment Directory values above are not mandatory. You may safely substitute with values of your own choosing, or leave the default values.
Note: If changed from the default, you must manually create the directories before deploying the application, and the Oracle Application server owner must have write access to them.
Note: Oracle on Windows requires that back-slash (\) delimiter be used for these two fields. 3 In Server Properties, under Command Line Options, append Java Options by arguments: -Xms256m -Xmx512m -DHYPERION_HOME=
where
Deploying workspace.war There are two ways to deploy web-application to Oracle 10g Application Server: 1. “Using Oracle Enterprise Manager” on page 135—This method is more user-friendly, but requires web-application to be copied to host running browser. 2. “Using Oracle Distributed Configuration Management Command Line Utility” on page 136—This method does not require a browser or copy web-application across network.
Using Oracle Enterprise Manager
➤ To deploy workspace.war using Oracle Enterprise Manager: 1 Copy
Deploying Workspace Web Application 135 Using Oracle Distributed Configuration Management Command Line Utility The Oracle Distributed Configuration Management command line utility, dcmctl, may be used to deploy workspace.war. The dcmctl tool uses the same distributed architecture and synchronization features as Enterprise Manager Web console. To use dcmctl, you must log in to your operating system as the user that installed Oracle 10g Application Server. The dcmctl utility supports single word, non case-sensitive commands.
➤ To deploy workspace.war: 1 Execute dmctl with the following arguments: deployApplication -f
where
Note: Arguments are case-sensitive. Enter them exactly as documented. 2 After successful deployment, start the Workspace OC4J instance.
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:
136 Manually Deploying into Oracle 10g Release 2 (10.1.2.0.2) Application Server where
where
Creating context.properties
➤ To create context.properties: 1 With a text editor, create:
Note: Leave HPSU and ChangeMangement as Y. b. Assign an appropriate Y or N to each value in accordance with the Reporting and Analysis modules you have installed:
● Financial Reporting (Reports)
● Web Analysis (Analyzer)
● Planning (HP)
● Performance Management Architect (BPMA)—Used with Financial Management or Planning
Deploying Workspace Web Application 137 ● Financial Management (HFM)
● Performance Scorecard (HPS) 3 Start or restart the Workspace OC4J instance.
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. b. In the line: DEPLOYMENT_PATH=$J(servletConfig.deploymentPath)
replace $J(servletConfig.deploymentPath) with the actual location of deployed Workspace application. The default is:
a. In the line: HYPERION_HOME=$J(HYPERION_HOME)
replace $J(HYPERION_HOME) with your actual HYPERION_HOME location. b. In the line: BRIO_LIB=$J(trustedPass.installLib)
replace $J(trustedPass.installLib) with your actual
replace =$J(trustedPass.deploymentHome) with the actual location of deployed Workspace application. The default is:
138 Manually Deploying into Oracle 10g Release 2 (10.1.2.0.2) Application Server Modifying portlet.xml
➤ To modify portlet.xml to support portlets: 1 With a text editor, open:
Preference Change value to:
pr_wsrp_producer_url http://
ir_wsrp_producer_url http://
fr_wsrp_producer_url http://
wa_wsrp_producer_url http://
workspace_url
foundation_port
foundation_host
3 Start or restart the Workspace OC4J instance.
Deploying Financial Reporting
Creating an OC4J Instance To prevent the Web application being deployed from inheriting unwanted runtime settings, you must create and use a new OC4J instance. Deploying more than one Web application to the same OC4J instance may yield unsuccessful results.
Deploying Financial Reporting 139 Financial Reporting does not require modifications to Oracle HTTP Server listen port(s). However, if you wish to modify these ports, it is recommended that you do so before continuing. Refer to the appropriate Oracle® Application Server guide for details on changing port numbers.
➤ 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 ias_admin. The password is specified during the Oracle 10g Application Server installation. Contact your Oracle Administrator for more information. 2 Click Create OC4J Instance. 3 In the Create OC4J Instance Page, type FinancialReporting in the OC4J Instance name field, then click Create.
Configuring a FinancialReporting OC4J Instance The size of the OC4J instance heap must be increased in order to successfully deploy the Financial Reporting application, and the default deployment directory must be changed.
➤ To configure OC4J instance properties: 1 Navigate to OC4J > Financial Reporting:> Administration page of the Oracle Enterprise Manager’s 10g Web site and drill down to Server Properties. 2 Optional: In Server Properties, under General, provide the following values for Application Directory and Deployment Directory:
where
Note: If changed from the default, you must manually create the directories before deploying the application, and the Oracle Application server owner must have write access to them.
140 Manually Deploying into Oracle 10g Release 2 (10.1.2.0.2) Application Server Note: Oracle on Windows requires that back-slash (\) delimiter be used for these two fields. 3 In Server Properties, under Command Line Options , append the following Java Options, substituting values in <> with actual locations: -DHYPERION_HOME=
for example: -DHYPERION_HOME=C\Hyperion -DBIPLUS_HOME=C:\Hyperion\BIPlus -DADM_HP_LIB=C:\Hyperion\ADM\Planning\9.3.1\lib -Xms256m -Xmx512m
Note: Define -DADM_HP_LIB entries, even if Planning is absent in your environment; for example: - DADM_HP_LIB= 4 If Oracle Application Server is running on Windows, Linux, Solaris, or HP-UX, add the following Java options: -XX:PermSize=64m -XX:MaxPermSize=128m 5 If Oracle Application Server is running on Solaris 10 for SPARC, add the following Java option, as in Metalink 431167.1: -Djava.nio.channels.spi.SelectorProvider=sun.nio.ch.PollSelectorProvider 6 In the same field, remove the -Djava.awt.headless=true property. 7 Under Environment Variables, ad the following, substituting values in <> with actual locations: HYPERION_HOME
for example: HYPERION_HOME C:\Hyperion ESSLANG English_UnitedStates.Latin1@Binary BIPLUS_HOME C:\Hyperion\BIPlus ARBORPATH C:\Hyperion\common\EssbaseRTC\9.3.1 ESS_ES_HOME C:\Hyperion\BIPlus\bin\EssbaseJAPI 8 Click Apply. 9 Click OK.
Deploying Financial Reporting 141 Deploying HReports.ear There are two ways to deploy web-application to Oracle 10g Application Server: 1. “Using Oracle Enterprise Manager” on page 142—This method is more user-friendly, but requires web-application to be copied to host running browser 2. “Using Oracle Distributed Configuration Management Command Line Utility” on page 142—This method does not require to use browser or copy web-application across network
Using Oracle Enterprise Manager In order to deploy Financial Reporting web-application you must copy
to browser client host.
➤ To deploy HReports.ear: 1 Navigate to the OC4J > FinancialReporting > Applications >Deploy EAR file in Oracle Enterprise Manager. 2 Enter HReports.ear file path toJ2EE Application. 3 Enter “FinancialReporting” as Application Name and click Continue. 4 Leave all fields on URL Mapping for Web Modules with their default values, click Finish and Deploy 5 After deployment process done hit OK. 6 Start FinancialReporting application server instance.
Using Oracle Distributed Configuration Management Command Line Utility In order to avoid copying HReports.ear file across the networks, the Oracle Distributed Configuration Management command line utility, dcmctl, may be used to deploy HReports.ear. The dcmctl tool uses the same distributed architecture and synchronization features as Enterprise Manager Web console. To use dcmctl, you must log in to your operating system as the user that installed Oracle 10g Application Server. The dcmctl utility supports single word, non case-sensitive commands. To deploy HReports.ear execute dmctl with the following arguments: deployApplication -f
where
For example:
142 Manually Deploying into Oracle 10g Release 2 (10.1.2.0.2) Application Server
Note: Arguments are case-sensitive. Enter them exactly as documented.
Start FinancialReporting application server instance.
Deploying Web Analysis
Creating an OC4J Instance To prevent the Web application being deployed from inheriting unwanted runtime settings, you must create and use a new OC4J instance. Deploying more than one Web application to the same OC4J instance may yield unsuccessful results. Web Analysis does not require modifications to Oracle HTTP Server listen port(s). However, if you wish to modify these ports, it is recommended that you do so before continuing. Refer to the appropriate Oracle® Application Server guide for details on changing port numbers.
➤ 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 ias_admin. The password is specified during the Oracle 10g Application Server installation. Contact your Oracle Administrator for more information. 2 On the home page for the Oracle Application Server Enterprise Manager, under System Components, click Create OC4J Instance. 3 In the Create OC4J Instance Page, type WebAnalysis in the OC4J Instance name field. 4 Click Create.
Note: Creation of the OC4J instance may take a while to complete, depending on the configuration of Application Server.
Deploying Web Analysis 143 Configuring the WebAnalysis OC4J Instance The size of the OC4J instance heap must be increased in order to successfully deploy the Web Analysis application, and the default deployment directory must be changed.
➤ To configure OC4J instance properties: 1 Navigate to OC4J > WebAnalysis: > Administration page of the Oracle Enterprise Manager’s 10g Web site and drill down to Server Properties. 2 Optional: In Server Properties, under General, provide the following values for Application Directory and Deployment Directory:
where
Note: If changed from the default, you must manually create the directories before deploying the application, and the Oracle Application server owner must have write access to them.
Note: Oracle on Windows requires that back-slash (\) delimiter be used for these two fields. 3 In Server Properties, under Command Line Options, append Java Options by arguments: -Xms256m -Xmx512m -DHYPERION_HOME=
Note: The additional JVM argument -Ddeployment.mode=true is required at the first deployment time only and should be removed after successful application deployment. 4 If you’re running Hyperion products in 64 bit mode you must also add -d64 argument to the beginning of Command Line Options field. 5 In the same field, remove the -Djava.awt.headless=true property. 6 Click Apply. 7 Click OK.
Environment Variables The Hyperion Configuration Utility prepares the JVM environment with the necessary environment variables for WebAnalysis to function correctly. Reporting and Analysis creates WebAnalysis.env which sets required environment variables at runtime. The file is located in:
144 Manually Deploying into Oracle 10g Release 2 (10.1.2.0.2) Application Server
Deploying WebAnalysis.ear There are two ways to deploy web-application to Oracle 10g Application Server: 1. “Using Oracle Enterprise Manager” on page 145—This method is more user-friendly, but requires web-application to be copied to host running browser. 2. “Using Oracle Distributed Configuration Management Command Line Utility” on page 145—This method does not require a browser or copy web-application across network.
Using Oracle Enterprise Manager
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 copy WebAnalysis.ear locally.
➤ To deploy WebAnalysis.ear: 1 Navigate to the OC4J > WebAnalysis > Applications Deploy EAR file in Oracle Enterprise Manager. 2 Enter WebAnalysis.ear file path to J2EE Application. 3 Enter “WebAnalysis” as Application Name and click Continue. 4 Leave all fields on URL Mapping for Web Modules with their default values, click Finish and Deploy. 5 After deployment process done hit OK.
Using Oracle Distributed Configuration Management Command Line Utility In order to avoid copying WebAnalysis.ear file across the networks, the Oracle Distributed Configuration Management command line utility, dcmctl, may be used to deploy WebAnalysis.ear. The dcmctl tool uses the same distributed architecture and synchronization features as Enterprise Manager Web console. To use dcmctl, you must log in to your operating system as the user that installed Oracle 10g Application Server. The dcmctl utility supports single word, non case-sensitive commands. To deploy WebAnalysis.ear execute dmctl with the following arguments: deployApplication -f
where
Deploying Web Analysis 145 For example:
Note: Arguments are case-sensitive. Enter them exactly as documented.
Configuring Oracle HTTP Server for Oracle 10g Release 2
● “Configuring Reporting and Analysis” on page 146
● “Configuring Performance Management Architect or Planning” on page 147
● ???
● “Defining Additional Parameters for Workspace” on page 148
Configuring Reporting and Analysis
➤ To configure Oracle HTTP Server for Reporting and Analysis modules: 1 Open:
Note: The last parameter of the Oc4jMount directive should correspond to the name of the OC4J Instance in Oracle Enterprise Manager.
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
146 Manually Deploying into Oracle 10g Release 2 (10.1.2.0.2) Application Server Oc4jMount /workspace/ Workspace Oc4jMount /workspace/*.jsp Workspace Oc4jMount /workspace/*.jsv Workspace Oc4jMount /workspace/*.jsw Workspace Oc4jMount /hr FinancialReporting Oc4jMount /hr/* FinancialReporting Oc4jMount /HReports FinancialReporting Oc4jMount /HReports/* FinancialReporting Oc4jMount /WebAnalysis/ServerConsole/* WebAnalysis Oc4jMount /WebAnalysis/templates/* WebAnalysis Oc4jMount /WebAnalysis/hfmtemplates/* WebAnalysis Oc4jMount /WebAnalysis/hitemplates/* WebAnalysis Oc4jMount /WebAnalysis/processor WebAnalysis Oc4jMount /WebAnalysis/servlet/* WebAnalysis 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
Configuring Performance Management Architect or Planning
➤ To configure Performance Management Architect or Planning, open mod_oc4j.conf and create the Oc4jMount directives:
● If Planning or Performance Management Architect is running on a the same machine as the Oracle HTTP Server:
Note: The last parameter of the Oc4jMount directive should correspond to the name of the OC4J Instance in Oracle Enterprise Manager.
Performance Management Architect Oc4jMount /awb/ BPMA Oc4jMount /awb/* BPMA
Planning Oc4jMount /HyperionPlanning/ Planning Oc4jMount /HyperionPlanning/* Planning
● If Planning or Performance Management Architect is running on a different machine than the Oracle HTTP Server, you need to change the directive. See section 8.32 of the Oracle® HTTP Server Administrator's Guide for 10g Release 2 (10.1.2). For example, for Planning, the Oc4jMount directives should be:
Configuring Oracle HTTP Server for Oracle 10g Release 2 147 Oc4jMount /HyperionPlanning/* ajp13://
The AJP port is not the HTTP port. To see the AJP port, you need to logon to the Oracle Enterprise Manager console for the application server where Planning is running and click the Ports link.
Configuring Financial Management
➤ To route requests through Oracle HTTP Server to the Web server used by Financial Management: 1 With a text editor, create or update:
so that it contains:
where
and add the line: Include conf\hfm.conf
Defining Additional Parameters for Workspace If Oracle HTTP Server and target OC4J instance are both located on the same computer, you need to define additional parameters for Workspace.
➤ To define additional parameters: 1 Open
148 Manually Deploying into Oracle 10g Release 2 (10.1.2.0.2) Application Server "
WebAnalysis: Alias /WebAnalysis "
If browser clients using short hostname or hostname aliases will access Reporting and Analysis, 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/1.3/mod/core.html#usecanonicalname. 2 Restart the Oracle HTTP Server.
Configuring Oracle Single Sign-On on Oracle 10g Release 2
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: 1 Configure the Identity Management Infrastructure database:
for example:
For validating registration and updating properties, login into the following SSO administration page:http://
Configuring Oracle Single Sign-On on Oracle 10g Release 2 149 Note: Where
Note: When deploying EAR files, you can automatically enable SSO by selecting “Use JAZN LDAP User Manager.” 3 Log into Oracle Console > HTTP Server > Administration > Advanced Server Properties > mod_osso.conf 4 Protect/unprotect specific resources by inserting the following directives into
150 Manually Deploying into Oracle 10g Release 2 (10.1.2.0.2) Application Server OssoSendCacheHeaders off 6 Update:
as follows: a. Uncomment and set UseSecurityAgentTokenWithoutDomain to true. b. Update SSOProviderSessionCookieID and set value: OHS-
then click File->Save and File->Exit. d. Change settrusted password value by running:
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:
Note: User must have Global Administrator role assigned to perform these changes. b. Click Show host properties. c. Click the Authentication tab and set the password. d. Click OK.
Configuring Oracle Single Sign-On on Oracle 10g Release 2 151 Configuring Shared Services
➤ To configure Shared Services: 1 Log on to Shared Services. 2 Navigate to Administration->Configure User Directories. 3 Select Support Security Agent for Single Sign-on. 4 Click Save. 5 Select Requisite Provider (Oracle Internet Directory) and click Edit. 6 Select Trusted. 7 Click Save. 8 Restart all components.
Testing Module Availability For each of the products used, verify the setup by using the URLs below. If you have changed the web server configuration, restart the web server before running these tests.
Product URL* Expected Result
Workspace http://
Financial Reporting http://
Web Analysis http://
Performance Management Architect http://
Financial Management http://
Planning http://
*URL: Where
152 Manually Deploying into Oracle 10g Release 2 (10.1.2.0.2) Application Server If an error message is received, see “Error Messages When Testing Module Availability” on page 65.
Post Configuration Tasks To finish the configuration, see “Post Configuration Tasks” on page 66.
Post Configuration Tasks 153 154 Manually Deploying into Oracle 10g Release 2 (10.1.2.0.2) Application Server Manually Deploying into 11 WebLogic 9.1
In This Chapter Prerequisites...... 155 Preparing the Environment...... 155 Deploying Workspace into WebLogic...... 156 Deploying Financial Reporting into WebLogic...... 159 Deploying Web Analysis into WebLogic...... 160 Configuring a Web Server for WebLogic 9.1...... 161 Testing Module Availability...... 178 Post Configuration Tasks...... 179
Prerequisites
● Shared Services
❍ Install Shared Services
❍ Verify that it is up and running.
❍ Test the installation and make sure they 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.
Preparing the Environment To prevent the Web application being deployed from inheriting unwanted runtime settings, you must create and use a new WebLogic server. Deploying more than one Web application to the same WebLogic server instance may yield unsuccessful results.
Prerequisites 155 Note: Reporting and Analysis can contain up to three Web applications: Workspace (required), Financial Reporting and Web Analysis. You must create a separate Web Logic Server for each of them.
Deploying Workspace into WebLogic
Creating a New Domain
➤ To create a new Workspace:domain: 1 Create a new domain, or use an existing domain 2 Create a new managed server called Workspace, and specify the listen port as 45000. 3 Copy \bin\startWeblogic.cmd to WLS_DOMAIN>\bin\startWorkspace.cmd. 4 Edit startWorkspace.cmd by adding the following to the top of the file, replacing
by adding: set CLASSPATH=%LIB_DIR%\iona63.jar;%LIB_DIR%;%CLASSPATH% set JAVA_OPTIONS=- Djavax.xml.parsers.SAXParserFactory=org.apache.xerces.jaxp.SAXParserFactory Impl %JAVA_OPTIONS% 6 Run startWorkspace.cmd.
Modifying setDomainEnv.cmd
➤ To modify setDomainEnv.cmd: 1 Open:
156 Manually Deploying into WebLogic 9.1 XParserFactory Impl %JAVA_OPTIONS%
Deploying Workspace
➤ To deploy: 1 Using the jar command, extract the contents of:
into
to start the Workspace Managed Server.. 3 Deploy the new Web application modules to the Workspace server: a. From the WebLogic Administration Console, start the Workspace server. b. From the WebLogic Administration Console, select Deployments and deploy/install a new web application module. c. Select the path to the interop folder (/servers/Workspace/ webapps). d. In the subsequent installation screens, select the following options:
● Install this deployment as application.
● The target server is Workspace.
● Retain the deployment name as workspace
● Select I will make the deployment accessible from the following location and specify the full path to the workspace folder. e. Save and activate the changes. f. Stop and restart the Workspace server. g. Select Deployments and then workspace web application and click Start -> servicing all requests. Once the status of the application changes to "active", the application is available.
4 Click Activate changes. 5 Start the target server and application. Turn the application state from Prepared to Active. 6 Test Workspace availability: http://
where
Deploying Workspace into WebLogic 157 Modifying portlets.xml
➤ To modify portlets.xml: 1 With a text editor, open:
Preference Change value to
pr_wsrp_producer_url http://
where
ir_wsrp_producer_url http://
where
fr_wsrp_producer_url http://
where
wa_wsrp_producer_url http://
where
workspace_url
where
● Apache—19000 ● IBM HTTP Server—19000 ● IIS—80 ● Oracle HTTP Server—19000
foundation_port
where
● Apache—19000 ● IBM HTTP Server—19000 ● IIS—80 ● Oracle HTTP Server—19000
foundation_host
where
3 Start or restart the Workspace application server.
158 Manually Deploying into WebLogic 9.1 Post Deployment for Workspace
Creating context.properties
➤ To create context.properties: 1 With a text editor, create:
Note: Leave HPSU and ChangeMangement as Y. b. Assign an appropriate Y or N to each value in accordance with the Reporting and Analysis modules you have installed:
● Financial Reporting (Reports)
● Web Analysis (Analyzer)
● Planning (HP)
● Performance Management Architect (BPMA)—Used with Financial Management or Planning
● Financial Management (HFM)
● Performance Scorecard (HPS) 3 Start or restart the Workspace application server.
Deploying Financial Reporting into WebLogic
➤ To deploy the Financial Reporting Web application: 1 Login in to your WebLogic Admin Console WebLogic admin server. 2 Click Deployments. 3 Click the Lock and Edit button. 4 Click Install.
Deploying Financial Reporting into WebLogic 159 5 Click the correct drive and navigate to the newly created enterprise archive file:
where
Deploying Web Analysis into WebLogic This section describes how to deploy Web Analysis into WebLogic.
Verifying Web Analysis Environment Variables The Hyperion Configuration Utility prepares the JVM environment with the necessary environment variables for WebAnalysis to function correctly. Reporting and Analysis creates WebAnalysis.env which sets required environment variables at runtime. The file is located in:
Deploying Web Analysis
➤ To deploy the Web Analysis Web application: 1 Edit the Application Server startup script by adding to the JAVA_OPTIONS environment variable, the following option: -Ddeployment.mode=true
Note: The additional JVM argument -Ddeployment.mode=true is required at first deployment time only and should be removed after successful application deployment. 2 Log on to your WebLogic Admin Console for WebLogic admin server.
160 Manually Deploying into WebLogic 9.1 3 Click Deployments. 4 Click the Lock and Edit. 5 Click Install. 6 Click the correct drive and navigate to the newly created enterprise archive file:
where <
Configuring a Web Server for WebLogic 9.1 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. See “Web Server Use in Hyperion” on page 16.
Configuring Apache HTTP Plug-in
● “Configuring for Reporting and Analysis and Hyperion Applications” on page 162
● “Configuring for Performance Management Architect” on page 169
● “Configuring for Financial Management” on page 169
● “Configuring for Performance Scorecard” on page 170
● “Configuring for Planning” on page 170
Configuring a Web Server for WebLogic 9.1 161 Configuring for Reporting and Analysis and Hyperion Applications 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 Apache Web Server: 1 Use the Apache Web Server installed with Reporting and Analysis, or optionally install Apache Web Server 2.0 and verify that mod_so.c module is enabled by executing:
Note: 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 Plug-in module: a. Copy the mod_wl_20.so file located in:
to the
replacing
162 Manually Deploying into WebLogic 9.1 KeepAliveSecs 20 WeblogicCluster
Configuring a Web Server for WebLogic 9.1 163 WeblogicCluster
164 Manually Deploying into WebLogic 9.1
Configuring a Web Server for WebLogic 9.1 165
166 Manually Deploying into WebLogic 9.1
Configuring a Web Server for WebLogic 9.1 167 SetHandler weblogic-handler PathTrim / KeepAliveEnabled ON KeepAliveSecs 20 WeblogicCluster
and add the lines: Include conf/HYSL-WebLogic.conf Alias /wsmedia "
● “Configuring for Performance Management Architect” on page 169
● “Configuring for Financial Management” on page 169
● “Configuring for Performance Scorecard” on page 170
● “Configuring for Planning” on page 170 5 Test the plug-in by using a URL:
● Financial Reporting—http://
● Web Analysis—http://
● Workspace—http://
168 Manually Deploying into WebLogic 9.1 Configuring for Performance Management Architect
➤ To configure Performance Management Architect with Apache Web Server: 1 See “Configuring for Reporting and Analysis and Hyperion Applications” on page 162, step 1 through 4. 2 Open:
where
Configuring for Financial Management
➤ To configure Financial Management with Apache Web Server: 1 See “Configuring for Reporting and Analysis and Hyperion Applications” on page 162, step 1 through 4. 2 With a text editor, create:
with the following contents, replacing
ProxyRequests On
Configuring a Web Server for WebLogic 9.1 169 ProxyPreserveHost On ProxyPass /hfm http://
where
and add the line: Include conf/hfm.conf 4 Restart the Web server after making changes to this file.
Configuring for Performance Scorecard
➤ To configure Performance Scorecard with Apache Web Server: 1 See “Configuring for Reporting and Analysis and Hyperion Applications” on page 162, step 1 through 4. 2 Open:
where
Configuring for Planning
➤ To configure Planning with Apache Web Server: 1 See “Configuring for Reporting and Analysis and Hyperion Applications” on page 162, step 1 through 4. 2 Open:
170 Manually Deploying into WebLogic 9.1 3 Edit with real values for
where
Configuring Microsoft IIS The Microsoft Internet Information Server (IIS) Plug-in for WebLogic proxies requests from IIS to WebLogic. The web applications that comprise the Application Layer Web Tier of Reporting and Analysis are distributed among more than one WebLogic server instance, which include the Workspace, and one or more of the following Workspace modules:
● Financial Reporting
● Web Analysis
● Performance Management Architect
● Planning
● Performance Scorecard All Hyperion products that are accessed through Performance Management Architect must share the same Web server hostname and port. See “Web Server Use in Hyperion” on page 16. The following procedure describe configuring Microsoft IIS and the IIS plug-in for WebLogic to fulfill this requirement. See “Installing and Configuring the Microsoft IIS Pug-in” section of BEA WebLogic Server documentation for configuration options not covered by this Installation Guide. For WebLogic 8.1: http://e-docs.bea.com/wls/docs81/plugins/isapi.html For WebLogic 9.1: http://e-docs.bea.com/wls/docs91/plugins/isapi.html
Configure Proxying by Path
➤ To configure proxying by path: 1 Create a directory to store the configuration files needed to configure proxying by path; for example:
Configuring a Web Server for WebLogic 9.1 171 C:\Hyperion\WebLogicVHosts 2 Copy
Web Analysis dynamic content forward paths: /WebAnalysis/ServerConsole,/WebAnalysis/templates,/WebAnalysis/ hfmtemplates,/WebAnalysis/hitemplates,/WebAnalysis/portlettemplates,/ WebAnalysis/servlet,/WebAnalysis/modules,/WebAnalysis/resources,/ WebAnalysis/processor,/WebAnalysis/DirectoryServlet,/WebAnalysis/config,/ WebAnalysis/Config,/WebAnalysis/wa_javadocs/*,/WebAnalysis/*.jsp,/ WebAnalysis/*.xml,/WebAnalysis/*.jar,/WebAnalysis/*.exe
iisproxi.ini that include both Workspace and Web Analysis: WlForwardPath=/workspace/cdsrpc,/workspace/administration,/workspace/ browse,/workspace/personalpages,/workspace/viewmanager,/workspace/ jobmanager,/workspace/ihtml,/workspace/dataaccess,/workspace/logon,/ workspace/prefs,/workspace/js,/workspace/modules,/workspace/resources,/ workspace/conf,/workspace/media,/workspace/BPMContext,/workspace/*.jsp,/ workspace/*.jsv,/workspace/*.jsw,/workspace/wsrp4j/*,/workspace/ ResourceProxy,/WebAnalysis/ServerConsole,/WebAnalysis/templates,/ WebAnalysis/hfmtemplates,/WebAnalysis/hitemplates,/WebAnalysis/ portlettemplates,/WebAnalysis/servlet,/WebAnalysis/modules,/WebAnalysis/ resources,/WebAnalysis/processor,/WebAnalysis/DirectoryServlet,/ WebAnalysis/config,/WebAnalysis/Config,/WebAnalysis/wa_javadocs/*,/ WebAnalysis/*.jsp,/WebAnalysis/*.xml,/WebAnalysis/*.jar,/WebAnalysis/*.exe
Register iisforward.dll with IIS You must register iisforward.dll with the IIS website that will be used to proxy request to WebLogic.
➤ To register: 1 Open the Internet Information Service Manager, and expand Web Sites. 2 Right click the Web Site that will be used to proxy requests; for example: Default Web Site. 3 Select Properties from the context menu, and then click the ISAPI Filters tab. 4 Click Add, and enter WLFilter in Filter Name.
172 Manually Deploying into WebLogic 9.1 5 Provide the full path to iisforward.dll; for example: C:\Hyperion\WebLogicVHosts\iisforward.dll 6 Click OK. 7 If you are configuring IIS 6.0 (Windows 2003), do the following: a. Click Web Service Extensions. b. In the right side pane, click Add a new Web service extension. c. In Extension Name, enter WLFilter. d. Add the full path to iisforward.dll to Required Files by clickingAdd; for example: C:\Hyperion\WebLogicVHosts\iisforward.dll e. Check Set extension status to Allowed. f. Click OK.
Configure Proxy by File Extension
Create File-system Directories and Configuration Files A file-system directory must be created for Workspace and each Workspace module for which IIS will act as a proxy.
➤ To create and configure: 1 Create a directory to store the configuration files needed to configure proxying by extension for Workspace; for example: C:\Hyperion\WebLogicVHosts\workspace 2 Repeat this process, creating a directory for each Workspace module you have installed; for example: C:\Hyperion\WebLogicVHosts\WebAnalysis C:\Hyperion\WebLogicVHosts\FinancialReporting C:\Hyperion\WebLogicVHosts\BPMA 3 Copy
If proxying to a WebLogic cluster, substitute WebLogicHost with WebLogicCluster, and do not include WebLogicPort; for example: WebLogicCluster=host1.example.com:
For a full list of supported plug-in parameters, see BEA documentation: For WebLogic 8.1: http://e-docs.bea.com/wls/docs81/plugins/plugin_params.html
Configuring a Web Server for WebLogic 9.1 173 For WebLogic 9.1: http://e-docs.bea.com/wls/docs91/plugins/plugin_params.html Example iisproxy.ini for Workspace: WebLogicHost=somehost.example.com WebLogicPort=45000 KeepAliveEnabled=true KeepAliveSecs=20
Create Application Pools (IIS 6.0) If you are configuring IIS 6.0 (Windows 2003), perform this procedure for each file-system directory you created.
➤ To create application pools: 1 Open the Internet Information Service Manager. 2 Right click on Application Pools. 3 Select New > Application Pool from the context menu . 4 Assign the same name given to your file-system directory in Application pool ID ; for example Workspace. 5 Click OK.
Create IIS Virtual Directories IIS Virtual Directories must be created for Workspace and each Workspace module for which IIS will act as a proxy.
For Workspace
➤ To create IIS virtual directories for Workspace: 1 Open the Internet Information Service Manager, and expand Web Sites. 2 Right click the Web Site that will be used to proxy requests; for example Default Web Site. 3 Select New > Virtual Directory from the context menu. 4 Click Next, then specify workspace in the Alias field.
Note: Aliases are case-sensitive. Enter aliases exactly as documented. 5 Provide the full path to the workspace_static directory inPath; for example:
174 Manually Deploying into WebLogic 9.1 9 Repeat the process to create a Virtual Directory called wsmedia that uses the full path to workspace_static\wsmedia;
for example:
for example:
For Web Analysis
➤ To create IIS virtual directories for Web Analysis: 1 Open the Internet Information Service Manager, and expand Web Sites. 2 Right click the Web Site that will be used to proxy requests; for example Default Web Site. 3 Select New > Virtual Directory from the context menu. 4 Click Next, then in the Alias field, specify WebAnalysis.
Note: Aliases are case-sensitive. Enter aliases exactly as documented. 5 In Path, provide the full path to the WebAnalysis_static directory; for example:
For Financial Reporting and Products that do Not Include Static Content For Workspace modules that do not include static content, such as Financial Reporting, create one virtual directory for each file-system directory you created in “Create File-system Directories and Configuration Files” on page 199. The Virtual Directory Aliases used must match the context root of the web application for which IIS will act as a proxy. For example:
Application Workspace Module) Application context root Virtual Directory Alias
Financial Reporting /hr hr
Performance Management Architect /awb awb
Performance Scorecard /HPSWebReports HPSWebReports
Planning /HyperionPlanning HyperionPlanning
Configuring a Web Server for WebLogic 9.1 175 ➤ For Financial Reporting and any products that do not include static content: 1 Open the Internet Information Service Manager, and expand Web Sites. 2 Right click the Web Site that will be used to proxy requests; for example Default Web Site. 3 Select New > Virtual Directory from the context menu. 4 Click Next, then specify an appropriate value from the table above in the Alias field; for example, hr
Note: Aliases are case-sensitive. Enter aliases exactly as documented. 5 In Path, provide the full path to the files-system directory that contains iisproxy.ini and iisproxy.dll for this proxy definition in the Path field; for example: C:\Hyperion\WebLogicVHosts\FinancialReporting 6 Click Next. 7 Select Read, Run scripts, Execute in the Virtual Directory Access Permissions dialog. 8 Click Next, then Finish. 9 Repeat this process for each additional application for which IIS will act as a proxy.
Add IIS Application Extension Maps
For Workspace and Web Analysis
➤ To add IIS application extension maps: 1 Open the Internet Information Service Manager, and expand Web Sites. 2 Expand the Web Site that will be used to proxy requests; for example Default Web Site. 3 Right click on the Virtual Directory called workspace, then select Properties. 4 Do one of the following:
● IIS 5.0 From Application Protection, select High (Isolated).
● IIS 6.0—Select the Application Pool that you created for this Virtual Host during “Create Application Pools (IIS 6.0) ” on page 200; for example, Workspace. 5 Click Configuration. 6 Under Application extensions, click Add. 7 In Executable, provide the full path to the copy of iisproxy.dll that resides in the file-system directory you created for this Virtual Host; for example: C:\Hyperion\WebLogicVHosts\Workspace\iisproxy.dll 8 In Extension, enter .wlforward. 9 Clear Verify that file exists. 10 Click OK.
176 Manually Deploying into WebLogic 9.1 11 Repeat this process for the Web Analysis Virtual Host.
For Financial Reporting and Products that do Not Include Static Content
➤ For Financial Reporting and any products that do not include static content: 1 Open the Internet Information Service Manager, and expand Web Sites. 2 Expand the Web Site that will be used to proxy requests; for example Default Web Site. 3 Right click on the Virtual Directory to be configured; for example: hr, then select Properties. 4 Do one of the following:
● IIS 5.0 (Windows 2000): Select High (Isolated) from Application Protection.
● IIS 6.0 (Windows 2003): Select the Application Pool that you created for this Virtual Host during “Create Application Pools (IIS 6.0) ” on page 200; for example, hr 5 Click Configuration. 6 Under Wildcard application maps, click Insert. 7 Provide the full path to the copy of iisproxy.dll that resides in the file-system directory you created for this Virtual Host; for example: C:\Hyperion\WebLogicVHosts\FinancialReporting\iisproxy.dll 8 Clear Verify that file exists. 9 Click OK. 10 Repeat this process for each additional application for which IIS will act as a proxy.
Allow ISAPI Extensions (IIS 6.0) If you are configuring IIS 6.0 (Windows 2003), you need to allow ISAPI Extensions. Do the one of the following security models:
● Allow all unknown ISAPI Extensions:
➤ To configure: 1 Open the Internet Information Service Manager. 2 Click Web Service Extensions. 3 In the right side pane, click All unknown ISAPI Extensions. 4 ClickAllow. 5 Click OK.
● Add a new Web service extension for each copy of iisproxy.dll
➤ To configure: 1 Open the Internet Information Service Manager.
Configuring a Web Server for WebLogic 9.1 177 2 Click Web Service Extensions. 3 In the right side pane, click Add a new Web service extension. 4 In Extension Name, enter a unique name that reflects the role of the extension; for example workspace- wls-proxy. 5 Add the full path to iisforward.dll to Required Files by clicking Add; for example: C:\Hyperion\WebLogicVHosts\iisforward.dll 6 Check Set extension status to Allowed. 7 Click OK. 8 Repeat process for each copy of iisproxy.dll.
Restart IIS Restart IIS to enable the Microsoft Internet Information Server (IIS) Plug-in for WebLogic.
➤ After restarting: 1 Open the Internet Information Service Manager, and expand Web Sites. 2 Right click the Web Site that will be used to proxy requests; for example Default Web Site. 3 Select Properties from the context menu, and then click the ISAPI Filters tab. 4 Ensure the WLFilter ISAPI Filter is loaded.
Testing Module Availability For each of the products used, verify the setup by using the URLs below. If you have changed the web server configuration, restart the web server before running these tests.
Product URL* Expected Result
Workspace http://
Financial Reporting http://
Web Analysis http://
Performance Management Architect http://
178 Manually Deploying into WebLogic 9.1 Product URL* Expected Result
Financial Management http://
Planning http://
*URL: Where
Post Configuration Tasks To finish the configuration, see “Post Configuration Tasks” on page 66.
Post Configuration Tasks 179 180 Manually Deploying into WebLogic 9.1 Manually Deploying into 12 WebLogic 8.1
In This Chapter Prerequisites...... 181 Creating WebLogic Domains...... 181 Deploying Workspace into WebLogic...... 182 Deploying Financial Reporting into WebLogic...... 186 Deploying Web Analysis into WebLogic...... 186 Configuring a Web Server for WebLogic 8.1...... 187 Testing Module Availability...... 204 Post Configuration Tasks...... 205
Prerequisites
● Shared Services
❍ Install Shared Services
❍ Verify that it is up and running.
❍ Test the installation and make sure they 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.
Creating WebLogic Domains To prevent the Web application being deployed from inheriting unwanted runtime settings, you must create and use a new server. Deploying more than one Web application to the same server may yield unsuccessful results.
Prerequisites 181 ➤ To create WebLogic domains: 1 Run BEA WebLogic Configuration Wizard:
● Workspace—45000
● WebAnalysis—16000
● FinancialReporting—8200 6 Configure SSL if necessary, then click Next.
Note: The name of the WebLogic configuration and the server names within it must be unique. You can leave the name of sever without changes; for example, myserver.) 7 Click Next. 8 The Managed Servers, Clusters and Machines Options is displayed. Click Next. 9 The Database (JDBC) Options is displayed. Click Next. 10 The Messaging (JMS) Options is displayed. Click Next. 11 Enter the administrator username and password, and click Next. 12 Choose Production Mode and BEA Supplied SDKs (Sun or JRockit SDK), and click Next. 13 Enter a configuration name (Workspace, WebAnalysis or FinancialReporting) and change the configuration location if necessary. Click Create.
Note: For every Application, create one unique domain.
Deploying Workspace into WebLogic
Modifying startWebLogic.bat
➤ To modify startWebLogic.bat: 1 Navigate to and open startWebLogic.bat :
182 Manually Deploying into WebLogic 8.1 set LIB_DIR=
set PRE_CLASSPATH=
set CLASSPATH=%LIB_DIR%\iona63.jar;%LIB_DIR%;%CLASSPATH%
set JAVA_OPTIONS="- Dorg.omg.CORBA.ORBClass=com.iona.corba.art.artimpl.ORBImpl -Dorg.omg.CORBA.ORBSingletonClass=com.iona.corba.art.artimpl.ORBSingleton"
set MEM_ARGS="-Xms256m -Xmx512m"
Where
Deploying Workspace
➤ To deploy: 1 Extract
to start the WebLogic Server Administration Console. 3 In a Web browser, enter the URL:
http://
where
Note: Do not select the workspace.war. 8 Review your choices, then click Deploy.
Deploying Workspace into WebLogic 183 The Workspace Web application is deployed. 9 See “Configuring with Reporting and Analysis and Hyperion Applications” on page 188.
Modifying portlets.xml
➤ To modify portlets.xml: 1 With a text editor, open:
Preference Change value to
pr_wsrp_producer_url http://
where
ir_wsrp_producer_url http://
where
fr_wsrp_producer_url http://
where
wa_wsrp_producer_url http://
where
workspace_url
where
● Apache—19000 ● IBM HTTP Server—19000 ● IIS—80 ● Oracle HTTP Server—19000
foundation_port
where
● Apache—19000 ● IBM HTTP Server—19000 ● IIS—80 ● Oracle HTTP Server—19000
foundation_host
184 Manually Deploying into WebLogic 8.1 Preference Change value to where
3 Start or restart the Workspace application server.
Post Deployment for Workspace
Compiling JSP For precompiling JSP create
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 Configure context.properties: a. Add the following values: HPSU=Y ChangeManagement=Y Reports=Y Analyzer=Y HP=N BPMA=Y HFM=N HPS=N
Deploying Workspace into WebLogic 185 Note: Leave HPSU and ChangeMangement as Y. b. Assign an appropriate Y or N to each value in accordance with the Reporting and Analysis modules you have installed:
● Financial Reporting (Reports)
● Web Analysis (Analyzer)
● Planning (HP)
● Performance Management Architect (BPMA)—Used with Financial Management or Planning
● Financial Management (HFM)
● Performance Scorecard (HPS) 3 Start or restart the Workspace application server.
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:
Deploying Web Analysis into WebLogic This section describes how to deploy Web Analysis into WebLogic.
Web Analysis Environment Variables The Hyperion Configuration Utility prepares the JVM environment with the necessary environment variables for WebAnalysis to function correctly. Reporting and Analysis creates WebAnalysis.env which sets required environment variables at runtime. The file is located in:
186 Manually Deploying into WebLogic 8.1 Deploying Web Analysis
➤ To deploy the Web Analysis Web application: 1 Edit the Application Server startup script by adding to the JAVA_OPTIONS environment variable, the following option: -Ddeployment.mode=true
Note: The additional JVM argument -Ddeployment.mode=true is required at first deployment time only and should be removed after successful application deployment. 2 Sign in to your WebLogic Admin Console. 3 In the left Navigation frame, select Deployments > Applications and select Deploy a new Application. 4 Select one as the archive to deploy:
where
Configuring a Web Server for WebLogic 8.1
Configuring Apache
● “Configuring with Reporting and Analysis and Hyperion Applications” on page 188
● “Configuring with Performance Management Architect with Apache Web Server” on page 195
● “Configuring with Financial Management with Apache Web Server ” on page 195
● “Configuring with Performance Scorecard with Apache Web Server” on page 196
● “Configuring with Planning with Apache Web Server” on page 196
Configuring a Web Server for WebLogic 8.1 187 Configuring with Reporting and Analysis and Hyperion Applications 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. See “Web Server Use in Hyperion” on page 16. The Apache Web Server Plug-in proxies requests from an Apache Web Server to a WebLogic Application 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 Apache Web Server: 1 Install Apache Web Server 2.0 and verify that mod_so.c module is enabled by executing:
Note: 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 Web Server Plug-in module: a. Copy the mod_wl_20.dll file located in:
with the following contents, replacing
188 Manually Deploying into WebLogic 8.1
Configuring a Web Server for WebLogic 8.1 189
190 Manually Deploying into WebLogic 8.1 SetHandler weblogic-handler PathTrim / KeepAliveEnabled ON KeepAliveSecs 20 WeblogicCluster
Configuring a Web Server for WebLogic 8.1 191 PathTrim / KeepAliveEnabled ON KeepAliveSecs 20 WeblogicCluster
192 Manually Deploying into WebLogic 8.1 KeepAliveSecs 20 WeblogicCluster
Configuring a Web Server for WebLogic 8.1 193 WeblogicCluster
and add the following: Include conf/HYSL-WebLogic.conf Alias /wsmedia "
● “Configuring with Performance Management Architect with Apache Web Server” on page 195
● “Configuring with Financial Management with Apache Web Server ” on page 195
● “Configuring with Performance Scorecard with Apache Web Server” on page 196
● “Configuring with Planning with Apache Web Server” on page 196 4 Restart the Apache HTTP Server.
194 Manually Deploying into WebLogic 8.1 Configuring with Performance Management Architect with Apache Web Server
➤ To configure Performance Management Architect with Apache Web Server: 1 “Configuring with Reporting and Analysis and Hyperion Applications” on page 188 2 Open:
where
Configuring with Financial Management with Apache Web Server
➤ To configure Financial Management with Apache Web Server: 1 See “Configuring with Reporting and Analysis and Hyperion Applications” on page 188. 2 With a text editor, create
ProxyRequests On ProxyPreserveHost On
Configuring a Web Server for WebLogic 8.1 195 ProxyPass /hfm http://
where
and add the line: Include conf/hfm.conf
Configuring with Performance Scorecard with Apache Web Server
➤ To configure Performance Scorecard with Apache Web Server: 1 “Configuring with Reporting and Analysis and Hyperion Applications” on page 188. 2 Open:
where
Configuring with Planning with Apache Web Server
➤ To configure Planning with Apache Web Server: 1 “Configuring with Reporting and Analysis and Hyperion Applications” on page 188. 2 Open:
196 Manually Deploying into WebLogic 8.1 PathTrim / KeepAliveEnabled ON KeepAliveSecs 20 WeblogicCluster
where
Configuring Microsoft IIS The Microsoft Internet Information Server (IIS) Plug-in for WebLogic proxies requests from IIS to WebLogic. The web applications that comprise the Application Layer Web Tier of Reporting and Analysis are distributed among more than one WebLogic server instance, which include the Workspace, and one or more of the following Workspace modules:
● Financial Reporting
● Web Analysis
● Performance Management Architect
● Planning
● Performance Scorecard All Hyperion products that are accessed through Performance Management Architect must share the same Web server hostname and port. See “Web Server Use in Hyperion” on page 16. The following procedure describe configuring Microsoft IIS and the IIS plug-in for WebLogic to fulfill this requirement. See “Installing and Configuring the Microsoft IIS Pug-in” section of BEA WebLogic Server documentation for configuration options not covered by this Installation Guide. For WebLogic 8.1: http://e-docs.bea.com/wls/docs81/plugins/isapi.html For WebLogic 9.1: http://e-docs.bea.com/wls/docs91/plugins/isapi.html
Configure Proxying by Path
➤ To configure proxying by path: 1 Create a directory to store the configuration files needed to configure proxying by path; for example: C:\Hyperion\WebLogicVHosts 2 Copy
Configuring a Web Server for WebLogic 8.1 197 4 Add the property WlForwardPath to iisproxy.ini, and specify a comma delimited list of paths to be proxied. Only Workspace and Web Analysis paths need be included, for this release, as they are the only applications that include static content. Other modules, such as Financial Reporting, include only dynamic content, and do not need to be included in WlForwardPath. Workspace dynamic content forward paths: /workspace/cdsrpc,/workspace/administration,/workspace/browse,/workspace/ personalpages,/workspace/viewmanager,/workspace/jobmanager,/workspace/ ihtml,/workspace/dataaccess,/workspace/logon,/workspace/prefs,/workspace/ js,/workspace/modules,/workspace/resources,/workspace/conf,/workspace/ media,/workspace/BPMContext,/workspace/*.jsp,/workspace/*.jsv,/workspace/ *.jsw/workspace/wsrp4j/*,/workspace/ResourceProxy
Web Analysis dynamic content forward paths: /WebAnalysis/ServerConsole,/WebAnalysis/templates,/WebAnalysis/ hfmtemplates,/WebAnalysis/hitemplates,/WebAnalysis/portlettemplates,/ WebAnalysis/servlet,/WebAnalysis/modules,/WebAnalysis/resources,/ WebAnalysis/processor,/WebAnalysis/DirectoryServlet,/WebAnalysis/config,/ WebAnalysis/Config,/WebAnalysis/wa_javadocs/*,/WebAnalysis/*.jsp,/ WebAnalysis/*.xml,/WebAnalysis/*.jar,/WebAnalysis/*.exe
iisproxi.ini that include both Workspace and Web Analysis: WlForwardPath=/workspace/cdsrpc,/workspace/administration,/workspace/ browse,/workspace/personalpages,/workspace/viewmanager,/workspace/ jobmanager,/workspace/ihtml,/workspace/dataaccess,/workspace/logon,/ workspace/prefs,/workspace/js,/workspace/modules,/workspace/resources,/ workspace/conf,/workspace/media,/workspace/BPMContext,/workspace/*.jsp,/ workspace/*.jsv,/workspace/*.jsw,/workspace/wsrp4j/*,/workspace/ ResourceProxy,/WebAnalysis/ServerConsole,/WebAnalysis/templates,/ WebAnalysis/hfmtemplates,/WebAnalysis/hitemplates,/WebAnalysis/ portlettemplates,/WebAnalysis/servlet,/WebAnalysis/modules,/WebAnalysis/ resources,/WebAnalysis/processor,/WebAnalysis/DirectoryServlet,/ WebAnalysis/config,/WebAnalysis/Config,/WebAnalysis/wa_javadocs/*,/ WebAnalysis/*.jsp,/WebAnalysis/*.xml,/WebAnalysis/*.jar,/WebAnalysis/*.exe
Register iisforward.dll with IIS You must register iisforward.dll with the IIS website that will be used to proxy request to WebLogic.
➤ To register: 1 Open the Internet Information Service Manager, and expand Web Sites. 2 Right click the Web Site that will be used to proxy requests; for example: Default Web Site. 3 Select Properties from the context menu, and then click the ISAPI Filters tab. 4 Click Add, and enter WLFilter in Filter Name. 5 Provide the full path to iisforward.dll; for example: C:\Hyperion\WebLogicVHosts\iisforward.dll 6 Click OK.
198 Manually Deploying into WebLogic 8.1 7 If you are configuring IIS 6.0 (Windows 2003), do the following: a. Click Web Service Extensions. b. In the right side pane, click Add a new Web service extension. c. In Extension Name, enter WLFilter. d. Add the full path to iisforward.dll to Required Files by clickingAdd; for example: C:\Hyperion\WebLogicVHosts\iisforward.dll e. Check Set extension status to Allowed. f. Click OK.
Configure Proxy by File Extension
Create File-system Directories and Configuration Files A file-system directory must be created for Workspace and each Workspace module for which IIS will act as a proxy.
➤ To create and configure: 1 Create a directory to store the configuration files needed to configure proxying by extension for Workspace; for example: C:\Hyperion\WebLogicVHosts\workspace 2 Repeat this process, creating a directory for each Workspace module you have installed; for example: C:\Hyperion\WebLogicVHosts\WebAnalysis C:\Hyperion\WebLogicVHosts\FinancialReporting C:\Hyperion\WebLogicVHosts\BPMA 3 Copy
If proxying to a WebLogic cluster, substitute WebLogicHost with WebLogicCluster, and do not include WebLogicPort; for example: WebLogicCluster=host1.example.com:
For a full list of supported plug-in parameters, see BEA documentation: For WebLogic 8.1: http://e-docs.bea.com/wls/docs81/plugins/plugin_params.html For WebLogic 9.1: http://e-docs.bea.com/wls/docs91/plugins/plugin_params.html Example iisproxy.ini for Workspace: WebLogicHost=somehost.example.com WebLogicPort=45000
Configuring a Web Server for WebLogic 8.1 199 KeepAliveEnabled=true KeepAliveSecs=20
Create Application Pools (IIS 6.0) If you are configuring IIS 6.0 (Windows 2003), perform this procedure for each file-system directory you created.
➤ To create application pools: 1 Open the Internet Information Service Manager. 2 Right click on Application Pools. 3 Select New > Application Pool from the context menu . 4 Assign the same name given to your file-system directory in Application pool ID ; for example Workspace. 5 Click OK.
Create IIS Virtual Directories IIS Virtual Directories must be created for Workspace and each Workspace module for which IIS will act as a proxy.
For Workspace
➤ To create IIS virtual directories for Workspace: 1 Open the Internet Information Service Manager, and expand Web Sites. 2 Right click the Web Site that will be used to proxy requests; for example Default Web Site. 3 Select New > Virtual Directory from the context menu. 4 Click Next, then specify workspace in the Alias field.
Note: Aliases are case-sensitive. Enter aliases exactly as documented. 5 Provide the full path to the workspace_static directory inPath; for example: C:\Hyperion\BIPlus\AppServer\InstalledApps\workspace_static 6 Click Next. 7 Select Read, Run scripts, Execute in the Virtual Directory Access Permissions dialog. 8 Click Next, then Finish. 9 Repeat the process to create a Virtual Directory called wsmedia that uses the full path to workspace_static\wsmedia;
for example:
200 Manually Deploying into WebLogic 8.1 C:\Hyperion\BIPlus\AppServer\InstalledApps\workspace_static\wsmedia 10 Repeat the process, again, to create a Virtual Directory called InsightInstaller that uses the full path to workspace_static\zeroadmin\component\Insight
for example: C:\Hyperion\BIPlus\AppServer\InstalledApps\workspace_static\zeroadmin \component\Insight
For Web Analysis
➤ To create IIS virtual directories for Web Analysis: 1 Open the Internet Information Service Manager, and expand Web Sites. 2 Right click the Web Site that will be used to proxy requests; for example Default Web Site. 3 Select New > Virtual Directory from the context menu. 4 Click Next, then in the Alias field, specify WebAnalysis.
Note: Aliases are case-sensitive. Enter aliases exactly as documented. 5 In Path, provide the full path to the WebAnalysis_static directory; for example: C:\Hyperion\BIPlus\AppServer\InstalledApps\WebAnalysis_static 6 Click Next. 7 Select Read, Run scripts, Execute in the Virtual Directory Access Permissions dialog. 8 Click Next, then Finish.
For Financial Reporting and Products that do Not Include Static Content For Workspace modules that do not include static content, such as Financial Reporting, create one virtual directory for each file-system directory you created in “Create File-system Directories and Configuration Files” on page 199. The Virtual Directory Aliases used must match the context root of the web application for which IIS will act as a proxy. For example:
Application Workspace Module) Application context root Virtual Directory Alias
Financial Reporting /hr hr
Performance Management Architect /awb awb
Performance Scorecard /HPSWebReports HPSWebReports
Planning /HyperionPlanning HyperionPlanning
➤ For Financial Reporting and any products that do not include static content: 1 Open the Internet Information Service Manager, and expand Web Sites.
Configuring a Web Server for WebLogic 8.1 201 2 Right click the Web Site that will be used to proxy requests; for example Default Web Site. 3 Select New > Virtual Directory from the context menu. 4 Click Next, then specify an appropriate value from the table above in the Alias field; for example, hr
Note: Aliases are case-sensitive. Enter aliases exactly as documented. 5 In Path, provide the full path to the files-system directory that contains iisproxy.ini and iisproxy.dll for this proxy definition in the Path field; for example: C:\Hyperion\WebLogicVHosts\FinancialReporting 6 Click Next. 7 Select Read, Run scripts, Execute in the Virtual Directory Access Permissions dialog. 8 Click Next, then Finish. 9 Repeat this process for each additional application for which IIS will act as a proxy.
Add IIS Application Extension Maps
For Workspace and Web Analysis
➤ To add IIS application extension maps: 1 Open the Internet Information Service Manager, and expand Web Sites. 2 Expand the Web Site that will be used to proxy requests; for example Default Web Site. 3 Right click on the Virtual Directory called workspace, then select Properties. 4 Do one of the following:
● IIS 5.0 From Application Protection, select High (Isolated).
● IIS 6.0—Select the Application Pool that you created for this Virtual Host during “Create Application Pools (IIS 6.0) ” on page 200; for example, Workspace. 5 Click Configuration. 6 Under Application extensions, click Add. 7 In Executable, provide the full path to the copy of iisproxy.dll that resides in the file-system directory you created for this Virtual Host; for example: C:\Hyperion\WebLogicVHosts\Workspace\iisproxy.dll 8 In Extension, enter .wlforward. 9 Clear Verify that file exists. 10 Click OK. 11 Repeat this process for the Web Analysis Virtual Host.
202 Manually Deploying into WebLogic 8.1 For Financial Reporting and Products that do Not Include Static Content
➤ For Financial Reporting and any products that do not include static content: 1 Open the Internet Information Service Manager, and expand Web Sites. 2 Expand the Web Site that will be used to proxy requests; for example Default Web Site. 3 Right click on the Virtual Directory to be configured; for example: hr, then select Properties. 4 Do one of the following:
● IIS 5.0 (Windows 2000): Select High (Isolated) from Application Protection.
● IIS 6.0 (Windows 2003): Select the Application Pool that you created for this Virtual Host during “Create Application Pools (IIS 6.0) ” on page 200; for example, hr 5 Click Configuration. 6 Under Wildcard application maps, click Insert. 7 Provide the full path to the copy of iisproxy.dll that resides in the file-system directory you created for this Virtual Host; for example: C:\Hyperion\WebLogicVHosts\FinancialReporting\iisproxy.dll 8 Clear Verify that file exists. 9 Click OK. 10 Repeat this process for each additional application for which IIS will act as a proxy.
Allow ISAPI Extensions (IIS 6.0) If you are configuring IIS 6.0 (Windows 2003), you need to allow ISAPI Extensions. Do the one of the following security models:
● Allow all unknown ISAPI Extensions:
➤ To configure: 1 Open the Internet Information Service Manager. 2 Click Web Service Extensions. 3 In the right side pane, click All unknown ISAPI Extensions. 4 ClickAllow. 5 Click OK.
● Add a new Web service extension for each copy of iisproxy.dll.
➤ To configure: 1 Open the Internet Information Service Manager. 2 Click Web Service Extensions. 3 In the right side pane, click Add a new Web service extension.
Configuring a Web Server for WebLogic 8.1 203 4 In Extension Name, enter a unique name that reflects the role of the extension; for example workspace- wls-proxy. 5 Add the full path to iisforward.dll to Required Files by clicking Add; for example: C:\Hyperion\WebLogicVHosts\iisforward.dll 6 Check Set extension status to Allowed. 7 Click OK. 8 Repeat process for each copy of iisproxy.dll.
Restart IIS Restart IIS to enable the Microsoft Internet Information Server (IIS) Plug-in for WebLogic.
➤ After restarting: 1 Open the Internet Information Service Manager, and expand Web Sites. 2 Right click the Web Site that will be used to proxy requests; for example Default Web Site. 3 Select Properties from the context menu, and then click the ISAPI Filters tab. 4 Ensure the WLFilter ISAPI Filter is loaded.
Testing Module Availability For each of the products used, verify the setup by using the URLs below. If you have changed the web server configuration, restart the web server before running these tests.
Product URL* Expected Result
Workspace http://
Financial Reporting http://
Web Analysis http://
Performance Management Architect http://
Financial Management http://
204 Manually Deploying into WebLogic 8.1 Product URL* Expected Result AboutHFM.asp? workspace=true
Planning http://
*URL: Where
Post Configuration Tasks To finish the configuration, see “Post Configuration Tasks” on page 66.
Post Configuration Tasks 205 206 Manually Deploying into WebLogic 8.1 Manually Deploying into 13 WebSphere 6.1
In This Chapter Prerequisites...... 207 Preparing the WebSphere Environment...... 207 Deploying Workspace...... 209 Deploying Financial Reporting...... 213 Deploying Web Analysis...... 214 Configuring a Web Server with WebSphere 6.1 Application Server...... 217 Testing Module Availability...... 225 Post Configuration Tasks...... 226
Prerequisites
● Shared Services
❍ Install Shared Services
❍ Verify that it is up and running.
❍ Test the installation and make sure they 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.
Preparing the WebSphere Environment To prevent the Web application being deployed from inheriting unwanted runtime settings, you must create and use a new WebSphere application server. Deploying more than one Web application to the same WebSphere application server may yield unsuccessful results.
Prerequisites 207 Note: You must have a configured Web server before proceeding. See IBM's document: http:// publib.boulder.ibm.com/infocenter/wasinfo/v6r0/topic/com.ibm.websphere.express.doc/ info/exp/ae/tihs_localsetup.html
WebSphere 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 2 Create a new application server for each module that will be deployed (freporting, webanalysis, workspace) by running the wsadmin.bat to get to the wsadmin prompt and enter a command; for example: $AdminTask createApplicationServer myhostNode01 {-name freporting - templateName default }
Tip: You can use the wsadmin scripting host to interactively create a new server by passing the createApplicationServer task –interactive 3 Save changes using the wsadmin scripting client; for example: $AdminConfig save 4 Restart the default application server; for example, server1. 5 Start the new application server(s); for example, freporting, webanalysis, workspace.
Add Virtual Host 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.
208 Manually Deploying into WebSphere 6.1 ➤ 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. 3 Supply the full server path to workspace.war; by default:
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.
Deploying Workspace 209 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 New. 5 Specify Name: SAP_LIBRARY. 6 Specify Classpath:
substituting
substituting
Assigning SAP_LIBRARY to Workspace
➤ To assign SAP_LIBRARY to Workspace: 1 Log in to the WebSphere console for the profile containing your application servers. 2 Navigate to Applications > Enterprise Applications >APP_NAME >Shared library references. 3 Select the APP_NAME application and click Reference Shared Libraries. 4 Select the SAP_LIBRARY library in the Available list and move it to the Selected list. 5 Click OK and then again click OK. 6 Save changes to Master Configuration.
Creating context.properties
➤ To create context.properties: 1 With a text editor, create:
210 Manually Deploying into WebSphere 6.1 Note: In the same directory, you can start with context.properties.sample. Uncomment and set the value for each property. 2 Configure context.properties: a. Add the following values: HPSU=Y ChangeManagement=Y Reports=Y Analyzer=Y HP=N BPMA=Y HFM=N HPS=N
Note: Leave HPSU and ChangeMangement as Y. b. Assign an appropriate Y or N to each value in accordance with the Reporting and Analysis modules you have installed:
● Financial Reporting (Reports)
● Web Analysis (Analyzer)
● Planning (HP)
● Performance Management Architect (BPMA)—Used with Financial Management or Planning
● Financial Management (HFM)
● Performance Scorecard (HPS)
Modifying portlets.xml
➤ To modify portlets.xml: 1 With a text editor, open:
Preference Change value to
pr_wsrp_producer_url http://
where
ir_wsrp_producer_url http://
Deploying Workspace 211 Preference Change value to where
fr_wsrp_producer_url http://
where
wa_wsrp_producer_url http://
where
workspace_url
where
● Apache—19000 ● IBM HTTP Server—19000 ● IIS—80 ● Oracle HTTP Server—19000
foundation_port
where
● Apache—19000 ● IBM HTTP Server—19000 ● IIS—80 ● Oracle HTTP Server—19000
foundation_host
where
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 Workspace is deployed. 4 In Initial Heap Size, enter 256. 5 In Maximum Heap Size, enter 512.
212 Manually Deploying into WebSphere 6.1 Note: These values may not be optimal for your user load, and may need to be adjusted. 6 Add additional Generic JVM argument: -Djava.awt.headless=false 7 Click OK, then save all changes. 8 Start or restart the application server. 9 Edit
replace $J(servletConfig.deploymentPath) with the actual location of deployed Workspace application. The default is:
Deploying Financial Reporting
➤ To deploy: 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; by default:
then click Next. 4 On Select installation options, verify that Precompile JavaServer Pages files is clear, then 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. 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. 6 Map virtual hosts for Web modules. 7 Acknowledge the summary of action to be performed, then click Finish to proceed with deployment. 8 Click Save to Master Configuration after deployment completes.
Deploying Financial Reporting 213 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 Navigate to Java and Process Management > Process Definition > Java Virtual Machine for the application server instance where Financial Reporting is deployed. 5 In Initial Heap Size, enter 256. 6 In Maximum Heap Size, enter 512.
Note: These values may not be optimal for your user load, and may need to be adjusted. 7 Add additional Generic JVM argument: -Djava.awt.headless=false 8 Click OK, then save all changes. 9 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 To enable the deployment mode option: a. In the left pane choose Servers > Application Servers. b. Choose the WebAnalysis server instance. c. In the Server Infrastructure area of the Configuration tab, click Java and Process Management > Process Definition > Java Virtual Machine. d. Edit the Generic JVM arguments field. Add the -Ddeployment.mode=true option. e. Click OK. f. Click Save to Master Configuration.
214 Manually Deploying into WebSphere 6.1 Note: The additional JVM argument -Ddeployment.mode=true is required at the first deployment time only and should be removed after successful application deployment. See step 8. 3 Navigate to Applications > Install New Application. 4 Supply the full server path to WebAnalysis.ear; by default:
then click Next. 5 Select Precompile JavaServer Pages files and click Next. 6 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. 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, the click Finish to proceed with deployment. 8 To remove the deployment mode option: a. In the left pane choose Servers > Application Servers. b. Choose WebAnalysis server instance. c. In the Server Infrastructure area of the Configuration tab, click Java and Process Management > Process Definition > Java Virtual Machine. d. Edit the Generic JVM arguments field. Remove the -Ddeployment.mode=true option. e. Click OK. 9 Click Save to Master Configuration.
Environment Variables The Hyperion Configuration Utility prepares the JVM environment with the necessary environment variables for WebAnalysis to function correctly. Reporting and Analysis creates WebAnalysis.env which sets required environment variables at runtime. The file is located in:
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.
Deploying Web Analysis 215 ➤ 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. 6 Specify Name as: SAP_LIBRARY. 7 Specify Classpath as:
where
where
➤ To assign SAP_LIBRARY to Web Analysis: 1 Log in to the WebSphere console for the profile containing your application servers. 2 Navigate to Applications > Enterprise Applications >APP_NAME >Shared library references. 3 Select the APP_NAME application and click Reference Shared Libraries. 4 Select the SAP_LIBRARY library in the Available list and move it to the Selected list. 5 Click OK and then again click OK. 6 Save changes to Master Configuration.
Configuring Web Analysis
➤ To configure Web Analysis: 1 Navigate to Session Management > Enable Cookies for the application server instance where Web Analysis is deployed. 2 Change the Cookie Path from / to /WebAnalysis, then click OK. 3 Navigate to Java and Process Management > Process Definition > Java Virtual Machine for the application server instance where Web Analysis is deployed. 4 In the Initial Heap Size field, enter 256. 5 In the Maximum Heap Size field, enter 512.
216 Manually Deploying into WebSphere 6.1 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
Configuring a Web Server with WebSphere 6.1 Application Server
Configuring Apache Server or IBM HTTP Server 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. 3 Select your Web server, and click Generate Plug-in. 4 Select your Web server, and click Propagate Plug-in or Copy:
into:
To: Configuring a Web Server with WebSphere 6.1 Application Server 217 Name="/workspace/administration/*"/> Web Analysis: Change the URI group definition which contains this single line: To: 218 Manually Deploying into WebSphere 6.1 Web Analysis: Alias /WebAnalysis " where Configuring IIS ➤ To configure IIS: 1 Start the IIS application. Configuring a Web Server with WebSphere 6.1 Application Server 219 2 Create a new virtual directory for the Web site instance that you intend to work with WebSphere Application Server. These instructions assume that you are using the Default Web Site. a. On the left navigation pane expand to Default Web Site. Right-click Default Web Site and select New > Virtual Directory to create the directory with a default installation. b. In Adding a virtual directory wizard, perform the following steps: i. Type sePlugins in the "Virtual Directory Alias" screen. ii. Browse to the WebSphere Application Server 220 Manually Deploying into WebSphere 6.1 d. Click Next, then specify workspace in the Alias field. Note: Aliases are case-sensitive. Enter aliases exactly as documented. e. Provide the full path to the workspace_static directory inPath; for example: ● Right click the InsightInstaller virtual directory and select Properties. ● Select HTTP Headers tab and click MIME Types. ● Add following Extension / MIME types pairs: .exe / application/octet-stream .ex_ / application/octet-stream .msi / application/octet-stream .boot / application/octet-stream .hdr / application/octet-stream .ini / application/octet-stream .xpi / application/octet-stream l. Click OK to close all windows. 6 Create IIS Virtual Directories for Web Analysis: a. Open the Internet Information Service Manager, and expand Web Sites. b. Right click the Web Site that will be used to proxy requests; for example Default Web Site. c. Select New > Virtual Directory from the context menu. d. Click Next, then specify WebAnalysis in the Alias field. Note: Aliases are case-sensitive. Enter aliases exactly as documented. e. In Path, provide the full path to the WebAnalysis_static directory; for example: Configuring a Web Server with WebSphere 6.1 Application Server 221 7 Create IIS Virtual Directories for Financial Reporting and products that do not include static content: a. Log in to the WebSphere Administrative Console for the profile containing your application servers. b. Navigate to Servers > Web Servers c. If IIS server you want to use with WebSphere is not in list, add it to list: i. Click New. ii. Specify the Server Name; for example, IIS. iii. Select Microsoft Internet Information Services (IIS) in Type field. iv. Specify the Host Name, where IIS installed. v. Click Next. vi. Click Next. vii. Specify the Web server Port, client machines will use to access Reporting and Analysis; for example, 19000. viii Specify the WebSphere Plug-in installation location. . ix. Click Next. x. Click Finish. d. Select your Web server, and click Generate Plug-in. 8 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: 222 Manually Deploying into WebSphere 6.1 Name="/workspace/logon"/> Web Analysis Change the URI group definition which contains this single line: Configuring a Web Server with WebSphere 6.1 Application Server 223 Name="/WebAnalysis/wa_javadocs" /> Note: The last line of the .loc file should be a blank line (carriage return). 10 Restart all IIS services. Configuring Financial Management with a Web Server Configuring Financial Management with Apache Web Server or IBM HTTP Server To configure Financial Management with Apache Web Server or IBM HTTP Server: using a text editor, open the Web server's configuration file (httpd.conf), and add the following directives, replacing where 224 Manually Deploying into WebSphere 6.1 Using Only IIS with Financial Management For using only IIS (for example, if Apache is not used at all): You must configure the IIS used by Financial Management as the front-end Web server for Workspace. You can have the Workspace Web application server running on a separate machine, but you must install the Workspace code onto the machine running IIS. The Workspace installation includes files that are served by the Web server, such as the help files. To install the Workspace code onto the IIS machine, after installing Workspace on the IIS machine, use Life Cycle Management and, or, regedit to change the Web server hostname. Testing Module Availability For each of the products used, verify the setup by using the URLs below. If you have changed the web server configuration, restart the web server before running these tests. Product URL* Expected Result Workspace http:// Financial Reporting http:// Web Analysis http:// Performance Management Architect http:// Financial Management http:// Planning http:// *URL: Where Testing Module Availability 225 Post Configuration Tasks To finish the configuration, see “Post Configuration Tasks” on page 66. 226 Manually Deploying into WebSphere 6.1 Manually Deploying into 14 WebSphere 6.0.2 In This Chapter Prerequisites...... 227 Preparing the WebSphere Environment...... 227 Deploying Workspace...... 229 Deploying and Configuring Financial Reporting...... 233 Deploying Web Analysis...... 234 Configuring a Web Server with WebSphere 6.0.2 Application Server...... 237 Testing Module Availability...... 245 Post Configuration Tasks...... 246 Prerequisites ● Shared Services ❍ Install Shared Services ❍ Verify that it is up and running. ❍ Test the installation and make sure they 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. Preparing the WebSphere Environment To prevent the Web application being deployed from inheriting unwanted runtime settings, you must create and use a new Application Server. Deploying more than one Web application to the same Application Server may yield unsuccessful results. Prerequisites 227 Note: You must have a configured Web server before proceeding. See IBM's document: http:// publib.boulder.ibm.com/infocenter/wasinfo/v6r0/topic/com.ibm.websphere.express.doc/ info/exp/ae/tihs_localsetup.html WebSphere 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 2 Create a new application server for each module that will be deployed (freporting, webanalysis, workspace) by running the wsadmin.bat to get to the wsadmin prompt and enter a command; for example: $AdminTask createApplicationServer myhostNode01 {-name freporting - templateName default } Tip: You can use the wsadmin scripting host to interactively create a new server by passing the createApplicationServer task –interactive 3 Save changes using the wsadmin scripting client; for example: $AdminConfig save 4 Restart the default application server; for example, server1. 5 Start the new application server(s); for example, freporting, webanalysis, workspace. Add Virtual Host 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. 228 Manually Deploying into WebSphere 6.0.2 ➤ 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. 3 Supply the full server path to workspace.war; by default: Note: Be sure to map the module to both an application server and web server. 11 In Map Virtual Hosts for Web modules, select the Virtual host from the drop down, and select the row check box. 12 Acknowledge the summary of actions to be performed, then click Finish to proceed with deployment. Deploying Workspace 229 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. 13 Click Save to Master Configuration after deployment completes. Creating a WebSphere Shared Library for SAP Authentication If Oracle's Hyperion® 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 In the line: DEPLOYMENT_PATH=$J(servletConfig.deploymentPath) replace: $J(servletConfig.deploymentPath) with the actual location of deployed Workspace application. The default is: 230 Manually Deploying into WebSphere 6.0.2 Assigning SAP_LIBRARY to Workspace ➤ To assign SAP_LIBRARY to Workspace: 1 Log in to the WebSphere console for the profile containing your application servers. 2 Navigate to Applications > Enterprise Applications > Workspace > Libraries. 3 Click Add and from the drop down, select SAP_LIBRARY. 4 Click OK. 5 Save to Master Configuration. 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 Configure context.properties: a. Add the following values: HPSU=Y ChangeManagement=Y Reports=Y Analyzer=Y HP=N BPMA=Y HFM=N HPS=N Note: Leave HPSU and ChangeMangement as Y. b. Assign an appropriate Y or N to each value in accordance with the Reporting and Analysis modules you have installed: ● Financial Reporting (Reports) ● Web Analysis (Analyzer) ● Planning (HP) ● Performance Management Architect (BPMA)—Used with Financial Management or Planning ● Financial Management (HFM) Deploying Workspace 231 ● Oracle's Hyperion® Performance Scorecard – System 9 (HPS) 3 Start or restart the Workspace application server. Modifying portlet.xml ➤ To modify portlet.xml: 1 With a text editor, open: Preference Change value to pr_wsrp_producer_url http:// where ir_wsrp_producer_url http:// where fr_wsrp_producer_url http:// where wa_wsrp_producer_url http:// where workspace_url where ● Apache—19000 ● IBM HTTP Server—19000 ● IIS—80 ● Oracle HTTP Server—19000 foundation_port where ● Apache—19000 ● IBM HTTP Server—19000 ● IIS—80 ● Oracle HTTP Server—19000 foundation_host 232 Manually Deploying into WebSphere 6.0.2 Preference Change value to where 3 Start or restart the Workspace application server. Configuring Workspace ➤ To configure Workspace: 1 Navigate to Web Container Settings > 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 Workspace 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 Click OK, then save all changes. 7 Start or restart the application server. Deploying and Configuring Financial Reporting ➤ To deploy: 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; by default: then click Next. 4 Select Generate Default Bindings. 5 Select Do not use default virtual host name for Web modules. 6 Acknowledge security warnings by clicking Continue. 7 Specify Web Application name: FReporting. 8 Clear Pre-compile JSP and click Next. Deploying and Configuring Financial Reporting 233 9 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. 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. 10 Map virtual hosts for Web modules. 11 Acknowledge the summary of action to be performed, then click Finish to proceed with deployment. 12 Click Save to Master Configuration after deployment completes. ➤ To configure Financial Reporting: 1 Log in to the WebSphere Administrative Console. 2 Navigate to Web Container Settings > Session Management > Enable cookies for the application server instance where Financial Reporting is deployed. 3 Change the Cookie Path from / to /hr, then click OK. 4 Navigate to Java and Process Management > Process Definition > Java Virtual Machine for the application server instance where Financial Reporting is deployed. 5 In Initial Heap Size, enter 256. 6 In Maximum Heap Size, enter 512. Note: These values may not be optimal for your user load, and may need to be adjusted. 7 Click OK, then save all changes. 8 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 To enable the deployment mode option: a. In the left pane choose Servers > Application Servers. b. Choose WebAnalysis server instance. 234 Manually Deploying into WebSphere 6.0.2 c. In the Server Infrastructure area of the Configuration tab click Java and Process Management > Process Definition > Java Virtual Machine. d. Edit the Generic JVM arguments field. Add the -Ddeployment.mode=true option. e. Click OK. Note: The additional JVM argument -Ddeployment.mode=true is required at the first deployment time only and should be removed after successful application deployment. See step 14. 3 Navigate to Applications > Install New Application. 4 Supply the full server path to WebAnalysis.ear; by default: . then click Next. 5 Select Generate Default Bindings. 6 Select Do not use default virtual host name for Web modules. 7 Acknowledge security warnings by clicking Continue. 8 Specify Web Application name: WebAnalysis 9 Clear Pre-compile JSP and click Next. 10 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. 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. 11 Map virtual hosts for Web modules. 12 On the Map security roles to users/groups click Next. 13 Acknowledge the summary of actions to be performed, the click Finish to proceed with deployment. 14 To remove the deployment mode option: a. In the left pane choose Servers > Application Servers. b. Choose WebAnalysis server instance. c. In the Server Infrastructure area of the Configuration tab click Java and Process Management > Process Definition > Java Virtual Machine. d. Edit the Generic JVM arguments field. Remove the -Ddeployment.mode=true option. e. Click OK. 15 Click Save to Master Configuration. Deploying Web Analysis 235 Environment Variables The Oracle's Hyperion® Configuration Utility™ prepares the JVM environment with the necessary environment variables for WebAnalysis to function correctly. Reporting and Analysis creates WebAnalysis.env which sets required environment variables at runtime. The file is located in: 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. 6 Specify Name as: SAP_LIBRARY. 7 Specify Classpath as: where where ➤ To assign SAP_LIBRARY to Web Analysis: 1 Log in to the WebSphere console for the profile containing your application servers. 2 Navigate to Applications > Enterprise Applications > WebAnalysis > Libraries. 3 Click Add and from the drop down, select SAP_LIBRARY. 4 Click OK. 5 Save to Master Configuration. 236 Manually Deploying into WebSphere 6.0.2 Configuring Web Analysis ➤ To configure Web Analysis: 1 Navigate to Web Container Settings > 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 the Initial Heap Size field, enter 256. 5 In the Maximum Heap Size field, enter 512. Note: These values may not be optimal for your user load, and may need to be adjusted. 6 Enter the following in Classpath, replacing Configuring a Web Server with WebSphere 6.0.2 Application Server Note: If the Web Server is on a different server than the Web Application, the static content (workspace_static & webanalysi_static directories) from the BIPlus deployment, coy the static content to the HTTP Server. Also, restart the Web server after making changes to the httpd.conf and plugin-cfg.xml files. Note: For WebAnalysis , you must modify WebAnalysis.properties to contain the correct ConfigURL. Modify the Configuring Apache Server or IBM HTTP Server This section describes the configuring of IBM HTTP Server or Apache. Configuring a Web Server with WebSphere 6.0.2 Application Server 237 ➤ To regenerate the Web server plug-in: 1 Log in to the WebSphere Administrative Console for the profile containing your application servers. 2 Navigate to Servers > Web servers. 3 Select your Web server, and click Generate Plug-in. 4 Copy: into: To: 238 Manually Deploying into WebSphere 6.0.2 Web Analysis: Change the URI group definition which contains this single line: To: Configuring a Web Server with WebSphere 6.0.2 Application Server 239 Workspace: Alias /workspace " Web Analysis: Alias /WebAnalysis " where Configuring IIS ➤ To configure IIS: 1 Start the IIS application. 2 Create a new virtual directory for the Web site instance that you intend to work with WebSphere Application Server. These instructions assume that you are using the Default Web Site. a. On the left navigation pane expand to Default Web Site. Right-click Default Web Site and select New > Virtual Directory to create the directory with a default installation. b. In Adding a virtual directory wizard, perform the following steps: i. Type sePlugins in the "Virtual Directory Alias" screen. ii. Browse to the WebSphere Application Server 240 Manually Deploying into WebSphere 6.0.2 vi. Browse to the Note: Aliases are case-sensitive. Enter aliases exactly as documented. e. Provide the full path to the workspace_static directory inPath; for example: ● Right click the InsightInstaller virtual directory and select Properties. ● Select HTTP Headers tab and click MIME Types. Configuring a Web Server with WebSphere 6.0.2 Application Server 241 ● Add following Extension / MIME types pairs: .exe / application/octet-stream .ex_ / application/octet-stream .msi / application/octet-stream .boot / application/octet-stream .hdr / application/octet-stream .ini / application/octet-stream .xpi / application/octet-stream 6 Create IIS Virtual Directories for Web Analysis: a. Open the Internet Information Service Manager, and expand Web Sites. b. Right click the Web Site that will be used to proxy requests; for example Default Web Site. c. Select New > Virtual Directory from the context menu. d. Click Next, then specify WebAnalysis in the Alias field. Note: Aliases are case-sensitive. Enter aliases exactly as documented. e. In Path, provide the full path to the WebAnalysis_static directory; for example: 242 Manually Deploying into WebSphere 6.0.2 8 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 a Web Server with WebSphere 6.0.2 Application Server 243 Web Analysis Change the URI group definition which contains this single line: Note: That the last line of the .loc file should be a blank line (carriage return). 10 Restart all IIS services. 244 Manually Deploying into WebSphere 6.0.2 Configuring Financial Management with a Web Server Configuring Financial Management with Apache Web Server or IBM HTTP Server To configure Financial Management with Apache Web Server or IBM HTTP Server: using a text editor, open the Web server's configuration file (httpd.conf), and add the following directives, replacing where Using Only IIS with Financial Management For using only IIS (for example, if Apache is not used at all): You must configure the IIS used by Financial Management as the front-end Web server for Workspace. You can have the Workspace Web application server running on a separate machine, but you must install the Workspace code onto the machine running IIS. The Workspace installation includes files that are served by the Web server, such as the help files. To install the Workspace code onto the IIS machine, after installing Workspace on the IIS machine, use Life Cycle Management and, or, regedit to change the Web server hostname. Testing Module Availability For each of the products used, verify the setup by using the URLs below. If you have changed the web server configuration, restart the web server before running these tests. Product URL* Expected Result Oracle's Hyperion® Workspace http:// Testing Module Availability 245 Product URL* Expected Result Oracle's Hyperion® Financial http:// Oracle's Hyperion® Web Analysis – http:// Performance Management Architect http:// Financial Management http:// Planning http:// *URL: Where Post Configuration Tasks To finish the configuration, see “Post Configuration Tasks” on page 66. 246 Manually Deploying into WebSphere 6.0.2 A ActiveX In This Appendix Whitepaper ...... 247 Sample Policy File ...... 248 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) ● XMLHttpRequest—a communication technique supported by newer browsers—joined with JavaScript on the client Whitepaper 247 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 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 Oracle's Hyperion® Reporting and Analysis – System 9 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" 248 ActiveX 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} 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 Sample Policy File 249 250 ActiveX ABCDEFGHI J LMNOPRSTUVW Index Hyperion License Server, 23 B database configuration, 53 backing up repositories, 23 upgrades, configuring, 50 BPM Architect, with Workspace Apache HTTP Plug-in A WebLogic 8.1, 195 browsers Active X settings, 36 description, 247 Web requirements, 35 sample policy file, 248 ADM driver, enabling the Planning driver, 61 Administrator User, provisioning, 75 C AJAX, 247 Cell Attachment requirements , 37 Analytic Provider Services Driver, enabling cell documents, print, 38 enabling support for Financial Reporting, 62 characters, restricted, 50 Apache HTTP Plug-in, with Workspace command line BPM Architect processor considerations, 40 WebLogic 8.1, 195 configuration Financial Management database, 53 WebLogic 8.1, 195 deployment, 55 WebLogic 9.1, 169 deployment, profiles and domains, 56 Performance Scorecard prerequisites, 50 WebLogic 8.1, 196 product upgrades, 50 WebLogic 9.1, 170 Shared Services registration, 52 Planning restricted characters, 50 WebLogic 8.1, 196 task list, 49 WebLogic 9.1, 170 task sequence, 50 Apache HTTP Server Plug-in, with troubleshooting, 50 WebLogic 9.1, 161 configuration files application server Oracle 10g, manual deployment, 118 deployment, 55 Hyperion Configuration UtilityConfiguration Utility application server host names, specifying, 54 deployment, 55 Application Server setting, 35 description, 49 authentication prerequisites, 50 SAP data source, 33 reconfiguration, 64 Authentication Service, defined, 18 Shared Services registration, 52 Authorization Service, defined, 18 task sequence, 50 configuring database software for the Repository, 24 Index 251 ABCDEFGHI J LMNOPRSTUVW IBM DB2, 24 WebSphere, 224, 245 connections, ODBC, creating, 32 prerequisites, 37 context path, customizing, 60 with Workspace context.properties, for WebLogic 8.1, Apache HTTP Plug-in, 195 WebLogic 8.1, manual deployment, 185 WebLogic 9.1, Apache HTTP Plug-in, 169 WebLogic 9.1, manual deployment, 159 Financial Reporting WebSphere 6.0.2, manual deployment, 231 enabling the Planning ADM driver, 61 WebSphere 6.1, manual deployment, 210 manual deployment cookie path, changing Oracle 10g, 139 WebSphere 6.1, manual deployment, 214 Oracle 10g Release 3, 119 Core Services, 18 WebLogic 8.1, 186 creating shared library for SAP authentication WebLogic 9.1, 159 WebSphere 6.0.2, 210, 230 WebSphere 6.0.2, 233 customizing context path , 60 WebSphere 6.1, 213 Print Server, 37 D print service and scheduler, configure, 63 print service configuration, 62 databases Report Server configuration, 53 configuration, 63 creating users, 28 SSAS 2005 connection, 32 repository size recommendations, 24 Financial Reporting servers, defined, 20 supported in Migration Utility, 100 firewalls to store Web server installation and, 36 metada, 27 firewalls, Oracle, 31 Interactive Reporting, 80 deployment, 55 folders installed deregistering Reporting and Analysis with Shared HYPERION_HOME directory, 44 Services functional services, 18 uninstalling and reinstalling, 87 domains WebLogic 8.1, creating, 181 G Global Security Kit, for WebSphere Express E installing, 34 GSM environment variables defined, 18 Web Analysis GSM host and port, specifying, 60 Oracle 10 Release 2, 144 WebLogic 9.1, 160 Windows, 27, 31 H error logs, 50 HTTP server Event Service Apache with WebLogic 8.1, 188 defined, 19 HTTP Server Plug-in Extended Access for Hyperion Interactive Reporting WebSphere 6.0.2, manual deployment Service, 19 Web Analysis, 237 WebSphere 6.1, manual deployment F Web Analysis, 217 Hyperion Home, 44 Financial Management Hyperion Interactive Reporting Data Access Service configuring with a Web server 252 Index ABCDEFGHI J LMNOPRSTUVW defined, 19 login, 28 Hyperion Interactive Reporting Service Microsoft Word, importing Financial Reporting defined, 19 contents into, 37 HYPERION_HOME environment variable, 44 migrating users and groups, 95 Migration Utility I installing, 99, 101 overview, 99 IBM DB2 post installation, 102 configuring, 24 requirements, 100 troubleshooting, 24 supported databases, 100 with Web Analysis, 27 migration, repository, 23 IIS only modifying portlet Financial Management Oracle 10g Release 3, 117 WebSphere, 225, 245 module installers, overview, 42 IIS Plug-in module-specific configurations, 59 Tomcat, 107 installers description by installer, 42 N description by modules, 42 Name Service installing, 46 defined, 18 Interactive Reporting configuring Production Reporting engine for, 60 O irmconfig.xml OC4J instance sample of, 78 Financial Reporting service types used in, 78 Oracle 10g Release 3, 119 Web Analysis J Oracle 10g Release 3, 122 JDBC driver, and IBM DB2, 27 OC4J instance in Job Service Workspace, 114, 134 defined, 19 OC4J instance, in JSP, compiling Financial Reporting, 139 in WebLogic 8.1, manual deployment, 185 Web Analysis, 143 ODBC connections, creating, 32 L OHS routing for Workspace, 118 Oracle launching Reporting and Analysis modules, 75 configuring, 28 license compliance, 23 database storage, 31 license server in 9.3.1, 23 Oracle 10g Release 2, manual deployment Logging Service Financial Reporting defined, 18 deploying, 139 LSC services HReports.ear, 142 defined, 17 OC4J instance, 139 LSM, 18 prerequisites, 133 SAP as an authentication provider, 136 M Web Analysis management services, 18 deploying, 143 Microsoft SQL Server environment variables, 144 Index 253 ABCDEFGHI J LMNOPRSTUVW OC4J instance, 143 P WebAnalysis.ear, 145 parameters Web server, 146 Oracle 10g Release 2, 148 additional parameters, 148 Performance Scorecard, with Workspace Architect or Planning, 147 Apache HTTP Plug-in Reporting and Analysis, 146 WebLogic 8.1, 196 Workspace WebLogic 9.1, 170 creating context.properties, 137 Planning, enabling the ADM driver, 61 OC4J instance, 134 Planning, with Workspace workspace.war, 135 Apache HTTP Plug-in Oracle 10g Release 3 WebLogic 9.1, 170 manual deployment WebLogic 8.1 prerequisites, 113 Apache HTTP Plug-in, 196 single sign-onReporting and Analysis port numbers configuring Shared Services, 131 changing Apache HTTP Server , 77 Oracle 10g Release 3, manual deployment, 113 Interactive Reporting Service, Job Service, Data Financial Reporting Access Service, 77 deploying, 119 ranges in Interactive Reporting, 78 HReports.ear, 121 used by Hyperion products, 40 OC4J instance, 119 portlet.xml, modifying modifying portlet, 117 Oracle Release 2, 139 SAP as an authentication provider, 115 post deployment Web Analysis WebLogic 8.1, Workspace, 185 deploying, 122 Powerpoint, importing Financial Reporting contents OC4J instance, 122 into, 37 WebAnalysis.ear, 124 print Web server, 125 cell documents, 38 Financial Management, 127, 148 requirements, 38, 39 Reporting and Analysis, 125 print service Workspace configuration, 62 creating context.properties, 116 privileges, granting, 28 deploying, 114 Production Reporting OC4J instance, 114 configuring engine for Interactive Reporting, 60 workspace.war, 115 server, configuring, 37 Oracle 10g, manual deployment provisioning an administrator, 75 OHS Routing for Workspace, 118 Publisher Service, defined, 18 Workspace deploying, 134 R OC4J instance, 134 reconfiguration, 64 Oracle Distributed Configuration Managemet registration, Shared ServicesShared Services, 52 Command Line Utility registry.properties, 51 Oracle 10g Release 2, 142 reinstalling, 90 Oracle Enterprise Manager Reporting and Analysis, 87, 90 Oracle 10g Release 2, 142 client, 91 Web Analysis, 145 prerequisites, 87 Oracle. 10g Release 3, manual deployment Services, 90 updating configuration files, 118 UIServices, 90 254 Index ABCDEFGHI J LMNOPRSTUVW repository for Microsoft IIS, 81 backup, 23 Manually Creating the Web server config file, 81 configuring database software, 24 Manually Creating the Web server Siteminder databases, size recommendations, 24 modules, 81 migration, 23 policy server, configuring, 81 Repository Service prerequisites, 80 defined, 18 restarting components, 84 requirements Trusted Password on the Authentication Service, print, 38, 39 setting up, 84 temporary space, 39 Workspace Web App parameters, 83 Web browsers, 35 space requirements, temporary, 39 restricted characters, 50 SQL Server reviewing selected components, 47 configuring, 27 SSAS connections, 32 S startup commands sample policy file, 248 for Shared Services server, 72 SAP startup dependencies access and authentication, 33 verifying, 71 scheduler,Print server startup, verifying for Shared Services, 73 configuration, 63 startWebLogic.bat, modifying, 182 secure sockets-capable servers, 36 stopping Service Broker Shared Services, 74 defined, 18 SyncCSSIdentity_BI utiltiy, 96 service ports, customizing Workspace, 60 services T Core, 18 tables defined, 18 manually creating, 31 functional, 18 temporary space, requirements, 39 summary, 20 Terminal Server configuration, 41 Session Manager Service, 18 testing module availabilty, 64, 131, 152, 178, 204, 225, shared library for SAP authentication 245 WebSphere 6.0.2, manual deployment troubleshooting, 50 Web Analysis, 236 WebSphere 6.1, manual deployment U Web Analysis, 215 uninstalling Shared Services Reporting and Analysis, 87 stopping, 74 prerequisites, 87 Single Sign-on uninstalling and reinstalling Oracle 10g Release 2, 149 deregistering Reporting and Analysis with Shared Oracle Release 3 Services, 87 manual deploy, 127 upgrades Single sign-on configuring, 50 Oracle 10g Release 3 upgrading manually deployed Web applications, 97 configuring shared Services, 131 Upgrading paths supported, 93 SiteMinder, with Transparent Logon upgrading toReporting and Analysis 9.3.1, 93, 94 Configuring Shared Serivces, 84 Index 255 ABCDEFGHI J LMNOPRSTUVW about SyncCSSIdentity_BI utiltiy, 96 Configuration Utility support, 58 migrating users and groups, 95 enabling, 57 running SyncCSSIdentity_BI utiltiy, 96 manual support, 58 upgrading to 9.3.1, prerequisites, 93 ports, specifying in Configuration Utility, 54 Usage Service WebLogic defined, 18 configuring User Management Console Financial Reporting, 186 launching, 73 single profiling, 56 user provisioning WebLogic 8.1 Migration Utility, 100 creating context.properties Workspace, 185 V deploying Web Analysis, 187 deploying Workspace, 183 verifying startup of Shared Services, 73 HTTP server virtual host definitions Apache, 188 WebSphere 6.0.2, 228 manual deployment, 181 WebSphere 6.1, 208 WebLogic 8.1 domains creating in manual deployment, 181 W WebLogic 8.1, manual deployment Web Analysis Web Analysis deploying into WebLogic 8.1, 186, 187 deployment, 186 deploying WebAnalyis.ear, 124 Workspace, 182 IBM DB2, 27 deploying, 156 SSAS 2005 connection, 32 post deployment, 185 WebLogic 9.1, manual deployment, 160 WebLogic 9.1 WebSphere 6.0.2, manual deployment, 234 Apache HTTP Server Plug-in, 161 configuring, 237 WebLogic 9.1, manual deployment, 155 HTTP Server Plug-in, 237 Financial Reporting, 159 shared library for SAP Authentication and Web Analysis, 160 reporting, 236 , 160 WebSphere 6.1, manual deployment, 214 environment variables, 160 configuring, 216 Workspace HTTP Server Plug-in, 217 post deployment, 159 shared library for SAP Authentication and WebSphere reporting, 215 single domain, 56 Web browsers requirements, 35 WebSphere 6.0.2, manual deployment, 227 Web environment add virtual host definitions, 228 configuring, 35 context.properties, 231 Web server creating shared library for SAP authentication, Oracle Release 2 HTTP Server, 146 210, 230 Architect or Planning, 147 Financial Reporting, 233 Reporting and Analysis, 146 prepare WebSphere environment, 227 Oracle Release 3 HTTP Server prerequisistes, 227 Financial Management, 127, 148 Web Analysis, 234 Reporting and Analysis, 125 configuring, 237 Oracle Release 3HTTP Server, 125 HTTP Server Plug-in, 237 Web server plug-in 256 Index ABCDEFGHI J LMNOPRSTUVW shared library for SAP Authentication and Workspace, configuring HTTP Plug-in reporting, 236 BPM Architect Workspace, 229, 233 WebLogic 8.1, 195 WebSphere 6.1, manual deployment add virtual host definitions, 208 configuring Financial Reporting, 214 context.properties, 210 Financial Reporting, 213 prepare WebSphere environment, 207 prerequisistes, 207 Web Analysis, 214 configuring, 216 HTTP Server Plug-in, 217 shared library for SAP Authentication and reporting, 215 Workspace, 209, 212 WebSphere Express, IBM Global Security Kit installing, 34 Windows services, 56 starting, 72 Workspace completing configurations, 59 customizing context path, 59 customizing service ports, 60 for WebLogic 8.1 creating context.properties, 185 in Configuration Utility, 60 into WebLogic 8.1, 183 post deployment WebLogic 8.1, 185 WebLogic 8.1, deploying, 182 WebSphere 6.0.2, 209, 229 WebSphere 6.0.2, manual deployment, 233 WebSphere 6.1, manual deployment, 212 Workspace, configuring Apache HTTP Plug-in Planning WebLogic 8.1, 196 WebLogic 8.1 Financial Management, 195 Performance Scorecard, 196 WebLogic 9.1 Financial Management, 169 Performance Scorecard, 170 Workspace, configuring apache HTTP Plug-in Planning WebLogic 9.1, 170 Index 257 ABCDEFGHI J LMNOPRSTUVW 258 Index