THEORY - MOSS 2007 Installation

Installing MOSS 2007 is based on a network-wide servers and common services in a cluster of computers which is commonly referred as Server Farm.

Further a Server Farm is two or more networked computers in a single location that host server software or shared network services. Server farms distribute the processing of client requests and server workload between the clustered computers in the farm using load-balancing techniques to more efficiently provide services across a client/server environment.

At the enterprise level, MOSS is installed on a server farm to better process user client requests to and from other servers, which could also be clustered into the server farm.

However, MOSS can also be installed on a single, standalone computer—meaning, a single server application. It can be installed on a single desktop computer, too, but much of its benefits would be lost. However, SharePoint can provide some benefits on a peer-to-peer network. Overall though, MOSS and the collaborative features built into Microsoft Office 2007 would be best in an enterprise installation.

(MOSS) in either a server farm or a standalone server.

THEORY: MOSS SERVER FARM CONFIGURATION

The components that make up your server farm will vary on the size and scope of the MOSS environment. There are recommended configurations for MOSS server farms in small, medium and large environments, however there are no hard and fast rules to gauge the size of the server farm.

A small MOSS server farm commonly includes the following:

· Front-end web and application servers to provide web content and MOSS services, such as search and indexing

· A database server running Microsoft SQL Server (Optional)

· A server supporting IIS and MOSS

A medium MOSS server farm consists of the following:

· A MOSS application server

· One or more front-end servers to provide IIS and MOSS services, such as indexing and Excel calculation

· A front-end web server

· A database server running Microsoft SQL server (Optional)

A large MOSS server farm consists of the following:

· Multiple load-balanced front-end web servers providing IIS and MOSS services

· Multiple applications servers supporting specific MOSS applications or services

· At least two clustered database servers running Microsoft SQL Server

· MOSS requires that each of the web servers in the sever farm have the same MOSS services and applications installed, regardless of the primary purpose of the server

This means that a standalone server cannot be added to the server farm to support a single Microsoft Office 2007 application. For example, a Microsoft Office Project Server 2007 server cannot be added to the server cluster and hope to integrate the Project 2007 data into the MOSS environment. The new server must also have MOSS installed, to the same level as any other web or application servers in the server farm, to function properly. However, on a particular application or web server, specific functions and services can be disabled as a security measure.

Enough of theory now, let us check it out, how.

Installation of Microsoft Office SharePoint Server 2007 can be broadly classified into 3 categories.

• Pre-Installation of MOSS 2007
• Installation of MOSS 2007 and
• Post-Installation of MOSS 2007

INSTALLATION OF MOSS 2007

• Standalone MOSS Installation
• Server Farm MOSS Installation

STANDALONE MOSS INSTALLATION

If you want to evaluate MOSS 2007 or where you want to publish only a small number of MOSS based web sites, it may be more useful and certainly more administratively efficient to install MOSS on a standalone server(not in server farm).

This installation is pretty simple, as MOSS itself will take care of the complexity of the pre-installation process, along with that of the actual default configuration settings assuming that Windows 2003 server is the installed operating system on that server.

Once the Pre-installation steps were followed, the later steps in a Standalone server are as follows:

Step 1: Run MOSS 2007 Setup CD

MOSS 2007 Setup has to be executed and when prompted have to produce the right Product key which, you will be getting along with your software. The software will be installed by itself and will create respective Configuration, Content DBs in SQL Server 2005 by creating a new instance usually “\OFFICESERVERS”.

Shared Service Provider (SSP) created during installation by the setup utility.

SharePoint site collection and default site will be created along with the SharePoint Central Administration web site.

NOTE: Remember that while some processes can be used to migrate a standalone server into a server farm using backup and restore processes, the MOSS portion of the migration cannot be directly upgraded from a single server installation to a server farm installation. So for at least the MOSS portion of the installation, if you decide to move the installation into a server farm, you’ll essentially need to reinstall the MOSS environment. Configure Server as a web server. A few pre-installation steps must be carried out before installing MOSS on a standalone server. As shown in the server farm pre-installation steps covered in the preceding sections, the environment must be established through the installation and configuration of the following systems or services.

