hyperion system 9 bi+ application builder j2ee release 9.2.0.1

Hyperion® System™ 9 BI+™ Application Builder J2EE™ Release 9.2.0.1 Readme

1


Readme File

This file contains the following sections:

Purpose....................................................................................................................... 1 Installation Updates.................................................................................................... 1 Support for WebSphere 6.1 ......................................................................................... 2 Considerations .......................................................................................................... 14 Installation Updates.................................................................................................. 17 Third-Party Products ................................................................................................. 19 Supported Platforms ................................................................................................. 20 Known Issues............................................................................................................ 21 Tips and Troubleshooting.......................................................................................... 24 Documentation Updates ............................................................................................ 24

Note: Any references in the documentation to the Hyperion Download Center pertain if your site has access.

Purpose

This document includes important, late-breaking information about this release of Hyperion® System™ 9 BI+™ Application Builder J2EE™. Review this information thoroughly before installing Application Builder J2EE.

Top

Installation Updates

The section includes important information about installing this release of Application Builder.

Required Environment Variables

To run or build the supplied applications with Application Builder J2EE, the following publicly available utilities must be installed:

• Jcrontab 1.4.1

• Trove4J 0.1.5

• FESI 1.1.8


2

To build applications, environment variables must be set:

• JCRONTAB_HOME

• TROVE4J_HOME

• FESI_HOME

See the Hyperion System 9 Application Builder J2EE Installation Guide for Windows or UNIX for more information.

Analytic Data Model Release 93

Application Builder J2EE 9.2.0.1 automatically installs Hyperion Analytic Data Model Release 9.3.

ADM SAP-BW BAPI Driver The ADM SAP-BW BAPI driver has been fully tested, but it has not been tested integrated with HAB. Hyperion does not support use of the ADM SAP-BW BAPI Driver with Application Builder J2EE at this time.

UNIX

It is recommended that all Hyperion applications be installed as the same user on UNIX platforms.

All Hyperion products install common third-party and internal components under HYPERION_HOME. To ensure that installers have the permissions required for modifying the HYPERION_HOME location on UNIX platforms, it is recommended that all Hyperion applications be installed under the same HYPERION user account.

Deprecated Functionality

The following functionality has been removed:

• Support for Hyperion Analyzer tags has been removed, so this release will not work with Hyperion System 9 BI+ Web Analysis. However, this release will work with Analyzer Release 7.2 and earlier.

• Support for Hyperion Reports tags has been removed, so this release will not work with Hyperion System 9 BI+ Financial Reporting™. However, this release will work with Reports Release 7.2 and earlier.

Top

Support for WebSphere 6.1

This section describes setting up HAB with WebSphere 6.1.

Important: Hyperion does not support 64-bit WebSphere.

Note: On Solaris, the LD_LIBRARY_PATH and ARBORPATH variables must be set up in the operating environment from which the WebSphere server is started.


Note: WebSphere 6.1 may run in headless mode by default on UNIX, causing charts to not render. To correct this, access Application Servers > [server name] > Process Definition > Java Virtual Machine and add "-Djava.awt.headless=false" to the JVM startup arguments.

Setting Up Security

To set up security:

1. Access the WebSphere Administrative Console by opening a browser and entering the following URL: https://<hostname>:9043/admin

2. On the login screen, enter an administrator user ID and click OK. Note: If you do not have security enabled, you my skip this step.

3. In the navigator, select Security > Secure administration, applications, and infrastructure.

4. On the Configure tab, do the following:

a. Under Administrative security, select Enable administrative security. Default: Off

b. Under Application security, select Enable application security. Default: Off

c. Under Java 2 security, deselect Use Java 2 to restrict application access to local .

d. Under User account repository, in Available realm definitions, select and option and click Configure.

Note: For options on configuring the WebSphere user account repository according to the instructions in the WebSphere documentation.

3


e. In Primary administrative user name, enter the name of the administrator user and click OK.

f. Under User account repository, click Set as current.

g. Click Apply.

Configuring the Shared ADM Instance

