The process of moving applications, configuration, and
databases from an earlier version of WebSphere Business
Monitor to this version of IBM® Business Monitor is
referred to as version-to-version migration, or simply migration.
What is version-to-version migration?
Version-to-version migration refers to
the movement of profiles, applications, and data associated with an
earlier version of WebSphere Business Monitor to a newly installed
version of IBM Business Monitor.
IBM Business Monitor Migration roadmap
The IBM Business Monitor migration
roadmap shows the high-level tasks involved in a version-to-version
migration.
Runtime migration
You can use runtime migration procedures and tools in production
environments to migrate topology configuration, applications, and
databases to the new version of IBM Business Monitor.
Supported source migration paths
The following product and version combinations are supported as sources for version-to-version migrations to IBM Business MonitorV7.5.1.
Migration types
Runtime migration supports the migration of stand-alone
environments and network deployment environments.
Runtime migration tools
Migrating stand-alone and network deployment environments
requires that you manage the production environment (start and stop
the deployment manager, servers, and nodes), migrate configuration
profiles, upgrade product databases, and migrate application data.
The runtime migration procedures guide you through the process and
the runtime migration tools are used to perform the required steps.
Profiles The runtime migration tools support the migration of IBM Business Monitor and WebSphere® Application Server source
profiles to the same profile type on the migration target.
Mixed-version environments
Version-to-version migration of network deployment-based
production environments frequently results in a period of time when
the network deployment environment is running applications on different
versions of IBM Business Monitor.
This concept is referred to as mixed versions.
Databases IBM Business Monitor uses
several product databases that are either automatically migrated or
must be manually migrated as part of the runtime migration procedure.
Downtime requirements
Stand-alone and network deployment migrations both require
a period of time during which the applications are unavailable.
What gets migrated
When you use the IBM Business Monitor runtime
migration procedures to migrate to IBM Business MonitorV7.5.1, the
following items are migrated: user applications, profile configuration
data, and data sources and providers.