This module introduces the architectural features that underpin Microsoft SharePoint Server 2013, both for on-premises and online deployments. This includes an examination of the features that are new in this version, as well as those that have been removed. This module reviews the basic structural elements of a farm deployment, and the different deployment options that are available in SharePoint 2013.

This module examines high availability and disaster recovery in SharePoint 2013. When designing high availability and disaster recovery strategies for a SharePoint farm, it is important to understand the different approaches required by each logical tier in the farm. High availability for the database tier requires understanding of how SQL Server provides high availability and the associated requirements. High availability for the application tier can be straightforward for some service applications, while other applications, such as Search, require additional planning and configuration for high availability. The web front end tier will also require additional planning and configuration for high availability, and architects should consider the new SharePoint 2013 request management feature. SharePoint farm disaster recovery has always required considerable planning and understanding of the necessary components and backup tools available. In this regard SharePoint 2013 is no different, and farm administrators should create a disaster recovery plan that states how content and configurations are backed up, how data can be restored, and what backup schedules are required.

Service applications were introduced in SharePoint 2010, replacing the Shared Service Provider architecture of Microsoft Office SharePoint Server 2007. Service applications provide a flexible design for delivering services, such as managed metadata or PerformancePoint, to users who need them. There are several deployment topologies available to you when you plan your service application implementation. These range from a simple, single-farm, single-instance service application model to more complex, cross-farm, multiple-instance designs. What remains most important is that you create a design that matches the needs of your organization's users in terms of performance, functionality, and security.

 

This module reviews the service application architecture, how to map business requirements to design, and the options for enterprise scale, federated service application architectures.

Most organizations store information in a variety of disparate systems. In many cases, these organizations want to be able to view and interact with information from these disparate systems from a single interface. This reduces the need for information workers to constantly switch between systems and creates opportunities for power users or analysts to aggregate data from multiple sources.

In SharePoint 2013, Business Connectivity Services (BCS) is a collection of technologies that enable you to query, view, and interact with data from external systems. In this module, you will learn how to plan and configure various components of BCS.

This module examines how SharePoint 2013 extends the ability of users to work collaboratively and increase productivity through seamless integration with external software platforms, additional SharePoint collaboration features, and the provision of flexible tools, with which users can develop their own solutions to business problems.

Business Intelligence (BI) continues to be an important area for large enterprise organizations. The key to successful BI is the ability to integrate the components that deliver the right information, to the right people, at the right time. Microsoft SharePoint Server 2013 Enterprise Edition provides a range of integrated solutions that enable both users and administrators across an organization to develop BI solutions to fit their business requirements. These BI tools extend beyond SharePoint to provide consistent information management from personal data analysis environments, which use Microsoft Excel, through to departmental or organizational data repositories, which use SQL Server Reporting Services (SSRS) and SQL Server Analysis Services (SSAS).

 

In this module you will see how SharePoint 2013 can deliver BI solutions for your business.

The Search service remains a cornerstone of the SharePoint platform’s success. In Microsoft SharePoint Server 2013 there have been major changes to the components that make up the service, to increase performance and configurability.

 

In this module, you will examine the configuration options in SharePoint Search that enable you to provide greater search result effectiveness by fine-tuning the service in various ways. The introduction of new functionality, such as result types and the increased move towards search-driven navigation mean that the role of the Search administrator has become even more important for business success. Search now enables you to delegate more of this management to site collection administrator and site owner levels, improving Search flexibility without increasing the administrative burden on a few Search service application administrators.

 

This module also examines Search analytics and reporting. To help you in your management of a Search environment, SharePoint 2013 now incorporates Search analytics and reporting into the Search service, rather than in a separate service application, as was the case in SharePoint Server 2010. The reports available will help you to monitor the service and optimize its configuration.

This module examines Enterprise Content Management (ECM), which is a set of technologies and features that administrators use to provide some control over sites and content. This could include control over how information is stored, how long information is kept, how information is visible to users while in use, and how information growth is kept under control.

 

Planning support for your ECM requirements requires a clear understanding of content requirements and how that content supports the organization. This means that, as a best practice, many different organizational roles should have input into the ECM strategy and supporting features.

As a SharePoint administrator, it is important to understand the features that are available in Microsoft SharePoint Server 2013. However, there are often specific functional requirements that may be part of SharePoint’s feature set but are not included in certain site templates. There may also be sites that require repeatable customization of lists or libraries, or custom code deployments that are necessary to add capabilities that are not available out-of-the-box. Developers use features and solutions to add and control these functionality requirements. Administrators, on the other hand, must understand how features and solutions are deployed and managed in order to meet user needs in a SharePoint farm.

SharePoint apps are new to Microsoft SharePoint Server 2013 and provide an additional capability to provide application functionality within the context of SharePoint. SharePoint apps supplement the capabilities of farm solutions and sandbox solutions, while providing a user experience that offers a measure of self-service customization capabilities without putting the stability or security of the farm at risk.

Governance as it relates to SharePoint can be described as a way of controlling a SharePoint environment through the application of people, policies, and processes. Governance is necessary for all IT systems as a whole, and in particular for SharePoint deployments, which often introduce significant change in business processes, available functionality, and day-to-day working practices.

 

It is important to understand that governance must reflect the needs of the organization and how it should best use SharePoint. Therefore, the IT department cannot be the only body governing SharePoint; input must come from corporate sponsorship across the organization. The IT department must still act as the technical authority for SharePoint; however, this is just a single part of how SharePoint governance must be brought together from different parts of the organization.

Upgrading your Microsoft SharePoint Server 2010 farm(s) to SharePoint 2013 is a major undertaking, so it is important that you carefully plan the upgrade activities. You need to ensure that your upgrade path—moving from version to version—is supported, that you have reviewed the business impact of your upgrade, and that you test your upgrade strategy to ensure business continuity. As with all such activities, preparation is crucial.

 

In contrast with earlier version of SharePoint, SharePoint 2013 supports only database-attach upgrades for content, but it now supports upgrades for some of the databases associated with service applications. You need to plan for these and ensure that you are prepared for any troubleshooting that may be required.

 

Another change in SharePoint 2013 is the approach to upgrading site collections. These are upgraded separately from the data and service applications. You can also delegate the upgrade tasks to site collection administrators.