Web Dashboard User Guide. Functional Area: Web Dashboard. Geneos Release: v4.6. Document Version: v1.0.0

Transcription

1 Web Dashboard User Guide Functional Area: Web Dashboard Geneos Release: v4.6 Document Version: v1.0.0 Date Published: 16 March 2018

2 Copyright ITRS Group Ltd. All rights reserved. Information in this document is subject to change without notice. The software described in this document is furnished under a license agreement or nondisclosure agreement. The software may be used or copied only in accordance with the terms of those agreements. No part of this publication may be reproduced, stored in a retrieval system, or transmitted in any form or any means electronic or mechanical, including photocopying and recording for any purpose other than the purchaser's personal use without the written permission of ITRS Group Ltd. ITRS Group Ltd 6th Floor, The Bonhill Building, 15 Bonhill Street, London, EC2A 4DN, UK t: +44 (0) f: +44 (0)

3 Web Dashboard Introduction Geneos Web Dashboard is a client/server web application that allows Active Dashboards to be published and viewed over the web. Existing Active Dashboards can be deployed to a centralised location and viewed remotely without requiring the installation of Active Console. With Web Dashboard, you are able to: Deploy a dashboard previously created in AC2 inside a web server. Access that dashboard from the web browser and see updates coming from Geneos. Navigate around and monitor multiple dashboards from the same web server. Access and execute data item commands for which the user has permission. Access external web pages if such links are defined within the dashboard contents. The following diagram describes the application: The server side deploys dashboards created with Active Console and renders them suitable to be seen through a web browser. It also establishes connections to Geneos Gateways to feed Geneos data to dashboards. The client side communicates with the server to display and interact with deployed dashboards in a web browser. Page 3 of 40

4 User Interface The user interface is accessed using a web browser. There are two main sections that can be accessed via the following URLs: Display and navigation of dashboards and slideshows: Configuration of connections, dashboards and slideshows: Page 4 of 40

5 Dashboard Navigation This user interface allows the navigation through the dashboards that have been uploaded in Web Dashboard and have been configured to appear in the navigation tree. The navigation tree also allows viewing the slideshows if they have been configured. The following picture shows the navigation page. Page 5 of 40

6 Dashboard Configuration This user interface is required to add/remove dashboards in Web Dashboard, configure the navigation tree, and define slideshows and connections. The following picture shows the configuration pages. System Requirements Web Dashboard is a 64-bit application on Linux and a 32-bit application on Solaris, with the following system requirements: CPU: Multicore Intel / AMD / SPARC RAM: 4GB Network: 1 Network Interface Card Disk: 500 MB available space Please refer to the Geneos Compatibility Matrix for the list of supported platforms and web browsers. Note: Other OS distributions may work with the correct libraries installed but are not officially supported. For x86-64 distributions, the required 32-bit libraries must be available on the system. Also, other web browsers may work but are not officially supported. Page 6 of 40

7 Installing Web Dashboard Retrieve the Web Dashboard binary from the Client area of the ITRS website. Extract the binary to a writable location in the host. This will become the installation directory. Start Web Dashboard. See Starting Web Dashboard for different run options. Take note of the host name or IP address of the server hosting Web Dashboard and the port number since these are applied in the URL used to access it. The default port number is If required, edit the GWS_PORT variable in either run or geneosws startup script to change the port number. Upgrading Web Dashboard Note: The steps below are for Web Dashboard users upgrading from versions 3.0.x. Make sure that Web Dashboard is not running. Extract the new Web Dashboard binary to a new folder. Copy config.xml and the.adb files from the old Web Dashboard directory into the new <web_dashboard_install_dir>/config and <web_dashboard_install_ dir>/dashboards/uploaded directories respectively. Edit config.xml and make sure that the paths defined for each dashboard item are pointing correctly to the new Web Dashboard directory. <dashboards> <dashboard name="sampledashboard" path="<web_dashboard_install_dir>/- dashboards/uploaded/sampledashboard.adb"/> </dashboards> Start Web Dashboard. Page 7 of 40

