Sharing information with the Dashboard Administrator
There are two types of activity involved in making dashboards available to end users:
Dashboard development, which requires the use of the Apama Dashboard Builder or
Dashboard Generation wizard, as well as the use of the Dashboard Deployment Configuration Editor to generate a deployment package.
Dashboard deployment, which requires installing and configuring the deployment package, as well as administering the Data Server or Display Server and managing dashboard security (see
Deploying and Managing Apama Applications).
Sometimes these activities are performed by different individuals. In such a case, the dashboard developer must be sure to communicate the following information to the dashboard administrator regarding the dashboard to be deployed:
Location and file name of the
.war file or
.zip file that was generated by the Deployment Configuration Editor when the developer prepared the dashboard for deployment
For Display Server deployments, the location of the dashboard project directory (the directory that contains the project’s
.rtv files)
For Web-based deployments, the Data Sever or Display Server host, port, and update rate that the builder supplied to the Configuration Editor
Logical name for each correlator as well as the host name and port for each
deployment correlator (if any) that was specified by the dashboard developer in the
Apama tab of the
Tools >
Options... dialog prior to the generation of the deployment package. See
Changing correlator definitions for deployment.
Trend-data caching requirements for the deployed dashboards. See Configuring Trend-Data Caching in
Deploying and Managing Apama Applications.
Whether SQL-based instance tables are used by the dashboard for data attachments. See Attaching dashboards to correlator data in Building dashboards in
Developing Apama Applications.
Copyright © 2013
Software AG, Darmstadt, Germany and/or Software AG USA Inc., Reston, VA, USA, and/or Terracotta Inc., San Francisco, CA, USA, and/or Software AG (Canada) Inc., Cambridge, Ontario, Canada, and/or, Software AG (UK) Ltd., Derby, United Kingdom, and/or Software A.G. (Israel) Ltd., Or-Yehuda, Israel and/or their licensors.