Microsoft SharePoint 2013 -

Open Text Live LinkVerified Against Build #15.0.4128.1014Prepared by

Sriram BalaSharePoint

Practice

Authentication Methods 2

Table of ContentsOpen Text eDOCS Integration for Microsoft SharePoint..................................................................2Consolidate SharePoint content into a centralized system for content lifecycle, records management and archival............................................................................................................2

Benefits........................................................................................................................................ 2Solution Components...................................................................................................................2Features....................................................................................................................................... 2

Configure Federated Search to get results from remote/another SharePoint 2010 /2013 Farm.....2Steps to configure it: (To achieve this configuration, you need to member of Farm Administrator group).................................................................................................................... 2

How to configure the Search Results Web Part to use a new result source in SharePoint 2013.....2How to turn off versioning for the Pages library...........................................................................2Why you should consider creating a result source for your Search Center..................................2How to create a result source......................................................................................................2How to configure the Search Results Web Part to use a new result source.................................2

Open Text Live Link References......................................................................................................2

Authentication Methods 3

Open Text eDOCS Integration for Microsoft SharePoint

Consolidate SharePoint content into a centralized system for content lifecycle, records management and archival

OpenText eDOCS Integration for Microsoft® SharePoint® by SeeUnity Inc.enables organizations to capture content created in SharePoint so that it can be centrally managed in accordance with regulatory and business requirements.

With eDOCS Integration for SharePoint, companies can develop comprehensive compliance solutions governing electronic content, including email, file systems, and other record-generating environments, while ensuring litigation readiness and supporting discovery processes.

Many organizations deploy SharePoint in a decentralized, departmental manner, oriented toward meeting user requirements. OpenText effectively enables organizations to balance that equation, excelling at enterprise-focused and global deployments that accommodate the needs of corporate compliance and centralized IT, without compromising user productivity.

With the flexibility offered by eDOCS Integration for SharePoint, organizations can choose the ideal SharePoint user experience while having confidence that they have a central records management and archival system to manage business content.

Benefits

Archive Content Interactively or Automatically

Control Content Lifecycle with eDOCS Records Management

Easily Adapt to Distributed and Changing Environments

Solution Components

OpenText eDOCS DM Extensions for Microsoft SharePoint – This product provides a series of Web Parts that allow a SharePoint user access into one or more eDOCS libraries.  The Web Parts can be configured in a variety of ways to optimize how content is displayed to the user.  This product also provides eDOCS Profile and Full-Text search capability from SharePoint.

Authentication Methods 4

OpenText eDOCS Integration for Microsoft SharePoint – This product provides all of the functionality of the DM Extensions for SharePoint, plus it adds an additional feature set that includes bi-directional synchronization of content between SharePoint and eDOCS.

OpenText Content Migrator for eDOCS – This product allows for migration of content from and to OpenText Content Server, OpenText eDOCS, and Microsoft SharePoint.  The migration tool allows administrators to quickly and efficiently move documents between these content repositories, as needed, to serve the given business need.

Features

Supports Microsoft SharePoint 2010, Microsoft SharePoint 2007, and Microsoft SharePoint 2003

Ensure tamper-proof storage: Robust authentication capabilities, including time stamps and system signatures, mean that you can not only be confident that enterprise content is genuine and accurate, but you can prove it.

Safeguard content for disaster recovery: Ensure that business-critical content is stored safely in multiple physical locations. Specify heightened security requirements for specific documents.

Provide immediate information access with powerful federated search: Extend SharePoint search, enabling users to simultaneously search across active content in SharePoint databases as well as archived records within eDOCS. A consolidated result list separates according to online or archived storage, enabling users to quickly identify which documents are in a final state and have been archived.

Ensure preservation of discoverable records: Apply a hold to the record, or to multiple records at once from the search results page. Applying a hold to a record freezes its lifecycle, and ensures that it cannot be deleted under any circumstances.

Integrate with other ECM systems: Make the most of existing investments by accessing advanced eDOCS ECM functionality—including document management, workflow, secure external collaboration, and reporting.

