Tuesday, December 6, 2011

Adding an extra index server

OK, so Microsoft tell us SharePoint is higly scalable and although that is true, the indexing role is not scalable and cannot per se be made high available. When using multiple query servers you can obtain some high-availability since the popagated index is still available and is thus searchable. You loose the ability to index new content, though.
I want to be able to spread the load by using one index server index the MOSS farm, another to index file shares, yet another to idex Lotus Notes and so on.
Here’s how that can be done:
  1. First, add the extra server as described here (Windows Server 2003 R2) or here (Windows Server 2008 )
  2. From Central Administration -> Operations -> Services on Server select the new index server and Custom
  3. Stop Windows SharePoint Services Incoming E-Mail and  Windows SharePoint Services Web Application
  4. Start Office SharePoint Server Search. Select Use this server for indexing content, enter username and password and start the service
  5. Start Windows SharePoint Services Search.  Enter the appropriate information and start the service.  
Create a new SSP to use for search
  1. From Shared Services Administration choose New SSP
  2. Name the SSP and click Create a new Web application
  3. Create the Web App with your preferred settings (port number, user name/password, database name etc) and click OK
  4. Back in New Shared Services Provider create a new Web App for MySites or use the newly created Web App if you wnat. I choose to use the newly created Web App, although it may not be best practices.
  5. Put in your credentials and database names
  6. Remeber to specify the newly added index server as the Index Server for the SSP. Now reate the SSP by clicking OK. You may see a warning if you didn’t create a seperate MySite Web App for this SSP
  7. That’s basically it. You can now use the new SSP’s Administration Page to configure Search or any other SSP-related functionality.

No comments:

Post a Comment