HYPERION® REPORTING AND ANALYSIS – SYSTEM 9 RELEASE 9.3.1
INSTALLATION GUIDE FOR UNIX Reporting and Analysis Installation Guide for UNIX, 9.3.1 Copyright © 1989, 2008, Oracle and/or its affiliates. All rights reserved. Authors: Marilyn Ghilardi The Programs (which include both the software and documentation) contain proprietary information; they are 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 ...... 29 Manually Creating Tables ...... 31 Database Storage Parameters for Oracle ...... 32 Creating ODBC Connections ...... 32 Obtaining and Preparing Pre-requisite Software ...... 33 SAP Data Source Access and Authentication ...... 33 Configuring SAP Data Source Access and Authentication ...... 33 Installing the IBM Global Security Kit for WebSphere Express ...... 34 Configuring X11 for UI Services for Financial Reporting and Web Analysis ...... 34 AIX 5L ...... 35 Solaris 9 ...... 35 Solaris 10 ...... 35 Red Hat Enterprise Linux Release 4 ...... 36 HP-UX 11i ...... 36
Contents iii Setting the DISPLAY Variable ...... 37 Web Environment ...... 37 Application Server Setting ...... 37 Web Browser Requirements ...... 37 Configuring a Web Environment ...... 38 Financial Reporting and Web Analysis Web Server Environment ...... 38 Financial Management Web Server Environment ...... 38 Browser Settings ...... 39 Module-specific Prerequisites ...... 39 Configuring a Production Reporting Server Installation ...... 39 Financial Management ...... 39 Financial Reporting ...... 40 Financial Reporting Print Server ...... 40 Environment Variables ...... 40 Production Reporting ...... 40 Relinking the Hyperion Production Reporting Server Executables ...... 40 Installing Considerations ...... 40 Satisfying Stack Size Limit ...... 41 Satisfying Temporary Space Requirements ...... 41 Command Line Processor Considerations ...... 42 UNIX Installation Mechanisms ...... 42 Fonts ...... 42 Updating the C++ Runtime Environment for AIX ...... 43 Creating a Reporting and Analysis User Account ...... 43 Port Numbers Used by Hyperion Products ...... 43
Chapter 3. Installing Reporting and Analysis ...... 45 Prerequisites ...... 45 Reporting and Analysis Installers ...... 45 Reporting and Analysis Module Installers ...... 46 About Hyperion Home ...... 47 Hyperion Home Location ...... 47 Files Installed in the HYPERION_HOME Directory ...... 48 Changing the Hyperion Home Location ...... 49 Installing Reporting and Analysis ...... 50 Running Silent Installations ...... 51
Chapter 4. Configuring Reporting and Analysis ...... 53 Hyperion Configuration Utility ...... 53 Task Sequence ...... 54
iv Contents Restricted Characters ...... 54 Troubleshooting ...... 54 Satisfying Initial Requirements ...... 54 Configuring Product Upgrades ...... 54 Configuring Reporting and Analysis ...... 55 Registering With Shared Services ...... 56 Configuring Databases ...... 57 Specifying Application Server Hostnames and Web Server Connector Plug-in Ports . . 58 Deploying to the Application Server ...... 58 What Happens During Deployment ...... 60 WebSphere and WebLogic 9.1.x ...... 60 WebLogic 8.1.x ...... 61 Enabling the Web Server Plug-in ...... 61 Hyperion Configuration Utility Web Server Plug-in Support ...... 62 Web Server Plug-in Manual Support ...... 62 Completing Module-Specific Configurations ...... 63 Workspace Configurations ...... 63 Customizing the Context Path ...... 63 Specifying the GSM Host and Port ...... 63 Customizing Service Ports for Reporting and Analysis ...... 64 Configuring the SQR Production Reporting Engine for Interactive Reporting .... 64 Interactive Reporting Configuration ...... 64 Financial Reporting Configurations ...... 65 Enabling the Planning ADM Driver ...... 65 Enabling the Analytic Provider Services Driver ...... 66 Workspace, Print Server, and Scheduler Server Configurations ...... 66 Report Server Configuration ...... 66 Web Analysis Configuration - Enabling the Analytic Provider Services Driver ...... 67 SQR Production Reporting Configurations ...... 67 Reconfiguring Products ...... 67 Testing Module Availability ...... 68 Post Configuration Tasks ...... 68 Error Messages When Testing Module Availability ...... 68 Post Configuration Tasks ...... 69 Configuring WebLogic 9.x OpenJMS for Web Analysis ...... 69 Installing OpenJMS ...... 69 Configuring OpenJMS Databases ...... 69 Configuring and Starting OpenJMS Server ...... 71 Configuring Web Analysis to use OpenJMS ...... 72
Contents v Setting up WebSphere 6.0 OpenJMS and Web Analysis ...... 73 Configuring WebSphere 6.0 Embedded Messaging and Web Analysis Cluster (Reporting and Analysis ) ...... 73 Configure Web Analysis to use WebSphere JMS ...... 74 Verifying Startup Dependencies ...... 75 Starting Shared Services ...... 75 Verifying Successful Startup of Shared Services ...... 76 Stopping Shared Services ...... 77 Reporting and Analysis Administrator User ...... 78 Configuring Production Reporting Post Configuration Tasks ...... 78 Setting up the Environment Variables ...... 78 Recreating the Executables ...... 79 Launching Reporting and Analysis Modules ...... 79 Adding Content Expiration Headers ...... 80 Changing the Apache Web Server Listen Port ...... 81 Customizing Ports Used by Interactive Reporting Service, Interactive Reporting Job Service and Interactive Reporting Data Access Service ...... 81 Guidelines for Changing Port Ranges ...... 82 Service Types Used in irmconfig.xml ...... 82 Sample irmconfig.xml ...... 82 Setting up SiteMinder with Transparent Logon ...... 84 Prerequisites ...... 84 Creating the IBM HTTP Server/Apache Web Agent Configuration File ...... 85 Configuring IBM HTTP Server/Apache SiteMinder Modules ...... 85 Configuring the SiteMinder Policy Server ...... 86 Setting up Workspace Web Application Parameters ...... 88 Setting the Trusted Password on the Authentication Service ...... 88 Configuring Shared Services ...... 88 Restarting Components ...... 89
Chapter 5. Uninstalling and Reinstalling Reporting and Analysis ...... 91 Prerequisites ...... 91 Deregistering Reporting and Analysis with Shared Services ...... 91 Uninstalling ...... 92 Reinstalling ...... 92 Reinstalling Services ...... 92 Reinstalling UIServices ...... 93 Reinstalling Client ...... 93
vi Contents Chapter 6. Upgrading Reporting and Analysis from 9.x to 9.3.1 ...... 95 Prerequisites ...... 95 Upgrading ...... 96 Migrating Users and Groups ...... 97 Prerequisites ...... 97 About SyncCSSIdentity_BI Utility ...... 97 Running SyncCSSIdentity_BI utility ...... 98 Using Most Provider Types ...... 98 Using Provider Type Sun One LDAP Server ...... 99 Upgrading Manually Deployed Web Applications ...... 99
Chapter 7. Installing the Reporting and Analysis Migration Utility ...... 101 Migration Utility ...... 101 Requirements ...... 102 Supported Source Databases ...... 102 Installing the Migration Utility ...... 103 After Installing the Migration Utility ...... 104
Chapter 8. Configuring a Web Server with Apache Tomcat ...... 105 Configuring Apache ...... 105 Copy Required Files to the Apache Machine ...... 105 Create the Tomcat Web Server Plug-in Configuration Files ...... 106 Enable the Tomcat Web Server Plug-in in httpd.conf ...... 107 Create Aliases for Workspace and Web Analysis ...... 108 Restart Apache and Test the Tomcat Web Server Plug-in ...... 108 Configuring IIS ...... 109 Copy Required Files to the IIS Machine ...... 109 Create the Tomcat HTTP Plug-in Configuration Files ...... 109 Create a Virtual Directory for the Tomcat HTTP Plug-in ...... 111 Register the Tomcat HTTP Plug-in as an ISAPI Filter ...... 112 Create Virtual Directory Aliases for Workspace and Web Analysis ...... 112 Restart IIS and Test the Tomcat HTTP Plug-in ...... 113
Chapter 9. Manually Deploying into Oracle 10g Release 3 (10.1.3.1.0) Application Server ...... 115 Prerequisites ...... 115 Deploying Workspace Web Application ...... 116 Creating an OC4J Instance ...... 116 Configuring the Workspace OC4J Instance ...... 116 Deploying workspace.war ...... 117 Configuring Workspace ...... 118
Contents vii Enabling SAP as an Authentication Provider ...... 118 Creating context.properties ...... 118 Modifying portlet.xml ...... 119 Update Oracle HTTP Server Routing for Workspace ...... 120 Updating Configuration Files ...... 120 Deploying Financial Reporting ...... 121 Creating an OC4J Instance ...... 122 Configuring the FinancialReporting OC4J Instance ...... 122 Deploying HReports.ear ...... 124 Deploying Web Analysis ...... 124 Creating an OC4J Instance ...... 124 Configuring the WebAnalysis OC4J Instance ...... 125 Deploying WebAnalysis.ear ...... 127 Configuring Oracle HTTP Server for Oracle 10g Release 3 ...... 128 Configuring Reporting and Analysis ...... 128 Configuring Financial Management ...... 130 Configuring Oracle Single Sign-on on Oracle 10g Release 3 ...... 130 Prerequisites ...... 130 Configuring the Oracle Application Server ...... 131 Configuring Shared Services ...... 134 Testing Module Availability ...... 134 Post Configuration Tasks ...... 135
Chapter 10. Manually Deploying into Oracle 10g Release 2 (10.1.2.0.2) Application Server ...... 137 Prerequisites ...... 137 Deploying Workspace Web Application ...... 138 Creating an OC4J Instance ...... 138 Configuring an OC4J Instance ...... 138 Deploying workspace.war ...... 139 Using Oracle Enterprise Manager ...... 139 Using Oracle Distributed Configuration Management Command Line Utility ..... 140 Configuring Workspace ...... 140 Enabling SAP as an Authentication Provider ...... 140 Creating context.properties ...... 141 Updating Configuration Files ...... 142 Modifying portlet.xml ...... 143 Deploying Financial Reporting ...... 143 Creating an OC4J Instance ...... 144 Configuring a FinancialReporting OC4J Instance ...... 144
viii Contents Deploying HReports.ear ...... 146 Using Oracle Enterprise Manager ...... 146 Using Oracle Distributed Configuration Management Command Line Utility . . 147 Deploying Web Analysis ...... 147 Creating an OC4J Instance ...... 147 Configuring the WebAnalysis OC4J Instance ...... 148 Environment Variables ...... 149 Deploying WebAnalysis.ear ...... 150 Using Oracle Enterprise Manager ...... 150 Using Oracle Distributed Configuration Management Command Line Utility ..... 150 Configuring Oracle HTTP Server for Oracle 10g Release 2 ...... 151 Configuring Reporting and Analysis ...... 151 Configuring Performance Management Architect or Planning ...... 152 Configuring Financial Management ...... 153 Defining Additional Parameters for Workspace ...... 153 Configuring Oracle Single Sign-On on Oracle 10g Release 2 ...... 154 Prerequisites ...... 154 Configuring the Oracle Application Server ...... 154 Configuring Shared Services ...... 157 Testing Module Availability ...... 157 Post Configuration Tasks ...... 158
Chapter 11. Manually Deploying into WebLogic 9.1 ...... 159 Prerequisites ...... 159 Preparing the Environment ...... 159 Deploying Workspace into WebLogic ...... 160 Creating a New Domain ...... 160 Modifying setDomainEnv.sh ...... 160 Deploying Workspace ...... 161 Modifying portlets.xml ...... 162 Post Deployment for Workspace ...... 163 Creating context.properties ...... 163 Deploying Financial Reporting into WebLogic ...... 163 Post Deployment for Financial Reporting ...... 164 Deploying Web Analysis into WebLogic ...... 164 Verifying Web Analysis Environment Variables ...... 164 Modifying setDomainEnv.sh ...... 165 Deploying Web Analysis ...... 166 Configuring a Web Server for WebLogic 9.1 ...... 166
Contents ix Configuring Apache HTTP Plug-in ...... 167 Configuring for Reporting and Analysis and Hyperion Applications ...... 167 Configuring for Performance Management Architect ...... 174 Configuring for Financial Management ...... 174 Configuring for Performance Scorecard ...... 175 Configuring for Planning ...... 176 Testing Module Availability ...... 176 Post Configuration Tasks ...... 177
Chapter 12. Manually Deploying into WebLogic 8.1 ...... 179 Prerequisites ...... 179 Creating WebLogic Domains ...... 179 Deploying Workspace into WebLogic ...... 180 Modifying startWebLogic.sh ...... 180 Deploying Workspace ...... 181 Modifying portlets.xml ...... 182 Post Deployment for Workspace ...... 183 Compiling JSP ...... 183 Creating context.properties ...... 183 Deploying Financial Reporting into WebLogic ...... 184 Deploying Web Analysis into WebLogic ...... 185 Web Analysis Environment Variables ...... 185 Deploying Web Analysis ...... 186 Configuring a Web Server for WebLogic 8.1 ...... 186 Configuring Apache ...... 186 Configuring with Reporting and Analysis and Hyperion Applications ...... 187 Configuring with Performance Management Architect with Apache Web Server ...... 194 Configuring with Financial Management with Apache Web Server ...... 194 Configuring with Performance Scorecard with Apache Web Server ...... 195 Configuring with Planning with Apache Web Server ...... 196 Testing Module Availability ...... 196 Post Configuration Tasks ...... 197
Chapter 13. Manually Deploying into WebSphere 6.1 ...... 199 Prerequisites ...... 199 Preparing the WebSphere Environment ...... 200 WebSphere ND ...... 200 WebSphere BASE/Express ...... 200 Add Virtual Host Definitions ...... 201
x Contents Deploying Workspace ...... 201 Creating a WebSphere Shared Library for SAP Authentication ...... 202 Assigning SAP_LIBRARY to Workspace ...... 202 Creating context.properties ...... 203 Modifying portlets.xml ...... 203 Configuring Workspace ...... 204 Deploying Financial Reporting ...... 205 Configuring Financial Reporting ...... 206 Deploying Web Analysis ...... 207 Deploying ...... 207 Environment Variables ...... 208 Creating a WebSphere Shared Library for SAP Authentication and Reporting ...... 209 Configuring Web Analysis ...... 209 Configuring a Web Server with WebSphere 6.1 Application Server ...... 210 Configuring Apache Server or IBM HTTP Server ...... 210 Configuring Financial Management with a Web Server ...... 213 Configuring Financial Management with Apache Web Server or IBM HTTP Server ...... 213 Testing Module Availability ...... 213 Post Configuration Tasks ...... 214
Chapter 14. Manually Deploying into WebSphere 6.0.2 ...... 215 Prerequisites ...... 215 Preparing the WebSphere Environment ...... 216 WebSphere ND ...... 216 WebSphere BASE/Express ...... 216 Add Virtual Host Definitions ...... 217 Deploying Workspace ...... 217 Creating a WebSphere Shared Library for SAP Authentication ...... 218 Assigning SAP_LIBRARY to Workspace ...... 219 Creating context.properties ...... 219 Modifying portlet.xml ...... 220 Configuring Workspace ...... 221 Deploying and Configuring Financial Reporting ...... 221 Deploying Web Analysis ...... 223 Deploying ...... 223 Environment Variables ...... 224 Creating a WebSphere Shared Library for SAP Authentication and Reporting ...... 225 Configuring Web Analysis ...... 226 Configuring a Web Server with WebSphere 6.0.2 Application Server ...... 226
Contents xi Configuring Apache Server or IBM HTTP Server ...... 227 Configuring Financial Management with a Web Server ...... 229 Configuring Financial Management with Apache Web Server or IBM HTTP Server ...... 229 Testing Module Availability ...... 230 Post Configuration Tasks ...... 230
Chapter 15. Manually Deploying into Sun Java System Application Server Enterprise Edition 8.1 05Q4 ..... 231 Prerequisites ...... 231 Creating a Node Agent ...... 231 Creating a New Standalone Server Instance ...... 232 Customizing a Standalone Server Instance ...... 233 Editing Standalone Server Instance JVM Options for Workspace ...... 235 Editing Standalone Server Instance JVM Options for Financial Reporting ...... 236 Financial Reporting Environment Variables ...... 236 Editing Standalone Server Instance JVM Options for Web Analysis ...... 237 Web Analysis Environment Variables ...... 238 Deploying the Workspace Web Application ...... 238 Creating context.properties ...... 239 Deploying the Financial Reporting Web Application ...... 240 Deploying the Web Analysis Web Application ...... 240 Post Deployment for Web Analysis Enterprise Applications ...... 241 Testing Web Applications ...... 241 Generating the JES Load Balancing Plug-in Configuration File ...... 242 SunOne Web Server 6.1 Configuration ...... 243 Automatically Installing the Load Balancing Plugin ...... 243 Manually Installing the Load Balancing Plug-in ...... 244 Configuring the Load Balancing Plug-in ...... 244 Create NameTrans Entries for Static Workspace Content ...... 245 Default Sun Java Enterprise Application Server Locations ...... 246 Testing Module Availability ...... 246 Post Configuration Tasks ...... 247
Appendix A. ActiveX ...... 249 Whitepaper ...... 249 Sample Policy File ...... 250
Index ...... 253
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 128
● Oracle 10g Release 2:“Configuring Oracle HTTP Server for Oracle 10g Release 2” on page 151
● SUN Java System Application Server Enterprise Edition: Chapter 15, “Manually Deploying into Sun Java System Application Server Enterprise Edition 8.1 05Q4 ”
● WebLogic 9.1: “Configuring a Web Server for WebLogic 9.1” on page 166
● WebLogic 8.1: “Configuring a Web Server for WebLogic 8.1” on page 186
● WebSphere 6.1: “Configuring a Web Server with WebSphere 6.1 Application Server” on page 210
● WebSphere 6.0.2: “Configuring a Web Server with WebSphere 6.0.2 Application Server” on page 226
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.
Reporting and Analysis Architecture 17 Because most of these services are replicable, you may encounter multiple instances of a service in a system.
Core Services Core Services are mandatory for authorization, session management, and document publication:
● Repository Service—Stores Hyperion system data in supported relational database tables, known collectively as the repository. 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
18 Reporting and Analysis Architecture Overview 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:
❍ 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
Reporting and Analysis Architecture 19 Financial Reporting Batch reports in the Reporting and Analysis repository and imports data into Interactive Reporting documents (.bqy) as Results sections.
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.
20 Reporting and Analysis Architecture Overview Services Tier Summary
LSC or RSC Service Type Name Instances
LSC Core Authentication Service Multiple
Core Authorization Service Multiple
Core Global Service Manager 1 per system
Core Local Service Manager Multiple
Core Publisher Service Multiple
Core Session Manager Multiple
Impact Management Assessment (Harvester) Service Multiple
Impact Management Update (Transformer) Service Multiple
Interactive Reporting Extended Access for Hyperion Interactive Reporting Service Multiple
Interactive Reporting Extended Access for Hyperion Interactive Reporting Service Multiple
Interactive Reporting Hyperion Interactive Reporting Data Access Service Multiple
Interactive Reporting Hyperion Interactive Reporting Service Multiple
Management Logging Service 1 per system
Management Usage Service Multiple
RSC Core Name Service 1 per system
Core Repository Service Multiple
Core Service Broker Multiple
Functional Event Service 1 per system
Functional Job Service Multiple
Assistive Hyperion Common Administration Services Shared Services 1 per system
Financial Reporting Servers Financial Reporting Communication Server
Financial Reporting Servers Financial Reporting Print Server Multiple
Financial Reporting Servers Financial Reporting Scheduler Server
Financial Reporting Servers Financial Reporting Server Multiple
Performance Scorecard Services Scorecard Module Services
SQR Production Reporting Service SQR Production Reporting Service Multiple
Smart View Services Oracle's Hyperion® Smart View for Office Services Multiple
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 ...... 37 Browser Settings ...... 39 Module-specific Prerequisites ...... 39 Installing Considerations ...... 40 Port Numbers Used by Hyperion Products...... 43
Hyperion no longer ships or requires Oracle's Hyperion® License Server™ (or standalone 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 home 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 29
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: DB2DIR\java\db2java.zip. 8 Set all necessary environment variables: Set DB2COMM, DB2INSTANCE, DB2DIR, and:
● Solaris, Linux—LD_LIBRARY_PATH
● AIX—LIBPATH
● HP-UX—SHLIB_PATH
Note: Connectivity to IBM DB2 on AIX 5.2 may fail if the installation is done on a remotely mounted location (a directory location mounted over the network). To resolve this issue, copy recursively the
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.
● Open odbc.ini file and add for DB2 UDB:
Collection= Location=
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.
Preparing an RDBMS for the Reporting and Analysis Repository 27 ➤ To configure Microsoft SQL Server for use with Reporting and Analysis: 1 Set up the database within your RDBMS. If a database device lacks sufficient disk space to store the Reporting and Analysis metadata, create a database device, using a command line or Enterprise Manager: DISK INIT NAME = 'logical_name', PHYSNAME = 'absolute_dir_path_and_file_name', VDEVNO = virtual_device_number, SIZE = size_in_2k_pages go
2 Create a database in which to store the metadata. CREATE DATABASE biplus ON device_name = size_in_MB go 3 Create a database user account for Reporting and Analysis. A user must be created. This user owns the Reporting and Analysis database tables and objects that are built and populated during this installation. The user created here is also the user that Reporting and Analysis services use to connect to the database. Hyperion suggests naming the user biplus.
Note: The Reporting and Analysis repository database user cannot be an administrator, nor can it be a user who is assigned the System Administrators role. 4 Create the Microsoft SQL Server login: sp_addlogin biplus, password mypassword go
Note: The password for the Microsoft SQL Server repository database should not be null. 5 Create the database user: use biplus go sp_adduser biplus go 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
28 Planning the Installation 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. 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';
Preparing an RDBMS for the Reporting and Analysis Repository 29 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:
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.
30 Planning the Installation 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 5 Set the necessary environment variables:
● ORACLE_HOME
● PATH
● Solaris/Linux—LD_LIBRARY_PATH
● AIX— LIBPATH
● HP—SHLIB_PATH ORACLE_HOME identifies the location of the Oracle database software.
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 57. 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:
Preparing an RDBMS for the Reporting and Analysis Repository 31 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) ) 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
32 Planning the Installation 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 Online documentation to configure the data source:
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:
● 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, place the SAP JCo binaries in
● com.sap.security.core.jar
Obtaining and Preparing Pre-requisite Software 33 ● 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 If you are using the IBM WebSphere application server, it is recommended that you use the same account to install, deploy, and execute Hyperion products you use to install WebSphere. Using the same account ensures that the Hyperion Configuration Utility can successfully deploy Hyperion products to WebSphere.
Note: When accessing Essbase, the Financial Reporting or Web Analysis user who starts the Hyperion Web Applications needs to have read and write access to the Essbase.id file. The Essbase.id file is created in the home directory of the user owning the application server process(es). For information on the Essbase.id file, see the Essbase documentation.
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: 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.aix.2047.tar. 2 Run gskit.sh as the root user.
Configuring X11 for UI Services for Financial Reporting and Web Analysis To perform chart generation, the Reporting and Analysis UI Services require access to a graphics display device, either real or virtual. It is recommended that an X virtual frame buffer (Xvfb) be used instead of a hardware graphics display device, as Xvfb performs all operations in memory and does not require that any screens or input devices be attached to the machine.
34 Planning the Installation AIX 5L
➤ To enable Xvfb for AIX 5L: 1 Log on to the computer that will run the Reporting and Analysis UI Services components as the root user. 2 Determine whether Virtual Frame Buffer support is available on your computer by issuing the following command: lslpp -l X11.vfb 3 If X11.vfb is not installed, install it from your AIX installation media. After installing the package, apply the latest PTF from: http://techsupport.services.ibm.com/rs6k/fixdb.html
Note: See Chapter 6 - The X Virtual Frame Buffer and Softgraphics at: http://www.redbooks.ibm.com/ redbooks/SG245130.html. 4 Start Xvfb: /usr/bin/X11/X –force –vfb :1 &
where :1 is the a display number not already in use.
Solaris 9
➤ To enable Xvfb for Solaris 9: 1 Log on to the computer that will run the Reporting and Analysis UI Services components as the root user. 2 Obtain and compile the X11R6 source distribution from: ftp://ftp.x.org, or obtain and install the binary distribution from ftp://www.ferret.noaa.gov/ special_request/xvfb/solaris 3 Start Xvfb: /usr/X11R6/bin/Xvfb :1 -screen 0 1152x900x8 & where :1 is the a display number not already in use.
Solaris 10
➤ To enable Xvfb for Solaris 10: 1 Log on to the computer that will run theReporting and Analysis UI Services components as the root user. 2 Determine whether Virtual Frame Buffer support is available on your computer by issuing the following command: pkgchk -l SUNWxwsrv 3 If SUNWxwsrv is not installed, install it from the Solaris installation media.
Obtaining and Preparing Pre-requisite Software 35 4 Start Xvfb: /usr/openwin/bin/Xvfb :1 > /dev/null 2>&1 & where :1 is the a display number not in use.
Red Hat Enterprise Linux Release 4
➤ To enable Red Hat Enterprise Linux Release 4: 1 Log on to the computer that will run theReporting and Analysis UI Services components as the root user. 2 Determine whether Virtual Frame Buffer support is available on your computer by issuing the following command: rpm -q xorg-x11-Xvfb
Note: If xorg-x11-Xvfb is not installed, install it from the Red Hat installation media or RHN Web site. 3 Start Xvfb: /usr/X11R6/bin/Xvfb :1 -screen 0 1152x900x8 & where :1 is the a display number not already in use.
HP-UX 11i
➤ To enable HP-UX 11i: 1 Log on to the computer that will run theReporting and AnalysisUI Services components as the root user. 2 Determine whether Virtual Frame Buffer support is available on your computer by issuing the following command: swlist -l product | grep 'Xserver cumulative patch' 3 Ensure that the patch level installed on your system corresponds with HP's recommended level (currently PHSS_31293). 4 Copy /etc/X11/X0screens to /etc/X11/X1screens, where 1 is a display number not already in use; for example: cp /etc/X11/X0screens /etc/X11/X1screens 5 Edit /etc/X11/X1screens by adding these lines to the end of the file:
ServerOptions ServerMode XVfb 6 Start Xvfb: nohup /usr/bin/X11/Xvfb :1 -screen 0 1024x800x8 \ -pn -fp /usr/lib/X11/fonts/misc -sp /etc/X11/SecurityPolicy & Where :1 is the display number not already in use.
36 Planning the Installation Setting the DISPLAY Variable Prior to starting the Reporting and Analysis UI Services components on UNIX, set the DISPLAY environment variable to an available physical or virtual (Xvfb) graphics device address; for example: DISPLAY=`hostname`:1.0 ; export DISPLAY
For the sake of convenience, it is recommended that DISPLAY be initialized automatically by editing theReporting and Analysis UI Services start scripts.
Note: Only the Financial Reporting and Web Analysis Reporting and AnalysisUI Services components require DISPLAY be set. The Workspace component does not require access to X11.
Tip: Display can be set for Financial Reporting by editing &_BIPLUS_HOME:/InstallableApps/ freporting_web.env
Web Environment The following topics describe pre-installation Web environment considerations:
● “Application Server Setting” on page 37
● “Configuring a Web Environment” on page 38
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.
Web Environment 37 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.
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.
38 Planning the Installation 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.
❍ 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 39
● “Financial Reporting Print Server” on page 40
● “Production Reporting” on page 40
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.
Browser Settings 39 Financial Reporting
Financial Reporting Print Server The Print Server only runs on Microsoft Windows. Refer to the Hyperion Reporting and Analysis - System 9 Installation Guide for Windows.
Environment Variables The following environment variables must be properly initialized in order to run Financial Reporting objects that include metadata containing non-English characters:
● LANG
● LC_ALL
● ESSLANG (if Essbase is used as a data source)
➤ To initialize, use login scripts, or edit:
● LANG, LC_ALL:
and
● ESSLANG:
Production Reporting The following requisites apply to Production Reporting
Relinking the Hyperion Production Reporting Server Executables A C compiler is required to relink the Production Reporting Server executables for all platforms except Sun Solaris. For the AIX platform, a C++ compiler is required. If you need an installed C++ compiler, you can download the required C++ components from the following locations. For AIX, go to: http://www-1.ibm.com/support/docview.wss?uid=swg24001174 No changes to the Production Reporting Server linking scripts are required.
Installing Considerations The following topics describe pre-installation installing considerations:
40 Planning the Installation ● “Satisfying Temporary Space Requirements” on page 41
● “Command Line Processor Considerations” on page 42
Satisfying Stack Size Limit The Reporting and Analysis installer requires 16384 Kb stack size limit. To verify current limit, execute limit command. To increase stack size value, execute limit stacksize 16384 command.
Satisfying Temporary Space Requirements The Reporting and Analysis installer requires 1 GB of temporary space.
➤ To specify the directory used to store temporary file created by the install process, pass the argument -is:tempdir. For example, $ ./
where
➤ To perform a GUI installation from a remote X session, you must ensure the launching user's DISPLAY variable is properly initialized, and that the remote X server is accepting connections. It is recommended that this be tested before launching the Reporting and Analysis install, by running xlogo, xclock, or other small X program. For example: On the remote X server machine, enable connectivity from a host: $ xhost +
On the server where you install Reporting and Analysis:
$ DISPLAY=
➤ To perform a console mode installation, pass the argument -console For example: # ./
Installing Considerations 41 Command Line Processor Considerations
● The InstallShield uses /var as temporary space. However, since most users don’t have a lot of space allocated there, Hyperion recommends redirecting the temporary space to a temporary directory where the installer can uncompress and run, for example: mkdir /home/user/tmp setup
UNIX Installation Mechanisms The installation program for Reporting and Analysis invokes a graphical user interface, by default. You must, therefore, have an X client available to perform the installation in graphical mode. If an X client is not available, the install can be run in console mode. Command prompt installer —see “Command Line Processor Considerations” on page 42.
Fonts Interactive Reporting Service must be configured with appropriate fonts to ensure that BQY documents in Workspace have a consistent look and feel with the Web Client. You must make Type1, TrueType, or OpenType fonts available to Interactive Reporting Service. The configured fonts must support characters for all intended languages. The Reporting and Analysis installer installs Andale WT font in
➤ To make Microsoft’s TrueType Web fonts available to Workspace: 1 Download the Microsoft TrueType Web fonts from: http://sourceforge.net/projects/corefonts/ or other source. 2 Create a directory to store the font files. 3 If using downloaded Microsoft fonts, extract each file (*.exe) into the newly created directory using the cabextract utility located in INSTALL_HOME/bin/, as below:
42 Planning the Installation 5 Add the fonts.dir directory to environment variable FONT_PATH, or add it to BQ_FONT_PATH environment variable inside
Updating the C++ Runtime Environment for AIX Interactive Reporting DAS, Financial Reporting and Web Analysis require an updated C++ runtime environment version on AIX 5L.
Note: To determine the current version of your C++ runtime environment, run "lslpp -l | grep xlC.aix50".(Use the correct C++ version).
➤ To obtain the update: 1 Go to the IBM technical support Web site: https://techsupport.services.ibm.com/server/aix.fdc?toggle=SEARCH 2 Enter the fileset, xlC.aix50.rte.6.0.0.7, or the PTF number, U489780, in the Search string field to locate the patch.
Creating a Reporting and Analysis User Account For Reporting and Analysis to properly operate, it must be able to run using a user account. For security purposes, Hyperion suggests creating a new, unique user account for Reporting and Analysis named biplus. You may use an existing user account, as long as you use the same one for all Reporting and Analysis installations. 1. Hyperion strongly recommends against installing Reporting and Analysis as a superuser to avoid a potential breach in system security. The Reporting and Analysis user account does not need root privileges.
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.
Port Numbers Used by Hyperion Products 43 44 Planning the Installation Installing Reporting and 3 Analysis
In This Chapter Prerequisites...... 45 Reporting and Analysis Installers...... 45 Reporting and Analysis Module Installers ...... 46 About Hyperion Home...... 47 Installing Reporting and Analysis...... 50 Running Silent Installations...... 51
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.
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 50.
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
Prerequisites 45 Installer Installer Description Executable Folder 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 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
46 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 -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 -Teradata: on Sun/ SPARC/Solaris and HP/PA-RISC/HP-UX
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.
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 value is stored in .hyperion.
Note: To ensure that all installers have the permissions required to modify the HYPERION_HOME location, Hyperion recommends that all Hyperion applications be installed under one HYPERION user account.
Hyperion Home Location The default location for Hyperion Home is $HOME/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.
About Hyperion Home 47 If the current installation is the first Hyperion installation on the computer, you can specify the location during installation.
Note: If the HYPERION_HOME directory is mounted on an NFS so that one HYPERION_HOME location is visible across multiple computers, Shared Services can be installed to only one computer. If you try to install Shared Services to an additional computer, the previous installation is detected.
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
JDBC JDBC files
JRE Java Runtime Environment files
lib common internal library files
loggers Files for external authentication logging
ODBC ODBC drivers
48 Installing Reporting and Analysis Folder Contents
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 updates the .hyperion.
➤ To change the Hyperion Home location: 1 Launch the migration utility:
● Choose a method:
❍ In XWindows, change to:
Then type migrationtool.sh.
❍ In a UNIX console, change to:
Then type migrationtool.sh -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, $HOME/Program Files is not acceptable.
About Hyperion Home 49 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 Set the X display: a. If using a remote X server, enable connectivity from the machine where the install is being run, or from all hosts; for example: $ xhost + b. On the server where you install Reporting and Analysis, set the DISPLAY environment variable. For example, using a Bourne compatible shell: $ DISPLAY=
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.
50 Installing Reporting and Analysis The Hyperion Home selection page is displayed. 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 Click Next. The Setup Type page is displayed. 13 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 45. To see the installers needed for each module, see Hyperion Reporting and Analysis Module Installers. 14 From the Summary screen, review the components selected for the install and click Next. The wizard installs the Reporting and Analysis components. 15 After the installation is complete, the installation wizard may, under certain circumstances, prompt you to launch the 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.
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.
Running Silent Installations 51 2 From a command line, run a command: setup.bin —options—record
where
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.
52 Installing Reporting and Analysis Configuring Reporting and 4 Analysis
In This Chapter Hyperion Configuration Utility...... 53 Satisfying Initial Requirements ...... 54 Configuring Product Upgrades...... 54 Configuring Reporting and Analysis ...... 55 Completing Module-Specific Configurations ...... 63 Reconfiguring Products ...... 67 Testing Module Availability...... 68 Post Configuration Tasks...... 68 Error Messages When Testing Module Availability ...... 68 Post Configuration Tasks...... 69
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 54
● “Restricted Characters” on page 54
● “Troubleshooting” on page 54
Hyperion Configuration Utility 53 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: UNIX —
● 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.
54 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:
❍ Change to
❍ 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 56.
Configure Database a. Start the database. b. Select the database type. c. Enter the information in “Configuring Databases” on page 57.
Deploy to Application Server a. Start the application server. b. Select the application server, then an option:
Configuring Reporting and Analysis 55 Selection Task
● 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
ProductHome>/
WebLogic 8.1.x—
Completing Module Specific Configurations See “Completing Module-Specific Configurations” on page 63
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.
56 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 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 57 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”
● Chapter 15, “Manually Deploying into Sun Java System Application Server Enterprise Edition 8.1 05Q4 ”
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.
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.
58 Configuring Reporting and Analysis Caution! IBM WebSphere: Install, deploy, and execute Hyperion products using the account you used to install WebSphere.
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”
❍ Chapter 15, “Manually Deploying into Sun Java System Application Server Enterprise Edition 8.1 05Q4 ”
Table 6 Automatic Deployment Parameters
Field Description
Location Path to the application server installation directory and examples:
● WebSphere Base:
/opt/WebSphere/AppServer ● WebSphere Express:
/opt/IBM/WebSphere/Express51/AppServer ● WebLogic 8.1.x:
Configuring Reporting and Analysis 59 Field Description
/opt/bea/weblogic81 ● WebLogic 9.1.x:
/opt/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 60.
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 60.
BEA Home (WebLogic) Path to the BEA Home directory (e.g.,/opt/)
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:
Note: It is not recommended to change other parameters in this file.
60 Configuring Reporting and Analysis 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 55. 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 62 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
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.
Configuring Reporting and Analysis 61 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:
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.
Table 7 Web server Plug-in Automatic:
Apache IBM
Web Logic9.1 Yes
WebLogic 8.1 Yes
WebSphere 6.1 Yes Yes
WebSphere 6.0 Yes Yes
Tomcat Yes
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 Manual Support:
Apache IBM Oracle HTTP Server
JES
Oracle “ <_sfe:CrossReferenceTitle>Manually Configuring Oracle HTTP Server ” on page 00
WebLogic 9.1 Configuring Apache
WebLogic 8.1 Configuring Apache
62 Configuring Reporting and Analysis Apache IBM Oracle HTTP Server
WebSphere 6.1 “Configuring Apache “Configuring Apache Server or IBM HTTP Server or IBM HTTP Server” on page 210 Server” on page 210
WebSphere 6.0 Configuring Apache or Configuring Apache or IBM IBM
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 63
● “Specifying the GSM Host and Port ” on page 63
● “Customizing Service Ports for Reporting and Analysis ” on page 64
● “Configuring the SQR Production Reporting Engine for Interactive Reporting” on page 64
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.
Completing Module-Specific Configurations 63 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:
● 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.
64 Configuring Reporting and Analysis Financial Reporting Configurations
● “Enabling the Planning ADM Driver” on page 65
● “Workspace, Print Server, and Scheduler Server Configurations” on page 66
● “Report Server Configuration” on page 66
Enabling the Planning ADM Driver
● “Enabling Planning 9.3.1” on page 65
● “Enabling Planning Details 9.2.0.x / 9.3.0.x” on page 65
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 Essbase Runtime Client (RTC) on the Reporting and Analysis machines. Refer to the Hyperion Planning Installation Guide. 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=
Completing Module-Specific Configurations 65 5 Restart Financial Reporting.
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
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.
66 Configuring Reporting and Analysis 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:
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.
Reconfiguring Products 67 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
Post Configuration Tasks To finish the configuration, see “Post Configuration Tasks” on page 69.
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.
68 Configuring Reporting and Analysis ➤ 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
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.
Post Configuration Tasks 69 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
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.
70 Configuring Reporting and Analysis 3 Edit %OPENJMS_HOME%\bin\setenv.bat: rem Configures the JDBC driver set JDBC_PATH=
where
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:
Post Configuration Tasks 71 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://
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.
72 Configuring Reporting and Analysis 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
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.
Post Configuration Tasks 73 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. 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:
74 Configuring Reporting and Analysis 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 75.
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 the processes in
Note: The user running this script must have job scheduling permissions.
Starting Shared Services
Post Configuration Tasks 75 ➤ 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:
where Shared Services has been deployed to instance “
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 the Tomcat application server, confirmation messages are logged to
76 Configuring Reporting and Analysis When Shared Services is deployed to WebLogic 8.1.x, if the log level is not set to WARN, the confirmation message is logged to
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.
Display of the Oracle's Hyperion® Shared Services User Management Console login page indicates that the Shared Services server started successfully.
Stopping Shared Services
➤ 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:
Post Configuration Tasks 77 Application Server Path to Script To start OC4J instance:
Apache Tomcat
2 On WebLogic, if a message that suggests using the FORCESHUTDOWN command is displayed, use the FORCESHUTDOWN command to stop Shared Services server: 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.
Configuring Production Reporting Post Configuration Tasks This section describes the post configuration tasks for Production Reporting:
● Setting the environment variables
● Recreating the executables
Setting up the Environment Variables You run a script to set the environment variables. The scripts are in specified database folders.
➤ To configure the environment variables, locate the environment scripts in the following directories:
where db_name is the name of the database. The following databases are supported: Sybase, Oracle, Informix, DB2, ODBC, DDO, and Teradata.
● For all databases, the following script configures the basic environment variables:
❍ For C Shell: source setenv.csh
❍ For Bourne or Korn Shell: setenv.sh
● For the DDO database, the following script configures additional environment variables:
78 Configuring Reporting and Analysis ❍ For C Shell: source setjre.csh
❍ For Bourne or Korn Shell: setjre.sh
Recreating the Executables You must recreate the executables if the version of the operating system or database client software is different from when the original executables were created. You find the versions by using the following command line flag: -id
➤ To recreate the executables, type the following commands from a shell:
cd hyperion/BIPlus/bin/SQR/Server/db_name/lib ./sqrmake
where db_name is the name of one of the following database names: Sybase, Oracle, Informix, DB2, ODBC, DDO, or Teradata.
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 79 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.
80 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 81 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:
82 Configuring Reporting and Analysis
Post Configuration Tasks 83
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
84 Configuring Reporting and Analysis 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 "
Linux and Solaris: LD_LIBRARY_PATH=
HP-UX: SHLIB_PATH=
IBM AIX:
Post Configuration Tasks 85 LIBPATH=
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.
● 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.
86 Configuring Reporting and Analysis 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. 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.
Post Configuration Tasks 87 Setting up Workspace Web Application Parameters
➤ To setup Workspace Web Application parameters: 1 Start Servlet Configurator:
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.
88 Configuring Reporting and Analysis 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. 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 89 90 Configuring Reporting and Analysis Uninstalling and Reinstalling 5 Reporting and Analysis
In This Chapter Prerequisites...... 91 Deregistering Reporting and Analysis with Shared Services...... 91 Uninstalling ...... 92 Reinstalling...... 92
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.
● 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 55. 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 91 Uninstalling
Caution! During uninstall, the Reporting and Analysis directory is deleted.
➤ To uninstall Reporting and Analysis: 1 Start the Uninstall wizard by browsing to the following locations and clicking uninstall.bin:
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.
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.
92 Uninstalling and Reinstalling Reporting and Analysis 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:
● 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 93 94 Uninstalling and Reinstalling Reporting and Analysis Upgrading Reporting and 6 Analysis from 9.x to 9.3.1
In This Chapter Prerequisites...... 95 Upgrading...... 96 Migrating Users and Groups ...... 97 Upgrading Manually Deployed Web Applications...... 99
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 95
❍ 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
● Repservices
Note: Be sure that during the installation of the upgrades, you select an existing installation folder (not the new installation option).
96 Upgrading Reporting and Analysis from 9.x to 9.3.1 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 101.
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.
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.
Migrating Users and Groups 97 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 98
● “Using Provider Type Sun One LDAP Server” on page 99
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:
98 Upgrading Reporting and Analysis from 9.x to 9.3.1 c. Publish one or more objects in Workspace as UserA. d. Grant ACL of a few objects to UserA. e. Move this user from one OU to different OU. f. Run the utility and verify that this user's identity is updated in Reporting and Analysis table V8_CSS_UESR. The above Use Case may be extended for Groups as well.
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 98. 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. 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.
Upgrading Manually Deployed Web Applications 99 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 15, “Manually Deploying into Sun Java System Application Server Enterprise Edition 8.1 05Q4 ”
● 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.
100 Upgrading Reporting and Analysis from 9.x to 9.3.1 Installing the Reporting and 7 Analysis Migration Utility
In This Chapter Migration Utility ...... 101 Requirements...... 102 Supported Source Databases ...... 102 Installing the Migration Utility...... 103 After Installing the Migration Utility...... 104
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 101 ❍ 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
102 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 Untar the UNIX TAR file for your platform. 3 Close all Reporting and Analysis programs. 4 Launch the installation setup file:
● AIX systems—setupAixPlatform.bin
● HPUX systems—setupHpPlatform.bin
● Linux systems—setupLinuxPlatform.bin
● Solaris systems—setupSolarisPlatform.bin 5 The Reporting and Analysis 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.
Installing the Migration Utility 103 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. 15 To verify the installation, run the migrator.sh file in the folder where you installed the Migration Utility. For example:
After Installing the Migration Utility The Hyperion Migration Utility:
● Creates a 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
● Migration logs are placed in:
104 Installing the Reporting and Analysis Migration Utility Configuring a Web Server with 8 Apache Tomcat
In This Chapter Configuring Apache...... 105 Configuring IIS...... 109
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 105 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:
106 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 107 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
108 Configuring a Web Server with Apache Tomcat Configuring IIS
Note: IIS is included in this UNIX manual for the use case: Tomcat is on UNIX/Linux and client is using 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"
Configuring IIS 109 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
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
110 Configuring a Web Server with Apache Tomcat /workspace/ResourceProxy=Workspace /workspace/administration/*=Workspace /workspace/cdsrpc=Workspace /workspace/logon/*=Workspace /workspace/jobmanager/*=Workspace /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.
Configuring IIS 111 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. 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:
112 Configuring a Web Server with Apache Tomcat InsightInstaller ...\workspace_static\zeroadmin\component\Insight wsmedia ...\workspace_static\wsmedia WebAnalysis ...\WebAnalysis_static
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 113 114 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...... 115 Deploying Workspace Web Application...... 116 Deploying Financial Reporting...... 121 Deploying Web Analysis...... 124 Configuring Oracle HTTP Server for Oracle 10g Release 3 ...... 128 Configuring Oracle Single Sign-on on Oracle 10g Release 3...... 130 Testing Module Availability...... 134 Post Configuration Tasks...... 135
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 operating system user who owns the Oracle Application Server instance should be used to install Reporting and Analysis. If that is not possible, the
Prerequisites 115
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.
116 Manually Deploying into Oracle 10g Release 3 (10.1.3.1.0) Application 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=
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.
Deploying Workspace Web Application 117 Configuring Workspace
Enabling SAP as an Authentication Provider If Shared Services is configured to provide SAP authentication, Workspace must have the SAP Java and Native libraries added to its OC4J environment.
➤ To add SAP to Workspace OC4J environment: 1 With a text editor, open:
where
where
Creating context.properties
➤ To create context.properties: 1 With a text editor, create:
Where
118 Manually Deploying into Oracle 10g Release 3 (10.1.3.1.0) Application Server HFM=N HPS=N
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:
● 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
Deploying Workspace Web Application 119 Preference Change value to:
● Apache—19000 ● IBM HTTP Server—19000 ● Oracle HTTP Server—19000 ● IIS—80
foundation_port
● 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)
120 Manually Deploying into Oracle 10g Release 3 (10.1.3.1.0) Application Server replace $J(HYPERION_HOME) with your actual HYPERION_HOME location. For example: $HOME/Hyperion b. In the line: DEPLOYMENT_PATH=$J(servletConfig.deploymentPath)
replace $J(servletConfig.deploymentPath) with the actual location of deployed Workspace The default is:
Where
a. In the line: HYPERION_HOME=$J(HYPERION_HOME)
replace $J(HYPERION_HOME) with your actual HYPERION_HOME location. For example: $HOME/Hyperion b. In the line: BRIO_LIB=$J(trustedPass.installLib)
replace $J(trustedPass.installLib) with your actual
replace $J(trustedPass.deploymentHome) with the actual location of deployed Workspace application. The default is:
Where
Deploying Financial Reporting Copy .hyperion-
Deploying Financial Reporting 121 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.
➤ 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:
122 Manually Deploying into Oracle 10g Release 3 (10.1.3.1.0) Application Server -DHYPERION_HOME=
for example: -DHYPERION_HOME=/home/hys9/Hyperion -DBIPLUS_HOME=/home/hys9/Hyperion/BIPlus -DADM_HP_LIB=/home/hys9/Hyperion/ADM/Planning/9.3.1/lib
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 Add required library search path Environment Variable: a. Execute the script:
using the copied script output for its value; for example: LD_LIBRARY_PATH=
for example: HYPERION_HOME /home/hys9/Hyperion ESSLANG English_UnitedStates.Latin1@Binary
Deploying Financial Reporting 123 BIPLUS_HOME /home/hys9/Hyperion/BIPlus ARBORPATH /home/hys9/Hyperion/common/EssbaseRTC/9.3.1 ESS_ES_HOME /home/hys9/Hyperion/BIPlus/bin/EssbaseJAPI DISPLAY
See Configuring X11 for UI Services for Financial Reporting and Web Analysis for more information. See “Configuring X11 for UI Services for Financial Reporting and Web Analysis” on page 34. 11 Click Apply. 12 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: /home/BIPlus/InstalledApps/HReports.ear
Note: If the Web browser used to deploy the HReports.ear archive is not on the same machine where Reporting and Analysis was installed, you must use copy Location on Server. 4 Click Next to create a new deployment plan. 5 In Application Name, type FinancialReporting and click Next. 6 Click Deploy. 7 After successful deployment, restart the FinancialReporting OC4J instance.
Deploying Web Analysis
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.
124 Manually Deploying into Oracle 10g Release 3 (10.1.3.1.0) Application Server 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. 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
Deploying Web Analysis 125 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=/home/hys9/Hyperion -DBIPLUS_HOME=/home/hys9/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
where
See Configuring X11 for UI Services for Financial Reporting and Web Analysis for more information. See “Configuring X11 for UI Services for Financial Reporting and Web Analysis” on page 34.
Note: Select Append for PATH definition.
126 Manually Deploying into Oracle 10g Release 3 (10.1.3.1.0) Application Server 10 Add one more variable for library path, depending on operating system, where Hyperion Reporting and Analysis are running:
● Linux and Solaris: LD_LIBRARY_PATH=
● HP-UX: SHLIB_PATH=
● IBM AIX: LIBPATH=
Note: Select Append for PATH and LD_LIBRARY_PATH/SHLIB_PATH/LIBPATH definitions. 11 Click Apply. 12 Restart the OC4J Instance.
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:
Deploying Web Analysis 127
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: 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 128.
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 128
● “Configuring Financial Management” on page 130
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:
128 Manually Deploying into Oracle 10g Release 3 (10.1.3.1.0) Application Server http://httpd.apache.org/docs/2.0/mod/core.html#usecanonicalname. 2 Edit
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
Configuring Oracle HTTP Server for Oracle 10g Release 3 129 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:
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.
130 Manually Deploying into Oracle 10g Release 3 (10.1.3.1.0) Application Server Configuring the Oracle Application Server
➤ To configure Oracle Single Sign-On on Oracle 10g Release 3: 1 On the Identity Management host (where 10.1.3.1.0 is installed), set the ORACLE_HOME and ORACLE_SID environment variables. 2 On the Identity Management host, run the ssoreg script, using the -remote_midtier option. The file is located at: ORACLE_HOME/sso/bin/ssoreg.sh
For example: $ORACLE_HOME/sso/bin/ssoreg.sh -oracle_home_path $ORACLE_HOME \ -config_mod_osso TRUE \ -site_name BIPlus \ -remote_midtier \ -config_file $ORACLE_HOME/Apache/Apache/conf/osso/myosso.conf \ -mod_osso_url http://myhost.domain.com:19000
The resulting configuration file (myosso.conf in this example) is an obfuscated OSSO configuration file. 3 Copy the obfuscated OSSO configuration file to the 10g Release 3 (10.1.3) middle-tier instance. 4 On the middle-tier host, run the following script to complete the registration: ORACLE_HOME/Apache/Apache/bin/osso1013 config_file 5 Update Identity Management properties for Workspace: a. 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:
Configuring Oracle Single Sign-on on Oracle 10g Release 3 131 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
132 Manually Deploying into Oracle 10g Release 3 (10.1.3.1.0) Application Server
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:
Configuring Oracle Single Sign-on on Oracle 10g Release 3 133 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://
134 Manually Deploying into Oracle 10g Release 3 (10.1.3.1.0) Application Server Product URL* Expected Result
Financial Management http://
Planning http://
*URL: Where
Post Configuration Tasks To finish the configuration, see “Post Configuration Tasks” on page 69.
Post Configuration Tasks 135 136 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...... 137 Deploying Workspace Web Application...... 138 Deploying Financial Reporting...... 143 Deploying Web Analysis...... 147 Configuring Oracle HTTP Server for Oracle 10g Release 2 ...... 151 Configuring Oracle Single Sign-On on Oracle 10g Release 2...... 154 Testing Module Availability...... 157 Post Configuration Tasks...... 158
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 operating system user who owns the Oracle Application Server instance should be used to install Reporting and Analysis. If that is not possible, the
Prerequisites 137
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:
138 Manually Deploying into Oracle 10g Release 2 (10.1.2.0.2) Application Server
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. 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 139—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 140—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 2 Copy
Deploying Workspace Web Application 139 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:
140 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 141 ● 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:
142 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 Copy .hyperion-
Deploying Financial Reporting 143 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.
➤ 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
144 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. 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=/home/hys9/Hyperion -DBIPLUS_HOME=/home/hys9/Hyperion/BIPlus -DADM_HP_LIB=/home/hys9/Hyperion/ADM/Planning/9.3.1/lib
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 Add required library search path Environment Variable: a. Execute the script:
using the copied script output for its value; for example:
Deploying Financial Reporting 145 LD_LIBRARY_PATH=
Note: Enable Append for LD_LIBRARY_PATH/SHLIB_PATH/LIBPATH definitions. 8 Under Environment Variables, ad the following, substituting values in <> with actual locations: HYPERION_HOME
See Configuring X11 for UI Services for Financial Reporting and Web Analysis for more information. See “Configuring X11 for UI Services for Financial Reporting and Web Analysis” on page 34. for example: HYPERION_HOME /home/hys9/Hyperion ESSLANG English_UnitedStates.Latin1@Binary BIPLUS_HOME /home/hys9/Hyperion/BIPlus ARBORPATH /home/hys9/Hyperion/common/EssbaseRTC/9.3.1 ESS_ES_HOME /home/hys9/Hyperion/BIPlus/bin/EssbaseJAPI DISPLAY
Deploying HReports.ear There are two ways to deploy web-application to Oracle 10g Application Server: 1. “Using Oracle Enterprise Manager” on page 146—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 147—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.
146 Manually Deploying into Oracle 10g Release 2 (10.1.2.0.2) Application Server 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:
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.
Deploying Web Analysis 147 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.
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
148 Manually Deploying into Oracle 10g Release 2 (10.1.2.0.2) Application Server 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. 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
➤ To create Environment variables: 1 In the Oracle Enterprise Manager Console, Navigate to OC4J > WebAnalysis > Administration page of the Oracle Enterprise Manager’s 10g Web site and select Server Properties. 2 Click Add Environment Variable to add environment variable. 3 Add following Environment Variables, substituting values in <> with actual locations:
HYPERION_HOME=
where
● Linux and Solaris: LD_LIBRARY_PATH=
Deploying Web Analysis 149 ● HP-UX: SHLIB_PATH=
● IBM AIX: LIBPATH=
Deploying WebAnalysis.ear There are two ways to deploy web-application to Oracle 10g Application Server: 1. “Using Oracle Enterprise Manager” on page 150—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 150—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.
150 Manually Deploying into Oracle 10g Release 2 (10.1.2.0.2) Application Server 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
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 151
● “Configuring Performance Management Architect or Planning” on page 152
● ???
● “Defining Additional Parameters for Workspace” on page 153
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
Configuring Oracle HTTP Server for Oracle 10g Release 2 151 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
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
152 Manually Deploying into Oracle 10g Release 2 (10.1.2.0.2) Application Server 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: 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.
Configuring Oracle HTTP Server for Oracle 10g Release 2 153 ➤ To define additional parameters: 1 Open
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:
154 Manually Deploying into Oracle 10g Release 2 (10.1.2.0.2) Application Server $ORACLE_HOME/sso/bin/ssoreg.sh -oracle_home_path $ORACLE_HOME -site_name BIPlus -config_mod_osso TRUE -mod_osso_url http://
For validating registration and updating properties, login into the following SSO administration page:http://
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
Configuring Oracle Single Sign-On on Oracle 10g Release 2 155
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:
156 Manually Deploying into Oracle 10g Release 2 (10.1.2.0.2) Application Server 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 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 157 Product URL* Expected Result
Financial Management http://
Planning http://
*URL: Where
Post Configuration Tasks To finish the configuration, see “Post Configuration Tasks” on page 69.
158 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...... 159 Preparing the Environment...... 159 Deploying Workspace into WebLogic...... 160 Deploying Financial Reporting into WebLogic...... 163 Deploying Web Analysis into WebLogic...... 164 Configuring a Web Server for WebLogic 9.1...... 166 Testing Module Availability...... 176 Post Configuration Tasks...... 177
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 159 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.sh to WLS_DOMAIN>/bin/startWorkspace.sh. 4 Edit startWorkspace.sh 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.sh.
Modifying setDomainEnv.sh
➤ To modify setDomainEnv.sh: 1 Open:
160 Manually Deploying into WebLogic 9.1 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 161 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.
162 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 163 5 Click the correct drive and navigate to the newly created enterprise archive file:
where
Post Deployment for Financial Reporting
➤ To deploy the Financial Reporting Web application: 1 Execute:
Deploying Web Analysis into WebLogic This section describes how to deploy Web Analysis into WebLogic.
Verifying Web Analysis Environment Variables Verify:
ARBORPATH=
164 Manually Deploying into WebLogic 9.1 PATH=
ICU_DATA=
PRE_CLASSPATH=
One of the following:
● Linux and Solaris: LD_LIBRARY_PATH=
● HP-UX: SHLIB_PATH=
● IBM AIX: LIBPATH
Modifying setDomainEnv.sh
➤ To modify setDomainEnv.sh: 1 Open:
where
. /lhome/qa90/brn247/biplus/InstallableApps/config/wa_env.sh
CLASSPATH="${PRE_CLASSPATH}${CLASSPATHSEP}${WEBLOGIC_CLASSPATH}$ {CLASSPATHSEP}${POST_CLASSPATH}${CLASSPATHSEP}${WLP_POST_CLASSPATH}$ {CLASSPATHSEP}${WL_HOME}/integration/lib/util.jar" export CLASSPATH
Deploying Web Analysis into WebLogic 165 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. 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
166 Manually Deploying into WebLogic 9.1 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 167
● “Configuring for Performance Management Architect” on page 174
● “Configuring for Financial Management” on page 174
● “Configuring for Performance Scorecard” on page 175
● “Configuring for Planning” on page 176
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
Configuring a Web Server for WebLogic 9.1 167 KeepAliveSecs 20 WeblogicCluster
168 Manually Deploying into WebLogic 9.1 WeblogicCluster
Configuring a Web Server for WebLogic 9.1 169
170 Manually Deploying into WebLogic 9.1
Configuring a Web Server for WebLogic 9.1 171
172 Manually Deploying into WebLogic 9.1 SetHandler weblogic-handler PathTrim / KeepAliveEnabled ON KeepAliveSecs 20 WeblogicCluster
and add the lines: Include conf/HYSL-WebLogic.conf Alias /wsmedia "
Configuring a Web Server for WebLogic 9.1 173 ● “Configuring for Performance Management Architect” on page 174
● “Configuring for Financial Management” on page 174
● “Configuring for Performance Scorecard” on page 175
● “Configuring for Planning” on page 176 5 Test the plug-in by using a URL:
● Financial Reporting—http://
● Web Analysis—http://
● Workspace—http://
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 167, 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 167, step 1 through 4. 2 With a text editor, create:
174 Manually Deploying into WebLogic 9.1 with the following contents, replacing
ProxyRequests On 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 167, step 1 through 4. 2 Open:
Configuring a Web Server for WebLogic 9.1 175 where
Configuring for Planning
➤ To configure Planning with Apache Web Server: 1 See “Configuring for Reporting and Analysis and Hyperion Applications” on page 167, step 1 through 4. 2 Open:
where
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://
176 Manually Deploying into WebLogic 9.1 Product URL* Expected Result Analysis splash screen, and a new browser window should open.
Performance Management Architect http://
Financial Management http://
Planning http://
*URL: Where
Post Configuration Tasks To finish the configuration, see “Post Configuration Tasks” on page 69.
Post Configuration Tasks 177 178 Manually Deploying into WebLogic 9.1 Manually Deploying into 12 WebLogic 8.1
In This Chapter Prerequisites...... 179 Creating WebLogic Domains...... 179 Deploying Workspace into WebLogic...... 180 Deploying Financial Reporting into WebLogic...... 184 Deploying Web Analysis into WebLogic...... 185 Configuring a Web Server for WebLogic 8.1...... 186 Testing Module Availability...... 196 Post Configuration Tasks...... 197
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 179 ➤ 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.sh
➤ To modify startWebLogic.sh: 1 Navigate to and open startWebLogic.sh:
180 Manually Deploying into WebLogic 8.1 LIB_DIR=
PRE_CLASSPATH=
CLASSPATH=$LIB_DIR/iona63.jar:$LIB_DIR:${CLASSPATH}; export CLASSPATH
JAVA_OPTIONS="-Dorg.omg.CORBA.ORBClass=com.iona.corba.art.artimpl.ORBImpl -Dorg.omg.CORBA.ORBSingletonClass=com.iona.corba.art.artimpl.ORBSingleton"
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. The Workspace Web application is deployed.
Deploying Workspace into WebLogic 181 9 See “Configuring with Reporting and Analysis and Hyperion Applications” on page 187.
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
182 Manually Deploying into WebLogic 8.1 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
Note: Leave HPSU and ChangeMangement as Y.
Deploying Workspace into WebLogic 183 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:
➤ To configure the Financial Reporting Web application after deployment: 1 Execute:
where
184 Manually Deploying into WebLogic 8.1 Note: The setting of LD_LIBRARY_PATH should be performed in startWebLogc.sh after running
Deploying Web Analysis into WebLogic This section describes how to deploy Web Analysis into WebLogic.
Web Analysis Environment Variables Verify that
ARBORPATH=
PATH=
ICU_DATA=
One of the following:
● Linux and Solaris: LD_LIBRARY_PATH=
● HP-UX: SHLIB_PATH=
● IBM AIX: LIBPATH=
➤ To modify startWebLogic.sh: 1 Open:
Deploying Web Analysis into WebLogic 185 where
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 187
● “Configuring with Performance Management Architect with Apache Web Server” on page 194
186 Manually Deploying into WebLogic 8.1 ● “Configuring with Financial Management with Apache Web Server ” on page 194
● “Configuring with Performance Scorecard with Apache Web Server” on page 195
● “Configuring with Planning with Apache Web Server” on page 196
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.so file located in:
Solaris—
with the following contents, replacing
Configuring a Web Server for WebLogic 8.1 187 KeepAliveEnabled ON KeepAliveSecs 20 WeblogicCluster
188 Manually Deploying into WebLogic 8.1 KeepAliveSecs 20 WeblogicCluster
Configuring a Web Server for WebLogic 8.1 189 WeblogicCluster
190 Manually Deploying into WebLogic 8.1
Configuring a Web Server for WebLogic 8.1 191
192 Manually Deploying into WebLogic 8.1 SetHandler weblogic-handler PathTrim / KeepAliveEnabled ON KeepAliveSecs 20 WeblogicCluster
and add the following: Include conf/HYSL-WebLogic.conf Alias /wsmedia "
Configuring a Web Server for WebLogic 8.1 193 ● “Configuring with Performance Management Architect with Apache Web Server” on page 194
● “Configuring with Financial Management with Apache Web Server ” on page 194
● “Configuring with Performance Scorecard with Apache Web Server” on page 195
● “Configuring with Planning with Apache Web Server” on page 196 4 Restart the Apache HTTP Server.
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 187 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 187. 2 With a text editor, create
194 Manually Deploying into WebLogic 8.1
ProxyRequests On ProxyPreserveHost On 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 187. 2 Open:
where
Configuring a Web Server for WebLogic 8.1 195 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 187. 2 Open:
where
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://
196 Manually Deploying into WebLogic 8.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 69.
Post Configuration Tasks 197 198 Manually Deploying into WebLogic 8.1 Manually Deploying into 13 WebSphere 6.1
In This Chapter Prerequisites...... 199 Preparing the WebSphere Environment...... 200 Deploying Workspace...... 201 Deploying Financial Reporting...... 205 Deploying Web Analysis...... 207 Configuring a Web Server with WebSphere 6.1 Application Server...... 210 Testing Module Availability...... 213 Post Configuration Tasks...... 214
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.
Note: On UNIX systems, Reporting and Analysis need not be installed as root. Doing so, in fact, is discouraged.
Prerequisites 199 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.
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.sh to get to the wsadmin prompt and enter a command; for example: $AdminTask createApplicationServer myhostNode01 {-name freporting - templateName default }
Tip: You can use the wsadmin scripting host to interactively create a new server by passing the createApplicationServer task –interactive 3 Save changes using the wsadmin scripting client; for example: $AdminConfig save 4 Restart the default application server; for example, server1. 5 Start the new application server(s); for example, freporting, webanalysis, workspace.
200 Manually Deploying into WebSphere 6.1 Add Virtual Host Definitions If client machines will access Reporting and Analysis using a non-default HTTP port, such as 19000, the Reporting and Analysis default, the following procedure must be performed. Definitions must also be added for each application server transport.
➤ To add virtual definitions: 1 Log in to the WebSphere console for the profile containing your application servers. 2 Navigate to Environment->Virtual Hosts and click on default_host. 3 Click Host Aliases > New. 4 Specify the hostname or IP address of your Web server in Host Name, or * to allow access from any host. 5 Specify the HTTP port client machines will use to access Reporting and Analysis; for example, 19000. 6 Repeat the process to add each application server transport chain; for example, 9081, 9082, 9083.
Tip: Navigate to Application Servers >
Deploying Workspace
➤ To deploy: 1 Log in to the WebSphere console for the profile containing your application servers. 2 Navigate to Applications > Install New Application. 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.
Deploying Workspace 201 Note: Due to the large size of the Workspace application, it is expected that deployment may take several minutes to complete. Do not interrupt the deployment process. 8 Click Save to Master Configuration after deployment completes.
Creating a WebSphere Shared Library for SAP Authentication If Shared Services is configured to provide SAP authentication, Workspace must have the SAP Java and Native libraries added to its runtime environment.
➤ To create a WebSphere Shared Library: 1 Log in to the WebSphere Administrative Console. 2 In the left pane, navigate to Environment > Shared Libraries. 3 In the right pane choose the Server scope for Shared Libraries by clicking Browse Servers, and selecting Workspace. 4 Click 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.
202 Manually Deploying into WebSphere 6.1 Creating context.properties
➤ To create context.properties: 1 With a text editor, create:
Note: In the same directory, you can start with context.properties.sample. Uncomment and set the value for each property. 2 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:
Deploying Workspace 203 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.
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.
204 Manually Deploying into WebSphere 6.1 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 Add additional Generic JVM argument: -Djava.awt.headless=false 7 Click OK, then save all changes. 8 Start or restart the application server. 9 Edit
replace $J(HYPERION_HOME) with your actual HYPERION_HOME location. b. In the line: DEPLOYMENT_PATH=$J(servletConfig.deploymentPath)
replace $J(servletConfig.deploymentPath) with the actual location of deployed Workspace application. The default is:
Deploying Financial Reporting
➤ To deploy: 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.
Deploying Financial Reporting 205 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.
Configuring Financial Reporting
➤ To configure Financial Reporting: 1 Log in to the WebSphere Administrative Console. 2 Navigate to Session Management > Enable cookies for the application server instance where Financial Reporting is deployed. 3 Change the Cookie Path from / to /hr, then click OK. 4 Perform the following: a. If the Reporting and Analysis installation is owned by a different operating system user than owns WebSphere, copy the ${HOME}/.hyperion_
206 Manually Deploying into WebSphere 6.1 Note: These values may not be optimal for your user load, and may need to be adjusted. 8 Add additional Generic JVM argument: -Djava.awt.headless=false 9 Click OK, then save all changes. 10 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.
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.
Deploying Web Analysis 207 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
➤ To create Environment variables: 1 Log in to the WebSphere Administrative Console 2 In the left pane, navigate to Servers > Application Servers > Your WebAnalysis server. 3 In the right pane click Java and Process Management > Process Definition > Custom Properties. 4 Create the following Environment Variables by clicking New in the right pane: HYPERION_HOME=
BIPLUS_HOME=
ARBORPATH=
ICU_DATA=
And::
where
● HP-UX: SHLIB_PATH
● IBM AIX: LIBPATH
● Linux and Solaris: LD_LIBRARY_PATH 5 Click OK and then save all changes.
208 Manually Deploying into WebSphere 6.1 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 >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.
Deploying Web Analysis 209 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 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:
210 Manually Deploying into WebSphere 6.1
To:
Web Analysis: Change the URI group definition which contains this single line:
Configuring a Web Server with WebSphere 6.1 Application Server 211 To:
Web Analysis: Alias /WebAnalysis "
where
212 Manually Deploying into WebSphere 6.1 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
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 213 Product URL* Expected Result
Financial Management http://
Planning http://
*URL: Where
Post Configuration Tasks To finish the configuration, see “Post Configuration Tasks” on page 69.
214 Manually Deploying into WebSphere 6.1 Manually Deploying into 14 WebSphere 6.0.2
In This Chapter Prerequisites...... 215 Preparing the WebSphere Environment...... 216 Deploying Workspace...... 217 Deploying and Configuring Financial Reporting...... 221 Deploying Web Analysis...... 223 Configuring a Web Server with WebSphere 6.0.2 Application Server...... 226 Testing Module Availability...... 230 Post Configuration Tasks...... 230
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.
Note: On UNIX systems, Reporting and Analysis need not be installed as root. Doing so, in fact, is discouraged.
Prerequisites 215 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.
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.sh to get to the wsadmin prompt and enter a command; for example: $AdminTask createApplicationServer myhostNode01 {-name freporting - templateName default }
Tip: You can use the wsadmin scripting host to interactively create a new server by passing the createApplicationServer task –interactive 3 Save changes using the wsadmin scripting client; for example: $AdminConfig save 4 Restart the default application server; for example, server1. 5 Start the new application server(s); for example, freporting, webanalysis, workspace.
216 Manually Deploying into WebSphere 6.0.2 Add Virtual Host Definitions If client machines will access Reporting and Analysis using a non-default HTTP port, such as 19000, the Reporting and Analysis default, the following procedure must be performed. Definitions must also be added for each application server transport.
➤ To add virtual definitions: 1 Log in to the WebSphere console for the profile containing your application servers. 2 Navigate to Environment->Virtual Hosts and click on default_host. 3 Click Host Aliases > New. 4 Specify the hostname or IP address of your Web server in Host Name, or * to allow access from any host. 5 Specify the HTTP port client machines will use to access Reporting and Analysis; for example, 19000. 6 Repeat the process to add each application server transport chain; for example, 9081, 9082, 9083.
Tip: Navigate to Application Servers >
Deploying Workspace
➤ To deploy: 1 Log in to the WebSphere console for the profile containing your application servers. 2 Navigate to Applications > Install New Application. 3 Supply the full server path to workspace.war; by default:
Deploying Workspace 217 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.
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
a. In the line: HYPERION_HOME=$J(HYPERION_HOME)
replace: $J(HYPERION_HOME)
218 Manually Deploying into WebSphere 6.0.2 with your actual
replace $J(servletConfig.deploymentPath)
with the actual location of deployed Workspace application. The default is:
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
Deploying Workspace 219 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.
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
220 Manually Deploying into WebSphere 6.0.2 Preference Change value to
● 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 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.
Deploying and Configuring Financial Reporting 221 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. 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 Perform the following: a. If the Reporting and Analysis installation is owned by a different operating system user than owns WebSphere, copy the ${HOME}/.hyperion_
222 Manually Deploying into WebSphere 6.0.2 Solaris/Linux: LD_LIBRARY_PATH AIX: LIBPATH HP-UX: SHLIB_PATH e. Paste the value returned for the appropriate variable as returned by the
Note: These values may not be optimal for your user load, and may need to be adjusted. 8 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 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.
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: .
Deploying Web Analysis 223 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.
Environment Variables
➤ To create Environment variables: 1 Log in to the WebSphere Administrative Console 2 In the left pane, navigate to Servers > Application Servers. 3 In the right pane click Java and Process Management > Process Definition > Custom Properties. 4 Create the following Environment Variables by clicking New in the right pane: HYPERION_HOME=
BIPLUS_HOME=
ARBORPATH=
224 Manually Deploying into WebSphere 6.0.2 ICU_DATA=
One of the following:
● Linux and Solaris: LD_LIBRARY_PATH=
● HP-UX: SHLIB_PATH=
● IBM AIX: LIBPATH=
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
Deploying Web Analysis 225 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.
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.
226 Manually Deploying into WebSphere 6.0.2 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.
➤ 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:
Configuring a Web Server with WebSphere 6.0.2 Application Server 227
Web Analysis: Change the URI group definition which contains this single line:
To: 228 Manually Deploying into WebSphere 6.0.2 Name="/WebAnalysis/wa_javadocs" /> Web Analysis: Alias /WebAnalysis " where 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 Configuring a Web Server with WebSphere 6.0.2 Application Server 229 #ProxyRequests Off #For Oracle HTTP Server, the following line: ProxyPreserveHost On ProxyPass /hfm http://HFM_HOST:HFM_PORT/hfm ProxyPassReverse /hfm http:// where 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 Post Configuration Tasks To finish the configuration, see “Post Configuration Tasks” on page 69. 230 Manually Deploying into WebSphere 6.0.2 Manually Deploying into Sun 15 Java System Application Server Enterprise Edition 8.1 05Q4 In This Chapter Prerequisites...... 231 Deploying the Workspace Web Application ...... 238 Deploying the Financial Reporting Web Application...... 240 Deploying the Web Analysis Web Application...... 240 Testing Web Applications...... 241 Generating the JES Load Balancing Plug-in Configuration File ...... 242 Default Sun Java Enterprise Application Server Locations...... 246 Testing Module Availability...... 246 Post Configuration Tasks...... 247 Prerequisites Note: There is only a manual deploy option in the Hyperion Configuration Utility on JES in this release of Reporting and Analysis. It is required that you run the Oracle's 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. The Reporting and Analysis web application archives will be available in these locations: ● ● ● Creating a Node Agent This section describes necessary steps to create a new Node Agent. If you are going to use an existing Node agent instance, skip this section. Prerequisites 231 ➤ To create a Node agent from the command line: 1 If not already started, start the Sun Java System Application Server domain using the asadmin command line tool: ➤ To create a Node agent using the JES Admin Console: 1 Log into the JES Admin Console: https:// Note: Make sure you have enough free space in your default ➤ To start a Node Agent, execute the following command: Creating a New Standalone Server Instance It is recommended that you create a new Standalone Server instance for each Reporting and Analysis Web module you intend to deploy (Workspace, Financial Reporting, or Web Analysis). This recommendation is based on the assumption that JES administrators do not want all deployed applications to inherit JVM runtime settings that pertain only to Reporting and Analysis. Each Sun Java System Application Server instance has its own J2EE configuration, J2EE resources, application deployment areas, and server configuration settings. Changes to one application server instance have no impact on other application server instances. You can have many application server instances within one domain. If you deploy the Web Application to an existing server instance, skip this section. 232 Manually Deploying into Sun Java System Application Server Enterprise Edition 8.1 05Q4 You can use the JES Admin Console to create new a standalone server instance. The JES Admin Console provides Web-based management tools designed specifically for Sun Java System Application Server. Using the Web Console, you can monitor and configure the components of your Application Server installations. ➤ To create a new standalone Server Instance: 1 If not already started, start the Sun Java System Application Server domain using the asadmin command line tool Note: *The selected Node Agent must be started. If no Node Agents are available, create one. See “Creating a Node Agent” on page 231. Customizing a Standalone Server Instance The default Java security policy must be customized for each Reporting and Analysis module being deployed. For Workspace: Copy to Append the following lines to workspace_server.policy: grant { Prerequisites 233 permission java.util.PropertyPermission "*", "read,write"; permission java.lang.RuntimePermission "modifyThreadGroup"; permission java.lang.RuntimePermission "setIO"; permission java.security.SecurityPermission "getPolicy"; permission java.util.logging.LoggingPermission "control"; permission java.io.FilePermission "< For Financial Reporting: Copy to Append the following lines to fr_server.policy: grant { permission java.util.PropertyPermission "*", "read,write"; permission java.lang.RuntimePermission "modifyThreadGroup"; permission java.lang.reflect.ReflectPermission "suppressAccessChecks"; permission java.lang.RuntimePermission "setIO"; permission java.security.SecurityPermission "getPolicy"; permission java.util.logging.LoggingPermission "control"; permission java.io.FilePermission "< For Web Analysis: Copy grant { permission java.util.PropertyPermission "*", "read,write"; permission java.lang.RuntimePermission "getProtectionDomain"; permission java.lang.RuntimePermission "modifyThreadGroup"; permission java.security.SecurityPermission "putProviderProperty.SunJCE"; permission java.security.SecurityPermission "insertProvider.SunJCE"; permission java.security.SecurityPermission "putProviderProperty.Certicom"; permission java.security.SecurityPermission "insertProvider.Certicom"; permission java.lang.reflect.ReflectPermission "suppressAccessChecks"; permission java.lang.RuntimePermission "setIO"; 234 Manually Deploying into Sun Java System Application Server Enterprise Edition 8.1 05Q4 permission java.security.SecurityPermission "getPolicy"; permission java.util.logging.LoggingPermission "control"; permission java.io.FilePermission "< ➤ To disable directory browsing: 1 Edit Editing Standalone Server Instance JVM Options for Workspace ➤ To edit standalone server instance JVM options for Workspace: 1 Log into the JES Admin Console. 2 Navigate to Configurations > Prerequisites 235 Editing Standalone Server Instance JVM Options for Financial Reporting ➤ To edit standalone server instance JVM options for Financial Reporting: 1 Log into the JES Admin Console. 2 Navigate to Configurations > where Financial Reporting Environment Variables You must prepare the JVM environment with the necessary environment variables for Financial Reports to function correctly. Add the following lines after second line of ARBORPATH= See Configuring X11 for UI Services for Financial Reporting and Web Analysis. 236 Manually Deploying into Sun Java System Application Server Enterprise Edition 8.1 05Q4 Note: If you wish to define environment variables for specific applications you can update Note: Restart application server components after making the appropriate modifications. Editing Standalone Server Instance JVM Options for Web Analysis ➤ To edit standalone server instance server JVM options for Web Analysis: 1 Log into the JES Admin Console. 2 Navigate to Configurations > where where ● AIX—aix ● HP-UX—hpux ● Linux—linux ● Solaris—solaris 7 Click Save. 8 Open JVM Options tab. 9 Change the -Djava.security.policy argument to point to wa_server.poilcy created previously. 10 Click Save. Prerequisites 237 Note: Restart application server components after making the appropriate modifications. Web Analysis Environment Variables You must prepare the JVM environment with the necessary environment variables for WebAnalysis to function correctly. Add the following lines after second line of HYPERION_HOME= See “Configuring X11 for UI Services for Financial Reporting and Web Analysis” on page 34. Note: If you wish to define environment variables for specific applications you can update Note: Restart application server components after making the appropriate changes, where Deploying the Workspace Web Application ➤ To deploy the Workspace Web application: 1 Log into the JES Admin Console. 2 Select Applications > Web Applications and click Deploy. 3 Provide the server path to the following, and click Next. Note: *You can add one or more server targets. 238 Manually Deploying into Sun Java System Application Server Enterprise Edition 8.1 05Q4 Note: Ensure that you have write permission and enough free space in your Creating context.properties ➤ To create context.properties: 1 Create a file named context.properties in 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) ● Oracle's Hyperion® Performance Scorecard – System 9 (HPS) 3 Save: Deploying the Workspace Web Application 239 Deploying the Financial Reporting Web Application ➤ To deploy the Financial Reporting Web Application: 1 Log into the JES Admin Console. 2 Select Applications > Enterprise Applications and click Deploy. 3 Provide the server path to Note: *You can add one or more server targets. Note: Ensure you have write permission and enough free space in your Deploying the Web Analysis Web Application ➤ To deploy: 1 Log into the JES Admin Console. 2 To enable the deployment mode option: a. In the left pane choose Configurations > 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 7. 3 Select Applications > Enterprise Applications and click Deploy. 4 Provide the server path to 240 Manually Deploying into Sun Java System Application Server Enterprise Edition 8.1 05Q4 Note: *You can add one or more server targets. Note: Ensure you have write permission and enough free space in your Post Deployment for Web Analysis Enterprise Applications ➤ After deployment, perform these tasks: 1 Edit sun-web.xml: a. Open Testing Web Applications The new standalone server instance is initially in a stopped state. Before testing the deployed and configured application, you should start it via Admin Console. Testing Web Applications 241 ➤ To test the Web applications: 1 Log into the JES Admin Console. 2 Select the Stand-Alone Instances tab and select an option: ● WorkspaceServer ● Financialreportingserver ● WebanalysisServer 3 Click Start. You can access the Web Application directly from a browser by entering: Workspace: http:// where Generating the JES Load Balancing Plug-in Configuration File For each server (Workspace, Web Analysis, and Financial Reporting) you must generate a load balancer plug-in configuration file. ➤ To generate a load balancer plug-in configuration file: 1 Open the asadmin utility located in: 242 Manually Deploying into Sun Java System Application Server Enterprise Edition 8.1 05Q4 host-name> --port SunOne Web Server 6.1 Configuration Automatically Installing the Load Balancing Plugin The recommended procedure for configuring SunOne Web Server 6.1 for use with Sun JES 8.1 is as follows: ● Launch the Sun JES install program ● Select the Sun Web Server 6.1 component ● Select the Sun JES Load Balancing Plugin component ● Select Configure Now The Sun JES install program will automatically copy the required load balancing plug-in files and modify Sun Web Server's configurations files obj.conf and magnus.conf. Refer to http://docs.sun.com for more information. Generating the JES Load Balancing Plug-in Configuration File 243 Manually Installing the Load Balancing Plug-in In the following procedure, substitute <> denoted values with actual install locations. For example, on Solaris, ➤ To manually install the load balancing plug-in: 1 Navigate to : ● sun-loadbalancer_1_0.dtd ● sun-loadbalancer_1_1.dtd 2 Create these directories: Configuring the Load Balancing Plug-in ➤ To configure if the Load Balancing Plug-in was installed automatically by the JES install program: 1 Copy: change the value of the config-file= parameter so that it refers to 244 Manually Deploying into Sun Java System Application Server Enterprise Edition 8.1 05Q4 ➤ To configure if the Load Balancing Plug-in was installed manually: 1 Open ##BEGIN EE LB Plugin Parameters Init fn="load-modules" shlib=" Create NameTrans Entries for Static Workspace Content The Workspace module contains static HTML content that can be served by Sun Web Server 6.1, instead of JES, for improved performance. ➤ To create NameTrans entries for static Workspace content: 1 Open Generating the JES Load Balancing Plug-in Configuration File 245 NameTrans fn="pfx2dir" from="/wsmedia" dir=" Default Sun Java Enterprise Application Server Locations Sun Java Enterprise System default installations: ● Solaris:-/opt/SUNWappserver/appserver ● Linux:-/opt/sun/appserver/ ● Windows:-SystemDrive:\Sun\AppServer Sun Java Enterprise System default components locations: ● Domains directory: /var/opt/SUNWappserver/domains/ ● Node-agents directory: /var/opt/SUNWappserver/nodeagents/ ● Server's home directory: 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:// Oracle's Hyperion® Financial http:// Oracle's Hyperion® Web Analysis – http:// Performance Management Architect http:// 246 Manually Deploying into Sun Java System Application Server Enterprise Edition 8.1 05Q4 Product URL* Expected Result Financial Management http:// Planning http:// *URL: Where Post Configuration Tasks To finish the configuration, see “Post Configuration Tasks” on page 69. Post Configuration Tasks 247 248 Manually Deploying into Sun Java System Application Server Enterprise Edition 8.1 05Q4 A ActiveX In This Appendix Whitepaper ...... 249 Sample Policy File ...... 250 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 249 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" 250 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 251 252 ActiveX ABCDEFGHI J LMNOPRSTUVWX Index Hyperion License Server, 23 B database configuration, 57 backing up repositories, 23 upgrades, configuring, 54 BPM Architect, with Workspace Apache HTTP Plug-in A WebLogic 8.1, 194 browsers Active X settings, 39 description, 249 Web requirements, 37 sample policy file, 250 ADM driver, enabling the Planning driver, 65 Administrator User, provisioning, 78 C AJAX, 249 C++, updating, 43 Analytic Provider Services Driver, enabling characters, restricted, 54 enabling support for Financial Reporting, 66 command line Apache HTTP Plug-in, with Workspace installer, 42 BPM Architect processor considerations, 42 WebLogic 8.1, 194 configuration Financial Management database, 57 WebLogic 8.1, 194 deployment, 58 WebLogic 9.1, 174 deployment, profiles and domains, 60 Performance Scorecard prerequisites, 54 WebLogic 8.1, 195 product upgrades, 54 WebLogic 9.1, 175 Shared Services registration, 56 Planning restricted characters, 54 WebLogic 8.1, 196 task list, 53 WebLogic 9.1, 176 task sequence, 54 Apache HTTP Server Plug-in, with troubleshooting, 54 WebLogic 9.1, 167 configuration files application server Oracle 10g, manual deployment, 120 deployment, 58 Hyperion Configuration UtilityConfiguration Utility application server host names, specifying, 58 deployment, 58 Application Server setting, 37 description, 53 authentication prerequisites, 54 SAP data source, 33 reconfiguration, 67 Authentication Service, defined, 18 Shared Services registration, 56 Authorization Service, defined, 18 task sequence, 54 configuring database software for the Repository, 24 Index 253 ABCDEFGHI J LMNOPRSTUVWX IBM DB2, 24 Extended Access for Hyperion Interactive Reporting connections, ODBC, creating, 32 Service, 19 context path, customizing, 63 context.properties, for F WebLogic 8.1, manual deployment, 183 Financial Management WebLogic 9.1, manual deployment, 163 configuring with a Web server WebSphere 6.0.2, manual deployment, 219 WebSphere, 213, 229 WebSphere 6.1, manual deployment, 203 prerequisites, 39 cookie path, changing with Workspace WebSphere 6.1, manual deployment, 206 WebLogic 8.1, Apache HTTP Plug-in, 194 Core Services, 18 WebLogic 9.1, Apache HTTP Plug-in, 174 creating shared library for SAP authentication Financial Reporting WebSphere 6.0.2, 202, 218 configuring X11–xvfb, 34 customizing context path , 63 enabling the Planning ADM driver, 65 environmental variables, 40 D manual deployment databases JES, 240 configuration, 57 Oracle 10g, 143 creating users, 28 Oracle 10g Release 3, 121 repository size recommendations, 24 WebLogic 8.1, 184 supported in Migration Utility, 102 WebLogic 9.1, 163, 164 to store WebSphere 6.0.2, 221 metada, 28 WebSphere 6.1, 205 Oracle, 32 Print Server, 40 DB2COMM, 27 print service and scheduler, configure, 66 DB2DIR, 27 Report Server DB2INSTANCE, 27 configuration, 66 deployment, 58 Financial Reporting servers, defined, 20 deregistering Reporting and Analysis with Shared firewalls Services Web server installation and, 38 uninstalling and reinstalling, 91 firewalls, domains Interactive Reporting, 84 WebLogic 8.1, creating, 179 folders installed HYPERION_HOME directory, 47 E fonts and Interactive Reporting Service, 42 functional services, 19 environment variables, 78 JES and Financial Reporting, 236 requirements, 40 G UNIX, 31 Global Security Kit, for WebSphere Express Web Analysis installing, 34 Oracle 10 Release 2, 149 GSM WebLogic 9.1, 164 defined, 18 error logs, 54 GSM host and port, specifying, 63 Event Service defined, 19 H HTTP server 254 Index ABCDEFGHI J LMNOPRSTUVWX Apache with WebLogic 8.1, 187 L HTTP Server Plug-in launching Reporting and Analysis modules, 79 WebSphere 6.0.2, manual deployment LD_LIBRARY_PATH, 31 Web Analysis, 226 LIBPATH, 31 WebSphere 6.1, manual deployment license compliance, 23 Web Analysis, 210 license server in 9.3.1, 23 Hyperion Home, 47 load balancing plug-in Hyperion Interactive Reporting Data Access Service JES, 242 defined, 19 JES, configuring, 244 Hyperion Interactive Reporting Service JES, installing defined, 19 automatically, 243 HYPERION_HOME environment variable, 47 manually, 244 Logging Service I defined, 18 LSC services IBM DB2 defined, 17 configuring, 24 LSM, 18 troubleshooting, 24 with Web Analysis, 27 IIS Plug-in M Tomcat, 109 management services, 18 installation mechanisms, 42 Microsoft SQL Server installers login, 28 description by installer, 45 migrating users and groups, 97 description by modules, 46 Migration Utility installing, 50 installing, 101, 103 Interactive Reporting overview, 101 configuring Production Reporting engine for, 64 post installation, 104 Interactive Reporting Service requirements, 102 fonts, 42 supported databases, 102 irmconfig.xml migration, repository, 23 sample of, 82 modifying portlet service types used in, 82 Oracle 10g Release 3, 119 module installers, overview, 46 J module-specific configurations, 63 JDBC driver, and IBM DB2, 27 JES N manual deployment, 231 Name Service Financial Reporting environment variables, 236 defined, 18 server locations, 246 NameTrans entries web server configuration, 243 creating, 245 Job Service node agent, 231 defined, 19 JSP, compiling O in WebLogic 8.1, manual deployment, 183 OC4J instance Financial Reporting Oracle 10g Release 3, 122 Index 255 ABCDEFGHI J LMNOPRSTUVWX Web Analysis WebAnalysis.ear, 127 Oracle 10g Release 3, 124 Web server, 128 OC4J instance in Financial Management, 130, 153 Workspace, 116, 138 Reporting and Analysis, 128 OC4J instance, in Workspace Financial Reporting, 144 creating context.properties, 118 Web Analysis, 147 deploying, 116 ODBC connections, creating, 32 OC4J instance, 116 OHS routing for Workspace, 120 workspace.war, 117 Oracle Oracle 10g, manual deployment configuring, 29 OHS Routing for Workspace, 120 database storage, 32 Workspace Oracle 10g Release 2, manual deployment deploying, 138 Financial Reporting OC4J instance, 138 deploying, 143 Oracle Distributed Configuration Managemet HReports.ear, 146 Command Line Utility OC4J instance, 144 Oracle 10g Release 2, 147 prerequisites, 137 Oracle Enterprise Manager SAP as an authentication provider, 140 Oracle 10g Release 2, 146 Web Analysis Web Analysis, 150 deploying, 147 Oracle. 10g Release 3, manual deployment environment variables, 149 updating configuration files, 120 OC4J instance, 147 WebAnalysis.ear, 150 P Web server, 151 parameters additional parameters, 153 Oracle 10g Release 2, 153 Architect or Planning, 152 Performance Scorecard, with Workspace Reporting and Analysis, 151 Apache HTTP Plug-in Workspace WebLogic 8.1, 195 creating context.properties, 141 WebLogic 9.1, 175 OC4J instance, 138 Planning, enabling the ADM driver, 65 workspace.war, 139 Planning, with Workspace Oracle 10g Release 3 Apache HTTP Plug-in manual deployment WebLogic 9.1, 176 prerequisites, 115 WebLogic 8.1 single sign-onReporting and Analysis Apache HTTP Plug-in, 196 configuring Shared Services, 134 port numbers Oracle 10g Release 3, manual deployment, 115 changing Apache HTTP Server , 81 Financial Reporting Interactive Reporting Service, Job Service, Data deploying, 121 Access Service, 81 HReports.ear, 124 ranges in Interactive Reporting, 82 OC4J instance, 122 used by Hyperion products, 43 modifying portlet, 119 portlet.xml, modifying SAP as an authentication provider, 118 Oracle Release 2, 143 Web Analysis post deployment deploying, 124 WebLogic 8.1, Workspace, 183 OC4J instance, 124 privileges, granting, 28 256 Index ABCDEFGHI J LMNOPRSTUVWX Production Reporting functional, 19 configuring engine for Interactive Reporting, 64 summary, 21 recreating the executables, 79 Session Manager Service, 18 relinking server executables, 40 setDomainEnv.cmd, modifying, 160 server, configuring, 39 setting up setting up the environment variables, 78 environment variables, 78 provisioning an administrator, 78 shared library for SAP authentication Publisher Service, defined, 18 WebSphere 6.0.2, manual deployment Web Analysis, 225 R WebSphere 6.1, manual deployment Web Analysis, 209 reconfiguration, 67 Shared Services registration, Shared ServicesShared Services, 56 stopping, 77 registry.properties, 55 Single Sign-on reinstalling, 92 Oracle 10g Release 2, 154 Reporting and Analysis, 91, 92 Oracle Release 3 client, 93 manual deploy, 130 prerequisites, 91 Single sign-on Services, 92 Oracle 10g Release 3 UIServices, 93 configuring shared Services, 134 repository SiteMinder, with Transparent Logon backup, 23 Configuring Shared Serivces, 88 configuring database software, 24 Manually Creating the Web server config file, 85 databases, size recommendations, 24 Manually Creating the Web server Siteminder migration, 23 modules, 85 Repository Service policy server, configuring, 86 defined, 18 prerequisites, 84 requirements restarting components, 89 temporary space, 41 Trusted Password on the Authentication Service, Web browsers, 37 setting up, 88 restricted characters, 54 Workspace Web App parameters, 88 reviewing selected components, 51 space requirements, temporary, 41 SQL Server S configuring, 27 sample policy file, 250 standalone server instance SAP creating, 232 access and authentication, 33 customizing, 233 scheduler,Print server editing, 235 configuration, 66 startup secure sockets-capable servers, 38 commands Service Broker for Shared Services server, 76 defined, 18 startup dependencies service ports, customizing verifying, 75 Workspace, 64 startup, verifying for Shared Services, 76 services startWebLogic.bat, modifying, 180 Core, 18 stopping defined, 18 Shared Services, 77 Index 257 ABCDEFGHI J LMNOPRSTUVWX SyncCSSIdentity_BI utiltiy, 97, 98 deploying into WebLogic 8.1, 185, 186 deploying WebAnalyis.ear, 127 T IBM DB2, 27 WebLogic 9.1, manual deployment, 166 tables WebSphere 6.0.2, manual deployment, 223 manually creating, 31 configuring, 226 temporary space, requirements, 41 HTTP Server Plug-in, 226 testing module availabilty, 68, 134, 157, 176, 196, 213, shared library for SAP Authentication and 230, 246 reporting, 225 troubleshooting, 54 WebSphere 6.1, manual deployment, 207 configuring, 209 U HTTP Server Plug-in, 210 UI Services shared library for SAP Authentication and configuring X11–xvfb, 34 reporting, 209 uninstalling Web browsers requirements, 37 Reporting and Analysis, 91 Web environment prerequisites, 91 configuring, 38 uninstalling and reinstalling Web server deregistering Reporting and Analysis with Shared Oracle Release 2 HTTP Server, 151 Services, 91 Architect or Planning, 152 upgrades Reporting and Analysis, 151 configuring, 54 Oracle Release 3 HTTP Server upgrading manually deployed Web applications, 99 Financial Management, 130, 153 Upgrading paths supported, 95 Reporting and Analysis, 128 upgrading toReporting and Analysis 9.3.1, 95, 96 Oracle Release 3HTTP Server, 128 about SyncCSSIdentity_BI utiltiy, 97 Web server plug-in migrating users and groups, 97 Configuration Utility support, 62 running SyncCSSIdentity_BI utiltiy, 98 enabling, 61 upgrading to 9.3.1, prerequisites, 95 manual support, 62 Usage Service ports, specifying in Configuration Utility, 58 defined, 18 WebLogic user accounts, creating, 43 configuring User Management Console Financial Reporting, 184 launching, 77 single profiling, 60 user provisioning WebLogic 8.1 Migration Utility, 102 creating context.properties Workspace, 183 V deploying Web Analysis, 186 deploying Workspace, 181 verifying startup of Shared Services, 76 HTTP server virtual host definitions Apache, 187 WebSphere 6.0.2, 217 manual deployment, 179 WebSphere 6.1, 201 WebLogic 8.1 domains creating in manual deployment, 179 W WebLogic 8.1, manual deployment Web Analysis Web Analysis configuring X11–xvfb, 34 deployment, 185 258 Index ABCDEFGHI J LMNOPRSTUVWX Workspace, 180 completing configurations, 63 deploying, 160 customizing post deployment, 183 context path, 63 WebLogic 9.1 customizing service ports, 64 Apache HTTP Server Plug-in, 167 for WebLogic 8.1 WebLogic 9.1, manual deployment, 159 creating context.properties, 183 Financial Reporting, 163, 164 in Configuration Utility, 63 Web Analysis, 166 into WebLogic 8.1, 181 , 164, 166 post deployment environment variables, 164 WebLogic 8.1, 183 Workspace WebLogic 8.1, deploying, 180 post deployment, 163 WebSphere 6.0.2, 201, 217 WebSphere WebSphere 6.0.2, manual deployment, 221 single domain, 60 WebSphere 6.1, manual deployment, 204 WebSphere 6.0.2, manual deployment, 215 Workspace, configuring Apache HTTP Plug-in add virtual host definitions, 217 Planning context.properties, 219 WebLogic 8.1, 196 creating shared library for SAP authentication, WebLogic 8.1 202, 218 Financial Management, 194 Financial Reporting, 221 Performance Scorecard, 195 prepare WebSphere environment, 216 WebLogic 9.1 prerequisistes, 215 Financial Management, 174 Web Analysis, 223 Performance Scorecard, 175 configuring, 226 Workspace, configuring apache HTTP Plug-in HTTP Server Plug-in, 226 Planning shared library for SAP Authentication and WebLogic 9.1, 176 reporting, 225 Workspace, configuring HTTP Plug-in Workspace, 217, 221 BPM Architect WebSphere 6.1, manual deployment WebLogic 8.1, 194 add virtual host definitions, 201 configuring Financial Reporting, 206 X context.properties, 203 X11–xvfb Financial Reporting, 205 for UI Services prepare WebSphere environment, 200 AIX 5L, 35 prerequisistes, 199 for Financial Reporting and Web Analysis, 34 Web Analysis, 207 HP-UX 11i, 36 configuring, 209 Red Hat Enterprise Linux, 36 HTTP Server Plug-in, 210 Solaris 10, 35 shared library for SAP Authentication and Solaris 9, 35 reporting, 209 setting the display, 37 Workspace, 201, 204 WebSphere Express, IBM Global Security Kit installing, 34 Windows services, 60 starting, 75 Windows user accounts, creating, 43 Workspace Index 259 ABCDEFGHI J LMNOPRSTUVWX 260 Index