In Central Administration, click Manage Service Applications, and then click your FAST Query SSA.

Under Administration, click FAST Search Administration.

Under Property Management, click Managed Properties. You should now see a list of all existing managed properties, as shown in Figure 6-2. For each property, the type, the property’s options, and any existing mappings from crawled properties are listed.

Figure 6-2. All existing managed properties, as shown on the FAST Query SSA.

Click Add Managed Property, and then fill out the details as needed.

At the very least, give the new property a unique name. A good practice is to prefix it with something unique in order to distinguish it from the other managed properties because there is no other way to group a set of managed properties. This makes future management easier.

Map one or more existing crawled properties to your new managed property.

Indicate whether it should be possible to sort on the new managed property, target a fielded query against it, or refine on it.

Decide whether you want to put the property into the default full-text index—that is, whether the content of the property should be searchable as-is. Note that if you omit mapping the property to a full-text index and choose not to check the Query Property, the new property will not be searchable in any way, nor can it be used as a refiner. However, it can still be used for presentation and sorting.

Click OK.

In Central Administration, click Manage Service Applications, and then click your FAST Query SSA.

Under Administration, click FAST Search Administration.

Under Property Management, click Crawled Property Categories. You should now see a list of all existing crawled property categories, shown in Figure 6-4. Because the number of crawled properties can be huge, FS4SP sorts the crawled properties into groups, typically according to content source.

Click any of the groups in which you want to modify a crawled property. In this example, click the SharePoint group.

Click the crawled property that you want to modify; alternatively, you can search for it using the Search box at the top. In this example, click the crawled ows_Company property.

On the Edit Crawled Property page, click the Add Mapping button. This opens a modal dialog box, shown in Figure 6-5.

Figure 6-4. All existing crawled property categories.

Figure 6-5. Select managed properties to which a crawled property should map.

Pick one or many managed properties to map the crawled property against.

Click OK.

Open an FS4SP shell.

Run Get-FASTSearchMetadataManagedProperty to list each managed property installed in your solution. Run Get-FASTSearchMetadataManagedProperty | Measure-Object to find out how many properties there are.

Run Get-FASTSearchMetadataManagedProperty -Name “Keywords” to inspect each property of the managed Keywords property. Your output should look similar to the following.

PS C:FASTSearchin> Get-FASTSearchMetadataManagedProperty -Name "Keywords"

Name                   : Keywords
Description            : Keywords for this document
Type                   : Text
Queryable              : True
StemmingEnabled        : True
RefinementEnabled      : False
MergeCrawledProperties : False
SubstringEnabled       : False
DeleteDisallowed       : False
MappingDisallowed      : False
MaxIndexSize           : 1024
MaxResultSize          : 64
DecimalPlaces          : 3
SortableType           : SortableDisabled
SummaryType            : Disabled

Compare your output to the listing of properties in Table 6-3. From here, you can tell right away that the Keywords property is used to hold regular text (Type), that it is possible to query using the “keyword: query” syntax (Queryable), and that it is neither used for deep refinement (RefinementEnabled) nor sorting (SortableType). You do not, however, know whether it is included as-is in a free text search because you cannot tell from this output alone whether the property is used in a full-text index. See the following section, Full-Text Indexes and Rank Profiles, for more information about this.

Changing any of the internal properties of a managed property is straightforward and can be done using two methods:

Open an FS4SP shell.

Use the New-FASTSearchMetadataManagedProperty cmdlet to create a managed property. This cmdlet has two required parameters: -Name and -Type. The former is simply the desired name of the new managed property. The latter indicates its data type, represented as an integer. Table 6-4 lists all available data types and which integer to use to reference it. For example, to create a managed property called Salary that uses the data type Float, run the following command.

New-FASTSearchMetadataManagedProperty -Name "Salary" -Type 4 –Description "A descriptive
text"

Open an FS4SP shell.

Use the New-FASTSearchMetadataCrawledPropertyMapping cmdlet to register the mapping. Unfortunately, you cannot reference the managed property and the crawled property by name. Instead, you first retrieve their object references.

