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

7.2.Schedules

(Email Archive ⇒ Settings Schedules button;
File Archive ⇒ Settings Schedules button;
Custom plugins ⇒ General Schedules button)

How to use schedulers in contentACCESS?
Jobs in contentACCESS can be automatically triggered with the help of schedules. Schedules are used to define, when a processing task should start automatically and when the processing should end and restart again. In other words, administrator may schedule jobs which will automatically run at times which is configured in the given job’s scheduler settings. It is possible to set numberless schedulers, and then select the appropriate one when configuring an exact job. Schedules help the users to work more efficiently, without wasting their time with logging into the software and start the processing manually.

Navigate to the Schedules page from the Documentation185.1 Schedules button on the ribbon. Here click on + new option. In the Add new scheduler dialog window enter the scheduler Name, select the Type of scheduler from the dropdown list. In contentACCESS, there are 3 types of schedulers which can be set: One time, Always run and Week schedule with repeat.

One time will run only once; by this type of scheduler we specify the start date only; the job will end when it finished the processing. One time schedulers are often used by restore or recovery jobs, i.e. by jobs which are run occasionally. The schedule that we set up now will start to run on 7th of September at 6 PM, and will end once the job finished its task:

Documentation186

Always run will run always without interruption. The job which uses this scheduler type will be started immediately when it is configured and saved. With the use of Frequency in minutes function the user may set the time intervals, when the scheduler should check, if the job is running. In case of our “Non-stop” scheduler (check the screenshot below) the running frequency is set to 1 minute, so the scheduler will wake up in each minute and will check, if the job is still running. If it is running, then it will check the running after 1 minute again; if it is not running, then the job will be started again. This scheduler type is typically used by archiving from journal mailboxes.

Documentation187

Week schedule with repeat will run at the same hours every week, repeatedly. In the scheduling tab click on the fields to set the days and hours, when the processing should start. One cell will mark one hour. By using the Running frequency in minutes option the user may set the time intervals, when the scheduler should check, if the job is running. If running frequency is set e.g. to 5 minutes, then the scheduler will check in every 5 minutes, if the job is still running. If it is running, then it will check the running after 5 minutes again: if it is not running, then the job will be started again. It is worth to use this option, if the processing should run continuously, e.g. from morning to evening, and new tasks are continuously added that should be processed. If we check the Run only once per interval checkbox, then the running frequency will be automatically deactivated, and the job will run only once in this time period. It is recommended to run a process once in an interval, if the processing should be performed e.g. at the end of each working day. With checking the Stop job at interval end checkbox the user may stop a job after the time interval, which is set. Never mind, if the processing has not been finished yet, the job will be forcibly stopped and it will be started again according to the calendar settings. The red color of the Add new scheduler’s cells mark the time intervals, when the job is stopped.

Our “Every night” scheduler (its setting can be viewed on the screenshot below) will run the job from 7 PM till midnight, will stop processing at midnight, nevertheless the process is finished. It will run only once in this interval. We can use a similar scheduler to archive the old company documents. It makes no sense to select running frequency in this case, because during the night nobody will add new files to archive into the file location.

Documentation188

Setting the Running frequency in minutes option might be useful when the user is archiving from an Exchange journal mailbox for example, or from any location, where the tasks to be performed are accumulating continuously during a time period. If the job processed all items, the schedule should also check periodically, if there is anything new to archive. The “Every working day” scheduler (on the screenshot below) is set to process the email records from 7 AM till 6 PM. The first archive process will run from 7 AM until it has finished all current tasks, and the scheduler will check in each 5 minutes, if any new tasks (email records) were added to process. The archiving will end at 6 PM each day, nevertheless there is something left unfinished. A scheduler similar to this may be set to archive journal mailboxes on the Exchange:

Documentation189

This scheduler type is often used to run provisioning jobs, too.

If the user would not like to end the processing at 7 PM, he should uncheck the “Stop job at interval end” option.

Tip: When the user is setting a desired time range, or just moves with the mouse over the selected time range, the Weekmap scheduler highlights this time range and displays the exact start and end times beneath the calendar:

cACCESS 2.9 doc 92

From the scheduler’s context menu, with a left click on ellipsis (Documentation189.1) it is possible to edit or delete this configuration if any modifications must be implemented. The scheduler type and its description can be also viewed in the grid.

Documentation190

Yes No Suggest edit
Help Guide Powered by Documentor
Suggest Edit