Nintex Workflow 2013 Installation Guide

8/20/2019 Nintex Workflow 2013 Installation Guide

1/39

Installation Guide:Nintex Workflow 2013 and

Nintex Forms 2013

Last updated Thursday, April 30, 2015


2/39

Legal Notices

For the latest information, please see http://en-us.nintex.com/company/legal.

© Copyright2015 Nintex UK Ltd. | Privacy Policy | Terms & Conditions | Cookie Preferences| Nintex Support

-i-

Installation Guide: Nintex Workflow 2013 and Nintex Forms 2013

http://www.nintex.com/EN-US/SUPPORT/Pages/default.aspxhttp://www.nintex.com/en-US/Pages/NintexCookies.aspxhttps://www.nintex.com/en-US/Pages/TermsAndConditions.aspxhttps://www.nintex.com/en-US/Pages/Privacy.aspxhttp://en-us.nintex.com/company/legal


3/39

Contents

Legal Notices i

Introduction 1

Print-outs 2

Installation checklist 2

Installation worksheet 3

Before you start 4

Plan your test and production environments 4

Obtain account with sufficient permissions 9

Obtain Nintex license files 10

Schedule deployment 11Install Nintex products to test environment and confirm 12

Install Nintex products to production environment 13

Run the installers 13

Deploy the solutions 15

Import the license files 17

Configure databases and other items 18

Connect and enable Nintex Live 23

Activate features in SharePoint 26

Confirm production installation 29

Test Nintex functionality 29

Confirm installer and configuration tasks (optional) 29Reinstate original server settings 31

Troubleshoot deployment 32

Identify the problem 32

Issues 33

Uninstall Nintex Workflow and Nintex Forms 36


-ii-


http://www.nintex.com/EN-US/SUPPORT/Pages/default.aspxhttp://www.nintex.com/en-US/Pages/NintexCookies.aspxhttps://www.nintex.com/en-US/Pages/TermsAndConditions.aspxhttps://www.nintex.com/en-US/Pages/Privacy.aspx


4/39

Introduction

This document provides guidance for installing the following Nintex products to yourSharePoint environment.

l Nintex Workflow 2013

l Nintex Forms 2013

l Nintex Live

The installation process involves planning your test and production environments,deploying to a test environment, confirming test deployment, deploying to production,and confirming production deployment.

Note: This guide is intended for brand-new installations of the listed products.For information on installing product updates or upgrading and migrating Nintexproducts, run this search on the Nintex Connect site.


-1-


http://www.nintex.com/EN-US/SUPPORT/Pages/default.aspxhttp://www.nintex.com/en-US/Pages/NintexCookies.aspxhttps://www.nintex.com/en-US/Pages/TermsAndConditions.aspxhttps://www.nintex.com/en-US/Pages/Privacy.aspxhttps://community.nintex.com/search.jspa?q=migration+upgrade+update+%22Nintex+Workflow%22+%22Nintex+Forms%22&type=document


5/39

Print-outs

Installation checklist 2

Installation worksheet 3

Installation checklistUse the following checklist to track your status in the installation process.

1. Plan

Plan your test and production environments

Obtain account with sufficient permissions

Obtain Nintex license files

Schedule deployment

2. Test

Deploy the solutions

Import the license files

Configure databases and other items

Connect and enable Nintex Live

Activate features in SharePoint

Confirm installation

3. Install


Import the license filesConfigure databases and other items

Connect and enable Nintex Live

Activate features in SharePoint

Confirm installation


-2-




6/39

Installation worksheetUse this worksheet to record locations of files and identifiers of servers used in install-ation.

Environment (Production / Test / Other): ______________________________________

Nintex Workflow

Files, account, and server used for running installer

Installer file location

License file locationUser account for install-ation processServer for runningNintex Workflow installer

Web applications

List each web application in the SharePoint farm that is expected to useNintex Workflow.

Databases

Nintex configuration databases:

Nintex configuration database name Failover database name Notes

Content databases:

Nintex content database name SharePoint content database name Notes

Global settings

Outbound SMTP Server

From Address

Reply to Address

Nintex Forms

Installer file location

License file locationUser account for install-ation processServer for runningNintex Forms installerNintex Forms databasename


-3-




7/39

Before you start

Before installing Nintex products, make sure your SharePoint environment is ready andthat all preparation is complete.

Plan your test and production environments 4

Obtain account with sufficient permissions 9

Obtain Nintex license files 10

Schedule deployment 11

Plan your test and production environmentsPlanning test and production environments involves meeting system requirements,reviewing topology considerations and best practices, setting up the topology for install-ation, and setting up the server to be used for running installers.

System requirements

Following are the system r equirements for Nintex Workflow and Nintex Forms.

Type Nintex Workflow 2013 Requirement

Operatingsystem

Microsoft Windows Server 2008 R2 or Microsoft Windows Server 2012(R2 is supported)

Browserclient

To design and run Nintex workflows, use the following browser versions.

l Minimum required: Microsoft Internet Explorer 8.x

l Recommended: Microsoft Internet Explorer 9 or greater

Software l Microsoft SharePoint Foundation 2013 or Microsoft SharePointServer 2013 (SP1 is supported)

Note: See the following Microsoft article. SharePoint 2013SP1 support in Windows Server 2012 R2.

l SQL Server 2008 R2 SP1, SQL Server 2012, or SQL Server 2014

Hardware Web servers: Nintex Workflow requires the same minimum requirementsthat are required when installing SharePoint 2013. See http://-technet.microsoft.com/en-au/library/cc262485.aspx .

Database servers: Nintex Workflow requires the same minimum require-ments that are required when installing SharePoint 2013. See http://-technet.microsoft.com/en-au/library/cc262485.aspx#section3 . Hard diskspace is dependent on the Nintex database growth rate. This rate isaffected by the following:

l The number of workflow instances that are executed

l The number of actions in a workflow instance

l The number of tasks assigned to used

Type Nintex Forms 2013 Requirement

Operatingsystem

Microsoft Windows Server 2008 R2 or Microsoft Windows Server 2012(R2 is supported)


-4-


https://support.microsoft.com/en-us/kb/2891274https://support.microsoft.com/en-us/kb/2891274http://technet.microsoft.com/en-au/library/cc262485.aspxhttp://technet.microsoft.com/en-au/library/cc262485.aspxhttp://technet.microsoft.com/en-au/library/cc262485.aspx#section3http://technet.microsoft.com/en-au/library/cc262485.aspx#section3http://www.nintex.com/EN-US/SUPPORT/Pages/default.aspxhttp://www.nintex.com/en-US/Pages/NintexCookies.aspxhttps://www.nintex.com/en-US/Pages/TermsAndConditions.aspxhttps://www.nintex.com/en-US/Pages/Privacy.aspxhttp://technet.microsoft.com/en-au/library/cc262485.aspx#section3http://technet.microsoft.com/en-au/library/cc262485.aspx#section3http://technet.microsoft.com/en-au/library/cc262485.aspxhttp://technet.microsoft.com/en-au/library/cc262485.aspxhttps://support.microsoft.com/en-us/kb/2891274https://support.microsoft.com/en-us/kb/2891274


8/39

Type Nintex Forms 2013 Requirement

Browserclient

To design Nintex forms, use the following browser versions.

l Minimum required: Microsoft Internet Explorer 8.x

l Recommended: Microsoft Internet Explorer 10 or greater

To run Nintex forms, use the following browser versions.l Minimum required: Microsoft Internet Explorer 8.x or latest version

of Chrome, Firefox, or Safari (Mac/iOS)

l Recommended: Microsoft Internet Explorer 10 or greater, or latestversion of Chrome, Firefox, or Safari (Mac/iOS)

Software l SQL Server 2008 R2 SP1, SQL Server 2012, or SQL Server 2014

