Showing posts with label Search. Show all posts
Showing posts with label Search. Show all posts

Tuesday, 29 November 2011

Configure search scopes in SharePoint 2007

Configure search scopes in SharePoint 2007

Activate Publishing Features on Site Collection1. Click Site Actions > Site Settings > Site Collection Features
2. Activate Office SharePoint Server Publishing Infrastructure
3. Activate Office SharePoint Server Search Web Parts
4. Return to Home Page of Site
Create Search Center
1. Click Site Actions > Create > Sites and Workspaces
2. Type in Name of Site
3. Click Enterprise Tab > Search Center
4. Click Create
5. Highlight the URL and Copy
6. Return to Home Site
Set New Search Settings
1. Site Actions > Site Settings
2. Click Use Custom Scopes
3. Paste the URL inside of box i.e,. http://sitename/search/results.aspx (Make sure you use results.aspx)
Search Scopes
1. Go to Central Admin > Shared Service Provider > Search Administration > Scopes
2. Click New Scope
3. Provide Scope Name > Ok
4. Click Add Rules
5. Click Web Address
6. Type in or copy in Web Address
7. Click Require every item in the Scope must match this rule.
Picking Search Scopes for Site
1. Go back to site you are tying the scope to.
2. Go to Site Actions > Site Settings > Scopes
3. Pick Edit Scope Display Group
4. Click Search Dropdown
5. Pick scope you created in the checkbox
6. Pick position from top = 1
7. Under Default Scope > Drop down the list to pick the Scope you created.
Activate Publishing Features on Site Collection
1. Click Site Actions > Site Settings > Site Collection Features
2. Activate Office SharePoint Server Publishing Infrastructure
3. Activate Office SharePoint Server Search Web Parts
4. Return to Home Page of Site
Create Search Center
1. Click Site Actions > Create > Sites and Workspaces
2. Type in Name of Site
3. Click Enterprise Tab > Search Center
4. Click Create
5. Highlight the URL and Copy
6. Return to Home Site
Set New Search Settings
1. Site Actions > Site Settings
2. Click Use Custom Scopes
3. Paste the URL inside of box i.e,. http://sitename/search/results.aspx (Make sure you use results.aspx)
Search Scopes
1. Go to Central Admin > Shared Service Provider > Search Administration > Scopes
2. Click New Scope
3. Provide Scope Name > Ok
4. Click Add Rules
5. Click Web Address
6. Type in or copy in Web Address
7. Click Require every item in the Scope must match this rule.
Picking Search Scopes for Site
1. Go back to site you are tying the scope to.
2. Go to Site Actions > Site Settings > Scopes
3. Pick Edit Scope Display Group
4. Click Search Dropdown
5. Pick scope you created in the checkbox
6. Pick position from top = 1
7. Under Default Scope > Drop down the list to pick the Scope you created.

Wednesday, 9 November 2011

SharePoint Search Result Open on Browser


Solution:

Add Following Javascript File to OSSSearchResults.aspx result page.

Javascript Code:

function getURLParam(strParamName)
{
var strReturn = "";
var strHref = window.location.href;

if ( strHref.indexOf("?") > -1 )
{
var strQueryString = strHref.substr(strHref.indexOf("?")).toLowerCase();
var aQueryString = strQueryString.split("&");
for ( var iParam = 0; iParam <>
{
if (aQueryString[iParam].indexOf(strParamName.toLowerCase() + "=") > -1 )
{

var aParam = aQueryString[iParam].split("=");
strReturn = aParam[1];
break;
}
}
}
return unescape(strReturn);
}

Thursday, 3 November 2011

Step by Step Configure Search Services Application

Step by Step Configure Search Services Application for Anonymous SharePoint 2010 Site

Steps to configure Search Services Application in SharePoint Server 2010 to crawling for anonymous SharePoint site. I think this is the best practice and the easiest way to crawl an Internet SharePoint site:

Enable Windows Authentication for SharePoint web application in anonymous zone

First of all anonymous SharePoint-site should have Windows Authentication enabled. Make sure that you enabled it for the web application in CA:
  1. Open SharePoint 2010 Central Administration
  2. Click Manage web applications under Application Management-section
  3. Select your web application's row
  4. Click Authentication Providers from ribbon
  5. Click Internet-zone (or what ever is defined for your anonymous site)
  6. Make sure that Enable Windows Authentication and Integrated Windows authentication are checked
  7. Click OK

Enable Windows Authentication for anonymous IIS web site

Second thing you need to check is the configuration of you anonymous web site under IIS. You need to check that Windows Authentication is enabled for your IIS web site. You have to perform this task to all crawl servers.
For IIS 7:
  1. Click Start -> Administrative Tools -> Internet Information Services (IIS) Manager
  2. Click Sites
  3. Select your anonymous site
  4. Double-click Authentication under IIS-section in the Features View
  5. Select Windows Authentication and click Enable from the Actions-pane on the right side of the window

Give full read access to default content access account

You should have a dedicated domain account that is used as a default content access account. This is important since this account is used by the crawler in any of the servers in your farm that has been assigned as crawl servers.
Default content access account needs to have Full Read-permissions to the SharePoint web application you are crawling.
  1. Open SharePoint 2010 Central Administration
  2. Click Manage web applications under Application Management-section
  3. Select your web application's row
  4. Click User Policy from the ribbon
  5. Click Add Users
  6. Click Next
  7. Input your default content access account to Users-box
  8. Select Full Read under Permissions
  9. Click Finish

Set default content access account in Search Administration

You need to define a default content access account in the Search Administration.
  1. Open SharePoint 2010 Central Administration
  2. Click Manage service applications under Application Management-section
  3. Click Search Service Application to open Search Administration
  4. In System Status-panel you will see Default content access account. Click on the right side of that row to define an suitable account
  5. Input your default content access account and password and click OK
That's it! Start a full crawl for your content source and you should see anonymous items crawled successfully.

Installing WSS and Search Server Express to make a Search and Collaboration appliance


WSS is great and Search Server Express is great, put the two together and you have an awesome collaboration and search solution in one.
But Search Server Express includes WSS so why install both of them?
Answer: If you don't already own a full SQL Server license then you Search Server Express provides MSDE which is limited to 4Gb of storage where as WSS include SSEE which is only limited by your local disk capacity (content database and concurrent user load effects on performance aside). So install both products and get (almost) unlimited WSS storage and Search Server Express MOSS like search capability.
I wanted to install this configuration for my church office as it represents good value for money.
They already had a W2K3 Server license + Windows CAL's but no SQL Server. So I installed the following:
  • WSS SP1 in Basic mode – provides unlimited storage SSEE database in single server only solution (no 4Gb limit like Express or MSDE)
  • Upgrade to Search Server Express – adds SQL Server 2005 Express for the SSP Content and Search db (this gives you MOSS search functionality for WSS sites, web sites and Network Shares)
Note: due to memory requirements of 2 SQL instances and WSS Web Application you will need to tweak some memory setting but if you have more than 50 users you will probably need a minimum of 4 Gb, preferably 8Gb, of memory which implies 64Bit Windows.

Problems with default WSS Install
There are a few strange WSS settings when you install in Basic Mode. Most notably:
  • No domain accounts used
  • "SharePoint – 80" IIS Web Site created (default IIS web site is also on port 80)
  • Web application on "SharePoint – 80" default zone security is set to Kerberos
Problem: if you change the AAM from the server netbios name to a friendly DNS name and add the host header to IIS, users can't login to the site.
Solution: Change the security provider for the Web Application Default zone to NTLM
Next, upgrade to Search Server Express following these instructions http://technet.microsoft.com/en-us/library/cc297193.aspx#UpgradeBasic
The SSE upgrade instruction state that:
By default, the Search Server 2008 upgrade wizard creates the default Search Center site on port 80. If there is an existing SharePoint site on that port, the Overwrite Default SharePoint Site screen appears. On this screen, click one of the following options:
  • Yes, overwrite the existing site with a new default SharePoint site.
  • No, do not overwrite the existing site. Create a new SharePoint site.
  • No, do not create a default site.
Problem: I do not get this prompt and the Configuration Wizard fails trying to create the sample data.
Solution: Delete the "SharePoint – 80" then using Central Admin:
  1. re-run the Configuration Wizard which will create a new "SharePoint – 80" web application
  2. delete the default search site collection created in the root of the new "SharePoint – 80" web application
  3. create a Collaboration site collection in the "SharePoint – 80" web application
  4. change the AAM settings if you don't want to use the server name + add IIS host header to "SharePoint – 80"
  5. configure the SSP search settings as required
Now you go to the Site Settings page of your new site on the "SharePoint – 80" web application and:
  1. create a new sub site using the Enterprise Search template
  2. set the site collection search settings to use the new search site
The last problem, if you used a host header, is that the crawler is blocked from accessing IIS regardless of the crawl account or Web Application Policy. Follow these steps to resolve http://support.microsoft.com/kb/896861