Moving from BMC Decision Support for Server Automation
Before you begin
Ensure that you do the following actions before moving to TrueSight Smart Reporting for Server Automation:
- Take a full backup of the Master, Work, Warehouse databases.
- Stop ETL on BMC Decision Support for Server Automation. Ensure that you move the run_etl.nsh file from $BDS_HOME/shared/odi/bin to $BDS_HOME/shared/odi directory.
- Ensure that there are no schedules for archival or ETL jobs in TrueSight Server Automation.
- If you are using custom reports in BMC Decision Support for Server Automation, note down the attributes used in the custom reports because after you migrate to TrueSight Smart Reporting for Server Automation, you need to create the custom reports again. For more information about how to create custom reports in TrueSight Smart Reporting for Server Automation, see Creating-reports.
- If you are using schedules in BMC Decision Support for Server Automation, note down the schedules for the reports because after you migrate to TrueSight Smart Reporting for Server Automation, you need to add all the schedules again by using the Broadcast option for the reports. For more information about how to create schedules for reports in TrueSight Smart Reporting for Server Automation, see Broadcasting-reports. As a TrueSight Smart Reporting - Platform administrator, you can log in to TrueSight Smart Reporting - Platform to view all the schedules in Administration > Schedule Management.
Scenarios for moving from BMC Decision Support for Server Automation
Where to go from here
Planning-for-TrueSight-Server-Automation-Data-Warehouse-deployment
Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*