Data Federation Service Queries Test

The efficiency of the Data Federation Service can be measured by the quality of the queries the data federation administration tool helps build. By periodically checking the feedback returned by the data federation query engine, administrators can determine the number of queries that may have to be optimized before being executed. The Data Federation Service Queries test helps administrators perform this check at regular intervals. With the help of the metrics reported by this test, administrators can quickly figure out if there are any queries that are consuming disk space and memory resources. In addition, the test also measures the query load on the data federation query engine, reports the count of queries in various stages of processing, and thus indicates where most queries are spending time – in analysis? In optimization? In execution? This way, the test points to bottlenecks in query processing and the source of these bottlenecks.

Target of the test : A SAP BOBI Node

Agent deploying the test : An internal/remote agent

Outputs of the test : One set of results for the Dashboards cache server running in the node 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 BOBI listens.
JMX Remote Port	Specify the RMI port number of the BOBI monitoring application.To know the RMI port number of the monitoring application, refer to Enabling the Monitoring Application of the SAP BOBI Platform.
JNDI Name	Specify the lookup name for connecting to the JMX connector of the BOBI monitoring application. To know the JNDI name, refer to Enabling the Monitoring Application of the SAP BOBI Platform.
JMX User and JMX Password	Enter the credentials of an enterprise authenticated BOBI user belonging to the default monitoring users group.
Confirm Password	Confirm the password by retyping it here.
Node Name	Specify the name of the BOBI node being monitored.

Measurements made by the test
Measurement	Description	Measurement Unit	Interpretation
Number of running queries	Indicates the number of running queries.	Number	The value of this measure includes both memory-consuming and non-consuming queries.
Queries consuming memory	Indicates the number of queries consuming memory.	Number	A non-zero value for this measure indicates that one/more queries are consuming memory resources. Queries that are consuming memory excessively could be candidates for optimization. You may want to view the query plan of every query in the data federation administration tool to know how much memory each query is consuming, which operators are consuming maximum memory, and how the query can be restructured to consume less memory.
Queries using disk	Indicates the number of queries using disk space.	Number	A non-zero value for this measure indicates that one/more queries are consuming disk space. Queries that are consuming disk space excessively could be candidates for optimization.
Queries waiting for resources	Indicates the number of running queries currently waiting for execution.	Number
Failed queries	Indicates the number of queries that failed.	Number	Ideally, the value of this measure should be 0. A non-zero value could indicate that one/more queries have failed. You can use the Query Monitoring tab of the data federation administration tool to view the exception that caused the query to fail and to troubleshoot the failure.
Queries in query analyze step	Indicates the number of running queries currently in analyze step.	Number	If, at any given point in time, the number of queries being analyzed are way more than the count of queries being executed, it could mean that queries are spending too much time in the analysis step.
Queries in query optimization step	Indicates the number of running queries currently in optimization step.	Number	If, at any given point in time, the number of queries being optimized are way more than the count of queries being executed, it could mean that too many inefficient/unoptimized queries are running.
Queries in query exec step	Indicates the number of running queries currently in the execution step.	Number
Data output by query execution	Indicates the amount of data output by the executed queries.	MB
Data transferred from data sources	Indicates the amount of data read from data sources.	MB
Memory used by query execution	Indicates the total amount of memory used by running queries.	MB	A high value is indicative of high memory consumption by one/more queries. Queries that are consuming memory excessively could be candidates for optimization. You may want to view the query plan of every query in the data federation administration tool to know how much memory each query is consuming, which operators are consuming maximum memory, and how the query can be restructured to consume less memory.
Disk used by query execution	Indicates the total amount of disk space used by running queries.	MB	A high value is indicative of high disk space usage by one/more queries. Queries that are consuming disk space excessively could be candidates for optimization.
Memory used by cache	Indicates the amount of memory used for caching metadata, statistics and connectors configuration.	MB