Backup and recovery: JavaServer Pages (JSP) files

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

JSP source and generated servlet classes

Application code and configuration (such as bindings) is located by default in the /QIBM/UserData/WebASE51/ASE/instance/installedApps directory. By saving this directory, you save your installed applications, including HTML, servlets, and JavaServer Pages (JSP) files. 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.

This command saves all installed applications:

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

This command saves the sampleApp application only:

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

When JSP files 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 - Express places the generated files (.class, .java, and optionally, .dat) in a temporary directory under the WebSphere Application Server - Express instance. For example:

/QIBM/UserData/WebASE51/ASE/instance/temp/node/
appserver/application/web_module

where instance is the name of your instance, node is the name of the iSeries server or partition on which your WebSphere Application Server - Express instance is running, appserver is the name of your application server instance, application is the name of the enterprise application to which the JSP file belongs, and web_module is the Web module that contains your JSP file.

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