Eric's profileiTrain Eric Ku BlogPhotosBlogListsMore ![]() | Help |
|
|
26 July Microsoft SharePoint Administration Toolkit v3.0The Microsoft SharePoint Administration Toolkit contains functionality to help manage Office SharePoint Server 2007 and Windows SharePoint Services version 3.0. This toolkit contains the ability to diagnose performance issues, perform bulk operations on site collections, an Stsadm operation to update alert e-mails after the URL for a Web application has been changed, and a User Profile Replication Engine tool. Click here for FREE download and detail. The installer is about 1.3MB in size.
25 July How to convert Excel Spreadsheet into a SharePoint ListConverting the spreadsheet into a listHere are the steps we took to convert an Excel spreadsheet to a SharePoint list.
22 February Installing Sharepoint on Windows Server 2008Since Sharepoint is no longer included in Windows Server 2008, you have to install it yourself. The issue is this. If you try to install WSS 3.0 on Windows 2008, it will not install. It will tell you that you have to install SP1 and you will probably wonder how you can do that without first installing WSS 3.0. The answer is that you need to install the Windows Sharepoint Services 3.0 with SP1 installer that bundles Sharepoint 3.0 and SP1 together. download Windows SharePoint Services 3.0 with SP1. SharePoint Server Farm Q & A1. What is a SharePoint Farm?
In the context of SharePoint, the term 'farm' is used to describe a collection of one or more SharePoint servers and one or more SQL servers that come together to provide a set of basic SharePoint services bound together by a single Configuration Database in SQL. 2. What is the difference between an 'Application Server' and a 'WFE Server'?
When SharePoint is installed, you have to select one of three installation options, they are:
An 'Application Server' is a server that is capable of running any of the services apart from the Windows SharePoint Services Web Application service. A 'Web Front End' (sometimes called a WFE) is the opposite in that it can only run the Windows SharePoint Services Web Application service. 'Complete' means that the server can run any SharePoint service.
The problem with selecting anything other than 'Complete' is that it means if you ever change your mind about what services a server can run, you'll need to re-install SharePoint on that server. For that reason alone, I would always recommend that you choose 'Complete' unless you have a very good reason to do otherwise.
3. How should I design my web applications within my farm?
One of the rules about SharePoint farms is that every server that is running the Windows SharePoint Services Web Application service has to serve every web application in the farm. It is not possible to say "Server X serves Web Application X". This means that when you create a new web application in Central Administration, the Windows SharePoint Services Timer on each server that is running the Windows SharePoint Services Web Application service creates the necessary sites and application pools in IIS to serve the web application.
What about Central Administration?
The Central Administration web application is no exception to this rule in that the web application does exist on every web server. However, the Central Administration service only runs on a single server and it is that server that responds to Central Administration requests. This is why the Central Administration site is always bound to a server name rather than an NLB-enabled host header.
4. What is a farm's relationship with the SSP One of the optional components in a farm is a Shared Service Provider (SSP). SSPs are optional applications that use a combination of web applications and server services to provide several shared services. The key thing to note here is that the SSP does not run on any single server within the farm, there is no such thing as an 'SSP server'. The SSP is actually an application that requires the following:
Once an SSP is configured, its shared services can be provided to all of the web applications within the local farm. An SSP can also provide services to separate farms; this is called 'cross-farm Shared Services' and is very common in large deployments.
5. How many SSPs should I have in my farm?
Generally speaking it is best practice to have only one SSP per farm. It is possible to have multiple SSPs, but that configuration introduces a whole load of issues.
Each Web Application in your farm must get its Shared Services from a single SSP; it is not possible to pick and choose certain SSPs for certain shared services. Neither is it possible to say that a certain SSPs only provides certain services. The problem with this is that if you do have 2 SSPs, then you have 2 My Sites per user, 2 profiles per user, 2 sets of search indexes etc. Companies that do have this configuration, generally have to do a load of development work to keep the SSPs in sync with each other and make sure that user's are redirected to the correct SSP for their My Site.
There are only two common reasons for having multiple SSPs, they are:
6. When to have multiple farms?
Several scenarios where multiple farms make sense:
27 November Forms Authentication in SharePointExplore several new features for authentication and authorization in Microsoft Office SharePoint Server (MOSS) 2007 and Windows SharePoint Services 3.0 that make it easier to develop and deploy solutions in Internet-facing and extranet environments. Here is the useful content from MSDN:
http://msdn.microsoft.com/en-us/library/bb975136.aspx
Introduction to Forms Authentication in SharePoint Products and Technologies Deciding to Use Forms Authentication Reviewing a Typical Scenario for Authentication Reviewing Changes to Authentication Terminology Setting Up Forms Authentication Granting Permissions to Create My Sites http://msdn.microsoft.com/en-us/library/bb975135.aspx
Developing Custom Membership and Role Providers Applying the XML File for the Data Source Inheriting from the Membership and Role Base Classes Minimum Interfaces Required by MOSS and Windows SharePoint Services Registering the Custom Provider Debugging the Custom Provider Writing a Custom Forms Logon Page Using Web Services with a Site Protected by Forms Authentication http://msdn.microsoft.com/en-us/library/bb977430.aspx
Introduction to Differences Between Forms Authentication and Windows Authentication Crawling Content Integrating with the 2007 Microsoft Office System Opening Documents in Internet Explorer Checking the "Sign me in automatically" Check Box at Logon Using an HttpModule During Authentication User Profile Imports Resolving Names Using an LDAP Provider Using the Microsoft Single Sign-On Service Conclusion Business Data Catalog tool for all SharePoint Developers and AdministratorsDo we really have to know XML coding to create an application defination for SharePoint Business Data Catalog? Here is the GUI tool can do it without coding XML.
BDC Meta Man is the first Business Data Catalog tool for all SharePoint Developers and Administrators interested in line of business data integration with SharePoint. Without writing a single line of code you can be viewing and searching across your business data through Microsoft Office SharePoint Server 2007 in minutes.
To download a trial copy click here http://www.lightningtools.com/bdc-meta-man/default.aspx
So, what is the applicaiton defination? An application definition describes a database or web service. It includes connection settings, authentication mode, definitions of available entities, and other information. After you upload an application definition to the Business Data Catalog, you can use its entities in lists, web parts, search, user profiles and custom applications. |
|
|