1. On the sharepoint server open the command line window and type cd C:Program FilesCommon FilesMicrosoft Sharedweb server extensions12BIN
2. To find out the current central admin port no. type stsadm.exe -o getadminport
3. To change the central admin port no type stsadm.exe -o setadminport -port <portnumber>

for example: if you want to set the admin port to 1499 type the command like

stsadm.exe -o setadminport -port 1499

Change central admin port number

Central Administration site after changing the port number

Usage Analysis Processing

On the Usage analysis processing page select the check box Enable logging in Logging Settings section
Enter the location of log file and the numeric value in number of log files to created:
Select the check box Enable usage analysis processing and select the Start and End time.

Clcik OK to save the configuration.

Enable Logging Settings and Processing Settings

2) Configure site usage reports in Shared Services Administration (SSP)

Go to, Shared Services Administration (SSP)

Configure site usage reports in SSP

Under section Office SharePoint Usage Reporting click on Usage reporting

On Configure Advanced Usage Analysis Processing page, under Processing Settings section Select the check box Enable advanced usage analysis processing

Under Search Query Logging Select the check box Enable search query logging

Configure Advanced Usage Analysis Processing in SSP

After enabling usage report in SSP, now activate the Reporting feature in site collection administrators

3) Activate reporting feature

Go to Site actions, click Site settings
On the site settings page, under Site Collection Administration section click on Site collection features
Click Activate button to activate Reporting feature.

Activate the reporting feature

To view site usage reports, go to Site Actions > Site Settings

If you are a site administrator, click on Site usage reports under Site Administration section

No problem, if you are not a site administrator, usage reports can be view by site collection administrator too, click on Site collection usage reports under Site Collection Administration section

To view the site usage reports

Site usage summary

Site usage summary

Site usage reports can viewed by site administrators, site collections administrators, SSP administrators and SSP site collection administrators in their respective area

• Creating the SQL database
• Creating the users in SQL database
• Creating two sharepoint sites (one is web application and other extending the web application)
• Configure membership, role provider and connection string in both web.config files of the Sharepoint site
• Configure authentication type in central administration

We will discuss all the above point in detail

Creating the SQL database

To create SQL database Microsoft has provided a utility called  aspnet_regsql.exe, browse to the location C:WINDOWSMicrosoft.NETFrameworkv2.0.50727

aspnet_regsql utility for creating SQL database

Creating SQL database

Creating SQL database

Creating SQL database

Creating the users in SQL database

To create users in SQL database first of all create one ASP.NET web application using Visual Studio 2005, open Visual Studio 2005, then click on.

File > New > Website

Select the ASP.NET website and click OK

Creating ASP.NET web application

To add the web.config file, right click on the project name in solution explorer select add new item, select web configuration file and then Add

or

Press F5 to automatically adding the web.config file to the project

Add the connection string in the web.config file

<!–Connection String Starts–>
<connectionStrings>
<add name=”Fbadb_sqlConnectionString”
connectionString=”uid=sa;pwd=sa;
Initial Catalog=FBADB;
Data Source=fivenumber” />
</connectionStrings>
<!–Connection String Ends–>

<system.web>

<!–Membership Provider Starts–>
<membership defaultProvider=”Fbadb_ASPNETSqlMembershipProvider”>
<providers>
<add name=”Fbadb_ASPNETSqlMembershipProvider”
type=”System.Web.Security.SqlMembershipProvider,
System.Web, Version=2.0.0.0,
Culture=neutral,PublicKeyToken=b03f5f7f11d50a3a”
connectionStringName=”Fbadb_sqlConnectionString”
enablePasswordRetrieval=”false”
enablePasswordReset=”true”
requiresQuestionAndAnswer=”true”
applicationName=”/”
requiresUniqueEmail=”false”
passwordFormat=”Hashed”
maxInvalidPasswordAttempts=”5″
minRequiredPasswordLength=”1″
minRequiredNonalphanumericCharacters=”0″
passwordAttemptWindow=”10″
passwordStrengthRegularExpression=”"/>
</providers>
</membership>
<!–Membership Provider Ends–>

<!–Role Provider Starts–>
<roleManager enabled=”true” defaultProvider=”Fbadb_ASPNETSqlRoleProvider”>
<providers>
<add name=”Fbadb_ASPNETSqlRoleProvider”
connectionStringName=”Fbadb_sqlConnectionString”
applicationName=”/”
type=”System.Web.Security.SqlRoleProvider,
System.Web,Version=2.0.0.0,
Culture=neutral,PublicKeyToken=b03f5f7f11d50a3a”/>
</providers>
</roleManager>
<!–Role Provider Ends–>

As show in the below image

Web configuration file

