Install and configure the Workflow Manager for SharePoint 2013

SharePoint Server 2013 brings a major advancement to workflow: enterprise features such as fully declarative authoring, REST and Service Bus messaging, elastic scalability, and managed service reliability.

SharePoint Server 2013 can use a new workflow service built on the Windows Workflow Foundation components of the .NET Framework 4.5. This new service is called Workflow Manager and it is designed to play a central role in the enterprise. Processes are central to any organization and workflow is the orchestrator of processes.

The SharePoint 2010 Workflow platform has been carried forward to SharePoint Server 2013. All of your workflows that were built by using SharePoint Server 2010 will continue to work in SharePoint Server 2013.

In SharePoint Server 2010 the workflow engine installed automatically with the product. This continues to be the case with the SharePoint 2010 Workflow platform in SharePoint Server 2013. If you simply install SharePoint Server 2013 and do not install and configure Workflow Manager then you will have a nearly identical experience with building workflows as you did in SharePoint Server 2010.

The SharePoint 2013 Workflow platform only becomes available to you, and your tools, after you download and install the new Workflow Manager service and configure it to communicate with your SharePoint Server 2013 farm.

SharePoint Designer 2013 includes new functionality designed specifically for Workflow Manager. In SharePoint Designer 2013 this new platform is known as the SharePoint 2013 Workflow platform. These new features include:

  • A visual workflow development experience that uses a Visio 2013 add-in

  • A new action that enables no-code web service calls from within a workflow

  • New actions for creating a task and starting a task process

  • New coordination actions that let you start a workflow built on the SharePoint 2010 Workflow platform from a workflow built on the SharePoint 2013 Workflow platform

  • A new Dictionary type

  • New workflow building blocks such as Stage, Loop, and App Step

Workflow Manager brings a new class of workflow to SharePoint Server 2013. Workflows built by using Workflow Manager can take advantage of several new capabilities. These include enterprise features such as:

  • High Density and Multi-Tenancy

  • Elastic Scale

  • Activity / Workflow Artifact Management

  • Tracking and Monitoring

  • Instance Management

  • Fully Declarative Authoring

  • REST and Service Bus Messaging

  • Managed Service Reliability
    [Source]

*This configuration is for HTTP only. The HTTPS configuration will be covered in later posts.

*Note that the below result is also applicable to Project Server.
Download WorkflowManager.exe from go.microsoft.com/fwlink/?LinkID=252092 Click on the WorkflowManager.exe to setup by a Web Platform Installer 4.5

*This is the latest version at the time of writing. The below steps will be identical when a new version is released.

clip_image002

clip_image004

Workflow Manager

clip_image002[5]

Prerequisites for installing Workflow Manager

clip_image004[5]

Installing the Workflow Manager

clip_image005

clip_image007

clip_image008

Choose Configure Workflow Manager with Default Settings (Recommended)

image

Complete fields to indicate SQL server and generate a Certificate Key

Configuration for Workflow Manager information:

Configuration for Workflow Manager

Management Database SQL Instance        YourSQLServer

Enable SSL connection with SQL Server instance        False

Authentication        Windows Authentication

Management Database Name        WFManagementDB

Instance Management Database SQL Instance        YourSQLServer

Enable SSL connection with SQL Server instance        False

Authentication        Windows Authentication

Instance Management Database Name        WFInstanceManagementDB

Resource Management Database SQL Instance        YourSQLServer

Enable SSL connection with SQL Server instance        False

Authentication        Windows Authentication

Resource Management Database Name        WFResourceManagementDB

RunAs Account        yourdomain\User

RunAs Password        ***********

Certificate Generation Key        ***********

Workflow Manager Outbound Signing Certificate        Auto-generated

Service SSL Certificate        Auto-generated

Encryption Certificate        Auto-generated

Workflow Manager Management Port        12290

HTTP Port        Disabled

Enable firewall rules on this computer        True

Administrators Group        BUILTIN\Administrators

Configuration for Service Bus

Management Database SQL Instance        YourSQLServer

