(iSeries)

Backing up and recovering servlets

Servlet source and class files, user profile data, Hypertext Transfer Protocol (HTTP) configuration, and administrative configuration should be considered for backup when using servlets. We should consider saving the HTTP configuration because changes to the HTTP configuration are often made to enable WebSphere Application Server to serve servlets and JSP requests, and to enable WAS security. We should consider backing up the user profile data if we use the User Profile function of WAS.

Tasks

• Backup servlet source and class files. Application code and configuration such as bindings, is located by default in the profile_root/installedApps directory. By saving this directory, you save your installed applications, including HTML, servlets, JSP files, and enterprise beans. Normally, each application is located in a separate subdirectory, so we can choose to save all applications or a subset.
  1. Save all installed applications. The following commands have been wrapped for display purposes. Enter each as a single command.

     SAV DEV('/QSYS.lib/wsalib.lib/wsasavf.file')
      OBJ(('/profile_root/installedApps'))
     

  2. Saves the sampleApp application only. The following commands have been wrapped for display purposes. Enter each as a single command.

     SAV DEV('/QSYS.lib/wsalib.lib/wsasavf.file')
      OBJ(('/profile_root/installedApps/cellName/sampleApp.ear'))
     

  If we have located utility or general purpose classes in other directories, such as profile_root/lib/app or profile_root/lib/ext, be sure to include those locations in the backup plan as well.

• Save HTTP configuration.

  The following information applies to IBM HTTP Server for iSeries (powered by Apache). If we are using Lotus Domino HTTP Server, see the Notes .net Documentation Library.

  1. Save the HTTP server instances for IBM HTTP Server for iSeries (powered by Apache). The HTTP server instances for IBM HTTP Server for iSeries (powered by Apache) are members of the QATMHINSTC file in the library QUSRSYS. An example save command for this file could be the following: SAVOBJ OBJ(QATMHINSTC) LIB(QUSRSYS) DEV(*SAVF) OBJTYPE(*FILE) SAVF(WSALIB/WSASAVF)

  2. Save the HTTP configurations for IBM HTTP Server for iSeries (powered by Apache). The HTTP configurations for IBM HTTP Server for iSeries (powered by Apache) are stored in the integrated file system in a subdirectory, chosen when the configuration was created. The recommended location is within the WebSphere instance directory. We can determine this file location by inspecting HTTP server instance member in the QATMHINSTC file in library QUSRSYS. An example save command for this file could be the following: SAV DEV('/QSYS.lib/wsalib.lib/wsasavf.file') OBJ(('profile_root/profile/apache/conf') ('profile_root/profile/htdocs')) where profile is the name of our instance. The default instance name is default.

Related:

Servlets

Assembling web applications

http://www.notes.net/notesua.nsf?OpenDatabase