Oracle Hyperion Performance Scorecard Install

HYPERION® PERFORMANCE SCORECARD – SYSTEM 9
RELEASE 9.3.1
INSTALLATION GUIDE
Performance Scorecard Installation Guide, 9.3.1
Copyright © 1999, 2008, Oracle and/or its affiliates. All rights reserved.
Authors: Emily Hamer
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. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
About Performance Scorecard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
The Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
The Relational Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
The Application Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
HYPERION_HOME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Licensing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Chapter 2. Planning the Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

General Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Component Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Creating Installation Directories on UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Preparing Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Configuring the JVM on a Thai Locale . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Preparing the Application Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Preparing Application Server Clusters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Preparing to use Essbase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Chapter 3. Installing Performance Scorecard and Optional Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Installing Performance Scorecard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Installing Using the Installation Program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Chapter 4. Configuring Performance Scorecard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Hyperion Configuration Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Task Sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Restricted Characters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Satisfying Initial Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Reconfiguring Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Configuring Product Upgrades . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Configuring Performance Scorecard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Registering With Shared Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Contents iii
Configuring Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Deploying to the Application Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Deploying to Clusters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
What Happens During Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Finishing Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Satisfying Startup Dependencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Starting Shared Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Stopping Shared Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Starting Performance Scorecard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Chapter 5. Uninstalling Performance Scorecard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Chapter 6. Upgrading Scorecard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Chapter 7. Configuring Performance Scorecard for External Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . 39

External Authentication Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Configuring for External Authentication and Single Sign-On . . . . . . . . . . . . . . . . . . . . . . 40
Configuring Basic JDBC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Configuring NTLM Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Configuring LDAP or MSAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Configuring SiteMinder for Single Sign-On . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Creating a Web Resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Adding and Managing User Directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Modifying User Directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Deleting User Directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Configuring the Search Order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Configuring the Preferred Logging Priority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Configuring the Token Time-out . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Chapter 8. Setting up Projects and Provisioning Users in Shared Services . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Using External User Directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Creating and Provisioning Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Provisioning the Admin User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Provisioning and Synchronizing Shared Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Appendix A. Manual Application Server Deployment Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Deploying to a Single Application Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Deploying to WebLogic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Deploying to WebSphere . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Deploying to JES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
iv Contents
Deploying to Oracle 10.1.3.1.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Deploying to Clusters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Mapping the WebAppsConf Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Deploying to a WebSphere Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Deploying to a WebLogic Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Deploying to a JES Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Deploying to an Oracle 10G Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Deploying on a Thai Locale . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Using Tomcat . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Using WebLogic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Appendix B. Installing, Configuring, and Uninstalling Data Integration Management Adapters . . . . . . . . . . . . . 71

Data Integration Management Adapters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
About Installing Data Integration Management Adapters . . . . . . . . . . . . . . . . . . . . . . . . 71
Installing DIM Adapter for Performance Scorecard . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Installing in Silent Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Installing From a Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Configuring DIM Adapter for Performance Scorecard . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Registering With a Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Configuring Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Configuring JVM Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Uninstalling DIM Adapter for Performance Scorecard . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Uninstalling in Silent Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Uninstalling From a Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Contents v
vi Contents
Overview
1
In This Chapter
About Performance Scorecard ..................................................................................................... 7
The Installation ...................................................................................................................... 7
About Performance Scorecard

Oracle's Hyperion® Performance Scorecard – System 9 is a Web-based solution that helps your
organization translate its corporate strategy into actions, set goals, and monitor performance
using recognized performance management methodologies. To enable you to share data and
users, Scorecard is bundled with Oracle's Hyperion® Shared Services. See the Hyperion Shared
Services Installation Guide.
You can install these components with Performance Scorecard:
Table 1 Components You Can Install
Component Description Installation
Alerter Enables users to monitor performance Optional component with custom

by notifying them by E-mail when the installations. Deployed as a separate web
performance of objects such as application.
measures depart from an acceptable
range.
Import / Export Flat File Utility Enables users to import and export data Optional component with custom
using CSV files. Data is transferred in installations.
batch operations manually or using
See the Hyperion Performance Scorecard
schedules.
— System 9 Administrator's Guide.
The Installation
This topic explains the role of database, application server, and HYPERION HOME directory in
the installation. It also outlines licensing.
About Performance Scorecard 7

The Relational Database
Application and Alerter (if you install it) data is housed in an Oracle, MS SQL, or IBM DB2
relational database that you create. You connect to this database after installing Performance
Scorecard using Oracle's Hyperion® Configuration Utility™.
To update a database you are using with an existing release of Performance Scorecard, perform
the steps in “Upgrading Scorecard” on page 37 and then connect to the database during
configuration.
The Application Server

You can deploy Performance Scorecard as follows:
● Automatically to a single application server during configuration
● Manually to a single application server during and after configuration
● Manually to an application server cluster during and after configuration
A cluster is a series of servers (nodes) that work together to run Web applications quickly and
continuously. Deploying to a cluster enables applications to support a large number of users.
The settings in HPSConfiguration.properties determine how often data is shared and
synchronized between nodes. See the Hyperion Performance Scorecard — System 9
Administrator’s Guide.
HYPERION_HOME
When multiple Hyperion products are installed on one computer, common internal and third-
party components are installed to a central directory called HYPERION_HOME. The Hyperion
Home location is defined in the system environment variable called HYPERION_HOME.The
Hyperion Home value is stored in .hyperion.<hostname> in the home directory.
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.
Location
The default location for HYPERION_HOME C:\Hyperion$HOME/Hyperion.
If you have an existing HYPERION_HOME, this folder is used and cannot be modified until
after configuration.
8 Overview
Note:
If the HYPERION_HOME directory is mounted on an NFS used by multiple computers,
installShared Services only one computer.
See “Changing the HYPERION_HOME Location” on page 10.
Contents
The following folders and files are installed in the HYPERION_HOME\commonHYPERION_HOME/
common directory with Shared Services.
Table 2 HYPERION_HOME Contents
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
Opatch Oracle patching tool files; for future use
PERL Scripting language files
SAP SAP files
The Installation 9
Folder Contents
SharedServices Supporting files for Shared Services
utilities Utilities to change the location of Hyperion Home and export, import, or validate
provisioning data
XML Common XML components
Changing the HYPERION_HOME Location

You can change the default location of HYPERION_HOME after configuration using a
migration utility. The utility moves the directory contents and updates the value of the
HYPERION_HOME environment variable.
The utility updates the .hyperion.<host> file, which resides in the directory that contains the
environment variable. Login initialization files, such as .profile and .logi are not updated.
Note:
Apache Tomcat 5.0.28 on Windows: If you installed the Shared Services server as a Windows
service, the Shared Services server does not launch automatically if you change the
HYPERION_HOME location. To solve this issue, manually update the location of the Windows
service.
➤ To change the Hyperion Home location:

1 Launch the migration utility:
● Choose a method:
❍ Select Start > Programs > Hyperion > Foundation Services > Home Migration
Utility.
❍ Double-click the run.exe file from <HYPERION_HOME>\common\utilities
\HyperionHomeTool\9.3.1\bin.
❍ From a Windows console, change to <HYPERION_HOME>\common\utilities
\HyperionHomeTool\9.3.1\bin. Then type run.exe -console.
● Choose a method:
❍ In XWindows, change to <HYPERION_HOME>/common/utilities/
HyperionHomeTool/9.3.1/bin. Then type migrationtool.sh.
❍ In a UNIX console, change to <HYPERION_HOME>/common/utilities/
HyperionHomeTool/9.3.1/bin. Then type migrationtool.sh -console.
2 When prompted, enter or browse to the new location for Hyperion Home.
Do not use a directory that contains a space character. For example, C:\Program Files
$HOME/Program Files is unacceptable.
10 Overview
Licensing
Hyperion no longer uses Oracle's Hyperion® License Server™ or license files with Hyperion.
To comply with your license agreement, perform these tasks:
● Implement an auditing process.
● Activate only the features that you purchased during configuration.
See “Hyperion License Compliance” in the Hyperion Installation Start Here.
The Installation 11
12 Overview
Planning the Installation
2
In This Chapter
General Requirements ............................................................................................................13
Component Requirements ........................................................................................................13
General Requirements
For basic operating system, database, application server, and third-party tool requirements, see
the Hyperion Installation Start Here.
Component Requirements
This section describe tasks that you may have to perform to prepare your environment for
Performance Scorecard. See:
● “Creating Installation Directories on UNIX” on page 13
● “Preparing Databases” on page 14
● “Preparing the Application Server” on page 16
● “Preparing Application Server Clusters” on page 16
● “Preparing to use Essbase” on page 17
Creating Installation Directories on UNIX

Perform these tasks:
1. Ensure that you have root privileges to the computer on which you install Performance
Scorecard.
2. Create a directory for the installation files. This is the Performance Scorecard installation
directory.
3. Create a user and grant them write-access to these directories:
● Performance Scorecard installation
● Application server installation
● HYPERION_HOME
General Requirements 13
Preparing Databases
Perform these steps:
1. Perform one of these tasks:
● New users - Create a database and a user with administrative rights to the database.
● Existing users - Have the information required to connect to the database. You enter
this information during configuration.
2. Create a user in the database.
3. Grant rights that enable the user to create and insert seed data, and delete and update tables.
4. DB2 or Oracle: Grant the user administrator rights to the database.
5. Start the database server.
6. MS SQL: See “Preparing Microsoft SQL Server” on page 14.
7. IBM DB2: See “Preparing an IBM DB2 Database” on page 15.
Preparing Microsoft SQL Server

By default, the SQL Server assigns system administrator permissions to the user established as
the database owner. If this user later generates an Hyperion® System™ 9 BI+™ Enterprise
Metrics™ database of Performance Scorecard data, a naming conflict occurs. Names are
modified with dbo. For example, HPS.HPS_STAR_MEASURES is referenced as
dbo.HPS_STAR_MEASURES.
➤ To prevent the naming conflict:

1 Open the SQL Server Enterprise Manager and select your SQL Server.
2 Under Security, click Logins.
3 If you are upgrading a database, double-click the user that owns the database tables.
4 In SQL Server Login Properties, click Server Roles.
5 Clear System Administrators Server Role.
6 Click OK.
➤ To confirm that the user is the table owner in the Enterprise Manager tables list:
1 Expand the Databases folder.
2 Navigate to the database and expand its directory.
3 Click Tables.
The table list is displayed on the right.
4 Check the table list to confirm that the owner is properly assigned.
14 Planning the Installation

Preparing an IBM DB2 Database
➤ To prepare the IBM DB2 server:

1 Increase the database log size to 6500.
2 Modify this script with information specific to your database:
SET HPSDB=<hpsdatabase>
SET ADMIN=<adminusername>
SET ADMINPWD=<adminpassword>
SET TBSFILE=<table space file location>
SET TMPFILE=<temp file location>
DB2 CONNECT TO %HPSDB% USER %ADMIN% USING %ADMINPWD%
DB2 UPDATE DATABASE CONFIGURATION FOR %HPSDB% USING APPLHEAPSZ 512
DB2 CREATE BUFFERPOOL HPS_BP SIZE 250 PAGESIZE 32 K
DB2 TERMINATE
DB2STOP
DB2START
DB2 CONNECT TO %HPSDB% USER %ADMIN% USING %ADMINPWD%
DB2 CREATE REGULAR TABLESPACE HPS_SPACE1 PAGESIZE 32 K MANAGED BY SYSTEM
USING ('%TBSFILE%') EXTENTSIZE 32 OVERHEAD 24.1 PREFETCHSIZE 32
TRANSFERRATE 0.9 BUFFERPOOL HPS_BP
DB2 COMMENT ON TABLESPACE HPS_SPACE1 IS 'HPS Table Space'
DB2 GRANT USE OF TABLESPACE HPS_SPACE1 TO PUBLIC
DB2 CREATE SYSTEM TEMPORARY TABLESPACE HPS_TEMP PAGESIZE 32 K MANAGED BY
SYSTEM USING ('%TMPFILE%') EXTENTSIZE 32 OVERHEAD 24.1 PREFETCHSIZE 32
TRANSFERRATE 0.9 BUFFERPOOL HPS_BP DB2 COMMENT ON TABLESPACE HPS_TEMP IS
'HPS Temporary Table Space'
DB2 TERMINATE
DB2STOP
DB2
3 Save the file as <name>.bat.
4 From the Command Center, execute the script.
5 Windows 2003 users: Perform these steps:
a. Select Control Panel > Computer Management > Users and Groups.
b. On the User Accounts box, click Advanced.
c. Select DB2Admin, right-click and select Properties.
d. On the Properties box, select Member Of.
e. Select Users, click Remove and Save.
Configuring the JVM on a Thai Locale

