pdf_icon Download contentACCESS Manual as PDF

  1. Introduction to contentACCESS
    1. Services provided by contentACCESS
    2. Software requirements
  2. Installation of contentACCESS
  3. contentACCESS Tools
    1. Installing Virtual drive
    2. Installing the Proxy server (contentACCESSWS)
    3. Installing the Proxy web services
    4. Installing Outlook forms
    5. Legacy email archive connectors
    6. Legacy archive connector for Metalogix Archive Manager Exchange Edition (MAM EE)
    7. Legacy archive connector for Email Lifecycle Manager (ELM)
    8. Installing TECH-ARROW’s WinShortcutter
  4. contentACCESS Central Administration
    1. Central administration login
    2. contentACCESS Central Administration user interface
  5. Tenants in contentACCESS
    1. How to create a new tenant
    2. Tenant limitations
    3. How to provide access to a tenant (adding new tenant administrators)
    4. Tenant administrator invitation types
  6. General system configurations
    1. Connection
    2. User interface
    3. Users — role types, creating new users, adding user logins
    4. How to activate your license key
    5. How to create user logins to an already existing user?
    6. System administrators
    7. Login providers
    8. System
    9. Licensing
    10. Notifications
    11. Monitoring — how to find out possible misconfigurations / reasons of potential system/job failures
    12. Distributed environment in contentACCESS — Clusters
    13. Statistics
    14. How to create/configure databases — All databases
  7. Common features
    1. Databases
    2. Schedules
    3. Retentions
    4. Storages
    5. Exchange connections
    6. Importing contentACCESS configurations from files
  8. Creating new jobs in contentACCESS
  9. Jobs’ page, jobs’ context menu
  10. File Archive
    1. Introduction to File system archive
    2. File Archive settings
    3. File archive Databases
    4. File archive System settings
    5. File archive Retentions
    6. File archive Storages
    7. Root folders
    8. Aliases
    9. File archive Schedules
    10. Provisioning settings and managing access to contentWEB
    11. Configuring aliases
    12. Configuration of jobs available in contentACCESS File Archive
    13. Configuration of File system archive job
    14. Configuration of a File system restore job
    15. Configuration of File system recovery job
    16. Configuration of Remote shortcutting job
    17. Active/inactive documents in File system archive
  11. Email Archive
    1. Important settings before creating an Email Archive job
    2. Database settings
    3. Email archive System settings
    4. Provisioning settings
    5. Retention settings
    6. Shortcuts in email archiving
    7. Storing of archived emails
    8. Creating email archive schedulers
    9. User experience
    10. Exchange 2013: Mail app in OWA 2013 or on MS Outlook 2013 desktop version
    11. Exchange 2010: OWA 2010 integration
    12. Address book objects
    13. Granting access rights for mailbox users and explicit users to view the mailbox archive?
    14. Creating contentWEB users (option 1)
    15. Manage access to a mailbox archive (option 2)
    16. How the end user should log in to contentWEB (archive) over Internet?
    17. Database and store assignment in email archiving
    18. How to assign database and storage to an Exchange group?
    19. How to assign database and storage to a mailbox?
    20. How to move data from source database/storage into a second (target) database/storage?
    21. Creating Email archive jobs: archive, restore, recovery, mailbox move
    22. Email archive job
    23. Email restore job
    24. Email recovery job
    25. Mailbox move job
  12. Custom plugins
  13. Email management job configuration
  14. SharePoint archive plugin
  15. Storage replication plugin
  16. Sharing plugin
  17. Datengut plugin
  18. Email synchronizer plugin
  19. contentWEB
  20. officeGATE
  21. accessGATE Mobile
  22. Virtual drive
  23. Terms of use
  24. FAQ


The “System” page (System ⇒ Services ⇒ Documentation106.1System) consists of 5 sections: General settings, Database settings, External accessibility settings, Active directory integration settings and Cluster settings. The first two sections are configured by the setup by default.

