The goal of migration is to reconstruct your earlier version of WebSphere® Application Server in a Version 8.5 environment. Coexistence allows you to create a mixed-version environment that is not in conflict and allows the nodes of all versions to start and run at the same time. Coexistence also facilitates rollback and allows one or the other version to run at one time. Interoperating is exchanging data between two coexisting product installations or between products on different systems.
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.
sptcfgCan I simply point to the new WebSphere Application Server for z/OS® Version 8.5 datasets and restart my servers?
No. WebSphere Application Server for z/OS Version 8.5 requires that you migrate your Version 6.1 or later configuration to the Version 8.5 level.
Is migration a node-by-node activity?
Yes. The process of migrating the configuration involves running the supplied utilities against each node in your configuration.
Although a stand-alone application server only has one node, that node needs to be migrated. The steps are essentially the same as the steps for migrating any other node, except that you do not have to have a deployment manager running. Read Migrating a z/OS stand-alone application server: Checklist for a checklist of activities for migrating a stand-alone application server node.
What do the migration utilities do?
The migration utilities serve the following purposes:
Utility | Purpose |
BBOWMG1B (stand-alone
application server migrations) BBOWMG1F (federated node migrations) |
Enables all servers on
the node being migrated to be configured to start in Peer Restart
and Recovery (PRR) mode After this job completes, you must start all servers on the node being migrated and wait for them to stop. PRR processing mode resolves any outstanding transactions, clears the transaction logs, and stops the server. This job is not needed for a deployment manager migration, and it is optional for configurations that do not use distributed transaction (XA) connectors. This job is required only if you are using XA adapters and you need to migrate the XA logs. Check your resource providers in the Version 6.1 or later administrative console by going to Resources > JDBC providers and checking to see if you have chosen any XA providers such as DB2®, Apache Derby, and so on. |
BBOWMG2B
(stand-alone application server migrations) BBOWMG2F (federated node migrations) |
Disables
PRR mode and returns all servers to normal operating state You are not required to start all servers after this job completes. This job is not needed for a deployment manager migration, and it is optional for configurations that do not use XA connectors. This job is required only if you are using XA adapters and you need to migrate the XA logs. Check your resource providers in the Version 6.1 or later administrative console by going to Resources > JDBC providers and checking to see if you have chosen any XA providers such as DB2, Apache Derby, and so on. |
BBOMBHFS
or BBOMBZFS (stand-alone application server migrations) BBOMDHFS or BBOMDZFS (deployment manager migrations) BBOMMHFS or BBOMMZFS (federated node migrations) |
Optional: Creates a file system and mount point for the Version 8.5 configuration root,
and mounts the file system If you want to use an existing file system to contain the Version 8.5 configuration, you must manually create the mount point specified when you create the migration definition and verify that the file system is mounted rather than run this job. In either case, the configuration file system and mount point must be created and the file system must be mounted before proceeding with the migration. |
For stand-alone
application server migrations, the following utilities:
For deployment manager migrations, the following utilities:
For federated node migrations, the following utilities:
|
BBOWMG3x runs the complete migration of the node from Version 6.1 or later to Version 8.5. BBOWxPRO just creates the WebSphere Application Server home and default profile. BBOWxPRE just runs the migration pre-upgrade process. BBOWxPOS just runs the migration post-upgrade and finish-up (change file permission) processes. |
BBOMBCP (stand-alone application
server migrations) BBOMDCP (deployment manager migrations) BBOMMCP (federated node migrations) |
Copies the generated Job
Control Language (JCL) procedures to start the servers to the specified
procedure library If you choose to have your Version 8.5 configuration make use of different JCL start procedure names, this utility updates the new Version 8.5 configuration, substituting your new JCL names for the names that existed in your original Version 6.1 or later configuration. |
Where should you run the migration jobs?
Run the jobs on the same system on which the node being migrated resides.
What happens when a node is migrated?
The migration utilities transform the contents of your present WebSphere Application Server Version 6.1 or later configuration file system and merge them into a new, separate Version 8.5 configuration file system.
Are my existing configuration lost during migration?
During the migration, the original WebSphere Application Server Version 6.1 or later configuration tree is unaffected. If for some reason the migration fails before completing, your previous configuration still exists.
If my node has multiple application servers, are all of them migrated?
Yes. The utility detects all servers and migrate all, including the node agent. One invocation of the migration utilities against the node migrates all the servers in the node.
Must I stop the servers in a node to perform the migration?
Yes. In a multinode configuration it is possible to have the other nodes still running. But any node that you want to migrate must have its servers stopped.
When an application server node that is part of a WebSphere Application Server, Network Deployment configuration is being migrated, the previously migrated Version 8.5 deployment manager for that cell must be running. This is because part of the migration involves the use of the wsadmin scripting function to synchronize the newly migrated application server node with the deployment manager. The deployment manager must be running in order to perform that synchronization.
Is it possible to have a cell operating with only some of the nodes migrated and others not?
Yes, that is possible. WebSphere Application Server Version 6.1 or later can coexist with Version 8.5 in the same cell and on the same logical partition (LPAR).
Can my newly migrated WebSphere Application Server for z/OS Version 8.5 deployment manager still communicate with the Version 6.1 or later nodes?
Is there a sequence to performing a multinode migration?
Is it possible to have cells at WebSphere Application Server for z/OS Version 8.5 coexist with other cells at Version 6.1 or later?