The administrative workstation (AW) provides the systems administrator with an array of
configuration tools to manage and maintain the UCCE platform
The most popular AW deployment is the AW-HDS-DDS.
The logger holds the database used by the central controllers, but rather than this database
being modified by the client applications, the configuration tools actually modify a
copy of the configuration data stored in the local database on the AW. When changes are
made in this database, the AW processes communicate with the loggers to instruct them
of the change.As well as containing a copy of the configuration data, the AW database also contains
data used for real-time reporting. Although this data is described as real-time, in practice
it should actually be termed “near real-time” as the data is updated approximately every
10–12 seconds.
Below are the database that are present in the mentioned deployment:
<instance name>_awdb: Used for storing UCCE configuration and real-time data
<instance name>_hds: Used by the HDS processes for long-term historical data storage
<instance name>_wv: Used by WebView for storing WebView-specific configuration
Where the instance-name is the customer instance name
The AW consists of many software processes:
configlogger: The Configuration Logger process stores configuration data in the AW
database.
replication: The Replication process receives historical data from the logger and
inserts this data into the HDS database on the AW.
rtdist: The Real-Time Distributor receives real-time data from the router and distributes
this data to all the real-time clients that are connected to it. These clients can be
other AWs, typically a client AW.
rtclient: The Real-Time Client on the AW is responsible for updating the local AW
database. The rtclient gets its data from the rtdist process.
updateaw: The UpdateAW process ensures that the local AW configuration database
remains current with configuration data from the central controller.
configuration tools to manage and maintain the UCCE platform
The most popular AW deployment is the AW-HDS-DDS.
The logger holds the database used by the central controllers, but rather than this database
being modified by the client applications, the configuration tools actually modify a
copy of the configuration data stored in the local database on the AW. When changes are
made in this database, the AW processes communicate with the loggers to instruct them
of the change.As well as containing a copy of the configuration data, the AW database also contains
data used for real-time reporting. Although this data is described as real-time, in practice
it should actually be termed “near real-time” as the data is updated approximately every
10–12 seconds.
Below are the database that are present in the mentioned deployment:
<instance name>_awdb: Used for storing UCCE configuration and real-time data
<instance name>_hds: Used by the HDS processes for long-term historical data storage
<instance name>_wv: Used by WebView for storing WebView-specific configuration
Where the instance-name is the customer instance name
The AW consists of many software processes:
configlogger: The Configuration Logger process stores configuration data in the AW
database.
replication: The Replication process receives historical data from the logger and
inserts this data into the HDS database on the AW.
rtdist: The Real-Time Distributor receives real-time data from the router and distributes
this data to all the real-time clients that are connected to it. These clients can be
other AWs, typically a client AW.
rtclient: The Real-Time Client on the AW is responsible for updating the local AW
database. The rtclient gets its data from the rtdist process.
updateaw: The UpdateAW process ensures that the local AW configuration database
remains current with configuration data from the central controller.
Świetnie napisane. Pozdrawiam serdecznie.
ReplyDelete