IBM Cognos FSR Version 6.6public.dhe.ibm.com/.../docs/en/6.6.1/installguide_fsr.pdf ·...

IBM Cognos FSRVersion 6.6.1

Installation Guide

��

NoteBefore using this information and the product it supports, read the information in “Notices” on page 47.

Product Information

This document applies to Cognos FSR Version 6.6.1 and may also apply to subsequent releases. To check for newerversions of this document, visit the IBM Cognos Information Centers (http://publib.boulder.ibm.com/infocenter/cogic/v1r0m0/index.jsp).

Licensed Materials - Property of IBM

© Copyright IBM Corporation 2007, 2012.US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contractwith IBM Corp.

http://publib.boulder.ibm.com/infocenter/cogic/v1r0m0/index.jsp

http://publib.boulder.ibm.com/infocenter/cogic/v1r0m0/index.jsp

Contents

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v

Chapter 1. Installation overview . . . . . . . . . . . . . . . . . . . . . . . . . 1IBM Cognos FSR network topology. . . . . . . . . . . . . . . . . . . . . . . . . . . . 1IBM Cognos FSR installation process . . . . . . . . . . . . . . . . . . . . . . . . . . . 2New functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Chapter 2. Hardware and software requirements . . . . . . . . . . . . . . . . . . 5IBM Cognos FSR Client user computer requirements . . . . . . . . . . . . . . . . . . . . . . 5IBM Cognos FSR Database server requirements. . . . . . . . . . . . . . . . . . . . . . . . 6IBM Cognos FSR Web Service requirements . . . . . . . . . . . . . . . . . . . . . . . . . 6

Chapter 3. Database installation . . . . . . . . . . . . . . . . . . . . . . . . . 9IBM Cognos FSR client prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Creating an empty database for Microsoft SQL Server Analysis Server 2005 or 2008 . . . . . . . . . . . 9Starting the IBM Cognos FSR Database installation program . . . . . . . . . . . . . . . . . . . 9Running the IBM Cognos FSR Database installation program . . . . . . . . . . . . . . . . . . . 10

Chapter 4. Client installations . . . . . . . . . . . . . . . . . . . . . . . . . . 11IBM Cognos FSR client prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Running the IBM Cognos FSR client installation program . . . . . . . . . . . . . . . . . . . . 11

Chapter 5. Web Service installation . . . . . . . . . . . . . . . . . . . . . . . 13IBM Cognos FSR Web Service prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . 13Configuring the Internet Information Services server for Web Service . . . . . . . . . . . . . . . . 13

Creating an application pool in Internet Information Services 6 . . . . . . . . . . . . . . . . . 13Creating an application pool in Internet Information Services 7 . . . . . . . . . . . . . . . . . 14Creating a website in Internet Information Services 6 . . . . . . . . . . . . . . . . . . . . 14Creating a website in Internet Information Services 7 . . . . . . . . . . . . . . . . . . . . 15Retrieving Web Service files for Internet Information Services 7 . . . . . . . . . . . . . . . . . 16Confirming that ASP 2.0 is allowed on Windows Server 2003 with Internet Information Services 6 . . . . . 16

Running the IBM Cognos FSR Web Service installation program. . . . . . . . . . . . . . . . . . 16Service account permissions in Microsoft SQL Server . . . . . . . . . . . . . . . . . . . . . 17

Adding permissions for the service account in Microsoft SQL Server Analysis Services 2005 and 2008 . . . . 17Web Service connectivity to the Internet Information Services server . . . . . . . . . . . . . . . . 18

Testing URL connectivity to the Internet Information Services server . . . . . . . . . . . . . . . 18Verifying Web Service connection parameters on the Internet Information Services server . . . . . . . . 18

Common troubleshooting techniques for logging in using the Web Service method . . . . . . . . . . . 18Accessing additional databases using Web Service . . . . . . . . . . . . . . . . . . . . . . 19

Chapter 6. Post-installation tasks . . . . . . . . . . . . . . . . . . . . . . . . 21Configuring Microsoft Windows authentication for Microsoft SQL Server Analysis Services 2005 and 2008 . . . 21Granting database permissions to users or groups in SQL Server Analysis Services 2005 and 2008 . . . . . . 22Access to IBM Cognos FSR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Testing access by logging in to IBM Cognos FSR . . . . . . . . . . . . . . . . . . . . . . 23

Chapter 7. Optional post-installation tasks . . . . . . . . . . . . . . . . . . . . 25Activating additional product features . . . . . . . . . . . . . . . . . . . . . . . . . . 25Activating additional menu options . . . . . . . . . . . . . . . . . . . . . . . . . . . 25Setting macro security for Oracle Hyperion Financial Management (HFM) . . . . . . . . . . . . . . 26Customizing configuration options . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Configuring IBM Cognos FSR to automatically refresh data when an Excel object is saved . . . . . . . . 27Configuring IBM Cognos FSR to always prompt to save in an Excel object . . . . . . . . . . . . . 28Configuring IBM Cognos FSR to disable the Microsoft Excel 2007 compatibility checker . . . . . . . . . 28

© Copyright IBM Corp. 2007, 2012 iii

Configuring IBM Cognos FSR to change the location of the temporary file folder . . . . . . . . . . . 28Configuring IBM Cognos FSR to monitor performance . . . . . . . . . . . . . . . . . . . . 29Configuring IBM Cognos FSR to enable a customized view in the data wizard . . . . . . . . . . . . 29Configuring IBM Cognos FSR to disable default initialization of Microsoft Excel . . . . . . . . . . . 30

Installing Essbase runtime client . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30Languages for the IBM Cognos FSR interface . . . . . . . . . . . . . . . . . . . . . . . . 30

Applying a preferred language on a user's computer . . . . . . . . . . . . . . . . . . . . 32Editing the configuration file for an IBM Cognos FSR language . . . . . . . . . . . . . . . . . 33

Accessing TM1 and Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33Configuring IBM Cognos FSR to access a TM1 account . . . . . . . . . . . . . . . . . . . . 33Configuring IBM Cognos FSR to access a Cognos Controller account . . . . . . . . . . . . . . . 34

Chapter 8. Upgrading from a previous version to IBM Cognos FSR Version 6.6.1. . . . 35Upgrading to Cognos FSR Version 6.6.1 . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Appendix. Multiple versions of Microsoft Office . . . . . . . . . . . . . . . . . . 37Effect of multiple versions of Microsoft Office if you use Microsoft Office 2003 . . . . . . . . . . . . . 37Effect of multiple versions of Microsoft Office if you use Microsoft Office 2007 or Microsoft Office 2010 . . . . 42

Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

iv IBM Cognos FSR Version 6.6.1: Installation Guide

Introduction

The Cognos® FSR Installation Guide is intended for use with IBM® CognosFinancial Statement Reporting (FSR). It describes how to install Cognos FSR.

Cognos FSR is a unified financial governance solution that focuses on improvingfinancial processes and controls, particularly in the final stages before disclosure. Ithelps the finance department improve the timeliness and quality of financialmanagement processes and reporting, facilitate audits, extend enterprise resourceplanning (ERP) transactional controls, and improve financial risk management.

Cognos FSR automates the process of eXtensible Business Reporting Language(XBRL) tagging for compliance with the Security Exchange Commission mandateas well as other XBRL mandates around the world.

Features and benefits:v Enhances internal controls over financial reportingv Improves visibility and audit trail in the entire reporting processv Links source data to report datav Uses prior report as a template for the next reportv Integrates Tag Once XBRL functionv Contains tools to promote collaborationv Delivers workflow and task management toolsv Includes business rules and validationv Has multiple output options, such as XBRL, EDGAR, HTML, Microsoft Word,

PDF, and Adobe InDesign

Audience

This guide is intended for individuals working in the Office of Finance, who needto create, manage, and administer financial reports and workflows that are createdwith Cognos FSR. To use this guide, you should have a strong background indeveloping financial reports for regulatory submission.

Finding information

To find IBM Cognos FSR product documentation on the Web, access the IBMSupport site at http://www.ibm.com/support/docview.wss?uid=swg27024548. Youcan also find PDF versions of the product release notes and installation guidesdirectly from IBM Cognos product disks.

To view Cognos FSR help in the product, click Help > Content.

Accessibility features

This product does not currently support accessibility features that help users witha physical disability, such as restricted mobility or limited vision.

© Copyright IBM Corp. 2007, 2012 v

http://www.ibm.com/support/docview.wss?uid=swg27024548

Forward-looking statements

This documentation describes the current functionality of the product. Referencesto items that are not currently available may be included. No implication of anyfuture availability should be inferred. Any such references are not a commitment,promise, or legal obligation to deliver any material, code, or functionality. Thedevelopment, release, and timing of features or functionality remain at the solediscretion of IBM.

vi IBM Cognos FSR Version 6.6.1: Installation Guide

Chapter 1. Installation overview

This document is intended to help guide you through the installation andconfiguration of IBM Cognos Financial Statement Reporting (FSR).

Cognos FSR provides a comprehensive solution to an organization’s externalreporting requirements by automating the creation of annual reports, 10K reports,10Q reports, board books, and any other statutory or regulatory filings.

Administrators can use Cognos FSR to create a report, and then delegate the workto end users and monitor their progress prior to publishing the final report.Cognos FSR leverages the power of OLAP and relational databases.

Important: For support information about third-party OLAP and relationaldatabase server applications such as Oracle Essbase and Microsoft SQL Server,consult the documentation provided by the software manufacturer. Cognos FSRdocumentation does not document aspects of these components beyond theminimal definitions required to perform specific Cognos FSR configuration tasks.

This document is intended to help guide you through the installation andconfiguration of Cognos FSR. It contains an overview of the high-level architecture,prerequisites, and installation steps. It is organized in sequential order, andtherefore each section should be read and followed in succession to ensure that theCognos FSR installation is a successful one.

IBM Cognos FSR network topologyBefore you install and configure this product, it is important to understand thenetwork topology that it requires.

End users use the IBM Cognos FSR client interface to work with reports and accessfinancial data from various sources. The Cognos FSR client communicates withdata sources (for example, relational or Microsoft Excel files) through the CognosFSR Database Server. OLAP data can be retrieved through the Cognos FSRDatabase, or directly from an OLAP database environment.

Cognos FSR uses server processes to coordinate communication from an end userclient to the database environment. Other components include administrator andend user client computers, and existing ERP systems.

Restriction: There is no write-back from the Database Server to the data source.

The following diagram illustrates the high-level technical architecture of CognosFSR.

© Copyright IBM Corp. 2007, 2012 1

�A� - Cognos FSR client computer

�B� - Cognos FSR database server

�C� - OLAP database server

�D� - Relational database server

�E� - Excel or text file

For a relational database environment, the Web Service can optionally be used toprovide a system account to the Cognos FSR client for authentication. The WebService is useful when you do not want to give client accounts direct access to thedatabase.

IBM Cognos FSR installation processInstallation packages are provided for use on 32-bit or 64-bit operating systems.Additionally, there are special considerations if you are using Oracle EssbaseVersion 7 software.

The IBM Cognos FSR installation package provides you with all of the requiredelements to successfully install and implement the Cognos FSR solution. CognosFSR consists of a database server and at least one client installation. You candownload the Cognos FSR installation package from IBM Passport Advantage®.

Important: Separate installation packages are provided for installation on 32-bit or64-bit operating systems. If you are accessing data from an Oracle Essbase Version

Figure 1. Architecture diagram

2 IBM Cognos FSR Version 6.6.1: Installation Guide

7 environment, the 32-bit version must be installed because Oracle Essbase Version7 does not support 64-bit installations. For Essbase Version 11.1.2.1, the 64-bit clientis supported through Essbase MDX. For standard report script, you must use the32-bit version of the client.

The Cognos FSR software solution consists of the following installations:v Cognos FSR Database Server installationv Cognos FSR Client installationv Optionally, Web Service installation

New functionalityThe latest version of IBM Cognos FSR contains several new features.

The following new features are included in Cognos FSR (including XBRL):v Native support for Microsoft Office 2007 and Microsoft Office 2010. You can now

work with your reports in native Microsoft Office 2003, Microsoft Office 2007,and Microsoft Office 2010.

v Adobe InDesign integration. If you plan to output your report to AdobeInDesign, versions CS 3 and CS 5.5, you can tag your data in Cognos FSR tomake formatting simpler when you import into Adobe InDesign.

v Localization of the Cognos FSR interface. You can now view the interface inseveral languages in addition to English.

v Ability to enable and disable users without deleting user data. If a user will notbe using Cognos FSR for a period of time, the administrator can now specifythat the user is inactive without having to delete the user's data and thenrecreate it when the user becomes active again.

v Additional configuration options. New configuration options are available, suchas performance monitoring, the ability to specify the location for temporary files,and customized views.

v Microsoft PowerPoint: Export to Microsoft PowerPoint 2007 and MicrosoftPowerPoint 2010 is now supported.

v SEC. Support for new US-GAAP 2012 taxonomy and updates to EFM (EDGARFiler Manual) validations is now provided.

v US GAAP 2012 (Taxonomy and EFM updates). Support for US-GAAP 2012 isnow provided.

v Solvency II. Support for draft taxonomy and specifications is now provided, asoutlined from consultations. Cognos FSR includes new functionality fordimensional tagging and for generating high volumes of XBRL from relationalsources.

v IFRS. Support for the IFRS international standard taxonomy with newfunctionality to reference linkbases directly is now provided.

Chapter 1. Installation overview 3


Chapter 2. Hardware and software requirements

Before you can install the software for IBM Cognos Financial Statement Reporting(FSR), you must ensure that all computers that will run and access this softwaremeet hardware and software requirements.

User client computers, database server computers, and computers that run a WebService have different hardware and software requirements.

IBM Cognos FSR Client user computer requirementsClient user computers must meet platform, software, hardware, and accessrequirements.

Platform requirements

Microsoft Windows XP Professional with SP2 operating system, or later. Windows7, 64-bit is recommended.

Software requirementsv Microsoft Office 2003 with the Microsoft Office Compatibility Pack, Microsoft

Office 2007, and Microsoft Office 2010 are supported in their native mode. If anobject is created in a later version of Microsoft Office, and a user with an earlierversion opens the object, the object opens in Program Compatibility mode. Formore information, see the IBM Cognos FSR Administration Guide.

Important: It is recommended that all users run the same Windows andMicrosoft Office platforms, including the latest service packs. If some users usedifferent versions of Microsoft Office, users of Microsoft Office 2003 must installthe Compatibility Pack. For more information, see the IBM Cognos FSRAdministration Guide. Users must also use the same screen resolution and theymust not change these settings. Normal font style and size should be consistentacross end-user client computers. It is recommended that all users apply thescreen resolution and default font size for Microsoft Excel and Microsoft Word.

v In addition to English, the Cognos FSR interface is available in French, German,Greek, Hebrew, Spanish, and Swedish. It is recommended that the language inwhich the user views Cognos FSR should be the same language that isconfigured in the user's operating system in regional settings. For moreinformation, see “Languages for the IBM Cognos FSR interface” on page 30.

v If you use Oracle Essbase software, connectivity and installation of the correctOracle Essbase Runtime Client software.

v TCP/IP connectivity with OLAP database environment (if applicable).v TCP/IP connectivity to the IBM Cognos FSR Database Server (Microsoft SQL

Server).v For Cognos FSR, NET Framework 3.5 SP1 software, or later, must be installed.

Hardware requirementsv At least 10 GB of free disk space.v Minimum 2 GB RAM. 4 GB RAM is recommended.v Minimum processor speed 2 GHz. 3 GHz is recommended.


Access requirements

For XBRL taxonomies, you need temporary Internet access to required websitesand their web pages:v http://www.xbrl.orgv http://www.xbrl.usv http://taxonomies.xbrl.usv http://xbrl.sec.govv http://www.sec.gov/info/edgar/edgartaxonomies.xmlv http://xbrl.fasb.orgv http://xbrl.iasb.org

IBM Cognos FSR Database server requirementsThe IBM Cognos FSR Database server must meet platform, database managementsystem, and other requirements.


Microsoft Windows Server 2003 operating system, or later. Windows Server 2008 isrecommended.

Database management system requirements

Microsoft SQL Server 2005 or 2008.

Important: SQL Server 2008 is recommended. The SQL Server edition should beStandard or Enterprise. You must create an empty SQL Server database before youinstall Cognos FSR. To connect to SQL Server Analysis Services 2005 or 2008, youmust install the SQL client tools on client computers.

Other requirementsv Minimum 4 GB RAM. 8 GB RAM is recommended.v 50 GB free disk space is recommended for future database growth. This does not

take into account other databases and their respective growth.v Minimum 2 CPUs at 3.x GHz.v Network bandwidth of 100 Mbps (minimum). 1 Gbps is recommended.v Minimum database permissions required:

– read/write– execute stored procedures– select views

IBM Cognos FSR Web Service requirementsIf you are implementing Web Service (system account solution), the servercomputer must meet platform and software requirements.


The server computer must be running the Microsoft Windows Server 2003operating system, or later.


http://www.xbrl.org

http://www.xbrl.us

http://taxonomies.xbrl.us

http://xbrl.sec.gov

http://www.sec.gov/info/edgar/edgartaxonomies.xml

http://xbrl.fasb.org

http://xbrl.iasb.org

Software requirementsv Microsoft Internet Information Services (IIS) Version 6.0 software, or later, must

be installed.

Important: The IBM Cognos FSR Web Service installer can only be used for IISVersion 6.0. To retrieve the web service files for IIS Version 7.0, refer to“Retrieving Web Service files for Internet Information Services 7” on page 16.

v For IBM Cognos FSR, Microsoft .NET Framework 3.5 SP1 software, or later, mustbe installed

Chapter 2. Hardware and software requirements 7


Chapter 3. Database installation

The IBM Cognos Financial Statement Reporting (FSR) Database is contained in aseparate installation program. To use Cognos FSR, the installation of the CognosFSR Database is mandatory.

IBM Cognos FSR client prerequisitesBefore you install the Cognos FSR Database, ensure that all database prerequisitesare met.

For more information, see “IBM Cognos FSR Database server requirements” onpage 6.

Creating an empty database for Microsoft SQL Server Analysis Server2005 or 2008

If you use Microsoft SQL Server Analysis Server 2005 or 2008, you must create anempty Microsoft SQL Server database before you can set up the IBM Cognos FSRdatabase.

Before you begin

Important: For the user credentials used to create the database, administratoraccess to SQL Server is required, with permissions to create a database.

Procedure1. Launch SQL Server Management Studio. The Connect to Server window

opens.2. For Server Type, click Database Engine from the menu.3. For Server Name, select the server that you want to create a database for.4. For Authentication, select the type of authentication that you want to log in

with.5. For Login, enter your username.6. For Password, enter your password.7. Click Connect. The SQL Server Management Studio window opens.8. Right-click Databases, and click New Database. The New Database window

opens.9. Enter a unique database name that is not currently in use within SQL Server

Management Studio.10. Click OK. The new database is created.11. To close SQL Server Management Studio, click File > Exit.

Starting the IBM Cognos FSR Database installation programAfter you create an empty database, you must download the Cognos FSR databaseinstallation program and extract its contents.


Procedure1. Download Cognos FSR Version 6.6.1 from IBM Passport Advantage and follow

the instructions in the download document available at http://www.ibm.com/support/docview.wss?uid=swg27024548.

2. Use a file compression utility to extract the contents from the .zip file to alocation on the local drive.

3. Use Windows Explorer to locate the setup.exe file in the root folder of theextracted .zip file (...\FSR Database Setup\setup.exe).

4. Double-click setup.exe to begin installation.

Running the IBM Cognos FSR Database installation programAfter you download the Cognos FSR Database installation program and extract itscontents, you must install the Cognos FSR Database.

Procedure1. Double-click the setup.exe file to start the installation wizard. The Setup

wizard window opens.2. Click Next. The License Agreement step opens.

v Select I Agree.3. Click Next. The Specify Databases and FSR Administrator step opens.4. Enter the Production Database name and an Administrator name. The

database name must have the same name as the empty database that wascreated specifically for Cognos FSR. The administrator name is for theproduction database instance that you are installing to.

5. Click Next. The Select Installation Folder step opens.6. Specify the folder path where you want to install the FSR database. Click

Browse and navigate to a new folder path if you want to change the defaultfolder.

7. Select the appropriate option to specify who can use the FSR client:v Everyone. Select this option to install the application for anyone who uses

the computer.v Just me. Select this option to restrict access to a single user only.

Important: It is highly recommended that you select Everyone unless there isa specific reason why you cannot select this option.

8. Optionally, you can click Disk Cost to view the available disk space on allavailable drives to which you can install the Database. The Disk Spacewindow opens. When you are finished, click OK to close the Disk Spacewindow.

9. Click Next. The Confirm Installation step opens.10. Click Next. The installation wizard installs the FSR Server with the parameters

that you specified. A message is displayed when the installation is complete.11. Click Close to exit the installation wizard.




Chapter 4. Client installations

The IBM Cognos Financial Statement Reporting (FSR) client is a tool that providesa collaborative user environment. It must be installed on individual administratorand user client computers.

Separate installation packages are provided for installation on 32-bit or 64-bitoperating systems. If you are accessing data from an Oracle Essbase Version 7environment, the 32-bit version must be installed because Oracle Essbase Version 7does not support 64-bit installations. For Essbase Version 11.1.2.1, the 64-bit clientis supported through Essbase MDX. For standard report script, you must use the32-bit version of the client. Ensure that you install the appropriate installationpackage for your operating system.

Important: When you are upgrading to Cognos FSR Version 6.6.1, the old versionof both the Cognos FSR Web Service and client must be uninstalled before you caninstall the new version. You do not have to uninstall the Cognos FSR database.

IBM Cognos FSR client prerequisitesBefore you install the Cognos FSR client, ensure that all client prerequisites aremet.

Before installation, ensure that all client prerequisites are met. For moreinformation, see “IBM Cognos FSR Client user computer requirements” on page 5.

Running the IBM Cognos FSR client installation programAfter you download the Cognos FSR client installation program and extract itscontents, you must install the client software on all administrator and end usercomputers.

Before you begin

Before you run the installation program, ensure that the computer on which youare installing the software meets all the hardware and software prerequisites. Thecomputer must also comply with all required software, hardware, andpre-installation configuration parameters. For more information, see “IBM CognosFSR Client user computer requirements” on page 5.

Procedure1. Double-click the setup.exe file to start the installation. The Setup wizard

opens.2. Click Next. The License Agreement step opens.

v Select I Agree.3. Click Next. The Specify Database and Web Service URL step opens.

v Enter a Database Server name. The default server is (local).v Enter a Database Name. The default name is FSR.v If you are using web service, enter a valid URL in the Web Service URL

field.4. Click Next. The Select Installation Folder step opens.


5. Specify the path where the Cognos FSR client will be installed. If you want tochange the default destination folder, click Browse and navigate to a newfolder path. The default folder is: C:\Program Files\IBM\Cognos FSR\

6. Select the appropriate option to specify who can use the FSR client:v Everyone. Select this option to install the application for anyone who uses

the computer.v Just me. Select this option to restrict access to a single user only.

Important: It is highly recommended that you select Everyone unless there isa specific reason why you cannot select this option.

7. Optionally, you can click Disk Cost to view the available disk space on allavailable drives to which you can install the Cognos FSR client application.The Disk Space window opens. When you are finished, click OK to close theDisk Space window.

8. Click Next. The Confirm Installation step opens, indicating that theinstallation program is ready to begin.

9. Click Next. The installation program runs and the Cognos FSR clientapplication is installed in the folder that you specified earlier. When thesoftware is installed, the Installation Complete step opens, informing you thatthe Cognos FSR client is installed and ready for use.

10. Click Close to exit the installation wizard.


Chapter 5. Web Service installation

Web Service is an optional portion of the installation process. Users of this methodin IBM Cognos Financial Statement Reporting (FSR) log in based on a systemaccount that is created in Microsoft SQL Server.

When users log in with credentials from a system account that is created in SQLServer, they do not need to specify a username or password while they log in toCognos FSR. The system automatically authenticates the users based on theaccount specified in the database.config file for Web Service. After the initial stepin the authentication is bypassed, Cognos FSR confirms the user's Windows loginfrom the dbo.TxUser table, and authorizes the user within the application.

Important: The Web Service setup method prevents users from having access tothe Cognos FSR database. Cognos FSR supports Active Directory.

Installing Web Service is a process that requires configuration on InternetInformation Server web server, installation of Cognos FSR Web Service, andconfiguration on the database.

IBM Cognos FSR Web Service prerequisitesBefore you install Web Service for Cognos FSR, ensure that all Web Serviceprerequisites are met.

For more information, see “IBM Cognos FSR Web Service requirements” on page 6.

Configuring the Internet Information Services server for Web ServiceBefore you can install Web Service for IBM Cognos FSR, you must create a CognosFSR application pool and website on the Internet Information Services (IIS) server.

Restriction: The IBM Cognos FSR Web Service installer can only be used for IIS 6.To retrieve the web service files for IIS 7, see “Retrieving Web Service files forInternet Information Services 7” on page 16.

Creating an application pool in Internet Information Services 6Before you can install Web Service for IBM Cognos FSR, you must create a CognosFSR application pool on the Internet Information Services (IIS) 6 server.

Procedure1. Start Internet Information Services (IIS) Manager.2. Under the Internet Information Services folder, right-click the Application

Pools subfolder, and click New > Application Pool. The Add New ApplicationPool window opens.

3. In the Application pool ID field, specify the application pool ID, and selectUse default settings for new application pool.

4. Click OK. The application pool is created and located in the Application Poolsroot folder.

5. Right-click the application pool and select Properties. The Properties windowopens.


6. In the Identity tab, select Predefined and select Network Service from the list.7. Click Apply, and then click OK.

Results

The application pool is configured.

Tip: If the Predefined button is already selected with Network Service as thedefault in the drop-down list, then click directly on OK.

Creating an application pool in Internet Information Services 7Before you can install Web Service for IBM Cognos FSR, you must create a CognosFSR application pool on the Internet Information Services (IIS) 7 server.

Procedure1. Start Internet Information Services (IIS) Manager.2. Under the root folder, right-click the Application Pools subfolder, and select

Add Application Pool. The Add Application Pool window opens.3. In the Name field, enter the name of the application pool.4. In the Managed pipeline mode list, click Classic.5. Click OK. The application pool is created.6. Click the Application Pools subfolder. The application pools are displayed on

the right.7. Right-click the application pool that was created and click Advanced Settings

from the menu. The Advanced Settings window opens.8. Under the General group, click Enable 32-Bit Application, and select True

from the list in the second column.9. Under the Process Model group, click Identity. Click the ellipsis icon in the

second column. The Application Pool Identity window opens.10. Click Build-in account and select Network Service from the list.11. Click OK. The Advanced Settings window opens.12. Click OK.

Results

The settings are saved for the application pool.

Creating a website in Internet Information Services 6Before you can install Web Service for IBM Cognos FSR, you must create a CognosFSR website on the Internet Information Services (IIS) 6 server.

Procedure1. Start Internet Information Services (IIS) Manager.2. Under the Internet Information Services folder, right-click the Web Sites

subfolder, and click New > Web Site. The Web Site Creation wizard opens.3. Click Next. The Web Site Description step opens.4. Enter a description for the website.5. Click Next. The IP Address and Port Settings step opens.6. Select or enter an IP address, enter the TCP port for the website and enter the

Host header for the website.


7. Click Next. The Web Site Home Directory step opens.8. Enter C:\inetpub\wwwroot in the Path field. This is the home directory where

the website will be located on the server.9. Clear the Allow anonymous access to this Web site check box.

10. Click Next. The Web Site Access Permissions step opens.11. Select the Read, Run scripts, and Execute check boxes.12. Click Next. If the website creation was successful, the following message is

displayed: You have successfully completed the Web Site Creation Wizard.13. Click Finish to exit the wizard.

Results

The website is created and located in the root folder of the website.

Important: If the following message is displayed: The Web Site Creation Wizarddid not complete successfully, check the IP address, port and Host headervalues to ensure they are unique. You can install only one website in the same IPaddress and same port unless you perform virtual hosting.

Creating a website in Internet Information Services 7Before you can install Web Service for IBM Cognos FSR, you must create a CognosFSR website on the Internet Information Services (IIS) 7 server.

Before you begin

Ensure that IIS Windows Authentication and the ASP.NET package is installedbefore creating a website.

Procedure1. Start Internet Information Services (IIS) Manager.2. Under the root folder, right-click the Sites subfolder, and select Add Web Site.

The Add Web Site window opens.3. Enter a site name.4. Click Select.5. Select the Cognos FSR application pool from the list.6. Click OK.7. Enter C:\inetpub\wwwroot\<Site name> in the Physical path field. This is the

home directory where the website will be located on the server.8. Select or enter an IP address.9. Enter the port.

10. Click OK. The website is created.11. In the IIS Manager tree, click the Cognos FSR web site under the Sites folder.12. On the right, click the Features View button on the bottom.13. Double-click the Authentication button. The Authentication pane opens.14. In the table, right-click Anonymous Authentication and select Disable. The

table updates.15. In the table, ensure that Windows Authentication is set to Enabled. If it is not

enabled, right-click Windows Authentication, and select Enable. The tableupdates.

Chapter 5. Web Service installation 15

Results

The Cognos FSR website is now installed and configured.

Retrieving Web Service files for Internet Information Services7

You can retrieve Web Service files for Internet Information Services (IIS) 7 in IBMCognos FSR.

About this task

You can retrieve Web Service files for Internet Information Services 7.

Restriction: The Cognos FSR Web Service installer can only be used for IIS 6.

Procedure1. Start the Web Service installer on an IIS 6 environment.2. Navigate to the location where all Web Service files have been saved. The

default location is C:\inetpub\wwwroot.3. Right-click the folder and click Copy.4. Navigate to the same folder location in IIS 7. Right-click the folder and click

Paste. Your Web Service files from IIS 6 have now been saved in IIS 7.5. Verify the database connection string being used to connect to the database

server in the database.config file. For more information see Verifying WebService connection parameters on the Internet Information Services server.

Confirming that ASP 2.0 is allowed on Windows Server 2003with Internet Information Services 6

Before you can install Web Service for Cognos FSR, you must confirm that ASP 2.0is allowed on Windows Server 2003 with Internet Information Services (IIS) 6.

Procedure1. Start Internet Information Services (IIS) Manager.2. Under the root folder, click the Web Service Extensions folder. The Web

Service Extensions list opens on the right.3. In the list, verify the status of ASP.NET v2.0 is set to Allowed.4. If it is set to Prohibited, right-click ASP.NET v2.0, and click Allow.

Running the IBM Cognos FSR Web Service installation programAfter you configure Internet Information Services for the Web Service, you can runthe Cognos FSR Web Service installation program.

Before you begin

Before you run the installation program, ensure that the computer on which youare installing the software meets all the prerequisites. It must comply with allsoftware, hardware, and preinstallation configuration parameters, as required.

Procedure1. Double-click the setup.exe file to start the installation wizard. The Setup

wizard opens.


2. Click Next. The License Agreement step opens.v Select I Agree.

3. Click Next. The Select Installation Address step opens.4. Select the website that was created for Web Service.5. Enter a virtual directory folder name. The default value is fsrwebservice.6. Select the application pool that was created for Web Service.7. Optionally, you can click Disk Cost to view the available disk space on all

available drives to which you can install the Web Service. The Disk Spacewindow opens. When you are finished, click OK to close the Disk Spacewindow.

8. Click Next. The Enter database connection information step opens. Enter thefollowing information:v The server name that the client must access.v The database name that the client must access.v The user ID and password for the service account.

Tip: To provide user access to multiple databases, you need to modify theconfiguration file. Otherwise, the user will not be able to connect to more thanthe database name specified in this step. For more information, see “Accessingadditional databases using Web Service” on page 19.

9. Click Next. The Confirm Installation step opens.10. Click Next. The setup process begins. When the software is installed, the

Installation Complete step opens, informing you that the Cognos FSR webservice is installed and ready for use.

11. Click Close to exit the installation wizard.

Service account permissions in Microsoft SQL ServerAfter you have successfully installed Web Service for IBM Cognos FSR, you mustadd permissions for the service account in SQL Server.

Adding permissions for the service account in Microsoft SQLServer Analysis Services 2005 and 2008

After you have successfully installed Web Service for IBM Cognos FSR, if you arerunning Microsoft SQL Server Analysis Services 2005 or 2008, you must addpermissions for the service account.

Procedure1. Launch SQL Server Enterprise Manager. The SQL Server Enterprise Manager

console opens.2. Expand the Security folder, right-click, and click New > Login. The Login -

New window opens.3. In the Login Name field, enter the user ID of the service account.4. Select SQL Server authentication.5. In the Password and Confirm password fields, enter the password of the

service account.6. Clear the Enforce password expiration check box.7. In the left pane, click User Mapping. The User Mapping window opens.8. In the Users mapped to this login list, select the check box for the database

that was specified for the service account.


9. In the Database role memberships list, select the db_owner and public checkboxes.

10. Click OK. The service account is added.

Web Service connectivity to the Internet Information Services serverAfter you install the Web Service for IBM Cognos FSR, you must test that the WebServer can connect to the Internet Information Services (IIS) server.

Testing URL connectivity to the Internet Information Servicesserver

After you have successfully installed Web Service for IBM Cognos FSR, you musttest URL connectivity to the Internet Information Services (IIS) server.

Procedure1. Open Internet Explorer.2. In the Address field, enter the URL that you want to test.

For example: http://server:81/fsrwebservice/CADesignService.asmxWhere:v server is the server specified during the Cognos FSR Web Service

installation.v 81 is the port number specified during the website creation.v fsrwebservice is the virtual directory specified during the Cognos FSR Web

Service installation.3. Press Enter. The website that you selected opens.

Verifying Web Service connection parameters on the InternetInformation Services server

After you have successfully installed Web Service for IBM Cognos FSR, you mustverify which Web Service connection parameters are in use on the InternetInformation Services (IIS) server.

Procedure1. Open the...\Inetpub\wwwroot\<web site name>\<virtual directory

name>\databases.config file.2. Verify the database connection string being used to connect to the database

server.

Common troubleshooting techniques for logging in using the WebService method

If you are having trouble logging into the IBM Cognos FSR application using theWeb Service method, the issue could exist in Internet Information Services (IIS)Manager or in the Microsoft SQL Server database.

Internet Information Services Managerv Check network connectivity and port settings on the website created for Cognos

FSR in IIS Manager.v Check authentication type of websites. They should be Windows authentication

with no anonymous access.


v Ensure that the website has Read, Run, and Execute permissions.v For instances where the Web Service is installed using IIS 6 in a Windows Server

2003 environment, ensure that ASP.NET v2.0 Web service extension is set toallowed.

Microsoft SQL Server databasev Ensure that the connection string has the right database name and SQL server.

They should be the same as how you log in to Cognos FSR.v Ensure that a SQL account is created and mapped to the database.v Ensure that the login ID that is used to log in to the PC is in the Cognos FSR

dbo.TxUser table.

Accessing additional databases using Web ServiceAfter you have successfully installed Web Service for IBM Cognos FSR, you canprovide access to additional databases.

About this task

If the user can access multiple databases, and if you are using Web Service, there isan additional step to configure Web Service. All databases that a user can accessmust be specified in the Cognos FSR databases.config file.

Procedure1. Open Windows Explorer.2. Navigate to the virtual directory subfolder (for example, fsrwebservice),

installed by default to ...\Inetpub\wwwroot\<virtual directory name>.3. In the virtual directory subfolder, right-click and open the databases.config

file using a text editor.4. Modify the databases.config file to include multiple databases:

a. Copy the entire line of code between <databases> and </databases>:<database serverName="TrainerEssC6" databaseName="FSR_10K"connectionString="Provider=SQLOLEDB; Data Source=TrainerEssC6;Initial Catalog=FSR_10K; User id=FSRUser; password=testpassword;" />

b. Paste the code, and modify it to reflect the additional database name andthe connection string. For example, replace references to "FSR_10K" databasewith "FSR_Test_Environment".

5. Repeat the previous step for each additional database that you want to add.6. Save the changes to the databases.config file, and close it.



Chapter 6. Post-installation tasks

After you have successfully installed IBM Cognos Financial Statement Reporting(FSR), you must perform a few additional configuration tasks.v Configure Windows authentication in the database.v Grant users or groups database permissions.v Test access to Cognos FSR.

Configuring Microsoft Windows authentication for Microsoft SQLServer Analysis Services 2005 and 2008

After you have successfully installed IBM Cognos FSR, if you are using SQL ServerAnalysis Services 2005 or 2008, you must configure Windows authentication.


opens.v For Server Type, select Database Engine from the list.v For Server Name, select the server name from the list.v For Authentication, select Windows Authentication.v For Login, enter your username.v For Password, enter your password.

2. Click Connect. The SQL Server Management Studio window opens.3. Right-click Security, and click New Login. The General page of the

Login-New window opens.4. Select the relevant database from the Default database list.5. Click User Mapping in the left pane. The User Mapping page opens.

v Select the check box for the relevant database in the Users mapped to thislogin list.

v Select db_owner in the Database role membership list.6. Click General in the left pane. The General page opens.7. Click Search. The Select User or Group window opens.8. Type the name of the user or group in the Enter the object name to select

field.9. Click Object Types. The Object Types window opens.

10. Select the Groups and Users check boxes.11. Click OK. The Select User or Group window opens.12. Click OK. The Login-New window opens. Click OK to close the window.13. In the SQL Server Management Studio window, navigate to the relevant

database in the left tree, and expand the folder.14. Expand the Security folder, and select Users. The new user is listed in the

Users table on the right.15. In the Users table, right-click the new user, and click Properties. The Database

User window opens.16. Select the db_owner check box in the Database role membership list.17. Click OK. Navigate to the Databases folder and expand.


18. Navigate to the database that you added the user to, and expand the Tablesfolder.

19. Right-click dbo.TxUser, and click Open Table. The table opens.20. In the last row of the table, add the new user and populate the required fields.21. Save the file. Windows authentication is configured for Cognos FSR.

Granting database permissions to users or groups in SQL ServerAnalysis Services 2005 and 2008

After you have successfully installed IBM Cognos FSR, if you use SQL ServerAnalysis Services 2005 or 2008, you must make sure that users and groups haveminimum database permissions in Microsoft SQL Server.

Before you begin

Ensure that the user or group has read and write permissions on the Cognos FSRdatabase.


opens.v For Server Type, select Database Engine from the list.v For Server Name, select the name of the server where the Cognos FSR

database resides.v For Authentication, select the type of authentication you want to log in

with.v For Login, enter your username.v For Password, enter your password.

2. Click Connect. The SQL Management Studio window opens.3. Click the New Query button in the SQL toolbar. A new query window opens.4. In the query window, enter the following code:

create proc FSRAssignPermissionsasbegincreate table tempTable(

procname varchar(500)

)

DECLARE @str VARCHAR(1000)set @str=’SELECT ’’GRANT EXECUTE ON ’’ + [name] + ’’ to [UserOrGroup] ’’ AS’’FSR Stored Procedures’’ FROM sys.Procedures WHERE TYPE=’’p’’ ANDis_ms_shipped=0 ORDER BY NAME

SELECT ’’GRANT SELECT ON ’’ + [name] + ’’ to [UserOrGroup] ’’ AS’’FSR Select Views’’ FROM sys.Views WHERE TYPE=’’V’’AND is_ms_shipped=0 ORDER BY NAME

’insert into tempTable

exec (@str)

endgoexec FSRAssignPermissionsDECLARE @name VARCHAR(500) -- database name


DECLARE db_cursor CURSOR FORSELECT procnameFROM tempTableOPEN db_cursorFETCH NEXT FROM db_cursor INTO @nameWHILE @@FETCH_STATUS = 0BEGINselect @name

exec (@name)FETCH NEXT FROM db_cursor INTO @name

ENDCLOSE db_cursorDEALLOCATE db_cursordrop table tempTabledrop proc FSRAssignPermissions

Where UserOrGroup is the unique user or group name that you are grantingpermissions for.

5. Select the correct database from the Available Databases list.6. Click Execute. The query executes, and the results are shown in the Results

pane.7. In Object Explorer, in the left pane, navigate to the Database folder, and

expand the Cognos FSR database folder.8. Expand to Security > Users. Right-click the user or group that you granted

permissions for and click Properties. The Database User window opens.9. Click Securables in the left pane. The Securables window opens.

10. In the Securables list, verify that the Stored procedure and View permissionshave been added.

Access to IBM Cognos FSRAfter you have successfully installed Cognos FSR, you can use various loginoptions to access Cognos FSR from client computers.

Cognos FSR can be accessed from the following Start menu path: Start > AllPrograms > IBM Cognos Financial Statement Reporting > IBM Cognos FinancialStatement Reporting

After Cognos FSR has been installed and configured properly, end users can accessthe application on their client computer (if their computer has the appropriatenetwork connections to the Cognos FSR Server and Database).

Depending on your configuration, you might have the following login options:v Windows Authentication. Cognos FSR supports instances where Microsoft

Windows authentication is used to log in to Microsoft SQL Server. The Windowsuser name and password are used with Cognos FSR as a single point of login.

v SQL Server. Users can use SQL Server login accounts to authenticate against theCognos FSR database.

v Web Service. Users can log in via Web Service with a valid URL.

Testing access by logging in to IBM Cognos FSRAfter you have successfully installed Cognos FSR, you should test access toCognos FSR to ensure that it is running correctly and that the end users canconnect to it.

Chapter 6. Post-installation tasks 23

Procedure1. On a remote client computer, open the Cognos FSR application with the

Windows Start menu. If the application is correctly installed, the login windowopens.

2. Specify a valid server and database name for Cognos FSR.3. Enable the login method:

Table 1. Login methods

Method Action

Log in to SQL Servervia WindowsAuthentication

Select Log in to SQL Server and select using WindowsAuthentication.

Log in to SQL Servervia SQL Server Account

Select Log in to SQL Server and select using SQL Serveraccount. Enter the User ID and Password of the account.

Log in via Web Service Select Log in via Web Service. Enter a URL for Web Service, forexample: http://server:port/fsrwebservice

Where:

v server is the server specified during the Cognos FSR WebService installation.

v port is the port number specified during the website creation.

v fsrwebservice is the virtual directory specified during theCognos FSR Web Service installation.

4. To save the current login details and automatically log you in for the nextsession, click Automatically log in next time.

5. To sign in with the credentials that you specified, click Log In. If yourconnection is successful, Cognos FSR lists all existing reports in the SelectReport window.

6. Click the report that you want to view, and click OK. The report opens.


Chapter 7. Optional post-installation tasks

Depending on the features that you are using in your instance of IBM CognosFinancial Statement Reporting (FSR), you might need to perform several optionalconfiguration tasks.

Activating additional product featuresAfter you have successfully installed IBM Cognos FSR, you can activate additionalproduct features.

About this task

You can activate additional product features by modifying the dbo.TxVersion tablein Microsoft SQL Server Management Studio.

Important: Administrator level access is required to add license keys to thedatabase.

Procedure1. Launch SQL Server Management Studio. The Connect to Server window opens.

v For Server Type, select Database Engine from the menu.v For Server Name, select the name of the server where the Cognos FSR

database resides.v For Authentication, select the type of authentication that you want to log in

with.v For Login, enter your username.v For Password, enter your password.

2. Click Connect. The SQL Management Studio window opens.3. Select the Cognos FSR database and expand the view. Expand the Tables folder

and navigate to dbo.TxVersion.4. Right-click dbo.TxVersion and click Open Table. The table opens.5. You can enable the following features:

v XBRL. Type 1 in the XBRLLic field.v Edgarization. Type 1 in the Edgarization field.

6. When are you finished enabling features, save the changes and exit SQLManagement Studio.

7. In Cognos FSR, open a report and click Administrators > Users.8. Grant permissions to Cognos FSR users by selecting the appropriate check

boxes for each feature (for example, XBRL Enabled). You can now use thefeatures in Cognos FSR.

Activating additional menu optionsAfter you have successfully installed IBM Cognos FSR, you can activate additionalmenu options.


About this task

By default, the following options are disabled in Cognos FSR:

Table 2. Menu options

Menu option Location in interface

Account Mapping Forms > Account Mapping

Adjustments Tools > Adjustments

Custom Groups Select Report window

Customized Views Data wizard

Global Variables Administration > Global Variables

Master Outline Administration > Master Outline

Recalculate Tools > Recalculate

Relational Database Data wizard

You can enable these options if necessary.

Procedure1. Open Windows Explorer.2. Navigate to the path where the Cognos FSR client was installed. The default

folder is: C:\Program Files\IBM\Cognos FSR\

3. Open the Clarity.FSR.UI.exe.config file.4. Locate the EnableLegacyAccountMapping key:

<add key="EnableLegacyAccountMapping" value="false" />

5. Modify the key:v By default, the value is set to "false". The options are disabled.v The value can be set to "true". The options are enabled.

6. Save the changes to the Clarity.FSR.UI.exe.config file.

Setting macro security for Oracle Hyperion Financial Management(HFM)

After you have successfully installed IBM Cognos FSR, if your organization usesOracle Hyperion Financial Management (HFM) with Cognos FSR, you canconfigure some Microsoft Excel settings.

Procedure1. In Excel, click Tools > Options > Security, and click Macro Security.2. Set the Security level to Medium (or lower).3. In the Trusted Publishers tab, enable the Trust access to Visual Basic Project

setting.4. Click OK to save the settings.

Customizing configuration optionsAfter you have successfully installed IBM Cognos FSR, you can customize the waythat Cognos FSR works.


About this task

You can customize configuration options for Cognos FSR.



3. Open the Clarity.FSR.UI.exe.config file and set the following options:a. Refresh data on save. Automatically refresh data after saving an Excel

object.b. Enable custom groups. Allows users to filter a report based on a custom

group in the Select Report window.c. Always prompt to save in an Excel object. Automatically save an Excel

object if users navigate from the object.d. Disable Excel 2007 Compatibility Checker. Turn off the compatibility

checker feature for Excel 2007.e. Change location of temporary objects folder. Allows users to choose

their own temporary folder for Cognos FSR objects.f. Monitor Performance. Allows users to identify bottlenecks during report

generation.g. Customized View. Allows users to enable this option in the data source

wizard.h. Default Excel Initialization. Determines whether or not Cognos FSR

uses the default method of initializing Excel or an alternative method.

Configuring IBM Cognos FSR to automatically refresh datawhen an Excel object is saved

By default, users are prompted with a confirmation window to refresh data afterthey save changes to an Excel object. However, you can configure Cognos FSR torefresh data automatically after users save an Excel object.



3. Open the Clarity.FSR.UI.exe.config file.4. Locate the RefreshDataOnSave key:

<add key="RefreshDataOnSave" value="false" />

5. Modify the key:v By default, the value is set to "false". Data is automatically refreshed when

the object is saved. No prompt is displayed.v The value can be set to "true". A prompt always opens to confirm that the

user wants data to be refreshed when the object is saved.6. Save the changes to the Clarity.FSR.UI.exe.config file.

Chapter 7. Optional post-installation tasks 27

Configuring IBM Cognos FSR to always prompt to save in anExcel object

By default, changes are not saved in an Excel object if a user navigates from theobject without saving. However, you can configure Cognos FSR so that a user isalways prompted to save when navigating from an Excel object.



3. Open the Clarity.FSR.UI.exe.config file.4. Locate the AlwaysPromptToSaveExcel key:

<add key = "AlwaysPromptToSaveExcel" value = "false" />

5. Modify the key:v By default, the value is set to "false". The user is not prompted with a

confirmation window.v The value can be set to "true", and the user is prompted to save when

navigating to another object.

Tip: It is recommended to set the AlwaysPromptToSaveExcel value to "true".Otherwise, Cognos FSR does not automatically save data, and content changesmight be lost after users navigate from the object.


Configuring IBM Cognos FSR to disable the Microsoft Excel2007 compatibility checker

By default, the compatibility checker feature for Excel 2007 is enabled in CognosFSR. You can configure Cognos FSR to disable this feature.



3. Open the Clarity.FSR.UI.exe.config file.4. Locate the last key in the file (for example, <add key=...), and place your

cursor after the > character. Press Enter.5. Add the following code: <add key="AllowExcelCompatibilityChecker" value

= "false" />


Results

The compatibility checker feature for Excel 2007 is disabled.

Tip: You can re-enable this feature by changing the key value to true.

Configuring IBM Cognos FSR to change the location of thetemporary file folder

You can configure Cognos FSR to change the location of the temporary file folder.




3. Open the Clarity.FSR.UI.exe.config file.4. Locate the TempPath key:

<add key="TempPath" value="false" />


the object is saved. No prompt is displayed.v The value can be set to "true". Specify the location where the temporary files

will be saved. A prompt always opens to confirm that the user wants data tobe refreshed when the object is saved.


Results

The location of the temporary file folder is changed.

Important: For Office 2010 users, ensure that the file directory is added to theTrust Center's Trusted Location configuration. For more information about workingwith Microsoft Office, see Microsoft documentation or Microsoft online help.

Configuring IBM Cognos FSR to monitor performanceYou can configure Cognos FSR to monitor performance to identify bottlenecksduring report generation in Cognos FSR.



3. Open the Clarity.FSR.UI.exe.config file.4. Locate the MonitorPerformance key:

<add key="MonitorPerformance" value="false" />


the object is saved. No prompt is displayed.v The value can be set to "true". A prompt always opens to confirm that the


Configuring IBM Cognos FSR to enable a customized view inthe data wizard

By default, the customized view option is disabled in Cognos FSR. You canconfigure Cognos FSR to enable this feature.




3. Open the Clarity.FSR.UI.exe.config file.4. Locate the CustomizedView key:

<add key = "CustomizedView" value = "false" />

5. Modify the key:v By default, the value is set to "false". The user is not prompted with a

confirmation window.v The value can be set to "true", and the user is prompted to save when

navigating to another object.6. Save the changes to the Clarity.FSR.UI.exe.config file.

Configuring IBM Cognos FSR to disable default initializationof Microsoft Excel

You can configure Cognos FSR to change whether Cognos FSR uses the defaultmethod of initializing Excel or an alternative method. An alternative method isused when add-ins are not loading properly.



3. Open the Clarity.FSR.UI.exe.config file.4. Locate the DefaultExcelInitialization key:

<add key="DefaultExcelInitialization" value="true" />

5. Modify the key:v By default, the value is set to "true". Data is automatically refreshed when

the object is saved. No prompt is displayed.v The value can be set to "false". A prompt always opens to confirm that the


Installing Essbase runtime clientIBM Cognos FSR supports versions 7, 9, and 11 for the Oracle Essbase runtimeclients. You can install the Essbase runtime client if necessary.

For Essbase connectivity, you must obtain and install the correct runtime client onthe Cognos FSR end user client.v For Essbase Version 7.x, use a version 7 runtime client.v For Essbase Version 9.x, use a version 9 runtime client.v For Essbase Version 11.x, use a version 11 runtime client.

Important: When you use Essbase, you must configure the ARBORPATH andPATH variables. Set both variables to point to the Essbase runtime client.

Languages for the IBM Cognos FSR interfaceIn addition to English, the IBM Cognos FSR interface is available in French,German, Greek, Hebrew, Spanish, and Swedish. When a particular language isconfigured on a user's computer, the user can work with the Cognos FSR interfacein the selected language.


Important: It is recommended that the language in which the user views CognosFSR should be the same language that is configured in the user's operating systemin regional settings. However, for other combinations, view the topics in thissection.

Factors that affect the language of a user's computer

When you set up a language on a user's computer, the setup process depends onthe following factors.

Table 3. Factors that affect the language of a user's computer

Factor Description

Preferred Cognos FSR language Can be English, French, German, Greek, Hebrew, Spanish,or Swedish. If your computer is configured to display anyother language, the language for the Cognos FSR interfaceis English.

Language of the version ofMicrosoft Office that isinstalled on the user'scomputer

Does not have to be the same as the preferred language.

Regional settings When you set the regional settings on the user'scomputer, the Cognos FSR interface is translated to thelanguage specified in the regional settings. For moreinformation about how to change regional settings, seethe Microsoft website.

Installed language packs It is recommended that the language used by the user toview Cognos FSR should be the same as the language ofMicrosoft Office that is installed on the user's computer.The computer automatically has the language packcorresponding to the language of Microsoft Office that isinstalled on the user's computer. For more informationabout how to obtain language packs, and how todetermine which language packs are already installed onthe user's computer, see the Microsoft website.Important: In a localized user environment, Cognos FSRdoes not require the Microsoft Office English languagepack. However, other third-party applications mightrequire it.

Settings in theClarity.FSR.UI.execonfiguration file

If the language of the installed version of Microsoft Officeis not English or the preferred language, then you mustedit two parameters in the Clarity.FSR.UI.execonfiguration file. For more information, see “Editing theconfiguration file for an IBM Cognos FSR language” onpage 33.

Example

If the user wants to see the interface for Cognos FSR in Spanish, and the version ofMicrosoft Office on the user's computer is English, you must ensure that theSpanish language pack is installed on the user's computer (the English languagepack is already installed automatically with the English version of MicrosoftOffice). In some situations, you might also need to edit two parameters in theClarity.FSR.UI.exe configuration file. For more information, see “Editing theconfiguration file for an IBM Cognos FSR language” on page 33.


Applying a preferred language on a user's computerWhen a particular language is configured on a user's computer, the user can workwith the IBM Cognos FSR interface in the selected language. You can set up auser's computer to use the language preferred by the user.

About this task

In addition to English, the Cognos FSR interface is available in French, German,Greek, Hebrew, Spanish, and Swedish. To configure one of these languages for auser, you need to know the language of the installed version of Microsoft Office.You also might need to work with regional settings, language packs, and theClarity.FSR.UI.exe configuration file. The computer automatically has thelanguage pack corresponding to the language of Microsoft Office that is installedon the user's computer.

Important: For more information about changing regional settings or installinglanguage packs, see the Microsoft website. For more information about editing theClarity.FSR.UI.exe configuration file, see “Editing the configuration file for anIBM Cognos FSR language” on page 33.

Procedure1. If the user prefers to view the Cognos FSR interface in English, complete one of

the following steps:v If the language of the installed version of Microsoft Office is English, you

might need to change the regional settings. For example, you might selectEnglish - United States or English - United Kingdom to ensure that theuser sees the correct date and time formats, currency, and measurements forthe region. You do not need to edit the Clarity.FSR.UI.exe configurationfile.

v If the language of the installed version of Microsoft Office is French, German,Greek, Hebrew, Spanish, or Swedish, you must make sure that two languagepacks are installed: English and the language of the installed version ofMicrosoft Office.

Important: In this situation, you must also edit the Clarity.FSR.UI.execonfiguration file to override the regional settings.

2. If the user prefers to view the Cognos FSR interface in French, German, Greek,Hebrew, Spanish, or Swedish, complete one of the following steps:v If the language of the installed version of Microsoft Office is English, make

sure that two Microsoft Office language packs are installed: English and thepreferred language. You must also change the regional settings. For example,if the preferred language is Spanish, you might select Spanish - Spain orSpanish - Mexico to ensure that the user sees the correct date and timeformats, currency, and measurements for the region. You do not need to editthe Clarity.FSR.UI.exe configuration file.

v If the language of the installed version of Microsoft Office is the same as thepreferred interface language for Cognos FSR, make sure that the MicrosoftOffice language pack for the preferred language is installed.

Important: In a localized user environment, FSR does not require theMicrosoft Office English language pack. However, other third-partyapplications might require it. Also, you must edit the Clarity.FSR.UI.execonfiguration file to override the regional settings.


Editing the configuration file for an IBM Cognos FSR languageWhen a particular language is configured on a user's computer, the user can workwith the IBM Cognos FSR interface in the selected language. To set up thelanguage preferred by the user, you must sometimes edit the Clarity.FSR.UI.execonfiguration file to override the regional settings.

About this task

To determine whether you must edit the Clarity.FSR.UI.exe configuration file, see“Applying a preferred language on a user's computer” on page 32.



3. Open the Clarity.FSR.UI.exe configuration file.4. Edit the LanguageID parameter, and specify the preferred language from the

following list of allowed values:v 0 (German)v 1 (English)v 2 (Spanish)v 3 (French)v 4 (Greek)v 5 (Hebrew)v 6 (Swedish)

For example, <add key="LanguageID" value="2" />

5. Edit the LocaleType parameter, and specify 1 from the following list of allowedvalues. If you specify 0, any selection that you make in the LanguageIDparameter is ignored:v 0 (Operating System Locale)v 1 (User Specified)

For example, <add key="LocaleType" value="0" />

6. Save your changes.

Accessing TM1 and ControllerYou can configure Cognos FSR to access TM1® and Controller accounts.

TM1 supported versions include TM1 9.5.1, TM1 9.5.2, and TM1 10.1.6237.61.Cognos Controller supported versions include Controller 8.5.1 IF7, Controller 8.5.1IF14, Controller 10.1 IF1 (10.1.335), Controller 10.1 IF2 (10.1.348), Controller 10.1 IF3(10.1.352), and Controller 10.1 IF4 (10.1.364).

Important: Macro security must be enabled when you use TM1 or Controller. Formore information about macro security, see the Cognos FSR Administration Guide.

Configuring IBM Cognos FSR to access a TM1 accountYou can configure Cognos FSR to access an account on a TM1 server. You use theCognos TM1 account window to configure access to the TM1 account.


Before you begin

Before you load Cognos FSR, you must have the Cognos TM1 add-in installed onthe client computer, and enabled in Microsoft Excel.

Procedure1. Open any report.2. Click Tools > Set Cognos TM1 Account. The Cognos TM1 Account window

opens.

Important: After you log in to Cognos FSR, the Cognos TM1 Account windowopens automatically. You can connect to only one TM1 server at a time. Youmust input the following information to connect to the target TM1 server, andto ensure that you are not prompted twice when you load an object thatcontains TM1 formulas.

3. In Server, type the name of the TM1 server.4. In User ID, type the user ID for the Cognos TM1 account.5. In Password, type the password for the Cognos TM1 account.

Configuring IBM Cognos FSR to access a Cognos Controlleraccount

You can configure Cognos FSR to access an account on a Cognos Controller server.You use the Cognos Controller Account window to configure access to theController account.

Before you begin

Before you load Cognos FSR, you must have the Cognos Controller add-ininstalled on the client computer, and enabled in Microsoft Excel.

Procedure1. Open any report.2. Click Tools > Set Cognos Controller Account. The Cognos Controller Account

window opens.

Important: After you log in to Cognos FSR , the Cognos Controller Accountwindow opens automatically. You can connect to only one Controller server at atime. You must input the following information to connect to the targetController server, and to ensure that you are not prompted twice when youload an object that contains Controller formulas.

3. In User ID, type the user ID for the account on the Cognos Controller server.4. In Password, type the password for the Cognos Controller account.5. In UDL Name, type the name of the Universal Data Link file that you are

using for storing connection information. This file should be configured on theserver of the Controller.


Chapter 8. Upgrading from a previous version to IBM CognosFSR Version 6.6.1

You can upgrade your current version of Cognos FSR to Cognos FSR Version 6.6.1.

Upgrading to Cognos FSR Version 6.6.1You can use the IBM Cognos Financial Statement Reporting (FSR) DatabaseUpgrade Utility to update the Cognos FSR database to Version 6.6.1.

Before you begin

Make sure that the following prerequisites are met before you start to perform theupgrade.v Microsoft .NET Framework 3.5 SP1 software, or later, must be installedv A previous version of Cognos FSR must be installed.v A backup of the database must be complete.

Important: If you want to use the upgrade utility to do the backup of thedatabase, you must deploy the utility on the same server as the Cognos FSRdatabase. The backup operations are performed locally.

v You must have administrator rights with db.owner permissions. Alternatively,you must be a privileged administrator with the following permissions:– DataReader to run SELECT statements– BackupOperator to run BACKUP statements– DDLAdmin permission to alter procedures– DataWriter to run UPDATE, INSERT, and DELETE statements

v All users must be logged out of Cognos FSR during the upgrade.v The FSR Database Scripts folder must be in the same folder as the utility after

extraction, to ensure that the user extracts all content of the upgrade folder intoone location.

v If taxonomies are used, an export of extended taxonomies must be completed.After you complete the database upgrade, you must also manage anytaxonomies that were in use in your previous version of Cognos FSR. For moreinformation, see the XBRL Reference Guide.

Important: In addition, make note of all additional required schema URIs forboth 2009 and 2011 taxonomies. Load the taxonomy, select Properties, andfollow the Edit Taxonomy wizard. Take note of data such as all explicit importsused, currency, and country.

About this task

This tool replaces previous methods of upgrading the Cognos FSR database andensures that only the required scripts are executed, thus reducing any errorsduring the upgrade process.

Important: The upgrade process might encounter issues if core product databaseobjects, such as stored procedures, views, and tables (including constraints, triggersand statistics), have been modified.


Procedure1. In the <build root folder>\Database\Upgrade\ folder, double-click

FSRDbUpgradeUtility.exe file. The IBM Cognos FSR Database Upgrade wizardwindow opens.

2. In the Server Name field, type the name of the SQL Server.3. In the Authentication field, select Windows Authentication or SQL

Authentication. The Login and Password fields become available and must becompleted with the user ID and password of the service account.

4. In the Database field, type the name of the database to be upgraded.5. Answer the question in the Has a database backup been created yet? field.

You cannot do the upgrade unless a backup of the database is complete.v If the database backup is created, in the Database backup window, select

Yes.v If the database backup is not created, select No and in the Would you like

the utility to create a backup for you?, field, select Yes. If you select No tothis question, the upgrade stops and the Upgrade Aborted message opens.

The utility searches for extended taxonomies. If extended taxonomies arefound, the Extended Taxonomy window opens. If extended taxonomies are notfound, the Upgrading window opens.

6. If the Extended Taxonomy window opens, answer the Has all extendedtaxonomies been exported yet? question. You cannot do the upgrade iftaxonomies are used and were not exported. Taxonomies are erased after thispoint, so you must import them again after the upgrade.v If taxonomies were exported, click Yes.v If extended taxonomies were not exported, click No. The Upgrade Aborted

message opens. For more information, see the prerequisites for exporting thetaxonomies.

7. If the Upgrading window opens, and if you requested the utility to do thebackup of the database, the backup is created before the upgrade. When theupgrade is successful, the Upgrade Completed window opens. Click Finish tocomplete.

Important: If the upgrade fails, or if errors are encountered during the processof upgrading the database or resetting the taxonomy, the database is rolledback to the state before the upgrade began. You can view the log file at c:\yourinstall directory\log.txt.

8. If taxonomies are used, ensure that the exported taxonomies are imported backinto Cognos FSR after the upgrade.


Appendix. Multiple versions of Microsoft Office

Your reports can contain Excel and Word objects. Some aspects of your reports andobjects depend on the version of Microsoft Office that was used to create theobject, and the version of Microsoft Office that you use to open the report.

The following list shows the versions of Microsoft Office that you and other usersof your report might use to create Excel and Word objects:v Microsoft Office 2003v Microsoft Office 2003 with the Microsoft Office Compatibility Pack for Word,

Excel, and PowerPointv Microsoft Office 2007v Microsoft Office 2010

If all objects in your report are created with the same version of Microsoft Office,and all users of your report use the same version of Microsoft Office, you do notneed to read the rest of the topics in this section.

However, if any objects in your report are created with different versions ofMicrosoft Office, or some users use a different version of Microsoft Office, read thefollowing sections for useful tips on how to work with your report and objects.

Important: It is recommended that all users use the same version of MicrosoftOffice. For more information on the impact of mixed environments, see thefollowing topics.

Effect of multiple versions of Microsoft Office if you use MicrosoftOffice 2003

If you use Microsoft Office 2003, some aspects of your reports depend on theversion of Microsoft Office that was used to create various objects. The version ofMicrosoft Office that you use can affect actions such as opening reports andobjects, pasting and exporting objects, and generating reports.

Important: You can use the Compatibility Pack for Word, Excel, and PowerPoint.The compatibility pack upgrades the functionality of Microsoft Office 2003 so thatit works more smoothly with later versions of Microsoft Office. You can downloadthe compatibility pack from the Microsoft website.

Opening reports and objects

If you use Microsoft Office 2003, consult the following table to learn about howdifferent Microsoft Office versions affect opening reports and objects.


Table 4. Effect of multiple Microsoft Office versions on opening reports and objects

SituationIf you use Microsoft Office2003

If you use Microsoft Office2003 plus the compatibilitypack

If the report contains Excelor Word objects that werecreated in Microsoft Office2003 only

You can open the report andall objects normally.

You can open the report andall objects normally.

If the report contains Excelor Word objects that werecreated in a later version ofMicrosoft Office

You cannot open the reportor view objects.

To open the report, you mustinstall the compatibility pack,or upgrade to the version ofMicrosoft Office that wasused to create the object.

You can open the report andall objects. You view laterobjects in Microsoft Office2003 format, but no changesare made in the database.

When you save a later object,you automatically save it inMicrosoft Office 2003 format,and you might lose featuresor formatting specific to thelater version.

To view or save the object inits original format, you mustupgrade to the version ofMicrosoft Office that wasused to create the object.

Important: You might open a report in Microsoft Office 2003, and then, while thereport is open, someone might create an Excel or Word object for the same reportin a later version of Microsoft Office. In this situation, you can still view the reportwhile it is open, but you cannot view the new object. If you close the report, youcannot open it again.

Copying and pasting objects

If you use Microsoft Office 2003, consult the following table to learn about howdifferent Microsoft Office versions affect copying and pasting objects.

Table 5. Effect of multiple Microsoft Office versions on copying and pasting objects




You can copy and paste anobject normally byright-clicking the object andthen clicking Copy andPaste.

You can copy and paste anobject normally byright-clicking the object andthen clicking Copy andPaste.


Table 5. Effect of multiple Microsoft Office versions on copying and pastingobjects (continued)




You cannot copy and pasteobjects.

To copy and paste objects,you must install thecompatibility pack, orupgrade to the version ofMicrosoft Office that wasused to create the object.

You can copy and paste anobject by right-clicking theobject and then clickingCopy and Paste. Youautomatically save the pastedobject in Microsoft Office2003 format, and you mightlose features or formattingspecific to the later version.

To save the pasted object inits original format, you mustupgrade to the version ofMicrosoft Office that wasused to create the object.

Working with shared objects

If you use Microsoft Office 2003, consult the following table to learn about howdifferent Microsoft Office versions affect shared objects.

Table 6. Effect of multiple Microsoft Office versions on shared objects


Result with Microsoft Office2003 plus the compatibilitypack


You can work with sharedobjects normally.

You can work with sharedobjects normally.

Appendix. Multiple versions of Microsoft Office 39

Table 6. Effect of multiple Microsoft Office versions on shared objects (continued)


Result with Microsoft Office2003 plus the compatibilitypack


You cannot work with sharedobjects.

To work with shared objects,you must install thecompatibility pack, orupgrade to the version ofMicrosoft Office that wasused to create the object.

Objects are opened inMicrosoft Office 2003 format.When you try to save theobject, you receive a messagein which you must specifywhether you want to save inMicrosoft Office 2003 format.

v If the shared object is aLink To Original, thecontent cannot bemodified. A linked objectactually has no content, sowhen an object is opened,the content is retrievedfrom the original sourceobject. This content opensin the version of MicrosoftOffice that is on yourcomputer, and you mightlose features or formattingspecific to the laterversion.

v If the shared object is aCopy, the content can bemodified because a copy istreated like any otherobject that has content. Alllater shared Excel or Wordobjects are saved inMicrosoft Office 2003format, and you mightlose features or formattingspecific to the laterversion.

To view and save the sharedobject in its original format,you must upgrade to theversion of Microsoft Officethat was used to create theobject.

Exporting Excel objects

If you use Microsoft Office 2003, consult the following table to learn about howdifferent Microsoft Office versions affect object exports.


Table 7. Effect of multiple Microsoft Office versions on exporting Excel objects




You can export objectsnormally.

You can export objectsnormally.


You cannot export objects.

To export objects, you mustinstall the compatibility pack,or upgrade to the version ofMicrosoft Office that wasused to create the object.

You can export the objectand select the format of thefinal output (xls, xlsx, orxlsm). When you open thedocument, it opens incompatibility mode, and youmight lose features orformatting specific to thelater version.

To export the object in itsoriginal format, you mustupgrade to the version ofMicrosoft Office that wasused to create the object.

Viewing and comparing audit trails or snapshots

If you use Microsoft Office 2003, consult the following table to learn about howdifferent Microsoft Office versions affect audit trails and snapshots.

Table 8. Effect of multiple Microsoft Office versions on audit trails or snapshots



If the report contains Excelor Word objects that werecreated in Microsoft Office2003 only, or if all snapshotswere created in MicrosoftOffice 2003 only

You can view and compareaudit trails or snapshotsnormally.

You can view and compareaudit trails or snapshotsnormally.

If the report contains Excelor Word objects that werecreated in a later version ofMicrosoft Office, or if at leastone of the snapshots wascreated in a later version ofMicrosoft Office

You cannot view or compareaudit trails or snapshots.

To view audit trails orsnapshots, you must installthe compatibility pack, orupgrade to the version ofMicrosoft Office that wasused to create the laterobjects or snapshots.

You can view and compareaudit trails or snapshots.When you select an audittrail entry or a snapshot, youview it in Microsoft Office2003 format, and you mightnot see features or formattingspecific to the later version.The changes are not saved tothe database.

To view and compare audittrails or snapshots in theiroriginal format, you mustupgrade to the version ofMicrosoft Office that wasused to create the objects orsnapshot.


Generating reports

If you use Microsoft Office 2003, consult the following table to learn about howdifferent Microsoft Office versions affect generating reports.

Table 9. Effect of multiple Microsoft Office versions on generating reports




You can generate the reportnormally. The report isgenerated as a .doc file.

You can generate the reportnormally. The report isgenerated as a .doc file.


You cannot generate thereport.

To generate the report, youmust install the compatibilitypack, or upgrade to theversion of Microsoft Officethat was used to create theobject.

You can generate the report.All later Excel and Wordobjects are converted toMicrosoft Office 2003 formaton your local machine, andyou might lose features orformatting specific to thelater version. However, theversion is not changed in thedatabase.

To generate the report withobjects in their originalformat, you must upgrade tothe version of MicrosoftOffice that was used tocreate the objects.

Performing report rollovers

When you roll forward a report containing mixed environments, all Excel andWord objects remain in the same version of Microsoft Office as before the rollover,because no conversion process takes place.

Effect of multiple versions of Microsoft Office if you use MicrosoftOffice 2007 or Microsoft Office 2010

If you use Microsoft Office 2007 or Microsoft Office 2010, some aspects of yourreports depend on the version of Microsoft Office that was used to create variousobjects. The version of Microsoft Office that you use can affect actions such asopening reports and objects, pasting and exporting objects, and generating reports.

Opening reports and objects

If you use Microsoft Office 2007 or Microsoft Office 2010, consult the followingtable to learn about how different Microsoft Office versions affect opening reportsand objects.


Table 10. Effect of multiple Microsoft Office versions on opening reports and objects

SituationIf you use Microsoft Office 2007 orMicrosoft Office 2010

If the report contains Excel or Word objectsthat were created in an earlier version ofMicrosoft Office

You can open and save reports and objects.When you save objects, you automaticallysave them in the format of the version ofMicrosoft Office that you use.

If the report contains Excel or Word objectsthat were created only in the version ofMicrosoft Office that you use

You can open and save reports and objectsnormally.

If the report contains Excel or Word objectsthat were created in a later version ofMicrosoft Office

You view the later object in the format of theversion of Microsoft Office that you use, andyou might not see features or formattingspecific to the later version. However, nochanges are made in the database.

To view the object in its original format, youmust upgrade to the version of MicrosoftOffice that was used to create the object.

Copying and pasting objects

If you use Microsoft Office 2007 or Microsoft Office 2010, consult the followingtable to learn about how different Microsoft Office versions affect copying andpasting objects.

Table 11. Effect of multiple Microsoft Office versions on copying and pasting objects



You can copy and paste an object byright-clicking the object and then clickingCopy and Paste. When you save a pastedobject, you automatically save it in theformat of the version of Microsoft Office thatyou use.


You can copy and paste an object normallyby right-clicking the object and then clickingCopy and Paste.


You can copy and paste an object byright-clicking the object and then clickingCopy and Paste. All later Excel and Wordobjects are saved in the format of the versionof Microsoft Office that you use, and youmight lose features or formatting specific tothe later version. The original object remainsin its original format.

To view and save a pasted object in itsoriginal format, you must upgrade to theversion of Microsoft Office that was used tocreate the object.


Working with shared objects

If you use Microsoft Office 2007 or Microsoft Office 2010, consult the followingtable to learn about how different Microsoft Office versions affect shared objects.

Table 12. Effect of multiple Microsoft Office versions on shared objects



You can work with shared objects. Allcopied Excel or Word objects are saved inthe format of the version of Microsoft Officethat you use.


You can work with shared objects normally.


Objects are opened in the format of theversion of Microsoft Office that you use.When you save the object, you receive amessage in which you must specify whetheryou want to save in the format of theversion of Microsoft Office that you use.

v If the shared object is a Link To Original,the content cannot be modified. A linkedobject actually has no content, so whenthe object is opened, the content isretrieved from the original source object.This content opens in the format of theversion of Microsoft Office that you use,and you might not be able to viewfeatures or formatting specific to the laterversion.

v If the shared object is a Copy, the contentcan be modified because a copy is treatedlike any other object that has content. Alllater Excel or Word objects are saved inthe format of the version of MicrosoftOffice that you use, and you might losefeatures or formatting specific to the laterversion.

To view a shared object in its originalformat, you must upgrade to the version ofMicrosoft Office that was used to create theobject.

Exporting objects

If you use Microsoft Office 2007 or Microsoft Office 2010, consult the followingtable to learn about how different Microsoft Office versions affect object exports.

Table 13. Effect of multiple Microsoft Office versions on exporting objects



You can export the object and select theformat of the final output (xls, xlsx, orxlsm).


Table 13. Effect of multiple Microsoft Office versions on exporting objects (continued)



You can export objects normally.


You can export the object and select theformat of the final output (xls, xlsx, orxlsm). When you open the document, itopens in compatibility mode, and you mightlose features or formatting specific to thelater version.

To export an object in its original format,you must upgrade to the version ofMicrosoft Office that was used to create theobject.

Viewing and comparing audit trails or snapshots

If you use Microsoft Office 2007 or Microsoft Office 2010, consult the followingtable to learn about how different Microsoft Office versions affect audit trails andsnapshots.

Table 14. Effect of multiple Microsoft Office versions on audit trails or snapshots


If the report contains Excel or Word objectsthat were created in an earlier version ofMicrosoft Office, or if the snapshots werecreated in an earlier version of MicrosoftOffice

You can view and compare audit trails orsnapshots. When you select an audit trailentry or snapshot, you view it in the formatof the version of Microsoft Office that youuse. The changes are not saved to thedatabase.

If the report contains Excel or Word objectsthat were created only in the version ofMicrosoft Office that you use, or if thesnapshots were created only in the versionof Microsoft Office that you use

You can view and compare audit trails orsnapshots normally.

If the report contains Excel or Word objectsthat were created in a later version ofMicrosoft Office, or if at least one of thesnapshots was created in a later version ofMicrosoft Office

You can view and compare audit trails orsnapshots. When you select an audit trailentry or a snapshot, you view it in theformat of the version of Microsoft Office thatyou use, and you might not see features orformatting specific to the later version. Thechanges are not saved to the database.

To view an audit trail entry or snapshot inits original format, you must upgrade to theversion of Microsoft Office that was used tocreate the objects in the audit trail or thesnapshot.


Generating reports

If you use Microsoft Office 2007 or Microsoft Office 2010, consult the followingtable to learn about how different Microsoft Office versions affect reportgeneration.

Table 15. Effect of multiple Microsoft Office versions on generating reports



You can generate the report. All earlier Exceland Word objects are saved in the format ofthe version of Microsoft Office that you use.The report is generated as a .docx file.


You can generate the report normally. Thereport is generated as a .docx file.


You can generate the report. All later Exceland Word objects are saved in the format ofthe version of Microsoft Office that you use,and you might lose features or formattingspecific to the later version. The report isgenerated as a .docx file.

To generate the report in its original format,you must upgrade to the version ofMicrosoft Office that was used to create theobject.

Performing report rollovers

When you roll forward a report containing mixed environments, all Excel andWord objects remain in the same version of Microsoft Office as before the rollover,because no conversion process takes place.


Notices

This information was developed for products and services offered worldwide.

IBM may not offer the products, services, or features discussed in this document inother countries. Consult your local IBM representative for information on theproducts and services currently available in your area. Any reference to an IBMproduct, program, or service is not intended to state or imply that only that IBMproduct, program, or service may be used. Any functionally equivalent product,program, or service that does not infringe any IBM intellectual property right maybe used instead. However, it is the user's responsibility to evaluate and verify theoperation of any non-IBM product, program, or service. This document maydescribe products, services, or features that are not included in the Program orlicense entitlement that you have purchased.

IBM may have patents or pending patent applications covering subject matterdescribed in this document. The furnishing of this document does not grant youany license to these patents. You can send license inquiries, in writing, to:

IBM Director of LicensingIBM CorporationNorth Castle DriveArmonk, NY 10504-1785U.S.A.

For license inquiries regarding double-byte (DBCS) information, contact the IBMIntellectual Property Department in your country or send inquiries, in writing, to:

Intellectual Property LicensingLegal and Intellectual Property LawIBM Japan Ltd.1623-14, Shimotsuruma, Yamato-shiKanagawa 242-8502 Japan

The following paragraph does not apply to the United Kingdom or any othercountry where such provisions are inconsistent with local law: INTERNATIONALBUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS"WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED,INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OFNON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULARPURPOSE. Some states do not allow disclaimer of express or implied warranties incertain transactions, therefore, this statement may not apply to you.

This information could include technical inaccuracies or typographical errors.Changes are periodically made to the information herein; these changes will beincorporated in new editions of the publication. IBM may make improvementsand/or changes in the product(s) and/or the program(s) described in thispublication at any time without notice.

Any references in this information to non-IBM Web sites are provided forconvenience only and do not in any manner serve as an endorsement of those Websites. The materials at those Web sites are not part of the materials for this IBMproduct and use of those Web sites is at your own risk.


IBM may use or distribute any of the information you supply in any way itbelieves appropriate without incurring any obligation to you.

Licensees of this program who wish to have information about it for the purposeof enabling: (i) the exchange of information between independently createdprograms and other programs (including this one) and (ii) the mutual use of theinformation which has been exchanged, should contact:

IBM Software GroupAttention: Licensing3755 Riverside DrOttawa, ON K1V 1B7Canada

Such information may be available, subject to appropriate terms and conditions,including in some cases, payment of a fee.

The licensed program described in this document and all licensed materialavailable for it are provided by IBM under terms of the IBM Customer Agreement,IBM International Program License Agreement or any equivalent agreementbetween us.

Any performance data contained herein was determined in a controlledenvironment. Therefore, the results obtained in other operating environments mayvary significantly. Some measurements may have been made on development-levelsystems and there is no guarantee that these measurements will be the same ongenerally available systems. Furthermore, some measurements may have beenestimated through extrapolation. Actual results may vary. Users of this documentshould verify the applicable data for their specific environment.

Information concerning non-IBM products was obtained from the suppliers ofthose products, their published announcements or other publicly available sources.IBM has not tested those products and cannot confirm the accuracy ofperformance, compatibility or any other claims related to non-IBM products.Questions on the capabilities of non-IBM products should be addressed to thesuppliers of those products.

All statements regarding IBM's future direction or intent are subject to change orwithdrawal without notice, and represent goals and objectives only.

This information contains examples of data and reports used in daily businessoperations. To illustrate them as completely as possible, the examples include thenames of individuals, companies, brands, and products. All of these names arefictitious and any similarity to the names and addresses used by an actual businessenterprise is entirely coincidental.

If you are viewing this information softcopy, the photographs and colorillustrations may not appear.


Trademarks

IBM, the IBM logo, ibm.com, and Cognos are trademarks or registered trademarksof International Business Machines Corp., registered in many jurisdictionsworldwide. Other product and service names might be trademarks of IBM or othercompanies. A current list of IBM trademarks is available on the Web at “ Copyrightand trademark information ” at www.ibm.com/legal/copytrade.shtml.

The following terms are trademarks or registered trademarks of other companies:v Microsoft, Windows, Windows NT, and the Windows logo are trademarks of

Microsoft Corporation in the United States, other countries, or both.

Notices 49

http://www.ibm.com/legal/copytrade.shtml

http://www.ibm.com/legal/copytrade.shtml

Date post:	03-Jun-2020
Category:	Documents
Upload:	others
View:	3 times
Download:	0 times

IBM Cognos FSR Version 6.6public.dhe.ibm.com/.../docs/en/6.6.1/installguide_fsr.pdf ·...

Documents