Portal V6.1.x on application server V7 cluster: Migrate a remote deployment manager

1. Copy the required files (including the migration plug-in) from the WebSphere Portal V8.0 binary installation to the deployment manager system...

   1. scp filesForDmgr.zip dmgr_host:/IBM/WebSphere/Appserver

   2. Log on to remote dmgr system as user who owns dmgr file system

   3. Stop the dmgr.
      /IBM/WebSphere/AppServer/bin/stopManager.sh

   4. Unzip files...
      cd /IBM/WebSphere/AppServer
      unzip filesForDmgr

   5. If the dmgr profile is not in default directory...
      AppServer/profiles/Dmgr01

      ...then...

      cp $WAS_HOME/profiles/Dmgr01/config/.repository/metadata_wkplc.xml $DMGR_PROFILE/config/.repository

   Failure to copy the plug-in files to the dmgr can result in the following error when you try to upgrade ConfigEngine...

   com.ibm.websphere.management.exception.InvalidConfigDataTypeException: ADMG0007E: The configuration data type CellCompRegistryCollection is not valid

2. On the Portal v8 server, create the file...
   WAS_V8_OS.arch_RemoteMigrSupport.jar file

   ...for example...

   WAS_V8_windows.x86_RemoteMigrSupport.jar

   ...by running...

   cd $WAS_HOME/bin/migration/bin/
   ./createRemoteMigrJar.sh -targetDir /path/to/remote_jar_dir 
   

   Where remote_jar_dir is an existing directory that will contain the generated file.

3. Copy WAS_V8_OS.arch_RemoteMigrSupport.jar from the Portal V8.0 server into a temporary directory on the source environment

4. Log on to the source environment and extract WAS_V8_OS.arch_RemoteMigrSupport.jar.

5. For AIX Linux Solaris only, ensure that read and execute permissions are set on the extracted files. For example:
   chmod -R 755 /path/to/supp_dir

6. On portal v8 host run WASPreUpgrade

   cd /path/to/supp_dir/bin
   ./WASPreUpgrade.sh /path/to/backup_dir \
                      /path/to/source_WasHome \
                      -traceString trace_spec \
                      -traceFile trace_file \
                      -oldProfile wp_profile_name \
                      -machineChange true \
                      -javaoption \
                      -Xmx2048m
   

   ...where...

   supp_dir

   Directory on the source portal server where you assembled the supplementary files required for migration.

   backup_dir

   Required. Must be the first parameter specified. Specifies the directory on the source portal where WASPreUpgrade stores the exported profile data. If the directory does not exist, WASPreUpgrade creates it. Neither the supp_dir nor WAS_HOME directories, depending on whether we are performing local or remote migration, or any of the nested subdirectories are valid for the location of backup_dir.

   source_WasHome

   WebSphere Application Server installation directory on the source server.

   trace_spec

   The trace information collect. To gather all trace information, specify: "*=all=enabled". Use -traceFile to specify location of output. Default is /path/to/backupDir/logs

   If we specify -traceString, but omit -traceFile, the command does not generate a trace file.

   trace_file

   Name of output file where trace information is stored. Default is backupDir/logs. If we specify -traceString, but omit -traceFile, the command does not generate a trace file.

   wp_profile_name

   Portal profile on the source environment.

   machineChange

   Required for remote migrations, that is when source and target environment are separate machines. If not specified, the default value is false and used for local migrations.

7. Move the backup directory containing the source portal exported data to the target node where the new version of WebSphere Portal is installed.

   Use a compression utility to compress the directory contents, or map a drive to the remote server. Then move the directory containing the exported data to the remote server.

8. Create a profile on the target deployment manager:

   cd WAS_HOME/bin/
   ./manageprofiles.sh -create \
                       -profileName dmgr_profile_name \
                       -templatePath WAS_HOME/profileTemplates/management \
                       - serverType DEPLOYMENT_MANAGER \
                       -nodeName node_name \
                       -cellName cell_name \
                       -hostName host_name
   

   ...where...

   dmgr_profile_name	Dmgr profile name
   node_name	Current dmgr node name.
   cell_name	Current cell name.
   host_name	Host name for the dmgr where we are creating the profile.

9. Run the WASPostUpgrade command:

   cd $WAS_HOME/bin/
   ./WASPostUpgrade.sh /path/to/backup_dir \
                       -profileName wp_profile_name  \
                       -oldProfile old_wp_profile_name  \
                       -username source_admin_user  \
                       -password source_admin_password  \
                       -replacePorts TRUE  \
                       -backupConfig TRUE  \
                       -scriptCompatibility TRUE  \
                       -keepDmgrEnabled TRUE
   

   ...where...

   backup_dir

   Directory where WASPreUpgrade stores the data that it exports from the source server, and from which the WASPostUpgrade command reads and imports data.

   wp_profile_name

   New portal profile on the target server or node to which the WasPostUpgrade command migrates the source portal profile.

   old_wp_profile_name

   Source portal's profile name. The profile name must already exist in the backup_dir directory you just provided.

   source_admin_user

   Administrator ID for the source portal. Specify the login form of the administrator ID rather than the fully qualified name; for example, specify wpsadmin rather than uid=wpsadmin, o=defaultWIMFileBasedRealm.

   source_admin_password

   Administrator ID password for the source portal.

Parent: Portal V6.1.x on application server V7 cluster: Migrating deployment manager