Architecture
Overview of the systems structural elements and relationships based on a concrete architecture.
Note that the documentation here describes a specific architecture chosen based on the general Protocols.
System overview
General overview of the system architecture and functionalities.
Protocols
This describes the protocol for the Bit Repository.
- Message exchange protocol —
- Message flow — Describes the general messageflow in communication between the Bit Repository components.
- Protocol messages — Description of the different protocol messages, which operation it applies to, and their types.
- Message format — Description of the the XML basic message structure and format.
- File Exchange protocol — Describes the underlying protocol used as the File Exchange.
- Protocol versioning — Describes how a system of components supporting different versions of the protocol should work.
- Operations descriptions — Documentation of the different operation primitives that the protocol describes
- GetFileInfos
- ReplaceFile — Operation to replace a file on one or more pillars in a collection.
- DeleteFile — Operation to remove a file from one or more pillars in a collection
- GetFile — Operation to retrieve a single file from a collection.
- GetAuditTrails — Operation to retrieve audittrails for a specific collection from one or more contributors
- PutFile — Operation to ingest a file on one or more pillars in a collection.
- GetChecksums — Operation to get checksums from one or more pillars in a given collection.
- GetStatus — Operation to retrieve status from components in a repository
- GetFileIDs — Operation to get fileIDs from one or more pillars in a given collection.
Security
Description of the security model of the Bit Repository
- Encryption — To prevent anybody from eavesdropping on the bit repository data and messages exchanged, all communication is encrypted.
- Authentication — To ensure messages are transmitted, untampered signature based authentication is used.
- Authorisation — Describes how messages requesting operation on a collection are checked against the permission model.