Completing postmigration steps

Following a successful BMC Helix Data Manager data migration, it is necessary to perform several postmigration steps to configure the target AR System. The high-level steps are:

1. Run data update scripts by using BMC Helix Data Manager.
2. Identify and transform server references by using BMC Helix Data Manager.
3. Start the AR System server.
4. Build any migrated SLA data source, targets, and agreements.
5. Build any migrated approval chains and notifications.
6. Configure entitlements.
7. Trigger an FTS rebuild.
8. (Microsoft SQL Migrations only) Rebuild indexes on Microsoft SQL.

To run data update scripts

Data update scripts provide a set of SQL updates that should be run after a successful migration. These updates apply transformations appropriate for the new ITSM and update core AR System data such as NextID for all forms. The template scripts appropriate for your upgrade can be downloaded from the BMC Electronic Product Distribution (EPD) website.

1. From the navigation bar, select Discovery & Analysis > System Analysis & Administration.
2. On the System Administration page, select the target system into which data was imported.
3. Click the Available Data Updates tab.
   A list of all Data Update templates you imported appears.
   
   If you have not yet imported the Data Updates appropriate for your upgrade, you can obtain these from the BMC Electronic Product Distribution (EPD) website. Import these in the same way as your migration packs. 
4. Select the template you want to use, and click Run Data Updates.
5. In the Create Data Update Job dialog box, confirm the details and optionally override the Update Job Name for your reference, and click Create New Data Update Job.
   The Track Data Update Jobs tab automatically displays your new data update job.
   
6. Click Run All Scripts to run all data updates in sequence.
7. Check the results Track Data Update Jobs tab to ensure that all updates ran successfully.
   Run these scripts once after the Global data and then the Company data is migrated. There are no harmful effects from running these scripts multiple times.

Server reference updates

BMC Remedy ITSM embeds AR System server and mid-tier names in some data. BMC Helix Data Manager can discover and transform these server references.

Download and import the templates from the BMC Electronic Product Distribution (EPD) website. It is essential to review these settings for a successful upgrade.

To build workflow after a data migration

After a data migration of any of the following components, you should trigger the AR System API to build the workflow associated with the data:

• Approval Chains
• Approval Notifications
• SLA Data Sources
• SLA Targets
• SLA Agreements

1. Start the AR System server.
2. Make sure your target system in BMC Helix Data Manager has an AR System API connection configured. See Registering-source-and-target-systems.
3. BMC Helix Data Manager will be triggering workflow so the AR System server it connects to must have the ability to make workflow changes.
4. From the navigation bar, select Discovery & Analysis > System Analysis & Administration from the navigation bar.
5. On the System Administration page, select the target system into which data has been imported, and click the Approval Chains tab.
6. Click Discover to extract the data for the approval chains in the target system.
   Discovery will not require an AR System API connection.
   When discovery is complete the details of the Approval Chains are displayed on the Discovered Configuration tab.
7. Click Build to open the Build Approval Chains dialog box.
   Optionally, you can change the qualification used to identify approval chains that should be built. Click Build Approval Chains to commence the update.
   BMC Helix Data Manager will track the progress and result of the update.
8. When the Approval Chains update is complete, repeat these steps for Approval Notifications and SLM Configuration.

To build SLA data sources, targets, and agreements manually

1. Log in to the target system, and select the Application Navigation > Administrator Console > Application Administration Console.
2. Click the Custom tab, and select Service Level Management > Configure Application Settings > Data Sources.
3. For each data source, click Create Fields and, when the build process is complete, click Create Filter.
4. Select Application Navigation > Service Level Management > Service Level Management Console.
   Each migrated SLA agreement will have its status automatically set to Build Pending by BMC Helix Data Manager.
5. Select each SLA agreement, and click Build. Click Yes in the dialog box to confirm the build.
   The AR Server automatically creates the workflow for the migrated SLA agreement.
   Each migrated SLA target will have its status automatically set to Build Pending by BMC Helix Data Manager.

6. Select each SLA target, and click Build. Click Yes in the dialog box to confirm the build.
   The AR System server automatically creates the workflow for the migrated SLA target.
   On rare occasions, the SLA target can fail to build the first time after being migrated. In the event of a failure, try a second build of the SLA target. In the event of another failure, contact BMC Support with the details found on the Administration tab of the SLA target, which displays the records and detailed failure messages.

   Important

   You cannot re-migrate SLA targets or SLA agreements after building them in the target system. This is due to the way in which the SLM module deletes and creates data and workflow as part of the build process. Manually delete SLA targets and SLA agreements before re-migrating them or plan your data migration to migrate these components only once, or to build them only once as part of the upgrade process.

To build approval chains and notifications manually

1. Log in to the target system, and select Application Navigation > Application Administration > Application Administration Console.
2. Click the Advanced tab, and select Service Request Management > Approval > Approval Chains.
   Each migrated Approval Chain that had an Enabled status will have its status automatically set to Offline by BMC Helix Data Manager.
3. Select each approval chain and click Modify to open a dialog box that shows the details.
4. Set the status to Enabled, and click Save.
   The AR System server automatically creates the workflow for the migrated approval chain.
   
   Rarely, a custom Approval Chain qualification might no longer be applicable for new version of BMC Helix ITSM. In this case, you cannot set the approval chain's status to Enabled without modifying the qualification. If you have any challenges in adapting qualifications for your new version of BMC Remedy ITSM, contact BMC Support.
   If you have used BMC Helix Data Manager to migrate any custom AP:Notification records, trigger the filter workflow to be built by setting the status of the migrated records to Enabled.

To configure entitlements

The SRM:ApplicationSettings form holds several environment-specific settings and the flag that controls whether entitlement is enabled. By default, entitlement is disabled in the Runtime template.

1. If you migrate the SRM:ApplicationSettings form, use the Server Reference feature in BMC Helix Data Manager to identify and transform environment references.
2. If you do not to migrate this data, manually configure the setting for entitlements:
   1. Log in to the target system, and select the Application Navigation > Application Administration > Application Administration Console.
   2. Select the Advanced tab.
   3. To open the Entitlement Management console, select Service Request Management > Entitlement > Entitlement Management.
      
      Changes are automatically updated without needing to confirm.
   4. Configure the settings for entitlement to match those in your source system.

To trigger an FTS rebuild

1. Make sure that at least one AR System server has been started.
2. Log in to the target AR System, and select Application Navigation > AR System Administration > AR System Administration Console.
3. Select System > General > Server Information.
4. Click the FTS tab, and select the Reindex FTS check box.
5. Click OK to trigger the AR System server to update its FTS caches with the migrated data.
   
   This operation might take some time depending on the number of FTS-indexed records that have been migrated.

To rebuild indexes on Microsoft SQL

Recent projects have encountered some performance issues when importing a delta data set to BMC Helix products after an initial bulk migration. The performance of these operations was impacted by high levels of fragmentation in Microsoft SQL indexes. To resolve these issues, you might need to rebuild the indexes.

1. Ensure that the AR System server is down and BMC Helix Data Manager Engine Service is stopped.
2. Open Microsoft SQL Server Management Studio.
3. Log in as an Administrator user.
4. Click New Query and select the AR System database.
5. Run the following SQL command:
   Exec sp_msforeachtable 'SET QUOTED_IDENTIFIER ON; ALTER INDEX ALL ON ? REBUILD'
   GO
   This can take several hours to run depending on the size of the database and disk performance. We recommend rebuilding indexes after a bulk load operation on BMC Helix ITSM.