SharePoint Workspace

Along with the power of the coordinator role comes the responsibility to create the workspace and organization of documents.Depending in its corporate philosophy, you may or may not want to start with the participation of users in a ' needs analysis. I think those polls get users involved, which ultimately makes workspaces more effectively and efficiently.

Document Folders

One of the benefits of SharePoint Portal Server is to embrace the modern document-centric view instead of the elderly application-centric view. In practical terms this means generating a folder called documents, such as 'Project X' & then add Word documents, Excel spreadsheets, images, Paint Shop Pro, all in the same folder.

Mayor V standard

Folders improved means you can publish, check in and check-out documents. To use the approval process then make sure to create an enhanced folders. None of these additional attributes are present in the standard folders.

Document Profiles

Profiles of success in the metadata. Metadata is data about data. The profiles are an extension of the properties that nobody seems to fill in Word documents. What SharePoint does is force everyone to be more aware of these properties. Moreover, as coordinator can force the authors to complete the metadata by presenting the properties menu, when ever you create or edit the document.
I hope you have already realized the benefits of collecting this data - more power to search documents. Better information for the search engine, means a greater likelihood that a user with only limited information, find the document that they should have. The end result is the most efficient system for the document use the material.

Document Categories

Another mechanism to help you find exactly the document you need. Use the Web folder view to rename and organize their categories. Papers are not restricted to just one category. Categories can also contain documents of a variety of folders in it an efficient and flexible support to the search.

SharePoint List

Collection SharePoint List Web may gather lists of different SharePoint sites in a single view. At the hearing, you can work with data and then export to a spreadsheet. To create a SharePoint list collection web, first you must select a site, a list on the site and a list view of the list.
Then select columns in the list to collect data, select or input new column names for original columns so these will be added and displayed in the collection of SharePoint Web list. Repeat above actions, you can get SharePoint lists.Eventually combined. All the combined elements of SharePoint list is displayed in the list of Web Parts collection.
You can create standard view, Gantt view and calendar view for collecting part of the SharePoint list Web for filtering, sorting or grouping data. These collection of SharePoint list views are also created to re-organize data collection from the list. You can create public or staff list collection view to determine which list or list will be filtered, which list columns will be displayed, and that the column will be sorted and grouped.
Creation and manipulation of list items in the collection of SharePoint Web parts list is the same operation on the list of SharePoint Web parts. You can view, edit and delete item, manage permissions, start workflow, version view, alert management, document open, check out / etc in the collection of SharePoint Web parts list .

Why We Build It

TSharePoint is attractive for organizations to build departmental sites to manage documents. Along with the increasing amount of data, SharePoint users need to easily track and control data elements in the list of Cross Site Data View. SharePoint List Collection Web helps users easily combine between sites and lists of items in the checklist in the application list the site as part of the defect and view web.

How SharePoint is not a database

Part of the problem is that business users to design the lists are not familiar with the basic concepts of databases - that only need to store your information. Part of the problem is false advertising consultants & / or Microsoft SharePoint is a miracle that platform can do anything - it does some things well, but to replace the SQL Server or Access database is not five of them. The other problem is that no nice way for bi-directional coating data from a SharePoint database - the Business Data Catalog only works in read-only mode & does not permit updates back to the underlying data store .
Here is a list of some of the features that have a SharePoint database is not compatible with - the moment that need these features will have a real database.

• Principal and foreign keys: one of the most basic concepts in a database is the application of a unique identifier (either system generated or supplied by the user) that can identify a record and on the link in the table relations of the child's parents.
  
• Transactions: if two changes are needed to go hand in hand and second hand does not want the first change to get rid (canceled).
  
• SQL language: complex queries can be written in the code myself using a standard language. Queries can be saved and purposes.
  
• Stored procedures: the database programmers can write complex routines can be called as the blocks of reusable code.
  
• Indexing and query optimization: is used to improve performance, the index allows the database designer pre-specific index fields that are frequently used in queries to improve performance. In addition, most engine optimization databases must be based on what they are trying to seek to optimize the way data is retrieved.
  
• Data from large binary fields: modern databases allow storing large binary files such as video files, large text books, images, etc in the database. SharePoint can do to get large files like documents, but you only get one per record and a spot of wine.
  
• Access beyond SharePoint: the lists are accessible outside of SharePoint, but only through XML or programming interfaces. Lists are not stores of data to be used for line of business applications made independently of SharePoint because integration is relatively poor compared with the execution of a SQL query in a database.
  
• Cascade Delete: If you delete a registry of parents, their children will also be deleted. In most databases, this can be configured to automatically pass or reject the removal of the parents until the children are deleted first. This eliminates the risk of children orphaned records.

These features are considered basic in databases - that have existed for decades and even more primitive databases such as Access or FileMaker Pro have most of these features.

SharePoint Site Moves, Database Moves and Balancing Growth

Adoption of SharePoint is the right of all times now with the release of MOSS 2007 and WSS 3.0, this is brilliant for its investment, but can be a nightmare for a poorly planned deployment that was not prepared for a giant growth. Of course, the operational tasks can be on the horizon to a better balance of content databases in relation to size, the size of the database and potentially even your SQL storage plan in general.
Move the Web are an important part of keeping your SharePoint environment. Situations may arise where a site has exceeded elsewhere for a substantial amount. To help support this larger site in a smart way we have to migrate to its own database collections away from other sites (Split). Also, if you know a site has the potential to grow substantially this would be a good idea as a proactive approach. We refer to this action as the division of a site. Other situations may also justify the division sites of a database as the site maximum cap is set high initially and now has also collections of sites are in each database or for legal or business is necessary to separate certain sites elsewhere, even in a database level.
Databases balance would be further action that may need to entertain to get more control over their growth. This can be as simple as separating a SQL database and move it to another LUN in your instance of SQL or the migration of the SQL database to a completely different server, or as complex as load balancing between the creation of site LUNS / SQL servers.

SharePoint Database

As we all know, Microsoft SharePoint Portal Server is used to develop portals smart enough to seamlessly connect users, teams and knowledge that allows us to take advantage of relevant information across business processes.
In that situation, it is essential to use the cross-that data are stored by SharePoint and any other application where you intend to use the same data, which is entering through graphical user interface of SharePoint. The actual cost, time and productivity advantage of SharePoint can be used by ourselves to allow the use of portals and data entered through these for integration with other applications smoothly. As such, we have no control over how data is stored within SharePoint portal but that should not be an obstacle in the design of user interfaces with SharePoint. SharePoint provides methods to play with all the data you want to integrate with other external applications to SharePoint.
Principally, SharePoint Portal Server and Windows SharePoint Services uses a database from SQL Server to store all your documents, web pages, and metadata. Another database is used to store the most detail. In fact, almost everything related to SharePoint is stored in a SQL Server 2000 or MSDE database. By its very design, the database is the heart of SharePoint, and developers must be partners with its format to make use of it. During installation, you can define whether the SharePoint database is to MSDE or SQL Server 2000. SharePoint data is stored in a relational database either using MSDE or SQL Server 2000 in terms of how it was installed. All SharePoint data can be seen in Enterprise Manager on the SQL server involved.
The database name differs based on how the portals have been named there. A few crucial databases and their SharePoint nomenclature are like this:

• The database that ends with _Config_db: database stores the configuration for the whole SharePoint server / farm. Anything pertaining to the global configuration and set through the SharePoint Central Administration is stored in this database.
  
• Finish _SITE database: stores all the contents of a specific portal. Contains files, web pages, websites, sites, and all things related to SharePoint infrastructure.
  
• Finish _PROF database: stores all information about user profiles, but also holds the details of what information we collect on different user profiles.
  
• Ending _SERV database: Stores data for searching, reporting, and indexing. It stores the gatherer log information as well as text indexes content that is crawled. In fact it can be easily controlled by the right mouse button on any of the databases and choosing Properties. In fact, this could be one way of knowing how much space each function or activity on your site, you are assuming.

ASP.NET Pages in Your SharePoint Portal

