Browse the glossary using this index
Special |
A |
B |
C |
D |
E |
F |
G |
H |
I |
J |
K |
L |
M |
N |
O |
P |
Q |
R |
S |
T |
U |
V |
W |
X |
Y |
Z |
ALL
Package Definition File (.aaPDF)
- The standard description file that contains the configuration data
and implementation code for a base template. File extension is .aaPDF.
|
|
Package File (.aaPKG) - The standard description file that contains the configuration data and implementation code for one or more object instances or Templates. File extension is .aaPKG.
|
|
Platform Count - Number of PCs in the Galaxy. Each Workstation and/or Server communicating directly with the Application Server requires a platform to be part of the Galaxy Namespace. This includes each InTouch 9.0 or higher and InTouch View 8.0 or higher client. Each InTouch Terminal Services Session needs IAS Terminal Services Session License. A Platform License includes a per seat FSCAL2000 with Microsoft 2000 SQL Server CAL. Stand-alone computers that only host Historian Servers or remote DA Servers do not need a platform license.
|
|
Platform Manager - The Platform Manager provides Galaxy application diagnostics by allowing you to view the run- time status of some system objects and to perform actions upon those objects. Actions include setting platforms and engines in an executable or idle mode and starting and stopping platforms and engines. This utility is an extension snap-in to the ArchestrA System Management Console (SMC).
|
|
Platform Object - An object that represents a single computer in a Galaxy, consisting of a system wide message exchange component and a set of basic services. This object hosts all Application Engines.
|
|
Primary Application Engine - The object created by the ArchestrA infrastructure when the Backup object has been created through Redundancy. See Redundancy for further detail.
|
|
Properties - Data common to all attributes of objects, such as name, value, quality, and data type.
|
|
Proxy Object - A Proxy Objects is an Automation Object that represents an actual product for the purpose of device integration with the Wonderware Application Server or InTouch® HMI. For example, there is a Proxy Object that enables the Wonderware Application Server to access an OPC server.
|
|