You are on page 1of 21

Five Keys to Building Better SharePoint Sites

Written by Doug Davis, Director of Product Management, Quest Software Contributing Author Adam Woodruff, Solutions Architect, Quest Software

White Paper

2009 Quest Software, Inc. ALL RIGHTS RESERVED.


This document contains proprietary information, protected by copyright. No part of this document may be reproduced or transmitted for any purpose other than the reader's personal use without the written permission of Quest Software, Inc.

WARRANTY
The information contained in this document is subject to change without notice. Quest Software makes no warranty of any kind with respect to this information. QUEST SOFTWARE SPECIFICALLY DISCLAIMS THE IMPLIED WARRANTY OF THE MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. Quest Software shall not be liable for any direct, indirect, incidental, consequential, or other damage alleged in connection with the furnishing or use of this information.

TRADEMARKS
All trademarks and registered trademarks used in this guide are property of their respective owners. World Headquarters 5 Polaris Way Aliso Viejo, CA 92656 www.quest.com e-mail: info@quest.com Please refer to our Web site (www.quest.com) for regional and international office information. UpdatedAugust 2009

WPA-FiveKeys2BuildingShPSites-US-AG

CONTENTS
INTRODUCTION ..........................................................................................1 THE SHAREPOINT FRUSTRATION PROGRESSION ........................................2 KEY 1: LEVERAGE WEB PARTS WHEREVER POSSIBLE..................................5 THE CASE FOR ADDITIONAL WEB PARTS ............................................................... 5 QUICKLY UNLOCKING SHAREPOINTS FULL POTENTIAL ............................................... 6 1. I just want to combine and enhance information in SharePoint............ 7 2. I want to enhance the user interface and develop applications. ........... 7 3. I want to use SharePoint to front-end my external data, and write back to the external databases from SharePoint......................... 8 KEY 2: USE SIMPLER DEVELOPMENT INTERFACES ......................................9 CONFIGURE RATHER THAN CODE ........................................................................ 9 KEY 3: BUILD UPON THE STRENGTHS OF SHAREPOINT ............................. 11 KEY 4: STOP WORRYING ABOUT WHERE THE DATA LIVES ........................ 13 KEY 5: DONT REINVENT THE WHEEL ........................................................ 15 CONCLUSION ............................................................................................ 16 ABOUT THE AUTHORS ............................................................................... 17 ABOUT QUEST SOFTWARE, INC. ................................................................ 18 CONTACTING QUEST SOFTWARE ....................................................................... 18 CONTACTING QUEST SUPPORT ......................................................................... 18

White Paper

INTRODUCTION
SharePoint is an excellent collaboration platform out of the box, with the added promise of allowing organizations to build business applications on its foundation. In fact, many organizations are thinking beyond using SharePoint just as a document repository and a place for team sites. They are considering (and using) SharePoint for: Hosting simple interfaces for their business applications Re-platforming applications that are based on aging technologies Building new applications as alternatives to .NET development Doing advanced project management portals and other core sites Pushing the collaboration envelope well beyond traditional methods

But using SharePoint beyond its out-of-the-box capabilities to create complex applications can be tedious, cost-prohibitive, time-consuming and, for some, even impossible. To deliver on the promise of SharePoint application development, most organizations are forced to rely on custom coding, with its inherent learning curve, costs and project delays. As long as SharePoint application development is dependent on custom coding, SharePoint cannot be the low-cost platform for rapid application creation that organizations envisioned when they invested in it. A core challenge for many organizations adopting SharePoint is that even basic development tasks can require a major investment in time and resources. Once SharePoint is entrenched in an organization, and its usage requirements become more complex, much more work must be devoted to satisfying those requirements. This paper will first explain how frustrations arise as usage requirements become more complex, then provide guidance to help you address these frustrations.

Five Keys to Building Better SharePoint Sites

THE SHAREPOINT FRUSTRATION PROGRESSION


The typical progression in frustration as SharePoint usage and complexity grows can look something like this:

Unlocking the full potential of SharePoint may not mean creating a customer relationship management (CRM) system, help desk application or project management portal for your organization. It might be simply combining information to improve efficiency of daily tasks so that anybody can take advantage of it. Complex SharePoint usage can include seemingly simple tasks, such as: Enhancing, combining and viewing information Rolling up multiple lists into a report or a 3-D chart Creating a hierarchical list view Modifying information within lists across sites Copying or moving documents between document libraries Creating advanced forms with tabs Improving the flow of actions in an application Combining SharePoint data and external data into sites

Take the basic example below. This site was built in about 15 minutes without any additional Web Parts or coding. The result is a useful site for file sharing and basic collaboration, and may be all an organization needs initially.

White Paper

But satisfaction can quickly lead to frustration as usage and demand for complexity grows.

Five Keys to Building Better SharePoint Sites

You can eliminate this frustration by following five key guidelines for building better SharePoint sites, with more speed and simplicity than you ever imagined. These five keys will help you unlock the full value of SharePoint for your organization to get the most out of your SharePoint investment and provide a richer user experience for everyone. The results will be that: IT can deliver SharePoint as a service to the organization Business owners get as much as they need from SharePoint and can use it as a reliable tool to efficiently manage projects Developers deliver value of SharePoint faster, then can focus on higherend coding (rather than tedious SharePoint tweaks)

White Paper

KEY 1: LEVERAGE WEB PARTS WHEREVER POSSIBLE


Out of the box, Microsoft has delivered a SharePoint framework that enables anyone to add Web Parts, build custom features and make the platform even more valuable. According to MSDN, ASP.NET Web Parts compose an integrated set of controls for creating web sites that enable end users to modify the content, appearance, and behavior of web pages directly in a browser. For our discussion in this paper, Web Parts are controls for creating and modifying SharePoint sites. Microsofts Library of Web Parts includes:
List views List forms Panel menus Document libraries Wikis Blogs Contacts DataViewer Calendars

However, each of these Web Parts is only a piece of the puzzle and each comes with caveats. One good example of this is the native discussion Web Part ,which does not track discussions intuitively and often introduces more confusion than help. Each web part has both the data and the presentation layer bound to the information that it is displaying, which will not allow for a combination of data from multiple lists into a single view. What is commonly known as a parent-child relationship is not possible in this locked-down dynamic.

The Case for Additional Web Parts


Many organizations will build Web Parts to expand SharePoint beyond its native capabilities. In fact, Microsoft encourages the use of custom developed Web Parts for exactly this purpose, even viewing them as part of the general platform. Beyond Microsofts Web Parts, there are many others available in the marketplace. This includes one-off versions developed in-house, those available free on sites like codeplex or www.sharepointforall.com, and those sold by third-party vendors that offer support and upgrades for these commercial offerings.
Web Parts tip: Not all Web Parts are created equal! Some are high-quality, while others arent worth a second glance. Each should be evaluated on its own merit. For serious production environments, its crucial to consider quality and supportability. Web Parts tip: When building, buying or downloading web parts, ensure that they have been designed to support the SharePoint Object Model.

While you can get some Web Parts from various sources, it often makes sense to use a combined set of them to get more from your application. Thats because many of the elements and design parameters will be the same from Web Part to Web Part, and they may even be integrated with one another and designed to work in tandem.
5

Five Keys to Building Better SharePoint Sites

Quickly Unlocking SharePoints Full Potential


Quest Web Parts for SharePoint allow your organization to reap all the benefits of SharePoint by enabling anyone to quickly become an effective SharePoint application designer. These Web Parts cover core areas that make up most of what organizations typically need to build SharePoint sites. They help perform the tedious and frustrating tasks that must occur before anyone even gets to application and business logic. Earlier in this document, we showed a basic SharePoint site (see page 3). In the same amount of time that site was createdabout 15 minuteswe leveraged Quest Web Parts to create this site:

Notice the dramatic change in whats possible in such a short amount of time. The power of these Web Parts increases your organizations ability to deliver SharePoint as a service and improves the business owners satisfaction level (with having all data in one place). And this site was built without coding! The user-friendly Web Parts enables power users, business analysts and developers to make changes like this and other SharePoint enhancements on the fly. The Quest Web Parts solution includes 18 Web Parts, three application templates, computer-based training, free trial downloads of industry-leading workflow software, and more. Lets take a closer look at them based on what your organization wants to do.

White Paper

1.

