Readme File for All Platforms

This file contains the following sections:

• What is Essbase Deployment Services?
• Platforms Supported
• Installation Information
• Release 6.5.3 Documentation
• Documentation Updates
• Fixed Problems
• Known Problems
• Installed Files
• Localization

Top

What is Essbase Deployment Services?

Essbase Deployment Services (EDS) provides a highly scalable, available, and reliable platform for developing large-scale, web-enabled Hyperion Essbase applications. Essbase Deployment Services works with Hyperion Essbase and large-scale Java programming technology to bring enterprise-level performance and reliability to Hyperion Essbase applications.

The Essbase Deployment Services platform supports large scale Hyperion Essbase applications by providing the following capabilities:

• Hyperion Essbase server clustering: Essbase Deployment Services allows you to group sets of Hyperion Essbase servers running applications with identical databases and use them as a single resource in your client programs.
• Hyperion Essbase server load balancing: Essbase Deployment Services servers can receive requests to a single Hyperion Essbase server and distribute requests across a cluster of Hyperion Essbase servers running copies of an application.
• Hyperion Essbase server failover support: Essbase Deployment Services detects Hyperion Essbase service interruptions and automatically re-routes requests to another Hyperion Essbase server.
• Hyperion Essbase server connection pooling: Essbase Deployment Services allows client requests to share connections, conserving software and network resources and improving performance.

These features create a highly scalable and reliable platform on which to build enterprise-level client applications for Hyperion Essbase.

Top

Platforms Supported

Essbase Deployment Services

Essbase Deployment Services supports the following operating systems:

• Windows NT 4.0
• Windows 2000
• Sun Solaris 7/8 (Sun OS 5.7/5.8)
• HP-UX 11.0 / 11i
• AIX 4.3.3, 5L

Middle-Tier Support

Essbase Deployment middle-tier web service requires the following server operating systems:

• Windows NT 4.0
• Windows 2000
• Sun Solaris 7/8 (Sun OS 5.7/5.8)
• HP-UX 11.0 / 11i
• AIX 4.3.3, 5L

Application Servers

Essbase Deployment Services requires a J2EE 1.3 application server, such as:

• BEA Weblogic Server 6.1
• Websphere Enterprise edition 4.0.1
• Apache Tomcat 4.0.3
• iPlanet 6.5

Essbase Deployment Services supports HTTP/1.1 and SSLv3 protocols.

Hyperion Essbase Servers

This release of Essbase Deployment Services supports Hyperion Essbase 6.2 and 6.5.x.

Top

Installation Information

Uninstalling Previous Versions of Essbase Deployment Services

If you have an older version of Essbase Deployment Services installed, before you install a newer version, you must run the uninstall program. In addition to running the uninstall program, you need to delete the folder where the previous version of the product was installed. You must do this step because the uninstall program does not remove completely the configuration information from the previous version of Essbase Deployment Services.

You need to manually delete the essbase.properties, domain.db, and Essbase_Enterprise_Services_65_Installog.log files as these files are not automatically removed by the uninstaller program.

If you want to uninstall the current version, install Essbase Deployment Services in the same location, and preserve the configuration information, you do not need to remove the files listed above.

Deploying Essbase Deployment Services as a Servlet on UNIX Platforms

When deploying Essbase Deployment Services as a servlet on a Web application server for UNIX platforms, be sure to update the PATH environment variable and add $EDSHOME/bin to PATH, where $EDSHOME is the location where you have installed Essbase Deployment Services. For example, if Essbase Deployment Services is installed in /home/essbase/ees, add the following to the PATH environment variable :

/home/essbase/ees/bin

If you encounter the error message "Could not load library" on any UNIX platform, make sure you have the following settings on your machine:

export PATH=.:../jre/bin:../essolap/bin:../essolap/locale:$PATH

export CLASSPATH=../lib/ess_japi.jar:../lib/ess_es_server.jar:$CLASSPATH

export LD_LIBRARY_PATH=.:../essolap/bin:../essolap/api/lib:../jre/lib:

export ARBORPATH=../essolap

export ARBORMSGPATH=../essolap/bin/essbase.mdb

export PATH=../jre/bin:$PATH

export CLASSPATH=../lib/ess_japi.jar:../lib/ess_es_server.jar:$CLASSPATH

export SHLIB_PATH=../jre/lib:.:../essolap/api/lib:../essolap/bin:$SHLIB_PATH:

