To upgrade the server, stop the server and run the new installation program.
Before you begin
If you are upgrading from version 4.8.5 or later but before 6.0, migrate the security
before you upgrade the server. See Migrating security settings.
If you are upgrading from a version prior to 6.2 to version 6.2 or later, and the server is
using an IBM JRE, upgrade the JRE to a version that is
shipped with version 6.2 or later.
Important: If you
are upgrading from version 6.2.3.0 and earlier, 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.
Important: Beginning in version 6.2.2, the IBM UrbanCode Deploy server and agent relays require Java™ Runtime Environment
(JRE) or Java Development Kit (JDK) version 8.
Important: After you upgrade to IBM UrbanCode Deploy version
6.2.2 or later, note these changes to 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.
If you have added custom keystores, certificates, or any other files to the
server_install/opt/tomcat directory, back up
those files before you upgrade. If you do not back up files that you have added to the
server_install/opt/tomcat directory, those files
are removed when the upgrade process runs.
Important: The artifact format changed in version 6.1. If you are upgrading from a
version before 6.1 to 6.1 or later, the amount of disk space that is used during the upgrade
is temporarily increased. Typically, the amount of space that is used is double the amount
that is normally used by artifacts. After the upgrade is complete, older artifact versions
are removed and the amount of storage is usually equivalent to the amount used before the
upgrade. This disk space requirement affects only upgrades of versions before 6.1 to 6.1 or
later. See
Automatic upgrades of files stored in the server CodeStation.
Important: If you are upgrading to version 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.
Important: If you are upgrading from versions before 6.2.1.1, to 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.
About this task
You can upgrade the server to version 6.0 or later from versions 4.8.5 or 5.0. If you use a
version before 4.8.5, you must upgrade to 5.0 first.
What to do next
If you are upgrading from version 6.2.3.0 to 6.2.3.1 or later, upgrade all
agent relays to the current version. Agents that connect through relays may not connect
successfully until both server and relay are upgraded.