Configuring Distributed Installations

To improve performance or to enhance security, you can install any one of the following components on a separate computer:

• gateway

• Application Tier Components

• Content Manager

• Cognos Content Database

For information about planning a distributed installation, see the Architecture and Deployment Guide.

You can install the Application Tier Components, gateway, and Content Manager on multiple computers.

If you are upgrading from ReportNet, all the distributed components must be the same version of Cognos 8. If you install Cognos 8 in new locations, you must update the locations using Cognos Configuration.

If you install Cognos 8 components on more than one computer, you must configure environment properties so that the distributed components can communicate with each other:

• The Content Manager computers must know the location of the content store, the other Content Manager computers, and the database that is used for notification.

• The gateway computer must know the location of at least one dispatcher.

  The dispatcher should be located on a report server computer.

• The Application Tier Components computer must know the location of the Content Manager computers and the database to use for job and schedule information.

You must also configure cryptographic properties to ensure that each computer uses the same settings.

In a distributed environment, the sequence in which you configure computers is important. You must configure and then start the services on at least one computer where you installed Content Manager before you configure other computers in your Cognos environment. You must configure the gateway computer last so that cryptographic keys are shared and secure communication can take place among the three components. The server specified for the External Dispatcher URI property on the gateway computer must be the last server that you start.

Use the following checklist to guide you through the required configuration tasks:

	Configure the Content Manager computers.
	Configure the Application Tier Components computers.
	Configure the gateway computers.
	Configure the Framework Manager computers, if required.
	Configure the Cognos 8 Transformer computers, if required.
	Configure the Metric Designer computers, if required.
	Create a metric package, if required.
	Start the Cognos 8 services.
	Test the installation and configuration.
	Finish the configuration.

After you complete these configuration tasks, you can configure Cognos 8 to use an authentication provider or change the default behavior of Cognos 8 components to better suit your Cognos environment.

We recommend that you specify the amount of resources the Cognos 8 service uses to ensure that performance is optimized.

Configuring Content Manager Computers  

Use the following checklist to guide you through the required configuration tasks for the Content Manager computers:

	Set the database connection properties for the content store.
	Specify a mail server account and notification database.
	Configure the environment properties.
	Update file location properties, if required.
	Start the Cognos 8 services.

Set Database Connection Properties for the Content Store 

You must specify the database server information to ensure that Content Manager can connect to the database you use for the content store. Content Manager uses the database logon to access the content store. After you set the database connection properties, you can test the connection between Content Manager and the content store.

If you installed Cognos Content Database on a different computer from where you installed Content Manager, you must set the database connection properties for Cognos Content Database. If you installed Cognos Content Database on the same computer as Content Manager, Content Manager is configured to use Cognos Content Database using the default values. If you install Cognos Content Database on the same computer as Content Manager, and you later decide to use another database for your content store, you must uninstall Cognos Content Database.

Ensure that you used one of the supported database servers to create the content store.

Note: Some database servers are available with advanced features. When you select an advanced database, Cognos 8 components use features of the database server to manage the connection. If you select the advanced Oracle database, for example, Cognos 8 components use enterprise-oriented Oracle features to select a listener, switch to another listener if the first listener fails, automatically reconnect to the database if the connection fails, balance connection requests among listeners, and balance connection requests among dispatchers.

Cognos 8 components require the TCP/IP protocol to access data and the content store. Ensure that the database server has the protocol set to TCP/IP.

If you are using Oracle, you do not have to install an Oracle client on the same computer as Content Manager. Content Manager, however, does require an Oracle JDBC driver called ojdbc14.jar. 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). The ojdbc14.jar driver file must be copied to the c8_location\p2pd\WEB-INF\lib directory where you installed the Content Manager. If the directory contains the classes12.jar file, you must delete it before installing the ojdbc14.jar file.

If you are upgrading from ReportNet, configure Cognos 8 to point to the existing content store. After you save the configuration and start the Cognos 8 service, the content store is automatically upgraded and cannot be used by ReportNet. If you keep ReportNet, you must configure Cognos 8 to point to a new content store.

Steps for Cognos Content Database

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

2. In the Explorer window, under Data Access, Content Manager, right-click Content Store, and then click Delete. Click Yes to confirm the deletion.

   This action deletes the default database.

3. Right-click Content Manager, and then click New resource, Database.

4. In the Properties window, configure Cognos 8 to use Cognos Content Database as the content store:

   • For Name, type cm.

   • For Database server and port number, type the name of the computer where you installed Cognos Content Database.

   • For User ID and password, click the edit button and specify cognos for both the userid and password to access Cognos Content Database.

   We recommend that you change the default user ID and password after configuring the new resource. For information about changing default values, see Change Default User and Password for Cognos Content Database.

5. From the File menu, click Save.

   The logon credentials are immediately encrypted.

6. In the Explorer window, right-click Content Store and click Test to test the connection between Content Manager and the content store.

   You must start the Cognos Content Database service on the computer where it is installed before the test will succeed.

   Content Manager connects to the database, checks the database permissions, and creates and populates a table. The table is not deleted and is used each time that the test is repeated.

Steps for Microsoft SQL Server, Oracle, DB2, and Sybase

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

2. In the Explorer window, under Data Access, Content Manager, right-click Content Store and click Delete.

   This deletes the default resource. Content Manager must be configured to access only one content store.

3. Right-click Content Manager, and then click New resource, Database.

4. In the Name box, type a name for the resource.

5. In the Type box, select the type of database and click OK.

   If you are upgrading and want to use an existing content store, ensure that you select the type of database you use for the older version of ReportNet.

   If you installed more than one version of Cognos 8, you must use a different content store for each version. When a content store is used by a new version of Cognos 8, it cannot be used by an older version of ReportNet.

   Tip: If you want to use Oracle Net8 keyword-value pair to manage the database connection, select Oracle database (Advanced).

