COGNOS MANAGEMENT SERIES

Transcription

1 COGNOS MANAGEMENT SERIES PLANNING ANALYST INSTALLATION GUIDE THE NEXT LEVEL OF PERFORMANCE

2 This document applies to Cognos Management Series Planning version 7.1 and may also apply to subsequent releases. To check for newer versions of this document, visit the Cognos support Web site ( This edition published Copyright Copyright (C) 2003 Cognos Incorporated While every attempt has been made to ensure that the information in this document is accurate and complete, some typographical errors or technical inaccuracies may exist. Cognos does not accept responsibility for any kind of loss resulting from the use of information contained in this document. This document shows the publication date. The information contained in this document is subject to change without notice. Any improvements or changes to either the product or the document will be documented in subsequent editions. U.S. Government Restricted Rights. The software and accompanying materials are provided with Restricted Rights. Use, duplication, or disclosure by the Government is subject to the restrictions in subparagraph (C)(1)(ii) of the Rights in Technical Data and Computer Software clause at DFARS , or subparagraphs (C) (1) and (2) of the Commercial Computer Software - Restricted Rights at 48CFR , as applicable. The Contractor is Cognos Corporation, 67 South Bedford Street, Burlington, MA This software/documentation contains proprietary information of Cognos Incorporated. All rights are reserved. Reverse engineering of this software is prohibited. No part of this software/documentation may be copied, photocopied, reproduced, stored in a retrieval system, transmitted in any form or by any means, or translated into another language without the prior written consent of Cognos Incorporated. Cognos and the Cognos logo are trademarks of Cognos Incorporated in the United States and/or other countries. All other names are trademarks or registered trademarks of their respective companies. Information about Cognos Products and Accessibility can be found at

3 Contents Chapter 1 System Requirements Analyst Configurations...4 Network Server System Requirements...5 Thick Client Workstation System Requirements...5 Thin Client Workstation System Requirements...5 Terminal Services/Citrix General Configuration...6 Stand Alone Workstation System Requirements...7 Chapter 2 Installation Overview...9 Configuration Types...10 Installation Methods...11 Installing Analyst...11 General Preparation...11 Network Installation...12 Client Installation...14 Terminal Server Installation...15 Citrix MetaFrame 1.8 Installation...17 Command Line Installation...19 SMS Deployment...22 Stand Alone Installation...25 Upgrading Analyst from Earlier Versions...26 Network and Client, Analyst Versions 3.0 and Stand Alone, Analyst Versions 2.4 and Additional Information...29 Installing Update Files...29 Network Access Rights...29 Filesys.ini File...29.tab and.log Files...29 Data Directories...30 Errorlog.dcf File...30 Registry Settings...31 Elevating Installation Privileges

4 Contents Chapter 3 Configuring the Analyst Add-in for Excel Setting Up the Analyst Add-in for Excel...33 Changing the Path to the Analyst.xla File...34 Starting Analyst Add-in for Excel...35 TCP/IP Protocol for the Analyst Add-in for Excel...35 Chapter 4 Configuration Starting Analyst...37 Changing Configuration Settings...42 Uninstalling Analyst

5 1 System Requirements Analyst is designed to work on a local area network (LAN) running the following Microsoft Software 32-bit operating systems: Windows 98. Windows Windows NT4. Windows XP. If you are considering running Analyst over a (WAN) connection, please contact Technical Support. System requirements differ according to whether you are installing on a network server, Terminal Server (Citrix), or a client workstation. If you plan to run Contributor and Analyst on the same system, see the Contributor Installation Guide for additional system requirements. 3

6 Chapter 1 System Requirements Analyst Configurations The following diagram shows potential Analyst configurations. The hardware and software requirements for these are described in the following sections. See Configuration Types on page 10 for a description of each configuration type and when they can be used. 4

7 Network Server System Requirements Network Server System Requirements We recommend the following network configuration: Mapping of logical drives must be supported. Minimum network speed of 10 Mbps for thick client configuration, 100 Mbps for a thin client configuration. At least 100 MB of hard disk storage space for each non-administrator should be reserved on the network server, and 200 MB of free space for each administrator. However, since this figure can vary considerably depending on model size, please consult your application consultant when preparing to build a model in Analyst. Analyst is compatible with Microsoft Windows Networking Systems. Thick Client Workstation System Requirements For best performance, we recommend a thick client installation rather than a thin client installation. Pentium processor with 100 MHz. 128 MB of RAM. We recommend a Pentium 3 processor with MB of RAM for best performance. Super VGA monitor with screen resolution. Video adapter with a minimum of 256 colors. Windows swap file based on the Microsoft recommendation for your configuration. Use automatic allocation if using Windows XP unless directed otherwise by Technical Support. Analyst Add-in for Excel users must have Microsoft Excel 97 or later, and must have TCP/ IP communication protocol. ODBC users must have a 32-bit ODBC driver. Thin Client Workstation System Requirements When using a thin client installation, it is essential to have a robust network connection otherwise performance will suffer. Pentium processor with 100 MHz. 128 MB of RAM. Super VGA monitor with screen resolution. Video adapter with a minimum of 256 colors. Windows swap file based on the Microsoft recommendation for your configuration. Use automatic allocation if using Windows XP unless directed otherwise by Technical Support. Analyst Add-in for Excel users must have Microsoft Excel 97 or later, and must have TCP/ IP communication protocol. ODBC users must have a 32-bit ODBC driver. 5

8 Chapter 1 System Requirements Terminal Services/Citrix General Configuration All operating specifications are required to meet the minimum requirements of the operating systems manufacturers in relation to service packs, network connections (Nic Card) and processor requirements. File Server This machine contains the Analyst libraries. It must be on the same sub-net as the terminal server. It needs to have the following specification: Pentium III 500 or better. 1 GB RAM. Free space depends on size of model+ recommended 200 MB space per user. Windows NT4.0, or Windows 2000 Server. Terminal Server Requirements Analyst needs to be installed on each terminal server in the farm (cluster). Each terminal server needs to have the following specification: Pentium PIII 800 or better (up to a quad processor). 1 GB RAM per processor (or per 15 users, which ever is greater). Windows NT4.0 or Windows 2000 Server. Microsoft Excel 97 or later (if using the Analyst Add-in for Excel). Client Requirements in a Terminal Server Configuration Each client machine needs to have the following specification: Pentium processor 100MHz, or Macintosh (must use Mac Citrix client). Windows 9x, Windows NT4.0, Windows 2000, Windows XP. 100 MB of free space (files should not be saved locally, only to Citrix server). 32 MB RAM. SVGA monitor 800X600 resolution. 6

9 Stand Alone Workstation System Requirements Stand Alone Workstation System Requirements For a stand alone installation, we recommend the following: Pentium processor with 100 MHz. 128 MB of RAM. Note We recommend a Pentium 3 processor with 256 MB - 512MB of RAM for best performance. CD-ROM drive. 275 MB of available hard disk space. Data space depends on the number and size of your models; at least 75 MB of hard disk space for the Analyst application itself and an additional 100 to 200 MB of free space for the data is recommended. A typical model has around 50 D-Cubes, each D-Cube requiring 0.5 to 3.0 MB. Super VGA monitor with screen resolution. Video adapter with a minimum of 256 colors. Windows swap file based on the Microsoft recommendation for your configuration. Use automatic allocation if using Windows XP unless directed otherwise by Technical Support. Analyst Add-in for Excel users must have Microsoft Excel 97 or later, and must have TCP/ IP communication protocol. ODBC users must have a 32-bit ODBC driver. 7

10 Chapter 1 System Requirements 8

11 2 Installation Overview This installation guide explains how to install Analyst and configure it to your needs. Compatibility Analyst, Manager, and Analyst Add-in for Excel - version 7.1, are fully forward compatible, so all models created in versions 2.4 and 3.0 can be used in version 7.1. For version 3.0 and later, version numbers must match between Contributor and Analyst for them to work as a pair. Analyst version 7.1 is not fully backward compatible. Manager version 7.1 is forward, but not backward compatible. You can upgrade existing reports from previous versions. If nothing has changed, you will not be asked to save the report on opening. Since there is full forward compatibility, but not full backward compatibility, you should not send reports created in versions 3.0 and 7.1 to users still running version 2.4. This is because arrows are stored differently in versions 3.0 and 7.1 to cope with snap to grid and improvements to moving groups of objects. To enable normal arrows drawn in a version 3.0 or 7.1 report to be viewed in version 2.4, choose Save As from the File menu, and click Convert for 2.4. This allows normal arrows drawn in versions 3.0 and 7.1 to work correctly in version 2.4. Note If a flowchart has been created using the new graphical browser in version 3.0 or 7.1, you will not be able to use it in version 2.4. Analyst Add-in for Excel version 7.1 works with Microsoft Office XP as well as all versions of Microsoft Excel supported by version

12 Chapter 2 Installation Configuration Types Before you begin to install Analyst you need to determine which configuration type is suitable. The configuration types that are available are as follows: Thick client For a network installation, this is the recommended configuration type. The Analyst software is installed on the local client drives of each workstation, and the data is stored in a shared location on the network server, along with the control files. Most of the processing is done on the client, reducing the amount of network traffic. Thin client The Analyst software and the data is stored on the network server. Since the Analyst software is located in the server, there is large amount of network traffic and so it requires a robust network connection. We do not recommend this option over a WAN. Terminal Server/Citrix Terminal Server installations do not have a client installation. All calculations are done on the server. This enables users to use Analyst with minimal local processing power. Stand Alone You can install Analyst onto an individual PC for stand alone operation. Comparison of Different Configuration Types The following table summarizes the differences between the different configuration types: Thick Client Thin Client Terminal Server/Citrix Stand Alone installation Program file location Local on client Remote on server Terminal Server Local Data location default Remote on server Remote on server Terminal Server or File Server Local Data sharing Yes Yes Yes No Network connection required? Yes Yes Yes No Calculations Performed by client CPU Downloads the program workspace from the server into local memory, then performs the calculations locally on the client CPU Performed on Terminal Server Performed by local CPU with no network connection required 10

13 Installation Methods Installation Methods There are a number of installation methods: Network You should choose this if you are the administrator and you are performing the initial setup for a network installation. Client This should be performed after a network installation. It can be done either by the administrator or by the user, who must be given elevated privileges, see Elevating Installation Privileges on page 31. Command line Analyst can be installed from the command line, and via various distribution methods such as SMS. Stand Alone This is for users who will be using Analyst for stand alone operation. These methods are described in the following sections. Installing Analyst General Preparation Before installation using any installation method, close all open programs and files. To install the Analyst Add-in for Excel, Microsoft Excel must have been opened at least once. But be sure to close Microsoft Excel before beginning installation, otherwise the Analyst Add-in for Excel will not install correctly. If you are upgrading from an earlier version of Analyst, see Upgrading Analyst from Earlier Versions on page 26. Analyst 7.1 will not install if an earlier version of Analyst is installed on the system. Only Analyst version 7.1 is supported with Contributor version

14 Chapter 2 Installation Network Installation This process sets up the locations for the client install. It puts the Filesys.ini file onto a network share and copies the installation files into the share ready for client installation. The Filesys.ini is the control file for the location of system settings. It is used by Analyst to locate other files. Installation should be performed using an account that has administrator rights on the network. Network Preparation Before you begin installation you need to set up a network share. This enables client machines to access the installation files. Two user groups need access to this share: Domain Users (or a group specifically created for Analyst users) Give NTFS permissions of Modify. Domain Administrators Give NTFS permissions of Full Control. It is assumed that users will access the share via UNC network paths. Installing on the Network The steps for installing from a network are: 1 Run the Cognos Management Series - Analyst And Contributor CD. 2 Click Install in the menu, select Analyst and then click here. 3 Follow the Wizard: a User Name the first user that will be set up will be called this (it can be changed later). b Installation type select Network. c Destination folder change the destination to the share that you set up, for example: \\machinename\analystshare\ d Custom Setup All elements are installed on the network. This screen gives you the opportunity to determine which components will be available to be selected during the client installation by clicking on the icon and selecting This feature will not be installed. The icon will change to a cross. These options can be changed at a later date by editing the install.ini file. See Custom Setup which components should I choose? for information on each option. 12

15 Network Installation Custom Setup which components should I choose? The choices are: Analyst This installs Analyst and accompanying documentation. Manager Manager is used to design reports using data stored in Analyst. Choosing this option installs Manager on its own. You might want to select this if you do not want users to have direct access to Analyst. You would need to configure users security to attain this. Note that if you choose this option on its own, Analyst is also installed, but it is only accessible though objects in a Manager report. Manager with Analyst This installs Manager and gives the user access to Analyst. Demo Files This installs several test libraries, see Adding Libraries and Users on page 38 for information on each of these. This is not an option in the Client installation as these files reside on the network. Excel Add-In This allows you to use Excel to create professional reports, tables, and graphs using data from Analyst. You can also use Excel as data entry into Analyst alternative, and use as a front end for the Analyst model builder. This option requires TCP/IP to be installed and configured correctly on the Client PC, as well as your server. For instructions, see Verifying That TCP/IP is Operational on page 35. Amending the install.ini file After a network installation, the administrator can change the options that are available during the client installation by amending the install.ini file. Edit the line Compori=ABCD, where: A = Analyst B = Add-in for Excel C = Manager D = Manager and Analyst Note that if you only selected A and B during the network installation, only these options will appear in the install.ini file. You can amend this file at any point after the network installation. The example shown below will give Analyst, and Manager with Analyst as options during the client installation. Install.ini example Enable=No MAXWS=64000 ServerPath=\\machinename\analystshare71\ Compori=AD [Compatibility] FlagsAsMasks=0 13

16 Chapter 2 Installation Client Installation This section explains how to install Analyst on a Microsoft Windows Client. You perform a Thick or Thin Client installation by running the AnalystClient.exe.The AnalystClient.exe is located in the Analyst folder only after an initial Analyst network installation is performed. See Configuration Types on page 10 to determine whether a Thick or Thin Client installation is appropriate. Client Preparation Before you begin, log on to a client machine and check that you can access the network share. Log onto the client workstation with elevated privileges, see Elevating Installation Privileges on page 31. Analyst stores software settings in the registry under HKEY_CURRENT_USER and HKEY_LOCAL_MACHINE. Installing on the Client To install Analyst on the client: 1 Run AnalystClient.exe from the network share. 2 Follow the wizard: a Installation Type choose Thick Client or Thin Client (see Configuration Types on page 10 for more information). b Destination folder this determines where the program files go. The default is: C:\Program Files\Cognos\epp1\Analyst\. c Custom Setup Choose the components that you want to install. The default selection of components is determined by the options selected during the Network installation, or the contents of the COMPORI section of the install.ini file if that has been subsequently modified. To remove a component from the installation, click on the icon and select This feature will not be installed. The icon will change to a cross. You need to configure the user name, the password and the default library, see Adding Libraries and Users on page 38 and Set or Change the Password as a User on page

17 Terminal Server Installation Terminal Server Installation This section explains how to install Analyst on a Terminal Server. The installation can be performed by either a Domain or Local Administrator account. Before You Start Any user that will create ODBC connections will need to be part of the power users group on the server. The Analyst Add-in for Excel requires TCP/IP to be installed and configured correctly on your Terminal Server. For instructions, Verifying That TCP/IP is Operational on page 35. Ensure the Terminal Server is set up in Application Mode if you are going to launch Terminal Server applications or run Citrix. Each client will need to connect to the Terminal Server via Terminal Server Client tools. Contact Microsoft for additional help with client tool installation. The connection to the Terminal Server must be made via TCP/IP. Prior to the application installation, set up a mapped share point. This share point will be needed for clients to access the data files, and can either be on the Terminal Server or a separate file server. How does a Terminal Server Installation Differ From a Standard Network Installation? Terminal Server installations do not require a client installation. The difference between a typical Server/Client relationship and a Terminal Server/Client relationship can be illustrated in the following way: A typical full install of Analyst installs the application to the client and accesses the data from the file server. All calculations are performed by the client workstation. A Terminal Server eliminates client dependency and performs any calculations on the server. It is assumed that the administrator has knowledge of Citrix and the prerequisites of installing Microsoft Office, including the need for an MST file. The administrator must also be able to amend the userlogon.cmd file. This file is used to map drives on a terminal server. 15

18 Chapter 2 Installation Installing Analyst on Terminal Server 1 Close all open applications. 2 Place the Terminal Server in Install Mode, or install the applications via Add/Remove programs. 3 Run the Cognos Management Series - Analyst And Contributor CD. 4 Click Install in the menu, select Analyst and then click here. 5 Follow the Wizard: a User Name the first user that will be set up will be called this (it can be changed later). b Installation type, select Stand Alone. c Destination folder change the destination to the desired location. d Custom Setup choose the components that you want to install. To remove a component from the installation, click on the icon and select This feature will not be installed. The icon will change to a cross. See Custom Setup which components should I choose? on page 13 for information about each option. e Select the Support Terminal Server Session check box to allow Analyst Add-in for Excel to run via Terminal Server clients. The installation is now complete. Note Because of the variations of Terminal Server operating systems, you may contact Technical Support for resource requirements for your particular operating system version. Resource recommendations given in this installation guide are meant as typical guidelines. 16

19 Citrix MetaFrame 1.8 Installation Citrix MetaFrame 1.8 Installation The following section is an overview of Analyst in a Citrix environment. The Analyst application is installed on the Terminal Server. The administration files and data files can be located on a File Server or the Terminal Server. It is recommended that the administration files reside on a separate network server. Citrix resides on a dedicated Terminal Server machine. Analyst is installed to the Citrix Server via the CD. Citrix (ICA) Client tools are installed on each of the client machines. The clients access the Analyst application via the LAN/WAN connection to the Citrix Server. No Analyst application files reside on client machines. All calculations are performed on the Citrix Server. If you have remapped Client drives during the MetaFrame installation on the server, any applications previously installed will need to be reinstalled. Publish Application Manager Overview for Citrix Metaframe 1.8 General steps to use the Publish Application Manager 1 Install Microsoft Excel. You should open it before continuing. 2 Install the Analyst components onto the Citrix Server, including Analyst, Manager, and Analyst Add-in for Excel (if needed). 3 Open Publish Application Manager to create or join the Citrix Server Farm. Select the scope of Citrix farm. 4 Select new application: a Enter the Application name (i.e., Analyst). Enter a detailed description if desired. b Choose Explicit as application type. Click Next. c Enter the Target path (Shortcut - Properties), for example: D:\Program Files\Cognos\epp1\Analyst\System\ADAYTUM.EXE PLANNING INIFILE= HKEY_LOCAL_MACHINE\Software\...\Analyst\dyalog Server=No Planning= Software\...\Analyst APPNAME=Analyst. d Select the Maximize Application at Start-up check box. Click Next. e Five drop-down selections are available. To maximize bandwidth availability, set: Audio and Video - OFF. Encryption - set to default Basic (contact Citrix for details on encryption between Server/Client). Window Size - select appropriate size. Window Colors - select 16 color for performance reasons. f Select the Add this Application in the Client Start Menu check box. g Select the Add this Application on the Client Desktop check box. h Select the group or user accounts that you want to grant access to run the application. i Choose the Citrix Servers where you want to run Analyst. 17

20 Chapter 2 Installation Citrix Connection on Client Machines Set up the Citrix client tools on each client machine that will be accessing Analyst via Citrix. Note Contact Citrix for installation details on ICA client tools. 18

21 Command Line Installation Command Line Installation It is possible to run the client installation and the standalone installation from the command line. This is described in the following sections. Client Command Line Installation Once a network installation has been run, a file called analystclient.exe is installed on the network share (see Network Installation on page 12). You can run analystclient.exe using the silent installation process. Client Options By default the client installation process installs a thick client to the following location: c:\program files\cognos\epp1\analyst These defaults can be changed using the options shown below. Choose Thick or Thin INSTALLDIR CLIENTOPTION="Thin" Optional, specifies an alternative installation location. Defaults to Thick if not specified. Defaults to c:\program files\cognos\epp1\analyst The features that will be installed are determined either during the network installation, or by modifying the install.ini file, see Amending the install.ini file on page 13. Client Installation Examples Thick client installation, alternative location: analystclient.exe /s /v"installdir="c:\analyst" /qn" Thin client installation, default location: analystclient.exe /s /v"clientoption="thin" /qn" Where: analystclient.exe Is the analyst client installation program. /s Suppresses the Setup.exe initialization window for the installation program. /v Specifies the values of public properties for a silent basic installation. / qn Specifies a silent install. 19

22 Chapter 2 Installation Stand Alone Command Line Installation It is possible to start the stand alone Analyst install from the command line utility msiexec.exe. In order to do this, the machine must already have Windows Installer Version 2 present. Normally, this is installed if required as a result of running setup.exe, however when running a command line install, we call the Windows Installer database (MSI file) directly, rather than the setup.exe bootstrap. If you need to install Version 2 of Windows installer, you will find it in the following location on the Cognos Management Series - Analyst And Contributor CD: bin\utils\windowsinstaller2\instmsiw.exe Using the command line options below with msiexec.exe, administrators can install Analyst silently, permitting the use of various distribution methods, such as SMS. Stand Alone Options By default, Analyst is installed to C:\Program Files\Cognos\epp1\Analyst with all features installed (Analyst, Manager, Manager with Analyst, Excel and demo files). You can configure the installation using the following optional property values: Features Alternate Install Location NO_ANALYST=1 NO_MANAGER=1 NO_MANAGER_W_ANALYST=1 NO_EXCEL=1 NO_DEMOFILES=1 INSTALLDIR="C:\Test\Analyst" Set to 1 to not install a feature. Stand Alone Examples Stand Alone, default location, all features, upgrade (if applicable): msiexec /i Analyst.msi /qn Stand Alone without Manager with Analyst and with alternative installation path: msiexec /i Analyst.msi INSTALLDIR= c:\analyst /qn NO_MANAGER_W_ANALYST=1 Stand Alone, without Excel, default location: msiexec /i "analyst.msi" NO_EXCEL=1 /qn 20

23 Command Line Installation Where: msiexec The Windows Installer command line utility. /i <InstallFile> Specifies the MSI file to be installed. This will need to be the full path if the specified file is not in the path. "Analyst.msi" Is the filename of Analyst.msi. / qn Specifies a silent install. Further information on msiexec command line parameters can be found at: prodtechnol/winxppro/proddocs/sag_wininstall_command_line_syntax.asp 21

24 Chapter 2 Installation SMS Deployment Microsoft Systems Management Server version 2.0 (SMS) enables you to automate installation of programs. You can create a package for the Analyst installation and distribute it in an SMS environment. The Package Definition File has the same filename extension as Adobe Acrobat Reader (.pdf). If the computer you are installing to has Acrobat installed, the Package Definition File may adopt the icon for Acrobat by default. You will need to right-click on the file and select Open With Notepad. The package definition file can be made into a SMS package in the following way: 1 In the SMS Administration Console, right click on the packages tree and select New, Package From Definition. 2 Follow the wizard and select the appropriate package definition file (PDF) file. This is located on the Analyst and Contributor CD, under Analyst\Utils\SMS. 22

25 SMS Deployment 3 This package requires source files so select Always obtain files from a source directory. 4 Complete the Package wizard. Once you have created the package it is possible to distribute that package to selected resource or collections of resources in you SMS environment. To distribute the package 1 In the SMS Administration Console, select Packages and right-click the package you have just created. 2 Select All Tasks, Distribute Software. 3 As you go through the Distribution wizard you will need to advertise the package and assign it to appropriate resources. 4 Advertising a program alerts client computers that software is available to be run. you can also determine which client computers receive software and upgrades and when. Advertising a program adds the program to Control Panel, Advertised Programs. Select Yes. 23

26 Chapter 2 Installation 5 Specify which collection will receive the advertisement. A collection is a group of computers based on processor type, user, user group, IP address, currently installed software, or a wide variety of administrator-specified attributes. You can specify an existing collection or create a new collection. 6 Specify when the program will be advertised. Enter a date and time, and choose whether the advertisement will have an expiry date or not. 7 Specify whether to assign the program or not. Assigning a program runs the program automatically on the client machine from a set time. 8 Complete the wizard. 24

27 Stand Alone Installation Stand Alone Installation The steps for installing on a stand alone PC are: 1 Run the Cognos Management Series - Analyst and Contributor CD. 2 Click Install in the menu, select Analyst and then click here. 3 Follow the Wizard: a User Name the first user that will be set up will be called this (this can be changed later). b Installation type, select Stand Alone. c Destination folder select a local destination or leave the default. d Custom Setup choose the components that you want to install. To remove a component from the installation, click on the icon and select This feature will not be installed. The icon will change to a cross. See Custom Setup which components should I choose? on page 13 for information about each option. Analyst Add-in for Excel requires TCP/IP to be installed and configured correctly on the PC. For instructions, see Verifying That TCP/IP is Operational on page

28 Chapter 2 Installation Upgrading Analyst from Earlier Versions Network and Client, Analyst Versions 3.0 and Log onto the machine with elevated privileges, see Elevating Installation Privileges on page Create a network share. Two user groups need access to this share: Domain Users (or a group specifically created for Analyst users) Give NTFS permissions of Modify. Domain Administrators Give NTFS permissions of Full Control. It is assumed that users will access the share via UNC network paths. 3 Uninstall Analyst on the clients. To do this, from the Start Menu, select Settings, Control Panel, Add/Remove Programs. 4 Back up your existing Analyst network installation files. \USERS.TAB \LIBS.TAB \GROUPS.TAB \PADLOCKS.TAB 5 Uninstall Analyst from the network using Add/Remove Programs. 6 Delete the original Analyst folder. This is important. 7 Install Analyst 7.1 into the network share, see Installing on the Network on page Copy the files backed up in step 4 to the network share. 9 Open the Filesys.ini and add the UNC paths for the USERS.TAB, LIBS.TAB, GROUPS.TAB, and PADLOCKS.TAB as shown below: Libs=\\Machinename\Analystshare71\LIBS.TAB Locks=\\Machinename\Analystshare71\System\Locks\LOCKS.LOG Logins=\\Machinename\Analystshare71\System\Locks\LOGINS.LOG MaxUsers=5 Groups=\\Machinename\Analystshare71\GROUPS.TAB Padlocks=\\Machinename\Analystshare71\PADLOCKS.TAB Users=\\Machinename\Analystshare71\USERS.TAB 10 Run the client install for at least one client, see Installing on the Client on page Ensure that all demonstration libraries are available if required: Tutorial Tutorial3 BiF Lib0 These are installed to Program Files\Cognos\epp1\Analyst\Examples, except Lib0 which is installed to Program Files\Cognos\epp1\Analyst\. See Adding Libraries and Users on page 38 for more information. 26

29 Network and Client, Analyst Versions 3.0 and For an upgrade from Analyst 2.4, delete the Program Files\eplan\Analyst directory on the client machines. For an upgrade from Analyst 3.0, delete the Program Files\Cognos\epp1\Analyst folder from the client. 27

30 Chapter 2 Installation Stand Alone, Analyst Versions 2.4 and Logon to the machine with elevated privileges, see Elevating Installation Privileges on page Backup the c:\program Files\eplan\analyst directory and your libraries. 3 Uninstall Analyst 2.4.To do this, from the Start Menu, select Settings, Control Panel, Add/Remove Programs. 4 Ensure that the Excel Add-in has been removed from Microsoft Excel. To do this: Upgrading from Analyst version 2.4: a Open Microsoft Excel. b From the Tools menu, select Add-ins. c If an item called Adaytum is listed and checked, click OK. You will be asked if you want to remove it. Click Yes. Upgrading From Analyst version 3.0: Open Program Files\Microsoft Office\Library and delete Adaytum.xla. 5 Install Analyst version 7.1, see Stand Alone Installation on page 25. Don t open it at this stage. 6 Go to your backup and copy the following files to your new installation path. The default is: C:\Program Files\Cognos\epp1\Analyst: \USERS.TAB \LIBS.TAB \GROUPS.TAB \PADLOCKS.TAB 7 Edit the Filesys.ini in C:\Program Files\Cognos\epp1\Analyst. You need to amend the path for LIBS.TAB and USERS.TAB and add the path for GROUPS.TAB and PADLOCKS.TAB, see the following example: Libs=C:\PROGRAM FILES\COGNOS\EPP1\ANALYST\LIBS.TAB Locks=C:\Program Files\Cognos\epp1\Analyst\System\Locks\LOCKS.LOG Logins=C:\Program Files\Cognos\epp1\Analyst\System\Locks\LOGINS.LOG MaxUsers=5 Users=C:\PROGRAM FILES\COGNOS\EPP1\ANALYST\USERS.TAB Groups=C:\PROGRAM FILES\COGNOS\EPP1\ANALYST\GROUPS.TAB Padlocks=C:\PROGRAM FILES\COGNOS\EPP1\ANALYST\PADLOCKS.TAB 8 Open Analyst: Start, Programs, Cognos Management Series, Planning - Analyst. 9 Add new demo libraries if required, see Adding Libraries and Users on page 38. You may also need to amend the file paths for old demonstration files. 28

31 Installing Update Files Additional Information Installing Update Files Update files (often referred to as UP1s) contain modifications to Analyst, or its components, that have occurred since the last release. Cognos can send you the update files on a disk or in an message. Occasionally, update files are sent with the program. Update files should be loaded only into the base versions for which they were defined. The update files should be copied into the directory from where the Analyst program runs. If Analyst is run centrally on the server, you must copy the update files into the location on the server, for example G:\Program Files\Cognos\epp1\Analyst\System directory on the server. If Analyst is to run locally on the client workstations, it is necessary to copy the update files into the C:\Program Files\Cognos\epp1\Analyst\System directories at each client workstation. For example, you receive an update file named XHLPTST1.UP1. Using Windows Explorer, copy this file to the C:\Program Files\Cognos\epp1\Analyst\System directory. No further action is necessary. The Analyst program automatically looks for and applies the update when you start the program. To check which update files are being used, in Analyst on the Help menu, click Updates. If you can see from the list that updates exist but are not being loaded, they probably relate to a previous release and are redundant. Network Access Rights At the network server level, you must give all Analyst users full network access rights to the following Analyst objects: Filesys.ini file.tab and.log files Data directories Filesys.ini File The Filesys.ini file is the main control file referred to when Analyst first starts. The Filesys.ini file contains information about the number of users and the number of system administrators..tab and.log Files The Filesys.ini file also defines the directory paths to the files that control the library and user setup used by Analyst. All users must have the same drive letter for network mappings of the directory path to the.tab files, unless UNC paths are used. 29

32 Chapter 2 Installation The following table describes the.tab files. Users.tab Groups.tab Libs.tab Padlocks.tab Locks.log Logins.log Defines valid users for Analyst. Defines the Analyst groups and the users that belong to those groups. This enables you to set up security for a group as a whole rather than by individual users. Defines directories (libraries) where the Analyst data is stored. Defines Analyst item-level security definitions. Defines simultaneous access rights to Analyst data files. Defines simultaneous access rights to Analyst data files. Data Directories The data directories are where users store and access data. All users must have full network access rights to their own as well as all other users data directories. Users store their D-Cubes and other data in directories such as H:\Cognos\epp1\Analyst\Examples\Lib01 and H:\Cognos\epp1\Analyst\Examples\Lib01. You can restrict user access internally within Analyst. Note We recommend that you do not store your data in the directory where Analyst is installed. Save your data in another directory, preferably on another drive: For example, Analyst could be installed to G:\Program Files\Cognos\epp1\Analyst, but you could store the current year s data in a H:\Cognos\epp1\Analyst\Examples\Lib01 directory, and the model showing next year s data in a H:\Cognos\epp1\Analyst\Examples\Lib02 directory. Errorlog.dcf File The Errorlog.dcf file prints system information in the event of an error. This file is located in the Windows temporary directory on the client workstation - usually C:\Windows\Temp, C:\Temp, or C:\Documents and Settings\Administrator\Local Settings\Temp. All users with access to Windows have automatic access to the Windows temporary directory. Therefore, even in a network installation with shared software, each user has his or her own error logging file in a private directory to which the user always has write access. 30

33 Registry Settings Registry Settings When the application is installed, the registry keys created by the install are written to <HKEY_LOCAL_MACHINE> (HKLM). This allows several users to use the same PC for running Analyst. Writing to HKLM requires power-user rights and access rights to the registry. All registry settings created or changed at runtime are written to <HKEY_CURRENT_USER> (HKCU). Analyst usually writes to HKCU. When trying to read from the registry, it will first look in HKCU to find a specific value. If it doesn t find the value it needs, it defaults to the value in HKLM. Consequently, multiple users can use the same machine but have different registry settings in the HKU/SID, which will keep customized settings from being overwritten by other users. Note Changes made to the Maximum Workspace Size (kb) setting (see Changing Filesys.ini File Path, Maximum Workspace, and Keyboard Layout on page 42) and the keyboard layout are written to HKLM and so only users with power user rights can change these settings. Elevating Installation Privileges Analyst needs to be installed under a user context which has local administrative rights. It is possible to set this as a Group Policy of an organizational unit. Even if the users are not local administrators they will be given these rights for the duration of the installation operation. This must be done for the User Configuration as well as the Computer Configuration. The Group Policy Editor defines and controls how programs, network resources, and the operating system behave for users and computers. It is a Microsoft management Console snap-in. 1 In the Group Policy Editor, select Administrative Templates, Windows Components, Windows Installer. 2 Double-click on Always install with elevated privileges and select Enable. 31

34 Chapter 2 Installation 32

35 3 Configuring the Analyst Add-in for Excel The Analyst Add-in for Excel is an add-in created by Cognos that connects to Analyst as a means of displaying the data held in D-Cubes. The add-in is designed to be compatible with Microsoft Excel and to run using the menu bar of a standard Excel spreadsheet. What you see in Excel is a file that can be treated like any other.xls file. The only difference is that when you want to refresh or recalculate a report using the underlying D-Cube data and formulas, you need a link to Analyst. Setting Up the Analyst Add-in for Excel If you selected the Analyst Add-in for Excel option when you installed Analyst, the installation program automatically inserts the Analyst menu on the Microsoft Excel toolbar. If the Analyst menu is not on the Microsoft Excel toolbar, follow the instructions below to add Analyst to the menu. To set up the Analyst Add-in for Excel 1 Open Excel. 2 If the Analyst menu does not appear on the Excel toolbar, on the Tools menu, click Add-Ins. 33

36 Chapter 3 Configuring the Analyst Add-in for Excel 3 In the Add-Ins dialog box, make sure that the Analyst check box is selected. 4 If the Analyst check box does not appear in the list of available add-ins, click Browse and search for the Analyst.xla file. If the Excel file was created on a different computer, the directory path to the Analyst.xla file must be correct or you cannot use the Excel file. To change the path, see the following section. 5 Click OK and restart Excel. Changing the Path to the Analyst.xla File If the Analyst.xla file is not in the appropriate directory, you must move the file into the appropriate directory before setting up Analyst Add-in for Excel. To change the path to the Analyst.xla file 1 In Excel, open the desired worksheet. 2 On the Edit menu, click Links. 3 In the Links dialog box, click Change Source. 4 In the Change Links dialog box, select the Analyst.xla file in the C:\Program Files\Microsoft Office\Office\Library directory, and then click OK. 5 In the Links dialog box, click OK. 34

37 Starting Analyst Add-in for Excel Starting Analyst Add-in for Excel To start Analyst Add-in for Excel 1 Open Excel. 2 On the Analyst menu, click Log On. 3 In the Analyst Logon dialog box, enter your user name and password and click OK. The connection between Excel and the Analyst Add-in for Excel is made, and a message appears notifying you that you are logged on. Note If you cannot start the Analyst Add-in for Excel, see Setting Up the Analyst Addin for Excel on page 33, Changing the Path to the Analyst.xla File on page 34, and TCP/IP Protocol for the Analyst Add-in for Excel on page Click OK. 5 To start to create reports, on the Analyst menu, click New View. TCP/IP Protocol for the Analyst Add-in for Excel Because the Analyst Add-in for Excel uses TCP/IP Protocol for communications between Excel and the Analyst server running in the background, each client workstation must have TCP/IP Protocol installed and correctly configured. Client workstations that are connected already to a network or dial-in server should be able to run the Analyst Add-in for Excel, so you should not need to adjust the TCP/IP Protocol settings for those workstations. Note If you do not have TCP/IP Protocol installed and/or correctly configured, please contact your IT department. Verifying That TCP/IP is Operational To see if TCP/IP is installed, at the MS-DOS command line C:\> prompt, type: ping If TCP/IP is installed, the system displays messages similar to the following: Pinging with 32 bytes of data: Reply from : bytes=32 time<10ms TTL=128 Reply from : bytes=32 time=10ms TTL=128 Reply from : bytes=32 time<10ms TTL=128 Reply from : bytes=32 time<10ms TTL=128 If the program displays the message Bad command or file name, you must install and configure TCP/IP. Note For Terminal Server clients, TCP/IP will already be installed because both ICA and RDP thin client connections require TCP/IP protocol. 35

38 Chapter 3 Configuring the Analyst Add-in for Excel 36

39 4 Configuration After installation, configure Analyst to meet your specific needs. This requires starting Analyst and adding the required libraries and users, defining access rights, and changing the configuration settings as needed. Starting Analyst To start Analyst 1 On the Windows Start menu, select Programs, Cognos Management Series, Planning - Analyst. 2 In the Login Please dialog box, click OK. Leave User Name as the default. The main Analyst screen appears. The Filesys.ini File The Filesys.ini file is the main control file for Analyst. This file tells Analyst where to find the list of libraries, users and groups of users, and defines the directory paths of the Users.tab, Groups.tab, Libs.tab, Padlocks.tab, Locks.log, and Logins.log files. There may be times when it is necessary to edit the Filesys.ini file. For example, during an upgrade or if you install Analyst in a new directory and move the.tab files, you would need to edit the Filesys.ini file. Or, if you install in a new directory but want to keep the libraries that contain models in their original locations, you should move the Users.tab, Groups.tab, Libs.tab, and Padlocks.tab files into the new directory, and then edit the Filesys.ini file and change the directory paths to the.tab files. Editing the Filesys.ini file is not normally required and should be done only with guidance from Technical Support, or as instructed in this guide. 37

40 Chapter 4 Configuration Below is a sample Filesys.ini file. [Cognos] Locks=C:\Program Files\Cognos\epp1\Analyst\System\Locks\LOCKS.LOG Logins=C:\Program Files\Cognos\epp1\Analyst\System\Locks\LOGINS.LOG MaxUsers=5 Users=10000 Libs= [Lib ] Name=Tutorial3 Owner=10000 Description=Contributor Test Model Path=C:\Program Files\Cognos\epp1\Analyst\Examples\Tutorial3\ [Lib 0] Name=Test Owner=10000 Description=Default Library Path=C:\Program Files\Cognos\epp1\Analyst\Lib0\ [User 10000] Name=Admin Address= Phone= Password= DefaultLib=0 [Lib ] Path=C:\Program Files\Cognos\epp1\Analyst\Examples\Tutorial\ Owner=10000 Name=Tutorial Description=Analyst Test Model [Lib ] Path=C:\Program Files\Cognos\epp1\Analyst\Examples\BiF\ Owner=10000 Name=BiF Library Description=Working examples of BiF functionality Adding Libraries and Users The libraries can be added by the system administrator. If this is the first time you have installed Analyst, some libraries already are set up for you. The demonstration files are located in the following libraries (assuming they are installed on the G drive). Analyst Tutorial G:\Program Files\Cognos\epp1\Analyst\ Examples\Tutorial This is used for exercises in the Analyst Tutorial. BiF Library G:\Program Files\Cognos\epp1\Analyst \Examples\BiF This contains examples of BiFs. Contributor Tutorial Model G:\Program Files\Cognos\epp1\Analyst\ Examples\Tutorial3 This is the test model used for Contributor. Analyst Add-in for Excel Tutorial G:\Program Files\Cognos\epp1\Analyst\ Examples\Tutorial This is used for exercises in the Analyst Add-in for Excel Tutorial 38

41 Starting Analyst To allow several users to go through the Tutorial exercises, copy the original files to a different location. If you don t plan for users to go through the exercises, you can remove the example libraries. For model building, you must create the directories (called libraries in Analyst) where users can store their model data. To add libraries 1 In Windows Explorer, create the directories in which to store the data for your users or models. For example, create a directory called H:\Cognos\epp1\Analyst\Examples\Lib01 for the current year and a directory called H:\Cognos\epp1\Analyst\Examples\Lib02 for the next year. Or, you can create directories to store the data for your own models. Note We recommend that you do not store your data in the directory where Analyst is installed. Save your data in another directory, preferably on another drive: For example, Analyst could be installed to G:\Program Files\Cognos\epp1\Analyst, but you could store the current year s data in a H:\Cognos\epp1\Analyst\Examples\Lib01 directory, and the model showing next year s data in a H:\Cognos\epp1\Analyst\Examples\Lib02 directory. 2 Start Analyst and, on the File menu, point to Administration and click Setup Libraries, Users, Groups, Masks. The Table maintenance dialog box appears with the Libraries tab active. The information displayed on the Libraries tab includes the list of available libraries and their associated numbers, directory paths, and owners. 39

42 Chapter 4 Configuration 3 Click Add. 4 In the Add Library dialog box, enter the library name, description, and directory path and click OK. To have the program automatically generate the library number, leave the Library no text box blank. 5 Repeat steps 4 and 5 for each library. The library name and properties appear in the Table maintenance dialog box. 6 In the Table maintenance dialog box, click the Users tab. 7 Add the user properties. Select a user name and click Properties. 8 In the dialog box, type the user number or leave the number blank to generate the number automatically. a Optional. Type the user address and telephone number. b In the Default Library list, select the default library in which to store the user models and data. c Select if the user is a system administrator. For stand alone installations, you must select the System Administrator. The system administrator has access to all user data and models. d Click OK. The user name and properties appear in the Administration dialog box. 9 Click Close. The new libraries now are ready for use. For instructions on setting security access rights within Analyst, see Analyst and Manager Help. 40

43 Starting Analyst Set or Change the Password as a User Passwords can be changed by the user when starting the program. To set or change the password as a user 1 Open Analyst. 2 On the File menu, select Administration and select Setup Libraries, Users, Groups, Masks... 3 Click the Users tab. 4 From the list, select the user you want to change the password for. 5 Click Password. 6 In the appropriate boxes, enter the new password and click OK. 7 In the Table maintenance dialog box, click Close. 41

44 Chapter 4 Configuration Changing Configuration Settings The default configuration settings are for a standard personal computer. You can change the configuration settings for Analyst to optimize performance. These settings control the directory path to the Filesys.ini control file, the maximum workspace size, the keyboard layout, the Undo/ Redo option, and the customized menu options. Changing Filesys.ini File Path, Maximum Workspace, and Keyboard Layout To change the Filesys.ini file path, maximum workspace size, and the keyboard layout 1 On the Tools menu in Analyst, click Options. 2 In the Options dialog box, click the General tab. 3 In the Active Filesys.ini file text box, change the directory path for the Filesys.ini file. By default, the Filesys.ini file is in the C:\Program Files\Cognos\epp1\Analyst directory for a stand-alone installation, and in the G:\Program Files\Cognos\epp1\Analyst directory for a network installation. 4 Optional. In the Maximum Workspace Size (kb) text box, type the new maximum workspace size, in kilobytes. The workspace size controls the amount of memory that Analyst reserves for internal use. The maximum workspace setting depends on the memory of the client workstation. If you store the model data on a network server whose connected client workstations have different memory capacities, you must adjust the maximum workspace settings according to the memory capabilities of each individual client workstation. 42

45 Changing Configuration Settings The following table provides the recommended maximums for a specific amount of RAM. RAM available (MB) Recommended maximum workspace size If you set the maximum workspace too low, the Out of Memory message appears when the system is performing memory-intensive operations such as breakback on a grand total or running a D-Link into a large D-Cube. If you set the maximum workspace too high, the system will begin to use virtual memory (swapping memory to the hard drive), causing performance to slow down dramatically. 5 Optional. In the Maximum simultaneous users text box, type the number of licenses you purchased. Contact your Account Manager for information on acquiring more licenses. 6 Click OK. 7 If you change the maximum workspace setting or the keyboard layout, you must exit Analyst and restart the program for the changes to take effect. On the File menu in Analyst, click Restart. 43

46 Chapter 4 Configuration Enabling the Undo/Redo Option Enabling the Undo/Redo option allows you to retrace your steps when you enter data in a D-Cube. Because retracing steps requires memory, the default mode for this option is disabled. To enable the Undo/Redo option 1 On the Tools menu in Analyst, click Options. 2 In the Options dialog box, click the Undo tab and select the Enable Undo/Redo check box. Note Because of the memory requirements for undoing or redoing data, when entering data in large D-Cubes, you may want to disable the Undo/Redo option. 44

47 Changing Configuration Settings 3 Optional. Change the values described in the following table. Undo Stack Size (excluding D-Cube data) D-Cube Data Undo Stack Size Maximum Undoable View Size (StackBytes) The amount of memory, in kilobytes, to allocate to undoing any operation except data entry in D- Cube cells. The default size is 1024 (1 MB). To allocate memory to undoing data entry in D-Cube cells, see the D-Cube Data Undo Stack Size option later in this table. (CubeStackBytes in the CP section of the Windows Registry) The amount of available memory, in kilobytes, that Analyst can use to store the cell data to undo or redo. When calculating the number of levels of undo allowed, the program counts the total number of cells in the selection, not the number of cells actually changed. Generally, 8 kilobytes is needed for each cell that is to be undone or redone. For example, if D-Cube Data Undo Stack Size = 1024, the system can undo the data entry in the last 128,000 cells (102,4000 / 8 = 128,000). That is, you can undo a 10,000- cell D-Cube selection 12 times, but you can only undo a 128,000-cell D-Cube selection once (assuming that you increased the Maximum Undoable View Size to allow it). (MaxViewCells*8) The amount of memory that controls the number of cells in a D-Cube selection where you want to use the Undo facility. For example, if you set this to 128, a D-Cube selection of more than 16,000 cells cannot be undone (128,000 bytes / 8 bytes a cell = 16,000 cells). 4 Click OK. 5 You must exit Analyst and restart the program for the changes to take effect. To implement the changes, in Analyst on the File menu, click Restart and exit the program. When you next start the program, the changes will take effect. 45

48 Chapter 4 Configuration Setting Up Custom Menus and Toolbar Buttons You can define the directory path for special text files used to create custom menus and toolbar buttons. First, you must create the text files. For instructions, see User-Defined Menus and Toolbar Buttons in the Analyst and Manager Help. To set up custom menus and toolbar buttons 1 In Analyst on the Tools menu, click Options. 2 In the Options dialog box, click the Custom tab. 3 In the Custom Menu File text box, type the directory path for your custom menu file. 4 In the Custom Toolbar File text box, type the directory path for your custom toolbar file. 5 Click OK. 6 You must exit Analyst and restart the program for the changes to take effect. To implement the changes, in Analyst on the File menu, click Restart. Setting Languages Optional: You can set the screen and keyboard languages from the Language tab. In the Supported languages list, select a language. In the Keyboard layout list, select a language for your keyboard layout. Obtaining More User Licenses To obtain additional licenses contact your Account Manager. 46