BW Templates Test

A Web template is the keystone of a Web application and contains placeholders for Web items, data providers and commands. For the Web application, the place holder is filled during runtime and Web items, data providers and commands are generated.

In the Web template, you determine from which data provider and in what way (Web items) the BI data is displayed. You also determine which additional operations are possible (commands). When a request is sent from a Web application to the application server for ABAP, a Template object is generated from which the structure of the requested XHTML page is derived.

If the web templates do not execute faster or if the queries executing on the templates fail, then the data could not be retrieved and generated for the target SAP Business Business Warehouse instance. To proactively figure out the templates that are taking too long to execute, administrators can use the BW Templates test.

This test auto-discovers the templates created on the target SAP Business Warehouse instance and for each template, this test reports the number of sessions that initiated the template. In additions, this test reports the number of times each template was executed and the time taken by each template for execution. Using this test, administrators can figure out the template that is the slowest to execute. The detailed diagnostics of this test provides in depth insights into the exact query / execution that was the reason behind the templates being slow to execute.

Target of the test : A SAP Business Warehouse Instance

Agent deploying the test : An internal agent

Outputs of the test : One set of results for each template created on the target SAP Business Warehouse Instance 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 at which the specified host listens.
ClientName	Specify the ID of the client system as what the eG agent will be connecting to the SAP ABAP instance. To know how to determine the client ID to use, follow the instructions provided in Determining the Client ID/Name for the eG Agent to Connect to the SAP ABAP Instance.
SAPUser	Typically, to connect to a SAP ABAP instance and run tests, the eG agent requires the permissions of a SAP user who has been assigned with certain authorization objects. Ideally, you will have to create a new user role on the SAP ABAP instance for this purpose, associate the above-mentioned authorization objects with that role, and assign the new role to an existing SAP user. The procedure for the same has been provided in Creating a New User Role for Monitoring and Assigning it to a SAP User. Once the new role is assigned to a SAP user, specify the name of this user against SAPUser.
Password	The password of the specified SAPUser.
Confirm Password	Confirm the password by retyping it here.
SysNo	An indicator of the TCP/IP port at which the SAP server listens. For example, for a server that listens at port 3200, the SysNo will be ‘00’. Similarly, if the SAP server port is 3201, the SysNo will have to be specified as ‘01’. Therefore, in the SysNo text box specify the system number of the SAP server with which the specified client communicates. To know the system number for the ABAP server being monitored, follow the procedure detailed in Identifying the SAP Router String and System Number.
Router	If the SAP client with the specified ClientName exists in a network external to the SAP server, then a router will be used to enable the server-client communication. In such a case, specify the router string of the router in the Router text box. If both the client and the server exist in the same network, then specify ‘none’ against the Router text box. To know what is the SAP Router string for the ABAP server being monitored, follow the procedure detailed in Identifying the SAP Router String and System Number.
InstanceName	This is set to default by default. This implies that the eG agent automatically discovers the instance name at run time.
Timeout	Indicate the duration (in seconds) for which this test should wait for a response from the SAP Business Wwarehouse Instance. By default, this is set to 120 seconds.
JCO Version	The eG agent uses the SAP JCO library to connect to the SAP ABAP system and pull out metrics. To enable the eG agent to make this connection and query the metrics, you need to specify the version of the SAP JCO library that the agent needs to use. For instance, to instruct the eG agent to use JCO v2.1.19, it would suffice if you specify the ‘major version number’ alone against JCO Version – in the case of this example, this will be 2.x. Note that if you have downloaded the SAP JCO CONNECTOR files for SAP JCO version 3 from the SAP market place (as instructed by Downloading the SAP JCO Connector files Required for Monitoring ), then the JCO Version configuration should be 3.x.
Event Window	By default, the BW events related to BW objects such as queries, templates and workbooks will be stored in an event table within the target SAP Business Warehouse Instance. An event record may be logged in the event table upon execution of the query on the template either immediately or with a time delay. When the event record is logged with a time delay, eG Enterprise may sometimes miss the event completely from the scope of monitoring. This is because, the event record will display the time stamp at which the event was logged rather than the time stamp at which the event actually started. To ensure that all the events related to the template are monitored, administrators can use the Event Window parameter. By default, this is set to 90 minutes indicating that the eG agent will look for the event records in the last 90 minutes and fetch the relevant metrics. This will ensure that the events related to the templates are monitored round the clock without a miss!
DD Frequency	Refers to the frequency with which detailed diagnosis measures are to be generated for this test. The default is 1:1. This indicates that, by default, detailed measures will be generated every time this test runs, and also every time the test detects a problem. You can modify this frequency, if you so desire. Also, if you intend to disable the detailed diagnosis capability for this test, you can do so by specifying none against DD frequency.
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
Sessions	Indicates the number of sessions in which this template was initiated during the last measurement period.	Number	A high value for this measure is a indication that the template is on high demand. This may in turn cause the template to load slower than usual.
Steps	Indicates the number of steps that were executed from this template during the last measurement period.	Number	A high value for this measure may result in the slowness of the template.
Executions	Indicates the number of times this template was executed during the last measurement period.	Number	This measure is a good indicator of load on the SAP Business Warehouse Instance. Compare the value of this measure across templates to figure out the template that is executed more frequently.
Execution rate	Indicates rate at which this template was executed during the last measurement period.	Execution/min
Response time	Indicates time taken by this template to complete an execution.	Seconds/execution	Compare the value of this measure across templates to figure out the template that is the slowest in terms of execution. Use the detailed diagnosis of this measure to figure out the executions that were the slowest for each template. The detailed diagnosis of this measure lists the name of the user, Start time, Info provider, Response time, Load time, Query time, Web item rendering time, Web reporting time, Closing time, Queries, OLAP time, Data manager time, Number of web items, Session ID, Step ID, Handle ID and Object properties.
Load time	Indicates the time taken to load this template upon an execution.	Seconds/execution	A low value indicates that the template is loading faster. Compare the value of this measure across templates to figure out the template that is the slowest to load upon execution.
Web item rendering time	Indicates the average time taken to generate the output upon execution of this template during the last measurement period.	Seconds/execution
Web reporting time	Indicates the average time taken by this template to generate the report upon execution.	Seconds/execution
Closing time	Indicates the average time taken by this template to close per execution.	Seconds/execution
Web reporting items	Indicates the number of items that were generated as a report upon execution of this template.	Items/execution
Queries	Indicates the number of queries raised to this template per execution.	Queries/execution
Query time	Indicates the time taken by the queries on this template for execution.	Seconds/execution	Use the detailed diagnosis of this measure to figure out the queries that are the slowest to execute on each template. For each template, the detailed diagnosis of this measure lists the name of the query, user executing the query, Info provider, Start time, Selected records, Transported records, Response time, OLAP time, OLAP cache time, Data manager time, OLAP authorization time, OLAP input help time, OLAP services time, Query Generation time, Data read time, Data selection time, Front end data transfer time, Read texts time, Badi compute time, Other events time, Properties, Session ID, Step ID and HandleID.
OLAP time	Indicates the Online Analytical processing time taken per execution by this template.	Seconds/execution
Data manager time	Indicates the time taken by this template to query the data manager package for data upon execution.	Seconds/execution

The detailed diagnosis of the Response time measure lists the name of the user, Start time, Info provider, Response time, Load time, Query time, Web item rendering time, Web reporting time, Closing time, Queries, OLAP time, Data manager time, Number of web items, Session ID, Step ID, Handle ID and Object properties. This helps to figure out the top executions that were the slowest for each template.

Figure 1 : The detailed diagnosis of the Response time measure