Note: Add the shared ADM instance to the server classloader. See Adding Libraries to a Classloader.

To configure the shared ADM instance:

1. After enabling security, access the WebSphere administrator utility.

2. On the login screen, log on as the administrator user set up in security. Click OK.

3. In the navigator, select Environment > Shared Libraries.

4. In Scope, select Cell= and click New.

5. In Name, enter a name for the ADM instance.

6. In Classpath, enter the classpath information. For example: C:\ApplicationBuilder\9.2.0.1\lib

4


C:\ApplicationBuilder\9.2.0.1\lib\HabAdm931.jar C:\ApplicationBuilder\9.2.0.1\lib\HabHubClient9201.jar C:\ApplicationBuilder\9.2.0.1\lib\HabJaxm111.jar C:\Hyperion\common\loggers\Log4j\1.2.8\log4j-1.2.8.jar C:\Hyperion\common\CSS\3.0.1\lib\css-3_0_1.jar C:\Hyperion\common\XML\JDOM\0.8.0\jdom.jar C:\Hyperion\common\XML\JAXP\1.2.2\xsltc.jar

7. In Native library path, enter the paths to ADM and Analytic Services. For example: C:\Hyperion\AnalyticServices\api\redist C:\Hyperion\Common\ADM\9.3.1\Essbase\bin Note: You must add the native libraries to the native search path for your operating system: Windows: PATH Solaris: LD_LIBRARY_PATH and ARBORPATH AIX: LIBPATH HP-UX: SHLIB_PATH

8. Click OK.

Creating and Configuring a WebSphere JDBC Data Source and Driver

To create a JDBC data source:

1. If you are not already logged on, access the WebSphere administrator utility, and log on as the administrator user set up in security.

5


2. In the navigator, select Environment > WebSphere Variables:

3. Under Name, click on the database driver type for your implementation and configure any variables related to your RDBMS. For example, if you are using DB2, click DB2UNIVERSAL_JDBC_DRIVER_PATH. Then, under Variable, enter the filepath to the JDBC driver and click OK:

4. In the navigator, select Resource > JDBC > JDBC Providers:

5. In Scope, select the scope for the node and server for the connection.

6


6. Click New:

7. In Database type, select the database platform.

8. In Name, enter a name.

9. Click OK.

10. In the navigator, select Resource > JDBC > Data Sources:

11. In Scope, select the scope for the node and server for the connection.

7


12. Click New:

13. If this is the first time you have run this wizard, click Create new J2C authentication alias:

a. Click New:

b. In Alias, enter a name.

8


c. In User ID, enter the user ID to access the data source.

d. In Password, enter the password.

e. Click OK.

f. Click Save.

14. For subsequent data sources:

a. In Data source name, enter the name of the data source.

b. In JNDI name, enter the naming service.

15. Click OK.

Deploying Applications

To deploy applications:


2. In the navigator, select Applications > Install New Application:

3. In Local file system or Remote file system, click Browse and select the.WAR file.

4. In Context root, enter the base URL.

9


5. Click Next:

6. On Select installation options, leave the defaults and click Next:

7. Select the module.

8. Click Next:

9. Under Specify authentication methods, select Use default method, and select the J2C authentication method used to connect to the database.

10


10. Under the Select column, select the module.

11. Under the Target Resource JNDI Name column, select the name.

12. Click Next:

13. On Map Virtual hosts for Web modules, select the module and click Next.

14. Review summary:

15. Click Finish.

16. Click Save.

17. Stop WebSphere.

18.Copy the following files: trove.jar Jcrontab-1.4.1.jar fesi.jar to the following location in the newly-deployed application directory, which located under the installedApps directory of the server profile by default:

11


WEB-INF/lib and add them to the following files: WEB-INF/classes/repository.xml WEB-INF/classes/WAADataSources.xml Instructions for editing the repository.xml and WAADataSources.xml can be found in the Hyperion System 9 BI+ Application Builder J2EE Installation Guide.

19. Restart WebSphere.