SharePoint ASP.NET provides a few pages that let you manage a portal. However, business situations arise that require developers to create their own ASP.NET pages. A position that comes to mind is an employee directory. In large establishments, it is possible that the task of showing to all employees on the basis of the employees are seeking standardsor a particular department. Once shown the list of employees, you may need to learn more about where that particular person, the biological information or floor to floor map of the employee's office. In this scenario we have the following options:



Create a Web Part to display the employee directory and then have another ASP.NET application that will have only three pages to show the location of the person. This ASP page. NET accepts a query string to get the ID for the employee. This would be the easiest way to do this option, but you have to maintain a separate application for a single page.
The next option might be the development of two web parts. The first part this site has a list of names of all employees. This part of the Internet is an element of attack. The second part will contain the site location information of the person. The second Web site will be a part of consumers. The first part of the Web site offers the second EmployeeID. The second part uses the EmployeeID web. This option is very good, unless the second Web part is a really huge screen plant leaf and the bolts where the person is exactly the user will have to scroll down the page to find the exact location of employees.
The last option is to build a Web similar to option 1 and then build a separate web page holding the information of location or soil map information. The Web will have a link and open floor map information in a separate window. With this option the ASP.NET website is also hosted in SharePoint portal. This sounds simple, but if you try to create ASP.NET pages as is done you will start getting errors because SharePoint does not recognize simple ASP.NET pages. Therefore, we might need some tweaks to understand that this is SharePoint SharePoint ASP.NET pages.

SharePoint, ASP.NET Relationship

aUnless you've been living under a big rock that you heard of this thing called Microsoft SharePoint. And, like Chicken Little, people in the community of SharePoint is running around saying that the end is near. While there are a lot of power that SharePoint offers it does not mean it will not be written in ASP.NET (define) for longer - on the contrary, SharePoint is a very good behavior ASP.NET 2.0 application itself - - at least in the 3.0/Microsoft Windows SharePoint Services Office SharePoint Server 2007 calendar anyway. That said, there are some differences when it comes to developing with SharePoint that the ASP.NET developer should consider. Here are a few:

Develop on a Server

Most ASP.NET developers are running Windows XP and use construction in IIS to develop your applications. That is the model that most developers are accustomed to. However, SharePoint can not debug remotely so that means developing a Windows Server 2003 or Windows 2003 R2. Of course, most people do not want to run Windows Server 2003 directly on your desktop or laptop. That means that either server virtualization with VMWare or Virtual PC 2007 - which is free. This in turn means more memory than most development teams have. You need at least a gigabyte of RAM for the development of moss and at least 768 megabytes to develop with WSS. Add Windows XP to overheads which actually watching an absolute minimum of 1 GB to do SharePoint development with 2GB of being more realistic, and 3 GB or more of the ideal. Not exactly your standard configuration.

Install

To create in ASP.NET, basically, you install Visual Studio & that is it. Everything is there. Your operating technique already has IIS, & even if you can not use the built in Casini. Unfortunately, nothing comes out of the box with SharePoint - SharePoint even itself. If you need to create WSS have to install WSS. That requires at least three discharges -. NET 3.0 & WSS.
First steps in development becomes more difficult after you install Visual Studio. It is also necessary to install two pieces: Visual Studio extensions for Windows Workflow Foundation (VSeWF) Visual Studio extensions for Windows SharePoint Services (VSeWSS) & Windows SharePoint Services Application Development Kit (SDK WSS). The VSeWF added workflow capabilities of Visual Studio. VSeWSS added some templates (including pieces of cloth & definitions of the list) & solutions of the generators. WSS SDK adds some SharePoint workflow templates specific - in addition to the documentation.

SharePoint Server 2007 SDK

The SDK for the 2007 Microsoft Office SharePoint Server describes technologies that Office SharePoint Server 2007 provides developers. It contains general information and step by step, how-to procedures for programming with Office SharePoint Server 2007 that can help you start writing applications. There's several examples of code in the documentation as well as some tips and best practices for using the development platform in Office SharePoint Server 2007.
After installing the SDK, those who are new to Microsoft SharePoint Products and Technologies must start with What is New for Developers in Office SharePoint Server 2007. Most experienced developers should also review the changes and improvements to SharePoint Portal Server 2003 and MCMS developers 2002.
Microsoft Office SharePoint Server 2007 builds on the Windows SharePoint Services 3. 0 of infrastructure to provide a true enterprise portal platform. For central platform documentation, refer to the Windows SharePoint Services 3.0 SDK.

SharePoint Themes

The easiest and fastest way to implement the same look and feel in any SharePoint site is the creation of a theme of the site. A SharePoint site theme basically consists theme.inf, theme.css, and image files. Theme.inf file basically represents the topic title. Theme.css is a stylesheet file that defines colors, header images and the layout of a site and image files can be referenced here to display on the page. When building a custom site theme, you can easily modify the style, but in fact, write and edit the style sheet can be chanllenging when more than one hundred items to try.
Here is a short procedure of creating a custom site theme named "Ghost":

• Copy any theme folder in "C: Program Sharedweb extensions12TEMPLATETHEMES server FilesCommon FilesMicrosoft folder and paste with its name replaced with" Ghost ". In this example, copy GRANITE folder.
• In Ghost folder, rename GRANITE.INF file for GHOST.INF capitalized.
• GHOST.INF Open file with notepad.
• Change the value of title under [Info] A Ghost.
• Replace every word, Granite, under [titles] with Ghost.
• Open "C: Program Sharedweb extensions12TEMPLATELAYOUTS1033SPTHEMES.XML server FilesCommon FilesMicrosoft" file with Notepad.
Add the following lines under <SPThemes> tag: <Templates> <TemplateID>Ghost</TemplateID> <DisplayName>Ghost</DisplayName> <Description>Ghost theme.</Description> <Thumbnail>images/thghost.gif</Thumbnail> <Preview>images/thghost.gif</Preview> </Templates>
• For display thumbnail and preview correctly, you need to capture the screen and save the file "C: Program Sharedweb extensions12TEMPLATEIMAGES server FilesCommon FilesMicrosoft" folder named thghost.gif. You can change the file name. Gif if you change the image filenames in the preview label.
• Make a iisrest for the server to recognize the new theme.

Fairly simple procedure. Now you are ready to test your new theme. In Site Settings, you can now choose Ghost theme, however, the issue is not different from the issue of granite. Now is the time for you to play with the theme.css file!

Customizing SharePoint Web Parts

Software developers have the flexibility to generate custom Web Parts to achieve sophisticated custom functionality in SharePoint Portal Server. Generally this is used to generate custom functionality common for an organization or project level. There is several properties available by default in SharePoint Portal Server to customize the Web. Alternatively, software developers can generate their own custom properties to achieve  additional customization at the site of appearance & behavior.

Properties

The Web Part base class provides a default set of properties that allows users to change the appearance and behavior. These properties are in the default Web property pages contain some basic properties and customization, such as height, width, state framesets and more (as illustrated below).

A custom property is a property that a software developer creates when it is necessary to introduce additional functionality or behavior on the Internet that is not covered by the base class.





/ / /
/ / Form available / default properties of the template
/ / /
[Browsable (true), Category ( "Miscellaneous")
DefaultValue (defaultText)
WebPartStorage (Storage.Personal)
FriendlyName ( "Text"), Description ( "Text Property")]
publicstring Text
(
get
(
return text;
)
set
(
text = value;
)
)

Laserfiche Web Part for SharePoint

The Laserfiche Web Part for SharePoint is key to image functionality to SharePoint collaboration portals. Once the component is added to the SharePoint server farm can be added to any form of SharePoint Portal Web itself anywhere, it adds. Allows users to browse any part of the Laserfiche folder structure through SharePoint. You may think that is putting the folder browser that is part of the Laserfiche client in the SharePoint interface.
The component has a number of parameters that can be defined. One is the ability to point the web part to a specific folder in Laserfiche, which makes it easy to include documents photographed in any collaborative process. Suppose a team is working on a new contract. It is likely that some of the documents they need to work with paper, and SharePoint does not offer an easy way to manage scanned paper. Thanks to LfSPI, however, is simple. In the portal project, add the Web Laserfiche and points to a folder in Laserfiche. Released Laserfiche scan directly from a button in the web interface and upload the Part Laserfiche newly scanned document. It is now safely stored in Laserfiche and available right in the team's SharePoint site.
This functionality helps the content for easy access to the user, because the relevant information presented to them in a single interface, uniform and have to try to determine if the document is actually stored.

