Deploying dashboards
Dashboard deployment and administration involves the following activities:
Before you perform these tasks, you should familiarize yourself with the deployment and administration concepts introduced in this section. Each concept described here is covered in more detail in
Dashboard Deployment Concepts.
Deployment options
Dashboards can be deployed as simple, thin-client Web pages, as Java applets, as Java Web Start applications, or as files that can be loaded into a locally-installed, desktop application, the Dashboard Viewer. These deployment options are described and compared in
Deployment options.
Data server and display server
Scalability and security of dashboard deployment are supported by the use of the
Data Server and
Display Server, which mediate dashboard access to running Scenarios and DataViews. The Data Server and Display Server are introduced in
Data server and display server.
Process architecture
Applet and Web Start dashboards communicate with the Data Server via servlets running on an application server. Simple, thin-client, Web-page dashboards communicate with the Display Server via servlets running on your application server. Locally-deployed dashboards communicate directly with the Data Server. The structure of deployed configurations is detailed in
Process architecture.
Builders and administrators
Dashboard deployment involves the use of a dashboard deployment package that was generated by Apama Studio’s Dashboard Deployment Configuration Editor. In some cases the user that generated the deployment package is different from the user that installs and configures the deployment and administers the Data Server. The information that must be transferred between these two types of users is discussed in
Builders and administrators.
Deployment package installation and configuration—see Deploying Dashboards.