HYPERION SYSTEM 9 BI+™ - Oracle€¦ · This chapter presents an overview of Hyperion System 9...

H Y P E R I O N ® S Y S T E M ™ 9 B I + ™

APPLICATION BUILDER J2EE™

R E L E A S E 9 . 2

G E T T I N G S T A R T E D G U I D E

Copyright 1998-2006 Hyperion Solutions Corporation. All rights reserved.

“Hyperion,” the Hyperion “H” logo, and Hyperion’s product names are trademarks of Hyperion. References to other companies and their products use trademarks owned by the respective companies and are for reference purpose only.

No portion hereof may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying, recording, or information storage and retrieval systems, for any purpose other than the recipient’s personal use, without the express written permission of Hyperion.

The information contained herein is subject to change without notice. Hyperion shall not be liable for errors contained herein or consequential damages in connection with the furnishing, performance, or use hereof.

Any Hyperion software described herein is licensed exclusively subject to the conditions set forth in the Hyperion license agreement.

Use, duplication or disclosure by the U.S. Government is subject to restrictions set forth in the applicable Hyperion license agreement and as provided in DFARS 227.7202-1(a) and 227.7202-3(a) (1995), DFARS 252.227-7013(c)(1)(ii) (Oct 1988), FAR 12.212(a) (1995), FAR 52.227-19, or FAR 52.227-14, as applicable.

Hyperion Solutions Corporation 5450 Great America Parkway Santa Clara, California 95054

Printed in the U.S.A.

Contents iii

Contents

CHAPTER 1 What is Application Builder? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Application Builder Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Client Tier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Application Tier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Data Tier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

ADM Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

WAA Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

J2EE Usage with Application Builder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

CHAPTER 2 Using Application Builder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Configuring Data Sources and Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Accessing Apache Tomcat and MySQL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Accessing the Launch Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Using Applications Provided with Application Builder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Using the Sample Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Using the Administration Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Accessing the Learning Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Accessing Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Accessing the Tutorials . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Accessing the Sample Pages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Accessing the Test Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

CHAPTER 3 Building Web Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Quick Builder and Dreamweaver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Configuring a Dreamweaver Site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Installing the Quick Builder Extensions for Dreamweaver . . . . . . . . . . . . . . . . . . . . . . . . . 29

Uninstalling Quick Builder Extensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Building Web Applications with Dreamweaver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Manually Building Web Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Setting up the Development Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Creating a New Project for Web Applications Using Ant . . . . . . . . . . . . . . . . . . . . . . . . . . 59

iv Contents

Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

What is Application Builder? 5

C h a p t e r

1What is Application Builder?

This chapter presents an overview of Hyperion System 9 BI+ Application Builder J2EE, describing its components and how they work together.

Application Builder is a Java-based tool used by developers to create custom business analysis applications for business users. Application Builder is a highly flexible, scalable enterprise solution built on a Java 2 Enterprise Edition (J2EE) foundation. It provides the requisite framework to construct Web-based analysis applications quickly. Using this infrastructure, developers can focus on the unique aspects of their custom business analysis solutions, and they can create application-specific displays and other specialized functionality.

Application Builder implements comprehensive APIs, components, services, a repository, alerts, and scheduling. Application Builder also includes the integration of Quick Builder, in which Application Builder components are presented using an interface provided by Macromedia® Dreamweaver MX.

Application Builder includes the following components:

● Web Application Architecture (WAA)

● Analytic Data Model (ADM)

● Administration Tools

Each component plays a key role in building applications. A solid understanding of the underlying concepts will enable you to build applications with ease.

6 What is Application Builder?

Application Builder ArchitectureThe architecture of Application Builder includes Analytic Data Model, Web Application Architecture, and the Sample Application.

Figure 1 Application Builder Architecture

Client TierYou perform the following tasks from the client tier:

● Use a Web browser to access a Application Builder application.

● Use Quick Builder to build an application within an IDE using tags from the Application Builder tag library.

Application TierThe application tier contains a Web server and a J2EE application server that manages Application Builder applications. The following components are on the Application Builder application tier:

ADM Architecture 7

● ADM, which is the Java Application Programming Interface (API) that provides generic access to OLAP data sources

● WAA, which consists of Java Server Pages (JSPs), servlets, tag libraries, JavaBeans, JavaScript, cascading style sheets, and applets

● Macromedia Dreamweaver MX, which is a professional HTML editor for designing, coding, and developing Web sites, Web pages, and Web applications.

Data TierThe data tier consists of OLAP data sources and a relational data source. The relational data source is used in the following ways:

● To query and view relational data

● To drill from summarized and calculated data stored in your OLAP data source to detailed data stored in a relational data source

● As an ATF repository that stores internal secured objects; for example, OLAP and relational views.

ADM ArchitectureThe following list describes the ADM components:

● ADM pooling, which defines the data sources and ADM pools that efficiently create and manage connections to the data source. Data source security is implemented with the ADM pools.

● ADM, which is a generic, object-oriented, OLAP database interface that accesses different OLAP data sources

● ADM drivers, which access the data source and map the data source’s characteristics to the generalized ADM model

The following figure shows the ADM architecture:


Figure 2 ADM Architecture

WAA ArchitectureApplication Builder's WAA is a set of Java Beans, JSPs, tag libraries, servlets, cascading style sheets, applets, and miscellaneous supporting elements that can be combined in a variety of ways to create Web-based analytic applications quickly.

Figure 3 Web Application Architecture

ADM Drivers

OLAPData Source

ADM Pooling(optional)ADM

AnalyticDataModel

RDBMS1

Utility Packages

OLAP RelationalCore

OLAP RelationalCore RDBMS

TagsWeb Packages

RDBMS

OLAP1 OLAP2

TagsTags

Web ApplicationArchitecture

Applications(Servlets, JSPs)

RDBMS2

RDBMS

RDBMS

Reports Analyzer

Reports Analyzer

J2EE Usage with Application Builder 9

WAA components are as follows:

● ADM, which is accessed by the OLAP domain of WAA. ADM provides access and connection pooling to OLAP data sources.

● JDBC, which is accessed by the relational domain of WAA. JDBC provides access to relational data sources.

● Utility packages, which contain components that handle low-level functions. For example, utility components perform processing for events, the repository, data queries, and error handling.

● Web packages, which contain components that handle Web application- specific functions. For example, in the Application Builder Sample Application, Web components handle user flow and events between the various JSPs.

● Tag libraries, which consist of a number of tags for using specific components or sub-components. Tag libraries enable you to use simple XML syntax on the JSP to instantiate and configure components, enabling development with limited or no knowledge of Java.

● The utility packages, Web packages, and tag libraries, which are placed into one of the following subpackages, relevant to their components:

❍ The OLAP subpackage. This subpackage contains components or tags designed to facilitate typical analysis tasks, such as building and saving queries, displaying members and data, and implementing drill-through functionality.

❍ The Core subpackage. This subpackage contains components or tags for the basic framework of the architecture as well as general purpose, reusable components. The Relational and OLAP Domains extend the core components.

❍ The Relational subpackage. This subpackage contains components or tags designed to create SQL queries against relational data sources, facilitate drill-through from an OLAP cube to a relational data source, and provide the functionality to edit and run an SQL query.

● Applications created by assembling WAA and ADM components into JSPs.

J2EE Usage with Application BuilderWAA is designed to work with J2EE-compatible application servers. The key enabling technologies that WAA relies on include servlets, JSPs, and JavaBeans.

The following figure illustrates the multitier environment typical of J2EE and implemented by Application Builder.

Note: In Figure 4, the circled specifications are used directly by Application Builder.


Figure 4 J2EE Model

The following table describes the key J2EE features utilized by Application Builder:

Table 1 J2EE Features Utilized by Application Builder

Technology Description

JDBC Provides access to relational databases. WAA can use any of several leading database servers, and can be customized to support others.

JDBC Standard Extensions Enables the hosting J2EE-compliant application server to perform connection pooling, authentication, and transaction coordination on behalf of WAA.

JavaBeans Most of WAA's functionality is implemented in Java classes that follow the standard JavaBean patterns.

J2EE Usage with Application Builder 11

JSPs Most of WAAs display activities are implemented using JSPs. Application Builder is written using the Model View Controller (MVC), and Java Beans is the mode.

Servlets Used specifically for the WAA controller servlet and as the back end for the Grid-Chart applet.

Java Naming and Directory Interface (JNDI) Used to access JDBC Standard Extension-compliant connection factories.

Applet Optionally, provides greater user interactivity with client-side Java code.

J2EE Security Used to secure access to the application.

Technology Description

Using Application Builder 13

C h a p t e r

2Using Application Builder

This chapter describes how to use Application Builder. It covers the following topics:

● “Before You Begin” on page 14

● “Using Applications Provided with Application Builder” on page 15

● “Accessing the Learning Tools” on page 18

14 Using Application Builder

Before You BeginIn order to use the Sample Application sample pages, tutorials, and test application, you must use the Typical installation option, which performs the following setup tasks:

1 Installs MySQL with sample data into HABDrill.

2 Installs Apache Tomcat.

3 Deploys all HAB applications to Apache Tomcat and sets up default application user IDs, passwords, and roles.

4 Creates the ATF repository in MySQL called HAB and initializes it.

5 Gives you access to a Launch Page that contains links to all HAB functionality.

