Previous Step   Previous Step Next Step   Next Step

Create the remote migration .jar file

Map Step 3 towards the goal: Scenario 2: Migrating cell configurations to new host machines using the command-line tool

About this task

This .jar file contains the files necessary to run the WASPreUpgrade command on a system which does not have WebSphere® Application Server installed.
Avoid trouble Avoid trouble: [Updated in August 2013] You must create the remote migration .jar file on same operating system and architecture as you installed the source. Because the archive that is generated contains operating system specific code, it only executes on this architecture. [Updated in August 2013]
aug2013
gotcha

Before you begin

Install WebSphere Application Server Version 8.0

Procedure

  1. Identify the operating system and architecture of the source profile. If the operating system and architecture of the source profile is different from the operation system or the architecture of the target profile, then you must install WebSphere® Application Server Version 8.0 on a system that matches the source profile before creating the remote migration jar. Once you have generated the remote migration jar, it will work on any system which matches the operating system and architecture.
  2. Create the remote migration .jar.
    1. In the command prompt, enter the following command:
      cd <
      app_server_root
      >/bin/migration/bin 
    2. To create the .jar file, enter this command:
      createRemoteMigrJar.bat(sh) -targetDir <directory for the remote migration jar>
      This creates the following file: WAS_V8_<OS>.<arch>_RemoteMigrSupport.zip. For example: WAS_V8_windows.x86_RemoteMigrSupport.zip
  3. Prepare the remote system for the WasPreUpgrade command.
    1. Send the .jar file to the system where your source profile resides.
    2. Extract the file to a temporary location.
    3. Cd to the bin directory in the temporary location.
    4. You are now ready to run the WASPreUpgrade command against the source profile. However, do not issue this command until you are told to do so in a later step.

What to do next

Create the target deployment manager profile

Previous Step   Previous Step Next Step   Next Step


Terms and conditions for information centers | Feedback

Last updated: Feb 6, 2014 11:50:09 PM CST
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=matt&product=was-nd-dist&topic=tmig_migrate_remote_commandline_step3
File name: tmig_migrate_remote_commandline_step3.html