Hyperion System 9 Shared Services Release 9.2 Readme

Hyperion System 9 Shared Services Release 9.2.0.3.0 Readme

1

Hyperion® System™ 9 Shared Services™ Release 9.2.0.3.0 Readme

This file contains the following sections:

Release 9.2.0.3 ........................................................................................................... 1 Purpose..................................................................................................................... 1 New Features ............................................................................................................ 1 Installation Instructions ........................................................................................... 2 Known Issues............................................................................................................ 2 Documentation Updates ............................................................................................ 8

Release 9.2.0.2 ......................................................................................................... 10 Defects Fixed .......................................................................................................... 10 Known Issues.......................................................................................................... 11 Other Updates ......................................................................................................... 12

Release 9.2.0.1 ......................................................................................................... 13 New Features .......................................................................................................... 13 Installation Updates................................................................................................ 17 Known Issues.......................................................................................................... 23

Release 9.2.0.3

Purpose

This service pack addresses defects and provides new features. It applies only to Shared Services 9.2.0.3, 9.2.0.2, 9.2.0.1, and 9.2.0.

This document includes important, late-breaking information about this release of Hyperion System 9 Shared Services. Review this information thoroughly before installing Shared Services and License Server.

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

Top

New Features

Shared Services Release 9.2.0.3 includes several new features related to security and user provisioning. For detailed information about these features, see the Hyperion System 9 Release 9.2.0.3 Documentation Addendum. This document is provided in the Shared Services


2

Installation Documentation zip file on Hyperion Download Center and on the Shared Services DVD.

Top

Installation Instructions

1. Download the Shared Services 9.2.0.3 installer from Hyperion Download Center.

2. Install Shared Services according to the instructions in the Shared Services Installation Guide provided in the Installation Documentation ZIP file on the same Hyperion Download Center page. You can install over the existing installation (9.2.0, 9.2.0.1, or 9.2.0.2). If the existing installation is earlier than release 9.2.0, you must first install release 9.2.0 before installing this release.

Note: If you are running version 9.0.0 or later, you do not need to upgrade Hyperion License Server.

3. Launch Hyperion Configuration Utility and select Shared Services as the product to configure.

4. Select database configuration and application server deployment as the configuration tasks to perform.

5. For database configuration, when prompted, choose the option to reuse data from the existing repository.

6. Redeploy to the application server.

7. Restart Shared Services.

8. After installing service packs for other Hyperion System 9 products, use Hyperion Configuration Utility to re-register those products with Shared Services.

Top

Known Issues

Every effort was made to ensure that Shared Services performs without problems. However, these issues remain at release time. Temporary solutions are provided when appropriate. Numbers in parentheses are internal reference numbers for Hyperion Solutions.

• Shared Services does not support the provisioning of MSAD groups if the group membership (sum of user and group members within the group) exceeds 1500 (MSAD on Windows 2003) and 1000 (MSAD on Windows 2000). Group members do not inherit the provisioning relationship assigned to the group. A workaround is to split the group into smaller groups such that their membership does not exceed the range retrieval limit of Shared Services. The limit is 1500 (MSAD on Windows 2003) and 1000 (MSAD on Windows 2000). (8-582895507, 8-580209841)


3

• For the Import/Export Utility, the Shared Services Installation Guide states that the export.producttype property supports the asterisk character (*). The example expression provided, however, is incorrect. To export product roles, either use the asterisk character as shown in the first of the following expressions or provide the product name and version, for example:

YES: export.producttype=*

YES: export.producttype=HP-1.0.0,HFM-7.1.2

NO: export.producttype=HFM*, Essbase*

(8-563504560)

• For WebLogic Express 8.1.4, the PATH variable is not updating correctly after Shared Services is installed as a service.

This is the PATH variable after installing Shared Services as a service:

C:\bea\WEBLOG~1\server\bin;C:\bea\jdk142_05\bin

The path is missing the Hyperion-specific parts and results in issues with adding additional providers. To resolve this issue, you must manually set the PATH variable to this:

PATH=%PATH%;%HYPERION_HOME%\common\CSS\9.2.0\bin

The resulting PATH variable is then set correctly:

C:\Hyperion\common\CSS\9.2.0\bin;C:\Hyperion\common\SAP\bin;;C:\bea\WEBLOG~1\server\bin;C:\bea\JROCKI~1\jre\bin;C:\bea\JROCKI~1\bin;C:\Oracle\product\9.2.0\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Tools;C:\Hyperion\common\CSS\9.2.0\bin;C:\Hyperion\common\ODBC\Merant\5.1\Drivers;C:\Hyperion\SharedServices\9.2\openLDAP;C:\bea\WEBLOG~1\server\bin\oci920_8

(8-554338104)

• When saving a taskflow with Scheduler information, a “Failure occurred during job recovery” error message displays and the taskflow is not created. The current version of workflow uses Quartz version 1.3 for its Scheduler. Versions 1.5 and earlier of Quartz have a known issue with SQL Server 2005. A workaround is to set up the database with case-insensitive mode. (8-536419401)

• If Shared Services is installed on a computer that is in a different time zone from the product server (more than 8 hours difference), configuration fails. To fix this problem you must adjust the token timeout setting in the external authentication configuration file (CSS.xml) so it is greater than 960.

To change the token timeout setting:

1. Using a text editor, open CSS.xml file.

This file is located in <HSS_HOME>/AppServer/InstalledApps/<App_server_name>/<App_server_versio


4

n/> directory. For example, C:\Hyperion\SharedServices\9.2\AppServer\InstalledApps\WebLogic\8.1 (for WebLogic 8.1 running on Windows) and /app/Hyperion/SharedServices/9.2/AppServer/InstalledApps/WebLogic/8.1 (for WebLogic 8.1 running on UNIX).

2. Change the value for token timeout to a value greater than 960 (the default value is 480).

<token>

<timeout>1000</timeout>

</token>

3. Save and close the CSS.xml file.

4. Restart Shared Services AND Hyperion products referencing the Shared Services external authentication configuration (including restarting Hyperion product services and servlets).

(8-527398085)

• Need to have a configurable timeout for resolving SAP keystore file. By default, Shared Services uses 10 seconds as the timeout for resolving SAP keystore file. You can override this value from the Shared Services configuration file.

To change the timeout for resolving SAP keystore file:

1. Using a text editor, open CSS.xml file.

This file is located in <HSS_HOME>/AppServer/InstalledApps/<App_server_name>/<App_server_version/> directory. For example, C:\Hyperion\SharedServices\9.2\AppServer\InstalledApps\WebLogic\8.1 (for WebLogic 8.1 running on Windows) and /app/Hyperion/SharedServices/9.2/AppServer/InstalledApps/WebLogic/8.1 (for WebLogic 8.1 running on UNIX).

2. Insert the following code into the SAP provider definition. This code must be placed immediately after the token timeout declaration.

<keystore>

<timeout><interval></timeout>

</keystore>

Be sure to replace <interval> with the desired keystore timeout interval in seconds. For example, <timeout>22</timeout> to set the interval to 22 seconds.

3. Save and close the CSS.xml file.


5

4. Restart the application server if it is running.

(8-519869039)

• When deploying the Oracle Web Application, ensure that you keep the bsf.jar and rhino.jar files in the classpath. The jar files are available in the following location:

%ORACLE-HOME%\j2ee\home\applications\SharedServices\SharedServices\WEB-INF\lib

