Default Parameters for BobiLSStTest

SAP Lumira is a self-service data discovery and visualization tool that allows users to find and analyze relevant business data and create custom interactive dashboards and analytics applications. SAP Lumira provides connectivity to SAP enterprise data models in SAP BW, SAP HANA, and SAP BusinessObjects universes (UNX) as well as to a wide variety of 3rd party databases and file data, for data acquisition, cleansing and manipulation.

To visualize data and enable interactivity, SAP Lumira provides powerful UI elements such as charts, crosstabs, geo maps and filter components out of the box, along with a rich set of ready-to-run analysis applications, templates, and samples. Both self-service dashboards and tailored, centrally (IT) managed applications are built from the same libraries of UI elements and the same data connections and sources, to provide a uniform and consistent experience for business end users.

SAP Lumira Discovery is the rich client for business key users who need a flexible tool to connect to data sources, acquire, manipulate, and merge data, to work offline with data, to explore and analyze data online, and to create stories with visualizations from all types of data in an ad-hoc fashion. SAP Lumira Designer is the rich client for professional analysis application designers (typically working in IT departments) to create corporate analysis applications and reports. Lumira Designer provides the same UI elements as Lumira Discovery and more, and allows full control of the application look and feel and user interaction through scripting and corporate CSS style sheets. Lumira Designer also enables the creation of shared UI elements (such as headers, footers, toolbars) and the breaking down of complex applications into smaller, more manageable parts, which enable cost-effective management of large corporate BI deployments.

SAP Lumira Server is installed on the SAP BusinessObjects BI platform and hosts the execution runtime of Lumira documents that are created from Lumira Discovery and Lumira Designer, as well as analysis applications created withLumira Designer or Design Studio.

If the Lumira Server is not running or is experiencing errors or is disabled, then critical data cannot be queried from storage and custom reports cannot be built. Likewise, if the Lumira Server is not sized with adequate threads, slowdowns in query processing become inevitable. To avoid this, administrators must be promptly alerted when a Lumira Server suddenly stops functioning or is about to run out of free threads. This is exactly what the BobiLSStTest does. This test tracks the overall health and status of the Lumira Server and notifies administrators if the server has stopped, has encountered errors, or is disabled. In addition, the test also monitors the thread pool usage of the server and proactively alerts administrators if the pool is over-utilized.

This page depicts the default parameters that need to be configured for the BobiLSStTest.

• The TEST PERIOD list box helps the user to decide how often this test needs to be executed.

• In large SAP environments, SAP BOBI installations can have several BI platform server hosts working together in a cluster. A node is a collection of BI platform servers running on the same host and managed by the same Server Intelligence Agent (SIA). One or more nodes can be on a single host. An Adapative Processing Server hosts a lot of BI services and processes non-Object/post processing requests. Multiple APSes may be defined on multiple nodes within a deployment. A single APS acts a primary server to process requests pertaining to the services hosted by the APS from the target SAP BOBI. In some environments, eG Enterprise failed to collect metrics from the target BOBI continuously. This was because, when the APSes failed over, the APS that was acting as a primary server corresponded to a different BOBI node and the eG agent failed to establish connection with the APS that was currently processing the service requests. To ensure that the metrics are collected seamlessly from the target BOBI, the eG agent should be equipped with the IP addresses of the target BOBI node as well as the IP addresses of all the Adaptive Processing Servers associated with the target BOBI node. For this purpose, specify a comma-separated list of IP addresses corresponding to the APSes in the MONITORING HOSTS text box.

• Specify the RMI port number of the BOBI monitoring application in the JMX REMOTE PORT text box.To know the RMI port number of the monitoring application, refer to Enabling the Monitoring Application of the SAP BOBI Platform.

• Specify the lookup name for connecting to the JMX connector of the BOBI monitoring application in the JNDI NAME. To know the JNDI name, refer to Enabling the Monitoring Application of the SAP BOBI Platform.

• Enter the credentials of an enterprise authenticated BOBI user belonging to the default monitoring users group in the JMX USER and JMX PASSWORD textboxes.

• Confirm the PASSWORD by retyping it in the CONFIRM PASSWORD text box.

• Specify the name of the BOBI node being monitored in the NODE NAME textbox.

• PROVIDER parameter appears only if the Mode is set to JMX. This test uses a JMX Provider to access the MBean attributes of the target Java application and collect metrics. Specify the package name of this JMX Provider in the PROVIDER textbox. By default, this parameter is set to default indicating that this test automatically discovers the JMX provider and report metrics.

• Specify the maximum duration (in seconds) for which the test will wait for a response from the server in the TIMEOUT textbox. The default TIMEOUT period is 30 seconds.

• Once the necessary values have been provided, clicking on the UPDATE button will register the changes made.

When changing default configurations of tests, the values with “$” indicate variables that will be replaced by the eG system according to the specific server being managed - for instance, $hostName is the host/nickname of the target host, $port is the port number of the server being monitored. E.g., for a server xyz:80, $hostName will be changed automatically by the eG manager to “xyz*” and $port will be changed to “80” when configuring a test.