Specifications

Data Access
PlantScape Server and Client Configuration Guide 339
Areas
An area must be configured on every server that accesses it. The configurations
must specify the same area code and server alias, and the code for each area
must be unique across all servers.
All points assigned to an area must be defined on the server specified in the
area’s definition.
Any point that is accessed from more than one server must be assigned to an
area.
By default, the server subscribes to alarms for all areas. You can unsubscribe to
alarms from a remote area by clearing its Enable Alarms checkbox on the Areas
summary.
For information about how to configure areas, see “Defining and Enabling Areas”
on page 92. For information about alarms in a distributed server architecture, see
“Notifications” on page 343.
Point IDs
Point IDs must be unique across all servers that share data, to eliminate the need
to specify the server when points are referenced (for example during engineering
activities). You might want to establish a point naming convention that ensures
uniqueness across all servers.
Note If points on two servers have the same point ID, a local server creates a cache
point from the first server that responds to its query.
Internal Point Numbers
Point data for a remote point is ultimately accessed by its internal point number
on its local server. If a point is deleted and then recreated, its internal point
number might change, which means that remote group, trend, and custom
displays can no longer access the point. You need to re-enter the point into the
remote group, trend, and custom displays that access it. For more information,
refer to “Understanding Internal Point Numbers” on page 189.
The cache points are automatically deleted from all remote servers when the
point is deleted at the data owner.
plscpcg.book Page 339 Monday, May 28, 2001 10:11 AM