Running ETL using BMC Server Automation jobs
A script is available for you to download and use to create a
Network Shell Script Job for running ETL from .The script, which is called run_etl_from_om.nsh, is included in the Inventory-Templates.zip file, which is located in the BDSSAInstallationDirectory/Contents directory. When you extract the contents of the Inventory-Templates.zip file and run the content installer, the script is added to
as a script. For information about running the content installer, see Running the content installer.You can use the run_etl_from_om.nsh script to create a
Script Job that you can use to run ETL on specified servers. You can execute the job for a one-time run or you can create a schedule for the job. The job performs the same task as the run_etl command (see Running-ETL-using-an-NSH-script).You can schedule ETL runs for multiple sites in a batch job. For more information, see Scheduling-ETL-for-multiple-sites.
This topic provides the details that you need to create a
Script Job for the run_etl_from_om.nsh script, including the flags and parameters.To create a Network Shell Script Job for the run_etl_from_om.nsh script
- Locate and select the run_etl_from_om.nsh script in the .
- Create a Script Job for the run_etl_from_om.nsh script.
The details about parameters and flags that you can set are included in the table in this topic. For information about creating a Network Shell Script Job, see Creating Network Shell Script Jobs. Create a schedule for the job if you want to run ETL on a schedule.
Script Job by using the run_etl_from_om.nsh script, you specify the parameters and flags to be used when the job runs.
When you create a
The following table lists the parameters and flags that you can specify in the Parameters panel of the job creation wizard.Parameter
Required?
Flag
Description/Value
ETL_HOME
Yes
-h
The directory in which the ETL-related files are located. The default location is BBDSSAInstallationDirectory/etl/bin (see the following image for an example, including a sample directory).
Note: Enter the path in NSH format.SITE
Yes
-s
The site ID. This should be a valid site ID from the BL_SITE table.
You can determine the site ID by using the Report Administration Utility show site command. See Report-Administration-Utility-commands for details.OM_VER
Yes
-v
The version number of BMC Server Automation from which data is to be transferred.
Do not include periods in the version number.
For information about the BMC Server Automation versions that work with BMC BladeLogic Decision Support for Server Automation, see BMC-Server-Automation-requirements.RPT_PROP
No
-f
The property file to run (for a list of the property files representing specific scenarios for report data groups see Property-files).
If you do not specify a property file, the default RunETL.properties file is used. This file includes all scenarios.LVL_PRL
No
-p
Indicates the number of scenarios to run in parallel.
The value can be any number from 1 to 20. It usually depends on system settings and underlying hardware load limits.
If you do not specify a level, the default level 20 is used.LOGLEVEL
No
-d
Indicates the log (or debug) level, which can be a value of 1 to 5, with 1 indicating the lowest logging level (minimal logging) and 5 indicating the highest logging level (detailed logging).
COG_FLAG
No
-l
Overrides the locking mechanism for the reports data model (1 indicates to override the locking mechanism; 0 indicates to not override the locking mechanism).
If you do not specify a value, the default setting of 0 is used.
Your job settings should look similar to the settings illustrated in the following example.
