Upgrading the server in silent mode

Use silent mode to upgrade without command-line prompts. To upgrade the server, stop the server, edit the properties file, 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 IBM DevOps Deploy (Deploy) 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. 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.
    Rotate and delete any 3DES keys if you are upgrading to v7.3.0 or later. See Rotating an encryption key for more information.
  2. Download and extract the installation files for Deploy.
    These files are available for download from the IBM® Passport Advantage® website.
  3. 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.
  4. Stop the server.
  5. 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. .
  6. Back up the database.
  7. Upgrade the version of Java on the server to version 11 or later.
    See Changing or updating the JRE of servers.
  8. In the installation files, open the install.properties file in a text editor.
    • Make sure that the following mandatory parameters are updated.
    vendor.name=ibm 
component.name=exampleComponent 
component.directory=devops-deploy/server 
version=8.1.0.0.1234567
    • Add the following line of code to the file.
    nonInteractive=true
install.server.dir=/opt/applocal/devops-deploy 
server.initial.password=admin 
com.urbancode.ds.cleanup.sourceConfig.fullCleanupSkip=true
    Note: When you perform a silent installation, the server.initial.password entry in the install.properties file is required. However, if you use the skip.db.install=Y option, the database is not updated during installation. Therefore, the password specified in the server.initial.password property is not applied.
    For a detailed description about these properties, see Server installation properties.
  9. From the command line, run the server installer program. 
    install-server.bat -silent -install-dir <\install\dir>-java-home <\jdk\dir> -frontend
    • 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.
    The arguments in the command correspond to properties in install.properties, and if specified they will override them. Corresponding properties are as follows:
    Argument Property Note
    -silent nonInteractive=true Running with -silent and without an -install-dir results in an error.
    -install-dir /install/dir install.server.dir=/install/dir Setting an install-dir that already has server results in a server upgrade.
    -java /jdk/dir install.java.home=/jdk/dir Running with -java for a server upgrade results in an error.
    frontend Optional Distributed front-end server. For more information, see Installing the distributed front-end server
  10. Start the server, and verify that the server is upgraded.
    If you get 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.
  11. Ensure that licensing is set up for the server.
    See Licensing.
  12. Optional: Upgrade the encryption key strength.
    See Upgrading encryption key strength.

  • After the upgrade, DBAs must monitor the database for atleast a week to ensure optimal performance. It is important to perform the necessary database statistics actions and verify that the database is using the most efficient execution plans. For larger databases, using outdated execution plans after an upgrade can lead to significant performance issues.

  • 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.
  • You may need to upgrade the plug-ins if they do not work after upgrade.