About Export and Import of Custom Java Procedures

Custom Java Procedure JARs are exported with a TDV full server backup (and when using the backup_export), although the tool backup_export -excludejars option can be used to omit those files when required.

An export exception: If the Custom Java Procedure makes use of one or more classpaths referring to other JAR files, those files must be backed-up or migrated separately because they are not picked up and replicated during export.

When a data source is exported, the adapter from which the data source was created is exported as well. In particular, all the files in the data source directory are included in the CAR file.

Custom Java Procedures (CJP) are normally imported into the directory conf/customjars/ when restoring TDV from the full server backup CAR.

The CJP cluster propagation is immediately propagated across the cluster along with its CJP library. Unlike other TDV-defined resources, those resources that can be referred to by a CJP data source's classpath are not propagated. Such resources must be manually distributed to all cluster nodes.