IBM Marketing Platform: Upgrade Guide

IBM Marketing PlatformVersion 9 Release 1October 25, 2013

Upgrade Guide

��

NoteBefore using this information and the product it supports, read the information in “Notices” on page 85.

This edition applies to version 9, release 1, modification 0 of IBM Marketing Platform and to all subsequent releasesand modifications until otherwise indicated in new editions.

© Copyright IBM Corporation 1999, 2013.US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contractwith IBM Corp.

Contents

Chapter 1. Upgrade overview . . . . . 1Upgrade roadmap . . . . . . . . . . . . 1How the installers work . . . . . . . . . . 2Modes of installation . . . . . . . . . . . 3

Sample response files . . . . . . . . . . 4Marketing Platform documentation and help . . . 4

Chapter 2. Planning the MarketingPlatform upgrade. . . . . . . . . . . 7Prerequisites . . . . . . . . . . . . . . 7Marketing Platform installation worksheet . . . . 8Upgrade prerequisites for all IBM EMM products . 10

Auto commit requirement for Oracle or DB2 . . 11Change in names of user-defined groups androles . . . . . . . . . . . . . . . . 11

Time zone support for scheduler . . . . . . . 11IBM Digital Analytics dashboard portlets . . . 11

Backing up the corporatetheme.css file and brandingimages . . . . . . . . . . . . . . . . 12Marketing Platform upgrade scenarios . . . . . 12

Chapter 3. Upgrading from version 8.xwith automatic migration . . . . . . . 15

Chapter 4. Upgrading from version8.0.x, 8.1.x, or 8.2.x before version8.2.0.7 with manual migration . . . . . 17

Chapter 5. Upgrading from version8.2.0.7 and 8.2.x versions with manualmigration. . . . . . . . . . . . . . 27

Chapter 6. Upgrading from version8.5.x with manual migration. . . . . . 35

Chapter 7. Upgrading from version8.6.x with manual migration. . . . . . 43

Chapter 8. Upgrading from version 9.xwith manual migration . . . . . . . . 49

Chapter 9. Deploying MarketingPlatform . . . . . . . . . . . . . . 55Guidelines for deploying Marketing Platform onWebLogic . . . . . . . . . . . . . . . 55

Guidelines for deploying Marketing Platform onWebSphere . . . . . . . . . . . . . . 56Verifying your Marketing Platform installation . . 57

Chapter 10. Configuring MarketingPlatform after deployment . . . . . . 59Default password settings . . . . . . . . . 59

Chapter 11. IBM Marketing Platformutilities and SQL scripts . . . . . . . 61Setting up Marketing Platform utilities on additionalmachines . . . . . . . . . . . . . . . 62Marketing Platform utilities . . . . . . . . . 63

alertConfigTool . . . . . . . . . . . . 63configTool . . . . . . . . . . . . . . 63datafilteringScriptTool . . . . . . . . . . 68encryptPasswords . . . . . . . . . . . 69partitionTool . . . . . . . . . . . . . 70populateDb . . . . . . . . . . . . . 72restoreAccess . . . . . . . . . . . . . 73scheduler_console_client . . . . . . . . . 74

Chapter 12. Marketing Platform SQLscripts . . . . . . . . . . . . . . . 77ManagerSchema_DeleteAll.sql . . . . . . . . 77ManagerSchema_PurgeDataFiltering.sql . . . . . 77SQL scripts for creating system tables . . . . . 78ManagerSchema_DropAll.sql . . . . . . . . 79

Chapter 13. Uninstalling MarketingPlatform . . . . . . . . . . . . . . 81

Before you contact IBM technicalsupport . . . . . . . . . . . . . . 83

Notices . . . . . . . . . . . . . . 85Trademarks . . . . . . . . . . . . . . 87Privacy Policy and Terms of Use Considerations . . 87

© Copyright IBM Corp. 1999, 2013 iii

iv IBM Marketing Platform: Upgrade Guide

Chapter 1. Upgrade overview

An upgrade of Marketing Platform is complete when you upgrade, configure, anddeploy Marketing Platform. The Marketing Platform Upgrade Guide providesdetailed information about upgrading, configuring, and deploying MarketingPlatform.

Use the Upgrade Roadmap section to obtain a broad understanding about usingthe Marketing Platform Upgrade Guide.

Upgrade roadmapUse the upgradem roadmap to quickly find the information that you need forinstalling Marketing Platform.

You can use Table 1 to scan the tasks that must be completed for installingMarketing Platform:

Table 1. Marketing Platform upgrade roadmap

Topic Information

Chapter 1, “Upgrade overview” This topic provides the followinginformation:

v “How the installers work” on page 2

v “Modes of installation” on page 3

v “Marketing Platform documentation andhelp” on page 4

Chapter 2, “Planning the Marketing Platformupgrade,” on page 7

This topic provides the followinginformation:

v “Prerequisites” on page 7

v “Marketing Platform installationworksheet” on page 8

v “Upgrade prerequisites for all IBM EMMproducts” on page 10

v “Time zone support for scheduler” onpage 11

v “Backing up the corporatetheme.css fileand branding images” on page 12

v “Marketing Platform upgrade scenarios”on page 12

Chapter 3, “Upgrading from version 8.x withautomatic migration,” on page 15

Read more about how to upgrade MarketingPlatform from version 8.x with automaticmigration.

Chapter 4, “Upgrading from version 8.0.x,8.1.x, or 8.2.x before version 8.2.0.7 withmanual migration,” on page 17

Read more about how to upgrade MarketingPlatform from version 8.0.x, 8.1.x, or 8.2.xversions before 8.2.0.7 with manualmigration.

Chapter 5, “Upgrading from version 8.2.0.7and 8.2.x versions with manual migration,”on page 27

Read more about how to upgrade MarketingPlatform from version 8.0.x, 8.1.x, or 8.2.xversions before 8.2.0.7 with manualmigration.

© Copyright IBM Corp. 1999, 2013 1

Table 1. Marketing Platform upgrade roadmap (continued)

Topic Information

Chapter 6, “Upgrading from version 8.5.xwith manual migration,” on page 35

Read more about how to upgrade MarketingPlatform from version 8.5.x with manualmigration.

Chapter 7, “Upgrading from version 8.6.xwith manual migration,” on page 43

Read more about how to upgrade MarketingPlatform from version 8.6.x with manualmigration.

Chapter 8, “Upgrading from version 9.x withmanual migration,” on page 49

Read more about how to upgrade MarketingPlatform from version 9.x with manualmigration.

Chapter 9, “Deploying Marketing Platform,”on page 55


v “Guidelines for deploying MarketingPlatform on WebLogic” on page 55

v “Guidelines for deploying MarketingPlatform on WebSphere” on page 56

v “Verifying your Marketing Platforminstallation” on page 57

Chapter 10, “Configuring MarketingPlatform after deployment,” on page 59


v “Default password settings” on page 59

Chapter 11, “IBM Marketing Platformutilities and SQL scripts,” on page 61


v “Setting up Marketing Platform utilitieson additional machines” on page 62

v “alertConfigTool” on page 63

v “configTool” on page 63

v “datafilteringScriptTool” on page 68

v “encryptPasswords” on page 69

v “partitionTool” on page 70

v “populateDb” on page 72

v “restoreAccess” on page 73

v “scheduler_console_client” on page 74

Chapter 12, “Marketing Platform SQLscripts,” on page 77


v “ManagerSchema_DeleteAll.sql” on page77

v “ManagerSchema_PurgeDataFiltering.sql”on page 77

v “SQL scripts for creating system tables”on page 78

v “ManagerSchema_DropAll.sql” on page79.

Chapter 13, “Uninstalling MarketingPlatform,” on page 81

This topic provides information about howto uninstall Marketing Platform.

How the installers workUse the IBM® EMM installer with the Marketing Platform installer when youinstall Marketing Platform.

2 IBM Marketing Platform: Upgrade Guide

The IBM EMM suite installer starts the individual product installers during theinstallation process.

Use the following guidelines to install Marketing Platform:v Make sure that the IBM EMM installer and the Marketing Platform installer are

in the same directory on the server where you want to install MarketingPlatform. When multiple versions of the Marketing Platform installer are presentin the directory with the IBM EMM installer, the IBM EMM installer shows thelatest version of Marketing Platform on the IBM EMM Products screen in theinstallation wizard.

v If you are planning to install a patch immediately after you install MarketingPlatform, make sure that the patch installer is in the same directory as that ofthe IBM EMM and the Marketing Platform installer.

IBM EMM is installed in one of the following directories by default:v /IBM/EMM (for UNIX)v C:\IBM\EMM (for Windows)

IBM EMM products are installed by default in a subdirectory of theIBMEMM_Home directory. For example, Marketing Platform is installed in theIBMEMM_Home/Platform directory.

However, you can change the directories during installation.

Modes of installationThe IBM EMM suite installer can run in one of the following modes: GUI mode,console mode, or silent mode (also called the unattended mode). Select a modethat suits your requirements when you install Marketing Platform.

GUI mode

Use the GUI mode for Windows or the X Window System mode for UNIX toinstall Marketing Platform by using the graphical user interface.

Console mode

Use the console mode to install Marketing Platform by using the command-linewindow.

Note: To display the Installer screens correctly in console mode, configure yourterminal software to support UTF-8 character encoding. Other character encoding,such as ANSI, will not render the text correctly, and some information will not bereadable.

Silent mode

Use the silent or unattended mode to install Marketing Platform multiple times.The silent mode uses response files for installation, and does not require user inputduring the installation process.

Chapter 1. Upgrade overview 3

Sample response filesYou must create response files to set up a silent installation of Marketing Platform.You can use sample response files to create your response files. The sampleresponse files are included with the installers in the ResponseFiles compressedarchive.

The following table provides information about sample response files:

Table 2. Description of sample response files

Sample response file Description

installer.properties The sample response file for the IBM EMMmaster installer.

installer_product intials and productversion number.properties

The sample response file for the MarketingPlatform installer.

For example,installer_umpn.n.n.n.properties is theresponse file of the Marketing Platforminstaller, where n.n.n.n is the versionnumber.

installer_report pack initials, productinitials, and version number.properties

The sample response file for the reportspack installer.

For example, installer_urpc.properties isthe response file of the Campaign reportspack installer.

Marketing Platform documentation and helpIBM Marketing Platform provides documentation and help for users,administrators, and developers.

Table 3. Get up and running

Task Documentation

View a list of new features, known issues, andworkarounds

IBM Marketing Platform Release Notes

Learn about the structure of the Marketing Platformdatabase

IBM Marketing Platform System Tables

Install or upgrade Marketing Platform and deploy theMarketing Platform web application

One of the following guides:

v IBM Marketing Platform Installation Guide

v IBM Marketing Platform Upgrade Guide

Implement the IBM Cognos® reports provided withMarketing Platform

IBM EMM Reports Installation and Configuration Guide

Table 4. Configure and use Marketing Platform

Task Documentation

v Adjust configuration and security settings

v Prepare Marketing Platform for users

v Run utilities and perform maintenance

IBM Marketing Platform Administrator's Guide


Table 5. Get help

Task Instructions

Open online help 1. Choose Help > Help for this page to open acontext-sensitive help topic.

2. Click the Show Navigation icon in the help windowto display the full help.

Obtain PDFs Use either of the following methods:

v Choose Help > Product Documentation to accessMarketing Platform PDFs and help.

v Choose Help > All IBM EMM Suite Documentationto access all available documentation.

Get support Go to http://www.ibm.com/support to access the IBMSupport Portal.

Chapter 1. Upgrade overview 5


Chapter 2. Planning the Marketing Platform upgrade

You can upgrade your current version of Marketing Platform to bring it up-to-datewith the latest features.

PrerequisitesBefore you install or upgrade any IBM EMM product, you must ensure that yourcomputer complies with all the prerequisite software and hardware.

System requirements

For information about system requirements, see the Recommended SoftwareEnvironments and Minimum System Requirements guide.

Network domain requirements

The IBM EMM products that are installed as a suite must be installed on the samenetwork domain to comply with the browser restrictions that are designed to limitthe security risks that can occur with cross-site scripting.

JVM requirements

IBM EMM applications within a suite must be deployed on a dedicated Java™

virtual machine (JVM). IBM EMM products customize the JVM that is used by theweb application server. If you encounter errors that are related to the JVM, youmust create an Oracle WebLogic or WebSphere® domain that is dedicated to theIBM EMM products.

Knowledge requirements

To install IBM EMM products, you must have a thorough knowledge of theenvironment in which the products are installed. This knowledge includesknowledge about operating systems, databases, and web application servers.

Internet browser settings