Configuring Data Sources and UsersBefore starting Application Builder, you must configure your data source and set up user IDs, passwords, and roles.

You must perform the following configuration tasks:

6 Load sample data in the Essbase databases for Demo Basic and Sample Basic.

7 Set up Essbase ID and Password.

8 Add the following user IDs and passwords to the Essbase OLAP server:

Table 2 Essbase User IDs and Passwords

Optional: If you are using the Essbase Deployment Server (EDS) add the same users.

Accessing Apache Tomcat and MySQLYou need to start Apache Tomcat and MySQL to run Application Builder. MySQL is started as a service. Apache Tomcat is started using the batch file hab_startup.bat.

➤ To start Apache Tomcat and MySQL, perform one of the following:

● Select Start > Programs > Hyperion Solutions > Application Builder > Start Tomcat.

● Navigate to the following file and click it:

<HAB Install Directory>\ApplicationBuilder\7.0.0\ hab_startup.bat where HAB Install Directory is the directory where Application Builder is installed.

Essbase servers User ID Password Permissions

administrator password All Access

analyst password Read/Write

viewer password Read Only

Using Applications Provided with Application Builder 15

Accessing the Launch PageThe Launch Page contains links to all Application Builder components and Learning Tools.

➤ To access the Launch Page:

1. Start Apache Tomcat by selecting Start > Programs > Hyperion Solutions > Application Builder > Start Tomcat.

2. Open the Launch Page in one of these ways:

● If you used the Typical installation option, click Start > Programs > Hyperion Solutions > Application Builder > Launch Page.

● If you did not use the Typical installation option, enter the following URL in your Web browser:

http://hostname:port/hab-samples/samplePages/ launchPage.html

where hostname:port is the computer name or IP address and port of the application. If you installed Application Builder on your computer, the hostname is localhost. If you use Apache Tomcat, the port is 8080.

Using Applications Provided with Application BuilderApplication Builder provides you with the following enterprise archive files that contain applications you can use to review the functionality of Application Builder:

● hab-samples - Contains Application Builder samples that you can use to review the basic

functionality of Application Builder. The hab-samples application includes the following components:

❍ The Sample Application, which is built using a Model-View-Controller design and custom Java code.

❍ The sample pages, which demonstrate JSP tag functionality

❍ The Launch Page, which contains links to documentation, code samples, and other information

❍ The tutorials, which provide step-by-step instructions to build JSPs

❍ Default XML files, which include default values for J2EE security, ATF repository, and ADM pooling. These XML files are used to run the applications deployed with the Typical Installation option.

For Sample Application information, see “Using the Sample Application” on page 17.

● hab-admin - Contains the Application Builder Administration Tools which provide the

following functionality for applications built with HAB:

❍ Edit Member - The Edit Member tool adds, deletes, or modifies dimension members from a browser and saves them to the OLAP data source.

❍ Repository Objects - Access views to OLAP data sources, and SQL queries to relational data sources. You can also create tasks, alerts and schedule them.


❍ XML Setup - The ability to configure XML files used to communicate data between the application and Application Builder. There are five separate setups that affect seven XML files.

❍ Conversion - provides a means by which an application that is storing data in the Application Builder release 3.0 ATF repository can convert the repository into a Application Builder release 7.0 repository. The data is pulled into the new repository and the old repository is not accessible to the Administration Tools.

❍ Security - The security tool provides all of the authorization data on users, which includes group management, role selection, and user management stored in the repository.

❍ Manage Model - Registers Application Builder with Shared Services and registers a server and URL which enable guided analysis functionality.

For Administration Tools Application information, see “Using the Administration Tools” on page 17.

● hab-docs - Contains all the documentation and Javadocs. The Information Map provides

centralized access to the Application Builder documentation set with links to:

❍ Application Builder on-line guides

❍ Application Builder Javadoc

❍ Third party software documentation for third party tools installed with Application Builder

❍ Links to Hyperion Solutions resources, such as technical support and Hyperion Partners

For Documentation information, see “Accessing Documentation” on page 18.

● hab-test - Contains sample JSPs and java code for advanced users. This application demonstrates the use of JSP tags and how to integrate them into existing client code and frameworks. By using the components, the application shows what is customizable, without having to extend from the classes to alter behavior and appearance. The Test Application also shows how to process input to and output from the WAA components. For information on the Test Application, see “Accessing the Test Application” on page 19

● hab-blank - Contains the WAA framework, minimal deployment information, and default XML files which include default values for J2EE security, ATF repository, and ADM pooling. You can use this to begin building custom applications for demonstration or test purposes.

● template project - Contains the WAA framework and blank XML files with no default values. The AntBuild.bat file provides a Create option to copy the template project into a new project. This creates a skeleton project, where you can begin building a custom application with no default values set. For information on creating an application using Ant, see “Creating a New Project for Web Applications Using Ant” on page 59.

If you installed Application Builder with the Typical installation option, the applications are automatically deployed into Apache Tomcat. The installer extracts the EAR files and copies them to the Apache Tomcat install directory.

Using Applications Provided with Application Builder 17

Using the Sample ApplicationYou can use the Sample Application to review the basic functionality of Application Builder. Examples of functionality:

● The Administration Guide describes how to deploy the sample Application into an application server

● The Sample Application XML files define default roles, User Ids, and web.xml files for CSS, ATF repository, and ADM pooling.

● Sample Application XML files are used in Administration Tools

➤ To access the Sample Application:

1 If necessary, start Apache Tomcat, MySQL, and Hyperion System 9 BI+ Essbase Analytics.

2 Open the Sample Application in one of the following ways:

● If you used the Typical installation type, select Start > Programs > Hyperion Solutions > Application Builder > Launch Page, then click Sample Application.

● If you did not use the Typical installation type, type the following URL in your Web browser:

http://hostname:port/hab-samples/SMPApplicationServlet

where hostname:port is the computer name or IP address and port of the Web application.If you installed Application Builder on your computer, the hostname is localhost. If you are using Apache Tomcat, the port is 8080.

3 Press Enter. The server logon screen is displayed.

4 Enter the username and password either as analyst and password or as viewer and password.

5 Click OK.

Using the Administration ToolsApplication Builder Administration Tools are designed to assist with the administration of custom applications.

➤ To access the Administration Tools:

1 If necessary, start the Web server, the Essbase OLAP Server, and Essbase Deployment Services.

2 Open the Administration Tools in one of the following ways:

● If you used the Typical Installation, click Start > Programs > Hyperion Solutions > Application Builder > Launch Page. Click Administration Tools.

● Log on to the Administration Tools by typing the following URL in your Web browser:

http://hostname:port/hab-admin/ADMINApplicationServlet


where hostname:port is the computer name or IP address and port of the Administration Tools. If you installed Application Builder on your computer, the hostname is localhost. If you are using Apache Tomcat, the port is 8080.

Note: User name and the password are Administrator and password.

Accessing the Learning ToolsThis section includes the following topics, which describe how to access the available tools to learn Application Builder:

● “Accessing Documentation” on page 18

● “Accessing the Tutorials” on page 18

● “Accessing the Sample Pages” on page 19

● “Accessing the Test Application” on page 19

Accessing DocumentationThe Information Map provides centralized access to the Application Builder documentation set.

➤ To access the Information Map:

1 If necessary, start the application server, relational data source server, and OLAP server.

2 Open the Information Map in one of the following ways:

● From the Start menu, select Programs > Hyperion Solutions > Application Builder > Launch Page, then in the Information Map section, click Information Map.

● Type the following URL in your Web browser:

http://hostname:port/hab-docs/docs/information_map_HAB.htm

where hostname:port is the computer name or IP address and port of the Web application. If you installed Application Builder on your computer, the hostname is localhost. If you are using Apache Tomcat, the port is 8080.

● Navigate to <HAB Install Directory>\ ApplicationBuilder\<release number>\docs\information_map_ HAB.htm where <HAB Install Directory> is the location where Application Builder is installed.

Accessing the TutorialsThe online tutorials help you get started using Application Builder. The tutorials contain step-by-step instructions for creating pages that perform various functions.

Accessing the Learning Tools 19

➤ To access the tutorials, take one of the following steps:

● Select Start > Programs > Hyperion Solutions > Application Builder > Launch Page and then click Tutorials.


http://hostname:port/hab-samples/samplePages/ Tutorials/html


Accessing the Sample PagesThe sample pages demonstrate how to use various features of Application Builder. You use the code from these samples to implement similar features in your applications. They include examples of the following features:

● Implementation of traffic lighting and data formatting by iterating across cube views

● Passing events between Application Builder components

● Demonstrations of how tag attributes affect the appearance of visible components

➤ To access the sample pages, do one of the following:

● From the Start menu, select Start > Programs > Hyperion Solutions > Application Builder > Sample Pages.


http://hostname:port/hab-samples/samplePages/ samplepages.html


Accessing the Test ApplicationThe test application demonstrates the use of WAA components and how to integrate them into existing client code and frameworks. By using the components, the application shows what is customizable, without having to extend from the classes to alter behavior and appearance. The Test Application also shows how to process input to and output from the WAA components.

Note: The Test Application does not have a central servlet framework, therefore you need to manage it more closely.

➤ To access the Test Application:

1 If necessary, start the Web server, MySQL, and the Essbase OLAP Server.