Step 2: Complete Configuration Steps for MOSS 2007

When setup completes, you are prompted to complete the configuration of the MOSS server. To complete the configuration, follow these steps:

a) On the dialog box that appears, select the checkbox corresponding to the Run

“The SharePoint Products and Technologies Configuration Wizard Now” option.

Click Close to launch the configuration process.

(Attach figure…coming soon)

b) “The SharePoint Products and Technologies Configuration Wizard” starts up and

Displays its welcome page. Click Next to continue.

(Attach figure…coming soon)

c) The configuration wizard then begins a series of ten configuration steps

automatically .

(Attach figure…coming soon)

d) If during the configuration process an error or a condition advice situation occurs, you may see a message box similar to “the need to restart certain services needed to complete the configuration …..”

(Attach figure…coming soon)

e) Click the OK button to allow the Configuration Wizard to correct the issue.

f) When the configuration wizard completes the configuration, a Configuration

Successful page displays. Click the Finish button to open the SharePoint site

You’ve just created.

SERVER FARM MOSS INSTALLATION

MOSS is designed to be installed fairly easily into a server farm environment for those

larger organizations that have their applications and network services deployed across

multiple, integrated computer servers or any organization that plans to support a large

number of web sites that draw on a large database or data store. However, you should

understand that a server farm installation of MOSS assumes its SharePoint services are

implemented across two or more servers dedicated to MOSS support.

The Administrator Tasks on the MOSS Diagnostic Logging Settings page.

NOTE A server farm deployment for any system, and especially an MOSS deployment, requires

some planning and server preparation. Before you begin your server farm installation of MOSS, you

should review the material and processes discussed in Chapters 1, 2, and 3.

Server Farm Types and Sizes

Microsoft defines three server farm types, designated by size:

▼ Small server farm This type of server farm consists of at least two servers: a

database server and an application server. The application server supports web

services and MOSS content and web site services.

■ Medium server farm A medium MOSS server farm adds additional frontend

servers to the topology of a small server farm. The front-end servers

assume the role of web services and MOSS basic services, relegating the

application server to supporting indexing, web crawling, processing search

queries, and such features as Excel Calculation Services.

▲ Large server farm A large MOSS server farm involves multiple clustered

database servers, multiple front-end servers that are load-balanced to support

web services and MOSS, and multiple applications servers, each supporting a

specific MOSS function.

Regardless of the size and topology of your server farm, each server on which all or

part of the MOSS environment is to be installed must be configured essentially the same.

The following sections outline this common configuration.

NOTE It is not a good idea to install MOSS on a domain controller for a variety of reasons, the primary

one being that additional, and somewhat complex, configuration is required. If this is something you

