Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "EclipseSCADA/GettingStarted/ESAC"
(→= By Uri) |
|||
| Line 83: | Line 83: | ||
Creates one hierarchy level based on the hostname. | Creates one hierarchy level based on the hostname. | ||
| − | ==== By Uri === | + | ==== By Uri ==== |
Creates a hierarchy based on the URL, with separate Levels for each part. | Creates a hierarchy based on the URL, with separate Levels for each part. | ||
Revision as of 07:07, 25 February 2014
Contents
The Eclipse SCADA Administration Client (ESAC)
Download the "Eclipse SCADA Administration Client" (http://www.eclipse.org/eclipsescada/downloads.html). The Client is available as a simple zip file for Windows, Linux and Mac. Additionally for Windows there is a MSI installer available.
The ESAC is primarily used for two things: Peeking into a running system, to browse tags/items, and to deploy configurations to a running Equinox based SCADA application. You can also use it to show the historical data and browse alarms and events.
Connections
Eclipse SCADA supports 3 basic (home grown) protocols:
- net/gmpp (the old protocol)
- ngp (the current protocol)
- sfp (in development, compact, less features but efficiently to implement, supports only DA)
Generally the standard protocol which is used throughout Eclipse SCADA is ngp. It supports flexible timeouts, streaming compression, ssl, callbacks.
On top of the basic protocol there exist 4 variants:
- da (Data Acquistion)
- ae (Alarms & Events)
- hd (Historical Data)
- ca (Configuration Administrator)
The reason for that is that it reduces the surface of the API, so you wouldn't need to have to include all ae/hd/ca functionality if you are only interested in DA. The consequence of it is, that each variant needs its own port. Maybe in the future there will be a wrapper that supports all variants over one connection, but for now that doesn't exist.
To connect to a Eclipse SCADA Server, you need to connect using an Eclipse SCADA URL. This takes the following shape:
[da|ae|hd|ca]:[net|ngp|sfp]://[[<username>]:<password>@]<host>:<port>[?<option>=<option value>[&<option>=<option value>]]
Examples:
da:ngp://localhost:2101 da:ngp://demo.openscada.org:2101 ca:ngp://myuser:mypassword@scada.example.org:2401?timeout=240000
All ports can be chosen freely, but within the project we use defined standard ports.
URL Options are documented here.
Adding connections
Within the ESAC, connections may be stored in 3 different places:
- standard file source
- user settings
- system settings
standard file source
Stores the configuration within the OSGi configuration area. When a new version of the ESAC is installed, the connections are lost.
user settings
The recommended place, to store the connections. The connections get stored per user. For that the standard java preferences API is used, so the actual storage is different depending on the platform (Registry on Windows, Home folder on Linux).
system settings
Available to every user, but only an administrator can actually store connections there.
The Connections tree
The Nodes where the connections can be created where already discussed above. There are other Nodes which are essentially a view on the existing connections.
OSGi Connection Services
Displays automatically registered connections. Since every explicitely added connection gets also registered, they will appear here as well.
All Connections
A flat list of all connections.
By target
Creates one hierarchy level based on the hostname.
By Uri
Creates a hierarchy based on the URL, with separate Levels for each part.