2 Open the Testing Application by typing the following URL in your Web browser:

http://hostname:port/hab-test/

where hostname:port is the computer name or IP address and port of the Test Application. If you installed Application Builder on your computer, the hostname is localhost. If you are using Apache Tomcat, the port is 8080.

Note: The username and password are analyst and password.

Building Web Applications 21

C h a p t e r

3Building Web Applications

This chapter describes the procedures needed to use Quick Builder with Dreamweaver MX 6.1 with Extension Manager 1.5.x or 1.6 when developing a Application Builder Web application. It includes the following topics:

● “Quick Builder and Dreamweaver” on page 22

● “Manually Building Web Applications” on page 58

22 Building Web Applications

Quick Builder and DreamweaverApplication Builder enables you to use tag libraries from within the Macromedia® Dreamweaver® environment. This ability is provided by a component called Quick Builder. You may use tag libraries in any HTML authoring tool; however, the integration of Quick Builder provided in this release is specific to Dreamweaver.

Configuring a Dreamweaver SiteA Dreamweaver site is a directory on your local computer that contains all the files for your application. These files may then be copied to your Web server for deployment.

You can use a wizard to configure a site. The following example uses the Apache Tomcat version 4.1.18 application server running on Windows. If your application server is running on a UNIX platform, you must use either FTP or Samba to connect to your testing server.

➤ To configure the Dreamweaver site:

1 Create a directory on your local disk drive. This should not be in the application server’s Application Builder deployment directory.

2 Start Dreamweaver, and from the main menu select Site > New Site.

3 Enter a site name, then click Next.

Note: To configure your site manually, select the Advanced tab and see “Installing the Quick Builder Extensions for Dreamweaver” on page 29 for further instructions.

Quick Builder and Dreamweaver 23

4 Select the Yes option, select JSP server technology, and click Next.


5 Select an editing option, enter the directory name that you created in step 1, and click Next.


6 Specify your testing server, which is the location where you want to test your files, and click Next.

The following example uses a Local /Network server and the <HAB Install Directory>\Jakarta-Tomcat-4.1.8\new project\ location where <HAB Install Directory> is the directory where you installed Application Builder.


7 Enter the URL for the root of your site.

8 Optional: Click the Test URL button to ensure that the URL is correct. Your application server must be running.

9 Click Next.


10 Select a check-in and check-out option, then click Next.

11 Review the summary of your new site, then click Done.


12 To edit the settings for your new site, select the Advanced tab and select a category to edit.

Assuming that the application server is running, you should now be able to run a simple JSP file from Dreamweaver.

13 To test this whether you can run a JSP from Dreamweaver, enter the word Test into the current document and then press

14 Preview the page in your Web browser by clicking F12.

The Web browser should display a page similar to the following page:

15 Close the Web browser window.

Note: In general, you should close the Web browser when not previewing changes, because it tends to cache pages without being prompted.


Installing the Quick Builder Extensions for DreamweaverAn extension is a piece of software that you add to an application to enhance the application’s capabilities. Application Builder offers two extensions, which the following table describes:

➤ To install the Quick Builder extensions in Dreamweaver:

1 Take one of the following actions:

● If you have previously installed Quick Builder extensions, uninstall them. For instructions, see “Uninstalling Quick Builder Extensions” on page 29.

● If you have not installed Dreamweaver, install it on the local computer and run the Application Builder installer using either of these Application Builder installation options:

❍ Typical Installation

❍ HTML Developer

2 Open the Dreamweaver Extension Manager in one of the following ways:

● From the Start menu, select Macromedia > Dreamweaver Extension Manager.

● From the Dreamweaver menu bar, select Commands > Manage Extensions.

3 From the Macromedia Extension Manager window, select File > Install Extension.

4 Navigate to the Dreamweaver MX directory; for example, <HAB Install Directory> \ApplicationBuilder\7.0.0\tools\DreamweaverMX,where <HAB Install Directory> is the directory where you installed Application Builder.

5 Navigate to the directory for the language that you want to use.

6 Select the HYSL_HAB.mxp file and click Install.

7 From the licensing window, click Accept to continue the installation.

8 Restart Dreamweaver when prompted.

Uninstalling Quick Builder ExtensionsBefore installing Quick Builder extensions for Dreamweaver, you must remove any previous Quick Builder installations.

Extension Description

HYSL_HAB.mxp Contains tags to build JSPs in Application Builder.

HYSL_HYA.mxp Contains tags to build JSPs in Hyperion System 9 BI+ Web Analysis. The Application Builder Dreamweaver integration with Web Analysis enables you to build a Web Analysis HTML Web client default report using the Analyzer HTML Web client tags within Dreamweaver. It also enables you to use Application Builder tags in your Web Analysis HTML Web client default report.


➤ To uninstall the Quick Builder integration from Dreamweaver:

1 Open the Dreamweaver Extension Manager in one of the following ways:

● From the Start menu, select the Macromedia > Dreamweaver Extension Manager.

● From the Dreamweaver menu bar, select Commands > Manage Extensions.

2 Select the Application Builder extension that you want to uninstall.

3 Click the Delete toolbar button.

4 Restart Dreamweaver.

Building Web Applications with DreamweaverThis section describes how to use Quick Builder to develop Web-based applications. It assumes you have a working knowledge of Dreamweaver and are familiar with OLAP concepts and terminology.

Quick Builder automates the process of using tags in a graphical IDE. Quick Builder is integrated with Macromedia® Dreamweaver® MX.

The Quick Builder components are available within Dreamweaver as standard Dreamweaver components. You can use the components individually within Dreamweaver by dragging them from the Application frame to the Document window or by selecting them from the Insert drop-down menu. You can also insert functional groups of components by running one or more of the Quick Builder wizards from the Command drop-down menu.

➤ To build a Web application with Dreamweaver:

1 If necessary, start the application server, relational data source server, and OLAP data source server.

Tip: You can start Apache Tomcat and MySQL from the Application Builder Start menu. Select Start > Programs > Hyperion Solutions > Application Builder > Start Tomcat.

2 Configure Dreamweaver to use Quick Builder, if necessary. For instructions, see “Configuring a Dreamweaver Site” on page 22.

3 Use Quick Builder to the drag components to a JSP:

● If you are a JSP Developer, use tag libraries to create JSPs.

● If you are a Java Developer, create new tags using Java code or modify existing tags. For more information, see the Web Application Architecture Developer’s Guide.


Quick Builder Components Available Within DreamweaverThe components available within Dreamweaver are grouped according to their general functionality. Access them either from the object palette under the appropriate Application Builder object palette or from the Insert menu. All of the Quick Builder components are described in the Hyperion System 9 BI+ Application Builder J2EE JSP Technical Reference Guide. You can use the index to look up the Quick Builder component name or the tag name.

Each Quick Builder component corresponds to a tag; when you insert a component in a JSP, you are actually inserting a tag and its attributes. You can access the following tags from the Insert > HAB Components menu in Dreamweaver:

● Foundation Tags - For getting and setting beans and iterating over them. Foundation tags also include tags for general purposes.

● OLAP Tags - For accessing an OLAP data source

● Relational Tags - For accessing a relational data source

● Universal Result Set Tags - For the Universal Result Set

● Product Integration Tags - For Web Analysis and Hyperion System 9 BI+ Financial Reporting integration

In addition to individual components, Quick Builder has a number of wizards that enable you to assemble functional component groups quickly. You can access the following wizards from the Commands menu in Dreamweaver:

You can insert Quick Builder components from Dreamweaver using the Application frame or the Insert menu, or by running one or more Quick Builder wizards from the Commands menu.

Inserting Components from the Dreamweaver Application FrameQuick Builder components are available from the Application frame. You use the Components tabs within the Application frame. All Quick Builder components consist of tag names and attributes.

➤ To use components from the Application frame:

1 Navigate to the Application frame.

Table 3 Quick Builder Wizards Available in Dreamweaver

Wizard Description

Insert HAB Page Template Inserts the HTML code required for a new page, including the import statements, taglib URIs, and the components Application Context, Application Session, Page Bean, Head Bean, Form Bean, and an HTML Form tag.

HAB OLAP Component Wizards Helps you insert all the OLAP components into the current page.

HAB Relational Component Wizards Helps you insert all the relational components into the current page.


2 Select the Components tab.

3 From the pull-down list, select HAB Components.

4 Expand the frame that you want to use, then drag an icon to the code view or design view.

Figure 5 Quick Builder Components

A dialog box is displayed that asks you to enter values for that tag’s attributes. Quick Builder automatically inserts the HTML code required to use this component, based on the values that you enter for the attributes (or on their default values.) Figure 6 shows a typical dialog for this purpose:

Figure 6 Quick Builder Component Dialog Box

MutuallyExclusiveAttributes


The area on the left lists the attribute groups for the component; the indentation indicates that the attributes are mutually exclusive. In this example, you define either a pooled connection or a direct connection but not both. The dialog box displays each attribute setting with a default value, enabling you to enter your own values.

Note: When you enter the ID or scope for an existing component, Quick Builder does not verify that your entry is correct, because it may have been defined on a different page, or it may be created in the future.

5 Enter the information requested in each of the dialog boxes that follow.

Tip: You can use the Tag Info for online help.

