upgrade instruction document - wonderware skelta · pdf fileif any of the skelta farm database...

Upgrade Instruction Document Skelta BPM.NET 2009

Version: 3.5.9124.0 (SP2)

Date: 27th July 2011

Upgrade Instruction Document Ver-1.0

© Skelta Software, 2009-2011 2

Table of Contents

OVERVIEW ........................................................................................................ 3

Introduction ................................................................................................... 3

UPGRADE PROCEDURE ......................................................................................... 3

Scenario: When only Skelta BPM.NET 2009 is installed on the machine ........................ 3 Scenario: When both Skelta BPM.NET 2009 and Skelta SharePoint Client 2009 are installed on the machine ................................................................................... 6

SKELTA UPGRADE WIZARD .................................................................................... 8

Skelta Upgrade Wizard on Sever Installation .......................................................... 9 If Farm and Data Source databases are on SQL server .............................................. 9 If any of the Farm or Data Source databases are on Oracle ..................................... 10 After running the Oracle scripts manually .......................................................... 12

Skelta Upgrade Wizard on Client Installation ....................................................... 14



Overview

Introduction

This document has instructions to upgrade Skelta BPM.NET 2009 version 3.5.9102.15 (March Update) to Skelta BPM.NET 2009 version 3.5.9124.0 (SP2) Prerequisites

1. Skelta BPM.NET 2009 of version 3.5.9124.0 (SP2) has to be applied only on versions of 3.5.9102.15 (March Update)

Following are the two upgrade scenarios you will find in this document:

1. When only Skelta BPM.NET 2009 is installed on a machine. 2. When both Skelta BPM.NET 2009 and Skelta SharePoint Client 2009 are installed on a

machine.

Note: To upgrade versions released prior to Skelta BPM.NET 2009 version 3.5.9102.15 (March Update) to Skelta BPM.NET 2009 version 3.5.9124.0 (SP2), first upgrade the older version to BPM.NET 2009 version 3.5.9102.15 (March Update) and then apply Skelta BPM.NET 2009 version 3.5.9124.0 (SP2).

Upgrade procedure

Scenario: When only Skelta BPM.NET 2009 is installed on the machine

1. Download the upgrade files. The compressed file is BPM-Upgrade-SP2.zip (BPM-2009)

2. Extract the zip file to a folder. The zip file contains:

a> One MSI file b> One BAT files. One is a Skelta BPM.NET 2009.bat file.

Notes:

It is important to place the MSI and the BAT files in the same folder.

If the product is installed on Windows Server 2008 OS, then you need to edit the BAT file. The full path of the MSI file has to be mentioned within double quotes. For example, “C:\Upgrade\Skelta BPM.NET 2009.msi”.

The first BAT file is for Forcible upgrade. In this upgrade, even if any files are modified by the user, they will be overwritten by the new files. Take a backup of Actions.xml file if this file has been modified.



The second BAT file is a plain upgrade file. If you upgrade files with this file, the modified file will not be overwritten with the new files.

3. Take a backup of all the Skelta files that were changed or modified for customization.

This is because after applying the upgrade through the forcible upgrade function, all Skelta files will be overwritten by new files and all customizations will be lost.

Note: The old Actions.xml gets renamed and the new Actions.xml gets created under WorkflowElements\Default\en-US\Actions\XML folder after the upgrade. For example, the old Actions.xml gets renamed to Actions.bak3312008_13338PM and then a new Actions.xml file is created. Update the changes in the new Actions.xml from old renamed Actions.xml. This happens, if you have upgraded normally. If you are upgrading forcibly then you need to take a backup of Actions.xml.

4. Take a backup of all Skelta databases, Farm and DataSource databases. 5. Manually stop all the SKELTA services.

Figure: Stop all the Skelta BPM.NET Services 6. Do an IISRESET and delete all temporary files and cache from the machine. To perform

IISRESET.

a. Go to Run and type iisreset. b. Press OK button.

Note: In case of Vista or Windows Server 2008, the user needs to have administrative privileges to perform IISRESET.



To delete temporary files:

a> Go to C:\Windows\temp folder. Delete the Skelta2009Temp folder under the temp folder.

b> Go to C:\Windows\Microsoft.NET\Framework\v2.0.50727\Temporary

ASP.NET Files folder. Delete all the folders under the Temporary ASP.NET Files folder.

7. Execute the BPM BAT file. The Command prompt window will appear along with the Installation Wizard screen.

8. Follow the instructions in the Installation Wizard to upgrade the current installation.

Note:

Do not execute the MSI file. Executing the MSI file directly installs a fresh instance of Skelta BPM.NET 2009. Executing the BPM BAT file will upgrade your current installation.

Before executing the BAT file, take a back up of the modified files in the existing BPMUITemplates in the Application directory folder.

9. After successfully completing the above installation, run the

SkeltaUpgradeManager.exe from the Skelta Installed BIN folder. Follow the procedure explained under the heading Skelta Upgrade Wizard to run the SkeltaUpgradeManager.exe.

10. Start all the Skelta services.

Figure: Start all the Skelta BPM.NET Services



Scenario: When both Skelta BPM.NET 2009 and Skelta SharePoint Client 2009 are installed on the machine

1. Download the upgrade files:

The compressed file is BPM-Upgrade-SP2.zip (BPM-2009) and SPC-Upgrade-SP2.zip (SPClient-2009).

2. Extract the BPM-Upgrade-SP2.zip file to a folder. The zip file contains:

a. One MSI file b. One BAT files. One is a Skelta BPM.NET 2009.bat file.

3. Extract the SPC-Upgrade-SP2.zip file to a folder. The zip file contains:

a. One MSI file b. One BAT files. One is a Skelta SharePoint 2009 Client.bat file.

Notes: i. It is important to place the MSI file and the BAT file in the same folder.

ii. If the product is installed on Windows Server 2008 OS, then you need to edit

the BAT file. That is, the MSI full path of the file needs to be mentioned within the double quotes.

For example, “C:\Upgrade\Skelta BPM.NET 2009.msi”

iii. The first BAT file is for Forcible upgrade. In this upgradation, even if any

files are modified by the user they will be overwritten by the new files. Take a backup of the Actions.xml, if this file has been modified. That is done forcibly.

iv. The second BAT file is a plain upgrade file. If you upgrade files using this file,

the modified file will not be overwritten with the new files. 4. Take a back up of all the Skelta files that were changed or modified for customization.

This is because through forcible upgrade, all Skelta files will be overwritten by new files and all customizations will be lost.

Note:

The old Actions.xml gets renamed and the new Actions.xml gets created under WorkflowElements\Default\en-US\Actions\XML folder after the upgradation.

For example, the old Actions.xml gets renamed to Actions.bak3312008_13338PM and a new Actions.xml file is created. This happens, if you have upgraded normally and not forcibly. If you are upgrading forcibly, then you need to take the backup of Actions.xml.

The old SharePointActions.xml gets renamed and the new SharePointActions.xml gets created under WorkflowElements\Default\en-US\Actions\XML folder after the upgradation.



For example, the old SharePointActions.xml gets renamed as SharePointActions.bak4302008_1545404 and a new SharePointActions.xml file is created. This happens, if you have upgraded normally and not forcibly. If you are upgrading forcibly, then you need to take the backup of SharePointActions.xml.

5. Manually stop all the SKELTA services.

6. Do an IISRESET and delete all temporary files and cache from the machine.

To perform IISRESET:

a. Go to Run and type IISRESET. b. Press OK button.

In case of Vista or Windows Server 2008 the user needs to have administrative privileges to perform IISRESET.

To delete temporary files:

a> Go to C:\Windows\temp folder. Delete the Skelta2009Temp folder under the temp folder.

b> Go to C:\Windows\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files folder. Delete all the folders under the Temporary ASP.NET Files folder.

7. Execute the BPM BAT file. The Command prompt window appears along with the

Installation Wizard screen. Follow the instructions in the Installation Wizard to upgrade the current installation.



Note:

Do not execute the MSI file. Executing the MSI file directly installs a fresh instance of Skelta BPM.NET 2009. Executing the BPM BAT file upgrades your current installation.

Before executing the BAT file, take a back up of the modified files in the existing BPMUITemplates in the application directory folder.

8. Execute the SPC BAT file. The command prompt window appears along with the

Installation Wizard screen. Follow the instructions in the Installation Wizard. Note:

Do not execute the MSI file. Executing the MSI file directly will install a fresh instance of Skelta SharePoint 2009 Client. Executing the SPC BAT file upgrades your current installation.

Before executing the BAT file, take a back up for the modified files in the existing BPMUISharePointTemplates in the Skelta installed path folder.

9. After successfully completing the above installation, run the SkeltaUpgradeManager.exe from the Skelta Installed BIN folder. Follow the procedure explained under the heading Skelta Upgrade Wizard to run the SkeltaUpgradeManager.exe.

10. Start all the Skelta services.

Figure: Start all Skelta BPM.NET Services

Skelta Upgrade Wizard

