BODS Jobs Executions Test

Jobs are key components of SAP Business Objects data service, The jobs can be configured to perform a number of specific tasks, but given that BODS is primarily a ETL tool, majority of jobs are ETL jobs which load the data from certain data store, transform and prepare it in a state that can be displayed through Business objects reports. Once the jobs are configured to carry out a specific tasks, these jobs can be executed manually, or can be configured to execute at given time or condition in an automated manner. The jobs can also be configured to execute at defined frequency and carry out the task. In typical business environments, a large number of jobs are configured to prepare the data for business critical reporting, if any of the jobs fail to execute, it can cause big impact on business. For smooth service to users, it is vital for all the jobs to execute successfully, with expected results and in timely manner. Given the criticality of jobs, and the impact of failure it is important to monitor execution of all jobs and fix any job which has failed before the business timelines are affected.

This test monitors Job execution and collect key metrics like number of jobs succeeded, failed, have errors and warnings, number of tests running etc. Administrators can use these metrics to get full picture of job execution and make sure that any failure is investigated and acted upon.

Target of the test : A SAP BODS Node

Agent deploying the test : An internal/remote agent

Outputs of the test : One set of result for the BODS node being monitored.

Configurable parameters for the test

Parameter	Description
Test period	How often should the test be executed.
Host	Host name of the server for which the test is to be configured.
Port	Enter the port to which the specified host listens. This should be the port at which the web application server hosting SAP BODS listens.
CMS System	URL of Central Management System.
Username & Password	Specify the credential of user created for BODs monitoring. The user should have been granted Monitoring role.
Confirm Password	Confirm the password by retyping it here.
Web Service Port	Specify the port at which BODS webservice is running.
Long Running Cut off	Specify the cutoff duration in seconds beyond which a job is considered a long running job.
Scan Period (HRS)	Specify the duration in hours within which eG agent should look for jobs that have started. By default this is set at 24 hours.
Detailed Diagnosis	To make diagnosis more efficient and accurate, the eG Enterprise embeds an optional detailed diagnostic capability. With this capability, the eG agents can be configured to run detailed, more elaborate tests as and when specific problems are detected. To enable the detailed diagnosis capability of this test for a particular server, choose the On option. To disable the capability, click on the Off option. The option to selectively enable/disable the detailed diagnosis capability will be available only if the following conditions are fulfilled: The eG manager license should allow the detailed diagnosis capability Both the normal and abnormal frequencies configured for the detailed diagnosis measures should not be 0.

Measurements made by the test

Measurement	Description	Measurement Unit	Interpretation
Succeeded	Indicates the number of successful executions of the job in the last measurement period.	Number	Detailed diagnosis provides of this measure details about these job executions such as Run ID, Time stamp, Execution time in seconds and Job server used.
Errors	Indicates the number of failed job executions in the last measurement period.	Number	Detailed diagnosis of this measure provides details about these job executions such as Run ID,Time stamp, Execution time in seconds, Job server used and Error log contents.
Recovered	Indicates the number of recovered job executions of the job in the last measurement period.	Number	Detailed diagnosis of this measure provides details about these job executions such as Run ID, Time stamp, Execution time in seconds and Job server used.
Running	Indicates the number of instances of the job that are currently running successfully.	Number	Ideally the jobs should complete within a short period of time, so there should be small number of running job at any given time.
Warnings	Indicates the number of instances of the job that are currently running with warnings.	Number	Administrators should investigate the warnings and make sure to remove them, so as to avoid any future issue,
Maximum recent execution time	Indicates the maximum time taken among all the job executions that ended in the last measure period.	Seconds	It is important for administrators to know which job is taking most time. If time is increasing over repeated measurements, there could be an issues with particular job.