The Thai locale is only supported with 1.4.1_xx of the JDK and JRE. If the application server is
installed on a computer with Thai settings, set up the Java Virtual Machine so that Performance
Scorecard runs internally in English/US locale. This maintains consistent dates in the application
database.
If you are using Tomcat, see “Manual Application Server Deployment Tasks” on page 55 after
configuring Performance Scorecard.
Component Requirements 15
Preparing the Application Server
To set up the application server, perform a task:
● WebSphere: If you will run multiple products on WebSphere, use the same account to install,
deploy, and run the product applications.
● Tomcat: Ensure that the CATALINA_HOME variable references the Tomcat installation
directory.
TIP: All default product default port numbers are in the Hyperion Installation Start Here.
Preparing Application Server Clusters

This section identifies tasks that you must perform to deploy to an application server cluster.
● “Creating Clusters” on page 16
● “Creating a Temporary Directory” on page 16
● “Preparing a WebLogic Cluster” on page 17
● “Preparing a WebSphere Cluster” on page 17
Creating Clusters
Perform these steps to create a cluster:
1. Create a cluster as described in your application server documentation.
2. Select one computer (managed server or node manager) to manage the others in the cluster.
3. Ensure that the servers in the cluster use the same port.
4. Windows: Set up a proxy server.
Note: Set up the computers using a static IP address. This ensures that the address will not
change after you install Performance Scorecard.
For information about creating clusters, see your application server documentation
Creating a Temporary Directory

Create a directory on the hard drive of all computers in the cluster to contain temporary files.
For example, C:\temp\hpstemp.
TIP: For better performance, create this directory on a high speed hard drive.
Preparing an Oracle Server Cluster

Perform these tasks before deploying to an Oracle cluster:
● Create a cluster as described in the Oracle Application Server Administrator's Guide.
● Install Performance Scorecard on all the computers in the cluster.

● Ensure that all instances of Performance Scorecard in the cluster are configured to use the
same database.
Preparing a WebLogic Cluster

To set up a WebLogic cluster:
1. Create a domain.
2. Select one computer in the cluster (managed server or node manager) that you use to manage
the cluster.
3. If you use a proxy server for load balancing, ensure that it is installed in the domain.
4. WebLogic 8.1.2: Perform these tasks:
a. Uninstall any existing releases of Performance Scorecard. See “Uninstalling
Performance Scorecard” on page 35.
b. Delete files that reference HPSWebReports and the Alerter from these directories:
● Microsoft Windows: <BEA_HOME>\user_projects\domains\<domain>\
myserver\.wlnotdelete\extract
● UNIX: <BEA_HOME>/user_projects/domains/<domain>/
myserver/.wlnotdelete/extract
Preparing a WebSphere Cluster

Perform these tasks to setup a WebSphere cluster:
1. Set up the hosts as nodes as described in your WebSphere documentation.
2. Ensure that WebSphere is installed on each node.
3. Ensure that you can access the WebSphere Network Deployment Manager and IBM Web
server.
Preparing to use Essbase

To use data from, or generate data to Oracle's Hyperion® Essbase® – System 9, perform these
tasks:
● Install the Essbase client.
● Ensure that the ARBORPATH variable references the Essbase installation directory.
● To later generate an Essbase database of Performance Scorecard data, install Essbase
Integration Services.
➤ To set up ARBORPATH:
1 Select Start > Settings > Control Panel.
2 Double-click Systems.
Component Requirements 17
3 On the System Properties box, select Advanced and then click Environment Variables.
4 In Systems Variables, select ARBORPATH.
5 If the incorrect path is shown, click Edit to modify the variable.

Installing Performance
3 Scorecard and Optional
Components
In This Chapter
Installing Performance Scorecard ................................................................................................19
You can install Performance Scorecard as follows:

● Using the installation program. See “Installing Using the Installation Program” on page
19.
● From an SMS distribution by converting the installation executable to a MSI file.
To upgrade a 9.2.0.3 or a 9.3.0.x release, see Chapter 6, “Upgrading Scorecard”.
Installing Performance Scorecard

This topic explains how to install Performance Scorecard and these optional components that
are available with a custom installation:
● Alerter
● Import / Export Flat File Utility
TIP: Use a custom installation to perform these tasks:
● Install only optional components, such as the Alerter.
● Return through the installation to select components that you forgot.
● Overinstall selected components.
To upgrade a 9.2.0.3 or a 9.3.0.x release, see Chapter 6, “Upgrading Scorecard”.
Installing Using the Installation Program

This topic describes how to install Performance Scorecard, the Alerter, and the Import / Export
Flat File Utility Tool.
➤ To install Performance Scorecard:

1 Start the Shared Services server. .
2 Close the browser.
Installing Performance Scorecard 19

3 Create a directory for the installation files.
4 Copy suite.jar and the file for your operating system from the DVD to directory you created.
If you downloaded the product files, copy and unpack the .zip,.tar, or .gz.
Operating System File
Microsoft Windows HPSsetupwin32.exe
Sun Solaris HPSsetupsolarisSparc.bin
AIX HPSsetupAIX.bin
HPUX HPSsetupHP11.bin
HPUX Itanium 64 HPSsetupHPIA64.bin
Linux HPSsetupLinux.bin
5 Run the .exe or .bin file.

Optional: To install using an SMS distribution, convert the installation executable to an .msi
file.
6 Select the language in which to install and click Next.
7 Click Next on the Welcome page.
8 Select your country from the list on the Country Selection panel.
9 Review the terms of the licence agreement and select I Agree.
10 Select the type of installation:
● To install optional components or overinstall components, select Custom.
● To install only Performance Scorecard, select Typical.
11 On the HYPERION_HOME panel, perform a task:
● Existing installation: Confirm that the HYPERION_HOME directory shown is correct. You
can modify the location after configuration.
● New installation: Accept the default HYPERION_HOME directory location or specify another
directory.
12 Click Next. The Product Installation window is displayed.
13 Accept the default installation directory or specify another directory, and click Next.
Note: To deploy to a cluster, install Performance Scorecard as follows:
● WebSphere: deployment manager\HPS\9.3.1\appserver\installedapps\WS
\version\manual\webapps
● WebLogic: <drive>\bea_home\appserver\InstalledApps\WebLogic\version
Installation summary information is displayed.
14 Select Launch Configuration Tool and click Finish.
20 Installing Performance Scorecard and Optional Components

15 Configure Performance Scorecard. See Chapter 4, “Configuring Performance Scorecard ”.
Installing Performance Scorecard 21

22 Installing Performance Scorecard and Optional Components
Configuring Performance
4 Scorecard
In This Chapter
Hyperion Configuration Utility .....................................................................................................23
Satisfying Initial Requirements ...................................................................................................24
Reconfiguring Products ...........................................................................................................24
Configuring Product Upgrades ....................................................................................................25
Configuring Performance Scorecard..............................................................................................25
Satisfying Startup Dependencies.................................................................................................31
Starting Performance Scorecard..................................................................................................33
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:
● 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.
● Alerter configuration — To enable users to receive E-mail notifications when the
performance of key metrics depart from an acceptable range, or when key tasks require
completion.
For information about the order of configuration tasks, acceptable characters, and resolving
configuration issues, see:
● “Task Sequence ” on page 24
● “Restricted Characters ” on page 24
● “Troubleshooting ” on page 24
Hyperion Configuration Utility 23

Task Sequence
Hyperion recommends that you configure products separately and perform all configuration
tasks. However, you can configure products simultaneously performing all, or specific,
configuration tasks.
Restricted Characters
Only enter alphanumeric, dash (-), dot (.) , underscores (_), and tildes (~) during configuration.
Tildes are only supported on Microsoft Windows. All other characters are not supported.
Troubleshooting
Terminating configuration for one product does not stop the configuration of other products.
All configuration warnings and errors are logged as follows:
Microsoft Windows — <HYPERION_HOME>\logs\config
UNIX — $HYPERION_HOME/logs/config
If you encounter errors, perform these tasks:
● 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 3 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
Reconfiguring Products
Hyperion Configuration Utility enables you to reconfigure products to incorporate changes in
your environment such as a different application server.
24 Configuring Performance Scorecard

To reconfigure, launch Hyperion Configuration Utility on the computer hosting the product,
and follow the procedures in this chapter.
Note:
Stop the server before reconfiguring products, and restart the server afterward.
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.
● 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.
See Chapter 6, “Upgrading Scorecard”.
Configuring Performance Scorecard

Run Hyperion Configuration Utility on the computer hosting the products to configure or
reconfigure.
➤ To configure Performance Scorecard:

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:
On Microsoft Windows:
❍ Select Start > Programs > Hyperion > Foundation Services > Configuration Utility.
❍ Double-click configtool.bat in: <HYPERION_HOME>\common\config.
❍ Change to <HYPERION_HOME>\common\config and type startconfigtool.bat
— console.
On UNIX:
❍ Change to <HYPERION_HOME>/common/config and type configtool.sh.
❍ Change to <HYPERION_HOME>/common/config and type configtool.sh —
console.
2 Select the language in which to configure and click Next.
Configuring Product Upgrades 25

3 On the Welcome page, click Next.
4 Select the products and the tasks to perform, then click Next.
5 Based on your selection, perform the following tasks, clicking Next between tasks.
Table 4 Configuration Tasks
Selection Task
Product Options First installation: This task is automatically selected, but does not require you to
perform any tasks. Reconfiguration: You can select this task, but will not need to
perform any tasks.
Shared Services Registration Enter the information in “Registering With Shared Services ” on page 27.
Configure Database a. Start the database.

b. Select the database type.
c. Enter the information in “Configuring Databases ” on page 28.
Tip: For simplicity, Hyperion recommends that you use the same, or the default,
database name (hypdb), username (hypuser), and password for all products that
you install.
Deploy to Application Server Tip: Hyperion recommends that you use the same application server, and domain
or profile.
a. Start the application server.
b. Select the application server, then an option:
● Automatic— Hyperion Configuration Utility deploys all files to the application
server, resulting in no or minimal post-deployment tasks:
❍ WebLogic: If disk space is inadequate, specify another location for the
WAR file and redeploy.
❍ WebSphere: If disk space is inadequate, Hyperion Configuration Utility
places java.io.tempdir in <HYPERION_HOME>
\temp<HYPERION_HOME>/temp. After deployment, the temp folder is
deleted.
● Manual— The EAR or WAR file is placed in this directory, enabling you to
manually deploy after configuration:
<ProductHome>\<AppServer>\InstallableApps\common
ProductHome>/<AppServer>/InstallableApps/common
WebLogic 8.1.x — <ProductHome>/<AppServer>/

InstallableApps
WebLogic 8.1.x — <ProductHome>\<AppServer>\InstallableApps

c. Enter the information in “Deploying to the Application Server ” on page 28.
d. To deploy manually, see Appendix A, “Manual Application Server Deployment
Tasks”.
WebLogic:A default username and password of hyperion are used internally for
deployment.
Alerter configuration a. Enter the name and port number of the computer on which the E-mail server is
installed.
b. Enter the ID and password that you use to log on to the E-mail server.

Selection Task
c. In Return E-mail Address, enter the E-mail address to which undelivered alert
notifications should be sent.
6 Click Finish.
Configuration time depends on the products and tasks you selected.
If errors display, perform these tasks:
● Configure products individually and perform tasks separately.
● See the Hyperion Installation and Configuration Troubleshooting Guide.
7 Perform any further configuration tasks identified in “Finishing Configuration” on page 31.
Registering With Shared Services

By default, the user you specify during registration is pre-provisioned as admin. This enables
you to log on toShared Services after configuration using admin/password, to create and
provision users.
Table 5 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.
HPS URL URL of the computer to which you deploy Performance Scorecard.
HPS Application Name Name for the Performance Scorecard application in Shared Services.
The application is automatically created during configuration. You need
not create it in Shared Services.
HPS Project Name for the Performance Scorecard project in Shared Services. This
project is automatically created during configuration. You need not
create it in Shared Services.
Use Shared Services for User Management Select to create users in Shared Services that you can also use in other
Hyperion product applications.
Use Shared Services Directory Definitions Select to authenticate users using Shared Services.
Configuring Performance Scorecard 27

