| Excerpt |
|---|
General overview of the system architecture and functionalities |
...
| Section |
|---|
| Column |
|---|
System componentsThere are the following types of clients |
|
...
components in a BitRepository system: PillarsPillars are responsible for maintaining copies of the store material and providing bit preservation related operations on these There are the following types of pillars seen from the data perspective: - A full copy pillar, which contains full copies of delivered files identified uniquely with a service level agreement
- A checksum pillar (with specific checksum type), which contains derived copies of delivered files, in form of a checksum. The checksums are identified uniquely with a service level agreement in the same way as for full copies pillars.
|
|
...
...
...
...
Clients which can be used to perform operations on the BitRepository, e.g. |
|
...
Specific implementation of services
In the reference implementation there have been made a choice to have a special service to take care of audit trails. This also include consideration on
- collection of alarms from any component in the system
- how alarm are mirrored in audit trails
- how relevant information from monitor service is passed
this is illustrated in the following figure:
...
PutFile, GetFile, etc. See Operations descriptions for a full listing of operations. ServicesServices actively perform tasks without user triggering, see Reference services for examples of services. InfrastructureProvides the communication infrastructure for integrating the components. This consists of: Principles- Components have no direct knowledge of each others location. Communication is rather performed indirectly by using the specified Queues and topics.
- All communication is asynchronous.
|
| Column |
|---|
| Gliffy |
|---|
| displayName | Coresystem |
|---|
| name | Coresystem |
|---|
| pagePin | 8 |
|---|
|
|
|