WebSphere Enterprise Service Bus, Version 6.2.0 Operating Systems: AIX, HP-UX, i5/OS, Linux, Solaris, Windows


Running the migration wizard

Run the migration wizard on AIX®, HP-UX, Linux®, Solaris, or Windows® systems to migrate WebSphere® ESB.

Before you begin

Make sure you have performed the required steps that precede the step for invoking the migration wizard. These steps differ depending on whether you are migrating a stand-alone server, a deployment manager, a non-clustered managed node, or a cluster.

About this task

Running the migration wizard is just one step in a larger series of steps required to migrate WebSphere Process Server from version 6.1.x or 6.0.2.x to version 6.2.
Note: If you have a WebSphere Application Server profile that was created in a WebSphere ESB environment, you must use the WebSphere ESB command line tools to migrate it. If you have a WebSphere ESB profile that was created in a WebSphere ESB environment, you can use either the migration wizard or the command-line tools to migrate it.
Note: The migration wizard cannot run in a non-graphical environment. Examples of non-graphical environments include the i5/OS® platform or telnet sessions. If you want to run migration in a non-graphical environment, use the WBIPreUpgrade and WBIPostUpgrade commands.
Procedure
  1. On the Welcome to the Migration wizard for WebSphere Process Server screen, read the Welcome panel to learn about the migration process, and then click Next.
  2. On the Detected version of WebSphere Process Server screen, select or specify a previous version of WebSphere ESB from which to migrate, and then click Next.

    Select the check box and enter the location of the previous installation if it does not appear in the selection list.

  3. On the Source profile selection screen, select the profile from the previous version of WebSphere ESB that you want to migrate, and then click Next.
  4. On the Target profile selection screen, you should select Create new profile to create a new, empty target profile for migration. Optionally, you can select a profile from the list of valid profiles for the version 6.2 installation, but it is strongly recommended that you use a new target profile for migration. For more information about creating target profiles for migration, refer to Target profile considerations.
    • If you selected Create new profile, enter a name for the profile and leave the host name (name of the system on which the profile will reside) as is, and then click Next.
      Note: It is recommended that you do not change the host name but if for any reason you change the host name, then after migration, you will need to manually update the host name in other places where it is configured.
    • You should consider backing up your target profile before you click Next. To decide whether to back up your target profile's configuration, consider the following suggestions:
      • If you have selected an already existing profile, you may want a backup of your target profile's configuration. Use the backupConfig command to back it up before proceeding.
      • If you are migrating a managed node, the migration will change the deployment manager's configuration. You should use the backupConfig command to back up the deployment manager's configuration before proceeding.
  5. On the Migration backup directory screen, specify a migration backup directory in which to place a backup copy of the configuration from the previous version. Depending on which version of WebSphere ESB you are migration from, the following options appear on the screen:
    • Migrating from version 6.0.2.x:

      During a migration from version 6.0.2.x to version 6.2, the back up operation backs up all of the profiles created under WebSphere ESB version 6.0.2.x installation.

      • If this is the first or only profile you are migrating in this WebSphere ESB installation, keep the Back up all existing profiles check box selected. The directory is created if it does not already exist. If the directory exists, it should be empty because the backup operation might overwrite existing backup files.
      • If you have already migrated another profile in this WebSphere ESB installation and have not made any configuration changes, you can choose not to back up the previous configuration at this point in the migration wizard. In this case, you can clear the Back up all existing profiles check box and make sure that the backup directory name is the same as that specified for the previous migration.
    • Migrating from version 6.1.x:

      During a migration from version 6.1.x to version 6.2, the back up operation backs up only the specified profile intended to be migrated from the WebSphere ESB version 6.1.x installation

      • If the directory does not already exist, it is created during migration.
      • If the directory exists, it should be empty because the backup operation might overwrite existing backup files.
    After entering the backup directory information, click Next.
  6. On the Migration settings for Applications screen, specify where the migrated applications should be located and then click Next.
    Note: The Migration settings for Applications screen appears only if you are migrating from version 6.0.2.x to version 6.2.
    You can choose any one of the following options:
    • Keep the current application installation directories.
      Restrictions: If you choose this option, the location is shared by the existing installation and the new installation. If you keep the migrated applications in the same locations as those of the previous version, the following restrictions apply:
      • Mixed-node support limitations must be followed. This means that the following support cannot be used when evoking the wsadmin command:
        • Precompile JSP
        • Use Binary Configuration
        • Deploy EJB
      • You risk losing the migrated applications unintentionally if you later delete applications from these locations when administering (uninstalling for example) your version 6.0.2.x installation.
    • Install the applications in the default directory of the target installation.
    • Install the applications in the following directory.

      In the directory field, you can either type the directory path or click Browse to search for it. It is recommended that you use the following directory path: ${USER_INSTALL_ROOT}\installedApps.

  7. On the Deployment manager option screen, you can optionally select Do not disable the deployment manager of the previous version. It is recommended that you leave this option unchecked to prevent conflicts with the version 6.2 deployment manager.
    Note: The Deployment manager option screen appears only if you are migrating from version 6.0.2.x to version 6.2.
  8. On the Port value assignment screen, select one of the options for assigning port values, and then click Next.
    Note: The Port value assignment screen appears only if you are migrating from version 6.0.2.x to version 6.2.
    You can choose to do any one of the following with the port values:
    • Use the port values assigned to the previous (source) installation.
    • Use the port values that are assigned to the specified target profile.
    • Define a block of port values starting at:

      If you select this option, enter the first value of the block of consecutive port numbers to assign.

  9. On the Additional migration options screen, enter the following information, then click Next.
    Important: The Support 6.0.x scripts in target profile check box is visible only if you are migrating from version 6.0.2.x.
    • Support 6.0.x scripts in target profile check box: If you are migrating from version 6.0.2.x, you can select this check box if you want to migrate to support script compatibility. If you select this option, the migration wizard creates the following configuration definitions of the version 6.0.2.x of WebSphere ESB:
      • Transport
      • ProcessDef
      • 6.0.2 SSL
      • 6.0.2 ORB service threadpool
      instead of the following version 6.2 configuration definitions:
      • Channels
      • ProcessDefs
      • version 6.2 SSL
      • version 6.2 ORB service threadpool

      Select this option in order to minimize impacts to existing administration scripts. If you have existing wsadmin scripts or programs that use third-party configuration APIs to create or modify your existing configuration definitions, for example, you might want to select this option during migration.

      Note: This is temporary until all of the nodes in the environment are at the newer level (for example, WebSphere ESB version 6.2.) When they are all at the new level, you should perform the following actions:
      1. Modify your administration scripts to use all of the settings for the new version (in this case version 6.2).
      2. Use the convertScriptCompatibility command to convert your configurations to match all of the settings corresponding to the new version.
        See the convertScriptCompatibility command.
        Note: When following the directions at this link to use the convertScriptCompatibility command, use the WBIPostUpgrade command rather than the WASPostUpgrade command.
    • Enter security credentials check box: If security was not enabled on the prior version of WebSphere ESB make sure the Enter security credentials check box is cleared and select Next.

      If administrative security was enabled on the version of WebSphere ESB you are migrating from, the Enter security credentials check box must be selected and a corresponding user name and password must be entered in the user name and password fields.

      If the migration wizard detects the user name and password that was configured in the earlier version of WebSphere ESB, then the Enter security credentials check box will be automatically selected and the correct user name and password will be automatically configured in the user name and password fields. If this occurs, verify that the user name entered is correct (the password will be masked) and select Next.

      If security was enabled in the prior version, but the migration wizard cannot detect the user name and password, it will check the Enter security credentials check box but leave the user name and password fields blank. If this occurs, enter the user name and password (the same as those used for administrative security in the previous version) and select Next.
      Note: Whether or not the wizard can detect the user name and password depends on which version of WebSphere ESB you are migrating from.
  10. On the Migration summary screen, check the information in the summary panel and make sure that it is correct, and then click Next to start the migration. During migration, the following panels may appear:
    • If you selected the option to create a new target profile, screens show the beginning and results of that creation.
    • Screens show the progress of the migration process.
    • If the migration is not successful, the wizard displays a failure screen. If the migration is partially successful, the wizard displays a warning screen. Correct any problems, and try the migration again.
    • If the post-migration is successful, the wizard displays an indication of success.
  11. Click Finish to exit the migration wizard.

Results

You can now start the migrated server in the WebSphere ESB environment at the new release level.


task Task topic

Terms of use | Feedback


Timestamp icon Last updated: 21 June 2010


http://publib.boulder.ibm.com/infocenter/dmndhelp/v6r2mx/topic//com.ibm.websphere.wesb620.doc/doc/tmig_vtv_sasmigwizdetail.html
Copyright IBM Corporation 2005, 2010. All Rights Reserved.
This information center is powered by Eclipse technology (http://www.eclipse.org).