21.3 enhancements and patches

(On-premises only) Downloading and installing the patch

21.3.05

Support for PostgreSQL database version 13.x

BMC Helix Data Manager version 21.3.05 supports PostgreSQL database version 13.x. In earlier versions of BMC Helix Data Manager, such as 21.3.01, 21.3, and 21.05, the HDM Repository runs on PostgreSQL version 9.x.

If you are using a previous version of the PostgreSQL database, you must update your PostgreSQL database to version 13.x. For steps to upgrade your PostgreSQL database, see Upgrading-the-PostgreSQL-database.

Upgrade your BMC Helix Data Manager

You can upgrade your BMC Helix Data Manager to the latest version.

For more information, see Upgrading-BMC-Helix-Data-Manager.

Additional commands for automating the migration

The command-line utility includes additional commands for enhancing the migration.

• SET-TRIGGER - enables or disables triggers for Relational database (Smart IT) system.
• EXPORT-META-DATA - exports the metadata files from any file system used for migration.
• VALIDATE-MIGRATION-PACK - gives a list of errors for all the unmapped form mappings for a specified migration pack.
• ADD-EXCLUDED-FORMS - adds the specified forms to the form exclusion list. 
• DELETE-EXCLUDED-FORMS -  deletes the specified forms present in the form exclusion list.
• MAP-SOURCE-LOOKUP-FIELDS - maps all the unmapped and ignored field mappings from the source lookup form and the target form.
• CREATE-HDM-DB-INTEGRATION - creates an BMC Helix Data Manager user and associated database functions to support discovery and data migration.
• REMOVE-HDM-DB-INTEGRATION - deletes the HDM user and associated database integration.

For more information, see Automating-the-migration-by-using-the-command-line.

Add custom and non-custom forms by using the command-line utility

You can add custom as well as non-custom forms to a migration pack by using the command-line utility that help you to migrate your customizations to the latest version of your application.

Use the following parameters when you run the COPY-MIGRATION-PACK command for the migration:

• add-custom-forms
• custom-form-migration-set
• custom-form-names

For more information, see Automating-the-migration-by-using-the-command-line.

Track detailed progress of an import job

Use the Progress Tracker tab to view the detailed progress of an import job.

The Progress tracker tab tracks each stage of the import process. If the import job fails, use the Progress Tracker tab to find the failed process.

For more information, see Viewing-and-monitoring-import-jobs.

Track list of SQL queries

Use the SQL Executed tab to view the list of the SQL queries executed during the import job. You can troubleshoot and debug the INSERT or MERGE errors by using this tab.

For more information, see Viewing-and-monitoring-import-jobs.

Ignore legacy fields automatically

Use the Ignore Legacy Fields option to ignore the SOURCE NOT MAPPED warnings in the migration pack.

After you perform multiple migration cycles, the legacy fields from earlier cycles are present in the system and the SOURCE_NOT_MAPPED warnings are displayed in the migration pack. The Ignore Legacy Fields option ignores these warnings in the next migration cycle.

For more information, see Managing-BMC-Helix-Data-Manager-Runtime.

Increase target field length automatically

While importing data by using BMC Helix Data Manager, you can automatically increase the length of the target field when the target field length is less than the source field length.

You can increase the target field length by using the Length Exception Retry option.

For more information, see Managing-BMC-Helix-Data-Manager-Runtime.

Export data in binary format

Use the Export Type option to export data into a binary file format. The Binary File export type avoids delimiter and special character issues in your migration.

For more information, see Managing-BMC-Helix-Data-Manager-Runtime.

Perform bulk modification of server references

You can update the value for multiple server references at the same time. You can discover all these references prior to a migration and then update them after the migration to ensure the data configuration works correctly in the new environment.

The Transform Value column displays a preview of all the server references after data transformation.

For more information, see Discovering-server-references.

Map data by using the current timestamp value

You can use the Current Timestamp option to map fields to the current timestamp value.

This option gives you the ability to populate fields in the target system by using the current timestamp value.

For more information, see Mapping-and-transforming-fields.

Delete data by using the Delete Tracking Enabled option

BMC Helix Data Manager tracks the deletions from the Action Request System and performs the deletion by using Delete Tracking Enabled option.

The Delete Tracking Enabled option performs the deletions faster than the traditional Form Deletion Template option. For more information, see Running-a-delta-data-incremental-migration-job.

You can also set the enable-delete-tracking option by using the command-line utility. For more information, see Automating-the-migration-by-using-the-command-line.

Import user cache data

Use the User Cache Import Action option to import the user cache during the import job. You can enable or disable the user cache processing by using this option.

For more information, see Running-an-import-migration-job.

You can also set the user-cache-action option by using the command-line utility. For more information, see Automating-the-migration-by-using-the-command-line.

Encrypt the connection to the database by using the command-line utility

Use the system-props parameter in the CREATE-SYSTEM command to set a JDBC URL for encrypted connection to the database.

For more information, see Automating-the-migration-by-using-the-command-line.

To encrypt the connection by using the BMC Helix Data Manager Workbench UI, see Actions-you-can-perform-on-a-system-you-have-registered.

21.3.01

Spring4Shell security vulnerability (CVE-2022-22965) fixed in BMC Helix Data Manager 21.3.01

A zero-day exploit for the vulnerability CVE-2022-22965 (code named Spring Shell or Spring4Shell) was publicly released on March 30, 2022. A detailed description of the vulnerability can be found on the Spring Framework RCE, Early Announcement page.

For BMC Helix Data Manager version 21.3.01, the fix for the security vulnerability is included in this release. If you have any questions about the problem, contact BMC Support.

Additional commands for automating the migration

The command-line utility includes additional commands for enhancing the migration.

• CREATE-FILE-SYSTEM
• UPDATE-FILE-SYSTEM
• SCAN-FILE-SYSTEM
• CREATE-SYSTEM
• UPDATE-SYSTEM
• DELETE-SYSTEM
• SCAN-METADATA-STORE
• IMPORT-META-DATA
• TEST-IMPORT
• TEST-EXPORT
• CREATE-DELETION-JOB

For more information, see Automating-the-migration-by-using-the-command-line.

Defect fixes

This release includes fixes for BMC Helix Data Manager related defects. For more information about the defects fixed in this patch, see Known-and-corrected-issues.

21.3

Automate migration by using the command-line utility

Automate the repetitive tasks performed during migration and reduce the need for user interaction and run the migration process by using the command line utility.

You can automate data migration by setting migration options, performing discovery, migrating data, performing data updates, comparing information between migrations, and by generating reports. In addition, you can also monitor job execution.

For more information about running the automation, see Automating-the-migration-by-using-the-command-line.

Support for BMC Helix Innovation Suite applications and BMC Helix Business Workflows

Use BMC Helix Data Manager to migrate application data from BMC Helix Innovation Suite applications and BMC Helix Business Workflows.

For more information, see the topic Registering-a-system-for-Innovation-Suite.

Defect fixes

This release includes fixes for BMC Helix Data Manager related defects. For more information about the defects fixed in this patch, see Known-and-corrected-issues.