To update a PolySpace installation to point to a new license server, you simply need to replace the existing license file with a new license file that has the information for the new server.
If the new license server is not in production, you can create a 2nd license file for the PolySpace installation. In this scenario, PolySpace will draw licenses from the original server. Once the original license server is taken down, the PolySpace installations then fail over to the second server specified in the second license file.
To find the license file location, see the Related Solution 1-CQKEMQ: "Where are the license files for Polyspace located?". This file has the following format:
SERVER server_name hostid
USE_SERVER
For example:
SERVER MyFlexServer 00123456abc1
USE_SERVER
To migrate the PolySpace installtions to the new license server, you can simply update the information in the license file for the new license server. You can also create a "network2.lic" file if the new license server is not yet in production (as mentioned above). In this case, PolySpace will use the license server specified in the other license file until that server is taken down. (PolySpace looks for license.dat or any file with a .lic extension)
NOTE: If you are utilizing redundant licenses servers, you should not use the license file. Instead, you should point PolySpace to the redundant servers using the MLM_LICENSE_FILE variable. See the Related Solution 1-1924T: "What are redundant servers and how do I incorporate a redundant server license file for MATLAB and associated products" for more information about setting up redundant license servers.
Best Answer