This version of the software is currently available only to customers in the Controlled Availability (CA) program.

Migrating BMC Helix Digital Workplace Catalog data

After you perform the data migration for BMC Helix ITSM, perform the BMC Helix Digital Workplace Catalog data migration.

The following image shows the tasks to migrate BMC Helix Digital Workplace Catalog data:

Important

  • The supported migration versions are not dependent on the version of the BMC Helix Data Manager tool. For example, you can use BMC Helix Data Manager version 21.3.05 to perform BMC Helix Digital Workplace data migration to version 22.1 or later.
    However, we recommend that you use the latest version of BMC Helix Data Manager. For more information on the supported versions, see Available migration packs.
  • After you perform the data migration, you can run delta data migration by using the Template DWPC Migration pack. Delta data migration is not supported for the Template DWPC Process Migration pack.

Before you begin

Make sure that you have completed the following actions:

  • Migrated BMC Helix ITSM data.
  • If you are migrating data from an Remedy on-premises system to BMC Helix Innovation Suite Cloud, make sure that you complete all the tasks of Stages 1 to 4 in the topic Migration process for Remedy on-premises to BMC Helix Innovation Suite Cloud Open link before you migrate the DWPC data.
  • If you are testing the application on Production database, make sure that you first take a backup of the database, test the application, and restore the backup after testing to avoid any new issues.
  • Downloaded and imported the following migration packs:

    Important

    To use BMC Helix Digital Workplace 23.3 SaaS Migration Packs, contact BMC Support.

    • Master Template Clear Down ITSM pack

    • Data Update Packs for ITSM and DWPC

    • Template DWPC Migration pack

    • Template DWPC Process Migration pack

    • DWPC Process Source Migration Template pack

  • Stopped BMC Helix Digital Workplace Catalog application and make sure that escalations in the source system are disabled during cutover, and escalations in the target system are disabled until the migration is fully complete.
  • Updated the company details for the hannah_admin the in Company*+ field in the CTM:People form in the BMC Helix ITSM target system.
    If not, set the customer name for the hannah_admin user as Company.
  • Created a back up of your source systems.

    Important

    Do not perform any data migration step on your production source systems. You must perform the data migration steps on the back up of your source systems.

  • Downloaded the BMC-DWPC-HDM_Accessories_21.xx.zip file located at BMC Helix Digital Workplace Catalog OnPrem Data Migration Accessories Open link on EPD.
    Search for BMC Helix Digital Workplace Advanced OnPrem and download the latest version of BMC-DWPC-HDM_Accessories_21.xx.zip file. The file includes the build_hdm_csv.py, Fix_cache-21.3, and processupgrader-21.x.jar utilities.

  • Installed Python version 3.10.5.
    To download Python version 3.10.5, see https://www.python.org/downloads/ Open link .
    For steps on installing Python, see Python documentation Open link .

  • Verified that the myit-sb:mp_search_categories table in DWP-C do not have any duplicate categories. Fix any duplicate categories in the DWP-C source system.

  • If you are migrating to BMC Helix Innovation Suite version 21.3.07 or above, set the CCS setting Disable-Process-Timer-Task-Execution value to T (true).
    1. In a browser, open the BMC Remedy AR System Administration Console, and click System > General > Centralized Configuration.
    2. In the AR System Configuration Generic UI form, from the Component Name list, select com.bmc.arsys.server.shared.*.
    3. Set the Disable-Process-Timer-Task-Execution setting to T and click Apply.

