How to setup the MOSS 2007 Protocol Handler for Lotus Notes to search multiple Domino Databases. Part 2 of 3
So you’ve finished the Domino side, time to work on the MOSS Side.
Check and double check the following permissions are set properly. If not, you can cause yourself a lot of unneeded frustration.
Create the following type of table on paper or in Excel as a guide; the account name below is an example.
Windows Account, local Administrator on the index server. |
SSP Account also know as Shared Services Administrator |
OSearch Service Account |
Domino Administrator ID mapping in the Comments field of the person document |
Tailspintoys\SearchLN |
Tailspintoys\SearchLN |
Tailspintoys\SearchLN |
Tailspintoys\SearchLN |
Then once this is all configured, log on to the index server with this account Tailspintoys\SearchLN
• |
An administrator of the Lotus Domino server that you want to crawl |
• |
A server administrator of the index server from which you want to crawl Lotus Notes content |
• |
A shared services administrator |
User accounts required to index Lotus Domino databases
A Domino administrator must grant a Lotus Notes user ID (which represents a Domino user) at least the Reader permission to the Domino databases and documents the shared services administrator wants to crawl. The Domino administrator must also add this Lotus Notes user ID and the Windows domain account that is assigned to the OSearch service to a mappings database on the Lotus Domino server that you want to crawl.
OSearch service and the Lotus Notes user ID
The MOSS Shared Services administrator provides the Lotus Domino administrator with the Windows domain user account assigned to the OSearch service. The Domino administrator must then use the mappings database to map this Windows domain account to a Lotus Domino user ID. Only the Windows domain account assigned to the OSearch service can be used. Because of this, the same Lotus Domino id file must be used when crawling multiple Lotus Domino servers. We recommend that you use the account that is already assigned to the OSearch service. The exception to this is if the account assigned to the OSearch service is a service account (such as Local Service) instead of a Windows domain account. In this case, you will need to change the service account to a Windows domain user account. Then you must add this Windows domain account to the Administrators group on the index server.
Verify OSearch service account - You must be a MOSS farm administrator to perform the following procedure 1. In the SharePoint Central Administration Web site, on the Operations tab, in the Topology and Services section, click Services on server. 2. Click Office SharePoint Server Search. 3. On the Configure Office SharePoint Server Search Service Settings page, in the Farm Search Service Account section, ensure that Configurable is selected and that a Windows domain user account is specified in the User name box. Note that the user name must be in the form of domain\username. 4. Grant permissions to the data folder so the process can use the API Use the following procedure to grant Full Control permissions for the WSS_WPG group on the <SystemDrive>:\Program Files\Lotus\Notes\Data folder on the index server. 1. On the index server, click Start, point to All Programs, point to Accessories, and then click Windows Explorer. 2. In Windows Explorer, go to the <SystemDrive>:\Program Files\Lotus\Notes\Data folder, where <SystemDrive> is the drive on which Lotus Notes is installed. 3. Right-click the Data folder, and then click Sharing and Security. 4. In the Properties dialog box, on the Security tab, click Add. 5. In the Select the object names to select box, do one of the following, and then click OK: • If Office SharePoint Server 2007 is installed on an Active Directory domain controller, type domain\WSS_WPG, where domain is the name of the domain associated with the domain controller. • If Office SharePoint Server 2007 is installed on a server that is not an Active Directory domain controller, type server\WSS_WPG, where server is the NetBIOS name of the index server. 6. In the Properties dialog box, in the Permissions for WSS_WPG section, select the Allow box 5. Verify access to the Lotus Domino database you want to crawl, launch the Lotus Notes client and ensure you have access to the databases. 6. Configure the Lotus Notes Search application on the index server 1. On the index server, in Windows Explorer, go to the <SystemDrive>:\Program Files\Microsoft Office Servers\12.0\Bin folder, where <SystemDrive> is the drive on which Office SharePoint Server 2007 is installed. 2. Double-click NotesSetup.exe. 3. On the Welcome to the Lotus Notes Index Setup Wizard page, click Next. 4. In the Register Lotus Notes for use with Microsoft Office Server dialog box, do the following: • In the Location of the notes.ini file box, ensure that the correct path to your Notes.ini file is specified. The default path to this file is <SystemDrive>:\Program Files\lotus\notes\notes.ini, where <SystemDrive> is the drive on which Lotus Notes is installed. • In the Location of the Lotus Notes install directory box, ensure that the correct path to the Lotus Notes install directory is specified. The default path to this directory is <SystemDrive>:\Program Files\lotus\notes. If Lotus Notes R5/6 is installed, the above two values are filled by the installer automatically. The installer read Notes installation paths from registry, but it would be better if you can double confirm them. If Lotus Notes R7 is installed, you have to fill in the paths yourself. • In the Password box, type the password for the user name that is associated with the Lotus Notes User ID, then in the Confirm Password box, retype the password again. 5. We recommend that you leave the Ignore Lotus Notes security while building the index box unselected. If you choose to ignore Lotus Notes security, all Lotus Notes documents are crawled and indexed without security information. This means that these documents will appear on search results pages to all users of SharePoint sites. Click Next. 6. On the Specify Lotus Notes Owner Field to Windows User Name Mapping page, do the following: • In the Lotus Notes server name box, type the NetBIOS name or IP address of your Domino server. This is listed in the Lotus Domino server's NetBIOS name or IP address. • In the Lotus Notes database file name box, type the file name of the Lotus Domino database that maps the Lotus Notes user IDs to Windows domain accounts. Be sure to include the .nsf file extension with this name, for example, names.nsf, as we did in the first blog. Remember, this name is case sensitive. • In the View name box, type the view name of the Lotus Domino database that stores the Lotus Notes user IDs to Windows user name mappings. This name is listed in the View name we used was Mappings, this name is case sensitive. • In the Lotus Notes field name column title box, type the name of the column in the Lotus Notes database file used to store Lotus Notes user IDs, we used the Owner column, and this name is case sensitive. • In the Windows user name column title box, type the name of the column in the Lotus Notes database file used to store the Windows user accounts, we used the WindowsAccounts column, this name is case sensitive. 7. Click Next, on the Completing the Lotus Notes Index Setup Wizard page, click Finish. Restart the MOSS server, to ensure proper configuration and closes and open programs/api so that when you configure the content source and run the first full index you don’t have conflicts. Once the MOSS server has restarted, log on as the search account we created. Tailspintoys\SearchLN Since we verified you had access to your Lotus Domino databases you are indexing prior to the reboot, don’t launch the Lotus client again on this machine, unless it is troubleshooting related. You’ll now do the following procedure, create a content source and crawl content 1. Launch SharePoint 3.0 Administration, Click the section under Shared Services Administration, On the Shared Services Administration page, in the Search section, and click Search settings. 2. On the Configure Search Settings page, in the Crawl Settings section, click Content sources and crawl schedules. 3. On the Manage Content Sources page, click New Content Source. 4. On the Add Content Source page, in the Name section, in the Name box, type a name for the content source. Remember, each content source name must be unique within the SSP in which it is created. 5. In the Content Source Type section, select Lotus Notes. 6. In the Server, Database, and Properties section, select one of the following: • Select a server from the following list. Then, from the list, select the name of the Lotus Domino server you want to index, or you can enter a server name. From the Select a Lotus Notes database to index list, select the name of the database you want to index. 7. In the Crawl Schedules section, you can specify the schedules you want for full and incremental crawls. 8. In the Start Full Crawl section, select the Start full crawl of this content source box, Click OK. Ok, great job! So if you’ve done it right, you are now indexing a Lotus Domino database with SharePoint! That’s great, how do I know if it worked and where do I see my results? Go back to the Shared Services Administration page, choose Crawl Logs, and choose the Hostname of the server where you just configured that database. If it worked, that’s great, launch your browser, specify the MOSS server, in the search section, specify some topic or document that was indexed. If this failed or you have errors, we’ll cover that in the third and final blog of troubleshooting, tips, tricks and other cool stuff. Lou MandichEnterprise Technology StrategistMicrosoft Corp |