To upgrade the server, stop the server and run the new
installation program. These instructions apply to upgrades to versions
6.0 and later.
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 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.
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.
Procedure
- Download and extract the installation files
for IBM UrbanCode Deploy.
These files are available for download from the IBM Passport Advantage® website. See the IBM UrbanCode Deploy download
document.
- Ensure that no application and generic processes are running. Open the Dashboard and confirm that no processes are running. If
processes are running, you can wait for them to complete or by clicking
Cancel in the same row as each process, cancel them.
- Stop the server.
- Ensure that the server is stopped:
- Check to ensure that there is no file server.pid in the
server_install/var folder.
- Check for running processes by using the netstat command. For example, if the server is running on port 8443, use the command netstat -nap |
grep 8443.
- If any server processes are still running, stop them.
If a server process is still running, when you install the new version, you see an
error that says "A previously installed version of IBM UrbanCode Deploy is running. Please shutdown the running IBM UrbanCode Deploy and start the installation again."
- If you are upgrading from a version before 6.1.1.5 and you are using high availability,
update the network storage to match the folders in the new version. For information about how to structure the folders, see Setting up high-availability clusters.
Depending on how you set up network storage
for the high-availability cluster in the previous version, you might need to move files
and folders to put them in the place that the new version of the server expects to find
them. When you run the installation program, specify the location of the
app_data folder in the Where should the server store application data such as logs,
plugins, and keystores?
prompt.
For more information, see Setting up high-availability clusters.
- From the command line, run the server
installer program.
Depending on your system settings, you might need to run this
file as an administrator.
- Read the license agreements for the software
package. Press Enter to show one page at a time, or press F and then
press Enter to show the entire license at once.
- If you agree to the terms of all of the license
agreements, press Y and then press Enter.
- At the prompt that says Enter the directory
where the IBM UrbanCode Deploy server
should be installed., specify the folder of the existing
installation and press Enter.
- At the prompt that says A previous version exists
in the specified directory. Do you want to upgrade the currently installed
version? press Y and then press Enter.
- Verify that the server is stopped and then press Enter
to start the upgrade process.
- Start the server and verify that the server has been migrated.
- Ensure that licensing is set up for the server. See License management.
- Optional: If you are upgrading the server from
version 6.0.1.1 or earlier to a version later than version 6.0.1.1,
upgrade the encryption key strength. See Upgrading encryption key strength.
- Optional: Upgrade the agents. See Upgrading agents. If you are upgrading from a version before 6.1.0.4 to
version 6.1.0.4 or later, you must upgrade agents that use Java™ plug-ins, including most source configuration plug-ins. If you do not upgrade the agents,
they will throw an IllegalCharsetNameException exception that refers to the variable
DS_SYSTEM_ENCODING.
What to do next
When you run
the server for the first time, you might see an error message that
says that no agent or tag is configured to import new component versions.
To import component versions, including built artifacts, you must
use an agent, and the server requires that you specify a default agent
for this purpose. You can override this default setting when you create
a component. Follow these steps to specify a default agent or agent
tag:
- To specify a default agent, click and under General
Settings, clear the Use Agent Tag For Integration check
box. Then, select an agent in the Agent for Version Imports list.
Then, at the bottom of the page, click Save.
- To specify a default agent tag, click and under General Settings, clear the Use Agent Tag
For Integration check box. Then, select an agent tag in the Agent Tag for
version imports list. Then, at the bottom of the page, click
Save. If no tags are listed, add a tag to one or more agents on the
server.