.
The strategy depends on the data that you want to use and any customizing
that you have done with your existing configuration.You must upgrade the software to move from an earlier version of Cognos 8, ReportNet, or Metrics Manager to a new version of Cognos 8. You must upgrade all components. Components from different versions are not compatible. If you are using Cognos Series 7 PowerCubes as a data source, it is not necessary to upgrade Transformer unless you want to use the features of the new version of Transformer. For more information, see Upgrading Transformer Models and PowerCubes. PowerCubes that are built using Series 7.3 Transformer (or later) and Cognos 8.3 Transformer are both supported with Cognos 8 reporting and metrics.
You can upgrade directly to Cognos 8 from the following product versions:
Cognos 8 8.1 or later, including MR releases
ReportNet 1.1 MR1 through MR4
Metrics Manager 2.0 or later
If you have an earlier version of ReportNet, you must first upgrade to one of the ReportNet 1.1 MR releases (1 through 4) and then upgrade to Cognos 8.
You can run different versions of the software on your computer at the same time, provided that you install them in different directories and configure each to use a different content store and a different set of ports and URLs for each version.
Before you begin upgrading, you must plan your upgrade strategy .
The strategy depends on the data that you want to use and any customizing
that you have done with your existing configuration.
When upgrading from ReportNet, if you want to use an existing configuration directory, you must ensure that the configuration data from ReportNet is copied to the Cognos 8 installation location. This includes backing up existing data, configuring Cognos 8 to use the existing content store or a copy of it, copying the configuration data files to the Cognos 8 installation directory, and reapplying any manual edits or customizations that you applied in the earlier version.
If both ReportNet and Metrics Manager are on the same computer and you plan to upgrade to Cognos 8, upgrade ReportNet first, and then Metrics Manager.
After upgrading to Cognos 8 using existing data, additional configuration may be required if you want to use new features. For information about new features in Cognos 8, see Cognos 8 New Features.
You must use the Cognos 8 SDK with Cognos 8 Business Intelligence.
When you upgrade, you must make some changes to your SDK program for it to function with the Cognos 8 version of the WSDL file. Some methods, classes, and properties have been deprecated in Cognos 8. Deprecated features continue to function as before, but will be removed in future releases. Some other methods, classes, and properties are obsolete, and have been removed from the Cognos 8 SDK.
For information about changes to methods, classes, properties, and enumeration sets, see the Release Notes appendixes in the Cognos 8 SDK Developer Guide.
New report specifications have been added in Cognos 8. If you run a ReportNet report in Cognos 8, it is automatically upgraded to the Cognos 8 format. After a report is upgraded to Cognos 8, it cannot be returned to the ReportNet format. Because of the potential for users to upgrade report specifications that SDK applications may depend on, we recommend that you set access permissions on those reports to limit user access. For more information about setting access permissions, see the Cognos 8 Administration and Security Guide.
Do not upgrade your report specifications if you have SDK applications that create, modify, or save report specifications. You must first update your SDK applications to comply with the Cognos 8 report specifications schema. Otherwise, your SDK applications may not be able to access the upgraded report specifications. For information about upgrading report specifications, see the Cognos 8 SDK Developer Guide.
We recommend that you do not upgrade your report specifications if you are unsure about whether you have SDK applications that create, modify, or save report specifications. Contact your SDK administrator for more information about your SDK applications.
When you upgrade ReportNet, Content Manager automatically upgrades the schema and contents in the content store. After you upgrade, you cannot use the upgraded content store with ReportNet because it is not backward compatible. To protect your original content store data, you must configure Cognos 8 to use a copy of the content store. You create a copy by backing up the original content store and restoring the data into a new content store.
Cognos 8 can read deployment archives produced by ReportNet.
If you saved reports from Series 7 PowerPlay or scorecards from Cognos Metrics Manager 2.x in ReportNet, the content store upgrade carries the saved reports and scorecards forward into Cognos 8.
You can use the same models and projects in Framework Manager for Cognos 8 that you used with the earlier version. When upgrading models, the validation process produces errors for every model. To upgrade a project, you open and save it in the new version of Framework Manager. For more information, see the Framework Manager User Guide.
If you have SDK applications that rely on an earlier version of the report specifications, you cannot use Framework Manager to publish your model without losing backward compatibility.
The upgrade does not account for such items as undocumented and unsupported features, changes in report behavior, and changes in formatting and style sheets. For more information, see the Report Studio Professional Authoring User Guide.
If you published cubes from Cognos Series 7 PowerPlay Enterprise Server in ReportNet, you may not be able to publish those same cubes in Cognos 8. The default cookie path that was used in ReportNet is changed in Cognos 8. To enable publishing of your Cognos Series 7 PowerCubes in Cognos 8, see Set Up to Publish Series 7 PowerCubes After Upgrade from ReportNet.
In earlier versions, Metrics Manager used a data store database to store, organize, and retrieve information. In Cognos 8, this database is referred to as the metric store. If you want to use data store content from an earlier version, you can export the content from the data store, install Cognos 8, and import the content into the metric store.
You cannot use the metric store with the earlier version of Metrics Manager because it is not backward compatible. Before exporting the data store content, ensure that you back it up, in case you must revert to the earlier version.
You can upgrade projects from earlier versions of Metrics Manager
if you want to use them with Cognos 8 Metric Designer .
You cannot use upgraded projects with the earlier version because they are not backward compatible. Before upgrading projects, ensure that you have backed them up, in case you need to revert to the earlier version.
When you upgrade from ReportNet or an earlier version of Cognos 8, security may be affected. For example, new roles may exist that were not in earlier releases and some roles may have new capabilities. As a result, the security of your upgraded system may not be at the desired level. To confirm the security level after upgrading, see the Administration and Security Guide.
As you upgrade your Cognos 8 products, you may choose to install some components on new operating systems. You must consider how these operating systems might affect the installation and configuration of Cognos 8.
If your upgrade includes installing Cognos 8 components on Windows Vista, you must consider the following:
roaming profiles
Profiles of users are stored in a different location than in earlier Windows operating systems. The Documents and Settings directory is replaced by the Users directory. The All Users directory is replaced by the Public directory.
environment variables
The default paths that are associated with environment variables are changed. If you use scripts or applications that reference the paths in the environment variables, you may need to update the scripts and applications.
In addition, you must
reconfigure the default file locations in Cognos Configuration so
that a single file location can be used across operating systems
in your Cognos 8 environment. For more information, see
the topics about updating file location properties in the configuration
chapter .
In you are upgrading Cognos 8 BI in an environment that includes earlier versions of other Cognos 8 products, such as Cognos 8 Controller 8.2, Cognos 8 Planning 8.2, or Cognos 8 BI Analysis for Excel 8.2, install the new version of Cognos 8 BI in a separate location from the other Cognos 8 product and configure Cognos 8 BI to operate independently of that product. After you upgrade the other product to a compatible version with Cognos 8 BI, you can then configure the two products to operate together.
You can upgrade Cognos 8 in the same directory as an earlier version or in a different directory.
If you want to upgrade Cognos 8 in the same directory, you must first back up your data, ensure that Framework Manager projects are not checked into a source control system, and uninstall the older version of Cognos 8. For complete instructions, see the steps to install in the same directory.
If you are installing on a new computer, see the steps to install in a new directory.
When you back up the configuration data, you store it in a secure directory. The directory must be protected from unauthorized or inappropriate access.
An alternative method of upgrading is to export the entire content store to a deployment archive and then import the deployment archive into Cognos 8 after the upgrade. For more information about deployment, see the Administration and Security Guide. A deployment upgrade is required if you want to change the type of database that you use for the content store. If you use the deployment upgrade method, only the steps for exporting and restoring the configuration data are different. All other steps are the same as documented in this section.
Cognos 8 installs and uses Tomcat as its application server by default. If you do not want to use Tomcat, you must follow a different set of steps to upgrade. For more information, see Upgrade to Cognos 8 in an Application Server Environment.
When you upgrade, the report administrator will no longer have access to the Content Administration tool. The report administrator will not be able to create deployment definitions in Cognos 8.
If you manually edited any configuration files, the changes will be overwritten during the upgrade. You must reapply the changes. You should keep a record of any customizations to ensure that they can be reapplied after upgrading. You should also back up these files so that the original version can be restored if necessary.
You may have modified files other than those in the configuration folder. If so, you should also back up the additional files before upgrading.
The Cognos 8 presentation service supports automatic upgrade of some system.xml files. If you made many customization changes to system.xml files, you can use this automatic upgrade feature instead of reapplying the changes manually after upgrading. The system.xml files are overwritten during the installation of Cognos 8. Therefore, you must back up the customized versions of these files and then copy them to the directory after upgrading Cognos 8. The automatic upgrade will be applied when you start the Cognos 8 service.
The system.xml files for which automatic upgrade is supported are in the following directories:
c8_location/templates/ps
c8_location/templates/ps/portal
c8_location/templates/ps/qs
Note: The recommended method to upgrade customized files is to manually reapply changes after the new software is installed. Automatic upgrade of system.xml files is to be used only when you have made a large number of customizations to these files.
Using your database tools, back up your existing content store database.
For information on how to do this, see the documentation for your database.
Back up the following files to a secure location:
coglocale.xml in the c8_location/configuration directory
server.xml in the c8_location/tomcat4.1.27/conf directory
system.xml in the appropriate directory, if required
Ensure that you note the directory path. For example,
c8_location/templates/ps
In Cognos Configuration, export the configuration data to the same secure location.
To make the data usable for upgrading, name the file cogstartup.xml.
Important: Because the exported crnstartup.xml file contains unencrypted passwords, ensure that the location is secure.
Back up any manually edited files in the c8_location/configuration and other directories to a secure location.
Stop all Cognos services.
If you use a source control system such as CVS, ensure that all Framework Manager projects you want upgraded are checked out before upgrading.
Any projects that are checked in when you uninstall will not be upgraded.
Prepare Transformer models, if required .
Upgrade or install third-party products .
Uninstall Cognos 8 from every Cognos 8
computer .
Install the newer version of Cognos 8 in the same directory
that you used for Cognos 8 on every computer .
Copy the .xml files from the secure backup location as follows:
Copy cogstartup.xml and coglocale.xml to c8_location/configuration.
Copy server.xml to c8_location/tomcat4.1.27/conf.
Copy system.xml to the appropriate directory, if required.
For example,
c8_location/templates/ps
If you are prompted to overwrite existing files, click Yes.
For files that you manually edited in earlier versions of Cognos 8, edit the same files in the c8_location directory and reapply the changes that you made to the original customized files.
Do not copy the customized files to the c8_location directories. The earlier versions of these files may not be compatible.
If you use Oracle for a data source, import source, logging database, or the content store database, delete the classes12.jar file from the c8_location\webapps\p2pd\WEB-INF\lib directory.
Older versions of Cognos 8 used this file, which conflicts with the ojdbc14.jar file that is used in newer versions.
In Cognos Configuration, review the configuration, and then save it.
When you save the configuration, an upgrade dialog appears and asks if you want to upgrade your report specifications. The default setting is to not upgrade report specifications.
Important: Do not upgrade your report specifications if you have SDK applications that create, modify, or save report specifications. You must first update your SDK applications to comply with the Cognos 8 report specifications schema. Otherwise, your SDK applications may not be able to access the upgraded report specifications. In addition, do not save your reports until the SDK applications have been updated. For information about upgrading report specifications, see the Cognos 8 SDK Developer Guide.
Start Cognos 8.
Cognos 8 automatically upgrades the content store. System.xml files are upgraded, if required, to a Cognos 8 compatible version.
Install and
configure Framework Manager.
Upgrade your Framework Manager projects and reports as
required. For instructions, see the Framework Manager User
Guide.
Report Studio users must clear their Web browser cache to get the latest images.
If you use pages created in earlier versions of Cognos 8, you may need to reconfigure the following properties:
Title
Open action links going outside a portal
For more information, see the Administration and Security Guide.
Install and
configure Transformer, if required.
Upgrade Transformer models and PowerCubes , if
required.
If you use SAP Enterprise Portal, upgrade your master iView.
Old SAP iViews will not work with the new Portal Services producer component. For information, see the topic about deploying Cognos Portlets to SAP Enterprise Portal in the Administration and Security Guide.
Using your database tools, copy your existing content store database into a new content store database.
For information on how to do this, see the documentation for your database.
Back up the following files to a secure location:
coglocale.xml in the c8_location/configuration directory
server.xml in the c8_location/tomcat4.1.27/conf directory
system.xml in the appropriate directory, if required
Ensure that you note the directory path. For example,
c8_location/templates/ps
In Cognos Configuration, export the configuration data to the same secure location.
To make the data usable for upgrading, name the file cogstartup.xml.
Important: Because the exported cogstartup.xml file contains unencrypted passwords, ensure that the location is secure.
Back up any manually edited files in the c8_location/configuration and other directories to a secure location.
Prepare Transformer models, if required .
Upgrade or install third-party products .
Install Cognos 8 in a new directory .
Copy the .xml files from the secure backup location to the following directory:
Copy cogstartup.xml and coglocale.xml to c8_location/configuration.
Copy server.xml to c8_location/tomcat4.1.27/conf.
Copy system.xml to the same directory in the new location as it was in the earlier version, if required.
For example,
c8_location/templates/ps
If you are prompted to overwrite existing files, click Yes.
For files that you manually edited, edit the same files in the c8_location directory and reapply the changes that you made to the original customized files.
Do not copy the customized files to the c8_location directories. The earlier versions of these files may not be compatible with Cognos 8.
Configure new Web server aliases .
In Cognos Configuration, configure Cognos 8 to point to
the new content store, configure new ports and URLs, use a different
cookie path, and then save the configuration .
Ensure that the port numbers and service name for this installation are different from those used for earlier versions so that there are no conflicts.
Ensure that security authentication settings are not changed. For example, the namespaces must be the same for policies, users, roles, and groups to work correctly.
When you save the configuration, an upgrade dialog appears and asks if you want to upgrade your report specifications. The default setting is to not upgrade report specifications.
Important: Do not upgrade your report specifications if you have SDK applications that create, modify, or save report specifications. You must first update your SDK applications to comply with the Cognos 8 report specifications schema. Otherwise, your SDK applications may not be able to access the upgraded report specifications. In addition, do not save your reports until the SDK applications have been updated. For information about upgrading report specifications, see the Cognos 8 SDK Developer Guide.
Start Cognos 8.
Cognos 8 automatically upgrades the new content store. System.xml files are upgraded, if required, to a Cognos 8 compatible version.
Install and
configure Framework Manager.
Upgrade your Framework Manager projects and reports as
required. For instructions, see the Framework Manager User
Guide.
Report Studio users must clear their Web browser cache to get the latest images.
Open the Administration portal, and unregister the dispatchers that are used with earlier versions of Cognos 8.
When you open the Administration portal in Cognos 8, you may see the dispatchers that are registered for both versions.
For more information, see the Administration and Security Guide.
If you use pages created in ReportNet, you may need to reconfigure the following properties:
Title
Open action links going outside a portal
For more information, see the Administration and Security Guide.
Install and
configure Transformer, if required.
Upgrade Transformer models and PowerCubes , if
required.
If you use SAP Enterprise Portal, upgrade your master iView.
Old SAP iViews will not work with the new Portal Services producer component. For information, see the topic about deploying Cognos Portlets to SAP Enterprise Portal in the Administration and Security Guide.
When you are ready to uninstall the previous version of Cognos 8, do the following:
Stop the Cognos 8 service.
Uninstall Cognos 8 from all computers.
For instructions, see Uninstalling Cognos 8.
When you complete the upgrade tasks, Cognos 8 is fully configured except for new properties and features, and scorecarding features.
If you use Chinese, Japanese, or Korean characters, you may notice differences in some characters after upgrading. For more information, see the Troubleshooting section of the Administration and Security Guide.
If you use a DB2 database for the content store, you can tune the database to take advantage of DB2 features. For more information, see the Architecture and Deployment Guide.
To ensure the security and integrity of Cognos 8, it is important to protect the installation directory from unauthorized or inappropriate access.
If you use your own installation of Apache Derby for the content store or notification databases, you must migrate the databases to Cognos Content Database before starting Cognos 8. To do this, remove the CognosCMDerby.jar file from the Apache Derby database and copy the database directories to the content store directory of the Cognos 8 installation.
Ensure that your Apache Derby Network Server is running.
Start the ij utility using the ij.bat or ij.ksh script file.
Connect to the Apache Derby database by typing the following ij utility command:
connect 'jdbc:derby://host:port/db_name;user=username;password=password';
Here is an example:
connect 'jdbc:derby://localhost:1527/cm;user=cognos; password=cognos';
If you changed the port number from the default 1527, use the correct port number for your Apache Derby database. Use the correct name of your Apache Derby database.
Clear the derby.database.classpath property of the database by typing the following ij utility command:
CALL SYSCS_UTIL.SYSCS_SET_DATABASE_PROPERTY('derby.database.classpath','');
Remove the existing jar file by typing the following ij utility command:
CALL sqlj.remove_jar('schema_name.CMFunctionsjar', 0);
For example, if your schema is cognos, type
CALL sqlj.remove_jar('cognos.CMFunctionsjar', 0);
Enable row level locking on the database by typing the following ij utility command:
CALL SYSCS_UTIL.SYSCS_SET_DATABASE_PROPERTY('derby.storage.rowLocking','true');
Close the ij utility by typing the following command:
disconnect;
Stop the Apache Derby Network Server.
Copy the content store and notification database directories to the c8_location\contentstore directory.
For example:
xcopy "c:\derby\data\cm" "c:\Program Files\c8\contentstore\cm" /s /ixcopy "c:\derby\data\notify_db" "c:\Program Files\c8\contentstore\notify_db" /s /i
In this example, the content store database is named cm and the notification database is named notify_db. They are located in the c:\derby\data directory.
After you upgrade from ReportNet, the product name will be changed to Cognos 8. In addition, some file, directory, and command names will be different. If you install Cognos 8 in a different directory from ReportNet, default directory names change when you install Cognos 8. If you install Cognos 8 in the same directory as ReportNet, the existing directory names do not change. Some file name changes occur when you install Cognos 8 and other changes occur after you save the Cognos 8 configuration. You must change the alias for the virtual directory manually, if required.
The following names are affected.
ReportNet name | Cognos 8 name | Description |
crn | c8 | Default installation directory |
crn | cognos8 | Default Web browser alias or virtual directory |
crnstartup.xml | cogstartup.xml | Configuration data file used when starting Cognos Configuration |
crnstartup_ yyyymmddhhmm.xml | cogstartup_ yyyymmddhhmm.xml | Configuration data file that stores choices made each time the configuration is saved |
crnlocale.xml | coglocale.xml | Configuration data file that stores codes for global configuration settings |
crnlocale_ yyyymmddhhmm.xml | coglocale_ yyyymmddhhmm.xml | Configuration data file that stores choices made each time global configuration settings are saved |
crnformat.xml | cogformat.xml | Configuration data file that stores formats for numeric data, dates, and times |
crnserver.log | cogserver.log | Default logging file |
crconfigw.exe | cogconfigw.exe | File to start Cognos Configuration on Windows |
crconfig.bat | cogconfig.bat | File to start Cognos Configuration in silent mode on Windows |
crconfig.sh | cogconfig.sh | File to start Cognos Configuration on UNIX and Linux |
crconfig.prefs | cogconfig.prefs | Configuration data file that stores user preferences for Cognos Configuration |
crconfig_ response.csv | cogconfig_ response.csv | Silent mode log file that stores activities performed while Cognos Configuration runs in silent mode |
xstartup | issetup | Command to start the installation wizard on XWindows |
xwsetup | issetupcc | Command to start the installation wizard on UNIX and Linux |
xwsetup.exe | issetup.exe | File to start the installation wizard on Windows |
ReportNetService_ languagecode.xml | CognosService_ languagecode.xml | Sample file for medium or large configuration |
You can install and upgrade to Cognos 8 in the same directory as ReportNet or in a different directory.
If you want to upgrade Cognos 8 in the same directory, you must first back up your data, ensure that Framework Manager projects are not checked into a source control system, and uninstall ReportNet. For complete instructions, see the steps to install in the same directory.
If you want to install Cognos 8 in a new directory, you can keep ReportNet active until you are satisfied with the operation of the new version. If you are installing on a new computer, see the steps to install in a new directory.
When you back up the configuration data, you store it in a secure directory. The directory must be protected from unauthorized or inappropriate access.
An alternative method of upgrading is to export the entire content store to a deployment archive in ReportNet and then import the deployment archive into Cognos 8. For more information about deployment, see the Administration and Security Guide. A deployment upgrade is required if you want to change the type of database that you use for the content store. If you use the deployment upgrade method, only the steps for exporting and restoring the configuration data are different. All other steps are the same as documented in this section.
Cognos 8 installs and uses Tomcat as its application server by default. If you upgrade from ReportNet and you do not want to use Tomcat, you must follow a different set of steps to upgrade. For more information, see Upgrade to Cognos 8 in an Application Server Environment.
When you upgrade from ReportNet 1.1 to Cognos 8, the report administrator will no longer have access to the Content Administration tool. The report administrator will not be able to create deployment definitions in Cognos 8.
If you manually edited any configuration files, the changes will be overwritten during the upgrade. You must reapply the changes in the Cognos 8 environment. You should keep a record of any customizations to ensure that they can be reapplied after upgrading. You should also back up these files so that the original version can be restored if necessary.
You may have modified files other than those in the configuration folder. If so, you should also back up the additional files before upgrading.
The Cognos 8 presentation service supports automatic upgrade of some ReportNet system.xml files. If you made many customization changes to system.xml files in ReportNet, you can use this automatic upgrade feature instead of reapplying the changes manually after upgrading. The system.xml files are overwritten during the installation of Cognos 8. Therefore, you must back up the ReportNet versions of these files and then copy them to the directory after installing Cognos 8. The automatic upgrade will be applied when you start the Cognos 8 service.
The system.xml files for which automatic upgrade is supported are in the following directories:
crn_location/templates/ps
crn_location/templates/ps/portal
crn_location/templates/ps/qs
Note: The recommended method to upgrade customized files is to manually reapply changes after the new software is installed. Automatic upgrade of system.xml files is to be used only when you have made a large number of customizations to these files.
Using your database tools, back up your existing content store database.
For information on how to do this, see the documentation for your database.
Back up the following files to a secure location:
crnlocale.xml in the crn_location/configuration directory
server.xml in the crn_location/tomcat4.1.27/conf directory
system.xml in the appropriate directory, if required
Ensure that you note the directory path. For example,
crn_location/templates/ps
In Cognos Configuration, export the configuration data to the same secure location.
To make the data usable for upgrading, name the file crnstartup.xml.
Important: Because the exported crnstartup.xml file contains unencrypted passwords, ensure that the location is secure.
Back up any manually edited files in the crn_location/configuration and other directories to a secure location.
Stop all Cognos services.
If you use a source control system such as CVS, ensure that all Framework Manager projects you want upgraded are checked out before uninstalling ReportNet.
Any projects that are checked in when you uninstall will not be upgraded.
Prepare Transformer models, if required .
Upgrade or install third-party products .
Uninstall ReportNet from every ReportNet computer.
For instructions, see the documentation for the older version of ReportNet.
Install Cognos 8 in the same directory that you used for
ReportNet on every computer .
Copy the .xml files from the secure backup location as follows:
Copy crnstartup.xml and crnlocale.xml to crn_location/configuration.
Copy server.xml to crn_location/tomcat4.1.27/conf.
Copy system.xml to the appropriate directory, if required.
For example,
crn_location/templates/ps
If you are prompted to overwrite existing files, click Yes.
For files that you manually edited in ReportNet, edit the same files in the crn_location directory and reapply the changes that you made to the original customized files.
Do not copy the customized files to the crn_location directories. The earlier versions of these files may not be compatible with Cognos 8.
If you use Oracle for a data source, import source, logging database, or the content store database, delete the classes12.jar file from the c8_location\webapps\p2pd\WEB-INF\lib directory.
Older versions of Cognos 8 used this file, which conflicts with the ojdbc14.jar file that is used in newer versions.
In Cognos Configuration, review the configuration, and then save it.
When you save the configuration, an upgrade dialog appears and asks if you want to upgrade your report specifications. The default setting is to not upgrade report specifications.
Important: Do not upgrade your report specifications if you have SDK applications that create, modify, or save report specifications. You must first update your SDK applications to comply with the Cognos 8 report specifications schema. Otherwise, your SDK applications may not be able to access the upgraded report specifications. In addition, do not save your reports until the SDK applications have been updated. For information about upgrading report specifications, see the Cognos 8 SDK Developer Guide.
Start Cognos 8.
Cognos 8 automatically upgrades the content store. System.xml files are upgraded, if required, to a Cognos 8 compatible version.
If the ReportNet service continues to run, manually uninstall
the ReportNet service .
Install and
configure Framework Manager.
Upgrade your Framework Manager projects and reports as
required. For instructions, see the Framework Manager User
Guide.
Report Studio users must clear their Web browser cache to get the latest images.
If you use pages created in ReportNet, you may need to reconfigure the following properties:
Title
Open action links going outside a portal
For more information, see the Administration and Security Guide.
If you published Cognos Series 7 PowerCubes in ReportNet,
restructure your virtual directories or change your cookie path .
Install and
configure Transformer, if required.
Upgrade Transformer models and PowerCubes , if
required.
If you use SAP Enterprise Portal, upgrade your master iView.
Old SAP iViews will not work with the new Portal Services producer component. For information, see the topic about deploying Cognos Portlets to SAP Enterprise Portal in the Administration and Security Guide.
Using your database tools, copy your existing content store database into a new content store database.
For information on how to do this, see the documentation for your database.
Back up the following files to a secure location:
crnlocale.xml in the crn_location/configuration directory
server.xml in the crn_location/tomcat4.1.27/conf directory
system.xml in the appropriate directory, if required
Ensure that you note the directory path. For example,
crn_location/templates/ps
In Cognos Configuration, export the configuration data to the same secure location.
To make the data usable for upgrading, name the file crnstartup.xml.
Important: Because the exported crnstartup.xml file contains unencrypted passwords, ensure that the location is secure.
Back up any manually edited files in the crn_location/configuration and other directories to a secure location.
Prepare Transformer models, if required .
Upgrade or install third-party products .
Install Cognos 8 in a new directory .
Copy the .xml files from the secure backup location to the following directory:
Copy crnstartup.xml and crnlocale.xml to c8_location/configuration.
Copy server.xml to c8_location/tomcat4.1.27/conf.
Copy system.xml to the same directory in the new location as it was in the ReportNet location, if required.
For example,
c8_location/templates/ps
If you are prompted to overwrite existing files, click Yes.
For files that you manually edited in ReportNet, edit the same files in the c8_location directory and reapply the changes that you made to the original customized files.
Do not copy the customized files to the c8_location directories. The earlier versions of these files may not be compatible with Cognos 8.
Configure new Web server aliases .
In Cognos Configuration, do the following:
For the new Cognos 8 instance, configure
Cognos 8 to point to the new content store, configure new ports
and URLs, and then save the configuration .
For ReportNet, configure ReportNet to use a new default cookie
path .
Ensure that the port numbers and service name for this installation are different from those used for earlier versions so that there are no conflicts.
Ensure that security authentication settings are not changed. For example, the namespaces must be the same for policies, users, roles, and groups to work correctly.
When you save the configuration, an upgrade dialog appears and asks if you want to upgrade your report specifications. The default setting is to not upgrade report specifications.
Important: Do not upgrade your report specifications if you have SDK applications that create, modify, or save report specifications. You must first update your SDK applications to comply with the Cognos 8 report specifications schema. Otherwise, your SDK applications may not be able to access the upgraded report specifications. In addition, do not save your reports until the SDK applications have been updated. For information about upgrading report specifications, see the Cognos 8 SDK Developer Guide.
Start Cognos 8.
Cognos 8 automatically upgrades the new content store. System.xml files are upgraded, if required, to a Cognos 8 compatible version.
Install and
configure Framework Manager.
Upgrade your Framework Manager projects and reports as
required. For instructions, see the Framework Manager User
Guide.
Report Studio users must clear their Web browser cache to get the latest images.
Open the Administration portal in Cognos 8, and unregister the dispatchers that are used with ReportNet.
When you open the Administration portal in Cognos 8, the portal shows the dispatchers that are registered for both versions.
For more information, see the Administration and Security Guide.
If you use pages created in ReportNet, you may need to reconfigure the following properties:
Title
Open action links going outside a portal
For more information, see the Administration and Security Guide.
If you published Cognos Series 7 PowerCubes in ReportNet,
restructure your virtual directories or change your cookie path .
Install and
configure Transformer, if required.
Upgrade Transformer models and PowerCubes , if
required.
If you use SAP Enterprise Portal, upgrade your master iView.
Old SAP iViews will not work with the new Portal Services producer component. For information, see the topic about deploying Cognos Portlets to SAP Enterprise Portal in the Administration and Security Guide.
When you are ready to uninstall ReportNet, do the following:
Stop ReportNet.
Uninstall ReportNet from all ReportNet computers.
For instructions, see the documentation for the older version of ReportNet.
When you complete the upgrade tasks, Cognos 8 is fully configured except for new properties and features, and scorecarding features.
If you use Chinese, Japanese, or Korean characters, you may notice differences in some characters after upgrading to Cognos 8. For more information, see the Troubleshooting section of the Administration and Security Guide.
If you use a DB2 database for the content store, you can tune the database to take advantage of DB2 features. For more information, see the Architecture and Deployment Guide.
To ensure the security and integrity of Cognos 8, it is important to protect the installation directory from unauthorized or inappropriate access.
You can run a silent configuration to upgrade the configuration from ReportNet to Cognos 8. Before you run the silent configuration, you must ensure that the option to upgrade the report specifications is set correctly. If you installed Cognos 8 in a new directory, you must also change the settings for ports and the Web server alias.
If you want to upgrade the configuration in silent mode, follow the steps in the preceding section and stop at the step to configure Cognos 8:
In the steps to install in the same directory, stop at step 12.
In the steps to install in a new directory, stop at step 8.
When you reach that step, do not start Cognos Configuration. Instead, perform the following steps and then return to the steps in the preceding section.
Edit the crnstartup.xml file in crn_location/configuration or c8_location/configuration and look for the following lines:
<crn:parameter name="doReportSpecUpgrade">
<crn:value xsi:type="xsd:boolean">false</crn:value>
</crn:parameter>
Set the value for the report specification upgrade:
To skip the upgrade of the report specifications, leave the value as false.
To upgrade the report specifications, change the value to true.
Modify other settings as required.
If you installed Cognos 8 in a new directory, see Run ReportNet and Cognos 8 at the Same Time for the settings to modify.
Type the configuration command:
On UNIX or Linux, type
./cogconfig.sh -s
On Windows, type
cogconfig.bat -s
You must install and upgrade to Cognos 8 in a different directory from the earlier version of Metrics Manager. You can keep Metrics Manager active until you are satisfied with the operation of Cognos 8.
If both ReportNet and Metrics Manager are on the same computer and you plan to upgrade to Cognos 8, upgrade ReportNet first, and then Metrics Manager.
Cognos 8 and earlier versions of Metrics Manager use different security models. If you want to upgrade the security information for the earlier version of Metrics Manager, you must follow a different set of steps to upgrade. For more information, see Upgrade Metrics Manager and Security Information.
Cognos 8 installs and uses Tomcat as its application server by default. If you upgrade from Metrics Manager and you do not want to use Tomcat, you must follow a different procedure to upgrade. For more information, see Upgrade from Metrics Manager to Cognos 8 in an Application Server Environment.
Export the contents of any data store that you want to use with Cognos 8 from the earlier version of Metrics Manager.
For more information, see the documentation provided with your earlier version of Metrics Manager.
Install Cognos 8:
If you are upgrading only Metrics Manager,
install Cognos 8 in a different directory from the earlier version
of Metrics Manager .
If ReportNet is on the same computer as Metrics Manager, follow
the steps to upgrade ReportNet to Cognos 8 .
Set up the environment .
If you exported the contents of one or more data stores in step
1, create one metric store database for the contents of each data store. For each
metric store, set up the database client and environment variables on UNIX .
Create a metric package .
If you exported content from data stores in step 1, import the contents of each data store into a different metric store.
For information about importing data, see the Metric Studio User Guide for Authors.
Install and
configure Metric
Designer on Windows.
Upgrade Metric Designer projects and extracts as required.
When you are ready, stop the earlier version of Metrics Manager and uninstall it as described in the documentation provided with it.
To ensure the security and integrity of Cognos 8, protect the installation directory from unauthorized or inappropriate access.
Cognos 8 and earlier versions of Metrics Manager use different security models. Before upgrading to Cognos 8, review the information about Cognos 8 security to determine if it meets your requirements. For information, see the Administration and Security Guide.
If the Cognos 8 security model does not meet your requirements and you must upgrade your existing security information, an upgrade utility is available. You use this utility during the upgrade process to map the security permissions for scorecards and metrics in the earlier version to corresponding permissions in Cognos 8.
The upgrade utility does not map the Deny permission if it was used in the earlier version of Metrics Manager. For example, assume a user belongs to two user classes. For the same scorecard, one user class has Read permission and the other user class has Deny permission. After the upgrade utility is run, the user will have only Read permission for the scorecard.
The upgrade utility maps security information for one data store using the information in a control file that you create. This file is a text file. If you plan to upgrade the content of more than one data store, you must create a control file for each data store and run the upgrade utility for each control file.
The following table describes the properties that must be defined in the control file. An example of a control file is provided below the table.
Property | Description |
scorecard_file | A comma delimited list of object_stage (.cmo) files that contain the scorecards from the earlier version of Metrics Manager. The list must include all of the scorecards that you want to import into the Cognos 8 metric store. Only scorecards are imported; other objects in these files are ignored. |
policy_file | A comma delimited list of source object_link_stage (.cml) files from the earlier version of Metrics Manager that contain the policies to be upgraded. The list of files must contain all of the policy links that you want to import into the Cognos 8 metric store. Only policy links are imported; other objects in these files are ignored. |
input_file_encoding | The character set of the input files. This property is optional. By default, the default character set of the platform is used. |
flat_file_version | The version of the flat file from the earlier version of Metrics Manager. The value may be 2.0 or 2.2. This property is optional. The default value is 2.2. |
output_file | The name of the file where the generated Cognos 8 policies will be written. This property is optional. The default output file name is policies.cms. |
output_file_encoding | The desired character set of the output file. This property is optional. By default, the default character set of the platform is used. |
read_mapping | A comma delimited list of Cognos 8 permissions to grant for the read permission level set in the earlier version of Metrics Manager. One of the following suffixes may be added to specify the permissions for a specific object type: .metric or .scorecard. |
write_mapping | A comma delimited list of Cognos 8 permissions to grant for the write permission level set in the earlier version of Metrics Manager One of the following suffixes may be added to specify the permissions for a specific object type: .metric or .scorecard. |
administrator_mapping | A comma delimited list of Cognos 8 permissions to grant for the administer permission level set in the earlier version of Metrics Manager. The permissions include:
One of the following suffixes may be added to specify the permissions for a specific object type: .metric or .scorecard. |
The following shows an example control file:
scorecard_file=c:\\cmm_exports\\export_scorecards.cmo
policy_file=c:\\cmm_exports\\export_permissions.cml
flat_file_version=2.2
output_file=new_policies.cms
read_mapping=read,readannotations
write_mapping=read,readannotations,annotate,writeProject
administrator_mapping=read,readannotations,annotate,writeProject,write, writeactual,writetarget,writetolerance,writeudc
Export the contents of the data store from the earlier version of Metrics Manager with the exception of users.
For more information, see the documentation provided with the earlier version of Metrics Manager.
Install Cognos 8:
If you are upgrading only Metrics Manager,
install Cognos 8 in a different directory from the earlier version
of Metrics Manager .
If ReportNet is on the same computer as Metrics Manager, follow
the steps to upgrade ReportNet to Cognos 8 .
Set up the environment .
Ensure that you create a metric store database and set
up the metric store database client and environment variables on UNIX .
Also, ensure that the Series 7 namespace is configured and available in the Cognos 8 environment.
Create a control file that references the object stage (.cmo) files, containing the scorecard definitions, and the object link stage (.cml) files, containing the permission definitions generated in step 1.
The control file is a text file. See the table and example above to help you create your control file.
In the c8_location\bin directory, type the following command from a command prompt:
cmm_migrate_policies control_file_name
Create a metric package .
Import the data store export you created in step 1 into the metric store.
You do not have to import the object link stage (.cml) files containing the permission definitions. In the example above, the file containing the permission definition is export_permission.cml.
For more information about importing, see the Metric Studio User Guide for Authors.
Import the contents of the output file generated using the cmm_migrate_policy command.
The output file is named new_policies.cms in the example above.
Ensure that you specify the import source file format to be 8.1.2MR2.
Install and
configure Metric
Designer on Windows.
Upgrade Metric Designer projects and extracts as required.
When you are ready, stop the earlier version of Metrics Manager and uninstall it as described in the documentation provided with it.
To ensure the security and integrity of Cognos 8, protect the installation directory from unauthorized or inappropriate access.
If you want to upgrade a Metrics Manager 2.2 calendar that uses a customized period start date and end date, you must create a standard calendar in Cognos 8 that reflects your custom calendar as closely as possible. You must then export the standard calendar and modify the import time periods file (.cal), import time levels file (.lvl), and time language text file (.tlt) so that the calendar equals your Metrics Manager 2.2 calendar.
When you upgrade Cognos 8, you may need to upgrade to new versions of third-party products, update some components of third-party products, or install additional third-party products to support new features in Cognos 8.
To view a list of third-party products that are used by Cognos 8, see Verify System Requirements.
To review an up-to-date list of environments supported by Cognos products, such as operating systems, patches, browsers, Web servers, directory servers, database servers, and application servers, visit the Cognos Global Customer Services Web site (http://support.cognos.com).
If you do not have the supported version of a required third-party product, install or upgrade the product.
Instructions are provided in this guide for some of the required third-party products:
setting up a database client
updating the Java environment
configuring a Web server
configuring a Web browser
changing the type of Java Virtual Machine (JVM) used in Cognos
8
changing the version of Java Runtime Environment used in Cognos
8
For instructions to install or upgrade other third-party products, see the instructions provided with each product.
You must change the ports and the Web server alias in Cognos 8 if you want to run Cognos 8 and ReportNet, or two versions of Cognos 8, on the same computer and at the same time.
In ReportNet, there is no default cookie path, which means the cookie is sent to all URLs on the Web server. If Cognos 8 uses the same Web server, Cognos 8 will then receive two cam_passport cookies. To prevent this conflict, you must set a cookie path in ReportNet.
Other configuration changes may be required depending on your environment. If you use Portal Services, you must specify the location of the applications.xml file. If you use an ISAPI gateway on an IIS 6.0 Web server, you must isolate the Cognos 8 gateway to prevent a conflict with the ReportNet gateway. You isolate the gateway by setting the application protection for the Web site and virtual directories to High.
In Cognos 8, start Cognos Configuration.
In the Explorer window, click Environment.
In the Properties window, under Dispatcher Settings, click the value for Internal dispatcher URI.
Select the port number and then type the new port number.
If required, change the port number for the following URIs to match the new port number that you entered for Internal dispatcher URI.
Under Dispatcher Settings, change the port for External dispatcher URI.
Under Other URI Settings, change the port for Dispatcher URI for external applications and Content Manager URIs.
Content Manager URIs does not appear on a gateway computer.
Under Gateway Settings, click the value for Gateway URI and ensure that the URI contains the correct Web server alias for Cognos 8.
For example, replace crn with cognos8.
If you are using Portal Services, update the applications.xml file:
In the Explorer window, click Environment, Portal Services.
In the Properties window, ensure that the port number for Location of Applications.xml matches the port for the other URI properties.
In the Explorer window, click Data Access, Content Manager, Content Store.
In the Properties window, configure Cognos 8 to use the new content store:
For Database name, specify the name of the new content store.
For User ID and password, click the edit button and specify the userid and password to access the new content store.
If you are running two instances of Cognos 8, change the cookie path for the new version of Cognos 8:
From the Actions menu, click Edit Global Configuration.
In the Global Configuration window, click Cookie Settings.
Go to a different path from the one that is used by the older version of Cognos 8.
Click OK.
Save the configuration and start Cognos 8.
If you use an ISAPI gateway on an IIS 6.0 Web server, change the application protection setting:
In IIS Manager, right-click the default Web site and then click Properties.
Click the Home Directory tab.
In the Application Protection box, click High and then click OK.
Repeat the above three bulleted steps for each of the virtual directories for Cognos 8, clicking the Virtual Directory tab instead of the Home Directory tab.
The next time the Cognos 8 gateway is requested, it will run in a separate memory space.
In ReportNet, start Cognos Configuration.
Change the cookie path:
From the Actions menu, click Edit Global Configuration.
In the Global Configuration window, click Cookie Settings.
Set the path to the installation directory (for example, /crn).
Click OK.
Save the configuration.
You can now run ReportNet and Cognos 8, or two instances of Cognos 8, at the same time.
Note: When you change from the default ports on Windows, the port number is automatically appended to the service name. The service name in Cognos Configuration does not show the port number. You can view the service name and port number under Services in your Windows administrative tools.
If the ReportNet service continues to run after you uninstalled ReportNet and then installed Cognos 8, you must manually uninstall the ReportNet service.
You can install more than one version of Cognos 8 in different locations on the same computer. If the versions use the same ports, the installation may not upgrade the service correctly. Cognos Configuration upgrades to the most recently configured service for Cognos 8.
Tip: To see if the correct Cognos 8 service is running, check the version number in the About window in Cognos Configuration.
Start Cognos Configuration.
Right-click the service node Cognos 8 (or other name that has been given to the service) in the Explorer panel and select Stop.
Open a Command Prompt window.
Go to the c8_location/bin directory.
Uninstall the service:
If you used the default name for the service, type cogbootstrapservice -u
If you specified another name, type cogbootstrapservice -u -name="c8_service_name"
Close the Command Prompt window.
Restart Cognos Configuration.
Cognos 8 upgrades to the correct service.
After you upgrade from Cognos ReportNet to Cognos 8, you may not be able to publish cubes from PowerPlay Enterprise Server to Cognos Connection. Similarly, if a user opens a cube from Cognos Connection that was published from PowerPlay Enterprise Server, they may receive the following error when they save the report to Cognos Connection:
Your session ticket is invalid. It may have expired.
To enable publishing of Series 7 PowerCubes after upgrading, you can either restructure your virtual directories so that the Series 7 and Cognos 8 gateways are within the same structure or change the default cookie path in Cognos 8 to the value specified below. If you use the specified cookie path value, you cannot run ReportNet and Cognos 8 on the same computer.
Create a virtual directory structure where both the PowerPlay Enterprise Server Series 7 gateway and the Cognos 8 gateway are within the same structure. For example, set up your virtual directories as follows:
Create an alias called cognos8 that points to the c8_location\webcontent directory.
Create an alias called cognos8/cgi-bin that points to the c8_location\cgi-bin directory.
Create an alias called cognos8/series7 that points to the series7_location\webcontent directory.
Create an alias called cognos8/series7/cgi-bin that points to the series7_location\cgi-bin directory.
Create an alias called cognos8/series7/help that points to the series7_location\Documentation directory.
Start Cognos Configuration.
Click Actions, Edit Global Configuration, and click the General tab.
In the Path box under Cookie Setting, type
/
Click OK.
Save the configuration.
Note: If you change the cookie path to the specified value, you cannot run ReportNet and Cognos 8 on the same computer. If you intend to run ReportNet and Cognos 8 on the same computer, correct this problem by changing your virtual directories as described above.
