+

Search Tips   |   Advanced Search

Portal V6.1.x on application server V7 cluster: Migrate a local dmgr


This topic provides instructions on migrating the dmgr in an environment without coexistence. If you have a high-availability system that needs to be available during the migration process, then we might consider migrating the clustered environment with coexistence.

When you migrate local dmgr on the same machine, the source dmgr will be disabled

  1. Copy the required files (including the migration plug-in) from the WebSphere Portal V8.0 binary installation to the dmgr system:

    1. Copy the filesForDmgr.zip file to the remote dmgr system.

    2. Stop the dmgr.

    3. Expand the filesForDmgr.zip file into the installation root directory of the dmgr; for example in the C:\IBM\WebSphere\AppServer directory.

      If the dmgr profile was not created in the default Appserver/profiles/Dmgr01 directory, then the metadata_wkplc.xml file, located in the Appserver/profiles/Dmgr01\config\.repository\metadata_wkplc.xml directory in the compressed file, must be copied into the config\.repository subdirectory under the dmgr profile directory.

    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

  2. On portal v8 host run WASPreUpgrade

      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.

  3. scp -r backup_dir target_v8_node:/tmp

  4. Create a profile on the target dmgr:

      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.

  5. 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 -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 V6.1.x on application server V7 cluster: Migrating dmgr