Upgrading the 8.x or 9.x model and installing new reports
Upgrading the 8.x or 9.x model and installing the new reports are the first steps that you must complete to upgrade your reports.
About this task
Procedure
- Browse to the Unica\ProductNameReportsPack\CognosN directory, where N is the version of your Cognos® installation.
-
Copy the reports archive .zip file, such as Unica Reports for
Campaign.zip, to the directory where your Cognos
deployment archives are saved.
The default location is the deployment directory under your IBM® Cognos installation. The directory is specified in the Cognos Configuration tool that is installed with the Cognos Content Manager, for example: cognos\deployment.
In a distributed IBM Cognos environment, the directory is a located on the system that runs the Content Manager.
- Copy the pre-upgrade version of the Campaign model to a directory on the server where your Framework Manager is installed. If the Reports Pack installation directory and Framework Manager are on different servers, locate the upgraded cognos10\model directory under the Reports Pack installation directory. Then, copy the appropriate upgrade.xml files to the directory on the server where Framework Manager is installed. Also, copy the translation folder of upgraded model in the old model that is copied to the directory on the server where Framework Manager is installed. If prompted for replacement, click Yes.
- If the Reports Pack installation directory and Framework Manager are on different servers, locate the cognos10\model directory under the Reports Pack installation directory. Then, copy the appropriate upgrade.xml files to the server where your Framework Manager is installed.
- Copy the translation folder of the upgraded Campaign model in the old model that you copied to a directory on a server where your Framework Manager is installed. If you see a prompt for replacement, click Yes.
-
If you did not install your HCL
EMM product
to the default C:\Unica directory on Windows™, you must update the upgrade scripts.
In each script, edit the file paths that point to directories where the localized language versions of the models are stored to reflect your product installation location. Modify the file path in each script for every language that your users need, for example:
install_directory\ReportsPackCampaign\cognosN\CampaignModel\translations\L\translations.txt
The N in the path refers to the Cognos version number.
The L in the path refers to one of the following language indicators:- fr
- de
- es
- it
- ja
- ko
- pt
- ru
- zh
- zh-tw
Edit the following upgrade scripts:
Campaignupgrade80to81.xml
upgrade81to85.xml
upgrade85to86.xml
upgrade86to90.xml
upgrade90to91.xml
upgrade91to911.xml
upgrade911to9112.xml
eMessageupgrade86to90.xml
upgrade8604to91.xml
upgrade90to91.xml
upgrade91to911.xml
upgrade9102to911.xml
(To upgrade from version 9.1.0.x.0.0 (x >= 2) and if you have not applied 9.1.0.2 Reports Feature Pack 1)upgrade910201to911.xml
(To upgrade from version 9.1.0.x.0.1 (x >= 2) and if you have applied 9.1.0.2 Reports Feature Pack 1)
Interactupgrade80to81.xml
upgrade81to85.xml
upgrade85to86.xml
upgrade86to90.xml
upgrade90to91.xml
upgrade91to911.xml
upgrade911to9112.xml
Leadsupgrade81to85.xml
upgrade86to90.xml
upgrade90to91.xml
upgrade91to911.xml
Campaign with Marketing Operationsupgrade80to81.xml
upgrade82to85.xml
upgrade86to90.xml
upgrade90to91.xml
upgrade91to911.xml
upgrade911to9112.xml
Marketing Operationsupgrade75to80.xml
upgrade80to81.xml
upgrade81to82.xml
upgrade82to85.xml
upgrade85to86.xml
upgrade86to90_DB2.xml
(for DB2® database only)upgrade86to90_Oracle.xml
(for Oracle database only)upgrade86to90_Sqlserver.xml
(for SQL Server database only)upgrade90to91.xml
upgrade91to911.xml
upgrade911to9112.xml
Distributed Marketingupgrade86to90.xml
upgrade911to9112.xml
- Open Cognos Connection.
- Select Administer Cognos Content > Configuration > Content Administration.
- Click the New Import button on the toolbar and import the reports folder.
- Open Cognos Framework Manager and open the project for the version from which you are upgrading.
- Select Project > Run Script.
- Run the following scripts from the new version of your
product:Note: You must consider the following points for the 8.x or 9.x version from which you are upgrading:
- You do not have to run the scripts that refer to earlier versions. For example, if you are upgrading Campaign reports from version 8.5.0, you do not need to run the upgrade80to81.xml and upgrade81to85.xml scripts.
- You must run the preUpgrade_86_fromanyversion.xml script for upgrades from all versions except 8.6.
- You cannot upgrade reports from any source version to a destination version. For example, to upgrade reports from version 9.0.0 to version 9.1.1, you must first upgrade from version 9.0.0 to version 9.1, and then upgrade from version 9.1 to version 9.1.1.
- Only for eMessage reports, you must upgrade from version 8.6.0.4 or later to 9.1 directly.
CampaignpreUpgrade_86_fromanyversion.xml
upgrade80to81.xml
upgrade81to85.xml
upgrade85to86.xml
upgrade86to90.xml
upgrade90to91.xml
upgrade91to911.xml
upgrade911to9112.xml
eMessageupgrade86to90.xml
upgrade8604to91.xml
upgrade90to91.xml
upgrade91to911.xml
upgrade9102to911.xml
(To upgrade from version 9.1.0.x.0.0 (x >= 2) and if you did not apply Reports 9.1.0 Feature Pack 1)upgrade910201to911.xml
(To upgrade from version 9.1.0.x.0.1 (x >= 2) and if you did apply Reports 9.1.0 Feature Pack 1)
InteractpreUpgrade_86_fromanyversion.xml
upgrade80to81.xml
upgrade81to85.xml
upgrade85to86.xml
upgrade86to90.xml
upgrade90to91.xml
upgrade91to911.xml
upgrade911to9112.xml
Leadsupgrade81to85.xml
upgrade86to90.xml
upgrade90to91.xml
upgrade91to911.xml
Campaign with Marketing Operationsupgrade80to81.xml
upgrade81to82.xml
upgrade82to85.xml
upgrade86to90.xml
upgrade90to91.xml
upgrade91to911.xml
upgrade911to9112.xml
Marketing Operationsupgrade75to80.xml
upgrade80to81.xml
upgrade81to82.xml
upgrade82to85.xml
upgrade85to86.xml
upgrade86to90_DB2.xml
(for DB2 database only)upgrade86to90_Oracle.xml
(for Oracle database only)upgrade86to90_Sqlserver.xml
(for SQL Server database only)upgrade90to91.xml
upgrade91to911.xml
upgrade911to9112.xml
Distributed Marketingupgrade86to90.xml
upgrade911to9112.xml
All the scripts are in the ProductNameReportsPack\cognosN\ProductNameModel directory under your HCL EMM product installation, where N is the Cognos version number.
- If you are upgrading eMessage reports, complete the following
steps:Note: If your database is DB2, change the statement termination character from ; (semicolon) to ! (exclamation point).
- Go to Campaign_ReportPack_Installer_Home\Cognos10\ emessage-ddl\DB Type\Upgrade.
- Run the following scripts in the sequence shown:
- If you are upgrading from eMessage 8.6.0.4 or later to eMessage
9.1:
acer_tables_upgrade_
dbname
.sql. Search for the base version name and run the following script:--8.6.0.4 Updates--
- If you are upgrading from eMessage 9.0 or later to eMessage 9.1:
acer_tables_upgrade_
dbname
.sql. Search for the base version name and run the following script:--9.0.x Updates--
acer_indexes_upgrade_
dbname
.sql. Search for the base version name and run the following script:--9.0.x Updates--
- If you are upgrading from eMessage 9.1.0.x.0.0 (x >= 0) to eMessage
9.1.1:
acer_tables_upgrade_
dbname
.sql. Search for the base version name and run the following script:--9.1.0.x updates (Not applicable for 9.1.0 Feature Pack 1 upgrade)--
Note: If you applied 9.1.0 Feature Pack 1, you do not need to run table or index upgrade scripts. - If you are upgrading from eMessage 8.6.0.4 or later to eMessage
9.1:
- Go to Campaign_ReportPack_Installer_Home\Cognos10\emessage-ddl\DB Type and
run the following script:
acer_scripts_
dbname
.sqlNote: You must run the acer_scripts_dbname
.sql script for a both a fresh installation and an upgrade of reports.Note: If you are using Microsoft™ SQL Server, you must drop the 8.6.0.4 version's procedures before you complete this step. -
Use
Run SQL Generator
to generate report view scripts. For Microsoft SQL Server, generate views. For Oracle and IBM DB2, create materialized views. - Run and schedule the stored procedures.Note: To ensure proper report performance, you must schedule the stored procedures to run regularly. For more information about eMessage stored procedures, see Running and scheduling stored procedures for eMessage.
- Publish the package to the Cognos content store.
- For all HCL
EMM products,
complete the following steps:
- Go to File > Report Package.
- Select the appropriate reports package according to your product and click OK.
- Complete prompts on the report as necessary.
- After the report is validated, click Close in the Validation Response window.
- Run a report to test your upgrade.