6 Click OK to save the values or Cancel to abort adding the component.

If you omit an attribute that is required, use an invalid attribute value, or use a scriptlet in an attribute that only accepts text, Quick Builder displays an error message whenever a frame is changed or you click OK. The error message is given once but is not updated or repeated unless an attribute value is changed.

Inserting Components from the Insert MenuThe components that are available from the Application frame are also available from the Insert menu.

➤ To insert a Quick Builder component:

1 Select the Insert > HAB Components option from the Dreamweaver menu bar.

2 Select a Application Builder component group to display the components available in that group.

3 Select a component to insert it in the document window where the cursor is located.

Editing ComponentsYou can edit components on your JSP from the code view or design view.

➤ To edit components after you have saved them:

1 Click the icon representing the component in design view, or click the tag in the code view.

2 Take one of the following actions:

● Click in the code view and select the Edit Tag option.

● From the code view or design view, click the Show Editor button on the Dreamweaver Property Sheet editor. The component’s dialog is displayed, enabling you to make updates.


Using Quick Builder WizardsQuick Builder provides several wizards to assist you in building a JSP.

➤ To use a wizard:

1 Select the Commands > HAB Tools from the Dreamweaver menu bar.

2 Select one of the Quick Builder wizards.

Page Creation with Wizards

Using a Quick Builder wizard is the fastest way to create a page. You can build the remainder of the page one component at a time or using additional wizards.

The Quick Builder wizard, Insert HAB Page Template, creates a standard page structure with components that all applications require:

● Application Context, to set available options for the application in general

● Application Session, to specify options for the current user’s session

In addition, some pages require the following components:

● Head Bean, to control page header components

● Page Bean, to define options for the current page

● Form Bean, to handle submission requests from the components

Note: You can also build this structure one component at a time using either the Application frame or the Insert menu.

The Form Bean is placed between the HTML <form> and </form> tags. In general, most other Quick Builder components are placed between the Form Bean components opening and closing tags.

Components that generate HTML code need to be inside the form. When you place a component on a page, the corresponding tag appears in the code view. All tags that end with the word Bean generate HTML code.

The remaining wizards walk you through each step required to build a completely functional page.

Creating a View List Page Using a WizardThe following procedure is an example of creating a view list page with a wizard. It builds a single page that displays a list of OLAP views stored in an ATF repository. To view the page in a Web browser, you must have the following prerequisites:

● A running OLAP server and database

● A running SQL database containing the ATF repository


● A running application server with hab-blank.ear deployed and copied into your custom project.

For prerequisite setup information, see “Building Web Applications with Dreamweaver” on page 30.

➤ To create a JSP in your Web browser:

1 Open Dreamweaver and select the site that you want to use.

2 To start a blank page, select File > New.

3 For the Category, select Dynamic and for Dynamic Page, select .JSP.

4 Select Commands > HAB Tools > Insert HAB Page Template.

The following information is displayed in the design view:

This view shows the components for the Head Bean and Form Bean. The Form Bean component has been automatically inserted into a form element (denoted by the dotted lines). Selecting View > Head Content makes the icon for the head component visible.

5 Position the cursor after the two Form Bean icons and select Commands > HAB Tools > HAB OLAP Component Wizards > Insert OLAP View List.

The following dialog box is displayed:


Note: The ATF repository stores the views that will be displayed in the view list. In this example, an ATF repository has not yet been defined an ATF repository, so New Repository is selected. This gives it an ID (“repository”) and the JNDI name of the database being used for the ATF repository, as defined in the application server. In this example, the ATF repository name is HAB.

6 Click Next.

7 Select any filtering information that you want to apply to the list of views, then click Next. Filtering restricts the views listed based on a schema, a cube, or a manual setting for the server, driver, schema, cube, and username.


8 Enter an ID to use for the View List component.

Note: Be sure the values that you use for the Form Bean ID matches the ID used when the Form Bean was created, the default is shown. The IDs of all components must be unique across your application (unless their context is Servlet); when you use the ID of a previously inserted component, you must match the case sensitive ID and the scope exactly.


9 Click Finish.

10 To preview the page in your Web browser, press F12.

11 On the Logon screen, enter the User ID and Password as analyst and password, respectively, then click OK.

Note: The view list may be empty if you do not have view data loaded.

Creating a Page Using Components You can create pages by clicking an area in the design view, then dragging to this area the component that you want to add. It is advisable to begin the page by using the Insert HAB Page Template wizard, which sets up the page context for you. The following procedure inserts a Member Tree component, which lists the members of a dimension; this component is not available with a wizard. To determine the required components, refer to the useMemberTree tag in the Hyperion System 9 BI+ Application Builder J2EE JSP Technical Reference Guide. The Member Tree component requires an OLAP schema, a means of connecting to it, a cube, and a dimension.

➤ To create a page using components:

1 From Dreamweaver, start a new page.

2 Select Commands > HAB Tools > Insert HAB Page Template. Place the cursor at the end of the Form Bean icons.

3 Connect to a schema using either a data source pool or a direct connection. For example, from the main menu, select Insert > HAB Components > OLAP Tags > data Access > Data Source Pool Manager.

The following screen is displayed:


Note: This example assumes that you have a data source configuration file named WAADataSources.xml in the root of your application server. For information about the data source configuration file, see the Hyperion System 9 BI+ Application Builder J2EE Windows System Administrator's Guide.

4 Click XML Configuration File and type /WAADataSources.xml.

5 Accept all other defaults and click OK.

6 From the Design view, position the cursor inside the HTML form tag after the Form Bean icon, then drag the OLAP Schema component from the Application frame.

The OLAP schema dialog box is displayed.

7 Accept the defaults and click OK.

8 Expand Connection Settings and click Pooled Connection. On the OLAP Schema - Pooled Connection screen, enter the following required data and then click OK:

Data Source ID - Open the WAADataSources.xml file and search for <Id>, where Id is the name of your data source. For example

<Id>LocalHost Essbase Demo</Id>

Copy and paste in between the Id line for the Data Source ID. For example,

LocalHost Essbase Demo

Pool Name - Type HAB_Analyst

Roles - Type False


9 From the Design view, position your cursor inside the HTML form and after the OLAP Schema icon, and drag the OLAP Tag > Data Access > Cube component from the Application frame. The following screen is displayed:

10 Click Cube and enter Basic and then, to accept all other defaults, click OK.

11 From the Application frame, drag the Dimension component.


12 Click Dimension and enter Year and then, to accept all other defaults, click OK.

13 From the Application frame, under the Component Bean Tags, drag the Member Tree component.



14 To accept the defaults, click OK.

The Design view window is displayed:

15 Press F12 to preview the page in your Web browser. On the Logon screen, enter the User ID and Password as analyst and password, respectively, then click Logon.

The Member List screen is displayed:


Creating a Multiple-Page Application Tag

This example shows how to create two pages that communicate with each other, so that changes in one page are available to components in the other page. The example uses the View Builder and Grid components. The View Builder is created on the first page, enabling you to create a view; the Grid is created on another page and displays the results of running the view. Communication between the pages is implemented using the Connect Components component. The scopes of the relevant components are set to Session, making them available across pages in the application.

Note: Quick Builder provides two components for communicating between other components: Connect Components and Event Mapper. Connect Components requires no programming, but is limited to communication between Application Builder components. The Event Mapper requires programming at the scriptlet level (Java code embedded in a JSP). For more information, see the “Using Tags” chapter in the Hyperion System 9 BI+ Application Builder J2EE Web Application Architecture Developer’s Guide.

➤ To create a multiple-page application:

1 To open a new window and create a new page, Page1.jsp, select Commands > HAB Tools > Insert HAB Page Template.

2 Select Commands > HAB Tools > HAB OLAP Component Wizards > Insert OLAP View Builder.



3 Because a component has not yet been created, select Scratch, then Click Next.

Note: When some components already exist, you select the appropriate component with which to begin.



4 To connect to the OLAP application (schema), you can use a data source pool (defined in a WAADataSources.xml) or a direct connection. This example uses a data source pool. Select Data Source Pool and click Next.



Note: In this example, the data source configuration file WAADataSources.xml contains definitions of available data sources. This file is generally set up by an administrator. For more information, see the Hyperion System 9 BI+ Application Builder J2EE Administrator's Guide.

The data source pool has not yet been created, so New Manager is selected. If one had been created on the same page, it would be displayed as a default in the drop-down list under On-Page Manager.

5 Click Next.

The following screen is displayed, with the name of the OLAP database and pool name are displayed by default.


6 Click Next.

7 Enter an ID to use when referring to the OLAP database (cube) and the name of the OLAP cube.


8 Click Next.

The Insert an OLAP View Builder screen is displayed.

9 Enter the following information:

a. Enter an ID to use when referring to the cube view (which is an OLAP query).

b. To prevent the View Builder from opening with an existing query, select the No Query option.

c. To prevent any cube view query from being executed, ensure that the options selected for both Execute and Modify are Never.

Note: Because users will create their own views, leave the specifications for Expression Text and Expression File Name blank, as shown in the following figure:


10 Optional: If you want the View Builder to open with a default query:

a. Enter the query details:

❍ To create the query manually, select Use ADM Query, and enter the Expression Text.

❍ To load a text file containing the query, select Use ADM Query on server file, and enter the file name in the Expression File Name text box.

