IBM BPM, V8.0.1, All platforms > Migrating and upgrading your IBM BPM environment > Migrating from previous versions > Migrating from IBM BPM Standard V7.5.x, Teamworks 7, or WebSphere Lombardi Edition > Migrating to IBM BPM V8.0.1 > Export and importing process assets
Applying customizations
Compare your customized files from the backups of your existing installations with the corresponding files in the new IBM BPM V8.0.1 installations to ensure that all of your settings are correctly applied to the new installations.
Ensure that you have applied customized settings for the following artifacts:
- Configuration files and settings
If you have customized the length of tracked fields in the Performance Data Warehouse database, update the value of the Performance Data Warehouse's max-length-of-string-columns property. See Extend the maximum number of characters in tracked performance data.
If you are currently running Teamworks 7.0.0 or 7.0.1, note that IBM BPM uses a different encryption algorithm. When you update configuration files, replace encrypted passwords created by your current version with passwords encrypted by IBM BPM V8.0.1. See Encrypt passwords.
- Application server database connection pool settings and tuning parameters
- Email templates
- Logging configurations
- Customized files such as CSS files, CoachDesigner.xsl, images, HTML files, and JAR files, by taking the following steps:
- Include as managed assets the customized files in your current version that have not yet been added to process applications or toolkits.
- If you customized CoachDesigner.xsl, upload
it as a managed asset so that you can use in place of the default xsl file that is installed as part of the migration.
Starting in WebSphere Lombardi Edition version 7.2.0, CoachDesigner.xsl is a managed asset. See Editing process application settings and Editing toolkit settings.
