 | |
| | |
| | |
| | |
| |
You can install Metric Designer, the metadata modeling tool for IBM Cognos 8 Metrics Manager, on the same computer as IBM Cognos 8 components, or on a different computer. All required files are copied to one computer. Default settings are used for the configuration. However, you may want to change these default settings if existing conditions make the default choices inappropriate, or if you installed IBM Cognos 8 on a different computer.
Before you install Metric Designer, 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.
We recommend that you install and configure all IBM Cognos 8 server components before you install Metric Designer.
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.
Install in a directory that contains only ASCII characters in the path name. Some servers do not support non-ASCII characters in directory names.
You should also install and configure the target application where you will load data or metadata.
Before you install Metric Designer, ensure that the Windows computer meets IBM Cognos 8 software and hardware requirements. The size of the your models determines the hardware requirements, such as disk space.
The following table lists the minimum hardware and software requirements to run Metric Designer.
Requirement | Specification |
Operating system | Windows (design interface and engine) UNIX (engine only): Sun Solaris HP-UX IBM AIX |
RAM | Minimum: 512 MB Recommended: 1 GB |
Disk space | Minimum: 500 MB of free space on the drive that contains the temporary directory |
Other | Microsoft Data Access Component (MDAC) 2.6 or later for use with product samples |
If you upgraded from Metrics Manager version 2.0 or later, you can use the same extracts and projects that you used with the older version. To upgrade existing projects, you must open them in the new version of Metric Designer and redefine the data source connections and other references.
Before you configure Metric Designer, other IBM Cognos 8 components must be installed and configured, and Metric Designer must be installed.
To install and configure Metric Designer, follow these steps:
The following table lists the default settings for the ports and URIs that are used by Metric Designer. After installation, you can use IBM Cognos Configuration to change the settings. You can also change them by editing the cogstartup.xml file in the c8_location\configuration directory.
Component | Default | Description |
Gateway | http://localhost:80/ cognos8/cgi-bin/ cognos.cgi | The URI to the gateway |
Dispatcher URI for external applications | http://localhost:9300/ p2pd/servlet/dispatch | The URI to the dispatcher |
Use the following steps to install Metric Designer.
If you are installing in a directory with other IBM Cognos 8 components, stop the IBM Cognos 8 service.
Insert the Metric Designer disk or go to the location where the installation files were downloaded and extracted.
The Welcome page of the installation wizard appears.
If no Welcome page appears, go to the operating system directory and double-click the issetup.exe file.
Select the language to use to run the installation wizard.
Follow the directions in the installation wizard to copy the required files to your computer.
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 Readme.
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.
If you use DB2, Oracle, or Microsoft SQL Server for the metric store, you must set up the database client or other drivers or utilities on the Metric Designer computer. Doing this allows Metric Designer to access the metric store database.
If you are using type 2 JDBC connectivity, install the DB2 client software on the Metric Designer computer.
If you use type 4 JDBC connectivity for DB2, you are not required to install the DB2 client software where Metric Designer is installed.
For more information about the differences between type 2 and type 4 drivers, see JDBC Driver Options for Using DB2 Database as a Content Store.
On Windows, stop the DB2 services and the HTML Search Server.
Copy the following files from DB2_installation/sqllib/java directory to the c8_location/webapps/p2pd/WEB-INF/lib directory.
the universal driver file, db2jcc.jar
the license file, for example db2jcc_license_cu.jar
On Windows, restart the DB2 services and the HTML Search Server.
On the computer where the Oracle client is installed, go to the ORACLE_HOME/jdbc/lib directory.
Copy the ojdbc14.jar file (or, for Oracle 11g, the ojdbc5.jar file) to the c8_location/webapps/p2pd/WEB-INF/lib directory on the Metric Designer computer.
If the directory contains the classes12.jar file, delete it before installing the ojdbc14.jar or ojdbc5.jar file.
The driver is available from an Oracle client or server install, and it can also be downloaded from the Oracle technology Web site (http://www.oracle.com/technology).
Install the SQL Loader utility on the Metric Designer computer.
Install the bcp utility on the Metric Designer computer.
If you install Metric Designer on a different computer from other IBM Cognos 8 components, you must configure it to communicate with the computers where the gateway and Content Manager are installed.
We recommend that you install and configure other IBM Cognos 8 components before you configure Metric Designer. You must first install and configure Content Manager and then start the IBM Cognos 8 service on at least one Content Manager computer before you configure Metric Designer. This ensures that the certificate authority service issues a certificate to the Metric Designer computer.
Before you configure Metric Designer, ensure that the Web server is configured and running, and the IBM Cognos 8 service is running.
If you are using an Apache Web server, ensure that you configure
it first 
.
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 .
On the computer where you installed Metric Designer, start IBM Cognos Configuration.
In the Explorer window, click Environment.
In the Properties window, in the Gateway URI box, type the appropriate value:
Change the host name portion of the Gateway URI from localhost to either the IP address of the computer or the computer name.
To use ISAPI, replace cognos.cgi with cognosisapi.dll.
To use an Apache Web server, type the following syntax:
http://host_name:port/cognos8/cgi-bin/module.suffix
where module is as follows:
Version | Module |
Apache 1.3 | mod_cognos |
Apache 2.0 | mod2_cognos |
Apache 2.2 | mod2_2_cognos |
and suffix is as follows:
Operating system | Suffix |
Windows | dll |
Solaris, AIX | so |
HP-UX PA-RISC | sl |
HP-UX IA, Linux | so |
Apache module 1.3 is not supported on HP-UX IA or Linux.
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 Metric Designer 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.
From the File menu, click Save.
Metric Designer is configured to communicate with other IBM Cognos 8 components.
The IBM Cognos 8 modeling tools create and manage metadata. Metric Designer creates and manages metadata required for the scorecarding 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 import source environment for Metric Designer. Commonly, these things depend on the other technology you use for your data or import source.
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.
Set the environment variable for multilingual support:
For Oracle, set the NLS_LANG (National Language Support) environment variable on each computer where Framework Manager or Metric Designer and the IBM Cognos 8 server are 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.
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.
For Oracle, copy the ojdbc14.jar file from ORACLE_HOME/jdbc/lib to the c8_location/webapps/p2pd/WEB-INF/lib directory. For Oracle 11g, 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.
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.
For Oracle, on the computer where Application Tier Components is installed, set the NLS_LANG (National Language Support) environment variable 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.
You can test your configuration by starting the application and creating a project.
To start Metric Designer, from the Start menu, click Programs, IBM Cognos 8, Metric Designer.
If you see the Welcome page of Metric Designer, your installation is working.