Single Version of the Truth: Using eDOCS Integration for SharePoint, users can gain access to a given document from any of a number of user experiences, SharePoint, directly from within Microsoft Office, Microsoft Outlook, from a Web Browser or even from within other line of business applications.

Authentication Methods 5

Configure Federated Search to get results from remote/another SharePoint 2010 /2013 Farm

Federated Search was introduced with an infrastructure update in MOSS 2007. Federated Search basically uses the index created by other search engine (in our case index created by SharePoint 2010 / 2013 Search). It supplies the keyword that you entered and gets the result from that Index.

Before I take you through the steps on configuration, let me talk about my lab setup. 2 SharePoint 2010 Farm (Farm A - sharepoint2010 2013, Farm B - sp2010 / 2013), 1 domain (contoso.com) -> A simple lab setup.

My Expectation: when I search in Farm A, the search core results web part will display content/search results from Farm A, and in a Federated Results web part I will get results for the same keyword from Farm B.

Steps to configure it: (To achieve this configuration, you need to member of Farm Administrator group)

Step1: Go to Central Administration of Farm A. Click on Manage Service Application -> Search Service Application

Step2: Choose Federated Locations under Queries and Results.

Step3: Click on New Location.

Step4: Give a Location Name (without any spaces), display name, description and Author (optional)

Step5: Leave the version blank, Under the Trigger choose "Always: Query should always match".

Step6: In the Location type choose "OpenSearch 1.0/1.1", and in the Query template specify the template in the following format http://server/SearchCenter/_layouts/srchrss.aspx?k={searchTerms} .In my scenario is was http://sp2010:81/Search/_layouts/srchrss.aspx?k={searchTerms} (sp2010 is FARM B)

Authentication Methods 6

Step7: Leave rest of the things to default except the Specify Credentials section. Here choose he relevant one for your environment. I have chosen NTLM - Specify a surname and password under Common.

Step8: Click OK. Go your Enterprise Search Site in Farm A. Type in a keyword. When you get to the search results page, click on Site Actions and Edit Page.

Step9: When the page is changed to Edit Mode. Click on Add web part and choose Federated Results web part. It’s found under the Categories Search.

Step10: Once you have added the Federated Results Web part, choose the right Location by going to Edit Web part. Click Apply and OK.

There you have it!!.. Search results from two SharePoint 2010 / 2013 farms in a single search. You can add multiple federated results web part to get data from multiple SharePoint farms.

How to configure the Search Results Web Part to use a new result source in SharePoint 2013

Topics

How to turn off versioning for the Pages library Why you should consider creating a result source for your Search Center How to create a result source How to configure the Search Results Web Part to use a new result Source

 How to turn off versioning for the Pages library

If you don’t want to check pages in and out when you configure the Search Results Web Part, you can turn off versioning for the Pages library.

To turn off versioning for the Pages library:

1. Go to Site settings --> Site contents.2. On the Site Contents page, click the Pages library.3. In the Pages library, click the LIBRARY tab and then Library Settings.4. On the Settings page, click Versioning settings.5. On the Versioning Settings page, in the Content Approval section, for Require content

approval for submitted items, select No.

Authentication Methods 7

6. In the Document Version History section, for Create a version each time you edit a file in this document library, select No versioning.

7. In the Require Check Out section, for Require documents to be checked out before they can be edited, select No.

 

Why you should consider creating a result source for your Search Center

A result source specifies where your search results can come from.

For example, in my scenario, I did not want search results to come from all sites within the SharePoint farm. I only wanted search results from one specific site within the farm.

The default result source in a Search Center returns search results from the entire SharePoint farm. If you want search results from the entire SharePoint farm, you can skip to the next blog post in this series.  However, if you want search results from only a sub set within your SharePoint farm (in my scenario, one specific site), you should create a result source.

Authentication Methods 8

 

How to create a result source

Depending on your permission level, you create a result source on three levels:

Permission level Where the result source will be added

Search service application administrator

To all site collections within the farm

Site collection administrator To all sites within a site collection

Site collection owner To a single site

To save space, I will only show you how to create a result source as a Site collection administrator.

