Preparing to migrate a stand-alone application server node
to WebSphere® Application Server Version 8.5 for z/OS® includes
activities related to inventorying your existing configuration as
well as generating CNTL and DATA datasets that you will use in the
actual migration.
Before you begin
Supported configurations: This
article is about configuration migration, such as migrating deployment
managers and federated nodes in a network deployment environment.
The Application Migration Toolkit for WebSphere Application Server
provides support for migrating applications from previous versions
of WebSphere Application Server to the latest product version. For
information about migrating applications, read more about the Application
Migration Toolkit.
sptcfg
Read Overview of migration, coexistence, and interoperability and Premigration considerations.
Migrating a stand-alone application server node is relatively
simple because it consists of a single server and a daemon.

You might have configured
multiple application servers inside a stand-alone application server
node. Generally, this configuration is not recommended; but if you
have this configuration, the migration utilities will migrate all
servers in the node just as it would all the servers in a Network
Deployment application server node.
WebSphere Application Server for z/OS
Version 8.5 supplies migration
jobs in the target dataset that you allocate when you generate your
migration jobs. Use these jobs to perform the actual migration.
- BBOWMG1B: Sets an XML flag to indicate the transaction logs are
to be cleared.
- BBOWMG2B: Sets the XML flag back to the normal state.
- BBOMBHFS or BBOMBZFS: Allocates and mounts the file system that
will be the target for the migration.
- BBOWMG3B: Performs the migration.
- BBOWBPRO: Creates the Websphere Application Server home and default
profile.
- BBOWBPRE: Runs the migration pre-upgrade process.
- BBOWBPOS: Runs the migration post-upgrade and finish-up (change
file permission) processes.
- BBOMBCP: Copies the generated Job Control Language (JCL) procedures
to start the servers to the specified procedure library. If your Version 8.5 configuration uses
different JCL start procedure names, this utility updates the new Version 8.5 configuration, and
substitutes your new JCL names for the names that existed in your
previous configuration.
For help, see Troubleshooting migration.
Procedure
- Inventory your configurations.
Print this
procedure, and enter the values for your configurations in the appropriate
columns of the following tables.
- WebSphere Application Server for z/OS Version 6.1, 7.x, or 8.0 configuration general information:
Table 1. Configuration general information. Enter your values:Item |
Value |
Cell short name: |
|
Cell long name: |
|
Sysplex name: |
|
Location of original Version 6.1, 7.x, or
8.0 configuration datasets: |
|
WebSphere Application Server
Version 6.1, 7.x, or 8.0 home directory (configuration file system): |
|
- WebSphere Application Server for z/OS Version 6.1, 7.x, or 8.0 stand-alone application server
node:
Table 2. Server node information. Enter your values:Item |
Value |
Configuration mount point: |
|
Configuration file system
dataset: |
|
Home directory: |
Default: /AppServer
Your value: ___________________
|
WebSphere Application Server SMP/E home: |
Default: /usr/lpp/zWebSphere/V5R1M2
Your value: ___________________
|
Controller Job Control Language
(JCL) start procedure: |
|
Servant JCL start procedure: |
|
Daemon JCL start procedure: |
|
- WebSphere Application Server for z/OS Version 8.5 installation
information:
Table 3. Installation information. Enter your values:Item |
Value |
Product dataset HLQ: |
|
Product directory (SMP/E
target for Version 8.5): |
|
WebSphere Application Server Version 8.0 in LPA/LNKLST?: |
__ No
__ Yes
|
- Produce migration CNTL and DATA datasets for the node.
You must provide a set of CNTL and DATA datasets for the
migration utilities to read in order to perform the migration. Generate
a set of customized jobs for the node in your configuration that you
want to migrate.

Some important points
about these steps:
The purpose of creating these customized CNTL and DATA
datasets is to give the migration utilities access to key information
about your new Version 8.5 configuration as well as access to shell scripts customized with
this new information. The migration utilities get the bulk of the
configuration information from your existing Version 6.1, 7.x, or
8.0 configuration file system.