Enable SSL connection with SQL Server instance        False

Authentication        Windows Authentication

Management Database Name        SbManagementDB

Gateway Database SQL Instance        YourSQLServer

Enable SSL connection with SQL Server instance        False

Authentication        Windows Authentication

Gateway Database Name        SbGatewayDatabase

Message Container SQL Instance        YourSQLServer

Enable SSL connection with SQL Server instance        False

Authentication        Windows Authentication

Message Container Database Name        SBMessageContainer01

RunAs Account        yourdomain\User

RunAs Password        ***********

Certificate Generation Key        ***********

Farm Certificate        Auto-generated

Encryption Certificate        Auto-generated

HTTPS Port        9355

TCP Port        9354

Message Broker Port        9356

Internal Communication Port Range        9000 – 9004

Enable firewall rules on this computer        True

Administrators Group        BUILTIN\Administrators

image

clip_image001

Created and Configured Service Bus farm, Service Bus gateway and farm management database

clip_image002

clip_image003

Workflow Manager, Service Bus 1.0, Execute ASP.NET iis Registration tool and Workflow Client were successfully installed

image

Service Bus and Workflow database were created

image

WorkflowMgmtPool and Workflow Management Site

clip_image002[7]

Install Windows Azure SDK, PowerShell, Cross-platform Command Line Tools

clip_image004[7]

Items Installed.

Register Workflow:

Open Sharepoint management shell as administrator:

Register-SPWorkflowService –SPSite "http://YourSQLServer" –WorkflowHostUri "http://YourSQLServer:12291" –AllowOAuthHttp

image

Installation done.

To test, open SharePoint designer and connect to the SharePoint Site:

image

To verify, create a new site workflow. If the SharePoint 2013 workflow option is listed, then the installation was a success:

clip_image002[9]

And DONE!

Installing and configuring the Office Web Application (WAC) Server

Install Pre-Requisites
Run Powershell as Admin:

image

Enter the following command:

Add-WindowsFeature Web-Server,Web-Mgmt-Tools,Web-Mgmt-Console,Web-WebServer,Web-Common-Http,Web-Default-Doc,Web-Static-Content,Web-Performance,Web-Stat-Compression,Web-Dyn-Compression,Web-Security,Web-Filtering,Web-Windows-Auth,Web-App-Dev,Web-Net-Ext45,Web-Asp-Net45,Web-ISAPI-Ext,Web-ISAPI-Filter,Web-Includes,InkandHandwritingServices

image

The server configuration will now run.

image

When prompted, restart the computer

Install Office Web Application Server

clip_image002[5]

Run Setup

clip_image004

Accept the license agreement and click Continue

clip_image006

Select the installation directory and click Install Now

clip_image008

clip_image010

Configure Office Web Applications Server

clip_image002[7]

Open PowerShell and run as admin

Run the following commands:

1. Import-Module OfficeWebApps

2. Get-Command “*Office*”

The first command imports the OWA cmdlets, and the second verifies they are available for your use.

clip_image004[6]

Now, we can create the actual OWA server farm:

New-OfficeWebAppsFarm –InternalURL http://yourserver –AllowHttp -EditingEnabled

Let’s break down the New-OfficeWebAppsFarm parameter:

InternalURL : Use the FQDN of the server to run OWA

-AllowHttp : This command tells OWA which protocol to use when communication occurs between the two entities. HTTP can also be used, but it is recommended that it is used for Dev purposes.

-EditingEnabled : Allows documents to be edit using OWA

image

To verify if the OWA farm was built correctly, run the following command in Internet Explorer:

http://yourserver/hosting/discovery

Log into your server, and run the following PowerShell command.

New-SPWOPIBinding -ServerName <WacServerName> -AllowHTTP

The –ServerName is the FQDN of the OWA farm server you just created. It should be the same as the –InternalURL you used earlier. Don’t use ‘Http://’ in the server name parameter, just the FQDN of the server.

By default OWA server farm wants to use HTTPS. You can force it to recognize HTTP with the following PowerShell OWA command:

