Difference between revisions of "Retain Google Apps"
(→Level 2) |
(→Level 1) |
||
| Line 1: | Line 1: | ||
==Level 1== | ==Level 1== | ||
| + | The Google Apps module allows Retain to archive Gmail data items from Gmail. To configure Retain for Gmail archiving, Retain needs Gmail to be configured to allow Retain access, and the appropriate information entered into Retain. | ||
| + | <br><br> | ||
| + | To Configure Gmail for Retain access, [http://support2.gwava.com/kb/?View=entry&EntryID=2340 login to the Gmail Admin Control panel to get the OathKey and OathSecret]. | ||
==Level 2== | ==Level 2== | ||
Revision as of 17:25, 2 September 2014
Level 1
The Google Apps module allows Retain to archive Gmail data items from Gmail. To configure Retain for Gmail archiving, Retain needs Gmail to be configured to allow Retain access, and the appropriate information entered into Retain.
To Configure Gmail for Retain access, login to the Gmail Admin Control panel to get the OathKey and OathSecret.
Level 2
The Google Apps job is multithreaded, with 6 folder threads and 2 message threads per folder thread. JavaMail, which is the code on which this is built, only supports 1 thread per message download, so once thread 1 has completed its download and begins transferring the message to the Server, thread 2 begins a download.
While an attachment is being downloaded, it is cached in temporary directory: /var/cache/retain-tomcat7/temp/stream. The job creates a subdirectory under that path where it stores the temp file. Once the attachment is processed, the temp file is deleted.