export ARBORPATH=../essolap

export ARBORMSGPATH=../essolap/api/lib/essbase.mdb

export PATH=.:../jre/bin:$PATH

export CLASSPATH=../lib/ess_japi.jar:../lib/ess_es_server.jar:$CLASSPATH

export LIBPATH=.:../essolap/api/lib:../essolap/bin:../jre/lib:$LIBPATH

export ARBORPATH=../essolap

export ARBORMSGPATH=../essolap/api/lib/essbase.mdb

Java Runtime Environment

On supported UNIX platforms, the Java Runtime Environment (JRE) must be installed and configured before running the Essbase Deployment Services installation. The JRE is included as part of this installation.

For information on the supported versions of the JRE see the Essbase Deployment Services Installation Guide (installgd.pdf).

Installation of the Java Runtime Environment may require operating system patches. Refer to the documentation which accompanies the Java Runtime Environment download site for more information.

EDS as a Service Under Windows NT

EDS can be run as a service under Windows NT. Some changes from the standard configuration must be made. In addition to the procedures covered in the EDS Installation Guide (installgd.pdf), the essbase.properties file must be edited to keep the command shell from starting automatically. Open /bin/essbase.properties with a text editor and change the system.cmdshell=true to system.cmdshell=false.

Associated Software

The following software products can be used with Essbase Deployment Services, but are not included with this release:

• WebLogic Server is available from the BEA Systems, Inc.:
  http://www.bea.com
• VisiBroker 4.1 is available from Inprise Corporation:
  http://www.inprise.com/visibroker
• DB2 is available from IBM Corporation:
  http://www.ibm.com/db2
• Oracle is available from Oracle Corporation:
  http://www.oracle.com
• SQL Server is available from Microsoft Corporation:
  http://www.microsoft.com/sqlserver
• MSXML3 parser is available from Microsoft Corporation:
  http://msdn.microsoft.com/downloads

NOTE:
The process of installing and configuring third-party software products, including required application servers, is specific to each software product. Installation information is available in the product documentation. Configuration topics specific to each of the approved third-party products are available under the Tips and FAQs section of the Resource Library menu on essbase.com.

Top

Release 6.5.3 Documentation

With the exception of this readme and the associated new online HTML documents, the documentation included in this release is identical to that included in Essbase Deployment Services Release 6.5.2.

Refer to essbase.com for information on configuring third-party software products.

The following online documentation is included with this release:

• Essbase Deployment Services Launch Page -- provides links to all the online documentation
  \hyperion\essbase\essenterprise\docs\index.htm
  Click here to open the online documentation.
  Note: Link works only if documentation is installed in the recommended structure.
• Essbase Deployment Services Installation Guide (PDF)
  \hyperion\essbase\essenterprise\docs\books\installgd.pdf
• Essbase Deployment Services Console online help (HTML)
  \hyperion\essbase\essenterprise\docs\console\console.htm
• Essbase Deployment Services Essbase.properties File Reference (HTML)
  \hyperion\essbase\essenterprise\docs\props\propfile.htm
• Essbase JAPI Reference (HTML)
  \hyperion\essbase\essenterprise\docs\ess_japi_html\index.html

NOTE:
The Essbase Deployment Services Console online help can be viewed in Internet Explorer (version 3.0 or later) or Netscape Navigator (version 3.0 or later). However, certain features of the help system are not supported by older versions of these browsers. For this reason, we recommend viewing the online help in the most recent version of Internet Explorer or Netscape Navigator.

Top

Documentation Updates

Delimiters Used in Separating User, Connection Pools, and Clusters Names

Under the Connection Pools properties, when specifying allowed users, user names should be separated by a semicolon.

Under the Cluster properties, when specifying service component names, the component names should be separated by a semicolon.

Under the Enterprise Servers properties, when specifying enabled connection pool names and enabled cluster names, each name is to be separated by a comma.

Using Existing Essbase User When Configuring Connection Pools and Clusters

When using connection pools and clusters, the administrator should make sure that the connection pool and cluster are configured with an existing Essbase user and that the user has access permission to use the application. (62020)

Logging into Console Using URL

When logging into the Essbase Deployment Services Console using HTTP mode, the user has a choice of specifying, in the Preferred Server field, the full URL address of the Essbase Deployment Services server or just the name of the Essbase Deployment Services server.

