In this section: |
The iWay Service Manager migration process moves the iWay environment and iWay components from one machine to another. Migration is performed for a variety of reasons, for example:
An effective migration must accurately map directories and data on the original system to the appropriate structure on the target system (which may be different from the original structure), provide methods to package data to be migrated, load that data onto the target system, and then verify that the target data and system support the intended processes and applications.
The iWay Service Manager migration process includes:
To migrate most iWay data you will use containers known as iWay packages and archives, which you create using iWay Service Manager tools. These packages and archives are files specially designed to contain iWay components, metadata, and configuration information. In this package and archive format, they can be easily added to or removed from specific server instances.
This guide focuses on moving iWay application metadata and the mechanisms used to accomplish this task. Occasionally, a migrated application will fail because of an intentional or inadvertent change to an internal iWay component, such as, an agent or adapter. Issues of this type are version specific. To review known cases, see the iWay Service Manager Release Notes on the iWay Documentation Web site, http://iwse.ibi.com/iway60/documentation/ism60/.
There are activities that are often confused with or referred to as migration, but are somewhat different and often more easily accomplished. The confusion is understandable since these activities concern either changing the software version or duplicating application functionality, which are sometimes side effects of a migration. Activities in this category are:
Upgrading to a new service pack within the same major release automatically preserves the host system, iWay Service Manager, and application configurations. For instruction on upgrading to a new service pack, see the iWay Service Manager Installation and Configuration Guide.
You can create multiple run-time configurations in an iWay Service Manager. A new configuration can be used for a completely new application or it can be closely related to an existing project, for example, application development, testing, or production. In the case of a production configuration, it is expedient to model the new configuration on the existing one. iWay Service Manager supports this kind of configuration "cloning" and copies all relevant metadata for you in one step. For instructions on creating a new configuration, see the iWay Service Manager User’s Guide.
iWay Software |