WebSphere Enterprise Service Bus for z/OS, Version 6.2.0 Operating Systems: z/OS


Migrating a managed node

Migrate an older version of WebSphere Process Server or WebSphere Enterprise Service Bus node to a newer version.

Before you begin

Before migrating any managed nodes in the cell, you must first migrate the deployment manager. See Migrating a deployment manager.
Procedure
  1. On the version 6.0.x or 6.1.x system, generate the migration jobs from the WebSphere® Application Server Customization ISPF panels:
    1. In a TSO session, enter the following command:
      ex 'high_level_qualifier.sbboclib(bbowstrt)' 'appl(bb61) lang(enus)'
      Where high_level_qualifier is the high-level qualifier of the WebSphere Application Server installation libraries.
    2. Select 4 - Migrate a Node, then select 3 - Migrate a federated node. The WebSphere Application Server migration jobs are generated in two PDS data sets that you created when you worked through the WebSphere Application Server Customization ISPF panels.
  2. Customize the generated migration jobs to pick up the user supplied parameters. For a managed node, customize the following jobs: BBOWMG1F, BBOWMG2F, and BBOWMG3F.
    1. In the installed WebSphere ESB JCL PDS(ZWESB.**.SBPZJCL), locate the corresponding sample WebSphere Process Server migration jobs BSBWMG1F; BSBWMG2F and BSBWMG3F. These jobs invoke the WebSphere ESB script wbimigrt2.sh, which is very similar to the WebSphere Application Server script bbomigrt2.sh. The wbimgrt2.sh script invokes the migration utilities WBIPreUpgrade.sh and WBIPostUpgrade.sh.
    2. Edit the BSBWMGxF jobs to make use of the parameters generated by the WebSphere Application Server Customization panels, which are now present in the BBOWMGxF jobs.
  3. Stop the version 6.0.x or 6.1.x managed node server but ensure that the deployment manager is running. See Stopping managed servers for more information.
  4. Back up the WebSphere ESB database. If necessary, you can then recover the version 6.0.x or 6.1.x system later.
  5. Back up the file system on the source managed node (the node you are migrating from).
  6. Submit the migration jobs that you have edited. The BSBWMG1F and BSBWMG2F jobs need to be run only if you had XA Connectors installed in the version 6.0.x or 6.1.x server. The BSBWMG3F job does the actual migration.
  7. Run the WBIProfileUpgrade.ant script. If you have migrated half the managed nodes, ensure that all the servers are stopped and the deployment manager is running, then run the WBIProfileUpgrade.ant command on the deployment manager's bin directory. This command only has to be run once for each cluster. If any of the nodes are still running, the command fails.
    Note: The exact syntax of the command to be run can be found in the WBIProfileUpgrade.ant.default.timestamp.log that resides in the deployment manager's temporary migration backup directory.
    For example:

    [wsadmin] Make sure the deployment manager is running and then invoke:

    [wsadmin] ws_ant.sh -f util/WBIProfileUpgrade.ant -DmigrationDir=/tmp/migrate/XXXXXX/dmgr_backup -Dcluster=ClusterT4

  8. Update the started task JCL members in USER.PROCLIB by running the BBOMMCP job from the jcl library that was generated. The job replaces the version 6.0.x or 6.1.x started task members with the newversion 6.2 members.
  9. Start the version 6.2 managed node server. See Starting a server from the MVS console for more information.

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