6. In the Properties window, provide values depending on your database type:

   • If you use a Microsoft SQL Server database, type the appropriate values for the Database server with port number or instance name and Database name properties.

     For a Microsoft SQL Server database, you can choose to use a port number, such as 1433, or a named instance as the value for the Database server with port number or instance name property.

     To connect to a named instance, you must specify the instance name as a JDBC URL property or a data source property. For example, you can type localhost\instance1. If no instance name property is specified, a connection to the default instance is created.

     Note that the properties specified for the named instance, along with the user ID and password, and database name, are used to create a JDBC URL. Here is an example:

     jdbc:JSQLConnect://localhost\\instance1/user=sa/more properties as required

   • If you use a DB2 database, for the Database name property, type the database alias.

   • If you use an Oracle database, type the appropriate values for the Database server and port number and Service name properties.

   • If you use an advanced Oracle database, for the Database specifier property, type the Oracle Net8 keyword-value pair for the connection.

     Here is an example:

     (description=(address=(host=myhost)(protocol=tcp)(port=1521)(connect_data=(sid=(orcl)))))

   • If you use a Sybase database, type the appropriate values for the Database server and port number and Database name properties.

7. If you want to change the logon credentials, specify a user ID and password:

   • Click the Value box next to the User ID and password property and then click the edit button when it appears.

   • Type the appropriate values and click OK.

8. From the File menu, click Save.

   The logon credentials are immediately encrypted.

9. Test the connection between Content Manager and the content store.

   Tip: In the Explorer window, right-click the new database and click Test.

   Content Manager connects to the database, checks the database permissions, and creates and populates a table. The table is not deleted and is used each time that the test is repeated.

Content Manager can now create the required tables in the content store when you start the Cognos 8 service for the first time. If the connection properties are not specified correctly, the tables are not created and you cannot connect to Cognos Connection.

If you are upgrading from ReportNet, Content Manager can now access the required tables in the content store that you used for ReportNet.

Specify a Mail Server Account and Notification Database  

Steps

1. On each computer where Content Manager is installed, start Cognos Configuration.

2. In the Explorer window, under Data Access, click Notification.

3. In the Properties window, for the SMTP mail server property, type the host name and port of your SMTP (outgoing) mail server.

4. Click the Value box next to the Account and password property and then click the edit button when it appears.

5. Type the appropriate values in the Value - Account and password dialog box and then click OK.

   Tip: If logon credentials are not required for the SMTP server, remove the default information for the Account and password property. When you are prompted for confirmation to leave this property blank, click Yes. Ensure that the default user name has been removed. Otherwise, the default account is used and notifications will not work properly.

6. In the Properties window, type the appropriate value for the default sender account.

   Tip: If you use the default notification database, you do not have to perform the following two steps.

7. Identify the database that is used for notification:

   • In the Explorer window, right-click Notification and select New resource, Database.

   • Type a name for the database resource.

   • Select the type of database from the pull-down menu.

   • Click OK.

8. In the Properties window, enter the values for the notification database resource.

   For a Microsoft SQL Server database, you can choose to use a port number, such as 1433, or a named instance as the value for the Database server with port number or instance name property.

   To connect to a named instance, you must specify the instance name as a JDBC URL property or a data source property. For example, you can type localhost\instance1. If no instance name property is specified, a connection to the default instance is created.

   Note that the properties specified for the named instance, along with the user ID and password, and database name, are used to create a JDBC URL. Here is an example:

   jdbc:JSQLConnect://localhost\\instance1/user=sa/more properties as required

9. From the File menu, click Save.

10. Test the notification and mail server connections. In the Explorer window right-click Notification and click Test.

    Cognos 8 tests the database connection and tests the mail server connection.

    If you have been using the content store database for notification, the schedules will be replicated in the tables of the new notification database.

Configure Environment Properties for Content Manager Computers 

After installing Content Manager on the computers you are using for failover protection, you must configure Content Manager on those computers. If you installed more than one Content Manager, you must list all Content Manager URIs on each Content Manager computer. If you are upgrading, you must also add the standby Content Manager URIs to the original Content Manager computer.

After you complete the required configuration tasks, the certificate authority service is available to issue certificates to other Cognos computers. You can then perform the required configuration tasks on other computers, such as the Application Tier Components computer and gateway computers. Otherwise you can continue to configure the Content Manager computers by changing the default property settings so that they better suit your environment. For example, you can configure Cognos 8 components to use an authentication provider , enable and disable services on the Content Manager computers, or change global settings .

Important: If you change global settings on one Content Manager computer, you must make the same changes on the other Content Manager computers.

Steps for the First Content Manager Computer

1. On the Content Manager computer that you want to designate as the default active Content Manager, start Cognos Configuration.

   Tip: We recommend that you use the computer with the highest processor speed for the default active Content Manager.

2. In the Explorer window, click Environment.

3. In the Properties window, click the value for Content Manager URIs and then click the edit button.

4. Specify the URIs for the other Content Manager computers:

   • In the Value - Content Manager URIs dialog box, click Add.

   • In the blank row of the table, click and then type the full URI of the Content Manager computer.

     Do not delete the first value in the table. This value identifies the local Content Manager computer and is required.

   • Repeat the previous two bulleted steps for each URI to be added.

     Important: You must include all Content Manager URIs in the list.

   • Click OK.

5. In the Explorer window, under Security, click Cryptography.

6. In the Properties window, under CSK settings, set Store symmetric key locally to True.

7. From the File menu, click Save.

Steps for Standby Content Manager Computers

1. Ensure that you already configured the Environment properties on at least one Content Manager computer and that Cognos 8 components are running on that computer.

2. On the standby Content Manager computer, start Cognos Configuration.

3. In the Explorer window, click Environment.

4. In the Properties window, click the value for Content Manager URIs and then click the edit button.

5. Specify the URIs for the other Content Manager computers:

   • In the Value - Content Manager URIs dialog box, click Add.

   • In the blank row of the table, click and then type the full URI of the Content Manager computer.

     Do not delete the first value in the table. This value identifies the local Content Manager computer and is required.

   • Repeat the previous two bulleted steps for each URI to be added.

     Important: You must include all Content Manager URIs in the list.

   • Click OK.

6. In the Explorer window, under Security, click Cryptography.

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

8. Under the Certificate Authority settings property group, set the Password property to match what you configured on the default active Content Manager computer.

