- Introduction to contentACCESS
- contentACCESS setup package
- contentACCESS components
- contentACCESS Tools
- Tenants in contentACCESS
- General system configurations
- User interface
- Users in contentACCESS
- Login providers
- Monitoring — how to find out possible misconfigurations / reasons of potential system/job failures
- Distributed environment in contentACCESS — Clusters
- How to create/configure databases — All databases
- Common features
- Exchange connections
- Importing contentACCESS configurations from files
- Creating new jobs in contentACCESS
- Jobs’ page, jobs’ context menu
- File Archive
- Introduction to File system archive
- File Archive settings
- System settings
- Root folders
- Provisioning settings and managing access to contentWEB
- Configuring aliases
- Configuration of jobs available in contentACCESS File Archive
- Configuration of File system archive job
- Configuration of a File system restore job
- Configuration of File system recovery job
- Configuration of Remote shortcutting job
- Active/inactive documents in File system archive
- Email Archive
- Important settings before creating an Email Archive job
- Database settings
- System settings
- Provisioning settings
- Retention settings
- Shortcuts in email archiving
- Storing of archived emails
- Creating email archive schedulers
- User experience
- Exchange 2013+: Mail app in OWA 2013+ or on MS Outlook 2013+ desktop version
- Exchange 2010: OWA 2010 integration
- Address book objects
- Granting access rights for mailbox users and explicit users to view the mailbox archive
- Creating contentWEB users (option 1)
- Manage access to a mailbox archive (option 2)
- Database and store assignment in email archiving
- How to assign database and storage to an Exchange group?
- How to assign database and storage to a mailbox?
- How to move data from source database/storage into a second (target) database/storage?
- Creating Email archive jobs: archive, restore, recovery, mailbox move, shortcut synchronizaion, shortcut repair
- Email archive job
- Email restore job
- Email recovery job
- Mailbox move job
- Shortcut synchronization job
- Shortcut repair job
- Public folder archiving
- SharePoint archive plugin
- Custom plugins
- accessGATE Mobile
- Virtual drive configurations
- Application settings
9.Jobs’ page, jobs’ context menu ↑ Back to Top
The Jobs page is accessible with a click on the Jobs button of the respective tab in the contentACCESS Central Administration ribbon (Email Archive ⇒ Archive ⇒ Jobs; File Archive ⇒ Archive ⇒ Jobs; Custom plugins ⇒ General ⇒ Jobs). Here you can view the list of all jobs created from a particular plugin type.
The grid contains the following columns. Each instance has an ID number, a Display name a Type and a Status. If the job is in Idle status, this means that it has completed the task, it is not running.
Next columns hold certain information about the Last start, Last duration and Next start of the job. The Progress column informs about the volume of the already processed items, while Summary gives a general overview about the processed/skipped/failed items. In Is active column can be viewed, if a job is active, or it is has been deactivated. Active jobs will run based on the schedule; the data that they are processing are accessible. Inactive (deactivated) jobs are not running (nor can be manually started); the data that they have processed are still accessible. In the Cluster node column we can check the node, where the selected job can run. The Running on column informs the user about the node, where the job is currently running. On the screenshot above we can see, that EBA’s mailbox archive_shortcutting job can be run on any available node, and is currently running on TANEWS.
Any operations to a job can be done from the job context menu, with selecting the corresponding job from the list and left click on the ellipses (…). Now we select EBA’s mailbox archive_shortcutting job from the list. With the help of this job we will demonstrate how to handle with jobs from the context menu.
The context menu of a job contains the following options:
- Clone: use this option to create a clone of an already configured job. A clone job has the same configurations as the original job that it was created from. With clicking the “Clone” option the “Clone job instance” window opens, which requires to name the job:
If a job with the same name already exists, an error message warns the user about this.
- Start: with a click on “Start” the administrator can start the job running manually;
- Stop: with a click on “Stop” the administrator stops the running of the selected job;
- Configure: required values can be configured for the job on its configuration page, which can be opened using this option.
- Show last logs: with selecting this option the user will be redirected to the monitoring page, where the last running of the selected job will be preselected, and the corresponding events will be displayed in the table of events;
- Edit: with a click on this option the Edit job dialog opens, where the user can:
✓ rename the job;
✓ change the node, where the job can be run.
- Deactivate: it is recommended to deactivate jobs which are not in use for a longer time, but very probably will be used in the future (e.g. restore or recovery jobs). With selecting this option the administrator does not permanently delete the job from the list. The deactivated job will be hidden only and it will not run according to the schedule (nor can be manually started). Running and waiting jobs cannot be deactivated.
- Delete: with this option the administrator can permanently delete selected jobs from the list; the processed data by some plugin types will not be accessible through the standard interfaces (data processed by file archive jobs will not be accessible if all file archive jobs wrote the data into the same database, and all of them were deleted; if only one job remained which wrote data into this particular database, then all data processed by all file archive jobs will be accessible. In case of email archive jobs the data will be still accessible, even the jobs have been deleted). Running and waiting jobs cannot be deleted.
- start immediately/stop: with a click on this option the administrator can start/stop the job running manually;
- refresh: click on this option and the status bar information about the progress of the job will be refreshed;
- disable/enable auto refresh: turn on/off the auto refresh of progress bar information (if enabled, the information will be refreshed in every 5 seconds)
- deactivate/activate job: use “deactivate” button if you want to temporarily cancel the job; use “activate” button if you want to restore the job among the active jobs;
- logs: with selecting this option the user will be redirected on the monitoring page, where the last running of the selected job will be preselected, and the corresponding events will be displayed in the table of events. Use this option for troubleshooting if any failure occurred during the job running;
- edit control button is used to change the name of the job and to specify the node on which the job should run.
Filtration between active/inactive jobs
A job can be either active (an active job will be started according to the configured schedule, or can be started manually), or its status may be set to deactivated (if the administrated sets a job to deactivated, it cannot be started neither by the scheduler, nor manually). On the page of Jobs the user can filter among Active/Deactivated jobs, or he can also choose to display all jobs in the list (Show all jobs).
If a job has been deactivated, it can be restored to the list of active jobs again. Select the job, open its context menu and choose Activate from the list:
Sorting between jobs
The jobs can be also sorted based on the type, status or cluster nodes where they are running. Click on the funnel () icon located next to the particular column in the grid:
Available operations from the status bar of the job
With a double click on the selected job in the list of jobs you open the configuration page to the job. On a blue background you will see the status bar of the job.
With the arrows mark () at the right side of the status bar the user may collapse or expand the progress information about the job’s running. The status bar’s last state is always stored, and the last state will be opened by navigating to the page again. The status bar of a job contains the following status bar buttons:
In the following chapters we will learn how to configure and use the contentACCESS File Archive, Email Archive, SharePoint archive, Email management. Store replication. Sharing and Email synchronization jobs.