$mp = Get-FASTSearchMetadataManagedProperty -Name "<ManagedPropertyName>"
$cp = Get-FASTSearchMetadataCrawledProperty -Name "<CrawledPropertyName>"
New-FASTSearchMetadataCrawledPropertyMapping -ManagedProperty $mp -CrawledProperty $cp

Open an FS4SP shell.

Use the Get- FASTSearchMetadataCategory cmdlet to list all available property categories.

Use Get- FASTSearchMetadataCategory “<category name>”, where <category name> is the name of the category to get a reference to only one category.

Open an FS4SP shell.

Use the New-FASTSearchMetadataCategory cmdlet to create a crawled property category. Replace <String> with the name you want to give your category and <Guid> with a GUID of your making. The following sample creates a category named FS4SP Book with a random GUID. Be sure to print and make a note of the GUID after creation.

$guid = [guid]::NewGuid()
New-FASTSearchMetadataCategory -Name "FS4SP Book" -Propset $guid

Open an FS4SP shell.

Run the following command to turn off automatic discovery of new crawled properties for the category and to make the crawled properties added to the category searchable by default.

$category = Get- FASTSearchMetadataCategory "FS4SP book"
$category.MapToContents = 1
$category.DiscoverNewProperties = 0
$category.Update()

Add a reference to the FS4SP administration main assembly by running the following.

<FASTSearchFolder>inMicrosoft.SharePoint.Search.Extended.Administration.dll

Add the corresponding namespaces.

using Microsoft.SharePoint.Search.Extended.Administration;
using Microsoft.SharePoint.Search.Extended.Administration.Schema;

Initialize the connection to FS4SP and acquire an object reference to the index schema.

SchemaContext schemaContext = new SchemaContext();
Schema indexSchema = schemaContext.Schema;

Add a new managed property using the following code.

indexSchema.AllManagedProperties.Create("MyMP", "A descriptive text", ManagedType.Text);

The AllManagedProperties property returns a special type of collection that lists all managed properties and exposes the Create method that adds new managed properties. The enum ManagedType exposes data type values that correspond to those listed in Table 6-4.

After running the code, run Get-FASTSearchMetadataManagedProperty -Name “MyMP” in an FS4SP shell to verify that the managed property was in fact created and deployed.

To map a crawled property to a managed property, you first need to obtain the index schema. Perform steps 1–3 from the previous example, “Create a managed property.” This leaves you with the indexSchema variable.

In this example, you map the crawled property ows_Name into the managed property Author. These are default properties, and unless you manually removed them, this step should work fine.

Just like you did when using the Windows PowerShell approach, in order to configure the mapping, you need to get objects for both the managed and the crawled properties. Let’s start with the easiest, the managed property.

var mp = indexSchema.AllManagedProperties["Author"];

As you saw in the section on crawled properties, you can use several methods for obtaining an object reference to a crawled property. In this example, you use the QueryCrawledProperties method, which lets you query for a crawled property name.

Note that this method returns an IEnumerable<CrawledProperty> because several crawled properties might share the same name. In this example, you are giving yourself the liberty of assuming that there is only one property called ows_Name, which is the case in a default FS4SP installation. Be sure to put proper safeguards in place in your production environment to avoid null-pointer exceptions.

var cp = indexSchema.QueryCrawledProperties("ows_Name", 0, 1).First();

The second and third parameters are a query offset and a limit on how many matching crawled properties should be returned. In this example, you want to search the whole set (starting from offset 0), and only care for one specific property (stop after 1 match) using the First() method provided by Microsoft Language Integrated Query (LINQ) in the .NET Framework.

Next, get a list of all existing mappings from the managed property, add the crawled property to that list, and write the list back to the managed property. Use the following code.

var mappings = mp.GetCrawledPropertyMappings();
mappings.Add(cp);
mp.SetCrawledPropertyMappings(mappings);

After running the code, use the following two lines of Windows PowerShell script, and verify that the crawled property was indeed mapped to the managed property.

$mp = Get-FASTSearchMetadataManagedProperty -Name "Author"
Get-FASTSearchMetadataCrawledPropertyMapping -ManagedProperty $mp

In Central Administration, point to Manage Service Applications, and then click your FAST Query SSA.

