This section describes how additional files and extra files properties are handled during migration. When an entity has extra file properties specified, those extra files are packaged in the exported Jaguar JAR file. However, it is not included with the standard J2EE archive files (EARs, WARs, EJB JARs). Instead the migration process (in addition to migrating the J2EE archives), migrates the Jaguar JAR for J2EE entities and extracts the extra files. Keep these details in mind when migrating extra files:
Files specified with an absolute name – copies the files only when migrating from a remote EAServer 5.x server.
Files beginning with “../” – indicates relative to an EAServer 5.x installation directory. These files are copied to the EAServer 6.0 installation directory.
Files beginning with “cpplib/” – copied to the EAServer 6.0 cpplib subdirectory.
Files beginning with “java/classes” – copied to the EAServer 6.0 genfiles/java/classes subdirectory.
Files beginning with an environment variable denoted by ${...} – copied to the corresponding location according to the environment variable if the contents are different then the existing files.
