Back Up Custom Code

Before you upgrade, be sure to back up your custom code, including the following:

C++ custom connectors
Provisioning manager plug-ins for Java custom connectors
Each cluster member’s customizations, such as non-default ports for workflow
Custom files inside the EAR, for example, files under the IdentityMinder.ear/custom/ directory. Do not back up any files under the following folders:
- resourcesBundles
- identitymanager
- provisioning
Note: If you are upgrading from CA Identity Manager r8.1 SP2 on WebSphere, export the entire IdentityMinder.EAR to back up your customizations.
Common program exits
Custom email templates at the following location:
```
...\IdentityMinder.ear\custom\emailTemplates
```
Universal Provisioning Option (UPO) program exits
Pluggable Authentication Module (PAM) DLLs
Identity Manager Server custom code, such as Event Listener class files, Business Logic Task Handler (BLTH) class files, and Logical Attribute Handler (LAH) class files, and property files at the following location:
```
 ...\IdentityMinder.ear\config
```

Customized skin folder at the following location:

...\IdentityMinder.ear\user_console.war\app\imcss\

Customized help, back up the help property file at the following location:
```
..\IdentityMinder.ear\config\com\netegrity\config\
```
Also, back up the help page HTML files mentioned in this property file.