New improvements in search results page:

You have everything ready for search lets start searching. Open the Enterprise Search center site collection.

New Improvements in Search results page are:

See the below Figure where you have different options to search like.

• Everything
• People
• Conversations
• Videos
• Reports

Below one is a basic search site, these options will be available in enterprise search as well. You can observe that under Result Type:1 you can search based on document type like PDF, web page, word etc.

Next one is based on Author:2 who created the document.

Third one is based on Modified date 3: where you can change the search results based on date can be changed using slider.

The options for slider are one year ago, one month ago, one week ago.

Once you select the document from the search results small popup opens where you can see

• Document name
• Document type
• Last modified
• Contributor

There are three more options to Open, send via email and View library to see the details of the library where the document or item stored.

No more PDF Ifilters:

You don't need to install the PDF Ifilter and make a lot of settings to search PDF documents in SharePoint 2013.

That will take care by SharePoint 2013 now, Please see above Figure, where i have uploaded a PDF document and it displayed for users without doing any configuration or settings. 

Conclusion:

We have created the Search service application, created the accounts required to create it and we have seen how search administration page looks and what are the new changes in Search topology. Then we created the Content source, while creating it we have seen new option called "Enable Continuous crawl", then we created the Search center and what are the new changes in search results page.

Hope this post is useful to start the basic search configuration for your farm environment.

In coming posts we will see more about search changes in SharePoint 2013.

Enjoy the SharePoint search features provided in SharePoint 2013.

Search Service Application Configuration in SharePoint 2013-Part 2

Search  Service Application Configuration in SharePoint 2013-Part 2

Configure a Search service application in SharePoint Server 2013

In this session, we have to follow the following main tasks:

1. Create accounts - certain domain user accounts are required specifically for a Search service application.
2. Create a Search service application - A Search service application provides enterprise search features and functionality.
3. Configure the Search service application - Basic configuration of a Search service application includes configuring a default content access account, an email contact, and content sources.
4. Configure the Search service application topology - you can deploy search components on various servers in the farm. You can also specify which instance of SQL Server is used to host the search-related databases.

Create accounts that are required for a SharePoint Search service application

The following table lists the accounts that are required when a Search service application is created.

To register a managed account

Use the following procedure to register a managed account:

1. On the "Central Administration" home page, in the "Quick Launch", click "Security".

2. On the Security page, in the "General Security" section, click "Configure managed accounts".
3. On the "Managed Accounts" page, click "Register Managed Account".

4. On the "Register Managed Account" page, in the "Account Registration" section, type the user name and password that you want to use as credentials for the service account.

5. If you want SharePoint Server 2013 to manage password changes for this account, select the "Enable automatic password change" check box and configure the parameters for automatic password change.
6. Click OK.

Create a SharePoint Search service application

Each Search service application has a separate content index. You can create multiple Search service applications if you want to have various content indexes for various sets of content. For example, if you want to segregate sensitive content (such as employee benefits information) into a separate content index, you can create a separate Search service application to correspond to that set of content.

How to create a Search Service application

Use the following procedure to create a Search Service application:

1. Verify that the user account that is performing this procedure is a member of the Farm Administrators group for the farm for which you want to create the service application.
2. On the "Central Administration" home page, in the "Application Management" section, click "Manage service applications".

• In the "Manage Service Applications" page, on the ribbon, click "New", and then click "Search Service Application".

On the Create New Search Service Application page, do the following:

3. Accept the default value for the "Service Application" name, or type a new name for the Search Service application.

In the "Search Service Account" list, select the managed account that you registered in the previous procedure to run the Search service.

In the "Application Pool for Search Admin Web Service" section, do the following:

4. Select the "Create new application pool" option, and then specify a name for the application pool in the"Application pool name" text box.

5. In the "Select a security account for this application pool" section, select the "Configurable" option, and then from the list select the account that you registered to run the application pool for the Search Admin Web Service.