Configuring Databases
Hyperion recommends that you use the same, or the default, database name (hypdb), username
(hypuser), and password for all products that you install.
You can use Windows Authentication for SQL Server connections if you use Microsoft SQL
Server database. See “Microsoft SQL Server Windows Authentication” on page 28.
Table 6 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.
Microsoft SQL Server Windows Authentication
➤ To set up Windows authentication for a SQL Server connection:

1 Set up SQL Server with your NT login user:
2 Ensure that your NT domain user is assigned to the SQL Server database (for example, hub).
3 Grant the NT domain user full access permissions to the database.
4 From the configuration task list, select Configure Database.
5 From the database list, select SQL Server.
6 Specify all database information except for Username and Password.
Deploying to the Application Server

You can deploy multiple products to one application server, in a single profile (WebSphere) or
domain (WebLogic 9.1.x). The application server must be installed on the same computer as
the products.

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. A default username and password of hyperion is used during
deployment.
● WebSphere application server. If you are using UNIX, Install, deploy, and execute Hyperion
products using the account you used to install WebSphere.
Deploying more than one Web application to the same OC4J instance, WebLogic server, or
WebSphere application server may yield unsuccessful results.
To deploy to a cluster, enter the following information, but see “Deploying to Clusters ” on page
30 afterward. To deploy manually, see the following sections:
● “Deploying to WebLogic” on page 55
● “Deploying to WebSphere” on page 56
● “Deploying to JES ” on page 57
● “Deploying to Oracle 10.1.3.1.0 ” on page 58
Table 7 Deployment
Field Description
Location Path to the application server installation directory:

● WebSphere Base:
c:\WebSphere\AppServer
or /opt/WebSphere/AppServer
● WebSphere Express:
c:\IBM\WebSphere\Express51\AppServer
/opt/IBM/WebSphere/Express51/AppServer
● WebLogic 8.1.x:
c:\bea\weblogic81
/opt/bea/weblogic81
● WebLogic 9.1.x:
c:\bea\weblogic91
/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 30.
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 30.
Configuring Performance Scorecard 29

