Sharepoint 2007 is in Beta 2 now and is
projected to be released at the beginning of the year but now is the time to
start looking at the new features that SharePoint 2007 and WSS V3.0 will
contain.
Below are some of the highlights of the new features that SharePoint 2007
and WSS V3.0 will contain.
Site columns provide a central, reusable model for column definition.
When you create a site column, each list that uses this column has the same
definition, and you do not have to do the tedious work of reproducing the
column in each list. Additionally, site columns provide you with the
simplicity of a single maintenance point. For instance, you can create a
status site column, which may contain multiple choices of an enterprise's
specific statuses, and implement the column in dozens of project master
lists across the site collection. If you add a new status, you can modify
the site column instead of having to modify each list that contains a status
column.
Content types are a core concept used throughout the functionality and
services offered in Microsoft Windows SharePoint Services (version 3) and
are designed to help users organize their SharePoint content in a more
meaningful way. A content type is a reusable collection of settings you want
to apply to a certain category of content.
Content types enable you to manage the metadata and behaviors of a document
or item type in a centralized, reusable way. For example, consider the
following two types of documents: software specifications and legal
contracts. You might want to store documents of those two types in the same
SharePoint document library. However, the metadata you would want to gather
and store about each of these document types would be quite different. In
addition, you would likely want to assign different workflows and retention
policies to the two types of documents. Content types enable you to store
multiple types of content in the same SharePoint library or list. In the
preceding example, you could define two content types, named Specification
and Contract. Each content type would include different columns for
gathering and storing item metadata and would have different workflows and
policies. Yet items of both content types could be stored in the same
SharePoint document library.
Recycle bins, or undelete functionality, is another important improvement
that has been added in Microsoft Windows SharePoint Services (version 3).
This functionality is available in both lists and document libraries.
Deleting an item from a list triggers a multilevel series of events. First,
the item is sent to a Web-level recycling bin. From here, the item can be
undeleted by any individual who has been given appropriate rights. When the
item is deleted from this bin, the item is sent to a second recycling bin,
controlled by the site administrator.
Among the design features of this bin are timers that allow you to automate
the removal of old documents. For example, an administrator may decide that
the vast majority of requests for item restores happen within the first 90
days. In this scenario, the administrator may set the timer such that items
older than 90 days are permanently deleted.
RSS has become a standard way of aggregating content from the Web. For more
information on RSS in Microsoft Windows Code Name "Longhorn," see the
technical article RSS Support in Longhorn on Microsoft Developer Network
(MSDN). By integrating RSS feeds for each SharePoint list, Microsoft Windows
SharePoint Services (version 3) provides a push mechanism for forwarding
information to end users.
Folders, one of the popular features from document libraries in Microsoft
Windows SharePoint Services (version 2), is now also available in lists.
Folders allow further segregation of content within a single list, adding
another level of versatility. One of the interesting features of folders is
the ability to assign metadata to a folder. This creates a rich content
holder that contains child content, while appearing as more than a
container. Essentially, this allows the folder to function as a separate,
but fully functional, item type. An example of this can be seen in Windows
SharePoint Services discussion boards. Each top-level discussion is, in
fact, a folder with metadata, containing one to n child objects. By
modifying the appearance of the folder, an end user can visualize the folder
as another list item rather than as a container. You can use this model in
custom lists to create a dynamic parent/child list. Many business
applications require rich container objects, for which a parent object has
both important data concerning itself, and one to n children with similar
data. Normally, you deal with this challenge by using lists in which a
parent, or master, list selection drives the display of a child, or detail,
list.
Because you can now assign metadata to folders in a SharePoint list, you can
achieve similar functionality with a single list.
Consider an Orders list, for example. You could provision a folder as an
order, and then assign metadata to it, such as order number, customer, and
shipment method. By doing so, you can make the folder mimic the master list
functionality. You can then fill the folder with order items list items,
each with its own metadata, such as item number, description, and price. Now
you have the rich functionality of a master/detail list within a single
list.
List Indexing. Integral to the idea of using Microsoft Windows SharePoint
Services as a platform is the ability to use its storage containers,
specifically lists and document libraries, for application storage. However,
a number of limitations restricted the true use of these containers in
Microsoft Windows SharePoint Services (version 2). One of the problems was
the inability to handle large lists. As lists began to grow, both in
metadata and list items, the mechanisms built into lists became clunky and
inefficient.
A key goal within Microsoft Windows SharePoint Services (version 3) was to
fix these restrictions and create a rich storage model with performance
capable of supporting applications, both external and those built upon the
Windows SharePoint Services platform. One of the key ways that Microsoft
Windows SharePoint Services (version 3) solves this issue is to include
indexing on columns. By allowing a column to be indexed, and stored as a
simple name/value pair in a separate database, access to specific items in
large lists is significantly improved. These kinds of performance
improvements allow SharePoint lists to become true data stores, capable of
supporting external applications as well as simple team sites.For example,
with an Orders list, you could provision a folder as an order and then
assign metadata to it, such as order number, customer, and shipment method.
Consider that by indexing the order number column, access to specific items
in the list by an external request becomes significantly cheaper.
Another scenario is an external application with hundreds of thousands of
records. Previously, your Web application could not use a SharePoint list as
a storage device. With the inclusion of indexing on columns, performance
increases allow this architecture. By using Windows SharePoint Services
storage, the standard features of the platform, such as views, alerts, and
RSS, can now be used as a data store explorer for internal use in simple
team sites.
Cross-List Queries - Another improvement made with the idea of using
Microsoft Windows SharePoint Services storage more effectively is cross-list
queries. Cross-list queries allow you to use the SPQuery object to query all
the lists within a Web or site collection. Previously, you had to iterate
through the parent objects to obtain a collection of SPList objects, query
the list to return the items, and then build your own collection of list
items from the multiple lists. This exercise was not only tedious and
redundant but expensive. Cross-list queries allow you to take advantage of
the efficiencies built into the SPQuery functionality in a number of
additional scenarios. Cross-list queries provide a rich querying capability,
similar to SQL queries, within SharePoint. Among the many possible scenarios
this functionality allows is the numerous aggregation scenarios commonly
requested by end users.
List Items. Several improvements in Microsoft Windows SharePoint Services
(version 3) are implemented on the item level rather than on the entire
list. The following is a list of several important new features.
Per-Item Security Item-level security is certain to be a popular new feature
in Microsoft Windows SharePoint Services (version 3). List and document
libraries now feature the ability to set roles on each item, rather than
simply at the lists level. In a developer scenario, if you combine per-item
security with other features, such as list events or extensible field types,
you could use per-item security to change who has access to an item, based
upon an entry in another field. For example, a change to the status of an
item could trigger a change in who has the ability to edit the item.
Versioning In Windows SharePoint Services (version 2), only document
libraries allowed versioning, and then only a major version would be
created. This basic functionality did not match the workflow normally
associated with documents; namely, the creation and edit process when a
document is in draft version, and then the publishing of a document to
public status. Microsoft Windows SharePoint Services (version 3) offers a
new, richer versioning model. This model includes both major and minor
versions, and versioning within lists as well as document libraries. In
addition, major and minor versions can have different security, allowing
separate draft and public version workflows. In a developer scenario,
versions are associated with a rich event model that allows numerous
scenarios, including custom workflows, item validation, and information
propagation.
Required Checkout In Windows SharePoint Services V2, users could modify
documents without checking those documents out from a document library. This
allowed multiple users to edit the same document, and left a complicated,
poorly understood merge/overwrite scenario. In Microsoft Windows SharePoint
Services (version 3), document edits are allowed only when the document has
been checked out. This forced checkout defines a clear owner model and
simplifies merging of changes.
Workflows In Microsoft Windows SharePoint Services (version 3), a workflow
allows you to attach a business process to items in SharePoint Products and
Technologies. This process can control almost any aspect of an item in
SharePoint Products and Technologies, including the lifecycle of that item.
For example, you could create a simple workflow that routes a document to a
series of users for approval.
Workflows can be as simple or complex as your business processes require.
You can create workflows that the user initiates, or workflows that
SharePoint Products and Technologies automatically initiate based on some
event, such as when an item is created or changed. In addition, your
workflows can interact directly with the user through workflow forms.
Workflow forms enable you to gather information from the user at each stage
of the workflow. You can create your workflow to interact with the user
through the standard SharePoint Products and Technologies browser-based
interface, through workflow forms in Microsoft Office client applications
such as Microsoft Word and Microsoft Excel, or even through your own custom
applications. Workflows are available to end users at the list or document
library level.
Workflows can also be added to content types. Multiple workflows may be
available for an item. In addition, multiple workflows can run
simultaneously on the same item, but only one instance of a specific
workflow type can run on a specific item at any given time. For example, you
might have two workflows, "SpecReview" and "LegalReview," available for a
specific content type, "Specification." Although both workflows can run
simultaneously on a specific item of the "Specification" content type, you
can't have two instances of the "LegalReview" workflow running on the same
item at the same time.
Events are key to transforming Microsoft Windows SharePoint Services into a
true developer platform.
Events enable first and third parties to hook into Windows SharePoint
Services behaviors and override default behaviors. Events fall into two
major categories:
List events Core events, including changes, additions, and removals of list
items and list columns (schema changes) Simple site events Deletion of sites
and site collections
Events are either synchronous "before" events, denoted by the "XYZing" name
format, or asynchronous “after” events, denoted by the "ABCed" name format.
Event receivers can be registered, through the "Features" feature, with an
Item, a List, a Web, or a Content Type. For example, an event receiver that
ensures a document always has a copyright in the footer can be associated
with a central Content Type and pushed down to all document libraries
associated with that type. As they do in Microsoft Windows SharePoint
Services (version 2), developers can override and extend the event handler
method. A new sequence number parameter allows for control of the firing
order of multiple events.
Features - Microsoft Windows SharePoint Services (version 3) contains a new
structure called a "feature." A "feature" is an end-user-oriented container
of one or more elements. An element is an atomic Windows SharePoint Services
concept. The "feature" is defined in an XML format, similar to other
existing SharePoint structures. Each “feature” definition is a set of XML
files. Many items that were previously contained within a site definition in
Windows SharePoint Services (version 2) are now able to fit as an element.
In Windows SharePoint Services (version 3), a SharePoint site definition is
transformed into a list of "features" plus a layout page and a master page.
The goal is that any templated SharePoint site can be transformed into
another templated SharePoint site simply by having the administrator toggle
features on the site and possibly switch the layout page or master page.
Upgrading a Windows SharePoint Services V2 site definition to a Windows
SharePoint Services V3 site is a process of breaking the XML files (such as
ONET.XML) into small chunks, componentizing them into arbitrary components,
and then packaging them as a Windows SharePoint Services V3 "feature" and
creating a workspace template that uses those "features."
About The Author
Jason Fortner is co-founder of Total Productivity Solutions. Total
Productivity Solutions provides custom SharePoint, webpart and .NET
development; and solutions to common software development issues are also
provided on the site.
Sharepoint sites, Sharepoint webparts and .NET Development
Following are the detailed instructions on how to install SharePoint 2007
Beta 2 on a clean version of Windows 2003. These instructions were done by
completing the installation on a Virtual Server 2005 machine that was NOT
joined to a domain. I have seen a lot of articles that say the server has to
be joined to a domain but that is not a requirement. Below are the detailed
installation instructions for SharePoint 2007 Beta 2 on Windows 2003 using
SQL Server 2005 on the same machine:
Install Windows 2003 and update the machine with the latest Services Packs
and hotfixes from Microsoft by using the "Windows Update" utility.
Create a local machine account to run SQL Server and SharePoint with. Make
sure that this account is set to be an administrator on the local machine
and that it is set to not have the password expire or to change the password
on the first login.
* If you are doing the installation on a server joined to a domain you can
use a domain account that is set as an administrator on the local machine
* To create a new local machine account go to Start and right click on "My
Computer". Select "Manage" from the list that appears and the "Computer
Management" snap-in appears. Expand "Local Users and Groups" and right click
on the "Users" folder. Select "New User" and fill in the appropriate
information.
Insert the SQL Server 2005 into the machine and make sure that "Autoplay" is
enabled so the initial installation screen appears.
From the initial screen select "Choose to Install components"
Click the "Accept terms" checkbox on the license screen that appears and
then click "Next"
Click "Install" on the next screen that appears.
Once the process to install "Native Client and Microsoft SQL Server 2005
setup support files" has completed click "Next".
Scanning of the system hardware will occur next.
On the screen that appears after the hardware scan is complete click "Next".
When the system configuration check has completed click "Next".
On the registration page enter the Name, Company and product key and click
"Next".
Select the components that should be installed.
You will need SQL Server Database Services, Workstation and Client
components; and may want to install Books Online and development tools.
You can click the "Advanced" button and select the specific components that
you would like to install. Click "Next".
Click "Default instance name" checkbox on the instance name screen and click
"Next".
On the next screen choose what account will run SQL Server 2005. Specify the
information for the domain/local account you created earlier to run SQL
Server in the appropriate boxes. Make sure the "Use a domain user account"
radio button is checked.
Click SQL server and SQL Server Agent check boxes at the bottom of the
screen. Click "Next".
On the next screen choose to use Mixed Mode authentication. You can change
this after the SharePoint setup is complete.
On the collations screen leave the defaults and click "Next".
On the "Error and Usage Report Settings" screen leave the defaults and click
"Next".
On the "Ready to Install" screen click "Install".
The setup process will run and you will see the setup progress screen.
When the setup completes click "Next". Then click "Finish".
Set the Sharepoint account that you created earlier, it can be the same
account that is used to run SQL Server, to be have Database Creator,
sysadmin and security admin rights on SQL server.
Next install Windows Workflow extensions. You will need to make sure that it
is version 3807.7 build or higher.
Double click on the install file for Windows Workflow.
Click "Ok" on the license screen that appears.
Install IIS on the sever and make sure ASP 2.0 is installed on IIS. If you
are not sure you can run the aspnet_regiis –I from within the 2.0 folder.
The default install location is C:\windows\Microsoft.NET\Framework\V2.0.50727.
* To install IIS on the server go to the "Control Panel" and double click on
"Add\Remove Programs". Click on "Add/Remove Windows Components" and in the
window that appears check the box next to "Application Server".
Highlight "Application Server" and click on the "Details" button. Make sure
that the check boxes next to "ASP .NET" and "Internet Information Services (IIS)"
are checked. Click OK and then click "Next".
Insert the SharePoint 2007 Beta 2 disk into the server.
If the disk doesn't autoplay, run setup.bat on the disk.
Enter the product key on the appropriate screen. Click "Continue".
Click the check box that you except the terms of use. Click "Continue".
You will need to choose if you are going to install SharePoint 2007 as
standalone single server, this will install SQL Desktop Express, or the
advanced version which can be for a single server or a server farm.
You will need SQL Server 2000 SP3 or SQL Server 2005 for the Advanced
version. We will do the advanced version in this process on SQL Server 2005.
Click "Advanced".
On the next screen you can choose from three options. We will be installing
on a single server and SQL Server 2005 so we will choose the first options
"Complete – Intall all components. Can add servers to form a SharePoint
farm." because the last option will install the desktop database engine
which we don’t want to install. On the file location tab you can pick the
installation location on the server.
Click "Install Now".
Make sure the "Run the SharePoint Products and Technologies Configuration
Wizard now." is checked and click "Close".
When the Configuration Wizard appears click "Next".
Click "Yes" on the pop-up window that appears about restarting services on
the server.
Click the "No, I want to create a new server farm" as we don’t have an
existing 2007 SharePoint installation.
On the Specify Configuration Database settings screen specify the name of
the server. If you used above the options above in the SQL Server setup this
will be the name of the server you are installing SharePoint 2007 on.
Leave the configuration database name as it is.
Enter the username and password of the account that you created earlier in
the setup process.
Click "Next".
Leave the default options on the screen that appears and click "Next".
On the next screen that appears click "Next".
Sharepoint will then complete 9 configuration tasks.
Once the tasks are completed you will be redirected to the Sharepoint
Administration page.
Jason Fortner is co-founder of Total Productivity Solutions. Total
Productivity Solutions provides custom SharePoint, webpart and .NET
development; and solutions to common software development issues are also
provided on the site.
Sharepoint sites, Sharepoint webparts and .NET Development
SharePoint Portal Server 2003 enables
enterprises to develop an intelligent portal that seamlessly connects users,
teams, and knowledge so that people can take advantage of relevant information
across business processes to help them work more efficiently. SharePoint
Portal Server 2003 provides an enterprise business solution that integrates
information from various systems into one solution through single sign-on
and enterprise application integration capabilities, with flexible deployment
options and management tools. The portal facilitates end-to-end collaboration
by enabling aggregation, organization, and search capabilities for people,
teams, and information. Users can find relevant information quickly through
customization and personalization of portal content and layout, as well
as by audience targeting. Organizations can target information, programs,
and updates to audiences based on their organizational role, team membership,
interest, security group, or any other membership criteria that can be
defined.
SharePoint Portal Server 2003 uses
Microsoft Windows SharePoint Services 2003 sites to create portal pages
for people, information, and organizations. The portal also extends the
capabilities of Windows SharePoint Services sites with organization and
management tools, and enables teams to publish information in their sites
to the entire organization.
- -
The portal, built on a scalable, highly distributed architecture,
provides flexible tools for deployment, development, and management, all
of which enable the portal to grow with your organization's needs. These
integration features enable you to harness information to make use of your
company’s resources. Users can extract and reuse timely and relevant information
from systems and reports, and quickly locate and access documents, projects,
and best practices across the company. The portal features search technology
developed by Microsoft Research that enables you to search file shares,
Web servers, Microsoft Exchange Server public folders, Lotus Notes, and
Windows SharePoint Services sites out of the box. In addition, you can
organize documents and information by topic and browse for relevant content.
Alerts notify you when new information is added or existing information
changes to help you better use the data.
SharePoint Portal Server 2003 provides
a powerful team collaboration environment that enables organizations to
aggregate, organize, find, and provision SharePoint sites across the enterprise.
SharePoint sites for teams, documents, and meetings can also be extended
to customers and partners, augmenting the reach and efficiency of existing
collaboration methods. The portal further facilitates end-to-end collaboration
by delivering document and content collaboration to individuals, teams,
business units, and the enterprise. Document versioning, approval workflow,
check in and check out, document profiling, and publishing facilitate easy
collaboration on documents, projects, and tasks. In addition, the portal
enables information workers to easily find and make use of people, teams,
and existing best practices—rather than reinvent the wheel with each project.
SharePoint Portal Server 2003 enables
IT departments and users customize and personalize the portal experience.
Relevant content, such as line-of-business and Office programs, Web services,
news, sales, and other company data, is delivered to the portal through
Web Parts. Web Parts can be downloaded from Microsoft and industry partners
by IT departments, or they can be developed using Microsoft Visual Studio
.NET. Authorized users can add Web Parts to organizational or divisional
portals
from Web Part galleries, without the need for any Web development experience.
In addition, IT departments can "lock down" specific Web Parts or page
zones so that organizations can distribute important information to all
employees through the portal. Users are also provided personal portal pages,
called My Site, where they can organize the information, programs, and
SharePoint sites they access throughout the day.
Book Description
The training material consists of 12 hours of recorded presentations and
demonstrations as well as a 350 searchable slide course workbook (provided
in electronic form) that can be printed for taking notes. Additionally,
6 hours of labs, which can be performed on the included Virtual PC image,
will help the reader solidify the concepts and examples learned.
More than 200 system architects,
developers, and administrators from companies such as Microsoft, Lexis
Nexis, Intel, and Nucor attended the "Microsoft SharePoint: Become an Expert"
class on which the content of this training course is based. Below are
some of the items that that the reader will learn as part of the course:
SharePoint features and how they differ
in Windows SharePoint Services (WSS) and Office Portal Server.
New features in Word, Excel, Outlook,
and InfoPath that make SharePoint really useful.
Best practices for organizing portal
and WSS sites.
How to administer WSS sites and Portal
areas content.
How to administer WSS sites and Portal
areas security.
How to administer user profiles, active
directory imports, and how to setup useful audiences.
How to plan deployment set up multiple
portals and content databases.
The architectural foundation of SharePoint
platform.
How to develop ASP.NET applications
that work with SharePoint object model.
How to modify site definitions; change
look and feel, add items to context menus, and add new columns to lists.
Differences between site definitions
and site templates and advantages, disadvantages of using one or the other.
How to develop and deploy web parts
that access SharePoint object model, external databases and web services.
How to use FrontPage 2003 to change
look and feel of SharePoint sites and create web parts that display information
from various data sources.
How to use out of box usage analysis
and how to extend it.
How to setup search indices, content
sources, and search scopes.
How and when to use various backup and
restore tools.
How to develop applications that use
document library events and how to extend workflow using document library
events.
How to administer single sign on and
how to build web parts that use single sign on object model.
About the Author Scot
Hillier is the Vice President of DataLan Corporation, a Microsoft Gold
Partner in Collaborative Solutions located in White Plains, NY. Scot is
the author of six books on developing with Microsoft technologies including
"COM+ Programming with Visual Basic". He is also the author of MTS Programming
with Visual Basic, VB6 Exam Guide, VB5 Exam Guide, Active Server Pages,
and Microsoft Visual Basic Scripting Edition A former VBITS speaker and
trainer, Scot brings a unique combination of technical skill and business
perspective to his presentations and books. Scot lives with his wife and
two children in Hamden, CT.
Book Description This
book provides guidance to readers who want to design and deploy business
solutions based on Microsoft SharePoint technologies. In this book, Hillier
will define the business case and scenarios for Microsoft SharePoint technologies.
Hillier will also review the installation, configuration, and administration
of business solutions based on Microsoft SharePoint technologies as well
as provide programming instruction, guidance, and examples for custom Web
parts and solutions built on Microsoft SharePoint technologies.
·Chapter structure and coverage
is targeted at getting started quickly with the products and technologies.
Will provide hands-on exercises for each chapter ·SharePoint applications
will be developed for the latest OS, Windows 2003 ·Provides a document
management strategy and Office solutions for a large corporate environment
Greg Lindhorst, Lead Program Manager,
SharePoint Web Part Infrastructure, Microsoft Corporation "A great, comprehensive
introduction to the world of SharePoint Web Parts."
Book Description Learn
the complex issues in creating Web Parts for SharePoint Portal Server 2003
and Windows SharePoint Services (built into Windows Server 2003). Save
countless hours by learning the correct way to develop Web Parts. This
book does not cover SharePoint administration...it just dives right into
Web Part development and related issues.
This book takes a rational, no-nonsense
approach in a compact guide - only 176 pages. The book is written for a
beginner to intermediate-level developer, so you get the basics…fast! It
covers the basics of virtually all areas of managing SharePoint Web Parts,
including creation, testing, and deployment. Technical accuracy is assured
by Zac Woodall, Program Manager, Office DBI, Microsoft Corporation.
This book comes with free bonus materials:
1. Extra Chapter - Using the WPPackager
2. Extra Chapter - Using External
Resources
3. Code examples in C# and VB .NET
4. Sample Web Parts and Policy File
Book Description Microsoft
SharePoint Portal Server 2003: Planning, Design and Implementation provides
an in-depth examination of the tasks involved in planning, designing and
deploying the product in your enterprise. The book examines the product
from the user's perspective, the administrator's perspective, and the application
developer's perspective and looks at how you can maximize your investment
by integrating the SPS with other enterprise applications in your environment.
The authors are experienced consultants that have helped many large corporations
deploy Microsoft technologies within their enterprise. This book is filled
with practical experience and knowledge gained from working with customers
in the field.
Complete guide to shared and work group
issues with SharePoint, Exchange 2003 and Office 2003
Critical techniques for systems administrators
to deploy and manage SharePoint tools
Features most important issues for day
to day efficient management of SharePoint
Book Description
Get the definitive resource for administering Microsoft SharePoint products
and services—with in-depth technical information and tools developed by
Microsoft Most Valuable Professionals (MVPs) and the Microsoft SharePoint
team. This exhaustive, 1000+ page reference delivers all the information
you need to plan, design, deploy, and manage strategic solutions using
Microsoft SharePoint Portal Server 2003 and Microsoft Windows® SharePoint
Services. Topics include architecture; capacity planning; deployment scenarios,
including small, medium, and large server farms; configuring administration;
working with SPPT; security features; maintenance and disaster recovery;
customization and solution development; using SharePoint with other Microsoft
products; and upgrading/migration strategies. The companion CD-ROM features
a fully searchable eBook, plus tools, scripts, and job aids—everything
you need to help save time and reduce ownership and support costs.
Book Description
As businesses attempt to maximize every employee hour, knowledge management
and collaboration tools have become more popular. SharePoint Portal Server
2003 offers businesses a secure enterprise portal solution for knowledge
management, document sharing, and user collaboration. Built as a hub for
the Office 2003 desktop, SharePoint makes it easy for users to get information,
work together, and make smarter, faster business decisions. Because the
adoption of the 2001 version of the server was slow, Microsoft built the
need for SharePoint into the new Office 2003 applications. For instance,
using FrontPage 2003 without SharePoint Portal Server 2003 allows only
60-70% of FrontPage functionality. The power of SPS 2003 allows users to
create and manage robust, easy-to-build Web sites for collaboration on
documents, projects and tasks, and allows these sites to be leveraged throughout
the organization. Features such as document versioning, approval workflow,
document profiling, and publishing help improve information flow. Microsoft
SharePoint Portal Server 2003 Unleashed fills the void readers have been
looking for in previous books on the topic with a complete reference written
by experts with valuable experience with enterprise-level solution design
and implementation.