6. In the "Application Pool for Search Query and Site Settings Web Service" section, do the following:
7. Choose the "Create new application pool" option, and then specify a name for the application pool in the"Application pool name" text box.
8. In the "Select a security account for this application pool" section, select the "Configurable" option, and then from the list select the account that you registered to run the application pool for the Search Query and Site Settings Web Service.
9. Click "OK".

Configure the SharePoint Search service application

You configure a Search service application on the Search Administration page for that service application. Use the following procedure to go to the Search Administration page for a particular Search service application.

1. Go to the Search Administration page
2. Verify that the user account that is performing this procedure is an administrator for the Search service application that you want to configure.

3. Please add the administrator account on the next screen.

4. On the home page of the Central Administration website, in the Application Management section, click Manage service applications.
5. On the Manage Service Applications page, click the Search service application that you want to configure.

On the Search Administration page, configure the settings as described in the following sections:

• Specify the default content access account
• Specify the contact email address 
• Create content sources

Specify the default content access account

When you create a Search service application, the account that you specify for the Search service is automatically configured as the default content access account. The crawler uses this account to crawl content that does not have an associated crawl rule that specifies a different account. For the default content access account, we recommend that you specify a domain user account that has read access to as much of the content that you want to crawl as possible. You can change the default content access account at any time. If you have to crawl certain content by using a different account, you can create a crawl rule and specify a different account for crawling.  For information about how to create a crawl rule, see "Manage crawl rules" (SharePoint Server 2013 Preview).

Use the following procedure to specify the default content access account.

Specify the default content access account

Use the following procedure to specify the default content access account:

1. On the "Search Administration" page, in the "System Status" section, click the link in the default content access account row.
2. In the "Default Content Access Account" dialog box, in the "Account" box, type the account that you created for the content access in the form domain\user name.
3. Type the password for this account in the "Password" and "Confirm Password" boxes.
4. Click "OK".

Specify the contact email address

The Search service writes the contact email address to the logs of the crawled servers. The default contact email address, someone@example.com, is a placeholder. We recommend that you change this to an account that an external administrator can contact when a crawl might be contributing to a problem such as a decrease in performance on a server that the search system is crawling.

Specify the contact email address

Use the following procedure to specify the contact email address:

1. On the "Search Administration" page, in the "System Status" section, click the link for the contact e-mail address.
2. In the "Search E-mail Setting" dialog box, in the E-mail Address box, type the email address that you want to appear in the logs of servers that are crawled by the search system.
3. Click "OK".

Configure Content Source

Use the following procedure to configure the content source:

1. Click on the content source on the right side as shown below:
   
   
2. Click on the Edit as shown below for the Local SharePoint Sites:
   
   
3. Please make sure you have added your site URL in the following rectangular space with each site in a separate new line.
4. Please configure an incremental crawl and a full crawl.
   
   
5. Once you are done with the steps above, please start a full crawl.
6. Please wait until the crawl is over. It will take some time to finish the crawl.
   
   
7. You can click on the Crawl Log and you will see the contents that were crawled, as in:
   
   
8. Now go to the site which we have added to the content source and enter something to search for as shown below:
   
   
9. You will see the results once the search button is clicked, as in:
   
   
10. We even can now apply filters with a progress bar. That's a Great thing. When you wait on a searched element, you will even be prompted by a new great tool where you can: 

• Open the searched element
• View the library
• Send the searched element.
  
  

Search Service Application Configuration in SharePoint 2013-Part 1

Search  Service Application Configuration in SharePoint 2013-Part 1


In this article we can learn how to configure SharePoint 2013 Search. In SharePoint 2013 the two search engines "SharePoint Search" and "FAST Search Server for SharePoint" was combined into one Search Engine. Much of the search enhancement is due to Analytics moving into search. This will make an Analytics Processing Component in SharePoint Server 2013 run various analytics jobs to analyze content in the search index and user actions that were performed on a site to identify items that users perceive as more relevant than others.....

Search components

 

Search databases

Crawl component

The crawl component crawls the content sources. You can crawl a wide variety of content sources, for example file shares, SharePoint content, line of business applications and many more. To retrieve information, the crawl component connects to the content sources by invoking the appropriate indexing connector or protocol handler. After retrieving the content, the crawl component passes crawled items to the content processing component.

