Performing the initial ETL run
Before using BMC BladeLogic Decision Support for Server Automation, you must start the ETL process to transfer data from the BMC Server Automation database to the reports data warehouse.
After you install BMC BladeLogic Decision Support for Server Automation at the primary BMC Server Automation site, you can run ETL to transfer data from the primary site to the reports warehouse.
The instructions in this topic describe how to run ETL from the command line. You can also create a BMC Server Automation Network Shell Script Job to run ETL. BMC recommends that you create a job for running ETL on a regular basis.
The initial ETL run can take a long time, because it is performing a full data load. Keep this in mind when deciding whether to run the initial ETL process from the command line or use a BMC Server Automation Network Shell Script Job. For information about how to create a Network Shell Script Job, see Creating Network Shell Script Jobs.
Before running ETL for the first time, ensure that you have assigned appropriate roles to the users (for example, a primary site user must have the GlobalReportAdmins role). For more information, see Managing-access.
To run ETL for the first time
- Navigate to the BDSSAInstallationDirectory/etl/bin directory.
On the reports server, from a command line, start the Network Shell and enter the following command:
./run_etl.nsh -s 1 -v <blVersion> -d 3Alternatively, from a command line, enter the following command:
nsh ./run_etl.nsh -s 1 -v <blVersion> -d 3In this command, replace <blVersion> with the version of BMC Server Automation that you use at your primary site.
This command uses standard values for the command arguments. For detailed instructions on running ETL and a description of the command arguments, see Running-ETL.
To transfer data from other sites, you must add those sites if they are not already added, and then re-run the run_etl command for each site. For more information, see Adding-sites.