Upgrading from Contact Optimization versions 8.5.0 and later
You can run an in-place upgrade from Contact Optimization 8.5.0 and later.
*
There is no upgrade path from Contact Optimization versions previous to 8.5.0. If you must upgrade from a previous version of Contact Optimization, you must first upgrade to version 8.5.0 or 8.6.0, and then upgrade to version 9.0.0.
You do not need to migrate Contact Optimization sessions from Contact Optimization 8.5.0 and later to the new version of Contact Optimization.
Before you upgrade Contact Optimization, collect the following information:
Marketing Platform information
The installation wizards for each IBM® EMM product must be able to communicate with the Marketing Platform system table database, to register the product.
Each time that you run the installer in a new location, you must enter the following database connection information for the Marketing Platform system table database.
*
*
*
*
*
*
JDBC connection URL to the Marketing Platform database. The installer provides the connection URL based on the values you provide, however, confirm the URL is correct.
For example, for SQL Server, the JDBC connection URL takes the following format:
jdbc:sqlserver://your_db_host:your_db_port;databaseName=your_db_name
You obtained this information when you created the database or schema.
Campaign information
The installation wizard for Contact Optimization must communicate with your Campaign system table database to create the Contact Optimization tables. You must collect the following information about your installation to allow the installer to set up database tables and properly configure Contact Optimization.
*
Whether your Campaign database is configured for Unicode.
*
Campaign database type.
If your database type is IBM® DB2® and installed on a UNIX system, you must also supply the DB2® instance path.
If your database type is Oracle, you must also supply the Oracle home directory.
*
Campaign database host name.
*
Campaign database port.
*
Campaign database name.
*
User name and password for the Campaign database account.
*
JDBC connection URL to the Campaign database. The installer provides the connection URL based on the values you provide, however, confirm the URL is correct.
For example, for SQL Server, the JDBC connection URL takes the following format:
jdbc:sqlserver://your_db_host:your_db_port;databaseName=your_db_name
*
The name of the system on which the Campaign web application server is installed.
*
The port on which the Campaign application server listens. If you plan to implement SSL, obtain the SSL port.
*
*
The path to CAMPAIGN_HOME.
If you are installing Contact Optimization and Campaign on separate systems, you must mount the Campaign directory for your Campaign installation as a network drive on the system that hosts Contact Optimization. The svrstop utility in the bin directory must have execute permissions on the Contact Optimization host. Define CAMPAIGN_HOME with the fully qualified path to your Campaign installation directory.
The new version of Contact Optimization has new configuration properties for tuning the optimization algorithm in the AlgorithmTuning category. The configuration properties are added when you upgrade Campaign. You do not need to modify these properties unless you want to tune your Contact Optimization installation for best performance. For details about tuning your installation, see the IBM® Contact Optimization User's Guide and the IBM® Contact Optimization Troubleshooting Guide.
1.
Stop the Contact Optimization listener.
2.
Run the new IBM® EMM installer, selecting Contact Optimization.
*
Select your previous Contact Optimization installation directory, for example C:\IBM\Optimize.
When prompted, select the Automatic database setup.
3.
Start the Contact Optimization listener.
In the latest version of Contact Optimization, the ACOServer script provides options to start and stop the Contact Optimization listener. This script is in the bin directory of your Contact Optimization installation.
On Windows: ACOserver.bat start
On UNIX: ACOserver.sh start
4.
Perform the following steps for all Contact Optimization sessions that are using session level advanced settings:
a.
b.
Saving the settings ensures that the session level advanced settings of the current optimization session are retained during the upgrade. If you do not save the advanced settings, ContinueOnGenerationLoopError might behave as if it is set to False, even if ContinueOnGenerationLoopError is set to True.