Upgrading Opportunity Detect from version 10.1 with automatic migration

Automatic migration allows the installer to run the SQL scripts and insert the configuration properties that are required to upgrade your Marketing Platform system tables. If your company policy does not allow automated updates to your system table database, you must use manual migration, described elsewhere in this guide.

Before you begin

Note: Important: If you are upgrading from a version prior to 10.1, you must first upgrade to version 10.1 and then upgrade to version 11.0. For information about upgrading to version 10.1, see the HCL Opportunity Detect 10.1 Upgrade Guide.

Ensure that you have the following installers in the same directory.

The HCL® Marketing Software master installer
The Opportunity Detect installer

Use the following guidelines as a best practice.

Place the installers in the same directory where you originally placed the installers for the earlier versions of your products.
Remove any earlier versions of the HCL Marketing Software product installers from the directory to avoid having the master installer attempt to install the earlier versions.

About this task

Upgrading from version 10.1 is an in-place upgrade. In an in-place upgrade, you install the new version of Opportunity Detect to the directory where your current version of Opportunity Detect is installed.

See Opportunity Detect and Interact Advanced Patterns upgrade scenarios for information about upgrading from other versions.

Note: If you are changing your database type, data migration is not supported. Perform a complete installation in a new location instead.

Procedure

Ask all users to log out of Opportunity Detect and stop all running services, including StreamsRCS, Interact Design Service, Real Time Connector, and the Streams instance.
Create a back-up copy of your Opportunity Detect system table database.

Important: Do not skip this step. If the upgrade operation fails, you cannot roll back your database and your data is corrupted.
Undeploy Opportunity Detect in your web application server.
Run the HCL Marketing Software master installer.
The HCL Marketing Software master installer starts. Complete the following steps in the HCL Marketing Software master installer.
- On the HCL Marketing Software Products window, do the following.
  - De-select HCL® Marketing Platform 11.0
  - Select HCL Opportunity Detect 11.0
- When the HCL Marketing Software master installer prompts you to choose an installation directory, choose the HCL Marketing Software installation directory, not the Opportunity Detect installation directory, which is under this root directory.
- When the HCL Marketing Software master installer prompts you to enter Marketing Platform database connection information, enter the information that pertains to your current Marketing Platform system tables.
The HCL Marketing Software master installer pauses and launches the Opportunity Detect installer.
Complete the following steps in the Opportunity Detect installer.
1. When the Opportunity Detect installer prompts you for an installation directory, select the directory of your current Opportunity Detect installation.
2. Allow the installer to create a back-up copy of your previous installation of Opportunity Detect.
3. On the Opportunity Detection Components window, select the components you want to install.
  
  You can run the installer multiple times to install components on different hosts.
4. On the DesignTime Database Setup window, select Automatic database setup.
5. Follow the remaining steps in the installation wizard and enter the requested information.
  
  Note: Pay close attention to the installation summary windows. If errors are reported, check the installer log files and contact HCL technical support if necessary.
If you are using DB2 for your system tables, and if you have installed the DB2 client in a location that is different from the default location, you must update the function.xml file as follows.

The function.xml file is located in the /home/streamsadmin/OpDetection/toolkits/unica_db_access/db.access/native.function directory.
1. Locate the following section in the file.
```
<library>
   <cmn:description></cmn:description>
      <cmn:managedLibrary>
         <cmn:lib>UnicaDatabaseAccessLib</cmn:lib>
         <cmn:lib>db2</cmn:lib>
         <cmn:libPath>../../impl/lib</cmn:libPath>
         <cmn:libPath>/IBM_DB2_installation_directory/
                lib64</cmn:libPath>
         <cmn:includePath>../../impl/include</cmn:includePath>
         <cmn:includePath>/IBM_DB2_installation_directory/
                include</cmn:includePath>
      </cmn:managedLibrary>
</library>
```
2. Correct the path in the following lines to reflect the location of your DB2 client. In the following example, the DB2 install path is /data/dbclient/DB2.
  
  <cmn:libPath>/data/dbclient/DB2/lib64</cmn:libPath>
  
  <cmn:includePath>/data/dbclient/DB2/include</cmn:includePath>
If you are using Interact Advanced Patterns, run the following update statements against your system table database.

update DeploymentConfiguration set inputMode = 3;

update DeploymentHistory set inputMode = 3;

These statements set the input mode to TCP.
If you are using Opportunity Detect and use the Web Service connector, run the following update statements against your system table database.

update DeploymentConfiguration set inputMode = 2;

update DeploymentHistory set inputMode = 2;

These statements set the input mode to Web.

What to do next

Complete post-installation steps as described elsewhere in this guide.