lmtransfer
The lmtransfer utility supports the transferring of licenses from a parent licensing server to a remote licensing server.
This utility runs on the FlexEnabled remote machine that stores transferred licenses. The FlexEnabled application users can use the utility to do the following:
| • | Initiating License Transferring |
| • | Clearing the Transferred License Setting |
| • | Purging Expired Licenses |
| • | Determining Transferred-License Status |
| • | Returning a Transferred License Early |
| • | Display Usage Information |
Initiating License Transferring
To initiate transferring, user of the FlexEnabled application sets the expiry period by running the lmtransfer from the command line or through lmtools on the FlexEnabled remote machine.
To initiate transferring
From the FlexEnabled remote machine, enter the following command:
lmtransfer vendorname -set dd-mmm-yyyy [hh:mm]
where:
|
Argument |
Description |
|
verndorname |
The vendor daemon name that serves the licenses to be transferred. |
|
-set dd-mmm-yyyy [hh:mm] |
Date the license is to be expired in dd-mmm-yyyy format. hh:mm is the time which is optional and is specified in 24-hour format in the FlexEnabled application’s local time. If time is unspecified, the checkout lasts until the end of the given end date. |
For example, you might enter the following:
lmtransfer sampled -set 20-aug-2023 [14:00]
To transfer licenses for the desired vendor name, on the same day and the same system that the user runs lmtransfer, run the applications to check out the licenses. If you run the applications more than once that day, no duplicate licenses are transferred. No licenses are transferred if the application is run on a day different than the date transferring is initiated.
Aside from the lmtransfer utility, you can initiate transferring by using the transferring interface included in the FlexEnabled application, if such an interface is provided.
Note:The lmrtransfersecure utility must be utilized in order to enable the encrypted communication with the vendor daemon.
Clearing the Transferred License Setting
Users of the FlexEnabled application can clear the transferred licenses setting to stop licenses from being transferred until transferring is initiated again. For example, users might run lmtransfer vendorname -clear after they have transferred licenses for features that are used offline if—before disconnecting from the network—they want to run an application that checks out additional features, served by that vendorname, that are not meant to be transferred. Clearing transferred licenses setting does not change the status for already transferred licenses.
To clear the transferred license setting in the Windows registry
From the FlexEnabled remote machine, enter the following command:
lmtransfer vendorname -clear
Note:The lmrtransfersecure utility must be utilized in order to enable the encrypted communication with the vendor daemon.
Users can remove expired transferred licenses from their FlexEnabled remote machine.
To remove expired transferred licenses
From the FlexEnabled remote machine, enter the following command:
lmtransfer.exe vendorname -purge
Tip:Combine this option with the -status option, both to purge expired transferred licenses from the remote machine and to display information about the still valid transferred licenses. For more detail, see Determining Transferred-License Status.
Note:The lmrtransfersecure utility must be utilized in order to enable the encrypted communication with the vendor daemon.
Determining Transferred-License Status
Users can use the following commands to display the status of licenses which are currently being transferred to a FlexEnabled remote machine.
To display the status of all currently transferred features, expired or not
From the FlexEnabled remote machine, enter the following command:
lmtransfer vendorname -status
To purge expired transferred licenses and display the status of non-expired transferred licenses
From the FlexEnabled remote machine, enter the following command:
lmtransfer vendorname -purge -status
Note:You can specify the -purge and -status options in any order. The result is always the same—expired transferred licenses are removed and the status of the remaining transferred licenses are displayed.
Note:Consider the following:
| • | The current status of transferred licenses is read from information stored on the FlexEnabled remote machine itself. Therefore, the FlexEnabled remote machine does not need to be connected to the network to obtain this information. |
| • | The lmrtransfersecure utility must be utilized in order to enable the encrypted communication with the vendor daemon. |
Returning a Transferred License Early
Users can early return a transferred license.
To return a transferred license early
From the FlexEnabled remote machine, enter the following command:
lmtransfer -return [-vendor name] feature
where:
feature used to specify the name of the transferred feature to be returned early. Use lmtransfer vendorname -status to get a list of transferred feature names.
Note:Consider the following:
| • | To return a transferred license early, parent licensing server should have the ls_borrow_return_early vendor variable enabled. |
| • | The lmrtransfersecure utility must be utilized in order to enable the encrypted communication with the vendor daemon. |
Users can display the lmtransfer usage information.
To display lmtransfer usage information
From the FlexEnabled remote machine, enter the following command:
lmtransfer -help
Note:The lmrtransfersecure utility must be utilized in order to enable the encrypted communication with the vendor daemon.