Exporting application artifacts from IBM Connections 4.0 and 4.5

Export application artifacts, such as configuration data, from your 4.0 or 4.5 deployment.

1. Perform a full synchronization of all the nodes in the cluster where IBM® Connections 4.0 or 4.5 is deployed.
   Note: The migration tool does not migrate custom fields in IBM Connections configuration files. Nor does it migrate the validation.xml file. This file is needed by the Struts validation framework and is accessed when IBM Connections starts. To ensure that your custom fields and files are usable after upgrading, see the Saving your customizations and Post-migration tasks topics.
2. Open a command prompt on the version 4.0/4.5 system, change to the migration directory and run the following command:
   Note: The migration tool does not migrate the content stores. For more information about migrating the content stores, see the Content store migration topic.
   • AIX® or Linux:

     ./migration.sh lc-export

   • Windows:

     migration.bat lc-export

   • IBM i:
     Start Qshell and run the following commands:

     export USER_INSTALL_ROOT=/QIBM/UserData/WebSphere/AppServer/<VERSION>/ND/profiles/dmgr  
     export WAS_CELL=cellname 
     cd /QIBM/ProdData/IBM/Connections/migration 
     migration.sh lc-export

   Notes:

   • The lc-export command exports the following data:
     • Configuration files in the LotusConnections-config directory. You can find this directory in a the following location:
       • profile_root/config/cells/DM_cell_name/LotusConnections-config
     • Properties files in the connections_root directory

   • The exported data is stored in the migration/work directory. Check the log file to validate the export. 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-20101215_1534_26.log

     • Windows:

       C:\Documents and Settings\Administrator\lc-migration-20101215_1534_26.log

     • IBM i:

       /home/<username>/lc-migration-20101215_1534_26.log

       Note: The value of <username> is the user who runs this export command.
   • You can reuse the 4.0/4.5 content stores or copy them to your new content store. For more information, see the Content store migration topic.
3. Back up the migration directory to a location outside your 4.0/4.5 deployment.