If you elect to use the full URL address, make sure you have selected the HTTP option from the ORB Type and enter the correct port number to use in the URL; otherwise, you will get an error.

When specifying just the server name, then the Essbase Deployment Services servlet needs to be installed in the default location of the application server. If using the URL method, the Essbase Deployment Services servlet can be installed on any root directory. (68443)

Default Heapsize

The default value for the HEAPSIZE option set in the shell script is now 256 MB.

Fault Tolerance Error Codes in essbase.properties File

The following error codes for fault tolerance are listed in the essbase.properties file. If you encounter error codes other than the ones listed below, add the error codes, separated by commas, in the essbase.properties fault tolerance entry. Note that the following properties are case sensitive:

system.faultTolerance.retryOnSameSvcComp.onErrorCodes=

system.faultTolerance.reconnectRetryOnSameSvcComp.onErrorCodes=1013095,1042006,1013136,

1051021,1051010,1042017,1042013,1013013

system.faultTolerance.retryOnNextSvcComp.onErrorCodes=1013009,1013204,1054009,1054010,1013110

Top

Fixed Problems

• 60835 - Logout the users from the Essbase agent crashes the EDS server.
• 60828 - The error code for fault tolerance are not completely documented.
• 60758 - If an application is stopped after a cluster is opened, EDS returns an error with null result.
• 60741 - EDS Server crashes when doing member selection in ESS after user is logged out.
• 60627 - Starting EDS as NT service takes 100% CPU usage. This is due to a specific setting in essbase.properties. Change the system.cmdshell=true setting to system.cmdshell=false.
• 58221 - The method IEssDataCell.getLinkedObjects() for HIS Drill-Through fails without error.
• 58077 - LRO Functionality Doesn't work with GUI Console.
• 57647 - Fault tolerance -- if user logged out by supervisor while query is executing, it throws exception
• 57519 - Multiple SetActive calls crashing the EDS server
• 60458 - The EDS installer pointed JRE 1.3.0, an unsupported version, and caused instability in EDS.
• 57392 - The Administrative console did not prompt the user to save changes.
• 57341 - The EDS service did not stay running when the user logged off or on.
• 57027 - Every request from ESS resulted in a Validate Login Session call to Essbase.
• 56948 - The method IEssCube.exportData() needed to be modified with Java API.
• 56642 - The method IEssSequentialIterator.isEndOfData returned an incorrect value.
• 56634 - The method IEssDimension.setLevelName() accepted any value as Level Value.
• 56633 - The arguments in IEssDimension.setLevelName(null) crashed the Server.
• 56518 - Adding an existing OLAP server name threw the error message twice.
• 56355 - The statistics page in the Administrative console showed all 0's.
• 56088 - The Administrative console showed the wrong value for the count of EDS servers.
• 56055 - EDS retrievals from Essbase 6.5 were unable to retrieve Chinese characters.
• 55973 - The default password was null, but this is an invalid value.
• 54922 - The arguments in IEssCubeOutline.deleteDTSMemberAlias(null,String) crashed the server.
• 54918 - The arguments in IEssCubeOutline.enableDTSMemberAlias(null,string) crashed the server.
• 54917 - The arguments in IEssCubeOutline.setDTSMemberAlias(null,string,string) crashed the server.
• 54905 - The arguments in IEssMember.addAliasCombination(string,null,string) crashed the server.
• 54901 - The arguments in IEssMember.setAlias(string,null) crashed the server.
• 28183 - The log file option accepted negative values.
• 28181 - If the log file buffer size option value was null, the server did not start.
• 28174 - There was no confirmation dialog for deletion of a cluster or a connection pool.
• 28039 - The method IEssCubeOutline.deleteAliasTable with a null argument crashed the EDS server.
• 28038 - The method IEssCubeOutline.renameAliasTable with a null argument crashed the EDS serve.
• 28036 - The method IEssCubeOutline.copyAliasTable with a null argument crashed the EDS server.
• 26542 - The Administrative Console and Java API did not work with connetion pools in the same manner.
• 26276 - Stopping the EDS server was not disabled when the server was not started.
• 26172 - The method Domain.createCluster allowed the creation of a cluster with spaces as the name.

Top

Known Problems

Every effort has been made to ensure that Essbase Deployment Services is as free of bugs as possible. However, there are some known problems.