To perform the full migration

  1. Register the following source and target systems:

    SystemSteps to register the system
    BMC Helix Digital Workplace Catalog source system
    1. Register a source system.
      Important:

      • While registering the BMC Helix Digital Workplace Catalog source system, specify the Catalog - Logical Db Name value as Catalog and Tenant - Logical Db Name value as Tenant.
      • Set the HDM User value to hdm.
      • In the BMC Helix Digital Workplace Catalog registered source system, set the Unique Id Transform value to 'D'. The value must be different from the Remedy Source system value.
        For more information about updating the Unique Id Transform value, see Actions you can perform on a system you have registered.
    2. Create a BMC Helix Data Manager user.
    3. Test system connectivity and get database character set details on the source system.
    4. Discover the source system.

    BMC Helix ITSM target system
    1. Register a target system.
    2. Test system connectivity and get database character set details on the target system.
    3. Discover the target system.
    BMC Helix Digital Workplace Catalog process migration source and target system
    1. Register source and target process system.
    2. Create a BMC Helix Data Manager user.
      Note - If you have already created an HDM user, you can skip this step.
    3. Test system connectivity and get database character set details on the source and target DWPC process system.
    4. Discover the source and target DWPC process system.
  2. Copy the Master Template Clear Down ITSM Pack, DWPC Migration Template Pack, and DWPC Process Migration Template Pack migration packs to the source and target data dictionaries.

    1. In BMC Helix Data Manager, select Data Migration > Migration Packs.
    2. Select the migration pack that you want to copy.
    3. Select Action > Copy.
    4. Select the source and target data dictionaries for the respective DWPC and Process systems.
      For the DWPC migration pack, select the following data dictionaries:

      Source data dictionaryCatalog and Tenant database registered as DWPC System in BMC Helix Data Manager.
      Target data dictionarySystem registered as Remedy in BMC Helix Data Manager and connecting to the database used for ITSM configuration.




      For the Process systems, select the following data dictionaries:

      Source data dictionaryTenant database defined as Relational System in BMC Helix Data Manager
      Target data dictionarySystem defined as Relational System in BMC Helix Data Manager and connecting to the database used by the standard migration pack on the target system.

    5. Click Copy Migration Pack.
  3. Set up the source and target systems for data migration.
    1. Take a backup of the target system.
    2. In the BMC Helix Digital Workplace Catalog process source system, run the pre-migration script.
      Perform the following steps:

      1. In BMC Helix Data Manager, select Discovery & Analysis > System Analysis & Administration, and select the BMC Helix Digital Workplace Catalog source system.

      2. Navigate to the Data Update tab and click Run Data Updates.

      3. Select Create Data Update Job.

      4. Select PreMigration Scripts_DWPC Source.

      5. For a 20.02 process source, run the Set DWPC Admin Flag, Set DWPC Agent Flag, and Update Process_permissions_x scripts by using the Run Selected Script option.
        For a 20.08 process source, run all the scripts by using the Run All Scripts option.

    3. Run the Data Update Job to tag the Groups linked to Virtual Marketplace in the source system.
      Perform the following steps:
      1. In BMC Helix Data Manager, select Discovery & Analysis > System Analysis & Administration, and select the BMC Helix Digital Workplace Catalog source system.
      2. Navigate to the Data Update tab and select Run Data Updates.
      3. Select Create Data Update Job.
      4. Select the latest Data Update Template - DWPC 20.02 or Above to 2x.x template and DWPC source system.
      5. Click Create New Data Update Job.
      6. Run the Tag groups linked to VM script using the Run Selected Script option.
    4. Take a backup of the configuration data.

      1. In BMC Helix Data Manager, select Discovery & Analysis > System Analysis & Administration, and select the target system.

      2. Navigate to the Data Updates tab and select Run Data Updates.

      3. Select Create New Data Update Job and select the DWPC Data Update Template and Target System.

      4. On the Track Data Update Jobs tab, select the data update job.

      5. Run the Pre-Migration Backup script by selecting it and clicking the Run Selected Script option.

      6. Verify that the job is successfully completed.

      7. If you are migrating your BMC Helix Digital Workplace Catalog data to target version 22.1.xx or 23.3.xx, run the PreMigrationDataFix_myit_sb_mp_product_products script. 


    5. Run Clear Down migration pack on the target system for BMC Helix Digital Workplace Catalog.

      Important

      • If you have already migrated ITSM data and run the Master Template Clear Down ITSM pack for ITSM, you do not need to run the clear down pack again.
      • If the Shared File System list is empty, create a new file system. Learn about how to create file system at Creating a file system.
      1. In BMC Helix Data Manager, select Data Migration > Delete Data, select the DWP Catalog 20.02 and above export template for BMC Helix Digital Workplace, and click Next.

      2. From the Migration Pack dropdown, select the Master Template Clear Down ITSM pack.
      3. On the Delete Data-Confirm page, specify the deletion job and forms for deletion, and click Confirm Delete.

      4. After the deletion job is completed, navigate to the Summary tab of the job, select Action > Start Export.
        After the export is completed, on the Summary tab of the job, select Action > Delete Data.


    6. Take a database backup of the target system gold build - Gold Build Backup 1.

  4. Perform data migration.
    1. Migrate BMC Helix Digital Workplace Catalog groups from the source system to target system.
    2. Export data.
    3. Import data.
    4. Run data update scripts.
  5. Fix overlays and process definitions by running the Process Definition utility.
  6. Apply the required licenses.
    For more information, see Activating application licenses Open link .
  7. Update the group_cache and user_cache tables.
  8. Running the postmigration utility for BMC Helix Digital Workplace.
  9. Perform the delta data migration.