Field Description
BEA Home (WebLogic) Path to the BEA Home directory (e.g.,c:\/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 <HYPERION_HOME>\deployments.
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.
Deploying to Clusters
This section explains how to deploy to a cluster.
➤ To deploy to a cluster:
1 On the Shared Directory window, enter a drive that all computers in the cluster can access.
2 On the Local Directory window, select the directory that you created to contain temporary files. See “Creating
a Temporary Directory” on page 16.
3 Click Next.
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:
HYPERION_HOME/deployments/<AppServNameAndVersion>
HYPERION_HOME\deployments\<AppServNameAndVersion>
Under this directory, the bin directory contains start and stop scripts for all deployed
applications. For each application, there is also a setCustomParams<Product>.bat file or a
shell script where JAVA_OPTIONS can be changed when starting using start scripts.
To change the default profile or domain directory, modify the deployment directory parameter
in the weblogic.properties or websphere.properties in:
HYPERION_HOME\common\config\resources\<AppServName>\resources
HYPERION_HOME/common/config/resources/<AppServName>/resources

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:
PRODUCT_HOME/AppServer/InstalledApps/<AppServName>/<Version>
PRODUCT_HOME\AppServer\InstalledApps\<AppServName>\<Version>
Finishing Configuration
If appropriate, perform these tasks after configuration:
● If you deployed manually or use a Thai locale, see Appendix A, “Manual Application Server
Deployment Tasks”.
● Start Shared Services. See “Satisfying Startup Dependencies” on page 31.
● Start Performance Scorecard. See “Starting Performance Scorecard” on page 33.
Satisfying Startup Dependencies

Before starting Performance Scorecard, verify that Shared Services server is running. See
“Starting Shared Services” on page 31 and “Stopping Shared Services” on page 32.
Starting Shared Services

If you deployed the Shared Services application server as a Windows service, to start Shared
Services manually, from the Windows control panel, select Administrative Tools > Services.
➤ If you did not deploy Shared Services application server as a Windows service, to start the Shared
Services server:
1 Select Start > Programs > Hyperion > Foundation Services > Start Shared Services.
2 If the menu item does not indicate the application server to which the Shared Services server is deployed,
you must start Shared Services server manually.
➤ To start Shared Services server manually, execute the startup script:
Application Server Path to Script
IBM WebSphere <HYPERION_HOME>\deployments\<AppServNameAndVersion>\bin

\startSharedServices9.bat
<HYPERION_HOME>/deployments/<AppServNameAndVersion>/bin/
startSharedServices9.sh
BEA WebLogic 8.1.x <HSS_HOME>\AppServer\InstalledApps\<AppServName>\<version>

\SharedServices9\startSharedServices.bat
Satisfying Startup Dependencies 31

<HSS_HOME>/AppServer/InstalledApps/<AppServName>/
<version>/SharedServices9/startSharedServices.sh
BEA WebLogic 9.1.x <HYPERION_HOME>\deployments\<AppServNameAndVersion>\bin

\startSharedServices.bat
startSharedServices.sh
Oracle To start Oracle Enterprise Manager:

<OracleInstallDir>\bin\emctl start iasconsole<OracleInstallDir>/
bin/emctl start iasconsole
To start all managed applications under Oracle Enterprise Manager:

<OracleInstallDir>\opmn\bin\opmnctl startall<OracleInstallDir>/
opmn/bin/opmnctl startall
To start OC4J instance:

<OracleInstallDir>\opmn\bin\opmnctl start process-type=<instance-
name><OracleInstallDir>/opmn/bin/opmnctl start process-
type=<instance-name>
where Shared Services has been deployed to instance “<instance-name>”.
Apache Tomcat <HYPERION_HOME>\deployments\<AppServName>\<version>\bin

\startSharedServices9.bat
<HYPERION_HOME>/deployments/<AppServName>/<version>/bin/
startSharedServices9.sh
Stopping Shared Services

If you installed the Shared Services application server as a Windows service, to stop Shared
Services server, use the Windows control panel.
➤ To stop Shared Services server manually:

1 Execute the stop script:
IBM WebSphere <HYPERION_HOME>\deployments\<AppServNameAndVersion>\bin

\stopSharedServices9.bat
stopSharedServices9.sh
BEA WebLogic 8.1.x <HSS_HOME>\AppServer\InstalledApps\<AppServName>\<version>

\SharedServices9\stopSharedServices.bat
<HSS_HOME>/AppServer/InstalledApps/<AppServName>/<version>/
SharedServices9/stopSharedServices.sh

BEA WebLogic 9.1.x <HYPERION_HOME>\deployments\<AppServNameAndVersion>\bin

\stopSharedServices.bat
stopSharedServices.sh
Oracle To stop Oracle Enterprise Manager:

<OracleInstallDir>\bin\emctl stop iasconsole<OracleInstallDir>/bin/emctl stop
iasconsole
To stop all managed applications under Oracle Enterprise Manager:

<OracleInstallDir>\opmn\bin\opmnctl stopall<OracleInstallDir>/opmn/bin/opmnctl
stopall
To start OC4J instance:

<OracleInstallDir>\opmn\bin\opmnctl stop process-type=<instance-
name><OracleInstallDir>/opmn/bin/opmnctl stop process-type=<instance-name>
where Shared Services has been deployed to instance “<instance-name>”.
Apache Tomcat <HYPERION_HOME>\deployments\<AppServName>\<version>\bin

\stopSharedServices9.bat
<HYPERION_HOME>/deployments/<AppServName>/<version>/bin/
stopSharedServices9.sh
Note:
Windows: You can also select Start > Programs > Hyperion > Foundation Services > Stop
Shared Services.
2 WebLogic: If prompted, 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.
Starting Performance Scorecard

➤ To launch Performance Scorecard
1 Start the Shared Services server and the application server. See “Starting Shared Services” on page 31.
2 Start the product as described for the operating system:
Starting Performance Scorecard 33

Table 8 Starting Performance Scorecard
Operating System Method
Microsoft Windows To start the Performance Scorecard server, select Start > Programs > Hyperion > Performance
Scorecard > startWebReports on <app server>
To start the Alerter server, select: Start > Programs > Hyperion > Performance Scorecard >
startHPSAlerter on <app server>
To start Performance Scorecard on another computer, navigate to: http:
\<computer>:<port>\HPSWebReports
UNIX From a command line, enter ./startHPS.sh in the deployment directory. To start the Alerter,
enter ./startAlerter.sh in the deployment directory.

Uninstalling Performance
5 Scorecard
➤ To uninstall Scorecard:
1 If you installed Performance Scorecard as a service, stop the service.
2 Copy the notes directory that contains current notes, annotation, and attachment files. By default, this
directory is in <HYPERION_HOME>\deployments\<web server>\webappsconf
\attachments.
3 Copy the config directory that contains the properties and XML files that you may have modified for the
current application. By default, this directory is in <HYPERION_HOME>\hps\9.3.1\AppServer
\Tomcat\5.0.28\webappsconf\config.
4 Copy the images directory that contains application graphics. By default this directory is
in<HYPERION_HOME>\hps\9.3.1\AppServer\installedApps\Tomcat\5.0.28
\webreportsDomain\HPSWebReports\images.
5 Launch the uninstall:
Operating Systems Task
Microsoft Windows NT Follow this path:

Start > Programs > Hyperion > Performance Scorecard > Uninstall Performance
Scorecard
Microsoft Windows 2003 From webappsconf\_uninstHPS, run java -jar uninstallHPS.jar.
UNIX From webappsconf\_uninst, run uninstallHPS.bin.
The Hyperion Uninstall program is launched.

6 Click Next.
A window displays the directory from which Performance Scorecard will be removed.
7 Click Next and then Finish.
8 Ensure that the hps directory was deleted from C:\HYPERION_HOME.
35
36 Uninstalling Performance Scorecard
Upgrading Scorecard
6
These upgrade paths are supported:
● 9.2.0.3 to 9.3.1
● 9.3.0.x to 9.3.1
To upgrade from a release prior to 9.2.0.3, upgrade to one of the releases noted above. You can
then upgrade to 9.3.1.
Support for upgrading a 9.2 release prior to 9.2.0.3 will be provided in an upcoming service pack
IBM DB2: Ensure that the admin user is not a member of USERS group. See “Preparing an IBM
DB2 Database” on page 15.
If you are upgrading Shared Services with other products, upgrade Shared Services first.
➤ To upgrade:
1. Note the settings that configured the existing release.
2. Stop the application server.
3. Launch the installation and select Upgrade Install.
4. Install this release of Performance Scorecard. See “Installing Performance Scorecard and
Optional Components” on page 19. Select Upgrade existing installation.
5. Launch the Hyperion Configuration Utility.
6. Connect to the database used with the previous release. See “Configuring Databases ” on
page 28.
7. Deploy to the application server. See “Deploying to the Application Server ” on page 28.
8. Move the note and attachment directories used in the old application to the same location
in the new deployment directory.
37
38 Upgrading Scorecard
Configuring Performance
7 Scorecard for External
Authentication
In This Chapter
External Authentication Options .................................................................................................39
Prerequisites........................................................................................................................40
Configuring for External Authentication and Single Sign-On ...................................................................40
Configuring SiteMinder for Single Sign-On.......................................................................................46
Creating a Web Resource .........................................................................................................48
Adding and Managing User Directories ..........................................................................................48
Configuring the Token Time-out...................................................................................................51
External Authentication Options

You can configure Performance Scorecard for external authentication as follows:
● Using Shared Services from the Shared Services Configuration Console. See the Hyperion
Security Guide.
Caution!
If you use Shared Services for external authentication or single sign-on, ensure that Basic
JDBC is last in the preferred search order list. See “Configuring the Search Order” on page
49.
● Using the Performance Scorecard Administrator

Log on to Scorecard using the admin user account or an account to which the admin role
is assigned and perform these tasks:
❍ Add a supported service provider.
❍ Edit an existing service provider or modify the search order.
❍ Delete an existing service provider.
❍ Set or modify the service provider search order.
Note: Configuration changes made using the Administrator are applied to Performance
Scorecard and the Alerter.
External Authentication Options 39

Prerequisites
Perform these steps before configuring for external authentication and single sign-on:
1. Create a user account (e.g. hpsAdmin) on the external authentication server. You will create
an identical account that becomes the Performance Scorecard admin user account in
Scorecard.
2. Start the application server and launch Scorecard.
If you are using Windows, select Start > Hyperion > Performance Scorecard >
startWebReports on<appserver>.
3. Log on to Scorecard using admin as the user name and password as the password.
4. Select Administration > User Accounts and create a user account called hpsAdmin.
For information about user accounts, see the Hyperion Performance Scorecard — System 9
Administrator’s Guide.
5. Assign the admin security role to the user account. Refer to the Hyperion Performance
Scorecard — System 9 Administrator’s Guide.
6. Decide which of the supported authentication providers, on which platforms, to make
available in the security realm.
If you are using an NTLM provider on UNIX system as the client application machine,
ensure that the HRAM is installed on a Windows NT, 2000, or 2003 server.
7. If you use SiteMinder to protect company Web resources, you can configure the security
platform to enable single sign-on between Hyperion applications and SiteMinder. The
Hyperion security platform supports SiteMinder Policy Server 5.5 Service Pack 2 and
SiteMinder Web Agent 5.5 Service Pack 2 also known as SiteMinder Web Agent 5.x QMR
5. For information, see “Configuring SiteMinder for Single Sign-On” on page 46.
8. To authenticate users from multiple Windows domains without setting up trust
relationships between the domains, install the HRAM on a separate Windows server.
This enables users of Hyperion products running on one domain to log into Hyperion
applications on other domains. All the domains involved must be running Hyperion
applications that are configured to use the same HRAM instance.
Configuring for External Authentication and Single Sign-On

This topic describes how to configure Performance Scorecard and the Alerter (if installed) to
authorize users using another supported authorization provider. These topics are covered:
● “Configuring Basic JDBC ” on page 41
● “Configuring NTLM Authentication” on page 41
● “Configuring LDAP or MSAD ” on page 45
40 Configuring Performance Scorecard for External Authentication

Configuring Basic JDBC
Performance Scorecard automatically uses basic authentication.
Follow the steps in this topic to add basic JDBC authentication if it was removed.
➤ To add basic JDBC authorization:

1 Log on to Performance Scorecard as an administrative user or using the admin user.
The Performance Scorecard Administrator or the Alerter is displayed.
2 Select Administration > Configure External Authentication Configuration.
The Service Providers page is displayed.
3 Click the lower Add button to add basic authentication as the new service provider. The Service Provider Type
page is displayed.
4 Select Basic Authentication and click Next. The Configure Basic Authentication Provider page is displayed.
5 Enter a name for the provider in Name.
Caution!
Do not use blanks in the name.
6 Click Save. The JDBC provider is added.

7 Define the search order. See “Configuring the Search Order” on page 49.
8 Restart the application server.
Configuring NTLM Authentication

This topic describes how to configure Performance Scorecard to authenticate users using an
NTLM user directory. This means that when users log on, Performance Scorecard verifies the
users and their passwords against the NTLM database.
Depending on your environment, you may need to perform the tasks in “Configuring NTLM
Authentication Using WebLogic” on page 45.
➤ To configure NTLM as an authentication service provider:

1 Log on to Performance Scorecard as an administrative user or using the admin user.
The Scorecard Administrator is displayed.
2 Select Administration > External Authentication Configuration. The Service Providers page is displayed.
3 Click the lower Add button to add an NTLM service provider. The Service Provider Type page is displayed.
4 Select NTLM and click Next. The Configure NTLM Provider page is displayed.
5 Enter the authorized Name for the NTLM service provider. This name can be any name; however, do not
include any blanks in the name.
Configuring for External Authentication and Single Sign-On 41

6 Enter the NTLM Domain name, then click Save.
8 Click Previous to return to the Initial Configuration Application page.
9 Stop the application server.
10 Remove the domain name, and save and close the file.
11 Restart the application server, and log on using the authenticated account.
12 Select Administration > User Accounts to add a Performance Scorecard user account with the same NTLM
user name. See the Hyperion Performance Scorecard — System 9 Administrator’s Guide.
13 WebLogic users: See “Configuring NTLM Authentication Using WebLogic” on page 45.
Before Configuring for NTLM

To use external authentication for Hyperion applications, your organization must have an
authentication directory that contains corporate user information.
➤ To prepare to configure for NTLM:

1. Copy CSS-9_3_1.dll from HYPERION_HOME\common\CSS\9.3.1.0\BIN to C:
\WINNT
2. Perform the steps outlined in “Setting Up User Rights for NTLM” on page 42.
3. If required, set up alternative configurations using these topics:
● “UNIX Application Support for NT LAN Manager” on page 44
● “Multiple-Domain Support for NT LAN Manager” on page 44
4. Enable the NTLM provider. See “Configuring NTLM Authentication” on page 41.
Setting Up User Rights for NTLM

To enable use of the NTLM provider, certain access rights are required of the Windows NT user
account on which the application or application server runs.
Note: Set up these rights on the computer where the application runs, not the NT domain
computer.
Additionally, certain access rights are required for end users. These access rights are required to
use an NTLM provider:
● Access this computer from the network (usually granted to Administrators). End users of
Hyperion products using external authentication require this right.
● Act as part of the operating system (normally not granted to anyone). The account used to
run Hyperion application processes requires this right in order for external authentication
to work.
● The logged on user should be a domain user. The user running the application or application
server of the Hyperion product should be a domain user rather than a local Windows user.

Refer to the appropriate procedure to set up user rights for your configuration:
● “Setting Up User Rights on Windows NT” on page 43
● “Setting Up User Rights on Windows 2000” on page 43
Setting Up User Rights on Windows NT

This topic describes how to set up user rights on Windows NT.
➤ To set up user rights on Windows NT:

1 From the Start menu, select Programs > Administrative Tools (Common) > User Manager.
2 In the User Manager dialog box, select the appropriate user name.
3 Select Policies > User Rights.
The User Rights Policy dialog box is displayed.
4 From Right, select Access this computer from network.
The users or groups with the selected policy setting are shown. If appropriate users are shown,
list box, click Cancel and go to step 6.
5 To grant the selected right, click Add, and complete the Add Users and Groups dialog box.
6 In the User Rights Policy dialog box, check Show Advanced User Rights.
7 From Right, select Act as part of the operating system.
The users or groups who have the selected policy setting are shown in Grant To. If the appropriate
user is shown in Grant To, click Cancel and skip the rest of this procedure.
8 Click Add, and complete the Add Users and Groups dialog box.
Setting Up User Rights on Windows 2000

This topic explains how to set up user rights on Windows 2000.
➤ To set up user rights on Windows 2000:

1 From the Start menu, select Setting > Control Panel > Administrative Tools > Local Security Policy.
The Local Security Settings dialog box is displayed.
2 In the left-pane tree of the Local Security Settings dialog box, expand Local Policies.
3 Click User Rights Assignment and then double-click Access this computer from the network.
The Local Security Policy Setting dialog box for the Access this computer from the network
policy is displayed.
4 If the relevant user account has the policy checked, click Cancel and go to step 9.
5 Click Add.
6 Select the name of the appropriate user or group needing the right.
7 Click Add.
8 Click OK.

9 In the right pane of the dialog box, double-click Act as part of the operating system.
The Local Security Policy Setting dialog box for the Act as part of the operating system policy is
displayed.
10 If the relevant user account has the policy checked, click Cancel and skip the rest of this procedure.
11 Click Add.
12 Select the name of the appropriate user or group needing the right.
13 Click Add and then OK.
UNIX Application Support for NT LAN Manager

If you install Performance Scorecard on a UNIX computer that uses an NTLM provider, ensure
that the Remote Authentication Module Installer is installed on a Windows NT/2000 server.
➤ To set up UNIX application support for NTLM:

1 Shut down the application server.
2 On the Windows NT/2000 server, install the Remote Authentication Module Installer by running
setup.exe in the NTLMRemoteServer folder on the root directory of the product DVD.
3 Accept the license agreement and click Next.
4 On the Welcome page, click Next.
5 Choose a destination location for the Remote Authentication Module Installer, and click Next.
6 Enter the host name and port number for the computer hosting the Remote Authentication Module Installer,
and click Next.
7 Optional: If you are going to use Secure Sockets Layer with your NTLM deployment, select the option to
support SSL and click Next.
8 If you are using a UNIX application in an NTLM domain, the security platform can communicate over a secure
medium such as Secure Sockets Layer (SSL) with the Hyperion Remote Authentication Module. If you need
to use SSL, select the SSL option when installing the Hyperion Remote Authentication Module.
Multiple-Domain Support for NT LAN Manager

In addition to UNIX application support, the Hyperion Remote Authentication Module
(HRAM) also enables Hyperion products to authenticate users belonging to other domains that
are not trusted by the domain on which the Hyperion application is installed. This removes the
necessity to establish trust relationships between the domains. Therefore, HRAM is useful for:
● UNIX application users who need to log in using a Windows domain
● Windows users who need to log in using more than one Windows domain, although there
are no trust relationships set up.

➤ To provide support for NTLM authentication using multiple Windows domains, instal l HRAM
on the Windows server.
Configuring NTLM Authentication Using WebLogic

This section explains how to use an NTLM provider and run Performance Scorecard and the
Alerter (if you installed it) on the same WebLogic server.
➤ To run Performance Scorecard and the Alerter (if you installed it) on the same application server:
1 Perform these tasks.
a. Start the WebLogic Admin Server Console.
b. Under <mydomain > Services, select XML.
c. Click Configure a new XML Registry.
d. Enter JAXP 1.2 in Name.
e. Enter the following in DocumentBuilderFactory:
org.apache.xerces.jaxp.DocumentBuilderFactoryImplSax
ParserFactory = org.apache.xerces.jaxp.SAXParserFactoryImpl
f. From When To Cache, select cache-at-initialization.
g. Click Create.
2 Select the “Targets ”tab.
3 Move myserver from the Available Servers to the Chosen Servers frame.
4 Click Apply.
5 Restart WebLogic.
Configuring LDAP or MSAD

This topic explains how to configure Performance Scorecard to use an LDAP or MSAD user
directory to authenticate users. When users who are using this authentication log in,
Performance Scorecard verifies the users and their passwords against the LDAP or MSAD
database, as appropriate.
Caution!
If you use Shared Services to configure for external authentication or single sign-on, make Basic
JDBC last in the preferred search order list. See “Configuring the Search Order” on page 49.
➤ To configure LDAP or MSAD as a service provider:

1 Log on as an administrative user or using the admin user.
2 Select Administration > External Authentication Configuration. The Service Providers page is displayed.

3 Click the lower Add button. The Service Provider Type page is displayed.
4 Select LDAP or MSAD and click Next.
The configuration page for the provider you chose is displayed. The contents of the page is the
same for LDAP and MSAD.
5 Enter the authorized Name for the service provider in Name.
Caution!
Do not include any blanks in the name.
6 Enter the URL, or Web path name, to the LDAP or MSAD server in URL
7 Enter cn=user information in User DN The user name is the information from a user account that has read-
only access to the directory stores.
8 Enter the password for the user or user group in Password.
9 Enter the user URL organizational unit information in User Organizational Unit URL. The organizational unit
is the information that indicates the branch in the directory server that contains user entries.
10 Optional: Enter the Login Attribute. This entry matches an attribute in the directory that uniquely identifies
user entries.
11 Enter the URL for the group user organizational unit in Group Organizational Unit URL.
12 Do not specify a Context Class.
13 Click Save to save the service provider settings, and return to the Initial Configuration page.
14 Add a Performance Scorecard user account with the same LDAP or MSAD name. Refer to the Hyperion
Performance Scorecard — System 9 Administrator’s Guide.
16 Restart the application to apply the configuration changes.
Configuring SiteMinder for Single Sign-On

If your corporate information is protected by Netegrity SiteMinder, you can configure
Performance Scorecard to use this authentication by modifying HyperionCSS.xml.
➤ To configure SiteMinder as a service provider:

1 Ensure that the authentication repository containing user and group information is trusted.
If your corporation uses a security agent to protect company Web resources, the authentication
repository (for example, LDAP, Microsoft Active Directory, or NT LAN Manager) must be
trusted, because the Hyperion security platform does not store a password in the token when a
security agent is used.
2 Open HyperionCSS.xml in any text editor. By default, this file is located in: <HPS install>
\AppServer\InstalledApps\<AppServer>\ <Version>\webappsconf\config

3 If the Web resource (the HTTP context of the application) is protected by the SiteMinder Security Agent, add
this text after the <logger></logger> topic but before </css>:
<logger>
<priority>FATAL</priority>
</logger>
<securityAgent name="NETEGRITY"/>
Note: You can only configure security agents for web-based applications.
If you later choose to discontinue using SiteMinder as an external user directory, remove this
code.
4 Modify HyperionCSS.xml as follows:
● To point to the same providers as those configured in the SiteMinder Policy Server.
● Add SiteMinder to the search order.
For example, if you use LDAP and want to use SiteMinder, the code should resemble the
following:
<?xml version="1.0" encoding="UTF-8"?>

<css xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<spi>
<provider>
</custom>
<ldap name="ldapServer">
<trusted>true</trusted>
<url>ldap://<machine>:<port>/
DC=ctgw2k-1,DC=hyperion,DC=com</url>
<userDN>cn=<name>,ou=people,DC=ctgw2k-1,DC=hyperion,DC=com</userDN>
<password>Jeff</password>
<authType>simple</authType>
<maxSize>40</maxSize>
<user>
<url>ou=People</url>
</user>
</ldap>
</provider>
</spi>
<searchOrder>
<el>ldapServer</el>
<el>siteminder</el>
</searchOrder>
<token>
<timeout>60</timeout>
</token>
<logger>
<priority>FATAL</priority>
</logger>
<securityAgent name="NETEGRITY" />
</css>
5 Save and close the file.
Configuring SiteMinder for Single Sign-On 47

7 Add a Performance Scorecard user account with the same SiteMinder user name. Refer to the Hyperion
Performance Scorecard — System 9 Administrator's Guide.
8 Define a web resource. See “Creating a Web Resource” on page 48.
Creating a Web Resource

If you use SiteMinder, create a protected Web resource (URL) for the HPSWebReports directory,
and, if you use the Alerter, the HPSAlerter directory.
➤ To create Web resources:

1 Navigate to the website for the application server and install the plug-in and the plug-in for the Web server.
2 Configure the Web resource URL to point to each application you deployed.
3 Ensure that the Web resource on the Web server is protected by SiteMinder.
These resources could be HTML, JSP, ASP, or other Web-based resource files. To do this, the
SiteMinder administrator needs to configure a “response” that would enable a HTTP header to
be added by SiteMinder. This HTTP header carries the login name of the user and makes the
login name available to the Web resources (the Hyperion application’s resources, in this case).
The header must be configured in the response to have the name HYPLOGIN, and the value
should be configured to be the login name of the authenticated user.
For example, if you are using an LDAP directory and cn is the login name attribute configured
in the security platform XML configuration file, then the HYPLOGIN header should carry the
cn value corresponding to the authenticated user in the LDAP directory. The administrator can
configure the header to SM_USERLOGINNAME, an attribute that holds the user name as specified
by the user in the login attempt. For more details, please refer to the “Responses and Response
Groups” topic of the Netegrity Policy Design.
4 Ensure the policy server is configured to use the same external user directory referenced in
HyperionCSS.xml.
Adding and Managing User Directories

This topic describes how to add, modify and delete user directories (providers). It also describes
how to modify the token time-out that defines when single sign-on between Hyperion products
expires. These topics are covered:
● “Modifying User Directories” on page 49
● “Deleting User Directories” on page 49
● “Configuring the Search Order” on page 49
● “Configuring the Preferred Logging Priority” on page 50
● “Configuring the Token Time-out” on page 51

Modifying User Directories
This topic describes how to change user directory settings. You must restart the server to apply
user directory modifications.
➤ To edit a user directory:

The Performance Scorecard Administrator opens.
2 Select Administration > Configure External Authentication. The Service Providers page is displayed.
3 Select the service provider and click Edit. The Service Provider page for the selected service provider is
displayed.
4 Modify the information for the selected service provider, as appropriate.
5 Click Save to save the modified service provider settings, and return to the Initial Configuration page.
Deleting User Directories

You can delete a service provider from the Authorization System Configuration page.
➤ To delete a service provider:

3 Select the service provider and click Delete.
Confirm that you want to delete the provider when prompted.
4 Click OK to delete the service provider from the list.
5 Restart the application server to apply the configuration changes.
Configuring the Search Order

If you use multiple external user directories to authenticate users, define the search order to
identify the order in which user directory are used. For example, if you use NTLM and MSAD
and most users are defined in MSAD, make MSAD first in the search order.
Configure the search order:
● To define the search order:
● To remove provider from the search order:
➤ To define the search order:

Adding and Managing User Directories 49

3 Select the user directory.
4 If this service provider was just added, click Add in Search Order to add the service provider to the search
order list.
5 Click the appropriate button in Search Order to move a service provider to the correct location in the search
order, as follows:
● Click Move Up to move the currently selected service provider up one level in the search
order.
● Click Move Down to move the currently selected service provider down one level in the
search order.
6 Click Previous to return to the Configure Application page.
➤ To remove provider from the search order:

3 Select the service provider and click Remove.
4 Click Remove in Search Order to remove the service provider from the Search Order list.
The service provider is not actually removed from the page, but is not used until you restore it
to the search order.
5 Click Previous to return to the Configure Application page.
Configuring the Preferred Logging Priority

This topic describes how to specify the type and level of authentication-related messages you
want Performance Scorecard to log if you are use one of these providers:
● LDAP
● MSAD
● NTLM
➤ To configure the error level setting:

1 In a text editor, open HyperionCSS.xml. This file is located in: <HPS install>\AppServer\
InstalledApps\<AppServer>\<version>\webappsconf\config
2 Locate this code:
<logger>
<priority>DEBUG</priority>
</logger>

3 Change the error-reporting value from ERROR to the type of authentication-related messages that you want
Performance Scorecard to log as shown in the table below. If the entire <logger></logger> topic
including the tags is deleted, the default value of ERROR is used. Do not delete just the values.
Note: Each level is inclusive of the levels below it.
Value Description
DEBUG Includes extensive information useful for debugging
INFO Includes information on the status of operations and requests
WARN Includes cautionary information, if relevant, for some operations and requests
ERROR Includes only statements pertaining to failed operations and requests
FATAL Includes only information about errors that result in a disconnection
Configuring the Token Time-out

When an externally authenticated user logs on to a Hyperion application, an authentication
token is generated to contain the login credentials. While the token is valid, the user can log on
to any other valid Hyperion application without signing on again, or remain logged on to the
current application. This single sign-on feature is designed to simplify the process for users who
need to access multiple Hyperion applications.
For security reasons, a token time-out is set to prevent unauthorized users from signing on to
other applications. You can modify this value in the HyperionCSS.xml file, to set the token
to expire after a specified number of minutes, instead of the default of 60 minutes.
Note: If you deploy Scorecard and the Alerter to the same computer, external authentication
configurations you make to the Alerter are automatically applied to Scorecard.
➤ To configure the token time-out:

1 In a text editor, open HyperionCSS.xml. By default, this file is located in: <HPS install>
\AppServer\InstalledApps\<AppServer>\<version>\webappsconf\config.
2 Locate this section of code:
<token>
<timeout>60</timeout>
</token>
3 Between the <timeout></timeout> tags, enter the number of minutes that should pass before a user
is required to authenticate again.
The default length for the time-out token in Performance Scorecard is set to 60 minutes. For
example, <timeout>300</timeout>.
Configuring the Token Time-out 51

5 Restart the server if required.
6 Shutdown and restart Performance Scorecard.

Setting up Projects and
8 Provisioning Users in Shared
Services
In This Chapter
Using External User Directories ...................................................................................................53
Creating and Provisioning Users ..................................................................................................53
Using External User Directories

To use MSAD, NTLM, or LDAP provider to authenticate users, add the provider in Shared
Services. See the Hyperion Security Guide.
Creating and Provisioning Users

This section describes how to set up the users that will use Performance Scorecard with any other
Hyperion products that they have installed. After provisioning these users, you import them
into Performance Scorecard.
Provisioning the Admin User

Before you can create users that will be shared by Hyperion product applications, provision the
admin user provided by Shared Services.
➤ To provision the Admin user:

1 In the Shared Services User Management Console, select User Directories > <provider>.
2 Select Users > admin.
3 Assign the Provisioning Manager role to the admin user.
4 Save your work.
5 Create all required users. See “Provisioning and Synchronizing Shared Users” on page 54.
Note: Admin is automatically provisioned. Use this feature to change the default provisioned
roles.
Using External User Directories 53

Provisioning and Synchronizing Shared Users
This section describes how to set up and provision the users that Hyperion products will share.
After provisioning the users in Shared Services, import them into Scorecard by synchronizing
the User Account List. See the Hyperion Performance Scorecard — System 9 Administrator's
Guide.
➤ To create and provision users:

1 In the Shared Services User Management Console, select Users > <provider>.
2 Select User > New User.
3 Assign the security role that will grant the user the correct level of access to Hyperion applications.
4 Repeat steps 2 - 4 to create the users that you need.
5 Add each user to the Performance Scorecard project that you created.
6 Log on to Performance Scorecard using admin user that you set up.
7 On the Object View, select Security > User Accounts. The User Account List is displayed, listing all users
accounts that have been created and that can be used by Performance Scorecard.
8 Optional: Add the users that you created in Shared Services by clicking Synchronize With Shared Services.
The users that you set up in Oracle's Hyperion® Shared Services are added toPerformance Scorecard.
54 Setting up Projects and Provisioning Users in Shared Services

Manual Application Server
A Deployment Tasks
In This Appendix
Deploying to a Single Application Server ........................................................................................55
Deploying to Clusters ..............................................................................................................61
Deploying on a Thai Locale .......................................................................................................68
Deploying to a Single Application Server

Deploy Performance Scorecard and the Alerter to a standalone application server, if you did not
deploy automatically, and performed a partial deployment using the Oracle's Hyperion®
Configuration Utility™. See:
● “Deploying to WebLogic” on page 55
● “Deploying to WebSphere” on page 56
● “Deploying to JES ” on page 57
● “Deploying to Oracle 10.1.3.1.0 ” on page 58
Deploying to WebLogic
This section describes how to deploy Scorecard manually to WebLogic.
➤ To manually deploy to WebLogic:

1 Create a new, or use an existing domain. Use the WebLogic Configuration Wizard to create a domain.
2 Create a new managed server called HPS, and specify 7001 as the listen port.
3 If you are not using Essbase, go to step 5.
4 If you are using Essbase, perform these steps
a. Make a copy of <domain>\startWeblogic.sh |.cmd and save it
asstartHPS.cmd|.sh in the same directory.
b. Scroll to the line for your operating system:
● Microsoft Windows: call "%DOMAIN_HOME%\bin\setDomainEnv.cmd" %*
● UNIX:. ${DOMAIN_HOME}/bin/setDomainEnv.sh $*
c. Add the code for the operating system after that line:
Deploying to a Single Application Server 55

Table 9 Editing startHPS.cmd |.sh
Operating System Code
Microsoft Windows call <HYPERION_HOME>\deployments\WebLogic9\manual\webappsconf

\bin\setHpsEnv.cmdset PATH=%HPS_PATH%;%PATH% set CLASSPATH=%
HPS_CP%;%CLASSPATH% <HYPERION_HOME>
UNIX call <HYPERION_HOME>\deployments\WebLogic9\manual\webappsconf

\bin\setHpsEnv.cmdset PATH=%HPS_PATH%;%PATH% set CLASSPATH=%
HPS_CP%;%CLASSPATH% <HYPERION_HOME>
d. Save and run the file.

5 In the WebLogic Administration Console, select Deployments > Web Application Module.
6 Click Deploy a new Web Application Module.
7 Browse to HPSWebReports.war as follows:
● 8.1: <HPS install>\deployments\WebLogic8\manual\webapps
● 9.1:Hyperion\deployments\WebLogic9\manual\webappswebapps
8 Click Target Module and then Deploy.
9 For 9.1: In subsequent screens, select Install this deployment as an application and specify HPS as the
target server.
10 Select I will make the deployment accessible from the following location, and specify the full path to
the.war file.
11 To deploy the Alerter. repeat these steps, but navigate to HPSAlerter.war.
Deploying to WebSphere
Unless you add another port, Performance Scorecard runs on the default port of 18080.
➤ To deploy to WebSphere:
1 Log on to the WebSphere Administrative Console.
2 Select Applications > Install New Application.
3 Ensure that Local File System is selected, then click Browse to navigate to HPSWebReports.war. This
file is in<HYPERION_HOME>\deployments\WebSphere6\manual\webapps.
4 Enter HPSWebReports in Context Root.
5 Click Next and then Continue.
6 Enter hps in Application Name.
7 Click Next.
8 On Map virtual hosts for web modules, select HPSWebReports.
9 Ensure that default_host is specified for Virtual Host.
10 Click Next.
56 Manual Application Server Deployment Tasks

11 Map the application to the default server1, or another server that you want to use, and click Next.
12 On the page that displays, click Finish.
13 After Performance Scorecard is deployed, click Save to Master Configuration and then Save.
14 Select Applications > Enterprise Applications.
15 Select HPSWebReports.war and click Start.
16 Repeat this procedure to deploy the Alerter, with these exceptions:
● Navigate to HPSAlerter.war.
● Enter HPSAlerter as the context root.
● Enter Alerter as the application name.
17 Start or restart the HPS server.
18 Verify the deployment by opening:http://websphere host:18080/HPSWebReports
Deploying to JES
This section explains to deploy to a standalone JES application server.
➤ To deploy to JES:
1 Launch the JES Admin Console.
2 In Common Tasks, select Configurations > <AppServerConfig> > JVM Settings.
3 On the JVM Settings page, select JVM options.
4 Scroll to the ninth line of code.
5 Delete the code after —Djava.security.policy=.
6 Click Path Settings.
7 In Native Library Path Prefix, add these lines of code:
● C:\Hyperion\9.3.1\AppServer\InstalledApps\JES\<version>\manual
\webappsconf\bin
● C:\Hyperion\common\CSS\9.3.1\bin
● C:\Hyperion\common\CLS\9.3.1\bin\Windows
● C:\Hyperion\common\EssbaseRTC\9.3.1\bin
8 Click Save.
9 In any text editor, open asenv.bat from <AppServer>/config.
10 Add this code: set ARBORPATH=C:\Hyperion\common\EssbaseRTC\9.3.1.
11 Restart the JES server.
12 In the JES Admin Console, select Common Tasks.
13 Select Deploy Web Applications.

The Deploy Web Module page is displayed.
14 In Location, browse to HPSWebReports.war. By default, this file is in: <HPS Install>
\AppServer\InstalledApps\HES_8\8.1\manual\webapps.
15 Click Next.
16 Accept the deployment defaults displayed and click OK.
17 On the Web Applications Page, click Launch besides HPSWebReports.
18 Restart JES.
If you installed the Alerter, perform these tasks but select HPSAlerter.war.
Deploying to Oracle 10.1.3.1.0

This section describes how to deploy to a single Oracle 10.1.3.1.0 application server. To prevent
the Web application you create to deploy Performance Scorecard from inheriting unwanted
runtime settings during deployment, create an OC4J instance called HPS. Assign this instance
to a group created for Performance Scorecard.You need not modify the Oracle HTTP Server
listen port(s), but should make any required port assignments or changes before deployment.
If possible, configure ports during installation using staticports.ini as documented in
the Oracle® Application Server Installation Guide.
Preparing to Configure
● If Oracle 10.1.3.1.0 Server is not installed, install it. Specify that you want to use HTTP
protocol.
● Install Performance Scorecard to the computer hosting Oracle 10.1.3.1.0 Server.
● Make any required port assignments or changes.
Creating the OC4J Instance
➤ To create the OC4J instance:

1 Start the SOA suite.
2 Log on to Oracle 10G by navigating to: http://<server>:<port> and specifying the username and
password you created when you installed Oracle. This launches the Oracle® Enterprise Manager 10g
Application Server Console.
3 Create an instance called HPS and assign it to the appropriate group. In this procedure, default_group is
used. See the Oracle® Containers for J2EE Configuration and Administration Guide. You will later start the
deployed web application using the port number that you specify when you create the instance.
4 Start the HPS instance.
5 See “Setting Properties and Variables” on page 59.

Setting Properties and Variables
➤ To configure the HPS instance:

1 Start the HPS instance if is not already started.
2 From the Cluster Topology page, navigate to Application Server: > HPS.
3 Select Administration > Server Properties.
4 In the Command Line Options area, enter 128 MB in Initial Heap Size and 256 MB in Maximum Heap
Size.
5 In the Environment Variables area, click Add Another Row.
6 Enter the HYPERION_HOME directory you specified during installation.
7 Click Apply and restart the HPS instance.
8 See “Deploying the Web Application” on page 59.
Deploying the Web Application
➤ To deploy the web application:

1 In the Oracle® Enterprise Manager 10g Application Server Console, go to the Cluster Topology page.
2 Click the HPS instance and Application.
3 On the page that displays, click Deploy.
4 In Archive Location navigate to HPSWebReports.war. By default, this file is in <HPS_INSTALL>
\AppServer\InstalledApps\Oracle\10g\manual\webapps.
5 Click Next.
6 Enter HPS in Application Name and click Next.
7 Accept the remaining defaults on the page.
8 Click Deploy.
9 Restart the HPS instance.
10 Optional: To deploy the Alerter, repeat this procedure but select HPSAlerter.war and specify a different
application name and context root. Deploy to the same instance.
Deploying If Using Essbase

This section describes how to deploy to Oracle if you are using Essbase, also called Analytic
Services.
➤ To deploy:
1 Modify the Path environment variable as follows:
a. Select Start > Control Panel > System > Advanced and click Environment Variables.

b. In System Variable, select Path and click Edit.
c. Add a semi colon (;) to the end of the existing value.
d. Insert the following directories, modified to reference your actual directory paths. Separate
the paths with semi colons.
● <HYPERION_HOME>\common\SAP\bin
● <HYPERION_HOME>\common\EssbaseRTC\9.3.1\bin
● <HYPERION_HOME>\<HPS install>\webappsconf\bin
●
2 Start the SOA.

4 Create an instance called HPS and assign it to the appropriate group. See the Oracle® Containers for J2EE
Configuration and Administration Guide.
6 At the bottom of the page, in Groups, select the HPS instance and click Next.
7 On the Group Properties page, select the Administration tab.
8 For Server Properties, select Go to Task.
9 In Options, click Add Another Row twice to add these lines that reference your HYPERION_HOME and Essbase
(or Analytic Services) installation directories:
● -Dhyperion.home=<HYPERION_HOME>.For example, C:\HYPERION
● -DESS_ES_HOME= <AnalyticServices>For example, C:\HYPERION
\AnalyticServices
10 In Environment Variables, click Add Another Row five times to add the following:
Table 10 Modifying Environment Variables
Variable Value
CIS_CLASSPATH <HYPERION_HOME>\common\SAP\lib;%CIS_CLASSPATH%
ISHOME If you use Oracle's Essbase® Integration Services to generate an Essbase database, specify the
installation directory, for example, C:\Hyperion\AIS.
HYPERION_HOME If you use Oracle's Essbase® Integration Services to generate an Essbase database, reference
the system variable. For example, C:\<HYPERION_HOME>
ARBORPATH Reference the installation directory or the EssbaseRTC common directory, as follows: C:
\<HYPERION_HOME>\AnalyticServices or C:\<HYPERION_HOME>\common
\EssbaseRTC\9.3.1
PATH Reference the contents of the PATH environment variable by performing these tasks:
a. Select Start > Settings > Control Panel > System > Advanced.
b. Click Environment Variables.

Variable Value
c. Select PATH, click Edit, select the content and press CTRL +C.
d. Append the copied path with ;%PATH%.
11 Click Apply. The update loads.

12 Select the Applications tab.
13 Click Deploy at the top of the page.
14 On the Select Archive page, select the first Archive option.
15 Click Browse and navigate to HPSWebReports.war in:<HPS_INSTALL>\AppServer
\InstalledApps\Oracle\10g\manual\webapps.
16 Click Next.
The deployment uploads and the Application Attributes page is displayed.
17 In Application Name, enter HPS.
18 Accept the remaining defaults and click Next.
19 On the Deployment Settings page, select the Configure Class Loading task.
20 In Configure Application Libraries, click Add Another Row four times to insert the following in Path:
Table 11 Updating Path
Row Code
1 <<HPS install>>\9.3.1\AppServer\InstalledApps\Oracle\10g\manual\webappsconf
\bin
2 <HYPERION_HOME>\common\CSS\9.3.1\bin
3 <HYPERION_HOME>\common\EssbaseRTC\9.3.1\bin or C:\<HYPERION_HOME>
\AnalyticServices\bin
4 <HYPERION_HOME>\common\SAP\bin
21 Click OK. You return to the Deployment Settings page.

22 Click Deploy.
23 Optional:To deploy the Alerter, perform the steps in “Deploying the Web Application” on page 59, but select
HPSAlerter.war and enter Alerter in Application Name.
Deploying to Clusters
The following sections describe how to deploy Performance Scorecard and the Alerter to a
cluster.
Perform the steps in “Mapping the WebAppsConf Directory” on page 62, and refer to these
sections:
● “Deploying to a WebSphere Cluster” on page 62
Deploying to Clusters 61
● “Deploying to a WebLogic Cluster” on page 63
● “Deploying to a JES Cluster” on page 66
● “Deploying on a Thai Locale” on page 68
● “Deploying to an Oracle 10G Cluster” on page 67
Mapping the WebAppsConf Directory

This section describes how to map the webappsconf directory to enable all computers in the
cluster to synchronize application data.
➤ To map webappsconf:
1 Navigate to the directory for the application server.
2 Right-click on the webappsconf directory and select Properties. The Properties dialog box is displayed.
3 Click Share this folder.
4 Enter webappsconf as the share name.
5 Select the users who will access this directory.
6 Select Tools > Map Network Drive. The Map Network Drive dialog box is displayed.
7 Select the drive to share and browse to webappsconf.
Deploying to a WebSphere Cluster

This section describes how to deploy Performance Scorecard and the Alerter (if installed) to a
WebSphere cluster.
Creating the Web Application

This section describes how to deploy HPSWebReports.war to WebSphere and synchronize all
nodes in the cluster.
➤ To deploy to WebSphere:
1 Log on to the WebSphere Administrative Console.
2 Select Applications > Install New Application.
3 Select Server Path and browse to HPSWebReports.war. This file is in <HYPERION_HOME>
\deployments\WebSphere\manual\webapps.
4 Click Apply and then OK.
5 InContext Root, enter HPSWebReports.
6 Click Next.
7 Click Next to accept the settings, such as the default host shown on the Step 1 and Step 2 pages.

8 On the Map modules to application servers page, select the cluster that you created for Scorecard.
9 Select HPSWebReports.war and click Next. The Summary window is displayed.
10 Click Finish.
11 Click Save to master configuration.
12 Click Save at the top of the page.
13 Select System Administration > Nodes.
14 Select the nodes participating in the cluster (hps-cluster1, hps-cluster2, etc.) and click Synchronize.
15 In the Administration Console, select Applications > Enterprise Applications.
16 Select the application (in this case HPSWebReports.war).
17 Under Related Items, click WebModules.
18 Select HPSWebReports.war.
19 Click Apply and Save when prompted.
20 On the Save to master configuration page, select Synchronize changes with nodes and then Save.
21 If required, start the cluster. If the cluster is started, start the hps application.
22 Select Environment > Update Web Server Plugin.
23 Click OK. This generates plugin-cf.xml in: <drive>:\<WebSphere install>
\DeploymentManager\config\cells.
24 Copy plugin-cf.xml to the appserver\config\cells directory on EACH server in the cluster.
This overwrites the existing plug-in file.
Deploying the Alerter

This section describes how to deploy the Alerter to a WebSphere cluster.
➤ To deploy the Alerter to WebSphere:

1 Perform the steps in “Creating the Web Application” on page 62, with these changes:
● Use HPSAlerter.war.
● Do NOT synchronize the nodes.
2 Regenerate plugin-cfg.xml file.
3 Copy plugin-cfg.xml to the webapps\Alerter directory for each server in the cluster.
4 Create mappings for all server in the cluster.
5 Do NOT restart the Web server.
Deploying to a WebLogic Cluster

This section describes how to deploy Performance Scorecard and the Alerter to a WebLogic
cluster.
Before deploying to a WebLogic cluster, perform these tasks:
● Satisfied the requirements in “Preparing Application Server Clusters” on page 16.
● Link webappsconf to the shared drive. See “Mapping the WebAppsConf Directory” on
page 62.
➤ To deploy:
1 Log on to the WebLogic Administration Console.
2 Select Deployments > WebApplication Modules.
3 Click Deploy a new Web Application Module.
4 Navigate to HPSWebReports.war as follows:
● 9.1: <HYPERION_HOME>\deployments\WebLogic9\manual\webapps
● 8.1: <HPS Install>\AppServer\InstalledApps\WebLogic\8.1\manual\webapps
5 Click Target Module.
6 Select the cluster and then All Servers in cluster.
7 Click Continue.
8 Select Copy this web application module onto every target for me.
9 Accept HPSWebReports as the name of the web application.
10 Click Deploy.
11 Perform steps 2-11 to deploy the Alerter, with these changes:
● Select HPSAlerter.war.
● Enter HPSAlerter as the application name.
12 Configure and start each server in the cluster using one of these options:
● “Using the Administration Console” on page 64
● “Using a Command Line” on page 65
13 Stop and restart each server.
14 Connect to each server in the cluster or the proxy server using the ports that you specified.
Using the Administration Console

This section describes how to set up servers using the Administration Console.
➤ To set up and start the servers:

1 Expand the Server directory and select one of the servers in the cluster. The Server window is displayed.
2 Click Configuration and then Remote Start.
3 Add these files to Class Path:

Directory Files
<shared drive>\lib ● EccpressoAll.jar

● flexlm.jar
● flexlmutil.jar
<bea_home>\jdk142_05\lib tools.jar
<bea_home>\weblogic81\server\lib ● weblogic_sp.jar
● weblogic.jar
Using a Command Line

This section describes how to set up and start the servers using a command line.
➤ To set up and start the servers:

1 On EACH computer in the cluster, navigate to <bea home>\user_projects\domains\
<domain>.
2 In any text editor, open the file for the operating system:
● Microsoft Windows - startManagedWebLogic.cmd
● Solaris - startManagedWebLogic.sh
3 Scroll to set classpath.
4 Perform the task for the operating system:
● On Microsoft Windows:
a. Before set classpath, enter call <shared drive>/bin/setHpsEnv.cmd.
b. Enter %HPS_CP%; where the WebLogic classpath is set.
The file should contain this information:
call z:\bin\setHpsEnv.cmd
set PATH=%HPS_PATH%,%PATH%
set CLASSPATH=%HPS_CP%,%WEBLOGIC_CLASSPATH%,%POINTBASE_CLASSPATH%;
%JAVA_HOME%\jre\lib\rt.jar,%WL_HOME%\server\lib\webservices.jar;
● On Solaris:
c. Before CLASSPATH=, enter <shared drive>/bin/setHpsEnv.sh.
Insert a space before <shared directory>.
d. Enter ${HPS_CP} where the WebLogic classpath is set.
The file should contain this information:
. /mnt/hpsconfig/bin/setHpsEnv.sh PATH=${HPS_PATH}:${PATH} CLASSPATH="$

{HPS_CP}:${WEBLOGIC_CLASSPATH}${CLASSPATHSEP}$ {POINTBASE_CLASSPATH}$
{CLASSPATHSEP}${JAVA_HOME}/jre/lib/rt.jar$ CLASSPATHSEP}${WL_HOME}/
server/lib/webservices.jar${CLASSPATHSEP} ${CLASSPATH}"
6 Run the file to start the server.
Deploying to a JES Cluster