are considering, visit the Microsoft TechNet site (http://technet2.microsoft.com/Office/en-us/library)

for additional information.

Topology Considerations

Let’s review a brief checklist of the services, technologies, and configuration you must

have in place before starting a server farm installation of MOSS. The following must

have been installed, configured, or completed before you begin to install MOSS in a

server farm environment:

▼ All server hardware meets or exceeds (highly recommended) the minimum

system requirements of the operating system, the database system, and MOSS.

■ The network operating system must be Windows Server 2003 with at least

Service Pack 1 (SP1) installed.

■ The database server must be running either SQL Server 2005 (with all updates

applied) or SQL Server 2000 with SP3a or later installed.

68 Microsoft Office SharePoint Server 2007: A Beginner’s Guide

■ Internet Information Services (IIS) must be installed and enabled on each of the

servers on which MOSS is to be installed.

■ Each MOSS server must have .NET Framework 3.0 and ASP.NET 2.0 installed

and enabled.

■ MOSS must be installed on the same disk drive (for example, each of the disk

drives must be designated as C:) in every server that will be a part of a loadbalancing

scheme.

▲ Each indexing server included in the server farm must have a different Shared

Services Provider designated for it.

MOSS Installation

You should configure your database server and, if possible, install

your database content, before starting the installation of MOSS. If you have all of the

preinstallation tasks completed and your computer servers are ready to go, install MOSS

and run the SharePoint Products and Technologies Configuration Wizard on each server

The next major step in the MOSS installation process for a server farm deployment is

to run the Setup program for MOSS on each of the appropriate servers in the server farm.

You should install MOSS on each server before you configure the server farm itself.

The MOSS setup program prompts you to indicate the type of installation you wish

to perform. The choices are:

▼ Complete Indicating you wish to install all MOSS components and configure

a server farm after installation.

■ Web front-end Indicating you wish to install only the MOSS components

required on this type of server.

▲ Standalone This is not the choice you want for a server farm installation.

There is no upgrade path available to move from a standalone installation to a

server farm installation.

Once the MOSS installation completes, you should run the SharePoint Products and

Technologies Configuration Wizard, at the end of which the Central Administration page

should open. If this page fails to open, open the SharePoint 3.0 Central Administration

page from the Start menu (Start | All Programs | Microsoft Office Server | SharePoint 3.0

Central Administration).

sitemap

xmlns="http://www.sitemaps.org/schemas/sitemap/0.9"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.sitemaps.org/schemas/sitemap/0.9
http://www.sitemaps.org/schemas/sitemap/0.9/sitemap.xsd">



http://sharepointgoogle.blogspot.com/
2010-01-25T07:16:41+00:00


http://sharepointgoogle.blogspot.com/2010/01/installation-of-microsoft-office.html
2010-01-25T07:16:41+00:00


http://sharepointgoogle.blogspot.com/2010_01_01_archive.html
2010-01-25T07:16:41+00:00


http://sharepointgoogle.blogspot.com/2010/01/plan-and-configuration-of-moss-2007.html
2010-01-25T07:16:41+00:00


http://sharepointgoogle.blogspot.com/2010/01/benefits-of-microsoft-office-sharepoint.html
2010-01-25T07:16:41+00:00


http://sharepointgoogle.blogspot.com/2010/01/introduction-to-microsoft-office.html
2010-01-25T07:16:41+00:00

Installation of Microsoft Office SharePoint Server 2007

As mentioned in my previous post, that, prior to the installation of MOSS 2007, it’s important to plan for the type of environment in which MOSS has to be installed. So, once the planning is done, we will follow the below steps to install MOSS 2007.

Installation of Microsoft Office SharePoint Server 2007 can be broadly classified into 3 categories.

• Pre-Installation of MOSS 2007
• Installation of MOSS 2007 and
• Post-Installation of MOSS 2007

PRE-INSTALLATION OF MOSS 2007

The installation steps mentioned below, will mention all the software installations on Windows Server 2003 Standard Edition, and are the same for any other versions of Windows Server 2003 Operating System.

Step 1: Hardware Specifications.

Minimum/Recommended Hardware Requirements for Windows Server 2003

Hardware Feature	Minimum Requirement	Recommended Requirement
CPU Speed	133 megahertz (MHz)	550 MHz
Memory	128 megabytes (MB)	256 MB
Hard disk space	1.5 gigabytes
CD-ROM drive	At least 12X
Monitor resolution	Super VGA (SVGA) 800 X 600	SVGA 1024 X 768

Apart from the above mentioned Minimum/Recommended Hardware Requirements for Windows Server 2003, there are some additional System requirements as listed below.

• A front-end web server or an application server computer must be a dual processor computer with processor clock speeds of 2.5 gigahertz (GHz) or higher and at least 2 gigabytes (GB) of RAM.
• A back-end database server must also be a dual-processor computer with processor clock speeds of 2.0 GHz or higher and a minimum of 2 GB of RAM.

Step 2: Create a Local Administrator Domain Account.

Before going further and installing any of the software, it is always recommended that you create a domain account specifically for installing MOSS and should be a local administrator domain account such that this account will be used to administer any administrative functions for MOSS and its supported services, such as SharePoint Administrator, Index Crawler and Application Pool etc,.

NOTE: Now logoff and login with this newly created domain account and follow the further steps.

Step 3: Install Windows Server 2003 Service Pack 1 (SP1).

Install Windows Server 2003 Service Pack 1 (SP1) and update with the latest downloads available.

Search for Windows Server 2003 Service Pack 1 (SP 1) in Google.

Step 4: Install IIS 6.0.

IIS 6.0 must be installed and made available and also ASP.NET 2.0 component must be installed and enabled.

In Add Remove Programs, Click on Add/Remove Windows Components, in which you select Application Server and then click details and select the check box saying Internet Information Services and install.

Note: This requires Windows Server 2003 Installation files with folder I386 which comes along with the licensed setup CD.

Note: (Optional) If required for remote transactions and remote access do the following:

• Enable COM+ for remote transactions
• Enable Microsoft Distributed Transaction Coordinator (DTC) for remote access

Step 5: Install .NET framework 3.0 or later and Allow ASP.NET 2.0 component.

After installing .NET framework 3.0 or later version, Open IIS Manager and expand the computer name and then select Web Service Extensions, in the details window, you can see ASP.NET v2.0x and if the status of this Web Service Extension is prohibited, change its status to allow.

Search for .NET framework 3.0 in Google.

Step 6: Install SQL Server 2005 Standard Edition or Enterprise Edition. (Optional)

Step 7: Install Workflow Foundation (WWF).

INSTALLATION OF MOSS 2007

Installation of MOSS 2007 can be again sub categorized into 2. They are:

• Standalone MOSS Installation
• Server Farm MOSS Installation

STANDALONE: MOSS INSTALLATION

Once the Pre-installation steps were followed, the later steps in a Standalone server are as follows:

Step 1: Run MOSS 2007 Setup CD

Setup will prompt you to enter the Product key, Kindly enter the right Product key so that “Continue” button will enable, so that you click to install MOSS 2007.

Step 2: Complete Configuration Steps for MOSS 2007

When setup completes, you are prompted to complete the configuration of the MOSS server. To complete the configuration, follow these steps:

a) On the dialog box that appears, select the checkbox corresponding to the Run “The SharePoint Products and Technologies Configuration Wizard Now” option. Click Close to launch the configuration process.

