Export application artifacts, such as configuration data, from your 4.5 or 5.0
deployment.
About this task
To export application data from your IBM® Connections
4.5 or 5.0 deployment, complete the following steps:
Procedure
-
Fully synchronize of all the nodes in the IBM Connections
cluster.
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 the upgrade is complete, see the
Saving
your customizations and
Post-migration tasks
topics.
-
Open a command line on the IBM Connections 4.5 or 5.0
system, change to the connections_root/migration directory and run the
following command:
Note: The migration tool does not migrate the content stores. For more information, see
Content store migration.
- AIX® or Linux™:
./migration.sh lc-export
- Windows™:
migration.bat
lc-export
Notes:
- The lc-export command exports the following data:
- Configuration files in the LotusConnections-config directory. You can find
this directory in 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 /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
- You can reuse the IBM Connections 4.5 or 5.0 content
stores or copy them to your new content store. For more information, see the Content store
migration topic.
- The properties that you export are no longer used in IBM Connections 5.5 due to a change in
technology used in the product. Therefore, you do not see these properties if you import application
artifacts after you migrate to IBM Connections 5.5, this is expected behavior.
-
Back up the /work directory to a location outside your IBM Connections deployment.
What to do next
Continue with the next task in the migration process.