Back up Application Engine configuration files
Should an Application Engine server fail, you must restore the software, either by reinstalling the software from the IBM FileNet P8 Platform installation image or by restoring the server files from a complete server backup. Once restored, you can restore Application Engine's functionality to the state before the failure by restoring its configuration files.
NOTE For optional expansion products installed on an Application Engine server:
Application Engine is installed as an application on your application server. IBM recommends that you back up your application server according to the instructions of your application server vendor. Since application server configurations and directory structures vary from vendor to vendor, this topic only provides general information about how Application Engine interacts with the application server. In general you should back up any P8 files that you edit directly on the Application Engine application server. Use the following table to determine the files to back up.
NOTE Where the Windows and UNIX paths are identical except for the separators, the Windows format is used.
Backup target | Default location | Frequency of changes / Can be recreated without backup |
Comments |
---|---|---|---|
Site preference configuration files | <AE_install_path>\<config_dir> |
Infrequent
NOTE The following files are modified when you edit Workplace site preferences.
|
Back up all files located in this directory. The config_dir is specified during installation and is stored in web.xml. For example, the default Windows path is: C:\Program Files\FileNet\Config\Application Engine |
Deployment descriptor file | In <app_root>\WEB-INF: web.xml |
Upon installation; subsequently, infrequently / Can be manually reconfigured |
Back up any time you make manual edits to this file. Consult your application server documentation to determine the location of the root application directory (<app_root>). |
WcmApiConfig.properties file | In <app_root>\WEB-INF: WcmApiConfig.properties |
Upon installation; subsequently, infrequently / Can be manually reconfigured |
Back up any time you make manual edits to this file. Consult your application server documentation to determine the location of the root application directory (<app_root>). See WcmApiConfig.properties file for more information. |
Encryption keys |
In <AE_install_path>\FileNet\Authentication: UTCryptoKeyFile.properties |
Upon installation; subsequently, infrequently / Can be manually reconfigured |
Back up any time you make manual edits to these files. |
Process Task Manager configuration files | In <AE_install_path>/FileNet/Router: taskman.properties |
Periodic / Can be manually reconfigured |
Back up any time you make manual edits to these files. |
Process Task Manager configuration file | In <AE_install_path>/FileNet/Router: taskman.login.config |
Upon installation; subsequently, infrequently / Can be manually reconfigured |
This file is modified if you change the Process Engine Connection Point in the Workplace site preferences. |
Component Manager "autostart" configuration files | WebLogic: weblogic.policy WebSphere: server.xml |
Upon initial configuration / Can be manually reconfigured |
These are the files which have optionally been modified in order to automatically start and stop Component Manager under the application server's control. See Configure Component Manager for WebLogic control or Configure Component Manager for WebSphere control for more information. |