Managing Custom JARs

A Custom JAR file is attached to a mapping in a similar way as a custom schema file is attached. The Custom JAR automatically follows the mapping’s lifecycle.

To manage Custom JARs, follow these guidelines:

• When you save a mapping to a server, or when you import a mapping from a server, the Custom JAR files used by the mapping are automatically included.

• When you generate, publish, activate or reactivate a mapping, the Custom JAR or JARs used by the mapping are automatically included in the server’s classpath.

• When you inactivate a mapping, the Custom JAR or JARs used by the mapping are automatically removed from the server’s classpath.

• When you export or import a mapping through file, the Custom JAR file or files used by the mapping are also automatically included.

A checksum algorithm is used for Custom JAR files in the same way as for schema files. You can use several different versions of the same Custom Jar file concurrently, since the checksum is calculated from the contents of the Custom JAR file. A Custom JAR, having a specific checksum, is stored in the Mapper Database only once, compare to how schemas are stored.