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


Migrating a deployment manager using command-line tools

Migrate a deployment manager from an older version to a newer version of WebSphere® ESB using the command-line tools.

Before you begin

Note: In a WebSphere ESB network deployment cell, the deployment manager must always be in a WebSphere ESB profile.
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.

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 using one of the following procedures, depending on your operating system.
    • For i5/OS operating system On i5/OS® platforms: Log on with an i5/OS user profile that has *SECOFR user class or *ALLOBJ special authority.
    • For Linux operating systemFor UNIX operating system On Linux® and UNIX® platforms: Log on as the root user.
    • For Windows operating system On Windows® platforms: Log on as a member of the Administrator group.
  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. 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.
    For more information about the stopServer command see the stopServer command. Use the following syntax:
    Note: On i5/OS platforms, you must run the scripts under QSHELL. To start a QSHELL session, open a CL command prompt and type QSH.
    • For i5/OS operating system On i5/OS platforms: profile_root/bin/stopManager
    • 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 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 i5/OS operating system On i5/OS platforms: profile_root/bin/stopManager -username user_ID -password password
    • For Linux operating systemFor UNIX operating system On Linux and UNIX platforms: profile_root/bin/stopManager.sh -username user_ID -password password
    • For Windows operating system On Windows platforms: profile_root\bin\stopManager.bat -username user_ID -password password
    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.
  4. Run the WBIPreUpgrade command, specifying the migration backup directory name and the existing WebSphere ESB directory name. The WBIPreUpgrade tool saves selected files from the install_root and profile_root directories to a backup directory you specify. See the WBIPreUpgrade command-line utility for details.
  5. Run the WBIPostUpgrade command, specifying the migration backup directory. The WBIPostUpgrade tool restores the backed up configuration in the backup directory into the new WebSphere ESB Deployment Manager profile. See the WBIPostUpgrade command-line utility for details.
    Important: Use the -createTargetProfile parameter when invoking WBIPostUpgrade. This option creates a matching required new target profile for migration. For more information about target profiles, refer to Target profile considerations.
    For i5/OS operating system Note: If you are migrating on an i5/OS platform, the target profile name must match the profile name of the source profile being migrated.
  6. 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.

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