Apama 10.3 | Apama Documentation | Building and Using Apama Dashboards | Dashboard Deployment | Dashboard Deployment Concepts | Builders and administrators
Builders and administrators
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, as well as the use of the Dashboard Deployment Configuration Editor to generate a deployment package. See Preparing Dashboards for Deployment.
*Dashboard deployment, which requires installing the deployment package, as well as administering the data server or display server and managing dashboard security.
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 dashboards to be deployed:
*The 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 server or display server host, port, and update rate that the builder supplied to the Configuration Editor.
*The 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.
*The trend-data caching requirements for the deployed dashboards. See Configuring Trend-Data Caching.

Copyright © 2013-2018 | Software AG, Darmstadt, Germany and/or Software AG USA, Inc., Reston, VA, USA, and/or its subsidiaries and/or its affiliates and/or their licensors.