b) “The SharePoint Products and Technologies Configuration Wizard” starts up and Displays its welcome page. Click Next to continue.

c) The configuration wizard then begins a series of ten configuration steps automatically .

d) If during the configuration process an error or a condition advice situation occurs, you may see a message box similar to “the need to restart certain services needed to complete the configuration …..”

e) Click the OK button to allow the Configuration Wizard to correct the issue.

f) When the configuration wizard completes the configuration, a Configuration Successful page displays. Click the Finish button to open the SharePoint site You’ve just created.

SERVER FARM: MOSS INSTALLATION

You should configure your database server and, if possible, install your database content, before starting the installation of MOSS. If you have all of the preinstallation tasks completed and your computer servers are ready to go, install MOSS and run the SharePoint Products and Technologies Configuration Wizard on each server. The next major step in the MOSS installation process for a server farm deployment is to run the Setup program for MOSS on each of the appropriate servers in the server farm.

You should install MOSS on each server before you configure the server farm itself.

The MOSS setup program prompts you to indicate the type of installation you wish to perform. The choices are:

1) Complete Indicating you wish to install all MOSS components and configure a server farm after installation.

2) Web front-end Indicating you wish to install only the MOSS components required on this type of server.

3) Standalone This is not the choice you want for a server farm installation.