This section explains how to deploy Performance Scorecard and the Alerter (if installed) to a
JES cluster.
➤ To deploy to a JES cluster:

1 Launch the JES Admin Console.
2 Create and set up the following items as described in the JES online help or documentation:
● Cluster
● Node agent
● Server instance
3 In Common Tasks, expand Configurations > <configuration for cluster> JVM Settings.
4 On the JVM Settings page, select JVM options.
5 Scroll to the ninth line of code.
6 Delete the code after —Djava.security.policy=.
7 Click Path Settings.
8 In Native Library Path Prefix, add these lines of code:
● C:\Hyperion\9.3.1\AppServer\InstalledApps\JES\<version>\manual
\webappsconf\bin
● C:\Hyperion\Common\CSS\9.3.1.0\bin
● C:\Hyperion\Common\CLS\9.3.1.0\bin\Windows
● C:\Hyperion\Common\EssbaseRTC\9.3.1.0\bin
9 Click Save.
10 In any text editor, open asenv.bat from <AppServer>/config in any text editor.
11 Add this code: set ARBORPATH=C:\Hyperion\Common\Essbase RTC\9.3.1.0.
12 Restart the JES server.
13 In the frame to the left, select Applications > Web Application.
The Web Module page is displayed.
14 Select the first option if you are deploying locally. Otherwise, select the second option.
15 Click Next.
16 Enter a name for the Performance Scorecard application in Application Name and Context Root.
17 In Target, select the cluster, click Add, and then OK.
18 On the Web Applications Page, click Launch besides HPSWebReports.

