=================================================================== DB2 OLAP Server Analyzer V8.1 -- Refreshed FixPak 4 FOR THE IBM PRODUCT, THIS DOCUMENT SUPERSEDES AND OVERRIDES THE DOCUMENTATION PROVIDED BY HYPERION. IF YOU SEE ANY INFORMATION IN THE HYPERION DOCUMENTATION THAT CONTRADICTS THIS README FILE, IGNORE THE INFORMATION IN THE HYPERION DOCUMENTATION. March 2004 Service level: Hyperion Analyzer 7.0.0.0.1472 First created: 02/23/04 =================================================================== CONTENTS 1. Welcome to FixPak 4 2. Before you install 3. Installing the FixPak on Windows 4. Installing the FixPak on UNIX 5. Known Isues - General - Installation - Uninstaller - Java Web Client - Analysis Tools - Design Reports Mode - Formatting - Pinboards - Relational Connectivity (formerly known as Virtual Cubes in IBM Analyzer v7.1) - Related Content - HTML Web Client - Hyperion Analyzer Analysis Server Console - Administration - API Toolkit - Third Party Software Issues 6. External Authentication and Single Sign-on - New Features - Known Issues 7. Fixed Issues =================================================================== 1. Welcome to FixPak 4 -------------------------- FixPak 4 offers the following enhancements: - Startup in Report Manager - Introduces Dependant Subscription Controls - Enhanced Relational Connections - FixPak 4 adds support for Windows 2003 Server - AIX 5.1 and 5.2 are supported with Analyzer 8.1 FP 4 - FixPak 4 supports WebSphere Application Server v5.0 and above Note: - This FixPak is English only. Though it is multi-byte enabled, it has not been translated. - The "Uninstaller" section under "Known Issues" may not be fully relevant to Analyzer FP4 since our installation process is different and does not include an Uninstaller program. - WebSphere v3.5.5 is not supported with FixPak 4 - HP-UX 11.0 is not a supported platform. Please ignore references to HP-UX 11.0 in the documentation. FixPak 4 is available from the IBM FTP site: ftp://service.software.ibm.com/ps/products/db2olap/fixes/ analyzer/v81/fp4/ =================================================================== 2. Before you install ---------------------- - FixPak 4 only supports the Refreshed edition of DB2 OLAP Server Analyzer Version 8.1. If you have not yet upgraded to the Refreshed edition, please do so before applying FixPak 4. - WebSphere Application Server v4.0 users MUST install FixPak 5 (to bring WebSphere up to v4.0.5 level) prior to installing Analyzer's FixPak 4. If this is not done, Analyzer will not work. - For customers who are installing Analyzer on a machine that already has WebSphere 5 installed, please create an empty file called admin.config and save it to the WAS_HOME\bin directory prior to installing Analyzer base code (v8.1 Refreshed). More information is available at: WAS5: ftp://service.software.ibm.com/ps/products/db2olap/fixes /analyzer/v81/fp3/anafp3_was5adv.pdf WAS 5 Express: ftp://service.software.ibm.com/ps/products/db2olap/fixes /analyzer/v81/fp3/anafp3_was5xprs.pdf Please note that the above documentation pertains to installing FP4 with Analyzer base code with WebSphere 5 and WebSphere 5 Express as well as with Analyzer FP3. - If there is a previous release of Hyperion Analyzer on the system, it is strongly recommended that you backup your current Analyzer repository prior to installing FixPak 4 as the database tables within the Hyperion Analyzer repository have been reorganized. During the installation, the tables are automatically migrated to the new structure. As a result of the table changes, previous releases (Analyzer FP2 and below) of Hyperion Analyzer repository do not work with this release of Hyperion Analyzer. - There are known memory issues regarding Analyzer on the Solaris platform. Please refer to section 5 called "Known Issues" under the "Installation" heading below. - Should a new FixPak for DB2 UDB 7.2 or DB2 UDB 8.1 be installed after Analyzer FP4 is installed, ensure to synch up the JDBC drivers (for example, db2java.zip with DB2 7.2, and db2java.zip and db2jcc.jar with DB2 8.1). Copy and replace the existing files of the same name to the following location: C:\WAS_HOME\installedApps\...\Analyzer70.ear\Analyzer70.war \WEB-INF\lib (Windows) /usr/WAS_HOME/installedApps/.../Analyzer70.ear/Analyzer70.war /WEB-INF/lib (AIX) /opt/WAS_HOME/installedApps/.../Analyzer70.ear/Analyzer70.war /WEB-INF/lib (Solaris) where WAS_HOME is the installation path for WebSphere. - It is recommended to uninstall Tomcat v4.0.4 prior to installing Tomcat v4.1.18 during the install of Analyzer FP4. - Downloading WebSphere Application Server 4.0.5 (Fixpak 5) You can download WebSphere Application Server 4.0.5 (Fixpak 5) from the following FTP sites: For Windows: ftp://ftp.software.ibm.com/software/websphere/appserv/support /fixpacks/was40/fixpack5/Windows/ For Advance Edition, download: Filename: was40_ae_ptf_5.zip File size: 69.5 MB Date: 12/11/2002 12:00 AM For Advance Edition Single Server, download: Filename: was40_aes_ptf_5.zip File size: 67.0 MB Date: 12/11/2002 12:00 AM For AIX: ftp://ftp.software.ibm.com/software/websphere/appserv/support /fixpacks/was40/fixpack5/AIX/ For Advance Edition, download: Filename: was40_ae_ptf_5_AIX.tar File size: 75.5 MB Date: 12/11/2002 12:00AM For Advance Edition Single Server, download: Filename: was40_aes_ptf_5_AIX.tar File size: 72.9 MB Date: 12/11/2002 12:00AM For Sun: ftp://ftp.software.ibm.com/software/websphere/appserv/support/ fixpacks/was40/fixpack5/Sun/ For Advance Edition, download: Filename: was40_ae_ptf_5_SUN.tar File size: 90.6 MB Date: 12/11/2002 12:00AM For Advance Edition Single Server, download: Filename: was40_aes_ptf_3_SUN.tar 5 File size: 87.5 MB Date: 12/11/2002 12:00AM - The directory structure "C:\hyperion\analyzer" in Windows, "/usr/hyperion/analyzer" in AIX, and "opt/hyperion/analyzer in Solaris (by default from a previous installation of Analyzer) must be intact for Fixpak 4 to be successfully installed. =================================================================== 3. Installing the FixPak on Windows ------------------------------------ Prior to installing Analyzer 8.1 FixPak 4, it is imparative that step 1 be done. Steps 2 and 3 are optional since Analyzer FP4 uses a new context root (Analyzer7_Server) and creates a new .ear file (Analyzer70.ear): 1) remove the ear subdirectory under C:\hyperion\analyzer (WIN) 2) remove the existing Analyzer65.ear (optional) 3) stop the Analyzer65 enterprise application in the Administrative Console (in WebSphere) and then uninstall Analyzer65 (optional) Proceed with the steps outlined below on installing this FixPak. This next section describes how to apply this FixPak: a) Download the analyzer81_fp4.zip file to a temporary directory on your Windows system. Make sure the path name of the directory does not include spaces. The FixPak installation program does not support directories whose names have spaces in them. Underscore characters are acceptable in directory names. b) Unzip the analyzer81_fp4.zip file to the same drive where Analyzer 8.1 Refresh is installed. Then run AnalyzerSetup.exe. c) Analyzer Windows Client and Analyzer Server are not separate downloads. On the installation panel called "Usage Mode", choose the appropriate radio button. To upgrade Analyzer Windows Client, choose the option called "Windows Client". To upgrade Analyzer Server, choose the option called "Enterprise Edition". d) Analyzer now requires that the location for the JDBC Driver Path (eg.db2java.zip for DB2 UDB v7.2 and db2java.zip for DB2 UDB v8.1) be supplied during installation (on panel "Configure RDBMS Repository"). If DB2 UDB is located on a remote machine, please copy the db2java.zip (for DB2 UDB 7.2) file and both db2java.zip and db2jcc.jar (for DB2 UDB v8.1) and put this (these) file(s) onto the local machine where Analyzer FP4 is being installed. By default, this file can be found at: Windows: C:\Program Files\SQLLIB\java (DB2 UDB 7.2) C:\Program FIles\IBM\SQLLIB\java (DB2 UDB 8.1) AIX: /home/db2inst1/sqllib/java12 (DB2 UDB 7.2) /home/db2inst1/sqllib/java (DB2 UDB 8.1) Solaris: /export/home/db2inst1/sqllib/java12 (DB2 UDB 7.2) /export/home/db2inst1/sqllib/java (DB2 UDB 8.1) where db2inst1 is the instance owner for DB2. e) If you install WebSphere Application Server 4.0 on a system that has DB2 Personal Edition installed on it, you might get an error message about not having proper version of DB2. The workaround is to click "Cancel" on the message dialog, and then "Resume Setup". The installation continues normally. f) To start the WebSphere Application Server 4.0 Service, the "Server" service must be present and started on the machine. The "Server" service can be installed by adding "File and Printer Sharing" from Network Connections in the Control Panel. You need the Windows CD to add "File and Printer Sharing" and then you need to reboot. WebSphere Application Server 4.0 requires the "Computer Browser" service to be started, which in turn is dependent on the "Server" and "Workstation" services. Note: If installing Fixpak 4 with the existing Analyzer repository (eg. default, ANALYZ60, ANALYZ62 or ANALYZ65), please backup the database (called ANALYZ60, ANALYZ62 or ANALYZ65) in DB2 UDB (or other RDBMS') prior to installing Fixpak 4. =================================================================== 4. Installing the FixPak on UNIX --------------------------------- Prior to installing Analyzer 8.1 FixPak 4, it is imparative that step 1 be done. Steps 2 and 3 are optional since Analyzer FP4 uses a new context root (Analyzer7_Server) and creates a new .ear file (Analyzer70.ear): 1) remove the ear subdirectory under /usr/hyperion/analyzer (AIX) /opt/hyperion/analyzer (Solaris) 2) remove the existing Analyzer65.ear (optional) 3) stop the Analyzer65 enterprise application in the Administrative Console (in WebSphere) and then uninstall Analyzer65 (optional) Proceed with the steps outlined below on installing this FixPak. This next section describes how to apply this FixPak: a) Download the analyzer81_fp4_aix.tar (or analyzer81_fp4_sun.tar) file to a temporary directory on your UNIX system. Make sure the path name of the directory does not include spaces. The FixPak installation program does not support directories whose names have spaces in them. Underscore characters are acceptable in directory names. b) Untar the analyzer81_fp4_aix.tar (or analyzer81_fp4_sun.tar) file to the same machine where Analyzer 8.1 Refresh is installed. Then run AnalyzerSetup. c) Analyzer now requires that the location for the JDBC Driver Path (eg.db2java.zip for DB2 UDB v7.2 and db2java.zip for DB2 UDB v8.1) be supplied during installation (on panel "Configure RDBMS Repository"). If DB2 UDB is located on a remote machine, please copy the db2java.zip (for DB2 UDB 7.2) file and both db2java.zip and db2jcc.jar (for DB2 UDB v8.1) and put this (these) file(s) onto the local machine where Analyzer FP4 is being installed. By default, this file can be found at: Windows: C:\Program Files\SQLLIB\java (DB2 UDB 7.2) C:\Program FIles\IBM\SQLLIB\java (DB2 UDB 8.1) AIX: /home/db2inst1/sqllib/java12 (DB2 UDB 7.2) /home/db2inst1/sqllib/java (DB2 UDB 8.1) Solaris: /export/home/db2inst1/sqllib/java12 (DB2 UDB 7.2) /export/home/db2inst1/sqllib/java (DB2 UDB 8.1) where db2inst1 is the instance owner for DB2. Note: If installing Fixpak 4 with the existing Analyzer repository (eg. default, ANALYZ60, ANALYZ62 or ANALYZ65), please backup the database (called ANALYZ60, ANALYZ62 or ANALYZ65) in DB2 UDB (or other RDBMS') prior to installing Fixpak 4. =================================================================== 5. Known Issues: -------------------- ===== General ===== - Labels on charts may disappear. There is a known issue with the Netchart engine where if there is something laying over a chart area, it will show in Normal view but will occasionally disappear and then reappear. 01-05-0113 (7258) - Help section under Administration Tools is pointing to the Java Client Usage document instead of the Administrator's Guide. The Workaround to view the correct document is to click on Help > Information Map and choose the Administrator's Guide. 04-03-0167 (7375) - On Solaris 5.8, OLAP Server cubes that have these special characters (eg. ç ã á é í ó ú ü) are not rendering within Analyzer's Database Connection. However, reports and report groups can be named with these special characters. (6920) - With Web Publish > Report Group, when the "Select a Directory" panel appears, the "file name" field is looking for a chosen folder name (ie. choose a folder for example, c:\temp) and then all the reports that are in the report group will get saved into the chosen foder (in this case, temp). - Within the Report Properties panel, note that only filename.jsp (for the JSP Template field) and filename.html (for the Publish To field) are needed. Filename.jsp needs to reside under APPSERVER_HOME\...\ Analyzer7_Server\wp_templates directory Filename.html needs to reside under APPSERVER_HOME\...\ Analyzer7_Server\wp_output directory - When adding, deleting, or renaming Hyperion Essbase dimensions in the outline, reports will not reflect changes to dimension names. The Hyperion Analyzer interface displays the dimension name used when the report was created. 02-04-0073, 03-08-0234 - The Java Plug-in 1.3 does not automatically download and install in Netscape implementations. You must obtain the Java Plug-in 1.3 manually from the Sun Web site. 01-05-0003 - The PLUGINSPAGE attribute of the EMBED tag is not applied using Netscape 7.02. 03-04-0247 - Web Publish Batch Export does not work with multi-byte regional settings such as Chinese, Japanese and Korean. 03-10-0125 - Hyperion Essbase "Change Password at Next Logon" does not work when accessing a database connection using default Analyzer Authentication. 03-10-0134 - Hyperion Analyzer supports EDS connectivity to Hyperion Essbase. However, connectivity via EDS to clustered Essbase Servers is not working at this time. - The Java Web Client appears hung when drilling down on a member that contains more than 20,000 members. 03-01-0057 - Dynamic Time Series (DTS) members not showing or working correctly in Quadrant Charts 03-06-0286 - Substitution Variables cannot be chosen as an axis member for a Quadrant Chart 03-06-0287 - Hyperion Essbase attribute calculations used without attribute member selections result in no data being returned. 03-07-0026 - When placing Dynamic Time Series dimension members on the page axis, an "All Data is hidden" message is displayed. 03-09-0031 - Removing or renaming members in the Essbase outline that are also first members on the page axis, causes the report not to load correctly. 03-09-0226 - When shared member name aliases and stored member names differ, and the shared members is on the page axis, an "All data is Hidden" message is displayed. 03-11-0087 - Hyperion Analyzer does not save carriage returns in header and footer definitions. 04-01-0200 - Freeze Headers can cause background colors to paint incorrectly. 02-10-0047 - Installations on Japanese Operating Systems Due to limitations in WebSphere 4.0.5 application server, the HTML Web Client and Analysis Server Console cannot transmit double-byte Kanji characters in WebSphere implementations. ===Installation === - The Tomcat 4.1.18 Application Server shutdown port is set to 8005. When this port number is not available, the Tomcat Application Server does not start. This port number can be changed after the installation is completed. To change to port number, locate the server.xml file found in the C:\Hyperion\common\appServers\Tomcat\4.1.18\conf directory and change the following xml tag: - When using Apache Tomcat 4.1.18, you cannot open Analyzer applications named with extended or multi-byte characters. Avoid using multi-byte characters in the application name. - Installation logs may contain exception errors related to the deployment of JDK samples in HP-UX deployments. This does not impact installation. 03-06-0247 - Those creating a new IBM DB2 Analyzer repository must create a blank database prior to installing Hyperion Analyzer. 02-04-0103 - When creating the Analyzer repository avoid usernames that begin with numeric characters. 03-11-0127 - Database for WebSphere Application Server 4.0.5 on AIX needs to be cataloged as a remote database even if it is not. Please refer to the IBM Redbook (http://ibm.com/redbooks) "IBM WebSphere V4.0 Advanced Edition Handbook for further details. - IBM DB2 8.1 Analyzer repositories: The specified JDBC driver directory must contain both the db2java.zip and the db2jcc.jar drivers. - Memory problems for Websphere on Solaris environment. There are two workarounds. Select the workaround that matches your installation. First workaround: Install Hyperion Analyzer 7.0 and deploy to WebSphere as described in Installation Guide. (This assumes that OLAP EDS has been installed). Then take these steps: 1. Copy the following files: ees_es_server.jar ees_japi.jar to this directory: /opt/WebSphere/AppServer/installedApps/Analyzer70.ear/ Analyzer70.war/WEB-INF/lib 2. Delete admees.jar from /opt/hyperion/analyzer/adm/lib 3. Edit the Analyzer.properties file in the following directory: /opt/WebSphere/AppServer/installedApps/Analyzer70.ear/ Analyzer70.war/WEB-INF/conf and set the following values: UseEssbasePassthru=true UseEDS=true EDSPort=5001 or whatever port EDS is using EDSServerName=hostname of EDS server 4. Modify the ADM.properties file in the following directory: /opt/WebSphere/AppServer/installedApps/Analyzer70.ear/Analyzer70.war /WEB-INF/classes and set the following values: ADM_USE_CORBA=0 5. Make sure there are no admserver processes running. The second workaround: A high level of exceptions causes the ADM server process to crash due to a buffer overrun in the Java Virtual Machine. To avoid this, start the ADM server process manually rather than allowing it to start automatically within the scope of the Web Application Server. 03-06-0333 To start the ADM server process manually: 1. Locate all adm.ior files on the Solaris server. These files are usually located in the web application server’s directory structure. 2. End the admserver process. 3. Delete all of the existing adm.ior files. Note: One adm.ior file is created in the next step. 4. Stop and re-start the Web Application Server, log on to Hyperion Analyzer and connect to Hyperion Essbase. This starts the ADM server process automatically. 5. Search for the adm.ior file. There should only be one copy of this file. You must now start the admserver process manually. 6. Stop the Web Application Server and end the admserver process. 7. Open the startup script for the Web Application Server and locate the JAVA_HOME environment variable. 8. Create a new .sh script in the directory where the adm.ior file from Step 5 resides with the following information (Be sure to edit the paths for JAVA_HOME and PATH to match your environment): JAVA_HOME=/opt/websphere/appserver/java export JAVA_HOME ADM_TRACE_LEVEL=4 export ADM_TRACE_LEVEL PATH=/opt/websphere/appserver/java/bin:$PATH export PATH java -version admserver -ORBStdProfileComponents 0 > adm.log 9. Start the ADM server process manually by executing this shell script prior to starting the Web Application Server. All ADM tracing is output to the file specified in the last line of the shell script (adm.log). - Analyzer sites using DB2/UDB 7.2 fixpak 9 (or DB2/UDB 8.1 fixpak 2)for Analyzer repository will receive the following errors on various client and admin functions: CLI0602E Memory allocation error on server. CLI0210E Memory allocation failure. DB2/UDB Fixpak 9 changes how memory was allocated by JDBC layer for CLOB objects, in some cases requesting too much memory. This problem is described in DB2/UDB APARs IY45529 and IY45585. We recommend that DB2/UDB fixpak 9 not be installed on the DB2 instance containing the Analyzer 8.1 repository, unless a critical DB2 fix is needed from that maintenance level. If DB2/UDB 7.2 fixpak 9 is required, then you will also need to apply a special build on top of fixpak 9 to resolve the memory allocation errors. These fixes will be integrated in a future DB2/UDB 7.2 fixpak. For DB2/UDB 7.2 fixpak 9 on AIX, use special build 7711. For DB2/UDB 7.2 fixpak 9 on Windows, use special build 7789. You may obtain a copy of the above special build files from the DB2 OLAP Server support page: http://www-3.ibm.com/software/data/db2/db2olap/support.html IBM DB2® OLAP Analyzer 8.1 sites that using DB2 UDB, Version 8.1 for the Analyzer repository may receive the following errors on various Analyzer client and Analyzer admin functions: This error occurs when the DB2 JDBC layer allocates too much memory for CLOB objects. This problem is described in DB2 UDB APAR IY47914. The following special fix builds are available to correct this problem. These special builds require DB2/UDB v8.1 fixpak 2 or fixpak 2+. Although the problem occurs at all levels of DB2 v8.1, the fix is only available at the fixpak 2 or 2+ level. Before applying the special build, confirm DB2 v8.1 is using one of the following two maintenance levels: Fixpak 2 (s030508) Fixpak 2+ (s030611) The following 6 special builds for DB2 UDB v8.1 are available to correct the memory error: hotfixpkg_8321.exe for DB2 v8.1 FP2 on Windows hotfixpkg_8324.exe for DB2 v8.1 FP2+ on Windows special_8322.tar.Z for DB2 v8.1 FP2 on AIX special_8325.tar.Z for DB2 v8.1 FP2+ on AIX special_8323.tar.Z for DB2 v8.1 FP2 on Solaris special_8326.tar.Z for DB2 v8.1 FP2+ on Solaris. These 6 special builds are available at the following FTP address: ftp://service.software.ibm.com/ps/products/db2olap/fixes/analyzer/v81 /db2v8fix Refer to the readme files in the above directory for additional installation instructions for the special builds. ===== Uninstaller ===== - The following options within uninstaller are not supported: Hyperion Look and Feel 1.0.0 Hyperion External Authentication Module 2.5.2 Apache Tomcat 4.1.18 Java Development Kit 1.3.1 Apache Log4j 1.2.8 Hyperion Hub SDK 7.0.0 Hyperion Analyzer repository - Uninstaller will remove all contents from the Analyzer install directory except for the classes.xml. - Windows installations using the default Tomcat Application Server, the following must be done to complete the uninstall: The following entry must be removed from the server.xml. If C:\Hyperion is the Hyperion Home, C:\Hyperion\common\appServers \Tomcat\4.1.18\conf is where the file is located. The following directories and files need to be removed: - C:\Hyperion\common\appServers\Tomcat\4.1.18\webapps \Analyzer7_Server directory - C:\Hyperion\common\appServers\Tomcat\4.1.18\bin\ Analyzer_Startup.bat - C:\Hyperion\common\appServers\Tomcat\4.1.18\bin\ Analyzer_Shutdown.bat - Unix installations using the default Tomcat Application Server, the following must be done to complete the uninstall: The following entry must be removed from the server.xml. If opt\Hyperion is the Hyperion Home, opt\Hyperion\common\appServers \Tomcat\4.1.18\conf is where the file is located. The following directories and files need to be removed: - opt\Hyperion\common\appServers\Tomcat\4.1.18\webapps\ Analyzer7_Server directory - opt\Hyperion\common\appServers\Tomcat\4.1.18\bin\ Analyzer_Startup.sh - opt\Hyperion\common\appServers\Tomcat\4.1.18\bin\ Analyzer_Shutdown.sh ===== Java Web Client ===== === Analysis Tools === - You cannot edit traffic lighting definitions in page axis dimensions. 03-06-0254 - Only the first constant calculation is displayed, when multiple calculations with constants are defined. 02-12-0073 - Analysis Tools definitions applied to specific dimension member aliases are lost when the alias table selection is changed. 03-12-0210, 03-12-0212, 03-12-0215 - Analysis Tools definitions applied to DTS members defined with substitution variables are lost when the substitution variable is updated. 04-01-0021 === Design Reports Mode === - Hyperion Analyzer Release 6.2.1 (and earlier) opaque Services button properties were stored incorrectly. When migrating to these Services buttons to Hyperion Analyzer Release 7.0, gray Service buttons are displayed white. 03-03-0146 - You cannot link Multi-level Combo Boxes to more than one data source. Instead use the new Dependent Subscription components. 03-07-0029 - You cannot modify Multi-level combo box member selections. Instead use the new Dependent Subscription components. 03-07-0082 - You cannot use Multi-level Combo Boxes with Relational Database Connections that contain more than 2 generations. Instead use the new Dependent Subscription components. 03-12-0250 - Netscape 7 fails to display the last two rows of SQL Spreadsheet components. 03-06-0166 - Though the Edit Data service button can be applied to a relational spreadsheet, relational data sources do not support this functionality. 03-09-0025 - You cannot use the Combo box component to dynamically populate relationally stored Siblings in Hybrid Analysis. 03-10-0121 === Formatting === - Drilling on a shared members with Selected Member First enabled causes members to display in the incorrect order. 03-05-0095 === Pinboards === - Large pin images cause layout pins to disappear in the Pinboard Designer. 02-12-0006 - Using animated GIFs as pins in a Pinboard may cause display issues. 02-05-0050, 03-02-0102 - When using Substitution Variables as Pins, the Pin member name doesn't update. 03-10-0022 === Relational Connectivity (formerly known as Virtual Cubes in IBM Analyzer v7.1) === - Dimension Browser returns only relational dimension members that exist in the fact table. 03-12-0198 - Custom Lookups, available in 6.5.1, are no longer supported. 03-12-0203 - Dimension members are not displayed in the order they are chosen in Dimension Browser. 04-01-0111 - The Virtual Cube Editor node tree, used to define generations, collapses when users change from ID to Description. 04-01-0117 - Row Headers display incorrectly when dimension members share the same ID. 04-01-0132 - Drill Linking yields unexpected results when dimension members share the same ID. 04-01-0136 - Pages display incorrectly when dimension members share the same ID. 04-01-0139 - When drilling down, the result set order differs from the Dimension Browser member selection order. 04-01-0110 === Related Content === - Essbase does not support adding Linked Reporting Objects to intersections using Attribute dimensions. 03-06-0021 - Report names with multibyte or localized characters (French, German, for example) do not display correctly in the Related Content dialog box. 03-10-0119, 03-10-0095 ===== HTML Web Client ===== - Service buttons with long wrapping labels may paint incorrectly. 03-06-0273 - HTML Web Client users cannot edit text in a text area custom report component. 02-06-0015 - The HTML Web Client does not indent Parent-Child hierarchies on the rows axis. 03-11-0160 - The HTML Web Client does not support reports with transparent split panels created in the Java Web Client. 02-11-0098 - The HTML Web Client cannot display entire charts when Chart Scrolling is enabled. 03-07-0113 - Reports created in the HTML Web Client do not support the swapping and moving of dimensions when a database connection Point of View definition is enabled. 04-01-0024 ===== Hyperion Analyzer Analysis Server Console ===== - The Hyperion Analyzer Analysis Server Console displays incorrect session information when used with clustered Analyzer Server deployments. 03-06-0207 - The Analysis Server Console does not honor default domain types. 04-01-0180 ===== Administration ===== - All users must be assigned a role. Documentation incorrectly states that users are assigned the Information Consumer role by default. 03-10-0111 - Administration Tools | Help | Context and Index launches the Analyzer Java Client online help system. To launch the Administration Tools online help use the Information Map. ===== API Toolkit ===== - Hyperion Analyzer 7.0 includes the Hyperion Analyzer 6.5 API Toolkit Developer’s Guide. The Hyperion Analyzer 7.0 API Toolkit Developer’s Guide will be available after the release. ===== Third Party Software Issues ===== - Page controls malfunction when selecting multiple Page axis Hyperion Financial Management dimension members with the same name. 03-04-0058 - Netscape does not support modal Hyperion Analyzer API Toolkit dialog boxes. 02-09-0041 - Column names containing apostrophes are not supported by the Oracle 9i JDBC driver and cannot be used in Relational Connections or SQL Spreadsheet objects. 03-04-0246 - The charting engine does not support long labels on the Z-axis. 03-03-0204 - The custom report HTML Browser object supports only basic HTML. It does not support dynamic HTML or JavaScript. 02-04-0116 - The HTML Web Client does not support the printing of custom report SQL Spreadsheet components. 03-06-0249, 02-08-0077, 02-05-0095 - Displaying too much information in a chart object may cause the chart to be blank. To avoid this, the Java console warns of insufficient room for chart data. Else, use chart scrolling. 02-04-0084 - When drilling up on a shared member, the base member’s parent is returned. 01-10-0168 - Hyperion Essbase Label mode settings set per dimension display incorrectly when dimensions are nested. Ensure that all dimensions on a given axis have the same label mode. 03-04-0171 - Hyperion Essbase | Suppress Shared Members only works for Also Select Level and Dim Bottom dynamic selections. 02-02-0128 - Hyperion Essbase | Select Dim Bottom member selection for a combo box does not return the bottom level relational member in applications using Hybrid Analysis. 02-05-0094 - Hyperion Financial Management duplicates the children of drilled members, when users drill down on the same member two times. 02-05-0073 - Using the Member List option to select invalid Hyperion Financial Management members may cause errors when the query is launched. 02-11-0085 - Selecting invalid Hyperion Financial Management members returns the top member for the dimension containing the invalid selection. This results in additional inconsistencies between the information panel and main display. 03-02-0095 - Drill to Descendants drill option is not supported by Hyperion Financial Management. 03-01-0036 - Drilling on a member causes incorrect header indentions by Hyperion Financial Management. 02-08-0077 =================================================================== 6. External Authentication and Single Sign-on -------------------------------------------- === New Features === - Single sign-on with Netegrity Siteminder The Hyperion Analyzer 7.0 enables single sign-on with Netegrity Siteminder 5.x. If the web resources in your environment is protected using Netegrity Siteminder, you can configure Analyzer for single sign-on through SiteMinder. The users will be authenticated by Siteminder and will not be required to present credentials again when logging in to Hyperion applications in the same Siteminder session. - Hyperion Remote Authentication Module can be used to link Windows domains. The Hyperion Remote Authentication Module 7.0, formerly called the NTLM Remote Server, can be installed from the Hyperion Download Center. In addition to enabling UNIX application users to log in using a Windows domain, the Hyperion Remote Authentication Module also allows Hyperion applications to authenticate users belonging to other domains that are not trusted by the domain on which the Hyperion application is installed. This removes the necessity to establish trust relationships between the domains. - When a domain element in the configuration file is unspecified, searches for specific users or groups on multiple authentication providers 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 that look for the "Administrators" group return only the "Administrators" group on the local computer. It is therefore recommended that you specify a domain element in the external authentication configuration file. When the same user ID exists simultaneously with different passwords in an NTLM repository and in 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. Hyperion Analyzer abandons the authentication process for all providers, when one provider is incorrectly configured in search orders with multiple providers. Ensure that the search order for directories in Hyperion Analyzer 7.0 is the same as the search order for directories in Netegrity SiteMinder. External Authentication is not supported for user IDs with empty passwords. === Known Issues === - Enabling SSL for communication between Hyperion Analyzer 7.0 and Hyperion Remote Authentication Module 7.0 can produce errors because of expired Class 3 and Class 2 Verisign PCA root certificates in various releases of J2SE SDK and JRE. For more information about this issue and its resolution, refer to this Web site: http://sunsolve.sun.com/pub-cgi/retrieve.pl?doc=fsalert%2F57436 - Earlier releases of Hyperion applications employing Hyperion Remote Authentication Module 7.0 return an incorrect list of users and groups when the domain element is specified in the configuration file. To avoid this situation, use Hyperion Remote Authentication Module 7.0 only with Hyperion Analyzer 7.0. - For earlier releases of Hyperion Analyzer, continue to use Remote Authentication Module 7.0 (previously called NTLM Remote Server). Microsoft Active Directory sp2 and earlier releases are known to have connectivity issues over SSL. To resolve this situation, refer to this Web site: http://support.microsoft.com/default.aspx?scid=kb;en-us;Q320711. - WebSphere Application Server 4.0.x supports the Java Secure Sockets Extension (JSSE) and the Java Cryptology Extension (JCE) only internally, within WebSphere. IBM does not provide support for JSSE and JCE usage in customer applications. Therefore Hyperion Analyzer 7.0 does not support SSL on WAS 4.0.x for communicating with LDAP and Microsoft Active Directory servers. For more information, refer to this Web site: http://www-1.ibm.com/support/docview.wss?uid=swg21044255 =================================================================== 7. Fixed Issues: -------------------- - In Administrator | Measures Formatting dialog, tree does not maintain the applied state of formatting and resolutions set to 800 x 600 the dialog is not completely viewable. 02-07-0001 - Reports connecting with Relational Connections a\k\a Virtual Cubes performs slow when running against large fact tables. 02-09-0177 - When a page member contains no data, Analyzer prints incorrectly on pages. 03-02-0025 - When label mode is set to descriptions (alias), shared members display the id (member name) until selected in the dimension browser. 03-04-0245 - If RDMBS userid (Security Principle in classes.xml) does not match schema name of Analyzer tables in the repository, Stand-alone client login goes into infinite loop. 03-05-0109 - Connecting to a 6.2.1 repository, the automatic migration from 6.2.1 to 6.5 does not keep the column size. 03-07-0091 - The number of line spaces in column headers double after saving and reloading a report. 03-08-0103 - Case-sensitive members do not display. 03-09-0107 - Using the Line Chart | Show Values Option, the line chart shows values for wrong series. 03-09-0235 - Using the dim bottom advanced selection on a relational connection a/k/a virtual cubes, the query appears to never return. 03-10-0036 - Using dimension browser on a relational connection a/k/a virtual cube, expanding a dimension with thousands of members does not work. 03-10-0038 - Migrating from 6.2.1 to 6.5.x, the scaling label on charts is truncated or unreadable. In version 7.0, Analyzer now appends the scaling label to the axis title. 03-10-0087 - Unable to save custom settings for a slider bar. 03-10-0093 - Creating a calculation using the advanced method does not allow selection of arguments. 03-10-0122 - With a screen resolution of 800x600, the Print dialog’s “Print” and “Close” buttons are not visible. 03-10-0129 - Selecting Refresh when in Edit Data mode against an Essbase connection, the changed data values remain in the cache. Thus, if commit/send button is selected, the changed data values will be sent to the Essbase server, even though the data values appears to be refreshed. 03-11-0002 - Using a shared member on a report that is subsequently renamed in the Essbase outline, the data results are correct, however, the member name does not change in spreadsheet. 03-11-0036 - Selecting Home after loading a report group or several reports is slow. 03-11-0077 - Returning reports with many rows and columns are slow with autosize enabled. 03-11-0113 - The ability to set the replace missing with text at the report level is missing compared to the 6.2.1 release. 03-11-0114, 03-11-0115 - Multi-byte characters are not working with AdminMigrate.exe. 03-11-0133, 03-11-0134 - Analyzer Web Publish does not work with IBM WebSphere 5, however, it does work with IBM WebSphere 4. 03-11-0139 - Changing the alias (description) of a member that Restrict Data is applied, the information dialog reads "The top/bottom definition (restrict data) could not be applied. Would you like to remove the definition?" Because the choices are “Yes”, which removes the definition from the query and “No”, which updates the definition, the choices are confusing. The choices are now “Remove” and “Update”. Restrict Data and Retrieve Top/Bottom definitions are based on position within the column (column 1, column 2, etc…) rather than member name (description/id). 03-11-0141 - Migrating pinboards from release 5.0.x, the pins do not appear in release 6.5.x. 03-11-0146 - Unable to see EIS drill through reports or Essbase Link Reporting Objects, if multiple dimensions in Filters axis have member selections defined. 03-11-0152 - Hierarchy structure does not display an indent for the Parent -> child relationship in rows in reports in the HTML Web Client 03-11-0160 - After adding tokens in Headers/Footers and choosing to save print setting with report, the print dialog becomes blank. 03-11-0173 - Analyzer Java Web Client’s default window size hides the Windows taskbar. 03-11-0175 - When database connnections are associated to user group(s) , users within these users group(s) are unable to set Alias Tables on the group associated database connections. 03-12-0001 - Column fly-overs display the wrong member name. 03-12-0007 - Selecting a cell with decimal values ( 6.45 ) with French regional settings in Edit Data mode, the decimals are removed and the value is incorrect when sent (645) to the Essbase server. 03-12-0024 - Exporting users, user groups and database connections with “&” in their name from Administrator, the created .aru file cannot be imported. 03-12-0025 - If you have division by zero using percent calculation, the result is incorrect. 03-12-0028 - Using the advanced selection, Also Select Previous, within a combo box, the selection cannot be renamed. 03-12-0080 - Using a resolution set to 800 x 600, the Analysis Tools Manager dialog is partially displayed. 03-12-0090 - When printing to PDF function, the data appears on alternate pages. 03-12-0108 - Drilling on an inner nested dimension member with expand drilling enabled and a calcuation is placed at top on the outmost dimension, the drill does not occur. 03-12-0216 - When switching between applications, some Analyzer dialogs disappear from view. 03-12-0217 - Using the Tomcat application server, the installer fails to path to the css.dll used for LDAP, MSAD, and NTLM authentication in the analyzer_startup.bat. 04-01-0062 - Increasing font size causes header and data font options to disappear from User Preferences Dialog. 04-01-0114 - When using Edit Data, users are unable to send data with members that contain an apostrophe in the description (alias). 04-01-0161 - When interacting with reports with read-only access, users are prompted to save reports. 04-01-0183 - Analyzer server crashes if a user attempts to define a cell note exceeding the 599 character limit. 04-02-0009 - Related Content links do not execute on relational (virtual cube) reports. 04-02-0012 =================================================================== Licensed Material - Program Property of IBM (c) Copyright IBM Corp. 1998, 2004. All Right Reserved. US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. IBM, DB2, and DB2 OLAP Server are trademarks of International Business Machines Corporation in the United States, other countries, or both. Portions (c) 1991-2004 Hyperion Solutions Corporation. All rights reserved. Hyperion is a registered trademark and Hyperion Solutions is a trademark of Hyperion Solutions Corporation. ===================================================================