Adding Users and Groups Using Roles

To add users or groups using roles:


2. In the navigator, select Applications > Enterprise Applications > <name>:

3. Select Security role to user/group:

12


4. Under Select, select a role.

5. Click Look up users or Look up group:

6. Click Search.

7. Under Available, select users or groups and click .

8. Click OK.

9. Click Save.

Adding Libraries to a Classloader

To libraries to a classloader:


2. In the navigator, select Applications > Enterprise Applications > <application name>.

3. Select Java and Process Management > Class loaders.

4. Click New to create a new classloader.

5. Click on the name of the new classloader.

6. Select Shared Library References.

7. Add a reference to the ADM shared library defined in Configuring the Shared ADM Instance.

8. Restart WebSphere.

Top

13


14

Considerations

Application Builder J2EE is fully tested to ensure high quality; however, some issues remain. The following sections describe the known issues in Application Builder J2EE.

General

• Automatic deployment to WebSphere is not supported.

• Automatic deployment to UNIX is not supported.

• HDP1.2(Hyperion Directory Protocol1.2)

If Hyperion Reports server supports HDP1.2, Hyperion Reports guided analysis does not work unless the alias mapping for Hyperion Reports server is defined at WAAGuidedAnalysis.properties located at WEB-INF/classes. Even though the alias is an optional feature, it must be defined for Reports server if it supports HDP1.2.

• In the Application Builder J2EE applications and sample pages, all usernames and passwords are case-sensitive.

• You must use a date format in queries, filters, and substitution variables that are appropriate to the relational database management system (RDBMS) packages you use for the repository and relational data sources.

• The tag useClientBean in the WAAAnalyzerDesign library has a version attribute that must be set to 6.5.1 or 7.0.0. This attribute is not documented in the JSP Technical Reference Guide.

• When you view a PDF file created by the Export to PDF functionality, an intermittent error may result in the display of a blank screen. This intermittent error occurs because Internet Explorer 6 fails to load the Adobe Acrobat plug-in.

To correct this problem, you must set up Adobe Acrobat Reader Version 4.x or 5.x as follows:

1. From Adobe Acrobat Reader, navigate to the Preferences panel.

2. Navigate to the Web browser options.

3. Clear the check box Web Browser Integration or Display PDF in Browser.

4. Click OK.

• An intermittent error may occur when you run a view using an applet. This intermittent error occurs because Internet Explorer 6 fails to load the correct plug-in.

• You cannot embed Application Builder J2EE functionality in a Hyperion System 9 BI+ Web Analysus JSP.

• You cannot use special characters in a view name. Special characters include the forward slash ( / ) and non alphanumeric characters.

• A filter for the HTTP session, called WAASessionNamespaceServletFilter, was added. If you are using guided analysis and have enabled cookies in your browser, you must enable the WAASessionNamespaceServletFilter filter in the web.xml. This enables the simulation of multiple sessions for a single HTTP session, which is directly linked to the single root browser window on which the cookie is set.


15

• Files with path names that exceed the Windows limit of 255 characters are not valid.

To ensure that you do not exceed this limit when you build an application, take the following steps:

1. Move the WAA directory to a directory with a shorter name.

2. Reset the WAA_HOME variable to the new location.

Solaris

• If you are using Solaris and a Corba server with JDK 1.3.1 or later, Hyperion suggests that you have the same adm.jar file in the classpath for both Application Builder J2EE and Common Warehouse Meta-Model. This way, there is only one administrator server instance running.

• For performance reasons, Hyperion recommends the ADM EDS driver instead of the ADM native driver for the Solaris platform.

Browsers

• Hyperion recommends that you use Microsoft Internet Explorer 6.0 or later to optimize performance.

• Do not use the Back button to navigate through applications. Application Builder J2EE is designed to cache the application state in such a way that use of the Back button may lead to unexpected application behavior.

WebSphere 5.x

When using the Hyperion Reports 7.2 integration with Application Builder J2EE on WebSphere 5.x, charts in HTML reports from Reports will not display correctly.