SharePoint List Synchronization

You can use SharePoint sites to store and present lists of useful information, including announcements, contacts, events, tasks, themes, and custom lists for other types of information. You can use Microsoft Office Excel 2003 and Microsoft Office Access 2003 to view and edit data stored in lists on SharePoint sites. This is a great way to share information with other users, make use of the information already published, and provide standardized lists of information (eg names of products or services of the company) that can be used throughout the company.



When Office 2003 is installed on your desktop computer, you can import data from a list on a SharePoint site to Excel 2003. You can then view, analyze, update and manipulate data in Excel. If you have the correct permissions on the SharePoint site, you can also use the data from Excel to update data online with the push of a button. Also you can export data from Excel 2003 or Access 2003 to generate a list on a SharePoint site, and can be used to generate an Access 2003 database table that is linked to data from the list on a SharePoint site. To build or import a list, you must be a member of a site group with the Manage Lists right for that SharePoint site.

Document Workspace Sites and Meeting Workspace Sites

Windows SharePoint Services provides document workspace sites and Meeting Workspace sites, new tools that are to communicate and share. A Document Workspace site or Meeting Workspace site is a SharePoint site that can quickly create from an Office 2003 to share a particular task, a document or project. This gives easy access to Windows SharePoint Services when and where you need them. Windows SharePoint Services also creates and stores lists that are relevant to the Document Workspace sites and Meeting Workspace sites, including tasks, members, links and related documents. To create a workspace site, you must be a member of a site group with the Create Subsites right for that SharePoint site. For more information, see "Document Workspace Sites" and "Meeting Workspace sites" later in this document.

Microsoft Office 2003 Integration

Each application of minimum standards that have been part of user adoption has been great. Capacity planning becomes an important exercise if you need to make sure your portal truly become a unique solution to its users. Excel Services, catalog data, document conversion services are all resources. Design of a farm that can scale with the business is of utmost importance to ensure a wonderful experience for users. Poor performance leads to poor user adoption leading to a rancid portal.

SharePoint Integration

Document management and participation are the most important features of Windows SharePoint Services. You can use these features to create, manage and share documents easily. Because of these features are included with Office 2003, you can easily find and use. In addition, you can take advantage of these features when using a Web browser to search, browse, or join forces in documents that are stored on a SharePoint site.

File Menu Integration

replaceof documents is completely unified on the File menu in most Office 2003 applications. You can use the File menu to open or save documents in a document library on a SharePoint site. When you save a document in a document library, Office 2003 also stores the metadata for the document in the library. When you close the document you may be asked to add or update metadata, or you can use the Document Information tab on the rear panel of the task of shared workspace in the Office application to view and modify the metadata for documents. You can customize the metadata schema of the documents, which means you can create libraries that are tailored for different types of documents. This makes it much easier for users to classify documents properly and to find documents at a later time.

Document Check-in and Check-out

Most of the methods of traditional document distribution using electronic mail or file shares for documents that have multiple authors or publishers. The problem with these methods is that they can quickly become confusing. Identifying users with the latest version of a document that is difficult, and many can edit a document at the same time, resulting in conflicting versions. Trying to track changes can lead to confusion and lost productivity, especially if a document should be reverted to an earlier version. To avoid these problems, Windows SharePoint Services provides an intuitive and easy to use method for tracking the version history of a document. First, if you want to work on a document that is stored in a document library, you can review the document. By doing this, other users can not make changes to the document. This helps avoid the confusion that can occur when multiple users make simultaneous changes in the same document. After finishing work on the document can be seen in the document that others can work on it. To check out a document, you must be a member of a group site with editorial articles for that SharePoint site.

Microsoft SharePoint Technologies Platform Solution

The integration of technology into practice ideas that provide SharePoint platform compatibility, stability and reliability that the CTP is necessary. The solution features high-level of students includes the integration of portal EagleNet online registration system of the TCC, where students can submit for classes, activate a eAccount receive their course grades online and paying dues . There was also the integration with the Black Board, a student-to-tool communication of energy used for distance learning. SharePoint services that were implemented included out of the box, and custom code. There was also the integration with Exchange and Active Directory forcertification and synchronizing Outlook e-mail and visibility of schedule. All services and consolidating applications always available through the single entry point - the student portal MOSS portal that provided single sign-on potential.
ROI
The "portal provides access to a variety of services through an access point:

• Exchange integration or synchronization and E-mail
  
• Black or EagleNet integration Integration Board
  
• Identification of hearing and customization
  
• Single Sign-on capacity
  
• Reporting capabilities

Microsoft SharePoint Implementation Solution

The integration of technology into practice ideas that provide SharePoint platform compatibility, stability and reliability needed VyStar. Based on Windows VyStar clogs time IT department to provide world-class connectivity and constraint products to its user community. By providing an infrastructure for SharePoint Portal Server 2007 for all branches and departments VyStar, VyStar IT department compliance with corporate objectives.

Return on Investment

• Distribution of branch administration at the departmental level and content of the site and the level of security to people in the business units where appropriate
  
• More specifically, this refers to documents and communications (news)
  
• Support for an integrated, extensible platform to manage intranet applications
  
• Offering an intuitive interface, rapid application development environment for creating forms (InfoPath), reducing the effort of creating and maintaining electronic forms
  
• Provide enhanced search capabilities for users
  
• The acceptable recovery time in case of a disaster

SharePoint implementation

Microsoft Office SharePoint Server (MOSS 2007) is a collaboration tool truly revolutionary. There are few technologies that can sell itself and MOSS is two of them. I have seen clients who have no idea what is required of SharePoint, but they require anyway. Microsoft has done an incredible job of showing what MOSS can do for the company and based on initial information that is on track to become the WebOS for the 21st century. like any other Microsoft product, MOSS is relatively easy to install and configure, and most companies think they can get a site up and walking without any design technique.



Based on my experience with the implementation of minimum standards in several companies, here are the top 10 reasons why an application may fail MOSS

Capacity Planning

Each application of minimum standards that have been part of user adoption has been great. Capacity planning becomes an important exercise if you want to make sure your portal truly become a unique solution to its users. Excel Services, catalog data, document conversion services are all resources. Design of a farm that can scale with the business is of paramount importance to ensure a good experience for users. Poor performance leads to poor user adoption leading to a rancid portal

setup a site, Joe User will love it

improve the productivity of information workers is a central goal for MOSS and employee engagement in the planning stage is that there is an adequate level of buy-in from all levels within the company. I am not recommending the "design by committee" here. The key stakeholders should be made to the product during the initial deployment phase of building their comfort level with the tool and get feedback. Increases their sense of ownership and lead to greater adoption. If users do not bother to create or maintain the contents of all you have is a stale website that displays the local time and displays the stock price and the company has spent $ 200k of your application.
A good business application MOSS strength to look to its line of business applications and evaluate their integration into the portal. A large number of stakeholders seize this opportunity to let go and want

• Surface of each line of business database in the moss
  
• Integration with LOB all settings MOSS 2-way synchronization
  
• To improve their infrastructure and reorganize your Active Directory domains
  
• Virtualize their servers all
  
• Update the SQL versions and LOB applications for the portal application

SharePoint Security and .NET Impersonation

Microsoft Windows SharePoint Services and SharePoint Portal Server 2003 have become very popular in recent years and have helped many businesses create an infrastructure for sharing and collaboration of internal information. Out of the box, SharePoint provides a wide variety of functions that spans many vertical markets and divisions within an organization. From a development perspective, the services of the SharePoint platform an IT organization, offers a unique opportunity to focus almost exclusively on providing domain-specific logic and functionality of value to businesses they support.
During the process of enlargement of SharePoint is essential to understand the security model of SharePoint. Several techniques can be applied to provide the optimum combination of ease of development, deployment, functionality and security. This article explains the basics of SharePoint Windows security authentication mode in the domain of IIS (SharePoint Account mode). Custom Web Parts are used to demonstrate the security infrastructure of SharePoint, and will be taught techniques to ensure that implementation is as safe as possible while providing a clean user experience and consistent.

SharePoint Authentication

To authenticate users, SharePoint has the ability to run on any of the modes that are available in IIS. These include Anonymous, Basic, Integrated Windows authentication or certificates (via SSL). This article assumes that runs in SharePoint integrated authentication mode of Windows, which is common for domestic situations in SharePoint is configured for mode domain user account. Since SharePoint is built on ASP.NET, it is configured much like a normal ASP.NET application. The following XML element that defines the authentication mode for a SharePoint installation can be found in the Web.config file in the root of a SharePoint installation (C: \ Inetpub \ wwwroot on my server):
The ASP.NET configuration item tells you what mechanism should be used to authenticate users to the site. Importantly, in addition to this piece of ASP. Network configuration, implementation of SharePoint Web IIS (Default Web Site on my server) is also configured to authenticate through Windows. Authentication modes are available in ASP.NET Windows Forms, Passport or none, not to be confused with IIS authentication modes.

SharePoint Security Concepts

Security is a hot topic these days and it is clear that the data need to be protected. At the same time, an amazing amount of data remains largely unprotected. Why? If you read this article that might agree with me that is (still) too complex to implement security strategies. The good news is, however, "Security and SharePoint" is not equivalent to "Mission Impossible".
SharePoint 2007 comes with a lot of important new security concepts and features. Much of the credit actually goes to the ASP.NET team who delivered many of the concepts that now shine in SharePoint 2007.
As with SharePoint administration in general, the security settings in SharePoint 2007 is the responsibility of different groups of people at different levels. IT managers determine which authentication and security policies are in effect as part of the overall server configuration. They also need permission to set up shared services farm. Separately below, the site collection administrators and site owners to manage the content approval. Both are equally important, as the best security measures will fail if a content management system accidentally gives you access to the wrong person. Therefore, even audits and records are important to control use, and to identify gaps and errors in the overall configuration.
One of the great steps forward with security in SharePoint 2007 are "fine-grained permissions. This means that permissions can now be set even at the "point", for example, individual documents and folders within a library or list. This enables existing groups, roles and users enough concept, ie it makes it much easier to make exceptions, and to give (temporary) access to a single document without changing the general safety rules.
At first glance it might seem strange that SharePoint, by default, it installs a collaboration portal with security enabled, instead of a web site with anonymous access. From a security posture that point, of course, has total sense. Microsoft even went a step further: even when anonymous access is enabled by default, access is very limited. Document creation and management is completely impossible with anonymous access.

SharePoint Services v3.0 vs Microsoft Office SharePoint Server

Hopefully most people know that Moss is a superset of WSS. In other words, MOSS has the foundation laid by WSS v3.0 and expands, creating functions that sit above it, use the basic framework of WSS, and extending it's good for the initiatives of large enterprise deployments and portal scenarios. The following is a list of things that MOSS not WSS v3.0. I thought it would be a waste of text to display the characteristics that the two have in common, or places that are reused nonvascular plants WSS practicality without change or improvement.

Social Networking

MOSS provides social networking features, including social networking Web Parts and profile link. MOSS allows linkage between colleagues and partners to identify the hierarchical relationships. These relationships can be published on my web pages and went through his personal profile which appears on a site / web part.

Site Directory

MOSS provides a new model site called "Site Directory. When you generate your first portal of moss, which comes with a directory of sites. This site template is designed specifically for tracking links to sites, displaying site maps and lists for site navigation and search through the site directory. With a web directory on the website, you are asked if you need to post a link to your site again each time you create a new web portal, regardless of their depth in the hierarchy. This unique feature is, in my opinion, absolutely necessary for any deployment of SharePoint intranet. And yes, that means that I think Moss is a prerequisite for any real Intranet deployment of SharePoint on any kind of significant scale.

Site Manager

MOSS provides for an easy drag-and-drop interface for managing navigation bars, navigation strips, portal hierarchy information, & much more. In general, managing sites, site hierarchies, & hierchical site content is much less hard (& in some cases basically made possible) with MOSS.

Knowledge Network / People Search

MOSS provides a greater "people search" tool that can be used to treat mine hidden relationship data and show the people related to knowledge. For example, if my name is splashed across dozens of websites that contain C #-related content, the idea is that the moss will show you my name and profile in response to the search for people related to C #, and I suggest as a local expert.

Business Data Catalog / Business Data Search

I think this is possibly three of the most important features of MOSS. Allows you to extend SharePoint data by integrating business data from external sources, such as Web Services or Relational Databases. This allows you to do things like display SAP data within your SharePoint portal, or add a column to a requirements document stored in SharePoint that points to data stored on a device management requirements in other parts of your business. The possibilities of the BDC are limitless, and I think each and every one of SharePoint 2007 developer needs to learn these things

Excel Services

MOSS offers the possibility, through shared service facilities, to have what amounts to an Excel server. This provides the ability to display the contents of the Excel spreadsheet Web Part, and selectively allow editing of secured regions of that spreadsheet, including evaluation of the formulas contained in the leaf and the results are displayed in real time. There is also a user interface, less version of this where you can access a stored central spreadsheet via web services, creating a "session", and programmatically feed data into the sheet and get formula to calculate the values of the sheet - all without interfering with other people using the same spreadsheet from a central location. The impact for companies that do nothing at all with Excel is enormous.

In short, Moss is a great advantage. I'm not talking about the prices, because the impact of dollars and cents in a business decision to implement a particular technology is always specific to industry and individual enterprise. But I will say this: prices aside, it would be very, very sure of your needs (or lack thereof) to circumvent the minimum standards and just use WSS v3.0.

PDF Document on a SharePoint SPS

Microsoft SharePoint SPS created to allow users the ability to place PDFs and Word documents online. SPS 2003 SharePoint Portal Server has enhanced security and basic fixes are not available in the 2001 version. Viewing a PDF online using SharePoint takes 5 to 10 minutes depending on file size.

Instructions

• Save the PDF file so it gives everyone the ability to read the file. Select the option "Allow View all users" option. The option will be in the "Save" button.
• Open SharePoint and making a portal area for the document you are. Click SharePoint program files or the desktop icon to open the SharePoint.
• Click "New" and select "web page". Click Edit on the menu to configure the website in edit mode before continuing.
• Select "Modify shared pages. This allows you to edit the page and insert the PDF.
• Open the "Add Web Parts" window and click "Browse" to locate the "Content Editor". Click "Content Editor" and drag it to the portal page where the PDF is displayed. To edit this page, click the down arrow and change the parameters to modify.
• "Click on Source Editor." This is located on the right side of the screen.

Properties in SharePoint Search

Most users of SharePoint Portal Server quickly become enamored with the ability to add new fields (with metadata) to documents in the document library. Suddenly it becomes possible to associate information to a file beyond the file name to us from the beginning limited to the computer age.
Few users, however, have the opportunity to understand how this meta data is used by SharePoint to search. This leads to problems when the user decides it is necessary to use SharePoint Portal Server Search to search the information in a field that had been added. In this article we will learn how SharePoint uses document library fields to create properties that can look and how to enable searching on those properties.

Power of Properties

Search SharePoint Portal Server is actually working in two different ways. First, is the full-text search. This searches through all the text in each document found in the index. This finding is most people think of when thinking about the search capabilities of SharePoint.
Second, is the search feature. During the indexing process, the IFilters to extract the text of the documents, put the information into segments that particular property ownership are held separately in the index so it can be searched separately. This allows you to set the properties of their Office documents, such as department, project number, author, keywords, etc, and then have the ability to search individual fields.



You can use the SharePoint search engine to search for documents in the engineering department and the project is 123. When a document search full-text engineering and 123 tickets are hundreds of words for engineering and 123 series appears in many documents, a search through the properties can give 10 or so documents that are actually relevant to your search.

