Procedure: Fast upgrade Unica Platform
Unica Platform pre-upgrade
Before you begin
About this task
Upgrading the Unica Platform database manually
You should manually execute the following scripts provided in the table underneath on the Unica Platform database while upgrading from various base versions:
Version | SQL scripts to execute |
8.6.x to 12.1.0 |
SQL Server
|
8.6.x to 12.1.0 |
Oracle
|
8.6.x to 12.1.0 |
DB2
OR if Unicode environment execute:
Or if Unicode environment execute:
Or if Unicode environment execute: <
Or if Unicode environment execute:
Or if Unicode environment execute:
Or if Unicode environment execute:
Or if Unicode environment execute:
Or if Unicode environment execute:
|
9.0.x to 12.1.0 |
SQL Server
|
9.0.x to 12.1.0 |
Oracle
|
9.0.x to 12.1.0 |
DB2
OR if Unicode environment execute: <PLATFORM_HOME>/db/upgrade90to91/ManagerSchema_DB2_91upg_unicode.sql
OR if Unicode environment execute: <PLATFORM_HOME>/db/ upgrade91to911/ManagerSchema_DB2_911upg_unicode.sql
OR if Unicode environment execute: <PLATFORM_HOME>/db/upgrade912to10/ManagerSchema_DB2_10upg_unicode.sql
OR if Unicode environment execute: <PLATFORM_HOME>/db/upgrade10001to10002/ManagerSchema_DB2_10002upg_unicode.sql
OR if Unicode environment execute: <PLATFORM_HOME>/db/ upgrade10002to101/ManagerSchema_DB2_101upg_unicode.sql
OR if Unicode environment execute: <PLATFORM_HOME>/db/ upgrade101to11/ManagerSchema_DB2_11upg_unicode.sql
Or if Unicode environment execute:
|
9.1.x to 12.1.0 |
SQL Server
|
9.1.x to 12.1.0 |
Oracle
|
9.1.x to 12.1.0 |
DB2 <PLATFORM_HOME>/db/upgrade91to911/ManagerSchema_DB2_911upg.sql OR if Unicode environment execute: <PLATFORM_HOME>/db/ upgrade91to911/ ManagerSchema_DB2_911upg_unicode.sql <PLATFORM_HOME>/db/upgrade912to10/DB2_QRTZ_Scheduler_10_upggrade_Script.sql <PLATFORM_HOME>/db/upgrade912to10/ManagerSchema_DB2_10upg.sql OR if Unicode environment execute: <PLATFORM_HOME>/db/upgrade912to10/ ManagerSchema_DB2_10upg_unicode.sql <PLATFORM_HOME>/db/upgrade10001to10002/ManagerSchema_DB2_10002upg.sql OR if Unicode environment execute: <PLATFORM_HOME>/db/upgrade10001to10002/ManagerSchema_DB2_10002upg_unicode.sql <PLATFORM_HOME>/db/ upgrade10002to101/ ManagerSchema_DB2_101upg.sql OR if Unicode environment execute: <PLATFORM_HOME>/db/ upgrade10002to101/ ManagerSchema_DB2_101upg_unicode.sql <PLATFORM_HOME>/db/upgrade101to11/ManagerSchema_DB2_11upg.sql OR if Unicode environment execute: <PLATFORM_HOME>/db/ upgrade101to11/ManagerSchema_DB2_11upg_unicode.sql <PLATFORM_HOME>/db/upgrade111to11102/ManagerSchema_DB2_11102upg.sql <PLATFORM_HOME>/db/upgrade11102to12/ManagerSchema_DB2_12upg.sql <PLATFORM_HOME>/db/ upgrade12to121/ ManagerSchema_DB2_121upg.sql OR if Unicode environment execute: <PLATFORM_HOME>/db/upgrade11102to12/ManagerSchema_DB2_12upg_unicode.sql <PLATFORM_HOME>/db/ upgrade12to121/ ManagerSchema_DB2_121upg_unicode.sql |
9.1.1.x to 12.1.0 |
SQL Server
|
9.1.1.x to 12.1.0 |
Oracle
|
9.1.1.x to 12.1.0 |
DB2
OR if Unicode environment execute: <PLATFORM_HOME>/db/upgrade912to10/ManagerSchema_DB2_10upg_unicode.sql
OR if Unicode environment execute: <PLATFORM_HOME>/db/upgrade10001to10002/ManagerSchema_DB2_10002upg_unicode.sql
OR if Unicode environment execute: <PLATFORM_HOME>/db/ upgrade10002to101/ManagerSchema_DB2_101upg_unicode.sql
OR if Unicode environment execute:
<PLATFORM_HOME>/db/upgrade111to11102/ManagerSchema_DB2_11102upg.sql <PLATFORM_HOME>/db/upgrade11102to12/ManagerSchema_DB2_12upg.sql <PLATFORM_HOME>/db/ upgrade12to121/ ManagerSchema_DB2_121upg.sql OR if Unicode environment execute:
|
9.1.2.x to 12.1.0 |
SQL Server
|
9.1.2.x to 12.1.0 |
Oracle
|
9.1.2.x to 12.1.0 |
DB2
OR if Unicode environment execute: <PLATFORM_HOME>/db/upgrade912to10/ManagerSchema_DB2_10upg_unicode.sql
OR if Unicode environment execute: <PLATFORM_HOME>/db/upgrade10001to10002/ManagerSchema_DB2_10002upg_unicode.sql
OR if Unicode environment execute: <PLATFORM_HOME>/db/ upgrade10002to101/ManagerSchema_DB2_101upg_unicode.sql
OR if Unicode environment execute: <PLATFORM_HOME>/db/ upgrade101to11/ManagerSchema_DB2_11upg_unicode.sql
Or if Unicode environment execute:
|
10.0.x to 12.1.0 |
SQL Server
|
10.0.x to 12.1.0 |
Oracle
|
10.0.x to 12.1.0 |
DB2
OR if Unicode environment execute: <PLATFORM_HOME>/db/upgrade10001to10002/ManagerSchema_DB2_10002upg_unicode.sql
OR if Unicode environment execute: <PLATFORM_HOME>/db/ upgrade10002to101/ManagerSchema_DB2_101upg_unicode.sql
OR if Unicode environment execute: <PLATFORM_HOME>/db/ upgrade101to11/ManagerSchema_DB2_11upg_unicode.sql
OR if Unicode environment execute:
|
10.1.0 to 12.1.0 |
SQL Server
|
10.1.0 to 12.1.0 |
Oracle
|
10.1.0 to 12.1.0 |
DB2
OR if Unicode environment execute: <PLATFORM_HOME>/db/ upgrade101to11/ManagerSchema_DB2_11upg_unicode.sql
Or if a Unicode environment exceute:
|
11.0.x to 12.1.0 |
SQL Server
Oracle
DB2
Or if a unicode environment exceute
|
11.1.0 to 12.1.0 |
SQL Server
Oracle
DB2
Or if a unicode environment exceute
|
11.1.0.2 to 12.1.0 |
SQL Server
Oracle
DB2
Or if a unicode environment exceute
|
12.0.0 to 12.1.0 |
SQL Server
Oracle
DB2
Or if a unicode environment exceute
|
Updating the JDBC files in Unica Platform
About this task
- Export the version configuration using the following command on clean 12.1
environment.
./configTool.sh -x -p "Affinium|Manager|about" -f "<PLATFORM_HOME>/conf/about.xml"
- Take a back up the jdbc.properties file from the 12.1.0 environment
(Platform/tools/bin/jdbc.properties). Update the username in the 12.1.0
platform system database / schema name in jdbc.properties file.
Example of jdbc.properties:
uasm.jdbc_driver=com.ibm.db2.jcc.DB2Driver
uasm.data_source=jdbc:db2://<DB_HOST>:<DB_PORT>/<DB2_SID>
uasm.data_source_login=<PLATFORM_DB_SCHEMA>
uasm.data_source_password=ENC(T+rsrWP41Vqu8SoDARMhDdWkf0dFB0Zc) hibernate.dialect=org.hibernate.dialect.DB2Dialect
- To update the encrypted password in the jdbc.properties file run the
following command:Navigate to Platform/tools/bin directory and execute the
below command:
./encryptPasswords.sh –d <PLATFORM_DB_USER_PASSWORD>
This will update the encrypted password in the jdbc.properties file. Save the Platform/tools/bin/jdbc.properties with this encrypted password of the new schema user.
- In the application server, update the JNDI details (schema / SID, userid, password) for Platform JNDI as per the new database schema used with v12.1.0 environment.
Upgrading the Unica Platform configuration
Procedure
-
Execute the following command to upgrade Unica Platform configurations to
12.1.0:
Navigate to <UNICA_PLATFORM_HOME>/tools/bin directory
Execute command:
./configTool.sh -vp -p "Affinium" -f "<UNICA_PLATFORM_HOME>/conf/Manager_config.xml"
Note: You may encounter an insertion of duplicate key related error or com.ibm.db2.jcc.am.SqlIntegrityConstraintViolationException:
See the Troubleshooting section.
- Execute the command: ./populateDb.sh -n Manager
-
Execute the command:
./configTool.sh -vp -p "Affinium|suite|uiNavigation|mainMenu|Analytics" -f "<PLATFORM_HOME>/conf/watsonAssistant_navigation.xml"
-
Execute the command: ./alertConfigTool.sh -i -f
"<UNICA_PLATFORM_HOME>/conf/Platform_alerts_configuration.xml"
Note: If upgrading from version 11.0.1, then do not execute the below scripts(step 5,6,7).
-
Execute the command: ./configTool.sh -vp -p
"Affinium|Report|integrations" -f
“<UNICA_PLATFORM_HOME>/conf/upgrade101to11/cognos11_integration.xml"
Note: If upgrading from version 8.6.0, execute steps 6 and 7.
- Execute the command: upgrade86to90(Only Upgrading from version 8.6.0)
- Execute the command: upgrade90to91(Only Upgrading from version 9.0)
-
Upgrade the scheduler jobs.
Use the quartzjobtool to update scheduler jobs. This is a required step. If this upgrade tool is not run, any existing scheduled job fails to start. The quartzjobtool is in the tools\bin directory under Unica Platform installation. Run this utility from the tools\bin directory.
Example command (Windows):
quartzjobtool.bat
Example command (Unix):
./quartzjobtool.sh
-
For Unica Insights users, execute the following command.
configTool -vp -p "Affinium" -f <Insights.xml directory_path>/Insights.xml(Insights.xml directory_path : /opt/HCL/Unica_12/Platform/Insights/conf)
If you are upgrading from version 12.0 and Birt is installed, do not run Insights.xml as it is handled by populateDb utility.
-
Execute the command:
./configTool.sh -vp -p "Affinium|suite|security" -f "/<UNICA_PLATFORM_HOME>/conf/upgrade12to121/APISecurity.xml"
-
Execute the command for Deliver:
./configTool.sh -vp -p "Affinium|suite|security|apiSecurity" -f "<UNICA_PLATFORM_HOME>/Platform/conf/upgrade12to121/APISecurity_Deliver.xml"
-
Execute the following command for Licensing:
./configTool.sh -vp -p "Affinium|suite|uiNavigation|settingsMenu" -f "<UNICA_PLATFORM_HOME>/conf/upgrade12to121/LicenseDeatilsNavigation.xml"
Setting the Unica Platform – Help About > Version
Procedure
- Import the about.xml edited file using the following command: ./configTool.sh -v -i -o -p "Affinium|Manager" -f <PLATFORM_HOME>/conf/about.xml.
-
Edit the exported about.xml.
<property id="xxxxxx" name="releaseNumber" type="string_property" width="40"> <value>12.1.0.0.GA_BUILD</value> </property>
Unica Platform post-upgrade
Procedure
- Unica Platform application navigation URL points to the old base environment. You must change the navigation URL using the SQL script from the Platform system database.
- The URL of the start page that appears when each users log in to HCL Unica products has to be changed manually from the USM_PERSONALIZATION table.
-
Check the following properties files from the source and destination
Environment. Copy all the urls mentioned in the respective properties files
from source to destination files.
1.Platform_Admin_URL.properties
2.Platform_Admin_View_Priv.properties
3.Platform_Admin_URL.properties
4.Platform_Admin_Scheduler_Scripts.properties
5.Platform_Admin_Scheduler_API.properties
- Perform UAT on Unica Platform application. Make sure all the functions are working correctly.
- If you configure Platform login method different than Platform login method, ensure that it is correctly configured and creating the expected number of users. Then you can proceed to next step and register licenses on your production server.