8 Starting Web Dashboard The first time Web Dashboard is started: The minimal template file config.xml.min.tmpl is automatically renamed to config.xml and used as minimal configuration by the server. A Logs folder is created in the installation directory with the file WebDashboard.log.{date}. Running Start Scripts Note: JRE 1.8.0_xxx 64-bit is required, specifically 1.8.0_144 being the tested version. For binaries packaged without JRE, JAVA_HOME environment variable should be set on the machine. There are two scripts in the installation directory to start Web Dashboard: run - starts Web Dashboard in the foreground and produces a standard output as well as a log file. This is the default mode, and the script can be run in all supported operating systems../run geneosws - starts Web Dashboard in the background as a service with the output sent to a log file. This script can only be run in Linux Redhat or CentOS operating systems. The following additional configuration must be done in order for the script to work: 1. Copy the geneosws script into the system s /etc/init.d directory. 2. Set the appropriate run level. For example, in CentOS, it is: chkconfig --level 345 geneosws on 3. Specify the user that will start the service by editing the USERNAME variable. This user must have administrative authorization to run the service. 4. Change the base directory by editing the SCRIPTPATH variable from. to the installation directory. By default, the geneosws script assumes that the base directory is the current directory. Page 8 of 40

9 The following commands are supported:./geneosws {start stop status try-restart restart force-reload reload} start - launches web server in the background stop - kills web server process status - checks if web server is running reload/restart/force-reload/try-restart - restarts web server process Enabling Authentication Note: Always clear browser cache and cookies when switching between authenticated and unauthenticated versions of Web Dashboard. Note: Single Sign On (SSO) must be disabled when enabling Authentication 1. Go to <web_dashboard_install_dir>/config directory. 2. Edit security.xml. Comment out: <intercept-url pattern="/**" access="permitall" /> Note: In XML documents, follow this syntax to comment out: "<!--Comment String Here-->" and uncomment the following: <intercept-url pattern="/**" access="isauthenticated()" /> <authentication-provider> <password-encoder hash="bcrypt"/> <user-service properties="file:./config/users.properties"/> </authentication-provider> 3. Edit users.properties. Follow the syntax indicated in the file to add users. To generate an encrypted password, run the following command at the <web_dashboard_install_dir> directory: Page 9 of 40

10 java -cp 'lib/*:lib/geneos-bcrypt-hasher.jar' com.itrsgroup.login.auth.bcryptpasswordhasher <password to encrypt> Enabling SSO Note: Authentication must be disabled when enabling SSO If Single-Sign-On (SSO) is enabled, the SSO Agent verifies the user permission. After the verification of user credentials, the Web Dashboard checks the user's group to grant the appropriate access. When the user logs in for the first time, the browser will automatically save the user's credentials in the cache. Clear the browser cache to change the current user. Go to your <web_dashboard_install_dir>/config directory Edit sso.properties Property sso.agent.url webdashboard.url dashboard.user.groups config.user.groups sso.enabled sso.pubkey Description SSO Agent URL and port Web Dashboard URL and port Comma-separated values that define the user groups that are allowed to access the Dashboards and Slideshows sections of Web Dashboard Comma-separated values that define the user groups that are allowed to access the Config section of Web Dashboard Determines whether SSO is enabled (true) or disabled (false) File where the public key for SSO Agent is located The public key is generated by the SSO Agent and must be in PEM format, with lines no longer thatn 76 characters. For example: -----BEGIN PUBLIC KEY---- MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA9KTR6IFL44UTGCs5Hi2x fiso7embaqf75bqym/e8woqe2noocyavshglaae9ohp4vqrnc+hhyds7ddf2u0vf cyp6r4uise+huka+wkjfszzfob5lfyzzfb7hrgvc5kmzevg7qybej/c37usb9r1/ T4yao3SAdHGEwlthTKf0V+TtDGvlWPKGzVdCYowmNC0Z1RxsT/X3jhNvnkHRQYXW hwgieku1+u7bgtlpzd/3ufqnzsoimfme9r53b+wjron04b6obb0jqmwftyaoxwh2 ozbk5xz1e165hanxaykec4rchdu8m0urk8jkkrby9m8uxxcatbvrtygosoi9jh+t 1wIDAQAB -----END PUBLIC KEY----- Page 10 of 40