Replace %ORACLE-HOME% with the full installation location of Oracle 10g Application Server. (8-546622001)

• The transaction log files for the OpenLDAP database (located in the <HSS_HOME>\OpenLDAP\var\openldap-data folder) become too large too fast and, if not properly maintained, disk space could run out unexpectedly.

For all platforms except for AIX, a workaround is to avoid generating OpenLDAP transaction logs by creating a configuration file and adding these configuration settings:

WARNING: If this configuration is used and the OpenLDAP database crashes, you cannot perform a catastrophic recovery.

1. Create a configuration file named DB_CONFIG in the <HSS_HOME>\OpenLDAP\var\openldap-data folder.

2. Add these flags to the file and save it:

• set_flags DB_TXN_NOSYNC

• set_flags DB_TXN_NOT_DURABLE

(8-505842531)

• When browser settings are set to Simplified Chinese, some text in the Shared Services External Authentication Configuration Console is not translated. The text is displaying in English instead. (8-580297496)

• While configuring external user directories in Turkish, ensure that you enter user and group URLs exactly as their values are specified in the user directory. Although the value of node names contained in user and group URLs are not case-sensitive, the use of letter i is case-sensitive if you are using Turkish version of Shared Services. For example, OU=aTurkishCo is not identical to OU=aTurkIshCo. (8-573534761)

• On an HP-UX 64-bit platform with Tomcat, a blank page displays when you attempt to change the Native Directory password in the Shared Services External Authentication Configuration Console. This issue is not observed with Weblogic 8.1.4. There is no known workaround for changing the password. You must use the default password. (8-579548531, 8-579335921)

• When using User Management Console on a Japanese locale, you may experience a Javascript error when you click Refresh. If this occurs, expand the project node and click Refresh again. (8-578263027)


6

• If using the Import/Export Utility to update provisioning data with multiple roles by importing from a CSV file, only one role will be updated. All other roles will not be updated. If you update provisioning data with a single role by importing from a CSV file, provisioning data will update successfully. (8-563909351)

• The Import/Export Utility fails to de-provision the user or group from other roles if the user defined role also provisioned to the user is deleted during import. Similarly, the Import/Export Utility fails to unassign the users or groups from a Native Group if one of the native users or groups assigned to it is deleted during import. (1-243987391)

• Searches are not supported at the sub-tree level of the user URL. Currently, searches are only supported at the user URL level. Also, the sub-tree scope is not supported for other features like groupfilter, loginAttribute, emailAttribute, and so on. (8-568725452)

• Sometimes projects disappear in Shared Services. If this occurs, restart Shared Services and Financial Management. Then you will be able to see the Projects once again in Shared Services. (8-582196101)

• When using the migration utility to migrate Hyperion Home on a Windows Vista system, the migration freezes and fails to delete the files and folders in the old location. A workaround is to delete the HYPERION_HOME environment variable and then install the client software being used, specifying a new HYPERION_HOME location. (8-578566471)

• Sun One LDAP Directory Server does not provide an option to move users across OUs. However, it provides the option to Cut ’n’ Paste user accounts across OUs. The Cut 'n' Paste process creates a new user account and invalidates the provisioning data in OpenLDAP.

To preserve the provisioning data of users when using Cut 'n' Paste to move users across OUs, use this workaround:

1. Install Shared Services Release 9.2.0.3.

2. Run the updateNativeDir utility to collect the Login attribute.

3. Move the users in Sun One LDAP Directory Server from one OU to another using the cut and paste option in the Sun Directory Service Control Center (DSCC).

4. Run the updateNativeDir utility.

5. Verify the Provisioning information and login attribute in the openLDAP.

(8-582247261)

• The following utilities do not work for HP-UX for OpenLDAP:

o Db_recover

o Db_archive

o Db_checkpoint

A workaround is to create a directory, manually make symbolic links to the libraries, and then run the utilities. Follow these steps:


7

1. As a privileged user, create a directory. For example:

# mkdir –p /raja/bdbbinaries

2. Then cd to the new /raja/bdbbinaries directory and create a symbolic link to the lib directory using this command:

# ln –s /hypbiprd/Hyperion/SharedServices/9.3/openLDAP/usr/local/bdb/lib .

Note: In the preceding command there’s a space after lib followed by a period.

The resulting directory listing of the /raja/bdbbinaries directory should look similar to the following listing:

drwxrwxrwx 2 root sys 96 May 2 10:07 .

drwxrwxrwx 3 root sys 96 May 2 10:07 ..

lrwxrwxrwx 1 root sys 70 May 2 10:07 lib -> /hypbiprd/Hyperion/SharedServices/9.3/openLDAP/usr/local/bdb/lib

(SR 8-594696061)

• If upgrading from Release 9.2.0.2 to Release 9.2.0.3, you cannot run Hyperion Configuration Utility without manual intervention. A workaround is to remove the older product folder under common/config/product. For example, there may be common/config/product/xx/9.2.0.2 and common/config/product/xx/9.2.0.3 )where xx is one of the Hyperion products); remove the folder xx/9.2.0.2 in this case. (8-581523001)

• In the Shared Services User Management Console, you may get the following error message when you select a user or group in an external directory:

"Selected user doesn't exist or has been deleted by another user"

This occurs because the user and/or group resides directly under the BASE DN setting in the external provider. If you get this error message, try these workarounds:

Split the BASE DN and set a user and a group URL. For example, if the base DN was set to ou=Hyperion,dc=mycompany,dc=com, then set the base DN to dc=mycompany,dc=com and set the user DN and group DN to ou=Hyperion.

If the error still occurs, set the identity attribute to nsuniqueid for LDAP or objectGUID for MSAD and migrate the identities in all Hyperion products as described in the Shared Services 9.2.0.3 Documentation Addendum.

(8-588240161)

Top


8

Documentation Updates

• All documentation for new features, enhancements, and fixed defects for System 9 security and user provisioning is contained in the Hyperion System 9 Shared Services Documentation Addendum. This document is provided with the Shared Services Installation Documentation zip file on Hyperion Download Center and on the Shared Services DVD.

• The following information updates the system requirements documentation in the Shared Services Installation Guide from Release 9.2.0:

o For AIX 5.2, ML7 is required.

o For AIX 5.3, ML3 is required.

o Windows Vista is now supported as a client operating system.

o Internet Explorer 7 is now supported as a Web browser.

o Firefox 2.0.0.3 is now supported as a Web browser.

o JDBC MySQL 3.0.8 is now required.

o IBM DB2 8.1 FP 7a / 8.2 is now required.

o Microsoft SQL Server 2000 SP3a and 2005 SP1.

o Domino LDAP 5.x is no longer supported as an authentication source.

o JDK – Server requirement:

1.4.2_13 (Windows/Solaris/Linux)

1.4.2_12 (HP-UX RISC and Itanium)

1.4.2 SR7 ca142-20061124 (AIX)

o JRE – Server requirement:

1.4.2_13 (Windows/Solaris/Linux)

1.4.2_12 (HP-UX RISC and Itanium)

1.4.2 SR7 ca142-20061124 (AIX)

o Browser Plug-in JVM requirement:

1.4.2_13 (Default)

• On page 130 of the Shared Services Release 9.2 Installation Guide, under “Setting Up SSL on OpenLDAP,” this link is referenced:

http://www.openldap.org/pub/ksoper/OpenLDAP_TLS_howto.html

