Summary: Describes the all new XAP web based dashboard application
Overview
In terms of functionality, it does not replace the existing Java-based GUI (the GigaSpaces Management Center), but rather augments it and provides a lightweight alternative for monitoring a running cluster without the need to install the GigaSpaces XAP runtime and run the standalone Java-based user interface. Starting the Dashboard Web ApplicationThe dashboard web application is located under GigaSpaces root/tools/gs-webui. This directory contains the web application itself (in the form of a standard JEE .war file), and a launcher library and shell scripts used to start in standalone mode (see below). Starting the Dashboard Web Application in Standalone ModeThis is the simplest way to run the dashboard web application. Simply click the gs-webui.sh(bat) script to start a Jetty web container with the web dashboard application running within it. Once started, there's no need to deploy or perform any additional steps. The web container in the standalone mode listens by default on port 8099, so in order to view the dashboard application you will need to point your browser to http://<standalone server host>:8099, where <standalone server host> is the host on which you launched the gs-webui script. Note that in this mode, the default context path for the dashboard web application is the root context path ("/"). To override the default port, you can either use the com.gs.webui.port system property, or specify -port <listen port> as an argument to the gs-webui script. Here is an example on how it's done(starting to listen on port 80):
Linux
#Specify port via a command line argument ./gs-webui.sh -port 80 #Specify port with a system property export WEBUI_JAVA_OPTIONS=-Dcom.gs.webui.port=80 ./gs-webui.sh Windows #Specify port via a command line argument gs-webui.bat -port 80 #Specify port with a system property set WEBUI_JAVA_OPTIONS=-Dcom.gs.webui.port=80 gs-webui.bat Note that you can also use the WEBUI_JAVA_OPTIONS environment variable to set any JVM parameter, such as heap size (defaults to -Xmx512m) and other JVM settings. Deploying the Dashboard Web Application to the GigaSpaces Runtime EnvironmentTo deploy the dashboard web application to the GigaSpaces Runtime Environment, you should simply point your deployment tool of choice (CLI, Admin API or the standalone Java-based UI) to the <GigaSpaces root>/tools/gs-webui/gs-webui.war file and deploy it. Note that in this case the web dashboard application actually monitors the runtime environment on which it runs. Here's an example of how to this with the CLI: <GigaSpaces root>/bin/gs.sh(bat} deploy -properties embed://web.port=80;web.context=/ \
<GigaSpaces root>/tools/gs-webui/gs-webui.war
The above command will deploy the dashboard web application to the GigaSpaces runtime environment, listening on port 80 with the root context path. For more details on GigaSpaces XAP web application support, please refer to this page. Deploying the Dashboard Web Application to a 3rd Party JEE Servlet ContainerIt is also possible to deploy the web application to a 3rd party servlet container (e.g. Apache Tomcat). Please consult your web container documentation for deployment directions.
Logging into the Web DashboardAfter you've started the dashboard web application, point your browser to the proper location (For example, if you stated it using the standalone web container, the default URL is http://<standalone server host>:8099. ![]()
Using the Web DashboardOnce you've passed the login screen, you will enter the dashboard's main screen. The web dashboard enables you to monitor the physical and logical resources of your cluster. The physical resources include the hosts and virtual machines, and the logical resources include the deployed processing units, spaces and web applications. Please refer the image below and the call-outs in it for more details. ![]() Runtime ConsiderationsDeployment Location of the Dashboard Web ApplicationSince the dashboard web application communicates with the runtime components of the GigaSpaces cluster, and receives notification from the GigaSpaces lookup service, it is highly recommended to run the dashboard web application in the same network segment of the other cluster components. Note that this does not affect the dashboard web browser client, which communicates with the dashboard web application using standard http and can be located anywhere, provided that it has access to the dashboard web application. |
![]() |
GigaSpaces.com - Legal Notice - 3rd Party Licenses - Site Map - API Docs - Forum - Downloads - Blog - White Papers - Contact Tech Writing - Gen. by Atlassian Confluence |