Content processing component

The content processing component processes crawled items and sends these items to the index component. The content processing component performs operations such as document parsing and property mapping. It also performs linguistics processing such as language detection and entity extraction. The component transforms crawled items into artifacts that are included in the search index. The content processing component also writes information about links and URLs to the link database. In turn, the analytics processing component writes information related to the relevance of these links and URLs to the search index through the content processing component.

Analytics processing component

The analytics processing component analyzes crawled items, which is referred to as search analytics, and how users interact with search, which is referred to as usage analytics. Examples of search analytics are links, anchor texts and metadata. An example of usage analytics is the number of times an item is viewed. The analytics processing component analyzes search analytics and usage analytics. Search analytics information is stored in the link database and usage analytics information in the analytics reporting database.

Index component

The index component is the logical representation of an index replica. In the search topology, you have to provision one index component for each index replica. The index component receives processed items from the content processing component and writes those items to an index file. Index files are stored on a disk in an index replica. The index component receives queries from the query processing component and returns result sets. You can divide the search index into discrete portions, called index partitions. Each index partition holds one or more index replicas. The search index is the aggregation of all index partitions.

Query processing component

The query component analyzes and processes queries and results. When the query processing component receives a query, it analyzes and processes the query to optimize precision, recall and relevance. The processed query is submitted to the index component. The index component returns a result set based on the processed query to the query processing component, which in turn processes that result set, before returning it to the front-end.

Search administration component

The search administration component runs the system processes for search. This component performs provisioning, which is to add and initialize instances of the other search components.

Crawl database

 The crawl database stores tracking information and details about crawled items. For example, it stores information about the last crawl time, the last crawl ID and the type of update during the last crawl.

Link database

The link database stores information extracted by the content processing component. It also stores information about the number of times people have clicked on a search result. The information is stored unprocessed; the analytics processing component performs the analysis.

Analytics reporting database

The analytics reporting database stores the results of usage analytics and extracts information from the link database when it is required.

Search administration database

The search administration database stores search configuration data and the access control list (ACL) for the crawl component. There can be only one search administration database per search service application.

Tabbed View Report using SSRS

Tabbed View Report using SSRS

Scenario Explained in the article:

Suppose take an example employee database which stores their professional summary, salary information, personal information, etc. The end user will search for an Employee by Emp ID as the parameter only one time and the result will be displayed in a tabbed view like professional summary in one tab, salary in another tab and personal information in another tab. Each tab should be clickable and when a Tab1 is clicked, other Tab result should be hidden. In the similar way, show and hide data should work for all the other tabs.

Tabbed View Report using SSRS

Introduction

SQL Server Reporting Services (SSRS) is an excellent reporting tool for various business needs. It provides a unified, server-based, extensible, and scalable platform from which to deliver and present information. Its scope extends from traditional paper reports to web-based delivery and interactive content. This article will explain about creating a SSRS report with tabbed view. Tabbed controls are not available as out of the box controls in SSRS report builder.

---

Scenario

Suppose take an example employee database which stores their professional summary, salary information, personal information, etc. The end user will search for an Employee by Emp ID as the parameter only one time and the result will be displayed in a tabbed view like professional summary in one tab, salary in another tab and personal information in another tab. Each tab should be clickable and when a Tab1 is clicked, other Tab result should be hidden. In the similar way, show and hide data should work for all the other tabs.

It will be cool to implement this feature in SSRS without writing single line of code. Let's implement it!

---

Prerequisites

1. SSRS installed in SharePoint Integrated Mode (you can choose SSRS in SQL native mode as well)
2. Sample Database (I will use Adventure Works DW 2012 database, "DimEmployee" table)
3. Report Builder for designing the report 

---

Solution

Open the report builder, create data connection to the Adventure Works DW 2012 database and create a data set as shown below: 

The SQL code used in the dataset is:

/****** Script for SelectTopNRows command from SSMS  ******/

 

DECLARE @EMPLOYEE_ID AS VARCHAR(20)

