6.20 Mobile Jobs

Before a job can be created the module must be configured Mobile Module.

A job is make up of:

Job configuration is only required for legacy Android application support and is not necessary with the current application. The following information is only necessary for supporting older application systems.

6.20.1 Core Settings Tab

The core settings tab contains information on the schedule, profile, and worker utilized for the mobile module, as well as the data expiration date.

The Data Expiration is an option to place a time stamp on data in the Retain database, which allows for ease of automation for the deletion manager. In addition, devices such as NetApp, Centera, and Hitachi HCAP may use this number to enforce hardware level protection of the stored item so that no one, including Retain, may delete the item before its expiration date. Job Expiration is not retroactive for messages in the database, and only applies to messages archived by the job that it is active for. In order to have messages with custom job or folder expiration dates properly expire, the deletion management date scope must be set to delete messages with an Expiration Date older than 1 day.

6.20.2 Notification Tab

When a job is run, the notification option allows the administrator to be emailed a summary of each running job if desired.

For notification to function correctly, the SMTP information for the desired SMTP server must be fully filled-out. How much information is required varied depending on the mail system used.

6.20.3 Status Tab

The Status tab displays the status of any currently running jobs, as well as the stats of the last completed job.

This tab is informational only for the Mobile module.

6.20.4 Next Step

Once a job has completed you can confirm the items are in the archive by checking the Search Message interface Retain Search Messages User Guide.