To migrate BMC Helix Digital Workplace Catalog groups from the source system to target system

  1. Prepare a group ID mapping sheet in CSV format with Source_Group_ID, Source_Group_Name, Target_Group_ID, and Target_Group_Name headers.

    Important

    If you are migrating your data from BMC Helix Digital Workplace version 21.3 to version 21.3, do not perform Group ID transformation.


    Use the build_hdm_csv.py script to prepare a group ID mapping sheet. To download the script, navigate to <FTP_directory>/BMC_Helix_Data_Manager/HDM Metadata/21.3 Target/DWPC/Utilities folder in the FTP directory. For information on accessing the FTP directory, see the topic Downloading the installation files.
    Perform the following steps:

    1. Run the following query in the source databases (DWPC tenant) and the target databases, and export the results to a CSV file respectively:

      select group_id, group_name from group_x

      After you run the command in the source databases and the target databases, you have two CSV files, <source>.csv and <target>.csv.

      Important

      Make sure that the CSV files to which you export the results do not contain any column titles or headers.

    2. Save the <source>.csv and <target>.csv files with UTF-8 encoding:
      1. Open the CSV file in Microsoft Excel.
      2. Select File > Save As.
      3. In the Save as type list, select CSV UTF-8 (Comma delimited) (. csv).
      4. Click Save.
    3. Run the script to prepare the group ID mapping sheets output.csv and output2.csv by using the following command:

      python3 build_hdm_csv.py source.csv target.csv output.csv output2.csv 

      If you are using a newer version of python, use the following command:

      py build_hdm_csv.py source.csv target.csv output.csv output2.csv
  2. To prepare the group ID mapping for a source database set as Assigned To = "Migrate" in group form for sbe-public-computed and dwpc-non-subtenant-admins group records, use the following premigration script:
    Perform the following steps:

    1. In BMC Helix Data Manager, select Discovery & Analysis > System Analysis & Administration, and select the BMC Helix Digital Workplace Catalog process source system.

    2. Navigate to the Data Update tab and click Run Data Updates.

    3. Select Create Data Update Job.

    4. Select PreMigration Scripts_DWPC Source.

    5. Run the Set DWPC Group Assigned To Migrate script.


  3. Upload the mapping sheet that you created in step 1 to the transformation group IDs in the DWPC Migration pack.

    1. In the BMC Helix Data Manager, navigate to the Data Migration tab, and select Data Mapping.
    2. Select the data migration pack name.
    3. From the list, select the mapping Tenant: ACT_GE_BYTEARRAY - > ACT_GE_BYTEARRAY.
    4. On the Data Enrichment tab, select each row in the tab and upload the respective CSV file.
    5. For the group ID, in the Mapping Data tab, click Upload CSV, and upload the group mapping sheet file output.csv generated in step 1b.

      Important

      Upload the same group mapping sheet file for data enrichment to the GroupIDListTransform, GroupIDListTransform2, GroupIDListTransform3, GroupIDListTransform4, and GroupIDListTransform_User group IDs.

