Migrating to IBM Connections 6.0
Migrate an installation of IBM Connections™ 5.0 or 5.5 to Connections 6.0. For any version of Connections before version 5.0, you must migrate to version 5.0 before you migrate to version 6.0.
Before you begin
Note: If you are migrating from version 4.5, or you are migrating from either version 5.0 or 5.5
that was previously migrated from version 4.5, and you have FileNet implemented, during CPE upgrade,
the CPE upgrade portion is supposed to change the setting in the FileNet security Directory
Configuration from VMM to CONNECTIONS.
To check
that the FileNet security Directory Configuration in version 6 has the correct setting, take the
following steps:
- Log in to the Acce Console server:port/acce.
- Go to the IC Domain - Directory Configuration.
- Make sure that the FileNet security Directory Configuration is set to CONNECTIONS.
- Make sure that the Directory Server Provider Class is com.filenet.engine.security.ConnectionsProvider.
If you want to change the display name to "IBM Connections Directory Service," follow
these steps:
- Log in to the Acce Console as a P8 domain administrator.
- Click the Directory Configuration tab, and click IBM Virtual Member Manager.
- Click Display Name and select Display or Edit Value from the list.
- Change the value to IBM Connections Directory Service.
- Click the domain tab, click ICDomain, and click Save.
Before you begin the migration, also address the following items:
- Ensure that your environment meets the hardware and software requirements for IBM® Connections 6.0 and any interim fixes or Cumulative Refreshes (CRs) you plan to install. For more information, see IBM Connections system requirements.
- Decide on a migration strategy and if needed install more hardware.
- A side-by-side data migration strategy minimizes the downtime of your production environment but costs more in terms of hardware resources because you keep your older data active during migration. You install Connections 6.0 and its supporting products on new hardware for testing before you deploy the new release. This strategy is used by most enterprises.
- An in-place data migration strategy minimizes costs because you do not need to deploy new hardware. However, it causes more downtime because you take the deployment offline to migrate to Connections 6.0, using the same hardware you used for the previous release. You must uninstall Connections 5.0 or 5.5 and if applicable, Cognos Business Intelligence, before you install the new release.
- A file-based repository is commonly used for administrative user accounts. When the data is
moved from one WebSphere deployment to another, the unique IDs for the file-based repository users
effectively change. This change causes the affected users to look like different users if stored in
the Communities database. Therefore, the Communities app might generate
MemberDuplicateLoginIdExceptions since it finds what appears to be two distinct users
that share the same login. To avoid this problem:
- Run the following command from a wsadmin prompt: execfile('communitiesAdmin.py')
- For each file-based repository user, run:
CommunitiesMemberService.syncMemberExtIdByLogin("<login name>"), for example:
CommunitiesMemberService.syncMemberExtIdByLogin("wasadmin")
About this task
If possible, set up a test environment and simulate the migration process. Correct the cause of
any errors that occur and then migrate your production environment.
Note: IBM Connections 5.0 GA, 5.0 (with CRs), 5.5 GA and 5.5 (with CRs)
can be migrated directly to Connections
6.0.
Procedure
Complete all steps that apply to your deployment.