Installing and Configuring Framework Manager 

You can install Framework Manager, the metadata modeling tool for IBM Cognos 8 for reporting, on the same computer as other IBM Cognos 8 components, or on a different computer. All required files are copied to one computer. Default settings are used for the configuration. You can change these default settings if necessary, or if you install Framework Manager on a separate computer from IBM Cognos 8.

If you upgraded from an older version of Framework Manager, you can use the same models and projects that you used with the older version. To upgrade existing projects, you must open them in the new version of Framework Manager.

If you are upgrading Framework Manager from an older version, you must first uninstall the older version of Framework Manager .

Before you install Framework Manager, we recommend that you close all programs that are currently running to ensure that the installation program copies all the required files to your computer.

Also, ensure that you have administrator privileges for the Windows computer you are installing on. If you are not an administrator, ask your system administrator to add you to the Administrator group on your computer. Administrator privileges are also required for the account that is used to run Framework Manager.

We recommend that you install and configure all IBM Cognos 8 server components before you install Framework Manager.

Install in a directory that contains only ASCII characters in the path name. Some servers do not support non-ASCII characters in directory names. Installing Framework Manager in directory that has an apostrophe in the path name may result in the help not opening properly.

If you are installing the modeling tool in the same directory as IBM Cognos 8 and do not stop the IBM Cognos 8 services, you are prompted to do so during the installation.

System Requirements for Framework Manager

Before you install Framework Manager, ensure that the Windows computer meets IBM Cognos 8 software and hardware requirements. The size of your models determines the hardware requirements, such as disk space.

The following table lists the minimum hardware and software requirements to run Framework Manager.

To install and configure Framework Manager, follow these steps:

	Install Framework Manager.
	Update the Java Environment.
	Set up the data source environment for Framework Manager
	Configure environment properties for Framework Manager.
	Test the Framework Manager installation

If you install Framework Manager on a different computer from the non-modeling components of IBM Cognos 8, you may also want to perform the following tasks:

• Configure a source control system.

• Update file location properties.

Default Settings for Framework Manager 

The following table lists the default settings for the IBM Cognos 8 ports and URIs that are used by Framework Manager. After installation, you can use the configuration tool to change the settings. You can also change them by editing the cogstartup.xml file in the c8_location\configuration directory.

Install Framework Manager

To install Framework Manager, use the IBM Cognos 8 Business Intelligence Modeling CD. When prompted for Component Selection, install all the components that are selected by default.

Steps

1. If you use an Oracle database as a data source for your reports, set the NLS_LANG environment variable by typing the following command on each computer where Framework Manager and the Application Tier Components are installed:

   NLS_LANG = language_territory.character_set

   For example, NLS_LANG = JAPANESE_JAPAN.UTF8

   The value of the variable determines the locale-dependent behavior of IBM Cognos 8. Error messages, sort order, date, time, monetary, numeric, and calendar conventions automatically adapt to the native language and locale.

   If the Application Tier Components are installed on a UNIX computer, the NLS_LANG variable must be set up for the user who owns and starts the IBM Cognos 8 service.

2. If you are installing in a directory with other IBM Cognos 8 components, stop the IBM Cognos 8 service.

3. Insert the Framework Manager disk or go to the location where the installation files were downloaded and extracted.

   The Welcome page of the installation wizard appears.

4. If no Welcome page appears, go to the operating system directory and double-click the issetup.exe file.

5. Select the language to use for the installation.

   The language that you select determines the language of the user interface. You can change the language to any of the installed languages after installation.

6. Follow the directions in the installation wizard to copy the required files to your computer.

   If you are installing IBM Cognos 8 on a computer that already has ReportNet or an older version of IBM Cognos 8, and you want to keep the older version running, you must install IBM Cognos 8 in a different directory.

   If you are installing in a directory that contains other IBM Cognos 8 components, you are prompted for the location of a directory in which to store backup copies of the files that will be overwritten.

7. In the Finish page of the installation wizard,

   • If you want to configure IBM Cognos components immediately, click Start IBM Cognos Configuration.

   • If you want to see late-breaking information about IBM Cognos components, click View the IBM Cognos Readme.

8. Click Finish.

   Use the Windows Start menu to start IBM Cognos Configuration from the shortcut folder.

To ensure the security and integrity of IBM Cognos 8, it is important to protect the installation directory from unauthorized or inappropriate access.

Update the Java Environment

IBM Cognos 8 cryptographic services use a specific .jar (Java Archive) file, named bcprov-jdknn-nnn.jar, that must be located in your Java Runtime Environment (JRE). This file provides additional encryption and decryption routines that are not supplied as part of a default JVM installation. To ensure security, the encryption file must be loaded by the JVM using the java extensions directory.