The link is old and the paper has been classified as obsolete. OpenLDAP users should, instead, consult the OpenLDAP Administrator's Guide for a detailed and up-to-date discussion of TLS/SSL use in OpenLDAP Software. (8-553764381)

• You may experience a problem in Internet Explorer 7 and Vista launching help. The new security in Internet Explorer prevents pop ups and, therefore, may prevent a Hyperion help

http://www.openldap.org/pub/ksoper/OpenLDAP_TLS_howto.html

http://www.openldap.org/doc/admin23/


9

system from launching correctly. If this problem occurs, you must disable Java or JavaScript in Internet Explorer.

To disable Java in Internet Explorer, follow these steps:

1. From the Tools menu, select Internet Options.

2. Click the Programs tab.

3. Click Manage Add-ons.

4. Highlight Java Plug-in.

5. Under Settings, select Disable.

6. Click OK, and then OK again.

To disable JavaScript in Internet Explorer, follow these steps:

1. From the Tools menu, select Internet Options.

2. Click the Security tab.

3. Click Custom Level.

4. Scroll to the “Scripting” section of the list. Click Disable.

5. Close and restart your browser.

• Changes to the Hyperion System 9 Shared Services Documentation Addendum:

o The statement that after migration the value of IDMIGRATION is changed is incorrect. The IDMIGRATION setting remains unchanged.

o The spelling of FORCEDMIGRATION is incorrect. The correct spelling is FORCEMIGRATION.

• When Analytic Services cannot migrate a user or group, it logs a message citing the reason in \Hyperion_Home\AnalyticServices\essbase.log.

• When using Hyperion Configuration Utility to configure a database, for the database name, you can enter only English alphanumeric characters and the dash character (-).