This section briefly explains how the Skelta Upgrade Wizard works. Skelta Upgrade Wizard upgrades the following components of SKELTA.



Upgrades all the Farm and Data Source databases

Upgrades all the list definitions

Upgrades all repositories and their properties

Skelta Upgrade Wizard on Sever Installation

This section explains the steps to run Skelta Upgrade Wizard on machines where Skelta BPM.NET is installed as a Server.

If Farm and Data Source databases are on SQL server.

If any of the Farm or Data Source databases are on ORACLE.

If Farm and Data Source databases are on SQL server

1. Go to Skelta BPM.NET 2009 installed BIN folder and then double click SkeltaUpgradeManager.exe.

2. The SkeltaUpgradeManager.exe opens up the Skelta Upgrade Wizard.

3. Click the Next button in the Skelta Upgrade Wizard welcome screen.

4. Wait for a few minutes at the Skelta Upgrade Progress screen. After a few minutes, the Update button is enabled if there are no errors in the Skelta upgrade process. Once the Update button is enabled, click Update and Close.



If any of the Farm or Data Source databases are on Oracle Before running the UpgradeManager.exe from the SKELTA Installed BIN folder, run the Oracle Update Scripts manually. To run the Oracle scripts manually, follow the below steps.



If any of the Skelta Farm database or data source database is in Oracle, then the Oracle upgrade scripts have to be run first and then the Skelta Upgrade wizard has to be run. The Oracle upgrade scripts are placed in the <SkeltaInstalledFolder>\DatabaseScripts\Oracle\UpgradeScripts folder. All the script names are suffixed with the version number and prefixed with the type.

If Farm is in ORACLE, then run the UpdateFarm_912400.sql script.

If Data Source is in ORACLE, then run the UpdateDataSource_912400.sql.

Running oracle update scripts In Oracle 10g

1. Open the SQL Plus Worksheet.

2. Connect to ORACLE by providing username, Skelta Farm or Data Source. 3. If the connected ORACLE user is of Farm type then copy the contents of UpdateFarm_912400.sql. Note: While running the “UpdateFarm_912400.sql” there is no need to give DB Owner. 4. If the connected ORACLE user is of Data Source type, then copy the contents of “UpdateDataSource_912400.sql”. 5. Change the db_Owner value in the sixth line of the script to the current ORACLE database username and then run the script for “UpdateFarm_912400.sql”. Note: While running the “UpdateFarm_912400.sql” there is no need to DB Owner.

6. Close the SQL Plus WorkSheet. 7. Perform the above 4 steps for all Farm and Data Source databases in Oracle.

Running oracle update scripts In Oracle 11g

1. Open the SQL Plus command prompt. 2. Connect to ORACLE by providing the username, Skelta Farm or Data Source.

If the connected ORACLE user is of Farm type then copy the contents of UpdateFarm_912400.sql and save it with new file name.

3. If the connected ORACLE user is of data source type then copy the contents of UpdateDataSource_912400.sql and save it with new file name.



4. Open the newly saved file and change the db_Owner value in the sixth line of the script to the currently connected ORACLE database User name and save the file.

5. Type the following statement at the SQL Plus command prompt and execute. Start “FilePath” where FilePath is the complete path of the newly saved file. 6. Close the SQL PLUS command prompt. 7. Perform the above 5 steps for all Farm and Data Source databases in Oracle.

After running the Oracle scripts manually After running the oracle scripts manually follow the steps given below to run the Skelta Upgrade Wizard.

1. Go to Skelta BPM.NET 2009 installed BIN folder and then double click

SkeltaUpgradeManager.exe. 2. The SkeltaUpgradeManager.exe opens up the Skelta Upgrade Wizard.

3. Click the Next button in the Skelta Upgrade Wizard welcome screen.



4. Wait for few minutes on the Skelta Upgrade Progress screen. After few minutes the Update button is enabled if there are no errors in the Skelta upgrade process. If any of the Farm or Data Source databases are in ORACLE, then the information is displayed on the Skelta Upgrade Progress screen indicating the Farm or Data Sources names that are in ORACLE.

5. If you have already run the oracle scripts manually then click the Update button to

start the wizard.



Skelta Upgrade Wizard on Client Installation

There is no need to run the Skelta Upgrade Wizard on machines where Skelta BPM.NET is installed as a Client installation. Note: If a client has Central Config or Enterprise Console Site configured, then it is required to run the SkeltaUpgardeWizard.exe.

upgrade instruction document - wonderware skelta · pdf fileif any of the skelta farm database...

Documents