Under Administration, click FAST Search Administration.

Under Property Management, click Managed Properties. You should now see a list of all existing managed properties, as shown in Figure 6-2 earlier.

Click a managed property, for example, body. This takes you to the Edit Managed Property page.

At the very bottom of the page, you can change which importance level, or “priority,” should be associated with the managed property by using a drop-down menu. In the same place, you can inspect the default full-text index; see which other managed properties belong to the index and what important levels they have been assigned. Clicking the View Mappings link, directly under the drop-down menu, brings up a modal dialog box with this information, as shown in Figure 6-6.

Open an FS4SP shell.

Create a full-text index and rank profile, and then save the object references.

$fti = New-FASTSearchMetadataFullTextIndex -Name "myfti" -Description "A short
description"
$rp = New-FASTSearchMetadataRankProfile -Name "myrp"

The previous command creates the rank profile with default values. Using the -Template parameter with New-FASTSearchMetadataRankProfile, you can use another existing rank profile to override the defaults. New-FASTSearchMetadataFullTextIndex does not support using a template, but you can easily change its default values after creation by modifying the properties of the $fti object.

Extract the existing rank components from the rank profile, and then add the rank components from the full-text index by using the following code.

$rankComponents = $rp.GetFullTextIndexRanks()
$rankComponents.Create($fti)

At this point, the new full-text index and rank profile is available and ready for use. However, the full-text index contains no managed properties, and the rank components are left at default values.

To start using the new full-text index right away, mark it as default.

$fti.MakeDefault()

To verify that the procedure worked as expected, either retrieve the list of full-text indexes by using the Get-FASTSearchMetadataFullTextIndex cmdlet and look for the isDefault property, or go to the Edit Managed Property page in Central Administration and click View Mappings, as shown in Figure 6-6.

Locate the rank profile you want to modify, and then extract its rank components.

$rp = Get-FASTSearchMetadataRankProfile -Name "MyRP"
$rankComponents = $rp.GetFullTextIndexRanks()

In this example, you want to increase the relevance boost of important managed properties, which you achieve by doubling the rank importance of the highest importance level (7). Unfortunately, there is no easy way to reference rank components belonging to a certain full-text index, so you have to resort to looping through them until you find the one you are looking for.

foreach ($ftiRankComponent in $rankComponents)
{
   if($ftiRankComponent.FullTextIndexReference.Name.Equals("MyFTI"))
   {
      var newFtiRankComponent = 2 * $ftiRankComponent.GetImportanceLevelWeight(7);
      $ftiRankComponent.SetImportanceLevelWeight(7, newFtiRankComponent);
   }
}

The changes to importance level weights do not take effect until the next recrawl. This is because the importance levels are part of static rank, which is evaluated at index time and not at query time.

The first step in working with full-text indexes in code is to obtain the index schema. Perform steps 1–3 from the .NET procedure “Create a managed property” in the Crawled and Managed Properties section earlier in this chapter. This leaves you with the indexSchema variable.

When you use the schema’s property AllFullTextIndecies, creating a new full-text index is straightforward and similar to creating a managed property.

var fti = indexSchema.AllFullTextIndecies.Create("MyFTI", "A descriptive text");

This creates a full-text index that has default values and is tied against the default rank profile.

To verify that the procedure worked as expected, run the Get-FASTSearchMetadataFullText-Index cmdlet and make sure the new full-text index is listed.

Because the full-text index uses the default rank profile, if you also want to associate it with a brand new rank profile, add the following lines of code.

var rp = indexSchema.AllRankProfiles.Create("newrp");
var rankComponents = rp.GetFullTextIndexRanks();
rankComponents.Create(fti);

Just as in the previous Windows PowerShell example, this creates a rank profile and associates the rank components with the full-text index. Note that the Create method on AllRankProfiles accepts a second parameter that specifies an existing rank profile as a template.

To start using the new full-text index right away, mark it as default by using the following code.

fti.MakeDefault();

To verify that the procedure worked as expected, either retrieve the list of full-text indexes by using the Get-FASTSearchMetadataFullTextIndex cmdlet and look for the isDefault property, or go to the Edit Managed Property page in Central Administration and click View Mappings, as shown in Figure 6-6 earlier.

