Upgrade remote nodes

Overview

If the source and target nodes are not located on the same server, follow the steps described here to migrate the source portal's application server profile to the primary node. After you complete the process for the primary node, repeat the procedure for each secondary node.

Complete the following steps on the Deployment Manager primary node. Then, repeat the procedure for each secondary node.

1. Set new new values for the host name and port number used for the dmgr in...
   WP_PROFILE/ConfigEngine/properties/wkplc.properties

   Verify that there are no SOAP communication errors:

   cd WP_PROFILE/ConfigEngine

   
   ./ConfigEngine.sh -DWasPassword=foo

2. If the target portal is on AIX, Linux, Solaris, or i, increase the file descriptor limit on the target portal to 200000. For example:
   ulimit -n 200000

   The ulimit command determines the maximum number of open files that the OS supports. By increasing the value before you migrate exported content into the new portal installation, you can avoid problems that might be caused if the value were too low. After migration is complete, you can restore the earlier value. OS.

3. Increase the Java maximum heap size for the WasPreUpgrade command.

   1. Edit the WasPreUpgrade command file.
      WAS_HOME/bin/WASPreUpgrade.sh

   2. Update the -Xmx parameter of the PERFJAVAOPTION variable to have a value of at least 1024 MB.
      For example:

      set PERFJAVAOPTION=-Xms512m -Xmx1024m -Xj9 -Xquickstart

   3. Save changes.

4. Run the WASPreUpgrade command:
   supp_dir/migration/bin/WASPreUpgrade.sh backup_dir source_WasHome -traceString trace_spec -traceFile trace_file -oldProfile wp_profile_name -machineChange true

   .where...
   supp_dir

   Directory on the source portal server where you assembled the supplementary files that are required for migration to a remote server.
   backup_dir

   Directory on the source portal where the WASPreUpgrade command stores the exported profile data. If the directory does not exist, the WASPreUpgrade command creates it.
   source_WasHome

   WAS installation directory on the source server.
   trace_spec

   An optional parameter that specifies the trace information that you want to collect. 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 you specify the -traceString parameter but omit the -traceFile parameter, the command does not generate a trace file.

   
   trace_file

   An optional parameter that specifies the name of the output file where trace information is stored.

   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 you specify the -traceString parameter but omit the -traceFile parameter, the command does not generate a trace file.

   
   wp_profile_name

   Portal profile on the target server or node to which the source portal profile is to be migrated.

5. Move the backup directory that contains the source portal's 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, and then move the directory containing the exported data to the remote server.

6. Create the new profile on the target node:
   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 for the node that is created with the new profile. Use a unique value within the cell or on the server.
   
   source_cell_name
   Cell name of the source portal profile.
   
   host_name
   Host name for the target server or dmgr where you are creating the profile.

7. Increase the Java maximum heap size for the WasPostUpgrade command.

   1. Edit the WasPostUpgrade command file.
      WAS_HOME/bin/WASPostUpgrade.sh

   2. Update the -Xmx parameter of the Java performance options variable to have a value of at least 1024 MB.

      For example:

      set PERF_JVM_OPTIONS=-Xms512m -Xmx1024m -Xj9 -Xquickstart

   3. Save changes.

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

   where
   backup_dir

   Directory where the WASPreUpgrade command 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 directory specified above.
   
   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
   An optional parameter that specifies the trace information that you want to collect. 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 you specify the -traceString parameter but omit the -traceFile parameter, the command does not generate a trace file.

   
   trace_file
   An optional parameter that specifies the name of the output file where trace information is stored.

   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 you specify the -traceString parameter but omit the -traceFile parameter, the command does not generate a trace file.

   After running the WasPostUpgrade command on a remote node, you cannot start the portal cluster for verification purposes. At this point in the remote migration process, the required V6.1 binary files are not located on the remote node, so the application is not yet complete. If you attempt to start the portal after the WasPostUpgrade command and before the upgrade-profile task, the portal will fail with numerous errors in the SystemOut.log file. This is expected behavior.

Parent

Upgrading WAS nodes

Related tasks

Upgrading the ConfigEngine tool on the primary and secondary nodes

  Updated first sentence to specify portal node instead of Deployment Ma...

+

Search Tips   |   Advanced Search