Upgrading Nintex Workflow 2007 to 2010

Document created by Emily Billing Employee on Jun 22, 2014Last modified by Pamela Denchfield on Apr 16, 2015
Version 8Show Document
  • View in full screen mode

1 Introduction

Before upgrading from Nintex Workflow 2007 to Nintex Workflow 2010, please ensure you are on the most current build of Nintex Workflow 2007 v1.13.1.

 

To upgrade to the latest build, see Product Downloads

For release notes and upgrade instructions, Nintex Workflow 2007 - Release Notes

 

You may also want to run the Nintex Workflow 2007 to 2010 Pre Update Check Tool. This provides a report of workflows in the SharePoint 2007 environment that may have an issue after upgrading to SharePoint 2010 and Nintex Workflow 2010.

 

This document describes the process to upgrade Nintex Workflow 2007 to Nintex Workflow 2010. It has two sections:

  • SharePoint “In Place” upgrade
  • SharePoint “Attach database” upgrade

 

The SharePoint method you use is your choice.

 

2 In-place Upgrade Method

SharePoint State: SharePoint 2007 has been completely upgraded to SharePoint 2010.

 

2.1 Before Upgrading

 

a) Moving Database

If you are moving the database to a different server or database name, please refer to Moving Nintex Workflow 2007 databases, and ensure that steps are followed in the Stage 2 - Update the references to the content databases topic which explains how to update internal references to the old server name stored within the database.

 

2.2 Uninstall Nintex Workflow 2007 MSI

  1. Log on to the server where the Nintex Workflow 2007 MSI was installed.
  2. Open Control Panel.
  3. Choose "Uninstall a program" ("Add remove programs" in earlier versions of Windows Server).
  4. Find Nintex Workflow 2007 and uninstall it.

 

2.3 Disable workflow timer job

  1. Browse to "Central Administration", click on "Monitoring".
    monitoring.png
  2. In Timer Jobs section, click on "Review job definitions".
  3. Click on the job called "Workflow" (it may not be listed on the first page).
    workflow.png
  4. Click the "Disable" button.

2.4 Remove Nintex Workflow 2007 Solution Packages

  1. Browse to "System Settings", click on "Manage farm solutions".
  2. Click on "NintexWorkflow2007.wsp".
  3. Select "Retract Solution".
  4. Wait for the solution to be retracted.
  5. Click on "NintexWorkflow2007.wsp" again.
  6. Select "Remove Solution".
  7. Repeat steps 2 – 6 as necessary for "NintexWorkflow2007EnterpriseFeatures.wsp" and “NintexWorkflow2007LiveConnector.wsp”.

 

2.5 Install and deploy Nintex Workflow 2010

Do the following. For instructions, see Installing Nintex Workflow 2010 and Nintex Forms 2010.

  • Run the installer for Nintex Workflow 2010
  • Deploy the solutions installed by the installer, including nintexlivecore.wsp if using Nintex Live

 

2.6 Import Nintex Workflow 2010 License

  1. Browse to "Nintex Workflow Management", click on "Licensing".
  2. Click the "Import" button, followed by the "Browse…" button.
  3. Select the Nintex Workflow 2010 license file.
  4. Click the “Import” button.

 

2.7 Update the Nintex Workflow Database

  1. Browse to "Nintex Workflow Management", click on "Database setup".
  2. A database update is available and will be indicated in green with an option to “Update now”. Click the "Update now" link.

update now.png

 

2.8 Web Application Activation

  1. Browse to "Nintex Workflow Management", click on "Web Application activation".
  2. Click the "Activate" button for all web applications that use Nintex Workflow.

 

2.9 Enable Nintex Workflow 2010 Workflow Actions

  1. Browse to "Nintex Workflow Management", click on "Manage allowed actions".
  2. Enable any new workflow actions.
  3. Perform an IISRESET on each web front end server.
  4. Restart the "SharePoint 2010 Timer" service on each web front end server.

 

2.10 Re-enable Nintex Live

  1. Browse to “Nintex Workflow Management”, click on “Live settings”.
  2. In the “Enable Nintex Live for Nintex Workflow”, click on the “Disable” button.
  3. Once the “Enable” button is available, click on the “Enable” button.
  4. Click “OK”.

 

2.11 Reactivate the workflow timer job

  1. Browse to "Central Administration", click on "Monitoring".
  2. In the “Timer Jobs” section, click on "Review job definitions".
  3. Click on the job called "Workflow".
  4. Click the "Enable" button.

 