Make sure that your internet browser complies with the following settings:v The browser must not cache web pages.v The browser must not block pop-up windows.

Access permissions

Verify that you have the following network permissions to complete theinstallation tasks:v Administration access for all necessary databasesv Read and write access to the relevant directory and subdirectories for the

operating system account that you use to run the web application server andIBM EMM components

v Write permission for all files that you must edit


v Write permission for all directories where you must save a file, such as theinstallation directory and backup directory if you are upgrading

v Appropriate read/write/execute permissions to run the installer

Verify that you have the administrative password for your web application server.

For UNIX, all installer files for IBM products must have full permissions, forexample, rwxr-xr-x.

JAVA_HOME environment variable

If a JAVA_HOME environment variable is defined on the computer where you installan IBM EMM product, verify that the variable points to a supported version ofJRE. For information about system requirements, see the Recommended SoftwareEnvironments and Minimum System Requirements guide.

Make sure that the JAVA_HOME environment variable points to JRE 1.6. If theJAVA_HOME environment variable points to an incorrect JRE, you must clear theJAVA_HOME variable before you run the IBM EMM installers.

You can clear the JAVA_HOME environment variable by using one of the followingmethods:v Windows: In a command window, enter set JAVA_HOME= (leave empty) and

press Enter.v UNIX: In the terminal, enter export JAVA_HOME= (leave empty) and press Enter.

export JAVA_HOME= (leave empty)

After the environment variable is cleared, the IBM EMM installers use the JRE thatis bundled with the installers. You can reset the environment variable after theinstallation is complete.

Marketing Platform installation worksheetUse the Marketing Platform installation worksheet to gather information about theMarketing Platform database and about other IBM EMM products that arerequired for the installation of Marketing Platform.

Use the following table to gather information about the database that contains yourMarketing Platform system tables:

Table 6. Information about the database

Field Notes®

Database type

Database name

Database account user name

Database account password

JNDI name UnicaPlatformDS

ODBC name


Checklist for IBM Marketing Platform database

The installation wizards for each IBM EMM product must be able to communicatewith the Marketing Platform system table database to register the product. Eachtime that you run the installer, you must enter the following database connectioninformation for the Marketing Platform system table database:v Database typev JDBC connection URLv Database host namev Database portv Database name or schema IDv User name and password for the database account

Checklist for IBM Marketing Platform deployment on the webapplication server

Obtain the following information before deploying Marketing Platform:v Protocol: HTTP or HTTPS if SSL is implemented in the web application server.v Host: The name of the machine on which the Marketing Platform will be

deployed.v Port: The port on which the web application server listens.v Domain name: The company domain of each machine where IBM products are

installed. For example, mycompany.com. All IBM products must be installed in thesame company domain, and you must enter the domain name in all lower-caseletters.If there is a mis-match in domain name entries, you may encounter problemswhen you attempt to use Marketing Platform features or navigate amongproducts. You can change the domain name after the products are deployed bylogging in and changing values of the relevant configuration properties in theproduct navigation categories on the Settings > Configuration page.

Checklist for enabling Marketing Platform utilities

If you plan to use the Marketing Platform utilities, obtain the following JDBCconnection information before you start to install the Marketing Platform.v Path to the JRE. The default value is the path to the 1.7 version of the JRE that

the installer places under your IBM installation directory.You can accept this default or specify a different path. If you specify a differentpath, you must point to the 1.7 version of the Sun JRE.

v JDBC driver class. The installer automatically provides this, based on thedatabase type you specifiy in the installer.

v JDBC connection URL. The installer provides the basic syntax, including the hostname, database name, and port. You can customize the URL by addingadditional parameters.

v JDBC driver classpath on your system.

Information about the web component

Obtain the following information for all IBM EMM products that have a webcomponent, which you deploy on a web application server:

Chapter 2. Planning the Marketing Platform upgrade 9

v The name of the systems on which the web application servers are installed. Youcan have one or several web application servers, depending on the IBM EMMenvironment that you are setting up.

v The port on which the application server listens. If you plan to implement SSL,obtain the SSL port.

v The network domain for your deployment system. For example,mycompany.com.

IBM Site ID

If you are installing an IBM EMM product in one of the countries listed on theCountry for Install screen of your product installer, you must enter your IBM SiteID in the space provided. Your IBM Site ID can be found on one of the followingdocuments:v IBM Welcome letterv Tech Support Welcome letterv Proof of Entitlement letterv Other communications that are sent when you purchase your software

IBM might use the data that is provided by the installed software to betterunderstand how customers use our products and to improve customer support.The data that is gathered does not include any information that identifiesindividuals. Complete the following actions if you do not want to have suchinformation to be collected:1. After Marketing Platform is installed, log on to Marketing Platform as a user

with administration privileges.2. Go to Settings > Configuration, and set the Disable Page Tagging property

under the Platform category to True.

Upgrade prerequisites for all IBM EMM productsMeet all requirements for permissions, operating system, and knowledge correctlybefore you upgrade Marketing Platform to ensure a seamless upgrade experience.

Removing response files generated by previous installations

If you are upgrading from a version before 8.6.0, you must delete the response filesthat are generated by previous Marketing Platform installations. Old response filesare not compatible with the 8.6.0 and later installers.

Failure to remove old response files can result in having incorrect data pre-filled ininstaller fields when the installer is run, or in the installer failing to install somefiles or skipping configuration steps.

The IBM response file is named installer.properties.

The response files for each product are namedinstaller_productversion.properties.

The installer creates response files in the directory that you specify duringinstallation. The default location is the home directory of the user.


User account requirement for UNIX

On UNIX, the user account that installed the product must complete the upgrade,otherwise the installer fails to detect a previous installation.

32-bit to 64-bit version upgrades

If you are moving from a 32-bit to a 64-bit version of Marketing Platform, ensurethat you complete the following tasks:v Ensure that the database client libraries for your product data sources are 64-bit.v Ensure that all relevant library paths, for example startup or environment

scripts, correctly reference the 64-bit versions of your database drivers.

Auto commit requirement for Oracle or DB2If your Marketing Platform system tables are in Oracle or DB2®, you must enablethe auto-commit mode for the environment open.

See the Oracle or DB2 documentation for instructions.

Change in names of user-defined groups and rolesYou must upgrade Marketing Platform before you upgrade Campaign. To avoidproblems when you upgrade the Marketing Platform, the names of the groups androles that are created by the user must be different from the names of the groupsor roles that are defined by Marketing Platform.

If the names are same, you must change the group or role names that you createdbefore the upgrade. For example, if you have created a group or role called Admin,you must change the name, because Admin is a name that is used in Campaign.

Time zone support for schedulerIn Marketing Platform you can use the Scheduler to configure a process to run atintervals that you define. With the Scheduler, you can schedule Campaignflowchart runs, Contact Optimization optimization sessions and post-optimizationflowchart runs, eMessage mailings, and PredictiveInsight model and score runs.

In Marketing Platform version 8.5.0, use the Scheduler to select a worldwide timezone for your tasks. If you scheduled tasks in Marketing Platform before version8.5.0, the tasks are set to the default time zone. The default time zone is the timezone of the server where the Marketing Platform is installed.

To take advantage of the time zone support in the Scheduler, edit your scheduledtasks and select the new time zone as required. See the IBM Marketing PlatformAdministrator's Guide for information about using the Scheduler.

IBM Digital Analytics dashboard portletsIf you have any dashboards that contain custom IBM Digital Analytics portlets,you must recreate those portlets after your upgrade is complete.


Backing up the corporatetheme.css file and branding imagesIf you rebranded the IBM frameset as described in the IBM Marketing PlatformAdministrator's Guide, you must back up the files that you modified before youupgrade Marketing Platform. You must restore the files after you complete theupgrade operation, but before you deploy the new version of Marketing Platform.

Typically, the corporatetheme.css file and branding images have to be modified.The corporatetheme.css file and the branding images are located under thecss\theme directory in the unica.war file.

Complete the following steps to back up the corporatetheme.css file and thebranding images:1. Make a backup copy of the unica.war file before you start the upgrade

procedure for Marketing Platform.2. Extract the unica.war file and set aside copies of the corporatetheme.css file

and the branding images.3. Proceed with the upgrade for Marketing Platform, but do not deploy Marketing

Platform.4. Extract the new unica.war file, and overwrite the existing images and the

corporatetheme.css file with your backed-up versions.5. Rewar the new unica.war file, and deploy Marketing Platform.

See the IBM Marketing Platform Administrator's Guide for more details onrebranding.

Marketing Platform upgrade scenariosUpgrade your installation of Marketing Platform after understanding theguidelines that are specific to your current version of Marketing Platform.

Follow the guidelines in the following table for upgrading Marketing Platform.

Table 7. Marketing Platform upgrade scenarios

Marketing Platformsource version Upgrade path

7.x A direct upgrade from version 7.x is not supported. Complete thefollowing steps to upgrade to Marketing Platform version 9.1.0:

1. Upgrade from version 7.x to version 8.6.0. To complete theupgrade to version 8.6.0, obtain the software and follow theinstructions in the installation guide for that version.

2. Complete the upgrade operation as described in one of thefollowing topics.

v Chapter 3, “Upgrading from version 8.x with automaticmigration,” on page 15

v Chapter 7, “Upgrading from version 8.6.x with manualmigration,” on page 43


Table 7. Marketing Platform upgrade scenarios (continued)


8.0.x or 8.1.x,integrated with anLDAP server

If you have mapped LDAP groups in the LDAP references for AMuser creation property that are not mapped in the LDAPreference to AM group map property, you must complete thefollowing steps in your current version of the Marketing Platformbefore proceeding with the upgrade:

1. Identify the groups in the LDAP references for AM usercreation property that are not mapped in the LDAP referenceto AM group map property.

2. Map the LDAP groups that you have identified to anappropriate Marketing Platform group. After you complete anLDAP synchronization, you can map the users to moreMarketing Platform groups to control their application accessas required. For instructions, see the IBM Marketing PlatformAdministrator's Guide.

Completing the previous steps ensures that all the required usersare created in Marketing Platform.

Complete the upgrade operation as described in one of thefollowing topics:


v Chapter 4, “Upgrading from version 8.0.x, 8.1.x, or 8.2.x beforeversion 8.2.0.7 with manual migration,” on page 17

v 8.0.x (not integratedwith an LDAPserver)

v 8.1.x (not integratedwith an LDAPserver)

v 8.2.x before version8.2.0.7

Upgrade your installation of Marketing Platform as described inone of the following topics:


v Chapter 4, “Upgrading from version 8.0.x, 8.1.x, or 8.2.x beforeversion 8.2.0.7 with manual migration,” on page 17

8.2.0.7 and 8.2.x Upgrade your installation of Marketing Platform as described inone of the following topics:


v Chapter 5, “Upgrading from version 8.2.0.7 and 8.2.x versionswith manual migration,” on page 27

8.5.x Upgrade your installation of Marketing Platform as described inone of the following topics:


v Chapter 6, “Upgrading from version 8.5.x with manualmigration,” on page 35

8.6.x Upgrade your installation of Marketing Platform as described inone of the following topics:


v Chapter 7, “Upgrading from version 8.6.x with manualmigration,” on page 43>


Table 7. Marketing Platform upgrade scenarios (continued)


9.x Upgrade your installation of Marketing Platform as described inone of the following topics:


v Chapter 8, “Upgrading from version 9.x with manualmigration,” on page 49>

The Marketing Platform upgrade installer can automatically complete the datamigration that is required for an upgrade. However, if your organization's policydoes not allow automatic data migration, you must complete the procedure toupgrade manually.


Chapter 3. Upgrading from version 8.x with automaticmigration

Automatic migration allows the installer to run the SQL script and insert theconfiguration properties that are required to upgrade your Marketing Platformsystem tables. Automatic migration is quick and error-free. However, if yourcompany policy does not allow automated updates to your system table database,you must use manual migration. Upgrading from version 8.x is an in-placeupgrade. In an in-place upgrade, you install the upgraded version of MarketingPlatform to the directory where your current Marketing Platform is installed.

Ensure that you have the following installers in the same directory:v The IBM EMM master installerv The Marketing Platform installer

You can use the following guidelines as a best practice:v Place the installers in the same directory where you originally placed the

installers for the earlier versions of your products.v Remove any earlier versions of the IBM EMM product installers from the

directory to avoid having the master installer attempt to install the earlierversions.

Complete the following steps to upgrade your installation of Marketing Platform:1. Create a back-up copy of your Marketing Platform system table database.

Important: Do not skip this step. If the upgrade operation fails, you cannot rollback your database and your data is corrupted.

2. Undeploy your Marketing Platform deployment.3. Run the IBM EMM master installer. The IBM EMM master installer starts. Use

