The deploy.txt File

Using License Keys > > Using License Keys > Deploying an Application > The deploy.txt File

The deploy.txt File

You cannot edit the deploy.txt file but it contains a record of your deployment and is useful if you encounter problems deploying your applications.

Content

The deploy.txt file contains:

For each product:

A copy of all valid runtime licenses found by jlmdeploy that apply to the application, including those of earlier versions.
In comments, a copy of one of the valid contractual development licenses that apply to the application. The hash code of this key is encrypted/obfuscated.

The name of the original JAR used for deployment.
The sum of all uncompressed sizes of the elements of the original JAR.
The date and time of the deployment.

Example

A typical deploy.txt looks like this:

# WARNING!! Editing this file will prevent ILOG products from working.
# ILOG-DEPLOY v1.0 - jarname:YouApp.jar jarsize:000001225 checksum:92DBB201 
date:2004-03-17-19:06:36-CET appname:myapp
LICENSE My-Company
RUNTIME  JViews-Diagrammer 6.000 NEVER SR941350WWS2 N application: myapp
# LICENSE ILOG-Test
# SITE JViews-Diagrammer 6.000 31-May-2010 BH35ZW8QXQ7C Y

Privacy

The deploy.txt file contains the RUNTIME keys needed by your application and the development keys in a modified form: the original key password has been encrypted so that no one can reuse the keys. Consequently the file does not compromise your privacy.

PREVIOUS NEXT