Portal V7.0 stand-alone: Migrating the portal profile to a remote server

Portal V7.0 stand-alone: Migrating the portal profile to a remote server

If the source portal and target portal are located on different servers, prepare the supplementary file required for remote migration, and then follow the steps described here to migrate the source portal profile.

The command parameters documented in this topic have been tested for the migration process. It is not recommended that we specify additional parameters for these commands, even if they are supported by the commands, unless specifically directed to do so.
If the source portal is on AIX , Linux, Solaris, or IBM i, increase the file descriptor limit on the source portal
ulimit -n 200000
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

WebSphere Application Server 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.
Move the backup directory containing the source portal's exported data to the target server where the new version of portal is installed.
Create the new profile on the target portal server:
 
cd WAS_HOME/bin/
./manageprofiles.sh -create 
                    -defaultPorts 
                    -enableAdminSecurity false 
                    -profileName wp_profile_name 
                    -profilePath profile_path 
                    -templatePath WAS_HOME/profileTemplates/default  
                    -nodeName source_node_name 
                    -cellName source_cell_name 
                    -hostName host_name 
                    -isDefault 
                    -omitAction samplesInstallAndConfig defaultAppDeployAndConfig 
...where...

wp_profile_name Profile on the target server or node to which the source portal profile is to be migrated.
profile_path Profile location on the target server or node that is to contain the migrated source portal profile.
source_node_name Node name of the source portal profile. Must be the same. We can change node name, only after migration.
source_cell_name Cell name of the source portal profile. Must be the same. We can change cell name, only after migration.
host_name Host name for the target server or dmgr where we are creating the profile.
If the target portal is on AIX, Linux, Solaris, or IBM i, increase the file descriptor limit on the target portal to 200000.
ulimit -n 200000

Run the WASPostUpgrade command:

WAS_HOME/bin/WASPostUpgrade.sh backup_dir -profileName wp_profile_name -oldProfile old_wp_profile_name -username source_admin_user -password source_foo -includeApps true -backupConfig false -traceString trace_spec -traceFile trace_file -javaoption -Xmx1536m

...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.

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.
Parent: Portal V7.0 stand-alone: Migrating the application server profile
Related reference:
Configure JVM heap size from command line

wp_profile_name	Profile on the target server or node to which the source portal profile is to be migrated.
profile_path	Profile location on the target server or node that is to contain the migrated source portal profile.
source_node_name	Node name of the source portal profile. Must be the same. We can change node name, only after migration.
source_cell_name	Cell name of the source portal profile. Must be the same. We can change cell name, only after migration.
host_name	Host name for the target server or dmgr where we are creating the profile.