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


Migrating a stand-alone server using the migration wizard

Migrate a stand-alone server from an older version to a newer version of WebSphere® ESB using the migration wizard.

Before you begin

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.
Note: The migration wizard supports only WebSphere ESB profiles. If you have WebSphere Application Server profiles, you must use the migration commands.
Make sure that the following conditions are met before you start the migration process:
  • Ensure that your system meets all hardware and software requirements for installing WebSphere ESB version 6.2, and that you have enough space (including temporary space) for your installation. See http://www.ibm.com/support/docview.wss?uid=swg27006912 for more information.
  • If you are migrating on the same physical computer system on which the older version of WebSphere ESB resides, you have installed the new version of WebSphere ESB side-by-side the old version on the same system.
    Note: If you plan to migrate to a new physical computer system then use the alternate procedure described in Migrating to a remote system. Or, if you plan to upgrade the version of the operating system on the computer that is running WebSphere Process Server, then use the alternate procedure described in Migrating from an operating system that is no longer supported.
  • The profile in the older WebSphere ESB which you are migrating is stand-alone (not federated to a cell).
  • Sufficient disk space is available for the migrated profile and its backup. See Premigration considerations for WebSphere ESB for disk space requirements.
Make sure that you have completed the following tasks before you start the migration process:
  • Back up the databases that support version 6.0.2.x or version 6.1.x WebSphere ESB components.
Procedure
  1. Log on as the root user on a Linux® or UNIX® system, or as a member of the Administrator group on a Windows® system.
  2. Stop the version 6.1.x or version 6.0.2.x server if it is running on the node to be migrated. Use the stopServer command from the profile_dir/bin directory for the profile of the affected server, or stop the server from the profile's First steps console.

    For more information about the stopServer command see the stopServer command. Use the following syntax:

    • For Linux operating systemFor UNIX operating system On Linux and UNIX platforms: profile_root/bin/stopServer.sh server_name
    • For Windows operating system On Windows platforms: profile_root\bin\stopServer.bat server_name
    If security is enabled, use one of the following commands instead. The user name provided must be a member of the operator or administrator role.
    • For Linux operating systemFor UNIX operating system On Linux and UNIX platforms: profile_root/bin/stopServer.sh server_name -username user_ID -password password
    • For Windows operating system On Windows platforms: profile_root\bin\stopServer.bat server_name -username user_ID -password password

    On the Windows operating system, even if security is enabled, the -username and -password parameters do not have to be specified if the server is running as a Windows service. In this case, the parameters are automatically passed into the script that the Windows service uses to shut down the system.

    Note: Before you start the migration process, you must stop the server from which you are migrating. It is not necessary to have that server running in order to migrate its configuration. The migration tools can retrieve all of the configuration data while the server is stopped.
  3. Optional: Create a new version 6.2 profile as the migration target using the Create new profile option in the migration wizard.
    For more information about creating target profiles, refer to Target profile considerations.
  4. Identify, in advance, the pre-existing information required for the migration, as listed below:
    Installation root directory
    See WBIPreUpgrade command-line utility for a description of the currentWebSphereDirectory parameter.
    Migration backup directory name
    See WBIPreUpgrade command-line utility for a description of the backupDirectory parameter.
    Administrative security user name (required if adminstrative security is configured)
    See WBIPostUpgrade command-line utility for a description of the -username parameter.
    Administrative security password (required if adminstrative security is configured)
    See WBIPostUpgrade command-line utility for a description of the -password parameter.
    Source profile name
    See WBIPostUpgrade command-line utility for a description of the -oldProfile parameter.
    Target profile name
    See WBIPostUpgrade command-line utility for a description of the -profileName parameter.
    Port value assignments (optional)
    See WBIPostUpgrade command-line utility for a description of the -replacePorts and -portBlock parameters.
    Note: This applies only if you are migrating from version 6.0.2.x toversion 6.2.
  5. Invoke the migration wizard.
    Invoke the migration wizard in one of the following ways:
    • From the WebSphere ESB First Steps console, select Migration wizard.
    • Run one of the following scripts (depending upon your operating system) stored in the install_dir/bin directory:
      • For Linux operating systemFor UNIX operating system On Linux and UNIX platforms: wbi_migration.sh
      • For Windows operating system On Windows platforms: wbi_migration.bat
      Note: You can optionally change the default trace setting (*=all=enabled:com.ibm.ws.migration.common.*=all=disabled) when invoking the migration wizard. The default trace setting enables tracing on only certain classes, but you can change the default to either enable full tracing or disable all tracing.
      • To enable full tracing, run one of the following scripts to invoke the migration wizard, depending on your operating system:
        • For Linux operating systemFor UNIX operating system On Linux and UNIX platforms: wbi_migration.sh -W -migrationPanel.traceString="*=all=enabled"
        • For Windows operating system On Windows platforms: wbi_migration.bat -W -migrationPanel.traceString="*=all=enabled"
      • To disable all tracing, run one of the following scripts to invoke the migration wizard, depending on your operating system:
        • For Linux operating systemFor UNIX operating system On Linux and UNIX platforms: wbi_migration.sh -W -migrationPanel.traceString="*=all=disabled"
        • For Windows operating system On Windows platforms: wbi_migration.bat -W -migrationPanel.traceString="*=all=disabled"

    For information about what processing the migration wizard actually performs, see What the migration wizard does.

  6. Follow the prompts for the migration wizard as described in Running the migration wizard.
  7. If you are migrating from version 6.0.2 to version 6.2.x you need to create the common database.

    For information, see Creating the common database and configuring the recovery subsystem when migrating from version 6.0.2 to version 6.2.x.

  8. If required, manually update the databases used by WebSphere ESB. Some database changes required by new versions of WebSphere ESB are made automatically. However, if you have Business Space configured, or if the server has insufficient permissions to access the database schema, or other database-specific requirements are not met, you must update the database manually. For more information see Upgrading databases for migration.

Results

You have now migrated your stand-alone server.

What to do next

Verify that the migration has been successful.

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_sa_wiz.html
Copyright IBM Corporation 2005, 2010. All Rights Reserved.
This information center is powered by Eclipse technology (http://www.eclipse.org).