Portal V7.0 cluster: Migrate a local dmgr

Portal V7.0 cluster: Migrate a local dmgr

When you migrate local dmgr on the same machine, the source dmgr will be disabled
From portal v8 binary install host, copy filesForDmgr.zip to the dmgr system.

Copy filesForDmgr.zip...
scp filesForDmgr.zip dmgr_host:/IBM/WebSphere/AppServer

Log on to dmgr host, stop dmgr, and unarchive file...
cd /IBM/WebSphere/AppServer/bin
./stopManager.sh
cd /IBM/WebSphere/AppServer
./unzip filesForDmgr.zip

If the dmgr profile location is not the default...
./Appserver/profiles/Dmgr01

...then copy metadata_wkplc.xml in the compressed file to the actual dmgr profile directory...
cp ./Appserver/profiles/Dmgr01/config/.repository/metadata_wkplc.xml $MY_DMGR_PROFILE/config/.repository

Failure to copy the migration plug-in files to the dmgr can result in the following error when you try to upgrade the ConfigEngine tool: com.ibm.websphere.management.exception.InvalidConfigDataTypeException: ADMG0007E: The configuration data type CellCompRegistryCollection is not valid
On portal v8 host run WASPreUpgrade
cd supp_dir/bin/
./WASPreUpgrade.sh backup_dir 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 file 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 WAS installation directory on the source server.
trace_spec Trace information to collect. Optional. To gather all trace information, specify "*=all=enabled" (including the quotation marks). If you include this parameter, also specify the trace_file. If you do not specify the -traceString or -traceFile parameter, the command creates a trace file by default and places it in the backupDir/logs directory. If we specify the -traceString parameter but omit the -traceFile parameter, the command does not generate a trace file.
trace_file Name of the output file where trace information is stored. Optional. If you do not specify the -traceString or -traceFile parameter, the command creates a trace file by default and places it in the backupDirectory/logs directory. If we specify the -traceString parameter but omit the -traceFile parameter, the command does not generate a trace file.
wp_profile_name Portal profile on the source environment.
machineChange Required for remote migrations when source and target environment are separate machines. If not specified, the default value is false and used for local migrations.
scp -r backup_dir target_v8_node:/tmp
Create a profile on the target dmgr:
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.
Run the WASPostUpgrade command:
cd WAS_HOME/bin/

./WASPostUpgrade.sh backup_dir 
                        -profileName wp_profile_name 
                        -oldProfile old_wp_profile_name 
                        -username source_admin_user 
                        -password source_foo 
                        -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_foo
     Administrator ID password for the source portal. 

 
Parent: Portal V7.0 cluster: Migrating dmgr

supp_dir	Directory on the source portal server where you assembled the supplementary file 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	WAS installation directory on the source server.
trace_spec	Trace information to collect. Optional. To gather all trace information, specify "*=all=enabled" (including the quotation marks). If you include this parameter, also specify the trace_file. If you do not specify the -traceString or -traceFile parameter, the command creates a trace file by default and places it in the backupDir/logs directory. If we specify the -traceString parameter but omit the -traceFile parameter, the command does not generate a trace file.
trace_file	Name of the output file where trace information is stored. Optional. If you do not specify the -traceString or -traceFile parameter, the command creates a trace file by default and places it in the backupDirectory/logs directory. If we specify the -traceString parameter but omit the -traceFile parameter, the command does not generate a trace file.
wp_profile_name	Portal profile on the source environment.
machineChange	Required for remote migrations when source and target environment are separate machines. If not specified, the default value is false and used for local migrations.

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.

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_foo	Administrator ID password for the source portal.