the following instructions after theIBM EMM master installer starts:v When the IBM EMM master installer prompts you to choose an installation

directory, choose the root installation directory, not the Marketing Platforminstallation directory, which is under this root directory.

v When the IBM EMM master installer prompts you to enter MarketingPlatform database connection information, enter the information that pertainsto your current Marketing Platform system tables.

The IBM EMM master installer pauses and launches the Marketing Platforminstaller.

4. Complete the following steps while the Marketing Platform installer is running:a. When the Marketing Platform installer prompts you for an installation

directory, select the directory of your current Marketing Platforminstallation, usually named Platform.

b. Select Automatic database setup.c. Follow the remaining steps in the installation wizard and enter the

requested information.5. Deploy your installation.


Note: Pay close attention to the installation summary windows. If errors arereported, check the installer log files and contact IBM EMM technical support ifnecessary.


Chapter 4. Upgrading from version 8.0.x, 8.1.x, or 8.2.x beforeversion 8.2.0.7 with manual migration

The Marketing Platform upgrade installer can perform all of the data migrationthat is required for an upgrade automatically. However, if the policy of yourorganization does not allow automatic migration, you must complete the migrationprocedure to upgrade Marketing Platform manually. To upgrade to MarketingPlatform version 9.1 manually, you must run specific SQL scripts and insert therequired configuration properties.

Ensure that you have the following installers in the same directory:v The IBM master installerv The Marketing Platform installer

Also, ensure that your installation of Marketing Platform 8.x is fully functional andyou can run the command-line tools. Running the command-line tools requires theuse of three Marketing Platform utilities that are in the tools/bin directory underyour Marketing Platform installation. Complete information about using theseutilities, including example commands for common tasks, is available in thefollowing topics:v “populateDb” on page 72v “configTool” on page 63v “alertConfigTool” on page 63

See “Marketing Platform upgrade scenarios” on page 12 for information aboutupgrading from other versions.

Note: When you upgrade from Marketing Platform version 8.2 to MarketingPlatform version 9.1, an error is seen in the logs. You can ignore this error becausethe required column is marked and null. Your installation is successful.

Complete the following steps to upgrade your Marketing Platform installation toversion 9.1:1. Create a back-up copy of your Marketing Platform system table database.

Important: Do not skip this step. If the upgrade operation fails, you cannotroll back your database and your data is corrupted.

2. Undeploy your Marketing Platform deployment.3. Run the IBM EMM master installer. The IBM EMM master installer starts. Use


directory, choose the root installation directory, not the Marketing Platforminstallation directory that is under this root directory.

v When the IBM EMM master installer prompts you to enter MarketingPlatform database connection information, enter the information thatpertains to your current Marketing Platform system tables.

The IBM EMM master installer pauses and starts the Marketing Platforminstaller.


4. Complete the following steps while the Marketing Platform installer isrunning:a. When the Marketing Platform installer prompts you for an installation


b. Allow the installer to create a back-up copy of your previous installationof Marketing Platform.

c. Select Manual database setup.d. Clear the Run Platform configuration check box.e. Follow the remaining steps in the installation wizard and enter the

requested information.5. Use the configTool utility to complete the following steps to ensure that the

SQL scripts that you run in step 7 work correctly:a. Export all your configuration properties from the Affinium root node. For

example, in Windows, use the following command to export the propertiesto the config_property_export.xml file, which is written to the installdirectory under your Marketing Platform installation:configTool.bat -x -p "Affinium" -f "C:\Unica\Platform\install\config_property_export.xml"

b. Delete all configuration properties from the Affinium root node. Forexample, in Windows, use the following command to delete the properties:configTool.bat -d -o -p "Affinium"

c. Import the configuration properties that you exported. For example, inWindows, use the following command to import the properties from theconfig_property_export.xml file, which is in the installation directoryunder your Marketing Platform installation:configTool.bat -i -o -f "C:\Unica\Platform\install\config_property_export.xml"

6. Use one of the scripts in the following table to locate the SQL scripts that areprovided with your new Marketing Platform installation against yourMarketing Platform system table database:

Note: Run the SQL scripts in the order shown.

Table 8. Scripts for upgrading from version 8.0.x

Script Name Location

ManagerSchema_DB_Type_81upg.sql

where DB_Type is the database type of your systemtables database.

db\upgrade80to81



db\upgrade82to8201



db\upgrade82to85

insert_new_85_locales.sql db\upgrade85to86


Table 8. Scripts for upgrading from version 8.0.x (continued)




db\upgrade85to86


active_portlets.sql db



db\upgrade86to90


or

ManagerSchema_DB_Type_91upg_unicode.sql


db\upgrade90to91

Use the scripts from the following table if you are upgrading from version8.1.x or 8.2.0:

Table 9. Scripts for upgrading from version 8.1.x or 8.2.0




db\upgrade82to8201



db\upgrade82to85




db\upgrade85to86




whereDB_Type is the database type of your systemtables database.

db\upgrade86to90


or



db\upgrade90to91

Use the scripts from the following table if you are upgrading from version8.2.0.1 and later patch versions before 8.2.0.7:

Chapter 4. Upgrading from version 8.0.x, 8.1.x, or 8.2.x before version 8.2.0.7 with manual migration 19

Table 10. Scripts for upgrading from version 8.2.0.1 and later patch versions before 8.2.0.7



where DB_Type is the database type of your systemtables database

db\upgrade82to85



where DB_Type is the database type of your systemtables database

db\upgrade85to86





db\upgrade86to90


or



db\upgrade90to91

7. Run one of the following commands:v For Windows:

installation_directory\platform\tools\bin\upgrade90to91.bat

v For Unix:installation_directoryplatform/tools/bin/upgrade90to91.sh

8. Use the populateDb utility to populate the system tables with defaultMarketing Platform configuration properties, users and groups, and securityroles and permissions.The populateDb utility is in the tools/bin directory under your MarketingPlatform installation. Example: populateDb -n Manager

9. Use the configTool utility to import configuration properties as described inthe following table:

Note: The configTool utility is in the tools/bin directory under yourMarketing Platform installation. For complete details on the function of theconfiguration properties, see the online help for the Configuration page, or theIBM Marketing Platform Administrator's Guide

The example commands in the following table are for the Windows operatingsystem.


Table 11. Files for upgrading from version 8.0.x, 8.1.x, or 8.2.x versions before 8.2.0.7

File details Example command

Skip this import if the property named LDAPBaseDN periodic search enabled is presentunder the Platform | Security | Loginmethod details | LDAP synchronizationcategory. This is the property you checked forin step 1 of this procedure.

If the property is not present, perform thefollowing import.

v File: Ldap_Auto_Sync_BaseDN_Settings.xml

v Location: conf\upgrade86to90 directoryunder your Marketing Platform installation

v Purpose: Import a configuration propertythat enables LDAP import search by DN

configTool.bat -i -p"Affinium|suite|security|ldapSynchronization|ldapProperties"-f "C:\Unica\Platform\conf\upgrade86to90\Ldap_Auto_Sync_BaseDN_Settings.xml"

v File: interaction_history_scheduler.xml

v Location: conf/upgrade85to86 directoryunder your Marketing Platform installation

v Purpose: Import the schedulerconfiguration properties required forInteraction History

configTool.bat -i -p"Affinium|suite|scheduler|taskRegistrations" -f"C:\Unica\Platform\conf\upgrade85to86\interaction_history_scheduler.xml"

v File: attribution_modeler_scheduler.xml


v Purpose: Import the schedulerconfiguration properties required forAttribution Modeler

configTool.bat -i -p"Affinium|suite|scheduler|taskRegistrations" -f"C:\Unica\Platform\conf\upgrade85to86\attribution_modeler_scheduler.xml"

v Files: coremetrics_configuration.xml andcoremetrics_navigation.xml

v Location: conf directory under yourMarketing Platform installation

v Purpose: Import the configurationproperties required for single sign-on withIBM Digital Analytics

v configTool.bat -i -p "Affinium" -f "C:\Unica\Platform\conf\coremetrics_configuration.xml"

v configTool.bat -i -p"Affinium|suite|uiNavigation|mainMenu|Analytics" -f"C:\Unica\Platform\conf\coremetrics_navigation.xml"

v File: cognos10_integration.xml


v Purpose: Import the configurationproperties required for reporting

configTool.bat -i -p "Affinium|Report|integrations" -f"C:\Unica\Platform\conf\upgrade85to86\cognos10_integration.xml"

v File: No file - removing properties

v Purpose: Remove JMS configurationproperties that are no longer used

v configTool.bat -d -o -p "Affinium|suite|jmsServer"

v configTool.bat -d -o -p "Affinium|suite|jmsPort"

v File: LDAP_Anonymous_bind.xml


v Purpose: Only if you are upgrading fromversion 8.2.0 or later, import a new LDAPconfiguration property

configTool -i -p"Affinium|suite|security|loginModes|LDAPPartitionLogin" -fC:\Unica\Platform\conf\upgrade85to86\LDAP_Anonymous_bind.xml


Table 11. Files for upgrading from version 8.0.x, 8.1.x, or 8.2.x versions before 8.2.0.7 (continued)


v File: quicklinks_category.xml


v Purpose: Import properties for quicklinksdashboard portlets

configTool.bat -i -o -p "Affinium|suite" -f"C:\Unica\Platform\conf\upgrade86to90\quicklinks_category.xml"

v File: manager_alerts_registration.xml


v Purpose: Import configuration propertiesthat create the alerts menu items

configTool.bat -i -o -p "Affinium|suite|uiNavigation|alerts"-f "C:\Unica\Platform\conf\manager_alerts_registration.xml"

v File: disablePageTagging.xml


v Purpose: Import a configuration propertythat determines whether IBM can gatherbasic statistics that track overall productusage trends.

configTool.bat -i -o -p "Affinium|suite" -f"C:\Unica\Platform\conf\upgrade82to85\disablePageTagging.xml"




v configTool.bat -i -o -p "Affinium" -f "C:\Unica\Platform\conf\coremetrics_configuration.xml"

v configTool.bat -i -o -p"Affinium|suite|uiNavigation|mainMenu|Analytics" -f"C:\Unica\Platform\conf\coremetrics_navigation.xml"

v File: scheduler.xml

v Location: db\upgrade90to91 directory underyour Marketing Platform installation

v Purpose: The boolean property to enable ordisable the scheduler feature in MarketingPlatform.

configtool -i -p "Affinium|suite|scheduler" -f"C:\Unica\Platform\conf\upgrade90to91\scheduler.xml"

v File: unknownPolling.xml


v Purpose: Imports properties for quicklinksdashboard portlets

configtool -i -p "Affinium|suite|scheduler" -f"C:\Unica\Platform\conf\upgrade90to91\unknownPolling.xml"

v File: communication_email.xml


v Purpose: Imports configuration propertiesto enable email notifications. When enabledMarketing Platform attempts to send emailsto users for system alerts and notifications.

configTool.bat -i -o -p "Affinium|Manager" -f"C:\Unica\Platform\conf\upgrade86to90\communication_email.xml"




v File: notification.xml


v Purpose: Imports configuration propertiesfor the notification feature. The followingproperties are added:

– The number of days to retain alerts - 90

– Frequency in minutes at which emailsare sent - 30

– Maximum number of retries for sendingand email - 1

configTool.bat -i -o -p "Affinium|suite" -f"C:\Unica\Platform\conf\upgrade86to90\notification.xml"

v File: is_clustered.xml


v Purpose: The boolean property to specify ifthe Marketing Platform instance isclustered. If you install Marketing Platformin a clustered deployment, set this propertyto True. Otherwise, retain the default valueof False.

configtool -i -p "Affinium|suite" -f "C:\Unica\Platform\conf\upgrade90to91\is_clustered.xml"

v File: taskNotification.xml


v Purpose: Imports the Group Name fieldwhere you can enter the groups that arenotified with scheduled notifications.

configtool -i -p "Affinium|suite|scheduler|taskRegistrations|Campaign|flowchart" -f "C:\Unica\Platform\conf\upgrade90to91\taskNotification.xml"

configtool -i -p "Affinium|suite|scheduler|taskRegistrations|Campaign|mailing" -f "C:\Unica\Platform\conf\upgrade90to91\taskNotification.xml"

configtool -i -p "Affinium|suite|scheduler|taskRegistrations|Campaign|optimize" -f "C:\Unica\Platform\conf\upgrade90to91\taskNotification.xml"

configtool -i -p "Affinium|suite|scheduler|taskRegistrations|InteractionHistory|ETL" -f "C:\Unica\Platform\conf\upgrade90to91\taskNotification.xml"

