<project_name>.jar * - a Generated Project File

This file always exists, and contains all of the compiled program files required to run a transformation.  The relationships, transforms, User Defined functions, and so on are all stored in this file. 

The .jar file name is set automatically, and cannot be modified.  Its name is based on the name of the project, with the .jar extension.   For example, the .jar generated files for the first version of a project called ErrorTrapping would be ETL_ErrorTrapping.jar.

Two settings in the TM Design Tool GUI affect the building and location of the .jar  file.

• Tools | Preferences | SML Generation | Jar Deployment Destination specifies the location of the .jar file
• Tools | Preferences | SML Generation | Remove Generated Code specifies that all code other than the Java file should be removed after the .jar file is built.

In order to deploy code generated from TM Design Tool all that is necessary is that the .jar file (and of course the invariant standard library ofetsr.jar supplied with TM) is added to the Java CLASSPATH.