×
 
 
  •  
$helper.renderConfluenceMacro('{bmc-global-announcement:$space.key}')

Unsupported content

 

This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.
BMC Decision Support for Server Automation 8.9 ... Using Working with views using Open schema

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.

Tip

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.

Tip

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.

Dimension tables

Table Name/DescriptionERD

D_BLGROUP

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.

D_JOB

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.

Note:

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.

D_SCHEDULE

Contains information about the job schedule, such as the schedule cadence (daily, weekly, or monthly), and the time of the last run.

Note:

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.


D_SERVER

Contains device details for the job, such as the name and description of a server, the OS release/version, and so on.

 Bridge tables

Table Name/DescriptionERD

B_BATCH_JOB_RUN

Contains details specific to Batch Job runs, such as the job run history ID, and so on.

Note:

F_JOB_RUN is also referenced in the ERD as DEPLOY_JOB_PHASE_RUN.

 

B_DEPLOY_JOB_RUN

Contains details specific to Deploy Job runs, such as the sequence of the Deploy Job runs, and so on.

Fact tables

Table Name/DescriptionERD

F_JOB_DEPOT_OBJECT

Provides the relationship between the job and its corresponding Depot object, as well as the BL Value ID for objects.

 

F_JOB_RUN

Contains details for the job run, such as the job type and the status of the run (completed, error, warning, or cancelled).

F_JOB_RUN_SERVER

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.

Generic tables

Table Name/DescriptionERD

DEPLOY_JOB_PHASE_RUN

Contains data about the various phases of the Deploy Job run, such as the job run start time, end time, status, and so on.

Note:

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.



 

JOB_RUN_EVENT

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.

Recommendation

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/DescriptionColumns in the viewExample

VO_DEPLOY_JOB_DETAIL_BY_SERVER

Provides details about all Deploy Jobsexecuted on a server, such as Deploy
job run start time, start and end time for the Deploy Job server phase, and server
run status of the Deploy Job.

  • BL_SITE_ID
  • JOB_HISTORY_ID
  • OS_NAME
  • JOB_NAME
  • JOB_TYPE
  • JOB_RUN_START_TIME
  • JOB_RUN_END_TIME
  • JOB_RUN_History Id
  • Run By Role
  • Run By User
  • Deploy Server History Id
  • Deploy Server Name
  • Deploy Job Server Phase
  • Deploy Job Server Phase Start Time
  • Deploy Job Server Phase End Time
  • Deploy Job Server Run Status

Select * from
vo_deploy_job_detail_by_server
where job_run_start_time between
"dd/mm/yyyy" and
"dd/mm/yyy" and bl_site_id = 1

VO_DEPLOY_JOB_SUMMARY

Shows high-level details of a Deploy Job, such as job name, job run start
time, role and user of a job, and the number of servers on which the job was run. 

  • BL_SITE_ID
  • JOB_TYPE
  • JOB_NAME
  • JOB_ID
  • JOB_HISTORY_ID
  • JOB_RUN_HISTORY_ID
  • JOB_RUN_START_TIME
  • JOB_RUN_END_TIME
  • TIME_TO_EXECUTE_(SEC)
  • DEPLOY_JOB_PHASE
  • SERVERS_ATTEMPTED
  • RUN_STATUS

Select * from
vo_deploy_job_summary
where job_run_start_time
between "dd/mm/yyyy" and
"dd/mm/yyy" and bl_site_id = 1

VO_JOB_ACTIVITY_SUMMARY

Shows a summary of all job activity, such as the number of jobs,
job runs, and the servers on which a job type was run over a
selected time interval.

  • BL_SITE_ID
  • JOB_TYPE
  • JOBS_COUNT
  • JOB_RUNS_COUNT
  • SERVERS_ATTEMPTED

Select * from
vo_job_activity_summary
where bl_site_id = 1

VO_JOB_RUN_SERVER_DETAILS

Shows job run details, such as role, user, status, OS name, and server name and
time for execution for a particular server.

  • BL_SITE_ID
  • JOB_HISTORY_ID
  • JOB_TYPE
  • PARENT_JOB_NAME (displayed if
    parent job exists)
  • JOB_NAME
  • JOB_RUN_HISTORY_ID
  • RUN_BY_ROLE
  • RUN_BY_USER
  • JOB_RUN_START_TIME
  • JOB_RUN_END_TIME
  • OS_NAME
  • SERVER_NAME
  • SERVER_HISTORY_ID
  • RUN_START_TIME (for server)
  • RUN_END_TIME (for server)
  • SERVER_RUN_STATUS

Select * from
vo_job_run_server_details where
job_run_start_time between
"dd/mm/yyyy" and "dd/mm/yyy"
and bl_site_id = 1

Where to go from here

Compliance domain

Patch Management domain

Role Based Access Control (RBAC) domain

This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Last modified by Bob Massa on Sep 30, 2016

Comments

Log in or register to comment.

Working with views using Open schema
Patch Management domain
© Copyright 2013 - 2017 BMC Software, Inc.
Legal notices

Powered by Atlassian Confluence and Scroll Viewport

© Copyright 2005-2024 BMC Software, Inc. Use of this site signifies your acceptance of BMC’s Terms of Use . BMC, the BMC logo, and other BMC marks are assets of BMC Software, Inc. These trademarks are registered and may be registered in the U.S. and in other countries.