Upgrading the server in interactive mode

To upgrade the server, stop the server, and run the new installation program.

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.

  1. Download and extract the installation files for IBM DevOps Deploy (Deploy).

    These files are available for download from the IBM® Passport Advantage® website.

  2. 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. You can use the Message of the Day feature (Settings > System > General Settings) to notify users of the planned upgrade, and request that they do not start new processes.
  3. Stop the server.
    Warning: If you are upgrading a high-availability installation, stop all of the servers. If any servers are accessing the database when the upgrade happens, the upgrade will cause errors. See Upgrading high-availability installations.
  4. Ensure that the server is stopped:
    1. Check that there is no server.pid file in the server_install/var folder.
    2. Check for running system processes.
      On Linux™, you can use the netstat or ps commands. For example, if the server is running on port 8443, use the command netstat -nap | grep 8443. You can also run ps -ef | grep server and look for the server system process in the results.
    3. Stop any running server process.
      If you try to upgrade with a running old server process, you get an error that says A previously installed version of Deploy is running. Please shutdown the running Deploy and start the installation again. .
  5. Back up the database.
  6. Upgrade the version of Java on the server to version 11 or later.
    See Changing or updating the JRE of servers.
  7. From the command line, run the server installer program.
    • On Windows™, run the install-server.bat file.
    • On Linux, run ./install-server.sh.
    • To install a FIPS-compliant server, add the -fips-semeru parameter to the command, such as install-server.sh -fips-semeru.
      Note:
      • If you install a FIPS-compliant server, cloud provisioning is not available.
      • Deploy supports IBM Semeru versions 11.0.24, 17.0.12, 21.0.4 or higher.
    Depending on your system settings, you might need to run this file as an administrator.
  8. 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.
  9. If you agree to the terms of all of the license agreements, press Y and then press Enter.
  10. At the prompt that says Enter the directory where the DevOps Deploy server should be installed., specify the folder of the existing installation and press Enter.
  11. 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.
  12. Verify that the server is stopped and then press Enter to start the upgrade process.
  13. Ensure that licensing is set up for the server. See Licensing.
  14. Upgrade the encryption key strength. See Upgrading encryption key strength.
  15. Start the server and verify that the server has been upgraded. If you get the error Shutdown file is present! Is the server running?, check that you are using Java 11. If so, remove the -Djava.endorsed.dirs=<PATH> from the JAVA_OPTS variable in the set_env file.
  • Upgrade the agents.

    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.

  • Upgrade all agent relays to the current version. Agents that connect through relays may not connect successfully until both server and relay are upgraded.