The first step in working with full-text indexes in code is to get the index schema. Perform steps 1–3 from the .NET procedure “Create a managed property” in the Crawled and Managed Properties section earlier in this chapter. This leaves you with the indexSchema variable.

Locate the rank profile you want to modify, and then extract its rank components by using the following code.

var rp = indexSchema.AllRankProfiles["MyRP"];

In the same manner as in the previous Windows PowerShell example, you now have to isolate the rank components that are associated with the targeted full-text index. Using LINQ, this is simple.

var rankComponents = rp.GetFullTextIndexRanks()
                       .Where(rc => rc.FullTextIndexReference.Name.Equals("MyFTI"));

Now modify each rank component the way you like; in this example, duplicate the scenario from the previous Windows PowerShell version.

foreach(var rc in rankComponents) {
    var oldWeight = rc.GetImportanceLevelWeight(FullTextIndexImportanceLevel.
ImportanceLevel7);
    rc.SetImportanceLevelWeight(FullTextIndexImportanceLevel.ImportanceLevel7, 2 *
oldWeight);
}

Open an FS4SP shell.

Using the following code, obtain a reference to the default rank profile (which also happens to be named default).

$RankProfile = Get-FASTSearchMetadataRankProfile -Name "default"

Obtain a reference to the managed property format.

$Property = Get-FASTSearchMetadataManagedProperty -Name "format"

Create the managed property boost for the value Document and set the weight.

$RankProfile.CreateManagedPropertyBoostComponent($Property, "Web Page, 5000")

The property boost should take effect without doing a recrawl, but the boost might take some time to kick in because of caching.

Open an FS4SP shell.

Obtain a reference to the default rank profile.

$RankProfile = Get-FASTSearchMetadataRankProfile -Name "default"

Obtain a reference to the managed property you want to update.

$Boost = $RankProfile.GetManagedPropertyBoosts()
          | where-object { $_.ManagedPropertyReference.Name -eq "format" –and
                           $_.BoostValue -eq "Web Page, 5000"}

Change the value to promote Word documents instead of webpages.

$Boost.BoostValue = "Microsoft Word, 5000"

Update the property boost.

$Boost.Update()

Open an FS4SP shell.

Obtain a reference to the default rank profile.

$RankProfile = Get-FASTSearchMetadataRankProfile -Name "default"

Obtain a reference to the managed property you want to delete.

$Boost = $RankProfile.GetManagedPropertyBoosts()
          | where-object { $_.ManagedPropertyReference.Name -eq "format" –and
                           $_.BoostValue -eq "Web Page, 5000"}

Delete the managed property boost.

$Boost.Delete()

The first step in working with full-text indexes in code is to get the index schema. Perform steps 1–3 from the .NET procedure “Create a managed property” in the Crawled and Managed Properties section earlier in this chapter. This leaves you with the indexSchema variable.

Using the schema’s property AllRankProfiles, you obtain a reference to the default rank profile.

RankProfile rankProfile = indexSchema.AllRankProfiles["default"];

Using the schema’s property AllManagedProperties, you obtain a reference to the managed property named format.

ManagedProperty managedProperty = indexSchema.AllManagedProperties["format"];

Obtain the existing managed property boost collection and create a boost for your managed property:

var managedPropertyBoosts = rankProfile.GetManagedPropertyBoosts();
managedPropertyBoosts.Create(managedProperty, "Web Page, 5000");

Open an FS4SP shell.

Obtain a reference to the default rank profile (which also happens to be named default).

$RankProfile = Get-FASTSearchMetadataRankProfile -Name "default"

Obtain a reference to the existing static rank components.

$QualityComponents = $RankProfile.GetQualityComponents()

Obtain a reference to the managed property size.

$Property = Get-FASTSearchMetadataManagedProperty -Name "size"

Add the managed property to the static rank.

$QualityComponents.Create($Property, 10)

In Central Administration, point to Manage Service Applications, and then click your FAST Query SSA.

Click the FAST Search Administration link in the left column, shown in Figure 6-8.

