Upgrade Guide for Release 3.0.0
About This Upgrade Guide
The Si Upgrade Guide walks you through the process of upgrading the Single Connect solution. This guide includes pre-upgrade and upgrading steps and other guidelines.
Make sure you read this guide thoroughly and follow the upgrading steps to ensure a smooth upgrade process.
Audience
This guide addresses administrators and clients responsible for installing and upgrading the Single Connect solution.
Version Information
This guide is valid for:
- Upgrading the Single Connect from 2.21.0 to 3.0.0.
- Upgrading the Single Connect from 2.21.1 to 3.0.0.
Related Documentation
Find the links to the related documentation set below. Note that only registered users can acess these documents.
Contact Us
If you need help with upgranding or have issues that we did not adress in this document, contact us through the following channels:
- Open a ticket at Kron Support Portal. Only registered users can open support tickets.
- Call Customer Service at +90 (539) 796 05 03. Customer service is 7/24 online for operational issues.
Pre-Upgrade Steps
- Please find the upgrade script at filerepo under the following path and download it to the server.
/home/krontech/SingleConnect/updates/singleconnect-3.0.0-update.tar
- Make sure that md5sum is correct before using the file.
MD5sum: “8ca7367a04f76fd9d882495f4672c031”
Upgrading Steps
Follow the steps below in the given order to upgrade Single Connect to 3.0.0:
- Unzip downloaded upgrade script.
- Run the following SSH command: tar -xvf singleconnect-3.0.0-update.tar
- Execute the upgrade script.
- Run the following SSH command: .\upgrade.sh
A new text-based GUI installer will be assisting users during the installation.
After Upgrading
The following items should be taken into consideration after the upgrade process.
- Remote root access to the Single Connect server is prevented with 3.0.0. During installation, you will be requested to set the password of pamuser. Remote access to the server should be done through the pamuser. All services will be run with this user.
- The database access method is changed. PostgreSQL requires an SSL connection now; therefore, clients should have the certificates created on the target server to reach the target database.
Be the first to add a reaction.