Actions you can perform on a system you have registered

The Action list on the System Configuration page supports the following functionality:

Test Database Connectivity—Test that the database connection details are valid.
Test Remedy API Connectivity—Test that the AR System API connection details are valid.
Discover Data Dictionary—Perform application discovery
System Admin—Navigate to the system Admin pages to allow for AR System API tasks and the management of post migration scripts
Get Database Character Set—Retrieves the character set for the database
Create BMC Helix Data Manager Database Integration—Create the BMC Helix Data Manager user and DB side objects
Remove Database Integration—Remove the BMC Helix Data Manager user and the DB side objects

Enabling a system for data migration

Enabling a system for data migration allows you to perform import and export operations for the system. Otherwise, you can perform only discovery and validate connectivity for the system.

The easiest way to enable the system for data migration is to use BMC Helix Data Manager to automatically obtain the database character set. (Select Action > Get Database Character Set.) Optionally, you can manually enter the following details:

Field	Description
Enabled for Data Migration	Select this option to enable a BMC Helix ITSM system to have data exported or imported. Enabling a BMC Helix ITSM system for data migration will prompt for the data migration fields.
DB Character Set	The character set used by the database hosting the application. This setting is critical in the case of character set conversions.

To test database connectivity

Perform the following steps to test that the database connection details are valid:

Log in to BMC Helix Data Manager.
On the System Configuration page, select Action > Test Database Connectivity.
A progress tracker appears and then displays a success or failure message.

To test AR System API connectivity

Perform the following steps to test that the AR System API connection details are valid:

Log in to BMC Helix Data Manager.
On the System Configuration page, select Action > Test Remedy API Connectivity.
A progress tracker appears and then displays a success or failure message with the relevant error.

Viewing properties of the configured system

The Properties tab shows the list of optional properties that are associated with the configured system.

The currently supported system properties are:

Type	Description
Midtier Name	Name of the mid tier you are using.
Server Name	Name of the server you are using.
Group Id Transform	(Optional) When migrating data between BMC Helix ITSM systems, you can apply a prefix to an AR System group to prevent clashes with data in the target BMC Helix ITSM system. This prefix is applied only for certain migration scenarios to avoid Group ID clashes. You must supply a unique prefix of up to three numbers for this field. For example, you may want to assign "111" as the prefix for your QA system. You can define only one Group ID Transform property for a BMC Helix ITSM system.
Unique Id Transform	(Optional) When migrating data between BMC Helix ITSM systems, you can apply a prefix to BMC Helix ITSM Ticket Numbers and Request IDs to prevent clashes with data in the target BMC Helix ITSM System. This prefix is applied only for certain migration scenarios to avoid Request ID clashes. You must supply a unique prefix of up to three characters for this field. For example, you might want to assign "QA" as the prefix for your QA system. You can define only one Unique ID Transform property for a BMC Helix ITSM system. When setting up a new BMC Helix ITSM System, an identifier prefix is automatically set up. This identifier prefix is used when importing records that have a Match On Key set to any value except Request ID. The imported Request ID is transformed to ensure that imported records do not clash with existing records in the system. The Identifier Prefix is automatically set to the first character of the name of the BMC Helix ITSM system or "A" if a name begins with a number.
Export Fetch Size	Export Fetch Size is the number of records exported by the BMC Helix Data Manager in one iteration. You can use this parameter to enhance the export performance of the system, specially when you are exporting PostgreSQL data. By default, this value is set to 100. We recommend you to set this value from 500 to 1000, as per your memory requirements.
Disable Triggers	(Optional) Use this property only when you migrate BMC Helix ITSM: Smart IT data. When you migrate the Smart IT data, the forms are migrated with no sequence and the qualifications in the dependent forms give an error. Use this property to disable the qualifications for a successful migration. Before performing the Smart IT migration, set the Disable Triggers property to True. After you complete the migration, set this property to False.
JDBC Override URL	(Optional) Used to create a JDBC connection string that BMC Helix Data Manager will use when connecting to the BMC Helix ITSM database. This value overrides the DB Network Address, DB Port, Remedy Schema Name, CMT DB User, and CMT DB Password values. This is typically used only when connecting to specially configured databases that cannot be connected to using the standard mechanisms and encrypted connection to database. (for example, clustered database servers). If you are using a PostgreSQL database and you want to use encrypted connections, configure the database to enable SSL connections. Use the following steps to connect BMC Helix Data Manager to the BMC Helix ITSM database: Important Note the database host name that you specify in the certificate common name (CN). Specify the same database host name as source / target connection. BMC Helix Data Manager requires root.crt file in order to configure secure and encrypted connection. Create a new directory as *<HDM_Installation_directory>\certs* and copy the certificate in it. After registering a system, navigate to System>Properties tab and click + button. From the Type list, select JDBC-Override. In the Value field, add the JDBC URL in the following format: jdbc:postgresql://host:port/database?ssl=true&sslmode=verify-ca&sslrootcert=C:\Program Files\BMC Software\Helix Data Manager\certs\root.crt Click Save. For more information on PostgreSQL parameters such as sslmode, sslrootcert, sslcert, sslkey, and other connection parameters, see https://jdbc.postgresql.org/documentation/ssl/#configuring-the-client in the PostgreSQL documentation.
Script Security	BMC Helix Data Manager allows database scripts to be executed against the target BMC Helix ITSM system after a data migration is performed. These scripts typically apply complex transformations that cannot be applied during the data migration. Typically, BMC provides all scripts and are signed to ensure that only authorized and validated scripts can be run against your BMC Helix ITSM systems. However, you can configure BMC Helix Data Manager to allow unsigned scripts to be executed. This must be configured against each BMC Helix ITSM system on which you want to execute unsigned scripts. You can set the following values for this property: Signed Scripts Only—Only scripts signed by BMC can be executed. This is the default value that is set if no property is defined Signed or Unsigned Scripts—Allows unsigned scripts to be run if the system has also been configured with an appropriate Script Security Signature property.
Script Security Signature	Must be configured if Signed or Unsigned Scripts is set for the Script Security property. To authorize your BMC Helix ITSM system to execute unsigned scripts, BMC must provide you with this encrypted string. Contact BMC support to obtain a signature for your BMC Helix ITSM system.
NLS_SORT	Used for Oracle Databases where the BMC Case Insensitivity guidelines have been followed. Setting this value to BINARY_CI ensures BMC Helix Data Manager fully supports NLS_SORT, NLS_COMP, and function-based indexes to ensure maximum performance where this option has been used. You will normally not need to set this as an option. If in doubt, contact your BMC Support.
Session Parameter	Used to set or modify any conditions or parameters that affect your connection to the database. The session that is set will be in effect until you disconnect from the database. An example entry is as follows: NLS_DATE_FORMAT For more information, see the NLS_DATE_FORMAT description in the Oracle documentation.