Google Apps Migration for Lotus Notes Installation & Administration Guide • Google Apps for Business • Google Apps for Education
Copyright, Trademarks, and Legal Google, Inc. 1600 Amphitheatre Parkway Mountain View, CA 94043 www.google.com Part number: IAG_GAMLN_R40_12 October 22, 2014 © Copyright 2010 Google, Inc. All rights reserved.
Software Corporation for their prior contributions. Google Compliance Policies Notice: Google assumes no responsibility in connection with the Compliance Policies lexicon-filtering feature, including any failure to recognize credit card or social security numbers that do not follow an applicable pattern as established in Postini’s systems or any failure to encrypt a credit card or social security number.
Google Apps Migration for Lotus Notes Installation & Administration Guide
Contents Introduction.......................................................................................................... 7 About this guide..................................................................................................... 7 Chapter 1: Overview............................................................................................ 9 General Features................................................................................................... 9 Mail Migration ..............
Chapter 4: Administration Tools...................................................................... 75 Change a User or Database Status..................................................................... 75 Set Migration Cutoff Dates .................................................................................. 76 Toggle Migration Processing Status for Document Types .................................. 77 Disable Roaming Status ..........................................................................
Introduction About this guide This guide is provided to help you understand and use Google Apps Migration for Lotus Notes (GAMLN). Important: Before you install GAMLN, make sure you read the file readme.txt included with the software. The file contains important compatibility information that may impact your installation.
How to provide comments about this guide Google values your feedback. If you have comments about this guide or suggestions for its improvement, please send your feedback to: enterprise-apps-doc-feedback@google.com In your message, be sure to tell us the specific section to which your comment applies. Thanks! Disclaimer for Third-Party Product Configurations Parts of this guide describe how Google products work with Lotus Notes and the configurations that Google recommends.
Overview Chapter 1 Google Apps Migration for Lotus Notes (GAMLN) is a native IBM Lotus Notes application that lets you migrate Notes users and Mail-In databases to Google Apps. Migration includes mail, calendars, personal contacts, and groups. You can also migrate data from a Lotus Notes discussion database or document library to a Google Group. You install GAMLN on an IBM Lotus Domino server running Microsoft Windows.
The following Notes mail features are converted to corresponding Gmail features automatically: • Notes mail addresses are converted to Gmail addresses. • Notes mail folders are mapped to labels in Gmail. • The yellow Gmail star is applied to mail that has a Notes follow-up flag. Additionally, the following GAMLN features help you fine-tune and monitor your mail migration: • A folder-inclusion or folder-exclusion list lets you manage which mail is migrated for each user.
• The system only supports events that are added to a Notes calendar through a supported Notes or Web client. Migration of events that have been created by third-party software, including custom Notes applications, is not supported. • Resource bookings are only supported where the user has booked the resource from their own Notes calendar. Bookings added directly into the Domino Resource Reservations database are not migrated.
Parallel processing Each migration server can process 10 users/databases concurrently. Migration performance depends on a number of factors. For example, the system migrates a maximum of one message per user/database per second, so: - 1 server processing 10 users = max 10 messages processed per second. If each of those 10 users has 4,000 messages, the system could migrate those messages in 4,000 seconds, or 1.
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.
• Feeder Database Agents. • Migrate runs in each Feeder database to carry out the data migration for each user or database that has been registered and activated in the Administration database. This agent runs every 30 minutes. The following diagram illustrates how the components work together.
For a full discussion of global settings, see “Configure the Administration Database” on page 30. Site Settings At the second level of the hierarchy, you define site settings, which include: • Site location • Site administrators • Migration start date for this site • Mail servers and the migration server for the site • Default settings for each newly registered user/database You must define at least one site profile before migration can begin.
Single Site If you are migrating data for a single location, you can install the system on either the mail server for that location or on a dedicated server. We recommend installation on a dedicated server so that mail-server performance is not degraded. In a single-site deployment, you install only a single instance of the Administration database. Multiple Site If you are migrating data for multiple locations, you can install a separate instance of the Administration database at each location.
Single Site, Single Mail Server, Multiple Migration Servers Migration Server Administration Database Feeder Database Domino Mail Server Google Apps Migration Server Administration Database Feeder Database Note: In this scenario: Each migration server has a unique version of the Administration database (not a replica). Each migration server migrates a unique set of users. Each migration server requires a site document with a unique name.
Multiple Sites, Replicated Administration Database Domino Mail Server Domino Mail Server Migration Server Migration Server Administration Database Feeder Database Google Apps Feeder Database Domino Mail Server 18 Google Apps Migration for Lotus Notes Installation & Administration Guide Administration Database
Installation Chapter 2 Important: Before you install GAMLN, make sure you read the file readme.txt included with the software. The file contains important compatibility information that may impact your installation. In order for you to successfully install and use Google Apps Migration for Lotus Notes (GAMLN), it is important that you carefully follow the guidelines provided here.
• Administrator access to mail files. We recommend that you use a generic Google Apps account with administrator privileges for your domain for the purposes of the migration and not a real user account. • Microsoft Core XML Services 6.0. If your version of Windows does not include Core XML Services 6.09, you can download it at: http://www.microsoft.com/downloads/details.aspx?FamilyID=993c0bcf-3bcf-4009-be2127e85e1857b1&DisplayLang=en Microsoft Core XML Services 6.
2.
3. If this is your first project: • Click the Create project button. This will create a new project called API Project • Click API project > Billing & settings. • Click the Rename project button, and change the name to gamln. If you have created projects previously: • Click on the < Projects link on the left hand side of the screen, then click the Create project button. • Enter a project name of gamln. It may take a few seconds for your project to be created.
10. Record the following two values from the top right hand side of the screen: • CLIENT ID • CLIENT SECRET The location of these values are marked in red in the image below: 11. Select APIs & auth > Consent screen. 12. Complete the EMAIL ADDRESS field by selecting your domain super administrator account and enter gamln into the PRODUCT NAME field as shown in the screenshot below: 13. Click the Save button to save your changes.
Enable API Access To enable API access in Google Apps, do the following: 1. From your Google Apps control panel, go to Security > API reference 2. Enable API access in the right hand pane. Configure your Domain Consumer key 1. From your Google Apps control panel, go to Security > Advanced settings and select Manage OAuth domain key from the right hand pane. 2. Enable your consumer key and copy your OAuth consumer secret to a safe place. You will need this later. 3.
Add API Scopes Before migrations can be allowed, you must grant the domain’s consumer key access to a number of Google APIs. This is done by adding a set of API scopes to the Manage OAuth client access page in the Control Panel. To add relevant API scopes to your Google Apps configuration, do the following: 1. From your Google Apps control panel, go to Security > Advanced settings and select Manage OAuth Client access from the right hand pane. 2. Enter your domain name into the Client Name field. 3.
These settings are found in Server Document > Server Tasks > Agent Manager. Check the Mail Server Field on your Migration Servers In your migration server’s Server document, confirm that the Mail server field’s Server document > Basics > Server Location Information section matches the Server name field Server document > Basics. Check the Number of MAIL.BOX Files on Each Server You need to have at least two MAIL.
4. In each server configuration, click the Router/SMTP tab, then click the Basics tab. 5. Set Number of mailboxes to 2 or more to ensure optimum performance during migration. Set Your Migration Servers’ MIME Outbound Settings Set your servers’ MIME conversion settings so that Notes rich text is converted to HTML: 1. Open Domino Administrator. 2. Click the Configuration tab, then click Server/Configurations. 3. Find the server configuration for each migration server.
4. Click the MIME tab, click the Conversion Options tab, then click the Outbound tab. 5. Set Message content to from Notes to HTML. Optimize Console Output To reduce console output as email is routed through the Feeder databases, you should add the following line to the Notes.ini file for each mail server and migration server: converter_log_level=10 Set Trusted Servers The servers on which you install the migration server need to have trusted access to your mail servers.
• Designer access to all mail databases that you want to migrate • Create database rights on the migration server. • Editor access to the Domino Directory, with Create document rights and the NetModifier role. • Must be listed as an Administrator on all mail and migration servers. • Must have the rights to run restricted agents on all migration servers.
When creating the database you need to select Show Advanced Templates when specifying the template to use. Create the administration from the template using the Notes menus. If you simply copy the NTF file to an NSF file, the monitoring agents will not run, and the ACL will not be configured correctly. Configure the Administration Database ACL Configure the Administration database ACL as described below. Global Administrators Global administrators are handled internally by the system setup profile.
Document Security The following table details the security that is automatically applied to each type of document in the Administration database. Document Editors Readers Global setup profile [Admin] All users Site documents [Admin], Site administrators All users Migration profile documents [Admin], Site administrators, owner All users User passwords [Admin], Site administrators, owner [Admin], Site administrators, owner Notes Editor rights for the [Admin] role are implicit.
Configure the General tab as described below. Status Set this field to Enabled so the crawl-and-feed process can run. If you set this field to Disabled, the crawl-and-feed process does not run. The setting here overrides any site-level settings. Administrators Select the users and groups you want as administrators. The default value is LocalDomainAdmins. If you are not a member of LocalDomainAdmins, add your name here so you can complete the configuration process and have administrative access later.
takes the group name, converts it to lowercase, and appends @.com to create the group address. Note: An invalid formula will result in name conversion failures during migration. Click Check Formula to validate your formula. Sites Tab Before you can proceed to the next step, you must add a site profile. Click New Site to create a new site profile. See “Configure Your Sites” on page 38 to learn how to complete a site profile.
Domain name Enter the name of the primary Google Apps domain to which you will be migrating data. You can find the primary domain name in the Google Apps Control Panel > Domain settings tab > Domain names tab > Primary domain field. OAuth consumer secret Enter your domain’s consumer secret that you recorded earlier. This value can be found in Google Apps Control Panel > Advanced Tools > Manage OAuth domain key. Domain administrator email address Enter the full email address of your domain administrator.
3. Press the Click here to complete the authorization process link in the ‘Authorization’ section of the Apps Domain tab. You will see the following dialog box. 4. Press the Get Authorization Code button. 5. Log in to your Apps domain using your Super Administrator credentials if prompted. You will see the following page. 6. Click Accept. You are redirected to the following page.
7. Copy the code from the web page into the Authorize dialog box as shown below. 8. Press the Get Access Token button. A message in the dialog box indicates the token has been obtained.
9. Press OK to close the dialog box. Check the Apps Domain tab and ensure that you have a valid Access token. This can be seen highlighted in yellow in the following screen capture. 10. If you do not see an Access token valid from date, an error occurred during the authorization process. Check the Migration Log and your Domino server console for more information.
Calendar migration test mode allows you to test your configuration prior to running a full production migration of your Lotus Notes calendars. In test mode, the system applies a random identifier to each copy of an event. Once you have verified the setup, you can wipe the Google Calendars and move onto production migration avoiding the possibility of conflicts.
Each document is checked to verify that it has at least the From, SendTo, and Body fields. If any of these fields is missing, that mail is excluded from the migration process. Site level custom settings/User level custom settings The custom-settings fields let you expose an additional tab on your Site and Migration profiles. The tabs contain a custom sub-form where you can place your own fields and controls to extend the functionality of the migration system.
General Tab Configure the General tab as described below. Site status Set the status to Enabled or Disabled as required. This setting along with the Migration start date for this site setting allows you to control when users from this site are migrated. Note: The value you chose for Global status in the General tab of the administrationdatabase setup form overrides this setting (see “Status” on page 31 for reference). Site time zone Select the geographic location of the site.
Migration start date Enter the date on which you want migration to begin. Leave this field blank to have migration begin immediately upon completion of the site profile. Number of Feeder databases Enter the number of Feeder databases you want to use for this site. The maximum is 10. Feeder databases are created automatically by the Check Feeders agent in the Administration database. For each Feeder database, the system creates a corresponding Mail-in database document in your Domino Directory.
Gmail Profile Defaults Tab Configure the Gmail Profile Defaults tab as described below. The values you set here become the default values for each new profile that you register for migration to a Google Apps account. You can change the values for individual users and mail-in databases after registration if required.
• Calendar processing status (and the optional cutoff date) • Contacts/groups processing status This field is used to specify whether end users can change the default values that are set at the site level. Set to Yes to allow users to set these values for themselves. Set to No to prevent users from modifying the default values. Allow users to select archives Set to Yes to allow users to add lists of archived databases to their migration profiles.
• All folders: Default setting. Migrates mail from all folders. • These folders only: Migrates mail from only the folders you specify in this field • All folders except these: Migrates mail from all folders except the ones you specify in this field Note: Mail in users’ trash is not migrated regardless of which option you choose. Users must undelete any mail in their trash that they want to migrate.
Set to No to refrain from migrating contacts and groups data. Note: For non-roaming users personal contacts and groups can only be migrated if your users have synchronized their personal address book with their mail files on the server. Refer to your Domino help for more information on how to synchronize address books in your environment. A roaming user’s contacts and groups are migrated from the server based address book that is specified in the user’s Person document.
If you select These folders only or All folders except these, then you must enter the full hierarchical names of the folders. Use a backslash “\” to separate each folder level and separate folder names with a comma. Migrate junk mail Set to Yes to migrate mail from the Notes Junk Mail folder. Set to No to exclude Junk Mail from the migration process.
Start mail Keep the default value, Migration started, to have the system send an email notification when a user’s migration has started. Leave the value blank to prevent the system from sending an email notification when a user’s migration has started. Completion mail Keep the default value, Migration completed, to have the system send an email notification when a user’s migration has completed.
Network Tab Configure the Network tab as described below. Delay between HTTP posts If you experience HTTP locks or service-unavailable responses from Google Apps, you may need to increase this value to introduce a delay between successive posts. For optimum performance, keep the default value of 0.0. For additional information, see “My migration quits with the following error in the Domino server log: Agent printing: ** Feed terminated: Microsoft Http / Network error occurred **” on page 97.
Network time-outs You may, on occasion, experience time-outs between your servers and the Google servers. The normal behavior in these circumstances is for the system to exit early and wait for the next scheduled run. To maintain normal system behavior, leave this set to the default value of On. If you wish to ignore time-outs and have the system wait for the Google servers to respond, set this to Off. You should only do this, however, if you are experiencing regular time-outs.
When this feature is enabled, failures encountered during migration to the Google servers are also captured and stored as exception documents on the migration profiles. Enable this option only to assist with the resolution of a problem, because it has a detrimental effect on performance. Set to Disabled to prevent the system from logging document-level events.
Handling of email removed from Notes inbox It is possible in Lotus Notes to remove a message from the inbox without placing it in a Notes folder. The message is then visible in the All mail view in Lotus Notes. This option allows you to control how this message is filed at migration time. The default is to show the message in the Gmail inbox, but you can also specify a Gmail label under which to file the message.
Support for each Google Apps service also depends on which method you use for registration: Single database By server From Directory Import from file User mail file Apps Account, Vault.
Status Hold Description An administrator has suspended the migration for the user or database. When the hold is released, the migration resumes from the point at which it was suspended. Register Single Database This section describes how to register a mail database for migration to an Apps Account. The end of this section describes the differences between registering for migration to an Apps Account and registering for migration to a Google Group. To register a single database for migration: 1.
3. Choose Register > For Apps Account > Single Database. (instead choose Register > For Groups Archive > Single Database at this stage if you want to migrate to a Google Group). 4. In the User field, click the + icon. 5. Select a server, and then the mail database you want to register. Note: 54 You must make sure that you choose a server that you have added to one of your site documents.
6. If the correct Gmail username is not already displayed, enter the username in the Values column. 7. In the Migration type field, select: • Mail to migrate to the Google Apps account • Vault to migrate directly to Google Apps Vault. Note: If you migrate to Vault, you cannot migrate calendar or contact information. 8.
14. If you want to migrate archived databases, click the Mail Archives tab. 15. In the Archive databases field, click the + icon, then select the server and databases you want to migrate. 16. In the Group archived mail field, select: • Yes to show all mail from the Notes archive databases in the Notes Archive label in Gmail. Folder names are retained and converted to labels beneath the Notes Archive label. • No to treat Archived mail the same as mail from the primary mail database.
3. Choose Register > For Apps Account > By Server or Register > For Groups Archive > By Server as required. 4. In the Server field, click the + icon. 5. Select the server you want, then click OK. 6. In the Folder path field, enter the name of the folder that contains the users/databases you want to register. 7. In the Recurse subdirectories field, select Yes if you want to also register users/databases in subdirectories of the folder you named above. 8. Click Register Now.
To register users and mail-in databases from a file: 1. Create a text file that includes the names of the users and mail-in databases that you want to import into the Administration database. Each name should be on its own line. The users and mail-in databases must exist in the Domino Directory. Each name must refer to a Person or Mail-In Database document in the Domino Directory. You can enter the name in Notes or Internet Address format. 2. Open the Administration database. 3.
4. Delete the GAMLN template files from the server. 5. Delete the “Gmail Feeder ” Mail in database documents from your Domino directory where matches the Site name given to the migration server you are uninstalling. 6.
Google Apps Migration for Lotus Notes Installation & Administration Guide
Installation 61
Google Apps Migration for Lotus Notes Installation & Administration Guide
Managing Your Migration Chapter 3 After you have created the Administration database, configured your site, and registered your users and databases, you are ready to begin the migration process. Before you start migration, you should assess how much information will be migrated to Google Apps for your users. Gathering Pre-Migration Statistics GAMLN provides a feature that lets you estimate how much information will migrate to Google Apps.
You must have access to the source mail files and databases and must be an allowable author of the migration profiles to use this feature. If you do not have the required level of access, the system logs the event and moves on to the next selected profile. Only profiles with “Draft” or “Invited” status are shown in the Notes Statistics views. The figures in this view are meant to be used as estimates only and may not reflect the final migration counts/size.
4. Click Calculator. The following dialogue appears: 5. Complete the table as follows: a. Select the appropriate site. The calculator uses the migration rates from the site you choose. b. Select the number of migration servers you have at the site you chose. c. Select the number of Feeders per migration server. d. Select how many hours per day you will allow migrations to run. e. Choose a MIME allowance.
The values are estimates only and you should always monitor the actual migration rates and migration times and compare actual results with the results predicted by the calculator. Where you have more than one site, you should run the calculator for each site separately to take into account differences in local bandwidth availability and network and server performance. You may see migration times must faster than those presented where Http compression is used during the migration process.
2. Select the users to whom you want to send invitations, then choose Send > Invitation. 3. Click Choose mail template.
4. Select Invitation to migrate, then click OK. The invitation form is populated with information from the mail template. It also includes buttons that provide options for users to synchronize their address books, decrypt email, and start the migration. 5. Press the Invite Users button. Each user you selected is sent an invitation email with a link to the respective user profile in the Administration database. Each of those mail profiles moves to the status of Invited.
• Migration completed • Migration exited early Create a Mail Template To create a new template: 1. Open the Administration database. Go to the Mail Templates tab on the System Setup profile. 2. Click New Email Template. 3. Complete the settings as follows: Setting Value Title Enter a title for the template. This value appears in any list of template choices. Include link to user profile Set to Yes if you want the email based on the template to include a link to the user’s profile.
Setting Name to user Value Select the format for the name following the greeting: • First name only • Full name • None Subject Enter the subject for the message. Content Enter the body of the message. This can include rich-text elements and attachments. Sign-off Enter or select a closing for the message (for example, Regards or Sincerely). 4. Click Save, then click Exit. The template is now available in any list of template choices, including the Send > Invitation and Send > Email commands.
To find the field names for the Site profile document: 1. Right-click the Site profile document, then click Document Properties. 2. Click the Fields tab. Email Restrictions If you want to send email from the system to more than one user at a time, each of those users must belong to the same site. You must be identified as an administrator for a site in order to use the system to send email to users who belong to that site.
The following table outlines the different statuses applied to each type of document. Status Calendar Contacts Mail Description Unprocessed Yes Yes Yes Document not yet processed by the migration system. Sent to repository N/A N/A Yes Mail has been routed to Feeder database for further processing. Repository error N/A N/A Yes An error occurred when sending this email to the Feeder database. The system will try again later. Migrated Yes Yes Yes Document sent to Google Apps.
To migrate a user or database that was successfully migrated and moved to Completed status: 1. Open the Administration database and select the Complete view. 2. Double-click the profile that you want to reprocess. 3. Click Migrate Again. This action sets the migration profile back to Draft status. Once activated all previously migrated content will be migrated again. This action is not the same as just setting the profile back to Active, which migrates previously unprocessed content only.
• The size of the Feeder databases. These databases can become large when you are migrating large amounts of information. Check that the server has been able to compact these databases, and if not, compact them manually, or delete them when they are empty. The system automatically creates new Feeders within one hour. • The indexes of the migration status views can become quite large, increasing the original mail file/database size by as much as 35%.
Administration Tools Chapter 4 You have administration tools available at the view level, as well as a number of agents you can run from the Actions menu. View-Level Actions Agent Actions Change a User or Database Status You can override the system workflow and change the status of one or more users or databases. To change profile status: 1. In the Administration database, open one of the Migration Profile views and select one or more profiles, or open an individual profile.
2. Choose Admin > Status Override (or Status Override if you have opened a profile). 3. Select a new status. 4. Click OK. Set Migration Cutoff Dates You can use this option to set migration cutoff dates for mail and calendar documents. To set migration cutoff dates: 1. In the Administration database, open one of the Migration Profile views and select one or more profiles. 2. Choose Admin > Set Cutoff Dates. 3. Select Yes for each type of document for which you want to set a cutoff date.
To clear migration cutoff dates: 1. In the Administration database, open one of the Migration Profile views and select one or more profiles. 2. Choose Admin > Set Cutoff Dates. 3. Select Yes for each type of document for which you want to clear the cutoff dates. 4. Leave the date field blank. 5. Click OK. Toggle Migration Processing Status for Document Types You can use this option to toggle migration processing status for mail, calendar, and contact/ group documents for specific users and databases.
Actions-Menu Agents You also have access to the following agents from the Actions menu. To access the agents, choose Actions > Admin > . Running the agents from the Actions menu does not override any site-level default schedules. Check Feeders Runs the Check Feeders agent. By default, this agent runs hourly on each migration server. Purge Documents Runs the Purge Documents agent. By default, this agent runs on each migration server at 1:30 A.M.
Check Network Runs the Check Network agent. This agent allows you to test that your Domino server can communicate with Google servers. Refer to the Migration Log database for the results of the network test. Refresh Access Token Forces a refresh of the access token needed to allow the system to access your domain. Use this action only if advised to do so by Google Support. Import from File Allows you to register users and mail-in databases from a text file with the migration system.
Google Apps Migration for Lotus Notes Installation & Administration Guide
Domino Directory Migration Chapter 5 Provisioning Domino Groups and Resources GAMLN allows you to create groups and resources in Google Apps from the groups and resources you have stored in your Domino Directory. Provisioning Groups The following actions can be performed only from a Notes Client for Windows. 1. Open the Directory Migration – Groups view. 2. Press Load Groups. Choose which group types to load from the Domino Directory when prompted and press OK.
3. After the groups have been loaded, select them and click Provision Groups. These groups are created in your Apps domain. Groups that are successfully created in Apps are shown with a green flag. Failures are shown with a white flag. For more information, refer to the Migration Log database. Provisioning Resources It is important that you populate the GAMLN Administration database with resource information before you start to migrate your users’ calendars.
4. After the resources have been loaded, select them and click Provision Resources. These resources are migrated to your Apps domain. Resources that have been successfully created in Apps are shown with a green flag. Failures are shown with a white flag. To find out why a particular resource creation has failed, open the Migration Log database and locate and expand the Provision Resources category.
• 84 Google Calendar resources are populated from event information that is held in your users’ calendars. The system does not migrate events that have been added directly into the Domino Resource Reservations database.
Extended and Mixed-Character Support Chapter A To configure the system to support extended character sets (such as Japanese as defined in ISO-2022-JP): 1. Open the Domino Directory, then open the Configuration > Messaging > Configurations view. 2. Edit the configuration documents that apply to your mail servers and to any server that is hosting the administration and Feeder databases, as described in the following steps.
3. Click the Basics tab. 4. Set the International MIME Settings for this document field to Enabled.
5. Click the MIME tab, then click the Settings by Character Set Groups tab. 6. Select the For outbound message options below use all possible choices (Advanced users) check box. 7. Use the MIME settings by character set group menu to select the character set group you want. 8. Under Outbound Message Options, set Header and Body Encoding to Quoted Printable. 9. Save your configuration document. 10.
Google Apps Migration for Lotus Notes Installation & Administration Guide
Working with the GAMLN API Chapter B The Feeder databases include a script library, Custom Events, that includes routines designed to let you interact with the GAMLN API. The routines are described below. PostFinaliseUser (userProfile As NotesDocument) Called after all email, calendar, and contacts/group entries have been successfully migrated to Google Apps, and the mail profile has the status of Complete. Passes in the user’s mail profile.
Function QueryMigrateUser (userProfile As NotesDocument) As Integer Called for each user prior to migrating content to Google Apps. Return False to skip the user. Return True to let processing proceed. Passes in the user’s mail profile. Function QueryMigrateUsers () As Integer Called just before the Feeder begins to process its first database. Return False to abandon the operation. Return True to let processing proceed.
Custom Settings Chapter C The system includes two custom sub-forms. You can use these sub-forms to add additional fields and programming logic to the site and migration profiles. You can also use the subforms in conjunction with the Provisioning API to present values that are derived from your own custom API code. Using the sub-forms requires that you are an experienced Notes developer. By default, the Custom Settings tabs are not displayed.
Google Apps Migration for Lotus Notes Installation & Administration Guide
Troubleshooting Chapter D Logging GAMLN uses the following types of logging: The migration agents that run in the Feeders write summary and statistical information to agent log documents in the Administration database and to each migration profile. Processing information for each profile can be viewed by using the Migration Events action at the view level or by selecting the Activity Log tab on the profile. 1.
• Optionally shown as error events in the Detailed Event logging database that is used by each Feeder Error types Initial communication errors Before the system attempts to migrate any content, it performs a check against the domain to verify that GAMLN and the Apps domain have been configured correctly. If this check fails, no users are migrated. The most common causes for failure are: 1. Invalid scope URLs added to the Apps domain administration panel 2.
• Cannot remove mail quota • Database open/access errors (insufficient rights to source file or server trust issue) • Access checks failed (signer does not have rights to source file) • Group does not exist Migration errors A migration error occurs when a single Notes document (mail, event, contact, group, or application document) cannot be migrated successfully. In this case, the error count on the migration profile is incremented, and the original document is marked as a Migration Error.
General troubleshooting I am seeing the following entry in the Migrate Users logs, but I know that the Provisioning API is enabled for my domain. What can this mean? ** Feed terminated: Provisioning API may be disabled ** You may see this error if you are attempting to migrate users with an Administrator account which has not yet logged into Google Apps and accepted the Terms of Service.
My migration quits with the following error in the Domino server log: Agent printing: ** Feed terminated: Microsoft Http / Network error occurred ** It is not uncommon to see occasional HTTP-connection timeouts. When these occur, the next migration run resumes from the point at which it left off. You can set the system to ignore network time-outs. See “Network time-outs” on page 48 for more information.
I migrated a user’s mail to a test account, and now I want to migrate it to his real account. What do I need to do? 1. Change the user’s Gmail user name in his migration profile. See “Register Single Database” on page 52. 2. Use the Migrate Again button to reset all of the mail in that user’s mail file. See “Resubmit Data to Google Apps” on page 72. I have a user whose status seems to be stuck in Active. 1. Open the mail database for that user. 2.
Index A about guide audience 7 contents 7 find latest version 7 send comments 8 administration database 13 ACL 29 create 29 administration tools agent actions 75 change user status 75 clear migration cutoff dates 77 system-integrity checks 78 toggle document processing status 77 view level 75 agents Check Feeders 13 API routines 89 architecture administration database 13 component interaction 14 components 13 data flow 14 feeder databases 13 global settings 14 site settings 15 users 15 administration data
O overview calendar migration 10 contacts and group migration options 11 features 9 P pre-installation prepare Domino servers 25 S site settings 15 sites configure 38 supported Google Apps editions 19 system requirements 19 system-integrity checks 78 T troubleshooting 93 U uninstall 57 users activate by invitation 66 activate for migration 66 change status 75 open mail database 79 register 50 status during migration 51 100 Google Apps Migration for Lotus Notes Installation & Administration Guide
