Configure the upgraded Semaphore software

The upgraded software should be re-configured as per the configuration of each product as per the information documented in earlier sections of this guide. The following sections describe the re-configuration requirements that are specific to core components.

Re-Configuring Classification Server

Complete the following tasks to reconfigure your Classification Server after upgrade.

• Adjust the Classification Server configuration file with the relevant configuration from the previous installation.

  If the upgrade installs a new configuration file, it will have the file extension .rpmnew (e.g., config.xml.rpmnew). Follow these steps to update and use the new configuration file:

  1. Compare the file with rpmnew extension with the existing configuration file (the one without the .rpmnew extension).

  2. Adjust the rpmnew file to match the settings in the previous configuration file as needed.

  3. Rename the updated .rpmnew file appropriately (e.g., rename config.xml.rpmnew to config.xml).

  Additionally, if you have other custom configuration files (e.g., config-instance.xml), ensure they are updated to align with the changes in the newly installed configuration file.

  Generally, to update the Classification Server configuration to match the previous installation, update the new config.xml configuration file to match the previous configuration. Key settings include:

  • port: The port property in the Classification Server bean should match the previous installation (the default value is 5058).

  • workers: The workers property in the CS bean should match the previous installation (the default value is 2). However, this value must also comply with the restrictions imposed by the licencing contract with Progress. If the licence has changed, this value might need be updated to reflect new restrictions.

  It is possible other sections of this configuration may have changed. If you are unsure of the changes, we recommend comparing the new version configuration with the old version.

• Copy into Classification Server any manually created/updated rulebases and templates.

  From the Classification Server backup, copy any files from the permanent sub-directory of the rulebases folder into the new Classification Server installation directory. Similarly, copy any files in the templates sub-directory of the back-up into the same folder in the new installation.

• If required, re-configure any /etc/init.d/ or systemd scripts if using multiple instances of Classification Server.

  Ensure that any /etc/init.d/ or systemd scripts used for multiple instances of the Classification Server are appropriately configured. This process might include copying previously backed-up directories/files into the updated instances.