3 Database Attach Upgrade Method

SharePoint State:

  • SharePoint 2010 installed and configured.
  • SharePoint 2007 content databases not yet attached.
  • The web application that will host the 2007 content has been created.

 

3.1 Before Upgrading

 

a) Nintex Live

Important: If Nintex Live is in use, take note of the Live ID.

  1. Browse to “Application Management”, in the “Nintex Workflow Management” section, click on “Live settings”.
  2. Note the Live ID. This Live ID will need to be specified in the SharePoint 2010 environment.
  3. Click OK.

 

3.2 Prepare your SharePoint 2010 environment

In preparation for the upgrade to Nintex Workflow 2010, all services that host/interoperate with the SharePoint workflow engine must be stopped.

 

a) Disable workflow timer job

  1. Browse to "Central Administration", click on "Monitoring".
  2. In the “Timer Jobs” section, click on "Review job definitions".
  3. Click on the job called "Workflow" (it may not be listed on the first page).
  4. Click the "Disable" button.

 

3.3 Install Nintex Workflow 2010

Do the following. For instructions, see Installing Nintex Workflow 2010 and Nintex Forms 2010.

  • Run the installer for Nintex Workflow 2010
  • Deploy the solutions installed by the installer, including nintexlivecore.wsp if using Nintex Live
  • Import licenses for Nintex Workflow 2010
  • Connect and enable Nintex Live (optional)

 

3.4 Nintex Workflow Configuration Database

 

a) Using a new configuration database

  1. Browse to "Nintex Workflow Management", click on "Database setup".
  2. Click the “Create” button in “Configuration Database”.
  3. Enter the name of your database server and database name.
  4. Click “OK”.

Note: A content database is created automatically. If the content database is not required, please follow the steps listed in step 6 of “Using an existing configuration database” to remove the reference.

  1. If using Nintex Live, add any Nintex Live services that were used in the 2007 environment using the Nintex Live Catalog. To add a Nintex Live service:
  2. Navigate to “Managed allowed actions”, in the Ribbon, click on “Catalog”.
  3. Select the Nintex Live service(s), click “Add”.
  4. Click “OK”.

Note: If a Nintex Live service was used in Nintex Workflow 2007, ensure that the Nintex Live service is also added in the 2010 environment; else an error message will be displayed when the content databases are attached.

 

b) Using an existing configuration database

 

In the SharePoint 2007 environment:

  1. Stop the “Windows SharePoint Services Timer” service. To stop the service:
    1. Open the “Start Menu”, select “Run” and type “Services.msc”.
    2. Locate the service. Right-click on the service and select “Stop”.
  2. Run “NWAdmin.exe –o DetachDatabase –serverName <myservername> -databaseName <mydatabasename>”. To run the NWAdmin command:
    1. Navigate to the “Start Menu” and click on “Command Prompt” option.
    2. Type the following: cd “C:\Program Files (x86)\Nintex\Nintex Workflow 2007”
    3. Type the following: NWAdmin.exe –o DetachDatabase –serverName <myservername> -databaseName <mydatabasename>
  3. Backup the database (using “Microsoft SQL Server Management Studio”).
  4. Start the “Windows SharePoint Services Timer”. To start the service:
    1. Open the “Start menu”, select “Run” and type “Services.msc”.
    2. Locate the service. Right-click on the service and select “Start”.

 

In the SharePoint 2010 environment:

  1. Restore the database that was backed up in step 3 to the 2010 location (using “Microsoft SQL Server Management Studio”).
  2. Execute “_PrepareForNewEnvironment” stored procedure.
    1. Launch “Microsoft SQL Server Management Studio” and open (expand) the restored database.
    2. Expand “Programmability” folder, expand the “Stored Procedures” folder.
    3. Right-click on the listing for “_PrepareForNewEnvironment” and choose “Execute Stored Procedure…”.
    4. In the opened dialog, click the “OK” button.

                Note: This stored procedure deletes existing references to content databases and Nintex Live service requests. These references will be re-added as needed when existing content databases are reattached.

  1. Navigate to Nintex Workflow Management and connect to the configuration database. To connect to an existing configuration database:
    1. Browse to "Nintex Workflow Management", click on "Database setup".
    2. Click the “Create” button in “Configuration Database”.
    3. Enter the name of your database server and existing configuration database name.
    4. Select the option “Connect to an existing database”.
    5. Click “OK”.

 

