21,99 €
Mehr erfahren.
- Herausgeber: John Wiley & Sons
- Kategorie: Fachliteratur
- Sprache: Englisch
* Microsoft SharePoint now has a 10 percent share of the portal market, and the new release, which features enhanced integration with Office 2007, is sure to give SharePoint a boost * Offers clear instructions and soup-to-nuts coverage of this complex product, focusing instead on practical solutions to real-world SharePoint challenges * Features tips, tricks, and techniques for administrators who need to install and configure a SharePoint portal as well as ordinary users who need to populate and maintain the portal and use it for collaborative projects * Topics covered include setting up a SharePoint portal, matching SharePoint to business needs, managing portal content, branding, collaborating on SharePoint sites, using a portal to improve employee relations and marketing, putting expense reports and other interactive forms on a portal, and monitoring and backing up SharePoint
Sie lesen das E-Book in den Legimi-Apps auf:
Seitenzahl: 586
Veröffentlichungsjahr: 2011
Ähnliche
Microsoft® SharePoint® 2007 For Dummies®
by Vanessa Williams
Microsoft® SharePoint® 2007 For Dummies®
Published byWiley Publishing, Inc.111 River StreetHoboken, NJ 07030-5774www.wiley.com
Copyright © 2007 by Wiley Publishing, Inc., Indianapolis, Indiana
Published by Wiley Publishing, Inc., Indianapolis, Indiana
Published simultaneously in Canada
No part of this publication may be reproduced, stored in a retrieval system or transmitted in any form or by any means, electronic, mechanical, photocopying, recording, scanning or otherwise, except as permitted under Sections 107 or 108 of the 1976 United States Copyright Act, without either the prior written permission of the Publisher, or authorization through payment of the appropriate per-copy fee to the Copyright Clearance Center, 222 Rosewood Drive, Danvers, MA 01923, (978) 750-8400, fax (978) 646-8600. Requests to the Publisher for permission should be addressed to the Legal Department, Wiley Publishing, Inc., 10475 Crosspoint Blvd., Indianapolis, IN 46256, (317) 572-3447, fax (317) 572-4355, or online at http://www.wiley.com/go/permissions.
Trademarks: Wiley, the Wiley Publishing logo, For Dummies, the Dummies Man logo, A Reference for the Rest of Us!, The Dummies Way, Dummies Daily, The Fun and Easy Way, Dummies.com, and related trade dress are trademarks or registered trademarks of John Wiley & Sons, Inc. and/or its affiliates in the United States and other countries, and may not be used without written permission. Microsoft and SharePoint are registered trademarks of Microsoft Corporation All other trademarks are the property of their respective owners. Wiley Publishing, Inc., is not associated with any product or vendor mentioned in this book.
LIMIT OF LIABILITY/DISCLAIMER OF WARRANTY: The publisher and the author make no representations or warranties with respect to the accuracy or completeness of the contents of this work and specifically disclaim all warranties, including without limitation warranties of fitness for a particular purpose. No warranty may be created or extended by sales or promotional materials. The advice and strategies contained herein may not be suitable for every situation. This work is sold with the understanding that the publisher is not engaged in rendering legal, accounting, or other professional services. If professional assistance is required, the services of a competent professional person should be sought. Neither the publisher nor the author shall be liable for damages arising herefrom. The fact that an organization or Website is referred to in this work as a citation and/or a potential source of further information does not mean that the author or the publisher endorses the information the organization or Website may provide or recommendations it may make. Further, readers should be aware that Internet Websites listed in this work may have changed or disappeared between when this work was written and when it is read.
For general information on our other products and services, please contact our Customer Care Department within the U.S. at 877-762-2974, outside the U.S. at 317-572-3993, or fax 317-572-4002.
For technical support, please visit www.wiley.com/techsupport.
Wiley also publishes its books in a variety of electronic formats. Some content that appears in print may not be available in electronic books.
Library of Congress Control Number: 2006939595
ISBN: 978-0-470-09941-4
Manufactured in the United States of America
10 9 8 7 6 5 4 3 2 1
About the Author
Vanessa Williams is an author and consultant specializing in SharePoint technologies. She helps organizations, technology professionals, and end users find meaningful uses for technologies, such as SharePoint, Office 2007, Visual Studio, and the .NET Framework.
Vanessa grew up in Indianapolis, where she graduated from the Kelley School of Business at Indiana University with a Bachelor of Science degree in Business Management and Computer Information Systems. She still lives in Indy, about three miles south of downtown in the wonderful Garfield Park South neighborhood.
In her spare time, Vanessa likes to read books about sociology, religion, spirituality, and current affairs. She enjoys hiking, traveling, and spending time with her family, including her two dogs Rosie and Buffy. She also enjoys staying current on enterprise technologies and consumer electronics.
Vanessa loves to talk about SharePoint. You can contact her via her Web site at www.sharepointgrrl.com.
Author’s Acknowledgments
In the time that’s passed since I wrote SharePoint 2003 For Dummies (Wiley), I now have two dogs and another cat. I couldn’t have finished this book if I didn’t have Buffy (Dog # 1) to lick my toes and Rosie (Dog # 2) to play tug-of-war with. The cat lies on my desk while I’m trying to work. I could do without the cat.
The number of people (and animals) it takes to produce a book is mind-numbing. I came in contact with a brave few this time around. I know them mostly by their assigned color and the initials they used to sign their editorial comments. Many thanks to pgl (pink), Jen (green), and kc (red). I’ll never forget our time together in SharePoint purgatory.
I must also thank all the poor souls who’ve had to endure my SharePoint-babble while writing this book — over breakfast with Mel, over far too many coffees with Denis, over e-mail with Katie, and over dinner with Mel. I promise to stop talking about SharePoint eventually.
Finally, I need to thank all the readers. You bought the first SharePoint book and sent wonderful feedback. You took me with you to your server rooms, board rooms, and rest rooms. I hope to have that privilege again.
Publisher’s Acknowledgments
We’re proud of this book; please send us your comments through our online registration form located at www.dummies.com/register.
Some of the people who helped bring this book to market include the following:
Acquisitions, Editorial, and Media Development
Project Editor: Paul Levesque
Acquisitions Editor: Katie Feltman
Copy Editor: Jennifer Riggs
Technical Editor: Ken Cox
Editorial Manager: Leah Cameron
Media Development Manager: Laura VanWinkle
Editorial Assistant: Amanda Foxworth
Sr. Editorial Assistant: Cherie Case
Cartoons: Rich Tennant (www.the5thwave.com)
Composition Services
Project Coordinator: Adrienne Martinez
Layout and Graphics: Stephanie D. Jumper, Barbara Moore, Laura Pence, Heather Ryan, Erin Zeltner
Proofreader: John Greenough
Indexer: Aptara
Anniversary Logo Design: Richard Pacifico
Publishing and Editorial for Technology Dummies
Richard Swadley, Vice President and Executive Group Publisher
Andy Cummings, Vice President and Publisher
Mary Bednarek, Executive Acquisitions Director
Mary C. Corder, Editorial Director
Publishing for Consumer Dummies
Diane Graves Steele, Vice President and Publisher
Joyce Pepple, Acquisitions Director
Composition Services
Gerry Fahey, Vice President of Production Services
Debbie Stailey, Director of Composition Services
Contents
Title
Introduction
Coming Out of the Shadows
Who Should Read This Book
How to Use This Book
Foolish Assumptions
How This Book Is Organized
Icons Used in This Book
Where to Go from Here
Part I : Setting Up SharePoint
Chapter 1: Getting to Know SharePoint
Understanding SharePoint Technology
SharePoint’s Role in Your Company
Getting Started with SharePoint
Preparing for SharePoint
Chapter 2: Installing SharePoint
Installing SharePoint
Creating an Evaluation Server
Accessing SharePoint’s Administrative Pages
Installing SharePoint for the Real World
Performing Administrative Tasks
Chapter 3: Creating the Site Hierarchy
Understanding Web Applications
Understanding Site Collections
Configuring Web Applications and Site Collections
Part II : Exploring SharePoint’s Building Blocks
Chapter 4: Introducing Sites and Site Content
Exploring SharePoint Sites
Creating Structure for Site Content
Using Web Pages
Using Lists and Libraries
Chapter 5: Navigating SharePoint
Exploring End User Navigational Elements
Modifying Navigation
Exploring Administrative Navigational Elements
Chapter 6: Granting Access to SharePoint
Delegating Authentication
SharePoint’s Authorization Model
Viewing Permission Assignments
Managing SharePoint Groups
Breaking Inheritance
Chapter 7: Managing Data with SharePoint
Defining Columns
Get a New View
Enabling Content Types
Chapter 8: Managing Business Processes with SharePoint
Using Workflows
Filling Out InfoPath Forms
Part III : Improving Information Worker Collaboration and Productivity
Chapter 9: Using SharePoint for Collaboration
Using SharePoint with Office 2007
The Many Faces of SharePoint
Integrating with Other Servers
Chapter 10: Communicating with SharePoint
Integrating with Outlook
Sending E-Mail to SharePoint
Chapter 11: Using Portal Sites
Exploring Collaboration Portals
Reaching Out with Publishing Portals
Chapter 12: Configuring Profiles and My Sites
Planning for My Site
Exploring My Site
Managing User Profiles
Chapter 13: Personalizing Sites
Knowing Your Audience
Targeting Content
Getting Personal
Chapter 14: Searching the Enterprise
SharePoint’s Search Offering
Searching SharePoint
Configuring Search
Part IV : Enterprise Applications for SharePoint
Chapter 15: Exploring Document and Records Management
Managing Documents
Managing Records
Chapter 16: Publishing Web Content
Authoring Web Content
Customizing Content Publishing
Chapter 17: Providing Access to Business Intelligence
Using Excel Services
Exploring Reports Center
Connecting to Data
Part V : Administering SharePoint
Chapter 18: Administering and Monitoring SharePoint
Exploring Central Administration
Configuring Shared Services
Monitoring Site Usage
Managing Site Collections
Chapter 19: Backing Up the Server
Recovering from End User Mishaps
Migrating Sites and Site Collections
Recovering from Disaster
Creating Your Backup Plan
Part VI : The Part of Tens
Chapter 20: Ten SharePoint Resources Worth Checking Out
Technically Speaking
Exploring MSDN
Digging Deeper with Software Development Kits
Getting Acquainted with Office Online
Downloading SharePoint Resources
Blogging SharePoint
Discovering SharePoint
Getting Support
Finding SharePoint Hosting
Getting a Head Start with Application Templates
Bonus Resource
Chapter 21: Ten Positive Outcomes from Implementing SharePoint
Increase User Productivity
Reduce Calls to the Help Desk
Increase Opportunities for Knowledge Transfer
Increase Employee Loyalty and Satisfaction
Minimize Communication Barriers between Departments
Improve Relationships with Partners and Customers
Mitigate the Risks of Software Development
Maximize ROI
Reduce Merger/Acquisition Costs
Build Bridges between Information Technology (IT) and Business Users
Introduction
SharePoint is nothing new. Heck, it’s been around since 2001. As fast as technology changes, SharePoint should be ancient history by now. Quite to the contrary, SharePoint has finally found its legs after all these years.
ShareWhat, you say? SharePoint is the server-side connective tissue that binds the slippery client-side outputs of office workers into a manageable, searchable, and accessible information environment. Gone are the days when workers just organized their files in electronic folders and had to call the help desk every time something was deleted accidentally. SharePoint provides a self-service environment where office workers can take control of information — how it’s organized, who gets access to it, and how it’s displayed.
Don’t feel bad if you don’t know SharePoint from Shinola. You aren’t alone. Many obstacles are along the path to a successful SharePoint implementation. This book uses plain English to get you started on your SharePoint journey so that nothing trips you up along the way.
Coming Out of the Shadows
Since SharePoint was first released in 2001, Microsoft has made steady progress on the product’s features. The first few releases of SharePoint consisted primarily of the ability to dynamically generate team Web sites. These sites hosted document libraries, tasks lists, and calendars to enable a small team of users to manage documents and collaborate on a project. The initial product was called SharePoint Team Services but was changed in 2003 to Windows SharePoint Services (WSS).
The building blocks — lists, libraries, and user-customizable Web pages — used by WSS to create team sites turned out to be very versatile and could be used for more than just team collaboration. Many companies started creating SharePoint sites to solve all kinds of business problems, such as managing help desk tickets and automating expense check requests.
Microsoft created a more expensive add-on product, SharePoint Portal Server, that added the ability to create portals and search across team sites. The portal allowed companies to provide centralized access to all their team sites.
Despite SharePoint’s usefulness, the product’s adoption was nichey and sporadic. Also, there was (and still is) significant confusion in the marketplace about what SharePoint is and what it does. When Microsoft sat down to consider the product’s future after the 2003 release, they saw an opportunity to more tightly integrate the product with the Office clients that virtually all office workers already have on their desktops. Increased integration with Office 2007 catapulted SharePoint onto center stage.
Microsoft used a host of existing and newly created products to develop the 2007 release of SharePoint. Like pieces of a puzzle, the following product opportunities came together to create a better SharePoint:
ASP.NET 2.0: The release of ASP.NET 2.0 provided the foundational layer that was missing in previous versions of SharePoint. By using ASP.NET 2.0, Microsoft was able to focus on building a better SharePoint without spending so much time on low-level services. Some of the ASP.NET 2.0 features used or extended by SharePoint include the Web Parts framework, personalization, pluggable authentication, and master pages. WSS 3.0 is truly a testimony to what you can build with ASP.NET 2.0!
Content Management Server 2002: Like chocolate and peanut butter, many companies, including Microsoft, realized that Content Management Server could be used to support SharePoint. Instead of having a separate server, Microsoft decided to roll Web content management into SharePoint.
Office 2007: Microsoft realized that companies need a compelling reason to upgrade to Office 2007. Adding more features to Word and Excel doesn’t cut it any more. In addition to completely redesigning the look and feel of most Office clients for the Office 2007 release, Microsoft added many new features that are available only via a server infrastructure. SharePoint is a major player in providing the Office 2007 server infrastructure.
Search: In 2006, Google went after the desktop, and Microsoft went after search. Microsoft introduced a family of search products that target the Web, desktop, and enterprise with the expressly stated intent of taking Google head-on. SharePoint is the key element that delivers enterprise search.
Windows Workflow Foundation (WF): The release of WF with version 3.0 of the .NET Framework brings a workflow engine to SharePoint, Office 2007, and all applications that run on Windows. Workflows make it possible to step through a process, such as submitting a document for approval. Building a separate workflow engine decouples workflow capabilities from specific server products. Instead of having only a few products with workflow, all products can have workflow. SharePoint extends WF and provides several out-of-the-box workflow implementations that businesses can use to automate business processes without writing custom code.
By taking advantage of these products along with the new goals of winning search while keeping its talons securely fastened to the business desktop, Microsoft completely re-architected SharePoint into a layer of technologies that consists of these two primary products:
Windows SharePoint Services (WSS) version 3.0 is the foundational productthat provides a set of building blocks for creating SharePoint applications. The two primary usage scenarios for WSS are still document management and collaboration. The third usage scenario is a platform for creating applications with SharePoint.
Microsoft Office SharePoint Server (MOSS) 2007 is the server-side infrastructure that turns Office 2007 clients into generators and consumers of content for SharePoint applications. MOSS 2007 is the successor to SharePoint Portal Server 2003. Although MOSS supports the creation of portals, Microsoft has expanded it to include many enterprise-level services, such as business intelligence and business process integration. MOSS 2007 is an example of an application created using WSS as a platform.
At this point, I could give you the obligatory laundry list of SharePoint’s features. Even if I did that, you still wouldn’t understand how to use SharePoint. Instead, this book focuses on using SharePoint’s out-of-the box application building blocks to get up and running solving problems relevant to your business.
Who Should Read This Book
Now that SharePoint is no longer the red-headed stepchild of Microsoft’s server family, an increasing amount of buzz surrounds it. Whether you’re brand new to SharePoint or you’re looking to get acquainted with SharePoint’s new features, this book is for you.
To help you cut through the hype, this book tells you everything you need to know to start using WSS or MOSS 2007 in your business today. If you’re unsure about which SharePoint product to implement, I give you the breakdown of where WSS features end and MOSS 2007 picks up.
You’ll get guidance for planning your project and ideas for ways you might use SharePoint in your organization. I don’t go into the details of performing upgrades in this book, although I do explain how to set up and configure a SharePoint infrastructure.
This book isn’t really intended for end-users unless you’re curious about SharePoint’s configuration options. Instead, I suggest my book Office 2007 and SharePoint Productivity For Dummies (Wiley). Also, I don’t cover customizing SharePoint in this book. I suggest you see my book SharePoint Designer 2007 For Dummies where I show you how to create custom sites and solutions for SharePoint that don’t require you to write code.
How to Use This Book
I know you don’t want to read this book cover to cover, and you don’t have to. Your role in SharePoint’s implementation makes some topics more relevant than others. If you want to zero in on a particular topic, you can use the table of contents and index to focus on that coverage. Part II focuses almost exclusively on Windows SharePoint Services, whereas Parts III and IV lean more toward MOSS 2007 coverage. I compiled a list of topics that I know many of you are interested in:
Setting up, configuring, deploying, and administering SharePoint — see Chapters 1, 2, 3, 18, and 19.
Understanding the basics of SharePoint sites, including how to create, configure, and secure them — see Chapters 4, 5, and 6.
Understanding how to add and manage content in SharePoint — see Chapters 7 and 8.
Figuring out how end users interact with SharePoint — see Chapters 9 and 10.
Setting up your portal and people directory in MOSS 2007 — see Chapters 11, 12, and 13.
Configuring and understanding SharePoint’s search features — see Chapter 14.
Diving into SharePoint’s options for document and records management — see Chapter 15.
Using SharePoint to manage and publish content to portals and Internet-facing sites and exploring your options for customizing SharePoint’s look and feel — see Chapter 16.
Getting introduced to SharePoint’s features for integrating enterprise applications into SharePoint, creating business intelligence (BI) dashboards and reports, and displaying Excel spreadsheets in SharePoint — see Chapter 17.
You’ll get the most out of this book if you work through the examples when you read the text. You may also find it helpful to have access to both a WSS server and a MOSS 2007 server so you can see the differences between the products.
I run both servers on a single physical machine using Virtual Server 2005. As long as you have a fast processor along with plenty of RAM and disk space, you should be fine using a virtual server for a testing environment.
Foolish Assumptions
While writing this book, I had to make a few assumptions about you — the reader. Don’t worry, I didn’t take you for the pocket protector type with a dozen servers in your bedroom. But I wouldn’t be surprised to find a hipster PDA and a pile of Mountain Dew cans.
In order to work the examples in this book, you need access to a working SharePoint installation with either WSS version 3 or MOSS 2007. If you don’t already have a SharePoint server, I walk you through how to install SharePoint in Chapter 2. I’m assuming you know your way around a Windows server and have basic networking skills. You certainly don’t need to be certified or know how to build a server.
I also assume that you’re working inside a Windows network that’s running Active Directory (AD). You don’t have to run AD to perform most of the examples in this book. The examples in this book haven’t been tested when accessing SharePoint from the Internet.
SharePoint is a server-based technology, so you have to know the name of your server in order to access SharePoint’s resources. Because I don’t know what the names of your servers are, I have to assume that you know the server names and URL paths to your SharePoint server. While I walk you through all the various ways you can access SharePoint (it isn’t just the browser, you know — see Chapter 6), you have to substitute your server and path names to access the resources in your SharePoint deployment.
How This Book Is Organized
This book groups related SharePoint topics together in parts. Each part covers a different aspect of implementing or using SharePoint.
Part I: Setting Up SharePoint
In this part, you get your first lessons in SharePoint-speak. I walk you through setting up SharePoint servers and configuring the high-level infrastructure that holds your business content. You probably want to read Chapter 1, but you can browse Chapters 2 and 3 if you already have a functioning SharePoint server.
Part II: Exploring SharePoint’s Building Blocks
Part II walks you through all the foundational elements used to create solutions in SharePoint. Chapters 4, 5, and 6 address issues related to creating, navigating, and securing a site infrastructure. Chapters 7 and 8 get into the meat and potatoes of solving business problems with two of SharePoint’s most useful features: data and business process management.
Part III: Improving Information Worker Collaboration and Productivity
In Part III, I start to look at some of the ways that end users interact with SharePoint in their native habitat, Windows client applications. Chapter 9 focuses on accessing SharePoint through Office 2007 clients, other Windows applications, and alternatives to using Web browsers. In Chapter 10, I explore using e-mail to send information to and receiving information from SharePoint. Chapters 11–14 deal primarily with MOSS 2007 features, including portals, user profiles, personalization, and enterprise search.
Part IV: Enterprise Applications for SharePoint
In this part, I cover some of the more advanced features of MOSS 2007. Chapter 15 explains the document management features offered by WSS and how MOSS 2007 expands on those with advanced document management and records management features. Chapter 16 explores Web content publishing, along with opportunities for customizing SharePoint’s look and feel. I explain the opportunities for data integration and creating business intelligence dashboards in Chapter 17.
Part V: Administering SharePoint
The chapters in this part follow up on the material covered in Chapters 2 and 3 by explaining SharePoint’s server farm administration features. You’ll see how to monitor your server farm and perform a backup.
Part VI: The Part of Tens
When it comes to SharePoint, a single resource is never enough. In Chapter 20, I share with you my top ten list of resources for staying up to speed on all things SharePoint. And because making the business case is vital to all successful SharePoint implementations, I offer you ten positive outcomes that you might aspire to achieve with your SharePoint implementation.
Icons Used in This Book
You’ll find a handful of icons in this book, and here’s what they mean:
Tips point out a handy shortcut or help you understand something important to SharePoint.
This icon marks something to remember, such as how you handle a particularly tricky part of SharePoint configuration.
This icon means that what follows is technical, insider stuff. You don’t have to read it if you don’t want to, but if you want to become a SharePoint pro (and who doesn’t?), take a look.
Although the Warning icon appears rarely, when you need to be wary of a problem or common pitfall, this icon lets you know.
Where to Go from Here
Alright, you’re all set and ready to jump into Chapter 1. You don’t have to start there; you can jump in anywhere you like — the book was written to allow you to do just that. But if you want to get the full story from the beginning, jump to Chapter 1 first — that’s where all the action starts. (If you already have a SharePoint server up and running, you might want to jump ahead to Chapter 4, where you can get your hands dirty with some site content.)
Part I
Setting Up SharePoint
In this part . . .
Discover SharePoint’s features and how they fit into your existing technology environment. I show you how to get up and running with your very own SharePoint server. Because installing SharePoint is only half the battle, I also get you started on the necessary next steps you’ll need to carry out before you can hang that Open sign on your SharePoint deployment.
Chapter 1
Getting to Know SharePoint
In This Chapter
Identifying the technologies that enable SharePoint
Figuring out licensing requirements
Discovering SharePoint’s role in your organization
Deciding which projects to start with
Getting ready to implement SharePoint
If you believe everything you read on the Internet (and who doesn’t?), you know that SharePoint is either an over-hyped Microsoft product with no real business value or it’s the next Messiah in information and knowledge management. So, which is it? Only you can answer that question.
SharePoint’s usefulness in your organization is determined by whether SharePoint has a role in your existing information systems environment. To determine SharePoint’s role, you really have to understand what SharePoint is and what it does. However, simply having this knowledge doesn’t guarantee you a successful SharePoint implementation. However, it does give you a strong foundation, which is what this chapter is all about.
Understanding SharePoint Technology
SharePoint is a family of technologies from Microsoft that provides a server infrastructure to support the needs of information workers and their employers. These needs include collaboration, knowing who’s online, document storage, and the ability to inform and be informed. The companies that hire information workers need to audit, monitor, organize, retain, and protect information.
SharePoint makes it possible for companies to engage all their information workers through the tools people are using already — Office clients (such as Word and Excel), Internet browsers (such as Internet Explorer), and e-mail clients (such as Outlook). Obviously, SharePoint works best with Office 2007. Whether you’re using Office 2007 or OpenOffice, SharePoint gives employers a means to connect with workers where they work — at their desktops.
By reaching workers where they work, companies can use SharePoint as a key component for implementing new strategic initiatives and internal communications plans. Beyond sending blast e-mails and convening one-time town hall meetings, companies can use SharePoint to integrate information about campaigns, achievement of performance objectives, and company news into workers’ daily routines. Sound like information overload? It need not be. SharePoint makes it easy to target content so that people see only the information that’s relevant to achieving their objectives.
With SharePoint, companies can create a managed information environment that isn’t centrally managed. Yes, it’s secure, protected, and audited, but workers make decisions about how information is organized. If workers change their minds about the organizing structure, it can be changed easily. By evaluating the ways that employees set up their work environments in SharePoint — where they store documents, the properties they affix to documents, and with whom they’re collaborating — the information environment created in SharePoint can provide companies with valuable feedback. When’s the last time your information environment told you how many Word documents pertained to a particular customer account or product? You can get that kind of information from SharePoint.
SharePoint also provides workers with the ability to connect with each other. Instead of sending files back and forth via e-mail, workers can set up information environments that make it easy to collaborate on documents or share a calendar.
SharePoint uses a Web site infrastructure to deliver the bulk of its features. Users can use a Web browser or familiar Office clients, such as Word and Excel, to access SharePoint’s features. Office clients enable information workers to use familiar tools in new ways, which reduces training and support costs and increases solution development opportunities. SharePoint offers organizations a much faster return on investment because SharePoint fits neatly into most companies’ existing technology infrastructures.
SharePoint isn’t a new technology. The ability to provision team sites for use with Office clients was first introduced in May 2001 (as shown in Figure 1-1) with a product called SharePoint Team Services. SharePoint Portal Server 2001, a product for connecting team sites, was released in June 2001. With each subsequent release, more and more features were added. Windows SharePoint Services (WSS) version 3, which was released in November 2006, represents a major re-architecting of the product.
Starting with the 2003 release, WSS became a component of the Windows Server operating system. The portal product, SharePoint Portal Server 2003, released alongside Office 2003. The latest release, Microsoft Office SharePoint Server (MOSS) 2007, is now officially part of the Microsoft Office suite of products.
Figure 1-1: SharePoint product release timeline.
In the days of client/server applications, an application commonly consisted of a relatively short stack of technologies. A Windows application might be written in a programming language, such as Visual Basic, that accesses a database on a database server. As long as you had network connectivity and your database was up and running, probability was high that you could use the application. More importantly, installing, supporting, maintaining, and troubleshooting the application was relatively easy.
In the same way that today’s information workers don’t work in isolation, neither can SharePoint. To support the needs of workers and their employers, SharePoint requires a relatively high stack of technologies. Understanding SharePoint’s technologies in broad terms is important because this knowledge helps you do the following:
Identify opportunities for reuse and customization: When you gain an understanding of the technologies SharePoint uses, you can leverage some of your existing infrastructure. You don’t have to start at square one. Also, you can extend SharePoint to find new ways to use the infrastructure.
Troubleshoot SharePoint: You’ll encounter many points of failure in SharePoint — and discover that many aren’t actually part of the SharePoint software proper. By understanding how SharePoint works and which technologies SharePoint uses, you can develop a systematic approach to troubleshooting.
Understand the skills necessary to implement and support SharePoint: SharePoint requires a lot of skills, and it’s not likely that you have all of them. I know I sure don’t. You have to make arrangements to acquire the skills you don’t have in-house.
The SharePoint family of technologies consists of several products. In this book, I focus on the two primary SharePoint products: Windows SharePoint Services (WSS) and Microsoft Office SharePoint Server 2007 (MOSS). Each of these products has a different role in the stack of SharePoint technologies.
See the section, “Licensing SharePoint,” later in this chapter, for a complete rundown of all the products available in the SharePoint family.
Laying the foundation
The core product in the family of SharePoint technologies is Windows SharePoint Services (WSS). Because WSS is the foundational product, no other product in the SharePoint family is possible without it.
WSS is a full-blown ASP.NET 2.0 Web application, which means it runs hosted inside ASP.NET. When you install WSS, you have to install ASP.NET and everything it requires to run, including the following:
Internet Information Services (IIS) version 6 or 7: This is Microsoft’s Web server, which is used to host SharePoint. Most typical SharePoint usage scenarios can configure IIS from within SharePoint. You don’t have to manage IIS directly very often.
.NET Framework version 2.0 and 3.0: This is a set of software that installs ASP.NET and Windows Workflow Foundation (WF). After you enable ASP.NET 2.0 on the server, you don’t have to do anything else to configure .NET.
SQL Server 2000 or later: This is Microsoft’s database management system. SharePoint can create all the databases it needs, or you can create them yourself. You’re responsible for managing backups of your data.
Windows Server 2003 or later: This is Microsoft’s server operating system. Monitor the servers that host SharePoint just like you would any server.
I walk you through installing these technologies on your server in Chapter 2. Figure 1-2 shows the stack of technologies required to run WSS. Note that these are logical servers. Your implementation may include several physical servers.
Figure 1-2: SharePoint requires many enabling tech-nologies.
ASP.NET is the Microsoft platform for building Web applications. A Web application is more sophisticated than a Web site, which may only display information. Web applications can provide services, such as electronic commerce. Much of the ability to customize and extend SharePoint comes from ASP.NET 2.0.
You can think of the technologies listed in Figure 1-2 as SharePoint’s enabling technologies. SharePoint requires these technologies in order to function properly. SharePoint integrates with many other technologies to provide extra functionality, such as Microsoft Exchange Server. See Chapter 9 for more information on such technologies.
WSS provides the core set of services consumed by all products in the SharePoint family, especially MOSS 2007. These services include the following:
Data storage and content management: WSS provides lists and libraries as structures for storing data. Lists are primarily used to store tabular data, whereas libraries store files. WSS provides a robust set of services for managing the data and files stored in lists and libraries, services that allow you to do the following:
• Associate metadata with list items and files (see Chapter 7).
• Create versions of list items and files (see Chapter 15).
• Check out files for editing (see Chapter 15).
• Index sites, lists, and libraries for searching purposes (see Chapter 14).
What’s in a name?
When someone says SharePoint, what does he mean? Is he referring to a specific SharePoint product or the whole kit and caboodle? The only way to know for sure is to ask him. Although, don’t be surprised if you don’t get a straight answer. With SharePoint, you inevitably encounter an abundance of hype, misunderstanding, and uncertainty. Generally speaking, when someone says SharePoint, I find he usually means whichever SharePoint product is most relevant given the context of the discussion, or he’s just referring to the SharePoint technologies. Many people genuinely don’t know.
Although I hate to add to the confusion, I find that constantly referring to a specific SharePoint product, such as WSS or MOSS 2007, is equally confusing. Because most people don’t know the difference between the two products, I usually just use the term SharePoint. In most cases, WSS can be used in many of the same ways as MOSS, so referring to them generically usually is technically correct. For example, both WSS and MOSS have document management features. (The MOSS features just expand on those found in WSS.) Similarly, MOSS has some very specific built-in features for business intelligence. However, that doesn’t mean that you couldn’t use WSS for business intelligence.
In this book, I try to be specific about which product I’m referring to, especially when I’m talking about MOSS 2007. I often use the generic term SharePoint any time I’m referring to WSS or any feature that’s available in both products.
• Manage content approval (see Chapter 15).
• Use list items and libraries in a business process (See Chapter 8)
WSS includes many specialized kinds of lists and libraries that you can use to perform certain tasks. See Chapter 4 for a complete run-down of the lists and libraries you encounter in SharePoint.
Web platform and site model: All SharePoint’s features are delivered via a hierarchy of Web sites. It takes only a few mouse clicks to generate sites with SharePoint’s site provisioning model (see Chapter 4). SharePoint generates a full-featured Web site based on an XML configuration file. (WSS includes many of these configuration files that allow you to create a variety of SharePoint sites to suit the needs of your business. You can also customize the files or create your own.)
Because SharePoint is an ASP.NET Web application, SharePoint is an excellent platform for delivering Web applications that include a Web part framework, navigation, and dynamic form and page generation. SharePoint gives you a viable alternative to building ASP.NET Web applications from scratch.
Security: SharePoint provides a security-trimmed user interface so that users see only the options they have permissions for. SharePoint uses groups and roles for granting access to secure content, and virtually everything in SharePoint is securable. The most common authentication scenario for SharePoint is Active Directory, although SharePoint supports custom authentication schemes (such as forms-based authentication) as well. See Chapter 6 for more details on SharePoint’s security features.
Management: SharePoint provides a multi-tiered administration model that makes it possible to isolate technical administrators from sensitive content. Administrators can’t see the files and other content that information workers save in SharePoint sites. Additional administration features include auditing, monitoring, and backing up and restoring tools. SharePoint provides specialized administration Web sites. All administrative features are also accessible from the command line and via code. Chapter 18 walks you through accessing the SharePoint administrative features.
Services: A number of services are provided by SharePoint that support SharePoint’s other core services. These include notification services, such as RSS feeds, alerts, and inbound e-mail (see Chapter 10). WSS indexes all list, library, and site content so these items can be searched (see Chapter 14). SharePoint also provides migration tools to assist with deploying SharePoint.
Application programming interfaces (APIs): SharePoint has a power-ful object model and Web services. Everything you can do from the SharePoint user interface uses SharePoint APIs; thus, you can write code to access all SharePoint’s features. SharePoint makes available numerous before-and-after events that make it possible to customize SharePoint’s default behavior.
Kicking it up a notch
Given that WSS is an application platform, it makes sense that Microsoft has released several products that are built upon that application platform. MOSS 2007 is one such product; it’s essentially a WSS application.
As a WSS application, MOSS consumes WSS resources and extends WSS to provide completely new features. Similar to how WSS consists of a set of services, MOSS adds the following services:
Core services are the foundational features that enable MOSS 2007 applications. Core services of MOSS 2007 include personalization, search, business data catalog, and Excel Services. MOSS 2007’s core services are shared services because they’re shared across an entire SharePoint deployment.
Application Services are the building blocks for creating applications in MOSS 2007. Examples include dashboards, workflows, and user profiles. These services are mixed and matched to provide a myriad of MOSS 2007 applications.
MOSS combines the services of WSS, along with its own core services and application services to create MOSS 2007 applications (see Figure 1-3). MOSS 2007 includes the following SharePoint applications right out of the box:
Figure 1-3: MOSS 2007 requires WSS.
Portals are an essential user interface feature of SharePoint and are used to aggregate content, highlight featured content, and provide access to other SharePoint resources (see Chapter 11).
Enterprise content management consists of document and records management (see Chapter 15) as well as Web content management (see Chapter 16). WSS also provides document management, but MOSS adds to those features with information management policies and document information panels. I like to think of Web content management as MOSS’s publishing feature. Web content management makes it possible to publish content to a site that’s intended to be read by many people.
People and personalization encompasses all the features related to managing user profiles, targeting content to audiences, and personalizing portal content. See Chapters 12 and 13.
Enterprise search provides the ability to index all content within SharePoint and content outside SharePoint. Search is configurable so that you can manage the relevancy of results delivered to users. See Chapter 14.
Business process integration provides the ability to integrate data from outside sources with SharePoint (see Chapter 17). MOSS can render InfoPath forms in the browser to automate business forms (see Chapter 8).
Business intelligence provides support for reports, dashboards, and Excel Services (see Chapter 17). Excel Services creates server-side versions of Excel spreadsheets and renders them in a Web page.
Chances are your company doesn’t rely on just one of these applications. In reality, you combine features from each application to meet your business’s needs. For example, your SharePoint implementation might be 75 percent document management and 25 percent business intelligence. Conversely, you might build your own SharePoint application by using the building blocks of WSS. If Microsoft’s Office developers can do it, so can you!
Licensing SharePoint
Figuring out which features go with which product is challenging. In this section, I explain the official products in the SharePoint family and what it takes to license them. Pricing varies depending on the kind of licensing agreement you have with Microsoft.
All SharePoint deployments require Windows Server 2003. WSS version 3 is part of Windows Server 2003, so you don’t have to buy separate licenses for WSS. You can download WSS from the Microsoft Web site.
MOSS 2007 products are available for purchase only through volume licensing agreements; you can’t buy them via retail channels. Microsoft offers several types of volume licensing agreements. The pricing associated with each agreement varies depending on the number of desktops in your organization, the benefits you receive, and whether you pay up-front or a certain amount each year. See the Microsoft Products Licensing Advisor at www.microsoft.com/licensing/mpla for assistance with choosing a licensing agreement.
Properly licensing MOSS 2007 requires a combination of server licenses and Client Access Licenses (CALs). A server license allows you to run the software, such as MOSS 2007, on your server. Clients need a CAL to access the server’s features. Two types of CALs are used for MOSS 2007:
Base CAL allows clients to access the portal, personalization, search, and enterprise content management features of MOSS 2007.
Enterprise CAL allows clients to access the business intelligence and business process integration features of MOSS 2007 (such as the Report Center, Business Data Catalog, Excel Services, and InfoPath Forms Services).
If you want users to access the features provided by the Enterprise CAL, you must also purchase a Base CAL. You need to provide an Enterprise CAL to only those clients who need to access the advanced services.
You have the option to buy a separate CAL for each user or device. Talk with your software acquisition professional for advice on which approach best suits your organization.
Several additional SharePoint products go beyond MOSS 2007:
MOSS 2007 for Search Standard Edition: This server license offers small- to medium-sized businesses all the features of Office SharePoint Server Search. The number of indexed documents is limited to 500,000.
MOSS 2007 for Search Enterprise Edition: This server has no limit to the number of documents that can be indexed with this edition.
MOSS 2007 for Internet Sites: This server license entitles you to use MOSS 2007 for Internet-facing Web sites that are accessed by non-employees. No separate CALs are required.
In addition to Windows Server 2003, you may need to implement the following:
Microsoft SQL Server: All SharePoint content is stored in a back-end database. WSS installs with an internal database; however, you likely want to use SQL Server 2000 with service pack 4 or higher or SQL Server 2005 with service pack 1 or higher.
Microsoft Internet Security and Acceleration (ISA) Server: To ensure that remote users are accessing SharePoint in the most secure fashion, implement ISA Server or a similar product. ISA Server has automatic configuration tools for protecting SharePoint.
Microsoft ForeFront Security for SharePoint: ForeFront protects your SharePoint server from malware, viruses, and enables compliance with content policies, such as prohibiting the use of profanity in documents saved to document libraries. If you choose not to use ForeFront, you need some kind of anti-virus solution.
Microsoft Exchange Server: Microsoft’s premiere e-mail and collaboration platform integrates with SharePoint search. Although Exchange and SharePoint play nicely together, you can use any e-mail server to send e-mail to SharePoint.
Office Live Communications Server: Enables presence information that lets users know who’s online and instant messaging in SharePoint with Communications Server.
Office 2007 Groove Server: Access SharePoint resources during real-time collaboration sessions with Groove Server.
Obviously, Microsoft wants you to run out and upgrade all your desktops to Office 2007. And while you’re at it, you might as well install Vista, too. The truth of the matter is that, although your users will certainly have the best experience with Office 2007, you can work just fine with Office 2003. You can use previous versions of Office and even non-Office applications with SharePoint. See Chapter 9.
To customize SharePoint, you need either SharePoint Designer 2007 or Visual Studio 2005.
SharePoint’s Role in Your Company
Although understanding the technologies that enable SharePoint and SharePoint’s features is important, I believe that understanding how SharePoint fits into your existing information systems environment is even more valuable than understanding all the SharePoint features. Just because SharePoint can be used for a certain purpose, doesn’t mean that your organization will find it useful. I believe that understanding SharePoint’s role in your organization is key to making the business case for implementing SharePoint.
An information systems environment is the mix of software, hardware, and manual processes within a company. In some cases, deciding to use SharePoint is easy because SharePoint solves an obvious problem. For example, you can use SharePoint to automate business processes by using electronic forms. However, I find that most companies intuitively think they need SharePoint but can’t quite figure out the arguments for why.
All the information found in an organization’s information systems environment are the company’s information assets. Typically, we think of assets as tangible items of value, such as equipment and land. Information (such as how well the company is performing and who the company’s top five competitors are) may be intangible, but I think most people agree they’re of value to the business.
Most organizations have many disparate repositories for storing their information assets. Some repositories are easier to manage than others. Listed here are some information assets and where they’re commonly stored:
General business transactions are stored in custom and off-the-shelf, line-of-business applications.
Department-specific transactions are stored in departmental software applications and tools.
Documents, spreadsheets, and images are stored in a user’s My Documents folder and network shares.
Directions, instructions, and reference materials are stored in three-ring binders.
Cheat sheets and calendars are stored on cork boards.
Archived files are stored on CDs and storage boxes.
Protected documents are stored as PDF files.
Links to resources on the Web are stored in a user’s Favorites folder.
Posts from syndicated blogs and Web sites are stored in feed readers.
Musings on life, love, and what’s for lunch are stored in blogs.
Ideas and actionable items from meetings and brainstorming sessions are stored on notepads, sticky notes, and easel paper.
Sanitized product and company information is stored on Web sites.
Meeting invitations, announcements, and discussion threads are stored in e-mail Inboxes.
Phone numbers and job titles are stored in a directory, such as Exchange Server.
Know-how is stored in the heads of employees.
In most organizations, Information Technology (IT) departments are charged with creating an information systems environment for managing all these information assets. Databases are a common repository used to manage information assets. Databases place a structure on information assets that makes them easier to manage. Even physical assets, such as vehicles and buildings, are often tracked in databases.
Not all information assets lend themselves well to the kind of structure required by most databases. These information assets are often saved to folders on file servers. Because there’s no way to enforce an organization scheme in file folders, the folders quickly erode into a dumping ground.
Whether you need to manage access to a set of disparate structured assets or gain more control over less structured assets, SharePoint creates an environment that equalizes the different properties of information assets.
Accessing structured assets with SharePoint
Structured assets are often found in the formal systems of organizations that use databases to store their data. Because they use databases, it’s relatively easy to query and aggregate data from these systems. Line-of-business applications are good examples of repositories for structured assets. Systems for managing structured assets are usually supported by IT staff and have the following characteristics:
Formal: They’re the “official” systems of the company, and everyone in the company can rattle off their names and what they’re used for.
Mature: Because it takes a long time to implement structured systems, they tend to be predictable and stable. Despite what businesses say about being innovative and thinking outside the box, an information systems environment isn’t the place most organizations want to find surprises.
Scope: A large number of people often use structured systems. These are often the systems for which permission is requested as a matter of course when someone is hired.
The problem with structured assets isn’t managing the assets; the problem is managing access to the assets. What makes structured assets so easy to manage also makes them difficult to access. It’s challenging to teach executives how to log into a system and run reports or to show a large group of end users how to navigate menus and access a single process, such as entering a purchase order. SharePoint makes it possible to more finely control the access to structured assets in the following ways:
Customize access to structured applications: Instead of granting large numbers of users access to enterprise applications when they only need limited access, you can provide alternative access in SharePoint. For example, if someone needs to look up lists of data, query the customer database, or look up a part number, you can make that data available via SharePoint.
Supplement structured applications: You can supplement structured applications by automating business processes. Oftentimes, an enterprise application encompasses only part of a business process, not the whole thing. For example, most software has purchase order or expense report processing. Oftentimes, the request is manual or in e-mail and must be signed by a manager. You can initiate the process in SharePoint and then queue the transactions in your primary system.
Link structured data to unstructured data: Commonly, Word documents and spreadsheets support a business transaction. You can link documents stored in a document repository to transactions in your structured systems.
Limit access: Create a data catalog in SharePoint to access data for the purposes of querying and report building.
Consolidate assets: Many times, you need to present an aggregated view of structured data that comes from multiple sources. SharePoint makes it possible to provide a consolidated view from multiple back-end sources.
Managing unstructured assets with SharePoint
Unlike structured assets, less structured assets (such as Word documents) usually aren’t stored in databases. They’re often stored on file servers and removable media, such as CDs. Other less structured assets (such as e-mails and blog posts) may be stored in databases, but the information conveyed by the e-mail or blog post isn’t managed. Instead, the mail server acts like a file server, and the e-mail acts like a file.
The problem with files is that they’re hard to manage and control. End users can easily store them on thumb drives and send them as e-mail attachments. Despite IT’s attempts to control files with policies and backups, files are slippery.
Contrary to what IT staff want to believe, less structured information assets are stored in more places than just file servers, such as the following:
My Documents folder
Favorites folder
RSS feed readers
Blog sites
Web sites
Inboxes and other mail folders
Filing cabinets
Off-site storages
Table 1-1 lists some of the less structured assets you can expect to find.
Although repositories for storing structured assets are formal, mature, and of a wide scope, the environment for less structured assets is often more difficult to control. Although businesses don’t want their employees’ sales presentations to be boring, stuffy, and staid, they do want the environment in which these documents are created to be manageable. By creating a manageable environment for less structured information, SharePoint confers the following benefits to less structured assets:
Structure: SharePoint stores everything in a database. As a result, users can create properties that describe their documents. These properties can be used to better organize documents. Some of the information found in documents is better suited for storage in a database table. Rather than storing the document in SharePoint, users can store the document’s data in the database.
Standardization: SharePoint allows you to define the kinds of documents and other information (or content types) stored in the database. When someone attempts to add documents, SharePoint prompts the user for the set of properties associated with that content type. Using content types ensures that the same properties are captured.
Share: SharePoint makes the information available in documents accessible to larger numbers of people. Oftentimes, the only way to distribute documents now is with an e-mail attachment.
Archive: SharePoint allows you to define policies that determine for how long a document must be archived.
Backup and restore: By keeping less structured assets in a common repository, SharePoint makes it possible to back up and restore these assets.
Secure: Creating a secure environment means more than just restricting unauthorized access. SharePoint makes it possible to extend those restrictions beyond the managed information environment by preventing unauthorized distribution of assets.
Audit: Part and parcel of securing assets is the ability to audit their access. SharePoint makes it possible to monitor the information environment for less structured assets in ways previously not possible.
Summarize, analyze, and mine data: By applying properties to less structured assets, SharePoint makes it possible to query and search these assets like structured assets.
Legitimize: By bringing in social tools (such as blogging, RSS, Web, and search) inside the information systems environment, SharePoint acknowledges the valuable role these tools play. Organizations don’t operate in a vacuum. SharePoint extends access to the external environment in a controlled and measured way that encourages productive and purposeful uses of these resources.
SharePoint as the hub
With the significant investment companies have made already in people and technology, how can SharePoint possibly have a role in this already crowded information systems environment? With IT staff overburdened already, it’s little wonder at the lack of enthusiasm in implementing yet another system.
Despite all the technological advances, the big budgets, and the far-reaching plans, many end users and members of the business community find themselves increasingly alienated from their company’s information environments. Most end users can tell you that something is clearly missing. SharePoint aims to be the missing link in a company’s information systems environment by acting as the hub, as shown in Figure 1-4. As the hub, SharePoint is an integral player in providing users access to information assets.
Whereas your current information environment uses file shares, e-mail Inboxes, and databases as storage repositories for information assets, SharePoint provides its own set of repositories for creating manageable information environments. These organizing containers are organized in a hierarchy. Organizing them in a hierarchy creates parent-child relationships between containers, which makes it possible for the settings in a higher-level container to apply to a lower-level container — a process called inheritance. Using a hierarchy also makes it possible for administrative tasks to be delegated to administrators of lower-level containers. For example, a higher-level administrator might choose to enable a set of features so lower-level administrators can disable those features if they want to.
Whether containers are administered by IT staff, power users, or information workers depends on how the company chooses to make administrative assignments. The containers that are often managed by IT include these:
Server farm: Like most server software, SharePoint often requires multiple servers — dubbed a server farm — to work productively. Although it’s possible to have multiple server farms, most companies only ever need one. IT is responsible for deploying the server farm and managing its health. I walk you through setting up SharePoint in a single-server or server farm configuration in Chapter 2.
Some editions of SharePoint (those based on MOSS 2007) have an additional component — the Shared Services Provider (SSP). The SSP is responsible for providing services that are required across the entire server farm, regardless of how many servers you have. Each server farm usually only has one SSP. See Chapter 2 for details on setting up the SSP.
SharePoint provides special administrative interfaces — Central Administration and Shared Services Administration — for managing the server farm and SSP, respectively.
Web applications: Web applications are most often used to create an information environment for a single company. If the company is especially large, IT may choose to create separate Web applications to separate the company’s divisions. For example, if the company has an operation in the United States and one in the United Kingdom, IT would likely create separate Web applications for each. Also, if the company wants to provide an information environment that will be accessed by the public, such as vendors or customers, they may choose to separate that content into its own Web application. I’m sure you guessed that you can apply some rules for when you should create separate Web applications. I discuss rules for creating Web applications and how to create Web applications in Chapter 3.
Site collections: Each Web application contains at least one site collection. A site collection can be used to create an information environment for a single company, or there may be separate site collections for each division within the company. Similar to Web applications, there are rules for how site collections are created (see Chapter 3). A site collection contains at least one top-level SharePoint site, which is used to store and display information. Site collections are usually created by IT staff, but their content is often administered by a member of the business staff.
Figure 1-4: SharePoint is your information environ-ment’s hub.
The containers that are often created and managed by business users include the following:
Sites: SharePoint sites are usually created for a specific purpose, such as coordinating a project team or providing an information environment for a department. It’s common for companies to create sites for each of the departments within their organization. SharePoint provides a special kind of site, called portals, which is intended for providing information to larger groups of people. For example, the top-level site in a site collection is often a portal. Sites can contain additional sites as well as lists and libraries. Each site has its own administrative interfaces for managing permissions, navigation, and appearance. I discuss sites in Chapter 4.
SharePoint sites can inherit permissions, navigation, and appearance settings from their parent site.
Lists: SharePoint provides a number of predefined lists that can be used to store data, such as tasks, events, and announcements. You can create your own custom lists to store data that’s specific to your business. By default, list data appears in a tabular format, but SharePoint provides additional view formats. You can easily customize how much data appears on the screen and whether the data is sorted, filtered, and grouped. You can even create master/detail displays of data. SharePoint automatically generates Web pages to add, edit, and display the data you store in lists.
Libraries: SharePoint sites can contain any number of libraries for storing files. The most common SharePoint library is the document library, although you can also use libraries to store electronic forms, pictures, and PowerPoint slides. You can create new file properties for the files you save in SharePoint libraries. SharePoint automatically prompts users to enter values for the properties when they upload files. Users can open files from and save files to SharePoint libraries from their usual desktop applications, such as Word and Excel.
From SharePoint’s perspective, all the information assets that you store and manage in SharePoint are content. All the Word documents, Excel spreadsheets, and PowerPoint slideshows that users upload to libraries are content. All the tasks, announcements, and other data that users enter into lists are content. Even the Web pages that are displayed in a portal are content. The sites, lists, and libraries that you create to display, organize, and store content are content structures.
SharePoint’s content structures are more than just passive storage containers. To have a managed information environment, SharePoint provides a framework of features that includes workflows, content types, versioning, content approval, and permissions management. I introduce lists and libraries in Chapter 4. You can read more about SharePoint’s content management features in later chapters.
Selling SharePoint
When you make new discoveries about SharePoint’s capabilities, don’t be surprised if everyone else doesn’t fall in line. You have to see SharePoint to believe its technologies. That’s why I think it’s so important to ask for a hunting license. Only by taking on a few projects and showing SharePoint’s value can you start to get people on board.