configtool -i -p "Affinium|suite|scheduler|taskRegistrations|AttributionModeler|TrainingRun" -f "C:\Unica\Platform\conf\upgrade90to91\taskNotification.xml"

configtool -i -p "Affinium|suite|scheduler|taskRegistrations|AttributionModeler|ScoringRun" -f "C:\Unica\Platform\conf\upgrade90to91\taskNotification.xml"




v File: config_data_filter_cache.xml


v Purpose: Allows you to configure the datafilter cache. If the configuration property isset to True, the data filter cache is enabledfor enhanced performance. If theconfiguration property is set to False, thecaching is not enabled, and all operationsare completed by connecting to thedatabase for each data filter request. Theconfiguration property is visible on the userinterface.

configTool.bat -vp -p "Affinium|Manager|datafiltering" -f"C:\Unica\Platform\conf\upgrade90to91\Config_data_filter_cache.xml"Note: If you change this value, you must restart the MarketingPlatform for the changes to take effect.

v File: Refresh_data_filter_cache.xml


v Purpose: If data filter caching is enabled,this configuration property ensures that thecache is refreshed every time that there is achange in the data filter definitions.

configTool.bat -vp -p "Affinium|Manager|datafiltering" -f"C:\Unica\Platform\conf\upgrade90to91\Refresh_data_filter_cache.xml"

v Files: navigation.xml andemm_spss_configuration.xml

v Location: conf\upgrade90to91

v Purpose: Import IBM SPSS® ModelerAdvantage Marketing Edition configurationproperties.

configTool -i -o -p"Affinium|suite|uiNavigation|mainMenu|Analytics" -f"C:\Unica\Platform\conf\emm_spss_navigation.xml"

configTool -i -o -p "Affinium" -f "C:\Unica\Platform\conf\emm_spss_configuration.xml"

10. Run the alertConfigTool utility from the tools\bin directory under yourMarketing Platform installation to register the Marketing Platform alerts andnotifications. Example command (Windows):alertConfigTool.bat -i -f "C:\Platform\conf\Platform_alerts_configuration.xml"

11. Run the upgrade85Dashboard script from the tools\bin directory under yourMarketing Platform installation to upgrade the dashboard.

12. Go to Help > About and complete the following steps to update the Aboutpage:a. Use the configTool utility to export the Affinium | Manager | about

category.

Note: The Affinium | Manager | about is not visible on theConfiguration page because it is marked hidden.Example (Windows):configTool.bat -x -p "Affinium|Manager|about" -f "C:\Unica\Platform\conf\about.xml"

b. Edit the exported XML file that you just created (about.xml in theexample) to change the version number and display name. Find thereleaseNumber property and change the value to the current version ofMarketing Platform. In the following example, change 8.0.0 to your newversion:


<property name="releaseNumber" type="string"><displayNameKey>about.releaseNumber</displayNameKey><value>9.1.0.0.0.build_number</value></property>

c. Use the configTool utility to import the revised file. You must use the -ooption to overwrite the node. You must specify the parent node when youimport. Example (Windows):configTool.bat -i -p "Affinium|Manager" -f "about.xml" -o

13. Deploy and verify your installation as described in the Chapter 9, “DeployingMarketing Platform,” on page 55 chapter.

After the upgrade process is successful and the application is up and running,delete the liferay tables by using the drop-liferay-tables.sql script. Thedrop-liferay-tables.sql is located in the Platform_installation/db/upgrade86to90/drop-liferay-tables.sql directory.

See the IBM EMM Reports Installation and Configuration Guide for the additionalsteps that are required for reporting upgrades.



Chapter 5. Upgrading from version 8.2.0.7 and 8.2.x versionswith manual migration




See “Marketing Platform upgrade scenarios” on page 12 for information onupgrading from other versions.

Complete the following steps to upgrade manually from version 8.5.0:1. Make a backup of your Marketing Platform system table database.

Important: Do not skip this step. If upgrade fails, you will not be able to rollback your database and your data will be corrupted.

2. Undeploy your current version.3. Run the IBM EMM master installer. The IBM EMM master installer starts. Use










requested information.5. Use the configTool utility to complete the following steps to ensure that the

SQL scripts that you run in step 7 work correctly:a. Export all your configuration properties from the Affinium root node. For

example, in Windows, use the following command to export the propertiesto the config_property_export.xml file, which is written to the installdirectory under your Marketing Platform installation:configTool.bat -x -p "Affinium" -f "C:\Unica\Platform\install\config_property_export.xml"

b. Delete all configuration properties from the Affinium root node. Forexample, in Windows, use the following command to delete the properties:configTool.bat -d -o -p "Affinium"

c. Import the configuration properties that you exported. For example, inWindows, use the following command to import the properties from theconfig_property_export.xml file, which is in the installation directory underyour Marketing Platform installation:configTool.bat -i -o -f "C:\Unica\Platform\install\config_property_export.xml"

6. In the db\upgrade82to85 directory under your Marketing Platform installation,edit the ManagerSchema_DB_Type_86upg.sql SQL script, where DB_Type is thedatabase type of your system tables database. Use the following guidelines toedit the ManagerSchema_DB_Type_86upg.sql SQL script:v For all database types, remove the following statement:

ALTER TABLE USCH_RUN ADD PAYLOAD NVARCHAR(4000);

v If your database is DB2, also remove the following statements:ALTER TABLE qrtz_job_details ALTER COLUMN job_data SET DATA TYPEblob(4000);

ALTER TABLE qrtz_triggers ALTER COLUMN job_data SET DATA TYPEblob(4000);

7. Use the following table to locate the SQL scripts that are provided with yournew Marketing Platform installation against your Marketing Platform systemtable database:

Table 12. Scripts for upgrading from version 8.2.0.7 or a later 8.2.x version




db\upgrade8207xto85




db\upgrade85to86




Table 12. Scripts for upgrading from version 8.2.0.7 or a later 8.2.x version (continued)




db\upgrade86to90


or



db\upgrade90to91








Table 13. Files for upgrading from version 8.2.0.7 or a later 8.2.x version








Chapter 5. Upgrading from version 8.2.0.7 and 8.2.x versions with manual migration 29

Table 13. Files for upgrading from version 8.2.0.7 or a later 8.2.x version (continued)



v Location: conf/upgrade85to86rectory underyour Marketing Platform installation










configTool.bat -i -p "Affinium" -f "C:\Unica\Platform\conf\coremetrics_configuration.xml"

configTool.bat -i -p"Affinium|suite|uiNavigation|mainMenu|Analytics" -f"C:\Unica\Platform\conf\coremetrics_navigation.xml"







configTool.bat -d -o -p "Affinium|suite|jmsServer"

configTool.bat -d -o -p "Affinium|suite|jmsPort"












configTool.bat -i -o -p "Affinium|suite|uiNavigation|alerts -f"C:\Unica\Platform\conf\manager_alerts_registration.xml"











configTool.bat -i -o -p "Affinium" -f "C:\Unica\Platform\conf\coremetrics_configuration.xml"

configTool.bat -i -o -p"Affinium|suite|uiNavigation|mainMenu|Analytics" -f"C:\Unica\Platform\conf\coremetrics_navigation.xml"



v Purpose: The boolean property to enable ordisable the scheduler feature in MarketingPlatform














































v Purpose: Import IBM SPSS ModelerAdvantage Marketing Edition configurationproperties.






category.


b. Edit the exported XML file that you just created (about.xml in theexample) to change the version number and display name. Find thereleaseNumber property and change the value to the current version ofMarketing Platform. In the following example, change 8.0.0 to your newversion:<property name="releaseNumber" type="string"><displayNameKey>about.releaseNumber</displayNameKey><value>9.1.0.0.0.build_number</value></property>







Chapter 6. Upgrading from version 8.5.x with manualmigration





Complete the following steps to upgrade manually from version 8.5.0:1. Make a backup of your Marketing Platform system table database.












requested information.5. Use the following table to locate the SQL scripts that are provided with your

new Marketing Platform installation against your Marketing Platform systemtable database:

Table 14. Scripts for upgrading from version 8.5.x




db\upgrade85to86




db\upgrade86to90


or



db\upgrade90to91









Table 15. Files for upgrading from version 8.5.x.



















configTool.bat -i -p "Affinium" -f "C:\Unica\Platform\conf\coremetrics_configuration.xml"

configTool.bat -i -p"Affinium|suite|uiNavigation|mainMenu|Analytics" -f"C:\Unica\Platform\conf\coremetrics_navigation.xml"







configTool.bat -d -o -p "Affinium|suite|jmsServer"

configTool.bat -d -o -p "Affinium|suite|jmsPort"





Chapter 6. Upgrading from version 8.5.x with manual migration 37

Table 15. Files for upgrading from version 8.5.x. (continued)

















configTool.bat -i -o -p "Affinium" -f "C:\Unica\Platform\conf\coremetrics_configuration.xml"

configTool.bat -i -o -p"Affinium|suite|uiNavigation|mainMenu|Analytics" -f"C:\Unica\Platform\conf\coremetrics_navigation.xml"


















































configTool -i -o -p"Affinium|suite|uiNavigation|mainMenu|Analytics" -fC:\Unica\Platform\conf\emm_spss_navigation.xml





category.


b. Edit the exported XML file that you just created (about.xml in theexample) to change the version number and display name. Find thereleaseNumber property and change the value to the current version ofMarketing Platform. In the following example, change 8.0.0 to your newversion:


<property name="releaseNumber" type="string"><displayNameKey>about.releaseNumber</displayNameKey><value>9.1.0.0.0.build_number</value></property>







Chapter 7. Upgrading from version 8.6.x with manualmigration



Also, ensure that your installation of Marketing Platform 8.x is fully functional andyou can run the command-line tools. Running the command-line tools requires theuse of three Marketing Platform utilities that are in the tools/bin directory underyour Marketing Platform installation. Complete information about using theutilities with example commands for common tasks is available in the followingtopics:v “populateDb” on page 72v “configTool” on page 63v “alertConfigTool” on page 63


Complete the following steps to upgrade your Marketing Platform installation toversion 9.1:1. Make a backup of your Marketing Platform system table database.












requested information.5. Run the ManagerSchema_DB_Type_90upg.sql script in the db\upgrade86to90

directory under your Marketing Platform installation.6. Run the ManagerSchema_DB_Type_91upg.sql script in the db\upgrade90to91

directory under your Marketing Platform installation.7. Run one of the following commands:

v For Windows:installation_directory\platform\tools\bin\upgrade90to91.bat



Note: The configTool utility is in the tools/bin directory under yourMarketing Platform installation. For complete details on the function of theconfiguration properties, see the online help for the Configuration page, or theIBM Marketing Platform Administrator's Guide.


Table 16. Files for upgrading from version 8.6.0.







configTool.bat -i -p"Affinium|suite|security|ldapSynchronization|ldapProperties"-f "C:\Unica\Platform\conf\Ldap_Auto_Sync_BaseDN_Settings.xml"







v Purpose: Import configuration properties toenable email notifications



Table 16. Files for upgrading from version 8.6.0. (continued)




v Purpose: Import configuration propertiesfor the notification feature































































category.








Chapter 8. Upgrading from version 9.x with manual migration

The Marketing Platform upgrade installer can perform all of the data migrationthat is required for an upgrade automatically. However, if the policy of yourorganization does not allow automatic migration, you must complete the migrationprocedure to upgrade Marketing Platform manually. To manually upgradeMarketing Platform from version 9.0 to version 9.1, you must run specific SQLscripts and insert the required configuration properties.


Also, ensure that your installation of Marketing Platform 8.x is fully functional andyou can run the command-line tools. Running the command-line tools requires theuse of three Marketing Platform utilities that are in the tools/bin directory underyour Marketing Platform installation. Complete information about using theutilities with example commands for common tasks is available in the followingtopics:v “populateDb” on page 72v “configTool” on page 63v “alertConfigTool” on page 63


Complete the following steps to upgrade your Marketing Platform installation toversion 9.1:1. Make a backup of your Marketing Platform system table database.



the following instructions after the IBM EMM master installer starts:v When the IBM EMM master installer prompts you to choose an installation









requested information.5. Run the ManagerSchema_DB_Type_91upg.sql script in the db\upgrade90to91

directory under your Marketing Platform installation.6. Run one of the following commands:

v For Windows:installation_directory\platform\tools\bin\upgrade90to91.bat



Note: The configTool utility is in the tools/bin directory under yourMarketing Platform installation. For complete details on the function of theconfiguration properties, see the online help for the Configuration page, or theIBM Marketing Platform Administrator's Guide.


Table 17. File names for upgrading from version 8.6.0.