9. Ensure that all other cryptographic settings match what you configured on the default active Content Manager computer.

10. In the Explorer window, under Data Access, Content Manager, click Content Store.

11. Ensure that the values for all of the properties match what you configured on the default active Content Manager computer.

12. From the File menu, click Save.

Update File Location Properties

Steps

1. Start Cognos Configuration.

2. In the Explorer window, click Environment.

3. In the Properties window, click Deployment files location.

4. Replace the relative path element, "..", with the appropriate environment variable and root directory:

   • On Windows, use the preset environment variables as shown in the table.

     Operating system	Per user	All users
     Windows XP	%APPDATA%	%ALLUSERSPROFILE%
     Windows Vista	%LOCALAPPDATA%	%PUBLIC%

   • On UNIX, use the environment variables that you set in advance.

   For example,

   On Windows XP, to set a single file location for all users, specify %ALLUSERSPROFILE%/c8/deployment.

   On UNIX, if you set an environment variable such as MYHOME for single users, specify $MYHOME/c8/deployment.

5. Repeat step 4 for the following properties:

   • Under Environment,

     - Data files location

     - Map files location

     - Temporary files location

   • Under Environment, Logging, File,

     - Log file location

   • Under Cryptography,

     - Common symmetric key store location

   • Under Cryptography, Cognos,

     - Certificate location

     - Signing key store location

     - Encryption key store location

6. From the File menu, click Save.

The environment variables are resolved when the file locations are accessed during system activities.

You are now ready to start the Cognos 8 services on the Content Manager computer or computers. As soon as the services start on the first Content Manager computer, the computer becomes the default active Content Manager. If you configured Cognos 8 with standby Content Manager computers and you use the default CGI gateway, you must configure Cognos 8 to use an ISAPI gateway. For more information, see Changing the Gateway.

Configuring Application Tier Components Computers  

You can install the Application Tier Components component on one or more computers, depending on your environment.

If you installed more than one Content Manager, you must list all Content Manager URIs on each report server computer.

If you are upgrading from ReportNet, Cognos 8 uses the existing configuration data for the Application Tier Components computers. However, if you installed the Application Tier Components in a new location, you must configure the environment properties.

Ensure that the computer where you installed the active Content Manager is configured and available before you configure Application Tier Components computers.

If Content Manager and the Application Tier Components are installed on separate computers, on the Application Tier Components computer, you must do the following:

	Specify a mail server account and notification database.
	Configure Environment properties.
	Update file location properties, if required.
	Start the Cognos 8 services.

Other configuration tasks are optional and may be performed later.

Specify a Mail Server Account and Notification Database

If you want to send reports by email, you must configure a mail server account. You must also specify the location of the database that is used by the notification server to store job and schedule information.

When you finish configuring a mail server account and notification database, you can test the connections to the mail server and notification database.

If you are upgrading from ReportNet, Cognos 8 uses the mail server account and settings that were set up for the older version.

You must configure all report server computers to use the same database for notification. You must use the same database that is used for notification on Content Manager computers.

Tip: To be able to open reports that are sent by email, you must change the host name portion of the Gateway URI from localhost to either the IP address of the computer or the computer name. Otherwise the URL in the email will contain localhost and remote users will not be able to open the report.

Steps

1. On each computer where Content Manager is installed, start Cognos Configuration.

2. In the Explorer window, under Data Access, click Notification.

3. In the Properties window, for the SMTP mail server property, type the host name and port of your SMTP (outgoing) mail server.

4. Click the Value box next to the Account and password property and then click the edit button when it appears.

5. Type the appropriate values in the Value - Account and password dialog box and then click OK.

   Tip: If logon credentials are not required for the SMTP server, remove the default information for the Account and password property. When you are prompted for confirmation to leave this property blank, click Yes. Ensure that the default user name has been removed. Otherwise, the default account is used and notifications will not work properly.

6. In the Properties window, type the appropriate value for the default sender account.

   Tip: If you use the default notification database, you do not have to perform the following two steps.

7. Identify the database that is used for notification:

   • In the Explorer window, right-click Notification and select New resource, Database.

   • Type a name for the database resource.

   • Select the type of database from the pull-down menu.

   • Click OK.

8. In the Properties window, enter the values for the notification database resource.

   For a Microsoft SQL Server database, you can choose to use a port number, such as 1433, or a named instance as the value for the Database server with port number or instance name property.

   To connect to a named instance, you must specify the instance name as a JDBC URL property or a data source property. For example, you can type localhost\instance1. If no instance name property is specified, a connection to the default instance is created.

   Note that the properties specified for the named instance, along with the user ID and password, and database name, are used to create a JDBC URL. Here is an example:

   jdbc:JSQLConnect://localhost\\instance1/user=sa/more properties as required

9. From the File menu, click Save.

10. Test the notification and mail server connections. In the Explorer window right-click Notification and click Test.

    Cognos 8 tests the database connection and tests the mail server connection.

    If you have been using the content store database for notification, the schedules will be replicated in the tables of the new notification database.

Configure Environment Properties for Application Tier Components Computers   

If you install the Application Tier Components component on a different computer than Content Manager, you must configure the Application Tier Components computer so that it knows the location of Content Manager. The distributed components can then communicate with each other.

Steps

1. Start Cognos Configuration.

2. In the Explorer window, click Environment.

3. In the Properties window, specify the appropriate value for the Gateway URI, by changing the localhost portion to the name of the gateway computer.

4. In the Properties window, click the value for Content Manager URIs and then click the edit button.

5. Change the localhost portion of the existing URI to the name of any Content Manager computer.

6. Specify the URIs for the remaining Content Manager computers:

   • In the Value - Content Manager URIs dialog box, click Add.

   • In the blank row of the table, click and then type the full URI of the Content Manager computer.

   • Repeat the previous two bulleted steps for each URI to be added.

     Important: You must include all Content Manager URIs in the list.

   • Click OK.

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

8. Under the Certificate Authority settings property group, set the Password property to match what you configured on the default active Content Manager computer.

9. Ensure that all other cryptographic settings match what you set on the default active Content Manager computer.

