About this task
Step 17 towards the goal:
Migrating Compute Grid or Feature Pack for Modern Batch using the command-line tools
Use the migration tool to migrate
the previous versions of the nodes in the configuration to
Version 8.5. Perform the following
procedure for each node that you plan to migrate to
Version 8.5.
Avoid trouble: For the migration to be successful, you must use the same source
node name and cell name for each node that you migrate to
Version 8.5.
gotcha
- Ensure that the Version 8.5 deployment manager
is running.
- Create the target node profile. Run the manageprofiles command with the appropriate parameters to create a new managed
profile. For example:
/opt/WebSphereV85/manageprofiles.sh -create -profileName node1 -templatePath
/opt/WebSphereV85/profileTemplates/managed -nodeName currentNode1Name -cellName
currentCellName -hostName mynode1host.company.com
- Run the WASPreUpgrade command to
save the current node X configuration information to a migration backup
directory. Choose a new directory for the backup files. For example:
/opt/WebSphereV85/bin/WASPreUpgrade.sh /mybackup/v70tov85node1
/opt/WebSphereV70 -oldProfile 70node1
- If the WASPreUpgrade command completed
with Success, then checking the logs for errors or warnings is not
necessary.
- Check the WASPreUpgrade console output for the following
messages: Failed with errors or Completed with
warnings.
- Look in the following logs for warnings or errors:
- migration_backup_dir/logs/WASPreUpgrade.old_profile.timestamp.log
- migration_backup_dir/logs/WASPreUpgrade.trace
- Stop the node agent. If you have Version
7.0 or above nodes running during a migration to Version 8.5, you must stop the
node agent on the node that you are migrating. If you do not stop
the node agent, you might encounter corruption problems.
- Run the WASPostUpgrade command to
restore the saved node X configuration into the new Version 8.5 managed profile. For example:
/opt/WebSphereV85/bin/WASPostUpgrade.sh /mybackup/v70tov85node1 -profileName
v70tov85node1 -oldProfile 70node1 -replacePorts TRUE -backupConfig TRUE
-scriptCompatibility TRUE -username myuser -password mypass
Avoid trouble: The script compatibility
flag on your deployment manager must be the same as the flag that
you use on your nodes.
gotcha
- If the command completed with Success, then checking
the logs for errors or warnings is not necessary.
- Check the WASPostUpgrade console output for the following
messages: Failed with errors or Completed with
warnings.
- Look in the following log files for errors or warnings:
- migration_backup_dir/logs/WASPostUpgrade.target_profile.timestamp.log
- migration_backup_dir/logs/WASPostUpgrade.target_profile.trace
Note: If the WASPostUpgrade command fails,
you might have to restore the Version 8.5 deployment manager
from the backupConfig file. If the WASPostUpgrade processing executed
the syncNode command, the deployment manager is
aware that the node X has been migrated. The node X cannot be migrated
again until you restore the deployment manager to the state before
the node X migration.
- To update the Compute Grid data in the new node, run
migrateConfigTo85.py. For example:
/opt/WebSphereV85/profiles/node1/bin/wsadmin.sh -lang jython -username myuser-password mypass -f
/opt/WebSphereV85/bin/migrateConfigTo85.py --restore -node node1
- Check the Version 8.5 deployment manager SystemOut.log for warnings
or errors.
Note: This topic references one or more of the application
server log files. As a recommended alternative, you can configure
the server to use the High Performance Extensible Logging (HPEL) log
and trace infrastructure instead of using SystemOut.log , SystemErr.log, trace.log, and activity.log files on distributed and IBM® i systems. You can also use
HPEL in conjunction with your native z/OS® logging facilities. If you are using HPEL, you can access
all of your log and trace information using the LogViewer command-line
tool from your server profile bin directory. See the information
about using HPEL to troubleshoot applications for more information
on using HPEL.
- Start the migrated Version 8.5 node X agent.
- Check the Version 8.5 deployment manager and node X SystemOut.log for warnings or errors.
- Synchronize the cell.
- Stop all the application servers on the Version 8.5 migrated node X.
- Start the appropriate application servers on the Version 8.5 migrated node X.
- Run the backupConfig command with
the appropriate parameters and save the Version 8.5 profile configuration
to a file. For example:
/opt/WebSphereV85/profiles/v70tov85node1/bin/backupConfig.sh /mybackupdir/
v70tov85node1.zip -username myuser -password mypass -nostop
Each time that you run the backupConfig command, use a new backup file name.
- To save the Deployment Manager configuration, run the backupConfig command. On the Version 8.5 Deployment Manager
host, change to the deployment_manager_profile
root/bin directory. Run the backupConfig command with the appropriate parameters and save the Version 8.5 profile configuration
to a file. For example:
/opt/WebSphereV85/profiles/Dmgr01/bin/backupConfig.sh /mybackupdir/
Dmgr01backupMigratedDmgrPlusNodeX.zip -username myuser -password mypass
Note: If you are migrating
a node to a different host, refer to the applicable steps in Migrating cell configurations to new host machines using the command-line
tool.
Note: For each node that you migrate, back up the Version 8.5 Deployment Manager
configuration to a new backup file.