I just want to combine and enhance information in SharePoint.


The following Quest Web Parts will help you enhance, combine and view information with ease.

QUEST PART qListView

WEB

KEY CAPABILITY

Allows you to easily combine data from multiple lists, even across sites, site collections and Web applications Allows you to create compelling 2-D or 3-D charts with information from multiple lists, even lists in different sites, site collections and Web applications Allows you to combine all your calendars into one view, including data from non-calendar lists Allows you to view data in Microsoft Excel, based on criteria passed from qListView, even when that data is not shown in the qListView Allows you to view the topic and responses of multiple discussion lists in one tree view and preview the selected item in a preview panel

qChartView qCalendarView qExcelView qDiscussionView

2.

I want to enhance the user interface and develop applications.


The following Quest Web Parts help you to rapidly build real applications in SharePoint.

QUEST WEB PART qListForm qSelector qMultiSelector qItemDisplay qPanelMenu qCascadingMenu qCaptionDisplay qHelpLink qPageRedirector

KEY CAPABILITY Provides a more advanced and capable list form, including functionality for separating form into tabs and creating space Displays data from a SharePoint list in a drop-down control Allows you to view master-detail data in multiple selectors Allows you to view a single item that has been selected in the qSelector, qListView or qListForm Allows you to have a collapsible and hierarchical panel menu for better navigation Provides a hierarchical menu system, letting you create complex menus that occupy minimum screen real estate Displays a message from a centralized SharePoint list, which allows you to maintain the content of the message easily Facilitates linking to a help file for your application Allows you to redirect a user to a specific page based on the mapping specified in the page redirector list

Five Keys to Building Better SharePoint Sites

3.

I want to use SharePoint to front-end my external data, and write back to the external databases from SharePoint.
The following Quest Web Parts enable easy data integration, including read/write capability, even in WSS. Its true.

QUEST WEB PART qSiListView qSiListForm qSiChartView qSiSelector

KEY CAPABILITY Displays data from your external data source in a grid and allows you to execute some actions on the data Allows you to create, view and edit your external data in a form Allows you to display your external data in a compelling 2-D or 3-D charts Allows you to display your external data in a dropdown control

The functionality provided in these 18 Web Parts is essential for getting the most from your SharePoint investment. Youd think most of it would natively come with SharePoint, but it doesnt. You might be able to create and design many of these elements using advanced tools such as SharePoint Designer and Visual Studio, but the time required to do so can be prohibitive and these design tools are not for novice users.

What about Visual Studio and SharePoint Designer?


Microsofts SharePoint Designer, Visual Studio and Quest Web Parts are used for different purposes and they complement each other. Visual Studio is used by developers to create web parts or complex, customized workflows. SharePoint Designer is used by developers to customize SharePoint sites, implement pre-configured workflows through a wizard, and to create custom reports. Quest Web Parts for SharePoint enables anyone to become a SharePoint application designer quickly, effectively and successfully.

White Paper

KEY 2: USE SIMPLER DEVELOPMENT INTERFACES


While it would be nice to have a team of .Net developers with SharePoint experience to respond to the requirements of every SharePoint user in an organization, thats not reality. In fact, finding these scarce resources can be difficult and potentially costly. SharePoint administrators, business analysts and power users will encounter a SharePoint limitation that should be a quick fix for the dev team. But changes that require custom development are rarely quick and often make your current environment more complex. And extensive changes involving custom coding pose potential risk over time, as application requirements change. If the original developer doesnt remain on the project, it could create costly, time-consuming rework, degradation in overall quality and questions about supportability.

Configure Rather Than Code


By removing the core challenges of code creation and complex data integration, Quest Web Parts radically simplifies the approach to SharePoint application development. By leveraging this unique, business-driven configuration technology built into every Quest Web Part, you will find yourself performing design tasks you never thought possible, in a fraction of time required by other Web Parts. In fact, the Quest Web Parts embedded configuration tool, ezEdit, allows users to configure rather than code, and reduces the time required to build applications by up to 80 percent. ezEdit allows you to: Move beyond the properties page with a built-in editor Make necessary large-scale changes to a Quest Web Part through an intuitive interface Skip XML, when desired Simplify custom actions, BDC-like capabilities and CAML without the upfront pain Make changes and updates with an immediate view of what has been done