b. In the Expression Type text box, enter the expression type (ALE or XML).

c. Select one of the Execute options:

❍ Changed - Executes the query only if data in the cube has changed.

❍ Always - Executes the query every time.

Note: Executing the query every time can tax system resources.

d. Select one of the Modify options:

❍ Once - Loads the query only the first time the cube view is loaded.


❍ Always - Always reload the default query regardless of the query defined in the View Builder component.

11 Click Next.

The Insert an OLAP View Builder screen is displayed.

12 Enter an ID to use when referring to the View Builder component.

13 Click Next.


14 Select a repository option and then click Next:

a. If you want the user to be able to save the queries they create, select New Repository, and enter an ID to use when referring to the repository, and the ATF repository JNDI name.

b. If you want to define a repository for this page, select the Repository ID and what component it defines.

c. If you do not want the user to save queries, select No Repository.


15 Enter ID information and select a layout:

a. Enter an ID to use when referring to the View Builder component.

b. Enter the ID of the form bean within which it is nested.

c. Select either a Tabular layout, which orients the separate sections of the View Builder across and down the page, or a Stacked layout, which orients the separate sections of the View Builder component in a single column on the page.

16 To change the scope of the View Builder component:

a. Highlight the View Builder icon.

b. From the Property Editor dialog box, select Show Editor.

c. To make the View Builder component available to all other components in the session, change the scope from the default “RootServlet” to “Session.”

17 Connect the source component:

a. Position the cursor after the View Builder component.


b. From the HAB Components > Foundation Tags > Object Manipulation Tags, drag the Connect Components to the View Builder component.

c. Select Source from the left window. The following screen is displayed:

The component automatically scans the page to the point of insertion, looking for potential source components. It locates the View Builder component and displays that as the default. (Had it found more than one, they would be displayed in a drop-down list.)

18 Change the scope to Session.

19 Connect the target component:

a. Select the Target component attribute group from the left frame. An automatic scan for potential target components finds none (because none has yet been created).

b. To make the View Builder component available to all other components in the session, select Grid as the Target Bean Id, and Session as the Target Bean Scope, then click OK.

20 To add a link to a Page2.jsp:

a. Position the cursor below the HTML form tag area.

b. Type View the Grid and highlight what you typed.

c. Select Modify > Make Link, and type Page2.jsp as the link target.

Page2.jsp is created next.

d. Save the file as Page1.jsp.

The following icons are displayed in the design view:


➤ To create Page2.jsp:

1 To open a new window and create a new page, Page2.jsp, select Commands > HAB Tools > Insert HAB Page Template.

2 To change the scope of the component:

a. Position your cursor after the Form bean icon.

b. From the HAB OLAP Components, expand Component Bean Tags, and drag the Grid component.


3 To allow the component to communicate with other components in the session, change the scope from the default Servlet to Session.

4 Click OLAP View and verify that the IDs and scopes of the Cube View components are the Same source and Target as those defined on Page1.jsp. For example, Source is ViewList and Target is Grid.

5 Click OK.

6 Save the file as Page2.jsp.

7 Post both files to the application deployment area either by copying them there or using the Dreamweaver Post command from the Site window.

Note: Although you can preview Page1.jsp in the normal way, you cannot link to Page2.jsp unless it is in the deployment area, because Dreamweaver creates the temp preview file in that directory.

8 Open your Web browser and enter the URL; for example:

http://localhost:8080/hab-blank/Page1.jsp

9 Preview Page1.jsp in the Web browser:


10 Create a view and click view the grid.

The grid is displayed:

Adding a Application Builder Component to an Existing Page

The following procedure takes an existing HTML page and adds a useDataSourceTreeBean tag to it using the Insert OLAP View List wizard. The Data Source Tree displays the data sources defined in the data sources configuration file. For more information about the data source configuration file, see the Hyperion System 9 BI+ Application Builder J2EE Administrator's Guide.


➤ To add a component to an existing page:

1 Open an existing HTML page in Dreamweaver:

2 Position the cursor on the page where you want to insert the component and select Commands > HAB Tools > Insert HAB Page Template. This places a Form Bean icon inside the form tag.

3 Position the cursor inside the form, after the Form Bean icon.

4 Add the data source:

a. From the Components tab, open OLAP Tags.

b. Under Data Access, drag the Data Source Pool Manager icon to the Form Bean.

c. Under Component Bean Tags, drag the Data Source Tree icon to the Form Bean.

d. Accept the default values. If your data source XML file is different, specify it correctly:

5 Save the HTML file as a JSP.

6 Press F12 to preview the JSP in the Web browser.


Cascading Style SheetsThe colors, fonts, backgrounds, and general appearance of pages created using Quick Builder are determined by a cascading style sheet located in the application deployment directory, under /html/waa/web/WAAApplication.css. This style sheet is designed so that you can add your own style classes by adding a prefix to the new styles and specifying that prefix in the component property sheet dialogs. You can use a different default style sheet for your application by specifying it in the Application Context component attribute CSS URI.

The style classes defined in the default style sheet are all prefixed with the word “default.” When a JSP is run, this style sheet is loaded by Javascript commands in the WAAApplication.js file. If no value is entered in the property sheet for CSS Class Prefix, it uses this default prefix when loading styles. If a value is entered, it looks for style classes prefixed by that value. In the following procedure, you create a style class that overrides the one used to represent alternating rows in a list (tr.defaultTableOddRow) by using the prefix “myStyles” rather than “default.”

Creating and Using a Style You can add a new style class by editing the style sheet using Dreamweaver’s style sheet editor. The following procedure changes the way alternate rows in a list are displayed by creating a variant of the tr.defaultTableOddRow class and adding a prefix to it.

➤ To create a style:

1 From the Dreamweaver Site window, open the View List page.

2 Select File > Open and browse to the <HAB Install Dir>\webapps\hab-samples\html\waa\web directory of your application deployment area and open WAAApplication.css.

3 Select Text > CSS Styles > Edit Style Sheet and scroll to the tr.defaultListOddRow class:


Note: Application Builder uses the style class tr.defaultListOddRow to define the background color of alternating rows in a list. The class definition is displayed at the bottom of the dialog; the background is defined here as #DDDDDD, which is a hex value for a light bluish color. This procedure adds a new class to display the background in red (#FF0000). It uses a new style prefix, “myStyle” to replace the prefix “default”. This new prefix can be used in the CSS prefix text box of the View List component or any other component that specifies a CSS prefix text box.

4 Click Duplicate, select the tr.MyStyleListOddRow class, change the name to tr.MyStyleListOddRow, and click OK.

5 Click the Edit button.

The Editor dialog box is displayed.

6 Select Background from the Category list, and change the background color to Red.


7 To save the new class, click OK.

8 In the Dreamweaver document window, highlight the View List component and click Show Editor.

9 In the CSS Class Prefix edit box, type the prefix myStyle.

10 Click Apply and Close.

11 Press F12 to preview the page in the Web browser.


The alternating rows now are displayed with a red background. The CSS Class Prefix attribute is specific to components that generate HTML code, and it enables components on the same page to have different styles. Because it is theoretically possible for Page Bean and Head Bean components to generate HTML code, these components also contain the CSS Class Prefix attributes, but they are not commonly used.

Manually Building Web ApplicationsThis section describes the procedures to build a Application Builder Web application. It includes the following topics:

● “Setting up the Development Environment” on page 58

● “Creating a New Project for Web Applications Using Ant” on page 59

Setting up the Development EnvironmentTo build a working Web application, ensure that the following prerequisites are set up:

● Application Builder deployed and running on an application server. The server need not be localhost, but you must be able to write into the deployed directory for Application Builder

● A running OLAP server and database with data and an administrative user and password with Administrator access. The ATF repository must be defined in the web.xml file

● A running SQL database containing the ATF repository and an administrative user and password with owner privileges

● OLAP and relational data sources defined in the WAADataSources.xml file

If you want a visual design environment, install Dreamweaver MX.

Manually Building Web Applications 59

Note: Without Dreamweaver, you enter the code for your JSP files.

Creating a New Project for Web Applications Using AntThis section describes the process of how to use Ant to create a new project for a custom application that you intend to use in a production environment. The template project should never be modified and should only be copied using the AntBuild.xml file, which replaces values in files with user input.

Note: The following procedure is written for Windows. To create a new project in a UNIX environment, substitute the BAT files for SH files. For example, change AntBuid.bat to AntBuild.sh.

In the following procedure, you create a new project using the AntBuid.bat file, which makes a copy of the <HAB Install Directory>\waa\ projects\template directory. You build your custom application in the new project. The new project is created in the <HAB Install Directory> \WAA\projects directory.

➤ To create a new project using the template project:

1 Ensure that the following variables are defined:

❍ JAVA_HOME = <directory where you installed JDK>

❍ ANT_HOME = <directory where you installed ANT>

2 Change directories to <HAB_Install_Dir>.

3 At a command prompt, type the following command:

set_hab_env waa

The set_hab_env command sets up the following directories:

● HAB_HOME =<directory where you installed Hyperion Application Builder>

● ADM_HOME = <directory where you installed ADM>

● ANT_HOME = <directory where you installed ANT>

4 Navigate to the following directory:

<HAB Install Directory>\WAA\projects