To install the Alerter, repeat these steps, but deploy HPSAlerter.war.
Deploying to an Oracle 10G Cluster

This section describes how to deploy to a Oracle 10.1.3.1.0 cluster. To prevent the Web
application you create to deploy Performance Scorecard from inheriting unwanted runtime
settings during deployment, create an OC4J instance called HPS. Assign this instance to a group
created for Performance Scorecard.You need not modify the Oracle HTTP Server listen port(s),
but should make any required port assignments or changes before deployment. If possible,
configure ports during installation using staticports.ini as documented in the Oracle®
Application Server Installation Guide.
Preparing to Deploy
Perform these tasks before deploying to an Oracle cluster:
● Satisfy the requirements for a cluster identified in “Preparing Application Server Clusters”
on page 16.
● If Oracle 10.1.3.1.0 Server is not installed, install it. Specify that you want to use HTTP
protocol.
● Ensure that all instances of Performance Scorecard in the cluster are configured to use the
same database.
● Make any required port assignments or changes.
Creating the OC4J Instance
➤ To create the OC4J instance:

1 Start the SOA suite.
3 Create an instance called HPS and assign it to the appropriate group. In this procedure, default_group is
used. See the Oracle® Containers for J2EE Configuration and Administration Guide. Note: You will later start
the deployed web application using the port number you specify when you create the instance.
5 See “Setting Properties and Variables” on page 59.
Setting Properties and Variables
➤ To configure the HPS instance:

