Save and restore: JavaServer Pages(TM) (JSP(TM)) files

The following items should be considered for backup when using JavaServer Pages(TM) (JSP(TM)) files:

JSP source and generated servlet classes

Application code and configuration (such as bindings) is located by default in the /QIBM/UserData/WebAS5/Base/instanceName/installedApps directory. By saving this directory, you save your installed applications, including HTML, servlets, JavaServer Pages (JSP) files, and enterprise beans. Normally, each application is located in a separate subdirectory, so you can choose to save all applications or a subset.

Note: The following commands have been wrapped for display purposes. Enter each as a single command, with a space between the end of DEV parameter and OBJ.

This command saves all installed applications:

SAV DEV('/QSYS.lib/wsalib.lib/wsasavf.file')
 OBJ(('/QIBM/UserData/WebAS5/Base/instance/installedApps'))

This command saves the sampleApp application only:

 SAV DEV('/QSYS.lib/wsalib.lib/wsasavf.file')
 OBJ(('/QIBM/UserData/WebAS5/Base/instance/installedApps/cellName/sampleApp.ear'))

When JSP files are run, a servlet class is generated, compiled, and then run. When saving and restoring your JSP files, you can elect to save only the JSP source or the generated files as well.

WebSphere Application Server places the generated files (.class, .java, and optionally, .dat) in a temporary directory under the WebSphere Application Server instance. For example, the default instance stores the generated files in this directory:

/QIBM/UserData/WebAS5/Base/instanceName/temp/node_name/application_server/enterprise_app/web_module
In this example:

Note: A .dat file is a helper file used by the generated servlet.