5 To build a new project based on template, at the command prompt, enter the following command:

AntBuild Create

6 When prompted, enter your new project’s short name, long name, and description.

The project is created in the <HAB Install Directory> \WAA\projects directory.


7 Change directories to <HAB Install Directory>\WAA\ projects\<new project>\source where new project is the name of the project that you created.

8 Enter the following command:

AntBuild.bat [target],

where [target] equals one or more of the following variables:

● Clean - Cleans the EAR file, WAR file and documentation.

● Build - Builds the EAR file, WAR file and documentation.

● BuildEAR - Builds the EAR file and WAR file.

● BuildWAR - Builds the WAR file.

● BuildDocs - Builds the documentation.

● BuildTlds - Builds the TLDs.

● BuildTagChangeLog - Builds a log of tag changes between major versions.

● BuildDWMX - Builds the DWMX extension for this project.

● BuildTagExtInfo - Synchronizes the DWMX file with the source.

● FixCRLF - Changes carriage-return/line-feeds for the platform, converts leading spaces to tabs, and trims trailing white space..

Glossary 61

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

Glossary

ad hoc report An online analytical query created on-the-

fly by an end user.

ADM Client Interfaces Exposes public client interfaces,

which are available for use by the developer to access a data

source.

ADM Pooling Enables users to share a connection to a

data source. ADM pooling also controls the security to

your data source.

Administration Tools A set of tools to assist with the

administration of applications created with Application

Builder.

ALE Analytic Language for Expression. A language-based

representation used to specify queries within the Analytic

Data Model (ADM).

ALE query Retrieves member information and data cells

from a data source using the Analytic Data Model. For

example, you can specify both member and data cell

queries using one of the following query representations:

Analytic Language for Expression (ALE);Extensible Mark-

up language (XML), which is an ADMML.dtd compliant

XML text; or an Expression Tree.

Analysis Tools Framework (ATF) repository Stores

secured object information for users, groups, folders,

views, task definitions, scheduled task definitions, and

permissions. It also includes a cron scheduling utility that

schedules and runs tasks.

Analytic Data Model (ADM) A generic, object-oriented

interface that accesses different OLAP data sources. The

ADM developed by Hyperion is used in several Hyperion

products, such as Hyperion Reports, Application Builder,

and Hyperion Financial Management.

annotation Text data that is stored for OLAP data or

relational data. There are two kinds of annotations: data

source and WAA. A data source annotation is assigned to

an OLAP data cell and can be either a Essbase Analytic

Services linked reporting object (LRO) or a Hyperion

Financial Management cell text. A WAA annotation is set

up using an XML file, and it can be assigned to an OLAP

cell, Olap view, relational row, or relational view. A WAA

annotation is text, a URL, or a file.

annotation repository Stores annotation information for

views and cell data. It also stores WAA drill-through

mapping information for a WAA drill-through.

ANT A Java-based build tool, part of the Jakarta project

from Apache. ANT users create XML-based build files that

describe their project build processes.

API See also Application Programming Interface (API).

applet In Java, a program that can run in a Web browser.

Small programs written in languages other than Java are

sometimes referred to as applets.

application A related set of dimensions and dimension

members that are used to meet a specific set of analytical

or reporting requirements.

Application Programming Interface (API) A library of

functions that you can use in a custom program. Provides

programmatic access to an application’s data or services.

Application Builder provides a Java API that you can use to

develop client programs.

application server A middle-tier server that is used to

deploy and run Web-based application processes.

authentication Verification of identity as a security

measure. Authentication is typically based on a user ID

and password. Passwords and digital signatures are forms

of authentication.

62 Glossary


bean A reusable component, or building block, that can

be combined with other components in the same or other

computers in a distributed network to form an

application.

calc script A set of commands that define how a database

is consolidated or aggregated. A calculation script may also

contain commands that specify allocation and other

calculation rules separate from the consolidation process.

cell A unit of data representing the intersection of

dimensions in a multidimensional database; the

intersection of a row and a column in a worksheet.

chart Charts are graphical representations of the data

retrieved from a specified grid. Examples of chart types

are bar, line, and pie.

child A member that has a parent above it in the database

outline.

class A template definition of the methods and variables

in a particular kind of object. The class defines all of the

common properties of the different objects that belong to

it. See also object.

column A vertical display of information in a grid or

table. A column can contain data from a single field,

derived data from a calculation, or textual information.

The terms column and field are sometimes used

interchangeably. Contrast with row.

component A module of program functionality that has

defined inputs, processes, and outputs, and that, when

incorporated into a larger program or system, provides

application functionality. The basic building block of both

Hyperion Analytic Application Framework and the

Analytic Applications. Hyperion Analytic Application

Framework Components include: Application-Server

Components, Common Application Components,

Custom Application Components, Snap-in Components,

Client Sub-Components. Analytic Application

components include: Application Component Classes and

Application Components (AC Instances).

composite objects A pattern in the ADM design which

describes the relationship between child objects and the

parent objects that contain them.

cube A block of data that contains three or more

dimensions. Multidimensional cubes are better suited for

complex data analyses than for relational databases

because relational databases are limited to two dimensions.

A Essbase Analytic Services database consists of miniature

cubes that make up a larger cube, or hypercube.

cube view An object that contains the XML

representation of an OLAP data query and partial results

of the query.

data The values (monetary or non-monetary) associated

with the query intersection.

data cell query The extraction of one or more values from

a multi-dimensional data source. For example, the

CubeView query navigates from the metadata to the data

cells.

data load The process of populating an Essbase Analytic

Services database with data. Loading data establishes

actual values for the cells defined by the structural outline

of the database.

data query The extraction of one or more values from a

multi-dimensional data source. A data query utilizes the

cube view object to return data cell values and data cell

attributes. It also enables access to member names and

usage of a data cell object for data persistence.

data source A storage area containing data that is available

to the user. A data source may be a multidimensional

database, a relational database, or a file.

data source annotation An annotation assigned to a

OLAP data cell. It can be either a Essbase Analytic Services

linked reporting object (LRO) or a Hyperion Financial

Management cell text.

data source drill-through A Essbase Analytic Services or

Essbase Integration Server (EIS) drill-through or a

Hyperion Financial Management drill-through line item

detail (DTLID).

data source XML file The XML file that specifies OLAP

data sources, Analytic Data Model pools, and relational

data sources. For example, the waadatasources.xml

file is the data source XML file used in the Sample

Application.

Glossary 63


database A collection of related information. Each unit

(record) of the database is typically organized in a fixed

format to make it easy to retrieve selected portions of the

data on demand. Each record is made up of one or more

data fields, and each data field can hold one piece of data

(known as a value).

database administrator (DBA) An individual who

administers database servers, such as Essbase Analytic

Services, and who may also design, maintain, and create

databases.

DB2 Database 2. A IBM-proprietary relational database

product, providing an open database environment that

runs on a wide variety of computing platforms.

DBA See also database administrator (DBA).

dimension A data category that is used to organize

business data for retrieval and preservation of values. Each

dimension usually contains a hierarchy of related members

grouped within it. For example, a Year dimension often

includes members for each time period, such as quarters

and months. Other common business dimensions may be

measures, natural accounts, products, and markets.

drill-through The navigation from a data value in one

cube to corresponding data in another data source. For

example, you can access context-sensitive transactional

data. Drill-through occurs usually from the lowest point of

atomicity in a database (detail) to a next level of detail in

an external data source.

drill-through XML file Contains information required to

map from an OLAP cube’s data cell to a SQL query to

retrieve detailed consolidation information. For example,

the WAADrillThrough.xml file is the drill-through XML

file used in the Sample Application.

DTD file A document type definition file. Defines the

type of elements, attributes, and entities in an associated

XML document.

Dynamic Time Series A process that is used to perform

dynamic period-to-date reporting for all values associated

with a query.

dynamic time series functions Hidden outline members

that provide period-to-date reporting at up to eight levels,

such as year-to-date and month-to-date totals. An

administrator assigns Dynamic Time Series members to

members of the time-based dimension in your database

outline.

EAR file An enterprise archive file used to distribute J2EE

Web applications. Contains WAR files, JAR files, and

deployment information.

edge A component of an OLAP cube. Valid edges include

Row, Column, Page, and Slicer. For example, if a report

has Product and Sales on the columns and Region on the

rows, then the Row edge contains Product and Sales and

the column edge contains Region.

Enterprise Beans Server-side components that

encapsulate the business logic of an application.

execute A command that runs a specified Calc script

object against a OLAP result set. In most cases, a Calc

script object represents a file containing Calc script

commands.

export A means by which a user can direct the output of

data or the results of a query.

expression tree query An object-based representation and

manipulation of Analytic Language for Expression queries.

This is ideal for interactive query building.

Extensible Markup Language (XML) A language

comprised of a set of tags used to assign attributes to data

that can be interpreted between applications based on the

schema used.

external authentication The practice of storing user logon

credentials in a corporate authentication repository (such

as Lightweight Directory Access Protocol, or LDAP,

directory) as an alternative to maintaining users and

groups for each Hyperion product.

fact table A container for one or more relational tables

that define the data values for each dimension intersection

in the OLAP model. For example, if the OLAP model

contains Products, Region, and Year dimensions, the fact

table might include data values for the number of units of

Product A sold in New York in January.

