Lumira Server Status Test

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 with Lumira 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 Lumira Server Status Test 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.

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 Lumira 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.
Monitoring Hosts	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.
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.
Provider	This 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.
Timeout	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 1000 seconds.
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
Health state	Indicates the current health state of the Lumira server in the monitored node.		The values that this measure can report and their corresponding numeric values are discussed in the table below: Measure Value Numeric Value Failed 0 Danger 1 Caution 2 Healthy 3 Disabled 4 Note: By default, this measure reports the Measure Values listed in the table above to indicate the health state of the server. In the graph of this measure however, the same is represented using the numeric values only.
Server running state	Indicates the current running state of the Lumira server.		The values that this measure can report and their corresponding numeric values are discussed in the table below: Measure Value Numeric Value STOPPED 0 STARTING 1 INITIALIZING 2 RUNNING 3 STOPPING 4 FAILED 5 RUNNING_WITH_ERRORS 6 RUNNING_WITH_WARNINGS 7 If the server is not healthy, the detailed diagnosis of this measure, if enabled, provides the process ID of the server. Note: By default, this measure reports the Measure Values listed in the table above to indicate the running state of the server. In the graph of this measure however, the same is represented using the numeric values only.
Server enabled state	Indicates whether/not the Lumira server is enabled.		The values that this measure can report and their corresponding numeric values are discussed in the table below: Measure Value Numeric Value Disabled 0 Enabled 1 Note: By default, this measure reports the Measure Values listed in the table above to indicate whether/not the server is enabled. In the graph of this measure however, the same is represented using the numeric values only.
Busy server threads	Indicates the number of server threads that are currently servicing requests.	Number	If this measure reaches the configured maximum thread pool size for the server, new requests to the server would have to wait until a server thread becomes free. If this happens often, it may significantly slowdown request processing by the server. In such a situation, you may want to consider resizing the thread pool.