If you have iWay Service Manager patches applied to support your application on the source server, you must apply them on the target server. This is only necessary if you are running the same version of iWay Service Manager in your target environment as that in the source environment. If you are running a newer version of iWay, apply the latest available cumulative patch to bring the target iWay Service Manager behavior up to date.

See the current iWay Release Notes or contact iWay Customer Support if you have any questions.

During development of your application, custom Java code may have been written, either by iWay consultants or in-house staff. To satisfy the application dependencies on them, copy the custom Java agents from [IWAYHOME]/lib on the source environment to the corresponding directory on the target environment.

For information on custom iWay agents and functions, see the iWay Adapter Manager Programmer's Guide.

To completely duplicate the functionality of an iWay Service Manager that has multiple configurations, the migrated version must have similarly named configurations. The new iWay Service Manager will be installed with the single default configuration named base. Therefore, you must manually recreate all other configurations that were on the original iWay Service Manager. For instructions on creating a configuration, see the iWay Service Manager User's Guide.

If your application requires server configurations other than the default base configuration, additional system services (on Windows) or startup scripts (on Unix and Linux) will need to be created. For Windows information, see How to Create a Windows Service for a New Configuration in the iWay Service Manager User's Guide. For Unix and Linux information, see How to Start a Configuration as a Service on a Non-Windows Platform in the iWay Service Manager User's Guide.

Using the target iWay Service Manager console, create user logins and permissions for your iWay developers and administrators, based on the source Service Manager. For details on creating users, see the iWay Service Manager User's Guide.

If the application you are migrating relies on public key cryptography for security, set up the Key Store of the target server as described in the Configuring Keystores section of the iWay Service Managers User's Guide.

Set up the iWay Designer to have access to the new (target) Repository. If you have installed iWay Service Manager and Designer on the same Windows machine the default Repository definition will be sufficient, otherwise, use the instructions in this section to configure a repository.

It can be advantageous for Designer to have access to both the target iWay server and the source server for certain migration operations. If there is adequate connectivity and the source server is up, you can follow this procedure to create a connection to the source server Repository.