Collaborative Lifecycle Management
Design, test, analyze, develop, deliver ... integrated by design
Collaborative Lifecycle Management 6.0
Upgrading to Collaborative Lifecycle Management 6.0
Before you upgradeIf you plan to upgrade to 6.0, be aware of the following issues:
- You can upgrade to this release from any 5.0, 5.0.1, or 5.0.2 release.
- If the CLM applications to upgrade are co-located in the same WebSphere Application Server profile or on Apache Tomcat, you must upgrade all the applications at the same time.
If you are upgrading any of the Change and Configuration Management (CCM), Quality Management (QM), and Requirements Management (RM) applications from version 5.0 and later, see Upgrading to version 6.0. If you are upgrading from a version 4 release, first upgrade to a version 5 release, preferably the latest 5.0.x release. For more information, see Upgrading from version 4 to the current version.
Requirements Management (RM) application onlyBefore you run the upgrade script or the -addTables command for the RM application, you can improve performance by increasing the memory allocation for repotools-rm.sh. If it's possible in your environment, in repotools-rm.sh, change VMARGS="$VMARGS -Xmx${REPOTOOLS_MX_SIZE:-1500}M" to VMARGS="$VMARGS -Xmx8G". For details, see Work Item 94505.
Quality Management (QM) application onlyThe QM application does not support online migration for upgrading to 6.0.