• On page 107 of the Hyperion System 9 Shared Services Installation Guide, the value of “password” is expressed in Japanese KATAKANA so that some users cannot log in. To obtain the correct password value, please check the English version of this guide on the Oracle Technology Network (OTN) Web site (http://www.oracle.com/technology/index.html).

Top

http://www.oracle.com/technology/index.html


10

Release 9.2.0.2

Defects Fixed

This service pack addresses the following defects:

If a Financial Management cluster name includes Japanese or Korean characters, when selecting a Financial Management application in User Management Console, the provisioning screen does not open. (1-281297381)

When loading a large security load in Financial Management, errors are returned due to a communication error between Financial Management and the external user directory. (1-397190392)

An LDAP user who logs into User Management Console may be given more permissions than he/she is granted. This problem occurs because the roles associated with a sibling group of the user’s group are being granted to the user. (1-421279962)

When assigning users to groups in nested Organizational Units (OUs), Shared Services does not display the complete group membership information. It only displays the group membership information defined at the top level OU. (8-514570481)

Where circular group memberships exist at nested levels, accurate group membership information is not being retrieved. An example of a nested relationship is where Group A is defined as a member of Group B and Group B is defined as a member of Group A. A user is assigned to be a member of Group A. Group A is in turn a member of another group (this is a nested group membership structure). Under these conditions, the user's group membership to A will not be displayed within Shared Services because A has a circular membership with B. (8-514460561)

Where circular group memberships exist (Group A as a member of Group B and Group B as a member of Group A) and you are provisioning, the system freezes when group membership APIs are being called within Hyperion System 9. (8-518992111)

Where users have identical common names, internal processing errors occur during provisioning due to the way in which Shared Services searches for those users. (8-515497407)

Where circular group memberships exist, out-of-memory exceptions are generated. (1-287556363)

Shared Services cannot communicate with other Hyperion products over a Secure Sockets Layer (SSL). (8-518242551)

Group filters do not work for LDAP. (8-516104499)

During product upgrade, when the products re-register as part of the upgrade process, the registered roles are not being updated with the upgraded product version. Therefore, administrators cannot view the roles associated with the upgraded product in the Shared Services interface. (8-515699672)


11

Analytic Services freezes when concurrent CSS calls are made during authentication. (8-514945354)

If a user is assigned to groups in a nested organizational unit, those group relationships are not getting processed within Shared Services. (8-519761621)

Users are not being successfully provisioned under the following condition: they exist in external directories that are configured in the CSS configuration file after another provider has been configured where circular group relationships exist. For example, the configuration file specifies these directories in the following order: MSAD1, LDAP1. If MSAD1 contains circular group relationships, users defined in LDAP1 will not be provisioned. (8-514842831)

When logging into Hyperion System 9, users belonging to groups that have circular references do not show any roles associated with those circular groups. (8-513602014)

In groups where circular relationships exist at the root level, group hierarchy information is incorrect. (8-511658125)

If circular group relationships exist, login to Planning and BI+ freezes. (8-509766681)

If circular group relationships exist, APIs are not returning accurate group membership information. (8-518992126)

If today’s date is greater than the maintenance date in the license file, you will get a CLS00009 “Your software maintenance agreement has expired” error message. If the maintenance has expired, you should be able to install and configure any version of the software that was available before it expired. (8-521748003)

Top

Known Issues


The security platform times out intermittently in very distributed environments where external repositories like MSAD and LDAP are in a different geographic location than Shared Services. For optimal performance, Hyperion recommends that the external repository be co-located in the same LAN environment. (8-522830181)

Access control lists in Hyperion products are not listing users and groups if an LDAP group that contains LDAP groups belongs to a Shared Services native group that is provisioned. If you do not see users that belong to a child group, create another Native Group and provision that group directly. (8-519896476)

If you are working with a large number of users or groups, you may need to increase the Java Runtime heapsize. (8-523280181, 8-523280151, 8-523525530)

A utility, called UpdateNativeDirectory, updates the Hyperion Native Directory with updated data from external providers. This utility updates external user and group identities in the Hyperion Native Directory for those objects that have moved in the external directory. This


12

utility is only available to specific customers who have experienced this issue. (8-524040331)

Top

Other Updates

In addition to the Oracle database versions supported by Shared Services as documented in the 9.0.0 installation guide, Shared Services also supports Oracle 10.2.0.2.

In Shared Services User Management Console, project names that start with the less than symbol (<), for example <my_project, do not appear in the Provisioning screen. Hyperion recommends that you do not create project names that start with a less-than character. (8-505959028)

Top


13

Release 9.2.0.1

New Features

This section lists the new features on 9.x codeline:

New Features in 9.2

Import/Export Utility for Provisioning Data This release includes a command-line utility that enables you to export, import, and validate user provisioning data in the native OpenLDAP directory. You can use the utility to create, modify, and delete users, groups, and roles that originate from the native user directory bundled with Shared Services, and you can modify relationship data for users/groups who are stored externally.

The utility is installed to <HYPERION_HOME>/common/utilities/CSSImportExportUtility. See the Shared Services Installation Guide for instructions on using the utility.

Support for SAP Provider Shared Services now supports single sign-on (SSO) to Hyperion applications from SAP using an existing SAP provider. This enables users defined in a SAP user store to navigate seamlessly between SAP (SAP Enterprise Portal, SAP R/3, and SAP BW) and Hyperion applications. You use Shared Services External Authentication Configuration Console to configure the SAP provider for external authentication.

Unicode-enabled SAP is not supported. See “SAP Configuration” in the Known Issues section for other important considerations about using SAP.

Removing Applications within Shared Services You can now deregister or temporarily disable an application within the Shared Services User Management Console. When you remove an application, all metadata information and provisioning relationships are removed, and the application is no longer registered with Shared Services. This operation should be used only if the application has been uninstalled, and there is no way to deregister or delete the application from the product.

To remove an application from Shared Services:

1. In User Management Console, select the application.

2. Right-click and select Delete.

New Features in 9.0.1

Licensing Support for Multiple Deployment IDs This feature allows you to combine multiple deployments of a product, as licensed with multiple Deployment IDs, within a single installation. For more information about Multiple Deployment IDs, see the Shared Services Installation Guide.


14

New Features in 9.0.0

Hyperion System 9 Shared Services Hyperion Hub functionality is now part of Hyperion System 9 Shared Services. Shared Services enables the following features in the Hyperion System 9 family:

User provisioning

External authentication definition

Metadata synchronization

Data synchronization

Task flow management

User provisioning functionality is described in the Hyperion System 9 Shared Services User Management Guide available on the Hyperion Download Center. External authentication definition is described in the Hyperion System 9 Shared Services Installation Guide available on the Hyperion Download Center. All other Shared Services functionality is described in the administrator’s and user’s guides for the products that implement Shared Services.

Hyperion System 9 Hyperion System 9 is a comprehensive Business Performance Management system. It integrates financial applications with a business intelligence platform to provide a modular system that adapts to any business need.

The major components of Hyperion System 9 are Hyperion System 9 Foundation Services™, Hyperion System 9 Applications+™, and Hyperion System 9 BI+™.

Hyperion System 9 Foundation Services is a base of common technologies that ease the installation and configuration process. It includes Shared Services, Hyperion System 9 Smart View for Office™, Hyperion System 9 Application Link™, Hyperion System 9 Master Data Management Services™, and Hyperion System 9 Business Rules™.

Hyperion System 9 Applications+ is a set of packaged applications for planning, consolidation, and scorecarding.

Hyperion System 9 BI+ is a comprehensive business intelligence platform. It provides management reporting and analysis from any data source, including transactional systems, data warehouses, Hyperion System 9 BI+ Analytic Integration Connector for SAP BW™, Hyperion System 9 BI+ Analytic Services™, and Hyperion financial applications.

Hyperion System 9 BI+ offerings:

User interaction with all types of information in one environment―report viewing, report processing and queries that include parameters, and using dynamic dashboards to view and interact with content

The richly interactive BI+ user interface, which serves as one thin client for reporting, analysis, and metrics management


15

The broadest set of modular BI functionality in the market, including production reporting, financial reporting, ad hoc query and analysis, and advanced analytics

Seamless integration and interaction with Microsoft Office

Flexible and complete content access, which integrates third-party content with Hyperion content in an easy to use interface

Capabilities including subscription notifications, favorites, and scheduling options to support a wide range of application uses

Integration with the full Foundation Services for central provisioning and management of all Hyperion System 9 users

Hyperion System 9 BI+ Module descriptions:

Hyperion System 9 BI+ Essbase Analytics™ and Hyperion System 9 BI+ Enterprise Analytics™—Collectively referred to as Analytic Services; provides powerful OLAP capabilities for high performance multidimensional reporting, analysis, and modeling

Hyperion System 9 BI+ Interactive Reporting™—Self-service, ad hoc query and analysis for relational databases that enable users to pivot interactively, and to slice and drill from summary to detailed data

Hyperion System 9 BI+ Production Reporting™—Visually clear, high volume, enterprise reporting with parameters

Hyperion System 9 BI+ Financial Reporting™—Highly formatted financial reports with access to Applications+, Analytic Services, and Analytic Integration Connector for SAP BW

Hyperion System 9 BI+ Web Analysis™—Interactive, visualization and reporting against Analytic Services, Applications+, and Analytic Integration Connector for SAP BW

Hyperion System 9 BI+ Enterprise Metrics™—Enterprise wide metrics management and analysis delivered through personalized, interactive dashboards

Hyperion License Server™ Hyperion uses a common license server to provide you with a uniform and consistent method of governing the use of your Hyperion products. Hyperion License Server uses a license file specific to your site to assist you in tracking and monitoring the following information:

The products that you purchased

Your feature options

The number of users that can access each product

The expiration dates of your license and maintenance agreements

Hyperion License Server uses a third-party component to provide a centrally managed administrative tool for managing your software licenses and ensuring license compliance.


16

Because Hyperion License Server is a process, not a physical server, it need not be installed on a dedicated computer. Hyperion License Server can be installed on a shared computer, so you can install it in an environment that enables the most efficient use of resources.

For more information about Hyperion License Server, see the Hyperion System 9 Shared Services Installation Guide available on the Hyperion Download Center.

Hyperion System 9 Shared Services User Management Shared Services User Management enables centralized management of user access rights and accessibility to applications created under various projects of different products. The user management process allows the administrator or delegated administrator to associate users and groups to projects and give them roles in that application.

User IDs and groups may exist in various authentication systems and also within products in an existing installation. Also, you can create users and groups and roles at the native level. Every product has product-specific roles defined at the product level.

A project may contain one or more applications. Users or groups can be associated with an application and can be assigned one or more roles per application.

For additional information about Shared Services user management, see the Hyperion System 9 Shared Services User Management Guide available on the Hyperion Download Center.

Hyperion Configuration Utility™ This release of Shared Services uses the Hyperion Configuration Utility to guide you through a series of screens to complete the following configuration tasks:

Product license activation

Configuration of relational databases as data sources

Automatic deployment of Shared Services to application servers

The Configuration Utility may also display additional product-specific options.

You can launch Hyperion Configuration Utility from the final screen of each product installer or from Start > Programs > Hyperion System 9 Foundation > Configuration Utility. Hyperion Configuration Utility also enables you to reconfigure Hyperion products. The reconfiguration process is similar to the initial process. For details, see the Hyperion System 9 Shared Services Installation Guide available on the Hyperion Download Center.

Support for Application System Members When Managing Models Application system members store critical system information such as currency rates and ownership information. Each product has certain application system members that, when exported to Shared Services, are displayed in the model hierarchy.

You can view the details and properties of an application system member; however you cannot delete, edit, add children to, or rename an application system member in Shared Services.

Application system members are filtered out of the hierarchy if they are not relevant to the product being viewed. The compare operation filters out application system members that are not valid for your product. For example, if you are viewing Hyperion System 9 Financial


17

Management™ models, Shared Services filters out application system members that are not valid for Financial Management.

For additional information about application system members, see the administrator’s or user’s guides for the Hyperion products that support managing Shared Services models.

Support for Running Programs on the Command Line When Managing Taskflows Shared Services provides a mechanism for executing external programs from a command line.

For additional information about running programs from a command line, see the Hyperion System 9 Financial Management Administrator’s Guide available on the Hyperion Download Center.

Password Encryption in the External Authentication Configuration File Passwords are now encrypted in the external authentication configuration file (CSS.xml).

Note: Do not edit the external authentication configuration file in a text editor. Instead, use the External Authentication Configuration Console to manage external authentication providers in your Hyperion environment.

Top

Installation Updates

The section includes important information about installing this release of Shared Services. For a complete list of supported platforms and other software requirements and for complete installation instructions, see the Hyperion System 9 Shared Services Installation Guide available on the Hyperion Download Center.

Note: Numbers in parentheses are internal reference numbers for Hyperion Solutions.

Upgrade Considerations

The following information updates the documentation on upgrading to this release of Shared Services.

Upgrading from Shared Services Release 9.0.0 When upgrading from Shared Services release 9.0.0 to 9.2.0 on Windows, you must

uninstall release 9.0.0 before upgrading to 9.2.0. Overinstalling is not supported due to a change in the OpenLDAP Windows service names between release 9.0.0 and 9.2.0. Uninstalling release 9.0.0 before upgrading ensures that the OpenLDAP service starts appropriately. (1-276747391)

When running the Hyperion Configuration Utility after upgrading products to release 9.2.0, the product selection page may display multiple listings for a product or may not list the product you are trying to configure. If this problem occurs, perform these steps:

1. Navigate to the following directory: (Windows): <HYPERION_HOME>\common\config\product\<product>


18

(UNIX): <HYPERION_HOME>/common/config/product/<product> Where <HYPERION_HOME> is the Hyperion Home location on the machine and <product> is the product name or abbreviation, for example: c:\hyperion\common\config\product\planning

2. Delete the oldest *.xml file from this directory. For example, if the directory contains two files named planning_1.xml and planning_2.xml, delete the older file.

3. Re-run the Configuration Utility.

Upgrading with Manual Deployment from Shared Services Release 9.0.1 When upgrading from Shared Services release 9.0.1 to 9.2.0 with manual application server deployment, you must run the Hyperion Configuration Utility after manual deployment to reconfigure the database used with Shared Services. Follow these steps after manual deployment:

1. Launch the Configuration Utility.

2. Choose “Relational Storage Configuration” as the task to perform.

3. Specify the current database password and choose to reuse existing data. If you choose the option to drop data, all current provisioning data is lost.

Platform Support

Supported platforms are listed in the Shared Services Installation Guide.

Updates to the documentation:

On AIX 5.2, FP4 is required for Shared Services server.

Shared Services supports IBM DB2 8.1 FP 7a / 8.2.

Shared Services supports Microsoft SQL Server 2000 SP3a and 2005 SP1.

Processor Support

Unless specifically stated in the installation documentation, Hyperion products operate on processors that are supported by the operating system. See the “Planning the Shared Services Installation” chapter in the installation guide for information about processor support.

Support for Third-Party Products

Shared Services 9.2 is the last release to support:

Firefox 1.0.7

Oracle Application Server 10G – 9.0.4


19

JDK Server 1.4.2_08

JRE Server 1.4.2_08

Browser Plug-in JVM 1.3.1_17

In addition, BEA WebLogic Application Server Version 7.0 is not supported with this release.

Configuration Utility Documentation Updates

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 (.)

When using the Configuration Utility to automatically deploy to an application server, you cannot enter a dash character (-) in the ServerName field. For WebLogic only, you also cannot use the dash character in the Domain field.

Installing as Root on HP-UX 64-Bit

When installing Shared Services on the HP-UX 64-bit platform, you must install as the root user. If you do not install as root, JDK is not installed properly. (1-175866370, 1-176548603)

Hyperion System 9 Installation Changes

The installation and configuration process changed significantly for System 9 release. Installing Shared Services is now required. To successfully install Shared Services you must follow a sequence of steps. The steps are included in the Hyperion System 9 Installation Start Here and in the Shared Services Installation Sequence chapter of the Hyperion System 9 Shared Services Installation Guide. These documents are available on the Hyperion Download Center.

Hyperion License Server

Note About Backward or Forward Compatibility with Hyperion License Server Hyperion License Server for Hyperion Essbase Release 7.1.2 and Release 7.1.3 will not function with Analytic Services Release 9.2; neither will Hyperion License Server for Analytic Services Release 9.x function with Hyperion Essbase Release 7.1.2, 7.1.3, or 7.1.5.

Application Server Deployments

Oracle 10g Application Server Deployment (Manual Only) This information updates the documentation in the Shared Services Installation Guide for manually deploying to Oracle 10g application server.

1. Download the Shared Services installer from Hyperion Download Center or from the CD.


20

2. Follow the instructions in the Shared Services Installation Guide (“Manual Configuration of the Web Environment” chapter) to install and manually deploy Shared Services to Oracle 10g.

3. Stop the application/application server.

4. Copy web.xml.oracle from this location: \HSS_Install_Location\AppServer\InstallableApps\other to this location: \OraHome1\j2ee\home\applications\SharedServices9\SharedServices9\ WEB-INF

5. Rename the existing web.xml in this location: \OraHome1\j2ee\home\applications\SharedServices9\SharedServices9\WEB-INF to: web.xml.back

6. Rename the copied web.xml.oracle in this location: \OraHome1\j2ee\home\applications\SharedServices9\SharedServices9\WEB-INF to: web.xml

7. Start the application/application server.

Application Server Manual Deployments When manually deploying application servers for Shared Services, you must manually create the SharedServices9\logs directory to enable Shared Services to start and function correctly. For example, C:\Hyperion\SharedServices\9.2\AppServer\InstallableApps\ common\SharedServices9\logs\. (1-123747677, 1-122876790)

Apache Tomcat Hyperion provides Apache Tomcat on the installation media for convenience if you want

to use it for your deployment. Hyperion does not own or maintain the Apache Tomcat application server and is not responsible for problems that you may encounter with its functionality. Hyperion, however, does fully support the use of Apache Tomcat in its products. In deployments where customers require high availability or failover, Hyperion recommends that you deploy a commercially supported application server where these capabilities are supported.

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


21

IBM WebSphere Application Server Deployments

WebSphere 6.0.2 Deployments If you see a JspTranslationException in User Management Console while performing operations, and Shared Services is deployed to WebSphere 6, ensure that the WebSphere version is 6.0.2.5.

Installing to Foreign Operating Systems

If you are installing Shared Services to a foreign operating system, you must install WebSphere application server FP6 for version 5.1.1. (1-125629152)

WebSphere ND Deployment The install does not automatically deploy Shared Services for WebSphere ND deployments. You must log on to the ND Manager console and follow the steps for manual deployment of the interop.war file.

AIX HTTP Transport Port Number

Deploying Shared Services 9.x for WebSphere application server on AIX can fail if the WebSphere sample applications are installed. In that case you get an error message stating that port 9091 is in use. To resolve this problem, perform the following steps:

1. Start the default server (usually server1).

2. Log into the management console (usually http://localhost:9090/admin).

3. Select the Server node.

4. Click the Application Server link.

5. Select the SharedServices9 server.

6. Click the Additional Property Web Container link.

7. Click the HTTP Transport link.

8. Click the link * for Port 9091.

9. Change the port number to 9099 or another free port.

10. Click OK to apply the change and return to the previous menu.

11. Select the menu item Save to save the change you just made.

12. You can now stop server1 and start the SharedServices9 server.

(6-CIS-664)

Shared Services Freezes During Database Configuration If you are deploying Shared Services on WebSphere and the system appears to freeze while configuring the Shared Services database, follow these steps:

1. Log into the WebSphere Admin Console.

http://localhost:9090/admin


22

2. Keep this session active.

3. Save the Shared Services database configuration again.

Native Library Path Location

For manual WebSphere application server deployments, the Shared Services Installation Guide provides an incorrect location for the Native Library Path. The correct location is %HYPERION_HOME%\common\CSS\9.2.0\bin.

Troubleshooting Manual WebSphere Application Server Deployments

After manually deploying WebSphere application server, if you are unable to start Shared Services or log on to the External Authentication Configuration Console:

1. Add HYPERION_HOME\common\CSS\9.2.0\bin to the PATH environment variable.

2. Review the following log file for errors:

For WebSphere 5.1.1: WEBSPHERE\WebSphere\AppServer\logs\server1\SystemOut.log

For WebSphere 6.0.2: WEBSPHERE\WebSphere\AppServer\profiles\default\logs\server1\ SystemOut.log

3. Restart the WebSphere server application.

Configuring External Authentication for Hyperion Products

Shared Services supports external directories for user authentication. To use Shared Services with other Hyperion products, all Hyperion products must be configured to use external authentication. You must use the External Authentication Configuration Console to manage external authentication providers in your Hyperion environment.

Additionally, you must install and configure Shared Services for external authentication first. The applications should be subsequently configured to use the configuration created by Shared Services.

Details on using the External Authentication Configuration Console to configure external authentication for Shared Services can be found in the Hyperion System 9 Shared Services Installation Guide. You can find this guide on your product CD or in the Installation Documentation Zip file on the Hyperion Download Center.

Evaluating the .hyperion.hostname UNIX File Before Starting Shared Services

On UNIX systems, Shared Services stores common environment settings in a file called hyperion.<<short hostname>>*, which is created in the installing user’s home directory. The .hyperion.<<short hostname>> file enables a user, whose home directory is shared by multiple computers, for example using NFS, to isolate environment settings per computer. This process ensures uniqueness.


23

(<<short hostname>> refers to the unqualified host name of the computer where Shared Services is installed; for example, myhostname versus myhostname.mydomain.com). The installing user’s current (interactive) shell must evaluate the variable declarations in this file before you start Shared Services.

The evaluation can be accomplished in various ways, depending on the installing user’s shell. Here are examples for Bourne compatible shells:

To cause evaluation of .hyperion.<<short hostname>> manually in the current shell:

(You must do this each time a Hyperion product is started or stopped.)

$ SHORT_HOSTNAME=`hostname | awk -F’.’ ‘{ print $1 }’` && export SHORT_HOSTNAME $ [ -f ${HOME}/.hyperion.${SHORT_HOSTNAME} ] &&\ > exec ${HOME}/.hyperion.${SHORT_HOSTNAME}

Or, more simply, but without error handling:

$ exec ${HOME}/.hyperion.<<short hostname>>

To evaluate {HOME}/.hyperion.<<short hostname>> automatically at login:

Add one of the previous examples to your login script (for example, .profile, .bashrc, or .login).

See the UNIX manual pages for exec, eval, and source or to your shell.

Note: Previous releases of Shared Services created and used a file called .hyperion. If this file is found during a software upgrade, the file contents are copied to the .hyperion.host file. The original file is saved as .hyperion.old.

Replicated OpenLDAP Environment Restriction

In a MASTER-SLAVE replicated OpenLDAP environment, creating or updating groups is not allowed when the master OpenLDAP server is down. (1-95998613)

Language Selection in Installer

On the Country Selection Panel in the installer, do not choose "Japan" as the language. If you are installing the product in Japan, choose the "Other" country option to ensure that the license panel in the installer displays correctly.

Top

Known Issues



24

Localization

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 with Shared Services in the Hyperion Configuration Utility, the Shared Services server name should be entered in English. (1- 215194141)

Some product installers display an incorrect translation of the Cancel button. (1-232246171)

On UNIX platforms, if you run an installer in graphical mode and see square blocks on the interface, run the installer in console mode. This problem occurs on Linux, AIX, and HP-UX for these locales: Japanese, Korean, Simplified Chinese, and Traditional Chinese. (1-225327495)

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)

Installing Shared Services in Traditional Chinese does not update the correct locale code in the cms.properties file. As a result, when the browser locale is not set, the Manage Models UI does not display in Traditional Chinese. A temporary solution is to open the cms.properties file from: \Hyperion\SharedServices\9.2\AppServer\InstalledApps\<App Server>\<Version Number>\ and modify the locale setting (cms.locale.language=zh) manually. (1-393129721)

On a Traditional Chinese operating system, during a custom Shared Services installation when MySQL is not already installed, the Browse button on the panel where you specify the MySQL location is not translated. (1-227893981)

Import/Export Utility: The Simplified Chinese configuration properties file value for importexport.locale is zh. For example, importexport.locale=zh.

Caution: Uninstalling Hyperion System 9 products on Japanese or Korean versions of Microsoft Windows using the Add/Remove program may cause an operating system crash. To avoid this potential problem when uninstalling, locate the uninstaller executable located in <HSS_HOME>\uninstall\ and double-click the executable to perform the uninstallation manually.

User Management Console does not open when launched from the Windows Start menu shortcut (Windows XP, Korean operating system, WebSphere 5.1.1.7 only). Use the URL http://localhost:58080/interop/index.jsp to launch the console instead of using the Start menu. (1-241779801)

On HP-UX 64-bit with a Korean locale, running the Hyperion License Server installer in console mode displays corrupted characters on the installer panels. (1-241513828)

http://localhost:58080/interop/index.jsp


25

On HP-UX 64-bit with a Korean locale, running the Hyperion License Server installer in console mode displays corrupted characters on the installer panels. (1-241513828)

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. (1-220188376)

On Solaris with a Brazilian locale, running the Shared Services installer or uninstaller in console mode does not display the language selection as Portuguese. (1-245301351)

On HP-UX 32-bit and 64-bit machines, set the LANG environment variable to English when running the Shared Services installer and the License Server installer. The installation does not work properly if LANG is set to Turkish. (1-245354751)

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, 1-397732171)

