BODS Data FlowsTest
Data flows are a core concept within BODS and play a crucial role in defining the ETL processes. A data flow is a logical representation of the flow of data within BODS. It consists of a series of data objects and transformations that describe how data moves from source to target. Data flows can be complex, involving multiple data sources and transformations. Once a data flow is defined, it can be executed to move and transform data from source to target. BODS provides scheduling and monitoring capabilities to manage and automate data flow execution. BODS offers comprehensive monitoring and logging capabilities, allowing you to track the progress of data flows, troubleshoot issues, and analyze performance.
This test monitors the data flows and collect key metrics like number of flows, average duration, average rows processed, buffer used etc. Administrators can use these metrics to get a full picture of data flows and make sure that data flows are executing optimally.
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.
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 |
Specify the 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. |
Max Execution Time |
Specify the cutoff duration in seconds. Only data flows with execution time greater than this cutoff period in seconds are monitored by this test (unless specified explicitly using the ‘include data flows’ parameter). |
Include Data Flows |
Specify the comma separated list of data flows which you always want to monitor even if they are not executing for below max execution time threshold. |
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:
|
Measurement |
Description |
Measurement Unit |
Interpretation |
---|---|---|---|
Flows |
Indicates the number of executions of the data flow in the last measure period. |
Number |
|
Average duration |
Indicates the average time taken for execution of this data flow in the last measure period. |
Seconds |
Slowness in data flow execution could be due to various reasons such as inefficient flow design, processing inefficiencies, delays at the database etc., Various means to combat this include using push downs, increasing the degree of parallelism, optimizing the flow design etc., Detailed diagnosis for this measure outlines details for these flows such as job ID, thread, CPU utilization, Job server, Timestamps, Elapsed time etc., for each of the processing threads. |
Average rows processed |
Indicates the average number of rows processed through the object. |
Number |
|
Average buffers used |
Indicates the average output buffer size used in the last measure period. |
KB |
|
Buffers used percent |
Indicates the percentage of instances of the job that are currently running with warnings. |
Percentage |
|
Average CPU utilization |
Indicates the average CPU utilization per thread for this data flow in the last measure period. |
Percentage |
|