There is no upgrade path available to move from a standalone installation to a server farm installation.

Once the MOSS installation completes, you should run the SharePoint Products and Technologies Configuration Wizard, at the end of which the Central Administration page should open. If this page fails to open, open the SharePoint 3.0 Central Administration page from the Start menu (Start | All Programs | Microsoft Office Server | SharePoint 3.0 Central Administration).

MOSS POST INSTALLATION

After the SharePoint installation (Setup.exe) completes as it should, the home page of your SharePoint site will display in your default Internet browser. While the temptation will be to start customizing the site collection and adding content immediately, you should review at least two groups of settings for possible changes: antivirus settings and diagnostic logging settings. While it is true that you don’t actually have to configure these settings before you go on to other actions, it is recommended you at least review these two settings areas before you do.

Antivirus Settings

To configure the antivirus settings for MOSS, assuming your antivirus is compatible with MOSS (check with your antivirus vendor), perform the following tasks:

1. Open the SharePoint Central Administration page and locate the Security Configuration section.

The stsadm.exe MOSS administration program can be used at a command line to set or alter the MOSS environment.

2. Click the Configure Antivirus Settings option to open the Antivirus page.

3. If you wish to scan all downloaded documents for viruses, check the Scan Documents On Download box.

4. If you wish to scan all uploaded documents for viruses, check the Scan Documents On Upload box.

5. If you wish to allow users to save a file that is infected with a virus on their local hard disk, check the Allow Users To Download Infected Documents box.

This option is not selected by default and must be overridden to allow an infected file to be downloaded.

6. By default, MOSS allows an antivirus program 5 minutes (300 seconds) to scan a document. However, if you wish to allow more (or less) time for the scan, change the number of seconds in the Time Out Scanning After ____Seconds box. Five minutes should be enough time for any antivirus program to complete its task, but if antivirus scanning is affecting system performance, you may want to alter this field.

7. If your antivirus software is server-based, it is likely that multiple instances of it may be active at any one time. The default number of threads allowed by MOSS for antivirus scanning is five, but should you wish to allow more or fewer antivirus scanning threads, you can change the value in the Allow Scanner To Use Up To ____ Threads box.

8. Click OK to complete the antivirus settings and enable this function.

Diagnostic Log Settings

To configure the diagnostic logging settings for MOSS, perform the following steps:

1. Open the Central Administration page.

2. Choose Diagnostics logging settings from the Administrator Tasks list or choose Diagnostic logging from the Logging and Reporting area of the Operations page. Either choice displays the Diagnostic Logging page. The Event Viewer showing the log files of an MOSS system.

The Diagnostic Logging page has 4 configuration areas:

1) Customer Experience Improvement Program If you are willing to work with Microsoft by providing anonymous information on your experiences regarding the reliability and performance of their products, you should select the Yes, I Am Willing … radio button. Otherwise, leave the default No, I Don’t Wish To Participate option selected.

2) Error Reports Whenever MOSS experiences a hardware or software issue, a report is generated for use by Microsoft (and its partners) to improve system quality and reliability. If you wish to allow error reports to be collected, select the Collect Error Reports radio button option and check the box for the method you wish to use. Otherwise, choose the Ignore Errors And Don’t Collect Information option.

3) Event Throttling You are able to set the event severity for each of the different service types for which you can capture event notices. Sample settings for MOSS general events logging. You can also set a threshold for the severity of the events to be captured using the Least Critical Event To Report To The Event Logs and the Least Critical Event To Report To The Trace Logs pull down lists. These lists are preordered with the most critical event types listed first.

4) Trace Log Should you wish to enable event tracing, you can designate where you wish the trace logs to be located, how many logs to keep, and the trace duration each log records.

High Level - Planning And Configuring Of MOSS 2007