11 Enabling SSL Here are the steps to enable SSL in Web Dashboard: Configure SSL Certificates A script called ssl_util.sh exists in the installation directory which is used to generate or import a certificate. The script needs to be updated first as per instruction written inside it before doing any of the configuration below and running it. There are two ways to configure an SSL certificate on the server: 1. Generate a new self-signed certificate Run./ssl_util.sh from <web_dashboard_install_dir> directory and specify the host name or IP address of the box. This will generate the certificate and add it to a keystore. cd <web_dashboard_install_dir>./ssl_util.sh add <hostname_or_ip> 2. Import an existing certificate for your domain name If the server running Web Dashboard has an existing SSL certificate issued by a Certificate Authority (CA), you will need to import that certificate and its private key into the server s keystore. Convert your existing certificate and private key into PKCS12 format. Your certificate file needs to be called <hostname_or_ip>.cer. cd <web_dashboard_install_dir>./ssl_util.sh convert <hostname_or_ip> <private_key_file> 3. If your CA provides multiple intermediary certificates, you will need to combine them into a single file using the command: cat my_cert.cer intermediate1.cer intermediate2.cer > hostname_or_ip.cer 4. Import the newly converted certificate using the command and specify the Export Password from step 1../ssl_util.sh import <hostname_or_ip> <export_password> Page 11 of 40

12 Edit config files Edit <web_dashboard_install_dir>/config/security.properties. If changes were made to the value of KEYSTORE and PASSWD in ssl_util.sh, update the values of the properties below as per changes made. keystore=config/keystore.db truststore=config/keystore.db keystorepassword=ab987c truststorepassword=ab987c To change the port number to use for secure connection, update the property below. port=7443 Edit scripts Edit the run or geneosws script depending on the start-up mode to use. Uncomment this line: #ENABLE_SSL="-ssl true" Restart Web Dashboard Restart your Web Dashboard server and verify that the certificate is being used by opening the following page: If you generated a self-signed SSL certificate, the browser will warn you that the certificate is not trusted - this is expected behavior. Add an exclusion rule (or continue). Configuring Web Dashboard Type the host and the port of Web Dashboard in the web browser to access the configuration page in the following format: Example: Page 12 of 40

13 Adding Active Dashboards Dashboards need to be created in Active Console and exported as.adb files before they can be added to Web Dashboard. The deployment of dashboards into Web Dashboard takes place in 3 steps: Connecting to gateways 1. Click on the Add Connection button to add a new gateway connection. 2. Edit the gateway connection fields. If connecting to a secure gateway, tick the Secure checkbox. 3. Click on the Save button for Web Dashboard to establish the new gateway connection and add it to config.xml. Page 13 of 40

14 Gateway connections in config.xml Each connection is defined by a <gatewayconnection> element with a name attribute. The connection has the following properties: Property Mandatory Description <enabled> <primary> <secondary> <secure> <description> <sslenabled> <user> <password> Example: Yes Yes No No No No No No Determines whether a connection is enabled (true) or disabled (false) Contains the primary gateway s host and port number defined in <host> and <port> Contains the secondary gateway s host and port number defined in <host> and <port> Determines whether a connection is secure (true) or insecure (false) The gateway s description Determines whether a connection will use SSL connection (true) or normal authentication (false). When this is + enabled, the user property becomes mandatory and the password is no longer used. Username to access the gateway Password to access the gateway. The password has an attribute called type which could have the values encrypted or plain. This attribute is used to determine if the password is encrypted or not. By default, the type is encrypted if the gateway connection has been entered through the configuration interface. <geneoswebserver> <gatewayconnections> <gatewayconnection name="gateway1"> Page 14 of 40

