Before starting this blog let me define multitenancy to ensure uniform understanding. Multitenancy in this context mean isolation of data (including backups), Isolation of usage (what data and services are exposed to the users), isolation of administration (administration of sites, services, customizations), etc. If we consider a hosted environments like SharePoint Online it offers customers 2 mode of hosting
Recently I was involved in the production deployment of a MOSS based Internet facing site. Just like any other site, this also had its search requirements. In the dry run of the production deployment, initially I deployed the application with Integration Authentication and then started the crawl. Post completion of this search was working fine. Since this was an Internet facing site, then as my next logical step in the deployment process was to change the settings of the Authentication of Application in Central Admin and within the Web Application permissions to Anonymous. We also removed Impersonate to true in Web.config as it was no longer required.
Continue reading "Search Crawl Issue for an Internet facing MOSS Site" »
MOSS supports the creation of custom timer jobs. These jobs are of repititive nature and serve the purpose of a scheduled or immediate execution of a task. In cases where the concurrency issue arise you need to attain lock on the code in the Execute() method of the timer class.
Continue reading "Why is the concept of a list so important in SharePoint" »
Last week we saw the First Part of the blog "Adding Additional Metadata to the list/library". Today we will see what next to be done post creation of the database.
The following activities will have to be done to take this to completion
• Remove the existing edit metadata page
• Create a new ASPX page which can be used to capture both the standard flat metadata and the hierarchical metadata
• Link this page with the document library
• Create a custom Edit Metadata page which would contain both the linear and the hierarchial metadata.
• Replace the existing edit metadata page with the custom one
Continue reading "Additional Relational Metadata for artifacts in MOSS -- Part 2" »
Content Databases of web sites in MOSS can get reach their maximum storage limit at times. In a real world scenario there may arise a need to move a Site from one Content Database to another to accommodate the proper functioning and performance which can be directly dependent on the available storage limit of the Content Database. Hence it is always advised that you change the Sites Content database. The STSADM tool provides the functionality of performing this operation with ease.
Continue reading "Move Sites Across Content Databases in MOSS using STSADM" »
Organizations which select Microsoft Office SharePoint Server 2007 (MOSS 2007) for managing artifacts (like documents, records) often leverage the out of the box (OOTB) features available in MOSS like libraries, OOTB Workflows, version management, workspaces, etc for the same. When it comes to the metadata, often there might be requirement to attach additional relational metadata in addition to the flat/standard metadata offered by MOSS. E.g. Documents/Records may have to be associated with different hierarchies like ABC.doc may need to be part of India zone and US zone drilling down through the structure, so that the document is retrieved when queried on data across both the zones.
We (myself and one of my collegue Prasana Srinivasan) did a small exercise and would like share the custom approach we took to add additional hierarchical metadata which involved a custom database and ASPX Page. We will have this as a 2 part series.
Continue reading "Additional Relational Metadata for artifacts in MOSS" »
There has been lot of confusion on the licensing information in SharePoint like what comes free, what is the licensed part of the product, what are the various client access license (CALs) options available. The following diagram helps clarify most of the doubts one will have around this.
Often there is a request which keeps coming asking for guidelines to select between sub site and site collections. Some of the following points can be kept in mind while taking a decision between the 2
101 Reasons to Adopt Microsoft Office SharePoint Server 2007: Handbook, fourth in the series of handbooks from Infosys' Microsoft Technology Center has been released. It provides critical evaluation of the features, view points and reasons for adopting MOSS 2007 in the enterprises. You can find the same at http://www.infosys.com/research/publications/books.asp.
Continue reading "101 Reasons to Adopt Microsoft Office SharePoint Server 2007: Book Released" »
Today we will look at the option of Site Definitions and Features for modifying the Master Pages.
Continue reading "Branding in SharePoint Technologies (PART 4)" »
Today we will look 3 options available for the modification of Site Master Pages. They include SP Designer, Site Template and File System options.
Continue reading "Branding in SharePoint Technologies (PART 3)" »
In this Part 2 blog I will focus more on Master Pages and will leave the css and themes out of scope of this blog 4 part blog series on branding. To start of let us understand what is a master page all about? Though most of us are aware of this, just to ensure everybody understands the same...
Continue reading "Branding in SharePoint Technologies (PART 2)" »
With SharePoint Technologies (Microsoft Office SharePoint Server (MOSS) 2007 and Windows SharePoint Services (WSS) 3.0 collectively referred to as) entering the mainstream development arena on the Microsoft platform, it is imperative for decision-makers to decide upon a strategy for adopting this technology.