Developing a plan always helps us to ensure the result we wish. So just diving into SharePoint isn’t something we should do without first analyzing the impact it may have on your business and understanding where the impacts will felt. Many of the decisions and choices that must be made before and during the MOSS installation directly impact how well the system will run the features and the ease with which you can later activate additional features and services. You and your company should perform Planning and Pre-installation steps to ensure a successful implementation.

Planning and configuring MOSS 2007 System needs a team which must need at least someone to represent each of the following areas.

• Key Decision Makers, who understand and can drive the vision of what MOSS brings to the company and its IT systems.
• Key Knowledge Workers, who know the processes and procedures and who can help with the improvements that better knowledge, collaboration, and document management can provide. In most of the cases, this team is also responsible for acceptance testing.
• Any key external entities that may be integrated into the workflows or information sharing provided by the system
• IT professionals from the company’s central IT authority, as well as the IT technicians from each of the company’s central IT authority, as well as the IT technicians from each of the company’s divisions or departments.
• And finally Key members of the design team who will be tasked with creating the visual look and feel of the system by developing the company’s templates, forms, Web Parts, Workflows, and other custom features, which to the end user, represent the "new system" and the "face of the change".

Now its time to see how to Install MOSS 2007 in different environments, which I am going to cover soon. See you then.

Tags: Planning of MOSS 2007, Configuring of MOSS 2007, Planning and Configuring of MOSS 2007.

Benifits Of Microsoft Office SharePoint Server 2007

Ok, as we are now familiar about the Introduction of Microsoft Office SharePoint Server 2007 (from now onwards I will name it as MOSS 2007) in my last post, it’s time for us to know about the benefits of MOSS 2007.

MOSS 2007 provides an enterprise with the means to solve a variety of information and data sharing collaboration requirements with a variety of new and upgraded features that give it the functionality to do so.

A fully implemented MOSS 2007 environment provides benefits to a company and its employees, and perhaps its customers, agents, and vendors, in the following areas:

MOSS 2007 provides an enterprise with the means to solve a variety of information and data sharing collaboration requirements with a variety of new and upgraded features that give it the functionality to do so. A fully implemented MOSS 2007 environment provides benefits to a company and its employees, and perhaps its customers, agents, and vendors, in the following areas:

• Familiarity
• Productivity
• Information management
• Information retrieval
• Data accessibility and audit
• Business application interface
• Sharing information
• Single platform solution

The above general categories are discussed below:

FAMILIARITY
All the Microsoft based Desktop applications, e-mail, along with their web browser, their user access, storing data, sharing data, information and documents that any user is accustomed for, will be similar and are very much familiar for the end users through MOSS 2007 System.

PRODUCTIVITY
MOSS 2007 defines variety of built-in Workflows, that simplify the user’s ability to create, track, and retrieve frequently used data to meet their most common business information based functions. Through these Workflows, the end users will be able to easily perform a number of document-based activities, including review, tracking, approval etc.,. The good thing about these Workflows is, it doesn’t need any administrator to meet this functionality by creating new macro-functions (custom code) or programming. However, for the more complex functionalities based on the business requirement, Workflows can be customized by either using SharePoint Designer(formally known as Microsoft office FrontPage) or by using Visual Studio With Workflow Foundation Extensions installed.

INFORMATION MANAGEMENT
Due to the increasing Business requirements regarding managing the business information, such as, storing the documents and other types of organized data, setting permissions to control, who can access the data, when necessary, based on the company’s policies etc., were provided by MOSS 2007 through its feature called Document Management Policies. The most driving feature in MOSS 2007 is Collaboration among users which also benefit the collaborative work among team members using the portal. MOSS 2007 System can also be used for translating the documents from one language to another, and is also helpful in maintaining the PowerPoint slides in a library to make a Presentation from the existing PPTs in the Library.

Document Policies: Like a written guideline or policy, MOSS 2007 document policies can be customized to include who can and can’t access a document, how long a document is to be retained, what to do with the document when its retention period expires, and whether or not an audit trail should be kept to track who accesses a document and when.