Save the web.config file and run ASP.NET configuration wizard by clicking on Website menu and click ASP.NET Configuration

ASP.NET Configuration wizard

ASP.NET Configuration wizard

To test the Membership and Role provider click provider tab and then click on Select a different provider for each feature (advanced)

Select your Membership provider name and click on Test link

ASP.NET Configuration wizard - Testing the Membership and Role Provider

If you can see the message like ‘Successfully established a connection to the database’ think that the communication between the interface and database is successfull

Now go on to create the user

Click on the Security tab of ASP.NET web site administration tool, under Users section click the link Select authentication type and select the radio button From the internet click Done

Then, again click on Security tab click on Create user fill the appropriate fields

Creating the user

Creating two sharepoint sites (one is web application and other extending the web application)

Go to Central Administration > Application Management > Create or Extend Web Application > Create New Web Application

Fill the appropriate fields

Creating the web application

Create a site collection by choosing a template (team site, collaboration portal etc)

After creating the Top Level Site Successfully

Now, Extend the web application

Go to Central Administration > Application Management > Create or Extend Web Application > Extend Web Application to Another IIS Web Site

Extending web application

After Extending the web application, now we should configure connection string in web.config file’s of sharepoint site (web application and extended application) by adding the connecton string tag exactly below the </configSections> tag and above the <sharepoint> tag (Note: Change the Data Source name according to your database servername)

<connectionStrings>
<add name=”FBA_sqlConnectionString” connectionString=”uid=sa;pwd=sa;Initial Catalog=FBADB;Data Source=fivenumber” />
</connectionStrings>

See the image below:

Web Configuration File of web application

Confiure Membership and Role provider in both the sharepoint sites (web application and extended application)

Search for the machinekey tag (<machineKey validationKey=”79DDCD075B91C0B088FA25244D65D0745641F91E8A823392″
decryptionKey=”C855BB4C77B455A6706638B8A9D1439B5BB0F3612F2F9DCA” validation=”SHA1″ />)

Copy and paste the below tags exactly after the machinekey tag

<!–Membership provider starts–>
<membership defaultProvider=”Fbadb_ASPNETSqlMembershipProvider”>
<providers>
<add name=”Fbadb_ASPNETSqlMembershipProvider”
type=”System.Web.Security.SqlMembershipProvider,
System.Web, Version=2.0.0.0, Culture=neutral,
PublicKeyToken=b03f5f7f11d50a3a”
connectionStringName=”FBA_sqlConnectionString”
enablePasswordRetrieval=”false”
enablePasswordReset=”true”
requiresQuestionAndAnswer=”true”
applicationName=”/”
requiresUniqueEmail=”false”
passwordFormat=”Hashed”
maxInvalidPasswordAttempts=”5″
minRequiredPasswordLength=”1″
minRequiredNonalphanumericCharacters=”0″
passwordAttemptWindow=”10″
passwordStrengthRegularExpression=”" />
</providers>
</membership>
<!–Membership provider starts–>
<!–Role provider starts–>
<roleManager enabled=”true” defaultProvider=”Fbadb_ASPNETSqlRoleProvider”>
<providers>
<add name=”Fbadb_ASPNETSqlRoleProvider”
connectionStringName=”FBA_sqlConnectionString”
applicationName=”/”
type=”System.Web.Security.SqlRoleProvider,
System.Web,Version=2.0.0.0,
Culture=neutral,PublicKeyToken=b03f5f7f11d50a3a” />
</providers>
</roleManager>
<!–Role provider ends–>

See the below image:

Configuring Membership and Role Provider

Configure the authentication type in central administration

Go to Central Administration > Application Management > Authentication Providers

Click on the extended web application (2nd in the row) enter the Membership provider name and Role provider name as shown in the below image:

Configuring Authentication Type

Now, add the user in the web application  (which you have created in SQL database) in Site Settings > Permissions > Add Users

Try to access the extended form based authentic web application

Form based authentication - SQL login

Extend the web application on to port 6

copy & paste the below tags exactly after machinkey tag (<machineKey validationKey=”7B896F9AC751CE89F7EEB83E766CF6004D42A26DB9C26C95″ decryptionKey=”2DB30482C44B8B6EE13444509E5243E761241B67209B6FF2″ validation=”SHA1″ />)

<membership defaultProvider=”LDAPMember”>
<providers>
<add name=”LDAPMember” type=”Microsoft.Office.Server.Security.LDAPMembershipProvider, Microsoft.Office.Server, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71E9BCE111E9429C” server=”fivenumber” port=”389″ useSSL=”false” userDNAttribute=”uid” userNameAttribute=”uid” userContainer=”*” userObjectClass=”person” userFilter=”(ObjectClass=person)” scope=”Subtree” otherRequiredUserAttributes=”sn,givenname,cn” />
</providers>
</membership>

