Built-In Reports
ActiveBatch provides the users two types of reports; SQL Server reports and Crystal reports. OLAP Reports are specific to ActiveBatch Instance Reporting, and both types of reports require an Instance Reporting database where data is populated. Moreover, the reports that use aggregated data require an OLAP cube that can be accessed through Microsoft’s Analysis services for SQL and Oracle’s Analytic Workspace Manager for Oracle reports. A number of canned reports are provided for both report types. In this section, the SQL Server reports are described.
These reports were created using Microsoft Visual Studio 2005, and can be opened and further customized using the same or compatible software.
Expand Reports to see a list of SQL Server built-in report names.

-
ActiveBatchReports_Home
-
AverageJobRunTime_byJobTag_Chart *
-
AverageJobRunTime_byMachine_Chart *
-
AverageVirtualMachineStartupTime_byJobScheduler_Chart
-
CompletedJobBreakdown_byMachineStats *
-
CompletedJobBreakdown_byTagStats *
-
CompletedJobBreakdown_DateTime_Stats *
-
CompletedJobStatus_Chart *
-
Dashboard_byJobScheduler
-
EventAudits_Changes_List
-
EventAudits_List
-
EventAuditType_byObject_Chart
-
EventAuditType_Chart
-
PlansJobs_List
-
SLABatches_List
-
SLACompletionStatus_Chart
-
SLARunTime_byJobScheduler_Chart
-
Top10Jobs_RunTime_byMachine_Stats
-
Top50JobsAvg_RunTime_List *
-
Top50JobsAvg_WaitTime_List *
-
Top50JobsInst_DiskIO_List
-
Top50JobsInst_Memory_List
-
Top50JobsInst_RunTime_List
-
Top50JobsInst_WaitTime_List
-
Top50Machines_CompletedJob_Stats *
-
Top50Machines_JobRunTime_Stats *
-
Top50Machines_JobWaitTime_Stats *
-
AverageJobRun_WaitTime †
-
AverageVirtualMachineStartupTime_Chart †
-
CompletedJob_Stats_ByMachine †
-
JobStatusDistribution †
-
JobCompletionStatus †
-
TopSLABatchesList †
-
SLACompletionStatus †
-
SLADashboard †
* requires an OLAP cube.
† to be viewed in the Analysis Dashboard
Expand Home Page to learn more about the ActiveBatch reporting home page.

While deploying your reports using the ActiveBatch Reporting Manager, two folders are created; DataSources and Reports. The DataSources folder contains two data sources to link the reports to the reporting database and OLAP cube.
The Reports folder contains the SQL reports that you previously deployed. Look for the file “ActiveBatchReports_Home”. Clicking on this link allows you to obtain a nicely formatted and readable webpage.
In order to run a report, click on the report name. The report is generated based on default parameters that are a part of your OLAP database.
Expand the desired report to learn more about it.

The Daily Dashboard report provides an overall view of job and machine statistics from the past day. It shows hourly job counts, busiest machines, longest running jobs and SLA statistics. You can drill down to the underlying data by click on each chart and dial. The dashboard report shows data from one job scheduler only. If you have multiple job schedulers, you can expand the parameters area on the top and select a different job scheduler from the dropdown.
Daily Dashboard

These reports contain charts that display average job run times per each selected tag or machine. The chart contains date/time information on the x-axis and average job run time (in minutes) on the y-axis. Depending on the length of the selected date range, the chart can display hours, dates, months and years on the x-axis. If the date range is less than 3 days, the chart displays hourly information grouped by days as shown in the figure below.
Average Job Run Time by Tag (Hourly)
If a longer date range is selected, the time information disappears and only dates are displayed. If the date range is longer than 15 days, the dates are grouped into months to avoid clutter.
You can navigate between the charts of different tags or machines through the left and right arrows on the menu bar. A chart will not be created if the tag(s)/machine(s) specified do not contain any run-time information based on your parameter values.
Average Job Run Time by Tag (Monthly)
The AverageJobRunTime_byMachine_Chart report is very similar to AverageJobRunTime_byJobTag_Chart. The only difference is that the charts are created per execution machine. Therefore in this report the Execution Machine parameter does not have a default value, and you are required to choose machine(s) before running the report.

These reports are very similar to the ones discussed above (Average Job Run time). The only difference is that the charts in these reports display average job wait times instead of average run times. Similarly, the average wait times are displayed in minutes.

