Monday, 2 March 2015

SharePoint 2013 Cross-Site Publishing(XSP)

SharePoint 2013 Cross-Site Publishing Overview: Part 1

What is XSP:
simple manner you write content in one place and have it published somewhere else

Cross-Site Publishing is very simple publishing is a feature driven method that lets you create and maintain content in one or more authoring site collections or web application and publish or display this content in one or more publishing site collections by using content Search Web Parts.
 Cross-site publishing complements the already existing publishing method, author-in-place, where you use a single site collection to author content and make it available to readers of your site.
In this post, I introduce the concepts behind XSP. In my next blog post,will do the configuration steps.


Quick Understanding about XSP

         An authoring site(Product Site) is where authors go to create and host content; think of it as the source in XSP. This is where a list that is marked as a catalog lives.
  • A catalog is an attribute that you can add to a list or a library in the authoring site. Marking a list or a library as a catalog makes the content easily accessible to other site collections.
  • Search is the engine that connects your catalog to a publishing site.
  • The term store holds metadata terms that are used to organize content for publishing on target sites.
  • A publishing site is where visitors go to see and read content & where the content needs to be publish.


Managed Navigation is a feature beyond the scope of this blog post, but to understand how the Term Store fits into this picture, its use should be briefly described.
To organize the content on the authoring site, a managed metadata site column is used to categorize the articles by type.
These tagging terms are used on the publishing side to build up a navigation structure and as part of the search query that is used to pull the article data.





How the cross-site publishing works
Cross-site publishing uses search technology to retrieve content.

  • On a site collection where the Cross-Site Collection Publishing feature is enabled, libraries and lists have to be enabled as catalogs before the content can be reused in other site collections.
  • The content of the library or list catalogs must be crawled and added to the search index.
  • The content can then be displayed in a publishing site collection by using one or more Search Web Parts.
  • When we are changing the content in an authoring site collection, those changes are displayed on all site collections that reuse this content, as we are using continuous crawl.

High Level Architecture for XSP:
Why XSP:
Let us assume the content authors can add content in a controlled environment, meaning they can add the content in authoring site which is AD authenticated. Let us name it https://gowthamproduct.
This content is shared or displayed in Published sites web application which is configured to allow anonymous access for external users. Let us name it https://gowthampublish
By the  time your goin to create another web application where you can store your site assets like images and videos. Now this web application allows read access to anonymous user while it requires authentication for modifying/adding contents. Let us name it https://gowthamelectronics


 
      
·          
· Imagine that you’re working on a small number of sites that all need to show content from a common library.
For example, my company team  created their Internet site for the india , but they  also want to put up a site in Europe.
 XSP can be used to author in one place, and then present the content in many other locations, too!



 



SharePoint 2013 Cross-Site Publishing Overview: Part 1

What is XSP:
simple manner you write content in one place and have it published somewhere else

Cross-Site Publishing is very simple publishing is a feature driven method that lets you create and maintain content in one or more authoring site collections or web application and publish or display this content in one or more publishing site collections by using content Search Web Parts.
 Cross-site publishing complements the already existing publishing method, author-in-place, where you use a single site collection to author content and make it available to readers of your site.
In this post, I introduce the concepts behind XSP. In my next blog post,will do the configuration steps.


Quick Understanding about XSP

         An authoring site(Product Site) is where authors go to create and host content; think of it as the source in XSP. This is where a list that is marked as a catalog lives.
  • A catalog is an attribute that you can add to a list or a library in the authoring site. Marking a list or a library as a catalog makes the content easily accessible to other site collections.
  • Search is the engine that connects your catalog to a publishing site.
  • The term store holds metadata terms that are used to organize content for publishing on target sites.
  • A publishing site is where visitors go to see and read content & where the content needs to be publish.


Managed Navigation is a feature beyond the scope of this blog post, but to understand how the Term Store fits into this picture, its use should be briefly described.
To organize the content on the authoring site, a managed metadata site column is used to categorize the articles by type.
These tagging terms are used on the publishing side to build up a navigation structure and as part of the search query that is used to pull the article data.





How the cross-site publishing works
Cross-site publishing uses search technology to retrieve content.

  • On a site collection where the Cross-Site Collection Publishing feature is enabled, libraries and lists have to be enabled as catalogs before the content can be reused in other site collections.
  • The content of the library or list catalogs must be crawled and added to the search index.
  • The content can then be displayed in a publishing site collection by using one or more Search Web Parts.
  • When we are changing the content in an authoring site collection, those changes are displayed on all site collections that reuse this content, as we are using continuous crawl.

High Level Architecture for XSP:
Why XSP:
Let us assume the content authors can add content in a controlled environment, meaning they can add the content in authoring site which is AD authenticated. Let us name it https://gowthamproduct.
This content is shared or displayed in Published sites web application which is configured to allow anonymous access for external users. Let us name it https://gowthampublish
By the  time your goin to create another web application where you can store your site assets like images and videos. Now this web application allows read access to anonymous user while it requires authentication for modifying/adding contents. Let us name it https://gowthamelectronics



 
      