Five Keys to Building Better SharePoint Sites

Figure 1: Quests ezEdit configuration interface radically simplifies Quest Web Part configuration, allowing non-developers to quickly and easily create menus, dashboards, charts and more. For the developer, ezEdit accelerates tedious tasks, but also exposes the code in cases where that is preferred.

10

White Paper

KEY 3: BUILD UPON THE STRENGTHS OF SHAREPOINT


SharePoint is about data, and using that data in new and exciting ways is what you want to do with your SharePoint environment. When you restrict yourself to the native Web Parts, you limit what you can do with the core of SharePoint, namely the data. All of the data in SharePoint is stored in a list. Document libraries, calendars, wikis and even contacts are all simply variations of a list. All of these lists have a particular display and value for the end user when they are created. As time goes on, however, it often makes sense to utilize this data throughout the platform and beyond the natural boundaries of a list. One of the biggest strengths of SharePoint is that the data within a list or library can be normalized using features such as Content Types, Lookup and required fields. Additionally, SharePoint can then front-end this data with an InfoPath form, which may require some level of coding and an understanding about the XML that is used behind this data. Quest Web Parts help you to enhance these basic SharePoint strengths by allowing you to add a number of components. With the qCalendarView, for example, you can take multiple calendars and even non-calendar data and roll them into a single view. No longer will you be attempting to cobble together multiple calendars and keep all of this data up to date manually.

Figure 2: Calendar created by Quest Web Part qCalendarView.

11

Five Keys to Building Better SharePoint Sites

InfoPath, with all its strengths, does not allow you to display data across multiple tabs. This need is real for most organizations and has traditionally been filled by a developer creating an ASP.Net form. Quest Web Parts provide the alternative to custom development. With Quest Web Parts, the end user, business analyst or even developer can consolidate data, create a place to enter additional data, and update it as needed across those multiple locations, without coding. This building block of application development without coding allows you to present any datasuch as that related to the help desk, human resources and customer relationship managementon the fly.

12

White Paper

KEY 4: STOP WORRYING ABOUT WHERE THE DATA LIVES


We consume new data sources at a furious rate. Having to worry about collecting the data into one SharePoint list is an inefficient use of time and resources. So dont worry about it. Leave the data where it is as long as that makes sense for your organization. Tie it all together nicely into a SharePoint dashboard or other mash up Quest Web Parts offer two effective methods to make you forget about where the data resides. The qListView can combine list data from multiple sites, and even between sites, and its fairly straightforward to use and understand. So that only leaves the harder question of how to gather external data from databases such as SQL, Oracle and SAP. One method naturally is to use the Business Data Catalog (BDC), but the BDC is available only in Microsoft Office SharePoint Server and is effectively read-only. In addition, for organizations getting by with WSS, the BDC isnt even an option and the limitation of using SharePoint data can only stifle SharePoint adoption. Consider the fact that there is a small cottage industry on how to use the BDC, a negative indicator for something that should be easy! You can also view external data in SharePoint using the Data Viewer Web Part. And with patience, you can create a data view that you read and write to, but the effort is significant, especially when you are first trying this process out. In the end, many developers get discouraged with the time and effort required to connect to even a simple database via BDC. Quests ezEdit interface is part of the SI Web Parts as well. While it may represent a step beyond what youd have to do with native SharePoint Web Parts, the ability to view, read and write data to and from external systems with little-to-no development completely leapfrogs the capabilities of the native tools. The Quest SI Web Parts simplify the process of connecting to external data and bringing it into SharePoint. And besides bringing in the data, you can use that data, edit it, chart it and create meaningful applications. The result is much greater efficiency, gained by eliminating the need to deploy a different application interface for every CRM, ERP or database system that your organization has purchased and developed. Plus, users across your organization can easily adjust to new applications because theyre leveraging the familiar SharePoint interface. This, of course, reduces desktop management and user training costs while maximizing your investment in SharePoint.

13

Five Keys to Building Better SharePoint Sites

Figure 3: The Quest SI Web Parts simplify the process of connecting to external data and bringing it into SharePoint. And besides bringing in the data, you can use that data, edit it, chart it and create meaningful applications.

