This document provides an overview of advanced SharePoint server concepts, including calculated columns, lookup columns, importing and exporting web parts, InfoPath forms, managed accounts in SharePoint 2013, prerequisites for SharePoint 2013, and logical and physical architectures. It discusses how to create formulas for calculated columns, set up relationships for lookup columns, import and export web parts between pages, use rules for InfoPath forms, configure managed accounts, install prerequisites, and design logical and physical server topologies for SharePoint 2013.

1. ADVANCED SHAREPOINT SERVER CONCEPTS
Course: SharePoint 2013 for Administrators and IT Pro's | Akrura Technologies
By : Isha Kapoor
SharePoint MVP, Author, Trainer and Founder
http://www.akruratechnologies.com/
http://www.learningsharepoint.com/ | @LearningSP
SharePoint

2. OUTLINE…
• Calculated Columns
• Look up Columns
• ImportExport WebPart’s on a Page
• InfoPath Forms
• Before the Install :
 Accounts in SharePoint 2013
 SharePoint 2013 Prerequisites
 Logical and Physical Architectures

3. CALCULATED COLUMNS
What is a Calculated Columns?
Calculated Columns are a type of Columns that are Created in a list or library.
With Calculated Columns, you can create a formula that includes data from other columns and performs functions to calculate dates
and times, to perform mathematical equations, or to manipulate text.
Look at some Calculated Formulas at :
http://yalla.itgroove.net/2012/09/sharepoint-calculated-column-formulas/
http://sharepoint.rackspace.com/calculated-columns-tutorial
Some of the Columns that cannot be used with Calculated Columns are –
• Multiple Lines of Text
• Lookup & Lookup with multiple choice
• Person or a Group
• Choice Checkboxes
• Hyperlink
• Id

4. What are Lookup Columns?
To create a relationship between two lists, in the source list, you create a lookup column that retrieves (or "looks up") one or more
values from a target list.
Once you create this lookup column (the primary column), you can continue to add additional columns (secondary columns) from
the target list to the source list.
Enforce relationship behavior for Lookup Column? You can set up a two kinds of relationships for a Lookup column.
Cascade Delete - When an item in the target list is deleted, the related item or items in the source list are also deleted. In this
case, you want to make sure that all related items are deleted as part of one database transaction. For example, if you delete an
order in a target list, you can ensure that the corresponding order items in the source list is also deleted. You don't want to have
order items without a corresponding order, because that would create "orphan" order items that might cause confusion later on.
Restrict Delete - When you try to delete an item in the target list, and it has one or more related items in the source list, you
are prevented from deleting the item in the target list. In this case, you want to ensure that the related item in the target list is
preserved. For example, if someone tries to delete an order item from a target list, a customer might still have that order pending,
and you want to prevent that delete operation from occurring until the order has been processed. You don't want the customer’s
order to be accidentally deleted because that would affect your ability to complete the order.
When you try to delete a source or target list item that does not have an enforced relationship, then the following occurs:
You can remove the item from the source or target list.
The related item in the target or source list is not deleted.
LOOKUP COLUMNS

5. IMPORTEXPORT WEBPART’S ON A PAGE
ImportingExporting WebParts - To save the web part and use it again, you must export the web part and then import it to the other page.
Following is the process to do that.
Export a Web Part - Exporting a web part involves saving the web part’s settings as a file to your computer.
Note : Not all web parts support this option, and in some web parts, the owner of the page may choose to disable this option.
Import a Web Part –
1. To import a web part that you have previously saved to your computer, open the page in editing mode and click the page properties ->
Import webpart.
2. When the dialog with the list of files appears, select a web part from your computer and the upload it.
3. Finally drag and drop the webpart onto the page.
When you select the webpart to be added to the page , the Webpart gets added in a WebPart gallery.

6. INFOPATH FORMS
What are InfoPath Forms?
Microsoft InfoPath is a Tool launched by Microsoft to create Custom Forms that are Published in a SharePoint site.
By default, SharePoint uses InfoPath forms for it’s Out of box features like Approval Workflows etc. You can customize these forms or can
replace them with your own using the InfoPath form designer.
What is InfoPath Form Services?
InfoPath Forms Services is a server technology that makes it possible for people to fill out forms in a Web browser.
With InfoPath Forms Services, Users don't have to have InfoPath installed on their computer to fill out a browser-enabled form template, nor
are they required to download anything extra from the Web. All they need is access to a browser, such as Windows Internet Explorer, Apple
Safari, or Mozilla Firefox etc.
InfoPath Rules : The following three types of rules are available:
Validation - Validation rules are used to indicate an error when the user enters an invalid value into a control. For example, a validation rule
on a text box can confirm that a user enters a valid e-mail address. For more information regarding validation rules, see Add rules for data
validation.
Formatting - Formatting rules are used to apply text formatting and background shading to controls when a condition has been met. They
can also be used to hide or disable a control. For example, a formatting rule can hide or display follow-up questions based upon a user’s
answer to a preceding question, instead of including instructions for the user to “skip to step X.” For more information regarding formatting
rules, see Add rules for conditional formatting.
Actions - Actions are the most varied type of rule. Use these to switch views, set values in other fields, submit the form, or query for data.
Actions are available depending on what you are trying to apply them to and whether you are building a browser form or an InfoPath Filler
form. For more information regarding rules that perform other actions, see Add rules for performing other actions.