filter functions Filter functions filter the set of objects

returned by execution of the query. The following member

filter functions are implemented by all Analytic Data

Model drivers: AllMembers, Children, Descendents,

Member, SystemMemberList, and TopOfHierarchy.

folder An object in the ATF repository used as a storage

container for other objects such as views, queries, or other

folders.

64 Glossary


generation A layer in a hierarchical tree structure that

defines member relationships in a database. For example,

Essbase Analytic Services orders generations incrementally

from the dimension (generation 1) down to the child

members.

grid A report object that can contain data from external

data sources. A grid contains a row, column, and

(optionally) a page axis.

guided analysis. Functionality that links and launches reports and views from one Hyperion product to another. Users can easily navigate from any Application Builder report to related financial reports (rendered in Hyperion Reports), unstructured content (using Hyperion Central) and interactive out-of-the-box analysis (rendered in Hyperion Analyzer).

hab-blank.ear file An enterprise archive file that contains

the WAA framework and minimal deployment

information to create a new web application.

hab-samples.ear file An enterprise archive file that

contains the WAA framework, deployment information,

and customized code for the Sample Application.

hierarchy A set of multidimensional relationships in an

outline, often created in a tree formation. For example,

parents, children, and generations represent a hierarchy.

Hypertext Markup Language (HTML) The programming

language used to generate Web pages on the World Wide

Web.

icon A graphical representation of an object or concept

that invokes an application or program. desktop shortcut

instantiate To create a single occurrence of an object

based upon its class.

invisible tags A tag which may or may not produce

invisible HTML elements on a Web page, as well as

processing server-side requests.

J2EE A framework for developing and deploying

enterprise applications. The J2EE platform consists of a set

of services, application programming interfaces (APIs),

and protocols that provide the functionality for developing

multitiered Web-based applications.

J2EE roles Used to implement ADM pooling. A J2EE role

assigned to J2EE users in your application server.

J2EE users J2EE application users that are assigned to

roles in your application server to access your Application

Builder application.

JAR file A Java archive file. A platform-independent file

format that permits many files to be aggregated into one

file.

Java Database Connectivity (JDBC) A Java API in the

J2EE framework that enables Java programs to execute

SQL statements. This allows Java programs to interact with

any SQL-compliant database supporting JDBC. JDBC

makes it possible to write a single database application that

can run on different platforms and interact with different

RDBMSs.

Java developer A person who is competent in Java

programming, specifically the Java 2.0 Standard Edition as

well as the Java 2.0 Enterprise Edition.

Java Development Kit (JDK) A software development kit

from JavaSoft used to produce Java programs, containing

the software and tools that developers need to compile,

debug, and run applets and applications.

Java Naming and Directory Interface (JNDI) A standard

extension to the Java platform, providing Java technology-

enabled applications with a unified interface to multiple

naming and directory services in the enterprise. It enables

seamless connectivity to heterogeneous enterprise naming

and directory services. It also enables developers to build

powerful and portable directory-enabled applications

using this industry standard.

Java Server Pages (JSP) Technology for controlling the

content and appearance of web pages through the use of

servlets.

Java Virtual Machine (JVM) Technology that enables the

Java 2 platform to host applications on any computer or

operating system without rewriting or recompiling. The

JVM is also responsible for the compactness of

applications targeting the Java 2 platform, and is the

foundation of its security capabilities.

JavaBeans Reusable software components written in the

Java programming language. You write JavaBeans just as

you write any other Java class. You can also take existing

components, applets, or Java classes and turn them into

JavaBeans.

Glossary 65


JDBC Pooling Database connectivity where a JDBC data

source is created and configured for connection pooling

with a relational database. The JDBC data source

efficiently creates and manages connections to a relational

database.

JDBC-ODBC Bridge Driver A bridge is a device that

governs the flow of traffic between networks or network

segments and forwards packets between them. A driver is a

program that extends the operating system to support a

device such as a disk or tape drive; or a program that

enables an application to use a device such as a printer.

join Creates a relationship between two tables based on

matching key column values in relational databases and as

an SQL command.

JSP developer A person that is competent in Java server

page technology and has user knowledge of an OLAP or

relational data source.

key column In relational databases, a column or columns

that form a unique identifier for each row. For example,

EMPLOYEE_ID might be a key column.

leaf member A member that has no children.

log A system-maintained record of transactional data

resulting from actions and commands.

log file A system-maintained file that records

transactional data resulting from actions and commands.

For example, an application log file records user actions

that are performed on that application; a client log file

records client messages, actions, and errors.

member query Enables you to navigate from the metadata

to the data. A member query utilizes the MemberSelection

object to return member objects and hierarchy

relationship objects. It also enables access to member

properties. For example, the logical relationships between

dimension/member and hierarchy/hierarchy relation are

described in the MemberSelection query. So the

MemberSelection query can access a member. You can also

specify the level of the members that you want in the

MemberSelection query.

member selection An object that contains the XML

representation of an OLAP member query and the results

of the query.

metadata A set of data that defines and describes the

properties and attributes of the data stored in a database or

used by an application. Examples of metadata are

dimension names, member names, properties, time

periods, and security.

Microsoft Virtual Machine (VM) A self-contained

operating environment that facilitates the execution of Java

programs on a Microsoft operating system.

Model-View-Controller Model (MVC) Consists of a

controller servlet that dispatches requests to appropriate

Action classes provided by the application developer, JSP

custom tag libraries, and associated support in the

controller servlet. For example, this model assists

developers in creating interactive form-based applications,

and utility classes to support XML parsing, automatic

population of JavaBeans properties (based on the Java

reflection APIs), and internationalization of prompts and

messages.

multidimensional database (MDDB) A method of

organizing, storing, and referencing data through three or

more dimensions. An individual value is the intersection

of a point for a set of dimensions.

multithreading Within a single program, concurrent

handling of multiple, separately executable sequences of

program instructions.

named group An object that describes levels and

generations for dimensions. A level is a branch within a

dimension. The levels are numbered incrementally from

the leaf member (level 0) towards the root. For example, in

a Essbase Analytic Services Accounts dimension that

consists of general ledger accounts, all of the detail

accounts are Level 0 members. The accounts one level

higher are Level 1, their parents are Level 2, and so on. It

can happen that a parent has two or more children that are

different levels.

object A program component that is related to an

application or database. Objects can be outlines, rules files,

calculation scripts, report scripts, or data sources. They are

stored within the application or database subdirectory on

the server or client machine.

object factory Enables developers to derive objects from

Web Application Architecture classes and have the

architecture instantiate them transparently. This makes

application customization much easier.

66 Glossary


Object Management Group (OMG) A consortium that

created the Common Warehouse Metadata Initiative,

which defines a standard model for OLAP metadata to be

browsed and interchanged.

ODBC See Open Database Connectivity (ODBC).

OLAP See online analytical processing (OLAP).

online analytical processing (OLAP) A

multidimensional, multi-user, client-server computing

environment for users who need to analyze consolidated

enterprise data. OLAP systems feature functionality such

as drilling down, data pivoting, complex calculations,

trend analyses, and modeling.

Open Database Connectivity (ODBC) Standardized

application programming interface (API) technology that

allows applications to access multiple third-party

databases.

order of precedence A set of rules that determines the

order in which arithmetic operations take place in a

formula. Multiplication (*) and division (/) are performed

first (first tier operations), followed by addition (+) and

subtraction (-) (second tier operations). When there are

multiple operations involving the same tier, the operations

are performed from left to right. Use of parentheses alters

the normal order, with the operations contained within the

innermost parenthesis performed first.

outline The database structure of a multidimensional

database, including all dimensions, members, tags, types,

consolidations, and mathematical relationships. Data is

stored in the database according to the structure defined in

the outline.

page axis Enables you to set up views (pages) of selected

members, to organize the data in a data entry form into

smaller, logical groups. Each page on the page axis can

have members selected from one dimension or from

multiple dimensions. For example, you could set up one

page to enter data for Radio promotions and another page

to enter data for Web promotions.

parent A member that has an aggregated branch of

children below it.

permission A level of access users and groups can have for

managing data or other users and groups. Permissions can

be granted to users and groups explicitly or by means of

filters. Administrators can also set global minimum

permissions as settings for Essbase Analytic Services

applications and databases, so that all users can have at

least access to data specified by the minimum permission

setting for a particular scope. The scope of a permission

refers to the area of data it encompasses. The scope of a

permission can be the system, an application, or a

database.

point of view (POV) A unique set of dimension members

that defines specific intersections of data.

POV See point of view (POV).

query To request information from a data provider. For

example, queries are used to access a relational data source.

query functions A method to filter retrieved information

in a query language. Enables you to filter the set of objects

returned by execution of an OLAP query. For example, the

following member query functions are implemented by all

Analytic Data Model (ADM) drivers: AllMembers,

Children, Descendents, Member, SystemMemberList, and

TopOfHierarchy.

queryInfo An object that contains a SQL query and

partial results of the query.

Quick Builder Enables you to build applications within

Macromedia Dreamweaver. Tags from the Application

Builder tag library are represented by icons, menus, and

wizards. For example, a Web designer can build an

application graphically by dragging and dropping

Dreamweaver icons onto a Java server page.

Quick Builder component Reference tags, from the

Application Builder tag library, that are displayed as icons