• 60425 - IEssDomain.setuserAuthenticatorType need to state calling updatepropertyvalues is required.
• 60379 - EDS server does not log error messages with EDS log if Essbase Server is not running.
• 60309 - IEssOpReport should provide a option to pick the report script from client place.
• 58220 - EDS server fails without error if the Essbase OLAP server is not ready.
• 57933 - IEssbase.changePassword - No Exception returned for Empty String as Password.
• 57181 - When setting up connection pool, if user name is null, GUI doesn't give a message
• 28186 - No errors reported by the server if the Log file name is empty or null
• 28026 - IEssOpReport not working with Japanese characters
• 27121 - HTTPS is not working with ConnectUsingHttpUrl sample.
• 26223 - IEssConnectionPool.setUserName -- shouldn't accept blank spaces/tabs
• 24904 - Cannot close the Admin GUI after closing the EES Server in Solaris.
• 23139 - IEssbase.signOn: error message is different from HTTP to TCP/IP
• 22818 - IEssDomain.getHierarchicalName doesn't work when you sign-on to a sub domain
• 22065 - IEssDimension.get methods: need to provide informative error messages
• 21898 - IEssMember.getDimensionStorageCategory is not properly working
• 21846 - clustering - if both agents stopped after EES started, infinite loop with err

Top

Installed Files

The installation program transfers the following files to the destination machine:

• /bin

  
     /eds.dll
  
     /eds_rexec.exe
  
     /essbase.properties    -- configuration file
  
     /EssbaseEnterprise.exe
  
     /Pdh.Dll
  
     /regact.cmd
  
     /startcmd.cmd
  
     /startees.cmd
  
     /startgui.cmd
  
     /startolap.cmd
  
     /unregact.cmd
  
     /viewdocs.cmd
  
  

• /data

  
     /domain.db
  
     /essbase.id
  
  

• /devcorner

  
     /designdocs
  
       /ess_japi.doc
  
       /ess_japi.mdl
  
     /examples
  
       /ConsoleComps.java
  
       /CubeLocks.java
  
       /GridGui.java
  
       /OlapSecurity.java
  
     /readme_dev_notes.htm  -- Dev Notes (HTML)
  
     /src/src.jar
  
  

• /docs

  
     /books/installgd.pdf  -- EDS Installation Guide PDF file
  
     /clickme.htm  -- starting point for EDS HTML documentation
  
     /console/*.*   -- EDS Console Help files
  
     /copy.htm
  
     /eesindex.htm
  
     /eeslist.htm
  
     /ess_japi_html/*.*    -- Java API HTML Reference
  
     /graphics/*.* -- graphics folder
  
     /help.htm
  
     /homedoc.htm
  
     /index.htm
  
     /japistart.htm
  
     /props/propfile.htm  -- essbase properties file documentation
  
     /readme_eds653.htm -- Readme file
  
     /techsupp.htm
  
  

• /essolap

  
     /essolap/*.*  -- Essbase OLAP server
  
        /bin
  
        /java
  
        /Locale
  
     /version.txt  -- text file specifying the Essbase version
  
  

• /external

  
     /external
  
        /j2ee  -- J2EE installation files
  
           /activation.jar
  
           /mail.jar
  
  

• /jre

  
     /jre/*.*  -- Java runtime environment files
  
  

• /lib

  
     /ess_es_ejb.jar    -- 
  
     /ess_es_gui.jar    -- 
  
     /ess_es_server.jar --  
  
     /ess_japi.jar      -- Essbase Java API. ESS is built on this API.
  
  

• /samples -- sample applications files

  
     /japi
  
     /jspi
  
  

• /UninstallerData

  
     /Essbase_Enterprise_Services_6.5_InstallLog.log
  
     /install.log
  
     /resource
  
        /iawin32.dll
  
        /remove.exe
  
        /ZGWin32LaunchHelper.exe
  
     /Uninstall EES.exe
  
     /Uninstall EES.ico
  
     /Uninstall EES.lax
  
     /uninstaller.jar
  
  

Top

Localization

Essbase Deployment Services supports the use of languages other than English. To use other languages, set the ESSLANG environment variable on the Essbase and Essbase Deployment Services server.

For more information on language code pages refer to : http://www.iana.org/assignments/character-sets

Matrix of ESSLANG Values for Windows Platforms

Matrix of ESSLANG Values for Unix Platforms

Top