See IBM Enterprise Marketing Management Products Recommended Software Environments and Minimum System Requirements.
|
||
Understanding prerequisites for eMessage.
|
||
Configure a user with access to the Settings > Configuration and Settings > Report SQL Generator pages so you can log in as this user when you need to configure the reporting properties and generate the SQL used to create reporting schema.
|
||
Installing the reporting schemas on the machine where the Marketing Platform is installed.
|
Place the IBM® master installer and the report pack installers in the same directory and launch the master installer.
|
|
In the application server where the Marketing Platform is deployed, create JDBC data source connections to the system table databases for the products you want to use for reporting.
|
||
Obtaining the JDBC driver used for the Marketing Platform system tables.
|
Copy the JDBC driver used for Marketing Platform to the machine where the Cognos® Content Manager is installed. When IBM® authentication is implemented, Cognos® uses this when it obtains user information.
|
|
Place the IBM® EMM master installer, Marketing Platform installer, and product report pack installers in the same directory on the machine where the Cognos® Content Manager is installed, and launch the master installer.
|
||
The Cognos® applications need to connect to the IBM® EMM application data sources for the reports. Use the Administration section of Cognos® Connection to create these data sources.
|
||
For eMessage, running scripts to create staging tables, indexes, and stored procedures.
|
||
To implement reporting for Campaign, eMessage, and Interact, you create reporting views or tables from which the reports extract reportable data. The reports packs contain templates that the Reports SQL Generator uses when generating SQL scripts for creating these views or tables. In this step, you load these templates into the Marketing Platform system table database.
|
||
If the data source login you used when you created the Cognos® data sources is not the owner of the IBM® EMM system tables, perform this step.
|
||
The IBM® EMM reports have standard links. To enable them, you must configure the redirect URL in the Cognos® data model.
|
||
This step varies, depending on whether you used the default data source names in Cognos® Connection, as described in that step.
|
||
To give users permission to run reports from within IBM® EMM applications, assign the default ReportsUser role to the appropriate user groups or users.
|
||
For eMessage, running and scheduling stored procedures.
|
eMessage reports use data that is contained in staging tables, which are populated by stored procedures that perform a delta refresh operation. The scheduling of the procedures depends on your database. Scheduling the procedures must be done by a database administrator who is familiar with your IBM® Campaign and eMessage environments and with your business requirements.
|
|
The IBM® EMM Authentication Provider enables the Cognos® applications to use IBM® EMM authentication to communicate with the Marketing Platform as if it were another application in the suite. This step has several sub-steps.
|
||
At this point, reporting is working properly and the example reports are in their default state. You may need to customize the reports or reporting schemas for Campaign, Interact, or Marketing Operations.
|
Copyright IBM Corporation 2014. All Rights Reserved.
|