1 Start the HPS instance if is not already started.
2 From the Cluster Topology page, navigate to Application Server: > HPS.
3 Select Administration > Server Properties.
4 In the Command Line Options area, enter 128 MB in Initial Heap Size and 256 MB in Maximum Heap
Size.
5 In the Environment Variables area, click Add Another Row.
6 Enter the HYPERION_HOME directory you specified during installation.
7 Click Apply and restart the HPS instance.
8 See the next section.
Deploying the Web Application
➤ To deploy the web application:

1 In the Oracle® Enterprise Manager 10g Application Server Console, go to the Cluster Topology page.
2 Click the HPS instance and Application.
3 On the page that displays, click Deploy.
4 In Archive Location navigate to HPSWebReports.war. By default, this file is in <HPS_INSTALL>
\AppServer\InstalledApps\Oracle\10g\manual\webapps.
5 Click Next.
6 Enter HPS in Application Name and click Next.
7 Accept the remaining defaults on the page.
8 Click Deploy.
9 Restart the HPS instance.
10 Optional: To deploy the Alerter, repeat these steps but select HPSAlerter.war and specify a different
application name and context root. Deploy to the same instance.
Launch Performance Scorecard using the URL from the managed server. This enables you to
use the application if any of the computers in the cluster fail]
Deploying on a Thai Locale

Perform these tasks to deploy Performance Scorecard on a Thai locale:
● “Using Tomcat ” on page 68
● “Using WebLogic” on page 69
Using Tomcat
Perform this procedure to run Scorecard on a Thai locale using Tomcat.

➤ To deploy to a Thai locale:
1 Shut down the application server.
2 Shut down Performance Scorecard.
3 From: <HPS install>\AppServer\InstalledApps\Tomcat\5.0.28\<domain>\bin,
open startHPS.bat in any text editor.
4 Change this code:
set CATALINA OPTS=<original value>
to:
:set CATALINA OPTS=-<original value> - Duser.language=en -
Duser.country=US
6 Restart the application server and Performance Scorecard.
Using WebLogic
This section describes how to deploy Performance Scorecard to a Thai locale if you are using
the WebLogic application server.
➤ To deploy to WebLogic:
1 Shut down ScorecardPerformance Scorecard and the application server.
2 Open <HPS install>\AppServer\InstalledApps\WebLogic\<version>
\<domain>startHps.bat in any text editor.
3 Scroll to a line of code:
set JAVA_OPTIONS=<original value>
If you are using SDK or JDK, scroll to:set JAVA_VENDOR=SUN

Change the code to:
set JAVA_OPTIOINS=<original value> -Duser.language=en -Duser.country=US
If you are using SDK or JDK, change set JAVA_VENDOR=SUN

Deploying on a Thai Locale 69

Installing, Configuring, and
B Uninstalling Data Integration
Management Adapters
In This Appendix
Data Integration Management Adapters .........................................................................................71
About Installing Data Integration Management Adapters ......................................................................71
Installing DIM Adapter for Performance Scorecard ............................................................................72
Configuring DIM Adapter for Performance Scorecard ..........................................................................73
Uninstalling DIM Adapter for Performance Scorecard .........................................................................76
Data Integration Management Adapters

Oracle's Hyperion® Data Integration Management enables you to unite disparate data sources
across an enterprise. For example, you can integrate data stored in multiple warehouses and data
marts, relational database management systems (RDBMS), and online analytical processing
(OLAP) stores. In addition to Performance Scorecard, you can install Adapters to retrieve and
write data to Oracle's Hyperion® Financial Management – System 9 and Oracle's Hyperion®
Essbase® – System 9.
About Installing Data Integration Management Adapters

You must have administrative privileges on the computer where you install Oracle's Hyperion®
Data Integration Management Adapter for Performance Scorecard. You can install as follows:
● Typical — install all components
● Custom — Install either of these components:
❍ Client Plug-in—Enables you to configure source and target definitions for the Hyperion
application in Designer. Install on the same computer as PowerCenter Client.
❍ Reader and Writer Plug-ins—Enable you to read information from the Hyperion
application and write information to it. Install on the same computer as PowerCenter
Server. Install in the same location.
Installing the DIM Adapter for Performance Scorecard sets these variables:
● Windows:
❍ HPSCONNECTORPATH is set to <Install dir>\HPSConnector\Bin.
❍ PATH is updated in <Install dir>\HPSConnector\Bin.
Data Integration Management Adapters 71

❍ CLASSPATH is updated in <Install dir>\HPSConnector\Bin\Resources and
<Install dir>\HPSConnector\Bin\Lib\HPSPlugin.jar (Reader and Write
plug-ins).
● Reader and Writer plugins on Solaris and AIX:
CLASSPATH is updated in <Install dir>/HPSConnector/Bin/Resources and
<Install dir>/HPSConnection/Bin/Lib/HPSPLugin.jar
Installing DIM Adapter for Performance Scorecard

In addition to the regular installation, you can install the DIM Adapter for Performance
Scorecard as follows:
● In silent mode. See “Installing in Silent Mode” on page 72.
● From a console. See “Installing From a Console” on page 73.
➤ To install the DIM Adapter for Performance Scorecard:

1 From the DVD or the adapter download folder, run a file:
● Windows—setupwin32.exe
● Linux — setupLinux.bin
● AIX—setupAix.bin
● Solaris — setupSolaris.bin
● HP—UX — setupHP11.bin
2 On the Welcome screen, click Next.
3 Select a country for the installation, and click Next.
4 Select I AGREE, and click Next.
5 Specify the installation directory and click Next.
6 Click Next to accept the HYPERION_HOME directory.
7 Select a setup type, and click Next.
8 Custom installation: Select the components to instal, and click Next.
9 Confirm the installation summary, and click Next.
When the installation finishes, Configuration Guidelines are displayed.
Installing in Silent Mode

In this installation mode, the installer retrieves the installation properties from a response file
instead of displaying screens where you enter data. You can create the response file from a
template before installation, or during the installation for use in subsequent silent-mode
installations.
72 Installing, Configuring, and Uninstalling Data Integration Management Adapters

➤ To install in silent mode, run:
InstallerFile -silent -options ResponseFile
InstallerFile is the platform-specific installation launch file (such as setupwin32.exe or
setupSolaris.bin).
ResponseFile is the property file that contains the required installation parameters.
Installing From a Console

When you install in console mode, you select input from a series of menus.
➤ To install in console mode, run this command:

InstallerFile -console
InstallerFile is a platform-specific installation program, such as setupSolaris.bin.
Configuring DIM Adapter for Performance Scorecard