Using a Turkish Linux operating system, several languages on the Language Selection panel in the installer are incorrectly displayed in English instead of Turkish. (1-230485951)

On the Shared Services registration/deregistration panel in the Hyperion Configuration Utility, using a Turkish keyboard to enter an IP address in the Server text box does not work properly. You must specify the host name rather than the IP address in the Server text box. (1-220531027)

On a Turkish operating system, provisioning information is not exported when provisioning multiple MSAD users or groups. In addition, provisioning and deprovisioning MSAD users or groups intermittently does not work properly. (1-235582173)

When Shared Services is running on a Turkish operating system, MSAD users and groups cannot be provisioned. This problem occurs due to the manner in which uppercase I characters are converted on a Turkish OS. A temporary solution is to change uppercase I characters to lowercase i characters in the MSAD provider's URL and userDN fields. (1-216200323)

With a Turkish locale, if the domain name in an NTLM configuration in CSS.xml has a lowercase “i”, it will not list the users in the view pane. For example, <domain>vmwin2kturk</domain>. The temporary solution is to use only uppercase letters in the domain name. For example, <domain>VMWIN2KTURK</domain>. (1-245923981)

Using a Russian operating system, the OK button on the Language Selection panel in the installer is displayed in English rather than Russian. (1-228824221)