Figure 6-8. The link to the FAST Search Administration page in the FAST Query SSA.

Under Property Extraction, click Manage Property Extraction.

Point to Locations, and click the down arrow. Then select Edit Include List, shown in Figure 6-9. Choose Edit Exclude List to add terms that you want to omit from the property extractor.

Click Add Item.

Enter the term to include a location name extraction, for example, North Pole, as shown in Figure 6-10.

Follow steps 1–3 from the previous “Add a term to a property extraction list” procedure.

Point to the term you want to remove, and then choose Delete Item, as shown in Figure 6-11.

Open an FS4SP shell.

No Windows PowerShell cmdlets are included with FS4SP to work with the property extractor lists, but you can use the .NET object in Windows PowerShell to accomplish your task. You can get a reference to the EntityExtractorContext object by using the following line of code.

$entityExtractorContext = New-Object -TypeName Microsoft.SharePoint.Search.Extended.
Administration.EntityExtractorContext

Get a reference to the Locations list.

$locationEntities = $entityExtractorContext.TermEntityExtractors | where { $_.Name -eq
"locations" }

Add a new term to the inclusion list.

$locationEntities.Inclusions.Add("North Pole")

Follow steps 1–3 from the previous “Add a term to a property extraction list” procedure.

Remove the term.

$locationEntities.Inclusions.Remove("North Pole")

Add a reference to the FS4SP administration main assembly.

<FASTSearchFolder>inMicrosoft.SharePoint.Search.Extended.Administration.dll

Add the corresponding namespaces.

using System.Linq;
using Microsoft.SharePoint.Search.Extended.Administration;
using Microsoft.SharePoint.Search.Extended.Administration.Linguistics;

Initialize the connection to FS4SP and acquire an object reference to the TermEntityExtractor for locations:

EntityExtractorContext entityExtractorContext = new EntityExtractorContext();
TermEntityExtractor locationEntitites = entityExtractorContext.TermEntityExtractors.
Where(t => t.Name == "locations").First();

Add a term to the inclusion list.

locationEntitites.Inclusions.Add("North Pole");

Follow steps 1–3 in the previous “Add a term to a property extraction list” procedure.

Remove the term from the inclusion list.

locationEntitites.Inclusions.Remove("North Pole");

Log on to the home page of your top-level site as a user with site collection administration privileges. Make sure the user is a member of either the local group FASTSearchAdministrators or FASTSearchKeywordAdministrators on the FS4SP administration server.

Go to Site Actions | Site Settings | Site Collection Administration.

Click FAST Search Keywords, shown in Figure 6-12.

Display the Manage Keywords page.

Click Add Keyword, shown in Figure 6-13.

Fill in the keyword information. The phrase you will match is fast search for sharepoint, and you will add two-way synonyms for fs4sp and enterprise search. This means that when a user searches for fast search for sharepoint, he will also search for fs4sp and enterprise search and vice versa. If you don’t want searches to match the synonym, use a one-way synonym instead. Several synonym terms can be added and separated with a semicolon, as shown in Figure 6-14.

Click OK.

Display the Manage Keywords page.

Point to your keyword, click the down arrow, and choose Add Best Bet from the displayed menu, as shown in Figure 6-15.

Fill in the Title, Description, and URL boxes for your best bet, as shown in Figure 6-16. This information will be shown above the other results on your search page in the Best Bets Web Part. You can also fill in a start date and an end date for when the best bet is to be shown, and associate one or more user contexts.

Click OK.

Display the Manage Keywords page.

Point to the best bet count for your keyword, and then click the down arrow.

Move your pointer over Delete Best Bets, and pick the best bet you want to delete, as shown in Figure 6-17.

Display the Manage Keywords page.

Move the mouse over your keyword, click the down arrow, and choose Add Visual Best Bet from the displayed menu, as shown in Figure 6-15.

Fill in the Title and URL boxes for the visual best bet, as shown in Figure 6-18. You can also fill in a start date and an end date for when the visual best bet is to be shown, and associate one or more user contexts.

Display the Manage Keywords page.

Point to the visual best bet count for your keyword, and then click the down arrow.

