The STS3S protocol is used for crawling SharePoint content that is exposed using SSL, without having to have URL links that lead to every possible content item in the web site. This protocol is used to index WSS 3.0 server farms using SSL (which MOSS 2007 is layered on top of ) STS3S protocol achieves this by using the Site Data Web service to determine all the content in your SharePoint site.

Some examples:
sts3s://www.yourdomain.com/
sts3s://www.yourdomain.com/teamsites/
sts3s://portal.yourdomain.com/

The protocol handlers (that ship out-of-the-box with MOSS 2007) translate the content source url from sts3s:// into a web service call sts3s://www.yourdomain.com is actually crawled on the web front end by the indexer using a SOAP call to the web service https://mysite.yourdomain.com/_vti_bin/spscrawl.asmx ( the STS3S SOAP call is made using HTTP protocol on TCP Port 56738 with SSL encryption )

Read more at the source about this and other protocols.

Tags: User Profiles, webservice

Search, SharePoint 2007 No comments yet, be the first »

Jul

27

Crawl and user information list dependency

MarC on July 27th, 2010

Only until now I realize that there is a dependency between the user information list and crawling the site. After a full crawl the user information list is updated with information in the User Profiles.

In a customer farm there are some accounts in the Imported User Profiles list where the display name is in the format domain\username. These names are also in the user information list (http://<portal>/_catalogs/users/simple.aspx). In the Imported User Profiles list you can edit these display names by editing the profiles. In the user information list this is not possible and I needed to change it because the people picker uses this list as source.

I searched the internet and found that a full crawl resolved this issue.

Tags: Profile import, User Profiles

Search, SharePoint 2007 No comments yet, be the first »

Jul

26

Renaming service application databases

MarC on July 26th, 2010

I have set up a SharePoint 2010 farm. Some databases have been configured by using PowerShell scripts. Therefore they have friendly names like SP2010_Config. I do not have made scripts for every configuration step yet so some database names are like this \WebAnalyticsServiceApplication_ReportingDB_2d5a77a9-8360-41cf-9294-14587f977d1d.

I would like to have nice looking names in my SQL server so I change the names of i.e. the WebAnalytics Service like this:

Go to Central Admin > Manage Service Applications
Select the Web Analytics Service Application:
Choose “Properties” in the ribbon:
Choose “Next” at the Edit Web Analytics Service Application screen
At the Edit Web Analytics Service Application Topology screen you can edit the database name:
Click on Reporting Database and choose “Edit Properties”:
In the next step you can change the database name:
When back in the Topology screen click “Next” and the changes are being processed:

Be aware: by doing this SharePoint will create new databases with the choosen name.

Tags: database, Howto, Service application, SP2010

SharePoint 2010 No comments yet, be the first »

Jul

23

First Cumulative Update for SharePoint 2010

MarC on July 23rd, 2010

This week the first cumulative update (CU) for SharePoint 2010 has been released. It is called June 2010 CU. It is not a single package but 6 installation files.

Downloads here:

KB2028568
KB983319
KB983497
KB2182938 (Only Japanese)
KB2281364
KB2124512

Future plans of BPOS

MarC on July 19th, 2010

Last week Microsoft shared their “official” roadmap for updating the company’s hosted Business Productivity Online (BPOS) suite.
[...]
Microsoft didn’t provide specific dates as to when they’d deliver the updates to each of its managed services, but did say the updates would happen in fiscal 2011 (which runs from July 1, 2010, to June 30, 2011).
[...]
The on-premise Office Communications Server 14 is likely to ship at the very the end of this year.

Also last week Microsoft rolled out the July refresh for BPOS, which added a hosted Blackberry Administration Center and Live Meeting updates to the current BPOS offering. Coming in the near term (again, no specific dates) are Office 2010 support and enhanced PowerShell scripting.

Here are some slides with detailed comparisons. First SharePoint:

(click to enlarge)