7. MANAGED ACCOUNTS IN SHAREPOINT 2013
What are Managed Accounts? Managed accounts allow administrators to maintain Windows system accounts, in use by
SharePoint, in a central location. Thus, if you need to change SharePoint to use a different service account, you have to change
it in only one place in Central Administration, and not across various services and applications (except for a few rare
circumstances). Managed accounts also allow SharePoint to manage password change, enforced by Domain Group Policy.
SharePoint requires several Managed Accounts or Service Accounts to be Created before you start the installation.
To create managed accounts go to Central admin -> Security -> Register Managed Accounts.
The first setup account (account used to install SharePoint) will be added by default.

8. SHAREPOINT 2013 PREREQUISITES
SharePoint 2013 Prerequisites - The SharePoint 2013 prerequisite installer (prerequisiteinstaller.exe) installs the following
software, if it has not already been installed on the target server, in this order:
• Microsoft .NET Framework version 4.5
• Windows Management Framework 3.0
• Application Server Role, Web Server (IIS) Role
• Microsoft SQL Server 2008 R2 SP1 Native Client
• Windows Identity Foundation (KB974405)
• Microsoft Sync Framework Runtime v1.0 SP1 (x64)
• Windows Identity Extensions
• Microsoft Information Protection and Control Client
• Microsoft WCF Data Services 5.0
• Windows Server AppFabric
• Cumulative Update Package 1 for Microsoft AppFabric 1.1 for Windows Server (KB 2671763)

9. LOGICAL AND PHYSICAL ARCHITECTURES
Logical Architecture - The logical result of SharePoint 2013's flexibility and richness can be a high degree of complexity around installing
and configuring SharePoint 2013 correctly. A fundamental understanding of the following key structural elements in a SharePoint 2013
environment is required in order to correctly deploy and support SharePoint 2013:
Server farm: The top-level element of a logical architecture design for SharePoint 2013.
Web application: An IIS Web site that is created and used by SharePoint 2013.
Content database: Provides storage Web application content. You can separate content into multiple content databases at the site
collection level.
Site collection: A set of Web sites that have the same owner and share administration settings.
Site: One or more related Web pages and other items (such as lists, libraries, and documents) that are hosted inside a site collection.
Physical architecture -
The physical architecture, which consists of one or more servers and the network infrastructure, enables you to implement the logical
architecture for a SharePoint 2013 solution.
The physical architecture is typically described in two ways: by its size and by its topology.
 Size, which can be measured in several ways, such as the number of users or the number of documents, is used to categorize a farm as
small, medium, or large.
 A small server farm typically consists of at least two Web servers and a database server. One of the Web servers hosts the
Central Administration site and the other handles additional farm-related tasks, such as serving content to users.
 A medium server farm typically consists of two or more Web servers, two application servers, and more than one database
servers. We recommend that you start with the preceding configuration and then scale out to accommodate the workload placed on
the servers.

10.  A large server farm can be the logical result of scaling out a medium farm to meet capacity and performance requirements or by design
before a SharePoint 2013 solution is implemented. A three-tier topology environment typically uses dedicated servers on all the tiers.
Additionally, these servers are often grouped according to their role in the farm. For example, all client-related services can be grouped
onto one or two servers and then scaled out by adding servers to this group as needed in response to user demand for these services.
 Topology uses the idea of tiers or server groups to define a logical arrangement of farm servers.
 In a single-tier deployment, SharePoint 2013 and the database server are installed on one computer.
 In a two-tier deployment, SharePoint 2013 components and the database are installed on separate servers. This kind of deployment
maps to what is called a small farm. The front-end Web servers are on the first tier and the database server is located on the second tier.
In the computer industry, the first tier is known as the Web tier. The database server is known as the database tier or database back-end.
 In a three-tier deployment, the front-end Web servers are on the first tier, the application servers are on the second tier, which is known
as the application tier, and the database server is located on the third tier. A three-tier deployment is used for medium and large farms.

11. WE ARE HERE TO
HELP.
Questions?