·          
· Imagine that you’re working on a small number of sites that all need to show content from a common library.
For example, my company team  created their Internet site for the india , but they  also want to put up a site in Europe.
 XSP can be used to author in one place, and then present the content in many other locations, too!



 

Image Renditions-Sharepoint2013

Image Renditions
·         Image renditions are new to SharePoint 2013 publishing sites,
·         Customize the appearance of an image and save that customization as a template.
·         You can upload a large photo to your SharePoint image library and ensure that it is always a given size on a given page, display template, search result etc.
·         The best reason to use renditions is instead of using CSS where a 3mb image after it is resized, it is still a 3mb in size.
·         Using renditions SharePoint will resize your image and create a new file, therefore your 3mb 1680×1050 resized to 100×62 could end up being 22kb, which is a lot better for a web image.
Prerequisite:
·         A SharePoint Server site with the publishing features activated
·         A picture library to test in. You can use the default Images library, or you can create a new picture library from Settings > Site contents > Add an app
·         Blob Caching needs to be turned on in your web.config file (so you will need access to the server SharePoint is installed on)
·         Steps to Create a New Image rendition size,
site settings->Look and Feel->Image Renditions
·         The page you will be taken to will probably have a few renditions on the page.
·          As you can see from my screen shot, they have an ID, Name, Width and Height. When you upload a picture to the image library, SharePoint will create 4 images, one for each rendition.
·          If there is a Width but no Height, SharePoint will ratio the height to the given width.


Sometimes it will show error in the site(Because of BLOB cache Disabled)

Steps to Enable the Blob Cache,
·         Go to web.config
·         Search for Blob Cache Section
·         Change the value of the attribute enabled to “true”

·         Save and close web.config and Refresh Image Rendition.
·         By default, there will be 4 predefined rendition configured on your SharePoint site.
 Create a new rendition, by adding new item link


·         To test the  image renditions, navigate to your picture library and upload a picture. Once the picture thumbnail shows in the library, hover over it, click the ellipsis in the bottom-right, and then click Edit Renditions.



My Sites-Configuration in SharePoint 2013


SharePoint 2013 major improvements are My Sites, User Profiles and news feeds. Here I will explain step-by-step process of setting up the my site Configuration in the SharePoint .
Prerequisites:
1. SharePoint 2013 installed on SharePoint server.
2. User Profile Configuration

Step1:Create a Separate Web Application for hosting My site
Go to the central administration->Application management->Manage web applications”

And create a dedicated web application (sd2013:101 in my example here)


Step2: Create a site collection in the root of the newly created web application
Site Collection must have “2013” experience and use “My Site Host” template.


Step3:Managed Paths
Once the  Site Collection creation has been completed click on the Managed Paths in the web application that you created to host My Sites.


Add a new managed path with wildcard inclusion.
Here we have  used “my” as the My Site managed path, but you can of course pick up anything else.

Step 4:Next click on Service Connections below Managed Paths.
There you need to make sure that the following is checked:
·         User Profile Service Application
·         Managed Metadata Service
·         Search Service Application



If you choose “Custom” (instead of the “Default”) in the Edit the following group of connections drop down, select any service applications to which you want to connect the web application.
Here We have selected as  “default”

Now setup self-service site creation also under the web app options
Go back to the Web application management, chose the application that you created to host My Sites, and click on the “Self Service Site Creation” button.

Click “On” in the “Site Collections” radio box, and enter your managed path in the “Start a Site” field (with “Prompt users to create a team site under” chosen)

step 5:Grant users permission to create new site collections (for my sites). Click on the “Permission Policy” button in the Web Application management, with the web application which hosts the my sites selected.

In the”Manage Permission Policy Levels”, click on the “Add Permission Policy Level”
Call it something like Mysite Creation.Grant Full Rights to "Create SubSites" and click on Ok.
·         Now you need to click on the user policy and then on add users.
·         Choose All Zones
·         On the next screen add the users you want to be able to create mysites. i Will use "Everyone"
·         Then check mySite Creation



·         And we need to grant that policy level to the users. Click on the “Users Policy” button in the Web Application management, with the web application that you created to host My Sites selected…

Click on the “Add users” link…


And select the users which you want to have rights to create my sites. On my case, it will be “Everyone”.


And now you should see “Everyone” with the new policy selected.


Step6: set up the my sites.
 Go to the Central Administration –> Application Management, and select “Manage service applications”.

Then select the “User Profile Service Application”

In the “User Profile Service Application”, click on “Setup My Sites”

STEP 7:setup the MySite Creation
In Central Admin go to Manage Service Applications -> User Profile Service Applications.
Then on "Setup My Sites"
Enter a preferred search center, My Site Host Location and personal Site Location ("My")
Step 8:Timer job feed activcation.
Go to the Central Administration –> Monitoring –>Timer Job –> Review job definitions

Find the “User Profile Service Application – Activity Feed Job”, and set up the activity feed sync timer according to your needs.






Click on Sites and you should get this. Go to the my site now and Enjoy the SharePoint .





Create Sites, Lists and Libraries in SharePoint 2016

Source:YouTube