Using a Russian keyboard to press keyboard shortcuts in the installers and Configuration Utility does not work. (1-205984971)


26

Using a Russian operating system or a Simplified Chinese operating system on HP-UX Itanium, incorrect Russian characters are displayed when running the Configuration Utility, the Hyperion Home Migration Utility, or the Hyperion License Server installer in console mode. (1-206616898)

On AIX 5.2 with an Italian locale, the drop-down list on the Language Selection panel in the installer is displayed behind the display window. (1-242110895)

Installation/Configuration

After upgrading Shared Services from version 9.0.1 to version 9.2.0 on Windows Professional XP systems, duplicate entries are displayed in the menu shortcuts. (1-226243923)

To use Shared Services with an Oracle relational database, these privileges are the minimum required for the Shared Services Oracle database user:

o CONNECT

o RESOURCE

o CREATE SESSION

o CREATE TRIGGER

o DROP ANY TRIGGER

o ALTER ANY TRIGGER

(1-176866841)

Due to an InstallShield bug, if you attempt to install Shared Services on the same computer on which PC Anywhere is currently installed, Java Virtual Machine (JVM) does not get installed. Temporary Solution: Uninstall PC Anywhere before installing Shared Services. The JVM is installed along with the product. After you complete installing Shared Services, reinstall PC Anywhere.