15 <enabled>true</enabled> <primary> <host>gateway1a-host</host> <port>30001</port> </primary> <secondary> <host>gateway1b-host</host> <port>30002</port> </secondary> <description>gateway One</description> <user>user1</user> <password type="encrypted">aabbzzyyzz</password> </gatewayconnection> <gatewayconnection name="gateway3"> <enabled>true</enabled> <secure>true</secure> <primary> <host>localhost</host> <port>80003</port> </primary> <secondary> <host/> <port>0</port> </secondary> <description>gateway Three</description> <user>admin</user> <password type="plain">myplainpassword</password> </gatewayconnection> <gatewayconnectionname="gateway2"> <enabled>true</enabled> <secure>true</secure> <primary> <host>gateway2a-host</host> <port>80004</port> </primary> <secondary> <host/> <port>0</port> </secondary><description>gateway Two</description> <sslenabled>admin</sslenabled> <user>admin</user> <passwordtype="plain"></password> Page 15 of 40

16 </gatewayconnection> </gatewayconnections> </geneoswebserver> SSL Certificate Authentication In addition to password authentication, a secure connection to a gateway can be established using an SSL Certificate. This authentication method can be enabled by ticking the SSL column of a gateway in the connections configuration page or by setting the gateway's sslenabled property to true. An SSL certificate/key pair needs to be added to the keystore and aliased 'geneosauthentication' before the Web Server is started. Generating an SSL Certificate and Private key pair To generate a public certificate and private key for Web Dashboard, see the examples in Secure Communications. The process is the same as when generating a certificate and private key for the Gateway or Netprobe. The certificate for Web Dashboard should be named geneosauthentication.cer and should be generated by the same Certificate Authority as the certificate issued for every Gateway Web Dashboard will connect to. Page 16 of 40

17 Adding a Certificate and Private Key to the keystore 1. Edit <web_dashboard_install_dir>/ssl_utl.sh and change the value of KEYSTORE to point to the desired keystore file. The keystore password can be changed by modifying the value of PASSWD. KEYSTORE=${WEB_DASHBOARD_CONFIG_DIR}/keystore.db 2. Convert your existing certificate and private key into PKCS12 format. The certificate needs to be called geneosauthentication.cer. cd <web_dashboard_install_dir> /ssl_util.sh convert geneosauthentication <private_key_file> 3. The converted certificate needs to be imported to the keystore using the password specified when the certificate was converted../ssl_util.sh import geneosauthentication <password> 4. if KEYSTORE or PASSWD have been changed in <web_dashboard_install_dir>/ssl_utl.sh then edit <web_dashboard_install_dir>/config/security.properties and update the values of the properties below accordingly: Page 17 of 40

18 keystore=config/keystore.db truststore=config/keystore.db keystorepassword=ab987c truststorepassword=ab987c Uploading.adb files 1. Select Dashboards from the left-hand navigation list in order to deploy a dashboard. 2. Click on the Add Dashboard button. This shows the Dashboard dialog. In the dialog, type a name for the dashboard. Note: Do not add URL character codes (e.g., %20, %5C ) in the dashboard name. 1. Click on the Browse button to locate the.adb file to upload. 2. Click on the Upload button to make a copy of the.adb file in the dashboard folder. 3. Click on the Save button for Web Dashboard to add the new dashboard to config.xml. Page 18 of 40

