In this guide, we will take a look at the steps involved in upgrading your current installation of Prolaborate version 3.7 to latest version.
For a smooth installation, it is recommended to upgrade your current installation of Prolaborate to version “V3.7”, if not done already, Please follow this steps to upgrade Prolaborate to version from “V3.2”to “V3.7”. Click here to know more.
Check the following points and decide whether you are fine/ready to go ahead with the upgrade.
As of now, Prolaborate supports EA repositories hosted on MS SQL and MySQL database servers only. Support for Postgres and Oracle databases are in the pipeline.
The password algorithm has been upgraded for enhanced security.
If you are using Prolaborate’s inbuilt User Management capabilities (and not integrated with AD or SAML SSO), the password will be reset for all users.
You should proceed with latest version only if you can handle the impact.
A quick update will be needed after the migration if you are using SAML integration of Prolaborate.
Proceed with latest version if the SSO team understands the change and is available.
Review the complete release notes to confirm all the features that you use right now are already released in latest version.Here is the link to a summary of the release.
For a smooth installation, it is recommended to upgrade your current installation of Prolaborate to version 3.5, if not done already. Learn more here.
Pro Cloud Server should be upgraded to version 5.0.105, if not done already. Click here to download the installer.
Once the decision is made to go ahead with latest version, you need to plan for it. This section will help you with the same.
Check out the details of this planning section and finalize the date of the upgrade.
Inform the business stakeholders about the Prolaborate latest version upgrade and the changes in advance.
You can inform them about the date and time of the upgrade, and the new features.
The plan should consider the following activities as a minimum:
|Prolaborate Upgrade||IT team|
|Post Installation - User Update||Architecture Team|
|Post Installation - SSO Update||SSo Team|
|Post Installation – SSL update and other steps||IT Team|
Follow these steps on the day of the upgrade.
Select a path to install Prolaborate. (Create a separate folder for V4 installation for safety purposes)
Important Note: Please use an alternate folder path rather than the one used for version 3 to avoid data conflicts. Also, this helps in rollback if needed.
Choose the Database server using which the Prolaborate database is hosted. Then choose Run Schema.
Improved version compatibility check during upgrade. If the previous version of Prolaborate is less than 3.5.0, the application throws a warning during the upgrade and halts the upgrade process.
Please ensure a backup of the database is taken. This step is just a gentle reminder and does not do anything.
Enter the IP address or domain name in Host. Enter a port that is not in use and open in Firewall. Port 443 is recommended. Enter an email address. This user will be made the super admin of Prolaborate.
Review the information and click Install
Once the installation is completed successfully, the following page will appear. Click Finish
The V4 application does not require an IIS manager to perform in Version 4. We upgraded the Config file, and it completed all of the manual work that required manual installation of IIS, and the user may access the web application through the domain that was specified during the installation phase Configure Prolaborate.
Data Migrator helps in migrating the data from V3 to V4. Existing configurations include dashboards, chart widgets, report widgets, discussions, reviews, users, modeling languages, etc can be transferred with the help of Data Migrator.
To initiate the migration process, go to the Prolaborate installation folder (For example, C:\Program Files (x86)\Prolaborate\ProlaborateDataMigration). Right click on “DataMigrator.exe” and choose ‘Run as Administrator’.
There are 2 ways how you can reset the password.
Users who want to run their application using HTTPS protocol in the sense have to do the following steps manually.
Please use this below-mentioned path to get Prolaborate Management
C:\Program Files (x86)\ProlaborateV4\ProlaborateManagement
Run Prolaborate Management as a Administrator.
Click Manage Configuration
Choose SSL certificate using browse icon
Enter the respective password for the certificate.
Select Use Https check box.
After installing Prolaborate, users must do the following steps in order to access the Application over HTTPS.
Open the application by entering the admin login credentials at the URL listed below.
Click the Edit button.
Change Protocol into HTTPS and also change the Respective Port number. Then Click Save Button.
Now that information is automatically updated in the OIDC table from the prolaborate database.
Following the upgrade, Prolaborate V4’s Application Base URL and Assertion consumer URL of Prolaborate V4 will be different from Prolaborate V3. Admin must change or modify the Prolaborate V4 Service Provider configuration details at the current SAML application from your SAML provider in order to ensure smooth execution.
Copy the Service Provider configuration details from Prolaborate and paste in the respective fields at the SAML application as described in the image below.
Now, configure Prolaborate to link with the SAML application. Copy the URL’s from the SAML Application and paste them in the respective fields under Identity Provider Configuration as shown in the image below.
In V4, we made it easier to map the attributes from the Prolaborate UI.
Map the attributes from the SAML SSO settings page, upload the SSL certificate and save the changes.
Attribute Mapping will be pre-filled with default values in SAML Single Sign-On page and they cannot be edited.
If required, users can change the values by clicking the toggle button from Default to Custom. Then copy the Attributes & Claims values from the SAML Application and paste them in Prolaborate Attributes Mapping.
In case of any questions, feel free to reach out to firstname.lastname@example.org