Back to top

To export data

Perform the following steps to export the BMC Helix Digital Workplace Catalog data:

  1. In BMC Helix Data Manager, select Data Migration > Migrate Data.
  2. On the Migrate Data page, in the Migration Pack field, select the DWPC Migration pack.
  3. Complete the fields and click Next.
  4. On the Migrate Data - Confirm page, in the Migration Job Name field, specify the migration job, and click Confirm Migration.
  5. On the Migration View Job page, click Start Export.

Perform the following steps to export the BMC Helix Digital Workplace Catalog process data:

  1. In BMC Helix Data Manager, select Data Migration > Migrate Data.
  2. On the Migrate Data page, in the Migration Pack field, select the DWPC Process Migration pack.
  3. Complete the fields and click Next.
  4. On the Migrate Data - Confirm page, in the Migration Job Name field, specify the migration job, and click Confirm Migration.
  5. On the Migration View Job page, click Start Export.

Back to top

To import data

You must import both the BMC Helix Digital Workplace Catalog data and BMC Helix Digital Workplace Catalog process data for successful migration.

To import BMC Helix Digital Workplace Catalog data

Perform the following steps to import the BMC Helix Digital Workplace Catalog data by using the DWPC Migration Pack:

  1. After the data export is complete, on the Migration View Job page, navigate to the Import tab.
  2. On the import tab, click Create import Job.


  3. On the Import Data page, in the Migration Pack field, select the DWPC Migration pack.


  4. Complete the fields and click Next.
  5. On the Import Data - Confirm page, in the Group IDs field, perform the following steps:

    Important

    If you are migrating your data from BMC Helix Digital Workplace version 21.3 to version 21.3, do not perform Group ID transformation.

    1. Apply the group ID transformations.

    2. Set User Cache Import Action to Modify.

    3. Set the Group IDs Prefix value to 1.
    4. Click Confirm Data Import.

      Important

      Do not apply any other transformations - Request IDs, Ticket Numbers, or SLA IDs to avoid errors in the migration. Apply the Group ID transformation only.

  6. On the Migration View Job page, to start the import job, click Start.

To import BMC Helix Digital Workplace Catalog process data

Perform the following steps to import the BMC Helix Digital Workplace Catalog data by using the DWPC Process Migration Pack:

  1. After the data export is complete, on the Migration View Job page, navigate to the Import tab.
  2. On the import tab, click Create import Job.


  3. On the Import Data page, in the Migration Pack field, select the DWPC Process Migration pack.
  4. Complete the fields and click Next.
  5. On the Import Data - Confirm page, perform the following steps:

    Important

    If you are migrating your data from BMC Helix Digital Workplace version 21.3 to version 21.3, do not perform Group ID transformation.

    1. In the Group IDs field, apply the group ID transformation.

    2. Set User Cache Import Action to Modify.
    3. Click Confirm Data Import.

      Important

      Do not apply any other transformations - Request IDs, Ticket Numbers, or SLA IDs to avoid errors in the migration. Apply the Group ID transformation only.



  6. On the Migration View Job page, to start the import job, click Start.

Back to top

