r9 - 2015-05-27 - 16:54:32 - Main.sbagotYou are here: TWiki >  Deployment Web > DeploymentTroubleshooting > UpgradeTroubleshooting > CLMUpgradeTroubleshooting > EnvironmentCheckList

Environment checklist

Authors: UpgradeTroubleshootingTeam
Build basis: CLM 4.x

This page discusses some of the changes to the supported environments for CLM deployments.

Before you upgrade

Before upgrading to CLM 4.x, it is important to ensure you are running in a supported environment. There are many changes between what is supported in 3.x and 4.x. Navigate to the 4.x System Requirements page for more information and to validate your environment is supported for the upgrade.

Important upgrade facts

The sections below address some important changes in the 4.x System Requirments which should be considered when planning your upgrade.

Database requirements

  • IBM Derby SDK and future fix packs is supported for evaluation purposes only (for small teams of 10 users or less) in CLM 4.x
  • Database support is 64-bit only to align with 64-bit server platforms
  • Oracle is not supported for System z or IBM i
  • SQL Server is supported on Windows Server only

Application server

  • WebSphere Application Server v7.0.0.23 is the minimum required v7 fixpack to host CLM 4.x, vs v7.0.0.19 in CLM 3.x
  • WebSphere Application Server 6.x is no longer supported in CLM 4.x

General deployment changes

  • 32-bit servers are no longer supported to host application servers running CLM applications, except for small-scale evaluation or demonstration purposes
  • For CLM4.x, clustering is supported with WAS ND ( or but also requires the bundled WXS

Version specific system requirements pages

Below are the links to the version specific system requirments:

Related topics:

External links:

  • None

Additional contributors: SusanWu

Edit | Attach | Printable | Raw View | Backlinks: Web, All Webs | History: r9 < r8 < r7 < r6 < r5 | More topic actions
This site is powered by the TWiki collaboration platformCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Contributions are governed by our Terms of Use. Please read the following disclaimer.