Important Tips when running WebSphere Application Server Migration Tools

Body

Configuration migration is the process of upgrading a WebSphere Application Server installation to a newer major release. Migration leverages the existing configuration and applications and migrates them to the newest version environment. This blog provides important tips when you are running Migration Utilities ( Configuration Migration Tool (CMT) or command line (WASPreupgrade/WASPostupgrade)) to migrate WebSphere Application Server from one version to another.
 

• Make sure that the ulimit for open files is not set to the default and is 10000 or higher.
   
• Migrate each profile separately starting with the deployment manager in an Network Deployment environment.
   
• Use the same cell name and node name from the old version that you are migrating.
   
• If you are migrating applications, verify that the applications will work on new versions as they exist before the migration. Use the Application Migration Toolkit to confirm if any changes are needed to the applications before migrating. See:
  http://www.ibm.com/developerworks/websphere/downloads/migtoolkit/
   
• Do not federate nodes. Each node will be automatically federated during node migration if you are creating profiles manually in the new version.
   
• After migrating the deployment manager to Version 8.5, make sure to do a full sync with all the old version nodes using the syncNode command. See: http://www.ibm.com/support/knowledgecenter/SSAW57_8.5.5/com.ibm.websphere.nd.doc/ae/rxml_syncnode.html
   
• For remote migrations, see the following instructions within the product documentation:
  http://www.ibm.com/support/knowledgecenter/SSAW57_8.5.5/com.ibm.websphere.migration.nd.doc/ae/tmig_migrate_remote_commandline.html
   
• If you are using remote migration but the operating system will change, WebSphere Application Server needs to be installed on the source operating system to create the remote migration Java archive (JAR) file, which is required for the waspreupgrade command.
   
• See the following pre-migration considerations
  http://www.ibm.com/support/knowledgecenter/SSAW57_8.5.5/com.ibm.websphere.migration.nd.doc/ae/cmig_pre.html
   
• Take a full system backup before you perform migration.

Important Reference
Webcast replay: Configuration Migration for WebSphere Application Server using Migration Tools
http://www.ibm.com/support/docview.wss?uid=swg27042334

Knowledge Collection: Migrating from other Application Servers to WebSphere Application Server
http://www.ibm.com/support/docview.wss?uid=swg27008729

Migration using Graphical Tools
http://www.ibm.com/support/knowledgecenter/SSAW57_8.5.5/com.ibm.websphere.migration.nd.doc/ae/tmig_profiles_gui.html

Migration Using Command Line ( WASPREUPGRADE and WASPOSTUPGRADE)
http://www.ibm.com/support/knowledgecenter/SSAW57_8.5.5/com.ibm.websphere.migration.nd.doc/ae/tmig_tools.html
 

Info-information-tipc-icon-support (modified) credit: (cc) Some rights reserved by geralt