General settings. If the checkbox is checked it will mean that the system is configured, thus connection to SQL Server database is well configured and the plugins directory is pointing to a correct folder. Until this checkbox is not checked, the contentACCESS will run in a so called “zombie” mode.

Plugins directory textbox contains the path where the processing plugins are stored on the server.


Under Database settings the system database configurations can be found, which are filled in by the setup by default. If you need to edit these settings (not recommended), click on the Configure button and fill the fields in the Database connection settings window:


By default contentACCESS is connected to the database with the credentials of the user, under whom contentACCESS is running. If you want to use SQL credentials which differ from these credentials data, then check checkbox Use explicit credentials and enter the User and Password that you want to use for connecting to database. You can also run a test connection with the Test button in the left corner of the window.

Under External accessibility settings: enter the externally accessible, fully qualified domain name for the proxy server into the Server FQDN textbox (in case the proxy is not installed, then the domain name of contentACCESS server need to be entered here). The proxy server ensures the communication between the user and the contentACCESS, and forwards user requests to the contentACCESS server. These external accessibility settings are used by the shortcut links in the Email Archive system. If you have contentACCESS Email Archive and/or accessGATE Mobile, then this setting is mandatory. In all other cases this setting is also highly recommended.


Active directory integration settings
Some contentACCESS functionalities [like contentWEB access for mailboxes or Virtual Drive] require LDAP connection. Enter the required data and the user/administrator credentials into the user name and password textboxes over which you would like to connect to the active directory. It is not necessary to fill in these fields in case that you use an online Exchange server.


Cluster settings
contentACCESS supports clustering, which enables to run contentACCESS and its jobs on multiple nodes, and thus improve performance. To adjust default cluster settings, scroll down on the System page. At the bottom of page, the following can be adjusted:


Node update interval (sec): in time intervals, which is set here (in our case in every 30 seconds) each node will “ping” the central database and will update his state in it.

Node auto logoff time (sec): if an input has not been received by a node during the time period set here, the node will automatically switch to offline.

Events retention time (sec): events (i.e. commands to run a job, added/changed/removed job configurations, changes in already set schedulers etc.) that are shared and distributed between nodes will be stored in the database during this retention time.

Events distribution interval (sec): events to be distributed between nodes are written into the system database. These events are periodically checked by each node in time periods, which is set here.

Task auto disable time (sec): if any failure occurred when running of a node (server shutdown, hardware problems etc.), the task(s) performed by this specific node (job running, retrieving contents etc.) will be automatically disabled within the time set here.

Stop task after ping failures (count): the value which is set here will determine, after how many ping failures will be the task stopped. After the ping failure count reaches this value, all the tasks running on a node will be stopped.

Node selection strategy: the administrator can select here, how the nodes will be automatically selected for processing. A node that is picked up for a task can be selected according to one of these strategies:

“First wins” strategy – using this strategy the first running node will be picked for the task.

“Balanced” strategy – by this strategy type the CPU- and memory usage, and the number of running jobs will be considered before picking up the node for a task.

Default node role: the administrator can select here the default role type of a node added to the system. It is recommended to set here “Universal”, i.e. when the node can be used both for processing and retrieving data. Later on, the role type of a node can be adjusted with navigating to System ⇒ Services ⇒ Cluster on the Central Administration ribbon, in the nodes’ grid, from the nodes’ context menu.

Enabled by default: by default all nodes are enabled (the checkbox is checked), i.e. if contentACCESS service starts up, the nodes start the processing (to run jobs, publish models etc.), too. In case the user will install contentACCESS components on next nodes, it is recommended to disable the nodes (uncheck this checkbox). The reason for this is, that a node must be fully configured before he picks up any job for processing. Enabled status of a node is marked with green color, disabled status is signed with yellow color in the nodes’ grid.

Yes No Suggest edit
Help Guide Powered by Documentor
Suggest Edit