within Dreamweaver.

RDBMS See relational database management system

(RDBMS).

related content. Information that is associated with OLAP or relational data such as a drill-through, annotation, or guided analysis link.

Glossary 67


relational data access component A component that can

be accessed within an application that enables you to view

the relational data that is associated with specific OLAP

members at the given cell.

relational database management system (RDBMS) A

database management system for accessing data in a

relational database and storing data in the form of related

tables. A RDBMS takes SQL statements entered by a user

or contained in an application program and creates,

updates, or provides access to the relational database.

repository group A parent object to repository users, or a

container for storing ATF repository users with the same

permissions.

repository user An individual who is registered in the ATF

repository.

role Used to define group privileges, and are granted to

users or groups of users in order to determine who can

perform the activities associated with the privileges. A user

may perform the activities only if he has been granted the

required role or if he is a member of a group that has been

granted the required role.

root member The highest member in a dimension

branch. See also leaf member.

row A horizontal display of information in a grid or table.

A row can contain data from a single field, derived data

from a calculation, or textual information. The words row

and record are sometimes used interchangeably. Contrast

with column.

schema In relational databases, a logical model that

represents the data and the relationships between the data.

schema definition Used to create objects and set their

properties. The objects you create correspond to your

metadata. For example, you create a dimension object for

each dimension in your data source.

servlet Small Java programs, or modules of Java code that

run in a server application. For example, an applet that

runs on a server, usually meaning a Java applet that runs

on a Web server.

sibling A child member at the same generation as another

child member and having the same immediate parent. For

example, the members Florida and New York are both

children of the member, East, and siblings of each other.

single sign-on The ability of an externally-authenticated

user to access multiple, linked Hyperion applications after

logging on to the first application. The user can launch

other applications from the first application (and from

other linked Hyperion applications) without logging on

again. The user’s ID and password are already

authenticated.

slicer The slicer edge can contain one or more

dimensions, but only one member can be specified for

each dimension. For example, if the member Actuals from

the Scenario dimension is on the slicer then the data in the

result set is all data that intersects the row, col, and page

members, and also has the scenario dimension set to

Actuals. The data omitted from this slice is any data

associated with the non-selected members of the Scenario

dimension, for example Budget, Variance, Forecast, etc.

special permission A group of predefined permissions

granted to users, groups, folders, views , or queries within

the repository. A special permission is a single bit, whereas

a permission is a combination of one or more special

permissions.

SQL See also Structured Query Language (SQL).

star schema A logical model that represents your

relational data in a form that mirrors that of OLAP data. A

star schema contains a fact table and one or more

dimension tables.

Structured Query Language (SQL) A computer language

used to access data in relational databases.

substitution variable A variable that acts as a global

placeholder for information that changes regularly. You set

the variable and a corresponding string value; the value

can then be changed at any time. Substitution variables can

be used in calculation scripts, report scripts, Essbase

Spreadsheet Services, and Essbase API.

table In relational databases, a form of data storage in

which data is stored in records comprised of fields. Each

record is defined by a unique, or primary, key.

tag A Java class that implements a specialized interface

enabling it to be used in a Java server page for processing.

68 Glossary


tag library A collection of custom tags which can be

imported for use in a JSP. Individual tags are grouped into

several tag libraries according to their functionality. A tag

library is similar to an XML document that contains

information about individual tags. For example, in

Application Builder, there is a relational tag library that

contains relational tags and an OLAP tag library that

contains OLAP tags.

thin driver A Java based driver that is inherently cross-

platform, because it is written exclusively in Java.

tool tip A tiny pop-up window that presents a short

description of a toolbar or picture button’s action. Tool

tips are dialogs that briefly describe or define a button’s

functionality.

top-level member A dimension member at the top of the

tree in a dimension outline hierarchy, or the first member

of the dimension in sort order if there is no hierarchical

relationship among dimension members. The top-level

member name is generally the same name as the

dimension name if a hierarchical relationship exists.

UDA A user-defined attribute. A UDA is a term associated

with members of an outline to describe a particular

characteristic of the members. Users can specify UDAs

within calculation scripts and reports so that they return

lists of members that have the specified UDA associated

with them. UDAs can be applied to dense as well as sparse

dimensions.

unary operator A group of mathematical indicators (+, -,

*, /, %) that define how roll-ups take place on the database

outline.

Uniform Resource Locator (URL) An address for a

resource located on the World Wide Web, such as a

document, image, downloadable file, service, or electronic

mailbox. URLs use a variety of naming schemes and access

methods, such as HTTP, FTP, and Internet mail. An

example of a URL is http://www.hyperion.com. A URL can

also point to a file located on a local or network drive, such

as file:///D:/essbase/docs/essdocs.htm.

union An SQL command that is a type of join that

combines the results of two SELECT statements. A union

is often used to merge lists of values contained in two

tables.

universal result set An object implementing the

IWAAGrid interface, enabling clients to access OLAP or

relational data in the same way. The advantage is that you

only need to create the JSP once to display both relational

and OLAP data. The Universal Result Set is also used to

generate output to various formats, for example PDF or

HTML. You can create a single JSP that can display either

relational and OLAP data in a grid.

URL See Uniform Resource Locator (URL).

User ID The key word that defines the user to the

authentication server, and the user to the external

authentication method. In some cases the User ID may be

a short “cryptic” id. In other situations the User ID may be

the users complete name.

view In relational databases, a logical table created by

combining columns from one or more tables. A view can

contain metadata and formatting information used to

query an OLAP data source.

visible tags A tag which produces visible HTML elements

on a Web page, as well as processing server-side requests.

WAA annotation Text, a URL, or a file. A WAA

annotation is set up using tags and it can be assigned to an

OLAP data cell or cubeView, and a relational row or

queryInfo.

WAA Core Domain Contains the basic framework for the

architecture, as well as general purpose, reusable

components. The relational and OLAP Domain extend the

core objects.

WAA drill-through Navigates from an OLAP data cell to

corresponding data in a relational data source.

WAA OLAP Domain Contains components designed to

facilitate typical analysis tasks, such as building and saving

queries, displaying members and data, drilldown, and so

on.

WAA Relational Domain Contains components designed

to facilitate SQL drill-through from an OLAP cube to the

relational database that was used to build the cube.

Functionality to edit and run an SQL query is also

provided.

WAA Utility Components Low level building blocks used

to perform processing for events, a repository, the

hashtable, and exceptions.

Glossary 69


WAA Web Components Handle functions specific to Web

applications. For example, Web components handle user

flow between the various JSPs. analysis tasks, such as

building and saving queries, displaying members and data,

drilldown, and so on.

WAR file A Web archive file. A WAR file contains the

complete directory structure and all files that define the

Web application. For example, Web applications are

typically distributed as WAR files.

Web Application Architecture (WAA) A set of Java beans,

Java server pages, servlets, applets, and miscellaneous

supporting elements that can be combined in a variety of

ways to quickly create Web-based analytic applications.

Web Application Architecture (WAA) provides tag

libraries and reusable components that implement from

50% - 80% of the functionality required for a typical

custom analytic application. The architecture is designed

with reuse and rapid development in mind.

web designer A person with HTML skills and user

knowledge of data sources.

web server A computer that delivers, or serves up, Web

pages.

XML query An ADM query formatted as an XML string.

For example, the tags defined in Application Builder are

used to define a member and data XML query.

70 Glossary

Index A 71


Index

AAnalytic Data Model (ADM) architecture, 7

Ant, create a new project with, 59

application tier, 6

architecture, Hyperion Application Builder, 6

Cclient tier, 6

component groups, inserting using wizards, 34

components

QuickBuilder, available within DreamWeaver, 31

core domain, 9

Ddata tier, 6

DreamWeaver

configuring for use with Quick Builder, 21

sites, configuring, 22

version, 22

Dreamweaver

components, 31

configuring for use with Quick Builder, 58

installing Quick Builder extension for, 29

Eexamples

adding a HAB component to an HTML page, 53

creating styles, 55

drag-and-drop page, creating, 38

multiple page application, creating, 42

view list page, creating, 34

Ggroups, component, inserting using wizards, 34

HHTML page example, 53

IInsert HAB Page Template wizard, 31

Insert Menu, inserting Quick Builder components from, 33

installation of Quick Builder extension for Dreamweaver, 29

Mmultiple page application, example, 42

Nnew project, using Ant, 59

OOLAP

domain, 9

Ppages

examples of creating

adding components, 53

building, 34

drag and drop, 38

multiple page, 42

styles, 55

HTML example, 53

72 Index Q


modifying the look and feel, 55

QQuick Builder

components available within DreamWeaver, 31

extension, installing, 29

Insert Menu, 33

using with Dreamweaver, 21, 58

wizards, 34

Quick Builder components available within, 31

Rrelational domain, 9

Ssite, DreamWeaver, 22

Ttiers, architecture, 6

Uutility components, 9

WWeb Applications

building, 21 to 30, 58

Web components, 9

wizards

examples, 34, 38, 42, 53, 55

wizards, Quick Builder, 34

HYPERION SYSTEM 9 BI+™ - Oracle€¦ · This chapter presents an overview of Hyperion System 9...

Documents

Transcript of HYPERION SYSTEM 9 BI+™ - Oracle€¦ · This chapter presents an overview of Hyperion System 9...