Procedure: Fast upgrade Interact
Before you begin
Pre-requisites to upgrade from Interact 8.6.x/later version to Interact 11.1.x:
Procedure
- Ensure that Platform and Campaign are upgraded successfully on the target setup. Install Interact 11.1.x on the setup.
- Take a Backup for source system Databases InteractDT, InteractRT,Interact Learning, Interact prod
- Make sure that the Interact related files in Campaign's 'partition' folder are copied from the source system to the target system.
- Restore the backed up database schema on target system.
- Create data sources on the target application server and point to the new database schema. You can use the same JNDI names as those in the source system to save effort in doing manual changes.
Upgrading Interact DT
Procedure
-
Update setenv.sh with the values required for upgrade. For details on the environment variables
in the setenv.sh file, refer to the Interact Upgrade guide.
- Pre-requisite to complete before running the Interact upgrade tool:Update the jdbc.properties file under:1. <Installation_Home>\install\2. <Interact_Home>\interactDT\tools\upgrade\conf The “jdbc.properties" file must contain the correct JDBC URL, Platform system database userID and encrypted password.If this information is incorrect, then the Interact upgrade tool will fail with database authentication related errors.
- Execute Interact “aciUpgradeTool.sh/bat?. This Upgrade tool execution is similar to the usual acUpgradeToolexecution of Campaign.
- While executing the upgrade tool you are prompted for database details. Enter the Interact DesignTime Database details.
- The tool will also prompt for “select base version to upgrade". You will able to see the upgrade version specified for CHOICES_FOR_PREVIOUS_VERSIONS. Select the fast upgrade base version to upgrade from.
- Once the upgrade tool execution completes, check the related logs to ensure that no errors were encountered during the upgrade tool execution.
Upgrading Interact RT, Interact learning and Interact Production databases
Procedure
-
Update setenv.sh with required values for Interact upgrade. For details on the environment
variables in the setenv.sh file, refer to the Interact Upgrade guide.
- Pre-requisite to complete before running the Interact upgrade tool: Update the jdbc.properties file under:1. <Installation_Home>\install\2. <Interact_Home>\tools\upgrade\confThe “jdbc.properties? file must contain the correct JDBC URL, Platform system database userID and encrypted password.If this information is incorrect, the Interact upgrade tool will fail with database authentication related errors.
-
Execute Interact “aciUpgradeTool_crhtab .sh/bat? . This Upgrade tool execution is similar to
the usual aciUpgradeTool.
- While executing the upgrade tool you are prompted for database details. Please mention the details of the Interact DesignTime Database. The tool will also prompt for “select base version to upgrade?. You will see the upgrade version specified with CHOICES_FOR_PREVIOUS_VERSIONS= . Select the fast upgrade base version you are upgrading from.
- Once the upgradetool execution completes, check the related logs and ensure that no errors were encountered during the upgrade tool execution.
-
Execute Interact “aciUpgradeTool_runtab.sh/bat?. This Upgrade tool execution is similar to the
usual aciUpgradeTool.
- While executing the upgrade tool you are prompted for database details. Enter the Interact RunTime Database details.The tool will also prompt for “select base version to upgrade?, you can see the upgrade version specified in CHOICES_FOR_PREVIOUS_VERSIONS. Select the fast upgrade base version you are upgrading from.
- Once the upgradetool execute completes, check the related logs and ensure that no errors were encountered during the upgrade tool execution.
-
Execute Interact “aciUpgradeTool_lrntab .sh/bat?. This Upgrade tool execution is similar to the
usual aciUpgradeTool.
- While executing the upgrade tool you are prompted for database details. Enter the Interact Learning Database details.The tool will also prompt for “select base version to upgrade?. You can see the upgrade version specified with CHOICES_FOR_PREVIOUS_VERSIONS. Select the fast upgrade base version to upgrade from.
- Once the upgradetool execution completes, check the related logs and ensure that errors were not encountered during the upgrade tool execution.
-
Execute Interact “aciUpgradeTool_usrtab.sh/bat?. This Upgrade tool execution is similar to the
usual aciUpgradeTool.
- During the execution of the upgrade tool, you are prompted for database details. Enter the Interact Production/prod Database details.The tool will also prompt for “select base version to upgrade?. You can see the upgrade version specified with CHOICES_FOR_PREVIOUS_VERSIONS.Select the fast upgrade base version to upgrade from.
- Once the upgradetool execution completes, check the related logs and ensure no errors were encountered during the upgrade tool execution.
Updating the JDBC file in InteractRT WAR
About this task
Procedure
- Back up the interactRT.war file from the 11.1 environment (Interact/interactRT.war).
- Unwar the interactRT.war file.
- Copy the jdbc.properties file from Platform/tools/bin/ directory and paste it under interactRT.war/WEB-INF/classes.
- Re-war the interactRT.
Post Upgrade
Procedure
-
Interact version registration:
- You need to remove the old Interact navigation and add a new one. Please execute the following commands on the destination 11.1 environment:Remove old menu:configTool.bat -d -p "Affinium|suite|uiNavigation|mainMenu|Campaign|Interactive Channels" -oAdd the new menu:configTool.sh/bat -i -p "Affinium|suite|uiNavigation|mainMenu" -f"full_path_to_Interact_installation_directory/conf/interact_navigation.xml"
- If you are upgrading from 11.0 to 11.1 then follow below steps: a. Remove the 11.0 menu using : ./configTool.sh -d -p "Affinium|suite|uiNavigation|mainMenu|Interact" -o b. Add 11.1 menu using : ./configTool.sh -i -p "Affinium|suite|uiNavigation|mainMenu|" -f /opt/Install_Home/Interact/interactDT/conf/interact_navigation.xml
- Platform – DBResourceBundle: The steps underneath will import resource bundles in Marketing Platform. Execute the script underneath as specified: a. Navigate to <platform_home>/tools/binb. DBResourceBundle.sh /bat -P interact-F <Interact_home>/resourcebundles
- If you have added any custom entries in the 'interact_log4j.xml' file on source 8.6 setup, then you will need to copy those custom entries into the target 'interact_log4j2.xml' file.
- If you have added any custom entries in the 'interact_log4j.xml' file on source 8.6 setup, then you will need to copy those custom entries into the target setup in the newly added 'interact_log4j2.xml' file.
- Deploy Interact RT WAR file
- Update the configuration instanceURLs accordingly for your ServerGroup defined at Affinium|Campaign|partitions|partition1|Interact|serverGroups
The second Interact runtime
Procedure
- Repeat the following steps for each Interact runtime if you have used a different server group and Platform.
- Install New Platform 11.1 with Interact RT.
- Perform the Platform upgrade and make the setup ready. (Refer the Platform Upgrade Guide.)
- Copy and restore the InteractRT database from the source to the target.
- Upgrade the database from source database to 11.1 by running the aciupgrade utility for RT.
- Create data sources on the target application server using the same JNDI names as the source setup.
- Deploy InteractRT.war.
Important
CFS updates: If the customer is using SOAP, then generate the proxy code based on the new WSDL and rebuild the CFS code using the new proxy.
Note
1. After Upgrade, it is observed that a Configuration Node sessionManagement is displayed
under:Affinium|interact|
Removal of this configuration can
be done using the Platform configTool.sh/configTool.bat tool.2. After
upgrade, it is observed that configuration Node treatmentStore is displayed
under:Affinium|Interact|services|contactHist|
Removal of
this configuration can be done using the Platform configTool.sh/configTool.bat tool3.
In case, after deployment during access, you encounter the "DB2 SQL Error: SQLCODE=-668,
SQLSTATE=57016, SQLERRMC=7" error, then contact your DBA and run the REORG query on the necessary
database tables.4. Removal steps are not applicable if you are upgrading from 11.0 to
11.1.