DB2 8.1 FP 7 and 8.2 FP2

When using DB2 8.x, you cannot write back to a data source.

Workaround: To write back to a data source, take the following steps:

1. Use the following DB2 driver class name:

com.ibm.db2.jcc.DB2Driver

Note: This driver is different from the DB2 class name.

2. Change the port used in the URL from 6789 to 50000. Do not use db2java.zip. The only DB2 driver files in use should be db2jcc*.zip.

Common Security Services • When using single sign-on with multiple applications, ensure that all applications are

pointing to the same LDAP server. If each application's WAACss.xml file points to a different LDAP server, unexpected results occur.


16

• When you do not specify a domain element in the configuration file, searching for a specific user or group specified in multiple places returns only the first match. The match order is as follows:

• Local computer

• Domain of local computer

• Trusted domains

For example, if the local computer and its domain both have an Administrators group and the domain element of the NTLM server is left empty in the external authentication configuration file, then all methods look for the Administrators group and return only one Administrators group. That group is the group on the local computer. It is therefore recommended that you specify a domain element in the external authentication configuration file.

• If the same user ID exists simultaneously with different passwords in an NTLM repository and another repository (LDAP or MSAD) and NTLM is earlier in the search order, authenticating the LDAP or MSAD user ID could result in locking out the NTLM user account. To address this situation, it is recommended that you use the provider hint while authenticating a user, if the authentication repository is known.

• When multiple providers are defined in the search order and one of the providers is misconfigured, Application Builder J2EE stops processing.

• The search order for directories in Application Builder J2EE must be the same as the search order for directories in Netegrity Siteminder.

• Users with empty passwords are not supported.

• Enabling Secure Socket Layer (SSL) connection for communication between Application Builder J2EE and Hyperion Remote Authentication Module can produce errors because of expired Class 3 and Class 2 Verisign PCA root certificates in various releases of J2SE SDK and JRE. To find out more and resolve the issue, refer to the following Web site:

http://sunsolve.sun.com/pub-cgi/retrieve.pl?doc=fsalert%2F57436

• Microsoft Active Directory SP2 and earlier releases are known to have connectivity issues over SSL. For information on resolving this situation, refer to the following Web site:

http://support.microsoft.com/default.aspx?scid=kb;en-us;Q320711.

Grid/Chart

When you export the grid to an RTF file, the Merged Cells option is disabled.

Quick Builder

You must use the Macromedia Dreamweaver Extension Manager version 1.6.062. Uninstall the previous Extension Manager first, then install version 1.6.062. Do not install over a previous version; you do not need to reinstall Dreamweaver MX or uninstall existing extensions first.

Third-Party Products

NetCharts NetCharts can only chart up to 50 rows. When you try to generate a chart with more than 50 rows, you receive only the first 50 rows.


17

Top

Installation Updates

Note: In this section, the term <HAB_INSTALL_DIR> refers to the directory where you installed Application Builder J2EE.

64-bit Processor Support

Application Builder J2EE does not support 64-bit processing.

General

• If the Extract Documentation (350 MB) feature is not selected, the installer calculates and uses up to an additional 230 MB of temporary disk space. This space is released at the end of the installation.

• During the installation process, if all features are not selected, the progress thermometer may not reach 100% before the installer completes the final actions of creating the uninstaller and presenting the next panel. Unless the Summary Panel reports an error, the installation successfully installed 100%.

• If Application Builder J2EE applications are deployed using a previous installation of MySQL that listens on a port different from the default value of 3306, you must make the following adjustment:

1. Stop Apache Tomcat, if it is running.

2. Open the file <HAB_INSTALL_DIR>\WAA\deployments\Tomcat\4.1.30\conf\server.xml.

3. Search for the string hab-admin and on the line that contains the string, find and replace both instances of 3306 with the port value specified in my.ini.

Note: To check the value for the port in my.ini in the Windows directory (usually C:\WINNT) use the section that starts with [Hyperion-MySQL-4.0.12].