10. From the File menu, click Save.

Update File Location Properties

Steps

1. Start Cognos Configuration.

2. In the Explorer window, click Environment.

3. In the Properties window, click Deployment files location.

4. Replace the relative path element, "..", with the appropriate environment variable and root directory:

   • On Windows, use the preset environment variables as shown in the table.

     Operating system	Per user	All users
     Windows XP	%APPDATA%	%ALLUSERSPROFILE%
     Windows Vista	%LOCALAPPDATA%	%PUBLIC%

   • On UNIX, use the environment variables that you set in advance.

   For example,

   On Windows XP, to set a single file location for all users, specify %ALLUSERSPROFILE%/c8/deployment.

   On UNIX, if you set an environment variable such as MYHOME for single users, specify $MYHOME/c8/deployment.

5. Repeat step 4 for the following properties:

   • Under Environment,

     - Data files location

     - Map files location

     - Temporary files location

   • Under Environment, Logging, File,

     - Log file location

   • Under Cryptography,

     - Common symmetric key store location

   • Under Cryptography, Cognos,

     - Certificate location

     - Signing key store location

     - Encryption key store location

6. From the File menu, click Save.

The environment variables are resolved when the file locations are accessed during system activities.

You are now ready to start the Cognos 8 services on the Application Tier Components computer. After you complete the required configuration tasks for each Application Tier Components computer in your environment, you can perform the required configuration tasks on other computers, such as the gateway computers. Otherwise you can continue to configure the Application Tier Components computers by changing the default property settings so that they better suit your environment. For example, you can enable and disable services , configure where to send log messages or configure the amount of resources the Cognos 8 service uses .

Configure Gateway Computers

You can install the gateway on one or more computers, depending on your environment.

If you are upgrading from ReportNet, Cognos 8 uses the existing configuration data for the gateway computers. However, if you installed the gateway in a new location, you must configure the gateway.

Ensure that the computer where you installed the active Content Manager is configured and available before you configure gateway computers.

If Content Manager and the gateway are installed on separate computers, on the gateway computer, you must do the following:

	Configure environment properties.
	Update file locations, if required.
	Start the Cognos 8 services.

Configure Environment Properties for Gateway Computers  

You can install the gateway on one or more Web server computers.

If you install the gateway component on a different computer than Content Manager or Application Tier Components, you must configure the gateway computer so that it knows the location of a dispatcher. A dispatcher is installed on every Content Manager and Application Tier Components computer. We recommend that the gateway use the dispatcher on a Application Tier Components computer.

For failover protection, you can configure more than one dispatcher for a gateway computer. When multiple dispatchers are configured, requests are normally routed to the first dispatcher in the list. If this dispatcher becomes unavailable, the gateway determines the next functioning dispatcher on the list and routes requests there. The primary dispatcher status is monitored by the gateway, and requests are routed back to this component when it returns to service.

After you do the required configuration tasks, the gateway computer can work in your environment.

Ensure that the computers where you installed Content Manager are configured and the default active Content Manager computer is available before you configure gateway computers.

Steps

1. Start Cognos Configuration.

2. In the Explorer window, click Environment.

