|
Planning for Upgrade from SP (SharePoint):-
Upgrade to SharePoint Foundation 2010 or SharePoint Server 2010, you must first be running Windows SharePoint Services 3.0 at SP2 or Microsoft Office SharePoint Server 2007 at SP2, respectively. For customers running prior versions of SharePoint, including Windows SharePoint Services 2.0 and SharePoint Portal Server 2007, this means that you must first upgrade to Windows SharePoint Services 3.0 SP2 or Microsoft Office SharePoint Server 2007 SP2 prior to upgrading to 2010 versions. Windows SharePoint Server 3.0 with SP2 is available as a free download, and trial versions of Microsoft Office SharePoint Server 2007 are available and supported for use in this upgrade/migration process:
SP2 Slipstream Downloads and Trial Versions: Windows SharePoint Services 3.0 (32-bit) with SP2
http://www.microsoft.com/downloads/details.aspx?FamilyId=EF93E453-75F1-45DF-8C6F-4565E8549C2A
Windows SharePoint Services 3.0 (64-bit) with SP2
http://www.microsoft.com/downloads/details.aspx?familyid=9FB41E51-CB03-4B47-B89A-396786492CBA
Microsoft Office SharePoint Server 2007 Trial Version (32-bit) with SP2
http://www.microsoft.com/downloads/details.aspx?FamilyId=2E6E5A9C-EBF6-4F7F-8467-F4DE6BD6B831
Microsoft Office SharePoint Server 2007 Trial Version (64-bit) with SP2
http://www.microsoft.com/downloads/details.aspx?familyid=3015FDE4-85F6-4CBC-812D-55701FBFB563
Please note that the trial product versions are licensed for 180 days of use from the date of installation.
Upgrade Method: This upgrade process should be done using the Database Migration approach documented in the following links: Windows SharePoint Services and Microsoft Office SharePoint Server 2007. Determine upgrade approach (Office SharePoint Server)
http://technet.microsoft.com/en-us/library/cc263447.aspx
Determine upgrade approach [Windows SharePoint Services]
http://technet.microsoft.com/en-us/library/cc287821.aspx
SharePoint Foundation 2010 and SharePoint Server 2010 (pre-release documentation)
Determine upgrade approach (SharePoint Server 2010)
http://technet.microsoft.com/en-us/library/cc263447(office.14).aspx
Determine upgrade approach (SharePoint Foundation 2010)
http://technet.microsoft.com/en-us/library/cc287821(office.14).aspx
Note that this method is referred to as “Database attach upgrade” in pre-release documentation
Please note that there are manual steps involved in this upgrade path in order to maintain some configuration information, as documented in the links above.
Example Upgrade Sequence : Upgrade documentation above should be referenced for full detail and information, but the following illustrates an example of an upgrade sequence for moving from Office SharePoint Server 2007 to SharePoint Server 2010.
1. Prepare Farms
*. Set up a small, temporary farm running Office SharePoint Server 2007
**. Set up full SharePoint 2010 farm and verify that it is configured and running correctly
2. Upgrade content from 2007 to 2010
*. Detach the content databases from the 2003 farm and take the 2003 farm offline
**. Attach the content databases to the 2007 farm and upgrade them
**. Verify the content has upgraded and that the 2007 farm is working correctly
3. Upgrade content from 2007 to 2010
*. Detach the content databases from the 2007 farm
**. Attach the content databases to the SharePoint Server 2010 farm and upgrade them in parallel
***. Verify the content has upgraded to SharePoint 2010 and is working correctly
4. Start serving requests on the SharePoint Server 2010 farm
Again, this is just an example for illustration: for full detail, including all steps and important considerations, please review the existing and pre-release documentation linked above. Information and Notes: Please note that SharePoint Server 2010 Beta cannot be upgraded to the final release version -RTM-. Any use of these steps or guidelines with any pre-release version of SharePoint 2010 should be for testing/evaluation only.
Upgrade path will necessarily mean a move from 32-bit OS architecture to 64-bit OS architecture. Windows SharePoint Services 2.0 and SharePoint Portal Server 2003 were supported only on 32-bit operating systems, as opposed to SharePoint Foundation 2010 and SharePoint Server 2010, which are supported only on 64-bit operating systems.
The database platform selected for Microsoft Office SharePoint Server 2007 or Windows SharePoint Services 3.0 should be consistent with the planned platform for Microsoft SharePoint Server 2010 or Microsoft SharePoint Foundation 2010. For example, if SQL Server 2008 will serve as the database software for the Microsoft Office SharePoint Server 2007 or Windows SharePoint Services 3.0 trial versions you should maintain that version for Microsoft SharePoint Server 2010 or Microsoft SharePoint Foundation 2010 to avoid downgrade support limitations such as SQL Server 2008 to SQL Server 2005. SQL Server 2008 downgrade & SQL Server 2008 Licensing :
http://www.microsoft.com/sqlserver/2008/en/us/licensing-faq.aspx
OS requirements of SharePoint 2010:-
Operating System: We’ve seen some confusion in the newsgroups and elsewhere on the versions and editions of Windows that SharePoint 2010 will run on. This post is meant to clarify some of the most common questions we have seen.
SharePoint 2010 will support only 64-bit (x64) versions of Windows Server 2008 SP2 and Windows Server 2008 R2. SharePoint will not install at all on 32 bit Windows, or any earlier version of Windows such as Windows Server 2000 or Windows Server 2003.
SharePoint is not supported on ‘Server Core’ installations of Windows Server 2008 and R2. The Server Core installations of Windows server do not contain some of the components required for SharePoint to be configured or run.
To make developing for SharePoint 2010 easier, it is possible to install SharePoint on 64-bit versions of Windows Vista SP2 and Windows 7. Note that running production environments on these OSes are not supported and it will not be possible to upgrade deployments running on client versions of Windows to future versions of SharePoint. Instructions on installing SharePoint 2010 on client versions of Windows are a bit more involved and we recommend reading the instructions at http://msdn.microsoft.com/en-us/library/ee554869(office.14).aspx
| Windows version/edition (64 bit only) |
SharePoint 2010 support |
| Windows Server 2008 R2 Foundation |
No |
| Windows Server 2008 R2 Standard |
Yes |
| Windows Server 2008 R2 Enterprise |
Yes |
| Windows Server 2008 R2 Datacenter |
Yes |
| Windows Web Server 2008 R2 |
No |
| Windows HPC Server 2008 |
No |
| Windows Server 2008 R2 for Itanium-based systems |
No |
| Windows Server 2008 Standard |
Yes |
| Windows Server 2008 Enterprise |
Yes |
| Windows Server 2008 Datacenter |
Yes |
| Windows Web Server 2008 |
No |
| Windows Storage Server 2008 |
No |
| Windows Small Business Server 2008 |
Yes 2 |
| Windows Essential Business Server 2008 |
Yes 2 |
| Windows Server 2008 for Itanium-based systems |
No |
| Windows Server 2008 Foundation |
No |
| Windows Vista |
Developer-only 1 |
| Windows 7 |
Developer-only 1 |
2 Small and Essential Business Server editions of Windows install SharePoint as an optional component.
1 Support for specific editions of Windows 7 / Vista are yet to be finalized, but are likely to be ‘Business’/'Professional’ editions and above.
SharePoint usage and monitoring:-
A always issue with SharePoint is that administrator have little or have no idea how it is being used. SharePoint does however provide several tools for monitoring usage and capturing and reporting errors. Both WSS and MOSS provide comprehensive site usage reports which are available at all the levels of the server farm from the SSP to each individual SharePoint site.
Before admins can review site usage reports, site usage reporting must be enabled for the server farm. Usage reporting occurs in two separate steps:
1.Web servers log site activity to the usage analysis logs.
2.SharePoint analyses the usage by reading logs from all servers in the farm and saves the data to a content database.
SharePoint usage analysis processing is a scheduled job which runs every 24 hours and as s a result, it is not possible to have live usage reports.
Note that you do not have to use the usage reporting that ships with SharePoint, several third-party tools exist to analyze SharePoint’s usage analysis logs.
The below steps will enable site usage reporting on WSS:
1.Navigate to the Operations page on the Central Administration site.
2.Click Usage Analysis Processing in the Logging and Reporting section and the Usage Analysis Processing screen will then appear.
3.Select Enable Logging .
4.Input the number of log files to create, note that SharePoint can a maximum of 30 days of log files.
5.Select Enable Usage Analysis Processing .
6.Enter the time of day to run the usage processing, it is not possible to control the exact time processing starts – the job is simply submitted during the specified time frame.
7.Click OK.
For SSP minimal usage reporting is enabled by default. Advanced reporting must be manually enabled if you wish to view more detailed information, such as search query results. Follow the below steps to to enable advanced usage reporting:
1.Navigate to the SharePoint Shared Services Administration site.
2.Select Usage Reporting in the Office SharePoint Usage Reporting section and the Configure Advanced Usage Analysis Processing page will appear.
3.Select Enable Advanced Usage Analysis Processing .
4.Select Enable Search Query Logging - Query logging is enabled by default.
5.Click OK to complete.
Before you are able to view usage reports for a site collection, you will need to enable the Reports feature in that site collection. To do this follow the below steps on every site collection that you wish to view the site usage reports on (note that this feature is only available in MOSS 2007):
1.Navigate to the top-level site in your site collection.
2.Navigate to the Site Settings page.
3.Select Site Actions > Site Settings > Modify All Site Settings in a MOSS publishing site. Select Site Actions > Site Settings in a team site.
4.Select Site Collection Features in the Site Collection Administration section.
5.Click Activate for the Reporting feature.
Note that it takes 24 hours to process usage data so expect a delay in being able to view usage reports.
Master Pages in SharePoint:-
Master pages are reusable page templates which use a combination of ASP.NET controls and HTML markup. Once a user creates a new Publishing page, that page’s look and feel derives from a master page; the content to be displayed the content’s layout comes from the page layout; and the content itself comes from the Publishing page instance which is created by the author. Thus, master pages, page layouts, and page instances create a hierarchical page model which separates the presentation from the content. Master pages and page layouts are kept in a dedicated document library called the Master Page gallery. Each site collection has a single Master Page gallery for its entire site collection which can be accessed from the top-level site’s Site Settings page.
A master page can be created from scratch or copied from an existing page and then edited. Initially it would be most convenient to copy and edit an existing master page. You will normally use a visual design tool, such as SharePoint Designer or Visual Studio , to edit and create master pages (note that you can download a free version of Visual Studio – Visual Web Developer from http://msdn.microsoft.com/vstudio/express/vwd).Masterpage file names must end with the file extension .master.
There are currently nine master pages in the Master Page gallery. Since the Master Page gallery is a document library, you may check out or upload a master page in the same manner you woulda Word document or any other file.
When a master page is opened, you see text that is actually a of HTML and ASP.NET , and importantly contains a series of ASP.NET placeholders. These placeholders are used to display the elements which will be displayed on every page which inherits from the master page, these elements will typically be page features such as navigation, search, or the footer. The content from the page layout is populated in the PlaceHolderMain. The code looks like this:
<asp:ContentPlaceHolder id=”PlaceHolderMain” runat=”server” />
Master pages normally link to Cascading Style Sheets (CSS) files, which defines the styles used to control the look and feel of the page. The CSS files which are used with master pages are stored in the Style library at the top-level site of a site collection. Master Pages are a an ASP.NET technology and so for a detailed tutorial of how master pages work and how to use them please see Master Pages – A Beginners Guide
To easily change the look of a page it is a simple process to change the master page associated with a site. Of the nine master pages included in MOSS 2007, all except BlueVertical.master and BlackVertical.master will work for internal SharePoint sites, these two master pages should only be used with Internet-facing sites.
To change the master page associated with a site, do the following:
1.Navigate to the Site Settings page for the relevant site.
2.Select Master Page in the Look and Feel section, and the Site Master Page Settings page will appear.
3.Under Site Master Page, select the master page to be used for all the Publishing pages in the site.
4.Under System Master Page , select the master page to be used for all the forms and view pages in the site.
5.For the Alternate CSS URL, select whether the site should use the default or custom CSS settings.
6.Click OK and the process is complete, and master pages are applied to the site.
If you use different master pages for Publishing and System pages, you can maintain one look for the Publishing pages while keeping the classic SharePoint look for default SharePoint pages like document libraries.
WSS supports using themes for changing the appearance of a site. Themes will change the fonts and color scheme used by a site without affecting the site’s layout. Follow the below steps to change the theme of a site:
1.Navigate to the Site Settings page for the site you wish to change the theme for.
2.Select Site Theme in the Look and Feel section, and The Site Theme page will appear.
3.Select the required theme from the theme listing.
4.SharePoint will then display a preview of the selected theme.
5.Click Apply, and that site’s fonts and colors are updated.
Themes do not have an inheritance hierarchy like master pages do. As a consequence, you will have to set the theme for every site in a site collection if you wish them all to have the same theme.
What is difference between WSS 3.0 and MOSS 2007:-
SharePoint is one of the buzzwords that are used almost in every office. When a newbie enters in the world of the SharePoint technologies, one of the first questions is: “What is the difference between the available distributions?” Generally there are two main distributions: Windows SharePoint Services 3.0 (WSS) and Microsoft Office SharePoint Server 2007 (MOSS). This article compares the WSS 3.0 and MOSS 2007 and outlines the differences between them.
The long story short: WSS comes as a free download if you have Windows Server 2003 or 2008. MOSS is build on top of WSS and must be purchased separately. Depending on the version (Standard, Enterprise, etc.) the license can be a significant financial investment. For details about difference licensing scenarios, you should contact your local Microsoft representative, because the licensing can vary if your server serves internet users or only intranet requests. Bellow I will summarize some of the most important features of both distributions.
Features of WSS: WSS is a collaboration platform, primary used for sharing and managing information and documents via a web site. The following are the most essential features:
*Site provisioning – WSS acts as a site provisioning engine that simplifies the process of creating new web sites.
*Document management – WSS provides support for document checkout before editing, the ability to view revisions to documents and restore to previous versions.
*Web Parts Infrastructure – web parts are special controls which can be added to certain areas of a web page (Web Part Zones). These controls enable end users to modify the content, appearance, and behavior of Web pages directly from a browser.
*Integration with Word, Excel, Access, Outlook - users can directly open a document from the server, without the need to download it first.
*Wikis, Blogs – wikis are supported as a site template, which allows you to create new pages quickly and easily, provides automatic linking and WYSIWYG editor. Blogs are supported as a site template as well, which provides features for article posting, reader comments and RSS feeds.
*Email integration – document libraries, discussion boards, calendars, and announcements can be configured to send emails upon new postings.
*Limited search support – WSS is is limited to showing results from the site and all of its subsites.
*Basic workflows support – you can create workflows, but you will need external tools like Visual Studio to do so. WSS is just a container that executes your workflow.
*Mobile devices support – the information is rendered using simplified text format.
*Server Farm – if you need high scalability, you can install WSS in a server farm mode which means that several machines will run the stateless presentation layer and all of them will be connected to the same SQL Server database.
Features of MOSS: MOSS installs on top of the WSS and extends the provided features. The major additions are :
*My Site personal site – each user has a site where the user can control the public and private content. It provides other users with the ability to learn about the user and the user’s areas of expertise, current projects, and colleague relationships. ‘My site’ acts as a central location to view and manage all of a user’s documents, tasks, links, calendar, etc.
*Extended workflow support – some existing workflow templates come with MOSS. If you want, you can create your own with tools like SharePoint Designer or Visual Studio.
*Site Directory – MOSS automatically creates a site map and presents it in an easy-to-use format.
*Business intelligence – MOSS provides support for business intelligence dashboards, Key Performance Indicators (KPI), Business Data Catalog (BDC), etc. BDC integrates external data into MOSS.
*Search – MOSS overcomes the limitation of WSS to search only within the current site and its subsites. You may search over file shares, web sites, etc.
*Enterprise Content Management – approval workflow allows web content to be sent for approval prior to publishing. Content deployment to production sites can be scheduled by setting up jobs.
*Audience targeting – the content inside lists, libraries, web parts, etc can be targeted to appear only to users who are members of a particular group or audience. The audiences can be identified via SharePoint groups, Distribution lists and Security groups.
*Excel Services – allows you to publish excel files so the user can view them in web page without the need of Microsoft Office Excel installed on his machine. You can control what part of the excel file to be visible and which part can be editable.
*InfoPath Forms – allows you to design forms in Microsoft Office InfoPath and distribute them via MOSS. Users will fill the form in the web browser without downloading the form.
The MOSS is distributed in several editions: Office SharePoint Server 2007 for Search, Office SharePoint Server 2007 Standard and Office SharePoint Server 2007 Enterprise. Logically not all of the features above are present in each version. More information about different MOSS versions can be found in the SharePoint Products Comparison.xls.
SharePoint Server 2010.
11 modules to help you learn what Microsoft SharePoint Server 2010 VideoTutorial.
1. This module introduces Microsoft SharePoint Server 2010 capabilities to IT professionals. Concepts covered include document sharing, lists, alerts, team sites, metadata, and more. From Ross SharePoint MVP.
2. SharePoint Server 2010 module (2 of 11) covers software and hardware requirements, and the basic concepts of Microsoft SharePoint Server 2010. How SharePoint Server 2010 Works from Drisgill, SharePoint MVP.
3. SharePoint Server 2010 module (3 of 11), we cover the process of using Microsoft SharePoint Server 2010 to create a single server environment for testing. Klindt, from SharePoint MVP-
4. Search in SharePoint Server 2010. SharePoint Server 2010 module (4 of 11), we help you learn about the search capabilities in Microsoft SharePoint Server 2010. Learn which content sources you can crawl to create an index, how to schedule crawls, and find out about IFilters for third-party file types. Ross from SharePoint MVP.
5. Backups in SharePoint Server 2010. SharePoint Server 2010 module (5 of 11), we cover new backup features in Microsoft SharePoint Server 2010. Learn how to back up your content not only by using the user interface, but also by using Windows PowerShell. You will also learn how to restore content from an unattached database.
6. Creating Your First Web Application, Site Collection and Web Site. SharePoint Server 2010 module (6 of 11), we help you create the first site on a SharePoint farm by using Microsoft SharePoint Server 2010. Learn how to create Web applications, site collections, and Web sites.
7. Security in SharePoint Server 2010. SharePoint Server 2010 module (7 of 11), learn how to give users permissions to the content, as well as who can access Central Administration and manage the service applications.
8. Windows PowerShell for SharePoint Server 2010 Administrators. SharePoint Server 2010 module (8 of 11), we cover Windows PowerShell basics and how administrators can manage Microsoft SharePoint Server 2010 by using cmdlets.
9. Tools to Optimize the Performance of SharePoint Server 2010. SharePoint Server 2010 module (9 of 11), we cover performance-related tools to manage resources, troubleshoot problems, and increase performance in Microsoft SharePoint Server 2010.
10. Introduction to Upgrade in SharePoint Server 2010. SharePoint Server 2010 module (10 of 11), we take a look at the upgrade process and options available to go from Microsoft Office SharePoint Server 2007 to SharePoint Server 2010.
11. Service Applications and Topologies in SharePoint Server 2010. SharePoint Server 2010 module (11 of 11), we explore how SharePoint 2010 provides services in a flexible and scalable architecture. Service applications are not just for SharePoint Server; SharePoint Foundation has the architecture as well.
If you can't able to download, so let me know that i have all those and advanced IT pro traning vedio.
Sharepoint Feb 2010:
Update februari 2010 för WSS 3.0 och MOSS 2007 finns nu att ladda hem.
Innan du installerar denna uppdatering så är det högst rekommenderat att installera Service Pack 2 först om detta redan inte är utfört.
SharePoint 2007/WSS 3.0 administrations- och migreringsverktyg från Xavor.
Dessa verktyg som är helt gratis ger dig som SharePoint administratör ytterligare stöd för att hantera behörigheterna mm i din SharePoint 2007 miljö samt migrera innehåll.
-
Xavor SharePoint Migration Tool
- Drag-n-drop stöd
- Migrera webbplatser, listor, webbdelar och behörigheter
- Uppdatering av URL:er
Ladda hem nya Beta 2 för SharePoint 2010 och Office 2010
Nu kan du helt publikt ladda hem och testa beta 2 för Office 2010 och SharePoint 2010 som nyligen släpptes.
Installera SharePoint 2010 Beta 2 i Windows 7
Microsoft har gjort det möjligt att installera Beta 2 SharePoint Server 2010 och SharePoint Foundation 2010 direkt i Windows 7. Här krävs det självklart x64 versionen av Windows 7. Detta kan vara en fördel när man är ute och demonstrerar SharePoint eller utvecklar utan att ha en Windows server igång. Nedan kommer tips på hur du i går tillväga för att installera beta 2 av SharePoint Server 2010 eller SharePoint Foundation 2010 på din Windows 7 x64 dator.
-
Installera SQL 2005 inkl SP3 och minst CU3 eller SQL 2008 inkl SP1 och minst CU2 (Express versionen funkar också om man inte har krav på t.ex. mycket utrymme i databaserna). För kännedom: SQL Server Express supporterar 1 fysisk processor, 1 GB minne och 4 GB lagring.
-
-
Att ha alla tjänster igång för SQL, SharePoint och IIS när man inte utvecklar eller testar funktionalitet kan kännas meningslöst och tar onödig kraft från din dator. Med hjälp av 2 PowerShell script som Emmanuel Bergerat på Microsoft satt ihop så kan du på ett snabbt och enkelt sätt starta och stoppa dessa. Ladda hem dem här http://blogs.msdn.com/emberger/archive/2009/11/16/stop-and-go-with-sharepoint-2010-on-your-workstation.aspx(se längst ner på sidan). En liten hake är att dessa är skapta för om du kör SQL Server och SharePoint Server 2010, men med lite modiferingar av dem så funkar även detta för SharePoint Foundation 2010 och SQL Express.
Microsoft Forefront Protection 2010 for SharePoint Release Candidate (RC)
Nu kan du ladda ner och utvärdera Microsoft Forefront Protection 2010 for SharePoint RC på din SharePoint 2010 eller MOSS 2007 miljö. Detta ger dig ett fullvärdigt anti-virus skydd mot filer som överförs till din SharePoint miljö. Ett anti-virus program finns oftast installerat på Windows Servern som har SharePoint installerat eller på företagens datorer enligt deras IT policy, men ger inte ett komplett skydd för SharePoint miljön. Microsoft Forefront Protection 2010 for SharePoint m.fl. ger dig ett bättre skydd och kontroll över de filer som överförs till din SharePoint miljö och i synnerhet om det är ett extranät där du har externa användare anslutna. Det är svårt att ha koll på hur deras datorers status ser ut, om de har ett anti-virus program installerat och inte minst om deras dator är smittad av något virus.
Viktig information vid installation av SharePoint 2010 Beta 2
Om du installerat SharePoint 2010 beta 2 på en Windows Server 2008 R2 eller Windows 7 så måste du ladda hem och installera en uppdatering. Detta för att åtgärda följande felmeddelande.
"System.Configuration.ConfigurationErrorsException: Unrecognized attribute 'allowInsecureTransport'. Note that attribute names are case-sensitive. (C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions14WebClients<Service Area>client.config line <Line Number>)".
Lycka till!
Tekniska Bakgrund:
Microsoft Share Point tekniken har mognat till stor del sedan dess begynnelse tillbaka i 2000-talet. Genom de här åren Microsoft som ett steg längre i varje release av SharePoint-versionen och den teknik för SharePoint-tjänster konvergerar och integreras till aktuell tid.
Under 2001 Microsoft gav Version 1 av SharePoint-tjänster vet lika SharePoint Team Services v.1 tillsammans med SharePoint Portal Server 2001. Den Team Services och Portal Server hanterades som olika enheter.
År 2003 Microsoft har släppt en serverlösning kallad Content Management Server 2002 tillsammans med uppgraderade utsättning av SharePoint-teknik som Share Point Portal Server 2003 och omdöpt version av tjänster kallas Windows SharePoint Services v2. Windows SharePoint Services v2 och SharePoint Portal Server 2002 integrerades noggrannare när Content Management Server 2001 var ett fristående.
Under 2006 Microsoft har publicerat en ökning av sin Windows SharePoint Services med version 3, med många nya framsteg och ovanpå dessa SharePoint-tjänster bygger den nya SharePoint-servrar. Microsoft släppte den första (beta) versionen av det nya Office-systemet kodnamnet som Office 12. Office 12 passar innehåller en rad SharePoint-servrar som Content Management Server och Portal Server är en integrerad del av dräkten. SharePoint Servers av Office 2007 passar kallas MOSS 2007.
En översikt av MOSS 2007:-
MOSS 2007 innehåller så många funktioner till ett organisationer computing företagsnivå krav. Funktionen som är uppdelad i följande kategorier:
1. Plattform. Platform Services är kärnan för MOSS 2007 arkitektur. Alla funktioner i MOSS 2007 bygger på framsteg i plattformen tjänster. Plattformstjänster del av MOSS 2007 arkitektur ger dessa anges funktioner.
• Arbetsytor Management.
• Säkerhet
• Lagring
• Server Topologi Management.
• Site Model
Microsoft Share Point tekniken har mognat till stor del sedan dess begynnelse tillbaka i 2000-talet. Genom de här åren Microsoft som ett steg längre i varje release av SharePoint-versionen och den teknik för SharePoint-tjänster konvergerar och integreras till aktuell tid. Samarbete inslag området MOSS 2007 innehåller rik stöd för olika typer av kommunikation och behov av samarbete över han företag inom avdelningar och mellan grupper. The feature set i samarbete omfattar följande.
• Dokument / uppgifter / kalendrar
• Bloggar
• Wikis
• E-post integration
• Projektledning Lite
• Outlook integration
• Offline dokument / listor.
2. Portal.
Portal område av MOSS 2007 arkitektur ger stöd för att integrera olika typer av webbplatser och webbplatssamling till en portal. Det kan vara så många portaler som krävs av företaget. Portalen funktionen ger en mycket mer framsteg och enkelhet för att skapa dessa sajtsamlingar och portaler. Funktionerna inom detta område är:
• Enterprise Portal-mall
• Site Directory
• Mina webbplatser
• Sociala nätverk
• Privacy Control.
3. Söka.
Sökområdet av MOSS 2007 arkitektur Förbättringar av följande egenskaper:
• skalbarhet
• Kontextuell betydelse
• rika människor och affärsdata sökning.
4. Content Management.
Som tidigare sagts att content management gavs i tidigare versioner av SharePoint-teknologin som en annan fristående server, men i MOSS 2007 här funktionen har endast en ur lådan funktionen. Content Management innehåller följande förbättringar till SharePoint Experience.
• Integrerad dokumenthantering
• Records Management
• Web Content Management med politik och arbetsflöde
5. Business Forms.
Med intåget av Windows Workflow Foundation, krävdes det att affärsprocessen formulär som används i de arbetsflöden som produceras av WWF sparas och dras med en motor typ av mekanism. Därför MOSS 2007 ingår en Forms Server som är ensam ansvarig för förvaltningen av verksamheten former i företaget i ett arbetsflöde. Affärsområdet utgör område ger följande funktioner:
• Rich och webbformulär baserat gränssnitt
• Pluggable Single Sign-On (SSO).
6. Business Intelligence.
Eftersom SharePoint-servrar har varit mycket framgångsrika i företagets breda sammanläggning av kommunikation och information finns det behövs sådana tjänster som kan visa affärsrelaterade uppgifter med tillhörande institutioner och arbetslag. Så att alla som har upphovsrätten till att visa affärsrelaterade uppgifter kan komma åt och analysera olika typer av information på portalen. Business Intelligence-funktionen område ger exakt den nödvändiga saker. Detta omfattar:
• Server-baserade Excel
• Server-baserade Excel-data visualisering
• Rapport Centers
• Business Intelligence webbdelar
• Key Performance Indicators (KPI) / instrumentpaneler
• viktiga förbättringar i MOSS 2007 / Begränsningar i SharePoint Portal Server 2003
Låt oss tala i detalj om den stora förbättringen i MOSS 2007 (begränsningar och smärtpunkter i SharePoint Portal Server 2003). Följande lista är en kort översikt över vilka funktioner i SharePoint Portal Server 2003 inte anges, men nu som en del av MOSS 2007.
• flerspråkiga.
• Autentisering
• Extranät portal adresser / alias / kartor.
• Finkorniga Access Control per listobjekt behörigheter
• Arbetsflöden
• Backup / Restore
• Sammanläggning av information och listor.
• Navigation användbarhet.
• Rapportera Center och Dash boards.
• Uppgifter och Kalender synkronisering med Outlook.
• Site Customization
• Offline dokument och listor.
• Sök förbättringar.
• Metadata Management
• användningsrapportering
• listings Usability
Dessa begränsningar / färg punkter har tagits upp med hjälp av förbättrad och integrerad MOSS 2007 arkitektur. Dessa begränsningar har behandlats av olika inslag områden (som diskuterats tidigare) av MOSS 2007. I följande avsnitt närmare utveckla några av de stora förbättringar som görs för att motverka dessa begränsningar. Dessa diskuteras per Feature området.
Plattformstjänster: Platform Services är kärnan avancemang i MOSS 2007 och många av de förbättrade funktionerna finns i denna kategori. Från de ovan nämnda lista. De förbättringar som plattformstjänster är.
Flerspråkig
Stöd för installation av flera språkpaket till samma server så att varje webbsida kan ha sitt eget språk, vilket ger stöd för flerspråkiga webbplatser samt
Authentication
Med hjälp av ASP.Net 2.0 plattformen Services tillhandahåller funktioner såsom ASP.Net Pluggable Authentication och webbformulär autentisering.
Extranet
Utplacering av extranät med hjälp av omvänd proxy och suppleanter webbadresser tillträde är möjligt.
Finkorniga Access Control
I SharePoint Portal Server 2003 bara Dokumentbibliotek (Lista) få tillgång stöddes där så nu finns det en per säkerhet på objektnivå definierade.
Workflow
Platform Services tillhandahåller support för Windows Workflow Foundation.
Backup / Restore
Förbättrad backup / restore inklusive papperskorg och VSS stöd
Aggregation
Sammanläggning stöd som hjälp av Cross-web lista delar tillhandahålls.
Navigation
Förbättrad Look & Feel och navigering med hjälp av huvudsidor och säkerhetspolitik-trimmade UI ges.
Site Customization
Anpassning förbättringar med hjälp av mallar, feature tänjbarhet och ASP.Net huvudsidor stöds.
Samverkan
Funktionen som föreskrivs i den kategori av samarbete har några mycket viktiga förbättringar i MOSS 2007 jämfört med SharePoint Portal Server 2003. Kärnan förbättringsområden är Dokumentbibliotek och Outlook Integration och synkronisering.
Dokumentbibliotek Förbättringar
I dokumentbiblioteket Förbättringar, stöder nu Kontroll av handlingar från dokumentbibliotek till lokala mappar större och mindre version spårning, versionshantering, olika typer av innehåll i samma dokument biblioteket och en trädvy av dokumentbiblioteket.
Outlook Integration förbättringar
I Outlook integration förbättringar, stöder
• Läsa och skriva på SharePoint-objekt, till exempel kalender, uppgifter, kontakter, diskussioner och dokument från Outlook-klienten.
• Dessutom är stöd för synkronisering med offline-dokument som har checkat ut för redigering i Microsoft Outlook från SharePoint-dokumentbibliotek.
• Även det stöd för kalendrar och uppgifter tvåvägs synkronisering.
Portal : Funktionen gäller portalen har också lite god förbättring som innehåller följande.
• Integration med Windows SharePoint Services
• Internt portalmall Topics, Site Directory
• Människor och Kompetens Sök
• Människor särskilda sökflik
• Social network support
• Förbättrad offentlig sida, Personlig hemsida
• Inriktning och anpassning
• Enklare inriktning Sändlistor och säkerhet Grupper
• Lagra förbättringar
• Skalbarhet, flexibelt schema, LDAP synkronisering.
Business Intelligence (BI):-
Microsoft SharePoint Portal Server teknik didnt tillhandahålla support för företaget eller verksamheten relaterad information delas och visas på SharePoint-portaler. I MOSS 2007, har Microsoft tänkt och uppnått målet att förbättra organisationer genom att tillhandahålla näringslivet insikter till alla anställda som leder till bättre, snabbare och mer relevanta beslut med hjälp av nya förbättringar och nya funktioner i SharePoint Portal Server.
MOSS 2007 ger dessa stöd med hjälp av följande funktioner:
Excel client / Excel Services
Dashboards & Key Performance Indicators
Excel Client används för att skapa kalkylblad och sedan publiceras på MOSS 2007 dokumentbibliotek. Excel Services tillhandahåller funktioner för att visa Excel-filer som rapporter i webbläsaren. Dashboard Aktiverar guidade och optimerad analys av data från användaren / anställd. Dessa data lagras i instrumentpaneler i form av Aggregate arbetsböcker, rapporter, styrkort, etc. instrumentpaneler göra den information som är relevant inom i rapporter, etc. också kommentera uppgifter med ytterligare information.
| 
Tutorials 