Table 17. File names for upgrading from version 8.6.0. (continued)






















Chapter 8. Upgrading from version 9.x with manual migration 51

Table 17. File names for upgrading from version 8.6.0. (continued)















v Files: cognos.xml


v Purpose: Imports cognos configurationproperties.

configTool.bat -i -o -p"Affinium|Report|integrations|cognos10" -f "cognos.xml"

v Files: taskNotificationNavImport.xml


v Purpose: Imports configuration propertiesfor task notification navigation.

configTool -i -p "Affinium|suite|uiNavigation|settingsMenu" -f"taskNotificationNavImport.xml"



category.

Note: The Affinium | Manager | about is not visible on theConfiguration page because it is marked hidden.Example (Windows):


configTool.bat -x -p "Affinium|Manager|about" -f "C:\Unica\Platform\conf\about.xml"





Chapter 8. Upgrading from version 9.x with manual migration 53


Chapter 9. Deploying Marketing Platform

You must follow a set of guidelines when you deploy Marketing Platform in yourweb application server. There is a different set of guidelines for deployingMarketing Platform on WebLogic and on WebSphere.

When you ran the IBM installer, you completed one of the following actions:v You included Marketing Platform in an EAR file.v You created the WAR file of Marketing Platform (unica.war).

If you included other products in an EAR file, you must follow the deploymentguidelines that are provided in the individual installation guides for the productsthat are included in the EAR file.

We assume that you know how to work with your web application server. Consultyour web application server documentation for details such as navigation in theAdministration console.

Guidelines for deploying Marketing Platform on WebLogicYou must follow a set of guidelines when you deploy Marketing Platform on theWebLogic application.

Use the following guidelines when you deploy the Marketing Platform productson any supported version of WebLogic:v IBM EMM products customize the Java™ virtual machine (JVM) that is used by

WebLogic. If you encounter errors related to JVM, you can create a WebLogicinstance that is dedicated to IBM EMM products.

v Open the startWebLogic.cmd file and verify that the SDK that is selected for theWebLogic domain that you are using is the Sun SDK for the JAVA_VENDORvariable.The JAVA_VENDOR variable must be set to Sun (JAVA_VENDOR=Sun). IftheJAVA_VENDOR variable is set to JAVA_VENDOR, it means that JRockit is selected.You must change the selected SDK, because JRockit is not supported. Refer tothe BEA WebLogic documentation to change the selected SDK.

v Deploy Marketing Platform as a web application.v If you are configuring WebLogic to use the IIS plug-in, review the BEA

WebLogic documentation.v Complete the following tasks if your installation must support non-ASCII

characters, for example for Portuguese or for locales that require multi-bytecharacters:1. Edit the setDomainEnv script in the bin directory under your WebLogic

domain directory to add -Dfile.encoding=UTF-8 to JAVA_VENDOR.2. In the WebLogic console, click the Domain link on the home page.3. In the Web Applications tab, select the Archived Real Path Enabled check

box.4. Restart WebLogic.5. Deploy and start the EAR file or the unica.war file.

v If deploying in a production environment, set the JVM memory heap sizeparameters to 1024 by adding the following line to the setDomainEnv script:


Set MEM_ARGS=-Xms1024m -Xmx1024m -XX:MaxPermSize=256m

Guidelines for deploying Marketing Platform on WebSphereYou must follow a set of guidelines when you deploy Marketing Platform onWebsphere.

Make sure that the version of WebSphere meets the requirements that aredescribed in the IBM Enterprise Products Recommended Software Environments andMinimum System Requirements document, including any necessary fix packs. Usethe following guidelines when you deploy Marketing Platform on WebSphere:v Specify the following custom property in the server:

– Name: com.ibm.ws.webcontainer.invokefilterscompatibility– Value: true

v See http://www-01.ibm.com/support/docview.wss?uid=swg21284395 forinstructions on setting a custom property in WebSphere.

v Deploy the IBM EAR file or unica.war file as an enterprise application. Whenyou deploy the EAR file or the unica.war file, ensure that the JDK source levelof the JSP compiler is set to Java 16 or 17, and that JSP pages are precompiledaccording to the following information:– In the form where you browse to and select the WAR file, select Show me all

installation options and parameters so the Select Installation Optionswizard runs.

– In step 1 of the Select Installation Options wizard, select PrecompileJavaServer Pages files.

– In step 3 of the Select Installation Options wizard, ensure that the JDKSource Level is set to 16 or 17.If you deployed an EAR, set the JDK Source Level for each WAR file.

– In step 8 of the Select Installation Options wizard, select UnicaPlatformDSas the matching Target Resource.

The context root must be it /unica, all lower case.v In the Web Container Settings > Web Container > Session Management section

of the server, enable cookies. Specify a different session cookie name for eachapplication that is deployed. Use one of the following procedures to specify acookie name:– Select the Override session management check box under Session

Management.If you deployed separate WAR files for your IBM EMM products, in theWebSphere console, in the Applications > Enterprise Applications >[deployed_application] > Session Management > Enable Cookies > CookieName section of the server, specify a unique session cookie name.If you deployed EAR files for your IBM EMM products, in the WebSphereconsole, in the Applications > Enterprise Applications >[deployed_application] > Module Management > [deployed_module] >Session Management > Enable Cookies > Cookie Name section of theserver, specify a unique session cookie name.

– If your installation must support non-ASCII characters, for example forPortuguese or for locales that require multi-byte characters, add the followingarguments to Generic JVM Arguments at the server level:-Dfile.encoding=UTF-8

-Dclient.encoding.override=UTF-8


http://www-01.ibm.com/support/docview.wss?uid=swg21284395

Navigation tip: Select Servers > Application Servers > Java and ProcessManagement > Process Definition > Java Virtual Machine > Generic JVMArguments. See the WebSphere documentation for additional details.

v In the Applications > Enterprise Applications section of the server, select theEAR file or WAR file that you deployed, then select Class loading and updatedetection and specify the following properties.– If you are deploying a WAR file:

- For Class loader order, select Classes loaded with local class loader first(parent last).

- For WAR class loader policy, select Single class loader for application.– If you are deploying an EAR file:

- For Class loader order, select Classes loaded with local class loader first(parent last).

- For WAR class loader policy, select Class loader for each WAR file inapplication.

v Start your deployment. If your instance of WebSphere is configured to use aJVM version 1.6 or newer, complete the following steps to work around an issuewith the time zone database.1. Stop WebSphere.2. Download the IBM Time Zone Update Utility for Java (JTZU) from the IBM

web site:http://www.ibm.com/developerworks/java/jdk/dst/index.html

3. Follow the steps provided by the IBM (JTZU) to update the time zone datain your JVM.

4. Restart WebSphere.v The following additional setting is required for WAS 8.5:

In Websphere Enterprise Applications, select Your Application > ManageModules > Your Application > Class Loader Order > Classes loaded with localclass loader first (parent last).

v The recommended minimum heap size for the basic functioning of theapplication is 512, and the recommended maximum heap size is 1024.Complete the following tasks to specify the heap size:1. In WebSphere Enterprise Applications, select Servers > WebSphere

application servers > server1 > Server Infrastructure > Java and ProcessManagement > Process definition > Java Virtual Machine.

2. Set the initial heap size to 512.3. Set the maximum heap size to 1024

See the WebSphere documentation for more information about sizing.

Verifying your Marketing Platform installationAfter you install and deploy Marketing Platform, you must verify that there are noerrors in your Marketing Platform installation and deployment. You can configureyour Marketing Platform installation after the verification.

Complete the following tasks to verify your Marketing Platform installation:1. Access the IBM EMM URL in a supported web browser.

If you entered a domain when you installed Marketing Platform, the URL is thefollowing, where host is the machine where Marketing Platform is installed,

Chapter 9. Deploying Marketing Platform 57

http://www.ibm.com/developerworks/java/jdk/dst/index.html

domain.com is the domain in which the host machine resides, and port is theport number on which the web application server listens.http://host.domain.com:port/unica

2. Log in using the default administrator login, which is asm_admin with passwordas the password.You will be asked to change the password. You can enter the existingpassword, but for good security you should choose a new one.The default home page is the dashboard, which you will configure later.

3. Under the Settings menu, check the Users, User Groups, and User Permissionspages to verify that the pre-configured users, groups, roles, and permissions arepresent, as described in the Marketing Platform Administrator's Guide.

4. Add a new user and group and verify that data is entered into the MarketingPlatform system table database.

5. Under the Settings menu, check the Configuration page to verify that theMarketing Platform configuration properties exist.

There are additional configuration tasks, such as configuring the dashboard, settingup user access to IBM applications, and integrating with an LDAP or web accesscontrol system (optional). See the IBM Marketing Platform Administrator's Guide forinstructions.


Chapter 10. Configuring Marketing Platform after deployment

For a basic installation of Marketing Platform, you must configure MarketingPlatform after deployment if you use the IBM EMM reporting feature, or if youwant to use a password policy.

If you use the IBM EMM reporting feature, see the IBM EMM Reports Installationand Configuration Guide. If you want to use a password policy in mind, see “Defaultpassword settings” to determine whether you must change the default passwordsettings.

The Marketing Platform has additional properties on the Configuration page thatperform important functions that you can optionally adjust. See the context helpfor the properties, or the IBM Marketing Platform Administrator's Guide to learnmore about what they do and how to set them.

Default password settingsIBM EMM provides default settings for using passwords. However, you can usethe IBM EMM > General > Password settings category on the IBM EMMConfiguration page to change the default settings, and create your passwordpolicies.

The default password settings apply to passwords for users that are created withinIBM EMM. The settings do not apply to the users that are imported throughsynchronization with an external system, such as Windows Active Directory, asupported LDAP directory server, or web access control server. The exception isthe Maximum failed login attempts allowed setting, which affects both internaland external users. Also note that this property does not override any similarrestriction set in an external system.

The following settings are the default password settings that IBM EMM:v Maximum failed login attempts allowed - 3v Password history count - 0v Validity (in days) - 30v Blank passwords allowed - Truev Allow identical user name and password - Truev Minimum number of numeric characters - 0v Minimum number of letter characters - 0v Minimum character length - 4

See the online help for descriptions of the default settings.



Chapter 11. IBM Marketing Platform utilities and SQL scripts

This section provides an overview of the Marketing Platform utilities, includingsome details that apply to all of the utilities and which are not included in theindividual utility descriptions.

Location of utilities

Marketing Platform utilities are located in the tools/bin directory under yourMarketing Platform installation.

List and descriptions of utilities

The Marketing Platform provides the following utilities.v “alertConfigTool” on page 63 - registers alerts and configurations for IBM EMM

productsv “configTool” on page 63 - imports, exports, and deletes configuration settings,

including product registrationsv “datafilteringScriptTool” on page 68 - creates data filtersv “encryptPasswords” on page 69 - encrypts and stores passwordsv “partitionTool” on page 70 - creates database entries for partitionsv “populateDb” on page 72 - populates the Marketing Platform databasev “restoreAccess” on page 73 - restores a user with the platformAdminRole rolev “scheduler_console_client” on page 74 - lists or starts IBM EMM Scheduler jobs

that are configured to listen for a trigger.

Prerequisites for running Marketing Platform utilities

The following are prerequisites for running all Marketing Platform utilities.v Run all utilities from the directory where they are located (by default, the

tools/bin directory under your Marketing Platform installation).v On UNIX, the best practice is to run the utilities with the same user account that

runs the application server on which Marketing Platform is deployed. If you runa utility with a different user account, adjust the permissions on theplatform.log file to allow that user account to write to it. If you do not adjustpermissions, the utility is not able to write to the log file and you might seesome error messages, although the tool should still function correctly.

Troubleshooting connection issues

All of the Marketing Platform utilities except encryptPasswords interact with theMarketing Platform system tables. To connect to the system table database, theseutilities use the following connection information, which is set by the installerusing information provided when the Marketing Platform was installed. Thisinformation is stored in the jdbc.properties file, located in the tools/bin directoryunder your Marketing Platform installation.v JDBC driver namev JDBC connection URL (which includes the host, port, and database name)v Data source login


v Data source password (encrypted)

In addition, these utilities rely on the JAVA_HOME environment variable, set either inthe setenv script located in the tools/bin directory of your Marketing Platforminstallation, or on the command line. The Marketing Platform installer should haveset this variable automatically in the setenv script, but it is a good practice toverify that the JAVA_HOME variable is set if you have a problem running a utility.The JDK must be the Sun version (not, for example, the JRockit JDK available withWebLogic).

Special characters

Characters that are designated as reserved characters in the operating system mustbe escaped. Consult your operating system documentation for a list of reservedcharacters and how to escape them.

