Set Up the Data Source Environment for Framework Manager

The IBM® Cognos® 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.

Before you begin

Install IBM Cognos Framework Manager. For information on how to install Cognos Framework Manager, refer to the IBM Cognos Analytics or IBM Cognos Business Intelligence installation procedures.

Ensure that you install the appropriate fonts to support the character sets and currency symbols you use.

Procedure

  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. 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 ccr_location/webapps/p2pd/WEB-INF/lib directory. For Oracle 11 g, copy the ojdbc5.jar file from ORACLE_HOME/jdbc/lib to the ccr_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.

    Table 1. Authorization objects to configure for SAP BW when you set up the data source environment for Framework Manager
    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 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.