Apama 10.3 | Apama Documentation | Building and Using Apama Dashboards | Dashboard Deployment | Administering Dashboard Security | Securing communications
Securing communications
For local application deployments, where dashboards communicate directly with the data server, your options for securing dashboard communications include:
*Enabling secure sockets (SSL) in the data server.
*Utilizing a secure channel (SSH) for all dashboard communication.
*Utilizing a virtual public network (VPN) for all dashboard access.
For thin-client deployments, where dashboards communicate through an application server, your options include the following:
*Enabling HTTPS in the application server.
*Utilizing a virtual public network (VPN) for all dashboard access.
As with all encryption technology, there is a cost in performing the encryption and decryption of data. For applications with a very high frequency of data changes, you should account for this cost when you determine how frequently a dashboard can be updated (see the description of the -u or --update option).

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.