Office Does a Slight of Hand

During the editing process, however, the Office is a slight bit of hand. We take the information you enter in the metadata fields of the document library and makes custom properties for the document. The net effect is that although only created the fields in a document library, documents now have custom properties.
These custom properties are picked up by the indexing process (specifically, the IFilter for Office documents) and placed in the search index. You can then use the properties of the provision through the advanced search page in SharePoint.But this also means that Office documents do not share the same relationship between the fields of the document library and the properties of each document. So if you're trying to develop a document search mechanism, such as TIF or PDF documents, you will find that the creation of a metadata field for the document libraries will not let you search for those documents directly through their properties. You will still be able to organize information

Extranet Double Authentication

GE-old problem that still exists today in SharePoint, is the double message authentication when trying to open an Office document that appears continuously (note: this is when working with a document more. In reading does not require authentication only, and do not interact with the document). This happens because of the nature of passing a logon token from the user's session to mount. Meaning, when you open an Office application, you can not lead to the web session in the client session (and the session is the appropriate user ID) because the session ID is considered new, SharePoint will try to verify user identity again. Ultimately, it would be great if the identity of Windows you are using SharePoint would persist through this border, however, is not in the cards now. The first mechanism is to move WSS v3 has an option that is available called "Extranet Mode". Extranet so disable all interface features that could cause the message to pass, but becomes part of the best document management features such as WebDAV dependent (Explorer View) and ActiveX (Upload multiple documents). The other option is to use forms-based authentication with persistent cookies. In general, writing a cookie to the client browser has mixed feelings about whether this is a viable security practice or not, but ASP.NET 2.0 Cookies are by default considered tamper-proof and encrypted .



I've read that many companies offer some type of application optimizers or whatever, anyway I'm not for a COTS solution since most customers will nix anyway, I think the fear OOB security solution when the code is not da. I know you can use ISA to solve it, but I've only seen one other solutions to this which solved my fine things in an extranet scenario. ISA tends to be a problem and for some organizations because, although not built in mechanisms that will help secure the release of a web server, it requires additional hardware, requires knowledge of ISA, an architect for the construction of an instance of ISA, and a person with the ISA manager (for things like connectivity verifiers and link the tasks of translation).