4. Repeat step 3 for each of the four Application Builder J2EE applications: hab-admin, hab-blank. hab-samples, and hab-test

5. Open the file <HAB_INSTALL_DIR>\WAA\projects\common\source\WEB-INF\classes\repository.xml, and locate the uncommented (active) JDBC-connection descriptor for MySQL4.x.

6. In the dbalias attribute, insert the port number immediately after the server name, and separate the server name and port number with a colon; for example: dbalias="//localhost:3306/HAB?useUnicode=true&characterEncoding=UTF-8"

7. Repeat steps 5 and 6 to update the repository.xml file located in WEB-INF\classes for each of the four Application Builder J2EE applications: hab-admin, hab-blank. hab-samples, and hab-test.

• During the installation process, if the Extract Documentation feature is selected on Windows, files with path names that exceed the Windows limit of 255 characters are not


18

installed. Therefore, some of the file links for the Javadoc are invalid. The files affected vary, depending on the choice for <HAB_INSTALL_DIR>.

• <HAB_INSTALL_DIR>\docs\WEB-INF is a temporary directory used during the installation process. This directory is not needed after the installation and can be deleted.

UNIX

• If your home directory is located on an NFS drive, the installation process freezes after you click the Finish button in the final frame. The installation succeeds, but the parent HAB<release><platform>Setup.bin process and the Java process it spawns must be ended.

• On all UNIX platforms, to ensure that starting MySQL service does not fail, ensure umask is set to 022 by default.

Otherwise, run the following command prior to running the installer:

umask 022

Alternatively, you can change the permissions of the my.cnf file to read-only by running the following command in the common/DBMS/MySQL/4.0.12/data directory:chmod 644 my.cnf.

WebLogic

• If the supplied applications are deployed to WebLogic 8, and the value for the Windows registry key, HKEY_LOCAL_MACHINE\SOFTWARE\BEA Systems\BEAHOMELIST, is not found or is incorrect, the deployment will fail. Before installing Application Builder J2EE, use the Windows regedit utility to check if this registry key is set.

Workaround: If this registry key is missing, you can add it with regedit or by creating and editing a registry script.

To create and edit a registry script:

1. Create a text file and name it BeaHome.reg.

2. Add the following entries, exactly as shown:

REGEDIT4

[HKEY_LOCAL_MACHINE\SOFTWARE\BEA Systems]

"BEAHOMELIST"="C:\\<BEA_Home_Directory>;"

where <BEA_Home_Directory> is the BEA WebLogic home directory.

Note: Use 2 backslashes for each directory separator as shown.

3. Execute this script by double clicking on it or by calling:

regedit BeaHome.reg

• If you are deploying to WebLogic, the installer calculates and uses up to an additional 230 MB of temporary disk space. This space is released at the end of the installation.


19

WebLogic 8.x

If the supplied applications are deployed to WebLogic 8, make the following change in <WEBLOGIC_DOMAIN_DIR>\hab_startWLS.cmd:

Change the following line from:

call "<WEBLOGIC_DOMAIN_DIR>\startWebLogic.cmd"

to:

call "<WEBLOGIC_DOMAIN_DIR>\<SERVER_NAME>.bat"

where <WEBLOGIC_DOMAIN_DIR> is the absolute path to the WebLogic domain directory and <SERVER_NAME> is the name of the WebLogic server that was created for this domain.

Uninstaller

On the Feature frame, all features are visible and available for selection, including features that should not be visible. The features immediately under Product Un-installation may be shared by other Hyperion products and are not uninstalled even if selected. The check boxes for features under Application Builder J2EE, further down in the hierarchy, should be cleared if you prefer to retain the features.

Shared Services Server Name in Configuration Utility

On the Shared Services registration panel in the Hyperion Configuration Utility in the Server field, you can enter only English alphanumeric characters and the following special characters:

• dash ( - )

• underscore ( _ )

• dot (.)

Cannot Deploy Products to WebLogic on Turkish OS

