Java API

• product - the product GUID to check, as defined in your LaaS instance through the Administrators Interface.  If null the product id embedded in the licensing file is used
• count - the transaction count which should be combined with the transaction count for the license to the product on the LaaS server, if null a count of 1 is assumed

public static int LastLicenseCheck()

Offline Checking

You can run your application "offline" without the need of an Internet connection and use a "Proxy Checker" machine to synchronize the licensing file.  See the section Proxy Checker in the Command Line Interface article on Licensing-as-a-Service.

Example

Check License

Check the license for the product that is defined in the licensing.properties file and increase the transaction (usage) count by 1 from a program called BasicProduct.  

import com.heirloomcomputing.ecc.HCILicensing;
public class BasicProduct {
    public static boolean verify() {
        String reason = HCILicensing.LicenseCheck(null, null);
        if (reason.isEmpty()) {
            return true;
        } else {
            System.err.println("Sorry, your license could not be verified: "
                + reason);
            System.err.println("Please see our web site to renew your license");
            return false;
        }
    }

    public static void main(String [] args) {
        boolean result = verify();
        if (result) {
            System.out.println("Basic Product is working...");
        } else {
            System.out.println("Basic Product cannot continue operation");
        }
    }
}

Compile this program with the command:

javac -cp HCILicensing.jar BasicProduct.java

You may want to create a jar file with the contents of the HCILicensing.jar together with your program or combine your program into a .ear or .war file while referencing the enclosed HCILicensing.jar through the manifest's Class-Path directive.  HCILicensing.jar is redistributable to your customers to allow them to verify their license files and perform the proxy checker process.  Remember, you can customize the Error Messages within HCILicensing for your company.  To run this from the command line, issue the following command:

root@pineapple:~$ java -cp HCILicensing.jar:. BasicProduct
Basic Product is working...
root@pineapple:~$

The license properties file is created with the Command Line Interface and contains at minimum the subscription_id,email_address, license_domain and check_service elements.  The product_id may be supplied as a parameter to the command line or API method.

#Heirloom Computing, Inc - License and Transaction Checking
#Fri Mar 01 13:16:28 PST 2013
check_service=http://myco.instances.heirloomcomputing.com/rest/2013-03-01/licensecheck
license_domain=myco
645d7dce-1b35-49f2-adb4-d027e1abc165.count=\u0001\u0000
email_address=myco@myco.com
product_id=645d7dce-1b35-49f2-adb4-d027e1abc165
subscription_id=00000000-8181-616d-6b72-61686e796569

Licensing.properties files are personalized and updated the first time a license is checked against them.  At that point the file is "locked" to that machine and cannot be transmitted to another unless for proxy checking purposes.  The number of machines the initial licensing.properties files may be installed upon (before being personalized) is based on the restriction attributes associated with the license.  See the LaaS Overview, Web Services and Administration Interface for more information.