Upgrading the server in interactive mode
To upgrade the server, stop the server and run the new installation program.
Depending on the version of IBM® UrbanCode® Deploy you are upgrading, be sure to address these build-specific considerations.
Affected Build | Consideration |
---|---|
6.1 and later | If the server is using an IBM JRE, upgrade the JRE to a version that is shipped with V6.2 or later. |
6.1 - 6.2.3.0 | IBM UrbanCode Deploy servers and relays must be upgraded at the same time. Agents that connect through relays may not connect successfully until both server and relay are upgraded. |
6.2.2 and later | IBM UrbanCode Deploy server and agent relays require a Java™ Runtime Environment (JRE) or Java Development Kit (JDK) version 11. After upgrading, these changes apply to the agent relays. Users might notice that some agent relays are no longer listed in the user interface even though they were able to view relays before the upgrade. The new version includes updated security controls. The agent relays are still available to the users. However, System Team administrators can assign agent relays to teams and set the View Agent Relays permission for roles so that appropriate users can see the agent relays in the user interface. Users can install and use agent relays. However, the relays are not listed in the user interface for the user until a System Team administrator assigns the agent relay to teams and sets the View Agent Relays permission. |
6.1 - 6.2.1.1 | Ensure that all secure property values are obscured, the values of all properties in the history for existing deployments are obscured. In the deployment history for deployments that you run after you upgrade, only secure properties are obscured in the logs. |
6.1 - 6.2.1.1 | New security features erase old component version import logs to hide secure information. If you want to keep the logs, in the installed.properties file, set the property com.urbancode.ds.cleanup.sourceConfig.fullCleanupSkip to True. |
7.0.5 | Upgrading to V7.0.5 enables compression of new VC entries that reduces the
vc_persistent_record table growth rate. If you are using MySQL or MariaDB, then the
upgrade may take longer due to the vc_persistent_record table changes. To avoid the
delay on MySQL 5.6 or MariaDB 10.0 or later, run the following SQL statement before starting the
upgrade: ALTER TABLE vc_persistent_record MODIFY persistent_data longtext null, ADD
compressed_data longblob null, lock=none Note that you can run this command without
shutting down the IBM UrbanCode Deploy server. Attention: If the command fails, proceed with the upgrade and let the upgrade
script make these changes. In such case, the upgrade requires downtime. It is recommended to run the
command on a cloned IBM UrbanCode Deploy database to get an estimate of downtime duration. |
7.1.1 | Includes a new version of Hibernate; V5.4.20. Hibernate V5.4.20 may require newer versions of the JDBC driver in order to function properly. Ensure that you have a driver version that works with your database and is compatible with Hibernate v5.4.20. This upgrade also removes the hibernate.dialect property from the installed.properties as the new Hibernate version itself determines the dialect. |
Note:
During the upgrade , the contents of the appdata/patches directory (including all .jar files) will be appended with .off, preventing the existing test fixes from being loaded once the Server is started post-installation. All UI test fixes applied to the Tomcat directory will be wiped by the upgrade and will not be recoverable.
If a text fix received for a reported defect is not fixed in the upgraded version, you may need to open a Support Case to request a new build.
Note: Setting com.urbancode.ds.cleanup.sourceConfig.fullCleanupSkip to
True is only effective upon upgrade. After upgrading, component version import logs are
automatically cleaned up after 24 hours by default. Refer to Component Versions.