Network and repository

To use commuter licenses, your application must be linked with the integrated library or its variant.

Both

>1 to 1827 days for long type licenses

>1 to 60 days for short type licenses

>If you have not specified any commuter duration, a license can be checked out up to license validity or expiration.

Manual

Your customers need to explicitly check out an authorization (unlike repository licenses which are automatically checked out). When checking out an authorization, the user may request authorization for a specific number of days or unlimited duration (valid up to the license expiration).

Optional

Since commuter authorizations expire after the specified number of days, so users need not bother checking the authorizations after returning. On the other hand, if the system administrators find that the license tokens for the licensed application are running out, they may want to encourage users always to check authorizations back in as soon as possible.

Also, note that the commuter licensing user must check an authorization back into the same License Manager from which the authorization was checked out.

Yes

A commuter license can be checked out and in for a remote user.

Yes

You must set up the persistence data for allowing use of commuter licenses on your customer's local computer. Execute sntl_persistence_create API. For more information on how to call, compile and execute this API, refer the sample available at …\9.8\Samples\C\Src\sntl_lspmgmtinit.c path.

For more details, refer to “Persistence Data-dependent License Models”

Normal

A commuter allowed network license cannot be used as a trial license

An authorization is locked to a portable computer using the local license request locking criteria

Use of Commute.dat File for Customizing Local Locking Criteria

Commuter and repository licenses make use of the local license request locking criteria. If no local locking criteria is provided, the license is locked to the default locking criteria 0x4 (disk ID). For more security, you may choose any other locking elements. You can provide the commute.dat file to your customer using which they can do custom selection of the locking criteria from the “desired” fields such that all "required" fields and the selected "desired" fields collectively meet the "minimum" number of locking criteria for the local license request to succeed. This file has the same format as the echoid.dat file. The commute.dat file must reside in the same directory as the WCommute or lcommute utility.

For example, a commuter license specifies "required" locking criteria as disk ID, "desired/floating" criteria as Ethernet card and Computer ID key and "minimum" criteria as two. Any client that has the required criteria (disk ID) along with any one of the desired criteria available, will be able to obtain the commuter authorization. In parallel, commute.dat can be edited to allow locking only to disk ID and Ethernet card or Computer ID key.

Yes

You need to initialize the system for that feature-version before using it for the first time, to set up persistence data for the license. For more details, refer to “Persistence Data-dependent License Models”

Yes

A commuter-allowed network license can be revoked.

See also: Deferred Revocation of Commuter and Repository Licenses

No

A commuter-allowed network license cannot have capacity associated with it.

No

License sharing rules are enforced by the License Manager to network licenses (which may also be commutable). A commuted license token on a local system acts as a standalone license and therefore sharing rules do not apply to it.

No

License holding feature is useful for the network licenses. But when a network license is in commuted state, the license holding feature is not needed.

Yes

You can use a redundant license for commuting purposes. However, the license authorization can only be checked out from the leader License Manager (and not from the followers). Similarly, the commuted token must be checked in to the same leader License Manager.

Limited private vendor information (up to 883 bytes) can be included in the commuter license strings installed on the on local systems.