New article from MSDN, SharePoint 2010 Architecture Overview, covers high level overview of SharePoint 2010 architectures. It covers SharePoint Development stack, the server and client object models, sandboxed & farm solutions, workflows and more ...
Check it out at: http://msdn.microsoft.com/en-us/library/gg552610.aspx
This article also enables you to do further researches on each discussed topic.
Tuesday, 22 February 2011
Thursday, 17 February 2011
Sharepoint 2010 Host-named site collection
In SharePoint environment, site collection can be created with following naming pattern:
One way to do this is to create SP Web Application for each application, however this way does not scale.
Create hundred of Web Application in a WFE does not look good to me. Some information regarding SharePoint limits and boundaries here.
Another way to do this is use host-named site collection. With one site collection per application, this scales as much as site collection does.
SharePoint Server 2010 provides two significant improvements to host-named site collections: the ability to use managed paths with host-named site collections, and the ability to use off-box SSL termination with host-named site collections.
Create a host-named site collection
You must use Windows PowerShell to create a host-named site collection. You cannot use the SharePoint Server 2010 Central Administration Web application to create a host-named site collection, but you can use Central Administration to manage the site collection after you have created it.
Reference: Plan for host-named site collections (SharePoint Server 2010)
http://company.com/sites/app1However, if there is a requirement to create applications with its unique DNS names, e.g app1.company.com, app2.company.com, while still maintain scalability of your SP Farm?
http://company.com/sites/app2
One way to do this is to create SP Web Application for each application, however this way does not scale.
Create hundred of Web Application in a WFE does not look good to me. Some information regarding SharePoint limits and boundaries here.
Another way to do this is use host-named site collection. With one site collection per application, this scales as much as site collection does.
SharePoint Server 2010 provides two significant improvements to host-named site collections: the ability to use managed paths with host-named site collections, and the ability to use off-box SSL termination with host-named site collections.
Create a host-named site collection
You must use Windows PowerShell to create a host-named site collection. You cannot use the SharePoint Server 2010 Central Administration Web application to create a host-named site collection, but you can use Central Administration to manage the site collection after you have created it.
New-SPSite http://host.header.site.url -OwnerAlias DOMAIN\username -HostHeaderWebApplication http://servernameTai -
Reference: Plan for host-named site collections (SharePoint Server 2010)
Hosts file and Browsers
Windows Hosts file can be used to re-map host name to an IP. For example, requests for information to particular addresses (hostnames) like “www.example.com” are directed to specific IP Addr.
You can use this technique to test how your web application response to requests with fully qualified domain name, when you don't actually buy any domain name. Say I have a real server with real IP:8.8.8.8. I want to know if my web application render correctly when user browse to [appname].myDomain.com. Add the following entry to the host file (windows\system32\drivers\etc)
Hope this can save someone sometime.
Tai -
You can use this technique to test how your web application response to requests with fully qualified domain name, when you don't actually buy any domain name. Say I have a real server with real IP:8.8.8.8. I want to know if my web application render correctly when user browse to [appname].myDomain.com. Add the following entry to the host file (windows\system32\drivers\etc)
8.8.8.8 appname.myDomain.comIt works well for awhile. Someday, some one come & buy myDomain.com, point it to another server say DomainMarket.com. The technique still work if your Internet does not goes through a proxy server (e.g at school or many businesses). when your browser behind a proxy, the proxy perform DNS lookups for you, then the HOSTS file is ignored. Ping in command line to appname.myDomain.com still resolves to 8.8.8.8, while your browser still resolves to DomainMarket.com
Hope this can save someone sometime.
Tai -
Subscribe to:
Posts (Atom)