EMC ApplicationXtender Workflow Manager 8.1 Installation Guide

EMC ® ApplicationXtender ®
Workflow Manager
Version 8.1
Installation Guide
EMC Corporation
Corporate Headquarters
Hopkinton, MA 01748-9103
1-508-435-1000
www.EMC.com
Legal Notice
Copyright © 2009–2017 EMC Corporation. All Rights Reserved.
EMC believes the information in this publication is accurate as of its publication date. The information is subject to change
without notice.
THE INFORMATION IN THIS PUBLICATION IS PROVIDED “AS IS.” EMC CORPORATION MAKES NO REPRESENTATIONS
OR WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION IN THIS PUBLICATION, AND SPECIFICALLY
DISCLAIMS IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Use, copying, and distribution of any EMC software described in this publication requires an applicable software license.
For the most up-to-date listing of EMC product names, see EMC Corporation Trademarks on EMC.com. Adobe and Adobe PDF
Library are trademarks or registered trademarks of Adobe Systems Inc. in the U.S. and other countries. All other trademarks
used herein are the property of their respective owners.
Documentation Feedback
Your opinion matters. We want to hear from you regarding our product documentation. If you have feedback
about how we can make our documentation better or easier to use, please send us your feedback directly at
ECD.Documentation.Feedback@emc.com
Table of Contents
..................................................................................................................
5
.....................................................................................................
7
........................................................................................
Planning the installation ...................................................................................
Installation prerequisites ...................................................................................
ApplicationXtender Workflow Manager .........................................................
ApplicationXtender Integration Framework components ................................
9
Revision History
Chapter 1
Overview
Chapter 2
Before You Install
Chapter 3
Chapter 4
Chapter 5
...................................................................................................
Installing ApplicationXtender Workflow Manager ..............................................
Installing ApplicationXtender Integration Framework components .....................
Installing the EDB and WIM on the same machine ..........................................
Installing the EDB and WIM on Separate Machines.........................................
Installing EDB ..........................................................................................
Installing WIM .........................................................................................
Verifying the installation ...............................................................................
Installation
.................................................................................
Upgrading ApplicationXtender Workflow Manager............................................
Backing up before upgrading ........................................................................
Planning the upgrade ...................................................................................
Upgrading ApplicationXtender Workflow Manager 6.5 SP2 to 8.1....................
Prerequisites ............................................................................................
Upgrading the installation package to Workflow Manager 8.1 .....................
Upgrading the database ............................................................................
Upgrading SQL server database ............................................................
Upgrading Oracle database ...................................................................
Applying Wonderware Skelta BPM 2014 – Advanced Server license.............
Verifying the upgrade process ...................................................................
Rolling back the upgrade ..........................................................................
Upgrading ApplicationXtender Workflow Manager 7.0 SP1 to 8.1....................
Prerequisites ............................................................................................
Upgrading the installation package to Workflow Manager 8.1 .....................
Upgrading the database ............................................................................
Upgrading SQL server database ............................................................
Upgrading Oracle database ...................................................................
Applying Wonderware Skelta BPM 2014 – Advanced Server license.............
Verifying the upgrade process ...................................................................
Rolling back the upgrade ..........................................................................
Upgrading ApplicationXtender Integration Framework components ...................
Upgrade Your Product
9
9
9
9
11
11
12
12
13
13
13
14
15
15
15
15
16
16
16
17
17
19
21
21
22
22
22
23
24
24
25
27
27
27
28
................................................................................... 29
Migrating ApplicationXtender Workflow Manager 8.1 Server .............................. 29
Backing up the database before migrating Workflow Manager Server .............. 29
Migrate Your Product
3
Table of Contents
Installing ApplicationXtender Workflow Manager 8.1 on new Server ...............
Migrating Workflow Server to new server ......................................................
Verifying ApplicationXtender Workflow Manager 8.1 Server
migration .....................................................................................................
Rolling back the migration ............................................................................
Migrating ApplicationXtender Workflow 8.1 Databases to new
Database server ................................................................................................
Backing up database before migrating databases to the new server ..................
Before migrating the database .......................................................................
Moving databases .........................................................................................
Redirecting to use new farm database ............................................................
Redirecting repository DataSources to use new database server .......................
Verifying database migration.........................................................................
Rolling back the database migration ..............................................................
4
29
29
30
30
31
31
31
31
32
32
32
33
Revision History
Revision Date
Description
January 2017
Initial publication.
5
Revision History
6
Chapter 1
Overview
This document provides instructions to successfully install ApplicationXtender Workflow Manager
8.1 and upgrade ApplicationXtender Workflow Manager 6.5 SP2 or 7.0 SP1 to 8.1. ApplicationXtender
Integration Framework components including Event Dispatch Broker (EDB) and Workflow
Integration Module (WIM) are required to integrate ApplicationXtender Workflow Manager with
other ApplicationXtender products such as ApplicationXtender Web Access, Document Manager,
and so on. The document also provides instructions to install and upgrade ApplicationXtender
EDB and WIM.
7
Overview
8
Chapter 2
Before You Install
Planning the installation
Wonderware Sketla BPM 2014 R2 SP1 Administrator Guide contains details about Workflow Manager
installation planning. Wonderware Skelta documents are available as help files you can install in
a standalone mode. You can download ApplicationXtender Workflow Manager Online Help from
EMC Online Support site. It contains Wonderware Sketla BPM 2014 R2 SP1 Administrator Guide and
other Wonderware Skelta BPM guides.
Installation prerequisites
ApplicationXtender Workflow Manager
Wonderware Skelta BPM 2014 R2 SP1 Administrator Guide contains prerequisites for installing
ApplicationXtender Workflow Manager.
ApplicationXtender Integration Framework components
• Microsoft .NET Framework 4.0
• Microsoft System CLR Types for SQL Server 2012
• Microsoft SQL Server 2012 Management Objects
• For Windows Server 2012, .NET Framework 4.5 features (WCF Services) is required to install EDB.
9
Before You Install
10
Chapter 3
Installation
Installing ApplicationXtender Workflow
Manager
1.
Locate the ApplicationXtender Workflow Manager.exe and select Run as administrator.
2.
Click Install if you are prompted to install any required software.
3.
Click Next on the ApplicationXtender Workflow Manager Welcome page.
4.
In the License agreement page, read the license agreement, select the option I accept the terms of
the license agreement and click Next.
5.
In the Customer Information page, provide customer information and specify who may use
the application.
6.
Click Next.
7.
In the Destination Folder page, to change the default installation directory, click Change and
specify a new directory if you want to change the destination folder.
8.
Click Next.
9.
In the URL for AxServicesInterface.asmx page, specify the location of the ApplicationXtender
Web Services interface as follows:
To specify the location of the interface on a dedicated ApplicationXtender Web Services server,
enter http://<machine name>/AppXtenderServices/AxServicesInterface.asmx,
where <machine name> is the hostname or IP address of the ApplicationXtender Web Services
server.
Note: The ApplicationXtender Web Service URL is required during installation. The
ApplicationXtender Web Access URL will not work as no integrated Web Service is available
from ApplicationXtender 8.0 onwards.
10. Click Next. The installation wizard validates the location of the Web Services machine and then
displays the Ready to Install the Program page.
11. Click Install.
12. Click Finish.
The wizard starts the Workflow Manager Farm Configuration wizard. Skelta BPM.NET 2014 R2
SP1 Administrator Guide provides more information about configuration.
11
Installation
Installing ApplicationXtender Integration
Framework components
The ApplicationXtender Integration Framework Components integrate the ApplicationXtender
Workflow Manager with other ApplicationXtender products. The setup package contains the
installation files for EDB and the WIM.
EDB and WIM can be installed on the same computer or installed separately. You can adopt
installation strategy based on your requirements.
Installing the EDB and WIM on the same machine
Install the components on the same machine if the machine has enough processing power to handle
the anticipated volume of transactions.
1.
Navigate to the setup package and run the setup.exe file.
2.
Install the prerequisite software if prompted. If the wizard displays a message indicating that
a reboot is necessary, click Yes to reboot your machine. After you reboot, click Install again
to resume the setup. The installation wizard displays the Welcome screen after all required
components have been located or installed.
3.
Click Next.
4.
In the License Agreement page, read and accept the license agreement and click Next.
5.
In the Customer Information page, provide customer information and specify who may use
the application.
6.
Click Next.
7.
In the Setup Type page, select Complete and click Next.
8.
In the Select Web Application page, select Default Web Site from the Site List and click Next.
9.
In the Destination Folder page, click Next.
10. In the WIM Configuration page, specify the URL for ApplicationXtender Web Access.
11. Specify user account credentials for the WIM service. The WIM uses the account to communicate
with the EDB.
Note: The user account must be associated with the Log on as a service policy in the WIM
machine security settings. Refer to the operating system help for information on how to assign
user rights.
12. Click Next.
13. In the Ready to Install the Program page, click Install.
14. Click Finish.
12
Installation
Installing the EDB and WIM on Separate Machines
Install the components on separate computers if one computer does not have enough processing
power to handle the anticipated volume of transactions.
Installing EDB
1.
Navigate to the setup package and run the setup.exe file.
2.
Install the prerequisite software if prompted. If the wizard displays a message indicating that a
reboot is necessary, click Yes to reboot your computer. After you reboot, click Install again
to resume the setup. The installation wizard displays the Welcome screen after all required
components have been located or installed.
3.
Click Next.
4.
In the License Agreement page, read and accept the license agreement and click Next.
5.
In the Customer Information page, provide customer information and specify who may use
the application.
6.
Click Next.
7.
In the Setup Type page, select Complete and click Next.
8.
In the Custom Setup page, specify the following installation options:
• Select ApplicationXtender Event Dispatch Broker.
• Clear Workflow Integration Module and ApplicationXtender Workflow Manager.
9.
Click Next.
10. In the Select Web Application page, select Default Web Site from the Site List and click Next.
11. In the Destination Folder page, click Next.
12. In the Ready to Install the Program page, click Install.
13. Click Finish.
Installing WIM
1.
Navigate to the setup package and run the setup.exe file.
2.
Install the prerequisite software if prompted. If the wizard displays a message indicating that a
reboot is necessary, click Yes to reboot your computer. After you reboot, click Install again
to resume the setup. The installation wizard displays the Welcome screen after all required
components have been located or installed.
3.
Click Next.
4.
In the License Agreement page, read and accept the license agreement and click Next.
5.
In the Customer Information page, provide customer information and specify who may use
the application.
13
Installation
6.
Click Next.
7.
In the Setup Type page, select Complete and click Next.
8.
In the Custom Setup page, specify the following installation options:
• Clear ApplicationXtender Event Dispatch Broker.
• Select Workflow Integration Module.
• To install support files for ApplicationXtender Workflow Manager, select ApplicationXtender
Workflow Manager.
9.
Click Next.
10. In the WIM Configuration page, specify the EDB server address in Event Dispatch Broker URL.
11. If you use ApplicationXtender Workflow Manager, specify the Web Access application URL in
AX Web Access URL.
12. Specify the user account credentials for the WIM service. The WIM uses the account to
communicate with the EDB.
Note: The user account must be associated with the Log on as a service policy in the WIM
computer security settings. Refer to the operating system help for information about how
to assign user rights.
13. Click Next.
14. In the Ready to Install the Program page, click Install.
15. Click Finish.
Verifying the installation
1.
Verify that ApplicationXtender Event Dispatch Broker 8.0 SP1 is available in Windows
Programs and Features.
2.
Verify that Event Dispatch Broker Database Configuration appears under All Programs >
ApplicationXtender Event Dispatch Broker.
3.
Verify that EDB site appears in the IIS Manager under Web Sites > Default Web Site.
4.
If you installed the WIM component, verify that the AppXtender WIM service appears in the
Windows Services console. The AppXtender WIM service starts automatically, by default.
14
Chapter 4
Upgrade Your Product
Upgrading ApplicationXtender Workflow
Manager
Backing up before upgrading
As you may encounter unexpected issues during the upgrade and migration process, ensure that you
take a backup of databases before the upgrade and migration process. You can then roll back the
upgrading and migration. You can follow any approach supplied by the database vendor to back up
your workflow-related databases including the farm and repository databases.
Proposed approach to take a backup of the SQL Server databases:
1.
Stop SQL Service.
2.
Copy Workflow Manager Database and log files to a new location.
3.
Start SQL Service.
Note: If the Workflow Manager server is running on a virtual machine, you can create a snapshot
before upgrading. Later, you can revert to the snapshot if you want to rollback the upgrading process.
Planning the upgrade
You can upgrade to ApplicationXtender Workflow Manager 8.1 from the following versions:
• ApplicationXtender Workflow Manager 6.5 SP2, see Upgrading ApplicationXtender Workflow
Manager 6.5 SP2 to 8.1, page 16.
• ApplicationXtender Workflow Manager 7.0 SP1, see Upgrading ApplicationXtender Workflow
Manager 7.0 SP1 to 8.1, page 22.
ApplicationXtender Workflow Manager 6.5 SP2 and 7.0 SP1 are supported to run on Windows
Server 2008 R2 and SQL Server 2008 R2. ApplicationXtender Workflow Manager 8.1 continues
to be supported on Windows Server 2008 R2 and SQL Server 2008 R2. You can upgrade to
ApplicationXtender Workflow Manager 8.1 on Windows Server 2008 R2 with SQL Server 2008 R2
without migration.
However, ApplicationXtender Workflow Manager 8.1 is supported on newer versions of Windows
Server and database server. If you need to run ApplicationXtender Workflow Manager 8.1 on a later
version of Windows Server and database server. You must upgrade Workflow Manager Server
to version 8.1 on the original Windows Server 2008 R2 first, and then migrate to the later version
of Windows Server and database server. See Migrating ApplicationXtender Workflow Manager
15
Upgrade Your Product
8.1 Server, page 29 and Migrating ApplicationXtender Workflow 8.1 Databases to new Database
server, page 31.
It is mandatory that all users have logged out of the current ApplicationXtender and Workflow
Manager system. Ensure that you schedule a downtime officially to complete the upgrade and
migration.
Upgrading ApplicationXtender Workflow Manager 6.5
SP2 to 8.1
Prerequisites
Follow the instructions in Backing up before upgrading, page 15 to take a backup of your system
and databases.
Tasks to complete before upgrading:
1.
Make sure no user is connected to the Workflow Server.
2.
Deactivate the Skelta licenses.
3.
Delete Skelta license files (*.Lic and *.LicActivation). The default location of the license files is
C:\Program Files\XtenderSolutions\Content Management\ApplicationXtender
Workflow Manager\Bin.
4.
Stop ApplicationXtender WIM Service (WIM.exe).
5.
Stop ApplicationXtender Scheduler Service (AxSchedulerService.exe) which is installed
with EDB.
6.
Stop the following Skelta Services:
• ArchestrA Mobile Notification Service (ArchestrAMobileNotificationService.exe)
• Skelta - Advanced Server (AdvServr.NET2.exe)
• Skelta - Client Service (SKClientSrv.exe)
• Skelta - Communication Service (NotfnEng.NET2.exe)
• Skelta - Task Scheduler Service (TaskSked.NET2.exe)
• Skelta - Workflow Engine (WFEngine.NET2.exe)
It can take a few minutes to stop the services. Make sure the processes are stopped in the
Windows Task Manager after stopping the services.
Upgrading the installation package to Workflow Manager 8.1
The installation of Workflow Manager 8.1 will remove or uninstall Workflow Manager 6.5 SP2 from
the server, automatically.
Installing Workflow Manager 8.1 on the server:
16
Upgrade Your Product
1.
Locate ApplicationXtender Workflow Manager.exe and select Run as administrator.
2.
Click Install if the installation wizard prompts you to install any required software.
3.
Click Next on the ApplicationXtender Workflow Manager Welcome page.
4.
In the Related Product Found page, click Next.
5.
In the URL for AxServicesInterface.asmx page, specify the location of the ApplicationXtender
Web Services interface as follows:
To specify the location of the interface on a dedicated ApplicationXtender Web Services server,
enter http://<machine name>/AppXtenderServices/AxServicesInterface.asmx,
where <machine name> is the hostname or IP address of the ApplicationXtender Web Services
server.
Note: The ApplicationXtender Web Service URL is required during installation. The
ApplicationXtender Web Access URL will not work as no integrated Web Service is available
from ApplicationXtender 8.0.
6.
Click Next. The installation wizard validates the location of the Web Services and then shows the
Ready to Install the Program page.
7.
Click Install.
8.
Click Finish to complete the installation.
9.
Replace the bin folder in the EnterpriseConsole folder with the bin folder of the ECSite
folder. By default, the EnterpriseConsole and ECSite folders are located here: C:\Program
Files\XtenderSolutions\Content Management\ApplicationXtender Workflow
Manager\Web.
10. Replace the Web.Config file in the EnterpriseConsole folder with the Web.config file in
the ECSite folder.
Upgrading the database
The database upgrade procedure is determined by the database on which the system is running.
If ApplicationXtender Workflow Manager is running on SQL server, see Upgrading SQL server
database, page 17. If the system is running on Oracle, see Upgrading Oracle database, page 19.
Upgrading SQL server database
1.
Stop the following Skelta BPM services:
• ArchestrA Mobile Notification Service (ArchestrAMobileNotificationService.exe)
• Skelta - Advance Server (AdvServr.NET2.exe)
• Wonderware Skelta BPM - Client Service (SKClientSrv.exe)
• Skelta - Communication Service (NotfnEng.NET2.exe)
• Skelta - Task Scheduler (TaskSked.NET2.exe)
• Skelta - Workflow Engine (WFEngine.NET2.exe)
17
Upgrade Your Product
It can take a few minutes to stop the services. Make sure the processes are stopped in the
Windows Task Manager after stopping the services.
Note: Even if you stopped the service before installing ApplicationXtender Workflow Manager
8.1, the setup procedure may start the services again. Hence, you must stop the services again
manually.
2.
Delete the following files:
• Delete the caches files from %SystemRoot%\Temp\SkeltaBPMTemp.
• Delete the ASP.NET Temp Files from %SystemRoot%\Microsoft.NET\Framework64
\v2.0.50727\Temporary ASP.NET Files and %SystemRoot%\Microsoft.NET
\Framework64\v4.0.30319\Temporary ASP.NET Files.
3.
Launch cmd.exe as administrator.
4.
Navigate to .\Bin\Upgrade in the installation directory.
The default installation directory is C:\Program Files\XtenderSolutions\Content
Management\ApplicationXtender Workflow Manager.
5.
Run WFM6.52-7.0SP1 Upgrade Manager1.bat, click Upgrade and complete the
ApplicationXtender Workflow Manager Upgrade wizard.
6.
Run WFM6.52-7.0SP1 Upgrade Manager2.bat, click Upgrade and complete the
ApplicationXtender Workflow Manager Upgrade wizard.
7.
7. Stop the following Skelta BPM services::
• ArchestrA Mobile Notification Service (ArchestrAMobileNotificationService.exe)
• Skelta - Advance Server (AdvServr.NET2.exe)
• Wonderware Skelta BPM - Client Service (SKClientSrv.exe)
• Skelta - Communication Service (NotfnEng.NET2.exe)
• Skelta - Task Scheduler (TaskSked.NET2.exe)
• Skelta - Workflow Engine (WFEngine.NET2.exe)
It can take a few moments to stop the services. Make sure the processes are stopped in Windows
Task Manager after stopping the services.
8.
Delete the following files:
• Delete the caches files from %SystemRoot%\Temp\SkeltaBPMTemp.
• Delete the ASP.NET Temp Files from %SystemRoot%\Microsoft.NET\Framework64
\v2.0.50727\Temporary ASP.NET Files and %SystemRoot%\Microsoft.NET
\Framework64\v4.0.30319\Temporary ASP.NET Files.
9.
Run WFM7.0SP1-8.0SP1 Upgrade Manager1.bat.
10. In the ApplicationXtender Workflow Manager Upgrade wizard, click Upgrade and complete
the ApplicationXtender Workflow Manager Upgrade wizard.
11. After running the Upgrade Manager instance, you are prompted to restart the computer. Click
Restart.
18
Upgrade Your Product
12. After restarting the computer, stop the following Wonderware Skelta BPM services:
• Wonderware Skelta BPM - Advance Server (AdvServr.NET2.exe)
• Wonderware Skelta BPM - Client Service (SKClientSrv.exe)
• Wonderware Skelta BPM - Communication Service (NotfnEng.NET2.exe)
• Wonderware Skelta BPM - Task Scheduler (TaskSked.NET2.exe)
• Wonderware Skelta BPM - Workflow Engine (WFEngine.NET2.exe)
• Wonderware Skelta BPM - Mobile Notification Service
(ArchestrAMobileNotificationService.exe)
It might take a few moments to stop the services. Make sure the processes are stopped in
Windows Task Manager after stopping the services.
13. Launch cmd.exe as administrator again.
14. Navigate to .\Bin\Upgrade in the installation directory.
15. Run WFM7.0SP1-8.0SP1 Upgrade Manager2.bat.
16. In the ApplicationXtender Workflow Manager Upgrade wizard, click Upgrade and complete
the ApplicationXtender Workflow Manager Upgrade wizard.
Upgrading Oracle database
You must run SQL scripts manually to upgrade an Oracle database. The upgrade scripts are located in
the C:\Program Files\XtenderSolutions\Content Management\ApplicationXtender
Workflow Manager\Bin\Upgrade\OracleUpgradeScripts folder.
Note: It is recommended to run the scripts using the SQL *Plus command tool. After you run the
scripts, use the COMMIT statement to commit the changes.
1.
Stop the following Skelta BPM services:
• ArchestrA Mobile Notification Service (ArchestrAMobileNotificationService.exe)
• Skelta - Advance Server (AdvServr.NET2.exe)
• Wonderware Skelta BPM - Client Service (SKClientSrv.exe)
• Skelta - Communication Service (NotfnEng.NET2.exe)
• Skelta - Task Scheduler (TaskSked.NET2.exe)
• Skelta - Workflow Engine (WFEngine.NET2.exe)
It might take a few moments to stop the services. Make sure the processes are stopped in
Windows Task Manager after stopping the services.
Note: Even if you stopped the service before installing ApplicationXtender Workflow
Manager 8.1, the setup procedure may start the services again. Hence, you must stop the
services again manually. Run Oracle_WFM71Farm(Part1).sql on the farm database and
Oracle_WFM71DataSource(Part1).sql on the Repository databases, sequentially.
2.
Launch cmd.exe as administrator.
3.
Navigate to .\Bin\Upgrade in the installation directory.
19
Upgrade Your Product
The default installation directory is C:\Program Files\XtenderSolutions\Content
Management\ApplicationXtender Workflow Manager.
4.
Delete the following files:
• Delete the caches files from %SystemRoot%\Temp\SkeltaBPMTemp.
• Delete the ASP.NET Temp Files from %SystemRoot%\Microsoft.NET\Framework64
\v2.0.50727\Temporary ASP.NET Files and %SystemRoot%\Microsoft.NET
\Framework64\v4.0.30319\Temporary ASP.NET Files.
5.
Run WFM6.52-7.0SP1 Upgrade Manager1.bat, click the Update button and complete the
ApplicationXtender Workflow Manager Upgrade wizard.
6.
Run Oracle_WFM71Farm(Part2).sql on the farm database and Oracle_WFM71DataSource
(Part2).sql on the Repository database, sequentially.
7.
Run WFM6.52-7.0SP1 Upgrade Manager2.bat, click Upgrade and complete the
ApplicationXtender Workflow Manager Upgrade wizard.
8.
Stop the following Skelta BPM services:
• ArchestrA Mobile Notification Service (ArchestrAMobileNotificationService.exe)
• Skelta - Advance Server (AdvServr.NET2.exe)
• Wonderware Skelta BPM - Client Service (SKClientSrv.exe)
• Skelta - Communication Service (NotfnEng.NET2.exe)
• Skelta - Task Scheduler (TaskSked.NET2.exe)
• Skelta - Workflow Engine (WFEngine.NET2.exe)
It might take a few moments to stop the services. Make sure the corresponding processes are
stopped in Windows Task Manager after stopping the services.
9.
Delete the following files:
• Delete the caches files from %SystemRoot%\Temp\SkeltaBPMTemp.
• Delete the ASP.NET Temp Files from %SystemRoot%\Microsoft.NET\Framework64
\v2.0.50727\Temporary ASP.NET Files and %SystemRoot%\Microsoft.NET
\Framework64\v4.0.30319\Temporary ASP.NET Files.
10. Run Oracle_WFM81Farm(Part1).sql on the farm database and Oracle_WFM81DataSource
(Part1).sql on the Repository databases, sequentially.
11. Run WFM7.0SP1-8.0SP1 Upgrade Manager1.bat, click the Upgrade button and complete
the ApplicationXtender Workflow Manager Upgrade wizard.
Note: After running the Upgrade Manager instance, you are prompted to restart the computer.
12. Click Restart.
13. After restarting the computer, stop the following Wonderware Skelta BPM services:
• Wonderware Skelta BPM - Advance Server (AdvServr.NET2.exe)
• Wonderware Skelta BPM - Client Service (SKClientSrv.exe)
• Wonderware Skelta BPM - Communication Service (NotfnEng.NET2.exe)
• Wonderware Skelta BPM - Task Scheduler (TaskSked.NET2.exe)
20
Upgrade Your Product
• Wonderware Skelta BPM - Workflow Engine (WFEngine.NET2.exe)
• Wonderware Skelta BPM - Mobile Notification Service
(ArchestrAMobileNotificationService.exe)
It might take a few moments to stop the services. Make sure the corresponding processes are
stopped in Windows Task Manager after stopping the services.
14. Delete the following files:
• Delete the caches files from %SystemRoot%\Temp\SkeltaBPMTemp.
• Delete the ASP.NET Temp Files from %SystemRoot%\Microsoft.NET\Framework64
\v2.0.50727\Temporary ASP.NET Files and %SystemRoot%\Microsoft.NET
\Framework64\v4.0.30319\Temporary ASP.NET Files.
15. Run Oracle_WFM81Farm(Part2).sql on the farm database and Oracle_WFM81DataSource
(Part2).sql on the Repository databases, sequentially.
16. Launch cmd.exe as administrator again.
17. Navigate to .\Bin\Upgrade in the installation directory.
18. Run WFM7.0SP1-8.0SP1 Upgrade Manager2.bat, click Upgrade and complete the
ApplicationXtender Workflow Manager Upgrade wizard.
Applying Wonderware Skelta BPM 2014 – Advanced Server license
1.
Launch Workflow Configuration Manager.
2.
Click Next.
3.
Select Change Product Key.
4.
Click Next.
5.
Specify the new Wonderware Skelta BPM 2014-Advanced Server license key
6.
Click Next.
7.
Activate the license in the Activate license window.
Verifying the upgrade process
1.
Restart the Wonderware Skelta Services.
2.
Restart IIS.
3.
Launch Enterprise Console and confirm that workflow is functioning properly.
21
Upgrade Your Product
Rolling back the upgrade
If you encounter an issue while upgrading, you must rollback the system to the original state. If you
have created a snapshot of the virtual machine for the workflow server, revert to the snapshot. Later,
restore the database to the state before upgrading.
Alternatively, roll back the system using the following instructions:
1.
Uninstall Workflow Manager 8.1 on the server.
2.
Delete CentralConfig.Xml available here if the file exists: C:\Program
Files\XtenderSolutions\Content Management\ApplicationXtender Workflow
Manager.
3.
Delete the C:\Program Files\XtenderSolutions\Content Management
\ApplicationXtender Workflow Manager\Web\EnterpriseConsole folder.
4.
Delete the C:\Windows\Temp\SkeltaBPMTemp folder.
5.
Install ApplicationXtender Workflow Manager 6.5 SP2 on the server.
6.
Restore the databases to the original state before upgrading.
7.
Start the Farm Configuration wizard.
8.
Click Workflow Farm Recovery.
9.
Recover the server from the database.
Upgrading ApplicationXtender Workflow Manager 7.0
SP1 to 8.1
Prerequisites
Follow the instructions in Backing up before upgrading, page 15 to take a backup of your system
and databases.
Tasks to complete before upgrading:
1.
Make sure no user is connected to the Workflow Server.
2.
Deactivate the Skelta licenses.
3.
Delete Skelta license files (*.Lic and *.LicActivation). The default location of the license files is
C:\Program Files\XtenderSolutions\Content Management\ApplicationXtender
Workflow Manager\Bin.
4.
Stop ApplicationXtender WIM Service (WIM.exe).
5.
Stop ApplicationXtender Scheduler Service (AxSchedulerService.exe) which is installed
with EDB.
6.
Stop the following Skelta Services:
• ArchestrA Mobile Notification Service (ArchestrAMobileNotificationService.exe)
• Skelta - Advanced Server (AdvServr.NET2.exe)
22
Upgrade Your Product
• Skelta - Client Service (SKClientSrv.exe)
• Skelta - Communication Service (NotfnEng.NET2.exe)
• Skelta - Task Scheduler Service (TaskSked.NET2.exe)
• Skelta - Workflow Engine (WFEngine.NET2.exe)
It can take a few minutes to stop the services. Make sure the processes are stopped in the
Windows Task Manager after stopping the services.
Upgrading the installation package to Workflow Manager 8.1
The installation of Workflow Manager 8.1 will remove or uninstall Workflow Manager 7.0 SP1 from
the server, automatically.
Installing Workflow Manager 8.1 on the server:
1.
Locate ApplicationXtender Workflow Manager.exe and select Run as administrator.
2.
Click Install if the installation wizard prompts you to install any required software.
3.
Click Next on the ApplicationXtender Workflow Manager Welcome page.
4.
In the Related Product Found page, click Next.
5.
In the URL for AxServicesInterface.asmx page, specify the location of the ApplicationXtender
Web Services interface as follows:
To specify the location of the interface on a dedicated ApplicationXtender Web Services server,
enter http://<machine name>/AppXtenderServices/AxServicesInterface.asmx,
where <machine name> is the hostname or IP address of the ApplicationXtender Web Services
server.
Note: The ApplicationXtender Web Service URL is required during installation. The
ApplicationXtender Web Access URL will not work as no integrated Web Service is available
from ApplicationXtender 8.0.
6.
Click Next. The installation wizard validates the location of the Web Services and then shows the
Ready to Install the Program page.
7.
Click Install.
8.
Click Finish to complete the installation.
9.
Replace the bin folder in the EnterpriseConsole folder with the bin folder of the ECSite
folder. By default, the EnterpriseConsole and ECSite folders are located here: C:\Program
Files\XtenderSolutions\Content Management\ApplicationXtender Workflow
Manager\Web.
10. Replace the Web.Config file in the EnterpriseConsole folder with the Web.config file in
the ECSite folder.
23
Upgrade Your Product
Upgrading the database
The database upgrade procedure is determined by the database on which the system is running.
If ApplicationXtender Workflow Manager is running on SQL server, see Upgrading SQL server
database, page 24. If the system is running on Oracle, see Upgrading Oracle database, page 25.
Upgrading SQL server database
1.
Stop the following Skelta BPM services:
• ArchestrA Mobile Notification Service (ArchestrAMobileNotificationService.exe)
• Skelta - Advance Server (AdvServr.NET2.exe)
• Wonderware Skelta BPM - Client Service (SKClientSrv.exe)
• Skelta - Communication Service (NotfnEng.NET2.exe)
• Skelta - Task Scheduler (TaskSked.NET2.exe)
• Skelta - Workflow Engine (WFEngine.NET2.exe)
It can take a few minutes to stop the services. Make sure the processes are stopped in the
Windows Task Manager after stopping the services.
Note: Even if you stopped the service before installing ApplicationXtender Workflow Manager
8.1, the setup procedure may start the services again. Hence, you must stop the services again
manually.
2.
Delete the following files:
• Delete the caches files from %SystemRoot%\Temp\SkeltaBPMTemp.
• Delete the ASP.NET Temp Files from %SystemRoot%\Microsoft.NET\Framework64
\v2.0.50727\Temporary ASP.NET Files and %SystemRoot%\Microsoft.NET
\Framework64\v4.0.30319\Temporary ASP.NET Files.
3.
Launch cmd.exe as administrator.
4.
Navigate to .\Bin\Upgrade in the installation directory.
The default installation directory is C:\Program Files\XtenderSolutions\Content
Management\ApplicationXtender Workflow Manager.
5.
Run WFM7.0SP1-8.0SP1 Upgrade Manager1.bat.
6.
In the ApplicationXtender Workflow Manager Upgrade wizard, click Upgrade and complete
the ApplicationXtender Workflow Manager Upgrade wizard.
7.
After running the Upgrade Manager instance, you are prompted to restart the computer. Click
Restart.
8.
After the system has restarted, stop the following Wonderware Skelta BPM services:
• Wonderware Skelta BPM - Advance Server (AdvServr.NET2.exe)
• Wonderware Skelta BPM - Client Service (SKClientSrv.exe)
• Wonderware Skelta BPM - Communication Service (NotfnEng.NET2.exe)
• Wonderware Skelta BPM - Task Scheduler (TaskSked.NET2.exe)
24
Upgrade Your Product
• Wonderware Skelta BPM - Workflow Engine (WFEngine.NET2.exe)
• Wonderware Skelta BPM - Mobile Notification Service
(ArchestrAMobileNotificationService.exe)
It can take a few moments to stop the services. Make sure the processes are stopped in Windows
Task Manager after stopping the services.
9.
Delete the following files:
• Delete the caches files from %SystemRoot%\Temp\SkeltaBPMTemp.
• Delete the ASP.NET Temp Files from %SystemRoot%\Microsoft.NET\Framework64
\v2.0.50727\Temporary ASP.NET Files and %SystemRoot%\Microsoft.NET
\Framework64\v4.0.30319\Temporary ASP.NET Files.
10. Launch cmd.exe as administrator.
11. Navigate to .\Bin\Upgrade in the installation directory.
12. Run WFM7.0SP1-8.0SP1 Upgrade Manager2.bat.
13. In the ApplicationXtender Workflow Manager Upgrade wizard, click Upgrade and complete
the ApplicationXtender Workflow Manager Upgrade wizard.
Upgrading Oracle database
You must run SQL scripts manually to upgrade an Oracle database. The upgrade scripts are located in
the C:\Program Files\XtenderSolutions\Content Management\ApplicationXtender
Workflow Manager\Bin\Upgrade\OracleUpgradeScripts folder.
Note: It is recommended to run the scripts using the SQL *Plus command tool. After you run the
scripts, use the COMMIT statement to commit the changes.
1.
Stop the following Skelta BPM services:
• ArchestrA Mobile Notification Service (ArchestrAMobileNotificationService.exe)
• Skelta - Advance Server (AdvServr.NET2.exe)
• Wonderware Skelta BPM - Client Service (SKClientSrv.exe)
• Skelta - Communication Service (NotfnEng.NET2.exe)
• Skelta - Task Scheduler (TaskSked.NET2.exe)
• Skelta - Workflow Engine (WFEngine.NET2.exe)
It might take a few moments to stop the services. Make sure the processes are stopped in
Windows Task Manager after stopping the services.
Note: Even if you stopped the service before installing ApplicationXtender Workflow Manager
8.1, the setup procedure may start the services again. Hence, you must stop the services again
manually.
25
Upgrade Your Product
2.
Delete the following files:
• Delete the caches files from %SystemRoot%\Temp\SkeltaBPMTemp.
• Delete the ASP.NET Temp Files from SystemRoot%\Microsoft.NET\Framework64
\v2.0.50727\Temporary ASP.NET Files and %SystemRoot%\Microsoft.NET
\Framework64\v4.0.30319\Temporary ASP.NET Files.
3.
Run Oracle_WFM81Farm(Part1).sql on the farm database and Oracle_WFM81DataSource
(Part1).sql on the Repository databases, sequentially.
4.
Launch cmd.exe as administrator.
5.
Navigate to .\Bin\Upgrade in the installation directory.
The default installation directory is C:\Program Files\XtenderSolutions\Content
Management\ApplicationXtender Workflow Manager.
6.
Run WFM7.0SP1-8.0SP1.
7.
Upgrade Manager1.bat and click Upgrade and run the ApplicationXtender Workflow Manager
Upgrade wizard.
8.
After running the Upgrade Manager instance, you are prompted to restart the computer. Click
Restart.
9.
After restarting the system, stop the following Wonderware Skelta BPM services:
• Wonderware Skelta BPM - Advance Server (AdvServr.NET2.exe)
• Wonderware Skelta BPM - Client Service (SKClientSrv.exe)
• Wonderware Skelta BPM - Communication Service (NotfnEng.NET2.exe)
• Wonderware Skelta BPM - Task Scheduler (TaskSked.NET2.exe)
• Wonderware Skelta BPM - Workflow Engine (WFEngine.NET2.exe)
• Wonderware Skelta BPM - Mobile Notification Service
(ArchestrAMobileNotificationService.exe)
It might take a few moments to stop the services. Make sure the processes are stopped in
Windows Task Manager after stopping the services.
10. Delete the following files:
• Delete the caches files from %SystemRoot%\Temp\SkeltaBPMTemp.
• Delete the ASP.NET Temp Files from %SystemRoot%\Microsoft.NET\Framework64
\v2.0.50727\Temporary ASP.NET Files and %SystemRoot%\Microsoft.NET
\Framework64\v4.0.30319\Temporary ASP.NET Files.
11. Run Oracle_WFM81Farm(Part2).sql on the farm database and Oracle_WFM81DataSource
(Part2).sql on the Repository databases, sequentially.
12. Launch cmd.exe as administrator again.
13. Navigate to .\Bin\Upgrade in the installation directory.
14. Run WFM7.0SP1-8.0SP1 Upgrade Manager2.bat, click Upgrade and complete the
ApplicationXtender Workflow Manager Upgrade wizard.
26
Upgrade Your Product
Applying Wonderware Skelta BPM 2014 – Advanced Server license
1.
Launch the Workflow Configuration Manager.
2.
Click Next.
3.
Select Change Product Key.
4.
Click Next.
5.
Specify the new Wonderware Skelta BPM 2014-Advanced Server license key
6.
Click Next.
7.
Activate the license in the Activate license window.
Verifying the upgrade process
1.
Restart the Wonderware Skelta Services.
2.
Restart IIS.
3.
Launch Enterprise Console and confirm that workflow is functioning properly.
Rolling back the upgrade
If you encounter an issue while upgrading, you must rollback the system to the original state. If you
have created a snapshot of the virtual machine for the workflow server, revert to the snapshot. Later,
restore the database to the state before upgrading.
Alternatively, roll back the system using the following instructions:
1.
Uninstall Workflow Manager 8.1 on the server.
2.
Delete CentralConfig.Xml available here if the file exists: C:\Program
Files\XtenderSolutions\Content Management\ApplicationXtender Workflow
Manager.
3.
Delete the C:\Program Files\XtenderSolutions\Content Management
\ApplicationXtender Workflow Manager\Web\EnterpriseConsole folder.
4.
Delete the C:\Windows\Temp\SkeltaBPMTemp folder.
5.
Install ApplicationXtender Workflow Manager 7.0 SP1 on the server.
6.
Restore the databases to the original state before upgrading.
7.
Start the Farm Configuration wizard.
8.
Click Workflow Farm Recovery.
9.
Recover the server from the database.
27
Upgrade Your Product
Upgrading ApplicationXtender Integration
Framework components
Before upgrading the ApplicationXtender Integration Framework components, stop the following
Windows services:
• AppXtender Schedule Service
• AppXtender WIM
Perform the following for upgrading the integration framework components from 6.5 SP2 or 7.0
SP1 to 8.1:
1.
Navigate to the setup package and run the setup.exe file.
2.
Install the prerequisite software if prompted. If the wizard displays a message indicating that a
reboot is necessary, click Yes to reboot your computer. After you reboot, click Install again to
resume the setup. The installation wizard displays the Welcome screen after all the required
components have been located or installed.
3.
Click Next.
4.
In the EDB Upgrade page, if you upgrade from version 6.52 SP2, go to Step 5; if you upgrade
from 7.0 SP1, go to Step 6.
5.
In EDB Website, enter the SQL Server username and password that you specified during the SQL
Server setup. The EDB uses these credentials to communicate with the Event Profile Database.
Replace the default user sa if necessary.
6.
In Workflow Integration Module, enter the user account credentials for the WIM service. The
WIM uses the account to communicate with the EDB.
Note: The user account must be associated with the Log on as a service policy in the WIM
computer security settings. Refer to the operating system help for information about how
to assign user rights.
7.
Click Next.
8.
In the Ready to Install the Program page, click Install.
9.
Click Finish.
28
Chapter 5
Migrate Your Product
Migrating ApplicationXtender Workflow
Manager 8.1 Server
Run Workflow Manager 8.1 on the newer version of Windows Server after upgrading. This section
provides instructions to migrate Workflow Manager 8.1 server from an old server to the new server.
Backing up the database before migrating Workflow
Manager Server
It is mandatory to back up databases before migration, so you can roll back the system if you
encounter any problem during migration. You can follow any database vendor supplied approach to
take a backup of your workflow related databases including the farm and repository databases.
The following is a simple approach to back up SQL Server databases:
1.
Stop the SQL Service.
2.
Copy the Workflow Manager Database and log files to a new location.
3.
Start SQL Service.
Installing ApplicationXtender Workflow Manager 8.1
on new Server
Follow the instructions provided in Installing ApplicationXtender Workflow Manager, page 11 to
install the Application Workflow Manager 8.1 on the new server. After the installation, the Workflow
Manager Farm Configuration wizard appears. Cancel it.
Migrating Workflow Server to new server
1.
Deactivate licenses on the old server.
2.
Stop the following Wonderware Skelta services on the old server before migration:
• Wonderware Skelta BPM - Advance Server (AdvServr.NET2.exe)
• Wonderware Skelta BPM - Client Service (SKClientSrv.exe)
• Wonderware Skelta BPM - Communication Service (NotfnEng.NET2.exe)
29
Migrate Your Product
• Wonderware Skelta BPM - Task Scheduler (TaskSked.NET2.exe)
• Wonderware Skelta BPM - Workflow Engine (WFEngine.NET2.exe)
• Wonderware Skelta BPM - Mobile Notification Service
(ArchestrAMobileNotificationService.exe)
It might take a few moments to stop the services. Make sure the processes are stopped in
Windows Task Manager after stopping the services.
3.
Launch Workflow Configuration Manager on the new server.
4.
Click Workflow Farm Recovery.
5.
In the Recovery type wizard page, click Next.
6.
In the Provide Product Key page, specify the Wonderware Skelta BPM 2014-Advanced Server
license key, and click Next.
7.
In the Database User Setting page, select Use SQL/Oracle user for authentication.
8.
Click OK.
9.
In the Database setting page, specify the database settings to Workflow database and click
Test Connection.
10. Select the older server name from the Replace Server drop-down list.
11. Click Next. It might take a few moments to recover. After successful recovery, a confirmation
message appears.
12. Click OK.
13. In the License activation window, click Activate Now to activate the license.
Verifying ApplicationXtender Workflow Manager 8.1
Server migration
1.
Restart the Wonderware Skelta Services.
2.
Restart IIS.
3.
Launch Enterprise Console and confirm that workflow is functioning properly.
Rolling back the migration
You may encounter unexpected issues during migration, and will need to roll back the migration. To
roll back the migration, restore the database to the state before the migration (see Backing up the
database before migrating Workflow Manager Server, page 29), and then you can run the Workflow
Manager 8.1 on the old server.
30
Migrate Your Product
Migrating ApplicationXtender Workflow 8.1
Databases to new Database server
You may want to run Workflow Manager 8.1 on a newer version of the database after upgrading.
This section provides instructions to migrate databases from the old database server to the new
database server.
Backing up database before migrating databases to
the new server
It is mandatory to take a backup of the databases before migration, so you can roll back the system
if you encounter any problem during migration. You can follow any database vendor supplied
approach to take a backup of your workflow related databases including the farm and repository
databases.
The following is a simple approach to back up SQL Server databases:
1.
Stop the SQL Service.
2.
Copy the Workflow Manager Database and log files to a new location.
3.
Start SQL Service.
Before migrating the database
1.
Stop all Wonderware Skelta BPM services on the Workflow Server.
2.
Stop IIS on the new Workflow Server.
Moving databases
You can adopt any approach that the database software allows, to move databases from the old
server to the new server.
The following approach enables you to move databases from SQL Server 2008 R2 to SQL Server
2012 R2:
1.
Stop the SQL Server service.
2.
Copy the WFM SQL databases and Log files to the new SQL server, including the FARM database.
Note: It is recommended to shrink each database before shutting down SQL to down-size log
flies before copying the files.
3.
On the new SQL server, attach each database and log file.
31
Migrate Your Product
4.
Assign the new SQL server user accounts (SYSOP and so on) to the respective databases and
grant appropriate roles.
Redirecting to use new farm database
On the Workflow Manager 8.1 Server, complete the following steps to redirect to use the new farm
database:
1.
Launch the Workflow Configuration wizard.
2.
Click Workflow Farm Recovery.
3.
In the Recovery type wizard page, clear the selection of Product Key, Services, and Central
Configuration and Enterprise Console, click Next.
4.
In the Database User Setting page, select Use SQL/Oracle user for authentication and click OK.
5.
In the Database setting page, specify the database settings to the new Workflow farm database
and click Test Connection.
6.
Click OK if you are prompted with this message: “Test Connection succeeded.”
7.
Click Next. It might take a few moments to recover. After successful recovery, a confirmation
message appears.
8.
Click OK.
Redirecting repository DataSources to use new
database server
1.
Restart IIS.
2.
Launch the CentralConfig site.
3.
Navigate to the Manage Data Source page.
4.
Change the Server Name and credentials for all DataSources to new databases.
5.
Click Test Connection.
6.
Click OK to apply the DataSource setting.
Verifying database migration
1.
Restart the Wonderware Skelta Services.
2.
Restart IIS.
3.
Launch Enterprise Console and confirm that workflow is functioning properly.
32
Migrate Your Product
Rolling back the database migration
You may encounter unexpected issues while migrating databases.
Perform the following to roll back the database migration:
1.
Repeat the instructions provided in Redirecting to use new farm database, page 32, and point
the database to the original farm database.
2.
Repeat the instructions provided in Redirecting repository DataSources to use new database
server, page 32, and point the databases to the original repository databases.
33
Download PDF
Similar pages