Standard options in Marketing Platform utilities

The following options are available in all Marketing Platform utilities.

-l logLevel

Set the level of log information displayed in the console. Options are high, medium,and low. The default is low.

-L

Set the locale for console messages. The default locale is en_US. The availableoption values are determined by the languages into which the Marketing Platformhas been translated. Specify the locale using the ICU locale ID according to ISO639-1 and ISO 3166.

-h

Display a brief usage message in the console.

-m

Display the manual page for this utility in the console.

-v

Display more execution details in the console.

Setting up Marketing Platform utilities on additional machinesOn the machine where the Marketing Platform is installed, you can run theMarketing Platform utilities without any additional configuration. However, youmight want to run the utilities from another machine on the network. Thisprocedure describes the steps required to do this.

Ensure that the machine on which you perform this procedure meets the followingprerequisites.v The correct JDBC driver must exist on the machine or be accessible from it.v The machine must have network access to the Marketing Platform system tables.


v The Java runtime environment must be installed on the machine or be accessiblefrom it.

1. Gather the following information about the Marketing Platform system tables.v The fully qualified path for the JDBC driver file or files on your system.v The fully qualified path to an installation of the Java runtime environment.

The default value in the installer is the path to the supported version of theJRE that the installer places under your IBM EMM installation directory. Youcan accept this default or specify a different path.

v Database typev Database hostv Database portv Database name/system IDv Database user namev Database password

2. Run the IBM EMM installer and install the Marketing Platform.Enter the database connection information that you gathered for the MarketingPlatform system tables. If you are not familiar with the IBM EMM installer, seethe Campaign or Marketing Operations installation guide.You do not have to deploy the Marketing Platform web application if you areinstalling the utilities only.

Marketing Platform utilitiesThis section describes the Marketing Platform utilities, with functional details,syntax, and examples.

alertConfigToolNotification types are specific to the various IBM EMM products. Use thealertConfigTool utility to register the notification types when the installer has notdone this automatically during installation or upgrade.

Syntax

alertConfigTool -i -f importFile

Commands

-i -f importFile

Import alert and notification types from a specified XML file.

Examplev Import alert and notification types from a file named

Platform_alerts_configuration.xml located in the tools\bin directory underthe Marketing Platform installation.alertConfigTool -i -f Platform_alerts_configuration.xml

configToolThe properties and values on the Configuration page are stored in the systemtables. You can use the configTool utility to import and export configurationsettings to and from the system tables.

Chapter 11. IBM Marketing Platform utilities and SQL scripts 63

When to use configTool

You might want to use configTool for the following reasons.v To import partition and data source templates that are supplied with Campaign,

which you can then modify and duplicate by using the Configuration page.v To register (import configuration properties for) IBM EMM products, if the

product installer is unable to add the properties to the database automatically.v To export an XML version of configuration settings for backup or to import into

a different installation of IBM EMM.v To delete categories that do not have the Delete Category link. You do this by

using configTool to export your configuration, then manually deleting the XMLthat creates the category, and by using configTool to import the edited XML.

Important: This utility modifies the usm_configuration andusm_configuration_values tables in the Marketing Platform system table database,which contains the configuration properties and their values. For best results,either create backup copies of these tables, or export your existing configurationsby using configTool and back up the resulting file so you have a way to restoreyour configuration if you make an error when you use configTool to import.

Syntax

configTool -d -p "elementPath" [-o]

configTool -i -p "parent ElementPath" -f importFile [-o]

configTool -x -p "elementPath" -f exportFile

configTool -vp -p "elementPath" -f importFile [-d]

configTool -r productName -f registrationFile [-o] configTool -uproductName

Commands

-d -p "elementPath" [o]

Delete configuration properties and their settings, specifying a path in theconfiguration property hierarchy.

The element path must use the internal names of categories and properties. Youcan obtain them by going to the Configuration page, selecting the wanted categoryor property, and looking at the path that is displayed in parentheses in the rightpane. Delimit a path in the configuration property hierarchy by using the |character, and surround the path with double quotation marks.

Note the following.v Only categories and properties within an application can be deleted by using

this command, not whole applications. Use the -u command to unregister awhole application.

v To delete categories that do not have the Delete Category link on theConfiguration page, use the -o option.


When you use -d with the -vp command, the configTool deletes any child nodes inthe path you specify if those nodes are not included in the XML file you specify.

-i -p "parentElementPath" -f importFile [o]

Import configuration properties and their settings from a specified XML file.

To import, you specify a path to the parent element under which you want toimport your categories. The configTool utility imports properties under thecategory you specify in the path.

You can add categories at any level below the top level, but you cannot add acategory at same level as the top category.

The parent element path must use the internal names of categories and properties.You can obtain them by going to the Configuration page, selecting the requiredcategory or property, and looking at the path that is displayed in parentheses inthe right pane. Delimit a path in the configuration property hierarchy by using the| character, and surround the path with double quotation marks.

You can specify an import file location relative to the tools/bin directory or youcan specify a full directory path. If you specify a relative path or no path,configTool first looks for the file relative to the tools/bin directory.

By default, this command does not overwrite an existing category, but you can usethe -o option to force an overwrite.

-x -p "elementPath" -f exportFile

Export configuration properties and their settings to an XML file with a specifiedname.

You can export all configuration properties or limit the export to a specific categoryby specifying a path in the configuration property hierarchy.

The element path must use the internal names of categories and properties, whichyou can obtain by going to the Configuration page, selecting the wanted categoryor property, and looking at the path that is displayed in parentheses in the rightpane. Delimit a path in the configuration property hierarchy by using the |character, and surround the path with double quotation marks.

You can specify an export file location relative to the current directory or you canspecify a full directory path. If the file specification does not contain a separator (/on UNIX, / or \ on Windows), configTool writes the file to the tools/bindirectory under your Marketing Platform installation. If you do not provide thexml extension, configTool adds it.

-vp -p "elementPath" -f importFile [-d]

This command is used mainly in manual upgrades, to import configurationproperties. If you applied a fix pack that contains a new configuration property,and you then upgrade, importing a configuration file as part of a manual upgradeprocess can override values that were set when the fix pack was applied. The -vpcommand ensures that the import does not override previously set configurationvalues.


Important: After you use the configTool utility with the -vp option, you mustrestart the web application server on which Marketing Platform is deployed so thechanges are applied.

When you use -d with the -vp command, the configTool deletes any child nodes inthe path you specify if those nodes are not included in the XML file you specify.

-r productName -f registrationFile

Register the application. The registration file location can be relative to thetools/bin directory or can be a full path. By default, this command does notoverwrite an existing configuration, but you can use the -o option to force anoverwrite. The productName parameter must be one of those names that are listedabove.

Note the following.v When you use the -r command, the registration file must have <application> as

the first tag in the XML.Other files can be provided with your product that you can use to insertconfiguration properties into the Marketing Platform database. For these files,use the -i command. Only the file that has the <application> tag as the first tagcan be used with the -r command.

v The registration file for the Marketing Platform is named Manager_config.xml,and the first tag is <Suite>. To register this file on a new installation, use thepopulateDb utility, or rerun the Marketing Platform installer as described in theIBM Marketing Platform Installation Guide.

v After the initial installation, to re-register products other than the MarketingPlatform, use configTool with the -r command and -o to overwrite the existingproperties.

The configTool utility uses product names as parameters with the commands thatregister and unregister products. With the 8.5.0 release of IBM EMM, manyproduct names changed. However, the names that are recognized by configTooldid not change. The valid product names for use with configTool are listed below,along with the current names of the products.

Table 18. Product names for configTool registration and unregistration

Product name Name used in configTool

Marketing Platform Manager

Campaign Campaign

Distributed Marketing Collaborate

eMessage emessage

Interact interact

Contact Optimization Optimize

Marketing Operations Plan

CustomerInsight Insight

Digital Analytics for On Premises NetInsight

Opportunity Detection Detect

Leads Leads

Interaction History InteractionHistory


Table 18. Product names for configTool registration and unregistration (continued)

Product name Name used in configTool

Attribution Modeler AttributionModeler

IBM SPSS Modeler Advantage EnterpriseMarketing Management Edition

SPSS

Digital Analytics Coremetrics

-u productName

Unregister an application that is specified by productName. You do not have toinclude a path to the product category; the product name is sufficient, and it isrequired. The process removes all properties and configuration settings for theproduct.

Options

-o

When used with -i or -r, it overwrites an existing category or product registration(node).

When used with -d, you can delete a category (node) that does not have theDelete Category link on the Configuration page.

Examplesv Import configuration settings from a file named Product_config.xml in the conf

directory under the Marketing Platform installation.configTool -i -p "Affinium" -f Product_config.xml

v Import one of the supplied Campaign data source templates into the defaultCampaign partition, partition1. The example assumes that you placed the Oracledata source template, OracleTemplate.xml, in the tools/bin directory under theMarketing Platform installation.configTool -i -p "Affinium|Campaign|partitions|partition1|dataSources" -fOracleTemplate.xml

v Export all configuration settings to a file named myConfig.xml in the D:\backupsdirectory.configTool -x -f D:\backups\myConfig.xml

v Export an existing Campaign partition (complete with data source entries), saveit to a file named partitionTemplate.xml, and store it in the default tools/bindirectory under the Marketing Platform installation.configTool -x -p "Affinium|Campaign|partitions|partition1" -fpartitionTemplate.xml

v Manually register an application named productName, by using a file namedapp_config.xml in the default tools/bin directory under the Marketing Platforminstallation, and force it to overwrite an existing registration of this application.configTool -r product Name -f app_config.xml -o

v Unregister an application named productName.configTool -u productName


datafilteringScriptToolThe datafilteringScriptTool utility reads an XML file to populate the datafiltering tables in the Marketing Platform system table database.

Depending on how you write the XML, you can use this utility in two ways.v Using one set of XML elements, you can auto-generate data filters based on

unique combinations of field values (one data filter for each uniquecombination).

v Using a slightly different set of XML elements, you can specify each data filterthat the utility creates.

See IBM Marketing Platform the Administrator's Guide for information about creatingthe XML.

When to use datafilteringScriptTool

You must use datafilteringScriptTool when you create new data filters.

Prerequisites

The Marketing Platform must be deployed and running.

Using datafilteringScriptTool with SSL

When the Marketing Platform is deployed using one-way SSL you must modifythe datafilteringScriptTool script to add the SSL options that perform handshaking.To modify the script, you must have the following information.v Truststore file name and pathv Truststore password

In a text editor, open the datafilteringScriptTool script (.bat or .sh) and find thelines that look like this (examples are Windows version).

:callexec

"%JAVA_HOME%\bin\java" -DUNICA_PLATFORM_HOME="%UNICA_PLATFORM_HOME%"

com.unica.management.client.datafiltering.tool.DataFilteringScriptTool %*

Edit these lines to look like this (new text is in bold). Substitute your truststorepath and file name and truststore password for myTrustStore.jks and myPassword.

:callexec

SET SSL_OPTIONS=-Djavax.net.ssl.keyStoreType="JKS"

-Djavax.net.ssl.trustStore="C:\security\myTrustStore.jks"

-Djavax.net.ssl.trustStorePassword=myPassword

"%JAVA_HOME%\bin\java" -DUNICA_PLATFORM_HOME="%UNICA_PLATFORM_HOME%"%SSL_OPTIONS%

com.unica.management.client.datafiltering.tool.DataFilteringScriptTool %*


Syntax

datafilteringScriptTool -r pathfile

Commands

-r path_file

Import data filter specifications from a specified XML file. If the file is not locatedin the tools/bin directory under your installation, provide a path and enclose thepath_file parameter in double quotation marks.

Examplev Use a file named collaborateDataFilters.xml, located in the C:\unica\xml

directory, to populate the data filter system tables.datafilteringScriptTool -r "C:\unica\xml\collaborateDataFilters.xml"

encryptPasswordsThe encryptPasswords utility is used to encrypt and store either of two passwordsthat Marketing Platform uses internally.

The two passwords that the utility can encrypt are as follows.v The password that the Marketing Platform uses to access its system tables. The

utility replaces an existing encrypted password (stored in the jdbc,propertiesfile, located in the tools\bin directory under your Marketing Platforminstallation) with a new one.

v The keystore password used by the Marketing Platform when it is configured touse SSL with a certificate other than the default one supplied with the MarketingPlatform or the web application server. The certificate can be either a self-signedcertificate or a certificate from a certificate authority.

When to use encryptPasswords

Use encryptPasswords as for the following reasons.v When you change the password of the account used to access your Marketing

Platform system table database.v When you have created a self-signed certificate or have obtained one from a

certificate authority.