These reports contain lists and graphs that display the statistics and breakdown of Completed Jobs (Succeeded, Failed or Canceled) by Machines and Tags. The Execution Machine parameter is omitted in the CompletedJobBreakdown_byMachineStats report, since it shows the breakdown of statistics for each machine and uses all machines available in the reporting database. Similarly, the Tag parameter is omitted in the CompletedJobBreakdown_byTagStats report. In both reports, the Job Scheduler parameter does not have a default value, and the user is required to select job scheduler(s) before running the reports.
The reports consist of three (3) parts: a top graph (pie chart), a list of statistics for each Machine/Tag and a bottom graph that shows the number of Completed Jobs for each Machine/Tag. The top pie chart displays simplified information about the Success, Failure and Cancelation (Abort) percentages of the selected jobs. The list displays the breakdown of percentages by Machines/Tags. The list also displays the actual number of completed jobs, and statistics about job run times, wait times, disk I/O reads/writes and memory usage. The totals are also displayed at the bottom of the list. Finally the bottom graph displays a bar chart that displays the breakdown of the job state percentages by Machine/Tag. The bottom chart expands when more than five (5) machines/tags are available in the reporting database. On the other hand, it is not shown if only one machine/tag is available.
Completed job breakdown by machine

This report displays Completed Job statistics per day, grouped by week, month and year. Similar to the CompletedJobBreakdown_byMachineStats and CompletedJobBreakdown_byTagStats reports, it contains a pie chart that displays the percentages and a detailed list that breaks down the statistics. The Execution Machine parameter is required and must be entered to run the report.
The dates in this report form a hierarchy such as Year -> Month -> Week -> Day. The report is divided into months, so that individual pie charts and lists are created on separate pages for each month. You can navigate between the pages by using the left and right arrows on the menu bar. The list contains a hierarchy between weeks and days, so the list initially displays weekly statistical information. You can expand each week by clicking on the + sign to see the daily statistics.
Job breakdown by date
The last page of this report displays the overall statistics. A pie chart displays the Completion Status breakdown in percentages and a table that displays the actual numbers.
Job breakdown by date, last page

This report contains a single line chart that displays the change of Job Completion Status over time. Four (4) lines are displayed representing the count of canceled, failed, successful jobs and their totals. The actual numbers are also displayed on these same lines. The dates are displayed on the x-axis and the “count of completed jobs” are displayed on the y-axis. Similar to the AverageJobWaitTime_byJobTag_Chart report, the dates are grouped into Months and Years depending on the date interval that is selected by the user. The Execution Machine parameter is required and must be entered to run the report.
Completed job status breakdown

The EventAudis_Changes_List report displays a list of ActiveBatch objects (i.e. job templates, queues, user account objects etc) that have been changed within the provided date range. The list contains the full paths and names of the objects, along with the date/time of the audit, the audit message and its severity (i.e. Informational, Warning or Error). If you are interested in the objects under a certain Plan or Folder, you can filter the list by providing the full path of that Plan/Folder inside the BasePath parameter. Moreover, you can further filter the list by the object name, type, audit severity, tag and audit user.
The list can be sorted by column by clicking on the up and down arrows in the column headers.
EventAudits_Changes_List

The EventAudits_List report is very similar to EventAudits_Changes_List. It also shows a list of audits for the ActiveBatch objects. In addition to the EventAudits_Changes_List report, the EventAudits_List report shows differnet audit types such as queue connected or disconnected. Similarly you can filter the list of audits by the object name, type, audit severity, tag and audit user.
EventAudits_List

This report shows a chart to display the ActiveBatch objects with most event audits. You can adjust the number of objects to be displayed in the chart. For each object, a colored bar showing the audit severities is displayed along with the total number of event audits for that object.
EventAuditType_byObject_Chart

The EventAuditType_Chart reports displays a chart showing the number of event audits per audit message. The reporting database contains about 30 different audit messages that are logged by the job scheduler. The chart displays a bar for each audit message, also showing the number of messages.
EventAuditsType_Chart