1. Go to Site settings --> Search Result Sources.2. On the Manage Result Sources page, click New Result Source.

3. On the Add Result Source page, enter a Name. Select values for Protocol and Type, and clickLaunch Query Builder. This will open a dialog box.

In my scenario, I named the result source Articles, and kept the default values for Protocol and Type.

Authentication Methods 9

4. In the Build Your Query dialog box, define the result source.

Remember, in my scenario, I only wanted search results to come from a particular site within the farm, so in the Query text field, I added the following:{searchTerms?} (contentclass:sts_listitem) path:http://<path>

Authentication Methods 10

Now, before we move on, let me break down what I entered:

{searchTerms?} In my result source, I wanted to include the words that users type in the query box whey then search for something. Obviously I have no way of knowing what users will type, so I added the query variable {searchTerms?} By the way, you can tell it’s a query variable because it’s enclosed in curly brackets.  When users enter a query, this query variable will be replaced by the words the users have typed in the query box. The question mark at the end of the variable means that if no words have been entered, the variable should be ignored.

(contentclass:sts_listitem)  This means that only list items will be included in my result source. path:http://<path>   This is the path to the site from where I wanted search results to come from.  

5. Test that the result source is working correctly by clicking on the TEST tab, and then Show more.

6. In the {searchTerms} field enter Query words to simulate a query entered by a user, and then click Test query.

In my scenario, I entered search configuration.

Authentication Methods 11

Notice that 52 results were returned (I will tell you why this is kind of cool in the next section…).

7. Click OK to close the dialog box, and then Save.

So now that we have a result source for the Search Center, we can move on to configuring the Search Results Web Part to use the new result source.

 

Authentication Methods 12

How to configure the Search Results Web Part to use a new result source

By default, the Search Results Web Part is used on the search results page. In order to configure theSearch Result Web Part, you have to navigate to the search results page.

1. On your Search Center home page (the default URL to this page is <site>/Pages/default.aspx), enter a query in the search box, and press Enter.

In my scenario, I entered search configuration.

When you press Enter, you will be taken to the to the search results page (the default URL to this page is <site>/Pages/results.aspx).

In my scenario, 1,051 search results were returned.

Authentication Methods 13

Remember, by default you’ll get search results from the entire SharePoint farm. To change this so that only search results from your newly created result source are returned, here’s what you should do:

2. On the search results page, click the Settings menu --> Edit Page.3. In the Search Results Web Part, click the Web Part Menu, and then Edit Web Part.

Authentication Methods 14

3. In the Web Part tool pane, click Change query. This will open a dialog box.

4. In the dialog box, from the Select a query menu, select your newly created result source.

In my scenario, I selected the Articles (Site Collection) result source.

Authentication Methods 15

5. Click OK in the dialog box, OK in the Web Part Tool pane, and then save the page. To verify that the configuration is working, enter a query.

In my scenario, I entered search configuration.

Authentication Methods 16

Authentication Methods 17

52 results were returned, which is the same number of items that was returned when I tested the query in the result source configuration. Cool, don’t you think?

Now that the Search Results Web Part displays the search results we are interested in, the next step is to make it easier for users to filter these search results. To do this, we'll use refiners, which is the subject of the next blog post. 

Open Text Live Link References

Open Text

http://www.opentext.com/What-We-Do/Industries/Legal/Legal-Content-Management-(eDOCS)/OpenText-eDOCS-Integration-for-Microsoft-SharePoint

Federated results webpart

Configure Federated Search to get results from remote/another SharePoint 2010 Farm

http://blogs.msdn.com/b/sharepoint__cloud/archive/2012/03/12/configure-federated-search-to-get-results-from-remote-another-sharepoint-2010-farm.aspx

How to configure the Search Results Web Part to use a new result source in SharePoint 2013

http://blogs.technet.com/b/tothesharepoint/archive/2013/11/06/how-to-configure-the-search-results-web-part-to-use-a-new-result-source-in-sharepoint-2013.aspx

Creating tabs for search

http://msdn.microsoft.com/en-us/library/ff513701.aspx