Please ensure that you have completed the tasks described here before attempting to deploy your application.

Determining the JAR Files to Be Deployed

The JAR files that make direct API calls to ILOG product_name need to be deployed. There can be a single JAR file or multiple JAR files. The JAR files of ILOG product_name products do not need to be deployed. If you repackage the ILOG product_name JAR files by unpacking them and rejarring them with your application classes, you will need to deploy the repackaged JAR file as well.

Declaring the Application Name in the Application

IlvProductUtil.registerApplication("application name");

This call must be executed before any service of the ILOG product is used, otherwise the license check may fail. It can be executed in a constructor that is executed once only, at the startup of the application, or in static initializers. Since static initializers can lead to problems that are difficult to debug, the former way of calling registerApplication is preferred.

Checking You Have the Relevant Keys

For every ILOG product used by your application, you have to possess two keys: a development key and its associated RUNTIME key.

Checking that keys.jlm Is Accessible

Check that the keys.jlm file is accessible from one of the CLASSPATH directories.

Completing All Development Tasks

If you perform some other processing on your JAR files, such as obfuscation or removal of unused methods, these steps must be performed before you run jlmdeploy. In other words, jlmdeploy is the last step before shipping a JAR.

The jlmdeploy tool must be the last tool in the deployment chain, except for jarsigner.

If you intend to deploy your JAR using the Pack200 utility of JDK 1.5, you will need to normalize the JAR before running jlmdeploy. Normalizing a JAR relative to the Pack200 compressor can be done by using the pack200 --repack command.