The following diagram shows the Journal Commander components:
The Journal Commander Core consists of three parts:
- Journal Commander User Interface
- Journal Commander Web Services
- Journal Commander Service
These are explained below.
User Interface (UI)
The main point of interaction with the administrator is through the web-based user interface. It allows access from anywhere within the enterprise by just using a web browser. It is even possible for archive migrations to be performed remotely from outside of an organization; for example, partner-managed migrations.
Using the wide range of options in the Journal Commander User Interface, the administrator can configure and manage archive migrations within an enterprise. The interface also provides at-a-glance progress monitoring, as well as reporting.
All interaction between Journal Commander and Journal Commander Modules is done through the Journal Commander Web Services. All modules communicate with the Web Services using HTTP(s). If HTTPS is to be used, there is additional configuration that needs to be performed.
The Journal Commander Service is a Windows Service which periodically executes Journal Commander scheduled tasks. These can be database maintenance tasks or other tasks that need periodic execution in Journal Commander itself.
Journal Commander has several modules that it uses to communicate with different systems to complete tasks. For best performance, modules are usually installed on the systems they interact with. Information relating to where each module should be installed is given in a later section of this document.
The following table describes each of the Modules which are available with Journal Commander:
|Active Directory Collector Module||The Active Directory Collector Module is responsible for resolving SIDs in AD and for retrieving all necessary data about a user (e.g., department) that might be necessary to filter data. It also collects information about the Exchange configuration of users (For example, on which Exchange Server / Database Availability Group (DAG) the user has a mailbox, if the mailbox has an Exchange Archive Mailbox enabled or not, and so on)|
|Enterprise Vault Collector Module||The Enterprise Vault Collector Module interacts with an Enterprise Vault Directory and is responsible for collecting all necessary metadata about Vault Stores, Archives, Items’ in each Archive and Enterprise Vault shortcuts in a mailbox.|
|Enterprise Vault Provisioning Module||The Enterprise Vault Provisioning Module creates new temporary archives for ingestion. It is able to map a temporary Archive to a User and can enable, disable, rename and ZAP existing Archives. This module utilizes EVPM to perform many tasks.|
|Enterprise Vault Export Module||The Enterprise Vault Export Module is responsible for exporting data from Enterprise Vault. It is multi-threaded and uses the Enterprise Vault APIs for accessing archived items. The exported data is stored on a Windows Network Share (SMB/CIFS). Please note that SMB 2 and SMB 3 are supported.|
|Enterprise Vault Import Module||The Enterprise Vault Import Module is responsible for ingesting data into the newly created or mapped archives in the target Enterprise Vault environment. It is multi-threaded and uses the Enterprise Vault APIs to ingest data. The data to import is read from the export location (SMB/CIFS Share). Please note that SMB 2 and SMB 3 are supported.|
|Enterprise Vault Shortcut processing Module||After migration has finished, the Enterprise Vault shortcuts in a users’ mailbox will be updated so that they refer to the migrated archive. Note: Non-shortcut items, such as calendar items, are also updated.|
|Exchange Import Module||The Exchange Import Module ingests data into a users’ mailbox. This can be the primary mailbox.|
|Metalogix Export Module||This module collects data from Metalogix Archive Manager and extracts data from that system.|
|Office 365 Module||The Office 365 Module processes data relating to migrations to Office 365. It collects metadata from Office 365, ingests items into Office 365 mailboxes, and post processes the target to remove Enterprise Vault shortcuts and pending items.|
|Native Format Import Module||The Native Format Import Module allows for data to be exported to PST file format. The resultant files are stored on a configurable destination folder (UNC path) and the files can be split at predetermined sizes. The filenames can also be customized if required.|
|Proofpoint Module||This module takes exported source environment data and prepares the data for Proofpoint ingestion.|
|EAS Module||This module collects data from Zantaz EAS and extracts data from that system.|
|PST Export Module||This module collects data from PST files and extracts the data from them.|
|Dell Archive Manager Module||This module collects data from DAM and extracts the data from that system.|
|SourceOne Module||This module collects data from SourceOne and extracts the data from that system.|