19 Uploaded dashboards in config.xml Dashboard information is contained in the <dashboard> element in config.xml with the following attributes: Attribute name path Description The name given to the dashboard The location where the.adb file used by the dashboard is contained By default, the path is installation_ directory/dashboards/uploaded folder if the dashboard has been uploaded using the configuration interface. Optionally, a user may allocate another path that contains the.adb file. Example: <geneoswebserver> <dashboards> <dashboard name="dashboard1" pathh="/path/to/dashboards/uploaded/dashboard1.adb"/> <dashboard name="dashboard2" path="/path/to/dashboards/uploaded/dashboard2.adb"/> <dashboard name="dashboard3" pathh="/path/to/dashboards/uploaded/dashboard3.adb"/> </dashboard> </dashboards> </geneoswebserver> Changing the default dashboards upload folder To change the default dashboard upload folder, edit the run script and a new parameter - Dcom.itrsgroup.dashboard.dir that has the value of the chosen folder the dashboard files will be uploaded. -Dcom.itrsgroup.dashboard.dir=<PATH TO DASHBOARDS UPLOADS FOLDER> For users who have as existing setup and would want to change their dashboard upload folder, the following steps have to be done: 1. Manually update the dashboard paths in the config.xml file to point to the new dashboard upload folder. Page 19 of 40

20 2. Copy all the dashboards (.adb) files from the old upload folder to the new one. Remember to do the 2 steps when setting a new upload folder from an existing setup. Doing only step 2 will cause the dashboards copied to the new upload folder to be deleted. Configuring the navigation tree Select Navigation from the left-hand navigation list in order to organize the tree of dashboards for viewing. 1. Select Dashboards which is the top of the tree. 2. Click on the Add Group button to add a group. This shows a dialog with a single field to type the name of the new group. 3. Select a group and click on the Add Dashboard button to add a dashboard in the group. This shows a dialog with a dropdown menu of dashboards that have been uploaded by Web Dashboard. Page 20 of 40

21 4. Typing in the first characters of a dashboard name filters the dropdown menu to the dashboard names that start with those characters. Continue creating new groups which can be populated with selected dashboards. A hierarchical order can be defined in the navigation tree by creating groups under groups. Page 21 of 40

22 Click on the Save button to save the configuration of the navigation tree in config.xml. Click on the Dashboard tab to check how the navigation will be seen by users. Page 22 of 40

23 Navigation tree in config.xml The navigation tree is defined under the <tree> element with the following properties: Property Mandatory? Attribute Description <group> No name A group contains one or more dashboards and could also contain another group. <dashboard> No name A dashboard is part of a group Example: <geneoswebserver> <tree> <group name="group 1"> <dashboard name="dashboard1a"/> <dashboard name="dashboard1b"/> </group> <group name="group 2"> <dashboard name="dashboard2a"/> <dashboard name="dashboard2b"/> <dashboard name="dashboard2ac"/> <group name="group 2.1"> <dashboard name="dashboard2.1a"/> <dashboard name="dashboard2.1b"/> </group> </group> <group name="group 3"> <dashboard name="dashboard3a"/> <dashboard name="dashboard3b"/> </group> </tree> </geneoswebserver> Defining slideshows Slideshows can be defined to view a set of dashboards or all dashboards, one after another at specified time intervals. Select Slideshows from the left-hand navigation list in order to define a slideshow. Web Dashboard can be configured to set: Page 23 of 40

24 A single slideshow for all dashboards defined in the navigation tree Any number of user-defined slideshows to view selected dashboards in the navigation tree Slideshow to display all dashboards in the navigation tree Tick the Add a slideshow with all dashboards checkbox. This shows the interval time field. The default interval time is 5 seconds. If a longer interval is required, edit the interval time. Click on the Save button to save the slideshow in config.xml. Go to the Dashboard tab to check the All Dashboards slideshow. Page 24 of 40

25 Slideshow to display selected dashboards Click on the Add Slideshow button to open a new slideshow row. Edit the name of the new slideshow. This shows the Dashboards dialog. The default interval time is 5 seconds. If a longer interval is required, edit the interval time. Click on the Add button in the Dashboards dialog. By default, the name of the first dashboard in the list appears. Click on the name to show the dropdown list of dashboards. Repeat step 4 to add more dashboards to this slideshow. The Up and Down buttons in the Dashboards dialog can be used to define the sequence of dashboards in the slideshow. Page 25 of 40

