Syncing CIs for BMC Helix Telco Extensions by using SmartGraph Sync
To perform impact analysis in BMC Helix Telco Extensions, you must first run the CMDB SmartGraph Sync schedule from the CMDB Portal.
Before you begin
To enable the CMDB SmartGraph Sync feature, contact BMC SaaS Support.
After the CMDB SmartGraph Sync schedule widget is enabled for your subscription, log in to CMDB Portal to set the schedule.
To schedule the CMDB SmartGraph Sync
- In CMDB Portal, select Configurations > SmartGraph Sync > Schedule.
- To create a schedule, click Add Schedule.
- Specify the time at which you want SmartGraph Sync to start.
Use the server time as a reference to set the schedule. - Specify the frequency at which you want SmartGraph Sync to run.
You can choose a custom interval by selecting the Interval option and then specifying the interval. The minimum required interval is 30 minutes.
To view the sync details and history, see the following forms in the Mid Tier:
- CMDB:DSMSync_Run_History
- CMDB:DSMSync_Failure_Details
- CMDB:DSMSync_Deletion_Log
- CMDB:DSMSmartGraph Sync Pending
The logs are located at cmdbdsmsyncplugin-<session id> plug-in server for dsm-sync under the directory - /opt/bmc/ARSystem/db
Failover support during the sync
During the sync, if temporary outages or failures occur, the sync automatically resumes from the point of interruption instead of restarting the entire process. Every sync run is tracked using a unique Run ID, and the status of each run is stored in the CMDB:DSMSync_Run_History form.
- If the AR server becomes unavailable, the system automatically retries the synchronization for up to 30 minutes, with attempts occurring at fixed intervals. After the server is back online, the sync resumes seamlessly without user intervention.
- If the plug-in server crashes or restarts, the sync process terminates, while the job status might still display as In Progress in the CMDB:DSMSync_Run_History form. In such cases, you must manually update the job status to Error and initiate a new sync.
This failover mechanism prevents data duplication, minimizes delays, and maintains consistency across synchronized records. In addition, users have improved visibility into the progress and status of synchronization activities.