Geeks With Blogs
Fringe SharePoint Continued
I feel a series coming on! I have been involved with a client to develop and customize their present SharePoint Environment. I have incorporated several solutions I would like to share. It was a learning experience and it was definitely Fringe SharePoint!!! The purpose of this post is to set up the scenario and to describe all the factors that were involved with the decision making of the overall solution. I hit several walls and blocking issues and feel it's important for anyone doing anything remotely close to this or maybe incorporating parts of this solution to understand.

This customer has a fairly common portal. I will try to describe the portal in generic terms, it is not important to understand the specific purpose of sub sites but to understand the overall structure of sites. The environment looks like the following:

The above is pretty common in companies. Usually there is only one company but I am using this example to show the hierarchy relationship of sites. This specific company was getting quite a bit of growth on the departments sites. It was expecting quite a bit of growth in the future and wanted to manage the quota at the department level. 

Problem 1: you cannot place quota on sub sites. It can only be set at the Site collection level.

The next thing that the client was complaining about was the fact that departments moved companies. In the present environment a department site needed to be moved(imported/exported) to other locations(Companies).

Problem 2: No way for companies to be able to move sites without having more than desired access to the site and server.

From an admin perspective, it is getting tougher and tougher to maintain the site collection because of the growing quota. Maintaining site quota to 100G recommended limit from Microsoft will very quickly be exceeded.

Problem 3: In order to manage content database size you will need to have a little more complicated process to provisioning new sites. Or create and manage Web Application to house a section of the sites so they are created under a new content database.

One thing I should mention is that several extensions of a web Application have been created to expose the sites with anonymous access, SSL and basic authentication schemes. Using the diagram above, it is desired that everyone inside and outside the company be able to access the Company level of the site collection. This part of the site is to be exposed anymously, Once navigating to the department level, it is desired that authentication occurs at that point. The department sites would need to be exposed over SSL.

Each Company has a webpart that lists all the department sites under that company. This web part has evolved over time, to satisfy and work under changing security schemes. It first started as a dataview webpart. Issues were encountered with the authentication of the connection string. It then was re-engeneered to be a visual studio web part and pull sub sites relative to the company the webpart was added to. The functionality of the webpart is really to list all the department sites by name and have a clickable link to them.

I feel like this is getting really long winded but In my next post I will describe the overall solution and split it up into sections that you can develop yourself as you see fit and just tackle one problem at a time.

Stay tuned!


  Posted on Tuesday, August 25, 2009 7:25 PM SharePoint | Back to top

Comments on this post: Mission Imposible Part 1 (introduction)

No comments posted yet.
Your comment:
 (will show your gravatar)

Copyright © juanlarios | Powered by: