InfoCenter Home >
3: Migration overview >
3.2: Migrating from previous product versions >
3.2.1: Migrating from Version 2.0x >
3.2.1.2: Migrating Web application files from Version 2.0x directories >
3.2.1.2.2: Quickly migrating Version 2.0x Web applications

3.2.1.2.2: Quickly migrating Version 2.0x Web applications

For the fastest deployment, maintain the Version 2 file organization on your Version 3.5 installation:

  1. Move the servlets and other Java components that were in the Version 2 \servlets directory to the Version 3 AS_install_root\servlets directory. If your servlets use package names, create subfolders under the \servlets directory to mirror the package name.
  2. Move the servlets and Java components that were in another Version 2 reloadable class path to the Version 3 AS_install_root\servlets directory, or add the Version 2 reloadable class path to the Version 3 default_app application class path.
  3. Keep any servlets and Java components that were in the system class path in that location. These are servlets that you do not want to have reloaded on your Version 2 installation. The same restriction applies to Version 3.
  4. If your servlets or applications use .servlet configuration files, move those files to the same directory as the servlet.
  5. Move the static HTML and related resources to the Web server document root.
  6. Invoke the servlets and applications in the same manner you used with Version 2.
Go to previous article: Optimally migrating Version 2.0x Web application files Go to next article: Migrating from Version 3.x

 

 
Go to previous article: Optimally migrating Version 2.0x Web application files Go to next article: Migrating from Version 3.x