Because of a known issue with WebLogic 8.1 using a Turkish operating system, Hyperion products cannot be deployed to WebLogic 8.1 in a Turkish operating system environment. You must switch the locale to English and then deploy the product. (1-237420421)

Top

Third-Party Products

This section contains information about third-party product support:

Deprecated Support

Application Builder J2EE Release 9.2 is the last release to support these products:

• MySQL 4.0.12

• Oracle Application Server 10G – 9.0.4


20

• JDK Server 1.4.2_08

• JRE Server 1.4.2_08

• Browser Plug-in JVM 1.3.1_17

WebLogic

Application Builder J2EE cannot be auto-deployed to BEA WebLogic if WebLogic application server is not installed in BEA_HOME. If BEA WebLogic application server is installed outside BEA_HOME, the auto-deployment process for Application Builder J2EE does not execute correctly. If you install in such an environment, use the manual installation method described in Chapter 8 of the Application Builder J2EE Installation Guide for Windows to deploy the supplied applications to the required instance.

Top

Supported Platforms

Application Builder J2EE is certified for use with the following:

Server Operating Systems

• Windows 2000 (SP4)

• Windows Server 2003 (SP1)

• Solaris 9

• Solaris 10

• AIX 5.2

• AIX 5.3

• RedHat Enterprise Linux AS 4.0

Client Operating Systems

• Windows 2000 Professional

• Windows XP Professional

Web Application Servers

• IBM WebSphere 6.1

Databases

• Oracle 9i-9.2.0.1

• Oracle 10g-10.1.0.2

• IBM DB2 8.1 FP 7

• IBM DB2 8.2 FP 2

• Microsoft SQL Server 2000 SP3a

• MySQL 4.0.12


21

• MySQL 4.0.23 (64-bit versions only)

Web Browser

• Microsoft Internet Explorer 6.0

Database Drivers

• JDBC DataDirect 3.4

• Hyperion JDBC MySQL 3.0.7

Java Components

• Sun Microsystems Java Development Kit (JDK) 1.4.2 Build 08 (Windows/Solaris/Linux)

• Sun Microsystems Java Development Kit (JDK) 1.4.2 Build cal 420-2004026 (AIX)

• Sun Microsystems Java Runtime Environment (JRE) 1.4.2 Build 08 (Windows/Solaris/Linux)

• Sun Microsystems Java Runtime Environment (JRE) 1.4.2 Build cal 420-2004026 (AIX)

Top

Known Issues

The following issues are known in this release:

Analytic Data Model

• SAP cannot handle recursive calls from ADM. (1-76446951)

For example:

SELECT {DrillDownMember( {[Z_SKU].[All] }, {[Z_SKU].[All], [Z_SKU].[100-10] }, RECURSIVE )} ON COLUMNS FROM [$ZADM_TBC]

• SAP cannot handle the following ADM function calls: (1-73784384) AddCalculatedMembers() StripCalculatedMembers()

The names of the corresponding functions in SAP have been changed as follows:

ADDCALCULATEDMEMBERS STRIPCALCULATEDMEMBERS

• Because Essbase Analytic Services supports one alias table per query, an ALE data query attempting to query for two alias names will return only one. For example, the ALE query below would return only a single result, even though it queries for both Select Name, "Long Names" and Select Name, Default: (1-15Y393) Select * From TOL PROJECT Year, "Pkg Type" ON EDGE COLUMN WITH


22

(Select Name, "Long Names" From Year Where Member("Qtr1", "Year")), (Select Name, "Long Names" From "Pkg Type" where Children("Pkg Type", "Pkg Type")) PROJECT PRODUCT ON EDGE ROW WITH (SELECT Name, "Default" FROM Product WHERE Descendants("500", "Product", true)) PROJECT Measures, Market ON EDGE PAGE WITH (SELECT * FROM Market WHERE Descendants("East", "Market",true)), (SELECT * FROM Measures WHERE Member("Profit", "Measures")) PROJECT Scenario ON EDGE SLICER WITH (SELECT * FROM Scenario WHERE Member("Actual", "Scenario"))

Apache Tomcat