Set-SPWopiZone –zone “internal-http”

image

Change the AllowOAuthOverHttp setting in SharePoint 2013 to True

To use Office Web Apps with SharePoint 2013 over HTTP in a test environment, set AllowOAuthOverHttp to True. Otherwise Office Web Apps will not work. You can change the current status by running the following example:

(Get-SPSecurityTokenServiceConfig).AllowOAuthOverHttp

$config = (Get-SPSecurityTokenServiceConfig)

$config.AllowOAuthOverHttp = $true

$config.Update()

image

Test whether the installation was successful:

(Get-SPSecurityTokenServiceConfig).AllowOAuthOverHttp

You should receive the following output:

image

Finding the ISE (Windows PowerShell Integrated Scripting Environment) on windows 8

Sometimes scripts need to be created from your local computer and using the standard Powershell tool can be cumbersome and irritating.

The ISE (Windows PowerShell Integrated Scripting Environment) is a great tool for creating and executing scripts. It even provides intellisense. In Windows server 2012 it is easy to find. One can open the home screen and type ISE to find it. It will display it as a result immediately.

In Windows 8 however, one cannot find it in that way and you might get the impression that it is not available or installed. Luckily it is installed but not that easily found as in Server 2012.

To find and open the ISE, use Window-R and type “PowerShell ISE” to start the PowerShell ISE.

Untitled

Sharepoint 2013 Log in as a different user missing, a simple workaround.

In their infinite wisdom, Microsoft decided to remove the ‘sign in as another user‘ option from the UI. For consultants and developers who need to test their solutions in an ongoing manner, user accounts need to be switched in order to test the myriad of permission issues sometimes experienced by users.

After some extensive research I have found a solution:

Simply append the following behind your URL – /_layouts/closeConnection.aspx?loginasanotheruser=true

e.g http://yoursite/_layouts/closeConnection.aspx?loginasanotheruser=true

Voila! You can now carry on as usual.

A system restart from a previous installation or update is pending when installing SharePoint 2013

I recently came across this annoying issue when installing the SharePoint 2013 preview:

image

Even though all the pre-requisites have been installed, this error persists after numerous system reboots.

To cure this problem, a registry entry needs to be deleted. Ensure that a full system backup is performed prior to changing this registry setting.

The below fix should get you back on track in no time:

Open the Registry editor and find the following entry:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager
Rename the “PendingFileRenameOperations” value to “PendingFileRenameOperations2

image
Reboot the server and re-run the installation.

Hopefully Microsoft will have this issue sorted out by the time the full release is available.

Links to the SharePoint 2013 Pre-requisites

As you may know, SharePoint 2013 can be installed either on Server 2008 R2 or on Server 2012. If you choose to install SharePoint on Server 2008 R2, you will need to install pre-requisites as with SharePoint Server 2010.

Mostly when installing SharePoint at a client site, their servers do not have access to the internet and the prerequisiteinstaller.exe tool cannot be run to automatically download and install the pre-requisites. In this case, the pre-requisites need to installed offline.

If need be, this process can be automated using the following Powershell Script:

http://wellytonian.com/2012/07/sharepoint-2013-pre-requisites-downloader/

The download locations for the files are located on this Technet Article.

Below I have listed the complete list of the SharePoint 2013 pre-requisites:

Sources:
technet.microsoft.com

Olivier Carpentier’s Blog

The “Alert Me” button is not visible on the ribbon in SharePoint 2010

I recently came across an issue where a client’s “Alert Me” button was missing from the ribbon when opening lists and document libraries.

image

This is because the Outgoing Mail settings are not configured in the server farm. This should however not be the case if the farm has been set up correctly from the beginning. This must always be one of the first configurations to be done when a ne farm is configured.

To configure this, Open Central administration and edit the Settings under the System Settings heading.

image

Enter the relevant information in the fields displayed under the Configure outgoing e-mail settings:

image

Click ok and the Alert Me button will now be visible on the ribbon.