Prerequisitesv Before running encryptPasswords to encrypt and store a new database password,

make a backup copy of the jdbc.properties file, located in the tools/bindirectory under your Marketing Platform installation.

v Before running encryptPasswords to encrypt and store the keystore password,you must have created or obtained a digital certificate and know the keystorepassword.

See Chapter 11, “IBM Marketing Platform utilities and SQL scripts,” on page 61 foradditional prerequisites.


Syntax

encryptPasswords -d databasePassword

encryptPasswords -k keystorePassword

Commands

-d databasePassword

Encrypt the database password.

-k keystorePassword

Encrypt the keystore password and store it in a file named pfile.

Examplesv When the Marketing Platformwas installed, the login for the system table

database account was set to myLogin. Now, some time after installation, you havechanged the password for this account to newPassword. Run encryptPasswords asfollows to encrypt and store the database password.encryptPasswords -d newPassword

v You are configuring an IBM EMM application to use SSL and have created orobtained a digital certificate. Run encryptPasswords as follows to encrypt andstore the keystore password.encryptPasswords -k myPassword

partitionToolPartitions are associated with Campaign policies and roles. These policies and rolesand their partition associations are stored in the Marketing Platform system tables.The partitionTool utility seeds the Marketing Platform system tables with basicpolicy and role information for partitions.

When to use partitionTool

For each partition you create, you must use partitionTool to seed the MarketingPlatform system tables with basic policy and role information.

See the installation guide appropriate for your version of Campaign for detailedinstructions on setting up multiple partitions in Campaign.

Special characters and spaces

Any partition description or user, group, or partition name that contains spacesmust be enclosed in double quotation marks.

See Chapter 11, “IBM Marketing Platform utilities and SQL scripts,” on page 61 foradditional restrictions.

Syntax

partitionTool -c -s sourcePartition -n newPartitionName [-uadmin_user_name] [-d partitionDescription] [-g groupName]


Commands

The following commands are available in the partitionTool utility.

-c

Replicates (clones) the policies and roles for an existing partition specified usingthe -s option, and uses the name specified using the -n option. Both of theseoptions are required with c. This command does the following.v Creates a new IBM EMM user with the Admin role in both the Administrative

Roles policy and the global policy in Campaign. The partition name you specifyis automatically set as this user's password.

v Creates a new Marketing Platform group and makes the new Admin user amember of that group.

v Creates a new partition object.v Replicates all the policies associated with the source partition and associates

them with the new partition.v For each replicated policy, replicates all roles associated with the policy.v For each replicated role, maps all functions in the same way that they were

mapped in the source role.v Assigns the new Marketing Platform group to the last system-defined Admin

role created during role replication. If you are cloning the default partition,partition1, this role is the default Administrative Role (Admin).

Options

-d partitionDescription

Optional, used with -c only. Specifies a description that appears in the output fromthe -list command. Must be 256 characters or less. Enclose in double quotationmarks if the description contains spaces.

-g groupName

Optional, used with -c only. Specifies the name of the Marketing Platform Admingroup that the utility creates. The name must be unique within this instance ofMarketing Platform

If not defined, the name defaults to partition_nameAdminGroup.

-n partitionName

Optional with -list, required with -c. Must be 32 characters or less.

When used with -list, specifies the partition whose information is listed.

When used with -c, specifies the name of the new partition, and the partitionname you specify is used as the password for the Admin user. The partition namemust match the name you gave the partition in when you configured it (using thepartition template on the Configuration page).

-s sourcePartition

Required, used with -c only. The name of the source partition to be replicated.


-u adminUserName

Optional, used with -c only. Specifies the user name of the Admin user for thereplicated partition. The name must be unique within this instance of MarketingPlatform.

If not defined, the name defaults to partitionNameAdminUser.

The partition name is automatically set as this user's password.

Examplesv Create a partition with the following characteristics.

– Cloned from partition1– Partition name is myPartition

– Uses the default user name (myPartitionAdminUser) and password(myPartition)

– Uses the default group name (myPartitionAdminGroup)– Description is "ClonedFromPartition1"

partitionTool -c -s partition1 -n myPartition -d "ClonedFromPartition1"

v Create a partition with the following characteristics.– Cloned from partition1– Partition name is partition2

– Specifies user name of customerA with the automatically assigned password ofpartition2

– Specifies group name of customerAGroup– Description is "PartitionForCustomerAGroup"

partitionTool -c -s partition1 -n partition2 -u customerA -gcustomerAGroup -d "PartitionForCustomerAGroup"

populateDbThe populateDb utility inserts default (seed) data in the Marketing Platform systemtables.

The IBM EMM installer can populate the Marketing Platform system tables withdefault data for Marketing Platform and for Campaign. However, if your companypolicy does not permit the installer to change the database, or if the installer isunable to connect with the Marketing Platform system tables, you must insertdefault data in the Marketing Platform system tables using this utility.

For Campaign, this data includes security roles and permissions for the defaultpartition. For Marketing Platform, this data includes default users and groups, andsecurity roles and permissions for the default partition.

Syntax

populateDb -n productName

Commands

-n productName


Insert default data into the Marketing Platform system tables. Valid product namesare Manager (for Marketing Platform) and Campaign (for Campaign).

Examplesv

Insert Marketing Platform default data manually.populateDb -n Manager

v

Insert Campaign default data manually.populateDb -n Campaign

restoreAccessThe restoreAccess utility allows you to restore access to Marketing Platform if allusers with PlatformAdminRole privileges have been inadvertently locked out or ifall ability to log in to the Marketing Platform has been lost.

When to use restoreAccess

You might want to use restoreAccess under the two circumstances described inthis section.

PlatformAdminRole users disabled

It is possible that all users with PlatformAdminRole privileges in MarketingPlatform might become disabled in the system. Here is an example of how theplatform_admin user account might become disabled. Suppose you have only oneuser with PlatformAdminRole privileges (the platform_admin user). Assume theMaximum failed login attempts allowed property property in the General |Password settings category on the Configuration page is set to 3. Then supposesomeone who is attempting to log in as platform_admin enters an incorrectpassword three times in a row. These failed login attempts cause theplatform_admin account to become disabled in the system.

In that case, you can use restoreAccess to add a user with PlatformAdminRoleprivileges to the Marketing Platform system tables without accessing the webinterface.

When you run restoreAccess in this way, the utility creates a user with the loginname and password you specify, and with PlatformAdminRole privileges.

If the user login name you specify exists in Marketing Platform as an internal user,that user's password is changed.

Only a user with the login name of PlatformAdmin and with PlatformAdminRoleprivileges can universally administer all dashboards. So if the platform_admin useris disabled and you create a user with restoreAccess, you should create a userwith a login of platform_admin.

Improper configuration of Active Directory integration

If you implement Windows Active Directory integration with improperconfiguration and can no longer log in, use restoreAccess to restore the ability tolog in.


When you run restoreAccess in this way, the utility changes the value of thePlatform | Security | Login method property from Windows integrated login toMarketing Platform. This change allows you to log in with any user account thatexisted before you were locked out. You can optionally specify a new login nameand password as well. You must restart the web application server on whichMarketing Platform is deployed if you use the restoreAccess utility in this way.

Password considerations

Note the following about passwords when you use restoreAccess.v The restoreAccess utility does not support blank passwords, and does not

enforce password rules.v If you specify a user name that is in use, the utility resets the password for that

user.

Syntax

restoreAccess -u loginName -p password

restoreAccess -r

Commands

-r

When used without the -u loginName option, reset the value of the Platform |Security | Login method property to Marketing Platform. Requires restart of theweb application server to take effect.

When used with the -u loginName option, create a PlatformAdminRole user.

Options

-u loginNname

Create a user with PlatformAdminRole privileges with the specified login name.Must be used with the -p option.

-p password

Specify the password for the user being created. Required with -u.

Examplesv Create a user with PlatformAdminRole privileges. The login name is tempUser

and the password is tempPassword.restoreAccess -u tempUser -p tempPassword

v Change the value of the login method to IBM Marketing Platform and create auser with PlatformAdminRole privileges. The login name is tempUser and thepassword is tempPassword.restoreAccess -r -u tempUser -p tempPassword

scheduler_console_clientJobs configured in the IBM EMM Scheduler can be listed and kicked off by thisutility, if they are set up to listen for a trigger.


What to do if SSL is enabled

When the Marketing Platform web application is configured to use SSL, the JVMused by the scheduler_console_client utility must use the same SSL certificatethat is used by the web application server on which the Marketing Platform isdeployed.

Take the following steps to import the SSL certificatev Determine the location of the JRE used by the scheduler_console_client.

– If JAVA_HOME is set as a system environment variable, the JRE it points to isthe one used by the scheduler_console_client utility.

– If JAVA_HOME is not set as a system environment variable, thescheduler_console_client utility uses the JRE set either in the setenv scriptlocated in the tools/bin directory of your Marketing Platform installation, oron the command line.

v Import the SSL certificate used by the web application server on which theMarketing Platform is deployed to the JRE used by scheduler_console_client.The Sun JDK includes a program called keytool that you can use to import thecertificate. Consult the Java documentation for complete details on using thisprogram, or access the help by entering -help when you run the program.

v Open the tools/bin/schedulerconsoleclient file in a text editor and add thefollowing properties. These differ depending on the web application server onwhich Marketing Platform is deployed.– For WebSphere, add these properties to the file.

-Djavax.net.ssl.keyStoreType=JKS-Djavax.net.ssl.keyStore="Path to your key store JKS file"-Djavax.net.ssl.keyStorePassword="Your key store password"-Djavax.net.ssl.trustStore="Path to your trust store JKS file"-Djavax.net.ssl.trustStorePassword="Your trust store password"-DisUseIBMSSLSocketFactory=false

– For WebLogic, add these properties to the file.-Djavax.net.ssl.keyStoreType="JKS"-Djavax.net.ssl.trustStore="Path to your trust store JKS file"-Djavax.net.ssl.trustStorePassword="Your trust store password"

If the certificates do not match, the Marketing Platform log file contains an errorsuch as the following.

Caused by: sun.security.provider.certpath.SunCertPathBuilderException:unable to find valid certification path to requested target

Prerequisites

The Marketing Platform must be installed, deployed, and running.

Syntax

scheduler_console_client -v -t trigger_name user_name

scheduler_console_client -s -t trigger_name user_name


Commands

-v

List the scheduler jobs configured to listen for the specified trigger.

Must be used with the -t option.

-s

Send the specified trigger.

Must be used with the -t option.

Options

-t trigger_name

The name of the trigger, as configured in the scheduler.

Examplev List jobs configured to listen for a trigger named trigger1.

scheduler_console_client -v -t trigger1

v Execute jobs configured to listen for a trigger named trigger1.scheduler_console_client -s -t trigger1


Chapter 12. Marketing Platform SQL scripts

This section describes the SQL scripts provided with Marketing Platform toperform various tasks relating to the Marketing Platform system tables.

The Marketing Platform SQL scripts are located in the db directory under yourMarketing Platform installation.

The scripts are designed to be run against the Marketing Platform system tables,using the database client.

ManagerSchema_DeleteAll.sqlThe Manager_Schema_DeleteAll.sql script removes all data from the MarketingPlatform system tables without removing the tables themselves. This scriptremoves all users, groups, security credentials, data filters, and configurationsettings from Marketing Platform.

When to use ManagerSchema_DeleteAll.sql

You might want to use ManagerSchema_DeleteAll.sql if corrupted data preventsyou from using an instance of Marketing Platform.

Additional requirements

To make Marketing Platform operational after runningManagerSchema_DeleteAll.sql , you must perform the following steps.v Run the populateDB utility as described in “populateDb” on page 72. The

populateDB utility restores the default configuration properties, users, roles, andgroups, but does not restore any users, roles, and groups you have created orimported after initial installation.

v Use the configTool utility with the config_navigation.xml file to import menuitems, as described in “configTool” on page 63.

v If you have performed any post-installation configuration, such as creating datafilters or integrating with an LDAP server or web access control platform, youmust perform these configurations again.

v If you want to restore previously existing data filters, run thedatafilteringScriptTool utility using the XML originally created to specify thedata filters.

ManagerSchema_PurgeDataFiltering.sqlThe ManagerSchema_PurgeDataFiltering.sql script removes all data filtering datafrom the Marketing Platform system tables without removing the data filter tablesthemselves. This script removes all data filters, data filter configurations,audiences, and data filter assignments from Marketing Platform.

When to use ManagerSchema_PurgeDataFiltering.sql

You might want to use ManagerSchema_PurgeDataFiltering.sql if you need toremove all data filters without removing other data in the Marketing Platformsystem tables.