26 The Remove button can be used to delete a dashboard from the slideshow. Once the new slideshow configuration is completed, click on the Save button to save the new slideshow details config.xml. Go to the Dashboard tab to check the new slideshow. Page 26 of 40

27 Slideshows in config.xml A slideshow is stored under the <slideshows> element with the following attributes: Attribute name interval Description The name given to the slideshow The time in seconds taken by every dashboard in the slideshow to be on display. Default value: 5 seconds And can contain one or more dashboards. Page 27 of 40

28 Example: <geneoswebserver> <slideshows> <slideshow name="all Dashboards" interval="5"/> <slideshow name="slideshow 1" interval="5"> <dashboard name="dashboard1"/> <dashboard name="dashboard2"/> <dashboard name="dashboard3"/> <dashboard name="dashbaord4"/></slideshows> </geneoswebserver> Settings for the visualization of dashboards in browsers config.xml contains the <dashboarddefaults> element with the settings applicable to all dashboards configured in Web Dashboard: <geneoswebserver> <dashboarddefaults> <updaterate>5</updaterate> <dashboardrefreshrate>3</dashboardrefreshrate> <tilesize> <width>200</width> <height>200</height> </tilesize> </dashboarddefaults> </geneoswebserver> Property Attribute Description <updaterate> Sets the interval time at which the Web Dashboard client checks for updates to a dashboard. Default value: 5 seconds <dashboardrefreshrate> Sets the frequency at which the Web Dashboard server processes dashboard updates. Default value: 3 seconds Page 28 of 40

29 Property Attribute Description <tilesize> <width> <height> Sets the tile size to be used by Web Dashboard when rendering the dashboard image. Default value for both attributes: 200 pixels It is not recommended to change these settings but, if required, these changes need to be implemented with care. The following points need to be taken in consideration: <updaterate> should be set equal or more than <dashboardrefreshrate> since clients are guaranteed not to receive an update until a dashboard refresh takes place. Faster <dashboardrefreshrate> makes dashboards appear more real-time but in turn increases CPU usage on the server and potentially increases network traffic as updates are being sent more frequently this assumes <updaterate> is closely aligned to <dashboardrefreshrate>. Tiling size allows for more granular control of how updates are processed on the server and sent over the network. Smaller values make more efficient use of network as clients download less redundant data but in turn makes many more requests. Also, CPU usage on the server may increase due to processing more granular updates and handling the increased number of requests. Note: The settings tilecachesize and tilecachetime have been removed from config.xml. Deleting a dashboard in Web Dashboard Removing a dashboard from the configuration takes place in 4 steps in a precise sequence: Removing the dashboard from a user-defined slideshow Go to the Slideshows configuration page. Click on the user-defined slideshow. This shows the Dashboards dialog. Select the dashboard in the Dashboards dialog list and click on the Remove button. Click on the Save button so that Web Dashboard modifies the <slideshows> element in config.xml. Page 29 of 40

30 Removing the dashboard from the Navigation tree Go to the Navigation configuration page. Locate the dashboard in the navigation tree and right-click on it. Select the Remove option. Click on the Save button so that Web Dashboard modifies the <tree> element in config.xml and its internal dashboard handler program. Deleting the dashboard from Web Dashboard Go to the Dashboards configuration page. Click on the dashboard so that the Remove Dashboard button is activated. Click on the Remove Dashboard button. Click on the Save button so that Web Dashboard modifies the <dashboards> element config.xml and deletes the uploaded.adb file in the installation directory. Deleting the gateway connection if it only served the deleted dashboard Go to the Connections configuration page. Locate the gateway and click on its X icon. Click on the Save button so that Web Dashboard modifies the <gatewayconnections> element in config.xml. Deleting a slideshow in Web Dashboard Go to the Slideshows configuration page. Locate the slideshow and click on its X icon. Click on the Save button so that Web Dashboard modifies the <slideshows> element in config.xml. Working with the Web Dashboard Navigation interface Opening the navigation interface Type the host and the port of Web Dashboard in the web browser to access the navigation interface in the following format: Example: Page 30 of 40