If you want to use your own JRE and have JAVA_HOME set to that location on Windows or if you are installing on UNIX, you may have to update the Java environment for the cryptographic services.

On Windows, you can set JAVA_HOME as a system variable or a user variable. If you set it as a system variable, it may be necessary to restart your computer for it to take effect. If you set it as a user variable, set it so that the environment in which Tomcat is running can access it.

If you do not have a JAVA_HOME variable already set on Windows or if JAVA_HOME points to a Java version that is not valid for IBM Cognos 8, the JRE files provided with the installation will be used, and you do not have to update any files in your environment.

Steps

1. Ensure that the JAVA_HOME environment variable is set to the JRE location.

   For example, to set JAVA_HOME to the JRE files provided with the installation, the path is c8_location/bin/jre/version.

2. Copy the bcprov-jdknn-nnn.jar file from the c8_location/bin/jre/version/lib/ext directory to the Java_location/jre/lib/ext directory.

Set Up the Data Source Environment for Framework Manager

The IBM Cognos 8 modeling tools create and manage metadata. Framework Manager creates and manages metadata for the reporting functions. Because metadata is derived from data sources in multi-platform or multilingual environments, there are several things you must think about or do when you set up the data source environment for Framework Manager. Commonly, these things depend on the other technology you use for your data or import source.

If you use a Sybase data source, these steps are not necessary.

If you upgraded from an older version of Framework Manager, you are not required to set up anything in the data source environment. You must set up the data source environment only if you installed Framework Manager in a different location from the older version.

If users operating in different languages will be connecting to a Microsoft Analysis Services (MSAS) 2000 data source, you must create a separate IBM Cognos 8 instance for each language.

Users operating in different languages can connect to an MSAS 2005 data source from the same instance of IBM Cognos 8. Modelers must create a separate package for each language. Users can run reports in any language.

For more information about data source connections, see the Administration and Security Guide.

Ensure that you install the appropriate fonts to support the character sets and currency symbols you use. For Japanese and Korean currency symbols to appear correctly, you must install the additional fonts from the Supplementary Languages Documentation CD. For more information, see Install and Configure Additional Language Fonts.

Steps

1. Set the environment variable for multilingual support:

   • For Oracle, set the NLS_LANG (National Language Support) environment variable on each computer where Framework Manager is installed by typing the following command:

     NLS_LANG = language_territory.character_set

     Examples are:

     NLS_LANG = AMERICAN_AMERICA.UTF8

     NLS_LANG = JAPANESE_JAPAN.UTF8

     The value of the variable determines the locale-dependent behavior of IBM Cognos 8. Error messages, sort order, date, time, monetary, numeric, and calendar conventions automatically adapt to the native language and locale.

   • For DB2, set the DB2CODEPAGE environment variable to a value of 1252.

     For more information about whether to use this optional environment variable, see the DB2 documentation.

   No settings are required for SAP BW. SAP support only a single code page on non-Unicode SAP BW systems.

2. For Oracle, add $ORACLE_HOME/lib to your LD_LIBRARY_PATH.

   When you set the load library paths, ensure that the 32-bit Oracle libraries are in the library search path, which is usually the $ORACLE_HOME/lib directory or the $ORACLE_HOME/lib32 directory if you installed a 64-bit Oracle client.

3. For Oracle, copy the ojdbc14.jar file from ORACLE_HOME/jdbc/lib to the c8_location/webapps/p2pd/WEB-INF/lib directory. For Oracle 11 g, copy the ojdbc5.jar file from ORACLE_HOME/jdbc/lib to the c8_location/webapps/p2pd/WEB-INF/lib directory.

   If the directory contains the classes12.jar file, delete it before installing the ojdbc14.jar or ojdbc5.jar file.

4. For SAP BW, configure the following authorization objects so that the modeling tool can retrieve metadata.

   Some of the values shown, such as *, are default values that you may want to modify for your environment.

   Authorization object	Field	Value
   S_RFC	Activity	16
   	Name of RFC to be protected	SYST, RSOB, SUGU, RFC1, RS_UNIFICATION, RSAB, SDTX, SU_USER
   	Type of RFC object to be protected	FUGR
   S_TABU_DIS	Activity	03
   	Authorization Group	&NC&
   S_RFC	Activity	16
   	Name of RFC to be protected	SYST, RSOB, SUGU, RFC1, RS_UNIFICATION, RSAB, SDTX, SU_USER
   	Type of RFC object to be protected	FUGR
   S_TABU_DIS	Activity	03
   	Authorization Groups	&NC&
   S_USER_GRP	Activity	03, 05
   	User group in user master main	*
   S_RS_COMP	Activity	*
   	Info Area	InfoArea Technical Name
   	Info Cube	InfoCube Technical Name
   	Name (ID) of reporting components	*
   	Type of reporting components	*
   S_RS_COMP1	Activity	*
   	Name (ID) of reporting components	*
   	Type of reporting components	*
   	Owner (Person Responsible)	*
   S_RS_HIER	Activity	71
   	Hierarchy Name	Hierarchy Name
   	InfoObject	InfoObject Technical Name
   	Version	Hierarchy Version
   S_RS_ICUBE	Activity	03
   	InfoCube sub-object	DATA DEFINITION
   	Info Area	InfoArea Technical Name
   	InfoCube	InfoCube Technical Name

   &NC& represents any table that does not have an authorization group. For security reasons, create a new authorization group and assign the table RSHIEDIR to it. The new authorization group restricts the user’s access to the above table only, which is needed by the modeling tool. Create the new authorization group as a customization in the SAP system.

   For more information about SAP BW authorization objects, see Transaction SU03.