INFORMATION RETRIEVAL
When compared to older versions of business requirements, the need for file sharing has changed a lot among the team members. Now that the user is trying to access a document over the company’s intranet and virtual private network (VPN) may have had some difficulty locating and retrieving the documents, which was made easy by MOSS 2007 system by its features which has the ability to access and use data and documents stored on both local and remote servers throughout the company.

DATA ACCESSIBILITY AND AUDIT
MOSS 2007 system allows users to store the data in one central repository and provides its users with the ability to easily locate, access and retrieve the documents based on their permission levels. As per the Policies in the Document Management Policy defined centrally for the entire system, and specifically to an individual document by its creator, the manager control of information is largely transparent to the end user.

BUSINESS APPLICATION INTERFACE
MOSS 2007 provides a number of “configurable back-end connections” or established interfaces that allow users to access the data managed by a variety of common business and enterprise systems, such as SAP and Siebel, to create individual views of the data. Users can also work through back-end connectors to set up data management interactions with these third-party systems using the Office 2007 applications on their desktops. MOSS 2007 also allows users to create electronic forms that can be used to enter, collect, and distribute data to and from external sources—such as customers, business partners, and vendors—through a web page interface on the company’s extranet or from the Internet and Web. The MOSS 2007 electronic forms feature allows for the definition of data integrity and validation rules, ensuring that data flowing into back-end systems is correct, thus eliminating the chance for data-entry errors or data duplication that could occur if the data had to be reentered manually.

SHARING INFORMATION
MOSS 2007 facilitates information sharing through its Excel Services. Users can have access to up-to-date, real-time spreadsheet data using a web browser from a central source to enable their productivity. MOSS 2007 uses various tools such as Business Intelligence (BI), Key Performance Indicators (KPIs) for the portals to retrieve and display information from a variety of document sources. The BI portal feature includes a number of functions, such as user dashboards and defined information pieces that can be incorporated into a user-defined web page, scorecards, and visual presentation tools called key performance indicators (KPIs).

SINGLE PLATFORM SOLUTION
As MOSS 2007 incorporates the functions of the Office 2007 applications and is based on a scalable, open architecture, it provides a broad-based single platform solution. In larger installations, MOSS 2007, installed on Microsoft Windows Server 2003, provides a single-source interoperable system solution by extending the capabilities of Microsoft SQL Server and WSS. MOSS 2007 extends its interoperability through its support of Extensible Markup Language (XML) and Simple Object Access Protocol (SOAP), which allows it to communicate with other systems and networks seamlessly. This is an important feature in that it allows the MOSS 2007 system to interface with any existing or future non-Microsoft systems the company may have or add.


Further to this, I am going to post about, the "Installation of SharePoint" - Will Catch you soon. - Good Night.

Tags: Benifits of SharePoint, Familiarity, Productivity, Information Management, Information Retrieval, Data Accessibility and audit, Business Application interface, Sharing Information, Single Platform Solution.

Introduction to Microsoft Office SharePoint Server 2007.

SharePoint is a Collaboration portal, and is also a Platform, for meeting the various requirements of the companies Websites ranging from creation of Sites, Lists, Webparts, User Groups, Workflows, InfoPath Forms, Search etc., to meet the goals of the Companies Business in a very Effective, Easy and in a very short time which indeed takes considerably enough time achieving it through any other technology.

The various features that are available in Microsoft Office SharePoint Server 2007, which can be developed ranging from a layman to an expert developer are as follows:

• Sites
• Document Management
• Project Management
• Calendars and Schedules
• Workspaces
• Workflows
• Blogs, Wikis, and Discussion Forums
• InfoPath
• Security
• Integration with other Enterprise Software
• Extensions
• Business Intelligence and
• Search


About Benefits of Microsoft Office SharePoint Server 2007...

Tags: SharePoint Introduction, What is SharePoint.