• If you are deploying to Apache Tomcat on a supported 64-bit platform, the machine hosting Tomcat must have a 32-bit JDK installation.

JVM Install Error When Installing on Same Computer on Which PC Anywhere is Installed

• Due to an InstallShield bug, if you attempt to install Application Builder J2EE on the same computer on which PC Anywhere is currently installed, Java Virtual Machine (JVM) does not get installed.

• Workaround: Uninstall PC Anywhere before beginning installation of Application Builder J2EE. The JVM will be installed along with the product. After you have completed installation of Application Builder J2EE, reinstall PC Anywhere.

WebSphere/Hyperion Product Permissions Issue

• Important: On UNIX platforms, if you are using the IBM WebSphere application server, ensure that you use the same account to install, deploy, and execute Hyperion System 9 products that you use to install WebSphere. Using the same account ensures that the Configuration Utility can successfully deploy Hyperion products to WebSphere.

Known Issues for System 9

The following known issues are general to this release of Hyperion System 9:

Hostnames Specified in English Only In product installers and the Hyperion Configuration Utility, hostnames (computer names) should not be localized and should be entered in English only. For example, when registering


23

with Shared Services in the Hyperion Configuration Utility, the Shared Services server name should be entered in English. (1- 215194141)

Product Activation with Invalid Deployment ID When a valid Deployment ID and an invalid (expired) Deployment ID are entered during product activation using the Configuration Utility, product activation is successful and the user can proceed with application registration. (1-240369941)

Incorrect Translation of Cancel Button in Product Installers Some product installers display an incorrect translation of the Cancel button. (1-232246171)

Error in Instructions for Starting License Server Manually The instructions for starting Hyperion License Server manually on Windows include a backslash character (\) that may cause confusion about what to type on the command line. The instructions should read as follows:

To start License Server with specific license files, use the following example as a guide:

At the command prompt (for example, C:\HYPERION\common\LicenseServer>), type

lmgrd -c Licenses\License_file_name

Note: “Licenses” is the folder that contains the license files, for example: C:\HYPERION\common\LicenseServer\Licenses

To specify the directory containing the license files (recommended), use the following example as a guide:

At the command prompt (for example, C:\HYPERION\common\LicenseServer>), type

lmgrd -c Licenses

Note: “Licenses” is the folder that contains the license files: C:\HYPERION\common\LicenseServer\Licenses

Hyperion Home Environment Variable in Migration Utility The Hyperion Home Migration Utility does not read the Hyperion Home environment variable even though it is already set. To migrate again, first open and close a command window before starting migration a second time. This ensures that the most recent Hyperion Home environment variable is displayed. This problem occurs only in the following languages: Dutch, Simplified Chinese, Traditional Chinese, Korean, and Russian. (1-203998684)

Language List in Portuguese Installer Using a Portuguese operating system, the drop-down list on the Language Selection panel in the installer incorrectly displays Simplified Chinese, Traditional Chinese, and Portuguese selections in Portuguese characters. All other language selections are displayed in English.

Top


Tips and Troubleshooting

Removing Shared Components

To uninstall shared components (i.e., Hyperion Hub, MySQL), please contact Hyperion Customer Support for details on the manual process.

Top

Documentation Updates

Hyperion System 9 Application Builder J2EE Installation Guide

• In each of the “Deploying and configuring Using NNNN”, where NNNN is the name of the Application Server, add the following line in the “Deploying the EAR File” section:

Copy HABADM.lic into WEB-INF\classes of each deployed application.

• Chapter 5: Deploying and Configuring Using Apache Tomcat

In the section, “Deploying a WAR file in Apache Tomcat”, you no longer deploy from the <Tomcat install Dir>. Deploy the supplied apps under the <HAB_INSTALL_DIR>\WAA\deployments\Tomcat\4.1.30.

Top

©2007 Hyperion Solutions Corporation. All Rights Reserved. http://www.hyperion.com

24

http://www.hyperion.com/

hyperion system 9 bi+ application builder j2ee release 9.2.0.1

Documents