Configure Environment Properties for Framework Manager Computers

When you install Framework Manager on a different computer from the non-modeling components of IBM Cognos 8, you must configure it to communicate with the other components.

If you install Framework Manager on the same computer as the non-modeling components of IBM Cognos 8, no configuration is required if you

• configure your Web server using the default virtual directories

• use the default ports

• use the default resources

• use the default cryptographic settings

Important: If IBM Cognos 8 was installed in more than one location, ensure that all URIs point to the correct version of IBM Cognos 8. Framework Manager must be configured to use the same version of IBM Cognos 8.

Installations with a Firewall

When the modeling tool is outside a network firewall that protects the Application Tier Components, communication issues with the dispatcher can arise. To avoid communication issues, you can install the modeling tool in the same architectural tier as the Application Tier Components or you can install and configure a gateway that is dedicated to modeling tool communications. For more information about the modeling tool and network firewalls, see Firewall Considerations.

The steps in this topic describe how to configure the modeling tool computer. If you are using a gateway that is dedicated to the modeling tool, you must also configure the dedicated gateway computer .

Prerequisites

Ensure that the IBM Cognos 8 service on at least one Content Manager computer is running. This ensures that the certificate authority service issues a certificate to the Framework Manager computer.

Ensure that the Web server is configured and running .

You must also set up the data sources before you configure Framework Manager.

Steps

1. On the computer where you installed Framework Manager, start IBM Cognos Configuration.

2. In the Explorer window, click Environment.

3. In the Properties window, in the Gateway URI box, type the appropriate value.

   • To use ISAPI, replace cognos.cgi with cognosisapi.dll.

   • To use an Apache Web server, type the following syntax:

     For Apache 1.3 module,

     http://host_name:port/cognos8/cgi-bin/mod_cognos.dll

     For Apache 2.0 module,

     http://host_name:port/cognos8/cgi-bin/mod2_cognos.dll

     For Apache 2.2.x module,

     http://host_name:port/cognos8/cgi-bin/mod2_2_cognos.dll

     Note: Ensure that you configured your Apache Web Server .

   • To use a servlet gateway, type the following syntax:

     http[s]://host_name:port/context_root/servlet/Gateway

     where context_root is the value you assigned to the ServletGateway Web application when you deployed the ServletGateway application.

     Note: Ensure that you configured your Web server to support the servlet gateway.

   • If you are not using a Web server, to use the dispatcher as the gateway, type the following syntax:

     http[s]://host_name:port/p2pd/servlet/dispatch

4. Change the host name portion of the Gateway URI from localhost to either the IP address of the computer or the computer name.

5. Specify the value for the Dispatcher URI for external applications.

   • If your Web server is configured not to allow anonymous access, type the URI of the dispatcher, ensuring that you change the host name in the URI from localhost.

   • If your Web server supports chunked transfer encoding and Framework Manager is inside the firewall, type the URI of the dispatcher, ensuring that you change the host name in the URI from localhost.

   • If you are using a dedicated gateway for modeling tool communication, type the dispatcher URI.

6. In the Explorer window, under Cryptography, click Cognos, the default cryptographic provider.

7. Under the Certificate Authority settings property group, for the Password property, type the same password you configured on the default active Content Manager computer.

8. From the File menu, click Save.

Framework Manager is configured to communicate with the other components of IBM Cognos 8. If you installed Framework Manager on a Windows Vista computer, you can update file location properties on Windows Vista computers .

Test the Installation and Configuration

You can test your configuration by starting the application and creating a project.

Step

• To start Framework Manager, from the Start menu, click Programs, IBM Cognos 8, Framework Manager.

  You may be prompted to upgrade if the model schema version is older than the currently supported version.

  If you see the Welcome page of Framework Manager, your installation is working.