Before you can use an ILOG product, you have to install the keys.jlm file that you received from ILOG commercial support. Only one copy of this file should be installed on any machine and you can edit it later if, for example, you need to add more keys. Installation is normally performed automatically by the product installer and the following details are for information.

Installing the keys.jlm File

To install the file:

Where to Install the Keys

Here is some guidance on where to install the keys.jlm depending on your platform and other requirements.

On Windows, the products are often installed in:

Similarly, on UNIX, the products are often installed in

More generally, the licensed ILOG products look for the keys.jlm file anywhere in the CLASSPATH. This means that the file can be located in a directory that is an element of the CLASSPATH or can be a top-level element in a JAR file that is an element of the CLASSPATH. You can do either of the following:

For more information on the use of classpath, consult the Java documentation.

Various Environments

If you are working with the ILOG JViews samples, you can store the keys.jlm file in the ILOG JViews installation directory. If you are working in other environments, you may need to copy keys.jlm. Generally, it is recommended to minimize the number of copies of keys.jlm. If you copy the keys.jlm, you have to update all the copies when you receive a new development or runtime key. Moreover, it is easier to debug possible license problems when only one keys.jlm exists.

When you create a command-line Java application, the keys.jlm should be in a directory on the classpath. In the simplest case, you append the ILOG/jlm directory of the JViews installation to the classpath.

When you work with the Eclipse IDE, you might want to create an Eclipse project that contains only a single resource directory, namely a link to the ILOG/jlm directory of the JViews installation. Adding this project to the dependencies of your other JViews project will have the effect to extend the classpath so that keys.jlm is found.

When you build a servlet application, the keys.jlm file should be copied into the WEB-INF/classes directory of the servlet. Some servlet containers also provide a directory for classes and resources common to all servlets. keys.jlm can be stored there as well. For example, Apache Tomcat 4 and 5 have a directory CATALINA_BASE/shared/classes; you can put keys.jlm there.

When you build a BEA Weblogic application, the keys.jlm file should be copied into the APP-INF/classes directory of the application.