When you update all the ReadyAPI instances, uninstall Protection! Licensing Server 4. See Installation Guide.Īpply the floating license. then replace all the class file in soapui-pro-crack-x.y.z.jar. found in a separate license agreement or Read Me file located near such. Note: On the Linux and macOS operating systems, the. soapUI Pro is for internal business purposes only. To do it, run the uninstall file from the ReadyAPI installation folder. Uninstall the current version of ReadyAPI.
How users can update ReadyAPI manually How users can update ReadyAPI manuallyĪfter you install the new version of the license server, you send this instruction to your ReadyAPI users so that they can update it manually.ĭownload the latest version of ReadyAPI from our site: You will be able to update ReadyAPI and Protection! Licensing Server any time later by using any of the previous options.
Besides that, the new ReadyAPI version provides you with new features and bug fixes. But, we do not recommend this approach, since Protection! Licensing Server 4 is less secure. Of course, you can stay at the current versions of ReadyAPI and Protection! Licensing Server.
Postpone the upgrade for the time being (Not recommended) To learn more about this approach, see the Step-by-step migration section below. During that time, the non-updated ReadyAPI instances will use Protection! Licensing Server 4. You will have one month since you get a new license file to update all the ReadyAPI instances in your network. You install a new version of the license server with the new license to a separate machine so the new license server will coexist with the old one in the same network. In case you face any issue blocking the upgrade process, you will be able to downgrade the software until you solve the issue with our support team. ReadyAPI 3.3 and earlier cannot work with Protection! Licensing Server 5, so they cannot consume the license and will not work. To learn more about this approach, see the Immediate upgrade section below. Then, you update all ReadyAPI instances in your network. You update your license server and install a new floating license. You have to contact our support team to get a new license file compatible with Protection! Licensing Server 5. Also, you will need a new license file as your current license is not compatible with Licensing Server version 5. If you use a floating license, when you update ReadyAPI to 3.3.1, you will also need to update the license server. It means that ReadyAPI 3.3.1 cannot work with Protection! Licensing Server version 4, and, vice versa, ReadyAPI prior to 3.3.1 cannot work with Protection! Licensing Server version 5. Earlier ReadyAPI versions use Protection! Licensing Server version 4 that does not support this protocol. This version uses a more secure protocol for communication with ReadyAPI. Starting from version 3.3.1, ReadyAPI uses Protection! Licensing Server version 5. For information on the new ID-based license type, see SmartBear ID-based Licenses. This page is related to file-based licenses - a regular license type used in ReadyAPI 3.40.