To run data update scripts

  1. In BMC Helix Data Manager, navigate to the Discovery & Analysis tab, and select the target system.


  2. Click Run Data Updates.

    Important

    If you are migrating your data from BMC Helix Digital Workplace version 21.3 to version 21.3, run the Data Update Template - DWPC 21.3 to 21.3.cmt script only.




  3. In the Create Data Update Job pane, specify the job details, and click Create New Data Update Job.


  4. (Microsoft SQL Server) Before running the data update scripts on a Microsoft SQL Server based target system, run the following SQL command:

    ALTER DATABASE ARSystem SET COMPATIBILITY_LEVEL = <COMPATIBILITY_LEVEL>

    where, 
    COMPATIBILITY_LEVEL can be { 160 | 150 | 140 | 130 | 120 | 110 | 100 | 90 | 80 }.
    To find out the COMPATIBILITY_LEVEL of your system, see ALTER DATABASE (Transact-SQL) compatibility level Open link .

  5. Run all the scripts based on the source version of BMC Helix Digital Workplace Catalog:

    Important

    • Do not run the PreMigration Scripts_DWPC Source and Tag groups linked to VM scripts in this step.
    • If you are migrating your data from BMC Helix Digital Workplace version 21.3 to version 21.3, run the Data Update Template - DWPC 21.3 to 21.3.cmt script only.

    Script details:

    OrderScript

    Application for 20.02-21.3.xx Migration

    Application for 20.08-21.3.xx Migration

    Application for 20.02/20.08-22.1.xx Migration

    Application for 20.02/20.08-23.3.xx Migration

    1PreMigrationBackupYesYesYesYes
    2Tag groups linked to VMYesYesYesYes
    2002001M20200302_02_PatchExistingContentsWithReferenceSourcesYes
    YesYes
    2002002M20200302_03_UpdateContentSecurityLabelToPublicYes
    YesYes
    2002003M20200710_01_
    PopulateMissingRowPermissionsToQuestionnaireTranslation
    Yes
    YesYes
    2002101M20200928_02_PopulateLastReopenDateForServiceRequestYesYesYesYes
    2002201M20201204_01_PopulateServiceRequestSubmittedDateYesYesYesYes
    2002202M20200205_01_PopulateLocaleForMessageTemplateYes
    YesYes
    2002301M20200506_01_
    UpdateProcessDefinitionToReplaceDollarExpressionForRenderTemplateAction
    Yes
    YesYes
    2002302M20200519_01_
    MigrateExistingConnectionConfigurationSettingsToTheirOwnBundles
    Yes
    YesYes
    2002303M20200528_01_UpdateRlsLabelsOfServiceRelatedEntitiesYes
    YesYes
    2002304M20200622_01_MoveConnectionComponentsFromMyitsbeToDwpcGroupYes
    YesYes
    2002305M20200729_01_UpdateLaunchServiceCatalogProductActionOutputYes
    YesYes
    2002306M20200819_01_NullifyUserSyncFlagsYes
    YesYes
    2002307M20200522_01_UpdateProcessExecutionPermissionToPublicYes
    YesYes
    2105001M20210520_01_InitializingServiceRequestIdsYesYesYesYes
    2105002M20210902_01_UpdateUserCriteriaInVirtualMarketplaceYesYesYesYes
    2130001M20220215_01_DisableIsDraftQuestionAnswersByDefaultYesYesYesYes
    2130002M20220613_01_UpdateContentDefinitionReferenceSourceYesYesYesYes
    2130003M20230301_01_UpdateRslReadForITSMIntegrationService

    YesYes
    2130004M20221102_01_SeedingServiceSearchCacheForITSMTicketService

    YesYes
    2130005M20220912_01_EnablePasswordVisibilityForQuestionnaire

    YesYes
    2130006M20230322_01_UpdateRslReadForHeadlessService 

    YesYes
    2130008M20220413_01_UpdateReopenTypeInServiceSearchCache

    YesYes
    2130009M20220603_01_UpdateReopenTypeInServiceVersion

    YesYes
    2130010M20221103_01_FixingProductIdForITSMTicketService

    YesYes
    2130011M20230307_01_InsertMissingContentDefinitionYesYesYesYes
    2130012CleanupDeletedRecordsFromSourceYesYesYesYes
    2130013M20230525_01_UpdatePricingRevisionIdForHeadlessServices


    Yes
    2130014M20230615_01_UpdateLogoForMissingContentDefinitions


    Yes
    2130015M20230621_01_FixServiceRevisionLogoId


    Yes
    2130016MM20231208_01_PopulateExternalLastModifiedDate


    Yes
    2130017M20231227_01_PopulateImportModeForExistingImports


    Yes
    9999993UpdateDataAccessGroupReadDataAccessGroupWriteYesYesYesYes
    9999994FixedLicenseToDWPCAdminUsersYesYesYesYes
    9999995UpdateEmptyGroupListYesYesYesYes
    9999996UpdateRemoteServerApplicationNameYesYesYesYes
    9999997UpdateApplicationLicenseYesYesYesYes
    9999998UpdateGroupListandFunctionalRolesYesYesYesYes
    9999999MergeSourceApplocalconfigstorageWithTargetYesYesYesYes
    10000000DeleteObsoleteGroupsYesYesYesYes
    10000001Process Context and Historic Process Context UpdatesYesYesYesYes
    10000002

    Update CTM:People Form License From User Form

    YesYesYesYes
    10000003UpdateStatusOfUsersYesYesYesYes
    10000004UpdateNameOfSubProcessesYesYesYesYes
    10000005Update Rls Write Fields when MSP is offYesYesYesYes
    10000007RemoveDomainNameSBRemoteApprovalConfigurationYesYesYesYes
    10000008Remove Users From Deleted GroupsYesYesYesYes
    10000009Insert Administrator Permissions For CTM:People Permission GroupsYesYesYesYes
    10000010MergeSourceCMDBConnectorApplocalconfigstorageWithTargetYesYesYesYes
    10000011Update functional_role_list For UserYesYesYesYes
    10000012MergeSourceISConnectorApplocalconfigstorageWithTargetYesYesYesYes
    10000013UpdateSbUserYesYesYesYes
    20000000Next IDYesYesYesYes

    To run a script, perform the following steps:

      1. Select the data update job that you created in step 3.

      2. Select the script that you want to run and click Run Selected Script.

      3. In some cases, the HDM user must be a super user to run the Data Update script. Run the following script on your target system to make the HDM user as super user:

        ALTER USER HDM WITH SUPERUSER;
  6. Perform the following steps to run the BMC Helix ITSM data updates.

    1. Navigate to the Discovery & Analysis tab, and select the target system.

    2. Click Run Data Updates.
    3. In the Create Data Update Job pane, specify the job details, and click Create New Data Update Job.

    4. In the data update job, select the Next ID script, and click Run Selected Script.