The PlansJobs_List report shows a list of completed instances based on your selection of parameter values. The list displays statistics about the actual instances, not their aggregates. Therefore depending on your selections, the list can be lengthy. The instances are grouped into the Plans that they belong to. The plans are further grouped by Job Scheduler(s). The list can be condensed by contracting the instances that are not of interest. Clicking the + sign next to the Plan names (i.e. full paths to the instances) will hide all instances under that plan. Similarly, if you click the + sign next to the Job Scheduler name, all plans and instances under that Job Scheduler will be hidden. (Due a bug in Microsoft SQL Server Reporting Services (2005), the + sign represents “Expanded” and – sign represents “Condensed”.)
The list can be sorted by column by clicking on the up and down arrows in the column headers.
Plans and jobs list
In order to help you navigate through the list, a document map is displayed on the right. From this map, you can click on the Plan path to directly navigate to the instances under that plan. The Plan names in the document map are sorted alphabetically.

These two reports list the Top X jobs with the highest average run time and wait times, respectively. The number of jobs to be listed is a variable that can be set using the “Top Elements” parameter (the default value is 50.) For each Top X job, the list contains information about the Job Scheduler that the jobs were submitted from, full job path, the jobs average run time / wait time (in minutes) and total number of completed instances of the job. The jobs are sorted according to their average run times / wait times (by default), however, they can be sorted alphabetically by clicking on the up and down arrows in the job column header. If multiple Job Schedulers are selected, the document map on the right helps you navigate through the list by clicking on the names of the Job Schedulers.
Top plans and jobs by average run time

These reports display the Top X job instances by their Disk I/O (Reads and Writes), Memory usage, Run Times and Wait Times. Different than the reports discussed in the previous section, these reports show the actual values per instance, not their aggregates. The instances in these reports are grouped by the Plans that they are contained in. The Plans are grouped by Job Scheduler. The number of instances to be listed can be adjusted by using the “Top Elements” parameter (the default value is 50). The column that the report is sorted by is highlighted as bold; however the reports can be sorted by other columns by clicking on the up and down arrows in the column headers.
Top instances by disk I/O

The contents of this report are similar to the CompletedJobBreakdown_byMachineStats report, with one important difference, this report displays the Top X machines with the highest number of Completed Jobs (the default value is 50). This report sorts the machines by total number of Completed Jobs. You must enter one or more Job Schedulers to run this report.

These reports display the detailed statistics of Top X machines according to average job run time and average job wait times. Among these statistics, the reports display the number of jobs ran on each machine, their success/failure percentages, average disk I/O and average memory usage. A graph displaying the average job run/wait times per machine is located at the bottom of the report. Both the list and the graph are sorted according to the average job run/wait times. The list can also be sorted alphabetically by clicking on the up and down arrows in the Machine column header.
You must select at least one Job Scheduler(s) to run a report. By default, all execution machines are selected and the Top 50 machines are displayed. The number of machines to be displayed in the report can be modified with the “Top Elements” parameter, and the report displays the Top X machines among the ones selected in the “Execution Machine” parameter.
Top 50 machines by average job wait times

This report shows the Top X longest running jobs for each machine. The report contains a list of instance-based running times, not the aggregated values. In addition to the running time, the report also shows the exit code, wait time, memory usage, disk reads/writes for each job. In the report, the jobs are grouped into plans and the plans are further grouped into Job Schedulers. The averages are for each machine and are also displayed at the bottom of the list. By default, the Top 10 jobs are displayed for each machine. This value can be changed through the “Top Elements” parameter.
Top 10 longest running jobs per machine

This report shows average startup time (in minutes) of the virtual machines associated utilized by the managed queues. The report shows the startup times averaged in time for the selected managed queue. Also, depending on the selected date range, the X-axis shows hourly, daily or monthly averages.
Average Virtual Machine Startup Times

This report shows the instance statistics and SLA statuses of SLA plans and jobs. The report layout is similar to the All Plans / Jobs list. There are 4 different SLA statuses listed in the report: SLA Successful, SLA Failed, SLA Aborted and SLA Breached.
SLA Plans/Jobs List

This report displays two charts for a selected SLA plan or job. The first chart shows the overall success rate of the SLA plan / job in the given time frame. The second chart shows the breakdown of the SLA breaches for the plan / job as failed, aborted or simply breached (i.e. completed successfully)
SLA Completion Status

This report shows the selected SLA plan or job’s run and wait times over time. The X-axis displays the SLA batch start time, while the Y-axis shows the SLA batch’s run & wait times in minutes.
SLA Run & Wait Times