SET @EMPLOYEE_ID = '690627818'

 

SELECT EmployeeNationalIDAlternateKey

      ,SalesTerritoryKey

      ,FirstName

      ,LastName

      ,MiddleName

      ,Title

      ,HireDate

      ,BirthDate

      ,LoginID

      ,EmailAddress

      ,Phone

      ,MaritalStatus

      ,EmergencyContactName

      ,EmergencyContactPhone

      ,SalariedFlag

      ,Gender

      ,PayFrequency

      ,BaseRate

      ,VacationHours

      ,SickLeaveHours

      ,CurrentFlag

      ,SalesPersonFlag

      ,DepartmentName

      ,StartDate

      ,EndDate

      ,Status

  FROM AdventureWorksDW2012.dbo.DimEmployee

  WHERE EmployeeNationalIDAlternateKey = @EMPLOYEE_ID

Comment the variable declaration and assignment while adding to the dataset in report builder. When you comment the variable declaration and assignment and save the dataset, it will automatically create the parameter in the Parameters section. Create another parameter named “ActiveTab” with Integer as Data Type which is hidden parameter and it will be used to store the value of the tab which is active in the report. Set the default value to “1” for this parameter. 

         
 
        
Let’s add two images (Unselected Tab and Selected Tab) in the images section for adding it for the Tab backgrounds.

 

Now, the report data in the designer should look this:

Let’s create three tabs for this example:

1. Tab1 –Personal Info (First Name, Middle Name, Last Name, DOB, Email Address, Phone, Marital Status, Phone, Emergency Contact)
2. Tab2 –General Info(Sales Territory Key, Title, Hire Date, Login ID, Department Name )
3. Tab3 –Pay Info(Base Rate, Pay Frequency, DOJ)   Note: If you have more than one dataset, you can display different datasets in different tabs with the Employee ID as the primary key in all datasets. To illustrate the example, I am using a single dataset

 Add a rectangle in the report design and then add three text boxes within it. In each text box – Background Image property, add the below expression as the value. If the tab is active, then the tab should highlight with Selected Tab Image and others should be Unselected Tab Image. Follow the same steps for the other two text boxes. 

IIF(Parameters!ActiveTab.Value=1,"SelectedTab","UnselectedTab")

IIF(Parameters!ActiveTab.Value=2,"SelectedTab","UnselectedTab")

IIF(Parameters!ActiveTab.Value=3,"SelectedTab","UnselectedTab")

In the same way, add the following expression for color:

IIF(Parameters!ActiveTab.Value=1,"White","Black")

IIF(Parameters!ActiveTab.Value=2,"White","Black")

IIF(Parameters!ActiveTab.Value=3,"White","Black")


To make Personal Info tab clickable, click on Personal Info properties -> Action -> Change action options -> Go to report -> Specify the report name (in my case it is EmployeeSearch).  

Then add two parameters one is Active Tab with the value as ‘1’ and other Employee ID with Employee ID parameter created as shown below:

 

Follow the same steps for the other two tabs with Active Tab values 2 and 3.Now, add the data for the tab 1. Insert a rectangle and add the data for tab 1. In the same way, add the data for tab 2 and 3 respectively. The entire design will look as shown below: 


If you run the report by entering the Emp ID in the search parameter, it will display all the grids in a same page as shown below:

 

We need to add an expression in each grid to hide and show the grids depending upon the selected tab. Click on the first grid and select properties and add the following expression for hide and show as shown below: 

All the three expressions are as follows: 

IIf(Parameters!ActiveTab.Value=1,False,True)

IIf(Parameters!ActiveTab.Value=2,False,True)

IIf(Parameters!ActiveTab.Value=3,False,True)

Let’s format the report and now search for an EMP ID:

---

Conclusion

Not a single piece of code is written but we were able to create a tabbed view of data in SSRS. Cool isn’t it? This shows one of the capabilities of SQL Server Reporting Services (SSRS) in Business Intelligence.

If the data is from different data sources / business objects, then this solution will be more powerful. 

---

Downloads

1. Adventure Works Database download link 
2. Report ".rdl" file