After installation, you must set up Oracle's Hyperion® Data Integration Management Adapter
for Performance Scorecard on the computers hosting the PowerCenter Server, Client, and
Repository Server components of Data Integration Management. See:
● “Registering With a Repository” on page 73
● “Configuring Connections” on page 74
● “Configuring JVM Options” on page 75
You can perform these tasks on Windows computers where PowerCenter Client is installed.
Registering With a Repository

If you install the Reader and Writer Plug-in, you must register the adapter with the repository.
Registration is not required for just the Client Plug-in.
➤ To register with a repository:

1 Copy Product.xml from HPSConnector\Bin to Repository Server Installation
Directory\bin\Plugin.
2 Ensure that the Data Integration Management Repository Server is running:
a. From the Windows Control Panel, select Administrative Tools.
b. Select Services.
c. In the Services window, check the status of Hyperion S9 Data Integration Management
Repository Server.
d. Click Start.
Configuring DIM Adapter for Performance Scorecard 73

Keep the window open.
3 Stop Data Integration Management Server, if it is running:
a. In the Services window, check the status of Hyperion S9 Data Integration Management
Server.
b. If the status is “Started,” click Stop.
4 Connect to the Repository Server host computer:
a. Select Start > Programs > Hyperion System 9 > Data Integration Management >
Informatica PowerCenter 7.1.4 - Client > Repository Server Administration Console.
b. In Repository Server Administration Console, right-click the name of the Repository
Server host computer, and select Connect.
c. Enter your password for the host computer, and click OK.
5 In Repository Server host computer name, click Available packages.
6 Right-click HPS.xml, and select Register.
7 Enter the repository administrator user name and password.
Note: If you use Informatica native authentication, the user name and password are
Administrator. If you use Shared Services authentication, they are admin and password.
8 When a message that the registration succeeded is displayed, click OK.
9 Repeat step 6 through step 8 for each adapter that you use.
See “Registering and Unregistering Repository Plug-ins” in the Informatica PowerCenter
Repository Guide.
Configuring Connections
Before you can extract data from sources or write data into targets, you must configure an
application connection in the Workflow Manager. You will specify attributes that Data
Integration Management Server uses to connect to a database during a Data Integration
Management session. The application connections that you define in Workflow Manager are
saved in Data Integration Management Repository.
➤ To configure application connections:

1 Ensure that Data Integration Management Repository Server is running:
a. From the Control Panel, select Administrative Tools.
b. Select Servers.
c. In the Services window, check the status of Hyperion S9 data Integration Management
Repository Server.
d. Click Start.
2 Start the repository:

a. Select Start > Programs > Hyperion System 9 > Data Integration Management >
Informatica PowerCenter 7.1.4 - Client > Repository Server Administration Console.
b. In Repository Server Administration Console, right-click the name of the Repository
Server host computer and select Connect.
c. Enter your password for the host computer, and click OK.
d. In Repositories, double-click the repository name.
Click Start.
3 Select Start > Programs > Hyperion System 9 > Data Integration Management > Informatica PowerCenter
7.1.4 - Client > Workflow Manager.
4 In Workflow Manager, connect to the repository:
a. In Repository Navigator, double-click the repository.
b. Enter the repository administrators user name and password, and then click Connect.
5 Select Connections > Application.
6 Click New.
7 Select the Hyperion Performance Scorecard Connection and click OK.
8 Enter this data and click OK:
● Name—A name for the connection
● User Name andPassword—Your user name and password for Performance Scorecard
● URL—The Hyperion product application URL that you want to use
● Host or ServerHost—The name of the computer hosting Oracle's Hyperion® Performance
Scorecard – System 9.
● Port—The port number used by the application.
See the Hyperion System 9 Installation Start Here for all default Hyperion product ports.
● Cluster —The name of the registered cluster where the application runs.
Application Connection Browser lists the new application connection.
Tip:
To edit or delete connections, select them in the Application Connection Browser and click Edit
or Delete.
Configuring JVM Options

➤ To configure JVM options:
1 Start Informatica Server Setup:
● Windows—Select Start > Programs > Hyperion System 9 > Data Integration Management
> Informatica PowerCenter 7.1.4 - Server > Informatica Server Setup.
Configuring DIM Adapter for Performance Scorecard 75

● UNIX—Run pmconfig from $DIM_HOME/Server/bin.
Solaris: Run ./pmconfig. The PM_HOME environment variable must reference the
PowerCenter Server installation directory.
2 Select Configure Informatica Service and click Continue.
3 Select JVM Options.
4 In VM Location, enter the fully qualified path to jvm.dll in your JAVA_HOME directory and click OK.
Uninstalling DIM Adapter for Performance Scorecard

➤ To uninstall a Data Integration Management adapter:
1 Run a file:
● Windows — uninstaller.exe
● UNIX—uninstaller.bin
2 On the Welcome screen, click Next.
3 Select the components to uninstall, and click Next.
4 On the summary screen, click Next.
5 When a summary displays, click Finish.
6 Optional: Remove the adapter from a repository:
a. Open Oracle's Hyperion® Data Integration Management Repository Server
Administration Console: Start > Programs > Hyperion System 9 > Data Integration
Management > Informatica PowerCenter 7.1.4–Client > Repository Server
Administration Console.
b. Select the repository in which the adapter is registered.
c. Stop the repository if it is running.
d. Click Repository > Registered packages and select HPS.xml.
e. Click Unregister.
f. In Remove Repository plug-in, enter the repository user name and password, and click
OK.
Uninstalling in Silent Mode

If you uninstall in silent mode, the uninstaller retrieves options from a response file instead of
displaying data entry screens.
➤ To uninstall in silent mode, run:

UninstallerFile -silent -options ResponseFile
UninstallerFile is Uninstall.exe or Uninstall.bin.

ResponseFile is the property file containing the parameters required for the uninstallation.
The uninstaller file is in the Uninstall subdirectory of the adapter installation directory.
Uninstalling From a Console

When you uninstall in console mode, you select input from a series of menus that are displayed.
➤ To uninstall from a console, run this command:

UninstallerFile -console
UninstallerFile is Uninstall.exe or Uninstall.bin.
The uninstaller file is in the Uninstall subdirectory of the adapter installation directory.
Uninstalling DIM Adapter for Performance Scorecard 77

A B C D E H I J L M N O P R S T U W
Index
Performance Scorecard deployment, 28

uninstalling, 35 deployment, profiles and domains, 30
preferred logging priority, setting, 50
product upgrades, 25
A provider search order, setting, 49
Alerter
reconfiguration, 24
description, 7
Shared Services registration, 27
installation, 19
requirements, 24
application database
restricted characters, 24
configuring, 26
task sequence, 24
description, 8
tasks, 23
requirements, 14
Thai locale deployment, 68
upgrading, 37
token time-out, setting, 51
application server
troubleshooting, 24
deployment, 28
Hyperion Configuration UtilityConfiguration Utility
manual deployment, 55
description, 23
requirements
cluster, 16
single server, 16 D
authentication Data Integration Management Adapter
basic JDBC, enabling, 41 configuring, 73
LDAP or MSAD, enabling, 45 installing, 72
NTLM, enabling, 42 overview, 71
uninstalling, 76
database
B configuration, 28
Basic JDBC authentication
dedicated for Performance Scorecard, 8
enabling, 41
existing, using, 37
requirements
C general, 14
characters, restricted, 24 IBM DB2, 15
clustered application servers Microsoft SQL Server, 14
manual deployment, 61 deployment
requirements, 16 cluster requirements, 16
configuration manual to WebLogic, 55
clustered application server deployment, 61 options, 26, 28
Data Integration Management Adapters, 73 Thai locale , 68
database, 28 to application server cluster, 61
Index 79
E WebLogic, 63
error logs, 24 WebSphere, 62
existing release of Performance Scorecard, upgrading, MS SQL Server requirements, 14
37 MSAD provider, enabling, 45
external authentication
MSAD or LDAP, enabling, 45
NTLM, enabling, 42
N
Netegrity SiteMinder, using, 46
NTLM
H multiple domain support, 44
HYPERION_HOME UNIX support, 44
contents, 9
default location, 8
overview, 8
O
Oracle
HYPERION_HOME environment variable, 8
10.1.3.1.0 application server, single server
deployment, 58
I cluster application server deployment, 67
IBM DB2, requirements, 15 database requirements, 14
IBM WebSphere
manual deployment to single server, 56
Import\Export Flat File Utility
P
Performance ScorecardPerformance Scorecard
description, 7
configuring, 23
installation, 19
existing release, updating, 37
installation
installation, 19
methods, 19
requirements, 13
starting, 33
J post-configuration tasks
JES Shared Services projects, setting up, 53
cluster deployment, 66 preferred logging priority, setting, 50
manual deployment provider search order, setting, 49
cluster, 66 provisioning users in Shared Services, 54
single server, 57
R
L reconfiguration, 24
LDAP provider, enabling, 45 registration, Shared ServicesShared Services, 27
repository plug-in
registering, 73
M requirements
manual deployment
application server
single Oracle application server, 58
cluster, 16
single server
single server, 16
JES, 57
configuration, 24
WebSphere, 56
database, 14
single server, WebLogic, 55
IBM DB2, 15
to application server cluster
Microsoft SQL Server, 14
JES, 66
Essbase, 17
Oracle, 67
80 Index
single application servers, 16 cluster deployment, 63

Thai locale, 15 manual deployment, 55
UNIX, 13 single profiling, 30
restricted characters, 24 WebSphere
cluster deployment, 62
manual deployment, 56
S single domain, 30
Shared Services
Windows services, 29
stopping, 32
starting, 31
users, provisioning, 53
using with Performance Scorecard, 53
starting
Performance Scorecard, 33
stopping
Shared Services, 32
T
Thai locale, deployment, 68
Tomcat
deploying on Thai locale, 68
troubleshooting, 24
U
uninstalling
UNIX
requirements, 13
using NT LAN Manager, 44
updating Performance Scorecard, 37
upgrades
configuring, 25
user directory
deleting, 49
enabling, 40
modifying, 49
user rights
NTLM, establishing, 42
Windows 2000, establishing, 43
Windows NT, establishing, 43
users
creating and provisioning in Shared Services, 54
synchronizing between Shared Services and
W
WebLogic
Index 81
82 Index

Oracle Hyperion Performance Scorecard Install

Diunggah oleh

Informasi Dokumen

Deskripsi Asli:

Judul Asli

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

Oracle Hyperion Performance Scorecard Install

Diunggah oleh

Hak Cipta:

Format Tersedia

HYPERION® PERFORMANCE SCORECARD – SYSTEM 9

Chapter 2. Planning the Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Chapter 3. Installing Performance Scorecard and Optional Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Chapter 4. Configuring Performance Scorecard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Chapter 5. Uninstalling Performance Scorecard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Chapter 6. Upgrading Scorecard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Chapter 7. Configuring Performance Scorecard for External Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Chapter 8. Setting up Projects and Provisioning Users in Shared Services . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Appendix A. Manual Application Server Deployment Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Appendix B. Installing, Configuring, and Uninstalling Data Integration Management Adapters . . . . . . . . . . . . . 71

About Performance Scorecard

Table 1 Components You Can Install

Component Description Installation

Alerter Enables users to monitor performance Optional component with custom

About Performance Scorecard 7

The Application Server

See “Changing the HYPERION_HOME Location” on page 10.

Table 2 HYPERION_HOME 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

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

JDBC JDBC files

JRE Java Runtime Environment files

lib common internal library files

loggers Files for external authentication logging

ODBC ODBC drivers

Opatch Oracle patching tool files; for future use

PERL Scripting language files

SAP SAP files

SharedServices Supporting files for Shared Services

XML Common XML components

Changing the HYPERION_HOME Location

➤ To change the Hyperion Home location:

Creating Installation Directories on UNIX

Preparing Microsoft SQL Server

➤ To prevent the naming conflict:

14 Planning the Installation

➤ To prepare the IBM DB2 server:

Configuring the JVM on a Thai Locale

Preparing Application Server Clusters

Creating a Temporary Directory

Preparing an Oracle Server Cluster

16 Planning the Installation

Preparing a WebLogic Cluster

Preparing a WebSphere Cluster

Preparing to use Essbase

18 Planning the Installation

You can install Performance Scorecard as follows:

Installing Performance Scorecard

Installing Using the Installation Program

➤ To install Performance Scorecard:

Installing Performance Scorecard 19

Operating System File

Microsoft Windows HPSsetupwin32.exe

Sun Solaris HPSsetupsolarisSparc.bin