The following items should be considered for backup when using enterprise beans.
Enterprise beans often use a database for back-end persistence. Container-managed persistence (CMP) entity beans always use a database for back-end persistence. This data should be backed up the same as any of your business data.
SAVLIB LIB(EJB) DEV(*SAVF) SAVF(WSALIB/WSASAVF) SAVOBJ OBJ(MYBEANTBL) LIB(EJB) DEV(*SAVF) OBJTYPE(*FILE) SAVF(WSALIB/WSASAVF)
It might be possible to save database objects while the product is active, if the save operation can obtain a snapshot of the data store. You may have to shut down if a snapshot cannot be obtained. This occurs if there are requests that obtain locks or have open transactions against the database being saved.
When you deploy enterprise beans, a WebSphere® Application Server-specific implementation of the enterprise beans is generated. Save these deployed Java(TM) Archive (JAR) files to avoid redeploying, and to preserve any binding information that was specified during the application installation. The JAR files, application code and configuration, such as bindings, are located by default in the profile_root/installedApps directory. By saving this directory, you save your installed applications, including HTML, servlets, JavaServer Pages(TM) (JSP(TM)) files, and enterprise beans. Normally, each application is located in a separate subdirectory, so you can choose to save all applications or a subset.
SAV DEV('/QSYS.lib/wsalib.lib/wsasavf.file') OBJ(('/profile_root/installedApps'))
SAV DEV('/QSYS.lib/wsalib.lib/wsasavf.file') OBJ(('/profile_root/installedApps/cellName/sampleApp.ear'))
If you 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 your backup plan as well.
For more information, see the topic Introduction: Administrative configuration data.