Move your pointer over Delete Visual Best Bets, and then pick the visual best bet you want deleted, as shown previously in Figure 6-17.

Display the Manage Keywords page.

Point to your keyword, click the down arrow, and then choose Add Document Promotion from the displayed menu shown in Figure 6-15 earlier.

Fill in the Title and URL boxes for your document promotion as shown in Figure 6-19. The promoted item will be moved to the top of a search query matching the associated keyword. You can also fill in a start date and an end date for when the document promotion should be active, and you can associate one or more user contexts.

Display the Manage Keywords page.

Point to the document promotion count for your keyword, and then click the down arrow.

Point to Delete Document Promotion, and then pick the promotion you want to delete.

Display the Manage Keywords page.

Point to your keyword, click the down arrow, and then choose Add Document Demotion from the displayed menu shown earlier in Figure 6-15.

Fill in the Title and URL boxes for your document demotion. The promoted item will be moved to the bottom of a search query matching the associated keyword. You can also fill in a start date and an end date for when the document demotion is to be active, and you can associate one or more user contexts.

Display the Manage Keywords page.

Point to the document demotion count for your keyword, and then click the down arrow.

Point to Delete Document Demotion, and then pick the promotion you want to delete.

Open an FS4SP shell.

You need to get a reference to a search settings group. If you added a keyword for a site collection by using SharePoint Site Collection Administration, this group is already created for you. If not, you need to create it yourself. If you have only one site collection, you have one search settings group and can omit the Name parameter. You can also execute Get-FASTSearchSearchSettingsGroup by itself to list all groups already created. The name of the search settings group is the ID of the site collection it belongs to.

$searchSettingGroup = Get-FASTSearchSearchSettingGroup -Name "<GUID>"

Add the keyword, and get a reference to it.

$keyword = $searchSettingGroup.Keywords.AddKeyword("fast search for sharepoint")

Now you need to add the synonyms either by using one-way or two-way expansion:

Open an FS4SP shell.

Get a reference to the keyword on the site collection where you want to add the best bet.

$searchSettingGroup = Get-FASTSearchSearchSettingGroup -Name "<GUID>"
$keyword = $searchSettingGroup.Keywords.GetKeyword("fast search for sharepoint")

Create a URI object that points to the location of the best bet, where <URL> is the URL, for example, http://www.contoso.com.

$uri = New-Object -TypeName System.Uri -ArgumentList "<URL>"

Add the best bet location to the keyword, where <BestBetName> is the title of the best bet and <HTMLTeaser> is the teaser linked to the best bet in HTML. The teaser is neither used nor displayed in the Best Bet Web Part.

$keyword.AddBestBet("<BestBetName>", "<HTMLTeaser>", $uri)

Follow steps 1–2 of the previous “Add a best bet” procedure.

Remove the best bet.

$keyword.RemoveBestBet("<BestBetName>")

Follow steps 1–3 of the “Add a best bet” procedure.

Add the visual best bet link to the keyword, where <VisualBestBetName> is the title of the visual best bet and the URL points to the visual best bet content.

$visualBestBet = $keyword.AddFeaturedContent("<VisualBestBetName>")
$visualBestBet.Uri = $uri

Follow steps 1–2 of the “Add a best bet” procedure.

Remove the visual best bet.

$keyword.RemoveFeaturedContent("<VisualBestBetName >")

Follow steps 1–2 of the “Add a best bet” procedure.

Add the document promotion, where <PromotionName> is the title of the document promotion, <DocumentId> is the URL of the item you want promoted, and <BoostValue> is the value you want to boost the item with. Negative values demote the item instead of promoting it. The value used via Central Administration is 1,000,000 to ensure the item is put at the top of the result list, but you can reduce the value to create a softer boost.

$promotion = $keyword.AddPromotion("<PromotionName>")
$promotion.BoostValue = "<BoostValue>"
$promotion.PromotedItems.AddPromotedDocument("<DocumentId>")

Follow steps 1–2 of the “Add a best bet” procedure.

Remove the document promotion, where <PromotionName> is the title of the document promotion and <DocumentId> is the URL of the item you promoted.

