The iWay Service Manager migration process involves migrating the following types of data:

• System level information (such as, environment variable settings).
• iWay SM Server support items (such as, configuration files and custom jar files).
• iWay application design-time data and metadata.
• iWay application run-time data and metadata.

In context of an iWay migration, an application is a group of related iWay channels or listeners, possibly sharing dependencies. An application can contain a single channel or listener, several channels, or all channels and listeners on a given server.

Note: As a general rule, we suggest that you create one archive file (using Archive Manager) for the Registry contents and one package (using Package Manager) for each configuration (instance) of iWay Adapter Manager or Service Manager.

Whether the bulk of your migration consists of using archives or packages is largely determined by how your application was built and deployed. If you created your application through registry-based channels, you would use archives to migrate them. If you built listeners directly in the Adapter Manager (blue) console, you would use packages.

The following tables itemize the system level information, iWay server components, and the iWay design-time and run-time components that you can migrate. Each table identifies the component, its format and location, and the tool or method used to migrate the component.