During the planning stage of your migration project, you must decide on whether to re-use or create additional instances of infrastructure components that support IBM Connections.
Directory Server and Tivoli Directory Integrator (TDI) migration
The Directory Server (for example, TDS) is a key infrastructure component of IBM Connections. The simplest migration path is to re-use the existing instance, but if this is not possible, you must devise a migration strategy for user profiles and synchronization, and the use of Tivoli Directory Integrator (TDI). It is imperative that the Global unique identifier (GUID)
which uniquely identifies each person and group in the organizations stays the same during the migration process. Otherwise, additional effort will be required to re-map all users to their existing content within IBM Connections as part of the migration strategy.
Cognos Business Intelligence migration
To migrate Cognos Business Intelligence from Connections 4.0 to 4.5, you must install a new Cognos Business Intelligence server instead of using the old one. However, the old Cognos database can be reused for the new installation if you want. Refer to Migrating Cognos Business Intelligence
for further details.
WebSphere Application Server / HTTP Server / Proxy Server migration
The difficulty level of migrating these components depends on your migration strategy, in-place verses side-by-side. In general, it is easier to migrate these components using the the side-by-side strategy as major release upgrades are required to these components to support migrating from earlier versions of IBM Connections to the latest product release.