14

White Paper

KEY 5: DONT REINVENT THE WHEEL


Your organization is no doubt trying to be more efficient and get more from its existing investments. This certainly holds true for IT when it comes to SharePoint. There is little value in building from scratch if rich templates are available to help streamline application development. Look for these! There are many examples, including: Microsofts Fab 40 http://technet.microsoft.com/en-us/windowsserver/ sharepoint/bb407286.aspx: Here you will find basic free SharePoint templates to use for functions such as the help desk, inventory tracking and call centers. And since all templates can consume other Web Parts, you can enhance these with Quest Web Parts Many organization have connectors for Quest Web Parts or applications they have already created using Quest Web Parts that you can leverage. http://www.quest.com/web-parts-for-sharepoint/partners.aspx Three templates in Quest Web Parts for SharePoint offering: Templates for CRM, help desk and project management teams will get you off to a fast start.

15

Five Keys to Building Better SharePoint Sites

CONCLUSION
SharePoint is an excellent collaboration platform environment out of the box, with the added promise of allowing organizations to build business applications. But most organizations are forced to rely on custom development coding, with its inherent learning curve, costs and project delays. This paper discussed how frustrations arise as usage requirements become more complex, then explained how you can eliminate this frustration by following five key guidelines for easily building better SharePoint sites without custom coding. Central to these five guidelines are Quest Web Parts, which offer value and capabilities far beyond whats available in native tools. Leveraging Quest Web Parts will help you get the most out of your SharePoint investment and provide a richer user experience for everyone.

16

White Paper

ABOUT THE AUTHORS


Adam Woodruff
Adam Woodruff has been creating solutions that utilize Microsoft systems and infrastructure since 1998. He is skilled in Microsoft Exchange, Active Directory and SharePoint integrations and configurations for deployment and operational management. He is currently a solutions architect for Quests SharePoint products. Prior to Quest, Adam worked for a number of consulting partners as a senior consultant for Windows Server 2008 and 2003, Exchange 2007 and 2003, SQL Server 2005 and SharePoint 2007 (MOSS). He has held positions at Convergent Consulting, Andelogic, Inc., Tech Heads, Inc., Interlink Group, LLC, and Microsoft, among others.

Doug Davis
Since 1999, Doug Davis has held senior positions at Quest Software in development, research and now product management. He is currently the director of product management for Quest's SharePoint group. Prior to joining Quest, Doug spent seven years as a network administrator for Stentor Canada and Telesat Canada. Doug graduated from Carleton University in Ottawa Canada.

17

Five Keys to Building Better SharePoint Sites

ABOUT QUEST SOFTWARE, INC.


Quest Software, Inc., a leading enterprise systems management vendor, delivers innovative products that help organizations get more performance and productivity from their applications, databases, Windows infrastructure and virtual environments. Quest also provides customers with client management through its ScriptLogic subsidiary and server virtualization management through its Vizioncore subsidiary. Through a deep expertise in IT operations and a continued focus on what works best, Quest helps more than 100,000 customers worldwide meet higher expectations for enterprise IT. Quest Software helps organizations deliver, manage and control complex database environments through award-winning products for Oracle, SQL Server, IBM DB2, Sybase and MySQL. Quest Software can be found in offices around the globe and at www.quest.com.

Contacting Quest Software


Phone: Email: Mail: 949.754.8000 (United States and Canada) info@quest.com Quest Software, Inc. World Headquarters 5 Polaris Way Aliso Viejo, CA 92656 USA www.quest.com

Web site:

Please refer to our Web site for regional and international office information.

Contacting Quest Support


Quest Support is available to customers who have a trial version of a Quest product or who have purchased a commercial version and have a valid maintenance contract. Quest Support provides around the clock coverage with SupportLink, our web self-service. Visit SupportLink at http://support.quest.com From SupportLink, you can do the following: Quickly find thousands of solutions (Knowledgebase articles/documents). Download patches and upgrades. Seek help from a Support engineer. Log and update your case, and check its status.

View the Global Support Guide for a detailed explanation of support programs, online services, contact information, and policy and procedures. The guide is available at: http://support.quest.com/pdfs/Global Support Guide.pdf
18

You might also like