Important: The ManagerSchema_PurgeDataFiltering.sql script does not reset thevalues of the two data filter properties, Default table name and Default audiencename. If these values are no longer valid for the data filters you want to use, youmust set the values manually on the Configuration page.

SQL scripts for creating system tablesUse the scripts described in the following table to create Marketing Platformsystem tables manually, when your company policy does not allow you to use theinstaller to create them automatically.

The scripts are shown in the order in which you must run them.

Table 19. Scripts for creating system tables

Datasource Type Script Names

IBM DB2v ManagerSchema_DB2.sql

If you plan to support multi-byte characters (for example,Chinese, Japanese, or Korean), use theManagerSchema_DB2_unicode.sql script.

v ManagerSchema__DB2_CeateFKConstraints.sql

v active_portlets.sql

Microsoft SQL Serverv ManagerSchema_SqlServer.sql

v ManagerSchema__SqlServer_CeateFKConstraints.sql


Oraclev ManagerSchema_Oracle.sql

v ManagerSchema__Oracle_CeateFKConstraints.sql


If you plan to use the scheduler feature that enables you to configure a flowchartto run at predefined intervals, you must also create the tables that support thisfeature. To create the scheduler tables, run the appropriate script, as described inthe following table.

Table 20. Scripts for enabling the IBM EMM Scheduler

Data Source Type Script Name

IBM DB2 quartz_db2.sql

Microsoft SQL Server quartz_sqlServer.sql

Oracle quartz_oracle.sql

When to use the create system tables scripts

You must use these scripts when you install or upgrade Marketing Platform if youhave not allowed the installer to create the system tables automatically, or if youhave used ManagerSchema_DropAll.sql to delete all Marketing Platform systemtables from your database.


ManagerSchema_DropAll.sqlThe ManagerSchema_DropAll.sql script removes all Marketing Platform systemtables from a database. This script removes all tables, users, groups, securitycredentials, and configuration settings from Marketing Platform.

Note: If you run this script against a database containing an earlier version of theMarketing Platform system tables, you might receive error messages in yourdatabase client stating that constraints do not exist. You can safely ignore thesemessages.

When to use ManagerSchema_DropAll.sql

You might want to use ManagerSchema_DropAll.sql if you have uninstalled aninstance of Marketing Platform where the system tables are in a database thatcontains other tables you want to continue using.

Additional requirements

To make the Marketing Platform operational after running this script, you mustperform the following steps.v Run the appropriate SQL script to re-create the system tables, as described in

“SQL scripts for creating system tables” on page 78.v Run the populateDB utility as described in “populateDb” on page 72. Running

the populateDB utility restores the default configuration properties, users, roles,and groups, but does not restore any users, roles, and groups you have createdor imported after initial installation.

v Use the configTool utility with the config_navigation.xml file to import menuitems, as described in “configTool” on page 63.

v If you have performed any post-installation configuration, such as creating datafilters or integrating with an LDAP server or web access control platform, youmust perform these configurations again.

Chapter 12. Marketing Platform SQL scripts 79


Chapter 13. Uninstalling Marketing Platform

Run the Marketing Platform uninstaller to uninstall Marketing Platform. When yourun the Marketing Platform uninstaller, the files that were created during theinstallation process are removed. For example, files such as configuration files,installer registry information, and user data are removed from the computer.

When you install IBM EMM products, an uninstaller is included in theUninstall_Product directory, where Product is the name of your IBM product. OnWindows, an entry is also added to the Add or Remove Programs list in theControl Panel.

If you manually remove the files in your installation directory instead of runningthe uninstaller, the result might be an incomplete installation if you later reinstallan IBM product in the same location. After uninstalling a product, its database isnot removed. The uninstaller only removes default files that are created duringinstallation. Any file that is created or generated after installation is not removed.

Note: On UNIX, the same user account that installed Marketing Platform must runthe uninstaller.

Complete the following tasks to uninstall Marketing Platform:1. If you have deployed the Marketing Platform web application, undeploy the

web application from WebSphere or WebLogic.2. Shut down WebSphere or WebLogic.3. Stop the processes that are related to Marketing Platform.4. If the ddl directory exists in the product installation directory, run the scripts

that are provided in the ddl directory to drop tables from the system tabledatabase.

5. Complete one of the following steps to uninstall Marketing Platform:v Double-click the Marketing Platform uninstaller that exists in the

Uninstall_Product directory. The uninstaller runs in the mode in which youinstalled Marketing Platform.

v In a command-line window, navigate to the directory where the uninstallerexists, and run the following command to uninstall Marketing Platform byusing the console mode:Uninstall_Product -i console

v In a command-line window, navigate to the directory where the uninstallerexists, and run the following command to uninstall Marketing Platform byusing the silent mode:Uninstall_Product -i silent

When you uninstall Marketing Platform by using the silent mode, theuninstallation process does not present any dialogs for user interaction.

Note: If you do not specify an option for uninstalling Marketing Platform, theMarketing Platform uninstaller runs in the mode in which Marketing Platformis installed.



Before you contact IBM technical support

If you encounter a problem that you cannot resolve by consulting thedocumentation, your company's designated support contact can log a call withIBM technical support. Use these guidelines to ensure that your problem isresolved efficiently and successfully.

If you are not a designated support contact at your company, contact your IBMadministrator for information.

Information to gather

Before you contact IBM technical support, gather the following information:v A brief description of the nature of your issue.v Detailed error messages that you see when the issue occurs.v Detailed steps to reproduce the issue.v Related log files, session files, configuration files, and data files.v Information about your product and system environment, which you can obtain

as described in "System information."

System information

When you call IBM technical support, you might be asked to provide informationabout your environment.

If your problem does not prevent you from logging in, much of this information isavailable on the About page, which provides information about your installed IBMapplications.

You can access the About page by selecting Help > About. If the About page is notaccessible, check for a version.txt file that is located under the installationdirectory for your application.

Contact information for IBM technical support

For ways to contact IBM technical support, see the IBM Product Technical Supportwebsite: (http://www.ibm.com/support/entry/portal/open_service_request).

Note: To enter a support request, you must log in with an IBM account. Thisaccount must be linked to your IBM customer number. To learn more aboutassociating your account with your IBM customer number, see Support Resources> Entitled Software Support on the Support Portal.


http://www.ibm.com/support/entry/portal/open_service_request


Notices

This information was developed for products and services offered in the U.S.A.

IBM may not offer the products, services, or features discussed in this document inother countries. Consult your local IBM representative for information about theproducts and services currently available in your area. Any reference to an IBMproduct, program, or service is not intended to state or imply that only that IBMproduct, program, or service may be used. Any functionally equivalent product,program, or service that does not infringe any IBM intellectual property right maybe used instead. However, it is the user's responsibility to evaluate and verify theoperation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matterdescribed in this document. The furnishing of this document does not grant youany license to these patents. You can send license inquiries, in writing, to:

IBM Director of LicensingIBM CorporationNorth Castle DriveArmonk, NY 10504-1785U.S.A.

For license inquiries regarding double-byte (DBCS) information, contact the IBMIntellectual Property Department in your country or send inquiries, in writing, to:

Intellectual Property LicensingLegal and Intellectual Property LawIBM Japan, Ltd.19-21, Nihonbashi-Hakozakicho, Chuo-kuTokyo 103-8510, Japan

The following paragraph does not apply to the United Kingdom or any othercountry where such provisions are inconsistent with local law: INTERNATIONALBUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS"WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED,INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OFNON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULARPURPOSE. Some states do not allow disclaimer of express or implied warranties incertain transactions, therefore, this statement may not apply to you.

This information could include technical inaccuracies or typographical errors.Changes are periodically made to the information herein; these changes will beincorporated in new editions of the publication. IBM may make improvementsand/or changes in the product(s) and/or the program(s) described in thispublication at any time without notice.

Any references in this information to non-IBM websites are provided forconvenience only and do not in any manner serve as an endorsement of thosewebsites. The materials at those websites are not part of the materials for this IBMproduct and use of those websites is at your own risk.


IBM may use or distribute any of the information you supply in any way itbelieves appropriate without incurring any obligation to you.

Licensees of this program who wish to have information about it for the purposeof enabling: (i) the exchange of information between independently createdprograms and other programs (including this one) and (ii) the mutual use of theinformation which has been exchanged, should contact:

IBM Corporation170 Tracer LaneWaltham, MA 02451U.S.A.

Such information may be available, subject to appropriate terms and conditions,including in some cases, payment of a fee.

The licensed program described in this document and all licensed materialavailable for it are provided by IBM under terms of the IBM Customer Agreement,IBM International Program License Agreement or any equivalent agreementbetween us.

Any performance data contained herein was determined in a controlledenvironment. Therefore, the results obtained in other operating environments mayvary significantly. Some measurements may have been made on development-levelsystems and there is no guarantee that these measurements will be the same ongenerally available systems. Furthermore, some measurements may have beenestimated through extrapolation. Actual results may vary. Users of this documentshould verify the applicable data for their specific environment.

Information concerning non-IBM products was obtained from the suppliers ofthose products, their published announcements or other publicly available sources.IBM has not tested those products and cannot confirm the accuracy ofperformance, compatibility or any other claims related to non-IBM products.Questions on the capabilities of non-IBM products should be addressed to thesuppliers of those products.

All statements regarding IBM's future direction or intent are subject to change orwithdrawal without notice, and represent goals and objectives only.

All IBM prices shown are IBM's suggested retail prices, are current and are subjectto change without notice. Dealer prices may vary.

This information contains examples of data and reports used in daily businessoperations. To illustrate them as completely as possible, the examples include thenames of individuals, companies, brands, and products. All of these names arefictitious and any similarity to the names and addresses used by an actual businessenterprise is entirely coincidental.

COPYRIGHT LICENSE:

This information contains sample application programs in source language, whichillustrate programming techniques on various operating platforms. You may copy,modify, and distribute these sample programs in any form without payment toIBM, for the purposes of developing, using, marketing or distributing applicationprograms conforming to the application programming interface for the operatingplatform for which the sample programs are written. These examples have not


been thoroughly tested under all conditions. IBM, therefore, cannot guarantee orimply reliability, serviceability, or function of these programs. The sampleprograms are provided "AS IS", without warranty of any kind. IBM shall not beliable for any damages arising out of your use of the sample programs.

If you are viewing this information softcopy, the photographs and colorillustrations may not appear.

TrademarksIBM, the IBM logo, and ibm.com® are trademarks or registered trademarks ofInternational Business Machines Corp., registered in many jurisdictions worldwide.Other product and service names might be trademarks of IBM or other companies.A current list of IBM trademarks is available on the Web at “Copyright andtrademark information” at www.ibm.com/legal/copytrade.shtml.

Privacy Policy and Terms of Use ConsiderationsIBM Software products, including software as a service solutions, ("SoftwareOfferings") may use cookies or other technologies to collect product usageinformation, to help improve the end user experience, to tailor interactions withthe end user or for other purposes. A cookie is a piece of data that a web site cansend to your browser, which may then be stored on your computer as a tag thatidentifies your computer. In many cases, no personal information is collected bythese cookies. If a Software Offering you are using enables you to collect personalinformation through cookies and similar technologies, we inform you about thespecifics below.

Depending upon the configurations deployed, this Software Offering may usesession and persistent cookies that collect each user's user name, and otherpersonal information for purposes of session management, enhanced user usability,or other usage tracking or functional purposes. These cookies can be disabled, butdisabling them will also eliminate the functionality they enable.

Various jurisdictions regulate the collection of personal information throughcookies and similar technologies. If the configurations deployed for this SoftwareOffering provide you as customer the ability to collect personal information fromend users via cookies and other technologies, you should seek your own legaladvice about any laws applicable to such data collection, including anyrequirements for providing notice and consent where appropriate.

IBM requires that Clients (1) provide a clear and conspicuous link to Customer'swebsite terms of use (e.g. privacy policy) which includes a link to IBM's andClient's data collection and use practices, (2) notify that cookies and clear gifs/webbeacons are being placed on the visitor's computer by IBM on the Client's behalfalong with an explanation of the purpose of such technology, and (3) to the extentrequired by law, obtain consent from website visitors prior to the placement ofcookies and clear gifs/web beacons placed by Client or IBM on Client's behalf onwebsite visitor's devices

For more information about the use of various technologies, including cookies, forthese purposes, See IBM's Online Privacy Statement at: http://www.ibm.com/privacy/details/us/en section entitled "Cookies, Web Beacons and OtherTechnologies."

Notices 87

http://www.ibm.com/legal/copytrade.shtml

http://www.ibm.com/legal/copytrade.shtml


��

Printed in USA

Documents

IBM Marketing Platform: Upgrade Guide