Back to top

To fix overlays and process definitions

You must fix your overlays and process definitions to preserve the customizations you performed before migration.

To fix overlays and process definitions by using Process Upgrader

Important

We recommend that you use the Process Upgrader utility to fix overlays and process definitions. If you are using other utilities like rxmigrator, contact BMC Support.

  1. Run the following command to run the Process Upgrader utility:

    java -jar processupgrader-21.3.jar <command> -dbtype <database type> -dbhost <database host> -dbport <database port> -dbname <database name> -dbuser <database user> -dbpassword <database password> -ignorefile <ignorefile.txt>

    Parameters list:

    Parameter

    Description

    <command>

    List of commands:

    CommandDescription
    fix-all

    This command runs all the fixes supported by this tool successively.
    We recommend you to use the fix-all command for optimal results.

    fix-overlay-groupThis command fixes the overlay group reference in the `smobjprop` field

    of process variables.

    fix-expressionsThis command upgrades the expressions in assignments, conditions. 
    fix-permissionsThis command enforces an execution permission open to 'Public' for all

    DWPC processes.

    connectThis command validates the connection to the database.
    helpThis command prints usage of the utility.

    -dbtype <database type>

    Type of database, such as:

    • postgres
    • oracle
    • mssql

    -dbhost <database host>

    Database host.

    For example, clm-dbhost

    -dbport <database port>

    Database port.

    For example, 5432

    -dbname <database name>

    Database Name.

    For example. ARSystem

    If you are using an Oracle database:

    • We recommend you to use a specific AR Database user, instead of a system-wide user like “system”.
    • use -dbname = <service name> (where <service name> is the Service Name/SID of Oracle DB)

    -dbuser <database user>

    Database user.

    For example, ARAdmin

    -dbpassword <database password>

    Database password.

    -ignorefile <ignorefile.txt>

    Ignore Text File to track the items processed by the tool.

    You can use any name for this file.

    -safemappings

    Option to allow the tool to run on a shorter list of mappings.

    Use this option when you re-run the tool. You can safely re-run the mappings on processed data.

    For example:

    java -jar processupgrader-21.3.jar fix-all -dbtype postgres -dbhost clm-dbhost -dbport 5432 -dbname ARSystem -dbuser ARAdmin -dbpassword password -ignorefile ignorefile.txt


  2.  After you successfully run the utility, restart all the AR pods on your environment.

