IBM FileNet P8, Version 5.2.1

Content Platform Engine configuration file backup

If a Content Platform Engine server fails, you must restore the software, either by reinstalling the same version of the software from the installation image or by restoring the server files from a complete server backup. If you reinstall the software, you can restore Content Platform Engine functionality to the state before the failure by restoring its configuration files.

Important: Back up these files after the initial installation and after each configuration change. The files must be restored to the same location.

What to back up

Content Platform Engine is installed as an application on your application server. 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 provides only general information about how Content Platform Engine interacts with the application server. Use the following table to determine the files to back up.

Where the Windows and UNIX paths are identical except for the separators, the Windows format is used.

Backup target	File name and default location	Frequency of changes	Can be reconfigured manually	Comments
Application server configuration files	Content Platform Engine interacts with the application server files in these areas: Configuring the authentication provider Configuring JDBC data sources and connection pools	Infrequently	Yes	Consult your application server documentation to determine the location of these configuration files.
The bootstrapped version of the Content Platform Engine EAR file	If you used the Configuration Manager tool to bootstrap the EAR file, the path to the file is as follows: `Content_Platform_Engine_installation_directory`\ContentEngine\tools\configure\profiles\profile_name\ear\Engine-ws.ear	Upon installation or upgrade; after installation, infrequently	No	The Content Platform Engine EAR file contains the CEMPBoot.properties file, which tells Content Platform Engine how to connect to the global configuration database and which account to run the Content Platform Engine application under, along with encryption algorithm information. If necessary, you can edit some of these properties by using the Bootstrap Configuration Utility. Attention: You cannot re-create the entire contents of this file. Loss of the Content Platform Engine EAR file renders your existing Content Platform Engine server inaccessible.
Configuration Manager profiles	`Content_Platform_Engine_installation_directory`\ContentEngine\tools\configure\profiles	Upon installation; after installation, infrequently.	If these files are not backed up, you can re-create the profiles by using Configuration Manager.	You can use the profile backup to rerun the Configuration Manager tasks that were used to originally configure the server .
Tivoli® Storage Manager options files Note: For FileNet® P8 systems with aTivoli Storage Manager fixed content device	The location is determined by the Configuration Files Share property of the Tivoli Storage Manager fixed content device	Upon creation of or updates to the Tivoli Storage Manager fixed content device	Yes	This directory contains the Tivoli Storage Manager options files that are used to connect to one or more Tivoli Storage Manager servers. This is a networked directory that is accessible by all Content Platform Engine servers in a server farm.
Tivoli Storage Manager DSMI directory Note: For FileNet P8 systems with aTivoli Storage Manager fixed content device (UNIX only)	The location is determined by the DSMI Directory property of the Tivoli Storage Manager fixed content device	Upon creation of or updates to the Tivoli Storage Manager fixed content device	Yes	On UNIX servers only, this directory contains the dsm.sys file that is used by the Content Platform Engine applications that run on that same host. When changes are made to the Tivoli Storage Manager fixed content device, updates are made to both the shared options files and the local dsm.sys file on each Content Platform Engine server in the server farm. Important: If you recover a single Content Platform Engine server in a UNIX server farm and the files that are located in the Configuration Files Share directory are intact, do not overwrite them with an older version from your backup. When the Content Platform Engine server starts up on the restored host, the local dsm.sys file is synchronized with the files in the Configuration Files Share directory.
XML schema and transform files	The location is determined by the workflow system XSL/XSD base directory property. This property is displayed on the Workflow System General tab in the administration console.	Infrequently	Yes	The contents of this directory change if XML schemas or transform files are used for workflows that invoke or provide complex Web Services.