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


Migrating a deployment manager using the migration wizard

Migrate a deployment manager 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.
Note: Migrate the WebSphere ESB version 6.0.x or 6.1.x deployment manager to version 6.2 before migrating the managed nodes that comprise the cell. The deployment manager must always be at the highest release and fix level within a cell in order for it to manage all nodes in the cell. A version 6.2 deployment manager can manage version 6.1.x and version 6.2 managed nodes. For migrations from version 6.1.x, this allows a cell to be upgraded to a new release one node at a time, with minimal impact to the applications that are running within the cell. For migrations from version 6.0.2.x, to keep the cell running with minimal down time, you must migrate to version 6.2 in two stages: first from version 6.0.2.x to version 6.1.x, and then from version 6.1.x to version 6.2. Alternatively you can shut down the entire cell and migrate in a single step, directly from version 6.0.2.x to version 6.2.

Members of a cluster cannot be running different versions (6.0.2.x, 6.1.x, 6.2) of WebSphere ESB. If you have configured a cluster containing servers running different versions, all the members running earlier versions of WebSphere ESB must be stopped before you start the first version 6.2 cluster member. Also, once you start a version 6.2 cluster member, do not start any version 6.1.x or 6.0.2.x cluster members in that cluster.

Restrictions exist on using mixed-release cells. For more information see "Restriction on using mixed-release cells" in the WebSphere Process Server information center.

Make sure that the following conditions are met before you start the migration process: Make sure that you have completed the following tasks before you start the migration process:
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. Identify, in advance, the pre-existing information required by the migration wizard, as listed below:
    Cell name
    Name of the cell managed by the deployment manager that you are migrating. The new version cell name must match the name in the old version's configuration.
    Node name
    Name of the node that you are migrating. The new version node name must match the name in the old version's configuration.
    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.
  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. Stop the deployment manager that you are about to migrate. Use the stopManager command from the deployment manager's profile_dir/bin directory or from the deployment manager's First steps console.

    Use the following syntax:

    • For Linux operating systemFor UNIX operating system On Linux and UNIX platforms: profile_root/bin/stopManager.sh
    • For Windows operating system On Windows platforms: profile_root\bin\stopManager.bat

    If you have security enabled, specify the -username and -password parameters of the command. For more information about the stopManager command see the stopManager command.

    Note: You must stop the previous version deployment manager before you start the migration process. If you do not, any configuration changes you make during migration process will not be migrated to the target profile.
  5. Invoke the migration wizard from the WebSphere ESB to which you are migrating.
    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 you need to manually update the Common database, do so now.
    Note: This task only applies when migrating from version 6.1 to version 6.2.
    See Upgrading the Common database manually for instructions. Normally, database changes required by new versions of WebSphere ESB are made automatically. When the server is first started the database tables are migrated to the new schema version. However, in cases in which the server has insufficient permissions to access the database schema, or other database-specific requirements are not met, you must update the database manually.
  9. Start the version 6.2 deployment manager.
    CAUTION:
    When the version 6.2 deployment manager is started, the federated nodes synchronize with the migrated deployment manager. This synchronization causes the applications to be reinstalled. If you have any applications running on active servers, those applications will appear to restart and be unavailable for a very short time.
    To start the deployment manager, use the startManager command from the profile_dir/bin directory or the First steps console. See startManager command for more information on the startManager command.
  10. Optional: Uninstall the version 6.0.x or 6.1.x deployment manager.

    Perform this step only after you are certain that you have successfully migrated the configuration of the deployment manager that you intend to delete. For more information about uninstalling, see Uninstalling the software.

Results

Your deployment manager is now migrated.

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