The following terms are used in the deployment scenarios documentation.
- Content Store
- Stores all the DITA content (maps, topics), non-DITA content (images, PDF files, videos, etc.), and workgroup configuration for the DITA CMS.
- Group of users in a company who share the same Content Store.
- Workgroup configuration
- Set of business rules that define the workflow for the DITA and non-DITA documents in the Content Store. This configuration specifies the sequence of states that the documents must follow as well as access rights, user group definitions, dictionaries, etc.
- Single-site deployment
- A deployment where all the users are in the same geographical location (office).
- Multi-site deployment
- A deployment where users work with the DITA CMS from multiple locations.
- Primary site
- In a multi-site deployment, this is the site where the primary Content Store is located.
- Secondary site
- In a multi-site deployment, users at a secondary site are connected to the rest of the company through a wide area network (WAN) and they access the DITA CMS using a remote application solution. If replication is used, a replicated Content Store may be located at this site.
- Satellite user
- A user who works from home or a very small office (with very few DITA CMS users).
- Process of creating one or more copies of the Content Store. These copies are then synchronized with the primary Content Store to provide read caching for geographically distributed teams, allowing them to perform read operations more effectively.
- If replication is implemented, all the read operations for users at secondary sites are performed locally on the replicated Content Store, while write operations are performed on the primary Content Store, over the network.
- Hypervisor with virtual machine
- A hypervisor, also called a virtual machine manager, is a program that allows multiple operating systems to share a single hardware host. The hypervisor controls the host processor and resources, allocates the needs of each operating system, and checks that the guest operating systems or the virtual machines do not disrupt each other.
- Cold standby
- Cold standby is a redundancy method in which the secondary (or standby) system
is turned on manually when the primary system fails. Note: Before the system on cold standby is brought online, the latest available copy of the data (including the Content Store) need to be installed or mounted in the cold standby system.
- Warm standby
- Warm standby is a redundant method in which the secondary (i.e., standby) server runs and receives replicated data from the primary server. Since the data is replicated to the standby server at regular intervals, there are times when both the servers do not contain the exact same data.