<roleManager defaultProvider=”AspNetWindowsTokenRoleProvider” enabled=”true” cacheRolesInCookie=”true” cookieName=”.PeopleDCRole”>
<providers>
<add name=”LDAPRole” type=”Microsoft.Office.Server.Security.LDAPRoleProvider, Microsoft.Office.Server, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71E9BCE111E9429C” server=”fivenumber” port=”389″ useSSL=”false” groupContainer=”*” groupNameAttribute=”cn” groupMemberAttribute=”member” userNameAttribute=”uid” dnAttribute=”fullname” groupFilter=”(ObjectClass=dominogroup)” scope=”Subtree” />
</providers>
</roleManager>

Register the Membership Provider in Web.config file of web application (created on port 5)

copy & paste the below tags exactly after machinkey tag (<machineKey validationKey=”17546320333E569C03469848807DDC42B88B99B6467F6172″ decryptionKey=”B8E349D60494DDF780898F55B74024D00048D5EF4F956BCB” validation=”SHA1″ />)

<membership defaultProvider=”LDAPMember”>
<providers>
<add name=”LDAPMember” type=”Microsoft.Office.Server.Security.LDAPMembershipProvider, Microsoft.Office.Server, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71E9BCE111E9429C” server=”fivenumber” port=”389″ useSSL=”false” userDNAttribute=”uid” userNameAttribute=”uid” userContainer=”*” userObjectClass=”person” userFilter=”(ObjectClass=person)” scope=”Subtree” otherRequiredUserAttributes=”sn,givenname,cn” />
</providers>
</membership>

<roleManager defaultProvider=”LDAPRole” enabled=”true” cacheRolesInCookie=”true” cookieName=”.PeopleDCRole”>
<providers>
<add name=”LDAPRole” type=”Microsoft.Office.Server.Security.LDAPRoleProvider, Microsoft.Office.Server, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71E9BCE111E9429C” server=”fivenumber” port=”389″ useSSL=”false” groupContainer=”*” groupNameAttribute=”cn” groupMemberAttribute=”member” userNameAttribute=”uid” dnAttribute=”fullname” groupFilter=”(ObjectClass=dominogroup)” scope=”Subtree” />
</providers>
</roleManager>

Register the Membership Provider in Web.config file of extended web application (which was extended on port 6)

copy & paste the below tags exactly after machinkey tag (<machineKey validationKey=”17546320333E569C03469848807DDC42B88B99B6467F6172″ decryptionKey=”B8E349D60494DDF780898F55B74024D00048D5EF4F956BCB” validation=”SHA1″ />)

<membership defaultProvider=”LDAPMember”>
<providers>
<add name=”LDAPMember” type=”Microsoft.Office.Server.Security.LDAPMembershipProvider, Microsoft.Office.Server, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71E9BCE111E9429C” server=”fivenumber” port=”389″ useSSL=”false” userDNAttribute=”uid” userNameAttribute=”uid” userContainer=”*” userObjectClass=”person” userFilter=”(ObjectClass=person)” scope=”Subtree” otherRequiredUserAttributes=”sn,givenname,cn” />
</providers>
</membership>

<roleManager defaultProvider=”LDAPRole” enabled=”true” cacheRolesInCookie=”true” cookieName=”.PeopleDCRole”>
<providers>
<add name=”LDAPRole” type=”Microsoft.Office.Server.Security.LDAPRoleProvider, Microsoft.Office.Server, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71E9BCE111E9429C” server=”fivenumber” port=”389″ useSSL=”false” groupContainer=”*” groupNameAttribute=”cn” groupMemberAttribute=”member” userNameAttribute=”uid” dnAttribute=”fullname” groupFilter=”(ObjectClass=dominogroup)” scope=”Subtree” />
</providers>
</roleManager>

After completing the above steps go to

Central Administration > Application Management > Authentication Providers

Click on the extended web application (2nd one in the row)

• Select the Authentication Type to ‘Forms’
• Enter the Membership Provider Name as ‘LDAPMember’
• Enter the Role Manager Name as ‘LDAPRole’

LDAP Authentication Type

Click ‘Save‘

After completing the above configuration settings

Add the LDAP user in port 5 site.

Add LDAP Member

Now, try to access the extended web application which was created on port 14 with LDAP username and password

Regional and Language Options

In Regional and Language Options box, under Supplemental language support section, check both check boxes
Install files for complex script and right-to-left languages
and
Install for East Asian languages
Click OK to install
Download language packs for Microsoft Office SharePoint Server (MOSS) 2007:

Select the language from Change Language dropdownlist

Available language packs:

Arabic
Bulgarian
Catalan
Chinese (Simplified)
Chinese (Traditional)
Croatian
Czech
Danish
Dutch
English
Estonian
Finnish
French
German
Greek
Hebrew
Hindi
Hungarian
Italian
Japanese
Korean
Latvian
Lithuanian
Norwegian (Bokmal)
Polish
Portuguese (Brazil)
Portuguese (Portugal)
Romanian
Russian
Serbian (Latin)
Slovak
Slovenian
Spanish
Swedish
Thai
Turkish
Ukrainian

After downloading the Server Language Pack.img

Extract the ServerLanguagePack.img file (I prefer to extract using ISO Edit)

Extract the ServerLanguagePack.img

Run Setup

After installing the language pack

Rerun the Sharepoint Products and Technologies Configuration Wizard using default settings.(If you don’t run the language pack will not be installed properly)

To run the Sharepoint Products and Technologies Configuration Wizard:

Click Start > Programs > Administration Tools click sharepoint Products and Technologies Configuration Wizard

then click Next

Click Yes in the dialog box.

On the modify server farm settings, click Do not disconnect from this server farm, then Next

After configuration successful click Finish

After success installation, you will be find the language pack which you installed before in the dropdownlist while creating the site collection

Creating site collection

Result:

Sharepoint collaboration portal in German language

Figure 1

Figure 1 of 2

Figure 2 of 2

Figure 3

Figure 4

Mail configured document library

Configure SMTP relay setting:

This can be done by network administrator, ask network person to add the Sharepoint server IP address in the relay restriction list as show in the above Figure 1

Configure Incoming E-Mail Settings in central administration:

As shown in Figure 1 of 2 and Figure 2 of 2

Creating Document library:

While creating the document library make sure to select the radio button ‘Allow this document library to receive e-mail’ to ‘Yes’

Follow the setting as show in the Figure 3

Configure incoming E-Mail Settings in document library settings:

Make sure that the settings match with the Figure 4

Install the SMTP service

Configure the SMTP service

Configure the SMTP service 'Relay settings'

Configure outgoing e-mail settings in Sharepoint Central Administration

Install SMTP service:

• Start > Settings > Control Panel Double click Add or Remove Programs.
• In Add or Remove Programs click on Add/Remove Windows Components.
• In the components box double click Application Server or check the Application Server and then click Details button below
• Now, you can see one more box, double click Internet Information Services (IIS) or check the Internet Information Services (IIS) and then click Details button below
• In the Internet Information Services (IIS) box, select the SMTP Service check box then click OK and click again OK to return Windows Commponents box, then click Next
• After installing the SMTP Service, click Finish button

Configure the SMTP service in IIS:

• Start > Settings > Control Panel, double click on Administrative Tools, open Internet Information Services (IIS)
• In IIS expand the treeview right click on SMTP virtual server and then click on Properties
• Click Access tab, under Access control click Authentication button
• In Authentication box, under Select acceptable authentication methods for this resource section confirm that anonymous access is checked and then click OK
• On the Access tab, under Relay restriction click on Relay button
• Under Relay Restriction box, to configure replaying from any of the server, select All except the list below
• To configure from one or more specified server select Only the list below and click on Add button to add the IP address, then click OK and again OK to close Relay Restrictions box and again OK to close properties box.

Configure outgoing e-mail settings in central administration:

• Open Central Administration > Operations, under Topology and Services click the link Outgoing e-mail settings.
• Type the Outbound SMTP, from address in the appropriate boxes.
• Set the character set to ’65001 (Unicode UTF-8)’ or set the character set to appropriate language.

But when I type keywords to search my business data (business data is nothing but apart from content database like Adventureworks, Northwind etc.) in sharepoint site, I was unable to view the single result, though the search is configured well for sharepoint site.

I did R & D on this and came to know that we should configure the search settings explicitly in the shared service administration for business data to display the results in sharepoint results.aspx

In this post we learn how to configure search for business data.

Steps:

• Go to Shared Service home page, under Search section click on Search Settings

Shared Services Home

• In the Configure Search Settings page click on Content sources and crawl schedules

Configure Search Settings Page

• In the Manage Content Sources page click on New Content Source which create new content source

Create New Content Source

• In the Add Content Source page type Name of the content source in the appropriate box, select the content source type as Business Data, under Applications select Crawl entire Business Data Catalog to crawl all application in the Business Data Catalog, else select Crawl selected applications to crawl specific application(s) and select the application instance then click OK.

Add Content Source

• Now we are almost done, it takes some time to crawl the content source, wait for few minutes, to see the search result(s) type the keyword related to the business data in sharepoint search box, now I want to check the results and I will type Race keyword which is there in the business data and now I can see the results perfectly

Business Data Results