When setting up a SQL Server database to use with Shared Services, your database must allow for native SQL Server authentication. (1-266503201)

Using Apache Tomcat on UNIX platforms, Application Server Deployment or Web Server Configuration tasks may fail if the temporary folder (as defined by the TEMP environment variable) contains *-build.xml files created by another user. Ensure that *-build.xml files do not exist in the temporary folder before running Hyperion Configuration Utility. (1-246275191)

Using WebSphere on UNIX platforms, Application Server Deployment or Web Server Configuration tasks may fail if the temporary folder (as defined by the TEMP environment variable) contains *-build.xml files created by another user. Ensure that *-build.xml files do not exist in the temporary folder before running Hyperion


27

Configuration Utility. In addition, you must delete the following files created by another user from the temporary folder:

o WEB-INF (folder)

o add_vhost_port.jacl

o script.jacl

o wsphere5-build.properties

o wsphere5-build.xml

Licensing

When deploying Named User licenses, if you reconfigure a product's Deployment ID after users have logged on (thereby "reserving" licenses for them), you need to remove the License Server linger file in order to unreserve them. To do so, delete HYSLDborrow, found in this location: On Windows: c:\Documents and Settings\All Users\Application Data\Macrovision\FLEXlm On UNIX: /var/tmp

On the Windows 2003 64-bit platform, if the License Server does not start and you have multiple license files in license folder, you need to combine the license files into a single file. To do so, first back up the original license files. Then copy all the INCREMENT lines from the second and subsequent license files and paste them at the end of the first license file. Then re-read the combined license into License Server. (1-112825276)

On the Windows 2003 64-bit platform, attempting to start License Server as a service returns an error, and the server is not started. A temporary solution is to start the server manually from a command-prompt window. (1-10Q21V)

After installing Hyperion License Server on AIX 5.3, the installer incorrectly creates two directories under Hyperion Home (e.g., /Hyperion/common/LicenseServer/Licenses and /Hyperion/commun/Licenserver/Licenses). When this occurs, edit the HYSLD.opt file in the /Hyperion/common/LicenseServer directory and change the path from “commun” to “common”. (1-225535511)

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


28

• 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

SAP Configuration

SAP Unicode known issues:

SAP Unicode is not supported. If Internet Explorer is used to connect to a Unicode SAP system for retrieval of user and role data, then single sign-on between Hyperion applications may be affected. This is due to the larger size of the SAP ticket and Internet Explorer limits on the “Query String”. A temporary solution is to use another supported browser, such as Firefox, to avoid the Internet Explorer limit.

The following issues pertain to Unicode-enabled SAP:

o SAP user names or passwords that contain the French µ character cannot be authenticated. (1-233496227)

o SAP user names that contain the German ß character cannot be authenticated. (1-227014411)

o You cannot log into the User Management Console as a Japanese user with the SAP provider. This problem occurs only in a SAP Unicode deployment. (1-233083235)

Secure Sockets Layer (SSL) and Secure Network Communications (SNC) are not supported with SAP in this release.

A list of SAP users and groups cannot be retrieved and cannot be authenticated if the application server is deployed as a Windows service. Use the following temporary solution for Tomcat, WebLogic 8.1.4, and WebSphere Application Server 5.1.1.7:

1. Set C:\Hyperion\common\SAP\bin to the system’s PATH environment variable.

2. Copy the dlls from C:\Hyperion\common\SAP\bin to C:\Hyperion\common\CSS\9.2.0\bin folder. This is to overcome the library.path not containing the SAP path.

3. Reboot the system. The updated system path setting is reflected for the service only after restart.

4. Start the service and access the application.


29

If deploying the application server as a non-service on Windows, no temporary solution is required. (1-238924916)

On HP-UX 64-bit systems, the tree is not loading in the browser pane after the admin user logs in using an SAP provider. Therefore, you must modify the Shared Services startup scripts for WebLogic and Tomcat with the following information:

o For a Tomcat deployment:

Modify the startSharedServices.sh script and change

JAVA_OPTIONS="$JAVA_OPTIONS -Dhyperion.home=/var/Hyperion

To

JAVA_OPTIONS="$JAVA_OPTIONS -Dhyperion.home=/var/Hyperion -d64

o For a WebLogic deployment:

Modify the startSharedServices.sh script and change

HUB_MEM_ARGS="-Xms256m -Xmx1024m"

To

HUB_MEM_ARGS="-d64 -Xms256m -Xmx1024m"

For both Tomcat and WebLogic deployments, you must give permissions to the SAP folder under $HYPERION_HOME/common/ as 775. For example, chmod –R 775 $HYPERION_HOME/common/SAP.

(1-245821916)

On UNIX, the library search path is not being set in the setSAPEnv.sh file. You must add the SAP libraries to the environment variable based on the platform:

LD_LIBRARY_PATH for Solaris, Linux SHLIB_PATH for HP-UX LIBPATH for AIX

(1-249429903)

When two SAP providers are listed in the search order, and if there are duplicate names in both providers, searching for a duplicate user from the second provider in the search order returns the user from the first provider. For example, if the search order specifies SAP1 and then SAP2, and the user ID “John” exists in both SAP1 and SAP2, searching for “John” from SAP2 returns “John” from SAP1 provider, because the SAP identity is stored on user name. In addition, if you provision a user from the first provider, the user in the second provider is assigned the roles provisioned to the user in the first provider. (1-221650230)


30

Import/Export Utility

The Import/Export Utility returns an incorrect error message when the properties file specifies a username that does not exist in any user directories configured for external authentication. For example, if you specify “importexport.username=jsmith” in the properties file, and “jsmith” does not exist in any configured user directories, the following error message is returned when you attempt to export:

User is found but could not authenticate

(1-235536554)

The Import/Export Utility returns an incorrect error message about an invalid username even when the properties file specifies a valid username and password. This problem occurs only when the “export.user.filter” value is blank. For example, upon export, the error is returned if the properties files contains:

importexport.username=admin importexport.password=password export.user.filter=

Where “admin” and “password” are valid.

The error message states:

Illegal or invalid userName passed in. Please check the argument.

(1-235480025)

External Authentication/User Provisioning

External Authentication Provider Names When adding or editing an external authentication provider, do not use the dot character

(.) in the provider name; for example, ldap.server. The User Management Console will not list the users and groups for a native or external provider if the provider name contains a dot. (1-119380193, 1-244837888)

When a provider name is “franÃƒÂ§aisÃƒÂ§”, users and groups are not displayed in the User Management Console view pane. (1-226070101)

Character Restriction in User/Group Names The following restrictions apply to user/group names:

The asterisk character (*) is not supported in any MSAD and LDAP user/group names.

