Difference between revisions of "Retain Migration"
(→Publisher) |
(→Viewer) |
||
Line 59: | Line 59: | ||
====Viewer==== | ====Viewer==== | ||
*The "Viewer", which provides a user interface to view the data in the published local archive database. The Viewer is able to export the archive data into PDF format or into a PST file. | *The "Viewer", which provides a user interface to view the data in the published local archive database. The Viewer is able to export the archive data into PDF format or into a PST file. | ||
− | *The database is a SQLite database. SQLite can be downloaded for free. | + | *The database is a SQLite database. SQLite can be downloaded for free. The db management software that development uses is SqliteBrowser. |
=====Sample SQLite Query===== | =====Sample SQLite Query===== |
Revision as of 20:42, 21 October 2016
Contents |
Exchange Plugins
This topic includes the Retain plugin for the Outlook client and the Retain plugin for Outlook WebAccess.
GroupWise to Exchange Migrator
This topic covers the migration utility built into Retain. This is not to be confused with the Migration Toolkit. The GroupWise to Exchange Migrator migrates GroupWise mail from the Retain mailbox to Exchange.
GroupWise Personal Archives Migrator (PAM)
The PAM utility moves items from a user's personal GroupWise archive, which is the GroupWise client archive feature, into the Retain archives.
GroupWise Plugins
This topic covers the Retain plugin for the GroupWise 32-bit Windows client and the Retain plugin for GroupWise WebAccess.
Messaging Architects Migrator
The Messaging Architects Migrator moves the archive data from a Messaging Architects archiving system over to Retain.
Migration Toolkit
The Migration Toolkit consists of a few feature sets:
- Migrate GroupWise users from eDirectory to Active Directory.
- Migrate items from GroupWise mailboxes to Exchange.
- Create PST files from a GroupWise personal archive (the GroupWise client's archive feature).
Export PST
This tool was built for a specific scenario. Development for this tool is currently on hold. Bug - http://bugzilla.gwava.com/show_bug.cgi?id=2437
This tool will do a mass export of the Retain archive data to PST. The only option for data selection currently is 'date range'. You can
PST Importer
The PST Importer imports the data from a PST file into Retain.
Retain_Publisher Publisher
The Retain Publisher consists of three different components that work together:
Publisher
- The "Publisher", which extracts data from Retain mailboxes into a local archive database for portability. The Publisher component will not display any information.
- Once the Publisher has been installed and the program is started you will be asked for information about the Retain Server you would like the Publisher to extract data from.
-Retain Server Information- provide the Retain Server address and a user account with the rights to publish messages
- Server address - This is the IP address or DNS for the Retain Server the Publisher will connect to
- Username and Password - This is a user within Retain. The Publisher will use this to login
- Save username and password - This will save the username and password for future use
- Advanced View - Checking this box will allow you to add 'https' and/or a port to the Server Address
-Publishing Location- Select a location to publish the archived messages
- Green plus button - This allows you to create a storage path for the archive being created
- Bundle the Viewer application with this archive - Check this to include a copy of the Viewer in the archive being created
- Require password to view the archive - Check this if you want to password protect the archive being created
- Enable redaction - Check this to enable redaction. You will have to enter and confirm a redaction password before you can continue
(If there is already an archive that has been created in the archive location selected you will be asked to replace, append or delete it) -Address Book- Choose the domains, post offices, and mailboxes to publish
- Dredge from Exchange journaling mailbox - Check this if your dredging against Exchange journaling
- Domain / PO / User - Expand and select entire domains, post offices or or single users
-Query Form- Select query for filtering data
- Use custom query - Check this if you want to archive messages with specific criteria only
-Folder Structure and Date Range- Select options for retrieving folder structure. If desired, you may publish messages from a specific time period
- Folder Structure - Choose weather or not to include Non-emtpy folders or All folders
- Date Range - Filter items by creation date (creation date range is required if any query is selected)
Viewer
- The "Viewer", which provides a user interface to view the data in the published local archive database. The Viewer is able to export the archive data into PDF format or into a PST file.
- The database is a SQLite database. SQLite can be downloaded for free. The db management software that development uses is SqliteBrowser.
Sample SQLite Query
A customer had published a set of data but had made a mistake in the query, so he only got partial data. He sent that data to the legal staff for processing and they had redacted out the items that they didn't need. He then realized that the data wasn't full, so he ran another publish job with the help of Support and got the full data. Because the legal staff had invested so many hours in processing the first set of data, they did not want them having to process data they had already completed. Using a SQLlite database management software, Support pulled in both databases and ran the following queries to remove the processed data from the second (full) data set so that the legal staff would only have to process the difference:
- delete from messageProperty where messageProperty.messageId in(select Id from Orig.message);
- delete from message_recipient where message_recipient.messageId in(select Id from Orig.message);
- delete from message where message.Id in(select Id from Orig.message);
Indexer
- The "Indexer", which indexes the item content in the published local archive database.