Installation & Administration Guide Manual

13
Architecture and Deployment Options Chapter 1
Architecture
This section covers the primary architectural components of Google Apps Migration for Lotus
Notes (GAMLN) and the hierarchy used to implement and manage data migration.
Components
GAMLN comprises the following primary components. These components taken together are
referred to as the migration server.
• The Administration database. This native Notes database (Migration Administration)
contains GAMLN configuration details.
• Feeder databases. These databases are the staging areas where mail being migrated to
a Google account and documents destined for a Google Group are converted to MIME
and then transformed to the format required by the Google APIs. Feeder databases also
manage the migration of calendar and contact information. A Feeder database processes
one user at a time. When you implement multiple Feeder databases, the databases work
simultaneously. For example, if you implement 10 Feeder databases, then you can
process 10 users at one time.
• Log databases. Each migration server has at least one log database. Tasks performed in
the Migration Administration database, such as user registration, are logged to this
database. Optionally, the server can also host a log database for each Feeder that logs
migration events for each user.
• Administration Database agents.
• Check Feeders runs in the Administration database. This agent creates the Feeder
databases, and also creates a Mail-in database document in your Domino directory
for each Feeder database. If you delete a Feeder database or Mail-in database
document, this agent recreates them. This agent runs every 60 minutes by default.
• Purge Documents runs in the Administration database. This agent removes any
temporary documents that are created by other processes in the Administration
database. This agent runs daily on the server specified at the system setup level.