Job Activity domain
The Job Activity domain contains various information related to job activity, such as:
- The number of jobs of a given type are running
- The platforms on which the jobs are running
- The success rate for the jobs
- Other detailed information, such as job scheduling and job approval details
The Job Activity domain also provides data and statistical measurements related to all jobs that run in BMC Server Automation. You can use this information to build your own custom Job Activity reports using your own reporting tool.
This topic contains the following sections:
Job Activity domain entity-relationship diagram (ERD)
The following figure provides the ERD for the Job Activity domain. It shows the relationships between the dimension, fact, bridge, and generic tables.
To view the detailed expressions that allow you to join tables, you can download the Job Activity schema definition HTML file.
To understand the relationships between tables, click the ERD image below and then click the magnifying glass icon to zoom in to the image.
Tables in the Job Activity domain
The following tables comprise the Job Activity domain:
- Dimension tables - Describe the properties of an object that are subject to change. These tables are prefixed with D_, for example, D_JOB.
- Bridge tables - Are used to link two tables. These tables are prefixed with B_, for example, B_BATCH_JOB_RUN.
- Fact tables - Contain factual information that remains constant and is required for reporting. These tables are prefixed with F_, for example, F_JOB_RUN.
- Generic tables - Are used in BMC Server Automation. These tables are not prefixed with any alphabet, for example, JOB_RUN_EVENT.
To view any of the ERD images in the tables below, click the image thumbnail and then click the magnifying glass icon to zoom in to the image.
Contains information about the folder group where the job is stored, such as the group name, the group type (Server, Job, Depot), the fully qualified path to the group, and the parent group details.
Note: D_BLGROUP is referenced in the ERD as D_SMART_BLGROUP.
Contains job details such as the name, description, and type of job, as well as the dates on which the jobs were created or modified.
D_BLROLE is referenced in the ERD as JOB_MODIFIED_BLUSER, JOB_CREATED_BLUSER.
B_BATCH_JOB is also referenced in the ERD as B_DEPLOY_JOB_JOB.
Contains information about the job schedule, such as the schedule cadence (daily, weekly, or monthly), and the time of the last run.
D_BLROLE is also referenced in the ERD as SCH_MOD_BLROLE, SCH_BLROLE.
D_BLUSER is also referenced in the ERD as SCH_MOD_BLUSER, SCH_BLUSER.
Contains device details for the job, such as the name and description of a server, the OS release/version, and so on.
Contains details specific to Batch Job runs, such as the job run history ID, and so on.
F_JOB_RUN is also referenced in the ERD as DEPLOY_JOB_PHASE_RUN.
Contains details specific to Deploy Job runs, such as the sequence of the Deploy Job runs, and so on.
Provides the relationship between the job and its corresponding Depot object, as well as the BL Value ID for objects.
Contains details for the job run, such as the job type and the status of the run (completed, error, warning, or cancelled).
Contains details for the job run by server, such as the start time and the end time of the job run, the job type, and the job run status.
Contains data about the various phases of the Deploy Job run, such as the job run start time, end time, status, and so on.
D_JOB is also referenced in the ERD as DEPLOY_JOB_PHASE.
F_JOB_RUN is also referenced in the ERD as DEPLOY_JOB_PHASE_RUN, DEPLOY_JOB_RUN_SERVER.
Contains event messages for each job run, including dates, job event ID, and so on.
Built-in Job Activity views
BMC Decision Support for Server Automation provides the following built-in views.
BMC recommends that you apply appropriate filters (such as date duration or bl_site_id) while querying the views. You can also apply other filters based on your requirements. Filtering the data improves performance by decreasing the amount of data being fetched, thereby minimizing the time required to process the views.
|View Name/Description||Columns in the view||Example|
Provides details about all Deploy Jobsexecuted on a server, such as Deploy
Shows high-level details of a Deploy Job, such as job name, job run start
Shows a summary of all job activity, such as the number of jobs,
Shows job run details, such as role, user, status, OS name, and server name and