iModelHub - The Backbone for iModel.js Applications
Like Git repositories for source code, in the iModel ecosystem copies of iModels are distributed widely in Briefcases. In fact, iModelHub's primary purpose is not to hold or process copies of iModels (it does so only to facilitate Briefcase checkout). Rather, iModelHub's main role is to maintain the sequence of ChangeSets that forms an iModel's Timeline. Like an accounting system does for financial transactions, iModelHub holds a ledger of all changes to an iModel.
iModelHub accepts ChangeSets from iModel.js backends through a process called push, and sends them to other validated users when requested through a process called pull. iModel.js applications determine when and how to push and pull changes.
See Working with iModelHub for a list of related learning topics.
- Every iModel has an identity registered in iModelHub.
- Users authenticate with iModelHub.
- iModel.js backends have an identity, registered with iModelHub.
- iModel owners decide, which users and which applications have access to their iModels.
When an iModel.js backend opens an iModel, it first verifies with iModelHub that the iModel's owner has granted the right for the specified user and application to access the briefcase. In this manner owners can maintain control over who-does-what with their iModels.
See Accessing iModels for further details.
When an iModel is first created, it is uploaded to iModelHub, assigned a Guid, associated with a connected context (e.g. a CONNECT Project), and its timeline is initialized. iModelHub provides tools to configure access to the iModel by users and applications. As new users and agents connect to iModelHub to access the iModel, they are each assigned briefcases with a unique Id.
See Working with iModels.
iModelHub holds an immutable ledger of all changes to an iModel. Similar to an accounting system for financial data, the ledger can provide a reliable record of what-happened-when and by whom. Since the ledger is reliable, immutable and append-only (i.e. it is not possible to revise history), it forms a timeline that can be referenced externally as an authoritative record of the state-of-the-iModel as of a given point in time. In this manner, iModelHub provides the means to sign the timeline rather than create external (and potentially forgeable) snapshots for archival or reference.
A local Briefcase holds the state of an iModel as of a given point in time, plus changes made locally, if any. To receive changes made by others, users synchronize their Briefcase from iModelHub. Any ChangeSets pushed to iModelHub by other users are pulled and merged into the local Briefcase.
To permanently save your changes, you push them in the form of a ChangeSet to iModelHub. You must always synchronize your Briefcase with iModelHub before you can upload changes. iModelHub enforces that ChangeSets it accepts must always be based on (i.e. synchronized with) the most recent ChangeSet. This is what establishes the linear timeline of changes.
Every ChangeSet on the timeline creates a new version of the iModel. However, some points on the timeline can represent important milestones or significant events to be saved (e.g. for a design review). iModelHub provides a way to mark a point on the timeline with a name. These time points are referred to as Named Versions. Since a specific action must be taken to create them, they are treated specially by iModelHub with caching to make them faster to access.
See Using Named Versions.
iModels are meant to be distributed widely in the form of Briefcases, and each Briefcase may be edited independently. However, certain actions among the distributed Briefcases are best coordinated to avoid conflicting changes. iModelHub provides services for acquiring Locks and Codes for this purpose.
Applications can register listeners for events from iModelHub. Events report on certain operations being performed on that iModel. It is possible therefore to create Agents that react to every ChangeSet, performing validation, tracking, synchronization with external systems, etc. Since each Agent works on a local Briefcase synchronized with ChangeSets, they can be deployed independently and the system is vastly scalable.
See Working with events.
Last Updated: 01 November, 2019