Configure Workflow Manager on a server that is NOT part of the SharePoint 2013 farm

Note: For configuring Workflow Manager on a server that is NOT part of the SharePoint 2013 farm, you must install the Workflow Manager Client on each server in the SharePoint farm before you run the pairing cmdlet.

For downloading and installing the Workflow Manager Client go here

To configure Workflow Manager on a server that is NOT part of the SharePoint 2013 farm and on which communication takes place by using HTTP

1. Log on to each server in the SharePoint Server 2013 farm.

2. Install the Workflow Manager Client on each server in the SharePoint farm.

3. Open the SharePoint Management Shell as an administrator. This is accomplished by right-clicking the SharePoint 2013 Management Shell command and choosing Run as administrator.

4. Run the Register-SPWorkflowService cmdlet. The cmdlet should be run only once and can be run from any of the servers in the SharePoint farm.

Register-SPWorkflowService -SPSite "http://myserver/mysitecollection" -WorkflowHostUri "http://workflow.example.com:12291" -AllowOAuthHttp

To configure Workflow Manager on a server that is NOT part of the SharePoint 2013 farm and on which communication takes place by using HTTPS

1. Determine whether you need to install Workflow Manager certificates in SharePoint 2013.

2. Log on to each server in the SharePoint Server 2013 farm.

3. Install the Workflow Manager Client on each server in the SharePoint farm.

4. Open the SharePoint Management Shell as an administrator. This is accomplished by right-clicking the SharePoint 2013 Management Shell command and choosing Run as administrator.

5. Run the Register-SPWorkflowService cmdlet.

Register-SPWorkflowService -SPSite "https://myserver/mysitecollection" -WorkflowHostUri "https://workflow.example.com:12290"

Reference

Configure Workflow Manager on a server that is part of the SharePoint 2013 farm

To configure Workflow Manager on a server that is part of the SharePoint 2013 farm and on which communication takes place by using HTTP

1. Log on to the computer in the SharePoint Server 2013 farm where Workflow Manager was installed.

2. Open the SharePoint Management Shell as an administrator. This is accomplished by right-clicking the SharePoint 2013 Management Shell and choosing Run as administrator.

3. Run the Register-SPWorkflowService cmdlet.

Register-SPWorkflowService -SPSite "http://myserver/mysitecollection" -WorkflowHostUri "http://workflow.example.com:12291" -AllowOAuthHttp

4. Log on to each server in the SharePoint Server 2013 farm. Each server in the SharePoint Server 2013 farm must have the Workflow Manager Client installed.

5. Install the Workflow Manager Client on each server in the SharePoint farm.

To configure Workflow Manager on a server that is part of the SharePoint 2013 farm and on which communication takes place by using HTTPS

1. Determine if you need to install Workflow Manager certificates in SharePoint.

2. Log into the computer in the SharePoint Server 2013 farm where Workflow Manager was installed.

3. Open the SharePoint Management Shell as an administrator. This is accomplished by right-clicking the SharePoint 2013 Management Shell and choosing Run as administrator.

4. Run the Register-SPWorkflowService cmdlet.

Register-SPWorkflowService -SPSite "https://myserver/mysitecollection" -WorkflowHostUri "https://workflow.example.com:12290"

5. Log on to each server in the SharePoint Server 2013 farm. Each server in the SharePoint Server 2013 farm must have the Workflow Manager Client installed.

6. Install the Workflow Manager Client on each server in the SharePoint farm.

For downloading and installing the Workflow Manager Client go here

Reference

Install and configure workflow for SharePoint Server 2013

1. Install and configure SharePoint Server 2013

2. Install and configure Workflow Manager

3. Configure Workflow Manager to work with the SharePoint Server 2013 farm

The following two key factors needs to be considered before configuring Workflow Manager to work with SharePoint Server 2013.

1. Is Workflow Manager installed on a server that is part of the SharePoint farm?

2. Will communication between Workflow Manager and SharePoint Server 2013 use HTTP or HTTPS?

These factors translate into four scenarios. Each scenario configures a SharePoint Server 2013 farm to communicate and function with the Workflow Manager farm.

1: Workflow Manager is installed on a server that is part of the SharePoint 2013 farm. Communication takes place by using HTTP.

2: Workflow Manager is installed on a server that is part of the SharePoint 2013 farm. Communication takes place by using HTTPS.

3: Workflow Manager is installed on a server that is NOT part of the SharePoint 2013 farm. Communication takes place by using HTTP.

4: Workflow Manager is installed on a server that is NOT part of the SharePoint 2013 farm. Communication takes place by using HTTPS.

Reference

SharePoint 2013 Crawl job will not stop

When you are unable to stop a crawl (full or incremental) using the Central Administration UI, you can try one of the below steps

Approach 1 (Restart Search services)

1. Stop and start the SharePoint Server Search 15 service

2. Go to services.msc -> SharePoint Server Search 15 -> Restart

Run the PowerShell script on the SharePoint server

Approach 2 (Using net start command)

net stop OSearch15

net start OSearch15

Approach 3 (Using PowerShell command)

Stop-Service -name OSearch15

Start-Service -name OSearch15

Approach 4 (PowerShell script to stop the SharePoint Crawl Job)

Add-PSSnapin "Microsoft.SharePoint.PowerShell"

Get-SPEnterpriseSearchCrawlContentSource -SearchApplication "Search Service Application" | ForEach-Object {

     if ($_.CrawlStatus -ne "Idle")

     {

         Write-Host "Stopping currently running crawl for content source $($_.Name)..."

         $_.StopCrawl()

       

         do { Start-Sleep -Seconds 1 }

         while ($_.CrawlStatus -ne "Idle")

     }

}

Approach 5 (Perform an Index rest)

Browse to Central Administration -> Search Service Application -> Crawling-> Index Reset -> Reset Now

Note: Resetting the crawled content will erase the content index. After a reset, search results will not be available until crawls have been run.