ESSBASE® ADMINISTRATION SERVICES - Oracle...Administration Services Introduction 9Administration...

E S S B A S E ® A D M I N I S T R A T I O N S E R V I C E S

R E L E A S E 9 . 2 . 1

I N S T A L L A T I O N G U I D E

Essbase Administration Services Release 9.2.1 Installation Guide

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

Authors: Loren Davidson

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 iii

Contents

CHAPTER 1 Installation Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Hyperion Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Administration Services Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Administration Services Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Relational Database Management System (RDBMS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Application Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Java Development Kit (JDK) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Analytic High Availability Server Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Analytic Services Smart View Provider Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Hyperion Business Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Hyperion Shared Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

CHAPTER 2 Installation Sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Essbase Installation Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

CHAPTER 3 Planning the Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Essbase Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Hardware Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Software Support Matrix for Windows and UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Detailed Memory Requirements for Administration Services . . . . . . . . . . . . . . . . . . . . . . . 31

Runtime Error Message on AIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Release Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Supported Essbase Server Releases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

64-bit Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Supported Analytic High Availability Server Releases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Supported Analytic Server Smart View Provider Releases . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Administration Services Server and Administration Services Console Compatibility . . . 34

Port Numbers Used by Hyperion Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

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

Deployment Example and Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Deployment of Administration Services with Essbase Server . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

iv Contents

Deployment Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Deployment and Configuration Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Upgrading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

CHAPTER 4 Installing Administration Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Launching Installers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Installing Administration Services Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

What Happens During Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Files Installed in the EASPATH Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Documentation Installed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

About Hyperion Home . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Hyperion Home Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Files Installed in the HYPERION_HOME Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Changing the Hyperion Home Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Selecting the ESSLANG Value . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Specifying Ports for Apache Tomcat . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Setting Up and Running Silent Installations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

CHAPTER 5 Configuring and Setting Up Administration Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Hyperion Configuration Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Task Sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Configuring Product Upgrades . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Launching the Configuration Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Registering Products with Shared Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Configuring Relational Storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Changing the Database Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Deploying Products to Application Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Deregistering Products with Shared Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Reconfiguration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Configuration Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Verifying Startup Dependencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Starting Shared Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Verifying Successful Startup of Shared Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Completing Advanced Installation Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Starting Administration Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Shutting Down Administration Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

Stopping and Restarting the MySQL Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

Running Administration Services Server as a Windows Service . . . . . . . . . . . . . . . . . . . . 71

Implementing SSL on Apache Tomcat . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Setting Up Administration Services Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

Setting Up Business Rules Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Contents v

Backing Up and Restoring User Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

Setting Up an SMTP Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

CHAPTER 6 Uninstalling Administration Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

CHAPTER 7 Upgrading Administration Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

Upgrading Administration Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

Uninstalling Previous Releases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

APPENDIX A Manually Configuring Third-Party Relational Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

Configuring an Oracle Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

Configuring an IBM DB2 Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

Configuring a SQL Server Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

Changing the Database Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

APPENDIX B Manually Configuring Web Application Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

Configuring BEA WebLogic 9.2 (MP1) Application Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

Preparing to Configure WebLogic 9.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

Creating a Domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

Deploying to WebLogic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

Configuring BEA WebLogic 8.1.4 Application Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

Configuring WebLogic 8.1.4 Application Servers on Windows . . . . . . . . . . . . . . . . . . . . . 96

Configuring WebLogic 8.1.4 Application Servers on UNIX . . . . . . . . . . . . . . . . . . . . . . . . 99

Enabling SSL for WebLogic 8.1.4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102

Configuring IBM WebSphere 6.1 Application Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

Preparing to Configure Websphere 6.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

Creating a Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

Deploying Administration Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

Configuring IBM WebSphere 5.1.1.7 Application Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

Configuring WebSphere 5.1.1.7 Application Servers on Windows . . . . . . . . . . . . . . . . . . 106

Configuring WebSphere 5.1.1.7 Application Servers on UNIX . . . . . . . . . . . . . . . . . . . . 109

Enabling SSL for WebSphere 5.1.1.7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

Configuring Oracle 10g Release 3 (10.1.3.1.0) Application Servers . . . . . . . . . . . . . . . . . . . . . 113

Preparing to Configure Oracle 10g Release 3 (10.1.3.1.0) Application Servers . . . . . . . . 113

Creating an OC4J Instance and Setting Properties and Variables . . . . . . . . . . . . . . . . . . . 113

Deploying to Oracle 10g Release 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115

Verifying the Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

vi Contents

Installation Overview 7

C h a p t e r

1Installation Overview

This chapter introduces you to Essbase Administration Services and explains how to deploy this administration tool.

In This Chapter Hyperion Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Administration Services Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Administration Services Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Analytic High Availability Server Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Analytic Services Smart View Provider Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Hyperion Business Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Hyperion Shared Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

8 Installation Overview

Hyperion OverviewHyperion is a comprehensive Business Performance Management system. It integrates financial applications with a business intelligence platform to provide a modular system that adapts to any business need. The major components of Hyperion are Hyperion® Foundation Services, Hyperion® Reporting and Analysis, and Hyperion® Applications+.

Foundation Services is a base of common technologies used by multiple products. It eases the installation and configuration process and provides metadata management and a common Microsoft Office interface. Foundation Services includes Hyperion® Shared Services, Hyperion® Data and Application Integration, Hyperion® Data Relationship Management, Hyperion® Workspace, and Hyperion® Smart View for Office.

Reporting and Analysis is a comprehensive business intelligence platform. It provides management reporting and analysis from any data source, including transactional systems, data warehouses, SAP BW, Hyperion® Essbase® – System 9, and Hyperion financial applications.

Applications+ is a set of packaged applications for planning and modeling, consolidation, and scorecarding.

Administration Services Introduction 9

Administration Services IntroductionAdministration Services is the cross-platform framework for managing and maintaining the Essbase environment. This product provides the following:

● The functionality of Application Manager

● Additional administrative features and an interface for Essbase administration tools, such as MaxL

● A framework for plug-in components

● Administration of Analytic High Availability Servers

● Administration of Analytic Services Smart View Provider

● Administration of Hyperion Business Rules

ArchitectureAdministration Services works with Essbase Servers in a three-tiered system consisting of a client user interface, a middle-tier server, and one or more database servers (Essbase Servers). The middle tier coordinates interactions and resources between the user interface and Essbase Servers. The three tiers may or may not share a computer or platform. See “Deployment Scenarios” on page 38.

The three tiers include the following:

● Client tier: Administration Services Console—Java client console enabling administrators to manage the Essbase environment from a robust graphical user interface.

● Middle tier: Administration Services Server—Java middle-tier server communicating with both Administration Services Console and Essbase Servers. Administration Services Server maintains communication and session information for each connection to Essbase Servers. Administration Services Server also stores documentation files so that console users can access documentation without having to install it locally.

● Database tier: Essbase Server—one or more Essbase Servers to store and process multidimensional database information. Essbase Server are installed separately from Administration Services.

Note: If you do not want to install Administration Services Console on a client computer, you can launch it from a Web browser instead. See “Starting Administration Services Console using Web Launch” on page 66.


Administration Services Server is the middle tier between Administration Services Console and Essbase Servers.

Figure 1 Administration Services Architecture

Administration Services ComponentsAdministration Services consists of Administration Services Server and Administration Services Console.

Administration Services Server requires the following third-party components:

● A relational database management system (RDBMS), required only for the Log Analyzer feature and Hyperion Business Rules

● An application server

● Java Development Kit (JDK)

Relational Database Management System (RDBMS)Administration Services Server requires a relational database for storage of Log Analyzer information and for Business Rules. A default relational database is installed and configured. You can also deploy to other supported third-party databases.

For information about supported databases, see “Software Support Matrix for Windows and UNIX” on page 27.

For instructions to automatically deploy to supported third-party databases using the Configuration Utility, see Chapter 5, “Configuring and Setting Up Administration Services.”

For instructions to manually configure supported third-party databases, see Appendix A, “Manually Configuring Third-Party Relational Databases.”

Analytic Services Smart View Provider Administration 11

Application ServerAdministration Services Server requires an application server, which provides the business logic for Administration Services. A default application server is installed and configured. You can also deploy to other supported third-party application servers.

For information about supported application servers, see “Software Support Matrix for Windows and UNIX” on page 27.

For instructions to automatically deploy to supported third-party application servers using the Configuration Utility, see Chapter 5, “Configuring and Setting Up Administration Services.”

For instructions to manually configure supported third-party application servers, see Appendix B, “Manually Configuring Web Application Servers.”

Java Development Kit (JDK)Administration Services is a Java application and therefore requires a Java Development Kit (JDK) to execute the program. This release requires JDK version 1.4.2 and installs this version automatically. For information about Java requirements, see “Software Support Matrix for Windows and UNIX” on page 27.

Analytic High Availability Server AdministrationYou can use Administration Services Console to manage Essbase Server databases that are connected through Analytic High Availability Servers. You must install, configure, and start Analytic High Availability Servers separately from Administration Services.

Each Administration Services user can add Analytic High Availability Servers to the Enterprise View tree in Administration Services Console. The added Analytic High Availability Servers are listed under the Analytic High Availability Servers node in Enterprise View. For instructions about adding and managing Analytic High Availability Servers, see Analytic Essbase Administration Services Online Help.

You can install Administration Services on the same or another computer as Analytic High Availability Server, in various configurations. Analytic High Availability Servers can be configured for TCP/IP or HTTP operation; both modes can be managed through Administration Services. For information about supported versions of Analytic High Availability Server, see “Release Compatibility” on page 33.

For information about installing and configuring Analytic High Availability Servers, see Analytic High Availability Services Installation Guide.

Analytic Services Smart View Provider AdministrationAnalytic Services Smart View Provider is a middle-tier data source provider for Hyperion Smart View for Office clients. This provider interacts with Essbase Server and provides scalability and reliability in a distributed Web-enabled enterprise environment.


Analytic Services Smart View Provider is administered through Administration Services Console.

Administration Services Console enables you to:

● Administer Analytic Services Smart View Providers

● Add, remove, and list standalone Essbase Server being accessed by the Smart View client

● Create, remove, and list Essbase Clusters being accessed by the Smart View client

● Add and remove Essbase databases belonging to an Essbase Cluster

● Enable or disable database components belonging to an Essbase Cluster

● Monitor Analytic Services Smart View Provider sessions

● Set the type of log messages to view

Hyperion Business RulesIn this release of Administration Services, Business Rules is installed and configured automatically with Administration Services. The Administration Services installation installs all necessary Business Rules files, and Business Rules is configured automatically when you use the Configuration Utility to configure Administration Services.

Business Rules guides users through the creation, execution, and management of business rules on Essbase Server.

In a traditional multidimensional application, users must program complicated calculations to perform the business rules they need. In addition, business rule logic creation, validation, and error detection are usually time consuming and frustrating for users. Also, users must modify calculations often, sometimes weekly or hourly, to keep up with business demands. These frequent changes create high maintenance and incur high cost for the customers of Essbase applications.

Business Rules improves the response time to changing business application needs, shortens application development cycles, increases business user productivity, improves re-use of application components, and increases the overall return on analytic application investments.

The main features and benefits of Business Rules are described in the following topics.

● Easy to Create

❍ Macros simplify the creation of business rules and sequences, and save business rule designers time by enabling them to reuse pieces of business rules in other business rules or macros.

❍ Variables of the saved selection type can be used not only at run-time, but also during design time to make business rules easier to design.

❍ Pre-defined and re-usable formulas that define unique cost and revenue calculations save business rule designers time during the design process.

❍ The graphical depiction of components, formulas, and actions makes it easy to construct business rules in a multidimensional application.

Hyperion Shared Services 13

● Easy to Use

❍ Business rules can be launched by business users via Business Rules within Administration Services Console, the Business Rules Web Launcher, the Business Rules Command Line Launcher, and the Hyperion Planning Web Client.

❍ Business rules can be launched in all Essbase Server environments.

❍ Business rules can be stored and run on a server across a wide area network (WAN).

❍ Business rules with run-time prompts ensure valid inputs from budget preparers.

❍ Entry of run-time prompt values during launching makes a single, centrally created business rule reusable by several users.

● Easy to Maintain

❍ The Business Rules architecture supports enterprise-wide maintenance and methods of use that can be successfully managed and deployed to multiple business users.

❍ Business rules, sequences, macros, variables, and projects can be stored in the following repositories: Microsoft SQL Server, Oracle, or DB2 for shared, enterprise-wide access.

❍ Use of a central repository makes administration and maintenance of business rules easy, because the repository stores information for several applications in one database.

❍ The logical organization of business rules, sequences, macros, and variables into projects makes them easier to find and maintain.

Hyperion Shared ServicesHyperion Hub functionality is now part of Hyperion Shared Services.

Features enabled by Shared Services:

● User provisioning

● External authentication definition

● Metadata synchronization

● Data synchronizatyes n

● Task flow management

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

Installation Sequence 15

C h a p t e r

2Installation Sequence

This chapter provides the following information about installing, configuring, and setting up Analytic Services components:

● High level task flow identifying basic steps

● Installation checklist to guide you through each step in the installation and configuration process

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

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

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

STEP INSTRUCTION PRODUCT COMPONENT DOCUMENTATION

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

Shared Services installer

Hyperion Configuration Utility™

Shared Services Installation Guide

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

Shared Services External Authentication Configuration Console

Shared Services Installation Guide

3 Install Hyperion products. Hyperion product installers Product installation guides

http://edelivery.oracle.com/

http://edelivery.oracle.com/

16 Installation Sequence

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

Hyperion Configuration Utility Product installation guides

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

Shared Services User Management Console

Shared Services User Management Guide

STEP INSTRUCTION PRODUCT COMPONENT DOCUMENTATION

Essbase Installation Checklist 17

Essbase Installation Checklist This checklist contains the detailed steps required for a successful installation of Essbase product components:

● Essbase (Essbase Server and clients)

● Administration Services

● Integration Services

● Analytic High Availability Services

● Analytic Services Smart View Provider (and Smart View client)

Note: Analytic Services Smart View Provider does not automatically install the Smart View client, but places SmartView.exe in the SUP_HOME/redist directory.

This checklist and Chapter 3, “Planning the Installation” cover all Essbase product components. The other chapters in this guide provide installation information specifically for Administration Services.

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

✔ Install Shared Services and Configure the Shared Services Application Server and RDBMS Reference

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

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

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

Note: These steps don't apply if you are using Essbase in native security mode and you are not using external authentication.

Hyperion Shared Services Installation Guide

✔ Configure the Shared Services External Authentication Provider Reference

1. Ensure that your Shared Services server is running.

2. Using Shared Services, configure External Authentication Provider.

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

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

4. Optionally, configure Shared Services to use Single Socket Layers and install the Hyperion Remote Authentication Module.

Note: These steps don't apply if you are using Essbase in native security mode and you are not using external authentication.

Hyperion Shared Services Installation Guide


✔ Install Essbase Reference

Step 1. Prepare to Install Essbase

Download Essbase components from the Oracle® E-Delivery site. Essbase includes the following components:

● Essbase


● High Availability Services

● Analytic Services Smart View Provider

Print and review the Readmes and installation documentation before installing products.

Readmes for:

● Essbase




● Smart View

Installation Guides:

● Hyperion Essbase – System 9 Installation Guide

● Essbase Administration Services Installation Guide

● Analytic High Availability Services Installation and Administration Guide

● Analytic Services Smart View Provider Installation and Administration Guide

Step 2. Install Essbase Components

Install Essbase components:

● Essbase (install client components first, followed by Essbase Server)




Note: Smart View client installation instructions can be found in the Analytic Services Smart View Provider Installation and Administration Guide.

Common components are installed to the Hyperion_Home\Common directory to be shared by all products.

Readmes for:

● Essbase


● Integration Services



● Smart View

Installation Guides:

● Hyperion Essbase – System 9 Installation Guide


● Analytic Integration Services Installation Guide



Essbase Installation Checklist 19

✔ Configuration Tasks Reference

Activate and configure Essbase components and register with Shared Services using the Hyperion Configuration Utility

● Configure Essbase Components and register with Shared Services.

❍ Essbase

❍ Administration Services

❍ High Availability Services

❍ Analytic Services Smart View Provider

● Specify the Shared Services server location

● Configure relational databases and repositories (if applicable)

● Auto-deploy products to application servers (if applicable)

Note: The Shared Services Server must be running to perform this step for Administration Services and for Analytic Services.

All of the installation guides for the Essbase components contain configuration information.

● Analytic Services Installation Guide




✔ Additional Configuration Tasks Reference

● Perform additional configuration tasks for Essbase, such as installing documentation or configuring Essbase for relational integration.

● No additional tasks are required for Administration Services, High Availability Services, or Analytic Services Smart View Provider.

● For Essbase, see Hyperion Essbase – System 9 Installation Guide Chapter 5, Configuring and Setting Up Essbase

✔ Assign Roles for Shared Services User Management and Provision Users Reference

After migrating users to Shared Services, a Shared Services administrator must perform the following tasks:

● Assign the Project Manager role to users who are responsible for creating projects and assigning applications to projects.

● For each application, assign the Provisioning Manger role to users who are responsible for assigning roles and access control permissions to users of the application.

● Assign the Directory Manager role to users who are responsible for managing the native Shared Services directory.

Project Managers can now create projects and add applications to projects as necessary. Provisioning Managers for each application can now provision users and groups (assign roles and access control permissions) for their applications.

Hyperion System 9 Shared Services User Management Guide

Planning the Installation 21

C h a p t e r

3Planning the Installation

Read this chapter for information on planning the installation of Essbase products and components on all supported platforms.

In This Chapter Essbase Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Release Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Port Numbers Used by Hyperion Products. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Deployment Example and Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Deployment of Administration Services with Essbase Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Upgrading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

22 Planning the Installation

Essbase RequirementsAnalytic Services consists of five separate components:

● Essbase, including Essbase Server and Essbase client components (runtime client, Spreadsheet Add-in, Application Programming Interface)

● Essbase Administration Services, which includes Administration Services Server and Administration Services Console

● Essbase Integration Services

● Analytic High Availability Services

● Smart View, which includes Analytic Services Smart View Provider and the Smart View client

Different Essbase components may have different requirements. For example, Administration Services requires deployment of an application server while Essbase does not.

Note: Estimated disk space and RAM requirements in this document are approximate. The actual requirements may be higher.

This section contains requirements for a representative deployment with up to 150 total users, 30-40 concurrent users, and one Essbase application. (See “Deployment Example and Requirements” on page 36.)

For larger deployments, we highly recommend that you contact Hyperion Consulting Services to determine the appropriate number of servers for your environment.

The following topics describe hardware and software requirements for Essbase:

● “Hardware Requirements” on page 22

● “Software Support Matrix for Windows and UNIX” on page 27

● “Deployment Example and Requirements” on page 36

Hardware RequirementsThe tables in each of the following topics provide hardware requirements for Essbase components:

● “Hardware Requirements for Windows” on page 23

● “Hardware Requirements for UNIX” on page 25

Note: Disk space estimates may include documentation files (if applicable) and Hyperion common components. Documentation is installed automatically with some products. The installer program calculates the amount of required disk space, based on your installation choices.

Essbase Requirements 23

Hardware Requirements for Windows

Table 1 Hardware Requirements for Windows

Essbase (Essbase Server)

Disk space Approximately 260 MB for Essbase Server software and the sample applications

RAM 100 MB

Note: The base recommendation for running Essbase Server and its sample applications is 64 MB. Start with this amount and then allocate additional memory to accommodate the Essbase Server applications.

Processor ● Pentium or higher for 32-bit Analytic Services

● Itanium 2 for 64-bit Analytic Services

Network protocol TCP/IP

Essbase Clients for Windows (Runtime Client and Spreadsheet Add-in)

Disk space ● 20 MB for Spreadsheet Add-in

● 20 MB for Runtime Client

● 20 MB for Application Programming Interface

RAM ● 16 MB for Spreadsheet Add-in

● 64 MB for Application Programming Interface (128 or more recommended)

Processor ● Pentium or equivalent, or better for 32-bit Analytic Services


Network protocol TCP/IP

Display Resolution of at least 800 x 600 (1024 x 768 or more recommended)

Essbase Administration Services: Administration Services Server

Disk space 400 MB minimum for 32-bit and 64-bit Windows platforms

● This estimate includes documentation files and Hyperion common components. The installer program calculates the amount of required disk space, based on your installation choices.

● Allow extra disk space for data files and outline files that are copied to Administration Services Server during data loads and outline editing, respectively.

RAM See the “Detailed Memory Requirements for Administration Services” on page 31.

Note: 512 MB for 64-bit Windows platforms

Processor ● Pentium or equivalent, or higher for 32-bit Administration Services

● Itanium 2 for 64-bit Administration Services

Network protocol HTTP


Essbase Administration Services: Administration Services Console

Disk space 150 MB minimum

● This estimate includes documentation files and Hyperion common components. The installer program calculates the amount of required disk space, based on your installation choices.


Note: 512 MB for 64-bit Windows platforms

Processor ● Pentium or equivalent, or better for 32-bit Administration Services



Screen resolution 1024 x 768

Analytic High Availability Services

Disk space 148 MB

RAM 128 MB

Processor ● Pentium or equivalent, or better for 32-bit Analytic High Availability Services

● Itanium 2 for 64-bit Analytic High Availability Services

Network protocol TCP/IP, HTTP

Analytic Services Smart View Provider

Disk space ● 250 MB on 32-bit Windows

● 330 MB on 64-bit Windows

RAM 128 MB

Processor ● Pentium or equivalent, or better for 32-bit Analytic Services Smart View Provider

● Itanium 2 for 64-bit Analytic Services Smart View Provider

Network Protocol HTTP

Smart View client

Disk space Negligible

RAM Negligible

Processor Pentium or equivalent.

Table 1 Hardware Requirements for Windows


Hardware Requirements for UNIX

Table 2 Hardware Requirements for UNIX

Essbase

Disk space Solaris, Linux, and AIX:

310 MB is required.

Note: To run Essbase on AIX 5.2, you may need to update the C++ runtime environment. See “Updating C++ Runtime Environment for AIX” on page 33.

HP-UX (32-bit and 64-bit):

480 MB is required.

Swap space At least two times the amount of physical memory is recommended when physical memory is less than .5 GB. Contact your system administrator or hardware vendor for optimum swap configuration.

RAM 128 MB RAM (256 or more MB recommended)

Note: Large databases have greater memory requirements.

Thread type POSIX Kernel Threads (included with the operating system)

Processor Solaris:

● Sun SPARC or ULTRASPARC

AIX:

● PowerPC

Linux:

● Intel X86

HP-UX:

● PA-RISC for 32-bit Essbase

● Itanium for 64-bit Essbase

Network protocol TCP/IP (included with the operating system)

Essbase Application Programming Interface

Disk space 20 MB for API

RAM 128 MB (256 or more MB recommended)

Processor Same as Essbase Server

Network protocol TCP/IP (included with the operating system)

Essbase Administration Services Administration Services Server:

Disk space ● 300 MB minimum for Solaris, AIX, and Linux

● 500 MB minimum for HP-UX 11i

● 400 MB minimum for 64-bit HP-UX

Note: Allow extra disk space for data files and outline files that are copied to Administration Services Server during data loads and outline editing, respectively.


Note: 512 MB minimum for 64-bit HP-UX


Processor Same as Essbase Server


Essbase Administration Services Administration Services Console

Not applicable


Disk space Disk space:

● 85 MB for the server software, API, sample applications, and documentation

● 20 MB for the Essbase libraries

● 40 MB for the Java Runtime Environment

RAM Physical memory 128 MB RAM

Processor Solaris:


AIX:

● PowerPC

Linux:

● Intel X86

HP-UX:


● Itanium 2 for 64-bit Essbase

Network protocol TCP/IP (included with the operating system), HTTP


Disk Space ● 125 MB on Solaris

● 140 MB on AIX

● 120 MB on Linux

● 525 MB on HP-UX 32-bit

● 800 MB on HP-UX 64-bit

RAM 128 MB

Processor Solaris:


AIX:

● PowerPC

Linux:

● Intel X86

HP-UX:


● Itanium 2 for 64-bit Essbase



Software Support Matrix for Windows and UNIXSoftware requirements for all products are itemized in Table 3. Requirements are included for supported third-party products and variances by product.

Network Protocol HTTP

Smart View client

Not applicable

Table 3 Essbase Software Support Matrix for Windows and UNIX

Essbase Server

Operating system ● Windows 2000 Server (SP4)

● Windows 2003 (SP1)

● Windows 2003 Server Enterprise Edition 64-bit (on Itanium only)

● AIX V5.2 and V5.3

● Sun Solaris 8, 9

● HP-UX 11i

● HP-UX 11.23 (on Itanium only) for 64-bit Analytic Services

● Redhat Linux AS 3.0 (Intel X86 only. Support for the Sun JRE only.)

Note: To run Essbase on AIX, you may need to update the C++ runtime environment. See “Updating C++ Runtime Environment for AIX” on page 33.

Java Runtime Environment ● Java Runtime Environment (JRE) 1.4.2_08, installed automatically on supported Windows, HP-UX, Solaris, and Linux platforms.

● Java Runtime Environment (JRE) 1.4.2 bld cal 1420-2004026 AIX

Note: On AIX, you must install JRE separately. Hyperion provides the JRE installation files for AIX.

Authentication sources ● IBM Tivoli Directory Server V5.2

● Lightweight Directory Access Protocol (LDAP)

❍ Sun One 5.2

❍ Novell eDirectory 8.7

❍ IBM Directory Server 5.1

❍ Domino LDAP 5.x and 6.0

● Microsoft Active Directory 2000, 2003

● Microsoft NTLM

● NTLan Manager (NTLM)

● OpenLDAP 2.2.23

Required Hyperion Products ● Shared Services

● License Server



Essbase Administration Services: Administration Services Server

Operating system ● Windows 2000 Server (SP4)

● Windows 2003 (SP1)


● AIX V5.2 and V5.3

● Sun Solaris 9,10

● HP-UX 11i

● HP-UX 11.23 (on Itanium only) for 64-bit Essbase

● Redhat Linux AS 3.0 (Intel X86 only. Support for the Sun JDK only.)

Java application server ● Apache Tomcat 5.0.28, installed automatically on all platforms

● BEA WebLogic 8.1.4

● IBM WebSphere 5.1.1.7

Relational database ● MySQL 4.0.12 (32-bit), 4.0.23 (64-bit HP-UX), installed automatically on all platforms

● Oracle 9i - 9.2.0.5

● Oracle 10g - 10.1.02 (10.1.03 for Linux)

● IBM DB2 8.1 FP7a

● IBM DB2 8.2

● Microsoft SQL Server 2000 SP3a

Supported authentication sources

● Lightweight Directory Access Protocol (LDAP)

❍ Sun One 5.2

❍ Novell eDirectory 8.7

❍ IBM Directory Server 5.1

❍ Domino LDAP 5.x and 6.0

● NTLan Manager (NTLM)

● Microsoft Active Directory 2000, 2003

● IBM Tivoli Directory Server V5.2

● OpenLDAP 2.2.23

Java components ● Java Development Kit (JDK) 1.4.2_08, installed automatically on supported Windows, HP-UX, Solaris, and Linux platforms

● Java Runtime Environment (JRE) 1.4.2 bld cal 1420-2004026 on supported AIX platforms

Required Hyperion Products ● Essbase

● Shared Services (unless using Administration Server in native security mode)



Essbase Administration Services: Administration Services Console

Operating system ● Windows 2000 (SP4)

● Windows 2003

● Windows XP Professional


Java components ● Java Development Kit (JDK) 1.4.2_08, installed automatically on supported Windows, HP-UX, Solaris, and Linux platforms

● Java Runtime Environment (JRE) 1.4.2 bld cal 1420-2004026 on supported AIX platforms



Operating system ● Windows 2000 (SP4), 2003

● AIX V5.2 and 5.3

● Solaris 8, 9

● HP-UX 11i

● Redhat Linux AS 3.0

Client operating system Windows 2000, 2000 Professional, 2003, XP Professional



● IBM WebSphere 5.0.2

● IBM WebSphere 5.1.1


● Microsoft NTLM

● Sun Open Net 5.2 LDAP

● Novell eDirectory 8.7 LDAP

● IBM Directory Server 5.1 LDAP

● Domino LDAP 5.X and 6.0

● Microsoft Active Directory 2000


Java Components Java Development Kit (JDK) 1.4.2 bld 08, installed automatically

Note: On AIX, you must install JDK separately. Hyperion provides the JDK installation files for AIX with Analytic High Availability Services.

Communication Protocol HTTP, TCP/IP


● Shared Services





Operating system ● Windows 2000 (SP4), 2003


● AIX V5.2 and 5.3

● Solaris 8, 9

● HP-UX 11i

● HP-UX 11.23 (Itanium only) for 64-bit Analytic Services

● Redhat Linux AS 3.0 (Intel X86 only)



● IBM WebSphere 5.1.1.7

●


● Microsoft NTLM

● Sun Open Net 5.2 LDAP

● Novell eDirectory 8.7 LDAP

● IBM Director Server 5.1 LDAP

● Domino LDAP 5.X and 6.0



Java components Java Development Kit (JDK) 1.4.2 bld 08, installed automatically on all platforms

Hyperion Products ● Essbase

● Shared Services




Detailed Memory Requirements for Administration ServicesTable 4 lists detailed memory requirements for Administration Services Server.

Table 5 lists detailed memory requirements for Administration Services Console.

Table 4

Component Requirement Discussion

Startup memory ● 38 MB (32-bit Windows)

● 75 MB (64-bit Windows)

● 64 MB (64-bit HP-UX)

Startup memory (32-bit Windows) consists of:

16 MB initial heap + 22 MB for code

Working memory per concurrent Administration Services Server user



● 16 MB (64-bit HP-UX)

For example (32-bit Windows):

When 10 administrators are connected to Administration Services Server:

32 MB * 10 = 320 MB

Outline memory For outlines open in Outline Editor, per member:

● 1 KB (32-bit Windows)

● 6 KB (64-bit Windows)

● 5 KB (64-bit HP-UX)

This memory is used by the outline API cache when outlines are opened in Outline Editor.

-Xmx parameter in adminsvr.lax

Default value = 128 MB

Recommended value = initial heap memory + working memory

This parameter is in the following file:

EASPATH\server\bin\adminsvr.lax

in the “lax.nl.java.option.additional” section.

The -Xmx parameter controls the maximum memory available to Administration Services Server (excluding outline memory), which is limited by the physical memory available on the operating system.

It is recommended that you calculate the value for this parameter using the following formula:

initial heap memory + working memory

For example:

16 MB + (32 MB * n) where n = number of concurrent Administration Services Server users


Table 5

Component Requirement Discussion

Startup memory 33 MB Startup memory consists of:

8 MB initial heap + 25 MB for code

Working memory 64 MB* per connected Essbase Server

* For small-sized Essbase installations, working memory can be reduced to 32 MB per connected Essbase Server. For an example of a small-sized installation, see “Deployment and Configuration Guidelines” on page 40.

For example:

64 MB * 3 (connected Essbase Servers) = 192 MB

Essbase Servers that are listed in Enterprise View but are not connected do not use memory. Administration Services Console caches most of the information retrieved from Essbase Server until the user disconnects from Essbase Server. Examples of information kept in cache include

● application list

● database list

● user list

● filter list

● group list

● open calculation scripts, report scripts, and MaxL scripts

To reduce memory usage, close unnecessary instances of script editors.

Outline memory Outline Editor:

32 MB + (500 B per member)

In Outline Editor, a maximum of 5,000 level-0 members per parent are retrieved into memory:

● Non-level-0 members are retained in memory.

● Memory is not released for members that are modified during the editing session. For example, deleted or renamed members are retained in memory.

For example, if the outline has 1,000 non-level-0 members and 100,000 level-0 members, then memory usage would be:

33,554,432 + (500 * 1,000) + (500 * 5,000) = 36,554,432 B

Outline Viewer:

32 MB + (8 B * number of visible members)

In Outline Viewer, a member is considered “visible” if its parent is expanded.

For example, if the outline has 1,000 non-level-0 members and 100,000 level-0 members, then memory usage would be:

33,554,432 + (8 * 101,000) = 34,362,432 B

-Xmx parameter in admincon.lax

Default value = 256 MB

Recommended value =initial heap memory + working memory + outline memory

This parameter is in the following file:

EASPATH\console\bin\admincon.lax

in the “lax.nl.java.option.additional” section.

The -Xmx parameter controls the maximum memory available to Administration Services Console.

It is recommended that you calculate the value for this parameter using the following formula:

initial heap memory + working memory + outline memory

Release Compatibility 33

Runtime Error Message on AIXIf the following error message is displayed on AIX, you must install an updated C++ runtime environment on that computer:

exec(): 0509-036 Cannot load program ESSBASE because of the following errors: 0509-150 Dependent module /usr/lib/libC.a(shrcore.o) could not be loaded. 0509-152 Member shrcore.o is not found in archive

Updating C++ Runtime Environment for AIX

If you receive a runtime error message on AIX, follow these instructions to download the file required to update the C++ runtime environment.

➤ To download this file:

1 Go to the IBM technical support website:

https://techsupport.services.ibm.com/

2 Search for the PTF number (U489780) or the fileset (xlC.aix50.rte.6.0.0.7).

3 Download the file.

Release CompatibilityUse these topics for release compatibility information:

● “Supported Essbase Server Releases” on page 33

● “64-bit Support” on page 34

● “Supported Analytic High Availability Server Releases” on page 34

● “Supported Analytic Server Smart View Provider Releases” on page 34

● “Administration Services Server and Administration Services Console Compatibility” on page 34

Supported Essbase Server ReleasesAdministration Services supports Essbase Server Release 7.0 or higher.

Although you can use Administration Services to connect to an earlier release of Essbase Server, you cannot use the features introduced in later releases of Essbase Server.

https://techsupport.services.ibm.com/


64-bit Support This section includes support information for the 64-bit releases of Administration Services and Essbase Server.

● 64-bit Administration Services Server supports only 64-bit Essbase Server and 64-bit Administration Services Console.

● 32-bit Administration Services Server supports 32-bit and 64-bit Essbase Server.

● 32-bit Administration Services Server supports with 32-bit Administration Services Console.

● Apache Tomcat 5.0.28 and WebLogic 8.1.4 are the only application servers supported on 64-bit platforms.

Supported Analytic High Availability Server ReleasesAdministration Services Server supports Analytic High Availability Server Release 7.1 or higher.

Supported Analytic Server Smart View Provider ReleasesAdministration Services Server supports Smart View Provider Release 9.0 or higher.

Administration Services Server and Administration Services Console CompatibilityWhen you upgrade Administration Services, you must upgrade Administration Services Server and Administration Services Console.

Port Numbers Used by Hyperion ProductsDuring Hyperion product installation, the default port number for application servers is automatically populated. You can change the default port number during the configuration process. If you do not modify the value during installation, the software is installed with the ports listed below. For information about modifying default ports after installation, see Chapter 5, “Configuring and Setting Up Administration Services”.

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

Port Numbers Used by Hyperion Products 35

Default Port Numbers for Remote Method Invocation (RMI) Servers

Table 6 Port Numbers Used by Hyperion Products

Hyperion Product Listen Port SSL Listen PortShutdown Port for Apache Tomcat

Shared Services 58080 58090 58005

Application Builder J2EE 21080 21090 21005

Application Builder.NET 22080 22082 22081

Essbase Administration Services 10080 10090 10005


11080 11090 11005

Planning 8300 8300 8301

Hyperion Translation Manager 14080 14090 14005

Financial Reporting 8200 8201

Web Analysis 16000 16001

Hyperion Business Modeling 17080 17090 17005

Performance Scorecard 18080 18090 18005

Performance Scorecard Alerting 18081 18091 18006

Enterprise Metrics 8180 8280

8205

8105


13080 13090 13005

Workspace 19000 45001

Table 7 Default Port Numbers for RMI Servers

Hyperion Components RMI Ports

Hyperion Remote Authentication Module 58000

Financial Reporting 1099

Planning 11333

Strategic Finance 1493 and 1495

Hyperion Performance Suite Legacy 1494 - 1498

Hyperion Performance Suite GSM 1800


Deployment Example and RequirementsThis section presents requirements for a representative deployment of Essbase components for up to 150 users (30-40 concurrent users). Your actual configuration may differ from this example depending on your company’s environment.

Keep the following considerations in mind as they may affect hardware requirements:

● Concurrent usage may differ in your environment than in this example. For instance, your organization may have 150 users total, but concurrent usage may typically be around 80 (rather than 30-40), increasing hardware requirements.

● The frequency of queries and the volume of report generation affect hardware requirements.

● Adequate load & performance testing should be integrated into the testing phase of your implementation to validate your production environment hardware sizing and assess overall technical readiness.

l

Hyperion Performance Suite Services 1801-1803

OpenLDAP 58081

Table 8 Essbase Components Installation for up to 150 Users—Hardware Requirements

Hyperion Component Hardware Required

Machine 1:

● Shared Services

Dual Pentium 4, 2 GHz and higher, 4 GB RAM, 32 GB Disk (After OS installation 10 GB available)

Machine 2:

Essbase Server


Machine 3:

● Administration Services Server

● High Availability Server


Table 7 Default Port Numbers for RMI Servers

Hyperion Components RMI Ports

Prerequisites 37

PrerequisitesBefore installing Administration Services, meet these prerequisites:

● Ensure that your Essbase Server release is compatible with this release of Administration Services. See “Release Compatibility” on page 33.

If you are installing Essbase Server simultaneously with Administration Services, you can install them in any order. Administration Services deploys its own set of Essbase shared libraries and sets ARBORPATH internally. There is no dependency on an existing Essbase Server installation.

● On UNIX platforms, if HYPERION_HOME is defined from a previous Hyperion product installation on your machine, ensure that it is set before launching the Administration Services installer. HYPERION_HOME is where common components are installed during some Hyperion product installations. If HYPERION_HOME exists on the computer to which you are installing, setting the environment before launching the installer ensures that the appropriate components are installed to HYPERION_HOME. You must install common components to HYPERION_HOME. See “About Hyperion Home” on page 46.

● If you plan to deploy Administration Services Server on a supported third-party application server, install the application server on the computer hosting the application server.

● If you plan to use a supported third-party relational database, install and create the database.

Note: If you are using IBM DB2 as the relational database, when you create the database, specify UTF-8 as the code set on the “Specify locale for this database” panel.

● Be aware of existing port usage in order to resolve port conflicts during installation.

Table 9 Essbase Components Installation for up to 150 Users—Software Requirements

Hyperion Component Software Required

Machine 1:

● Shared Services

● See the Hyperion Shared Services Installation Guide

Machine 2:

● Essbase Server

● Essbase Integration Services

See “Software Support Matrix for Windows and UNIX” on page 27

Machine 3:

● Administration Services Server

● High Availability Server

See “Software Support Matrix for Windows and UNIX” on page 27


● The installation program prompts for a value for ESSLANG, which points Administration Services Server to the correct Global C code page. For detailed information about the ESSLANG value, see “Selecting the ESSLANG Value” on page 49.

Deployment of Administration Services with Essbase ServerThis section describes how to deploy Administration Services with Essbase Servers. For information about deploying Administration Services with Analytic High Availability Servers, see “Analytic High Availability Server Administration” on page 11.

You can install Administration Services on the same or another computer as Essbase Server, in various configurations. For example, you can install Essbase Server on a computer running UNIX and install Administration Services Server and Administration Services Console on a computer running Windows. You can also install Administration Services Server and Administration Services Console on separate computers and platforms. For a list of supported platforms for each component, see “Software Support Matrix for Windows and UNIX” on page 27.

See the following topics when considering deployment:

● “Deployment Scenarios” on page 38

● “Deployment and Configuration Guidelines” on page 40

Deployment ScenariosEssbase components can be installed in many deployment scenarios. The best configuration depends on your organizational requirements and on which release of Essbase Server you are using. Before selecting a deployment scenario, read the information in “Deployment and Configuration Guidelines” on page 40.

Here are a few possible deployment scenarios:

● Administration Services Server on one computer, Essbase Server on a separate computer, and Administration Services Console on one or more client computers

Figure 1 Multiple Servers and Multiple Clients

Deployment of Administration Services with Essbase Server 39

You can also have multiple Administration Services Server computers and multiple Essbase Server computers, each running on a different platform. Consider this configuration if you have multiple administrators working with large outlines and Essbase Server has limited resources, or if you will administer large outlines during heavy Essbase usage, such as querying or building databases.

● Everything on one computer

Figure 2 Single Computer

Consider this configuration if you have limited resources or if you must perform administration tasks from the computer hosting Essbase Server. See “Deployment and Configuration Guidelines” on page 40 for important requirements for this scenario.

● Essbase Server and Administration Services Server on one computer, and Administration Services Console on one or more client computers

Figure 3 Single Server Computer, Multiple Clients

Each computer can run on a different platform. Consider this configuration if you have limited resources but must administer Essbase Servers from multiple locations.


Deployment and Configuration GuidelinesThis topic discusses guidelines to consider when choosing a deployment scenario and configuring the Administration Services Server computer.

Administration Services Server and Administration Services Console should be installed on the same computer only if the following requirements are met:

● You want to run Administration Services Server on a Windows platform. (Administration Services Console is supported only on Windows platforms).

● Only one administrator uses Administration Services to manage small-sized Essbase Server installations. (As an example, a small-sized Essbase Server installation includes fewer than 10 applications, each of which contains fewer than 1000 users, fewer than 1000 filters per database, and no scripts larger than 1 MB).

● The computer has the required amount of memory for both components. For detailed memory requirements, see “Hardware Requirements” on page 22.

● Outline editing is carefully monitored. Outline editing consumes memory on Administration Services Server and Administration Services Console. Consider how many outlines are being edited simultaneously and how large the outlines are. For detailed outline memory requirements for Administration Services Server, see Table 4. For detailed outline memory requirements for Administration Services Console, see Table 5.

In all other cases, Administration Services Server and Administration Services Console should be installed on separate computers. The configuration of the Administration Services Server computer depends upon the potential workload of Administration Services Server. Use the following guidelines when configuring the Administration Services Server computer:

● Administration Services Server is one process and can address only 2 GB of memory; therefore, it runs out of memory if users are simultaneously editing outlines. Consider deploying multiple instances of Administration Services Server if users will edit multiple outlines simultaneously.

● If more than 10 users will connect to Administration Services Server simultaneously, consider (1) using a computer that employs multiple CPUs for Administration Services Server or (2) deploying multiple instances of Administration Services Server on separate computers to improve performance.

Note: For detailed information on memory requirements for Administration Services Server and Administration Services Console, see “Hardware Requirements” on page 22.

UpgradingIf you are upgrading from a previous release of Administration Services, see Chapter 7, “Upgrading Administration Services.”

Installing Administration Services 41

C h a p t e r

4Installing Administration

Services

This chapter provides instructions for installing Administration Services on all platforms and describes what happens during the installation process.

Before beginning installation, read and follow the instructions outlined in Chapter 3, “Planning the Installation.”

In This Chapter Launching Installers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Installing Administration Services Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

What Happens During Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

About Hyperion Home . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

42 Installing Administration Services

Launching InstallersYou can install Administration Services from files downloaded from Oracle® E-Delivery site or from a CD.

➤ To launch the Administration Services installer from the self-extracting download file from Oracle® E-Delivery site:

1 Log on to Oracle® E-Delivery site.

2 Navigate to the Administration Services product page for your platform and language.

3 Download and execute the installer.

➤ To launch the Administration Services installer from the CD:

1 Navigate to the aas directory on the CD.

2 Navigate to the directory for your platform.

3 Run one of the following:

● For Windows, run setup.exe.

● For UNIX, run setup.bin.

On UNIX platforms, you can launch the installer from the console or in XWindows.

➤ To launch the installer in XWindows, type

./setup.bin

➤ To launch the installer in the console, type./setup.bin -console

Installing Administration Services SoftwareAdministration Services provides a cross-platform installer for Windows and UNIX platforms.

If you want to make the installer available to users who cannot access Oracle® E-Delivery site or the CD, download the program to a network.

Note: You can leave Essbase Server running while installing Administration Services.

➤ To install Administration Services on Windows or UNIX:

1 Verify that all prerequisites and system requirements are met.

See Chapter 3, “Planning the Installation.”

2 Download and launch the applicable installer program for Administration Services.

See “Launching Installers” on page 42 .

What Happens During Installation 43

3 Follow the installation prompts, keeping in mind the following:

● You cannot install Administration Services to a directory containing a space in the directory name (for example, c:\Program Files). The default directory is c:\hyperion\AdminServices.

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

● Hyperion common components are installed to a location called “Hyperion Home” (HYPERION_HOME\common). See “About Hyperion Home” on page 46.

● A typical installation installs Administration Services Server, Administration Services Console components, and the documentation. A custom installation enables you to install Administration Services Server and Administration Services Console components separately.

If you do not want to install Administration Services Console on client computers, you can launch the console from a Web browser on a client computer. See “Starting Administration Services Console using Web Launch” on page 66.

● The installer prompts you to select a value for the ESSLANG variable. The default value for the ESSLANG variable is English (Latin1). See “Selecting the ESSLANG Value” on page 49.

● After installation is complete, install additional Hyperion products, if applicable.

● After installation is complete, see “Completing Advanced Installation Tasks” on page 62.

4 When you finish installation, run the Configuration Utility to configure Administration Services for use.

See Chapter 5, “Configuring and Setting Up Administration Services.”

What Happens During InstallationDuring installation, the Administration Services installer performs the following operations:

● Creates directories and subdirectories under the location that you specify in the installer

In the documentation, the directory where you install Administration Services is referred to as the EASPATH directory. For a listing of directories created during installation, see “Files Installed in the EASPATH Directory” on page 44.

● Installs Hyperion common components to the HYPERION_HOME\common directory

For information about HYPERION_HOME, see “About Hyperion Home” on page 46.

● Installs and configures Apache Tomcat application server during the Administration Services Server installation

Apache Tomcat is installed to the HYPERION_HOME\common directory. For information about default ports for Apache Tomcat, see “Specifying Ports for Apache Tomcat” on page 49. For information about deploying to other supported third-party application servers instead of Apache Tomcat, see Chapter 5, “Configuring and Setting Up Administration Services.”


● Installs and starts the MySQL database during the Administration Services Server installation

MySQL is installed to the HYPERION_HOME\common directory. For information about deploying to other supported third-party relational databases instead of MySQL, see Chapter 5, “Configuring and Setting Up Administration Services.”

On Windows platforms, MySQL is installed and started automatically as a Windows Service (Hyperion-MySQL-4.0.12). On UNIX platforms, MySQL is started in the background. If MySQL stops and you want to use Log Analyzer or Business Rules, you must restart MySQL. See “Stopping and Restarting the MySQL Database” on page 70.

● Installs documentation files to the Administration Services Server computer

Documentation is installed in

EASPATH\deployments\Tomcat\5.0.28\webapps

If you deploy Administration Services Server on a supported third-party application server, the documentation is deployed on that application server.

For information about documentation, see “Documentation Installed” on page 45.

● On Windows, adds shortcuts to the Start menu

● Installs an uninstaller program in EASPATH\uninstall

For uninstallation instructions, see Chapter 6, “Uninstalling Administration Services.”

● Installs Business Rules software and documentation

Files Installed in the EASPATH Directory

The directory where you install Administration Services is referred to as the EASPATH directory. The default for EASPATH is c:\hyperion on Windows platforms and /home/hyperion on UNIX platforms.

Table 10 describes the directories that the installer program creates for a typical (server and console software) installation.

Table 10

Directory Contents

EASPATH Documentation launch files and other miscellaneous files

\AppServer \InstallableApps—Files required by the Configuration Utility for auto-deployment

\InstalledApps—Files/directories created by the Configuration Utility during auto-deployment

\console Administration Services Console executable files, Java class files, Business Rules plug-in files, and temporary files created by the console installation

\deployments Default application server files, documentation files, and files to support administration of Analytic High Availability Servers

What Happens During Installation 45

Documentation InstalledDocumentation files are installed to Administration Services Server so that all console users can access documentation without installing it locally. If you deployed Administration Services Server on a supported third-party application server, the documentation is deployed to that server. For information about supported third-party application servers, see Chapter 5, “Configuring and Setting Up Administration Services.”

All Administration Services documentation can be launched from the Administration Services Information Map. All Business Rules documentation can be launched from the Business Rules Information Map.

➤ You can launch the Information Maps in the following ways:

● Open Administration Services Console, and from Help, select Information Map.

● From the EASPATH directory, double-click doc_launcher.htm.

● From the EASPATH\en_US directory, double-click hbr_doc_launcher.htm.

● On Windows platforms, select:

❍ Start > Programs > Hyperion System 9 BI+ > Analytic Administration Services > Administration Services Information Map

or

❍ Start > Programs > Hyperion System 9 BI+ > Analytic Administration Services > Business Rules Information Map

Browser RecommendationsFor best results, Hyperion recommends viewing Essbase Administration Services Online Help in Internet Explorer version 6.0 or later or in Netscape Navigator version 7.0 or later. Certain features of the help system, however, are not supported by Netscape Navigator.

On UNIX platforms, you must launch the HTML Information Map to access documentation. If you use Netscape Navigator to view the Information Map, you may need to open Netscape before you attempt to launch the help system from the Information Map.

\migrationutility One of the utilities needed to change the Hyperion Home location

See “Changing the Hyperion Home Location” on page 47.

\server Administration Services Server executable files, default relational database files, Java class files, Business Rules server files, and server locale files

\uninstall Files for uninstalling Administration Services

Table 10

Directory Contents


About Hyperion HomeWhen multiple Hyperion products are installed on the same computer, common internal and third-party components used by the products are installed to a central location, called Hyperion Home. On Windows platforms, the Hyperion Home location is defined in the system environment variable called HYPERION_HOME. On UNIX, the Hyperion Home value is stored in .hyperion.<hostname> in the /home directory.

Hyperion Home LocationThe Administration Services installer prompts you to define the location for Hyperion Home. The default location is C:\Hyperion for Windows and $HOME/Hyperion for UNIX. If the location has been previously defined for another Hyperion product, the installation uses that location and the Hyperion Home location cannot be changed through the installer. If this is the first Hyperion installation on the computer, and you have not already specified the location for Hyperion Home, you can specify the location during installation.

Files Installed in the HYPERION_HOME DirectoryTable 11 lists the files that are installed in the HYPERION_HOME\common directory by a default installation of Administration Services. Some common components are optional and may not be installed.

Table 11 Directories Created in the HYPERION_HOME\common Directory

Directory Contains files for

appServers Apache Tomcat Server (installed by default)

config Configuration Utility

CSS Hyperion external authentication

DBMS MySQL database management system (DBMS) (installed by default)

HyperionLookAndFeel Installer user interface

JCE Java Cryptography Extension (JCE), for encryption, key generation and key agreement, and Message Authentication Code (MAC)

JDBC Java Database Connectivity (JDBC)

JDK Java Development Kit (JDK)

JRE Java Runtime Environment (JRE)

loggers External authentication logging

utilities One of the utilities needed to change the location of Hyperion Home

See “Changing the Hyperion Home Location” on page 47.

XML Common XML components

About Hyperion Home 47

Caution! Do not manually move, delete, or overwrite the common components.

Changing the Hyperion Home LocationAfter Hyperion Home has been defined through any product installation, you must run a migration utility to change the Hyperion Home location. The first utility moves the files installed in Hyperion Home to the new location, and the second utility fixes all internal references to the old Hyperion Home location. Both utilities are provided with the Administration Services installation.

➤ To change the Hyperion Home location:

1 Launch the migration utility:

● On Windows, choose a method:

❍ Double-click the run.exe file from:

%HYPERION_HOME%\common\utilities\HyperionHomeTool\1.0.1\bin

❍ From a Windows console, change to this directory:

%HYPERION_HOME%\common\utilities\HyperionHomeTool\1.0.1\bin

Then type:

run.exe -console

● On UNIX, choose a method:

❍ In XWindows, change to this directory:

$HYPERION_HOME/common/utilities/HyperionHomeTool/1.0.1/bin

Then type:

migrationtool.sh

❍ In a UNIX console, change to this directory:

$HYPERION_HOME/common/utilities/HyperionHomeTool/1.0.1/bin

Then type:

migrationtool.sh -console

The migration utility is launched.

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

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

For Windows, the utility updates the HYPERION_HOME environment variable. For UNIX, the utility updates the .hyperion_<HOSTNAME> file in the home directory containing the environment variable. Login initialization files, such as .profile and .login are not updated on UNIX systems.


3 Launch the second utility by executing the following file from the Administration Services installation location:

Windows:

EASPATH\migrationutility\bin\MigrationUtility.exe

UNIX:

EASPATH/migrationutility/bin/MigrationUtility.bin -console

The migration utility is launched.

4 Step through the screens, and when prompted, enter both the new and old Hyperion Home locations, or click Browse to navigate to the desired locations.

5 When prompted, confirm or correct the current locations of installed Hyperion products.

The migration utility first creates a backup of all files that contain references to Hyperion Home. Then the utility opens the files, searches for the old Hyperion Home location, replaces all references with the new Hyperion Home location, and saves the files. The last screen of the utility lists the files that were changed.

Specifying Ports for Apache Tomcat 49

Selecting the ESSLANG ValueThe Administration Services installer prompts you to select a value for the ESSLANG variable. ESSLANG points Administration Services Server to the correct Global C code page (installed in the EASPATH\server\locale directory). The default value for ESSLANG is English (Latin1).

The Administration Services installer provides a list of supported locales, displayed in abbreviated format: Language (code page), for example, English (Latin1). Once set, the ESSLANG environment variable value contains the full value for the locale (for example, English_UnitedStates.Latin1@Binary).

ESSLANG must match on the Essbase Server computer and on the Administration Services Server computer. The ESSLANG value for a computer must agree with the encoding of the operating system of that computer.

Note: For important information about ESSLANG and Unicode applications on Essbase Server, see the Hyperion Essbase – System 9 Installation Guide.

The ESSLANG value selected during installation is stored in EASPATH/server/olapadmin.properties.

On Windows, if ESSLANG is set on the computer to which you are installing Administration Services Server, the current value is selected by default in the installer. On UNIX, the installer always defaults to English (Latin1), even if ESSLANG is set to another value. When the installer prompts you, you must select the value of the existing ESSLANG setting; otherwise, your applications may fail to start.

For the full list of supported ESSLANG values, see Hyperion Essbase – System 9 Database Administrator’s Guide.

ESSLANG does not need to be set on the computer where Administration Services Console is installed, unless it shares a computer with Administration Services Server. If you are installing only the console, the installer does not prompt you to set ESSLANG.

Specifying Ports for Apache TomcatThe Administration Services installer automatically installs and deploys the Apache Tomcat application server using default port numbers. If you want to change the default port numbers, you can run the Configuration Utility. For a list of default ports, see “Port Numbers Used by Hyperion Products” on page 34.


Setting Up and Running Silent InstallationsTo install Administration Services on multiple computers and use identical installation options for each installation, you can record installation settings and run a “silent” installation from the command line. Silent installations automate the installation process for multiple computers.

To record installation settings, create a “response” file and run the regular installation to record your settings in the response file. When you run the silent installation from the command line, the response file is used to select the installation options of the regular (nonsilent) installation.

➤ To record installation settings and run a silent installation:

1 Navigate to the directory that contains the product installer.

2 From a command line prompt, run the following command:

The <responsefilename> can include an absolute path and/or file name for the response file.

The regular (nonsilent) product installer is launched.

3 As you step through the installer, specify the settings to be recorded.

The installation options are recorded in the response file. You can modify this file if you want to change installation options.

You are now ready to run the installation in silent mode.

4 From the command line, enter the following:

The installation runs in the background.

Windows setup.exe —options—record <responsefilename>

UNIX (AIX, Solaris, Linux, HP-UX)

setup.bin —options—record <responsefilename>

Windows setup.exe —options <responsefilename> —silent

UNIX (AIX, Solaris, Linux, HP-UX)

setup.bin —options <responsefilename> —silent

Configuring and Setting Up Administration Services 51

C h a p t e r

5Configuring and Setting Up

Administration Services

This chapter describes how to configure Hyperion products using the Hyperion Configuration Utility. It provides instructions for activating products, registering with Hyperion Shared Services, configuring a relational database, deploying products on an application server, and performing product-specific configuration.

In This Chapter Hyperion Configuration Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Task Sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Configuring Product Upgrades . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Launching the Configuration Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Registering Products with Shared Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Configuring Relational Storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Deploying Products to Application Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Deregistering Products with Shared Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Reconfiguration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Configuration Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Verifying Startup Dependencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Starting Shared Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Completing Advanced Installation Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

52 Configuring and Setting Up Administration Services

Hyperion Configuration UtilityThe Configuration Utility is a common tool used to configure installed Hyperion products. This utility is installed with the first product installed on a machine, and you can use it to configure all products that are installed on that machine. You must run the Configuration Utility on each machine to which a product is installed.

The Configuration Utility provides the appropriate set of configuration tasks for the products installed on the machine:

● Shared Services Registration—Required for all products. See “Registering Products with Shared Services” on page 54.

● Relational Storage Configuration—Required for products that use a database to store and retrieve data. See “Configuring Relational Storage” on page 55.

● Application Server Deployment—Required for products that deploy on an application server. See “Deploying Products to Application Servers” on page 57.

● Shared Services Deregistration—For registered products, required to deregister from Shared Services before uninstalling the product. See “Deregistering Products with Shared Services” on page 59.

Product-specific configuration tasks may also be provided.

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

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

PrerequisitesComplete these tasks before using the Configuration Utility:

Task Documentation

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

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

“Starting Shared Services” on page 60

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

Prepare a database to use for relational storage.

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

Database documentation

Install Hyperion products.

Note: Do not start the product you are configuring.

Product installation guide

Launching the Configuration Utility 53

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

● Product activation

● Shared Services registration

● Database configuration

● Application server deployment

Some products may require a different configuration order.

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

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

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

Note: The Configuration Utility is backward compatible with the previous release (9.0.0 or 4.0.0) and can be used to configure products for that release.

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

➤ To launch the Configuration Utility:

1 Choose a method:

● On the last page of a product installer, select the option to launch the Configuration Utility.

● On Windows, choose a method:

❍ From Start, select Programs > Hyperion System 9 Foundation > Configuration Utility.

❍ Double-click the configtool.bat file from:


\HYPERION_HOME\common\config

❍ From a Windows console, change to this directory:

\HYPERION_HOME\common\config

Then type:

startconfigtool.bat -console

● On UNIX, choose a method:

❍ In XWindows, change to this directory:

$HYPERION_HOME/common/config

Then type:

configtool.sh

❍ In a UNIX console, change to this directory:

$HYPERION_HOME/common/config

Then type:

configtool.sh -console

Note: If you are running the Configuration Utility in console mode, follow the command-line prompts.

2 On the welcome page, click Next.

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

A list of configuration tasks is displayed.

4 Follow the instructions for configuration tasks, as appropriate for the selected products:

● “Registering Products with Shared Services” on page 54

● “Configuring Relational Storage” on page 55

● “Deploying Products to Application Servers” on page 57

● “Deregistering Products with Shared Services” on page 59

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

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

➤ To register products with Shared Services:

1 Launch the Configuration Utility.

See “Launching the Configuration Utility” on page 53.

Configuring Relational Storage 55


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

4 Specify Shared Services server information:

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

Configuring Relational StorageWhen you configure products to use a database, the Configuration Utility checks for connectivity to the database and ensures that the database is a supported database type. If an existing database is detected, you may be prompted to re-use the database or create a new one.

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

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

➤ To configure a database:




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

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

The relational storage configuration details page is displayed.

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

5 Specify database information:

Table 12 Shared Services Server Fields

Server Enter the computer name (host name) where Shared Services server is installed. Do not specify an IP address for the server, especially in DHCP environments.

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

User Enter the username of the Shared Services Administrator.

Password Enter the password for the Shared Services Administrator.

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


6 Click Next to view configuration status.


Changing the Database PasswordFollow this procedure to change the password for the database owner.

➤ To change the password for the database owner (as specified during configuration):

1 Change the user’s password externally in the database.

Note: For MySQL, you do not have to change the password in the database; you can change it using only the Configuration Utility.

2 Shut down Administration Services.

See “Shutting Down Administration Services” on page 68.

Note: If you want to change the password for multiple products, shut down each product. You do not need to shut down Shared Services.




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

Table 13 Database Configuration Fields

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

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

● DB2—50000

● Oracle—1521

● SQL Server—1433

● MySQL—3306

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

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

Username Enter the name of the database owner.

Password Enter the password of the database owner.

Deploying Products to Application Servers 57

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

The relational storage configuration details page is displayed.

7 For Password, enter the new password for the user.

Note: If you also change the username to a different database owner, data is not migrated with the new user.

8 Click Next.

9 At the prompt to create a new repository or to reuse the existing repository, choose to reuse the existing repository.

10 Select Next and then Finish.

The Configuration Utility updates the appropriate configuration files with the new password.

11 Start Administration Services.

See“Starting Administration Services” on page 62 .

Deploying Products to Application ServersThe Configuration Utility enables you to deploy multiple Hyperion products to the same application server. The application server must be installed on the same machine as the products you are deploying.

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

Caution! On UNIX platforms, if you are using IBM WebSphere application server, use the same account to install, deploy, and execute Hyperion products that you use to install WebSphere. Using the same account ensures that products are deployed successfully.

➤ To deploy products to an application server:




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

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

A page specific to the selected application server is displayed.

5 Specify application server information:


Table 14 Application Server Configuration Fields

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

For example:

● For WebSphere Base—

c:\WebSphere\AppServer on Windows

or

/opt/WebSphere/AppServer on UNIX

● For WebSphere Express—

c:\IBM\WebSphere\Express51\AppServer on Windows

or

/opt/IBM/WebSphere/Express51/AppServer on UNIX

● For WebLogic—

c:\bea\weblogic81 on Windows

or

/opt/bea/weblogic81 on UNIX

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

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

Username and Password (WebLogic only)

Enter your WebLogic username and password.

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

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

Hyperion <Product> <AppServer><Version#>

For example:

Hyperion SharedServices9 WAS51

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

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

ServerName Enter the name of the server where you can access the deployed product. You can enter only English alphanumeric characters and the dash character (-).

Deregistering Products with Shared Services 59

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

6 Click Next to view configuration status.


Deregistering Products with Shared ServicesIf you need to uninstall a Hyperion product after installation and configuration, and if the product is registered with Shared Services, first deregister the product before uninstalling it.

➤ To deregister products with Shared Services:




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

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

4 In the Password text box, enter the password for the specified Shared Services user.


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

Each application port number must be unique. For a list of default port numbers, see “Port Numbers Used by Hyperion Products” on page 34 .

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

Table 14 Application Server Configuration Fields


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

Product activation is not required when you reconfigure.

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

● Windows: %HYPERION_HOME%\common\config\logs

● UNIX: $HYPERION_HOME/common/config/logs

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

Verifying Startup DependenciesBefore starting Administration Services , you must verify that these dependent software components are running:

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

➤ To start Shared Services server:

1 Choose a method:

● On Windows, select Start > Programs > Hyperion System 9 Foundation > Start Shared Services.

Component How to Verify Successful Startup How to Start

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

See “Starting Shared Services” on page 60.

Starting Shared Services 61

The menu item indicates which application server the Shared Services server is deployed to.

● Execute the startup script:

Verifying Successful Startup of Shared Services

➤ To verify successful startup and configuration of Shared Services:

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

● Database Configuration Test Passed

● Security System Initialized Successfully

● Shared Services Initialized Successfully

On UNIX, when Shared Services is deployed to the Tomcat application server, these confirmation messages are logged to the following file: <HSS_HOME>/AppServer/InstalledApps/<AppServName>/<version>/ SharedServices9/logs/Catalina.out

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

Application Server Path to Script

IBM WebSphere Windows:

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

UNIX:

<HSS_HOME>/AppServer/InstalledApps/<AppServName>/<version>/SharedServices9/bin/startSharedServices9.sh

BEA WebLogic Windows:

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

UNIX:

<HSS_HOME>/AppServer/InstalledApps/<AppServName>/<version>/SharedServices9/startSharedServices.sh

Oracle Windows:

<OracleInstallDir>\bin\emctl start iasconsole<OracleInstallDir>\opmn\bin\opmnctl startall

UNIX:

<OracleInstallDir>/bin/emctl start iasconsole<OracleInstallDir>/opmn/bin/opmnctl startall

Apache Tomcat Windows:

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

UNIX:

<HSS_HOME>/AppServer/InstalledApps/<AppServName>/<version>/SharedServices9/bin/startSharedServices9.sh

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


● Windows:

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

● UNIX:

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

On UNIX and Windows, when Shared Services is deployed to WebLogic, these confirmation messages are also logged to the following file, unless the log level is set to WARN:

● Windows:

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

● UNIX:

<HSS_HOME>/AppServer/InstalledApps/WebLogic/8.1/SharedServices9/logs/SharedServices_Metadata.log

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

a. Open a browser and enter this URL:

http://SharedServicesServerName:port#/interop

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

http://jdoe:58080/interop/

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

b. On Windows, select Start > Programs > Hyperion System 9 Foundation > User Management Console.

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

Completing Advanced Installation TasksThis section describes the tasks that can be performed after installation is complete.

Starting Administration ServicesAfter you install Administration Services, start Administration Services Server and then Administration Services Console.

Completing Advanced Installation Tasks 63

Note: For information about how connections to Essbase Servers are established and how ports are established, see Essbase Administration Services Online Help.

Starting Administration Services ServerWhen you start Administration Services Server, ARBORPATH is set internally to the following location:

EASPATH\server

This internal setting overrides (but does not replace) the value for the ARBORPATH system environment variable, if it is set on the same computer.

Note: EASPATH is the directory where you install Administration Services.

➤ To start Administration Services Server on Windows, use one of the following methods, according to the application server you deployed to:

Note: If you changed the domain name, script names and menu items may differ from this table.

Table 15 Administration Services Server Launch Methods for Windows

Application Server Launch File Start Menu

BEA WebLogic 8.1.4 EASPATH\server\bin\ startEASWebLogic81eas.bat

Start > Programs > Hyperion System 9 BI+ > Analytic Administration Services > Start Administration Services Server (WebLogic81 eas)

IBM WebSphere 5.1.1.7 EASPATH\server\bin\ startEASWebSphere51eas.bat

Start > Programs > Hyperion System 9 BI+ > Analytic Administration Services > Start Administration Services Server (WebSphere51 eas)

IBM WebSphere 5.0.2 EASPATH\server\bin\ startEASWebSphere50eas.bat

Start > Programs > Hyperion System 9 BI+ > Analytic Administration Services > Start Administration Services Server (WebSphere50 eas)

Apache Tomcat 5.0.28 EASPATH\server\bin\ startEASTomcat5eas.bat

Start > Programs > Hyperion System 9 BI+ > Analytic Administration Services > Start Administration Services Server (Tomcat eas)

Apache Tomcat 5.0.28 (default version provided during installation)

EASPATH\server\bin\ startEAS.exe

Start > Programs > Hyperion System 9 BI+ > Analytic Administration Services > Start Administration Services Server


➤ To start Administration Services Server on UNIX, launch one of the following files in the foreground or the background, according to the application server you deployed to:


Starting the Administration Services Server Windows Service

Note: If Administration Services Server is installed and running as a Windows service, you cannot also start it manually because the default port number is being used by the Windows service. If you try to start Administration Services Server manually, an error message appears indicating that the port is in use.

If Administration Services Server is deployed as a Windows service, start the service from Windows Control Panel. The service name depends on the application server you deployed to:

Table 16 Administration Services Server Launch Methods for UNIX

Application Server Launch in Foreground Launch in Background

BEA WebLogic 8.1.4 From the EASPATH/server/bin directory, type

./startEASWebLogic81eas.sh

From the EASPATH/server/bin directory, type

./startEASWebLogic81eas.sh &

or

nohup ./startEASWebLogic81eas.sh &

IBM WebSphere 5.1.1.7 From the EASPATH/server/bin directory, type

./startEASWebSphere51eas.sh


./startEASWebSphere51eas.sh &

or

nohup ./startEASWebSphere51eas.sh &

IBM WebSphere 5.0.2 From the EASPATH/server/bin directory, type

./startEASWebSphere50eas.sh


./startEASWebSphere50eas.sh &

or

nohup ./startEASWebSphere50eas.sh &

Apache Tomcat 5.0.28 From the EASPATH/server/bin directory, type

./startEASTomcat5eas.sh


./startEASTomcat5eas.sh &

or

nohup ./startEASTomcat5eas.sh &



./startEAS


./startEAS &

or

nohup ./startEAS &


Note: If you changed the domain name, the service name may differ from this table.

For more information about managing the Windows service, see “Running Administration Services Server as a Windows Service” on page 71.

Starting Administration Services ConsoleThis section describes two methods of starting Administration Services Console:

● How to start Administration Services Console when it is installed locally on a client computer. See “Starting Administration Services Console Locally” on page 66.

● How to launch Administration Services Console from a Web browser on a client computer when the console component is not installed on the client. See “Starting Administration Services Console using Web Launch” on page 66.

Table 17 Windows Service Names for Administration Services Server

Application Server Windows Service Name in Control Panel

BEA WebLogic 8.1.4 beasvc easWL8.1_server1

IBM WebSphere 5.1.1.7 IBM WebSphere Application Server V5 - easWAS5.1

IBM WebSphere 5.0.2 IBM WebSphere Application Server V5 - easWAS5.0

Apache Tomcat 5.0.28 Hyperion eas Tomcat5


Starting Administration Services Console Locally

➤ To start Administration Services Console:

1 Launch EASPATH\console\bin\admincon.exe.

Note: If you chose to add shortcuts to the Start menu during installation, you can start Administration Services Console from the Start menu (Start > Programs > Hyperion System 9 BI+ > Analytic Administration Services > Start Administration Services Console).

When Administration Services Console starts properly, the Administration Services Login dialog box is displayed.

2 In the Administration Services Login dialog box, perform the following steps:

a. Enter the Administration Services Server name.

This is the name of the computer on which you installed Administration Services Server.

Note: If the value for the Administration Services Server port was changed from the default value, you must specify the port value after the Administration Server name (for example, AdminServerName:9002). See “Setting Up and Running Silent Installations” on page 50.

b. Enter your Administration Services Server username.

If you do not have this information, contact the Administration Services administrator. If you are connecting for the first time after installation, use the default username, admin.

c. Enter your Administration Services Server password.

If you do not have this information, contact the Administration Services administrator. If you are connecting for the first time after installation, use the default password, password.

The console is displayed with Enterprise View in the left frame and a blank workspace in the right frame.

Starting Administration Services Console using Web Launch

If you choose not to install the Administration Services Console component on a client computer, you can launch the console from a Web browser on the client computer. The first time you launch the console from a browser, all .jar files for the Java console application are downloaded from Administration Services Server to the client computer and are cached until you manually clear them. After this initial download, launch the console from a Web browser, and the application runs locally. Disk space and memory requirements on the client computer are identical to a local console installation. For information about requirements, see “Hardware Requirements” on page 22. For instructions about where the downloaded files are cached, and for instructions on how to clear the files from the client computer, see “Clearing Console Application Files from Client Computers” on page 68.


The Administration Services Server installation includes all files needed to launch the console from a Web browser on the client computer. If Administration Services Server is re-installed or upgraded, the updated files are automatically downloaded to the client computer the next time the console is launched from a browser.

Because Administration Services uses Java Web Start technology for Web launch of the console, Java Development Kit (JDK) 1.4.2 or higher must be installed on the client computer. You can obtain a free JDK download from the Sun Microsystems Web site (http://www.sun.com).

➤ To launch Administration Services Console from a Web browser:

1 Start Administration Services Server.

2 Open a browser window, for example, Internet Explorer.

3 In the address bar, type the following URL:

http://AdministrationServerName:port#/eas/easconsole.html

where AdministrationServerName is the name of the computer on which Administration Services Server is installed and port# is the Administration Services Server port number. For example:

http://jdoe:10080/easconsole/console.html

Note: The default port number is 10080; if Administration Services Server is installed to a non-default port, specify the non-default port value.

The Web Launcher window is displayed.

4 Select your country, and click Launch.

If this is the first time launching Administration Services Console from a browser, the console application files are downloaded to the client computer.

5 Press the Enter key.

If this is the first time launching Administration Services Console from a browser, a security warning is displayed.

When Administration Services Console is first launched from a browser, it is not yet running as a regular Java application; therefore, the application cannot access resources on the local computer. To grant access to local computer resources, a certificate is created and all .jar files are signed with the certificate.

6 If the security warning dialog box is displayed, click the Start button.

Note: Depending on which JDK version you have installed, the security warning message may differ. Respond in the affirmative to this security warning.

When Administration Services Console starts properly, the Administration Services Login dialog box is displayed.


7 In the Analytic Administration Services Login dialog box, perform the following steps:

Note: The Administration Services Server field is populated with the Administration Server computer name and port value, as specified in step 3.

a. Enter your Administration Services Server username.

If you do not have this information, contact the Administration Services administrator. If you are connecting for the first time after installation, use the default username, admin.

b. Enter your Administration Services Server password.

If you do not have this information, contact the Administration Services administrator. If you are connecting for the first time after installation, use the default password, password.

The console is displayed with Enterprise View in the left frame and a blank workspace in the right frame.

Clearing Console Application Files from Client Computers

You can use the Java Plugin Control Panel to clear the console application files that are downloaded to the client machine when you launch the console from a Web browser. This is the equivalent of running an uninstaller program.

➤ To remove the downloaded console application files from a client machine:

1 Open the Windows Control Panel (select Start > Settings > Control Panel).

2 Open the Java Plugin Control Panel.

3 Select the Cache tab.

4 Click the Clear button and respond to the confirmation prompt.

5 Close the Java Plugin Control Panel.

Shutting Down Administration ServicesThe process for shutting down Administration Services is described in the following topics:

● “Closing Administration Services Console” on page 69

● “Stopping Administration Services Server” on page 69


Closing Administration Services Console

➤ To close Administration Services Console:

1 From the console menu bar, select File > Exit.

2 You are prompted to save information, such as settings and modifications.

In instances where your session has timed out but you still have open files that require action (for example, a report script), you are prompted to log back on to Administration Services Console before closing. You can change the timeout setting for Administration Services sessions. For information on setting the timeout, see Essbase Administration Services Online Help.

Stopping Administration Services Server

Note: EASPATH is the directory where you install Administration Services.

➤ To stop Administration Services Server on Windows, use one of the following methods, according to the application server you deployed to:


Table 18 Administration Services Server Stop Methods for Windows

Application Server Stop Script Start Menu

BEA WebLogic 8.1.4 There is no stop script for WebLogic. There is no stop menu item for WebLogic.

IBM WebSphere 5.1.1.7 EASPATH\server\bin\ stopEASWebSphere51eas.bat

Start > Programs > Hyperion System 9 BI+ > Analytic Administration Services > Stop Administration Services Server (WebSphere51 eas)

IBM WebSphere 5.0.2 EASPATH\server\bin\ stopEASWebSphere50eas.bat

Start > Programs > Hyperion System 9 BI+ > Analytic Administration Services > Stop Administration Services Server (WebSphere50 eas)

Apache Tomcat 5.0.28 EASPATH\server\bin\ stopEASTomcat5eas.bat

Start > Programs > Hyperion System 9 BI+ > Analytic Administration Services > Stop Administration Services Server (Tomcat eas)


EASPATH\server\bin\ stopadminsvr.exe

Start > Programs > Hyperion System 9 BI+ > Analytic Administration Services > Stop Administration Services Server


➤ To stop Administration Services Server on UNIX, launch one of the following files, according to the application server you deployed to:


Note: If you are using the middle-tier MySQL database, the database is not stopped when Administration Services Server is stopped. See “Stopping and Restarting the MySQL Database” on page 70.

Stopping and Restarting the MySQL DatabaseIf you are using the MySQL database, it is started during the installation. On Windows platforms, the database runs as a Windows service named Hyperion-MySQL-4.0.12. On UNIX platforms, the database runs in the background. The database is not stopped when you shut down Administration Services Server.

➤ To stop the Hyperion-MySQL-4.0.12 service on Windows platforms, use the Windows Control Panel or enter the following string at a command prompt:

net stop “Hyperion-MySQL-4.0.12”

➤ To stop MySQL on UNIX platforms, run the following script:

HYPERION_HOME/common/DBMS/MySQL/4.0.12/bin/stop_mysql.sh

or, for 64-bit HP-UX:

HYPERION_HOME/common/DBMS/MySQL/4.0.23/bin/stop_mysql.sh

If MySQL is stopped, you must restart MySQL manually.

➤ To restart MySQL on Windows platforms, use Windows Control Panel to restart the Hyperion-MySQL-4.0.12 service or enter the following string at a command prompt:

net start “Hyperion-MySQL-4.0.12”

Table 19 Administration Services Server Stop Scripts for UNIX

Application Server Stop Script

BEA WebLogic 8.1.4 There is no stop script for WebLogic.

IBM WebSphere 5.1.1.7 From the EASPATH/server/bin directory, type

./stopEASWebSphere51eas.sh

IBM WebSphere 5.0.2 From the EASPATH/server/bin directory, type

./stopEASWebSphere50eas.sh

Apache Tomcat 5.0.28 From the EASPATH/server/bin directory, type

./stopEASTomcat5eas.sh



./stopEAS


➤ To restart MySQL on UNIX platforms, run the following script:

HYPERION_HOME/common/DBMS/MySQL/4.0.12/bin/start_mysql.sh

or, for 64-bit HP-UX:

HYPERION_HOME/common/DBMS/MySQL/4.0.23/bin/start_mysql.sh

Note: To start MySQL, you must be logged on to the UNIX server on the account that was used to install Administration Services Server.

Running Administration Services Server as a Windows ServiceWhen you use the Configuration Utility to automatically deploy to a supported third-party application server, you can specify that the server be deployed as a Windows service. Running Administration Services Server as a Windows service enables you to start and stop it from the Windows Control Panel. Running Administration Services Server as an automatic service starts Administration Services Server as a service when you start Windows.

For information about how the Windows service names appear in the Windows Control Panel, see “Starting the Administration Services Server Windows Service” on page 64.

This section contains the following topics:

● “Verifying That Administration Services Server Is Running as a Windows Service” on page 71

● “Stopping the Administration Services Server Windows Service” on page 72

● “Starting the Administration Services Server Windows Service” on page 72

● “Resetting the Administration Services Server Windows Service” on page 73

● “Uninstalling the Administration Services Server Windows Service” on page 73

Verifying That Administration Services Server Is Running as a Windows Service

➤ To verify that Administration Services Server is running as an automatic Windows service after you reboot:

1 Select Start > Settings > Control Panel.

2 Double-click Administrative Tools.


3 Double-click Services.

In the list of services, find the service name (see “Starting the Administration Services Server Windows Service” on page 64). The Startup (or Startup Type) field for the service should say Automatic, and the Status field should say Started.

Note: If the Startup field is blank or if it says Disabled or Manual, see “Resetting the Administration Services Server Windows Service” on page 73.

Stopping the Administration Services Server Windows Service

➤ To stop the Administration Services Server Windows service:




4 Find the service name.

See “Starting the Administration Services Server Windows Service” on page 64 for a list of service names.

5 Highlight, but do not double-click, the service name.

6 Select Action > Stop.

The Service Control message box is displayed briefly. After the message box is displayed, the Status field for the server is blank.

Starting the Administration Services Server Windows ServiceIf you stop the Administration Services Server Windows service or if you have just added Administration Services Server as a Windows service, you can start the service from the Services dialog box of the Control Panel.

➤ To start the Administration Services Server Windows service:




4 Find the service name.


5 Highlight, but do not double-click, the service name.

6 Select Action > Start.

The Service Control message box is displayed briefly when the Status field for the server says Started.


Resetting the Administration Services Server Windows ServiceIf someone disables the service or sets it to manual startup, you can reset Administration Services Server to start automatically.

➤ To reset Administration Services Server to start automatically:




4 Double-click the service name.


5 Set the service to log on automatically as a system account.

a. In the properties dialog box, select Automatic from the Startup type drop-down list.

b. In the Log On tab, select Local System account.

Uninstalling the Administration Services Server Windows Service

➤ To uninstall the Administration Server Windows service:

1 Stop the service.

See “Stopping the Administration Services Server Windows Service” on page 72.

2 From a command prompt, navigate to the following directory:

EASPATH\server\bin


3 Run the following command, according to the application server you deployed to:


A message displayed in the command prompt window indicates that the service is removed.

Reinstalling the Administration Services Server Windows Service

➤ To reinstall the Administration Server Windows service:

1 Uninstall the service.

2 From a command prompt, navigate to the following directory:

EASPATH\server\bin

Table 20 Scripts to Uninstall Administration Server Windows Service

Application Server Script Start Menu

BEA WebLogic 8.1.4 uninstallEASWebLogic81eas.bat Start > Programs > Hyperion System 9 BI+ > Analytic Administration Services > Uninstall Administration Services Server (WebLogic81 eas)

IBM WebSphere 5.1.1.7 uninstallEASWebSphere51eas.bat Start > Programs > Hyperion System 9 BI+ > Analytic Administration Services > Uninstall Administration Services Server (WebSphere51 eas)

IBM WebSphere 5.0.2 uninstallEASWebSphere50eas.bat Start > Programs > Hyperion System 9 BI+ > Analytic Administration Services > Uninstall Administration Services Server (WebSphere50 eas)

Apache Tomcat 5.0.28 uninstallEASTomcat5eas.bat Start > Programs > Hyperion System 9 BI+ > Analytic Administration Services > Uninstall Administration Services Server (Tomcat eas)


3 Run the following command, according to the application server you deployed to:


Implementing SSL on Apache Tomcat

➤ To implement SSL for Administration Services on Apache Tomcat:

1 Obtain private keys and digital certificates. To generate a certificate using keytool, run the command keytool -genkey -alias tomcat -keyalg RSA.

The .keystore file will be created in the EAS_HOME directory.

OPTIONAL: To specify a different location or filename, add the -keystore parameter, followed by the complete pathname to your keystore file, to the keytool command. You must reflect this location in the server.xml configuration file, as described in step 2.

For example, to specify a different location or file name for the following keystore file:

keytool -genkey -alias tomcat -keyalg RSA -keystore "c:\ “

Add the following full path name:

Keytool -genkey -alias tomcat -keyalg RSA -keystore "c:\MyTomcat\mytomcat.keystore" ("c:/MyTomcat/mytomcat.keystore" on UNIX)

2 In the Tomcat configuration file located at EASHOME/deployments/Tomcat/5.0.28/conf/server.xml

(EASHOME\deployments\Tomcat\5.0.28\conf\server.xml on UNIX), edit the keystoreFile and keystorePass lines, inserting the values from the previous step. Example:

keystoreFile="c:\MyTomcat\mytomcat.keystore" (keystoreFile="c:/MyTomcat/mytomcat.keystore" on UNIX)

keystorePass="<generated password>"

3 Configure the Administration Services server by adding the following lines to the EASHOME\server\OlapAdmin.properties file (EASHOME/server/OlapAdmin.properties on UNIX):

Table 21 Scripts to Install Administration Server Windows Service

Application Server Script Start Menu

BEA WebLogic 8.1.4 installEASWebLogic81eas.bat Start > Programs > Hyperion System 9 BI+ > Analytic Administration Services > Install Administration Services Server (WebLogic81 eas)

IBM WebSphere 5.1.1.7 installEASWebSphere51eas.bat Start > Programs > Hyperion System 9 BI+ > Analytic Administration Services > Install Administration Services Server (WebSphere51 eas)

Apache Tomcat 5.0.28 installEASTomcat5eas.bat Start > Programs > Hyperion System 9 BI+ > Analytic Administration Services > Install Administration Services Server (Tomcat eas)


ALWAYS_USE_SSL=true

SSL_PORT=10090

4 7.Configure Administration Services Console by opening the AASHOME\console\bin\admincon.lax file (AASHOME/console/bin/admincon.lax on UNIX) and adding the following lines to the line starting with lax.nl.java.option.additional:

-Djavax.net.ssl.trustStore=c:\MyTomcat\mytomcat.keystore (Windows)

-Djavax.net.ssl.trustStore=c:/MyTomcat/mytomcat.keystore (UNIX)

-Djavax.net.ssl.password=<password>

After editing the line, it will look similar to this example (Windows):

lax.nl.java.option.additional=-Xmx256M -DUSE_FOXTROT_BY_DEFAULT=NO- DEAS_HOME=AASHOME\AdminServices -Djava.io.tmpdir=..\temp -Djavax.net.ssl.trustStore=c:\MyTomcat\mytomcat.keystore -Djavax.net.ssl.password=password

5 8.Import the AAS server root certificate to AAS console cacerts: from the command prompt window, navigate to <HYPERION_HOME>\JDK\Sun\1.4.2\jre\bin, and execute following keytool command:

- keytool -import -alias <alias_name> -file < aas_server_certificate_name> -keystore

"<HYPERION_HOME>\JRE\Sun\1.4.2\lib\security\cacerts -storepass changeit

Setting Up Administration Services UsersAdministration Services Server can run in native security mode or in Shared Services security mode. User setup differs for each mode.

● “Setting Up Native Users” on page 77

● “Setting Up Users in Shared Services” on page 77

For complete information about managing Administration Services users in either security mode, see the Essbase Administration Services Online Help. For information about managing Essbase users in either security mode, see the Hyperion Essbase – System 9 Database Administrator’s Guide.


Setting Up Native Users

In native security mode, you can use the User Setup Wizard to add users to Administration Services Server and populate each user’s Enterprise View with the appropriate Essbase Servers.

Note: If Administration Services Server is running in Shared Services security mode, the User Setup Wizard is not available.

➤ To add users to Administration Services Server and populate each user’s Enterprise View:

1 From the Administration Services Console window, launch the User Setup Wizard by selecting Wizards > User Setup Wizard.

2 In the User Setup Wizard, follow the prompts to set up users for Administration Services, keeping in mind the following factors:

● If you connected using the default administrator information, change the password for the administrator account.

● If you need help while using the User Setup Wizard, click Help.

Note: Users can also manage their own list of Essbase Servers using the User Setup Wizard, the User Properties window, or the right-click menu off of the Essbase Servers node in Enterprise View.

Setting Up Users in Shared Services

When Administration Services Server is running in Shared Services security mode, most user management tasks are performed using the Shared Services User Management Console. Only the currently logged on user is displayed in Enterprise View in Administration Services Console. Each Administration Services user can also manage his or her own list of Essbase Servers using the User Properties window or the right-click menu off of the Essbase Servers node in Enterprise View.

For general instructions on using the User Management Console, see the Hyperion System 9 Shared Services User Management Guide.

Setting Up Business Rules UsersAfter installing and configuring Administration Services, you must use the Shared Services User Management Console to provision Business Rules users. For general instructions on using the User Management Console, see Hyperion System 9 Shared Services User Management Guide. For information on provisioning Business Rules users, see the Hyperion System 9 Business Rules Administrator’s Guide.


Backing Up and Restoring User InformationAfter you create Administration Services users and establish each user’s list of Essbase Servers, you should export user information so that you can restore if necessary.

Note: This section applies only if Administration Services Server is running in native security mode.

➤ To back up (export) user information:

1 From the Administration Services Console window, under the Administration Services Servers node, select the Administration Services Server name.

2 Right-click and select Export users.

3 In the Export Users dialog box, specify the location for the export file.

4 Click Export.

The user information is exported to the specified location in XML format, with sensitive data encrypted. The user information for the default administrator account is not exported.

➤ To restore (import) user information:

1 From the Administration Services Console window, under the Administration Services Servers node, select the Administration Services Server name.

2 Right-click and select Import users.

3 In the Import Users dialog box, navigate to the location of the export file.

4 Click Import.

User information is restored. Current users are not overwritten.

Setting Up an SMTP ServerSimple Mail Transfer Protocol (SMTP) is a protocol for sending e-mail messages. To enable administrators to send e-mail messages directly from Administration Services Console to other administrators or to Hyperion Technical Support, an outgoing mail (SMTP) server must be specified on the Administration Services Server computer. When an administrator sends e-mail from Administration Services Console, the specified SMTP server is used to send the message to the receiver's e-mail client.

Specify an SMTP server in Administration Services Console on the Admin Server Properties window—Configuration tab. If an SMTP server is not specified, administrators cannot send e-mail from the console.


➤ To specify an outgoing mail server:


See “Starting Administration Services” on page 62.

2 From the Administration Services Console window under the Administration Services Servers node, select the Administration Services Server name.

3 Right-click and select Edit properties.

4 In the Admin Server Properties window, select the Configuration tab.

5 In the E-mail Server area, enter the name of the SMTP server.

6 Click Apply and close the Admin Server Properties window.

For more information about setting up an SMTP server, see Essbase Administration Services Online Help.

Uninstalling Administration Services 81

C h a p t e r

6Uninstalling Administration

Services

This chapter provides instructions for using the cross-platform uninstaller program to remove Administration Services Server and Administration Services Console Release 9.0 from your system.

The uninstaller program does not remove the following information:

● The common components that reside in the HYPERION_HOME\common directory

● Files used to store Administration Services user information (from the EASPATH\storage\easusers directory)

● Log files that reside in the EASPATH\server directory.

● Other files or directories that are created after installation

If you are using the default application server, documentation files are removed by the uninstaller.

➤ To uninstall Administration Services:

1 If you want to retain Administration Services user information, back up the directory used to store Administration Services users and objects that are saved on Administration Services Server:

EASPATH\eas\storage

2 If you are uninstalling Administration Services Server and you installed Administration Services Server as a Windows service, stop and remove the Administration Services Server Windows service.

See “Uninstalling the Administration Services Server Windows Service” on page 73.

3 Stop all instances of Administration Services Server and Administration Services Console.

4 Launch the uninstaller program for your platform.

Note: On Windows platforms, you can also uninstall from the Control Panel (Add/Remove Programs).

5 Follow the uninstaller prompts.

Table 22 Administration Services Uninstaller Program

Platform Uninstaller Program

Windows EASPATH\uninstall\uninstall.exe

UNIX EASPATH/uninstall/uninstall

82 Uninstalling Administration Services

Upgrading Administration Services 83

C h a p t e r

7Upgrading Administration

Services

This chapter describes the process for upgrading from a previous release of Administration Services to this release.

In This Chapter Upgrading Administration Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

Uninstalling Previous Releases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

84 Upgrading Administration Services

Upgrading Administration ServicesAll products in release 9.2.1 including Administration Services (Data Integration Management excepted) support upgrades from Releases 7.2.5.2, 9.0.1x and 9.2.

➤ To upgrade from a previous release of Administration Services to this release:

1 Verify that you have all necessary software and documentation for this release.

2 Decide how you want to deploy Administration Services.

See “Deployment of Administration Services with Essbase Server” on page 38.

3 Ensure that system requirements and prerequisites are met.

See Chapter 3, “Planning the Installation.”.

4 From the previous installation, back up the directory used to store Administration Services users and objects that are saved on Administration Services Server:

EASPATH\storage

5 Stop Administration Services Server and Administration Services Console.

6 If you are uninstalling Administration Services Server and you installed Administration Services Server as a Windows service, stop and remove the Administration Services Server Windows service.

See “Uninstalling the Administration Services Server Windows Service” on page 73.

7 Uninstall previous releases of Administration Services.

See “Uninstalling Previous Releases” on page 84.

8 Delete the following directory:

EASPATH

9 Install this release of Administration Services.

See “Installing Administration Services” on page 41.

10 Restore the storage directory that you backed up in step 4.


See “Starting Administration Services Server” on page 63.

Uninstalling Previous ReleasesThis section describes how to uninstall a previous release of Administration Services. For information about uninstalling the current release, see Chapter 6, “Uninstalling Administration Services.”

➤ To uninstall a previous release of Administration Services:

1 Stop all instances of Administration Services Server and Administration Services Console.

2 Launch the uninstaller program for your platform:

● Windows: EASPATH\uninstall\uninstall.exe

Uninstalling Previous Releases 85

● UNIX: EASPATH/uninstall/uninstall

Note: On Windows platforms, you can also uninstall from the Control Panel (Add/Remove Programs).

3 Follow the uninstaller prompts.

4 After the uninstallation is complete, delete the EASPATH directory.

86 Upgrading Administration Services

Manually Configuring Third-Party Relational Databases 87

A P P E N D I X

AManually Configuring Third-

Party Relational Databases

This appendix describes how to manually configure supported third-party relational databases for use with Administration Services. To view the list of supported databases for this release, see “Software Support Matrix for Windows and UNIX” on page 27.

You can automatically deploy to supported third-party relational databases using the Configuration Utility. See “Hyperion Configuration Utility” on page 52.

In This Appendix Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

Configuring an Oracle Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

Configuring an IBM DB2 Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

Configuring a SQL Server Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

Changing the Database Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

88 Manually Configuring Third-Party Relational Databases

Overview

The relational database used with Administration Services is used only to store Log Analyzer information and for Business Rules.

By default, the Administration Server installation automatically installs, configures, and starts the MySQL database. For other supported databases, you can use the Configuration Utility to provide configuration information for another supported database. The Configuration Utility prompts you for the database name/SID, host name, port number, and user ID. You can also modify configuration information manually after the initial configuration, either by running the Configuration utility again or by following the procedures in the sections below.

For more information about the MySQL database, see “Installing Administration Services Software” on page 42.

Note: Third-party databases do not have to be installed on the same computer as Administration Services Server.

Configuring an Oracle DatabaseFollow this procedure if you need to modify configuration information for the database after installation.

➤ To enable Oracle support:

1 In Oracle, create an Oracle user with permissions to create tables.

2 Navigate to EASPATH\server and back up the dao.properties file.

Note: The directory where you install Administration Services is referred to as the EASPATH directory.

3 Copy the contents of the dao.properties.oracle file into the dao.properties file.

4 In a text editor, open the dao.properties file and replace the following values:

● Replace eas.user and eas.password with the user connection values for the Oracle user created in Step 1.

● Replace HOSTNAME with the hostname where Oracle is currently running and replace SID_NAME with the Oracle SID to be connected. Both of these values are Oracle-specific.

5 Optional: Replace port number 1521 with the port number for the Oracle database.

Note: If Oracle is running on the default port, you can skip this step and proceed to the next step.

Configuring an IBM DB2 Database 89

6 Navigate to EASPATH\server\dbms and run the InitDB.exe file (InitDB on UNIX). This file creates the required tables in Oracle.

Tip: You can ensure that the tables are created correctly by viewing the InitDB.log file.

7 Restart Administration Services Server and Administration Services Console.


Configuring an IBM DB2 DatabaseFollow this procedure if you need to modify configuration information for the database after installation.

➤ To enable IBM DB2 support:

1 In DB2, create a DB2 user with permissions to create tables.



3 Copy the contents of the dao.properties.db2 file into the dao.properties file.


● Replace eas.user and eas.password with the user connection values for the DB2 user created in step 1.

● Replace HOSTNAME with the hostname where DB2 is currently running and replace DB_NAME with the DB2 database name.

Caution! The DB2 database name must be uppercase. For example, DBNAME.

5 Optional: Replace port number 50000 with the port number for the DB2 database.

Note: If DB2 is running on the default port, you can skip this step and proceed to the next step.


6 Navigate to EASPATH\server\dbms and run the InitDB.exe file (InitDB on UNIX). This file creates the required tables in DB2.




Configuring a SQL Server DatabaseFollow this procedure if you need to modify configuration information for the database after installation.

➤ To enable SQL Server support:

1 In SQL Server, create a user with permissions to create tables.



3 Copy the contents of the dao.properties.sqlserver file into the dao.properties file.


● Replace eas.user and eas.password with the user connection values for the SQL Server user created in step 1.

● Replace HOSTNAME with the hostname where SQL Server is currently running and replace DB_NAME with the SQL Server database name.

Caution! The SQL Server database name must be uppercase. For example, DBNAME. In addition, When you create a SQL Server database, do not start the repository name with a number. If you do, the database connection may fail when you test it.

5 Optional: Replace port number 1433 with the port number for the SQL Server database.

Note: If SQL Server is running on the default port, you can skip this step and proceed to the next step.

Changing the Database Password 91

6 Navigate to EASPATH\server\dbms and run the InitDB.exe file (InitDB on UNIX). This file creates the required tables in SQL Server.




Changing the Database PasswordIn some cases, it might be necessary to change the database password without connecting to Administration Services Server.

➤ To change the database password:

1 In a text editor, navigate to the EASPATH\server directory and open the dao.properties file.


2 Change the value of the eas.password field in the dao.properties file. The password is in an unencrypted format.


When Administration Services is started, Administration Services Server finds and encrypts the unencrypted password in the dao.properties file.

Manually Configuring Web Application Servers 93

A P P E N D I X

BManually Configuring Web

Application Servers

This appendix explains how to perform manual deployment to supported third-party Web application servers for use with Administration Services. To view the list of supported Web application servers for this release, see “Software Support Matrix for Windows and UNIX” on page 27.

You can automatically deploy to supported third-party application servers using the Configuration Utility. See “Hyperion Configuration Utility” on page 52.

This appendix includes the following topics:

In This Appendix Configuring BEA WebLogic 9.2 (MP1) Application Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

Configuring BEA WebLogic 8.1.4 Application Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

Configuring IBM WebSphere 6.1 Application Servers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

Configuring IBM WebSphere 5.1.1.7 Application Servers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

Configuring Oracle 10g Release 3 (10.1.3.1.0) Application Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

94 Manually Configuring Web Application Servers

Configuring BEA WebLogic 9.2 (MP1) Application ServersIf you deploy WebLogic 9.2 servers manually, rather than with Hyperion Configuration Utility, use the following procedures.

Preparing to Configure WebLogic 9.2● If WebLogic Server is not installed, install it.

● Install Essbase Administration Server to the computer hosting WebLogic Server.

Creating a Domain

➤ To create a domain:

1 Launch BEA Weblogic Configuration Wizard

2 Select Create a new WebLogic Domain and click Next

3 Select Generate a Domain configured automatically to support the following BEA products and click Next

4 Enter the username and password for the default domain administrator and click Next

5 Select either Development Mode or Production Mode, select the JDK, and click Next

6 In Customize Environment and Setting Screen, select No, then Next

7 Enter the domain name and file path and click Create

8 Select Start Admin Server, enter the username and password you created in step 4 and click Done

Deploying to WebLogic

➤ To deploy the eas.ear file from EASPATH/AppServer/InstallableApps/common (UNIX) or EASPATH\AppServer\InstallableApps\common (Windows):

1 Start the WebLogic administration console by launching a Web browser and entering the URL http://<servername>:7001/console.

2 Log on to the administration console using the username and password created in “Creating a Domain” on page 94.

3 In Change Center, click Lock and Edit.

4 In Domain Structure, click Deployments.

5 In Summary of Deployments, click Install.

6 Browse to the eas.ear file and select it, then click Next.

7 Select Install this deployment as an application and click Next.

Configuring BEA WebLogic 9.2 (MP1) Application Servers 95

8 Leave all default settings in the remaining screens. Click Next on each screen until the last one, then click Finish.

9 Click Save.

10 In Change Center, click Activate Change.

11 In a text editor, open <DOMAIN_HOME>/bin/setDomainEnv.sh (UNIX) or <DOMAIN_HOME>\bin\setDomainEnv.cmd (Windows) and enter the following at the end of the file:

(Windows)

set EAS_HOME=<EASPATH>set ARBORPATH=%EAS_HOME%\serverset PATH=%ARBORPATH%\bin;%EAS_HOME%\server\bin;%HYPERION_HOME%\common\SAP\bin;%HYPERION_HOME%\common\SAP\lib\sapjco.jar;%PATH%;set CLASSPATH=%HYPERION_HOME%\common\SAP\bin;%HYPERION_HOME%\common\SAP\lib\sapjco.jar;%CLASSPATH%set JAVA_OPTIONS=-DEAS_HOME=%EAS_HOME% -DEAS_LOG_LEVEL=5000 -DEAS_LOG_LOCATION=%ARBORPATH%/bin/easserver.log -Djava.io.tmpdir=%EAS_HOME%/deployments/Tomcat/5.0.28/tempset PRE_PATH=%HYPERION_HOME%\common\CSS\9.2.1\bin;%HYPERION_HOME%\common\SAP\bin;%HYPERION_HOME%\common\SAP\lib\sapjco.jar;set PRE_CLASSPATH=%HYPERION_HOME%\common\JCE\1.2.2\jce1_2_2.jar;%HYPERION_HOME%\common\JCE\1.2.2\local_policy.jar;%HYPERION_HOME%\common\JCE\1.2.2\sunjce_provider.jar;%HYPERION_HOME%\common\JCE\1.2.2\US_export_policy.jar;%HYPERION_HOME%\common\SAP\bin;%HYPERION_HOME%\common\SAP\lib\sapjco.jar;set CLASSPATH=%PRE_CLASSPATH%;%CLASSPATH%

(UNIX)

export EAS_HOME=<EASPATH>export ARBORPATH=$EAS_HOME/serverexport PATH=$ARBORPATH/bin;$EAS_HOME/server/bin;$HYPERION_HOME/common/SAP/bin;$HYPERION_HOME/common/SAP/lib/sapjco.jar;$PATH;export CLASSPATH=$HYPERION_HOME/common/SAP/bin;$HYPERION_HOME/common/SAP/lib/sapjco.jar;$CLASSPATHexport JAVA_OPTIONS=-DEAS_HOME=$EAS_HOME -DEAS_LOG_LEVEL=5000 -DEAS_LOG_LOCATION=$ARBORPATH/bin/easserver.log -Djava.io.tmpdir=$EAS_HOME/deployments/Tomcat/5.0.28/tempexport PRE_PATH=$HYPERION_HOME/common/CSS/9.2.1/bin;$HYPERION_HOME/common/SAP/bin;$HYPERION_HOME/common/SAP/lib/sapjco.jar;export PRE_CLASSPATH=$HYPERION_HOME/common/JCE/1.2.2/jce1_2_2.jar;$HYPERION_HOME/common/JCE/1.2.2/local_policy.jar;$HYPERION_HOME/common/JCE/1.2.2/sunjce_provider.jar;$HYPERION_HOME/common/JCE/1.2.2/US_export_policy.jar;$HYPERION_HOME/common/SAP/bin;$HYPERION_HOME/common/SAP/lib/sapjco.jar;export CLASSPATH=$PRE_CLASSPATH;$CLASSPATH


Note: DOMAIN_HOME is the domain directory path created in “Creating a Domain” on page 94, and EASPATH is the directory in which Administration Services was installed.

Note: In some UNIX shells, set a=b is not supported. In these shells, substitute the following: a=b; export a

12 Save the file and restart the server

13 Log on to the administration console

14 In Deployments, select eas and click start. Essbase Administration Server will start on port 7001 by default.

Configuring BEA WebLogic 8.1.4 Application ServersThe following sections describe how to deploy Administration Services Server on a WebLogic Server by platform:

● “Configuring WebLogic 8.1.4 Application Servers on Windows” on page 96

● “Configuring WebLogic 8.1.4 Application Servers on UNIX” on page 99

Configuring WebLogic 8.1.4 Application Servers on WindowsConfiguring WebLogic 8.1.4 consists of the following tasks:

● Meet prerequisites.

● Create a domain.

● Modify and execute the startup script.

● Deploy to WebLogic.

● Log on.

PrerequisitesBefore you begin, perform these tasks:

● If it is not installed, install WebLogic Server.

● Install Administration Services Server to the computer hosting WebLogic Server.

Creating a Domain

➤ Detailed steps to create a domain are as follows:

1 Launch the WebLogic Configuration Wizard by running:

weblogic81\common\bin\config.cmd

Configuring BEA WebLogic 8.1.4 Application Servers 97

2 Accept the defaults and click Next until you reach the Configure Administrative Username and Password panel.

3 Enter the username and password (for example, enter aas for the username and password for the password).

4 In the Configure Server Start Mode and Java SDK panel, choose development mode or production mode. Select the default SDK value.

5 In the bottom-right corner of the Create WebLogic Configuration panel, rename the configuration, for example, to aasdomain.

6 Click Create.

7 Click Done to exit the Configuration Wizard.

Modify and Execute the Startup Script

➤ Modify and execute the startEASWebLogic.bat startup script:

1 Change the directory to EASPATH\server\bin, where EASPATH is the directory to which Administration Services is installed.

2 Open the startEASWebLogic.bat file in a text editor.

3 Replace WEBLOGIC_INSTALL_DIR with the directory to which WebLogic is installed.

4 Replace HYPERION_HOME with the HYPERION_HOME directory specified at installation time.

5 Execute startEASWebLogic.bat and pass the domain name created earlier as a parameter to this script:

Run startEASWebLogic.bat <domain name>

where <domain name> is the domain name you created earlier, for example, aasdomain.

Note: The startEASWebLogic.bat file must be executed from EASPATH\server\bin.

Deploy to WebLogicDeploy the eas.ear file from EASPATH\AppServer\InstallableApps\common.

➤ Detailed steps to deploy to WebLogic are as follows:

1 Connect to the WebLogic administration console using the following URL:

http://machineName:7001/console

By default, WebLogic runs on port 7001 on machineName; if using another port, specify the port value when connecting.

If prompted for a username and password, provide the username and password specified when you created the domain.


Note: If you are accessing the WebLogic administration console locally, you can start the administration console using the Windows Start menu. You can also run the administration console on Windows to connect to WebLogic Server on UNIX.

2 From the WebLogic Server Admin Console, select Deployments > Applications.

3 Click Deploy a new Application.

4 Click upload your file(s)

5 Click Browse.

6 Navigate to the following directory:

EASPATH\AppServer\InstallableApps\common

where EASPATH is the directory to which Administration Services is installed.

7 Select the eas.ear file, and click Open and Upload.

Note: If you are accessing WebLogic remotely, you must first copy the .ear file to your local machine and browse to the local directory to select the .ear file.

8 Select myserver and upload.

9 Select eas.ear, and click Target Module.

10 Click Deploy.

After a brief wait, you will see Administration Services Server messages in the WebLogic Server window. These messages indicate that Administration Services is deployed and ready to be used. By default, WebLogic runs on port 7001; therefore, use machineName:7001 when connecting to Administration Services Server.

Log On to Administration Services Console

➤ Log on to Administration Services Console on the WebLogic Application Server:

1 Launch Administration Services Console.

2 In the Analytic Administration Services Login dialog box, type the following in the Administration Services Server text box:

machineName:7001

Note: The default port number that is used by WebLogic is 7001. If you are using another port number, use that number instead to connect to WebLogic.

Other tasks such as undeploying Administration Services, redeploying Administration Services, and changing the default port number can also be accomplished using the WebLogic Server Admin Console.


Deploying Administration Server on WebLogic Server with JRockit JVM (Windows)

➤ If Administration Server is running on a WebLogic 8.1.4 Server with the JRockit JVM 1.4.x, you must modify the startEASWebLogic.bat file, as follows:

1 Navigate to the EASPATH\server\bin directory, where EASPATH is the directory to which Administration Services is installed.

2 Open the startEASWebLogic.bat file in a text editor.

3 Change the following line:

set JAVA_OPTIONS=-DEAS_HOME=%CD%

to

set JAVA_OPTIONS=-Xss256K -DEAS_HOME=%CD%

4 Save and close the file.

Configuring WebLogic 8.1.4 Application Servers on UNIXConfiguring WebLogic 8.1.4 consists of the following tasks:


● Create a domain.

● Modify and execute the startup script

● Deploy to WebLogic.

● Log on.


● If it is not installed, install WebLogic Server.

● Install Administration Services Server to the computer hosting WebLogic Server.

Creating a Domain

➤ Detailed steps to create a domain are as follows:

1 Launch the WebLogic Configuration Wizard by running:

weblogic81/common/bin/config.sh

2 Accept the defaults and click Next until you reach the Configure Administrative Username and Password panel.


3 Enter the username and password (for example, enter aas for the username and password for the password).

4 In the Configure Server Start Mode and Java SDK panel, choose development mode or production mode. Select the default SDK value.

5 In the bottom-right corner of the Create WebLogic Configuration panel, rename the configuration, for example, to aasdomain.

6 Click Create.

7 Click Done to exit the Configuration Wizard.


➤ Modify and execute the startEASWebLogic.sh startup script:

1 Change the directory to EASPATH/server/bin, where EASPATH is the directory to which Administration Services is installed.

2 Open the startEASWebLogic.sh file in a text editor.

3 Replace WEBLOGIC_INSTALL_DIR with the directory to which WebLogic is installed.

4 Replace HYPERION_HOME with the HYPERION_HOME directory specified at installation time.

5 Execute startEASWebLogic.sh and pass the domain name created earlier as a parameter to this script:

Run startEASWebLogic.sh <domain name>

where <domain name> is the domain name you created earlier, for example, aasdomain.

Note: The startEASWebLogic.sh file must be executed from EASPATH/server/bin.

Deploy to WebLogic Deploy the eas.ear file from EASPATH/AppServer/InstallableApps/common.

➤ Detailed steps to deploy to WebLogic are as follows:

1 Connect to the WebLogic administration console using the following URL:

http://machineName:7001/console

By default, WebLogic runs on port 7001 on machineName; if using another port, specify the port value when connecting.

If prompted for a username and password, provide the username and password specified when you created the domain.

2 From the WebLogic Server Admin Console, select Deployments > Applications.

3 Click Deploy a new Application.

4 Click upload your file(s) and click Browse.


5 Navigate to the following directory:

EASPATH/AppServer/InstallableApps/common


6 Select the eas.ear file, and click Open and Upload.

Note: If you are accessing WebLogic remotely, you must first copy the .ear file to your local machine and browse to the local directory to select the .ear file.

7 Select myserver and upload.

8 Select eas.ear, and click Target Module.

9 Click Deploy.

After a brief wait, you will see Administration Services Server messages in the WebLogic Server window. These messages indicate that Administration Services is deployed and ready to be used. By default, WebLogic runs on port 7001; therefore, use machineName:7001 when connecting to Administration Services Server.

Log On to Administration Services Console

➤ Log on to Administration Services Console on the WebLogic Application Server:



machineName:7001

Note: The default port number that is used by WebLogic is 7001. If you are using another port number, use that number instead.

Other tasks such as undeploying Administration Services, redeploying Administration Services, and changing the default port number can also be accomplished using the WebLogic Server Admin Console.

Deploying Administration Server on WebLogic Server with JRockit JVM (UNIX)

➤ If Administration Server is running on a WebLogic 8.1.4 Server with the JRockit JVM 1.4.x, you must modify the startEASWebLogic.sh file, as follows:

1 Navigate to the EASPATH/server/bin directory, where EASPATH is the directory to which Administration Services is installed.

2 Open the startEASWebLogic.sh file in a text editor.


3 Change the following line:

set JAVA_OPTIONS=-DEAS_HOME=$CDIR

to

set JAVA_OPTIONS=-Xss256K -DEAS_HOME=$CDIR

4 Save and close the file.

Enabling SSL for WebLogic 8.1.4

➤ To enable SSL for WebLogic 8.1.4:

1 Procure digital certificate or use keytool to generate digital certificates: keytool -genkey -alias weblogic -keystore EasWLKeyStore.jks -storepass password.

2 Log in to WebLogic Administration Console (http://hostname:10080/console) and perform these steps:

a. In the navigation panel, expand Servers under eas domain and select eas to configure keystores.

b. Select Server1.

The configuration page is displayed.

c. Under the General tab, select SSL Listen Port Enabled and enter 9443 in the SSL Listen Port text field. This is the port on which the server will listen for HTTPS requests.

d. Click Apply.

e. Select Configuration > Keystores, then select the SSL tab.

f. Click Change on the Keystore Configuration page to configure new keystores.

g. On the Configure Keystores page, select the Custom Identity and Custom Trust keystore option from the drop-down list and click Continue.

h. Define attributes for the keystore:

❍ Select Custom Identity Keystore File Name.

❍ Provide the absolute path to the generated keystore.

i. Under the Custom Identity heading on the Configure Keystore Properties page, change the specified fields as required:

❍ For Custom Identity Keystore, provide the absolute path to generated keystore (for example: C:\WLSert\EasWLKeystore.jks on Windows or C:/WLSert/EasWLKeystore.jks on UNIX).

❍ For Type, enter JKS.

❍ For Pass Phrase, enter password specified during keystore generation.

❍ For Confirm Pass Phrase, reenter the password.

j. Under the Custom Trust heading, change the specified fields as required:

Configuring IBM WebSphere 6.1 Application Servers 103

❍ For Custom Identity Keystore, provide the absolute path to generated keystore (for example: C:\WLSert\EasWLKeystore.jks on Windows or C:/WLSert/EasWLKeystore.jks on UNIX).

❍ For Type, enter JKS.

❍ For Pass Phrase, enter password specified during EasWLKeystore.jks generation.

❍ For Confirm Pass Phrase, reenter the password.

k. Click Continue.

3 Review SSL Private Key Settings:

● For Private Key Alias, enter the alias specified during generated during keystore generation (for example, weblogic).

● For Passphrase, enter the password specified during EasWLKeystore.jks generation.

● For Confirm Passphrase, reenter the password.

4 Click Finish, and restart WebLogic Server.

5 Import the AAS server root certificate to AAS console cacerts: from the command prompt window, navigate to <HYPERION_HOME>\JDK\Sun\1.4.2\jre\bin, and execute following keytool command:

- keytool -import -alias <alias_name> -file < aas_server_certificate_name> -keystore <HYPERION_HOME>\JRE\Sun\1.4.2\lib\security\cacerts -storepass changeit

Configuring IBM WebSphere 6.1 Application ServersIf you deploy Websphere 6.1 servers manually, rather than with Hyperion Configuration Utility, use the following procedures.

Preparing to Configure Websphere 6.1If WebSphere Application Server is not installed, install it. Install Essbase Administration Server to the computer hosting WebSphere Application Server.

Creating a ProfileBefore deploying Administration Services on WebSphere 6.1, you must create a profile. A profile enables users to run separate instances of WebSphere, where each instance can have a set of deployed applications. A default profile is automatically created when installing WebSphere.

➤ To create a profile and deploy Administration Services on WebSphere 6.1:

1 Launch the First Steps wizard from WAS_HOME/AppServer/profiles/AppSrv01/firststeps/firststeps.sh (UNIX) or WAS_HOME\AppServer\profiles\AppSrvr01\firststeps\firststeps.bat (Windows), where WAS_HOME is the WebSphere installation directory.


2 Select Profile Management Tool.

3 In the Welcome panel, click Next.

4 In the Environment Selection panel, select Application Server, then Next.

5 In the Profile Creation Options panel, select Advanced Profile Creation, then Next.

6 In the Optional Application Deployment panel, leave both options selected and click Next.

7 In the Profile Name and Location panel, enter the profile name and directory path. Select the other options only if appropriate for your deployment, and then click Next.

8 In the Node and Host Names panel, leave the default values as displayed and click Next.

9 In the Administrative Security panel, select Enable Administrative Security, enter your username and password, and click Next.

10 In the Port Values Assignment panel, select Default Port Values and verify that none of the ports conflict with existing applications. If a conflict exists, select Recommended Port Values. When all port value conflicts have been resolved, click Next.

11 Windows Only: In the Windows Service Definition panel, select whether to run WebSphere as a Windows service, then click Next.

12 In the Web Server Definition panel, click Next.

13 In the Profile Creation Summary panel, review your options, then click Create.

14 Run the following:

● In Windows, from the WAS_HOME\AppServer\profiles\profile_name\bin directory, run startServer.bat server1, where WAS_HOME is the WebSphere installation directory and profile_name is the profile name created in step 7.

● In UNIX, from the WAS_HOME/AppServer/profiles/profile_name/bin directory, run startServer.sh server1, where WAS_HOME is the WebSphere installation directory and profile_name is the profile name created in step 7.

Deploying Administration ServicesAfter creating a WebSphere profile, continue deploying Administration Services.

➤ To deploy Administration Services:

1 Launch a Web browser and connect to the WebSphere server at http://hostname:port_num/admin, where hostname is the name of the WebSphere host and port_num is the Administration port number determined while creating a profile. The default username is admin.

2 In the WebSphere console, expand the Application Node in the left frame and click Install New Application.

3 In the right frame, browse to the file location of eas.ear and click Next. The default location of eas.ear is EASHOME/AppServer/InstallableApps/Common/eas.ear (UNIX) or EASHOME\AppServer\InstallableApps\Common\eas.ear (Windows).

Configuring IBM WebSphere 6.1 Application Servers 105

4 In the next two screens, leave all default values and click Next.

5 In the Map Modules to Servers screen, select all four Administration Services modules and click Next.

6 In the next screen, select all four Administration Services modules and click Next.

7 In the next screen, click Finish.

8 Click Save to Master Configuration.

9 In the next screen, click Save to save all workspaces.

10 Confirm deployment of the EAR file by clicking Applications > Enterprise Applications in the left frame. “Analytic Administration Server 9.x.x” or “eas” should display with status “stopped” in the right frame.

11 Click Servers > Application Servers in the left frame.

12 Select the checkbox for server 1 to display the Application Services screen.

13 Select Server Infrastructure > Java and Process management on the Configuration tab of the Application Services screen, then select Process definition.

14 Under Additional properties in the next screen, click Java Virtual Machine.

15 In the Generic JVM Arguments text box, enter the following, then click OK:

● Windows: -Djava.awt.headless=true -DEAS_HOME=EASHOME -Dorg.apache.xerces.xni.parser.XMLParserConfiguration=org.apache.xerces.parsers.StandardParserConfiguration -

Djava.library.path=EASHOME\server\bin -DEAS_LOG_LEVEL=5000 -DEAS_LOG_LOCATION=EASHOME\server\bin\easserver.log

● UNIX: -Djava.awt.headless=true -DEAS_HOME=EASHOME -Dorg.apache.xerces.xni.parser.XMLParserConfiguration=org.apache.xerces.parsers.StandardParserConfiguration -

Djava.library.path=EASHOME/server/bin -DEAS_LOG_LEVEL=5000 -DEAS_LOG_LOCATION=EASHOME/server/bin/easserver.log

●

16 For UNIX systems, in the <PROFILE_HOME>/<profile_name>/bin/setupCmdLine.sh file, append the following:

● AIX:

LIBPATH=EASPATH/server/bin

export LIBPATH

● Solaris and Linux:

LD_LIBRARY_PATH=EASPATH/server/bin

export LD_LIBRARY_PATH

● hpux32 and hpux64:

SHLIB_PATH=EASPATH/server/bin.

export SHLIB_PATH

17 Click OK on the process definition screen and the server 1 configuration screen.

18 Click Save on the application server screen.


19 Click Save on the next screen.

20 Close the console window, and stop the server by executing WAS_HOME/AppServer/profiles/profile_name/bin/stopServer.sh server1 (UNIX) or WAS_HOME\AppServer\profiles\profile_name\bin\stopServer.bat server1 (Windows).

21 Restart the server by executing WAS_HOME/AppServer/profiles/profile_name/bin/startServer.sh server1 (UNIX) or WAS_HOME\AppServer\profiles\profile_name\bin\startServer.bat server1 (Windows).

22 Log into the WebSphere server as in step 1, above.

23 Select Applications > Enterprise Applications > Analytic Administration Server 9.x or eas. Start the server if it is not already started.

Configuring IBM WebSphere 5.1.1.7 Application ServersThe following sections describe how to deploy Administration Services Server on a WebSphere 5.1.1.7 Server by platform:

● “Configuring WebSphere 5.1.1.7 Application Servers on Windows” on page 106

● “Configuring WebSphere 5.1.1.7 Application Servers on UNIX” on page 109

Note: If you deploy Administration Services Server on a WebSphere 5.1.1.7 Server, you cannot start Essbase Server remotely from Administration Services Console.

Configuring WebSphere 5.1.1.7 Application Servers on WindowsConfiguring WebSphere 5.1.1.7 consists of the following tasks:



● Deploy to WebSphere.

● Restart and log on.


● If it is not installed, install WebSphere Application Server.

● Install Administration Services Server to the computer hosting WebSphere Application Server.

Configuring IBM WebSphere 5.1.1.7 Application Servers 107


➤ Modify and execute the startEASWebSphere.bat startup script:

1 Change the directory to EASPATH\server\bin, where EASPATH is the directory to which Administration Services is installed.

2 Open the startEASWebSphere.bat file in a text editor.

3 Replace WEBSPHERE_INSTALL_DIR with the directory to which WebSphere is installed.

4 Execute startEASWebSphere.bat and pass the server name to this script:

Run startEASWebSphere.bat server1

Note: The startEASWebSphere.bat file must be executed from EASPATH\server\bin.

Deploy to WebSphere

➤ Detailed steps to deploy to WebSphere are as follows:

1 Launch the WebSphere Administration Console, using the following URL:

http://machineName:9090/admin

By default, WebSphere runs on port 9090 on machineName; if using another port, specify the port value when connecting.

2 Log in if you are prompted to do so.

3 Modify server properties for the WebSphere server instance:

a. Under the Servers node, select Application Servers.

b. Click Server1 to edit.

c. Under Additional Properties, select Process Definition.

d. Under Additional Properties, select Java Virtual Machine.

e. Under General Properties, for Generic JVM Arguments, enter the following information:

-DEAS_HOME=EASPATH -Dorg.apache.xerces.xni.parser. XMLParserConfiguration=org.apache.xerces.parsers. StandardParserConfiguration


Note: All information starting with “-Dorg.apache...” in the examples above must be entered exactly as shown, all as one entry. Typing errors result in WebSphere not starting properly.

f. Under the General Properties table, click Apply.

g. From the toolbar, click Save.

h. Under Save to Master Configuration, click Save.


4 Deploy the .ear file to install Administration Services as a WebSphere application:

a. Under the Applications node, select Install New Application.

b. Choose one of the following steps, depending on the location of the eas.ear file:

❍ If your browser and the eas.ear file are on the same machine, select Local path and browse to and select the eas.ear file in the following directory:

EASPATH\AppServer\InstallableApps\common\eas.ear


Note: The WebSphere server may be on another machine.

❍ If the eas.ear file resides on the machine running the WebSphere server and if your browser is on another machine, select Server path and enter the absolute path to the location of the eas.ear file on the server machine.

c. Click Next.

d. Accept all defaults and click Next or Continue until the final installation screen displays.

e. Click Finish.

f. Click Save to Master Configuration.

g. Click Save.

Restart and Log On

➤ After everything is installed, stop WebSphere Application Server and restart it.

1 Stop the WebSphere application server by using the Windows Start menu or by executing the following script:

WEBSPHERE_INSTALL_DIR\AppServer\bin\stopServer.bat server1

2 Restart the WebSphere application server by executing startEASWebSphere.bat and passing the server name to this script:

Run startEASWebSphere.bat server1

Note: The startEASWebSphere.bat file must be executed from EASPATH\server\bin.



machineName:9080

Note: The default port number that is used by WebSphere Application Server is 9080. If you are using another port number, use that number instead to connect to WebSphere Application Server.


Configuring WebSphere 5.1.1.7 Application Servers on UNIXConfiguring WebSphere 5.1.1.7 consists of the following tasks:



● Deploy to WebSphere.

● Restart and log on.


● If it is not installed, install WebSphere Application Server.

● Install Administration Services Server to the computer hosting WebSphere Application Server.


➤ Modify and execute the startEASWebSphere.sh startup script:

1 Change the directory to EASPATH/server/bin, where EASPATH is the directory to which Administration Services is installed.

2 Open the startEASWebSphere.sh file in a text editor.

3 Replace WEBSPHERE_INSTALL_DIR with the directory to which WebSphere is installed.

4 Execute startEASWebSphere.sh and pass the server name:

Run startEASWebSphere.sh server1

where server1 is the default server name.

Note: The startEASWebSphere.sh file must be executed from EASPATH/server/bin.

Deploy to WebSphere

➤ Detailed steps to deploy to WebSphere are as follows:

1 Launch the WebSphere Administrative Console, using the following URL:

http://machineName:9090/admin

By default, WebSphere runs on port 9090 on machineName; if using another port, specify the port value when connecting.

2 Log in if you are prompted to do so.

3 Modify server properties for the WebSphere server instance:

a. Under the Servers node, select Application Servers.


b. Click on Server1.

c. Under Additional Properties, select Process Definition.

d. Under Additional Properties, select Java Virtual Machine.

e. Under General Properties, for Generic JVM Arguments, enter the following information:

-DEAS_HOME=EASPATH -Dorg.apache.xerces.xni.parser. XMLParserConfiguration=org.apache.xerces.parsers. StandardParserConfiguration


Note: All information starting with “-Dorg.apache...” in the examples above must be entered exactly as shown, all as one entry. Typing errors result in WebSphere not starting properly.

f. Under the General Properties table, click Apply.

g. From the toolbar, click Save.

h. Under Save to Master Configuration, click Save.

4 Deploy the .ear file to install Administration Services as a WebSphere application:

a. Under the Applications node, select Install New Application.

b. Choose one of the following steps, depending on the location of the eas.ear file:

❍ If your browser and the eas.ear file are on the same machine, select Local path and browse to and select the eas.ear file in the following directory:

EASPATH/AppServer/InstallableApps/common/eas.ear where EASPATH is the directory to which Administration Services is installed.

Note: The WebSphere server may be on another machine.

❍ If the eas.ear file resides on the machine running the WebSphere server and if your browser is on another machine, select Server path and enter the absolute path to the location of the eas.ear file on the server machine.

c. Click Next.

d. Accept all defaults and click Next or Continue until the final installation screen displays.

e. Click Finish.

f. Click Save to Master Configuration.

g. Click Save.


Restart and Log On

➤ After everything is installed, stop WebSphere Application Server and restart it.

1 Stop the WebSphere application server by using the Windows Start menu or by executing the following script:

WEBSPHERE_INSTALL_DIR/AppServer/bin/stopServer.sh server1

2 Restart the WebSphere application server by executing startEASWebSphere.sh and passing the server name to this script:

Run startEASWebSphere.sh server1

Note: The startEASWebSphere.sh file must be executed from EASPATH/server/bin.



machineName:9080

Note: The default port number that is used by WebSphere Application Server is 9080. If you are using another port number, use that number instead to connect to WebSphere Application Server.

Enabling SSL for WebSphere 5.1.1.7

➤ To enable SSL for WebSphere 5.1.1.7:

1 Install Sun Java Secure Sockets Extension (JSEE) and configure it for WebSphere:

a. Download and unzip the JSEE files from http://java.sun.com/products/jsse/index-103.html#downloads

b. Delete any existing JSEE files from WebSphere\AppServer\java\jre\lib\ext (Windows) or WebSphere/AppServer/java/jre/lib/ext (UNIX).

c. Copy all the jar files (jcert.jar, jnet.jar, and jsse.jar) from Sun_JSSE_dir\lib to WebSphere\AppServer\java\jre\lib\ext (Windows) or WebSphere/AppServer/java/jre/lib/ext (UNIX).

d. Register Sun JSSE implementation as a security provider by opening WebSphere\AppServer\java\jre\lib\security\java.security in a text editor (WebSphere/AppServer/java/jre/lib/security/java.security on UNIX) and adding security.provider.2=sun.security.provider.Sun as the second provider in the provider list.


Caution! Do not set sun.security.provider.Sun as the first provider. Doing so will cause the java.lang.NoSuchMethodException to occur on execution.

e. Change the entry ssl.KeyManagerFactory.algorithm=IbmX509 in the java.security file to ssl.KeyManagerFactory.algorithm=SunX509.

f. Change the entry ssl.TrustManagerFactory.algorithm=IbmX509 in the java.security file to ssl.TrustManagerFactory.algorithm=SunX509.

g. Uncomment the ssl.SocketFactory.provider= and ssl.ServerSocketFactory.provider= entries in the java.security file and set them to: ssl.SocketFactory.provider=com.sun.net.ssl.internal.ssl.SSLSocketFac

toryImpl and ssl.ServerSocketFactory.provider=com.sun.net.ssl.internal.ssl.SSLServerSocketFactoryImpl

h. Save and close the java.security file.

i. Restart all the applications and the node agent.

2 Log in to the administrative console of the WebSphere application server instance that hosts Administration Server.

3 Create a new HTTP transport for communicating requests to the Web container as follows:

a. Select Servers > Application Servers and select the application server that hosts Administration Server.

b. From Additional Properties, select Web Container.

c. On the Web Container screen, select HTTP transports from Additional Properties.

d. Select New.

e. Enter the following values:

❍ For Host, enter an asterisk (*).

❍ For Port, enter the SSL port; for example, 9443.

❍ Select the Enable SSL checkbox.

f. Click Apply, then click OK.

g. Save changes to the Master Configuration.

h. Select Environment > Virtual Hosts > New.

i. Enter a name for the virtual host and click Reply.

j. Select Configuration > Addition Properties > Host Aliases, then click New.

k. Enter the host name and port number that you entered in step e on page 112.

l. Click Apply, then save changes to the Master Configuration.

m. Restart the WebSphere server.

4 On the computer running Administration Server, edit EASHOME/server/OlapAdmin.properties (UNIX) or EASHOME\server\OlapAdmin.properties (Windows) to include the following:

Configuring Oracle 10g Release 3 (10.1.3.1.0) Application Servers 113

ALWAYS_USE_SSL=true

SSL_PORT=port number

where port number is the SSL port number set in step e on page 112.

5 Save the file and restart WebSphere.

6 Import the AAS server root certificate to AAS console cacerts: from the command prompt window, navigate to <HYPERION_HOME>\JDK\Sun\1.4.2\jre\bin and execute the following keytool command:

- keytool -import -alias <alias_name> -file < aas_server_certificate_name> -keystore <HYPERION_HOME>\JRE\Sun\1.4.2\lib\security\cacerts -storepass changeit

When connecting to the WebSphere server from Administration Services Console, connect using the HTTP port, not the SSL port. Administration Services Console will automatically determine the SSL port.

Configuring Oracle 10g Release 3 (10.1.3.1.0) Application Servers

If you deploy Oracle 10.1.3 servers manually, rather than with Hyperion Configuration Utility, use the following procedures.

Preparing to Configure Oracle 10g Release 3 (10.1.3.1.0) Application Servers● If Oracle 10.1.3 Server is not installed, install it.

● Install Essbase Administration Server to the computer hosting Oracle 10.1.3 Server.

Creating an OC4J Instance and Setting Properties and VariablesTo prevent all deployed applications from inheriting JVM runtime settings that pertain only to Administration Services, Oracle recommends creating a new OC4J instance. Administration Services does not require your Oracle HTTP Server listen port(s) be modified. It is recommended, however, that you make desired port assignments or changes before continuing with deployment. When possible, ports should be configured during installation using staticports.ini as documented in the Oracle® Application Server Installation Guide.

➤ To create an instance and set properties and variables:

1 Follow the instructions in the Oracle® Containers for J2EE Configuration and Administration Guide to create a new OC4J instance called EAS.


Note: OC4J group administrative settings such as environment variables are shared by all group members. Assign your newly created OC4J instance to a group that makes sense for your cluster topology. Refer to the Oracle® Process Manager and Notification Server Administrator's Guide for more information..

2 Set JVM properties:

a. Log on to Oracle® Enterprise Manager 10g Application Server Control.

b. Start the EAS OC4J instance if it is not running.

c. From the Cluster Topology page in Application Server Control Console, navigate to Application Server:instance name.

d. Click the EAS OC4J instance link, then the Administration link, and finally the Server Properties link.

e. Increase the initial heap size to 128 MB and the maximum heap size to 256 MB.

f. Append the following to Start-parameters: Java Options: -DEAS_HOME=EASPATH.

g. Append the following Java options:

❍ Windows, Linux, Solaris, or HP-UX:

-XX:PermSize=64m

-XX:MaxPermSize=128m

❍ Solaris 10 for SPARC:

-Djava.nio.channels.spi.SelectorProvider=sun.nio.ch.PollSelectorProvider

h. Click Apply, then restart the EAS OC4J instance.

3 Configure environment variables:

a. From the Cluster Topology page in Application Server Control Console, navigate to Application Server:instance name.

b. Click the EAS OC4J instance link, then the Administration link, and then the Server Properties link.

c. In the Administration page, select Server Properties.

d. In Environment Variables, click Add Environment Variable, and append the following environment variables:

❍ ARBORPATH

❍ HYPERION_HOME

❍ EASPATH

❍ ESSLANG

with the directory paths specific to your installation, for example /vol0/hyperion (UNIX) or c:\hyperion (Windows) for HYPERION_HOME.

e. Append the following environment variable appropriate to your server operating system:

❍ AIX: LIBPATH=EASPATH/server/bin

❍ SOLARIS and Linux: LD_LIBRARY_PATH=EASPATH/server/bin

Configuring Oracle 10g Release 3 (10.1.3.1.0) Application Servers 115

❍ HP-UX: SHLIB_PATH=EASPATH/server/bin

f. Update your PATH environment variable with the following: PATH = $PATH;EASPATH/server/bin (UNIX) or PATH=EASPATH\server\bin (Windows)

g. Click Apply to save the configuration.

h. Restart the OC4J instance EAS.

Deploying to Oracle 10g Release 3

➤ To deploy to Oracle 10g Release 3:

1 From the Cluster Topology page in Application Server Control Console, navigate to Application

2 Server:instance_name.

3 2 Click the EAS OC4J instance link, then the Applications link, and then the Deploy button.

4 3 Provide the location of the eas.ear Web archive (EASPATH/AppServer/InstallableApps/common for UNIX, EASPATH\AppServer\InstallableApps\common for Windows).

5 4 Click Next to create a new deployment plan.

6 5 Provide an Application name; for example EAS, and click Next.

7 6 Click Deploy.

8 7 Restart the OC4J instance EAS.

Verifying the ConnectionTo verify the connection to Essbase Administration Services, open the Administration Services

Console and log on.

Index Symbols 117

A B C D E F G H I J K L M N O P Q R S T U V W X Y Z

Index

Symbols.dll files, Analytic Services, 37

Aadding

Administration Services users, 77

Analytic Servers to Enterprise View, 77

adding Administration Server as a Windows service, 71

admin account

password, 66, 68

username, 66, 68

ADMINCON.EXE, 66

Administration Server, 31

adding as a Windows service, 71

adding users, 77

ARBORPATH environment variable requirement, 63

compatibility with Console, 34

described, 9

disk space requirements, 22

ESSLANG variable requirement, 38

names, 66, 68

network protocol support, 22

platform support, 22

RAM requirements, 31

reinstalling the Windows service, 74

resetting the Windows service, 73

running as a Windows service, 71

shutting down, 68

starting, 63

starting the Windows service, 72

stopping the Windows service, 72

system requirements, 22

uninstalling, 81, 84

uninstalling the Windows service, 73

Administration Server Windows service

reinstalling, 74

resetting, 73

starting, 72

stopping, 72

uninstalling, 73

verifying, 71

Administration Services

connecting to, 66, 68

described, 9

exiting, 68

installing, 41

logging in, 66 to 67

order of installation, 37

starting, 62


upgrading from previous releases, 84

Administration Services Console

closing, 68

compatibility with Administration Server, 34

described, 9

disk space requirements, 22

logging in again after session timeout, 69

platform support, 22, 29

RAM requirements, 31 to 32

starting, 65



Administration Services. See Analytic Administration Services

AIX

C++ Runtime requirement, 33

installing on, 42

setting environment before installation, 37

starting Administration Server, 63

118 Index B


Analytic Administration Services. See Administration Services

Analytic Deployment Servers. See Analytic High Availability Server

Analytic High Availability Server

adding to Administration Services Console, 11

deploying with Administration Services, 11

files installed, 44

release compatibility, 34

Analytic Servers

adding to Enterprise View, 77

connecting to, 62

disconnecting from, 68

installation order, 37


removing from Enterprise View, 77

ARBORPATH environment variable

Administration Server requirement, 63

dependencies, 37

architecture, 10

automatic service, running Administration Server as, 71

automating installation, 50

Bbackground process

MySQL, 44

background process (UNIX)

running Administration Server as, 64

backing up user information, 78

BEA WebLogic. See WebLogic application server

browser support, documentation, 45

Business Rules

described, 12

files installed, 44

installation overview, 12

setting up users, 77

CCD, launching installers from, 42

client tier, 9

closing Administration Services, 68

code pages, setting the ESSLANG variable, 49

common components installed, 46

COMMON directory, 46

compatibility

Administration Server and Console, 34

with Analytic Server releases, 33

with High Availability Server releases, 34

with Smart View Provider releases, 34

configuration guidelines, 40

Configuration Utility

application server deployment, 57

custom tasks, 52

database configuration, 55

database password, changing, 56

database user rights, 52

described, 52

launching, 53

log file, 60

order of tasks, 53

prerequisites, 52

reconfiguration, 60

Shared Services deregistration, 59

task list, 52

troubleshooting, 60

upgrades and, 53

connecting to

Administration Services, 66, 68

Analytic Servers, 62

console mode, launching UNIX installers, 42

Ddatabase, mid-tier. See MySQL

DB2 database

database naming requirements, 89

manual configuration, 89

port, 89

UTF-8 requirement, 37

versions supported, 28

defaults

password, 66, 68

username, 66, 68

deleting Administration Services, 81

deployment scenarios and guidelines, 38

directories

HYPERION_HOME/common, 46

in AASPATH, 44

spaces in install directory, 43

disk space requirements

Index E 119



Administration Services Console, 22

doc_launcher.htm, 45

documentation

browser support, 45

deploying with application server, 45

installed, 45

downloading installers, 42

EEAS. See Administration Services

EAS. See Analytic Administration Services

EASPATH. See also AASPATH environment variable

environment, setting on UNIX, 37

ESSLANG variable

Administration Server requirement, 38

described, 49

exiting Administration Services, 68

Fforeign language support, 49

Hhardware requirements



UNIX, 25

hardware requirements for UNIX, 25

hardware requirements for Windows, 23

HBR. See Business Rules

HP-UX

installing on, 42



Hyperion Business Rules. See Business Rules

Hyperion Download Center

launching the installer from, 42

Hyperion Home

location and files installed, 46

Hyperion License Server, 15

Hyperion security platform. See security platform

HYPERION_HOME directory, 46

HYPERION_HOME environment variable

detecting on UNIX, 37

IIBM DB2. See DB2 database

IBM WebSphere. See WebSphere application server

information map, accessing, 45

installation

instructions, 42

preparing, 21

prerequisites, 37

requirements, 37

scenarios, 38

installed documentation, 45

installers

launching on Windows, 42

JJava Runtime Environment (JRE) requirements. See Java

requirements

JDBC, changing the password, 91

JDK requirements. See Java requirements

JRun application server

manual deployment to, 93

prerequisite, 37

supported versions, 28

Llaunch files for Administration Server

UNIX, 64

Windows, 63

launching

documentation map, 45

installers, 42

on UNIX, 42

User Setup Wizard, 77

License Server, 15

Linux

installing on, 42


LOCALE directory, 49

logging in to Administration Services, 66 to 67

Mmachine requirements



120 Index N


Macromedia JRun. See JRun application server

mail server, setting up outgoing, 78

MBCS support, 49

memory requirements


Administration Services Console, 31 to 32

Microsoft SQL Server. See SQL Server

middle tier, 9

migrating

Administration Services software, 84

users from 6.5.3 or 7.0, 84

MySQL, 44

restarting, 70

stopping, 70

version supported, 28

Windows service, 44

Nname of Administration Server, 66, 68

network protocol support, 22

nohup (UNIX), 64

OOLAP Server. See Analytic Server

Oracle database



outgoing mail server, setting up, 78

outline editing, effect on server configuration, 40

outline memory



Ppassword

for admin account, 66, 68

for JDBC, 91

physical memory requirements, 22

Administration Services Console, 31 to 32

platform requirements

UNIX, 25

platform support, 22, 29

ports

IBM DB2 database, 89

Oracle database port, 88

SQL Server database, 90

POSIX Kernel Threads, 25

preparing for installation, 21

prerequisites to installation, 37

processing threads, 31

Program Files directory, installing to, 43

RRAM requirements, 22

RDBMS. See relational databases

reinstalling the Administration Server Windows service, 74

relational databases

manual configuration of, 87

supported, 28

release compatibility

Administration Server and Console, 34

with Analytic Server, 33

with High Availability Server, 34

with Smart View Provider, 34

removing Administration Services, 81

requirements

Administration Services, 23


Analytic High Availability Services, 24

Analytic Services Smart View Provider, 24

Smart View client, 24

requirements, system, 37

resetting the Administration Server Windows service, 73

resolution (screen), recommended, 24

restarting MySQL, 70

restoring user information, 78

running Administration Server as a Windows service, 71

Sscreen resolution, recommended, 24

security, backing up, 78

server names, 66, 68

session timeout, 69

setting up

an SMTP server, 78

users, 77

shortcuts on Start menu, 44

silent installation, 50

Smart View Provider

Index T 121



SMTP server, setting up, 78

software requirements

UNIX, 27

Windows, 27

software requirements, verifying, 27

Solaris

installing on, 42



spaces, in install directory name, 43

SQL Server database


port, 90

uppercase naming requirement, 90


start files for Administration Server

UNIX, 63 to 64

starting



MySQL, 70

the Administration Server Windows service, 72

User Setup Wizard, 77

stop scripts for Administration Server

UNIX, 70

Windows, 69

stopping

Administration Services, 68

MySQL, 70

the Administration Server Windows service, 72

support matrix

Analytic Server releases, 33

High Availability Server releases, 34

platform support, 22

Smart View Provider releases, 34

system requirements



UNIX servers, 25

Tthird-party products, 10

configuring, 93

thread type, 25

threads, Administration Server, 31

timeout for session, 69

Uuninstalling Administration Services, 81, 84

uninstalling the Administration Server Windows service, 73

UNIX

installing on, 42

launching installers, 42




UNIX servers


upgrading Administration Services, 84

user name for admin account, 66, 68

User Setup Wizard, launching, 77

users

adding, 77

backing up, 78

migrating from 6.5.3 or 7.0, 84

Vverifying

requirements, 27

WWebLogic application server


prerequisite, 37


WebSphere application server


prerequisite, 37


Windows

installing on, 42

Start menu, 44


Windows service

running Administration Server as, 71

running MySQL as, 44

122 Index X

XXWindows, launching installers in, 42

ESSBASE® ADMINISTRATION SERVICES - Oracle...Administration Services Introduction 9Administration...

Documents

Transcript of ESSBASE® ADMINISTRATION SERVICES - Oracle...Administration Services Introduction 9Administration...