Procedure: Fast upgrade Unica Plan
Plan pre-upgrade
About this task
- Existing customers who want to upgrade to JBOSS + 12.0, must perform the following steps:
- Clear the recent items for all the users. Note: Administrator: Please communicate to all the users to clear their respective recent items prior to the migration to JBOSS.
- Clear the directory <plan_home>/recentdata.
- Migrate to JBOSS + 12.0.
- No change is required to be done by new customers who are installing JBOSS + 12.0. This is because recent items will not be present in their case.
- No change is required to be done by new customers who are installing JBOSS + 12.0. This is because recent items will not be present in their case.
Procedure
Upgrading Unica Plan
Updating JDBC files
About this task
Procedure
Upgrade to 12.0 config
About this task
Procedure
Upgrading Plan database
Procedure
Import the database with the source system tables of the VM containing
the fresh installation of 12.0 Plan.
Unica Plan post-upgrade
Unica Plan Configuration changes
About this task
Note:
About log4j upgrade
Prior to 12.0 log4j1x API was used by Plan source (config file being used for that was plan_log4j.xml).
With 12.0
- log4j2x API is used by Plan source (config file being used for that is plan_log4j.xml for fresh install and plan_log4j.12.0.xml for upgrade).
- log4j1x API is still used by unica_common.jar inside Plan JVM since Platform source (which results in unica_common) has not been changed to use log4j2x.
Hence additionally we also ship plan_log4j_1x.xml which is as per the log4j1x syntax . This file is not used by source code in Unica Plan.
With 12.0, you must not use existing system properties related to log4j1x setting and instead use the new additional system properties.
Procedure
Setting the Plan – Help About > Version
About this task
Procedure
Plan Post Upgrade Functional check
About this task
Perform UAT on the plan application. Ensure that all the Plans, Programs, Projects, Tasks, Approvals are opening and that the data is successfully imported. Ensure if all the configurations nodes are available.