How to Renew a subscription

About Renewals

A license file contains your support expiry date and new major.minor releases whose release date preceed that date will work with the license. It may also contain a license expiry date which limits the operation of the software (perpetual licenses do not have this limit).

You can see these dates in the information presented about your lines, for example from the License Manager:

Or from the License CLI:

Line # | Product              | License Type    | License Use     | Qty | license exp | support exp
1      | XML Compare Java     | Server 2 Cores  | PRODUCTION      | 3   | 2022-01-01  | 2022-01-01 

Renewing a subscription license will allow your software to continue to operate beyond the current expiry date. It will also allow you to install newer software versions released during your renewal period.

The renewal process consists of replacing your existing license file with a new license file.

We recommend updating the license file before your annual renewal date to ensure continued operation of subscription licenses. Your new license file will work with your existing installed software - there is no need to upgrade software versions when renewing the license file.

Using the License Manager to Renew a subscription

For each of your systems you will need to generate a new license and reinstall that file so as to replace the existing file(s).

When your renewal is invoiced we will update the records in our system and the line display will show these new dates. Then you can download a new license file for each system.

When you look at a specific line and expand the systems you should see each of the activated systems and the hostIds you have chosen, for example:

For each system perform the ‘Download’ action. This will cause a file to be regenerated using the new dates and downloaded in your browser. If downloading licenses for multiple systems at the same time some may be renamed or have ‘(1)’ or similar suffixes applied. The files however must be installed with their correct filenames on the appropriate systems. You may be able to identify the systems by their currently activated HostId. Additionally the license file itself contains a comment line which includes the systemId used in the licensing system.

Using the License CLI to Renew a subscription

Use the info argument to the CLI to list the lines and systems of the purchase that has been renewed. The support expiry and possibly license expiry dates will have been updated in our system as part of the renewal process and illustrated in this example:

$ java -jar  licensing-cli-1.0.1.jar info
Purchase: DelCo Software 10001                                      Customer: DelCo Software                 Support Expiry: 2022-01-01 lines:  3
    Line # | Product              | License Type    | License Use     | Qty | license exp | support exp
    1      | XML Compare Java     | Server 2 Cores  | PRODUCTION      | 3   | 2022-01-01  | 2022-01-01 
        System Id                            | Size | Current HostId                           | Last Modify
        a2a50834-ccd9-4b57-b5d2-39a9dc8d1db1 | 1    |              | 2021-04-29T13:43:49.257397Z
        d9fcba70-2875-4075-bc2a-110c88c53199 | 1    |               | 2021-04-29T13:44:16.439249Z
        c5d36e3c-b8c7-4e75-8d0a-a56841d8ec61 | 1    |              | 2021-04-29T13:45:38.171704Z

For each system perform the download action with the CLI. By default the license will be saved into a filename that can be used directly with the software. Therefore when doing downloads for multiple systems consider using the optional filename argument to specify different result files. The following example illustrates this process for the purchase shown above:

$ java -jar licensing-cli-1.0.1.jar download a2a50834-ccd9-4b57-b5d2-39a9dc8d1db1 prod2.lic
New license being stored at: /Users/nigelw/prod2.lic
$ java -jar licensing-cli-1.0.1.jar download d9fcba70-2875-4075-bc2a-110c88c53199 uat1.lic
New license being stored at: /Users/nigelw/uat1.lic
$ java -jar licensing-cli-1.0.1.jar download c5d36e3c-b8c7-4e75-8d0a-a56841d8ec61 prod1.lic
New license being stored at: /Users/nigelw/prod1.lic

These files could now the moved the the respective systems and renamed according to the software product. They should replace a license file of the same name.

If you are renewing the license file a product with a REST API (where the jar provides a REST service) schedule a restart so that the new license file is read.

#content .code