So they tend to lean toward a VC + + ISAPI filter (could accomplish the same thing with XMLHTTP ActiveX or I'm not sure.) To intercept the requests as are pipes in SharePoint as an ISAPI filter will be able to inject any more times during the life of a user request. Generally, you can customize the ISAPI filter to build the same type of persistent cookie with FBA offered with Windows authentication schemes such as basic or integrated authentication through an extranet. This would be quite easy to build as the ISAPI filter can intercept HTTP requests as the last user if the cookie does not exist create a new cookie with a session and GUID if the cookie exists extract the GUID cookie and finally passed all this information by the extensive use of the head of the streaming application for approval of IIS.



Although I am 100% sure this route works well, the writing unmanaged code is not particularly lucrative several options because most people (like me) have been spoiled by the existence of so long. Only wants to go again in unmanaged really do not like (even with the help of being able to build an ISAPI filter Skelton.
To write an ISAPI filter for SharePoint, you will have to investigate the construction of at least two entry points GetFilterVersion and HttpFilterProc. GetFilterVersion is the main entry point for the ISAPI filter structure HTTP_FILTER_VERSION taking as a parameter, which will determine the website to request notifications encountered by the ISAPI filter, or is to preprocess headers (as in the example below ) and priority flags that should be related. Basically, what tells the filter to listen, and the creation of an initial call for the first time.

Restore Individual File Items in Microsoft SharePoint Using NetBackup

Microsoft SharePoint has become increasingly popular and powerful tool for business collaboration. While the main impetus behind the adoption of SharePoint is very easy file sharing and collaborative editing of documents, using group calendar, common lists, and track events have become increasingly important for business users. Common methods to restore SharePoint data do not permit the restoration of individual files, only one data set of complete restoration. As a result, SharePoint users need a solution to protect and restore individual files, calendar items, discussion threads, and lists. This explains how to use TechTip Symantec NetBackup files to backup SharePoint data so that individual file restores are now possible.
The system requirements to perform individual SharePoint file restores are:

• Symantec NetBackup 6.5.4
• The entire disk image-based backup SharePoint data
• NFS Client enabled on the SharePoint SQL server and all servers that will be supported
• The NFS protocol must be enabled on the media server NBU (port mapper service)
• Backup data can not be compressed or encrypted

Only NetBackup version 6.5.4 or high is subject of various item restores; upgrade to this version to add this important SharePoint functionality.
Once you have upgraded to version 6.5.4, perform a full backup SharePoint data in a resource-based disk. The backup must be a full backup of a single item restores can only be made in full copies NetBackup SharePoint data.
In addition, the backup must reside on disk, tape, optical or removable media are not supported for individual file restores. If your organization regularly protects your data files or SharePoint on removable media, you can easily configure NetBackup to make additional copies to removable media, or copy a disk-based backup on removable media.
To maintain this ability to restore individual files to the SharePoint data, it is recommended that your organization conducts disk-based full image copies on a regular basis. Obviously, the granularity of restoration capabilities depends on the frequency of disk-based full backups.
To restore a single element of SharePoint, NetBackup restore using the GUI to navigate the appropriate SharePoint directory. Tag the individual item or items you want to restore. Restore Select '. You have two options to restore the file (s):

• Restore the file to the current location will overwrite the existing file in the directory of SharePoint. Use with caution, usually when the existing file is corrupted or has been accidentally deleted.
• Restore the file with a new name to preserve your existing data file, but add the restored data to be loaded into SharePoint.

By improving the granularity of your SharePoint recovery capacities, NetBackup can save valuable maintenance and management of time and add greater protection to user data in SharePoint.

Relationship between Windows SharePoint Services and SharePoint Portal Server 2003

Microsoft SharePoint Products and Technologies alleviate collaboration within an system and with partners and clients. Using the combined collaboration features of Windows SharePoint Services and SharePoint Portal Server 2003, users in your system can easy make, manage, and make their own collaborative Web sites and make them available throughout the organization. Microsoft SharePoint Products and Technologies alleviate collaboration within an organization and with partners and clients. Using the combined collaboration features of Windows SharePoint Services and SharePoint Portal Server 2003, users in your system can easy create, manage, and make their own collaborative Web sites and make them available throughout the organization. Windows SharePoint Services is a collection of services for Microsoft Windows Server 2003 that you can use to share data, collaborate with other users on documents, and create lists and Web Part pages. You can also use Windows SharePoint Services as a development platform for making collaboration and information-sharing applications. SharePoint Portal Server 2003 is a secure, scalable, enterprise portal server built upon Windows SharePoint Services that you can use to aggregate SharePoint sites, information, and applications in your organization into a single, easy-to-use portal. In addition to the features of Windows SharePoint Services, SharePoint Portal Server 2003 includes the following features:

• News and Issues
• My Site, with personal views and public
• Information targeted to specific
• The indexing and powerful search through file shares, Web servers, secure Web servers, Exchange public folders, Lotus Notes and SharePoint sites
• Alerts that notify you when changes are made to relevant information, documents, or applications
• Single sign for enterprise application integration
• Integration with Microsoft BizTalk Server

Because SharePoint Portal Server 2003 requires Windows SharePoint Services, all features of Windows SharePoint Services are available in SharePoint Portal Server 2003.

Customizing SharePoint

One of the most popular personalization systems SharePoint have is how to manage the process of implementing the code. Organizations usually have guidelines for configuration management that help them regulate how code makes it into the product if that is the internally developed code or patches are used for the operating system and products being leveraged.
The problem is that SharePoint does not fit a model very clean. Because much of SharePoint is the configuration and data driven, code that works on the development or test environment may not work in Prod because things are configured differently or there are different data to operate.
So how do handle a situation where you have the configuration data needed to comply with the code to create a complete solution? In this article I will address this problem, a generic approach, and discuss some of the edges of strategy will have to educate everyone.
In order to facilitate a discussion, let's assume that we have three formal environments:
Development - a systems integration environment where developers have approach to servers and administrative controls. Some systems call this environment the "Wild West" because it is only slightly in configuration management. This actually a systems integration environment where all code is special to live together with test data before going further.
Quality Assurance (QA) / Test - The Quality Assurance (QA) or test environment is where the development code and content or a subset of the contents of the production comes together. This is where final signoffs received before going into production. There may be multiple quality control environments in an organization, but for our purposes can be considered once and we all live in the same space of configuration management. This environment is generally well controlled and follows a process of change management - but usually with less strong commitment to the production environment.
Production The production environment is strictly controlled in the tightest restrictions on access and where the availability, reliability and scalability are of paramount importance. This is the final resting place for the code and at least in some environments is the origin of any content.
It is certainly possible environments or have a more involved, however, this simple example will make it better to talk about the concepts. The assumption that is not listed as a good environment in the former is that developers will have their own local environment that have not been formalized. Its initial development work will take place on their local machines or dedicated development machines - not the development environment.

What is SharePoint

SharePoint is an initiative information portal site, from Microsoft, that can be corporate to run Intranet, Extranet and Net sites. Microsoft Office SharePoint Server 2007 provides people, teams and expertise to connect and collaborate. A SharePoint enterprise portal is composed of both SharePoint Portal and Windows SharePoint Services, with SharePoint being made upon WSS. WSS is typically used by little teams, projects and companies. SharePoint Server is designed for individuals, teams and projects within a average to large company wide enterprise portal.

SharePoint facts

• SharePoint is the fastest growing product in Microsoft history
• Over 100 million licenses of SharePoint have been sold worldwide
• SharePoint has been adopted by more than 17,000 companies worldwide
• SharePoint is listed, by Forrester, as the number 1 portal product
• SharePoint is positioned as a leader in Gartner's Magic Quadrant for Horizontal Portals products
• In SharePoint 2008 sales exceeded 1 billion U.S. $

Why should we use SharePoint?

• As companies grow so does the amount of your files. It soon becomes difficult to keep track of the documents of multiplication and their locations. SharePoint overcomes this by allowing you to store and share your files on a central site.
• job sharing files through email is a cumbersome process. SharePoint eliminates this by allowing files to be stored in one place, allowing easy access to all team members.
• Business Intelligence has traditionally remained in the hands of a few key decision makers in organizations. Over the years, has been the target of the BI vendors to "democratize business intelligence, by making it available to all levels of employees in enterprises. With the addition of PerformancePoint to the Enterprise version of SharePoint SharePoint, this vision is realized, finally taking business intelligence of a few hands and the hands of many.
• Today's work occurs in multiple locations, either in different countries, offices, separate or home office. SharePoint enables teams and individuals to connect and collaborate together regardless of where they are.
• Studies have shown that employees can take up to 20 to 30% of their time looking for data and information. SharePoint eliminates this drag on productivity by providing powerful search functionality to find the necessary information and

Windows SharePoint Services

Windows SharePoint Services allows teams to generate Websites for information sharing & document collaboration, benefits that help increase individual & team productivity. Windows SharePoint Services is a component of the Windows Server 2003 information worker infrastructure & provides team services & sites to Microsoft Office Process & other desktop programs. It also serves as a platform for application development. Including such IT resources as portals, team workspaces, e-mail, presence awareness, & Web-based conferencing, Windows SharePoint Services enables users to locate distributed information quickly & efficiently, as well as connect to & work with others more productively.

How Windows SharePoint Services Works

Windows SharePoint Services allows teams to generate Websites for information sharing & document collaboration, benefits that help increase individual & team productivity. Windows SharePoint Services is a component of the Windows Server 2003 information worker infrastructure & provides team services & sites to Microsoft Office Process & other desktop programs. It also serves as a platform for application development. Including such IT resources as portals, team workspaces, e-mail, presence awareness, & Web-based conferencing, Windows SharePoint Services enables users to locate distributed information quickly & efficiently, as well as connect to & work with others more productively.

Individual Empowerment

Microsoft Office Technique programs use SharePoint site content. All of a site's collaborative content—for example, documents, lists, events, task assignments, & membership rosters—can be read & edited within Microsoft Office Word 2003, Microsoft Office Excel 2003, & Microsoft Office PowerPoint 2003. Picture editing of Web-based photo libraries is also possible. Microsoft Office Outlook 2003 allows SharePoint site event calendars to be viewed side-by-side with personal calendars, & it also creates meeting-specific workspaces to augment group appointments.
SharePoint site members can find & communicate with key contacts & experts, both by e-mail & with instant messaging. Site content can be easily searched, & users can also get alerts to tell them when existing documents & information have been changed, or when new information or documents have been added. Site content & layout can be personalized on a per-user basis, & Web Parts can be used to present targeted information to specific users on precise topics.

Administration and Deployment

Windows SharePoint Services can scale to thousands of websites within an system. It fully supports load-balanced Web farm and clustered database deployments. For website and server managers, quotas can be set and applied not only on memory, but on sites per-server and users per-site. Site usage can be monitored to detect and retire |still sites. Detailed security options are available and easily managed. Server managers can delegate to end users the ability to create their own sites. Sites and servers can be managed from a Web browser, command-line tools, or a Web service-accessible object model.

SharePoint Installation

The Windows environment is recommended that offers the best performance for SharePoint is available 64-bit servers. This environment offers a much larger address space than 32-bit one, more space for combinations of SharePoint, the CLR / Native APIs, network stack, IIS / ASP.NET and other components housed in their respective levels.

Windows Server 2008 and SQL Server

SharePoint installed on Windows Server 2003 and 2008. The recommendation is to use Windows 2008 because it has the outermost security. For Windows 2008 you need to activate the following functions: Web Server role and Microsoft. NET Framework 3.5.
Note that Windows 2008 Web Edition is not compatible with the duties of the farm, except for the WFE boxes, due to restrictions of the Web editions of SQL Server on Windows 2008 Web Edition. The release of SQL Server 2008 Web Edition "extends the use of Windows 2008 Web Edition for SharePoint.
Do not install SharePoint on the domain controller box in a virtualized environment. Role Windows 2008 DC limited hard disk performance by disabling caching to provide consistency AD. DC virtualized facilities may not operate properly.
The installation of SharePoint support SQL 2005 and 2008 Servers (including SQL Server 2000 is compatible but not much more advantage from its use). SQL Exress Edition is also supported, but for basic MOSS installation, but the basic installation of WSS 3.0 uses the internal database of Windows (MED has no size limitation). SharePoint installed only on SQL Server, but you can use content from BDC use 3 databases of third parties.
Some advantages of SQL Server 2008 SQL Server 2005 are running, encryption, clustering, reflecting, etc. In addition, updates the SharePoint Web parts for Reporting Services and KPI.

Install Microsoft Office 2007 on farm premises

Office 2007 is not necessary in the SharePoint server, but it would be good to have somewhere that the farm buildings (non-server box) for managers, especially when they outsource their support and / or administrators to connect remotely. In this case, you may need client applications installed somewhere to access

• Word and Excel documents to document library
• The PowerPoint slides for the document library
• Access to "Edit in Datasheet" support in the Document Library

Consider the same for Office SharePoint Designer (SPD), which is needed for purposes of personalization. (SPD is a free product to be distributed as a separate product that is not included in Office)

Install SharePoint

Installing SharePoint on all servers in the farm. Start with WSS / MOSS wake package (integrated with the latest service pack) instead of using basic WSS / MOSS installation and implementation of later service pack.

• Application Server in the Central Administration site will be held
• All front-end Web servers
• The index server (if using a separate server for search queries and indexing)
• Query servers, when separated from the WFE servers
• Other application servers (optional)

Consider using scripts to automate installation and configuration of SharePoint deployment of large farms. SharePoint provides several configuration files and console commands that do all the deployment-wizard. This will speed up the installation and provides consistency in the construction and reconstruction of the servers in the farm.
There are three commands to automate the installation of SharePoint:

• SharePoint Setup.exe + config.xml - the script configuration questions
• Psconfig.exe - Assistant configuration script
• STSADM.EXE - the instrument Central Admin UI to create web applications and site collections

Alternative energy use is preconfigured and shell scripts. "Deploying SharePoint" tool on CodePlex provides scripts to set the standard installation, which can be adapted to any environment.

Install SharePoint updates

Install all SharePoint updates (Infrastructure Updates and/or |Extra Patches) ater grow is deployed. Find the free notes of the latest |extra patch if it accepts all previous patches and updates. Sometimes you need to install other updates manually. Cumulative patch releases each 2 months. Follow the regular documentation “Deploy software updates for Office SharePoint Server 2007” for the processes of how to deploy substructure update (WSS Upgrade needs to be installed first and only then MOSS upgrade).



There are several hot solutions, such as "Coreserver.msp" package, which are released after cumulative patch. However, be careful with these arrangements because they are temporary solution before the next official update, and are subject to tests. Installing fixes for specific problems.

SharePoint design

There are some tools that my son's hand. He is five years and frankly there is no reason why they do not want to work with chain saws. Occasionally we need a chainsaw to cut a tree or cut a fallen branch. But it is a tool that asked him to use.
I feel the same about SharePoint Designer (SPD) - in the hands of and under the right circumstances, can be a powerful tool that can save organizations money. However, in the hands of others, can be a bad influence that makes it more difficult for organizations that are well governed and that the system uses.
In this article we will walk through a high level summary of characteristics of the SPD and how these features should and should not be used. At the end of this article should be able to identify situations that may be useful SPD and identify situations where the use of SPD may be more a hindrance than a help.

HTML Design

Within the context of SharePoint how does this help? SharePoint is made on top of the ASP.NET 2.0 framework and accepts both a maser pages and web form pages. Master pages offer a way to make a consistent look and feel across the site. The individual web pages allow for various layouts and structures to support the needs of the content. SPD is a capable editor of both of these three core file types in SharePoint.

Perhaps the most obvious feature of SPD is seen from the position of its Front Page inheritance. Even the product's predecessors were HTML designers. They were designed to make the performance of editing HTML more usable for the masses. Over the years the tools have "grown up" to include professional-quality editing support. While there's competing products in the HTML editing space, SPD (and its sibling, Expression Web) has a solid set of tools for editing HTML.

When you are using Microsoft Office SharePoint Server (MOSS) there is a terminology modify to be aware of. MOSS includes a feature called web content management (WCM). In this feature, there's page layouts to consider. These page layouts are the templates that content is put in. They are -- in essence -- the same web form pages that you might edit directly. The key difference is that they contain content placeholders in to which content will be inserted by the WCM subsystem. So pages in Windows SharePoint Services (WSS) -- & non WCM MOSS sites -- are essentially the same as Page Layouts for WCM.

In addition to HTML editing, web-site design today is controlled by cascading style sheets (CSS). SPD is a lovely editor of CSS sheets as well. In the SharePoint world CSS is important because much of what is displayed is styled with CSS sheets. A great deal of customization of the look & feel can be done without ever editing a master page or a page itself.

From the perspective of working with SharePoint, SPD's key feature is probably its direct integration with SharePoint. It understands the APIs & what to do in order to get pages & content & how to return them safely to SharePoint. In this integration, there's, however, some hidden concerns.

Site Collections and Sites

Some of you may be aware that there is a distinction within SharePoint from a normal site, which a developer is more apt to call SPWeb, and a collection of sites, which a developer is able to call SPSite. The difference is that a site collection is an object of limits. It defines the boundaries of different APIs and also storage. A site collection can only be stored in a database of content. A site collection is the limit for many APIs - for example, quotas, content consulting, etc.

MS SharePoint Server

SharePoint is an initiative information portal, from Microsoft, that can be |corporate to run Intranet, Extranet and Internet sites. Microsoft Office SharePoint Server 2007 allows people, teams and expertise to join and collaborate. A SharePoint enterprise portal is published of both SharePoint Portal and Windows SharePoint Services, with SharePoint being built upon WSS. WSS is typically used by small teams, projects and companies. SharePoint Server is designed for individuals, teams and projects within a medium to large company wide enterprise portal.

Some SharePoint facts

• SharePoint is the fastest-growing product in the history of Microsoft
• Over 100 million licenses of SharePoint have been sold worldwide
• SharePoint has been adopted by over 17,000 companies worldwide
• SharePoint is listed, by Forrester, as the number 1 portal product
• SharePoint is positioned as a leader within the Gartner Magic Quadrant for Horizontal Portals products
• In 2008 sales of SharePoint surpassed 1 billion US dollars

Microsoft Office SharePoint Server 2007

The main parts of SharePoint are collaboration, portals, enterprise search, enterprise content management, business system & forms, & business intelligence. Previous variations of SharePoint Server included SharePoint Portal Server 2003 & before that SharePoint Portal Server 2001.
Microsoft Office SharePoint Server 2007 is a collaborative initiative portal that is built on WSS 3.0. MOSS 2007 allows people, teams & expertise to connect & collaborate. Unlike WSS, SharePoint Server is not free & requires an additional license. MOSS 2007 comes in two versions – Standard & Enterprise.

Windows SharePoint Services 3.0

Windows SharePoint Services 3.0 is the program on which all SharePoint Products and Technologies are made. WSS 3.0 is for is fit for small teams, projects and systems.
WSS’s project collaboration, document workspace, meeting sub-site, and discussion board features allow individuals and little teams to collaborate and part information online. Past versions of Windows SharePoint Services included Windows SharePoint Services 2.0 and SharePoint Team Services. New features in WSS 3.0 include integrated workflows, RSS feeds, blogs, wikis and ASP-style Web parts.

Active Directory & SharePoint

A new feature of Microsoft Windows SharePoint Services is account creation mode for Active Directory directory service. This feature replaces the local account creation feature in SharePoint Team Services 1.0 from Microsoft. Use Active Directory account creation mode when it is necessary to generate new user accounts than using existing domain accounts. For example, an Web service provider (ISP) might need the ability to permit SharePoint site owners the capability to generate user accounts or invite users to collaborate on a Website where existing domain accounts for those users do not already exist.

In order to run Windows SharePoint Services in Active Directory account creation mode, your Web servers must be members of a Microsoft Windows 2000 or Microsoft Windows Server 2003 domain.



To configure any way to perform the following tasks on the domain controller, SQL Server, and Web server in the order listed.

• To configure any way to perform the following tasks on the domain controller, SQL Server, and Web server in the order listed.
• Create an organizational unit (OU) for the user accounts.
• Delegate permissions to the organizational unit.

Prepare the Web server computers:

• Install Windows SharePoint Services with the option of the farm.
• Create the group's virtual server management applications.
• Create the configuration database and specify the creation of Active Directory account mode.
• For IIS traditional accommodation, use HTML Administration pages.
• For IIS scalable hosting, use the command line utility stsadm.exe.
• Specify the mail server settings.
• Extending a virtual server.
• Specify how to host the host name for the first site (scalable only).

The steps to prepare the domain controller and SQL Server is the same for either mode. The steps for the preparation of Web server computers differ slightly. When using scalable hosting mode make sure to use the parameter of HH (only available from the command line) to create the configuration database, which is covered in Configuring Windows SharePoint Services to hosting scalar mode.

Create a domain account for Windows SharePoint Services processes

• In the domain controller, create an account to be used by Windows SharePoint Services to create new domain accounts.
• For example, create a new account called SharePoint_admin.
• Configure the account so that the password not be changed at next logon and does not expire.
• If you are using Kerberos authentication and account security is not a network service, set up accounts as a service principal name (SPN).

Microsoft SharePoint Portal Technology

SharePoint is involved to help you understand the capabilities of the product, as well as offer tips and tricks, growth ideas, information from Microsoft, information from the community, and perhaps some samples.It will accept how-to articles that can help you with your deployments; ways to customize a page; deployment scenarios; and content management.
SharePoint Designer
The beginning point for most discussions about branding is SharePoint Designer. SharePoint Designer is the preeminent editor for SharePoint and can handle editing the master page, page layouts, and pages themselves. The master pages, ASP.NET Master Pages to be more specific are the master layout for the page. The content from a page layout which is used in web content management, or a page drops in to placeholders in the master page. Page layouts further contain content from the items they are associated with but otherwise are edited the same way that regular pages are.
Certainly that is not a bad capabilities list. There's some pages that SharePoint Designer cannot alter. It cannot alter any of the "application" pages. Those are the pages that exist in the _layouts directory. This can be an issue because a quantity of the pages that users see -- such as upload file, and view all site content, come from this directory.
SharePoint Designer is as well as a great editor for Cascading Style Sheets (CSS) both from the context of editing your own CSS sheets in a site as well as for editing the CSS sheets that are essential to themes.
More From Jupitermedia
IDM Dreamweaver Tutorial
Why Ubuntu Linux Tops Debian
Generating a PHP-Based Content Management Process
Top Intranet Trends: Usability, Access, Personalization
The 2008 IT Salary Guide
If you need to comment on these or any other articles you see on Intranet Journal, we'd like to hear from you in our IT Management Forum. Thanks for reading.
FREE IT Management Newsletters
- Tom Dunlap, Managing Editor.
The challenge with SharePoint Designer is that the changes apply only to the site collection, site, and page that SharePoint Designer is editing. That is great if you need to customize the look of one site -- but what if you need the look and feel to apply to multiple sites?
Understanding the SharePoint, ASP.NET Relationship
Unless you have been living under a sizable rock you have probably heard about this thing called Microsoft SharePoint. & like Chicken Tiny, people in the SharePoint community are jogging around saying that the finish is coming.
While there is a great deal of power that SharePoint offers it doesn't mean that you won't be writing in ASP.NET (define) any longer -- the contrary, SharePoint is a well behaved ASP.NET 2.0 application itself -- at least in the Windows SharePoint Services 3.0/Microsoft Office SharePoint Server 2007 timeframe anyway. That being said, there's some differences when it comes to developing with SharePoint that the ASP.NET developer should be aware of. Here are a quantity of them:

Back up, restore, or move a SharePoint site

When you back up & restore a site, you actually perform two separate operations: First, you back up the site to a single file. Then you generate a new empty site as a location. Finally, you restore the backup site to that location.
Suppose that your team has posted their latest quarterly reports to various document libraries on the team site, & you need to back up the site at this critical juncture. Or suppose that your team has been moved to a different group in your organization, so you need to move your team site to another server. You can use Microsoft Office SharePoint Designer 2007 to generate a backup copy of a site or subsite, & then re-create that site on the same server or on another server.
There are three different features of the Web sites of packaging: In Office SharePoint Designer 2007, you can make backup copies of a site or create a Web package, and the browser that you can save a site as a site template. That the property you choose depends on what you want to achieve.
Web Package (FWP archivo.) Use this feature when you want to share or reuse Web pages or a site, list or structure of the library. With web packages, you may or package an entire site or select specific pages, lists or libraries you want. Web packages are a great way to duplicate site structure, but can not include list data, subsites, or security and permission settings. In addition, a Web package can include custom link bars. After creating a package, you can import and display the file in as many sites as you want. For more information on web packages, see Export or import a Web package.
Backup and Restore (. Cmp) Use this feature when you want to back up the entire site or subsite, or when you want to move an entire site or subsite to another server or location. Unlike Web packages, the content migration packages include list data, and you can choose to include only specific site elements. Note that you may lose some customizations or settings in the process. For example, the backup file does not include workflows, alerts, and properties stored at the site collection level. The backup file also includes the state of the Recycle Bin or the goods inside. To use Backup and Restore, you must have administrator permissions for that site.
Site Template (. Stp) Use this feature when you want to create multiple Web sites that begin with the same base content or site structure. For example, you may want to all subsites Creating a site to have a similar structure, the appearance, and even content. You can do this by saving a site as a site template and add it to the gallery web templates for anyone to use the site as a template. Unlike Web packages, site templates may include list data. You must have both administrative permission to the website where you want to create the site template and write access to a site template gallery. Find a link to more information about site templates in the See Also section.

How we move a SharePoint site from one location to another?

SharePoint sites are not actually moved from one location or server to another; , they are backed up to a file, & then the content or site is re-created from the backup file.
The Backup & Restore feature in Office SharePoint Designer 2007 is the best way to move an individual site or subsite from one server to another, but this method has limitations, as outlined earlier in this news story. However, if you are a server administrator, Microsoft Windows SharePoint Services includes a powerful command-line administration tool called Stsadm.exe. With this tool, you can back up or restore one site collection at a time, meaning one top-level site & all its subsites. However, you cannot use Stsadm.exe to back up an individual subsite, only the collection. For more information on using Stsadm.exe, see the "Windows SharePoint Services Administrator's Guide."

Back up a Web site

Backing up a Web-site creates a content migration package, or .cmp file. When you back up a Web-site, you can pick to back up either the top-level Web-site or the top-level Web-site and any subsites. The backup file that you generate includes list or library content, security settings, user information, navigation, customizations, and personalizations (such as views, site templates, and content types). The backup file does not include workflows, alerts, and properties stored at the site collection level.
To back up a site, you must have administrator permissions for that site, but you do not require administrative access to the server that is walking Windows SharePoint Services 3.0.
1. On the File menu, click Open Site.
2. In the Open Site dialog box, browse to and click the Web-site that you require to back up, and then click Open.
3. On the Site menu, point to Administration, and then click Backup Web Site.
4. In the Backup Web Site dialog box, to include all subsites of the current Web-site in the backup, select the Include subsites in archive check box.
5. If the current Web-site is low on obtainable storage space, click Advanced, enter a new location, and then click OK.
Backing up a Web-site requires a location to store temporary backup files. By default, Office SharePoint Designer 2007 uses the current Web-site. You can use another site on the same server or a location on another server on the same network — for example, \\Server name\Share name.
6. In the Backup Web Site dialog box, click OK.
7. In the File Save dialog box, select the location where you require to store  the .cmp file.
8. In the File name box, type the name for the file, and then click Save.
If the site that you are backing up or restoring is huge, the process can take a while.

Restore a Web site

Step 1: Create a new Web site as a destination

• On the File menu, click New.
• In the New dialog box, click the Web Site tab, click General, and then click Empty Web Site.
• In the Specify the location of the new Website box, enter the location where you require to restore the backup site.
• You can restore the site to a different server, and you can restore it as either a new top-level site or a subsite under an existing top-level site.
• Click OK.

Step 2: Restore the backup file to the destination

• In the destination site open, on the Site menu, select Administration and then click Restore Web Site.
• In the File Open dialog box, locate and click the CMP. File you want to restore, and then click Open.
• If the current site has little storage space available, click Advanced, and then do any of the following:

Content SharePoint

Regular readers may have seen that I have been a bit quieter than usual in recent weeks - in fact I have not slacking, but working on a tool that can be useful from time to time. As I discussed in numerous posts, the deployment of SharePoint artifacts is something that is perhaps more complex than it should be, and the standard tools provided do not always simplify this picture. Personally, over my past, few projects of minimum standards, there have been several times when I thought:

• I just need to move this document library from A to B
• I just need to move these selected files (eg home page, page layouts, CSS, etc.) from A to B
• I just need to move this web from A to B
• I just need to move this site collection from A to B
• I just need to move these items 20 List from A to B

If only one easy way! CMS 2002 users can recall the SDO export mechanism that has allowed to use a TreeView to select exactly the content they want to move, but unfortunately there is a similar tool for MOSS. Of course, we have distribution of content, etc. STSADM export, but the lowest level of granularity is a network, and do not want to rewrite the whole thing can not use the option. The only other option is to write code that uses the Content Migration API. This is fine for projects that are developing the right skills and time, but otherwise things can be difficult.
Enter the Deployment Wizard for SharePoint content.
The tool provides a wizard-like approach to deploying content between SharePoint sites. The selected content is exported using the Content Migration API (PRIME), giving a. CMP (Content Migration Package) which can be copied to other servers.