31 If authentication is enabled, the page displays a log-in screen. See Enabling Authentication in Starting Web Dashboard section to set up users. Note: Username is case-insensitive. If authentication is disabled or after a successful log-in, the page displays the navigation tree with 2 root entries: Dashboards and Slideshows. The Dashboards group expands to the first level if the navigation tree has been configured. Page 31 of 40

32 Selecting a dashboard to view There are 2 ways to bring a dashboard to be displayed: Select the dashboard in the Dashboards navigation tree. This may require to expand a group in the tree by clicking on its plus icon. Access the dashboard directly by adding #WebDashboard:<dashboardname> to the basic URL, e.g., Maximizing the view of the dashboard By default, the dashboard on display occupies a pane beside the navigation tree and under the top banner. There are 2 ways to maximize the display of a dashboard: Right-click anywhere in the dashboard and select Toggle Full Screen. The same steps can be used to return to the normal view. Select the dashboard in the Dashboards navigation tree and add?fullscreen to the basic URL, e.g., Page 32 of 40

33 Executing data item commands Right-click on a data item in the dashboard to access data item commands. This action prompts Web Dashboard to display a menu with the commands relevant to the data item. If the selected command requires user input, the page displays a dialog for the user to fill in. Page 33 of 40

34 If the execution of the command results to an output, the page displays a command output dialog. Executing hyperlinks If hyperlinks have been defined in the dashboard, these can be accessed through the right-click menu of the data item. Select a link to open its page as a new tab in the browser. Page 34 of 40

35 Selecting a slideshow to view There are 3 ways to bring a slideshow to be displayed: Click on the slideshow in the Slideshows navigation tree. Right-click on the slideshow in the Slideshows navigation tree and select the Play option. Access the slideshow directly by adding #Slideshow:<slideshowname> to the basic URL, e.g., Slideshow 1 The slideshow displays the sequence of dashboards it was configured with. The time a dashboard remains in view is the time interval defined in the configuration of the slideshow. Every dashboard in the slideshow that is displayed is highlighted in the Dashboards navigation tree. This allows the user to follow the order of the sequence. Page 35 of 40

36 Stopping a slideshow There are 2 ways to stop a slideshow: Right-click on the slideshow in the navigation tree and select the Stop option. Select and click on any other dashboard in the navigation tree. Troubleshooting Defining update rates or tiling size settings for individual dashboards By default, the settings in the <dashboarddefaults> element are applied to all dashboards configured in Web Dashboard. However, if these settings are not adequate for an individual dashboard, specific settings may be set for that dashboard only. Edit the dashboard entry in config.xml and add the new settings. Example: <dashboarddefaults> <updaterate>5</updaterate> <dashboardrefreshrate>3</dashboardrefreshrate> <tilesize> Page 36 of 40

37 <width>200</width> <height>200</height> </tilesize> </dashboarddefaults> <dashboards> <dashboard name="dashboard1" path="/root/dashboards/uploaded/db1.adb"/> <dashboard name="dashboard2" path="/root/dashboards/uploaded/db2.adb"/> <dashboard name="dashboard3" path="/root/dashboards/uploaded/db3.adb"> <!-- DASHBOARD SPECIFIC SETTINGS --> <updaterate>10</updaterate> <dashboardrefreshrate>5</dashboardrefreshrate> <tilesize> <width>400</width> <height>400</height> </tilesize> </dashboard> </dashboards> In this example, Dashboard1 and Dashboard2 use the default settings, while Dashboard3 has its own settings. Redirecting the dashboard loading folder By default, Web Dashboard uploads the.adb files into the <web_dashboard_install_ dir>/dashboards/uploaded/ folder and then loads the dashboard from that location. If a different location is required, edit config.xml to change the path attribute of the dashboard under the <dashboards> element. Example: <dashboards> <dashboard name="dashboard_a2" path="/home/gelo/etc/support_dashboard.adb"/> <dashboard name="dashboard_b1" path="/home/gelo/etc/test.adb"/> </dashboard> </dashboards> Resolving high CPU/memory of Web Dashboard CPU and memory used by Web Dashboard are largely determined by the contents and updates of the dashboards it has been configured with. Page 37 of 40

