I found that the most important topic for the BPM developers, Architects and DBAs is Disaster Recovery specially in production environments. Many of the BPM projects are tracking and live systems which are updated round the clock. So it becomes a headache if the system crashes or is unavailable to the users. This post will show how to avoid the problem and then use the data from the database and move it to a new location is the application server crashes booth in the case of weblogic server or standalone.
Before starting disaster recovery we should have the backup of the following databases and
Few of the ways are given in the link below by oracle administration guide:
Take the back up of the following files whenever you make configuration changes or periodically.
Oracle BPM Files for backup
| File Type | Description | Location |
|---|---|---|
| Configuration Files | $INST_DIR/enterprise/conf | |
| Non-versionable JAR Files | Java libraries that are not part of a project file. |
|
| Properties Files | ../directory.properties | |
| Web Applications | Customized application files, including CSS files, custom JSPs, and image files. | |
| WorkSpace | Custom JSP used by WorkSpace | $INST_DIR/webapps/portal/WEB-INF/portal.properties |
| WorkSpace Administrator | Workspace Administrator properties file | $INST_DIR/webapps/portaladmin/WEB-INF/portaladmin.properties |
| Archive Viewer | Property and configuration files for the Archive Viewer application. |
|
