Upgrading to the latest version of Data360 Analyze - Data360_Analyze - 3.20

Data360 Analyze Server Installation
Product type
Software
Portfolio
Verify
Product family
Data360
Product
Data360 Analyze
Version
3.20
ft:locale
en-US
Product name
Data360 Analyze
ft:title
Data360 Analyze Server Installation
Copyright
2025
First publish date
2016
ft:lastEdition
2026-07-17
ft:lastPublication
2026-07-17T15:06:17.073000
L1_Product_Gateway
Verify
L2_Product_Segment
Data Quality
L3_Product_Brand
Precisely Infogix
L4_Investment_Segment
Data 360
L5_Product_Group
Data 360
L6_Product_Name
Analyze

If you do not have an existing installation of Data360 Analyze, see Downloading and installing Data360 Analyze.

During the upgrade process, you will be prompted to choose whether to install Python 2.
  • Select this option if your data flows use Python 2-based nodes.
  • Deselect this option if you do not use Python 2-based nodes. (Recommended, as Python 2 is deprecated.)
    Important: If Python 2 is already installed in your existing installation, it will remain selected by default during the upgrade.
Note: You cannot choose to install or remove Python2 after installing Data360 Analyze. If you want to do so later, you must restore from a pre-installation backup and select or deselect Python2 option accordingly.
Warning: Do not stop the web application process during the first boot after upgrading Data360 Analyze. Crucial upgrade operations occur during this time and may take a while. Interrupting the process could leave the system in an unstable state, requiring rollback and re-upgrade.

Prerequisites

  • Consider turning off any anti-virus software that may interrupt the installation process.

  • If you have specified a custom version of ls.brain.tempDir in the <Data360 Analyze site directory>/cust.prop, remove this line from the <Data360 Analyze site directory>/cust.prop and instead set this as the value of the ls.host.brain.tempDir property in the <Data360 Analyze site directory>/cust.prop file.
  • Locate the value of the ls.lae.shareRootDir property in the <Data360 Analyze site directory>/cust.prop and set this as the value of the ls.host.lae.shareRootDir property in the <Data360 Analyze site directory>/cust.prop. Remove the line for the ls.lae.shareRootDir from the <Data360 Analyze site directory>/cust.prop. Note that failing to update the property in the cust.prop and remove the entry from the cust.prop will only cause a problem if you are intending on using execution sandboxing and you are either on Windows or have changed the location from the default.
  • Ensure that you have enough space available for the Postgres database upgrade. During upgrade, Postgres requires 1.5 times the disk space of the current Postgres database size.

Manual HTTPS configuration requirement for upgrades from versions earlier than 3.20.0

Important: If you are upgrading from a version of Data360 Analyze earlier than 3.20.0, you must manually update the HTTPS connector configuration in the server.xml file. Starting with version 3.20.0, the application uses an updated HTTPS configuration based on Tomcat’s <SSLHostConfig> and <Certificate> elements. HTTPS connector settings from older versions might not be migrated automatically during the upgrade process. To update the HTTPS configuration, follow the instructions in the Enable HTTPS topic in the Data360 Analyze Server Help:
  • For self‑signed .cer certificates: see the updated configuration in Step 6.
  • For .pfx certificates: see the updated configuration in Step 8.
  • For .pfx or .p12 file directly in Tomcat: see the updated configuration in Step 3.
If you do not apply these updates, HTTPS will not function correctly after the upgrade.

Breaking changes

  • The Microsoft SQL Server JDBC driver shipped with the installation has been upgraded from 9.X to 12.X. Note that the default for the 12.X drivers is to have TLS enabled. To disable TLS set the DBOptions property on the JDBC related nodes to encrypt=false. If using a self-signed certificate for SQL Server, DBOptions will need to be set to trustServerCertificate=true
  • The MariaDB driver has been updated from version 2.7.X to 3.3.X, introducing several changes to the JDBC URL parameters. While the 2.7.X version is still included with the product and supported by the MariaDB project, it can be set as the default version for Data360 Analyze installation. However, the 2.7.X version will reach end of life in 2025, after which it will no longer be supported by Data360 Analyze.

    For more information, see MariaDb Connector/J.