Property files
You can use property files with the scenario execution script (also called the run ETL command) to specify the report data group scenario that you want to run.
The property files are installed in the etl/bin directory.
Most of the report data group scenarios are associated with property files. In addition to the associated report data group scenario, a property file includes the parent scenarios on which the child scenario depends (1_MASTER, 2_FOUNDATION, and if applicable, 3_CONFIG_OBJECTS) to ensure that scenarios run in the required execution sequence. You provide a property file as an argument to the scenario execution script, run_etl.nsh. Only one property file can be provided as an argument.
The RunETL.properties property file is the default property file used by the scenario execution script. If you do not specify a property file with the -f argument in the run_etl.nsh command line, this property file is used.
BMC BladeLogic Decision Support for Server Automation contains the following property files:
Property file | Included in the default ETL run? | Description |
|---|---|---|
RunETL.properties | Yes | Runs all scenarios |
agentlogs.properties | No | The default property file, RunETL.properties, does not include a scenario for the agent logs report data group. Agent logs is a unique data group. You can run data from the agent logs group with the run_etl.nsh script by providing the agentlogs.properties file as the value for the -f argument. When you run the script, the 3_AGENT_LOGS scenario is called after the 1_MASTER and 2_FOUNDATION scenarios. |
audit.properties | Yes | The default property file, RunETL.properties includes a scenario for the audit report data group. You can also run this scenario separately, by providing the audit.properties file as the value for the -f argument in the run_etl.nsh script. When you run the script, the 4_AUDIT scenario is called after the 1_MASTER, 2_FOUNDATION, and scenarios starting with the number 3. |
compliance.properties | Yes | The default property file, RunETL.properties includes a scenario for the compliance report data group. You can also run this scenario separately, by providing the compliance.properties file as the value for the -f argument in the run_etl.nsh script. When you run the script, the 3_COMPLIANCE scenario is called after the 1_MASTER and 2_FOUNDATION scenarios. |
inventory.properties | Yes | The default property file, RunETL.properties includes a scenario for the inventory report data group. You can also run this scenario separately, by providing the inventory.properties file as the value for the -f argument in the run_etl.nsh script. When you run the script, the 4_INVENTORY scenario is called after the 1_MASTER, 2_FOUNDATION, and scenarios starting with the number 3. |
jobactivity.properties | No | The default property file, RunETL.properties does not include a scenario for the job activity report data group. This is a unique report group. You can also run this scenario separately, by providing the inventory.properties file as the value for the -f argument in the run_etl.nsh script. When you run the script, the 3_JOB_ACTIVITY scenario is called after the 1_MASTER and 2_FOUNDATION scenarios. |
jobrunevent.properties | No | The default property file, RunETL.properties, does not include the scenario for job run events. This is a unique scenario. You can run the job run event scenario with the run_etl.nsh script by providing the jobrunevent.properties file as the value for the -f argument. When you run the script, the 3_JOB_RUN_EVENT scenario is called after the 1_MASTER and 2_FOUNDATION scenarios. |
jobschedule.properties | Yes | The default property file, RunETL.properties, includes the scenario for job schedules. You can also run this scenario separately with the run_etl.nsh script by providing the jobschedule.properties file as the value for the -f argument. When you run the script, the 3_JOB_RUN_SCHEDULE scenario is called after the 1_MASTER and 2_FOUNDATION scenarios. |
kpi.properties | No | The default property file, RunETL.properties, does not include the scenario for the KPI data group. This is a unique scenario. You can run the KPI scenario with the run_etl.nsh script by providing the kpi.properties file as the value for the -fargument. When you run the script, the 4_KPI scenario is called after the 1_MASTER, 2_FOUNDATION, and scenarios starting with the number 3. |
patch.properties | Yes | The default property file, RunETL.properties includes a scenario for the patching report data group. You can also run this scenario separately, by providing the patch.properties file as the value for the -f argument in the run_etl.nsh script. When you run the script, the 3_PATCH scenario is called after the 1_MASTER and 2_FOUNDATION scenarios. |
property.properties | Yes | The default property file, RunETL.properties includes a scenario for the properties report data group. You can also run this scenario separately, by providing the property.properties file as the value for the -f argument in the run_etl.nsh script. When you run the script, the 3_PROPERTY scenario is called after the 1_MASTER and 2_FOUNDATION scenarios. |
provisioning.properties | Yes | The default property file, RunETL.properties includes a scenario for the provisioning report data group. You can also run this scenario separately, by providing the provisioning.properties file as the value for the -f argument in the run_etl.nsh script. When you run the script, the 3_PROVISIONING scenario is called after the 1_MASTER and 2_FOUNDATION scenarios. |
rbac.properties | Yes | The default property file, RunETL.properties includes a scenario for the RBAC report data group. You can also run this scenario separately, by providing the rbac.properties file as the value for the -f argument in the run_etl.nsh script. When you run the script, the 3_RBAC scenario is called after the 1_MASTER and 2_FOUNDATION scenarios. |
smartgroup.properties | No | The default property file, RunETL.properties, does not include the scenario for smart groups. This is a unique scenario. You can run the smart group scenario with the run_etl.nsh script by providing the smartgroup.properties file as the value for the -f argument. When you run the script, the 3_SMART_GROUP scenario is called after the 1_MASTER and 2_FOUNDATION scenarios. |
updatecognos.properties | Yes | The default property file, RunETL.properties includes a scenario for updating Cognos. You can also run this scenario separately, by providing the updatecognos.properties file as the value for the -f argument in the run_etl.nsh script. When you run the script, the 4_UPDATE_COGNOS scenario is called after the 1_MASTER and 2_FOUNDATION scenarios. |
For a description of the scenario associated with each property file, see Scenario-descriptions. For instructions on using property file arguments with the scenario execution script, see Running-ETL-using-an-NSH-script.