Upgrading local nodes

If the source and target nodes are on the same server, complete the steps documented 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. Create the new profile:

    • Windows™: WAS_HOME/bin/manageprofiles.bat -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

    • UNIX™: 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

    • i: 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

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

      profile_path

        Specifies the 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

        Specifies the cell name of the source portal profile.

      host_name

        Host name for the target server or dmgr where you are creating the profile.

  2. Update wkplc.properties with the new values for the host name and port number used for the dmgr.

      The wkplc.properties file is located in the WP_PROFILE/ConfigEngine/properties directory.

      Run the following command from the WP_PROFILE/ConfigEngine, and verify that there are no SOAP communication errors:

      • Windows: ConfigEngine.bat -DWasPassword=foo

      • UNIX: ./ConfigEngine.sh -DWasPassword=foo

      • i: ConfigEngine.sh -DWasPassword=foo

  3. 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. For more information on ulimit, see the reference documentation for OS.

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

    1. Edit the WasPreUpgrade command file.

    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.

  5. Run the WASPreUpgrade command:

    • Windows: WAS_HOME/bin/WASPreUpgrade.bat backup_dir source_WasHome -traceString trace_spec -traceFile trace_file -oldProfile wp_profile_name

    • UNIX: WAS_HOME/bin/WASPreUpgrade.sh backup_dir source_WasHome -traceString trace_spec -traceFile trace_file -oldProfile wp_profile_name

    • i: WAS_HOME/bin/WASPreUpgrade.sh backup_dir source_WasHome -traceString trace_spec -traceFile trace_file -oldProfile wp_profile_name

      where
      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

        Specifies the 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

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

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

    1. Edit the WasPostUpgrade command file.

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

        For example:

        • Windows: 

            set PERFJAVAOPTION=-Xms512m -Xmx1024m -Xj9 -Xquickstart

        • UNIX: 

            set PERF_JVM_OPTIONS=-Xms512m -Xmx1024m -Xj9 -Xquickstart

        • Solaris: 

            set PERF_JVM_OPTIONS="-Xms512m -Xmx1024m -XX:PermSize=128m -XX:+UnlockDiagnosticVMOptions -XX:+UnsyncloadClass"

    3. Save changes.

  7. Run the WASPostUpgrade command:

    • Windows: WAS_HOME/bin/WASPostUpgrade.bat 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

    • UNIX: 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

    • i: 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 local node, it is possible to start the portal cluster for verification purposes. However, because the migration process is not complete, there might be errors in the SystemOut.log file. These errors are usually resolved after the upgrade-profile task completes. It is important that you not attempt to run in production when the migrated portal is in this state. If you start the portal for verification at this point, stop the portal before running the upgradeConfigEngine command.

  8. Update WP_PROFILE/ConfigEngine/properties/wkplc.properties with the correct WAS administrator password for the portal that you want to migrate.

WAS provides a Migration wizard, WAS_HOME/bin/migration.bat(sh), that automatically creates the profile in the WAS_HOME/profiles directory. To create the profile in a specified location, you can use either the Profile Management Tool (PMT) (on 32-bit application server) or the manageprofiles command (on 64-bit application server). Then, when you use the Migration wizard, you can select the new profile as the target profile for migration. When pre-creating a profile, create a default application server profile and install the admin console only; do not install any sample applications.

To migrate the application server profile on i, use the manual steps provided above; WAS does not provide a Migration wizard on i.


Upgrading WAS nodes


Related tasks


Upgrading the ConfigEngine tool on the primary and secondary nodes

  Minor change Minor change Updated the description of wp_profile_name for WASPreUpgrade command Removed Deployment Manager from the introductory sentence and removed ... Submitted by John De Binder on Jul 21, 2011 9:25:50 AM

Re: Upgrading local nodes

Opps, its the WASPreUpgrade command in WAS 7.0! Submitted by John De Binder on Jul 20, 2011 6:33:16 PM

Re: Upgrading local nodes

I looked up the WASPreUpgrade command in WAS 6.1 info center. There is no -oldProfile parameter defined for the command. I wondered why the description for the oldProfile parameter said it "specifies the portal profile on the target server...." But I guess since it's not even necessary it won't matter :-)


+

Search Tips   |   Advanced Search