Friday, 27 August 2010

Using the new IBM Lotus Connections 2.5 migration tool

A useful article from the IBM China labs, worth a read if you're looking to migrate to Lotus Connections 2.5 - I'm guessing that there'll be a new version along once the next release of Connections is available: -

This article describes the new IBM® Lotus® Connections 2.5 migration tool, including its architecture, how to use it, and how to troubleshoot errors and perform a recovery. The new migration tool is based on Extensible Stylesheet Language Transformation (XSLT) technology and provides a simple, effective way to migrate all necessary artifacts, freeing you from manually reapplying configurations.


Migrating artifacts is a key task when you are migrating your existing Lotus Connections version. Using the migration tool in version 2.0.1, you were able to accomplish this task to some extent; for example, you could migrate some configuration and all data files. You still had to customize many configurations manually, which is one of the most painful tasks in the migration process.

The newly added features in Lotus Connections 2.5 mean that many more configurations must be migrated. The latest migration tool, which is based on XSLT technology, provides a simple and effective way to migrate all necessary configurations and data files. With its help, you don't need to manually reapply all configurations.

This article explains how to use the Lotus Connections 2.5 migration tool, including how to troubleshoot errors and perform a recovery, so that you can understand the migration tool and correctly migrate the artifacts of your existing Lotus Connections environment.

It is assumed that you have a good understanding of IBM WebSphere® Application Server and a general understanding of XSLT and XML Path Language (XPath) technology.

Using the new IBM Lotus Connections 2.5 migration tool

No comments:

Note to self - use kubectl to query images in a pod or deployment

In both cases, we use JSON ... For a deployment, we can do this: - kubectl get deployment foobar --namespace snafu --output jsonpath="{...