Migrate the portal's V6.1 application server profile to a remote server

If the source portal and target portal are located on different servers, ensure that you have prepared the supplementary files that are 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 you specify additional parameters for these commands, even if they are supported by the commands, unless specifically directed to do so.

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

      The ulimit command determines the maximum number of open files that the OS supports. After migration is complete, you can restore the earlier value. For more information on ulimit, see the reference documentation for OS.

  2. On the source portal server, run the WASPreUpgrade command:

    • Windows™: supp_dir/migration/bin/WASPreUpgrade.bat backup_dir source_WasHome -traceString trace_spec -traceFile trace_file -oldProfile wp_profile_name -machineChange true

    • UNIX™: supp_dir/migration/bin/WASPreUpgrade.sh backup_dir source_WasHome -traceString trace_spec -traceFile trace_file -oldProfile wp_profile_name -machineChange true

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

        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.

  3. Move the backup directory that contains the source portal's exported data to the target server 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.

  4. Create the new profile on the target portal server:

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

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

  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 remote server, you cannot start the portal server for verification purposes. At this point in the remote migration process, the required V6.1 binary files are not located on the remote server, 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.

  8. To upgrade the ConfigEngine tool from V6.1 to V7, run the following command:

    • Windows: $PORTAL_HOME/bin/upgradeConfigEngine.bat profile_name -hostname host_name -user admin_name bind -password foo

    • UNIX: $PORTAL_HOME/bin/upgradeConfigEngine.sh profile_name -user admin_name bind -password foo

    • i: $PORTAL_HOME/bin/upgradeConfigEngine.sh profile_name -user admin_name bind -password foo

      where
      profile_name

        Name of the WAS V7 profile that is the target of the upgrade.

      host_name

        Host name of the application server (when migrating a stand-alone server) or Deployment Manager (when migrating a clustered environment).

      admin_name

        Specifies the administrator user ID for the application server.

      foo

        Specifies the password for the administrator user ID.

      Trace information is stored in the UpgradeConfigEngineTrace.log file in the WP_PROFILE/ConfigEngine/log directory.


Parent

Migrate the portal's V6.1 application server profile


Related tasks


Prepare supplementary files for remote migration from V6.1

 


+

Search Tips   |   Advanced Search