PRG Mbox Studio Manual 3.8 - Manual (Page 146)

138 MBOX ® STUDIO USER MANUAL
CONTENT MANAGEMENT
Overview
About Mbox Remote Content Management
The Mbox Remote Content Management system allows quick and easy management of content between Mbox
servers. For this purpose, the Remote application window provides three main areas for display of managed servers
(left), status/content (middle), and file details/history (right) as shown in the example below:
The following components are required in order to use the Mbox Content Management system:
+ The first required application is Mbox Remote. Remote is the user interface into the Content Management system
and must be running on at least one machine and connected to the same network as the other Mboxes in the
system.
+ The second required application is Mbox Daemon. Daemon is the service provider that allows Mbox Remote to
control, monitor, and manage content and settings of an Mbox server. Mbox Daemon must be running and
correctly configured in order for Mbox Remote to function. (When an instance of Mbox is started, the last version
of Daemon will be will also be started automatically.)
+ Finally, an Mbox application itself must be running (i.e., Mbox Designer, Mbox Studio, or Mbox Mini). Although
Mbox is not required to be running in order to use the Content Management system in its basic form, having
Mbox running exposes all of the features of Remote for management.
Terminology
In order to fully understand how content management works, it’s important to understand some basic terminology.
+ Server - An Mbox server consists of two major software components with respect to Content Management:
Mbox Daemon and Mbox application. Although the Mbox application is required for some features of Remote and
Content Management to function, it does not need to be running for basic Content Management.
+ Server Roles - Within Content Management, each server takes the role of either the Master or a Member server in
a Collection (described later). Each Collection of servers must contain exactly one Master and at least one
Member in order to synchronize content between the servers.
+ Master - The Master server acts as the "source" for Content Management in a Collection; meaning that changes
made on the Master server synchronize to all of the Member servers in the same Collection. Masters are denoted