[z/OS]

Migrating a federated node

After the deployment manager is migrated and restarted, you can perform the actual migration of its federated application server nodes by running the JCL jobs that you generated. When you generated your custom migration jobs, you also created customized instructions for preparing and running the migration jobs in the BBOMMINS members of the CNTL data set that was used to generate your jobs. Follow these customized instructions to complete the process of migrating your federated nodes to Version 6.1.

Before you begin

For help in troubleshooting problems when migrating, see Troubleshooting migration.

Procedure

  1. Ensure that the application servers and the node agent are stopped for the federated node being migrated.

    You must stop the Version 5.x or 6.0.x federated node before proceeding.

  2. Ensure that the newly migrated deployment manager is up and running.

    In order for the application server node to be properly migrated, the deployment manager must be running. In order for this migration to work, the deployment manager must be up and listening on its SOAP port.

    Check Off Item
      Access the administrative console of the WebSphere Application Server Version 6.1.x deployment manager. This validates that the deployment manager is running.
    Check Off Item
      Ensure that the WebSphere Application Server Version 6.1.x copy of the code is running. Under "About your WebSphere Application Server," the build number should begin with W61.
  3. Create and mount a new Version 6.1.x configuration file system.

    Before you perform the migration, Version 6.1.x requires that a configuration file system be present for your new configuration. You can run BBOMMHFS or BBOMMZFS to create and mount a new configuration file system, or you can mount one manually. Either way, you must have a file system for your Version 6.1 configuration created and mounted before you proceed. This configuration file system is the target of the migration; your Version 5.x or 6.0.x configuration file system is the source.

    BBOMMHFS or BBOMMZFS creates a mount-point directory, allocates the configuration's file system, and mounts the file system at whatever value you specified for the mount point when you generated your migration jobs.

    Before you proceed, ensure that you have allocated, created, and mounted your configuration file system data sets either manually or using BBOMMHFS or BBOMMZFS. The mount point should be owned by the WebSphere Administrator user ID and have permissions of at least 755. The new configuration file system structures should be included in BPXPARM so that they will be mounted at the next IPL.

  4. Submit BBOWMG1F and BBOWMG2F.
    Note: If you are not using XA connectors, submitting BBOWMG1F and BBOWMG2F is optional. However, you should submit both jobs to ensure that your transaction logs are clear.

    BBOWMG1F enables all servers on the federated application server node being migrated to start in PRR processing mode. PRR processing mode resolves any outstanding transactions, clears the transaction logs, and terminates the server. BBOWMG2F disables PRR mode and returns all servers to normal operating state.

    Follow these steps to clear the XA transaction logs:
    1. Submit the job BBOWMG1F, and verify a return code of 0.
    2. Restart the federated application server, and wait for it to perform PRR processing and terminate automatically.
    3. Submit the job BBOWMG2F, and verify a return code of 0.
  5. Copy your generated JCL procedures.

    The migration utility BBOMMCP copies the generated JCL procedures to start the servers to the specified procedure library. Your Version 6.1.x configuration must use different JCL procedures from those used by your Version 5.x or 6.0.x configuration. This utility will update the new Version 6.1.x configuration, substituting your new JCL names in place of the names that existed in your original Version 5.x or 6.0.x configuration.

    Caution: This utility copies the generated JCL to your procedure library. If you specified the same names as you used in your Version 5.x or 6.0.x configuration when you generated your migration jobs, this utility will overlay the existing procedures. If you are using the same names, make sure that you back up the existing Version 5.x or 6.0.x procedures before running this utility in case you need to roll back later.

    Submit BBOMMCP, and verify a return code of 0.

  6. If you specified new procedure names, update your RACF STARTED profiles for the controller and daemon.
    The STARTED profile used by controller regions is based on the procedure name and JOBNAME. You must ensure that a STARTED profile will apply so that the proper identity will be assigned to the started task. If your Version 5.x or 6.0.x controller JCL procedure name is AZACR and you specified AZ1ACR for Version 6.1, for example, then you would need to create a STARTED profile for that new procedure name:
                  new controller      same identity used in
                     JCL name         V5.x or 6.0.x configuration
                        |                    |
     RDEFINE STARTED AZ1ACR.* STDATA(USER(AZACRU) GROUP(AZCFG) TRACE(YES))
    Note:
    • Do not use a different user ID to start. There are other things tied to the user ID, and other changes would also be required if you change the user ID.
    • If your original STARTED profile was generic, STARTED AZ*.* ... for example, you would not need to create a new STARTED profile.
    • Servant region STARTED profiles are based on JOBNAME, not procedure name. So there is no issue with the servant when you use a different procedure name.
    • Daemons and node agents are controllers; so, using different procedure names for these implies a new STARTED profile.
  7. Delete and redefine the log stream if necessary.
    Perform this step only if you previously configured the transaction XA partner log or compensation log on the Version 5.x or 6.0.x server to use a log stream.
    1. Make sure that the node is shut down.
    2. Delete and redefine the log stream.

      You can use the BBOLOGSD and BBOLOGSA jobs that were created during Version 5.x or 6.0.x customization if you configured the server initially to use the log stream.

      The following sample shows an example of such a job:
      //RLSP1A  JOB 'xxxx,yyy,?','USERID',MSGCLASS=H,
      //         CLASS=J,MSGLEVEL=(1,1),REGION=4M,NOTIFY=&SYSUID
      //STEP1    EXEC PGM=IXCMIAPU
      //STEPLIB  DD   DSN=SYS1.MIGLIB,DISP=SHR
      //SYSPRINT DD SYSOUT=*
      //SYSIN    DD *
      
      DATA TYPE(LOGR) REPORT(YES) /* Default to show output of job */
       DELETE LOGSTREAM NAME(P1ACEL6A.W51ASA2.D)
       DEFINE LOGSTREAM NAME(P1ACEL6A.W51ASA2.D)
              LOWOFFLOAD(20)
              HIGHOFFLOAD(79)
              STG_DUPLEX(YES)
              DUPLEXMODE(UNCOND)
              STG_DATACLAS(OPERLOG)
              STG_SIZE(5000)
              HLQ(Q10RRS)
              LS_SIZE(5000)
              LS_DATACLAS(OPERLOG)
              STRUCTNAME(WAS_LOGRLS)
      /*
      

    If you are migrating nodes in a sysplex, follow this procedure for each federated node that you migrate.

  8. Submit BBOWMG3F.

    BBOWMG3F is the job that performs the physical migration of the Version 5.x or 6.0.x node to Version 6.1.x based on the information that you supplied when you generated your migration jobs. Submit BBOWMG3F, verify that you are getting return codes of 0, and review the log files in the temporary migration directory on the configuration file system. The migration temporary directory is temporary_directory_location/nnnnn, where temporary_directory_location is the directory specified for the temporary directory location (/tmp/migrate by default) and nnnnn is the numeric value generated for the migration identifier when you generated your migration jobs.

  9. Ensure that the old daemon is shut down.

    Ensure that all federated nodes in the same cell on this LPAR are shut down.

  10. Update daemon JCL procedure if necessary.

    WebSphere Application Server for z/OS Version 6.1.x requires that the daemon process be at the highest level of code of any of the servers that it manages on the same LPAR. It will be at the Version 6.1.x level when this federated node is started. If there are any additional nodes on the same LPAR and in the same cell as this migrated managed node, you must update the additional down-level node's daemon JCL procedure to STEPLIB to both the Version 6.1.x libraries and those of the highest-level of the down-level nodes.

    If you are migrating from Version 5.1 and you have an additional application server node on the same LPAR and in the same cell, for example, add the following to both your Version 6.1.x and Version 5.1 daemon JCL procedure's "Z" member ("Z=BBO5DMNZ" ) using your library names:

    //*STEPLIB Setup
    //*
    //STEPLIB  DD DSN=hlq61.SBBOLD2,DISP=SHR
    //         DD DSN=hlq61.SBBOLOAD,DISP=SHR
    //         DD DSN=hlq61.SBBOLPA,DISP=SHR
    //         DD DSN=hlq51.SBBOLD2,DISP=SHR
    //         DD DSN=hlq51.SBBOLPA,DISP=SHR
    //*                                 
    Note: The hlq51.SBBOLOAD library is intentionally left out of this example. It will not do any harm if it is there, but it is not needed.

    After you migrate all nodes to Version 6.1.x and before you remove the previous version's libraries from the system, you must update the daemon JCL procedure and remove the previous version's libraries from the STEPLIB concatenation. Failure to do so will result in a failure of the daemon to start.

  11. Start the new federated application server node.
    1. Start the node agent.
      The following message is displayed on the console and in the job log of BBON001:
      BBOO0019I INITIALIZATION COMPLETE FOR WEBSPHERE FOR z/OS CONTROL PROCESS BBON001
    2. Start the federated application server.

      Use the existing command that you would use to start a Version 5.x or 6.0.x application server, but replace the RACF STARTED procedure name with the value that you entered in the federated node panel for the controller procedure name when you generated your migration jobs. This command starts the Version 6.1.x federated application server. Wait until the server is finished initializing before proceeding.

      The following message is displayed on the console and in the job log of BBOS001:
      BBOO0019I INITIALIZATION COMPLETE FOR WEBSPHERE FOR z/OS CONTROL PROCESS BBOS001

    At this point, your migration to Version 6.1.x is complete.

What to do next

After you verify a successful migration to Version 6.1.x and are successfully running a migrated configuration, you should delete the following items:
  • Everything in the source configuration's file system
  • Everything in the target configuration's temporary_directory_location/nnnnn directory, where temporary_directory_location is the directory specified for the temporary directory location (/tmp/migrate by default) and nnnnn is the numeric value specified for the migration identifier when you created your migration jobs
  • The bbomigrt2.sh file



In this information ...


IBM Redbooks, demos, education, and more

(Index)

Use IBM Suggests to retrieve related content from ibm.com and beyond, identified for your convenience.

This feature requires Internet access.

Task topic Task topic    

Terms and conditions for information centers | Feedback

Last updatedLast updated: Aug 31, 2013 1:23:07 AM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=pix&product=was-nd-dist&topic=tmig_z_amn
File name: tmig_z_amn.html