Linux upgrade
This topic describes how to upgrade an existing installation on Linux. We recommend using the latest version of of the product and its connectors to benefit from the added capabilities and enhanced stability.
Note: Connect for Linux is distributed as a tgz/tar.gz bundle, but not in a Linux package manager format such as RPM or DEB. Therefore, installation, uninstallation, and upgrades require manual intervention. Only attempt these actions if you have extensive knowledge in Linux.
Important note before upgrading to 25.3
Starting with version 25.2, Connect exclusively supports only PostgreSQL as the database. Derby is officially deprecated.
If you are currently using a version earlier than 25.2 please first consult the documentation on how to upgrade to 25.2. For details, see Linux upgrade.
Database installation, upgrade, and management are the responsibility of the administrator.
Upgrade process
This section lists the steps for performing an upgrade.
To perform the upgrade:
- Download Connect Core for Linux from the AppDelivery Marketplace.
- Download the latest version of the relevant connectors from AppDelivery Marketplace.
- Download all connector dependencies as specified in the connector Readme files. The Readme files are included in the download packages.
-
Stop any connections that are running in the existing installation to prevent data loss.
-
Stop the Connect web server:
sudo systemctl stop connect
-
Go to the directory where Connect is installed. Zip and back up the entire Connect folder:
tar -czvf mfconnect-backup.tar.gz MicroFocusConnect/
-
Go to the Connect directory:
cd MicroFocusConnect
-
Uninstall the Connect web server:
sudo ./uninstall_service.sh
-
Go to the parent directory:
cd ..
-
Remove the Connect files:
rm -rf MicroFocusConnect/
-
Create a folder for the Connect installation, and unpack the files from the downloaded archive:
tar -xvf mfconnect-linux-<build>.tar.gz
-
Copy the downloaded relevant connectors with dependencies to the AppData/connectors directory.
-
Restore required configuration files from the backup copy:
rm -rf ./previous-connect
mkdir previous-connect
tar -xf mfconnect-backup.tar.gz -C ./previous-connect
-
If you have modified the Connect environment in the file ./previous-connect/MicroFocusConnect/WebServer/bin/setenv.sh, merge the modifications into the newly installed setenv.sh file.
-
Copy all configuration files:
cp -r ./previous-connect/MicroFocusConnect/AppData/data/* ./MicroFocusConnect/AppData/data
-
Copy the sso configuration files:
cp -r ./previous-connect/MicroFocusConnect/AppData/osp-server-configuration/* ./MicroFocusConnect/AppData/osp-server-configuration/
cp ./previous-connect/MicroFocusConnect/AppData/osp-filter-configuration.properties ./MicroFocusConnect/AppData/
-
If you have modified logging configuration files (for example log4j2.xml), merge the modifications into the newly installed configuration file. The files are installed together with Connect.
Caution: Do not copy older configuration files and replace new configuration files with them, as this overwrites new version configurations.
-
If you have modified utility scripts (for example the .bat or .sh files), merge the modifications into the newly installed utilities. The utilities are installed together with Connect.
Caution: Do not copy over or merge older .jar files back into the new (upgraded) installation files.
-
If you have installed security certificates, copy the certificates from the backup and replace cacerts in <install path>/Connect/jre/lib:
cp ./previous-connect/MicroFocusConnect/jre/lib/security/cacerts ./MicroFocusConnect/jre/lib/security/
-
If you changed the running port or are using https/ssl, copy the server.xml file from the backup, and use it to replace server.xml in <install path>/Connect/WebServer/conf:
cp ./previous-connect/MicroFocusConnect/WebServer/conf/server.xml ./MicroFocusConnect/WebServer/conf/
-
Change the directory to the deployment folder:
cd MicroFocusConnect
-
Prepare the database. Run the prepare_database.sh script:
./prepare_database.sh
-
Using the sudo user, deploy the Connect service:
sudo ./install_service.sh
-
Start the Connect service with one of the following commands:
sudo systemctl start connect
sudo systemctl enable connect
-
To verify the installation, check the service's status:
sudo systemctl status connect
Wait for the system to return an Active status.
-
To secure the database, refer to PostgreSQL database.
-
Log in to Connect using the URL and the credentials provided to you. For example, log in using the URL http://my_server:8081/ConnectWeb/index.html.
See also: