This change has been incorporated into the documentation in Release 2012a (R2012a). For previous releases, read below for any additional information:
It is possible to upgrade the PolySpace Server and process jobs from previous versions. This is possible starting with release R2007a. This update will prevent you from having to update the client machines until you are ready. In order to perform this procedure, you will need to first install the older release and then install the newer release on top. It is not possible to do so in the reverse order. If you have installed the newer release and want to go back, you will need to uninstall, then follow the procedure below.
To setup this type of configuration, follow the instructions below:
1) First you will need to install the newer version on the PolySpace server and pick the same PolySpace root folder.
2) Once the installation is complete, the PolySpace_Common folder will be overwritten, but you will have two PolySpaceForCandCpp/PolySpaceForAda folders in the root PolySpace folder, one for each release.
3) You will need to ensure that the queue manager is setup for both versions. To do so, launch the Remote Launcher Manager (Windows) or open the file /etc/polyspace/polyspace.conf file (Solaris/Linux).
For the Remote Launcher Manager, under PolySpace products, check that both folders are listed for both versions. If both are not listed, click the folder button and add in the folder for the PolySpace product you wish to serve. Once updated, click Apply and then Start Daemon to restart the service with the changes.
For Solaris/Linux servers, check that the polyspace.conf file has a "product=" line for both versions. If not, add a new product= line for the missing version. Once updated, restart the daemon by running the following command as root:
/etc/init.d/polyspaced restart
Once updated, the PolySpace server machine will automatically choose the appropriate version of the product based on what version the client passes to the server.
When using R2013a versions with R2013b, the workflow is as follows.
On the server, as soon as you have installed Polyspace R2013a kernel and then installed R2013b MATLAB+MATLAB Parallel Server+Polyspace Bug Finder +Polyspace Code Prover , two services will be able to manage requests R2013a and R2013b client: polyspaced service from R2013b which will take care of R2013a client requests and mdce service R2031b that will take care of R2013b client.
Moreover, they will share same Polyspace web metrics repository (handle by polyspaced service) that will allow to manage 13a and 13b analysis.
This scenario was possible because polyspaced service R2013b is compatible with request coming from R2013a client as soon as Polyspace for R2013a is also installed on the server.
NOTE: Starting in R2019a the following name changes occurred:
- MATLAB Distributed Computing Server was renamed to MATLAB Parallel Server
- mdce_def was renamed to mjs_def
- mdce binary was renamed to mjs