3.5 Enable Nintex Workflow 2010 Workflow Actions

  1. Browse to "Nintex Workflow Management", click on "Manage allowed actions".
  2. Enable any new workflow actions.

 

3.6 Restoring the Live ID

  1. Browse to “Nintex Live Management”, click on “Connection settings”.
  2. Select the option “Override Live ID” and replace it with the Live ID noted in the SharePoint 2007 environment before the upgrade.
  3. Click OK.

 

3.7 Attach SharePoint 2007 content database

Attach your SharePoint 2007 content database as following Microsoft’s guidance.

 

3.8 Attaching Nintex Workflow Content Databases

 

Note: Content databases can be added gradually over time as SharePoint content databases are migrated. Ideally, there is a one-to-one mapping between a SharePoint database and a Nintex Workflow database.

 

A one-to-one mapping between SharePoint databases and Nintex Workflow can be achieved by using the NWAdmin –o MoveData command to split data from one database to many. Refer to NWAdmin Operations - Nintex Workflow 2010 for more information.

 

Note: If the content database you are migrating is the same physical database as the configuration database, start from step 6 below to attach the database as a content database in SharePoint 2010.

 

In the SharePoint 2007 environment:

  1. Stop the “Windows SharePoint Services Timer” service. To stop the service:
    1. Open the “Start Menu”, select “Run” and type “Services.msc”.
    2. Locate the service. Right-click on the service and select “Stop”.
  2. Run “NWAdmin.exe –o DetachDatabase –serverName <myservername> -databaseName <mydatabasename>”. To run the NWAdmin command:
    1. Navigate to the “Start Menu” and click on “Command Prompt” option.
    2. Type the following: cd “C:\Program Files (x86)\Nintex\Nintex Workflow 2007”
    3. Type the following: NWAdmin.exe –o DetachDatabase –serverName <myservername> -databaseName <mydatabasename>
  3. Backup the database (using “Microsoft SQL Server Management Studio”).
  4. Start the “Windows SharePoint Services Timer”. To start the service:
    1. Open the “Start menu”, select “Run” and type “Services.msc”.
    2. Locate the service. Right-click on the service and select “Start”.

 

In the SharePoint 2010 environment:

(Note: The Workflow job should be stopped at this point as instructed in “Disable workflow timer job”)

  1. Restore the database that was backed up in step 3 to the 2010 location (using “Microsoft SQL Server Management Studio”).
  2. Run “NWAdmin.exe –o AttachDatabase –serverName <myservername> –databaseName <mydatabaseName>”.
    1. Navigate to the “Start Menu” and click on “Command Prompt” option.
    2. Use the "cd" command to navigate to the directory containing the NWAdmin.exe tool.
      By default, the NWAdmin.exe tool is installed to the SharePoint hive, typically at the following path.
      %ProgramFiles%\Common Files\Microsoft Shared\Web Server Extensions\14\BIN
      Note: For some versions of Nintex Workflow 2010, the NWAdmin tool is installed in the installation directory, typically at the following path:
      %ProgramFiles%\Nintex\Nintex Workflow 2010.
    3. Type the following: NWAdmin.exe –o AttachDatabase –serverName <myservername> -databaseName <mydatabasename>

 

Why do I have to run a detach command before backing up the database?

 

The detach command must be used to store some data from the 2007 environment that is not initially present in the content database. For example, when the DetachDatabase command is run, information on pending Nintex Live service requests is stored in the content database. When the AttachDatabase command is run in the 2010 environment, the data is extracted from the database into the environment. If these steps were not followed, the workflows waiting at a Nintex Live service request would never continue.

3.9 Web Application Activation

  1. Browse to “Nintex Workflow Management”, click on “Web Application Activation”.
  2. The default web application name should be automatically chosen. Click “Activate”.

 

3.10 Map SharePoint Content Database to Nintex Workflow Content Database

  1. Configure a mapping for the SharePoint content database and the Nintex Workflow content database.
    1. Browse to "Nintex Workflow Management", click on "Database setup".
    2. Click on “Manage database mappings”.
    3. To map a “SharePoint Content Database” select the desired database in the “Map to Workflow Content Database” drop-down.

 

3.11 Restart all services that were stopped in the pre-installation phase

  1. Enable the Workflow timer job in Central Administration.
  2. Restart the SharePoint 2010 timer service in Server Manager to ensure any cached data pertaining to Nintex Workflow is purged.

Attachments

    Outcomes