Back to top

To update the group_cache and user_cache tables

During the migration, the user and group records are modified. You must refresh or update the group_cache and user_cache tables to reflect the changes in the user and group records.

To update the group_cache table, perform the following steps:

  1. In your BMC Helix Data manager workbench, copy the fixcache utility JAR file.
  2. In a command prompt, navigate to the location where you have copied the JAR file.
  3. (Optional) Take a backup of the group_cache table through a database client by using the following command:

    SELECT * into bkup_group_cache FROM group_cache
  4. Run the fixcache utility by using the following command:

    java -jar fixcache-21.3.00-SNAPSHOT.jar -h <AR_EXTERNAL_IP> -t <PORT> -u <AR_ADMIN> -p <AR_ADMIN_PASSWORD> -c group

To update the user_cache table, perform the following steps:

  1. In your BMC Helix Data manager workbench, copy the fixcache utility JAR file.
  2. In a command prompt, navigate to the location where you have copied the JAR file.
  3. (Optional) Take a backup of the user_cache table through a database client by using the following command:

    SELECT * into bkup_user_cache FROM user_cache
  4. Run the fixcache utility by using the following command:

    java -jar fixcache-21.3.00-SNAPSHOT.jar -h <AR_EXTERNAL_IP> -t <PORT> -u <AR_ADMIN> -p <AR_ADMIN_PASSWORD> -c user

    Back to top

To perform the delta data migration

You must perform the delta data migration to fully synchronize the source and target systems. Use the Template DWPC migration pack for running the delta data migration.

Important

You can run the delta data (incremental) migration for DWPC by using the Template DWPC migration pack only. You cannot use the Process Migration pack for delta data migration.

Perform the following steps:

  1. Download the Form Deletion Set DWPC.cmt file from BMC FTP.
    To download the file, navigate to <FTP_directory>/BMC_Helix_Data_Manager/HDM Metadata/21.x Target/DWPC folder in the FTP directory. For information on accessing the FTP directory, see the topic Downloading the installation files.
  2. Copy the Form Deletion Set DWPC.cmt file to the <HDM_Installation_directory>/Metadata folder.
  3. Log in to HDM and select Configuration > Import HDM Meta Data from the navigation bar.
  4. Select Scan.
  5. Select Form Deletion Set DWPC.cmt from the list and click the Import Meta Data button.
    After the import is successful, you can see the deletion list in the Configuration > Form Deletion list.

  6. Click Data Migration > Migrate Data.
  7. On the Migrate Data page, in the Migration Pack field, select the DWPC source, DWPC target, and DWPC Tenant Migration pack.
  8. From the Export Template list, select All Data Incremental.
  9. Complete all the fields and click Next.
  10. Specify the Incremental Start and End date.
  11. Click Next and run the export job.
  12. After the export is completed successfully, click Create Import Job to open the Create Import Job dialog box.

  13. On the Import Data page, click Next.
  14. Select Form Deletion Set as DWPC, apply Group ID transformation and set User Cache Import Action to Modify and confirm.

    Important

    • Make sure that you have not selected the Form Deletion Check as Default.
    • If you are migrating your data from BMC Helix Digital Workplace version 21.3 to version 21.3, do not apply Group ID transformation.

  15. Click Confirm Data Import.
  16. After the delta migration is complete, rerun the DWPC data update template and ITSM data updates postmigration scripts.

