10/27/06
For a complete list of requirements, see the STRATEGY Analyzer 6.1 Guide .
Server
STRATEGY 4.5 with patch 4 (4.50.040) or later.
OS/400 Version 5 Release 1 (V5R1).
Adequate free disk space to install the server.
Disk space required for server installation:
Component
Space Required
Analyzer Server
100MB
Temporary Space
50MB (After installation, this space is freed when the installer signs off.)
Run Time Space
500 MB (This temporary space is allocated by JDBC and is used for improving
performance. The memory will be released when you stop the Orion Application Server.)
Orion Application Server
Essbase/400 6.5 (if Analyzer is used with multidimensional databases).
JDK 1.3.1 with Java group PTF SF99069-11 or later.
Database group PTF SF99501-09 or later. You must also have the ability to run the iSeries RUNSQLSTM command.
Client
PC Requirements:
Computer IBM or IBM compatible personal computer Operating System Microsoft Windows 98; Microsoft Windows NT 4.0, Service Pack 6; Microsoft Windows 2000, Service Pack 2; or Microsoft Windows XP Web Browser Microsoft Internet Explorer 5.5 or later Microprocessor 450 MHz minimum. 850 MHz recommended. Note: Because Analyzer processing is done via an applet on the PC, performance will increase relative to processor speed. RAM 128MB Hard Disc Space 30MB temporary space Plug-in Sun Java Plug-in 1.3.1 with the latest patch.
For a complete list of enhancements and release notes, see the STRATEGY Analyzer 6.1 Guide, Release Overview chapter.
Documentation is available at the following locations:
http://support.spss.com/. Find the Documentation link, and then click STRATEGY Manuals. A login is required.
All STRATEGY Analyzer documentation is available on the Analyzer CD, or from the Analyzer Information Map after installing Analyzer. To access the Information Map, from the Analyzer Launch Page, click the Analyzer Information Map link. Hyperion® documentation is also available from the Information Map.
Analyzer 6.1 documentation includes:
STRATEGY Analyzer 6.1 Guide : Provides a release overview, installation and uninstallation instructions, and administration and maintenance information.
Analyzer 6.1 Installation Quick Start: This short document provides a brief overview of requirements, enhancements, and installation instructions. It is available on the CD and in printed copy.
Analyzer 6.1 Readme: Provides last-minute release notes. It is available on the CD as anzreadme.htm.
Hyperion Documentation is available on the CD.
Microsoft Internet Explorer 7.x
Analyzer does not currently support Microsoft Internet Explorer 7.x
In order to use the Landscape option when printing, the option must be specified in both Printer Orientation and Printer Properties. Setting the Landscape option solely from the print button will NOT print in landscape. You also need to set the option through the printer's Printer Properties.
The Delete and Convert processes generate an error when changing Security models, if logged into Administration Tools with an externally authenticated user. The error message is generated because the profile logged into Administration Tools is one that is deleted.
Note: The delete process deletes the user profile(s) up to, and including, the user profile that is logged in to Admin Tools and stops there. The remaining externally authenticated user profile(s) are not deleted. The Integrated Security setting in System Settings does not set Analyzer Security, it remains on "Use OS/400 Integrated Security".
The Measures parent is not displayed in a relational report, but its children are. 4.x versions of Analyzer display the Measures parent.
User is required to reload a report in order to view the Calculation Script results.
Linked Reporting Objects (LRO) do not work properly under EES.
The SYNCSECTOEES command in EES creates a user in EES with the password value specified in the command, not the Essbase user profile's password. If an Analyzer user tries to create an Essbase database connection using the essbase1/newuser profile, they will receive an error. The reason they receive the error is because when EES performs the sync it creates the profile in EES using the password value specified in the string (in this case 'password').