3. In the Properties window, under Gateway Settings, specify the values for Dispatcher URIs for the gateway:

   • Click in the value column.

   • Click the edit button.

   • Change the localhost portion of the URI to the name or IP address of an Application Tier Components computer.

     Tip: If you want to send requests to the dispatcher from an SDK application or a Cognos 8 modeling tool that is outside of a network firewall, we recommend that you connect to a dedicated gateway that is configured to connect to the dispatcher using the Internal dispatcher URI for your environment (for example, http://localhost:9300/p2pd/servlet/dispatch). For security reasons, the default setting for the Dispatcher URI for gateway property prevents the dispatcher from accepting requests for an SDK application or modeling tool that is outside the firewall. Ensure that you configure appropriate security for this dedicated gateway. Do not change your main gateway to use the Internal dispatcher URI. Doing so will reduce the security of the Cognos 8 portal and studios. For more information about the modeling tool and network firewalls, see Firewall Considerations.

   • If you want to add another URI, click Add and change the localhost portion of the new URI to the name or IP address of another Application Tier Components computer.

     Tip: If you want to use the dispatcher on a standby Content Manager computer, ensure that you add it after you add the Application Tier Components computers. If you add the dispatcher from the active Content Manager computer, ensure that it is last in the list.

   • After you specify all the URIs, click OK.

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

5. Under the Certificate Authority settings property group, set the Password property to match what you configured on the default active Content Manager computer.

6. Ensure that all other cryptographic settings match what you set on the default active Content Manager computer.

7. Test that the symmetric key can be retrieved. In the Explorer window, right-click Cryptography and click Test.

   Cognos 8 components check the CSK availability.

8. From the File menu, click Save.

Update File Location Properties

Steps

1. Start Cognos Configuration.

2. In the Explorer window, click Environment.

3. In the Properties window, click Deployment files location.

4. Replace the relative path element, "..", with the appropriate environment variable and root directory:

   • On Windows, use the preset environment variables as shown in the table.

     Operating system	Per user	All users
     Windows XP	%APPDATA%	%ALLUSERSPROFILE%
     Windows Vista	%LOCALAPPDATA%	%PUBLIC%

   • On UNIX, use the environment variables that you set in advance.

   For example,

   On Windows XP, to set a single file location for all users, specify %ALLUSERSPROFILE%/c8/deployment.

   On UNIX, if you set an environment variable such as MYHOME for single users, specify $MYHOME/c8/deployment.

5. Repeat step 4 for the following properties:

   • Under Environment,

     - Data files location

     - Map files location

     - Temporary files location

   • Under Environment, Logging, File,

     - Log file location

   • Under Cryptography,

     - Common symmetric key store location

   • Under Cryptography, Cognos,

     - Certificate location

     - Signing key store location

     - Encryption key store location

6. From the File menu, click Save.

The environment variables are resolved when the file locations are accessed during system activities.

You are now ready to start the Cognos 8 services on the Gateway computer. After you complete the required configuration tasks for each gateway computer in your environment, you can continue to configure the gateway computers by changing the default property settings so that they better suit your environment. For example, you can configure a gateway to use a namespace.

Create a Metric Package 

Before you can use the New Metric Package wizard, you must have access to a metric store used with Metrics Manager version 2.0 or later or you must create a database for a new metric store .

Steps

1. Start Cognos Connection.

2. Click the New metric package button .

3. Type a name and description for the Metric Studio application to represent this metric package, and click Next.

4. Click New data source.

5. Type a name and description for the data source connection for the metric store that contains the content for this metric package, and click Next.

6. In the Type box, click the database type.

7. Select the isolation level, and click Next.

8. Specify the information required for your database type:

   • For a Microsoft SQL Server database, type the name of the database server and the database. Under Signons, select the Password and Create a signon that the Everyone strategy can use check boxes, and type the user ID and password of the user account with access to the database.

   • For an Oracle database, type the connection string. Select User ID, select the Password and Create a signon that the Everyone strategy can use check boxes, and type the user ID and password of the user account with access to the database.

   • For a DB2 database, type the name of the database, the connection string, and the collation sequence. Select User ID, select the Password and Create a signon that the Everyone strategy can use check boxes, and type the user ID and password of the user account with access to the database.

   Tip: To test whether the parameters are correct, click Test.

9. Click Next and then click Finish.

10. Click the new data source and click Next.

11. Click Next and follow the prompts to provide the information necessary to initialize the database. When you see the page that summarizes the data source details and the metric store settings, click Initialize.

12. Select Open this package with Metric Studio after closing the wizard and then click Finish.

Steps Using an Existing Metric Store

1. Start Cognos Connection.

2. Click the New metric package button .

3. Type the name and description for the Metric Studio application to represent this metric package and click Next.

4. Click New data source.

5. Type the name and description for the data source connection for the metric store that contains the content for this metric package, and click Next.

6. In the Type box, click the database type and click Next.

7. Specify the information required for your database type:

   • For a Microsoft SQL Server database, type the name of the database server and the database. Under Signons, select the Password and Create a signon that the Everyone group can use check boxes, and type the user ID and password of the user account with access to the database.

   • For an Oracle database, type the connection string. Under User ID, select the Password and Create a signon that the Everyone group can use check boxes, and type the user ID and password of the user account with access to the database.

   • For a DB2 database, type the name of the database and the connection string. Select User ID, select the Password and Create a signon that the Everyone group can use check boxes, and type the user ID and password of the user account with access to the database.

   Tip: To test whether the parameters are correct, click Test.

8. Click Next.

9. Select Open this package with Metric Studio after closing the wizard and then click Finish.

   Metric Studio opens and the new metric package is displayed in Cognos Connection.

10. Click the new data source and click Next.

11. Click Upgrade.

    The wizard updates the database schemas and other information.

Configuring Framework Manager Computers 

After you install Framework Manager on your Windows computer, you configure it so that it works in your reporting environment.

Some configuration tasks are optional. You perform them to change the default property values used by Framework Manager.

If you install Framework Manager on the same computer as the non-modeling components of 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

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 install Framework Manager on a different computer from the non-modeling components of Cognos 8, you must do the following:

	Configure environment properties for Framework Manager computers.
	Configure a source control system.
	Upgrade Framework Manager projects, if required.

Configure Environment Properties for Framework Manager Computers 

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

We recommend that you install and configure Cognos 8 components before you configure Framework Manager. You must first install and configure Content Manager and then start the Cognos 8 service on at least one Content Manager computer before you configure Framework Manager. This ensures that the certificate authority service issues a certificate to the Framework Manager computer.

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

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 gateway 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 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

     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 Cognos 8. You can configure a source control system.

Configure a Source Control System 

To help you manage, share, and secure different versions of your metadata, you can configure Framework Manager to use a source control system.

You must already have one of the following source control system clients set up on the same computer as Framework Manager:

• Component Software Concurrent Versions System

• Visual Source Safe

For more information about installing and setting up source control systems, see Repository Control in the Framework Manager User Guide.

Steps

1. Start Cognos Configuration.

2. In the Explorer window, under Environment, right-click Source Control Systems and click New resource, Source Control System.

   Source Control System is available on Windows computers that have Framework Manager installed and on Windows or UNIX computers that have Application Tier Components installed.

3. In the Name box, type a name for your source control system.

4. In the Type box, select a source control system from the list.

5. Click OK.

6. In the Properties window, for the Source control system executable file (.exe) location property, specify the file location and name of the .exe file.

   • For VSS, type file_location\ss.exe

   • For CVS, type file_location\cvs-version.exe

     where version is the CVS version number.

7. From the File menu, click Save.

You can now test your installation and configuration. You can also change default settings, if required. For example, you can change a port, configure SSL protocol, configure cryptographic settings, or change the Gateway URI to use an alternate gateway.

If you upgraded from an older version of Framework Manager, you can upgrade existing projects in the new version of Framework Manager.

Upgrade Framework Manager Projects 

You can upgrade the metadata in an earlier version of a Framework Manager project by opening the project in the latest version of Framework Manager. A message appears indicating that the project was created using an older version of Framework Manager and asking if you want to specify a location for the backup file.

Before upgrading a project, we recommend that you do the following:

• Update any dependent projects or segments that you referenced in your project.

  For example, if your project links to a segment in a different project, you must upgrade the segment first. You can then upgrade the parent project.

  For more information, see the Framework Manager User Guide.

• Check out the project you want to upgrade using the third-party repository control.

  For more information, see the third-party vendor documentation.

• To upgrade a model that is located on a LAN, you must copy the model to a folder on a local machine. From your local machine, upgrade the model, and then copy the project back to the original LAN location.

Steps

1. Start Framework Manager.

   If the model schema version is older than the currently supported version, you may be prompted to specify a location for a backup of the project. If you click Cancel, Framework Manager will not open the project.

2. In the Start page, click Open a project.

3. Locate the project folder you want to open, and click the .cpf file.

4. Click Open.

5. If you are prompted for a location to store the backup, choose a location:

   • To save the backup model in the default location, click No.

   • To specify a different location, click Yes and browse to the location.

6. Click OK.

You must now republish your packages to a current version of the Application Tier Components server. For more information, see the Framework Manager User Guide.

To take a tour of Cognos 8, start Cognos Connection and select Quick Tour. For information about using different Cognos 8 components, see their documentation.

Configuring Transformer

If you install Cognos 8 Transformer on a different computer from the non-modeling components of Cognos 8, you must configure it to communicate with the other components. You may also want to make Transformer available for Transformer modelers to personally install on their computers.

The instructions in this topic are for the installer or administrator. If you are the Transformer modeler or business specialist who wants to download and use Transformer, see Deploying Cognos 8 Transformer for Modelers.

If you install Transformer on a Windows Vista computer, and you plan to use the cogtr.xml.samples file as a template, you must update default preferences in the Transformer configuration file.

If you want to use Transformer models from Cognos Series 7 and you want to continue to use IQD data sources, you must add the locations of your Cognos Series 7 data sources to the Cognos Series 7 gateway file.

To configure the Transformer computers, do the following:

	Configure properties on the Transformer computers.
	Update default preferences in the Transformer configuration file, if required
	Add the locations of your Cognos Series 7 data sources to the Cognos Series 7 gateway file, if required

To make Transformer available for modelers to install, do the following:

	Create a network installation location for Transformer.
	Export configuration data for Transformer modelers.

Configure Cognos 8 Transformer Computers

You must configure Cognos 8 Transformer to communicate with the other Cognos 8 components.

The instructions in this topic are for the installer or administrator. If you are the Transformer modeler or business specialist who wants to download and use Transformer, see Deploying Cognos 8 Transformer for Modelers.

If you install Cognos 8 Transformer on the same computer as the non-modeling components of 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

You can upgrade models from Series 7.x versions of Transformer if you have saved them as MDL files.

You can continue to use PowerCubes built with Series 7.3 and higher versions of Transformer in Cognos 8. However, to use Cognos 8 authentication providers, you must upgrade the PowerCubes.

To upgrade PowerCubes to Cognos 8 PowerCubes, you must:

• open the Series 7.x Transformer model MDL file in Cognos 8 Transformer

• rebuild the PowerCube in the Cognos 8 Transformer

For more information about upgrading Series 7 PowerCubes, see Upgrading Transformer Models and PowerCubes.

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

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 gateway computer .

Ensure that the Web server is configured and running .

To support the use of Cognos 8 data sources (including packages and reports) in Transformer, ensure that the database client is installed on the Transformer computer .

Steps

1. On the computer where you installed Cognos 8 Transformer, start 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

     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 Cognos 8 Transformer 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.

   Cognos 8 Transformer is configured to communicate with the other components of Cognos 8.

9. If you installed Transformer on a Windows Vista computer, or if any Cognos 8 BI component is installed on a Windows Vista computer, update your file location properties:

   • Log on as an administrator.

   • In the c8_location\configuration directory, open cogtr.xml.sample in a text editor.

   • Locate all values that use a relative path, "..\directory".

   • Replace the relative path element, "..", with the same environment variable and root directory as you use for file locations on the other Cognos 8 computers.

   • Save the file as cogtr.xml.

   • In the c8_location\CS7Gateways\bin directory, open cs7g.ini in a text editor.

   • Add the locations for your Cognos Series 7 data sources to the file.

   • Save the file.

   Changes are applied the next time you open Transformer.

Update Default Preferences for Windows Vista

With security enhancements in Windows Vista, Microsoft changed the structure of user directories. If you want to use the cogtr.xml.samples file as a template, you must edit the default preferences settings. If you want all users to have the same default directories, you must change the default preferences to a common location to which users have access. If you want users to have the Windows Vista directories, you can delete the default preferences for the directories.

The instructions in this topic are for the installer or administrator. If you are the Transformer modeler or business specialist who wants to download and use Transformer, see Deploying Cognos 8 Transformer for Modelers.

Steps

1. Log on as the administrator.

2. In the c8_location\configuration directory, open cogtr.xml.sample in a text editor in elevated mode by right-clicking on the text editor and selecting Run as Administrator.

3. If you want all users to have the same default directories, change the directories to a location to which all users have read and write access.

   The directories to change are as follows:

   • <Preference Name="CubeSaveDirectory" Type="string" Value="..\temp"/>
   • <Preference Name="DataSourceDirectory" Type="string" Value="..\temp"/>
   • <Preference Name="DataWorkDirectory" Type="string" Value="..\temp"/>
   • <Preference Name="LogFileDirectory" Type="string" Value="..\logs"/>
   • <Preference Name="ModelSaveDirectory" Type="string" Value="..\temp"/>
   • <Preference Name="ModelWorkDirectory" Type="string" Value="..\temp"/>

4. If you want users to have the Windows Vista default directories, delete the preferences specified in step 3 from the file.

   The Windows Vista default directories for Transformer are

   • CubeSaveDirectory

     Documents\Transformer\PowerCubes

   • DataSourceDirectory

     In Cognos Configuration, under Environment, Data files location property

   • DataWorkDirectory

     In Cognos Configuration, under Environment, Temporary files location property

   • LogFileDirectory

     Documents\Transformer\Logs

   • ModelSaveDirectory

     Documents\Transformer\Models

   • ModelWorkDirectory

     In Cognos Configuration, under Environment, Temporary files location property

5. Change other settings as required.

6. Save the file as cogtr.xml.

   The changes are applied the next time you open Transformer.

Add Cognos Series 7 Data Sources to Transformer

If you plan to use Transformer models and data sources from Cognos Series 7, you must add the location of your Cognos Series 7 data sources to the Transformer gateway file.

The instructions in this topic are for the installer or administrator. If you are the Transformer modeler or business specialist who wants to download and use Transformer, see Deploying Cognos 8 Transformer for Modelers.

Steps

1. Log on as the administrator.

2. In the c8_location\CS7Gateways\bin directory, open cs7g.ini in a text editor.

   On Windows Vista, open it in elevated mode by right-clicking on the text editor and selecting Run as Administrator.

3. Add the locations for your Cognos Series 7 data sources to the file.

4. Save the file.

   The changes are applied the next time you open Transformer.

Create a Network Installation Location for Transformer Modelers

Your organization may have specialized business or power users who want to build PowerCubes that are modeled on a combination of corporate and personal data sources. These users may want to do their own analysis of the data for their line of business or a small group of users. An installer or administrator can download an executable file to a Web or LAN location, where modelers can run the file to launch the Cognos 8 Transformer installation wizard.

The instructions in this topic are for the installer or administrator. If you are the Transformer modeler or business specialist who wants to download and use Transformer, see Deploying Cognos 8 Transformer for Modelers.

Before you make the installation file available to Transformer modelers, other resources and permissions must be set up:

• Database client software is installed, or available for modelers to install, on the Transformer computers that are used to access Cognos 8 data sources or Cognos Series 7 IQD data sources.

• Modelers must have privileges to create a data source in Cognos Administration.

  Modelers do not need direct access to Cognos Administration. They can create and update data sources by using Transformer or command line tools. You can provide modelers with a secured folder in Cognos Connection in which to publish PowerCube packages.

• Modelers must have access to a location in which to store the PowerCube after building it.

  This location must also be accessible to the Cognos 8 service and can be a secured share on a LAN.

• Modelers may require special privileges to remotely run the Cognos 8 PowerCube Connection utility, which is located on the Cognos 8 server. For more information, see the topic about updating published PowerCubes and PowerCube connections in the Transformer User Guide.

• To build PowerCubes on a specific Transformer server, modelers should have FTP privileges to transfer models and execute privileges to build cubes on that server.

  Modelers can transfer models and execute cube builds using scripts. Modelers can also use automated methods to build PowerCubes. For more information, see the Administration and Security Guide.

Steps

1. Insert the CD for Cognos 8 Transformer modeling product.

2. If the Welcome page of the installation wizard appears, exit the wizard.

3. On the CD, locate the c8transformerinstall.exe file.

4. Copy the file to a secure location to which your Transformer modelers have access.

Export Configuration Data for Transformer Modelers

If you want to make the Transformer installation file available to Transformer modelers, the modelers will need the dispatcher and encryption settings to configure Transformer on their local computer. You can export the configuration from one Transformer computer for use with all other Transformer computers. The modelers can copy the exported configuration file to their Transformer installation directory and then run the command to configure the Transformer computer silently.

The instructions in this topic are for the installer or administrator. If you are the Transformer modeler or business specialist who wants to download and use Transformer, see Deploying Cognos 8 Transformer for Modelers.

If you updated the coglocale, cogtr.xml, or cs7g.ini files on the Transformer computer, you must copy these files to the Web or LAN location so that Transformer modelers can download them to their computer.

To export the configuration, the source computer must have the same Cognos 8 components as the Transformer modeler computers . If some modelers will be installing on Windows Vista, you must create an export file from a Windows Vista computer. We suggest creating separate folders on the Web or LAN location for Windows and Windows Vista.

Steps to Export the Transformer Computer Configuration

1. In Cognos Configuration, from the File menu, click Export as.

2. If you want to export the current configuration to a different folder, in the Look in box, locate and open the folder.

   Ensure that the folder is protected from unauthorized or inappropriate access.

3. In the File name box, type a name for the configuration file.

4. Click Save.

5. Rename the exported file to cogstartup.xml.

6. Copy the exported cogstartup.xml file from the source computer to the same Web or LAN location as the Transformer installation file.

7. If you changed the global configuration on the source computer, copy the coglocale.xml file from the source computer to the same Web or LAN location as the Transformer installation file.

   The default location of the coglocale.xml file is c8_location\configuration.

Steps to Download Transformer Configuration Files

1. If you updated the cogtr.xml, copy it from the c8_location\configuration directory to the same Web or LAN location as the Transformer installation file.

2. If you updated the cs7g.ini file, copy it from the c8_location\CS7Gateways\bin directory to the same Web or LAN location as the Transformer installation file.

Deploying Cognos 8 Transformer for Modelers

If you are the business specialist or Transformer modeler, you must now deploy Transformer so that you can build PowerCubes and publish them to selected users or groups.

If you have not completed the installation, follow the steps to install Transformer. To configure Transformer so that it can communicate with the Cognos 8 dispatcher, follow the steps to configure Transformer.

If Cognos Connection is secured, you must have privileges to create data sources and publish packages in Cognos Connection.

You can upgrade models from Series 7.x versions of Transformer if you have saved them as MDL files.

You can continue to use PowerCubes built with Series 7.3 and higher versions of Transformer in Cognos 8. However, to use Cognos 8 authentication providers, you must upgrade the PowerCubes. After upgrading, the PowerCubes are no longer compatible with Series 7 Transformer.

To upgrade PowerCubes to Cognos 8 PowerCubes, you must:

• open the Series 7.x Transformer model MDL file in Cognos 8 Transformer

• rebuild the PowerCube in the Cognos 8 Transformer

For more information, see Upgrading Transformer Models and PowerCubes.

To support the use of Cognos 8 data sources (including packages and reports) in Transformer, ensure that the database client is installed on the Transformer computer .

Steps to Install Transformer

1. From the Web or LAN location that the administrator provided, run the c8transformerinstall.exe file.

   The contents are expanded to the Documents and Settings\username\Local settings\Temp directory and then the Transformer installation wizard opens.

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

   Tip: The Series 7 IQD Bridge component is not supported on Linux and HP-UX Itanium.

3. In the Finish page of the wizard, select View the Readme and then click Finish.

   Tip: For character-mode installations on UNIX and Linux, close the readme text file by pressing Ctrl + C or Q.

4. Create a MANPATH environment variable and configure it to point to the cogtr.1 file in the Transformer_location/webcontent/documentation/en directory.

   The cogtr.1 file provides the syntax for UNIX command line options that are supported by Cognos 8 Transformer. The man page is accessible in UNIX by typing man.

Steps to Configure Transformer

1. Go to the same Web or LAN location as the Transformer installation file.

2. If any .xml files are present, copy them to the Transformer_location\configuration directory, where Transformer_location is the directory where you installed Transformer.

   The default location is C:\Program Files\Cognos\c8.

3. If an .ini file is present, copy it to the Transformer_location\CS7Gateways\bin directory.

4. Go to the Transformer_location\bin directory.

5. Type the configuration command:

   ./cogconfig.bat -s

   Cognos Configuration applies the configuration settings specified in the local copy of cogstartup.xml, encrypts credentials, generates digital certificates, and starts the Cognos 8 service.

6. To test Cognos 8 Transformer, from the Start menu, click Programs, Cognos 8,Transformer.

   If you see the Transformer window, your installation is working.

7. After Transformer is intalled and running successfully, delete the installation files that were extracted from the installation file.

Configure Metric Designer 

Configure Environment Properties for Metric Designer Computers 

If you install Metric Designer on a different computer from other 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 Cognos 8 components before you configure Metric Designer. You must first install and configure Content Manager and then start the 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 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 gateway computer .

Steps

1. On the computer where you installed Metric Designer, start Cognos Configuration.

2. In the Explorer window, click Environment.

3. 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 apache_mod, type the following syntax:

     http://host_name:port/cognos8/cgi-bin/module

     where module is as follows:

     Operating system	Apache 1.3 module	Apache 2.0 module
     Windows	mod_cognos.dll	mod2_cognos.dll
     Solaris or AIX	mod_cognos.so	mod2_cognos.so
     HP-UX PA-RISC	mod_cognos.sl	mod2_cognos.sl
     HP-UX IA	(not supported)	mod2_cognos.so

4. 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.

5. From the File menu, click Save.

Metric Designer is configured to communicate with other Cognos 8 components.

Upgrade Metric Designer Projects 

You can upgrade the metadata in an earlier version of a Metrics Designer project by opening the project in the current version of Metric Designer. A message appears indicating that the project was created using an earlier version of Metrics Designer and asking if you want to specify a location for the backup file.

Before upgrading a project with a model that is located on a LAN, you must copy the model to a folder on a local machine. From your local machine, upgrade the model, and then copy the project back to the original LAN location.

Steps

1. Start Metric Designer.

2. In the Start page, click Open a Project.

3. Locate the project folder you want to open, and click the .cpf file.

4. Click Open.

5. If you are prompted for a location to store the backup, choose a location:

   • To save the backup model in the default location, click No.

   • To specify a different location, click Yes and browse to the location.

   You are prompted to back up the project if the model schema version is older than the currently supported version. If you click Cancel, Metric Designer will not open the project.

6. If the metric package or data source connection associated with the project no longer exists, you are prompted to choose an existing metric package or data source connection to be used.

7. Click OK.

Start the Cognos 8 Services

Steps

1. Start Cognos Configuration.

2. Ensure that you save your configuration, otherwise you cannot start the Cognos 8 service.

   If you are upgrading, a message appears indicating that configuration files were detected and upgraded to the new version.

3. From the Actions menu, click Test.

   Cognos Configuration checks the CSK availability, tests the namespace configuration, and tests the connections to the content store and logging database.

   If you are using the notification database and the mail server, they are tested as well.

   Tip: If Test is not available for selection, in the Explorer window, click Local Configuration.

4. If the test fails, reconfigure the affected properties and then test again.

   You can test individual services by right-clicking the service in the Explorer panel and selecting Test.

   Do not start the service until all tests pass.

5. From the Actions menu, click Start.

   It may take a few minutes for the Cognos 8 service to start.

   This action starts all installed services that are not running. If you want to start a particular service, select the service node in the Explorer window and then click Start from the Actions menu.

Test the Installation and Configuration 

You can test your configuration settings by running the test feature as you configure Cognos 8. After you have completed the configuration and started the services, you can test the installation by opening Cognos Connection. If you installed Framework Manager, Cognos 8 Transformer, or Metric Designer, you can test it by starting the application and creating a project.

If you installed Metric Studio and you have created a package, you have already tested your installation and configuration. You can create a metric package only if Metric Studio is installed and configured properly.

Steps for Content Manager or Application Tier Components Computer

1. Open a Web browser.

2. Test the availability of the dispatcher by typing

   http://ContentManagerComputer_name:port/p2pd/servlet

   If the response includes the string State: Running, the dispatcher is available.

Steps for Gateway Computer

1. Open a Web browser.

2. Test the availability of the dispatcher by typing

   http://ContentManagerComputer_name:port/p2pd/servlet

   If the response includes the string State: Running, the dispatcher is available.

3. Open Cognos Connection by typing one the following, where cognos8 is the virtual directory you created when you configured the Web server.

   • For the CGI gateway:

     http://GatewayComputer_name:port/cognos8

   • For an ISAPI gateway:

     http://GatewayComputer_name:port/cognos8/isapi

   • For Apache Connector on Windows:

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

   • For Apache Connector on Solaris or AIX:

     http://GatewayComputer_name:port/cognos8/cgi-bin/mod_cognos.so

   • For Apache Connector on HP-UX PA-RISC:

     http://GatewayComputer_name:port/cognos8/cgi-bin/mod_cognos.sl

   • For Apache Connector on HP-UX IA:

     http://GatewayComputer_name:port/cognos8/cgi-bin/mod2_cognos.so

   • For a gateway servlet:

     http://GatewayComputer_name:port/context_root/servlet/ Gateway

   It may take a few minutes for the Web page to open. If you see the Welcome page of Cognos Connection, your installation is working.

Step for Framework Manager

• To start Framework Manager, from the Start menu, click Programs, 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.

Step for Cognos 8 Transformer

• To start Cognos 8 Transformer, from the Start menu, click Programs, Cognos 8,Transformer.

  To start Cognos 8 Transformer manually, double-click the following file in the c8_location\bin directory:

  • For Windows, cogtr.exe

  • For UNIX or Linux, cogtr.sh

  If you see the Transformer window, your installation is working.

Step for Metric Designer

• To start Metric Designer, from the Start menu, click Programs, Cognos 8, Metric Designer.

  If you see the Welcome page of Metric Designer, your installation is working.