l Nintex Workflow 2013 if using Nintex Forms with Nintex Workflow(for the required version number, see the latest Nintex Forms 2013release notes on Nintex Connect: https://-community.nintex.com/docs/DOC-1161)

l Microsoft SharePoint Foundation 2013 or Microsoft SharePointServer 2013 (SP1 is supported)

Note: See the following Microsoft article. SharePoint 2013SP1 support in Windows Server 2012 R2.

Note: Publishing forms to Nintex Live may require speciallicensing for external or anonymous users. For more inform-ation, reference SharePoint Server 2013 for Internet Sites(SharePoint FIS) licensing details, such as the followingTechNet article: http://blogs.technet.com/b/volume-licens-ing/archive/2013/08/08/licensing-how-to-sharepoint-server-2013-licensing-changes.aspx.

Hardware No Nintex-specific requirements

Review topology considerations and best practices

This section provides guidance on preparing your environment for Nintex installation.

High availability

This section describes topology considerations and best practices related to high avail-ability of Nintex databases.

Capacity considerations

Nintex Workflow follows the same scalability and limitations as SharePoint workflows;

both Nintex and SharePoint use the workflow engine inside SharePoint.Storage space

Size your Nintex databases according to the anticipated use of Nintex workflows and thelevel of complexity in those workflows (numbers of actions and tasks).

Content databases and performance

Nintex Workflow installation involves creating Nintex content databases and mappingthem to SharePoint content databases. Nintex content databases store workflow andtask history.

For more information about database mapping for Nintex Workflow, see the followingNintex Connect article: Database Design Guide: Nintex Workflow.


-5-


https://community.nintex.com/docs/DOC-1161https://community.nintex.com/docs/DOC-1161http://blogs.technet.com/b/volume-licensing/archive/2013/08/08/licensing-how-to-sharepoint-server-2013-licensing-changes.aspxhttp://www.nintex.com/EN-US/SUPPORT/Pages/default.aspxhttp://www.nintex.com/en-US/Pages/NintexCookies.aspxhttps://www.nintex.com/en-US/Pages/TermsAndConditions.aspxhttps://www.nintex.com/en-US/Pages/Privacy.aspxhttps://community.nintex.com/docs/DOC-1426http://blogs.technet.com/b/volume-licensing/archive/2013/08/08/licensing-how-to-sharepoint-server-2013-licensing-changes.aspxhttp://blogs.technet.com/b/volume-licensing/archive/2013/08/08/licensing-how-to-sharepoint-server-2013-licensing-changes.aspxhttp://blogs.technet.com/b/volume-licensing/archive/2013/08/08/licensing-how-to-sharepoint-server-2013-licensing-changes.aspxhttps://support.microsoft.com/en-us/kb/2891274https://support.microsoft.com/en-us/kb/2891274https://community.nintex.com/docs/DOC-1161https://community.nintex.com/docs/DOC-1161


9/39

During the planning phase, determine the optimal number of Nintex content databasesfor your workflow traffic. Ensuring a sufficient number of content databases canimprove performance of the workflow engine across all site collections in the farm aswell as facilitating backup, restore, and migration.

For site collections that use workflows, scale each SharePoint content database to oneof the following levels of granularity, depending on the degree of traffic in your

environment:l Multiple web applications per SharePoint content database

l A single web application per SharePoint content database

l Multiple site collections (in a single web application) per SharePoint content data-base

l A single site collection (in a single web application) per SharePoint content data-base

For environments with high workflow traffic, we recommend using the most granularlevel: a single site collection in a single web application per SharePoint content data-base.

Following these guidelines optimizes performance by automatically distributing work-

flows to corresponding content databases, thereby helping to avoid workflow time-outissues.

SharePoint and SQL Server

For high availability guidance specific to SharePoint and SQL Server, refer to Microsoftresources at msdn.microsoft.com and technet.microsoft.com, such as the followingarticles:

l Database Mirroring and Log Shipping (SQL Server)

l Create a high availability architecture and strategy for SharePoint 2013

l Capacity planning for SharePoint Server 2013

l Estimate performance and capacity planning for workflow in SharePoint Server2013

l High Availability Solutions (SQL Server)

l Workflow Scalability and Performance in Windows SharePoint Services 3.0

Security

This section describes topology considerations and best practices related to security of Nintex databases.

Ensuring security for SQL Server and SharePoint addresses the security needs of Nin-tex.

For security guidance specific to SharePoint and SQL Server, refer to Microsoftresources at msdn.microsoft.com and technet.microsoft.com, such as the following art-icles:

l Security planning for SharePoint 2013 farms

l Security Considerations for a SQL Server Installation

Backup and recovery

This section describes topology considerations and best practices related to backup andrecovery of Nintex databases.

Database mapping

Every SharePoint content database that contains site collections using Nintex Workflowshould be mapped to a Nintex Workflow content database. The ideal number of SharePoint content databases per Nintex Workflow content database varies by envir-onment. One-to-one mapping often serves smaller environments while others are


-6-


http://msdn.microsoft.com/en-us/library/ms187016.aspxhttp://technet.microsoft.com/en-us/library/cc748824(v=office.15).aspxhttp://technet.microsoft.com/en-au/library/ff758645.aspxhttp://technet.microsoft.com/en-us/library/gg508755.aspxhttp://msdn.microsoft.com/en-us/library/ms190202.aspxhttp://technet.microsoft.com/en-us/library/hh377941(v=office.15).aspxhttp://msdn.microsoft.com/en-us/library/ms144228(v=sql.110).aspxhttp://www.nintex.com/EN-US/SUPPORT/Pages/default.aspxhttp://www.nintex.com/en-US/Pages/NintexCookies.aspxhttps://www.nintex.com/en-US/Pages/TermsAndConditions.aspxhttps://www.nintex.com/en-US/Pages/Privacy.aspxhttp://msdn.microsoft.com/en-us/library/ms144228(v=sql.110).aspxhttp://technet.microsoft.com/en-us/library/hh377941(v=office.15).aspxhttp://msdn.microsoft.com/en-au/library/dd441390.aspxhttp://msdn.microsoft.com/en-us/library/ms190202.aspxhttp://technet.microsoft.com/en-us/library/gg508755.aspxhttp://technet.microsoft.com/en-us/library/gg508755.aspxhttp://technet.microsoft.com/en-au/library/ff758645.aspxhttp://technet.microsoft.com/en-us/library/cc748824(v=office.15).aspxhttp://msdn.microsoft.com/en-us/library/ms187016.aspx


10/39

better served by grouping SharePoint content databases by department or other func-tion and mapping each set of SharePoint content databases to a single Nintex Workflowcontent database. For more information, see the following Nintex Connect article: Data-base Design Guide: Nintex Workflow.

Simultaneous backups and restores

To retain integrity of data, back up and restore the related and databases at the sametime.

For more information, see the following article: Nintex Workflow Backup and Restore.

SharePoint and SQL Server

For backup and recovery guidance specific to SharePoint and SQL Server, refer toMicrosoft resources at msdn.microsoft.com and technet.microsoft.com, such as the fol-lowing articles:

l Plan for backup and recovery in SharePoint 2013

l Back Up and Restore of SQL Server Databases

Set up topology for installation

This section provides guidance for preparing all servers in the SharePoint farm for theNintex installation process. This task involves ensuring that the required services arerunning and disabling antivirus software—on all servers in the farm.

Ensure services are running

This section provides instructions for ensuring that the required services are running onall servers in the SharePoint farm.

Nintex Workflow installation requires that the following Microsoft Windows andSharePoint services be running.

Microsoft Windows services required:

l SharePoint Administration

l SharePoint Timer Service

SharePoint services required:

l Microsoft SharePoint Foundation Web Application (for Web Front End (WFE) serv-ers)

l Microsoft SharePoint Foundation Workflow Timer Service

Note: On application servers running Microsoft SharePoint FoundationWorkflow Timer Service, the Microsoft SharePoint Foundation Web Applic-ation service can be turned off by following Microsoft’s recommended prac-tices. See Microsoft article 2674684. The Windows PowerShell commandlisted in the "Resolution" section must be run on a Web Front End (WFE)server that has the Microsoft SharePoint Foundation Web Application ser-vice running. In addition, we recommend running the IISRESET commandand restarting the SharePoint Timer Service after running the WindowsPowerShell command.

Nintex Forms installation does not require any services to be running other than thoserequired to run SharePoint.

To ensure that required Microsoft Windows services are running on all servers in the farm

1. On each server, open the Services Microsoft Management Console (MMC) snap-in.


-7-


http://technet.microsoft.com/en-us/library/cc261687(v=office.15).aspxhttp://www.nintex.com/EN-US/SUPPORT/Pages/default.aspxhttp://www.nintex.com/en-US/Pages/NintexCookies.aspxhttps://www.nintex.com/en-US/Pages/TermsAndConditions.aspxhttps://www.nintex.com/en-US/Pages/Privacy.aspxhttp://support.microsoft.com/kb/2674684http://msdn.microsoft.com/en-us/library/ms187048(v=sql.110).aspxhttp://technet.microsoft.com/en-us/library/cc261687(v=office.15).aspxhttps://community.nintex.com/docs/DOC-1094https://community.nintex.com/docs/DOC-1426https://community.nintex.com/docs/DOC-1426


11/39

Note: For instructions on accessing the Services Microsoft ManagementConsole (MMC) snap-in, see the Microsoft TechNet Library at http://-technet.microsoft.com/en-us/library/cc772408.aspx.

2. For any required services that are not running, click Start.

To ensure that required SharePoint services are running on all servers in the farm

1. On the Central Administration Home page, click System Settings.

2. Under Servers, click Manage servers in this farm.

Each server on the farm is listed, along with services running on that server.

3. If required services are not running on a server, go back to the Central Admin-istration Home page, click System Settings, and then click Manage serviceson this server under Servers.

4. On the Services on Server page, select the server from the Server list to displayits SharePoint services.

5. For any required services that are not running, click Start.

Disable antivirus software

The installation process for Nintex Workflow and Nintex Forms requires antivirus soft-ware to be disabled.

To disable antivirus software on all servers in the farm

1. On each server, note original settings for antivirus software.

You'll need the original settings to revert after installation.

2. On each server, disable all antivirus software.

Set up server used for running installers

Setting up the server used for running installers involves temporarily disabling User

Account Control (UAC), ensuring that the application pools are started, and ensuringthat Windows PowerShell scripts can be run by the installers.

Note: The Nintex Forms installer must be run on a front end server.

Note: The installers need to be run on a single server in the farm only. If youplan to use Nintex Live, choose a server that hosts SharePoint Central Admin-istration. Doing so allows you to avoid extra steps when connecting and enablingNintex Live.

To temporarily disable User Account Control (UAC)

1. On the server that you plan to use for running the installers, from Control Panel,select Change User Account Control settings.

2. Note the original settings for User Account Control (UAC).

You'll need the original settings to revert after installation.

3. Disable User Account Control (UAC).

For instructions on disabling UAC, see the following URL: http://win-dows.microsoft.com/en-us/windows/turn-user-account-control-on-off#1TC-C=windows-7


-8-


http://technet.microsoft.com/en-us/library/cc772408.aspxhttp://www.nintex.com/EN-US/SUPPORT/Pages/default.aspxhttp://www.nintex.com/en-US/Pages/NintexCookies.aspxhttps://www.nintex.com/en-US/Pages/TermsAndConditions.aspxhttps://www.nintex.com/en-US/Pages/Privacy.aspxhttp://windows.microsoft.com/en-us/windows/turn-user-account-control-on-off#1TC=windows-7http://windows.microsoft.com/en-us/windows/turn-user-account-control-on-off#1TC=windows-7http://windows.microsoft.com/en-us/windows/turn-user-account-control-on-off#1TC=windows-7http://technet.microsoft.com/en-us/library/cc772408.aspxhttp://technet.microsoft.com/en-us/library/cc772408.aspx


12/39

To ensure that the application pools are started

1. On a server that can access the application pools, open IIS Manager.

For instructions, see http://msdn.microsoft.com/en-us/library/vstudio/bb763170(v=vs.100).aspx.

2. Expand the server and then click Application Pools.

Status is indicated for each application server, such as SharePoint - 80 andSharePoint Central Administration v4.

To ensure that Windows PowerShell scripts can be run by the installers

1. On the server that you plan to use for running the installers, determine if Win-dows PowerShell script execution is set by group policy:

a. Open the Local Group Policy Editor (gpedit.msc); for instructions, seehttp://technet.microsoft.com/en-us/library/cc731745.aspx .

b. Navigate to Local Computer Policy > Computer Configuration> Administrative Templates > Windows Components > Windows Power-Shell.

c. Click Turn on Script Execution.

d. In the Turn on Script Execution dialog box, determine if the Enabled set-ting is grayed out (unavailable).

Unavailability of this setting indicates that group policy is used.

e. Navigate to Local Computer Policy > User Configuration > AdministrativeTemplates > Windows Components > Windows PowerShell.

f. Click Turn on Script Execution.

g. In the Turn on Script Execution dialog box, determine if the Enabled set-ting is grayed out (unavailable).

Unavailability of this setting indicates that group policy is used.

2. If group policy is used for script execution, ask your network administrator to doone of the following:

l Allow script execution policy to be set individually (turn off group policy forthat server).

l Set the policy to Unrestricted for the user and server to be used forinstallation.

When the ability to execute Windows PowerShell scripts is available, you can con-tinue on to the next step in setting up the topology for installation.

Obtain account with sufficient permissionsTo successfully install Nintex products, obtain a user account with sufficient per-missions.

Typical account used for Nintex installation

In most cases, the Farm Installation account (used to install SharePoint) satisfies thepermission requirements for the full installation process.

To identify the Farm Installation account

Note: By default, the SharePoint Central Administration v4 application pool isconfigured to run using the Farm Installation account.

1. Open IIS Manager.

For instructions, see http://msdn.microsoft.com/en-us/library/vstudio/bb763170(v=vs.100).aspx.


-9-


http://msdn.microsoft.com/en-us/library/vstudio/bb763170(v=vs.100).aspxhttp://technet.microsoft.com/en-us/library/cc731745.aspxhttp://www.nintex.com/EN-US/SUPPORT/Pages/default.aspxhttp://www.nintex.com/en-US/Pages/NintexCookies.aspxhttps://www.nintex.com/en-US/Pages/TermsAndConditions.aspxhttps://www.nintex.com/en-US/Pages/Privacy.aspxhttp://msdn.microsoft.com/en-us/library/vstudio/bb763170(v=vs.100).aspxhttp://msdn.microsoft.com/en-us/library/vstudio/bb763170(v=vs.100).aspxhttp://technet.microsoft.com/en-us/library/cc731745.aspxhttp://msdn.microsoft.com/en-us/library/vstudio/bb763170(v=vs.100).aspxhttp://msdn.microsoft.com/en-us/library/vstudio/bb763170(v=vs.100).aspx


13/39

2. Under your server, click Application Pools.

3. Select SharePoint Central Administration v4.

4. Under Edit Application Pool, click Advanced Settings.

The Farm Installation account is indicated in the Identity row under ProcessModel.

Least permissions model

Installation and deployment of Nintex products requires an account with at least the fol-lowing permissions.

l SharePoint permissions:

l Ability to modify farm properties (required to import the license file).

Any user account in the Farm Administrators group has the ability to modifyfarm properties. To view members of this group, navigate to Central Admin-istration > Security > Users > Manage the farm administrators group.

l SharePoint_Shell_Access role membership for the SharePoint configurationdatabase, Central Administration database, and all SharePoint content data-bases.

For instructions on provisioning this membership using Windows Power-Shell, see http://technet.microsoft.com/en-us/library/ff607596(v=o-ffice.15).aspx. For more information about account permissions andsecurity settings in SharePoint 2013, see http://technet.microsoft.com/en-us/library/cc678863(v=office.15).aspx.

l SQL Server permissions:

l Ability to create databases as well as modify permissions on databases.

l A Microsoft Windows-based login to SQL Server that is a member of the fol-lowing roles:

l securityadmin fixed server role

l dbcreator fixed server role

l db_owner fixed database role for all databases in the server farm thatwill be used during installation

l Windows PowerShell permissions:

l SharePoint_Shell_Access role membership (required to access parts of SharePoint via Windows PowerShell).

l Ability to run Windows PowerShell scripts if script execution is set by grouppolicy; needed for the server on which the installers are run only. For moreinformation, see "To ensure that Windows PowerShell scripts can be run bythe installers" on the previous page.

l Windows permissions:

l Membership of the Administrators group for every server in the farm.

To determine if a user account has local administrator rights on the server,view the Administrators group: In the Services Microsoft Management Con-sole (MMC) snap-in, expand Local Users and Groups, expand Groups, anddouble-click Administrators. If your account is not listed, note originalstatus for reverting after installation is complete, then add the account tothe group. For information about Local Users and Groups in the ServicesMicrosoft Management Console (MMC) snap-in and instructions on addingaccounts to the Administrators group, see http://msdn.microsoft.com/en-us/library/ee250492(v=bts.10).aspx .

Obtain Nintex license filesMake sure your Nintex license files are up to date.


-10-


http://technet.microsoft.com/en-us/library/ff607596(v=office.15).aspxhttp://technet.microsoft.com/en-us/library/cc678863(v=office.15).aspxhttp://technet.microsoft.com/en-us/library/cc678863(v=office.15).aspxhttp://www.nintex.com/EN-US/SUPPORT/Pages/default.aspxhttp://www.nintex.com/en-US/Pages/NintexCookies.aspxhttps://www.nintex.com/en-US/Pages/TermsAndConditions.aspxhttps://www.nintex.com/en-US/Pages/Privacy.aspxhttp://msdn.microsoft.com/en-us/library/ee250492(v=bts.10).aspxhttp://msdn.microsoft.com/en-us/library/ee250492(v=bts.10).aspxhttp://technet.microsoft.com/en-us/library/cc678863(v=office.15).aspxhttp://technet.microsoft.com/en-us/library/cc678863(v=office.15).aspxhttp://technet.microsoft.com/en-us/library/ff607596(v=office.15).aspxhttp://technet.microsoft.com/en-us/library/ff607596(v=office.15).aspx


14/39

If you have questions about your license files, contact your Nintex territory manager oryour Nintex Partner.

Schedule deploymentTo minimize interruption of services, determine the best time for deployment to pro-duction. Follow best practices for announcing deployment.


-11-




15/39

Install Nintex products to test environment andconfirm

Complete all installation steps on a test SharePoint environment and then confirm suc-cessful installation. See "Install Nintex products to production environment" on the next

page and "Confirm production installation" on page 29.


-12-




16/39

Install Nintex products to production envir-onment

This section provides guidance for installing Nintex Workflow and Nintex Forms to yourproduction environment. Installation involves running the installers, deploying the

provided Nintex solutions, importing the Nintex license files, configuring databases, con-necting and enabling Nintex Live, and activating Nintex features in SharePoint.

Run the installersRun the installer for each product being installed.

You can download the installer files from the product download page of the Nintex Con-nect site at https://community.nintex.com. For more information, contact your Nintexterritory manager or your Nintex Partner.

Nintex Workflow installer

This section applies to installation of Nintex Workflow. If you are not installingNintex Workflow, you can skip this section.

To install Nintex Workflow

1. Set up a server for running the installers. See "Set up server used for runninginstallers" on page 8.

2. Double-click the installer file to display the installation dialog box.

Example installer file: NintexWorkflow2013Int.exe

Note: To run the installer with a user account other than the logged-inuser account, press and hold SHIFT, right-click the installer file, selectRun as different user, and then enter the credentials for the desiredaccount.

3. On the Welcome to the Installation Wizard page, click Next.

4. On the License Agreement page, review the license, click I Agree, and then clickNext.

5. Nintex Live: Choose the desired option.

l To install Nintex Live, select the check box for Install Nintex Live andthen click Next.

Note: Any currently installed version of Nintex Live is auto-matically upgraded regardless of the selected option.

Note: For more information on Nintex Live, see "Connect andenable Nintex Live" on page 23. For licensing information, seewww.nintex.com/licensing.

l To continue without installing Nintex Live, clear the check box for InstallNintex Live and then click Next.

6. Click Yes to initiate adding the solution to SharePoint and then click Next.

Note: You can optionally select No to export the Nintex Workflow solu-tions for manual deployment later.

Installation status is indicated by messages and a progress bar.


-13-


http://www.nintex.com/licensinghttp://www.nintex.com/licensinghttp://www.nintex.com/licensinghttp://www.nintex.com/EN-US/SUPPORT/Pages/default.aspxhttp://www.nintex.com/en-US/Pages/NintexCookies.aspxhttps://www.nintex.com/en-US/Pages/TermsAndConditions.aspxhttps://www.nintex.com/en-US/Pages/Privacy.aspxhttp://www.nintex.com/licensinghttps://community.nintex.com/


17/39

7. When installation is complete, click Close to close the installation dialog box.

The installer installs Nintex-named assemblies and SharePoint features locally.For more information, see "Nintex assemblies and features" on page 29.

The solutions are now available for deployment to your SharePoint farm. Forinstructions on deploying solutions, see "Steps for deploying solutions" on thenext page.

Nintex Forms installer

This section applies to installation of Nintex Forms. If you are not installingNintex Forms, you can skip this section.

To install Nintex Forms

Note: The Nintex Forms installer must be run on a front end server.

1. If you plan to use Nintex Forms with Nintex Workflow, make sure that theNintex Workflow solutions are already deployed to the required Web applic-ations.

2. Set up a server for running the installers. See "Set up server used for runninginstallers" on page 8.

3. Double-click the installer file to display the installation dialog box.

Example installer file: NintexForms2013Int.exe

Note: To run the installer with a user account other than the logged-inuser account, press and hold SHIFT, right-click the installer file, selectRun as different user, and then enter the credentials for the desiredaccount.

4. On the Welcome to the Installation Wizard page, click Next.

5. On the License Agreement page, review the license, click I Agree, and then clickNext.

The Installing page appears with a description of the Nintex Live installation.

6. Nintex Live: Choose the desired option.

l To install Nintex Live, select the check box for Install Nintex Live andthen click Next.

Note: Any currently installed version of Nintex Live is auto-matically upgraded regardless of the selected option.

Note: For more information on Nintex Live, see "Connect and

enable Nintex Live" on page 23. For licensing information, seewww.nintex.com/licensing.

lTo continue without installing Nintex Live, clear the check box for InstallNintex Live and then click Next.


-14-


http://www.nintex.com/EN-US/SUPPORT/Pages/default.aspxhttp://www.nintex.com/en-US/Pages/NintexCookies.aspxhttps://www.nintex.com/en-US/Pages/TermsAndConditions.aspxhttps://www.nintex.com/en-US/Pages/Privacy.aspxhttp://www.nintex.com/licensing


18/39

7. On the Confirm Installation page, click Yes to initiate adding the solution toSharePoint and then click Next.

Installation status is indicated by messages and a progress bar.

Note: You can optionally select No to export the Nintex Workflow solu-tions for manual deployment later.

8. When installation is complete, click Close to close the installation dialog box.

The installer installs Nintex-named assemblies and SharePoint features locally.For more information, see "Nintex assemblies and features" on page 29.

The solutions are now available for deployment to your SharePoint farm. Forinstructions on deploying solutions, see "Steps for deploying solutions" below.


Sequence of solution deployment

Use the following sequence when deploying your Nintex solutions.

1. Nintex Workflow

a. NintexWorkflow2013core.wsp

b. NintexWorkflow2013.wsp

c. Other Nintex Workflow solutions as desired, in any sequence

2. Nintex Forms

Note: If a backwards-compatible user interface solution was provided for theproduct and you decide to use it, deploy it after all other solutions for the givenproduct.

Steps for deploying solutions

Follow these instructions to deploy each Nintex solution to your SharePoint envir-onment.

To deploy a Nintex solution


2. In the Farm Management section, click Manage farm solutions.

The Solution Management page appears. Solution deployment status is indicatedin the Status column; the Web applications to which the solutions are deployedare indicated in the Deployed To column.


-15-




19/39

3. Determine the required Web application deployments for each solution by review-ing the following table. Disregard solutions for Nintex products that you are notinstalling.

Solution name

(ordered alphabetically)

Description Required deployments

(Web applications)

All con-

tent Web

applic-

ations

Central

Admin-

istration

Web applic-

ation

nintexforms2013.wsp Nintex Forms

2013 web

application-

specific func-

tionality

(globally

deployed

auto-

matically)

(globally

deployed auto-

matically)

nintexforms2013core.wsp Nintex Forms

2013 farm-

wide func-

tionality

(globally

deployed

auto-

matically)

(globally

deployed auto-

matically)

nintexforms2013backwardscompatibilityui.wsp Nintex Forms

2013 back-

wards-com-

patible user

interface

(optional)

Yes No

nintexlivecore.wsp Nintex Live (globally

deployed

auto-

matically)

(globally

deployed auto-

matically)

nintexworkflow2013core.wsp Nintex Work-

flow 2013

farm-wide

functionality

(globally

deployed

auto-

matically)

(globally

deployed auto-

matically)

nintexworkflow2013.wsp Nintex Workf-

low 2013

web applic-

ation- spe-

cific

functionality

Yes* Yes*

nintexworkflow2013backwardscompatibilityui.wsp Nintex Workf-

low 2013

backwards-

compatible

user inter-

face

(optional)

Yes Yes

nintexworkflow2013enterprisefeatures.wsp Nintex Workf-

low 2013

Enterprise

(for Enter-

prise report-

ing)

Yes Yes


-16-




20/39

Solution name

(ordered alphabetically)

Description Required deployments

(Web applications)

All con-

tent Web

applic-

ations

Central

Admin-

istration

Web applic-

ation

nintexworkflow2013enterprisefeaturesbackwardsc

ompat.wsp

Nintex Workf-

low 2013

Enterprise

backwards-

compatible

user inter-

face

(optional)

(for Enter-

prise report-

ing);

ensures that

Enterprise

featuresrender cor-

rectly when a

site is run-

ning in back-

wards

compatibility

mode

Yes Yes

* Before deploying nintexworkflow2013.wsp, confirm that nin-texworkflow2013core.wsp has been deployed.

4. If deployment to all content Web applications is required, do the following:

Note: Make sure you deploy the solution to all content Web applicationsfirst (if required). Make sure you deploy Nintex Workflow solutionsbefore Nintex Forms solutions (if using Nintex Forms withNintex Workflow).

a. Display the Deploy Solution page: Click the solution that you want todeploy and then click Deploy Solution.

b. In the Deploy When? section, select Now.

c. In the Deploy To? section, select All content Web applications.

d. Click OK.

5. If deployment to the Central Administration Web application is required, do thefollowing:

a. Display the Deploy Solution page: Click the solution that you want todeploy and then click Deploy Solution.

b. In the Deploy When? section, select Now.

c. In the Deploy To? section, select the URL for the Central AdministrationWeb application.

d. Click OK.

Import the license filesFor full product functionality you must have a license file issued by Nintex for eachproduct. Each license can be either a full production license or an evaluation license.The license files must be imported into SharePoint Central Administration.


-17-




21/39

Note: No separate license file is required for Nintex Live; however, theproduct-specific license key must be explicitly activated for Nintex Live.

To import each license file

1. On the Central Administration Home page, display the licensing page for yourproduct:

l For Nintex Workflow, click Nintex Workflow Management and thenclick Licensing.

l For Nintex Forms, click Nintex Forms Management and then clickLicensing.

2. On the selected licensing page, click Import.

The page displays a Browse button.

3. Click Browse to locate your license file and then click Import.

The licensing information is displayed.

4. Click OK.

When all license files have been imported, you can proceed to configure data-bases for Nintex Workflow and Nintex Forms.

Configure databases and other items

Nintex Workflow configuration

This section provides guidance on configuration tasks for Nintex Workflow, including con-figuring databases, activating web applications, enabling workflow actions, configuringemail settings, and setting up LazyApproval.


Configure databases for Nintex WorkflowThis section provides instructions for Nintex Workflow database configuration.

Nintex Workflow requires a configuration database. While the configuration databasecan technically serve as the sole content database for Nintex Workflow, we recommendmultiple content databases to ensure high availability. For more information, see "Con-tent databases and performance" on page 5.

To set up configuration and content databases

1. Create a Nintex configuration database:

a. On the Central Administration Home page, click Nintex Workflow Man-agement.

b. Click Database setup.

c. In the Configuration Database section, click Create.

d. On the Create configuration database page, enter the name of your data-base server and enter a database name.

Note: The default value for Database Server is the defaultSharePoint database server.

e. Click OK.

A database connection string appears in the Configuration Database sec-tion.


-18-




22/39

2. Add content databases as needed to store workflow and task history (optional;see "Content databases and performance" on page 5):

a. To redisplay the database setup page, on the Central Administration Homepage, click Nintex Workflow Management and then click Databasesetup.

b. For each content database to be added, do the following:

i. In the Content Databases section, click Add content database.

ii. In the Add content database page, enter the name of your databaseserver and a database name; leave all other settings as default.

iii. Click OK.

A database connection string appears in the Configuration Data-base section.

3. Map Nintex content databases to SharePoint content databases:

a. To redisplay the database setup page, on the Central Administration Homepage, click Nintex Workflow Management and then click Databasesetup.

b. Click Manage database mappings.

c. For each SharePoint content database corresponding to a site collectionthat uses Nintex Workflow, select a Nintex Workflow content databaseunder Map to Workflow Content Database.

For more information about database mapping for Nintex Workflow, seethe following Nintex Connect article: Database Design Guide: Nintex Work-flow.

d. Click OK.

4. Run the IISreset command to implement the changes:

a. Start a command prompt as an administrator.

For instructions, see the following TechNet article: http://-technet.microsoft.com/en-us/library/cc947813(v=WS.10).aspx

b. Enter the following command.

IISreset

Activate the web applications

Nintex Workflow requires activation of web applications that will use the product.

To activate th e web applications

1. On the Central Administration Home page, click Nintex Workflow Man-agement.

2. Click Web Application activation.

The default web application name is automatically selected.

3. To activate all web applications for Nintex Workflow, select the check box for Allcontent web applications and then click Activate.

4. To activate a subset of web applications for Nintex Workflow, select each webapplication and then click Activate; repeat until all desired web applicationshave been activated.


-19-


http://www.nintex.com/EN-US/SUPPORT/Pages/default.aspxhttp://www.nintex.com/en-US/Pages/NintexCookies.aspxhttps://www.nintex.com/en-US/Pages/TermsAndConditions.aspxhttps://www.nintex.com/en-US/Pages/Privacy.aspxhttp://technet.microsoft.com/en-us/library/cc947813(v=WS.10).aspxhttp://technet.microsoft.com/en-us/library/cc947813(v=WS.10).aspxhttps://community.nintex.com/docs/DOC-1426https://community.nintex.com/docs/DOC-1426


23/39

Enable actions for Nintex Workflow

This section provides instructions for enabling Nintex Workflow actions. Only the actionsyou enable are displayed in the Workflow designer.

To enable Nintex workflow actions

1. On the Central Administration Home page, click Nintex Workflow Man-

agement.2. Click Manage allowed actions.

By default, for new installations, no actions are selected.

3. Click the check box in the heading row to enable all actions.

Alternatively, to enable a subset of the available actions, select the check box foreach desired action.

Enabled actions become available in the Workflow designer.

4. Click OK.

The web.config file for each web application is updated to list enabled actions assafe controls.

Configure SharePoint email prerequisites

This section provides instructions for completing SharePoint email settings that arerequired for using LazyApproval and sending email from Nintex workflows. SharePointemail settings include configuring incoming email, confirming that required services arerunning, and ensuring that incoming emails are sent to the correct servers.

To configure incoming email for the farm

l See the following Microsoft article: Configure incoming email for a SharePoint2013 farm.

SharePoint automatically populates the incoming email address for the farm usingthe fully qualified domain of the server. To view or edit this address, go to the Cen-tral Administration Home page, click System Settings, and then click Configure

Incoming E-mail Settings.To confirm that required services are running

l On each server in your farm that is running the service Microsoft SharePointFoundation Incoming E-Mail, do the following:

For this ser-vice...

Do this to confirm that the service is running:

MicrosoftSharePoint Found-ation Incoming E-Mail

On the Central Administration Home page, click Manageservers on this farm (under System Settings).

Microsoft

SharePoint Found-ation Web Applic-ation

On the Central Administration Home page, click Manageservers on this farm

(under System Settings).

SMTP Reference the "Install and configure the SMTPservice" section of the following Microsoft article: Con-figure incoming email for a SharePoint 2013 farm.

To ensure that incoming emails are sent to the correct servers (environments with multiple

front-end servers)

l Configure your load balancer to forward incoming emails to servers with theSMTP service enabled. Refer to your organization's SharePoint environment doc-umentation.


-20-


http://technet.microsoft.com/en-us/library/cc262947(v=office.15).aspxhttp://www.nintex.com/EN-US/SUPPORT/Pages/default.aspxhttp://www.nintex.com/en-US/Pages/NintexCookies.aspxhttps://www.nintex.com/en-US/Pages/TermsAndConditions.aspxhttps://www.nintex.com/en-US/Pages/Privacy.aspxhttp://technet.microsoft.com/en-us/library/cc262947(v=office.15).aspxhttp://technet.microsoft.com/en-us/library/cc262947(v=office.15).aspxhttp://technet.microsoft.com/en-us/library/cc262947(v=office.15).aspx#section2http://technet.microsoft.com/en-us/library/cc262947(v=office.15).aspx#section2http://technet.microsoft.com/en-us/library/cc262947(v=office.15).aspxhttp://technet.microsoft.com/en-us/library/cc262947(v=office.15).aspx


24/39

Configure Nintex Workflow email settings

This section provides instructions to configure email settings for Nintex Workflow.

To configure email settings for Nintex Workflow

1. Ensure that the SharePoint email prerequisites are met.

For more information, see "Configure SharePoint email prerequisites" on the pre-vious page.

2. On the Central Administration Home page, click Nintex Workflow Man-agement.

3. Click Global settings.

4. Under Email settings, enter the following details.

l Outbound SMTP Server

Enter the URL used for outgoing mail in your SharePoint farm.

Example: exchange.example.com

l From Address

Example: [email protected]

l Reply To Address


Note: When using LazyApproval, the Reply To Address must beidentical to the alias specified on the LazyApproval settings page. If you would like the workflow-triggered emails to display an emailaddress other than the configured LazyApproval account, then spe-cify the different email address in From Address. Make sure thatReply To Address is the LazyApproval alias. This way the emailsender can be identified as a portal email address, such [email protected], while replies are sent to the LazyApprovalalias, such as [email protected].

5. Edit other settings on the page as needed for your environment.

6. Click OK.

Set up LazyApproval

LazyApproval allows users to respond to requests in real language, even when on the goand without access to the SharePoint portal.

Setting up LazyApproval involves enabling LazyApproval for the server farm, con-figuring the LazyApproval alias for email, and optionally editing phrases recognized andignored by the LazyApproval process.

To set up LazyApproval

1. Ensure that SharePoint email prerequisites and Nintex Workflow email settingsare configured.

For more information, see "Configure SharePoint email prerequisites" on the pre-vious page and "Configure Nintex Workflow email settings" above.


-21-




25/39

2. Go to the LazyApproval Settings page:

a. On the Central Administration Home page, click Nintex Workflow Man-agement.

b. Click LazyApproval settings.

c. Click Enable / Disable LazyApproval for the current server farm.

Note: The page displays a message if either of the followingrequirements is missing: email configuration for Nintex Workflowand incoming email for the farm. For more information, see "Con-figure SharePoint email prerequisites" on page 20 and "ConfigureNintex Workflow email settings" on the previous page.

3. Under Enable LazyApproval via email, select Yes.

4. In the Email alias text box, enter a unique account name.

The alias is the name that will be used as the email address that sends the noti-fications and accepts the LazyApproval replies. The domain is determined by theincoming email address for the farm. To view or edit this address, go to the Cen-

tral Administration Home page, click System Settings, and then click ConfigureIncoming E-mail Settings.


Note: Ensure that the email alias complies with standard SharePointrequirements for email-enabled document libraries and lists. Forexample, the email alias cannot have an inbox in Exchange as having oneprevents transmission to SMTP.

Note: Contacts in Active Directory are not required. There is no need forDirectory Management Service.

5. Click OK to save changes.

Note: If the Reply To Address setting under Nintex Workflow > Globalsettings differs from the Alias setting, then Nintex updates the Reply ToAddress setting to match the Alias setting. These email settings must beidentical for LazyApproval to function.

The changes propagate to all servers within about 15 minutes.

A list of phrases recognized and ignored by the LazyApproval process appears.

6. Add, edit, or remove phrases at your discretion.

l

To add a recognized phrase, click Create a new LazyApproval term forthe current server farm and enter the desired phrase and outcome.

l To edit a recognized phrase, click the phrase, then change settings in theEdit LazyApproval Phrase page.

l To remove a recognized phrase, click the phrase, then click Delete in theEdit LazyApproval Phrase page.

l To add an ignored phrase, click Create a term to ignore and enter thedesired phrase.

l To remove an ignored phrase, click the Delete icon next to the phrase.

The changes propagate to all servers within about 15 minutes.

7. (Optional) To implement changes immediately, run the IISreset command.


-22-




26/39

Nintex Forms configuration

This section applies to installation of Nintex Forms. If you are not installingNintex Forms, you can skip this section.

Configuring settings for Nintex Forms involves creating the database and activating fea-tures on the relevant web applications. The Nintex Forms database stores Nintex Formsconfiguration and application settings.

To create the database for Nintex Forms

Note: The Nintex Forms database is required.

1. On the Central Administration Home page, click Nintex Forms Management.

2. Click Manage database.

When Nintex Forms is newly installed, the Manage Database page displaysdefault settings for the Nintex Forms database.

3. If needed, edit the database settings.

4. Click OK to create the database.

To activate Nintex Forms on a web application

1. On the Central Administration Home page, click Application Management.

2. In the Web Applications section, click Manage web applications.

3. In the Name column, select the web application on which you want to activateNintex Forms.

For example, select SharePoint -80.

4. In the Web Applications ribbon, click Manage Features.

The Manage Web Application Features dialog box appears.

5. In the Nintex Forms section, click Activate.

After a short delay, the dialog box refreshes and the status is "Active."

6. Click OK.

Connect and enable Nintex LiveThis section applies to installation of Nintex Live. If you are not installing Nintex Live,you can skip this section.

Connecting and enabling Nintex Live involves establishing a connection to Nintex Live,enabling Nintex Live for Nintex Workflow and Nintex Forms, registering the SharePointfarm, and optionally changing the managed user account that runs the Nintex Live ser-vices.

Following are the features requiring enabling for Nintex Live:

l Nintex Live for Nintex Workflow: Allows users to add web services from theNintex Live Catalog to the Nintex workflow actions toolbox.

l Nintex Live Forms: Allows form designers to make designated forms available tointernet users via Nintex Live, with anonymous or secure access via third-partyauthentication providers.

To connect and enable Nintex Live

1. If Nintex Live was not installed from the installer, manually install and deploy it.

The Nintex Live solution is named nintexlivecore.wsp; you must also import allcertificates from the “Certs” folder. This solution and its certificates are locatedin the installation folder for Nintex Workflow and for Nintex Forms when the rel-evant option is selected from the installer, causing the solution to be exported forlater deployment.


-23-




27/39

2. If Nintex Live was installed on a machine that does not host SharePoint CentralAdministration, run the following command:

a. Log on to the server hosting SharePoint Central Administration.

b. Open a SharePoint PowerShell command prompt and run the followingcommand:

install-liveservice

3. Make sure the certificates used by Nintex Live are available.

a. On the Central Administration Home page, select Security.

b. In the General Security section, click Manage trust.

c. Review availability of the following certificates; if any are unavailable,update to make them available.

l Baltimore CyberTrust Root.crt

l GTE CyberTrust Global Root.cer

l Microsoft Internet Authority.cer

l Microsoft Secure Server Authority.cer

l Thawte Primary Root CA.cerl Thawte SSL CA.cer

4. Enable Nintex Live for Nintex Workflow.

a. On the Central Administration Home page, select Nintex Workflow Man-agement.

b. Click Live settings.

c. In the Enable Nintex Live for Nintex Workflow section, click Enable andthen click OK.

5. Enable Nintex Live for Nintex Forms.

a. On the Central Administration Home page, select Nintex Forms Man-agement.

b. Click Live Forms settings.

c. In the Enable Nintex Live Forms section, click Enable.

d. To allow Live Forms to be submitted by anonymous users over the Inter-net, in the Allow anonymous form submissions section, select Yes, andthen confirm the action.

Note: Allowing anonymous form submissions may requireMicrosoft server internet licensing.


-24-




28/39

6. Establish a connection to Nintex Live.

The Nintex Live Framework (installed with Nintex Live) requires a connection tothe internet to communicate with Nintex Live.

a. On the Central Administration Home page, select Nintex Live Man-agement.

b. Click Health Checks.

If the connection to Nintex Live can be established, a "Success" messageis displayed in the status column.

Note: If your network requires a proxy server to access the inter-net, specify the server details in the Proxy server section. Thesesettings are specific to the Nintex Live Framework and will be theonly application allowed access to the internet.

7. Confirm that the server can access the Nintex Live URLs: From the server run-ning the Nintex Live services, navigate to each of the following URLs.

l https://live.nintex.com

l https://liveservices.nintex.com

l https://nintexlive.blob.core.windows.net/serviceicon

l https://nintexrelay.servicebus.windows.net/

Nintex Live Relay Service accesses these URLs for both Nintex Workflow andNintex Forms.

8. Nintex Forms: Register the SharePoint farm for Nintex Live for Mobile Access.

a. If you have a firewall in place, make the following ports accessible (theports will be used by Nintex Live Relay Service).

l 9351/HTTP

l 80/HTTP

l 443/HTTPb. On the Central Administration Home page, click Application Man-

agement.

c. In the Service Applications section, click Manage services on server.

d. Click Start for Nintex Live Relay Service.

e. Click Nintex Forms Management and then click Manage Live MobileAccess.

f. Click Enable.


-25-




29/39


30/39

3. Nintex Workflow: For each feature listed, in the sequence listed, click Activateto activate.

a. Activate Nintex Workflow 2013.

This feature allows SharePoint lists and libraries in this site collection toutilize Nintex Workflow features.

After a short delay, the page refreshes and the feature status becomes “Active.”

b. Activate each additional feature desired.

Feature (listed in alpha-betical order)

Description

Nintex Workflow 2013InfoPath Forms

Allows Nintex Workflow to use startforms and task forms designed withMicrosoft InfoPath 2013 or MicrosoftInfoPath 2010.

Nintex Workflow 2013Reporting Web Parts

Note: This feature isonly available for theEnterprise edition of Nintex Workflow.

Allows the Nintex Workflow Enter-prise reporting web parts to beadded to sites in this site collection.

Nintex Workflow 2013 WebParts

Allows the Nintex Workflow webparts to be added to sites in this sitecollection.

c. If using Nintex Live, activate Nintex Workflow - Nintex Live Catalog.

This feature allows Nintex Workflow designers to browse the Nintex LiveCatalog.

Note: This feature is only available if Nintex Live was installedand deployed.


-27-




31/39

4. Nintex Forms: For each feature listed, in the sequence listed, click Activate toactivate.

a. Activate Nintex Forms Prerequisites Feature.

This feature allows SharePoint lists and libraries in this site collection toutilize Nintex Forms features.

After a short delay, the page refreshes and the feature status becomes “Active.”

b. Activate each additional feature desired.

Feature (listed in alpha-betical order)

Description

Nintex Forms for NintexWorkflow

Allows Nintex Workflow in this site col-lection to utilize Nintex Forms fea-tures.

Nintex Forms forSharePoint List Forms

Allows SharePoint lists and libraries inthis site collection to utilizeNintex Forms features.

Nintex Live Forms Allows Nintex Forms designers to pub-

lish forms to Nintex Live

Nintex Forms features are now ready to use on all sites in the site col-lection; Nintex Workflow features require activation in each relevant sitein the site collection.

To activate features on each relevant site in your SharePoint environment (Nintex Workflow

only)


1. From your top site level home page, access Site Settings (in SharePoint 2013,use the gear icon).

2. In the Site Actions section, click Manage site features.

3. On the Site Features page, for each desired feature, click Activate.

Feature (listed in alphabetical order) Functionality

Nintex Workflow 2013 Nintex Workflow

Nintex Workflow 2013 EnterpriseReporting

Note: This feature is only availablefor the Enterprise edition of Nintex Workflow.

Nintex Workflow Enterprisereporting

After a short delay for each feature activation, the page refreshes and the fea-

ture status becomes “Active.”

Nintex Workflow features are now ready to use on the site.


-28-




32/39

Confirm production installation

This section provides guidance on confirming successful installation of Nintex products.This confirmation involves testing Nintex functionality, confirming that installer and con-figuration tasks were completed, and reinstating original server settings.

Test Nintex functionalityMake sure you test functionality for Nintex on each SharePoint list and library expectedto use Nintex Workflow or Nintex Forms.

To test functionality for Nintex Workflow (SharePoint document library)

l Select the Library tab from the ribbon, click Workflow Settings, and then selectNintex Workflow to display the Nintex Workflow designer; add workflow actionsand publish.

To test functionality for Nintex Workflow (SharePoint list)

l Select the List tab from the List Tools ribbon , click Workflow Settings, and thenselect Nintex Workflow to display the Nintex Workflow designer; add workflow

actions and publish.To test functionality for Nintex Forms (SharePoint list only)

l Select the List tab from the List Tools ribbon and then click Nintex Forms to dis-play configuration options for the default Nintex form.

Confirm installer and configuration tasks (optional)As part of confirming successful installation, you can confirm that expected installer andconfiguration tasks were completed. Following is a summary of these tasks.

l Nintex assemblies and features

l Solution deployments

l Licensingl Databases

l Enabled actions (safe controls)

Nintex assemblies and features

As part of confirming installation, you can check for Nintex-named assemblies andSharePoint features. The Nintex installers install assemblies and SharePoint features loc-ally.

Assemblies are installed into the Global Assembly Cache (GAC). Both .NET Framework3.5 and .NET Framework 4.0 assemblies are installed.

SharePoint features are installed into the SharePoint 2013 hive.

Solution deployments

During installation, the Nintex solutions need to be deployed to all required Web applic-ations. For more information, see "Steps for deploying solutions" on page 15.

To view deployment status for solutions in the farm


2. In the Farm Management section, click Manage farm solutions.

The Solution Management page appears. Solution deployment status is indicatedin the Status column; the Web applications to which the solutions are deployedare indicated in the Deployed To column.


-29-




33/39

Licensing

During installation, the license files for installed products need to be imported intoSharePoint Central Administration as indicated in "Import the license files" on page 17.

To view imported license files

l On the Central Administration Home page, click the option for your product (Nin-

tex Workflow Management or Nintex Forms Management) and then clickLicensing.

l For Nintex Live, click Nintex Live Management and then click Health checks.

Databases

Successful installation of Nintex Workflow requires that a configuration database existas well as any additional Nintex content databases needed for your environment; all Nin-tex content databases must be mapped to the corresponding SharePoint content data-bases. For more information, see "Content databases and performance" on page 5.

For Nintex Forms, confirm that the automatically created database exists. See"Nintex Forms configuration" on page 23.

In addition to ensuring that all required databases are set up, confirm that the webapplication user accounts are members of the custom database role WSS_Content_Application_Pools for all Nintex databases. This membership configuration is completedby Nintex installers; the WSS_Content_Application_Pools database role has all requiredSELECT and EXECUTE rights to the database required for Nintex functionality.

To confirm database role memberships for web application user accounts

1. Identify the names of all web applications used by Nintex.

a. On the Central Administration Home page, click Application Man-agement.

b. In the Web Applications section, click Manage web applications.

Example name of web application: SharePoint - 80

2. Identify the user account for each web application.

a. On the Central Administration Home page, click Security.

b. In the General Security section, click Configure service accounts.

c. In the Service Accounts page, select the web application name identifiedin the previous step.

Note: The web application name is prefixed by the phrase "WebApplication Pool."Example: Web Application Pool - SharePoint - 80

The user account for the web application is identified under Select anaccount for this component.

Example user account: NINTEXTEST/PM13-SPWebApp01


-30-




34/39

3. View the database role membership for each user account on all Nintex data-bases.

a. View the login user accounts for the database server containing the Nintexdatabases: In Microsoft SQL Server Management Studio, expand the data-base server folder, expand the Security folder, and then expand theLogins folder.

b. Double-click the user account identified in the previous step to display theproperties dialog box.

c. Click the User Mapping page to view the databases mapped to the loginuser account.

d. For each Nintex database:

i. Confirm that the check box for the database is selected.

ii. Select the database to display the database role memberships, andthen confirm that the check box for WSS_Content_Application_ Pools is selected.

If the check box for the database is not selected, or if the check box forWSS_Content_Application_Pools is not selected, go ahead and selectit and then click OK.

Enabled actions (safe controls)

When workflow actions are enabled in SharePoint, the web.config files for the webapplications are updated with "safe controls."

To confirm that web.config files were updated with Nintex "safe controls"

l From IIS Manager, right-click the web application, select Explore to view its filesin Windows Explorer, and then open the web.config file in a text editor.

Example excerpt from web.config file indicating enabled actions:

Reinstate original server settingsWhen installation is complete, reinstate original server settings across the farm.

On the server used for running the installers, reinstate the following server settings(see "Set up server used for running installers" on page 8):

l User Account Control: reinstate at the original level

l User account rights: If you added the Farm Installation account (or other useraccount used for installation) to the Administrators group for the server on whichyou installed Nintex, remove the account from the group. Leaving the account inthe Administrators group results in report warnings from the SharePoint HealthAnalyzer.

l Group policy for script execution: reinstate if needed

On all servers in the farm, reinstate the following server settings (see "Disable antivirussoftware" on page 8):

l Antivirus software: re-enable original programs


-31-




35/39

Troubleshoot deployment

This section describes ways to narrow down deployment problems as well as resolutionsfor deployment issues that may come up.

Identify the problemThis section describes methods for narrowing down problems with solution deployment.

Deploy test solution packages

Deployment issues with the Nintex Workflow solution package (nin-texworkflow2013.wsp) may indicate an issue with the SharePoint environment. If yoususpect issues with the SharePoint environment, you can deploy test solution packagesto determine if the deployment issues persist.

The following test solution packages are available from Nintex:

l TestingSolutionGlobal.zip: This solution deploys globally; no URL needs to be spe-

cified. The solution creates the following file:C:\Program Files\Common Files\Microsoft Shared\Web Server Exten-sions\15\TEMPLATE\TestingSolutionGlobal.txt

If Solution 1 does deploy correctly, then please try Solution 2 as well, which isslightly more advanced.

l TestingSolutionForWebApps.zip: This solution requires selection of a web applic-ation. The solution creates the following file:

C:\Program Files\Common Files\Microsoft Shared\Web Server Exten-sions\15\TEMPLATE\TestingSolutionForWebApps.txt

The solution also deploys a file called SimpleSolution.dll to the GAC and adds anentry to the web.config f ile for the web application as follows:

Note: The SimpleSolution.dll contains no code that executes.

To deploy test solution packages

1. Download the test solution packages from the following URLs:

http://download.nintex.com/sl/supportfiles/TestingSolutionGlobal.zip

http://download.nintex.com/sl/supportfiles/TestingSolutionForWebApps.zip

2. Run the following command to add the solutions to the solution store:

stsadm.exe -o addsolution -filename

For a mapping of Stsadm operations and their equivalent Windows PowerShellcmdlets, see the following Microsoft TechNet article: http://-technet.microsoft.com/en-us/library/ff621081.aspx

3. Deploy the test solution packages from Central Administration. For instructions,see "Steps for deploying solutions" on page 15.

If deployment does not successfully complete with one or more of the test solu-tion packages, the SharePoint environment may have an issue. We suggest con-tacting Microsoft for additional support with your SharePoint environment.

If deployment successfully completes with both test solution packages, contactNintex Support.


-32-


http://download.nintex.com/sl/supportfiles/TestingSolutionForWebApps.ziphttp://download.nintex.com/sl/supportfiles/TestingSolutionForWebApps.ziphttp://download.nintex.com/sl/supportfiles/TestingSolutionGlobal.ziphttp://download.nintex.com/sl/supportfiles/TestingSolutionForWebApps.ziphttp://technet.microsoft.com/en-us/library/ff621081.aspxhttp://technet.microsoft.com/en-us/library/ff621081.aspxhttp://www.nintex.com/EN-US/SUPPORT/Pages/default.aspxhttp://www.nintex.com/en-US/Pages/NintexCookies.aspxhttps://www.nintex.com/en-US/Pages/TermsAndConditions.aspxhttps://www.nintex.com/en-US/Pages/Privacy.aspxhttp://technet.microsoft.com/en-us/library/ff621081.aspxhttp://technet.microsoft.com/en-us/library/ff621081.aspxhttp://download.nintex.com/sl/supportfiles/TestingSolutionForWebApps.ziphttp://download.nintex.com/sl/supportfiles/TestingSolutionGlobal.ziphttp://download.nintex.com/sl/supportfiles/TestingSolutionForWebApps.ziphttp://download.nintex.com/sl/supportfiles/TestingSolutionGlobal.zip


36/39

Review SharePoint ULS log files

The SharePoint Unified Logging Service (ULS) log files may contain helpful informationfor troubleshooting issues with deployment of solution packages.

For example, the following error suggests a critical timer job error related to internalSharePoint problems persisting objects to the database. These errors also mention an"update conflict" as experienced when attempting solution deployment. This underlyingissue may be preventing solution deployment and should thus be resolved. ContactMicrosoft for additional support if presented with this err or.

“The Execute method of job definition Microsoft.Of-fice.Server.Search.Administration.IndexingScheduleJobDefinition (ID xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx) threw an exception. More information isincluded below. An update conflict has occurred, and you must re-try this action.The object IndexingScheduleJobDefinition Name=Indexing Schedule Manager onservername Parent=SearchService Name=OSearch is being updated byDOMAIN\username, in the OWSTIMER process, on machine SERVERNAME. Viewthe tracing log for more information about the conflict."

By default, ULS logs are located in the SharePoint hive. For example, the default loc-

ation for SharePoint 2013 ULS logs is %ProgramFiles%\Common Files\MicrosoftShared\Web Server Extensions\15\Logs.

Note: For more information about ULS logging, see the following MSDN article.http://msdn.microsoft.com/en-us/library/office/ff595318(v=office.14).aspx.

In your review of the log files, search for logged information during the time range inwhich the solution was scheduled to be deployed.

To aggregate all log files from SharePoint servers

l Use the Merge-SPLogFile cmdlet in a SharePoint Management Shell window.

IssuesThis section provides guidance for resolving common issues related to deployment.

Installation error for "Admin SVC": Nintex Forms 2013

Symptom

The installer displays the following error message:

“Admin SVC must be running in order to create deployment timer job.”

Cause

The Microsoft Windows service SharePoint Administration is not running.

Resolution

Make sure that the service is running. For instructions, see "Ensure services are run-ning" on page 7.

LazyApproval issues occur

For help troubleshooting LazyApproval issues, see the following Nintex Connectarticle: LazyApproval Guide.


-33-


http://msdn.microsoft.com/en-us/library/office/ff595318(v=office.14).aspxhttp://technet.microsoft.com/en-us/library/ff607721(v=office.15).aspxhttp://www.nintex.com/EN-US/SUPPORT/Pages/default.as

Nintex Workflow 2013 Installation Guide

Documents

Transcript of Nintex Workflow 2013 Installation Guide