Determining which components are required

To see which components you need for your Journal Commander project, click here.

Where to set up Journal Commander components

The core Journal Commander Components include the following:

  • Journal Commander Core Web Interface
  • Journal Commander Core Web Services
  • Journal Commander Core Service

It is recommended to install these components on the same server. For a production environment, this must be a dedicated server (physical or virtual). They can; however, be installed on separate servers.
Please see the Chapter “Hardware requirements for Journal Commander Core Server” in the Installation Guide for more information about prerequisites.
Journal Commander also has the following Modules

  • Journal Commander Active Directory Collector Module
  • Journal Commander Enterprise Vault Collector Module
  • Journal Commander Enterprise Vault Export Module
  • Journal Commander Enterprise Vault Import Module
  • Journal Commander Enterprise Vault Provisioning Module
  • Journal Commander Enterprise Vault Shortcut Processing Module
  • Journal Commander Exchange Import Module
  • Journal Commander Office 365 Module
  • Journal Commander Native Format Import Module
  • Journal Commander EAS Module
  • Journal Commander Metalogix Module
  • Journal Commander PST Export Module
  • Journal Commander Dell Archive Manager Module
  • Journal Commander SourceOne Module

Depending on the migration scenario, some or all of these modules have to be installed.
The following table provides a guideline on where to install these modules:

MODULE NUMBER OF MODULES NOTES
Active Directory Collector Module One per Active Directory forest Needs to be installed on a Server in the Active Directory Forest where data is to be collected from. The account that it is running under must have privileges to read Active Directory and its objects – a normal user account is sufficient.
Enterprise Vault Collector Module Minimum: One per source Enterprise Vault environment
Recommended: One per Enterprise Vault Server hosting a Vault Store.
Note: If performing an EV to EV migration, this module is also needed in the target environment to gather site settings (HTTP/HTTPS) used when running ‘Fix Shortcuts’.
There needs to be at least one Enterprise Vault Collector Module installed in the source Enterprise Vault environment. It is recommended to install this component near the SQL Server that hosts the Vault Store databases. Care should be taken when additional Enterprise Vault Collector Modules are installed. Performance might not necessarily be increased, the limiting factor is usually the time it takes to retrieve data from the Vault Store databases.
Enterprise Vault Provisioning Module One per source Enterprise Vault environment, and one per target Enterprise Vault environment. There needs to be one Enterprise Vault Provisioning Module per Enterprise Vault environment, i.e. per Enterprise Vault Directory Database. This module uses EVPM. It is recommended to install this component on the least busy Enterprise Vault server.
Enterprise Vault Export Module Minimum: One per source Enterprise Vault environment
Recommended: One per Enterprise Vault Server hosting a Vault Store.
There needs to be at least one Enterprise Vault Export Module installed in the source Enterprise Vault environment. It is recommended to install the Enterprise Vault Collector module on each Enterprise Vault server that hosts Vault Store partition data, in the source environment. This module requires the Enterprise Vault API. If this module is to be installed on a non-Enterprise Vault server, then the Enterprise Vault API Runtime needs to be installed.
Enterprise Vault Import Module
Note: This module is only required if the migration scenario includes migration to an Enterprise Vault environment.
Minimum: One per target Enterprise Vault environment.
Recommended: One per target Enterprise Vault Server hosting a Vault Store.
There needs to be at least one Enterprise Vault Import Module per target Enterprise Vault environment, i.e., Enterprise Vault Directory. It is recommended to install an Enterprise Vault Import Module on each Enterprise Vault Server where the Vault Store to import to is hosted. This module requires the Enterprise Vault API. If this module is to be installed on a non-Enterprise Vault server, then the Enterprise Vault API Runtime needs to be installed.
Shortcut Processing Module Minimum: One per target environment. There needs to be at least one Shortcut Processing Module per target environment.
This module must be installed on a Server with Microsoft Outlook 2007/2010/2013 (32 bit).
Note: An optional change in the System Configuration can change this module to use EWS rather than MAPI (however the installation of the module still requires Outlook)
Exchange Import Module
Note: This module is only required if the migration scenario includes migration to an Enterprise Vault environment.
Minimum: One per target Exchange environment. There needs to be at least one Exchange Import Module per target Exchange environment. This module requires Microsoft Outlook to be installed. It is not supported to install the module on an Exchange Server. It is recommended to install this module on a dedicated physical or virtual machine.
To improve performance, multiple Exchange Import Modules can be installed. It is recommended to start with one module and add more modules (up to one per Exchange database) if required.
Office 365 Module One per environment There needs to be an Office 365 module in order to migrate containers to Office 365. This module collects data about Office 365 mailboxes, as well as migrating data into the target container and post-processing the ingested data to remove Enterprise Vault shortcuts and pending items.
The module connects to Office 365 using the credentials specified in the Credential Editor, which is installed by the module.
Native Format Import Module One per environment One Native Format Import Module is required in order to take extracted data and create PST files. This module will split PST files at predetermined sizes and store them with a name defined by policy into a UNC accessible staging area which is defined per link.
This module must be installed on a Server with Microsoft Outlook 2007/2010/2013 (32 bit).
Proofpoint Module One per environment One Proofpoint Module is required in order to take extracted data and prepare/construct the data required for Proofpoint ingestion.
This module must be installed on a Server with Microsoft Outlook 64-bit. This module also requires a 64-bit JRE. Additional information is available in the Installation Overview.
EAS Zantaz Module One per environment One EAS Module is required on a machine which can communicate with an EASIIS Server which has access to all the required Document Repositories.
Metalogix One per environment One Metalogix Module is required on a machine which can communicate with an Metalogix Server which has access to all the required Document Repositories.
PST Export Module One per environment One PST Export Module is required, and can process a number of UNC paths to extract data from PST files which are located there.
Dell Archive Manager Module One per environment One Dell Archive Manager module is required for the source environment.
SourceOne Module One per environment One SourceOne module is required for the source environment.
Print Friendly, PDF & Email