To migrate DWPC process data

Perform the following steps if you want to re-run the migration to migrate the process data for DWPC:

  1. Download the PreDDM Process Deletion_DWPC.cmt file from BMC FTP.
    To download the file, navigate to <FTP_directory>/BMC_Helix_Data_Manager/HDM Metadata/21.x Target/DWPC folder in the FTP directory. For information on accessing the FTP directory, see the topic Downloading the installation files.
  2. Copy the PreDDM Process Deletion_DWPC.cmt file to the <HDM_Installation_directory>/Metadata folder.
  3. Log in to HDM and select Configuration > Import HDM Meta Data from the navigation bar.
  4. Select Scan.
  5. Navigate to Discovery & Analysis > System Analysis & Administration and select the Process target system.
  6. In the Available Data Updates tab, select PreDDM Process Deletion and click Run Data Updates.
  7. Click Run Selected Script.

    The Process deletion script is run successfully.
  8. Run the migration again for process data.
  9. After you complete the migration, run data update scripts.
  10. Fix overlays and process definitions.

Where to go from here

Running the postmigration utility for BMC Helix Digital Workplace


Was this page helpful? Yes No Submitting... Thank you

Comments

  1. Dnyaneshwar Nanaware

    Link for Registering the target system for DWPC taking us to the page of 'registering source system'? is configuration for target and source is same ?

    Apr 13, 2023 03:05
    1. Himanshu Raul

      Hi Dnyaneshwar,

      Thank you for your comment. We have updated the documentation.

      If you want to configure target system for DWPC, you can refer the same topic for the steps. See Registering a system for BMC Digital Workplace Catalog.

      Regards,

      Himanshu

      Apr 19, 2023 01:10
      1. Dnyaneshwar Nanaware

        Thanks Himanshu !

        Apr 19, 2023 09:33
  2. Dnyaneshwar Nanaware

    Section "To Migrate data" : Point 3-B-ii and Point 3-C-ii where it says "Navigate to the Data Update tab and select Create Data Update Job." but there is no option available to create data update job under tab "Data update"

    You need to first click on "Run Data Updates" button and then window appear to configure new data update job.

    This is confusing and steps are not clear here. You need to consider this to be corrected.

    Apr 19, 2023 09:32
    1. Himanshu Raul

      Hi Dnyaneshwar,

      Thank you for pointing out this issue with the content. We have corrected the topic with your feedback.

      Regards,

      Himanshu

      Apr 26, 2023 05:35
  3. Dnyaneshwar Nanaware

    Section "To Migrate data" : Point 3-d In "Track Data Update Jobs" tab you won't have jobs there, you need to first create job then it will appear there and you can run the individual scripts.

    Apr 19, 2023 10:24
    1. Himanshu Raul

      Hi Dnyaneshwar,

      Thank you for pointing out this issue with the content. We have corrected the topic with your feedback.

      Regards,

      Himanshu

      Apr 26, 2023 05:36
  4. Dnyaneshwar Nanaware

    Section : "To migrate BMC Helix Digital Workplace Catalog groups from the source system to target system"

    Where there is important warning says "Make sure that the CSV files to which you export the results do contain any column titles or headers" so is it "do contain" OR "Do not contain"?

    Apr 20, 2023 02:19
    1. Himanshu Raul

      Hi Dnyaneshwar,

      Thank you for pointing out this issue with the content. We have corrected the topic with your feedback.

      Regards,

      Himanshu

      Apr 26, 2023 05:35
  5. Stefan F.

    Section "Before you begin": "Verified that the myit-sb:mp_search_categories table in DWP-C do not have any duplicate categories. Fix any duplicate categories in the DWP-C source system."

    Can you specify what makes a category a duplicate? Is it by name only or by name and Parent_id? In our system I can see 3 ootb entries for "Productivity" but they are linked to 3 different parent_ids - is this considered a duplicate?

    Feb 02, 2024 06:18