$promotedItems = $keyword.Promotions["<PromotionName>"].PromotedItems
foreach ($promotedDocument in @($promotedItems.GetPromotedDocumentEnumerator()))
{
   if ($promotedDocument.DocumentId -eq "<DocumentId>")
   {$promotedItems.Remove($promotedDocument)}
}

Open an FS4SP shell.

Get a reference to the search settings group on the site collection where you want to add the global best bet.

$searchSettingGroup = Get-FASTSearchSearchSettingGroup -Name "<GUID>"

Create a URI object that points to the location of the best bet, where <URL> is the URL, for example, http://www.contoso.com.

$uri = New-Object -TypeName System.Uri -ArgumentList "<URL>"

Add the global best bet or visual best bet.

// Add a global best bet
$searchSettingGroup.BestBetsWithoutKeyword.AddBestBet("<GlobalBestBetName>", $uri)

// Add a global visual best bet
$searchSettingGroup.FeaturedContentWithoutKeyword.AddFeaturedContent("<GlobalVisualBestB
etName>", $uri)

Follow steps 1–2 of the “Add a best bet” procedure.

Add the document promotion, where <GlobalPromotionName> is the title of the document promotion, <DocumentId> is the URL of the document you want promoted, and <BoostValue> is the value you want to boost the document with. Negative values demote the document instead of promoting it.

$globalPromotions = $searchSettingGroup.PromotionsWithoutKeyword
$globalPromotion = $globalPromotions.AddPromotion("<GlobalPromotionName>")
$globalPromotion.BoostValue = "<BoostValue>"
$globalPromotion.PromotedItems.AddPromotedDocument("<DocumentId>")

Log on to the home page of your top-level site as a user with site collection administration privileges. Make sure the user is a member of either the local group FASTSearchAdministrators or FASTSearchKeywordAdministrators on the FS4SP administration server.

Go to Site Actions | Site Settings | Site Collection Administration.

Under Site Collection Administration, click FAST Search Site Promotion And Demotion.

Click Add Site Promotion.

Give the site promotion a title, and then click the Add button in the Promoted Sites category to add a new site to promote.

Enter the URL of the site you want to promote, and then click Add. You can add several URLs by repeating this step. Example: http://www.contoso.com/.

Log on to the home page of your top-level site as a user with site collection administration privileges.

Navigate to Site Actions | Site Settings | Site Collection Administration.

Under Site Collection Administration, click FAST Search Site Promotion And Demotion.

Click Manage Site Demotion.

Click Add Site Demotion.

Give the site demotion a title, and then click the Add button in the Demoted Sites category to add a new site to demote.

Enter the URL of the site you want to demote, and then click Add. You can add several URLs by repeating this step. Example: http://www.contoso.com/.

Open an FS4SP shell.

Get a reference to the keyword on the site collection where you want to add the best bet.

$searchSettingGroup = Get-FASTSearchSearchSettingGroup -Name "<GUID>"
$keyword = $searchSettingGroup.Keywords.GetKeyword("fast search for sharepoint")

Add the document promotion, where <PromotionName> is the title of the site promotion, <URL> is the URL of the site you want promoted, and <BoostValue> is the value you want to boost the site with. Negative values demote the site instead of promoting it.

$promotion = $keyword.AddPromotion("<PromotionName>")
$promotion.BoostValue = <BoostValue>
$uri = New-Object -TypeName System.Uri -ArgumentList "<URL>"
$promotion.PromotedItems.AddPromotedLocation($uri)

Follow steps 1–2 of the previous “Add a site promotion to a keyword” procedure.

Add the site promotion, where <GlobalPromotionName> is the title of the site promotion, <URL> is the URL of the site you want promoted, and <BoostValue> is the value you want to boost the site with. Negative values demote the site instead of promoting it.

$globalPromotions = $searchSettingGroup.PromotionsWithoutKeyword
$globalPromotion = $globalPromotions.AddPromotion("<GlobalPromotionName>")
$globalPromotion.BoostValue = "<BoostValue>"
$uri = New-Object -TypeName System.Uri -ArgumentList <URL>
$globalPromotion.PromotedItems.AddPromotedLocation($uri)