Import application artifacts, including configuration data
and properties files, into your new deployment.
Before you begin
Ensure that you completed the steps in the Exporting
application artifacts from IBM Connections
4.5 topic.
About this task
To import application data into your IBM® Connections 5.0 deployment, complete the
following steps:
Procedure
- Start the Deployment Manager in your IBM Connections 5.0 deployment.
- Copy the migration directory that
you backed up from your 4.5 deployment to the connections_root directory
in your 5.0 deployment.
Note: Be sure not overwrite the
5.0 migration directory with the 4.5 migration directory. Only copy
the 4.5 migration/work directory into the existing migration directory
on the 5.0 system.
- Import your 4.5 data. Open a command prompt, change to the migration
directory in the connections_root in your 5.0 deployment, and run the following command:
- AIX or Linux:
./migration.sh lc-import -DDMUserid=dm_admin -DDMPassword=dm_password
- Windows:
migration.bat lc-import -DDMUserid=dm_admin -DDMPassword=dm_password
- IBM
i:
migration_OS400.sh lc-import -DDMUserid=dm_admin -DDMPassword=dm_password
- where dm_admin is the administrative user ID for WebSphere® Application Server Deployment Manager and
dm_password is the user password.
Note: Check the log file to validate the import. The log file is stored in the system user's home
directory, and uses the following naming format:
lc-migration-yyyyMMdd_HHmm_ss.log
For example:
- AIX or Linux:
/root/lc-migration-20110215_1534_26.log
- Windows:
C:\Documents and
Settings\Administrator\lc-migration-20110215_1534_26.log
- Windows Server
2008:
C:\Users\Administrator\lc-migration-20110215_1534_26.log
- IBM
i:
/home/username/lc-migration-20110215_1534_26.log
Where username is the user that you run this command with.
- If your deployment uses multiple nodes, synchronize the
nodes.
What to do next
Complete the steps in Post-migration tasks.
If the migration fails,
restore the Deployment Manager profile and complete the steps in this task again. If you customized
your 4.5 environment, reapply your customizations to the relevant XML files.
For more
information, see the Rolling back a migration topic.
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, causing these
users to look like different users if stored in the Communities database. As such, Communities might
generate MemberDuplicateLoginIdExceptions since it has apparently found two distinct
users sharing the same login id. 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")