The pound sign (#) is not supported for MSAD user/group URLs and OU in userDN for external authentication configurations.

The comma character (,) is supported for MSAD and LDAP user/group URLs and OU in userDN for external authentication configurations although you must escape the comma character with a backslash (\).


31

In the userDN for MSAD and LDAP external authentication configurations, the login user (for example, cn=test\\+user) with special characters is not supported.

Certain combinations of special characters are not supported in user/group names for MDAD, LDAP, and the native Shared Services (OpenLDAP) directory. For example:

test/\user1 test\/user1

The following characters are supported: ( ) ‘ “ \ / & + $ ^ = < > ; @

Empty Passwords

Users with empty passwords are not supported.

Character Restriction in Aggregated Role Names

The & (ampersand) character is not supported in aggregated (custom) role names. Do not use this character when creating aggregated roles in the User Management Console. (1-167957726)

Special Character Restriction in Project Names

The forward slash character (/) is not supported in project names.

You cannot modify or delete projects whose names that contain a percent sign (%) or a plus sign (+). (1-242546201)

MSAD

Microsoft Active Directory sp2 and earlier releases of Hyperion applications are known to have connectivity issues over SSL. To resolve such issues, refer to:

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

LDAP

If an LDAP provider is configured with an incorrect Group URL, group roles are not assigned to LDAP users who are part of the group when those users log into the User Management Console. (1-226070419)

HRAM and SSL on AIX

Hyperion Remote Authentication Module 9.x does not support SSL connections on AIX.

Miscellaneous

When editing users, groups, or roles in User Management Console, if you press the Enter key after selecting a user, group, or role to add, the selection is added and overwrites the existing members of the user, group, or role. (1-172185471)

If one server in a WebLogic server cluster is stopped, you may experience intermittent errors when performing provisioning tasks in User Management Console. For example, Move to and Copy functionality does not work correctly. (1-149158985, 1-149158950)

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


32

At times, when generating a provision report, Internet Explorer displays the following error message: "A script on this page is causing Internet Explorer to run slowly. If it continues to run, your computer may become unresponsive. Do you want to abort the script? Yes No"

If this error message displays, click No to continue. (1-121812101)

Do not delete projects that contain applications. Doing so removes all provisioning settings for all applications. Before deleting a project, assign the applications to another project. This maintains the user/group/role associations for each application within the project.

If two applications use duplicate names (belonging to different projects), and if a user is provisioned to both applications simultaneously, the screen that describes the provisioning summary lists the provisioning assignments only for the first application. This does not affect the provisioning assignments. (1-135627318)

Managing Models

This section describes information to consider when managing models.

Performance If using Apache Tomcat, the Work directory under the Tomcat directory may get full, thus causing performance to degrade. Should this happen, delete the following directory (and its contents):

\Tomcat\5.0.28\Work

Note: The Tomcat service needs to be stopped to delete it. The directory is automatically recreated.

Shared Models

The Tomcat memory settings may be updated to share models such as the accounts dimension. To do so:

Update the Startup.bat file in the Tomcat directory and set: JAVA_OPTS=-server -Xms256m -Xmx1024m and start Tomcat server in Console mode

Update the StartServices.bat file in the Tomcat directory and set: CATALINA_OPTS=-server -Xms256m -Xmx512m

Managing Data

This section describes information to consider when managing data.

Data Integrations

If you use an asterisk in the data integration member selector, the following error is displayed: “No Match found below the current selection. Try starting higher in the member list, or enter another value.”


33

Managing Taskflows

This section describes information to consider when managing taskflows.

Firefox is not supported when you use Events Services on Windows 2003. The workaround is to use Internet Explorer on Windows 2003, or use Firefox on either Windows 2000 or Windows XP.

Hyperion highly recommends that the locale used for creating taskflows, running taskflows, and the agents be the same. For the links View Status and My Tasks, you can be on any locale.

Fixing “Session Expired” Errors for Oracle Application Server Deployments

If you deployed Shared Services to Oracle Application Server and you are experiencing “Session Expired” errors while doing a single sign on to Shared Services, a known server configuration issue exists. By default, Oracle Application Server appends the domain name to the server name during installation; whereas the application URLs may be resolved without the domain name suffixed to the hostname, thus causing the problem.

If you experience this error, follow these steps to resolve it:

1. From any Taskflow Management page (for example, Manage Taskflows), right-click in the right frame and note the server name that is displayed in the URL. For example, http://<servername>/interop/framework/workflow/start?targetFile=manageTaskFlow

Where <servername> refers to the host name of your server.

2. Navigate to the <Oracle home for OAS>\Apache\Apache\conf directory and, using a text editor, open the httpd.conf file.

3. Change the value for the key ServerName to the server name you noted in the URL.

4. Save the file and close it.

5. You must restart Oracle Application Server for the changes to take effect. To do so, go to the Windows Services panel (Start > Settings > Control Panel > Administrative Tools > Services) and restart the services beginning with Oracleoracleas<servicename>.

6. If after following these steps and restarting Oracle Application Server you still experience “Session Expired” errors, follow the additional steps in the section below (Fixing “Session Expired” Errors on Microsoft Internet Explorer) to fix this problem.

Fixing “Session Expired” Errors on Microsoft Internet Explorer

If you are experiencing “Session Expired” errors, follow these steps:

1. Open Internet Options (Start > Settings > Control Panel, Internet Options).

2. Select the Privacy tab.


34

3. Click Advanced.

4. Select Override automatic cookie handling.

5. Select Always allow session cookies.

6. Click OK.

7. Click OK.

Virtual Hosts on Tomcat

To run Shared Services on Tomcat, you must verify that the virtual host name is the Fully Qualified Domain Name (FQDN).

To do so:

1. Open the server.xml file located in the Tomcat deployment directory (for example, C:\ hyperion\SharedServices\9.2\deployments\Tomcat\5.0.28\conf).

2. Replace the following text:



<Host name="localhost" debug="0" appBase="webapps" unpackWARs="true" autoDeploy="true">

With the following text:



<Host name="test.hyperion.com" debug="0" appBase="webapps" unpackWARs="true" autoDeploy="true">

Ensure that you use the fully qualified URL when you connect to the product from a Web-based UI, for example:

http://test.hyperion.com:9080/myProduct

This affects Tomcat application servers only. Do not change the virtual host name for the other supported application servers (WebLogic, WebSphere, and Oracle).

Netscape Save or Cancel Alerts for Managing Taskflows

Note: Ignore this section if taskflow alerting on Netscape is not required.

For managing taskflows, if the alerting (Save or Cancel prompt) is required by the products, follow these guidelines:

1. Create a JSP file (prodrefInclude.jsp) and add the following domain name setting code.

<% String serverName = request.getServerName();

http://test.hyperion.com:9080/myProduct


String domainName="";

if(serverName.indexOf(".")!=-1){

domainName = serverName.substring((serverName.indexOf(".")+1),serverName.length());

}else{

domainName = serverName;

}

%>

<script language="javascript">

document.domain = "<%=domainName%>";

</script>

2. Include this JSP file in the other JSP files that reside in the interop/taskflow folder.

Whenever redirect is used, the domain name which is set is lost and it gets the original domain name again. To avoid this, include this JSP file in every Page in the application.

3. To run the product on these servers (for example), change the following code in the JSP files:

getServletContext().getInitParameter("HUB_HOSTNAME")

To:

getServletConfig().getServletContext().getInitParameter("HUB_HOSTNAME")

In the URL in EAP files, replace localhost with a fully qualified Host name (machine name + domain name).

Top

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

P/N: DH08692030

35

http://www.hyperion.com/