Backing up resources before migration

Back up your resources before you start to migrate components to IBM® Integration Bus Version 10.0.

Before you begin

To plan your migration strategy, read Preparing for migration.

Before you complete migration tasks, back up your current resources by completing the following steps.

Optional: If your message flows access user databases through an ODBC connection, back up the ODBC files that you use for these connections.
Take a copy of these files and store them safely in a different location.
Optional: If you have created or configured configurable services for your message flows, record the properties of all your configurable services.
For example, a message flow might access databases through a JDBC connection, for which you have set up a JDBCProvider configurable service. Run the mqsireportproperties command for these services, take a copy of the output, and store it safely in a different location.
Back up your IBM Integration Toolkit or WebSphere® Message Broker Toolkit workspace and resources; for example, message flow files, message set definition files, Java™ files, ESQL files, mapping files, XML Schema files, and BAR files.
- Export all your projects from your current IBM Integration Toolkit or WebSphere Message Broker Toolkit.
- Archive your workspace resources:
  - If you manage your workspace resources in a shared repository, for example CVS, follow standard backup procedures for safeguarding versions. Create a version for storing Version 10.0 resources.
  - If you maintain your workspace resources on a local or shared disk, copy your workspace directory to a different location.

After you have backed up your resources, update your ODBC definitions by following the instructions in Updating ODBC definitions when you migrate to IBM Integration Bus Version 10.0.