38 Edit config.xml to slow down the update rate for: The <dashboarddefaults> element - this action implies that the new settings for <updaterate> and <dashboardrefreshrate> are applied to all dashboards. Individual dashboards if they have been identified as main contributors to the high CPU/memory - the settings for <updaterate> and <dashboardrefreshrate> need to be added to the specific dashboard under the <Dashboards> element. In both cases, it is recommended that <dashboardrefreshrate> is equal or faster than <updaterate> to ensure timely updates. Resolving the constant flickering and blank areas of a dashboard on display This issue may be the result of: Having more updates than those processed by Web Dashboard in the time set by the <dashboardrefreshrate> parameter. If this is the case, increase the value of this parameter up to the value of the <updaterate> parameter. Having increased the tile size, which implies that there is too much data through the network for each tile. If this is the case, reduce the values of the <tilesize> element. Preventing memory buildup due to gateway disconnection By default, Web Dashboard will try to reconnect to a disconnected gateway over and over again until the connection is restored. This, in turn, causes rapid memory buildup. To prevent this behavior: Edit the run script to add: export ORBFASTER_FAST_CALLBACK=false Save the changes and restart Web Dashboard. Applying MySQL to Web Dashboard Web Dashboard supports database queries required for historical charts. Although no changes are required for Sybase, MSSQL, or Oracle, the connection to MySQL needs to be manually incorporated to the geneos-web-server.jar file. Create a temporary directory (e.g., gws) under the Web Dashboard installation directory. Copy geneos-web-server.jar into the gws directory. Extract the jar file with the following command: Page 38 of 40

39 jar xvf geneos-web-server.jar The gws directory will contain the folders: com and META-INF. Delete geneos-web-server.jar from the gws directory. Navigate to the META-INF folder. Open MANIFEST.MF in an editor. Add the path to the MySQL driver to the end of the Class-Path pair and save the MANIFEST.MF file. Go back to the gws directory and recreate geneos-web-server.jar with the following command: jar cmf META-INF/MANIFEST.MF geneos-web-server.jar * Replace geneos-web-server.jar in the Web Dashboard installation directory with the new geneos-web-server.jar file just created. Note: The jar command is present in the Java JDK package, and the path must be indicated. The MANIFEST.MF file must end with a blank line, and the maximum width of the line is 70 characters. Enabling DEBUG in Web Dashboard Sometimes, there may be issues with Web Dashboard that need further investigation, and a detailed log file may be useful. Edit log4j.properties and modify the log4j.rootlogger parameter from: log4j.rootlogger=off, CONSOLE, FILE to: log4j.rootlogger=debug, CONSOLE, FILE Page 39 of 40

40 Save the changes and restart Web Dashboard. Repeat the actions that led to the issue. Send the log file to Geneos Support for assistance. Gateway connections are not displayed when opening the Configuration interface Frequent manipulation of config.xml may disrupt the presentation of the Connections page. Press the Reload button to restore the gateway connections or press F5 to refresh the page. Cannot remove a dashboard in the Dashboards configuration interface This action will not be allowed if the dashboard has been configured in the Navigation tree and has been included in Slideshows. Remove the dashboard from Slideshows and then in the Navigation tree. Remove the dashboard from the Dashboards configuration interface. Slideshow on display does not seem to update if a new dashboard has been added Press F5 to refresh the slideshow on display. Page 40 of 40