Documente Academic
Documente Profesional
Documente Cultură
800xA - System
System Version 4.1
In no event shall ABB be liable for direct, indirect, special, incidental or consequential
damages of any nature or kind arising from the use of this document, nor shall ABB be
liable for incidental or consequential damages arising from use of any software or hard-
ware described in this document.
This document and parts thereof must not be reproduced or copied without written per-
mission from ABB, and the contents thereof must not be imparted to a third party nor used
for any unauthorized purpose.
The software or hardware described in this document is furnished under a license and
may be used, copied, or disclosed only in accordance with the terms of such license.
This product meets the requirements specified in EMC Directive 89/336/EEC and in Low
Voltage Directive 72/23/EEC.
TRADEMARKS
All rights to trademarks reside with their respective owners.
TABLE OF CONTENTS
Section 1 - Introduction
Overview..........................................................................................................................17
System Checker ...............................................................................................................17
System Language Package ..............................................................................................18
Precautions ......................................................................................................................18
Planning ...........................................................................................................................19
Minimum Hardware Requirements .................................................................................20
Firmware Memory Consumption ....................................................................................20
Supported Operating Systems .........................................................................................20
3BSE036342R4101 5
Table of Contents
6 3BSE036342R4101
Table of Contents
3BSE036342R4101 7
Table of Contents
8 3BSE036342R4101
Table of Contents
3BSE036342R4101 9
Table of Contents
INDEX
10 3BSE036342R4101
About This Book
General
This instruction covers the following:
Upgrading SV 4.0 to SV 4.1.
Upgrading SV 3.1/2 to SV 4.1.
Upgrading SB 2.1/2 to SV 4.1.
Third Party Software for SV 4.1.
Warning and Error Messages.
Upgrading directly from SV 3.1 or SV 3.1/1 to SV 4.1 is not supported. If
running one of these versions, it is necessary to upgrade to SV 3.1/2 before
upgrading to SV 4.1.
Intended User
This instruction is intended for installation engineers with experience with process
control systems, the ABB Industrial IT 800xA System, and Microsoft
Windows operating systems. Standard 800xA System and Microsoft Windows
functions are not described in this instruction.
3BSE036342R4101 11
Document Conventions About This Book
Current system = System Version 3.1 with Service Pack 2 (SV 3.1/2): Refer
to Section 3, Upgrading SV 3.1/2 to SV 4.1.
Current system = System Baseline 2.1/2 (SB2.1/2): Refer to Section 4,
Upgrading SB 2.1/2 to SV 4.1
Read the applicable section through in sequence before attempting to upgrade the
system. While reading, note which parts of the upgrade procedures pertain to the
specific system configuration in the organization. During the actual upgrade
procedure, perform only those procedures that apply to the specific system
configuration.
This instruction contains upgrade preparation and post upgrade procedures.
Upgrading most individual application software requires referring to Industrial IT,
800xA - System, Installation to install the application software. Unless otherwise
noted, the procedures for installing the application software for a new installation
and installing the application software as part of an upgrade are identical. If
required, differences in the two installation procedures will be clearly identified.
Refer to Industrial IT, 800xA - System, Release Notes before starting an upgrade
or installation.
Document Conventions
The following conventions are used for the presentation of material:
The words in names of screen elements (for example, the title in the title bar of
a window, the label for a field of a dialog box) are initially capitalized.
Capital letters are used for the name of a keyboard key if it is labeled on the
keyboard. For example, press the ENTER key.
Lowercase letters are used for the name of a keyboard key that is not labeled on
the keyboard. For example, the space bar, comma key, and so on.
Press CTRL+C indicates that you must hold down the CTRL key while
pressing the C key (to copy a selected object in this case).
Press ESC E C indicates that you press and release each key in sequence (to
copy a selected object in this case).
The names of push and toggle buttons are boldfaced. For example, click OK.
12 3BSE036342R4101
About This Book Use of Warning, Caution, Information, and Tip Icons
The names of menus and menu items are boldfaced. For example, the File
menu.
The following convention is used for menu operations: MenuName >
MenuItem > CascadedMenuItem. For example: select File > New > Type.
The Start menu name always refers to the Start menu on the Windows
Task Bar.
System prompts/messages are shown in the Courier font, and user
responses/input are in the boldfaced Courier font. For example, if you enter a
value out of range, the following message is displayed:
Entered value is not valid. The value must be 0 to 30.
You may be told to enter the string TIC132 in a field. The string is shown as
follows in the procedure:
TIC132
Variables are shown using lowercase letters.
sequence name
Warning icon indicates the presence of a hazard which could result in personal
injury.
Caution icon indicates important information or warning related to the concept
discussed in the text. It might indicate the presence of a hazard which could
result in corruption of software or damage to equipment/property.
Information icon alerts the reader to pertinent facts and conditions.
3BSE036342R4101 13
Applicable Specifications About This Book
Tip icon indicates advice on, for example, how to design your project or how to
use a certain function
Although Warning hazards are related to personal injury, and Caution hazards are
associated with equipment or property damage, it should be understood that
operation of damaged equipment could, under certain operational conditions, result
in degraded process performance leading to personal injury or death. Therefore,
comply fully with all Warning and Caution notices.
Applicable Specifications
This product meets the requirements specified in EMC Directive 89/336/EEC and in
Low Voltage Directive 72/23/EEC.
Related Documentation
Table 1 lists and describes the ABB documentation related to and/or referred to in
this instruction.
14 3BSE036342R4101
About This Book Related Documentation
3BSE036342R4101 15
Related Documentation About This Book
16 3BSE036342R4101
Section 1 Introduction
Overview
This instruction describes how to upgrade to ABB IndustrialIT 800xA System
Version 4.1 (SV 4.1). It covers the following scenarios:
Upgrading SV 4.0 to SV 4.1.
Upgrading SV 3.1/2 to SV 4.1.
Upgrading SB 2.1/2 to SV 4.1.
The topics in this section briefly describe the prerequisite requirements, procedures,
and other considerations depending on the current software version. Review this
information before installing SV 4.1.
Upgrading directly from SV 3.1 or SV 3.1/1 to SV 4.1 is not supported. If
running one of these versions, it is necessary to upgrade to SV 3.1/2 before
upgrading to SV 4.1.
System Checker
The System Checker is designed for the purpose of checking, verifying,
documenting, and troubleshooting an 800xA System. It includes the following:
Node Report tool.
System Checker tool.
System Information Collector tool.
System Report tool.
The System Checker supports 800xA System Versions 3.x and 4.x. It also supports
System Baseline 2.x with some limitations. Those limitations, as well as the
installation and use of the System Checker is described in Industrial IT, 800xA -
System, System Checker.
3BSE036342R4101 17
System Language Package Section 1 Introduction
Precautions
There are third party backup/restore and hard drive cloning/imaging utilities that are
useful when software or data becomes corrupted to the point that the node will no
longer function correctly. A limited number of hardware failures can also be
compensated for by using these utilities. However, it is important to understand the
limitations and ramifications associated with these utilities. In some cases (such as
corrupted data, corrupted software, or hard disk failures) these utilities can be useful
while in other cases (such as replacing a node) these utilities may be of limited use.
It is recommended that cloning/imaging software be used to save (and restore if
necessary) an image of node hard drives after installation of third party software
and/or after installing all software.
The 800xA System import/export utility can be used to save 800xA System
information one portion at a time. However, the 800xA System backup utility is the
functional equivalent of exporting all 800xA System information at one time. The
critical difference between these utilities is that individually exported portions of
800xA System information can be imported back into the original system or into a
completely different system while backed up 800xA System information can only
be used to restore a specific system on specific nodes.
18 3BSE036342R4101
Section 1 Introduction Planning
Planning
1. For optimal hardware and software prerequisites, refer to Industrial IT, 800xA -
System, Installation. The prerequisites depend on the functions installed in the
system, or on each node type.
2. For an upgrade, performance will be determined by the actual hardware of the
system. System performance after the upgrade is completed will be determined
by the hardware being upgraded. Memory size and processor speed have a
direct impact on system performance. Refer to Minimum Hardware
Requirements on page 20 to determine the performance after upgrading an
existing system.
3. If upgrading from SB 2.1/2 or SV 3.1/2 to SV 4.1, order new SV 4.1 licenses.
New licenses are not required if upgrading from SV 4.0 to SV 4.1. Contact
your ABB sales representative to perform the license upgrade.
4. Consider other issues that are important prior to starting the upgrade, such as:
Concurrent access to the current 800xA System version and the SV 4.1 system
is recommended until the upgrade has been performed. This makes it possible
to easily retrieve any data or files that have been missed. Concurrent access
depends upon many different factors, including:
Configuration of the existing system.
Desired configuration of the SV4.1 system.
PC use strategy.
Configuration of user and user groups.
Use of service accounts.
Domain controllers.
Redundancy.
Logical and physical networks.
One strategy is to leave a minimal part of the existing system intact, such as an
Aspect Server, while preparing a major part of the SV 4.1 system. Another
strategy is to prepare a minimal SV4.1 system.
Retaining an Aspect Server from the existing system minimizes the time it
takes to retrieve data or files from it. A disk drive image provides a quick way
to recover, but often it requires no hardware upgrade. Try to delay the upgrade
of the hardware in one Aspect Server as long as possible.
3BSE036342R4101 19
Minimum Hardware Requirements Section 1 Introduction
20 3BSE036342R4101
Section 1 Introduction Supported Operating Systems
All nodes being upgraded from SB 2.1/2 to SV 4.1 must be reformatted and the
operating system installed, even if the existing operating system is compatible.
All IM (Information Management) Server nodes being upgraded from SB2.1/2
to SV 4.1 or SV 3.1/2 to SV 4.1 must be reformatted and the operating system
installed, even if the existing operating system is compatible.
All nodes being upgraded from SV 3.1/2 to SV 4.1, that are not IM Server
nodes, with a compatible operating system require an update to the existing
operating system.
3BSE036342R4101 21
Supported Operating Systems Section 1 Introduction
22 3BSE036342R4101
Section 2 Upgrading SV 4.0 to SV 4.1
Introduction
Not all products that require upgrading from SV 4.0 to SV 4.1 are mentioned in
this instruction. Those products not mentioned require no preparation or post
upgrade procedures, nor do they require that the previous version be uninstalled.
Refer to Industrial IT, 800xA - System, Installation to silently install the upgrades
for those products.
Upgrading the 800xA System requires the plant to be shut down. To guarantee
the functionality of the upgraded system, follow these upgrade instructions
carefully and perform them in a well defined order.
It is recommended that an image copy of all disks on each node be made after
software installation and setup are completed. It is also recommended to back up
the aspect directory, reports, history data, graphics, and other application data
before installing this upgrade.
Upgrade Procedure
This section is organized so that the instructions are presented in the proper upgrade
order. Do not skip any steps.
The person performing this procedure must be familiar with the Configuration
Wizard. Detailed Configuration Wizard procedures are not included.
1. All Applicable Nodes: Refer to System Preparation on page 26 and perform
system preparation procedures on all applicable nodes. Return to this procedure
when complete.
2. All Nodes: Shut down all 800xA client applications and tools, (e.g.
Workplaces).
3BSE036342R4101 23
Upgrade Procedure Section 2 Upgrading SV 4.0 to SV 4.1
a. Stop the server. Use the Stop Server feature in the Configuration Wizard.
b. Stop Windows Services. Refer to Stopping Windows Services on page 40.
Return to this procedure when complete.
4. All Remaining Nodes: Stop Windows Services. Refer to Stopping Windows
Services on page 40. Return to this procedure when complete.
5. All Applicable Nodes: Use the Add or Remove Programs feature in
Windows Control Panel to uninstall the following 800xA System software:
Uninstall only the listed 800xA System software. Software not listed does not
need to be uninstalled before performing the upgrade.
Some of the uninstall programs will indicate that a reboot is necessary after
unistalling the software. If desired, wait until all uninstallations are complete
before rebooting.
ABB Central Licensing System.
ABB Central Licensing System Extension 4.0.0/0 (licensing server only).
ABB MOD 300 Connect (800xA for MOD 300).
ABB PAS - System Services (800xA for MOD 300).
ABB 800xA for TRIO.
ABB 800xA for Harmony.
ABB Diagnostics Collection Tool 4.0.0/0.
ABB Batch Management Environment.
ABB Batch Management Client.
ABB PC, Network and Software Monitoring 4.0.0/0.
ABB Fieldbus Builder PROFIBUS/HART with OPC Server 4.0.0/0.
ABB FDT Shared Components 4.0.0/0.
ABB FDT Base Container 4.0.0/0.
ABB PROFIBUS Device Integration Library 4.0.0/0.
ABB HART Device Integration Library 4.0.0/0.
ABB Basic PROFIBUS DTM / PROFIBUS DTM Builder 4.0.0/0.
ABB Basic HART DTM / HART DTM Builder 4.0.0/0.
24 3BSE036342R4101
Section 2 Upgrading SV 4.0 to SV 4.1 Upgrade Procedure
3BSE036342R4101 25
System Preparation Section 2 Upgrading SV 4.0 to SV 4.1
Refer to Industrial IT, 800xA - System, Post Installation for 800xA for TRIO
installation procedures.
Do not initialize the Batch Management database when prompted during
installation of Batch Management software.
9. All Applicable Nodes: Restart the node after installing all 800xA System
software.
10. Primary Aspect Server Node: Start the server. Use the Start Server feature in
the Configuration Wizard.
11. Primary Aspect Server Node: Refer to System Extension Maintenance on
page 50 and update the required system extensions. Return to this procedure
when complete.
External Alarm Service Group: Before updating the required system
extensions, keep only one External Alarm Service Group and move the provider
or providers to the Aspect Servers. Do this before loading the system extensions,
or the PPA system extension will not be loaded.
12. All Other Server Nodes: One server node at a time, start the server in the
following order. Use the Start Server feature in the Configuration Wizard.
a. Aspect Servers (other than the primary Aspect Server node).
b. Connectivity Servers.
c. Application Servers.
13. All Applicable Nodes: Refer to Post Upgrade Procedures on page 52 and
perform all applicable post upgrade procedures.
System Preparation
The person performing this upgrade must use the same user account that was used
during the installation of the 800xA System software, unless otherwise indicated in
these instructions.
Some 800xA System software requires preparatory steps before shutting down
800xA System processes. If the 800xA System includes any of the following
applications, refer to the referenced section to perform these steps:
Control IT for AC 800M Preparation on page 27.
26 3BSE036342R4101
Section 2 Upgrading SV 4.0 to SV 4.1 Control IT for AC 800M Preparation
3BSE036342R4101 27
PROFIBUS and HART Device Integration Preparation Section 2 Upgrading SV 4.0 to SV 4.1
28 3BSE036342R4101
Section 2 Upgrading SV 4.0 to SV 4.1 800xA for Harmony Preparation
3BSE036342R4101 29
Engineering Studio Preparation Section 2 Upgrading SV 4.0 to SV 4.1
4. If the Event Server Pre Treatment function is being used in the application
(refer to Industrial IT, 800xA System - PLC Connect, Configuration for more
information), make a backup of PreEvent.dll. PreEvent.dll is located in the
following folder on the PLC Connect Connectivity Server:
...\ABB Industrial IT\Operate IT\PLC Connect\Bin
The path is the default location of the file. If it has been placed somewhere else,
make a backup from that location.
5. Make a backup of the VB application projects for PreEvent.dll.
30 3BSE036342R4101
Section 2 Upgrading SV 4.0 to SV 4.1 Asset Optimization Preparation
3BSE036342R4101 31
Asset Optimization Preparation Section 2 Upgrading SV 4.0 to SV 4.1
b. The MxDef files provide the mapping between the 800xA System
environment and the Maximo system.
Do not edit the MxDef files without an extensive knowledge of the Maximo SDK
for Business Components documentation. Do not edit the MxDef files without a
close consulting association with MRO Software Inc. personnel to determine
what fields are required. Editing these files without the required knowledge and
experience may result in problems with the Maximo system and CMMS
interface to the Maximo system.
Perform the following procedure if changes are made to the MxDef files, in order
to prevent the customized MxDef files from being overwritten during an upgrade
or reinstallation of Asset Optimization. The software will first look in the
subdirectories created in the procedure for the MxDef files before looking in the
default MxDef file location.
c. Assuming the default directory was selected during Asset Optimization
installation, the MxDef files supplied with Asset Optimization are located
in:
...\Program Files\ABB Industrial IT\Optimize IT\
Asset Optimization\ABBAO\Services\MOM\MxDefs
d. If changes are made to the MxDef files, create and save them in the
following location (assuming the default directory was selected during
Asset Optimization installation):
...\Program Files\ABB Industrial IT\Optimize IT\
Asset Optimization\ABBAO\Services\MOM\MxDefs\
<server_name>\<app_server>
Where:
<server_name>\<app_server> is the combination of the MRO
Server Name and the MRO Application Server Name fields from the
Maximo Equipment ID aspect. These fields are configured in the Aspect
System Structure in the Maximo Equipment ID aspect. The resultant path
to the customized MxDef files will look like, for example:
...\Program Files\ABB Industrial IT\Optimize IT\Asset
Optimization\ABBAO\Services\MOM\MxDefs\Maximo5\MxServer
32 3BSE036342R4101
Section 2 Upgrading SV 4.0 to SV 4.1 Asset Optimization Preparation
This allows for customization of MxDef files on the Maximo Server level
as well as on the Maximo Application Server level. Refer to Maximo
documentation for an explanation of Maximo Application Servers.
3. SAP/PM Integration:
The SAP/PM Integration information can be found on Asset Optimization Server
nodes. Reference the Service Structure for the Asset Optimization Server.
a. Although the SAP/PM system is separate from the 800xA system, it is a
good idea to back up the system in use. Follow SAP/PM standard
practices for the third party SAP/PM system backup.
b. The SAPDef files provide the mapping between the 800xA System
environment and the SAP/PM system.
Do not edit the SAPDef files without a close consulting association with SAP,
AG personnel to determine what fields are required. Editing these files without
the required knowledge and experience may result in problems with the SAP/PM
system and CMMS interface to the SAP/PM system.
c. Assuming the default directory was selected during Asset Optimization
installation, the SAPDef files supplied with Asset Optimization are
located in:
...\Program Files\ABB Industrial IT\Optimize IT\
Asset Optimization\AoAIPSAPWebSrv\SAPXML
d. Save these files. If changes were made to the default files, save them as
well.
4. DMS Calibration Integration:
Refer to the Meriam Process Technologies Device Management System Users
Guide for information about saving the DMS Server data.
Asset Optimization DMS Calibration Integration SV 4.1 functions with DMS
software Version 2.2.
5. Shut down the Asset Monitoring Servers.
The following actions only apply to the Asset Optimization Application Server
node, and must be performed for every Asset Monitoring Server aspect.
3BSE036342R4101 33
PC, Network and Software Monitoring Preparation Section 2 Upgrading SV 4.0 to SV 4.1
a. Use the Structure Selector to open the Control Structure in the Plant
Explorer Workplace.
b. Use the Object Browser to navigate to an Asset Optimization Server
aspect.
c. Click Navigate to AssetMonitoring Service and deselect the
AssetMonitoring Service check box in the Service Provider Definition
aspect.
d. Either restart the Asset Optimization Application Server node,
-or-
Use standard Windows procedures, via the Component Services selection
from Administrative Tools in Windows Control Panel, to shut down the
following COM+ components (the items in the list depends on the
installed Asset Optimization components):
AbbAoMSSoap.
AbbAoMSSoapAsync.
OPTAOWebService.
SOAPMaximoSrv.
DMSComPlus.
DMSSession.
34 3BSE036342R4101
Section 2 Upgrading SV 4.0 to SV 4.1 PC, Network and Software Monitoring Preparation
TC06067A
3BSE036342R4101 35
Batch Management Preparation Section 2 Upgrading SV 4.0 to SV 4.1
36 3BSE036342R4101
Section 2 Upgrading SV 4.0 to SV 4.1 Manufacturing Management Preparation
3BSE036342R4101 37
Calculations Service Preparation Section 2 Upgrading SV 4.0 to SV 4.1
38 3BSE036342R4101
Section 2 Upgrading SV 4.0 to SV 4.1 Information Management Preparation
3. Select the ABB Process Administration Service, and set it to Manual. This is
required because of reboots.
4. Close the Services utility window.
3BSE036342R4101 39
Stopping Windows Services Section 2 Upgrading SV 4.0 to SV 4.1
40 3BSE036342R4101
Section 2 Upgrading SV 4.0 to SV 4.1 Information Management Upgrade
Oracle 9
3BSE036342R4101 41
Oracle 9 Section 2 Upgrading SV 4.0 to SV 4.1
3. Select Step 2 Install 9.2.0.6.0 button to start the upgrade. This will stop the
ABB Services as indicated in the expanded Advanced View window. After the
services are stopped, the Installing Oracle Patch begins and the Oracle
Universal Installer is started.
4. Select Next from the Oracle Universal Installer:Specify File Locations
window. This starts the installation. When complete, Step 2 will show that
9.2.0.6.0 is installed.
42 3BSE036342R4101
Section 2 Upgrading SV 4.0 to SV 4.1 Oracle 9
5. Select Step 3 Upgrade Database button, Figure 7, to start the upgrade of the
database.
Windows XP
To install the Oracle 9.0.2.6 upgrade on Windows XP:
1. Insert the InfoMgmt2 DVD with Oracle 9.0.2.6.
3BSE036342R4101 43
Oracle 9 Section 2 Upgrading SV 4.0 to SV 4.1
3. Select Step 2 Install 9.2.0.6.0 button to start the upgrade. To stop the ABB
Services, Windows XP must be restarted in safe mode.
44 3BSE036342R4101
Section 2 Upgrading SV 4.0 to SV 4.1 Oracle 9
5. Select Diagnostic Startup - load basic devices and services only and then
select OK.
6. Select Restart to continue. Windows will restart in safe mode with the no ABB
Services present in the expanded Advanced View window. Installing Oracle
Patch begins and the Oracle Universal Installer is started.
3BSE036342R4101 45
Oracle 9 Section 2 Upgrading SV 4.0 to SV 4.1
46 3BSE036342R4101
Section 2 Upgrading SV 4.0 to SV 4.1 Information Management
Information Management
If the Plant Explorer is open on the node where you are installing this upgrade,
close the Plant Explorer window BEFORE you begin the installation.
3. Select the Upgrade All option. This option automatically detects the
Information Management software components installed on this PC.
4. Select the Upgrade button to start the Information Management upgrade and to
proceed to the upgrade pages.
The wizard will perform the entire upgrade without requiring any operator
input. The wizard will first check whether or not the ABB Process
Administration Service, ABB ServiceManager Service and IIS have been
3BSE036342R4101 47
Information Management Section 2 Upgrading SV 4.0 to SV 4.1
stopped, and stop them if necessary. During this phase a Windows command
prompt will open briefly, and then close automatically.
When it has been determined that the services are stopped, the wizard will first
remove the applicable components, Figure 13, and then reinstall them.
48 3BSE036342R4101
Section 2 Upgrading SV 4.0 to SV 4.1 Information Management
5. Click Exit when the Upgrade Complete message is displayed, Figure 14.
3BSE036342R4101 49
System Extension Maintenance Section 2 Upgrading SV 4.0 to SV 4.1
TC08123A
50 3BSE036342R4101
Section 2 Upgrading SV 4.0 to SV 4.1 System Extension Maintenance
3. Select the system extension to update in the list in the left pane and move it to
the list in the right pane by clicking >. To move all the system extensions from
the left pane to the right pane, click >>.
4. The Thumb up/down icon (Figure 16) indicates the status of the dependency
evaluation. If the list in the right pane contains more than one system extension,
click Press header to autosort to sort the system extensions load order with
regard to dependencies.
TC08124A
3BSE036342R4101 51
Post Upgrade Procedures Section 2 Upgrading SV 4.0 to SV 4.1
5. All system extensions listed in the right pane should be marked with the
Thumb up icon. Click Next and the Apply Settings dialog similar to the one
shown in Figure 17 appears.
TC08125A
6. Click Finish. The system extension updates will load into the system.
7. A progress dialog is shown during the load. Click View Log to view log
messages during load.
8. When the load operation has finished, click Finished and view the
Configuration Wizard log to verify that no errors occurred during the load.
9. Close the Configuration Wizard.
52 3BSE036342R4101
Section 2 Upgrading SV 4.0 to SV 4.1 Control IT for AC 800M Post Upgrade
800xA for Advant Master and 800xA for SafeGuard RTA Board Files on page
57.
800xA for Harmony Post Upgrade on page 57.
800xA for MOD 300 Post Upgrade on page 59.
PLC Connect Post Upgrade on page 61.
Engineering Studio Post Upgrade on page 62.
Asset Optimization Post Upgrade on page 63.
PC, Network and Software Monitoring Post Upgrade on page 66.
Batch Management Post Upgrade on page 69.
Manufacturing Management Post Upgrade on page 70.
Information Management Post Upgrade on page 71.
SoftPoint Service Post Upgrade on page 74.
Calculations Service Post Upgrade on page 75.
Scheduling Service (Application Scheduler) Post Upgrade on page 75.
Restart the system after completing all post installation procedures.
3BSE036342R4101 53
FOUNDATION Fieldbus Device Integration Post Upgrade Section 2 Upgrading SV 4.0 to SV 4.1
54 3BSE036342R4101
Section 2 Upgrading SV 4.0 to SV 4.1 FOUNDATION Fieldbus Device Integration Post Upgrade
3BSE036342R4101 55
PROFIBUS and HART Device Integration Post Upgrade Section 2 Upgrading SV 4.0 to SV 4.1
56 3BSE036342R4101
Section 2 Upgrading SV 4.0 to SV 4.1 800xA for Advant Master and 800xA for SafeGuard RTA
800xA for Advant Master and 800xA for SafeGuard RTA Board Files
AC 400 Connect is referred to as 800xA for Advant Master after the upgrade.
SafeGuard Connect is referred to as 800xA for SafeGuard after the upgrade.
Restore the files:
DATHR1.CD
DATHR2.CD
DATHR3.CD
to the folder:
\Program Files\ABB Industrial IT\OperateIT\AC400CI\AdvantBase\
Data\RTA\Init\
to the node where they belong.
3BSE036342R4101 57
800xA for Harmony Post Upgrade Section 2 Upgrading SV 4.0 to SV 4.1
2. Restore the 800xA for Harmony Configuration information that was saved
during 800xA for Harmony Preparation on page 29.
a. Select:
Start > All Programs > ABB Industrial IT 800xA > 800xA for OCS
Systems > Harmony > Configuration > Restore Configuration
b. Click Connect in the Harmony Connect Configuration Backup/Restore
window.
c. Enter the name of the Harmony Configuration Server database backup file
in the Backup File field.
d. Click Restore.
e. If a prompt appears indicating that the system version does not match the
backup version, click OK and the backup file will be saved to a temporary
SQL database. Its components will then be migrated to the Configuration
Server database.
If a prompt does not appear, it means that the versions are the same and
the backup will be restored directly to the Configuration Server database,
overwriting it if it already exists.
f. If the message Services must be stopped, REBOOT system now
then restart this application! is displayed, restart the node and
repeat Step a through Step e.
g. Click Exit when the restore operation is complete.
58 3BSE036342R4101
Section 2 Upgrading SV 4.0 to SV 4.1 800xA for MOD 300 Post Upgrade
Step 3 assumes the aspects being removed are not being used. If they are, they
need to be manually modified.
3. From the [Graphics Structure]\Graphics Tools\OCS Graphics Subelements,
remove OCS Input Field, OPC Quality Indicator and OPC Quality Text
aspects.
4. If you have created graphics that reference this MOD_DValue subelement, do
not remove it. Instead, follow the remaining steps. This does not include the
Measure_DValue, Setpoint_DValue, Output_DValue, Command_DValue or
State_DValue aspects on the CCF object types. Although graphics referencing
these aspects need to be redeployed.
5. Create an aspect of category Reference Configuration on the object containing
references to the MOD_DValue aspect. The reference configuration aspect will
list all object and aspect references in all aspects on the object.
6. Select an aspect that references the old MOD_DValue (OCS Graphic
Subelements:MOD_DValue).
7. Select Reselect and browse to the new MOD_DValue (MOD Graphic
Subelements:MOD_DValue).
8. Repeat Step 6 and Step 7 until all references have been updated.
9. Select Rebind to apply the updates.
10. Delete Reference Configuration aspect.
11. Deploy updated sub elements/graphics and subelements/graphics referring to
any of these changes.
3BSE036342R4101 59
800xA for MOD 300 Post Upgrade Section 2 Upgrading SV 4.0 to SV 4.1
The PAS System Services will not start until you initialize the communications
settings as described in the next steps.
15. Initialize the OMF settings to start system services. Use the Administrative
Tools in the Window Control Panel to select:
PAS > Settings.
This displays the Communications Configuration Tool.
The message:
Would you like to revert back to saved settings?
is displayed if settings were previously saved. To restore the previous settings, do
steps a through d as follows.
a. Select Yes at the message
Would you like to revert back to saved settings?
This opens the Communication Settings display.
b. Select OK on the Communication Settings display to save the settings and
close the window.
c. Select OK to the message:
Settings have been saved . ...
d. Select OK at the informational message that the settings have been
changed. You must always restart if you change the Control Network
Setting, OMF Memory, or TCP/IP enabled setting.
16. Restart Windows. Restart Windows at this time.
60 3BSE036342R4101
Section 2 Upgrading SV 4.0 to SV 4.1 PLC Connect Post Upgrade
Restoring PreTreat2.dll
To restore PreTreat2.dll:
1. If the PLC Connect Communication Server Pre Treatment function is being
used in the application, copy PreTreat2.dll from the backup location to the
same folder as it was backed up from on the PLC Connect Connectivity Server.
If the default folder is used, that location is:
...\ABB Industrial IT\Operate IT\PLC Connect\Bin
2. Register the PreTreat2.dll file (refer to Industrial IT, 800xA System - PLC
Connect, Configuration for more information).
3. Restart the PLC Connect Connectivity Server for the changes to take effect.
4. Restore the VB project for PreTreat2.dll.
3BSE036342R4101 61
Engineering Studio Post Upgrade Section 2 Upgrading SV 4.0 to SV 4.1
Restoring PreEvent.dll
To restore PreEvent.dll:
1. If the PLC Connect Event Server Pre Treatment function is being used in the
application, copy PreEvent.dll from the backup location to the same folder
as it was backed up from on the PLC Connect Connectivity Server. If the
default folder is used, that location is:
...\ABB Industrial IT\Operate IT\PLC Connect\Bin
2. Register the PreEvent.dll file (refer to Industrial IT, 800xA System - PLC
Connect, Configuration for more information).
3. Restart the PLC Connect Connectivity Server for the changes to take effect.
4. Restore the VB application project for PreEvent.dll.
62 3BSE036342R4101
Section 2 Upgrading SV 4.0 to SV 4.1 Asset Optimization Post Upgrade
Function Designer.
Function Designer for AC800M.
Function Designer for AC800M SB2 Libraries.
Function Designer for FB PH.
Topology Designer.
Topology Designer for AC800M.
Reuse Assistant.
Script Manager.
When working with SV 4.1, if the Advanced selection in the Engineering
Workplace context menu appears multiple times:
1. Use the Structure Selector to select the Workplace Structure.
2. Use the Object Browser to navigate to and select Engineering
Workplace.
3. Delete all aspects from the Preview Pane called Engineer IT Global
Menus and Engineering.
Although Control Builder base libraries 1.0/0, 1.0/1, 1.1/0, etc. were released in
SV 3.1, changes were made in the current versions of those libraries. Engineering
Studio Function Designer detects this as an interface change and changes the
diagram state of already existing instances to red. This requires that the
configuration be generated and loaded again to ensure that the loaded diagrams
are the same as the ones stored in the Aspect System.
3BSE036342R4101 63
Asset Optimization Post Upgrade Section 2 Upgrading SV 4.0 to SV 4.1
64 3BSE036342R4101
Section 2 Upgrading SV 4.0 to SV 4.1 Asset Optimization Post Upgrade
This allows for customization of MxDef files on the Maximo Server level
as well as on the Maximo Application Server level. Refer to Maximo
documentation for an explanation of Maximo Application Servers.
3. SAP/PM Integration:
The SAP/PM Integration information MUST be restored on all Asset
Optimization Server nodes. Reference the Service Structure for the Asset
Optimization Server.
a. If using SAP/PM Integration, restore the SAPDef files to the following
directory (assuming the default directory was selected during Asset
Optimization installation):
...\Program Files\ABB Industrial IT\Optimize IT\
Asset Optimization\AoAIPSAPWebSrv\SAPXML
Refer to Industrial IT, 800xA - Asset Optimization, Configuration for more
information on SAPDef files.
4. DMS Calibration Integration:
Restore DMS Calibration Integration information. Refer to the Meriam Process
Technologies Device Management System Users Guide for information about
restoring DMS Server data.
Asset Optimization DMS Calibration Integration SV 4.1 functions with DMS
software Version 2.2.
5. After a restore of a SV 4.1 system, the Asset Optimization Server (Monitor
Server/Engine) may appear to be running. The AO Server tab of the Asset
Monitoring Server aspect will show a status of good: AM Engine Running.
a. Clicking the Asset Monitors tab and selecting AMs assigned to this AM
Engine will show that the values in the Status column are Configured
and NOT Loaded.
b. Click Load all AMs and after the load status is good, select AMs
assigned to this AM Engine again. The Status column should now
indicate Loaded for all Asset Monitors assigned to the Asset Monitoring
Engine for this node.
6. In the Control Structure, open the AOServer1, AOServer object, Asset
Optimization Server aspect.
3BSE036342R4101 65
PC, Network and Software Monitoring Post Upgrade Section 2 Upgrading SV 4.0 to SV 4.1
66 3BSE036342R4101
Section 2 Upgrading SV 4.0 to SV 4.1 PC, Network and Software Monitoring Post Upgrade
Type Change
Asset Monitor in the instance that has Object This Asset Monitor will be set to inherit from
Type. Object Type's Asset Monitor.
Corresponding Asset Monitor exists in the object
type and the
Object Type Definition Aspect > Aspect
Control Tab > Copy to all instances
check box is selected. Then for each of the 4 configuration tabs (Asset
Monitor, Conditions, Asset Parameters, Input
Records) if the configuration matches the
configuration in Object Type, inheritance values
will be set to TRUE, else to FALSE.
Asset Monitor is on the Object Type. This Asset Monitor will be set to inherit from the
Asset Monitor category.
Asset Monitor is on the instance of the generic
object.
Asset Monitor in the instance that has Object
Type.
Corresponding Asset Monitor does not exist in Then for each of the 4 configuration tabs (Asset
the Object Type. Monitor, Conditions, Asset Parameters, and
Asset Monitor in the instance that has Object Input Records) the configuration inheritance
Type. values will be set to their pre 4.1 values.
Corresponding Asset Monitor exists in the object
type the
Object Type Definition Aspect > Aspect
Control Tab > Copy to all instances
check box NOT selected.
2. Perform the following steps on the PC, Network and Software Monitoring
Server node.
The following steps assume that the required system extensions were loaded on
the primary Aspect Server node.
3BSE036342R4101 67
PC, Network and Software Monitoring Post Upgrade Section 2 Upgrading SV 4.0 to SV 4.1
a. Use the Structure Selector to open the Service Structure in the Plant
Explorer Workplace.
b. Use the Object Browser to navigate to the:
Services > OpcDA_Connector, Service > SG_IT Server
object. If there is no object to navigate to, skip to Step l.
c. Open the OPCDA_Provider_<servername> object and double-click on the
Service Provider Definition aspect.
d. On the Configuration tab select the Enabled check box and click Apply.
The Current field should change to Service.
e. Use the Structure Selector to open the Control Structure.
f. Use the Object Browser to navigate to the IT Server object.
g. Double-click on the OPC Data Source Definition aspect in the Aspect List
Area.
h. Click on the Service Group drop-down menu and select the SG_IT
Server.
i. Click on the OPCDA_Provider_<servername> that was configured in
Step c.
j. Click Apply.
k. The procedure is complete. Step l through Step r are only required if the
condition in Step b is met.
l. Use the Structure Selector to open the Control Structure.
m. Use the Object Browser to navigate to the IT Server object.
n. Double-click on the OPC Data Source Definition aspect in the Aspect List
Area.
o. Select New.
p. Click Add and select the appropriate Service Provider from the list.
q. Click OK twice.
r. Click Apply.
68 3BSE036342R4101
Section 2 Upgrading SV 4.0 to SV 4.1 Batch Management Post Upgrade
Restoring Batches
To restore batches:
1. Click Pick Files.
2. Select the batch files to be restored in the standard Windows Open window.
3BSE036342R4101 69
Manufacturing Management Post Upgrade Section 2 Upgrading SV 4.0 to SV 4.1
3. Click OK.
4. Repeat Step 1 through Step 3 until all the desired batch files are selected.
5. Click Restore.
Use the Remove from List and Clear All buttons to delete the selected batch or all
the batches from the list.
Click View Log to view a record of the actions taken during the last restore
operation.
70 3BSE036342R4101
Section 2 Upgrading SV 4.0 to SV 4.1 Information Management Post Upgrade
Use the following procedure to upgrade Batch Management recipes that utilize
Manufacturing Management extension action blocks:
1. Verify that the Manufacturing Management 4.1 system extension has been
installed.
2. For each Batch Management recipe procedure that contains Manufacturing
Management extension action blocks:
a. Open the procedure in the Procedure Configuration Editor window.
b. Select an extension action.
c. Select Procedure > Assign Object.
d. Click Action Definition in the Action Definition window.
e. Select MM Server.
f. Click OK.
g. Click OK in the Extension Action Assignment window.
h. Repeat Step b through Step g for each extension action block in the recipe.
i. Save the procedure and exit the Procedure Configuration Editor window.
j. Approve the procedure.
3. Delete the MM Extension Action and MM Extension Action Definition aspects
from the Manufacturing Management object in the Library Structure.
3BSE036342R4101 71
Information Management Post Upgrade Section 2 Upgrading SV 4.0 to SV 4.1
Select this procedure in step 2 and then in step 5 select the Enable PAS procedure
72 3BSE036342R4101
Section 2 Upgrading SV 4.0 to SV 4.1 Information Management Post Upgrade
3. In the Set PAS Service Account dialog, Figure 19, enter the user account and
password has specified in the System Workplace Client Configuration Wizard
System Software User Settings dialog.
4. Confirm the password, then click OK.
Figure 19. Setting User Name and Password for PAS Services
3BSE036342R4101 73
SoftPoint Service Post Upgrade Section 2 Upgrading SV 4.0 to SV 4.1
74 3BSE036342R4101
Section 2 Upgrading SV 4.0 to SV 4.1 Calculations Service Post Upgrade
3. Click Deploy to start the deploy process. Completion of the deploy process is
indicated by the Deploy ended message, Figure 21.
3BSE036342R4101 75
Scheduling Service (Application Scheduler) Post Upgrade Section 2 Upgrading SV 4.0 to SV 4.1
76 3BSE036342R4101
Section 3 Upgrading SV 3.1/2 to SV 4.1
Introduction
Upgrading directly from SV 3.1 or SV 3.1/1 to SV 4.1 is not supported. If
running one of these versions, it is necessary to upgrade to SV 3.1/2 before
upgrading to SV 4.1.
Upgrading the 800xA System requires the plant to be shut down. To guarantee
the functionality of the upgraded system, follow these upgrade instructions
carefully and perform them in a well defined order.
Upgrade Order
This section is organized so that the instructions are presented in the proper upgrade
order. Do not skip any steps.
3BSE036342R4101 77
Upgrade Paths Section 3 Upgrading SV 3.1/2 to SV 4.1
Upgrade Paths
Figure 22 shows a high level flow of the upgrade paths.
All paths require, after backup and before restore, installing the 800xA System
software and creating the system as if it were a new installation.
78 3BSE036342R4101
Section 3 Upgrading SV 3.1/2 to SV 4.1 SV 3.1/2 Upgrade Activities
3BSE036342R4101 79
System Preparation and Shutdown Section 3 Upgrading SV 3.1/2 to SV 4.1
80 3BSE036342R4101
Section 3 Upgrading SV 3.1/2 to SV 4.1 System Preparation and Shutdown
h. Open the newly created result.txt file using Windows Notepad or any other
suitable editor and verify that all registrations were successful.
5. Start the System Message Service.
6. Start the Alarm and Event Service.
3BSE036342R4101 81
System Preparation and Shutdown Section 3 Upgrading SV 3.1/2 to SV 4.1
82 3BSE036342R4101
Section 3 Upgrading SV 3.1/2 to SV 4.1 System Preparation and Shutdown
3BSE036342R4101 83
System Preparation and Shutdown Section 3 Upgrading SV 3.1/2 to SV 4.1
84 3BSE036342R4101
Section 3 Upgrading SV 3.1/2 to SV 4.1 System Preparation and Shutdown
3BSE036342R4101 85
System Preparation and Shutdown Section 3 Upgrading SV 3.1/2 to SV 4.1
86 3BSE036342R4101
Section 3 Upgrading SV 3.1/2 to SV 4.1 System Preparation and Shutdown
a. If Runtime Asset Monitors are being used in the system, save the Runtime
Asset Monitor data directory (DeviceRunTimeMSLogicStore) to a safe
media. Assuming the default directory was selected during Asset
Optimization installation, the Runtime Asset Monitor data directory is
located in:
...\Program Files\ABB Industrial IT\Optimize IT\Asset
Optimization\AssetMonitorEnvironment\Bin
Save the entire DeviceRunTimeMSLogicStore data directory. The Bin directory
contains the DeviceRunTimeMSLogicStore data directory as well as individual
files named DeviceRunTimeMSLogicStore.dll and
DeviceRunTimeMSLogicStore.pdb. If the individual files are saved instead of the
entire data directory, the configuration will be lost.
b. If XY Profile Deviation Asset Monitors are being used in the system, save
the XY Profile Deviation Asset Monitor data directory
(XY_Reference_Profiles) to a safe media. Assuming the default directory
was selected during Asset Optimization installation, the
XY_Reference_Profiles directory is located in:
...\Program Files\ABB Industrial IT\Optimize IT\Asset
Optimization\AssetMonitorEnvironment\Bin
2. Save Maximo Integration:
The Maximo Integration information can be found on the Asset Optimization
Server node. Reference the Service Structure for the name of the Asset
Optimization Server node.
a. Although MRO Software's Maximo system is separate from the 800xA
system, it is a good idea to back up the system in use. Follow Maximo
standard practices for Maximo system backup.
b. The MxDef files provide the mapping between the 800xA System
environment and the Maximo system.
Do not edit the MxDef files without an extensive knowledge of the Maximo SDK
for Business Components documentation. Do not edit the MxDef files without a
close consulting association with MRO Software Inc. personnel to determine
what fields are required. Editing these files without the required knowledge and
experience may result in problems with the Maximo system and CMMS
interface to the Maximo system.
3BSE036342R4101 87
System Preparation and Shutdown Section 3 Upgrading SV 3.1/2 to SV 4.1
Perform the following procedure if changes are made to the MxDef files, in order
to prevent the customized MxDef files from being overwritten during an upgrade
or reinstallation of Asset Optimization. The software will first look in the
subdirectories created in the procedure for the MxDef files before looking in the
default MxDef file location.
c. Assuming the default directory was selected during Asset Optimization
installation, the default Maximo Definition (MxDef) files supplied with
Asset Optimization are located in:
...\Program Files\ABB Industrial IT\Optimize IT\Asset
Optimization\ABBAO\Services\MOM\MxDefs
d. If changes are made to the MxDef files, create and save them in the
following directory (assuming the default directory was selected during
Asset Optimization installation).
...\Program Files\ABB Industrial IT\Optimize IT\Asset
Optimization\ABBAO\Services\MOM\MxDefs\server_name\
app_server
Where:
<server_name>\<app_server> is the combination of the MRO
Server Name and the MRO Application Server Name fields from the
Maximo Equipment ID aspect. These fields are configured in the Aspect
System Structure in the Maximo Equipment ID aspect. The resultant path
to the customized MxDef files will look like, for example:
...\Program Files\ABB Industrial IT\Optimize IT\Asset
Optimization\ABBAO\Services\MOM\MxDefs\Maximo5\MxServer
This allows for customization of MxDef files on the Maximo Server level
as well as on the Maximo Application Server level. Refer to Maximo
documentation for an explanation of Maximo Application Servers.
Refer to Industrial IT, 800xA - Asset Optimization, Configuration for more
information on MxDef files.
88 3BSE036342R4101
Section 3 Upgrading SV 3.1/2 to SV 4.1 System Preparation and Shutdown
3BSE036342R4101 89
System Preparation and Shutdown Section 3 Upgrading SV 3.1/2 to SV 4.1
d. Click the Configuration tab to produce a view in the Preview Area such
as the one shown in Figure 23.
TC06067A
Item Setting/Value
Spooler Settings
90 3BSE036342R4101
Section 3 Upgrading SV 3.1/2 to SV 4.1 System Preparation and Shutdown
Table 3. SMS and e-mail Messaging GSM Hardware Setup Worksheet (Continued)
Item Setting/Value
Port Settings
Save PIN (only if Query PIN is checked) Checked or Unchecked (circle one)
3BSE036342R4101 91
System Preparation and Shutdown Section 3 Upgrading SV 3.1/2 to SV 4.1
Table 3. SMS and e-mail Messaging GSM Hardware Setup Worksheet (Continued)
Item Setting/Value
Use for Delivery Notification Only Unchecked (verify and do not change)
92 3BSE036342R4101
Section 3 Upgrading SV 3.1/2 to SV 4.1 System Preparation and Shutdown
and placed in a safe place, the data for that batch should be removed from the
batch database.
Archiving batch data has no effect on the uniqueness of the batch ID. Even
after data associated with a batch ID has been removed from the system, a
record of the batch ID will be retained on the system. The batch ID can never
be reused.
Do not archive directly to or restore directly from CDs or DVDs. Archive to or
restore from hard disk drives which can be backed up to CDs or DVDs using
commercially available software.
3. Use the Batch Management backup/restore utility to back up and PFC color
configuration information and batch IDs. Access this utility by selecting:
Start > Programs > ABB Industrial IT > 800xA System >
Batch Management > Backup Restore
Enabling any of the options listed in the backup/restore utility enables the
Backup and Restore buttons.
The options are:
PFC color configuration.
Batch IDs.
When Backup is selected, a standard Windows open file window that allows
browsing to any desired folder is presented. A confirmation window provides
the chance to cancel before the backup file is written.
4. Disable the Batch Alarm & Event Service Group and Batch Service Group
before proceeding. To disable the service groups:
a. Open a Plant Explorer Workplace.
b. Use the Structure Selector to open the Service Structure.
c. Use the Object Browser to select:
Services\Alarm & Event, Service\batch_group_name,
Service Group
d. Select Service Group Definition in the Aspect List Area.
e. Select the Configuration tab in the Preview Area.
3BSE036342R4101 93
System Preparation and Shutdown Section 3 Upgrading SV 3.1/2 to SV 4.1
94 3BSE036342R4101
Section 3 Upgrading SV 3.1/2 to SV 4.1 System Preparation and Shutdown
This opens the Process Administration Service dialog shown in Figure 24.
3BSE036342R4101 95
System Preparation and Shutdown Section 3 Upgrading SV 3.1/2 to SV 4.1
The History database can be backed up to any drive on the machine, including any
mapped network drives. The database may also be divided among several drives
(different files may be located on different drives on the machine). This may occur,
for example, if the History quota is exceeded on one of the drives, forcing any
remaining History database files to be stored on a different drive.
To avoid any ambiguity, the backup operation produces a zipped archive of
compressed History database files for each drive that contains at least some portion
of the database, where each archive contains only the database files that are stored
on the corresponding drive. The backup utility uses the naming convention name-
drive.zip for the zipped archives that it produces. For example, if the History
database is located entirely on the C:\ drive and you wish to back up the database to
a zipped archive called hist, the backup operation will compress the database files
into a zipped archive named hist-C.zip.
If the data files exceed two gigabytes, or if there are more than 25,000 files, then
multiple zip files will be created using the following naming convention:
First File name-drive.zip
Next File name-drive01.zip
Next File name-drive02.zip
Considerations. When backing up the History database, make sure the disk is
ready and available on the machine on which the procedure is to occur. The log file
should be checked after the backup operation to make sure that the backup operation
completed successfully.
It is recommended that you clean the history database BEFORE you make the
backup. Open a Windows Command Prompt window and enter hsDBMaint -
clean.
Make sure the system Archive is not getting full. Temp space is required to make the
backup. If the log file indicates that the Oracle export failed, use the option to export
to a disk with more space.
96 3BSE036342R4101
Section 3 Upgrading SV 3.1/2 to SV 4.1 System Preparation and Shutdown
-a D:\HSBATA\History
3BSE036342R4101 97
System Preparation and Shutdown Section 3 Upgrading SV 3.1/2 to SV 4.1
8. After the HsBAR Output Window closes, monitor the progress in the Progress
Status area of the IM Historian Backup/Restore Utility window and click
Finish when the backup is complete.
If a message appears stating that there are inconsistencies between the log
configurations in the Aspect System and the log configurations in Oracle, it may
be because the database was not cleaned before running the backup. Use the
hsDBMaint Clean function to clean the database and then rerun the backup. If
this does not fix the problem, contact ABB Technical Support for further
assistance.
Saving Other Information Management Related Files. There are several other
files related to Information Management to be saved as part of a total system
backup.
More detailed instructions for this procedure can be found in the section on
backing up individual Information Management applications in the appropriate
Information Management instruction.
History Archive Data: For each archive device, go to the location specified by
the Device Filename and copy the folders under that directory to a safe
location. Do this even if automatic backup is configured.
History Archive State Information: The folder that holds the last archive
time and other archive state information must be copied to a safe location. The
folder name is Archive and it is located in:
...\Documents and Settings\All Users\
Application Data\ABB\IM\Archive
Copy the entire folder.
Reports: Save any report template files created in Microsoft Excel,
DataDirect, and/or Crystal Reports . Also save report output files created as a
result of running these reports via the Scheduling Services.
Desktop Trends: Back up trend display, ticker display, and tag explorer files.
Display Services: Back up the directories for custom users, as well as display
and user element definitions.
DataDirect: Back up custom text files for object, object type, and attribute
menus used on the DataDirect windows.
98 3BSE036342R4101
Section 3 Upgrading SV 3.1/2 to SV 4.1 System Preparation and Shutdown
3BSE036342R4101 99
System Preparation and Shutdown Section 3 Upgrading SV 3.1/2 to SV 4.1
100 3BSE036342R4101
Section 3 Upgrading SV 3.1/2 to SV 4.1 800xA System Backup
Requirements
All system extensions that are part of the system must be installed and added on the
node where the backup will be taken (usually the main Aspect Server node). No
changes can be made (especially to the Aspect directory) during the online backup
process.
Backup Procedure
The following steps outline the 800xA system backup procedure. Refer to Industrial
IT, 800xA - System, Operator Workplace, Configuration for more detailed
information.
3BSE036342R4101 101
800xA System Backup Section 3 Upgrading SV 3.1/2 to SV 4.1
102 3BSE036342R4101
Section 3 Upgrading SV 3.1/2 to SV 4.1 Stopping Windows Services
3BSE036342R4101 103
SV 4.1 Upgrade Activities Section 3 Upgrading SV 3.1/2 to SV 4.1
104 3BSE036342R4101
Section 3 Upgrading SV 3.1/2 to SV 4.1 System Upgrade
System Upgrade
The Microsoft Windows operating systems supported in SV 4.1 are:
Refer to Industrial IT, 800xA - System, Installation for specific information on
what node types can be installed on each operating system.
Windows XP Professional with SP2.
Windows Server 2003 with SP1.
Windows 2000 Server with SP4.
The following rules apply:
Any existing nodes that do not have one of these operating systems must be
reformatted and the compatible operating system must be installed.
All IM (Information Management) Server nodes being upgraded must be
reformatted and the operating system installed, even if the existing operating
system is compatible.
All nodes being upgraded, that are not IM Server nodes, with a compatible
operating system require an update to the existing operating system.
Refer to Upgrade Paths on page 78 for more information.
3BSE036342R4101 105
System Upgrade Section 3 Upgrading SV 3.1/2 to SV 4.1
4. Refer to Industrial IT, 800xA - System, Installation and update third party
software approved by ABB (refer to Appendix A, Third Party Software for SV
4.1 in this document).
5. Refer to Industrial IT, 800xA - System, Installation and install all required
800xA System software.
Initialize the Batch database during installation of the Production Management -
Batch Management software.
6. Install the License Server on the primary Aspect Server node and install the
license file (refer to Industrial IT, 800xA - System, Installation).
7. Refer to Industrial IT, 800xA - System, Post Installation if it is necessary to set
up shared folders for PROFIBUS and HART Device Integration and/or
FOUNDATION Fieldbus Device Integration.
8. Refer to 800xA System Restore on page 107 of this instruction and perform all
necessary steps.
9. Refer to Post Upgrade Procedures on page 113 of this instruction and perform
all necessary steps.
10. Refer to Industrial IT, 800xA - System, Post Installation to perform any post
installation tasks that are not restored.
106 3BSE036342R4101
Section 3 Upgrading SV 3.1/2 to SV 4.1 800xA System Restore
5. Refer to Industrial IT, 800xA - System, Installation and install all required
800xA System software.
6. Refer to Industrial IT, 800xA - System, Installation and install the license files
on the primary Aspect Server node.
7. Refer to Industrial IT, 800xA - System, Post Installation if it is necessary to set
up shared folders for PROFIBUS and HART Device Integration and/or
FOUNDATION Fieldbus Device Integration.
8. Refer to 800xA System Restore on page 107 of this instruction and perform all
necessary steps.
9. Refer to Post Upgrade Procedures on page 113 of this instruction and perform
all necessary steps.
10. Refer to Industrial IT, 800xA - System, Post Installation to perform any post
installation tasks that are not restored.
3BSE036342R4101 107
800xA System Restore Section 3 Upgrading SV 3.1/2 to SV 4.1
Restore Procedure
The following steps outline the 800xA system restore procedure. Refer to Industrial
IT, 800xA System, Operator Workplace, Configuration for more detailed
information.
1. Minimize the system to a single node primary Aspect Server using the
following procedure:
a. Disconnect and shut down all clients from each client.
b. Stop the 800xA system from the primary Aspect Server node.
c. At each Connectivity Server, Application Server, and redundant Aspect
Server node:
Restart node (frees links to file system and processes).
Stop the server.
Delete the system.
Use the Configuration Wizard to verify there is no system remaining.
Verify that OperateITData and/or OperateITTemp directories do not exist
in the root of any drive. Delete them manually if found.
Shut down all nodes except the one being used to restore the 800xA
system. This is the same node from which the backup was taken.
108 3BSE036342R4101
Section 3 Upgrading SV 3.1/2 to SV 4.1 800xA System Restore
TC07438A
3BSE036342R4101 109
800xA System Restore Section 3 Upgrading SV 3.1/2 to SV 4.1
4. Check for messages in the log file. Refer to Appendix B, Warning and Error
Messages to resolve any received warning or error messages.
5. Check CPU load in the workstation. System Message service may generate a
high load (>90%). If this continues for longer than approximately 10 minutes,
restart the service.
6. One node at a time, start up all nodes again and connect them to the 800xA
system in the following order:
Aspect Server nodes.
Connectivity Server nodes.
Application Server nodes.
Client nodes.
a. Use the following guidelines while connecting nodes, using the
Configuration Wizard as shown in Figure 29 and Figure 30. This must be
performed on the node that is going to be connected, not on the node on
which the restore was performed.
TC07431A
110 3BSE036342R4101
Section 3 Upgrading SV 3.1/2 to SV 4.1 800xA System Restore
TC07432A
Set the current system as the default system when connecting nodes to the
system Figure 31 and Figure 32:
TC07433A
3BSE036342R4101 111
800xA System Restore Section 3 Upgrading SV 3.1/2 to SV 4.1
TC07434A
112 3BSE036342R4101
Section 3 Upgrading SV 3.1/2 to SV 4.1 Post Upgrade Procedures
b. Record the number of objects and aspects listed in the System Size
Information area of the window.
c. Right-click the Control Structure\control_network_name, Control
Network\Control Structure aspect of one of the control networks
contained in the system.
d. Select Properties on the pop-up menu.
e. Select the Statistics tab.
f. Record the number of objects listed.
Step g through Step k are not applicable to systems with only 800xA for
Harmony.
g. Right-click the Control Structure aspect within a controller project of the
control network selected in Step c.
h. Select Properties on the pop-up menu.
i. Record the number of objects listed.
j. Repeat Step g through Step i for all the controller projects within the
control network.
k. Repeat Step c through Step j for every control network in the system.
The number of aspects and objects after system restoration should be in the same
range as those recorded during system backup, although there will likely be more.
3BSE036342R4101 113
Post Upgrade Procedures Section 3 Upgrading SV 3.1/2 to SV 4.1
Connections between Alarm List and Alarm and Event OPC Server. This
connection is valid only for upgrading of Alarms and Events.
SV 3.1/2 has one layer between the clients (e.g. an alarm list) and the OPC Alarm
and Event Server that provides the alarms. This layer is realized by the Alarm and
Event Service, as shown in Figure 33.
ALARM LIST
T05252B
114 3BSE036342R4101
Section 3 Upgrading SV 3.1/2 to SV 4.1 Post Upgrade Procedures
SV 4.1 has two layers, realized by the Alarm Manager which is on top of the Event
Collector as shown in Figure 34.
Figure 34. Alarm Manager and Event Collector Layers for SV 4.1
Automatic Configuration. The object tree below the Alarm and Event Service is
recreated below the Event Collector Service. The required library objects are
also created.
The Alarm Manager Service is automatically configured. Some manual
configuration is also required.
3BSE036342R4101 115
Post Upgrade Procedures Section 3 Upgrading SV 3.1/2 to SV 4.1
To help with this task, the upgrading code reports, with messages, how the
configuration was in the backed up system. The messages become part of the
Configuration Wizard log and are similar to the following:
Wed Aug 11 10:34:58 2004: For service group
SoftAlarms, the AE Server before upgrade was
ABB.AdvAeSoftAlarmsHandler.1.
Use this information to configure the service groups below the Event Collector
Service correctly when the nodes have been added to the upgraded system.
The Alarm and Event Service uses another identification of the OPC Alarm and
Event Server than the Event Collector does. The translation of the identification
is usually easy, e.g. ABB.AdvAeSoftAlarmsHandler.1 to
AdvAeSoftAlarmsHandler Class. In some cases, the OPC Alarm and Event
Server might have been given a different name and consequently, the
identification will be according to that name.
Organizing the Library Objects
The upgrade code creates one library object per Alarm and Event Service
Group that was found in the backup. The library objects are located below the
Alarm Collection Definitions object in Library Structure. The intention,
however, is that there should be one library object per OPC Alarm and Event
Server type that exists in the system, because the library object describes the
capabilities of an OPC Alarm and Event Server. All groups working towards a
specific OPC Alarm and Event Server type can share one library object.
After an upgrade, you should organize the structure so that it complies with the
above intention. Do not forget to update the settings that refer to the library
object in the Event Collector Service Groups, in the Special Configuration tab
of the Service Group Definition aspect.
Check Alarm Manager Service Configuration
In SV 3.1/2, it is possible to have a number of Alarm and Event Service groups,
all with individual configurations. In SV 4.1, these groups are replaced with
one group. Consequently, the individual configurations are replaced with one
configuration. This common configuration is automatically generated from the
individual configurations and should be checked, because:
There are one or more new parameters that should be configured.
116 3BSE036342R4101
Section 3 Upgrading SV 3.1/2 to SV 4.1 Post Upgrade Procedures
Backed up data may be ambiguous. One Alarm and Event Service group
might have another configuration than another group in the backed up
system.
Modifications might need to be made.
The configuration is found in the Special Configuration tab of the Service
Group Definition aspect of the Alarm Manager Service group.
Figure 35 shows an example of what is automatically specified after the
upgrade and Figure 36 shows how to select the OPC Alarm and Event Server
for AC 800M.
TC07437A
3BSE036342R4101 117
Post Upgrade Procedures Section 3 Upgrading SV 3.1/2 to SV 4.1
TC07436A
118 3BSE036342R4101
Section 3 Upgrading SV 3.1/2 to SV 4.1 Post Upgrade Procedures
3BSE036342R4101 119
Post Upgrade Procedures Section 3 Upgrading SV 3.1/2 to SV 4.1
120 3BSE036342R4101
Section 3 Upgrading SV 3.1/2 to SV 4.1 Post Upgrade Procedures
Post Upgrade Procedure. Use the following procedure to restore Control IT for
AC 800M information:
1. Configure the memory setting for OPC Server and Control Builder (found in
the Setup Wizard for each product) to the saved and recorded values.
2. Control Builder stores its settings (systemsetup.sys) on disk in the following
directory:
...\ABB Industrial IT Data\Engineer IT Data\Control
Builder M Professional
Add the file saved on the safe media to the system.
3BSE036342R4101 121
Post Upgrade Procedures Section 3 Upgrading SV 3.1/2 to SV 4.1
122 3BSE036342R4101
Section 3 Upgrading SV 3.1/2 to SV 4.1 Post Upgrade Procedures
3BSE036342R4101 123
Post Upgrade Procedures Section 3 Upgrading SV 3.1/2 to SV 4.1
124 3BSE036342R4101
Section 3 Upgrading SV 3.1/2 to SV 4.1 Post Upgrade Procedures
To restore the parameter value set for each user-modified block class:
- Right-click and select Parameters... from the context menu that appears.
- Press the Reset button. Then choose User defined values, block type
specific and select the previously stored parameter value set from the list.
Press OK button.
- Important: Now leave the parameter dialog via the OK button.
To restore the dialog editor settings for each user-modified block class:
- Right-click and select Dialog editor... from the context menu that
appears.
- Select the existing Dialog Description and delete it.
- Click Import and open the appropriate file.
- Check the new values by clicking Check.
- Leave the Dialog editor by clicking OK.
Exit Fieldbus Builder FF.
b. To restore user-made changes of the Object Types in the FF Libraries:
After performing Step 2, (Check, Save, and Upload FF Libraries), Object
Types of existing instances have been moved to the FF Duplicates still in use
folder, located below the FFLibraries Object Type Group node of the Plant
Explorer Workplace.
To restore additional aspects of library objects:
Move additional aspects from Object Types (e.g. representing a device or
block type) in duplicate folders to the corresponding Object Types in the
FF device type folder.
c. Repeat Step 2 to synchronize the FF Libraries.
4. Update FF Libraries for HSE Subnet (Library Update).
Perform the following procedure for each HSE Subnet.
3BSE036342R4101 125
Post Upgrade Procedures Section 3 Upgrading SV 3.1/2 to SV 4.1
126 3BSE036342R4101
Section 3 Upgrading SV 3.1/2 to SV 4.1 Post Upgrade Procedures
3BSE036342R4101 127
Post Upgrade Procedures Section 3 Upgrading SV 3.1/2 to SV 4.1
800xA for Advant Master and 800xA for SafeGuard RTA Board Files
AC 400 Connect is referred to as 800xA for Advant Master after the upgrade.
SafeGuard Connect is referred to as 800xA for SafeGuard after the upgrade.
1. Restore the files:
DATHR1.CD
DATHR2.CD
DATHR3.CD
to the folder:
...\Program Files\ABB Industrial IT\OperateIT\AC400CI\AdvantBase\
Data\RTA\Init\
to the node where they belong.
2. Replace them if asked to do so.
3. Restart the RTA Board.
4. Restore the:
Time synchronization registry key (REVERSED_SYNC_MODE):
HKEY_LOCAL_MACHINE\SOFTWARE\ABB\AFW\SystemModules\
AfwTimeServerAdaptor\1.0-0\Private
MB300 node and network address for RTA board in RTA board
Configuration Aspect.
128 3BSE036342R4101
Section 3 Upgrading SV 3.1/2 to SV 4.1 Post Upgrade Procedures
Restore 800xA for Harmony Information. Use the following procedure to restore
800xA for Harmony information:
1. Log in to the 800xA for Harmony local service account on the primary
Connectivity Server node.
2. Use the 800xA for Harmony Configuration backup/restore utility to restore the
800xA for Harmony Configuration information from a saved backup.
a. Select:
Start > All Programs > ABB Industrial IT 800xA > 800xA for OCS
Systems > Harmony > Configuration > Restore Configuration
b. Click Connect in the Harmony Connect Configuration Backup/Restore
window.
c. Enter the name of the Harmony Configuration Server database backup file
in the Backup File field.
d. Click Restore.
e. If a prompt appears indicating that the system version does not match the
backup version, click OK and the backup file will be saved to a temporary
SQL database. Its components will then be migrated to the Configuration
Server database.
If a prompt does not appear, it means that the versions are the same and
the backup will be restored directly to the Configuration Server database,
overwriting it if it already exists.
f. If the message Services must be stopped, REBOOT system now
then restart this application! is displayed, restart the node and
repeat Step a through Step e.
g. Click Exit when the restore operation is complete.
Harmony Alarm and Event OPC Provider Setup. This requires the user to add the
Harmony OPC alarm server program ID to a Service Group under the Event
Collector category in the Service structure:
1. In Plant Explorer Workplace, select the Service Structure.
2. Use the Object Browser to navigate to:
Services > Event Collector, Service
3BSE036342R4101 129
Post Upgrade Procedures Section 3 Upgrading SV 3.1/2 to SV 4.1
3. If they do not already exist, create the Service Group and Service Provider
Objects by right-clicking on EventCollector, Service and select New Object
from the context menu that appears.
4. The New Object dialog appears. Select Service Group and enter a name, such
as Harmony_AE_SGx (where x is a running number) and click Create.
5. Right-click on the newly created Service Group object and select New Object
from the context menu that appears.
6. The New Object dialog appears. Select Service Provider and enter a name,
such as Harmony_AE_SP_nodename (where nodename is a Connectivity
Server name) and click Create.
7. Select the Service Provider Definition aspect for the
Harmony_AE_SP_nodename Service Provider Object in the Aspect List Area.
8. Select the Configuration tab in the Preview Area.
9. Select the name of the Harmony Connectivity Server in the Node drop-down
list box.
10. Click Apply.
11. Repeat Step 5 through Step 10 for a backup Connectivity Server.
12. Use the Object Browser to navigate to the Event Collector Service Group
previously created.
13. Select the Service Group Definition aspect in the Aspect List Area.
14. Select the Special Configuration tab in the Preview Area.
15. Select ABB Maestro/OPC Event Server (InProc) in the Alarm Server drop-
down list box.
16. Select Harmony Alarms in the Collection Definition drop-down list box.
17. Verify the connection by clicking on the Status tab on the Event Collector
object and verify that the state is Service for the Primary Connectivity Server
and Standby for the Redundant Connectivity Server.
18. Use the Object Browser to navigate to AlarmManager, Service and expand
it.
19. Select Basic, Service Group
130 3BSE036342R4101
Section 3 Upgrading SV 3.1/2 to SV 4.1 Post Upgrade Procedures
Synchronize the Aspect Directory. Synchronize the Aspect directory with the
Harmony Configuration Server using the Harmony Synchronizer Aspect, which is
part of the Harmony OPC Server network. Refer to Industrial IT, 800xA - System,
800xA for Harmony, Configuration for more detailed information on how to
synchronize.
3BSE036342R4101 131
Post Upgrade Procedures Section 3 Upgrading SV 3.1/2 to SV 4.1
4. The InstallShield Wizard for PLC Connect appears. Refer to Industrial IT,
800xA - System, Installation to select and install the desired features.
5. If the IEC60870 feature is installed refer to Industrial IT, 800xA System - PLC
Connect, Configuration and reload the saved IEC configuration.
132 3BSE036342R4101
Section 3 Upgrading SV 3.1/2 to SV 4.1 Post Upgrade Procedures
2. Use the Object Browser to navigate to the first Generic Control Network
object.
3. Select Deploy in the Aspect List Area.
4. Press the SHIFT key and click Deploy in the Preview Area to ensure that a full
deploy is done.
5. The deploy begins and the progress is displayed in the Preview Area. The
deploy is completed when Deploy ended is displayed.
6. Repeat the procedure for any additional Generic Control Network objects.
3BSE036342R4101 133
Post Upgrade Procedures Section 3 Upgrading SV 3.1/2 to SV 4.1
134 3BSE036342R4101
Section 3 Upgrading SV 3.1/2 to SV 4.1 Post Upgrade Procedures
3BSE036342R4101 135
Post Upgrade Procedures Section 3 Upgrading SV 3.1/2 to SV 4.1
9. One of the new features in Asset Optimization Version 4.1 is support for Object
Type inheritance. An Asset Monitor on the Object Instance inherits its
configuration from the Asset Monitor in the Object Type if it was created via
the Copy to all instances property check in the Type Definition aspect. When
importing configurations that existed before Version 4.1, the configuration
inheritance changes shown in Table 5 will be made:
Type Change
Asset Monitor is on the Object Type. This Asset Monitor will be set to inherit from the
Asset Monitor category.
Asset Monitor is on the instance of the generic
object.
Asset Monitor in the instance that has Object
Type.
Corresponding Asset Monitor does not exist in Then for each of the 4 configuration tabs (Asset
the Object Type. Monitor, Conditions, Asset Parameters, and
Asset Monitor in the instance that has Object Input Records) the configuration inheritance
Type. values will be set to their pre 4.1 values.
Corresponding Asset Monitor exists in the
Object Type and the
Object Type Definition Aspect > Aspect
Control Tab > Copy to all instances
check box NOT selected.
136 3BSE036342R4101
Section 3 Upgrading SV 3.1/2 to SV 4.1 Post Upgrade Procedures
Type Change
Asset Monitor in the instance that has Object This Asset Monitor will be set to inherit from
Type. Object Type's Asset Monitor.
Corresponding Asset Monitor exists in the
Object Type and the
Object Type Definition Aspect > Aspect
Control Tab > Copy to all instances
check box is selected. Then for each of the 4 configuration tabs (Asset
Monitor, Conditions, Asset Parameters, Input
Records) if the configuration matches the
configuration in Object Type, inheritance values
will be set to TRUE, else to FALSE.
3BSE036342R4101 137
Post Upgrade Procedures Section 3 Upgrading SV 3.1/2 to SV 4.1
a. Use the Structure Selector to open the Service Structure in the Plant
Explorer Workplace.
b. Use the Object Browser to navigate to the:
Services > OpcDA_Connector, Service > SG_IT Server
object. If there is no object to navigate to, skip to Step l.
c. Open the OPCDA_Provider_<servername> object and double-click on the
Service Provider Definition aspect.
d. On the Configuration tab select the Enabled check box and click Apply.
The Current field should change to Service.
e. Use the Structure Selector to open the Control Structure.
f. Use the Object Browser to navigate to the IT Server object.
g. Double-click on the OPC Data Source Definition aspect in the Aspect List
Area.
h. Click on the Service Group drop-down menu and select the SG_IT
Server.
i. Click on the OPCDA_Provider_<servername> which was configured in
step Step c.
j. Click Apply.
k. Skip to IT Control Connection Update (Step 3).
l. Use the Structure Selector to open the Control Structure.
m. Use the Object Browser to navigate to the IT Server object.
n. Double-click on the OPC Data Source Definition aspect in the Aspect List
Area.
o. Select New.
p. Click Add and select the appropriate Service Provider from the list.
q. Click OK twice.
r. Click Apply.
138 3BSE036342R4101
Section 3 Upgrading SV 3.1/2 to SV 4.1 Post Upgrade Procedures
3BSE036342R4101 139
Post Upgrade Procedures Section 3 Upgrading SV 3.1/2 to SV 4.1
140 3BSE036342R4101
Section 3 Upgrading SV 3.1/2 to SV 4.1 Post Upgrade Procedures
To restore batch history, select the batch history restore aspect. By default a Batch
History Restore aspect is located in Library Structure\Batch
Management\Overviews. However, this aspect can be added to any 800xA System
object. The Batch History Restore window is displayed.
3BSE036342R4101 141
Post Upgrade Procedures Section 3 Upgrading SV 3.1/2 to SV 4.1
Configure the PAS User Account. The user account for the Process
Administration Service (PAS) must be configured to match the service account
information entered during 800xA System installation. This allows related services
to log on to the Information Management Server where they will run.
The service account information entered during 800xA System installation (not
the password) is available from the System Software User Settings selection in
the Configuration Wizard.
142 3BSE036342R4101
Section 3 Upgrading SV 3.1/2 to SV 4.1 Post Upgrade Procedures
2. Click Run Selected Configuration Tool to launch the Set PAS Service
Account dialog shown in Figure 38.
3. Enter the service account username and password as entered during 800xA
System installation and click OK.
4. Return to the Information Management Configuration Assistant.
3BSE036342R4101 143
Post Upgrade Procedures Section 3 Upgrading SV 3.1/2 to SV 4.1
5. Run the Configuration Tool for all applications with Required in the
Required column and Not Complete in the Status column.
When creating the Oracle instance, deselect the check box on the Summary
Display so that a History Database is not created. This will prevent History from
starting until after the History Database is restored.
Considerations. When restoring the History database, make sure the disk is ready
and available on the node on which the procedure is to occur. Also, ensure that no
applications are accessing the Oracle database. The log file should be checked after
the restore operation to make sure that the restore operation completed successfully.
This procedure can also be performed by using the pasgui command in the Run
dialog (Start > Run).
144 3BSE036342R4101
Section 3 Upgrading SV 3.1/2 to SV 4.1 Post Upgrade Procedures
1. Use PAS to stop all Information Management processes and the Inform IT
History service provider for this node.
a. Use the Windows Taskbar to select:
Start > Programs > Administrative Tools > PAS
b. Click Stop All in the PAS dialog. This will stop the Inform IT History
Service Provider.
If it is suspected that the Inform IT History Service Provider has not stopped, it
can be stopped now by selecting the Inform IT History Service Provider for this
node in the Service Structure, selecting the Configuration tab on the Service
Provider Definition aspect, deselecting Enabled, and clicking Apply.
2. Ensure that no third party applications access the Oracle database during the
restore operation.
3. Select:
Start > All Programs > ABB Industrial IT 800xA > Information
Mgmt > History > Backup and Restore.
4. Verify Restore configuration from a backup file(s) is enabled in the
Welcome to IM Historian Backup and Restore Utility dialog as shown in
Figure 39.
3BSE036342R4101 145
Post Upgrade Procedures Section 3 Upgrading SV 3.1/2 to SV 4.1
146 3BSE036342R4101
Section 3 Upgrading SV 3.1/2 to SV 4.1 Post Upgrade Procedures
If the restore operation fails with Oracle Error Message 1652 - Unable to
extend tmp segment in tablespace tmp - it may be due to a large OPC
message log which exceeds the tmp tablespace capacity during the restore
operation.
Use the Database Instance Maintenance wizard to increase the tmp tablespace.
The default size is 300 megabytes. Increase the tablespace in 300-Megabyte
increments and retry the restore operation until it runs successfully.
10. Click Finish when a message stating the execution is complete is displayed as
shown in Figure 41.
If the Progress Status dialog has warning messages with possible solutions as
indicated in Figure 42, read the possible solutions carefully, then click Finish and
proceed with the solution that best fits your problem. Refer to the Information
Management Release Notes for further guidelines.
3BSE036342R4101 147
Post Upgrade Procedures Section 3 Upgrading SV 3.1/2 to SV 4.1
11. Start all processes under PAS supervision. This will start the Inform IT History
Service Provider.
If it is suspected that the Inform IT History Service Provider has not started, it can
be started now by selecting the Inform IT History Service Provider for this node
in the Service Structure, selecting the Configuration tab on the Service Provider
Definition aspect, selecting Enabled, and clicking Apply.
12. Restart the Basic History Service Provider for this node:
a. Select the Basic History Service Provider object for the Information
Management node in the Service Structure in the Plant Explorer.
b. Select the Service Provider Definition aspect.
c. Select the Configuration tab.
d. Disable the Enabled option.
e. Click Apply.
f. Enable the Enabled option.
g. Click Apply.
Restoring Other Information Management Related Files. There are several other
files related to Information Management that need to be restored as part of total
system restore.
More detailed instructions for this procedure can be found in the section on
restoring individual Information Management applications in the appropriate
Information Management instruction.
History Archive Data: For each archive device, copy the appropriate folders
from the safe media to the location specified by the Device Filename.
History Archive State Information: Stop the Industrial IT Archive service in
the Service Structure. Copy the folder that holds the last archive time and other
archive state information from the safe media to:
...\Documents and Settings\All Users\Application
Data\ABB\IM\Archive
Restart the Industrial IT Archive service.
148 3BSE036342R4101
Section 3 Upgrading SV 3.1/2 to SV 4.1 Post Upgrade Procedures
3BSE036342R4101 149
Post Upgrade Procedures Section 3 Upgrading SV 3.1/2 to SV 4.1
2. Use the Structure Selector to open the Control Structure in the Plant Explorer
Workplace.
3. Use the Object Browser to navigate to Softpoint Generic Control
Network for the node where you want to deploy the SoftPoints (Figure 44).
4. Select Deploy in the Aspect List Area. This aspect provides a listing of
configuration changes that have occurred since the last deployment, and
indicates whether it requires a full or incremental deployment.
Incremental deploys only those changes that have been made since the last
deployment and is the typical selection. A prompt indicates when a Full deploy
is required.
5. Click Deploy to start the deploy process. During this time, SoftPoint
processing is suspended, and current values and new inputs are held. This
process is generally completed within five minutes, even for large
configurations. Completion of the deploy process is indicated by Deploy
ended.
150 3BSE036342R4101
Section 3 Upgrading SV 3.1/2 to SV 4.1 Post Upgrade Procedures
3BSE036342R4101 151
Post Upgrade Procedures Section 3 Upgrading SV 3.1/2 to SV 4.1
152 3BSE036342R4101
Section 3 Upgrading SV 3.1/2 to SV 4.1 Post Upgrade Procedures
3BSE036342R4101 153
Post Upgrade Procedures Section 3 Upgrading SV 3.1/2 to SV 4.1
154 3BSE036342R4101
Section 4 Upgrading SB 2.1/2 to SV 4.1
Introduction
Upgrading an 800xA System from SB 2.1/2 with Process Portal A, Control IT for
AC 800M, Information Manager, or AC 400 Connect products and applications to
SV 4.1 should be performed by someone with a comprehensive knowledge of the
system and the applications being upgraded. When other 800xA System products
and applications are included in the upgrade, it is recommended that ABB
Technical Support be contacted for assistance prior to starting the upgrade.
Upgrading the 800xA System requires the plant to be shut down. To guarantee
the functionality of the upgraded system, follow these upgrade instructions
carefully and perform them in a well defined order.
Maintain concurrent access to both the new and previous versions until the
upgrade has been performed. This makes it possible to easily retrieve any missing
data or files.
Test the Export files in a separate node before installing any new software. This
will verify the application was exported successfully, and can then be imported
reliably following the upgrade.
If any Control IT for AC 800M products are installed, refer to Control IT for AC
800M Considerations on page 157 before beginning the upgrade.
Porting of event data (system messages) from SB 2.1/2 to SV 4.1 is not
supported.
Upgrade Order
This section is organized so that the instructions are presented in the proper upgrade
order. Do not skip any steps.
3BSE036342R4101 155
Upgrade Paths Section 4 Upgrading SB 2.1/2 to SV 4.1
Upgrade Paths
Figure 45 shows a high level flow of the upgrade paths.
All paths require, after backup and before restore, installing the 800xA System
software and creating the system as if it were a new installation.
156 3BSE036342R4101
Section 4 Upgrading SB 2.1/2 to SV 4.1 SB 2.1/2 Upgrade Activities
3BSE036342R4101 157
Control IT for AC 800M Considerations Section 4 Upgrading SB 2.1/2 to SV 4.1
158 3BSE036342R4101
Section 4 Upgrading SB 2.1/2 to SV 4.1 System Backup
Issue Considerations
Compatibility AC 800M Connect, Control Builder M, Control Builder M Firmware, and
OPC Server for AC 800M must all be upgraded to the new version in
order to work together. However, controller peer-to-peer
communication is possible with other controllers running version 2.x/x
or 3.x./y by means of Access Variables.
Control Builder M All privilege/user handling done in Control Builder M in the previous
version (PrivUsers/PrivClasses) will be lost at the upgrade. Control
Builder M now uses the security function in the 800xA System.
AC 800C and Advant Projects including these controller types cannot be upgraded.
Controller 250 is no
longer supported.
System Backup
Make a complete backup of each node in the system using either the Windows
backup utility, Ghost, or an equivalent method before starting the upgrade
procedure. A valid backup insures that the system can be restored in the event the
upgrade procedure fails.
Back up all applications using the 800xA System backup function. Do not make any
modifications during the backup. If errors occur during backup, correct the error and
repeat until there are no remaining errors.
3BSE036342R4101 159
Save Application and Configuration Data Section 4 Upgrading SB 2.1/2 to SV 4.1
160 3BSE036342R4101
Section 4 Upgrading SB 2.1/2 to SV 4.1 Save Application and Configuration Data
3BSE036342R4101 161
Save Application and Configuration Data Section 4 Upgrading SB 2.1/2 to SV 4.1
Naming Conventions for Export Files. Use a naming convention for the export
files, to make them easier to import.
For example, a naming convention such as:
01_01_AspectSystemStructure
02_01_LibraryStructure_LogTemplates
02_02_LibraryStructure_TrendTemplates
will sort the files in the correct order for importing.
Export Procedure (General). Use the following general procedure to export the
contents of all structures:
1. Open the Import Export Tool and select:
Action > Export Structure
2. Select the structure to export in the Select Structure drop-down list box. Entire
structures should be selected for export only when the structure is user-defined.
Use the filtered export to select a specific Object Type to export from the selected
structure.
3. Click OK to export all objects and aspects in the selected structure.
4. Save the selected structures. Avoid more than 5,000 objects per AFW file.
When finished exporting application data from all structures in the system, refer
to Verify Exported Application Data on page 181 to verify the successful export
of all required data.
162 3BSE036342R4101
Section 4 Upgrading SB 2.1/2 to SV 4.1 Save Application and Configuration Data
Export
Structure Description/Procedure
Order
1 Aspect System Export objects that have been added or modified, such as user-
defined aspect categories and aspects.
Create AFW files that do not exceed 5,000 objects.
Engineering Studio: Export categories of Parameter Manager or
Document Manager if they have been modified or added.
Do not export the following categories:
- CBM_PulseSignalParameter
- CBM_SignalGroupInformation
- CBM_SignalParameter
- AutoCAD_Drawing
- Document
If there are any modifications done to these objects please redo them
manually in the new system
3BSE036342R4101 163
Save Application and Configuration Data Section 4 Upgrading SB 2.1/2 to SV 4.1
Export
Structure Description/Procedure
Order
1 (cont) Aspect System Information Manager:
(cont) Place content related to Information Manager in a separate file,
so it can be handled separately when working with the SV 4.1
system.
Create a security report for information about configured security
definition aspects.
Asset Optimizer Asset Monitoring
1. Use the import/export utility to export all project specific Asset
Monitor, Aspect Category objects in the Aspect System
Structure\Asset Monitoring, Aspect System\Asset Monitors,
Aspect Type\
2. Use the import/export utility to export all Asset Monitor Startup
Parameters which provide global configuration values for some
asset monitors (for example Running Time Check Asset Monitor)
in Aspect System Structure\Asset Monitoring, Aspect
System\Asset Monitors, Aspect Type\Running Time Check,
Aspect Category.
3. Use the import/export utility to export Process Portal B
Provider information in the Aspect System Structure\Asset
Monitoring, Aspect System\Process Portal B Provider, Aspect
Type\Process Portal B Provider, Aspect Category
DO NOT include dependencies in the resulting AFW file.
Asset Optimizer CMMS Connectivity
Use the import/export utility to export the CMMS System
identification information (Provider Properties) from the Aspect
System Structure\Maximo Connectivity, Aspect System\Maximo
Equipment ID, Aspect Type\Maximo Equipment ID, Aspect
Category
DO NOT include dependencies in the resulting AFW file.
164 3BSE036342R4101
Section 4 Upgrading SB 2.1/2 to SV 4.1 Save Application and Configuration Data
Export
Structure Description/Procedure
Order
1 (cont) Aspect System Asset Optimizer Messenger Service
(cont) 1. Use the import/export utility to export the Modem Device
parameters located in the Aspect System Structure\Messenger
Modem Device, Aspect System\Modem Device, Aspect
Type\Modem Device, Aspect Category.
2. Use the import/export utility to export the Email Device
parameters located in the Aspect System Structure\Messenger
Email Device, Aspect System\Email Device, Aspect Type\Email
Device, Aspect Category
DO NOT include dependencies in the resulting AFW file.
2 Library Export all additions/modifications, such as log templates, log template
groups (if they exist), trend templates, Event and Alarm templates,
ODA databases, and any created View Class definition.
Place the log templates related to Information Manager in a separate
file, and corresponding trend templates in another, so they can be
handled separately when working with the SV 4.1 system.
NOTE: Record all Alarm and Event List configurations as specified in
Step 6 under Process Portal A (Affinities, Securities, Service, and
User Structure) on page 179.
3 Graphical Export all additions/modifications, such as sub elements, property
elements, or graphic libraries (e.g. ActiveX libraries, added user
symbols). These objects are used by the Graphics Builder and runtime
system.
3BSE036342R4101 165
Save Application and Configuration Data Section 4 Upgrading SB 2.1/2 to SV 4.1
Export
Structure Description/Procedure
Order
4 Object Type Track the dependencies between different parts in the structure, such
as a library depending on a library, so that the import order will be
correct.
NOTE: Library dependencies can be viewed in the Control Builder.
AC 800M:
Do not export the Control Builder M standard libraries.
If there are additional graphic elements and/or special aspects
added to the Control Builder M standard libraries in the Object
Type Structure, these aspects must be exported in a separate file.
AC 800M:
Create AFW files for all user-defined libraries.
1. Use the Import/Export tool to export all user-defined libraries in
the Object Type Structure.
2. Include one library per file.
Create AFW files for the applications in the Object Type Structure:
1. Use the Import/Export tool to export all user-defined
applications from the Object Type Structure.
2. Include one application per file.
Create AFW files for any user made Hardware types in the Object
Type Structure:
1. Use the Import/Export tool to export all user made Hardware
types (created when inserted HWD-files in Control Builder M)
from the Object Type Structure.
Fieldbus Builder PROFIBUS/HART:
1. Export the Field Devices, Object Type Group folder.
2. Export HART field device objects that are not in the Field
Devices, Object Type Group folder.
3. Export user-made PROFIBUS field device objects, located in
the Controller Hardware folder.
166 3BSE036342R4101
Section 4 Upgrading SB 2.1/2 to SV 4.1 Save Application and Configuration Data
Export
Structure Description/Procedure
Order
4 (cont) Object Type Engineering Studio:
(cont) Do not export the following object types:
- CBM_Signals and its children
If there are any modifications done to these objects, they must be
redone manually in the new system
Asset Optimizer Asset Monitoring
Use the import/export utility to export all project specific Asset
Monitor object types.
5 Control AC 800M:
1. Create AFW files for the user-defined projects in the Control
Structure.
2. Use the Import/Export tool to export the user-defined projects
in the Control Structure.
3. Include one project per file.
4. Export the Control Network object in a separate file if there are
several projects below one Control Network object.
It is not necessary to export the Controllers part of a project, if that
part of the Control Structure does not include any manually added
aspects.
This part of the control Structure will automatically be regenerated, if
empty, when upgrading the Control Builder M project later on. Skipping
this part of the Control Structure significantly simplifies the upgrade.
3BSE036342R4101 167
Save Application and Configuration Data Section 4 Upgrading SB 2.1/2 to SV 4.1
Export
Structure Description/Procedure
Order
5 (cont) Control (cont) Fieldbus Builder PROFIBUS/HART:
1. Exclude Fieldbus Builder Management aspects and Device
Management aspects from Control Structure export (use filter
option to exclude).
2. Export the Control Structure again, but now only with Device
Management Aspects (use filter option to exclude all except
Device Management). Use a certain export file name for
identification.
3. Export Control Structure again, but now only with Fieldbus
Management Aspects (use filter option to exclude all except
Fieldbus Management). Use a certain export file name for
identification.
Do not export:
SoftPoint objects in the Control structure. These will be handled
by the SoftPoint export procedure as described in Information
Manager on page 174.
Lost and Found Branch.
6 Equipment Export the entire structure in one AFW file.
7 Procedure Export the entire structure in one AFW file.
8 Functional Export all application data in the structure.
Divide the export into several files if the structure contains more than
5,000 objects.
Do not export the sample ePlant, unless the application saved
information below it.
168 3BSE036342R4101
Section 4 Upgrading SB 2.1/2 to SV 4.1 Save Application and Configuration Data
Export
Structure Description/Procedure
Order
8 (cont) Functional (cont) Asset Optimizer Asset Monitoring
Use the import/export utility to export all objects that contain the
Asset Optimizer Asset Monitoring, Maximo Connectivity, and
Messenger object types, for example Asset Monitor Data Source.
Do not export Asset Monitoring Server aspects or Asset
Monitoring objects as this functionality has changed in 800xA SV
4.1.
Export the Asset Monitor Data Source Aspects from the objects.
Asset Optimization objects may also exist in the Location
Structure or Control Structure.
9 Location Export all application data in the structure.
Divide the export into several files if the structure contains more than
5,000 objects.
Do not export the sample ePlant, unless the application saved
information below it.
10 Workplace Export any application specific workplace, and additions or
modifications made to existing workplaces, such as logical colors.
Create AFW files for the changes in workplace structure, such as:
Logical colors (stored here in more than one branch).
Added workplaces.
Modified system aspects.
11 Admin Export document objects that have been added or modified.
Create a security report for information about configured security
definition aspects.
3BSE036342R4101 169
Save Application and Configuration Data Section 4 Upgrading SB 2.1/2 to SV 4.1
Export
Structure Description/Procedure
Order
12 User In general, export the entire structure in one AFW file. However, if
Asset Optimizer software is being used, separately export the
following aspects:
Maximo Credential
Devices
Message Schedule
Message Subscriber
DO NOT include dependencies in the resulting AFW file.
13 Scheduling1 Export Job Descriptions and related scheduling definition and action
aspects.
NOTE:
1. Schedules will automatically resume operation when the structure is imported following installation of the new
software unless they are disabled prior to export.
170 3BSE036342R4101
Section 4 Upgrading SB 2.1/2 to SV 4.1 Save Application and Configuration Data
2. Save all the files from the following directory of each Connectivity Server:
...\OperateITData1\History
3. Start the Basic History, Service Provider from the Service Structure.
OPC Server for AC 800M. Manually copy the following OPC Server for AC 800M
files from the Connectivity Servers to safe media:
systemsetup.sys, located in:
...\ABB Industrial IT Data\Control IT Data\
OPC Server for AC 800M n.n
Configuration files (*.cfg), located in:
...\ABB Industrial IT Data\Control IT Data\
OPC Server for AC 800M n.n\Files
3BSE036342R4101 171
Save Application and Configuration Data Section 4 Upgrading SB 2.1/2 to SV 4.1
Asset Optimizer. Use the following backup procedure to save Asset Optimizer
information:
Asset Optimizer is referred to as Asset Optimization after the upgrade.
1. Asset Monitoring:
Asset Monitoring directories will be found on the Asset Optimization Server
node.
a. If Running Time Check Asset Monitors are being used in the system, save
the Running Time Check Asset Monitor data directory
(DeviceRunTimeMSLogicStore). Assuming the default directory was
selected during Asset Optimizer installation, the Running Time Check
Asset Monitor data directory is located in:
...\Program Files\ABB Industrial IT\Optimize IT\Asset
Optimization\AssetMonitorEnvironment\Bin
Save the entire DeviceRunTimeMSLogicStore data directory. The Bin directory
contains the DeviceRunTimeMSLogicStore data directory as well as individual
files named DeviceRunTimeMSLogicStore.dll and
DeviceRunTimeMSLogicStore.pdb. If the individual files are saved instead of the
entire data directory, the configuration will be lost.
b. If XY Profile Deviation Asset Monitors are being used in the system, save
the XY Profile Deviation Asset Monitor data directory
(XY_Reference_Profiles). Assuming the default directory was selected
during Asset Optimization installation, the XY_Reference_Profiles
directory is located in:
...\Program Files\ABB Industrial IT\Optimize IT\Asset
Optimization\AssetMonitorEnvironment\Bin
172 3BSE036342R4101
Section 4 Upgrading SB 2.1/2 to SV 4.1 Save Application and Configuration Data
3BSE036342R4101 173
Save Application and Configuration Data Section 4 Upgrading SB 2.1/2 to SV 4.1
Where:
<server_name>\<app_server> is the combination of the MRO
Server Name and the MRO Application Server Name fields from the
Maximo Equipment ID aspect. These fields are configured in the Aspect
System Structure in the Maximo Equipment ID aspect. The resultant path
to the customized MxDef files will look like, for example:
...\Program Files\ABB Industrial IT\Optimize IT\Asset
Optimization\ABBAO\Services\MOM\MxDefs\Maximo5\MxServer
This allows for customization of MxDef files on the Maximo Server level
as well as on the Maximo Application Server level. Refer to Maximo
documentation for an explanation of Maximo Application Servers.
174 3BSE036342R4101
Section 4 Upgrading SB 2.1/2 to SV 4.1 Save Application and Configuration Data
3BSE036342R4101 175
Save Application and Configuration Data Section 4 Upgrading SB 2.1/2 to SV 4.1
8. After the HsBAR window closes, monitor the Progress in the Progress Status
dialog, and click Finish when the backup is completed.
If an exception message appears in the Progress Status dialog, there may be
inconsistencies between the log configurations in the Aspect System and the log
configurations in Oracle. Contact ABB Technical Support for assistance.
Exporting the SoftPoint Configuration and SoftPoint Data
This procedure exports all SoftPoint objects and aspects as well as related
aspects that may be attached to SoftPoints, such as property log configuration
aspects, and calculation aspects.
More detailed instructions for this procedure can be found in the section on using
the AFW export tool in Inform IT Information Manager SoftPoint Services
Configuration.
To export the SoftPoint configuration and data:
1. Create a folder where the configuration data will be exported.
2. Launch the AFW Export tool from the Windows task bar. Select:
Start > Programs > ABB Industrial IT > Inform IT > Softpoint Server
> Backup > Softpoint Afw Export.
3. Click Browse in the SCADA AFW Export Window to specify the export
location.
4. Use this dialog to select the export folder (created in Step 1), and specify a base
name for the export files. For each AFW file created as a result of this export, a
sequential number will be appended to this base name to make the name
unique.
5. Click Save when complete.
6. Click Start on the AFW Export tool to export the configuration data to the
specified location.
7. The AFW Export message bar will show the names of the objects and aspects
as they are being exported. When the export is finished, the message bar will
indicate Finished. Close the message box to exit.
8. Confirm that the export files have been created by checking the export folder.
176 3BSE036342R4101
Section 4 Upgrading SB 2.1/2 to SV 4.1 Save Application and Configuration Data
3BSE036342R4101 177
Save Application and Configuration Data Section 4 Upgrading SB 2.1/2 to SV 4.1
a. Use the File Path field to specify the full path and <file name>.xml where
the xml file will be stored as shown in Figure 46.
b. Click Save PPA Service Group Info.
178 3BSE036342R4101
Section 4 Upgrading SB 2.1/2 to SV 4.1 Document All Configuration Changes
3BSE036342R4101 179
Document All Configuration Changes Section 4 Upgrading SB 2.1/2 to SV 4.1
AC 400 Connect
Document the following for AC 400 Connect:
AC 400 Connect is referred to as 800xA for Advant Master after the upgrade.
Messenger Service
Document the following for the Messenger Service:
The Messenger Service is referred to as SMS and e-mail Messaging after the
upgrade.
Record all configuration information from the Alarm and Event Message Source
aspects. Record all information from the Destination tab of all Message Handler
aspects. Refer to the configuration worksheets for SMS and e-mail Messaging in
Industrial IT, 800xA - System, Configuration. Messenger related aspects and objects
in the User Structure must be recreated. This includes user groups that are message
destinations as well as Message Subscribers and Messenger devices. The linkages in
the restored Alarm and Event Message Source and Message Handler aspects must
be re-established.
180 3BSE036342R4101
Section 4 Upgrading SB 2.1/2 to SV 4.1 Verify Exported Application Data
Record all information from all Message Subscriber, Message Schedule, Email
Device, and Modem Device aspects found in User Structure\User Groups,
Everyone - IndustrialITUser, User Groups.
Information Manager
Document the following for Information Manager:
Information Manager is referred to as Information Management after the
upgrade.
1. Record all configuration data for ODA table aspects that have been added to
Object Types.
2. Record all configuration data for Calculation aspects that have been added to
Object Types, except for Calculations that have been added to SoftPoint Object
Types. Any Calculation aspects that are added to SoftPoint Object Types will
be restored along with their corresponding SoftPoint Object Types.
3. For numeric logs, record the configuration of the Archive Path specification for
all archive devices.
3BSE036342R4101 181
SV 4.1 Upgrade Activities Section 4 Upgrading SB 2.1/2 to SV 4.1
System Upgrade
Make sure the files created in Save Application and Configuration Data on page
160 have been verified using the procedure outlined in Verify Exported
Application Data on page 181.
For PROFIBUS and HART Device Integration: Do not include the system
extensions for these packages except the Fieldbus Builder PROFIBUS/HART
before importing the Control Structure. Refer to Fieldbus Builder
PROFIBUS/HART (PROFIBUS/HART Device Integration) on page 214.
The Microsoft Windows operating systems supported in SV 4.1 are:
Windows XP Professional with SP2.
Windows Server 2003 with SP1.
Windows 2000 Server with SP4.
The installation will fail unless all nodes being upgraded are reformatted and the
operating system installed, even if the existing operating system is compatible.
PC Clients with IM Desktop tools is not affected by this.
1. Reformat the drive.
182 3BSE036342R4101
Section 4 Upgrading SB 2.1/2 to SV 4.1 System Upgrade
2. Refer to Industrial IT, 800xA - System, Installation and install the new
operating system.
3. Apply updates and service packs approved by ABB (refer to Appendix A,
Third Party Software for SV 4.1) to existing operating system.
4. Refer to Industrial IT, 800xA - System, Installation and install third party
software approved by ABB (refer to Appendix A, Third Party Software for SV
4.1).
5. Refer to Industrial IT, 800xA - System, Installation and install all required
800xA System software.
Initialize the Batch database during installation of the Production Management -
Batch Management software.
6. Refer to Industrial IT, 800xA - System, Installation and install the license files
on the primary Aspect Server node.
7. Refer to the System Level Tasks section in Industrial IT, 800xA - System, Post
Installation to set up the 800xA System.
8. If using Information Management, refer to Industrial IT, 800xA - System, Post
Installation and perform all Information Management post installation steps.
The Oracle instance and history database must be created before restoring
application and configuration data and before performing the Service Group
restore.
a. Restore the Service Group configurations after successful creation of the
Oracle instance and after the node has been rebooted.
The post installation information for Information Management in Industrial IT,
800xA - System, Post Installation indicates that in some cases, the Upon
successful creation of Oracle Instance, create the History Database check box
can be disabled. When upgrading, never disable this check box.
9. Refer to Restore Application and Configuration Data on page 184 of this
instruction and perform all necessary steps.
10. Refer to Industrial IT, 800xA - System, Post Installation to perform any post
installation tasks that are not restored.
3BSE036342R4101 183
Restore Application and Configuration Data Section 4 Upgrading SB 2.1/2 to SV 4.1
184 3BSE036342R4101
Section 4 Upgrading SB 2.1/2 to SV 4.1 Restore Application and Configuration Data
4. Click Retrieve Imported PPA Nodes and Services and browse to the .xml file
created by the Service Backup.
5. Select the file, then click Open. This displays a list of node names that existed
in the system when you created the Service Backup as shown in Figure 49.
3BSE036342R4101 185
Restore Application and Configuration Data Section 4 Upgrading SB 2.1/2 to SV 4.1
a. For all nodes whose names have not changed from the original system to
the current system, the imported node names will be added to the
Matched column in the list of current node names.
b. For any node whose name has changed, select the Imported node name
that corresponds to the current node name. This is illustrated by Eng66 in
Figure 49.
6. Select and drag the imported node name into the Matched column for the node
(in this case Eng66). This activates Restore PPA Service Group Info.
Before clicking Restore PPA Service Group Info, make sure the Basic History
and Calculation Server check boxes in the Service list are selected.
186 3BSE036342R4101
Section 4 Upgrading SB 2.1/2 to SV 4.1 Restore Application and Configuration Data
Importing the Same Object into More than One Structure. There are some
important considerations to be taken into account when importing the same object
into more than one structure.
The Import/Export tool will present a question dialog when importing an object
that already exists. This will, for example, occur when the object is already
imported into the Control Structure, then imported into another structure, such as
the Functional Structure or Location Structure. The questions must be answered
as follows; otherwise the import will fail.
Always answer Yes in the Import/Export tool Replace Existing Object dialog
when it asks if it should overwrite an object with the one from the import file
(refer to Figure 50).
Always answer No in the Import Export tool Replace Existing Aspect dialog
when it asks if it should overwrite an aspect with the one from the import file
(refer to Figure 51).
3BSE036342R4101 187
Restore Application and Configuration Data Section 4 Upgrading SB 2.1/2 to SV 4.1
error messages. If the import is not interrupted due to any errors, the data will be
recovered.
The new version allows only one object icon per object. If the AFW files contain
more than one object icon per object, only one is imported. For the remaining object
icons, a dialog appears stating that it cannot be restored. The only accepted answer
is yes. The result can be that the wrong icon gets imported.
Ignore the following information messages that are displayed in the message
window of the Import/Export tool when importing an AFW file:
2003-10-25 13:32:31 (Info) Removed obsolete propagated
aspect 'Control Module' from instance 'cmt2_1'.
2003-10-25 13:32:31 (Info) Removed obsolete propagated
aspect 'Single Control Module' from instance 'SM1'.
2003-10-25 13:32:31 (Info) Removed obsolete propagated
aspect 'Function Block' from instance 'fb2'.
Error messages that are displayed in the message window of the Import/Export tool
when importing an AFW file indicate that there are two or more formal instances
with conflicting (identical) GUIDs in the file. All conflicting objects must be
removed from the AFW file before a new attempt to import the file can be
attempted. If help is needed to properly delete conflicting objects, contact ABB
Technical Support for assistance.
Examples of these types of error messages are:
2004-01-22 10:54:49 (Error) Illegal structure in
composite object type. Insert of object 'ConflictInst2'
failed.
(Info) Object ID = {85BC991D-85DF-478F-9A09-C6F71D9B50CD}.
(Error) Transaction Error (-1967453578):
'E_AFW_OT_ILLEGAL_COMPOSITE_TYPE_STRUCTURE(0x8ABB0A76)
Illegal structure in composite object type.
-or-
2004-02-09 14:14:09 (Error) Illegal structure in
composite object type. Insert of object 'ConflictInst1'
failed.
188 3BSE036342R4101
Section 4 Upgrading SB 2.1/2 to SV 4.1 Restore Application and Configuration Data
Import Procedure (General). Use the following procedure to import exported data
to SV 4.1 structures:
Stop PAS before importing the aspect objects that were previously exported.
Use the Import/Export tool to import data to the structures in the order they are
listed in Table 9.
3BSE036342R4101 189
Restore Application and Configuration Data Section 4 Upgrading SB 2.1/2 to SV 4.1
Import
Structure Procedure
Order
1 Aspect System Import AFW files containing custom aspect categories and aspects.
Do not forget custom structure categories.
Information Management:
Postpone the importing of Information Management AFW files for
this structure until after the Information Manager application data
has been restored (refer to Information Management on page
222).
Engineering Studio:
Filter the AFW files prior to import:
Exclude Aspect Data Sheet aspect system objects.
Exclude Aspect Data aspect type objects.
Exclude Aspect Information, Designations, Document
Designations, Document File Information, Document Information,
Document Revision Information, and Document Status aspect
categories.
When importing objects having aspects of the Categories mentioned
above, use the following settings in the Import/Export tool:
Select the Use Advanced Selection check box in the import
dialog.
Click Aspect Types and deselect the Aspect Data check box.
190 3BSE036342R4101
Section 4 Upgrading SB 2.1/2 to SV 4.1 Restore Application and Configuration Data
Import
Structure Procedure
Order
1 (cont) Aspect System Asset Optimization Asset Monitoring:
(cont) 1. Use the import/export utility to import all project specific Asset
Monitor, Aspect Category objects in the Aspect System
Structure\Asset Monitoring, Aspect System\Asset Monitors,
Aspect Type>
2. Use the import/export utility to import all Asset Monitor Startup
Parameters which provide global configuration values for some
asset monitors (for example Running Time Check Asset Monitor)
in Aspect System Structure\Asset Monitoring, Aspect
System\Asset Monitors, Aspect Type\Running Time Check,
Aspect Category.
3. Use the import/export utility to import Process Portal B
Provider information in the Aspect System Structure\Asset
Monitoring, Aspect System\Process Portal B Provider, Aspect
Type\>Process Portal B Provider, Aspect Category
Asset Optimization Maximo Connectivity:
Use the import/export utility to import the CMMS System
identification information (Provider Properties) in the Aspect
System Structure\Maximo Connectivity, Aspect System\Maximo
Equipment ID, Aspect Type\Maximo Equipment ID, Aspect
Category
SMS and e-mail Messaging:
1. Use the import/export utility to import the Modem Device
parameters in the Aspect System Structure\Messenger Modem
Device, Aspect System\Modem Device, Aspect Type\Modem
Device, Aspect Category.
2. Use the import/export utility to import the Email Device
parameters in the Aspect System Structure\Messenger Email
Device, Aspect System\Email Device, Aspect Type\Email Device,
Aspect Category.
3BSE036342R4101 191
Restore Application and Configuration Data Section 4 Upgrading SB 2.1/2 to SV 4.1
Import
Structure Procedure
Order
2 Library Import:
Added configurations, for example Alarm and Event templates.
Trend and History Log Templates.
ODA Database objects.
Redo filtering for all Alarm and Event Lists and Alarm and Event
templates.
3 Graphical Import the AFW files.
4 Object Type Import AFW files for any acquired libraries that are not delivered with
Control Builder M. Follow any further instructions provided by the
vendor of the acquired libraries.
If there are any dependencies to the Plant or ePlant example object
types, import them first. The import files are found in:
...\Program Files\ABB Industrial IT\Operate IT\Process Portal
A\importExamples.
For detailed information on how to import the Object Type, refer to the
Readme file in the same directory.
Import standard faceplates that were modified, and added faceplates.
192 3BSE036342R4101
Section 4 Upgrading SB 2.1/2 to SV 4.1 Restore Application and Configuration Data
Import
Structure Procedure
Order
4 (cont) Object Type Import user-defined libraries.
(cont) Use the Import/Export tool to import the previously created
library.
The import order should be according to the dependencies
between the user defined libraries.
Import additional graphics.
Use the Import/Export tool to import the additional graphic
elements and/or special aspects added to the Control Builder M
standard libraries.
Import application-defined types.
Use the Import/Export tool to import the previously created
application files.
Import any user made Hardware types.
Use the Import/Export tool to import the previously created
Hardware types files.
Fieldbus Builder PROFIBUS/HART:
Import Fieldbus Builder PROFIBUS/HART Object Types, which
were exported as described in Table 8.
IMPORTANT: Do not overwrite already existing items. Click NO
to skip the import of these items.
3BSE036342R4101 193
Restore Application and Configuration Data Section 4 Upgrading SB 2.1/2 to SV 4.1
Import
Structure Procedure
Order
4 (cont) Object Type Make a consistency check on all user-defined Object Types:
(cont) 1. Go to the Object Type Structure.
2. Mark the Object Type Definition aspect on an object.
3. Select the Consistency tab as shown in the following figure.
194 3BSE036342R4101
Section 4 Upgrading SB 2.1/2 to SV 4.1 Restore Application and Configuration Data
Import
Structure Procedure
Order
5 Control Import user-defined projects.
Use the Import/Export tool to import the previously created
project files.
Import the Control Network object first.
NOTE: The library references need to be deleted before the
import in the Import/Export tool as shown in the following figure,
otherwise the import will fail.
3BSE036342R4101 195
Restore Application and Configuration Data Section 4 Upgrading SB 2.1/2 to SV 4.1
Import
Structure Procedure
Order
5 (cont) Control (cont) Information Management:
If, during export, the export of the Control Structure was split into
multiple files, import those files in the same order that they were
exported.
Do not import the Log Configuration aspect export file at this time.
This will be restored after the Information Management history
database is restored, as described in Information Management
on page 222.
Systems without Information Management:
Import log configurations.
800xA for Advant Master:
RTA boards should be added and configured prior to the import
so that the correct network and RTA Board objects are in place in
the Control Structure. After import, verify that controller objects
are inserted below the correct Network object. Refer to AC 400
Connect on page 180 under Document All Configuration
Changes.
6 Equipment Import the AFW files.
7 Procedure Import the AFW files.
8 Functional Import the entire structure. If there are any dependencies to the Plant
or ePlant example object types, import them first. The import files are
found in:
...\Program Files\ABB Industrial IT\Operate IT\Process Portal
A\importExamples.
For detailed information on how to import the Object Type, refer to the
Readme file in the same directory.
196 3BSE036342R4101
Section 4 Upgrading SB 2.1/2 to SV 4.1 Restore Application and Configuration Data
Import
Structure Procedure
Order
8 (cont) Functional (cont) Asset Optimization Asset Monitoring
Use the import/export utility to import all objects that contain the
Asset Optimizer Asset Monitoring, Maximo Connectivity, and
Messenger object types, for example Asset Monitor Data Source.
Do not import Asset Monitoring Server aspects into 800xA SV
4.1. The Aspect OPCCONDITIONSPROPERTIES is obsolete
and it can be deleted or excluded from the import.
If the imported objects containing Asset Monitor aspects were not
in the Control Structure then they must be inserted in the Control
Structure.
If the Asset Monitor aspects were not assigned to the default AO
Server then navigate to the AO Server Object\Asset Optimization
Server Aspect. Select the Asset Monitors tab and click AM
Assigned to other AO Srvs. Once the list is generated, select all
the Asset Monitors to be assigned to this AO server and use the
right-click menu to Assign Asset Monitors to this AO Srv.
9 Location Import the AFW files.
10 Workplace Import the AFW files.
11 Admin Recreate Security and Affinity.
12 User Recreate the configuration based on the previous documentation.
1. Create Users and User Groups in the Windows domain, if they are
not already defined.
2. For each User Group, check and correct its association to Windows
groups and its role settings.
3. Use the Configuration Wizard to add users to appropriate user
groups. For each user, use Plant Explorer and either configure the
profile aspects (graphics profile values, status viewer profile values,
and workplace profile values) or import them. Ensure that the aspects
are added to the right user.
3BSE036342R4101 197
Restore Application and Configuration Data Section 4 Upgrading SB 2.1/2 to SV 4.1
Import
Structure Procedure
Order
12 User (cont) Import the entire structure if that is how it was exported. In some cases
(cont) it may be necessary to import the following Asset Optimizer aspect
from their own AFW file.
Maximo Credential
Devices
Message Schedule
Message Subscriber
When importing these aspects, they must be manually placed on the
target User object.
13 Scheduling1 Import Job Descriptions and related action aspects.
NOTE:
1. If schedules were enabled when exported, the schedules will automatically resume operation when the Scheduling
Structure is imported. If schedules were disabled prior to export, enable them in order to resume operation.
198 3BSE036342R4101
Section 4 Upgrading SB 2.1/2 to SV 4.1 Restore Application and Configuration Data
3BSE036342R4101 199
Restore Application and Configuration Data Section 4 Upgrading SB 2.1/2 to SV 4.1
200 3BSE036342R4101
Section 4 Upgrading SB 2.1/2 to SV 4.1 Restore Application and Configuration Data
Before adjustments:
FileUnits
( Application
( Name 'Application_1'
Directory '' )
Library
( Name 'AlarmEventLib'
Directory 'Libraries:\' )
Library
( Name 'IconLib'
Directory 'Libraries:\' )
Library
( Name 'MyOwnLibrary'
Directory '..\..\MyOwnLibs\' )
ControlSystem
( Name 'Controller_1'
Directory '' ) )
After adjustments:
FileUnits
( Application
( Name 'Application_1'
Directory '' )
Library
( Name 'AlarmEventLib'
Directory 'Libraries:\' )
Library
( Name 'IconLib'
Directory 'Libraries:\' )
Library
( Name 'MyOwnLibrary'
Directory '' )
ControlSystem
( Name 'Controller_1'
Directory '' ) )
3. Start Control Builder M Professional from the desktop icon and choose:
Tools > Maintenance > Upgrade Project
a. Click OK, and browse to the *.prj file of the project to migrate. This will
upgrade the selected project.
3BSE036342R4101 201
Restore Application and Configuration Data Section 4 Upgrading SB 2.1/2 to SV 4.1
202 3BSE036342R4101
Section 4 Upgrading SB 2.1/2 to SV 4.1 Restore Application and Configuration Data
3BSE036342R4101 203
Restore Application and Configuration Data Section 4 Upgrading SB 2.1/2 to SV 4.1
204 3BSE036342R4101
Section 4 Upgrading SB 2.1/2 to SV 4.1 Restore Application and Configuration Data
Issue Description/Solution
Shared Graphical Elements In SB 2.1/2, shared graphical elements were placed directly
under Libraries in the Object Type Structure. These elements did
not belong to any library, but were accessible from all libraries.
These elements are, in this version, copied to the new library
SupportLib. The new library is present, but all standard libraries
still use the old shared elements. Additionally, the old shared
elements are renamed to OBSOLETE OldName, where
OldName is the name of the corresponding element in the
previous version.
ABB does not recommend using the present version of
SupportLib, because the contents of SupportLib will be changed
in the next release and will not be compatible with the
application.
Redeploy Imported Graphics If it is not possible to view imported displays or composite
graphic or faceplate elements, and they have unresolved
references, redeploy the included elements.
3BSE036342R4101 205
Restore Application and Configuration Data Section 4 Upgrading SB 2.1/2 to SV 4.1
Issue Description/Solution
The Visual Basic resize code of Valid for users that have copied a template object from, for
the Display Element Reduced example, a Process Object Library, and are using its Display
Icon becomes corrupt after Element Reduced Icon.
deploy in Graphics Builder. Remove the source comments around the UserControl_Resize
method before deploying the Display Element Reduced Icon.
Edit the Display Element Reduced Icon, removing the
comments, and then deploy the Display Element Reduced Icon.
The source comments are:
$$ABB_BEGIN_USERCONTROL_RESIZE
---
$$ABB_END_USERCONTROL_RESIZE
NOTE: Delete only the comment lines. Do not delete the source
code between the comment lines.
System Library The SystemLib is split into two different libraries:
System: Includes firmware functions and data types that are
defined within firmware. This library is not version handled.
BasicLib: Includes the rest of the former SystemLib. This
library uses version handling.
Both libraries must always be inserted into the project.
Control Builder will display the Version Mismatch dialog when
downloading the project after upgrade to SV 4.x. Perform the
following so that the Cold Retain Values will not be lost.
1. If the Version Mismatch dialog indicates:
SystemLib not found
click Rename... and enter BasicLib.
2. The Version Mismatch dialog may also indicate several basic
data types; for example, ReallO, BoollO, etc. that are located
in the System library. Since the System library is automatically
connected to the applications in the project, it is not necessary to
rename the library. If this is the case, click Next mismatch.
206 3BSE036342R4101
Section 4 Upgrading SB 2.1/2 to SV 4.1 Restore Application and Configuration Data
Issue Description/Solution
AlarmEventLib The SimpleEventDetector (AlarmEventLib) is changed to be
based on GUID instead of name.
Normally, the Source Name of a SimpleEventDetector should be
equal to Object Name of its owner. If that is the case, the
changed behavior will not be noticeable.
A SimpleEventDetector might, however, be associated with
another object after upgrade if the two names are not equal.
There will be no problems if the naming recommendation was
observed (using the same name for source name and object). If
the naming recommendation was not observed, alter the
application so the naming will comply with the naming
recommendation.
Process Object Libraries This version contains enhanced versions (2.2/x) of the
ProcessObjBasicLib and ProcessObjExtLib libraries. These are
not fully compatible with the previous versions. The previous
versions (1.0/x) are included for upgrade reasons. Do not use
them for new applications.
3BSE036342R4101 207
Restore Application and Configuration Data Section 4 Upgrading SB 2.1/2 to SV 4.1
Issue Description/Solution
Communication Library The CommunicationLib is split into the following smaller libraries:
MMSCommLib
FFH1CommLib
SattBusCommLib
ModBusCommLib
COMLICommLib
S3964CommLib
ModemCommLib
They are fully compatible with the former CommunicationLib.
CommunicationLib (Version 1.0/0) is still included for upgrade
reasons, but will be removed in future versions.
The following steps are necessary when replacing the old library:
1. Open the project where CommunicationLib is still connected to
the applications/libraries.
2. Insert needed new communication libraries to the project, for
example MMSCommLib, if the MMS protocol is used.
3. Connect the inserted libraries to the applications/libraries in
the project.
4. Disconnect CommunicationLib from the applications/libraries.
All Function Blocks will automatically be replaced.
Perform the following additional steps for each instance of
CCToFF, FFToCC, CCToMMS, or MMSToCC in the
applications/libraries:
1. Connect the FFH1CommLib (CCToFF, FFT0CC) or
MMSCommLib (CCToMMS, MMSToCC).
2. Mark the instance in Project Explorer.
3. Right-click and select to replace the Type.
4. Disconnect the CommunicationLib.
5. Select the Type from the new library.
6. Save and close.
208 3BSE036342R4101
Section 4 Upgrading SB 2.1/2 to SV 4.1 Restore Application and Configuration Data
Issue Description/Solution
Communication Library (cont) Control Builder will display the Version Mismatch dialog when
downloading the project after upgrade to SV 4.x. Perform the
following so that the Cold Retain Values will not be lost.
If the Version Mismatch dialog indicates:
CommunicationLib not found
click Rename... and enter the name of the relevant
communication library.
Serial Library SerialLib has been renamed to SerialCommLib.
Perform the following steps:
1. Open the project where SerialLib is still connected to the
applications/libraries.
2. Insert the SerialCommLib library to the project.
3. Connect the SerialCommLib to the applications/libraries in the
project.
4. Disconnect SerialLib from the applications/libraries. All
Function Blocks will automatically be replaced.
Library Dependencies Circular dependencies between libraries is no longer permitted.
The use of circular dependencies causes compilation errors.
RealIO Status The status component of the RealIO data type has changed data
type from dInt to dWord. In most cases this change will be taken
care of automatically, but if the status component has been
referred to directly in application code, a manual change is
necessary. This also applies for any use in Process Graphics, for
example if the status has been used in a faceplate.
Hardware Definition Files Version 4.1 requires that used HWD-files are of a newer syntax
Syntax version. The new version (3.3) of the GSD Import Tool has an
option to transform older HWD-files to the syntax that is required
by Version 4.1. This is only applicable for user-made HWD-files,
all standard HWD-files are updated. For detailed information,
refer to the Update HWD-files online help topic in the GSD
Import Tool.
3BSE036342R4101 209
Restore Application and Configuration Data Section 4 Upgrading SB 2.1/2 to SV 4.1
Issue Description/Solution
User-Defined Hardware The behavior has been undefined when the 1131-variable has a
Definition Files when 1131- very large value (larger than the maximum value possible to write
application variables of type dInt on a specific hardware unit). The very large value has really
and dWord are written from the been truncated, a hardware unit receiving 8-bit data has received
application to I/O-channels. the 8 lowest bits in the dInt or dWord.
The behavior is redefined as follows:
The hardware unit will be written with the largest, which is
different depending on hardware, possible value if 1131-
variable has a very large positive value.
The hardware unit will be written with the largest, which is
different depending on hardware, negative value if 1131-
variable has a very large negative value.
S900 I/O Parameter Name S900 I/O parameter names have been changed, which will result
Changes in loss of configuration data when upgrading a project containing
S900 I/O modules.
Error messages will be given during upgrade of the project if it
has not been converted.
210 3BSE036342R4101
Section 4 Upgrading SB 2.1/2 to SV 4.1 Restore Application and Configuration Data
Issue Description/Solution
S900 I/O Parameter Name Before migrating a project, repeat the following steps for all *.con
Changes (cont) files in the project that may contain S900 I/O modules.
1. Locate:
CBMconS900Conv.exe
on in the System3\tools\ABB\CBMconS900Conv directory on the
800xA System Installation DVD 1.
2. Open a command prompt window and change to the directory
where the CBMconS900Conv.exe is present:
...\> CD Z:\tools\abb\CBMconS900Conv\
3. Enter CBMconS900Conv [path to project
folder]ControllerName.con. For example:
CBMconS900Conv ...\...Projects\MyProj\MyController.con.
4. Press Enter. The MyController.con file will be renamed to
MyController.bak, and a new converted MyController.con file will
be generated. A message that the file was converted
successfully will appear.
5. Repeat Step 3 and Step 4 for all *.con files that includes S900
I/O modules.
Metafiles Locations These files are not relocated on safe media during the source
code migration, which means that the image selectors will fail if
the paths to the image files are specified relative to the project
directory. If this happens; copy the files so that the used relative
path points to the files, or change the used path to explicitly point
to the image files (for example
...\ImageDirectory\ImageName.wmf).
Windows metafiles (wmf) or enhanced metafiles (emf) that are
used by image selectors in Control Module Diagrams are locally
stored on disk and need to be present on all Control Builder M
nodes. Only those with wmf and emf images included in Control
Module diagrams will be affected.
3BSE036342R4101 211
Restore Application and Configuration Data Section 4 Upgrading SB 2.1/2 to SV 4.1
Issue Description/Solution
CI840 CI840 must be upgraded to firmware Version 3.0/0 or later. The
CI840 firmware for upgrades will be located in the System1
directory on the 800xA System Installation DVD 1.
DP820 Scaling DP820 frequency scaling has changed. The default setting in SB
2.1/2 was 0.0 to 1500000.0 Hz. It should now be -15.00000.0 to
+1500000.0 Hz. DP820 will show the wrong frequency value if
this change is not done.
Internal MMS Communication The behavior of internal communication between two
between applications residing in applications in the same controller has changed.
the same controller. This kind of communication is now asynchronous; all data may
no longer always be received in the same scan.
The SV 4.1 version of When upgrading SB 2.1/2 applications that have instances of the
ControlFuzzyLib is not fully control module types FuzzyController1CC, FuzzyController2CC,
compatible with the SB 2.1/2 or FuzzyController3CC from ControlFuzzyLib, these instances
version of ControlFuzzyLib will be inconsistent after the migration. To restore the instances
1.0/0. Error messages may be perform the following:
displayed when importing a SB 1. Save instance specific aspects (log aspects, graphics, etc.) if
2.1/2 project to SV 4.1 if it there are any on the instances. Execute this by dragging and
contains objects from dropping to the Import/Export tool.
ControlFuzzyLib. If this
2. Open the project in Control Builder. Set all inconsistent
happens, the project
instances as not aspect objects via the context menu: Properties
inconsistencies must be
> Aspect Object. This will make the instance disappear in the
repaired manually.
Object Type Structure/Control Structure.
3. Set the instances to aspect objects again.
4. Import the instance specific aspects from Step 1.
212 3BSE036342R4101
Section 4 Upgrading SB 2.1/2 to SV 4.1 Restore Application and Configuration Data
Issue Description/Solution
There are more stringent Change the duplicate instance names so that they are unique.
naming rules in 800xA System
Version 4.x than in previous
system versions. Therefore, in
Control Builder SV 4.x, the
instance names for variables,
function blocks, control
modules, etc. must be unique
within the object where the
instance is declared; for
example, a program or control
module.
If the instance names are not
unique, when upgrading a
project from an older system
version and then trying to
download it, there may be error
messages during compilation,
such as:
The variable name
<name> is not unique
OPC Server for AC 800M. The memory setting for OPC Server needs to be set in
the Setup Wizard. This is the value recorded under Control IT for AC 800M Settings
on page 160. This OPC Data Source Definition aspect is set to its default during the
upgrade and must be checked that it is properly configured.
1. Manually restore the previously saved systemsetup.sys file to the following
location:
ABB Industrial IT Data\Control IT Data\OPC Server for
AC 800M 4.1
2. Restore the configuration files (*.cfg) to the Files folder in the same location.
3BSE036342R4101 213
Restore Application and Configuration Data Section 4 Upgrading SB 2.1/2 to SV 4.1
214 3BSE036342R4101
Section 4 Upgrading SB 2.1/2 to SV 4.1 Restore Application and Configuration Data
800xA for Advant Master and 800xA for SafeGuard RTA Board Files. To restore
800xA for Advant Master and 800xA for SafeGuard RTA Board files:
AC 400 Connect is referred to as 800xA for Advant Master after the upgrade.
Safeguard Connect is referred to as 800xA for SafeGuard after the upgrade.
1. Restore the files:
DATHR1.CD
DATHR2.CD
DATHR3.CD
to the folder
...\Program Files\ABB Industrial IT\OperateIT\
AC 400 Connect\AdvantBase\Data\RTA\Init\
to the Connectivity where they belong.
2. Replace them if asked to do so.
3. Restart the RTA Board.
3BSE036342R4101 215
Restore Application and Configuration Data Section 4 Upgrading SB 2.1/2 to SV 4.1
1. Asset Monitoring:
After upgrading, the Running Time Check Asset Monitor is referred to the
Runtime Asset Monitor.
Asset Monitoring directories must be restored on the Asset Optimization Server
node.
a. If Runtime Asset Monitors are being used in the system, restore the
Runtime Asset Monitor data directory (DeviceRunTimeMSLogicStore).
Assuming the default directory was selected during Asset Optimization
installation, the Runtime Asset Monitor data directory must be restored to
the following directory:
...\Program Files\ABB Industrial IT\Optimize IT\Asset
Optimization\AssetMonitorEnvironment\Bin
Restore the entire DeviceRunTimeMSLogicStore data directory. The Bin
directory contains the DeviceRunTimeMSLogicStore data directory as well as
individual files named DeviceRunTimeMSLogicStore.dll and
DeviceRunTimeMSLogicStore.pdb. If the individual files are restored instead of
the entire data directory, the configuration will be lost.
The saved data contains the Runtime Asset Monitor data present at the time of the
save. Use the Runtime Asset Monitor faceplate to reset the asset monitors by
adding the lost time to their accumulated run time or with some known values
based on other records. Ignore any alarms occurring during the backup.
After restoring, open each file with notepad and save each file as a UNICODE file
by setting the encoding to UNICODE.
b. If XY Profile Deviation Asset Monitors are being used in the system,
restore the XY Profile Deviation Asset Monitor data directory
(XY_Reference_Profiles). Assuming the default directory was selected
216 3BSE036342R4101
Section 4 Upgrading SB 2.1/2 to SV 4.1 Restore Application and Configuration Data
3BSE036342R4101 217
Restore Application and Configuration Data Section 4 Upgrading SB 2.1/2 to SV 4.1
218 3BSE036342R4101
Section 4 Upgrading SB 2.1/2 to SV 4.1 Restore Application and Configuration Data
Type Change
Asset Monitor in the instance that has Object This Asset Monitor will be set to inherit from
Type. Object Type's Asset Monitor.
Corresponding Asset Monitor exists in the object
type and the
Object Type Definition Aspect > Aspect
Control Tab > Copy to all instances
check box is selected. Then for each of the 4 configuration tabs (Asset
Monitor, Conditions, Asset Parameters, Input
Records) if the configuration matches the
configuration in Object Type, inheritance values
will be set to TRUE, else to FALSE.
Asset Monitor is on the Object Type. This Asset Monitor will be set to inherit from the
Asset Monitor category.
Asset Monitor is on the instance of the generic
object.
Asset Monitor in the instance that has Object
Type.
Corresponding Asset Monitor does not exist in Then for each of the 4 configuration tabs (Asset
the Object Type. Monitor, Conditions, Asset Parameters, and
Asset Monitor in the instance that has Object Input Records) the configuration inheritance
Type. values will be set to their pre 4.1 values.
Corresponding Asset Monitor exists in the object
type and the
Object Type Definition Aspect > Aspect
Control Tab > Copy to all instances
check box NOT selected.
3BSE036342R4101 219
Restore Application and Configuration Data Section 4 Upgrading SB 2.1/2 to SV 4.1
220 3BSE036342R4101
Section 4 Upgrading SB 2.1/2 to SV 4.1 Restore Application and Configuration Data
3BSE036342R4101 221
Restore Application and Configuration Data Section 4 Upgrading SB 2.1/2 to SV 4.1
Information Management. This section describes how to restore all application and
configuration data that was exported, copied to a safe media, or documented prior to
installing the new software. Perform the following procedures:
Information Manager is referred to as Information Management after the
upgrade.
Stopping System Services on page 222.
Importing the SoftPoint Data on page 223.
Restoring the History Database on page 225.
Import Archives Created on the Information Manager 3.5/2 System to the New
System Version 4.1 Database on page 229.
Restoring Other Information Management Related Files on page 229.
Restore Service Group Configuration on page 184.
Verify that the system has been created on the Aspect Server, all nodes have been
added to the system, and all system extensions have been added before starting to
restore data.
Stopping System Services
Use PAS to stop the system services:
The path to PAS now changed to Control Panel > Administrative Tools.
This procedure can also be performed by using the pasgui command in the Run
dialog (Start > Run).
222 3BSE036342R4101
Section 4 Upgrading SB 2.1/2 to SV 4.1 Restore Application and Configuration Data
3BSE036342R4101 223
Restore Application and Configuration Data Section 4 Upgrading SB 2.1/2 to SV 4.1
time, and must be imported in the same order in which they were created by the
Export tool (starting with 001).
Skip errors caused by limiter aspects.
If the export file contains an aspect named Softpoint Configuration
Aspect, delete that aspect from the export file before importing.
This import creates a SoftPoint virtual control network for each Information
Management server where the SoftPoint server runs.
2. When the import is finished, run AdsFinalizeMigration tool (located in
Program Files\ABB Industrial IT\OperateIT\Common\bin\System\Utilities).
3. Perform the following set up for SoftPoints.
These procedures are described in detail in the section on SoftPoints in Industrial
IT, 800xA - Information Management, Configuration.
For each node where SoftPoint Services is installed:
a. Create a SoftPoint service group object and service provider object.
b. Configure a virtual control network in the Control structure for each
SoftPoint server.
The SoftPoint Generic Control Network object is created automatically (refer to
Industrial IT, 800xA - System, Post Installation.) Perform the steps on adding the
Adapter Data Source Definition aspect and connecting the network to the
applicable OPCDA_Connector service provider.
c. Configure a Source Definition aspect for each network. This is required to
deploy the SoftPoints on their respective nodes.
d. Integrate the SoftPoint alarm and event messages into the 800xA System
message service.
e. Deploy the restored SoftPoint configuration. The Deploy function is not
enabled unless a change in the SoftPoint configuration has occurred since
the last deployment. Therefore you must simulate a change by making and
applying a small change and then reversing the change in order to enable
the deploy function.
4. Use the 800xA Import Export tool to restore:
ODA Table Definition aspects.
224 3BSE036342R4101
Section 4 Upgrading SB 2.1/2 to SV 4.1 Restore Application and Configuration Data
Calculation aspects.
Log Configuration aspects
5. Using the Calculation Status Viewer aspect in Calculation Server, manually
assign Calculations to Service Groups if previously in Service objects.
Restoring the History Database
To restore a backed up History database:
1. Use PAS to stop all Information Management processes.
a. Use the Windows Taskbar to select:
Start > Programs > Administrative Tools > PAS
b. Click Stop All in the PAS dialog. This will stop the Inform IT History
Service Provider.
If it is suspected that the Inform IT History Service Provider has not stopped, it
can be stopped now by selecting the Inform IT History Service Provider for this
node in the Service Structure, selecting the Configuration tab on the Service
Provider Definition aspect, deselecting Enabled, and clicking Apply.
2. Ensure that no third party applications access the Oracle database during the
restore operation.
3. Select:
Start > All Programs > ABB Industrial IT 800xA > Information
Mgmt > History > Backup and Restore.
3BSE036342R4101 225
Restore Application and Configuration Data Section 4 Upgrading SB 2.1/2 to SV 4.1
226 3BSE036342R4101
Section 4 Upgrading SB 2.1/2 to SV 4.1 Restore Application and Configuration Data
6. Specify the location of the backup files in the Path of IM historian backup:
field (Figure 56).
If you need to specify new mount points for file-based logs and/or a new Oracle
tablespace definition file, click Browse.
7. Click Next. The HsBAR Output Window appears.
8. Enable the Automatically close upon completion check box.
9. Monitor the progress in the Progress Status area of the IM Historian
Backup/Restore Utility window. Ignore the error messages indicating errors
deleting aspect.
Shortly after the message indicating the import is complete, the database
conversion tool will run automatically. Feedback will be provided in the
HsBAR window.
Shortly after the message indicating the database conversion is complete, the
history synchronization tool will run automatically. Again, feedback will be
provided in the HsBAR window.
If the restore operation fails with Oracle Error Message 1652 - Unable to
extend tmp segment in tablespace tmp - it may be due to a large OPC
message log which exceeds the tmp tablespace capacity during the restore
operation.
Use the Database Instance Maintenance wizard to increase the tmp tablespace.
The default size is 300 megabytes. Increase the tablespace in 300-megabyte
increments and retry the restore operation until it runs successfully.
10. Click Finish when a message stating the execution is complete is displayed as
shown in Figure 57.
3BSE036342R4101 227
Restore Application and Configuration Data Section 4 Upgrading SB 2.1/2 to SV 4.1
If the Progress Status dialog has warning messages with possible solutions as
indicated in Figure 58, read the possible solutions carefully, then click Finish
and proceed with the solution that best fits your problem. Refer to the
Information Management Release Notes for further guidelines.
11. Start all processes under PAS supervision. This will start the Inform IT History
Service Provider.
If it is suspected that the Inform IT History Service Provider has not started, it can
be started now by selecting the Inform IT History Service Provider for this node
in the Service Structure, selecting the Configuration tab on the Service Provider
Definition aspect, selecting Enabled, and clicking Apply.
12. Start the Basic History Service Provider for this node:
a. Select the Basic History Service Provider object for the Information
Management node in the Service Structure in the Plant Explorer.
b. Select the Service Provider Definition aspect.
c. Select the Configuration tab.
d. Disable the Enabled option.
e. Click Apply.
228 3BSE036342R4101
Section 4 Upgrading SB 2.1/2 to SV 4.1 Restore Application and Configuration Data
3BSE036342R4101 229
Restore Application and Configuration Data Section 4 Upgrading SB 2.1/2 to SV 4.1
DataDirect: Restore custom text files for object, object type, and attribute
menus used on the DataDirect windows.
Check Archive Path Specifications: If the disk configuration has
changed from the previous system to the new system (i.e. letter
designations for disks have changed: C,D,E, and so on), check the archive
device configurations to make sure the Archive Path specification points to
the correct disk drive and directory, Figure 59.
Reset the Last Archive Time for all Archive Groups: After the upgrade,
the timed archive schedules that were formerly defined via the Archive
Group objects, will now be defined via the combination of Archive Group
definitions and Scheduling Job Description objects with Archive Action
aspects. Before these jobs can run, the last archive time must be reset for
all archive groups. A prompt will appear, as shown in Figure 60, when an
Archive Action aspect is opened in the Scheduling Structure.
230 3BSE036342R4101
Section 4 Upgrading SB 2.1/2 to SV 4.1 Restore Application and Configuration Data
The last archive time for an archive group can be reset in the Archive
Action aspect as shown in Figure 61.
-or-
Go to the Archive Group object in the Node Administration structure,
select the group, right-click and choose Reset Last Archive Time from
the context menu as shown in Figure 62.
In either case, use the dialog to set the last archive time to a time in the
past.
Figure 61. Resetting Last Archive Time Via the Archive Action Aspect
Figure 62. Resetting last Archive Time Via an Archive Group Definition
3BSE036342R4101 231
Restore Application and Configuration Data Section 4 Upgrading SB 2.1/2 to SV 4.1
232 3BSE036342R4101
Section 4 Upgrading SB 2.1/2 to SV 4.1 Restore Application and Configuration Data
800xA for Advant Master. To recreate configuration changes for 800xA for Advant
Master:
AC 400 Connect is referred to as 800xA for Advant Master after the upgrade.
SMS and e-mail Messaging. To recreate configuration changes for SMS and e-
mail Messaging:
The Messenger Service is referred to as SMS and e-mail Messaging after the
upgrade.
3BSE036342R4101 233
System Backup Section 4 Upgrading SB 2.1/2 to SV 4.1
System Backup
Make a complete backup of the upgraded system as described in System Backup on
page 159.
234 3BSE036342R4101
Appendix A Third Party Software for SV 4.1
Introduction
Some third party software may offer a web browser popup blocker. Do not use
them with the thin client portions of the integrated applications (specifically
Asset Optimization), since these applications open child window browsers to
display application data for the user. If a popup blocker is being used on a web
browser, disable it during use of these web based applications.
This appendix details the third party software that has been evaluated for use with
the 800xA System. The 800xA System has been found to be fully compatible and
functional with this software as of the date of this document. Refer to ABB
Solutions Bank for an up to date, comprehensive listing of all software that has been
evaluated including service patches and hot fixes released following the 800xA
System release. The complete list of software can be found at:
http://solutionsbank.us.abb.com/
Table 12 lists the Microsoft Windows operating system software. Table 13 lists the
other Microsoft software programs that have been determined as needed to properly
run and interface with 800xA System software. The tables also detail the service
packs and hot fixes that the 800xA System software has been found to be
compatible with.
Table 14 lists other third party programs that may be needed with the various 800xA
System software packages.
Some of the software is included with the 800xA installation DVDs. In all cases, the
affect of any software should be determined for each installation particularly where
there may be interfaces external to the 800xA System.
Unless otherwise indicated, Microsoft service packs and hot fixes are not
included with 800xA System software. They can be downloaded from:
www.microsoft.com
3BSE036342R4101 235
Introduction Appendix A Third Party Software for SV 4.1
Service
Software Version Hot Fixes How Supplied
Pack
Windows Server 1.0 SP1 MS05-033 MS05-027 Vendor supplied.
2003
MS05-032 MS05-026
MS05-031 MS05-025
Windows 2000 1.0 SP4 MS05-032 MS04-044 Vendor supplied.
Server
MS05-031 MS04-043
MS05-030 MS04-041
MS05-027 MS04-037
MS05-026 MS04-036
MS05-025 MS04-032
MS05-024 MS04-031
MS05-019 MS04-022
MS05-018 MS04-020
MS05-017 MS04-019
MS05-016 MS04-016
MS05-015 MS04-014
MS05-013 MS04-012
MS05-012 MS04-011
MS05-011 MS03-049
MS05-010 MS03-043
MS05-009 MS03-042
MS05-004 MS03-041
MS05-003 MS03-023
MS04-045
Q8252371 KB817478 Included with 800xA.
236 3BSE036342R4101
Appendix A Third Party Software for SV 4.1 Introduction
Service
Software Version Hot Fixes How Supplied
Pack
Windows XP 1.0 SP2 MS05-033 MS05-015 Vendor supplied.
Professional
MS05-032 MS05-013
MS05-031 MS05-012
MS05-027 MS05-011
MS05-026 MS05-009
MS05-025 MS05-007
MS05-020 MS05-001
MS05-020 MS04-044
MS05-019 MS04-043
MS05-018 MS04-041
MS05-016
NOTE:
1. Q825237 was replaced by KB835517. Either one can be used.
Service
Software Version Hot Fixes How Supplied
Pack
.Net Framework 1.0 SP3 MS05-004 Software and Service Packs
Included with 800xA. Hot fixes
.Net Framework 1.1 SP1 MS05-004
are vendor supplied.
DirectX 9.0c Installed by Windows XP
Professional SP2 and
Windows Server 2003 SP1.
Included with 800xA and
manually installed for
Windows 2000 Server.
3BSE036342R4101 237
Introduction Appendix A Third Party Software for SV 4.1
Service
Software Version Hot Fixes How Supplied
Pack
Internet Explorer 6.0 SP1 MS04-028 Internet Explorer 6.0 with SP1
Installed as part of Windows
XP Professional SP2 and
Windows Server 2003.
Included with 800xA and
manually installed for
Windows 2000 Server.
Internet Information Server 5.0 Part of Windows XP and
Windows 2000 Server.
Internet Information Server 6.0 Part of Windows Server 2003.
MDAC 2.8 MS04-003 Included with 800xA and
manually installed for
Windows 2000 Server.
2.8 SP1 Included and installed with
Windows XP Professional SP2
2.8 SP2 Included and installed with
Windows Server 2003 SP1
MSDE - 2000 SP3a Q823490 Included and installed when
MS03-031 Engineering Studio is
selected; otherwise, vendor
supplied. Q823490 included
with 800xA. MS03-031 vendor
supplied.
MSMQ 5.0.720 Part of Windows Operating
Systems.
MSSOAP1 DLL Included and installed with
Version 800xA
1.2.814.0
MSXML (Windows 2000 3.0 SP4 Included with 800xA.
Server SP4)
MSXML (Windows XP 3.0 SP5 Vendor supplied.
Professional SP2)
238 3BSE036342R4101
Appendix A Third Party Software for SV 4.1 Introduction
Service
Software Version Hot Fixes How Supplied
Pack
MSXML (Windows Server 3.0 SP7 Vendor supplied.
2003 SP1)
MSXML 4.0 SP2 Included with 800xA.
Office 2003 - Excel 1.0 SP1 MS05-023 Vendor supplied.
Office 2003 - Word MS05-012
KB841532
Office 2003 - FrontPage 1.0 MS05-023
MS05-012
KB841532
Office XP - Excel 2002 1.0 SP3 MS05-023 Vendor supplied.
MS05-012
Office XP - Word 2002 MS05-005
MS04-027
SNMP driver Automatically installed with
Windows Operating Systems;
however, it must be enabled.
The Windows CD will be
required for Windows 2000
Server.
WMI-SNMP Provider 1.50.1085.5 Included and installed with
800xA.
SQL Server 2000 - SP3a MS03-031 Included with 800xA
Personal
SQL Server 2000 -
Standard
SQL Server 2000 -
Standard Client
3BSE036342R4101 239
Introduction Appendix A Third Party Software for SV 4.1
Service
Software Version Hot Fixes How Supplied
Pack
Visual BASIC Professional 6.0 SP6 Visual BASIC Professional
software purchased separately
using 800xA price list or from
another vendor. SP6 included
with 800xA.
Visual BASIC Runtime 6.0.97.86 Included and installed with
DLL 800xA.
Visual C7 7.00.9466.0
Runtime DLL
Windows Installer 2.0 Part of Windows 2000 Server
and Windows Server 2003
Operating Systems. Will only
exist on a node if it is an
upgrade.
Windows Installer 3.0 Part of Windows XP
Professional SP2.
Windows Installer 3.1 Part of Windows Server 2003
SP1.
240 3BSE036342R4101
Appendix A Third Party Software for SV 4.1 Introduction
OPC DA Auto 2.02 Merge Module 5.00 2.00.2.20 Included and installed by 800xA.
OPC Core Components 2.00 2.00.2.20
Oracle 9i Included with 800xA.
8 Client 2
SAP/PM 4.7 Purchased separately from SAP,
AG if SAP/PM Integration
functionality is selected.
Sentinel System Driver (Dongle) 5.41.0 Included and installed with 800xA.
3BSE036342R4101 241
Introduction Appendix A Third Party Software for SV 4.1
242 3BSE036342R4101
Appendix B Warning and Error Messages
The warning and error messages that can be generated by the 800xA backup/restore
function are described in the following topics. Suggested solutions are also
provided.
3BSE036342R4101 243
UnplacedObjects.afw Appendix B Warning and Error Messages
Solution
Install all system extensions on the node from where the backup is taken. Make sure
that the correct version of the system extension is installed.
UnplacedObjects.afw
Example
[Warning] c:\PPABackup\MyBackup\UnplacedObjects.afw created
Reason
During backup process, the backup tool goes through all structures, if there is an
object that doesn't exist in any structure, it will be placed in UnplacedObjects.afw
and write a warning in the backup log, therefore, UnplacedObjects.afw is used for
all objects which miss the structure.
Solution
Check if there is any important object in UnplacedObjects.afw. If there is an
important object in UnplacedObjects.afw, your backup is considered to be not
complete. In such case, investigate what kind of object it is, and try to repair the
system. One solution could be to add the object into the structure it should belong
to. Take another backup.
244 3BSE036342R4101
Appendix B Warning and Error MessagesSystem Extension xxxx with ID Guid` is not Installed on
Reason
When the backup was taken, the FSD cache was set too low. All data has NOT been
backed up. There should be warnings in the System Event list about overflow in the
Fsd cache.
Solution
Increase the Fsd Cache size (for all nodes).
3BSE036342R4101 245
Graphic Aspect = xxx Cannot be Imported. Appendix B Warning and Error Messages
Reason
History or System Message data was backed up using the backup/restore function.
This functionality is not yet supported.
Solution
History and System Message data has to be saved manually, as described in
reference [2] Release Notes. Create a new backup, without including History or
System Message data.
246 3BSE036342R4101
Appendix B Warning and Error Messages Aspect Category is Missing
Reason
The system was inconsistent at backup time (there were more than one aspect of
category 'Name' on an object). The backup does not react on this, but restore will
fail. The restore part will be fixed in a later release (it will be possible to import such
an object, but a warning will be granted).
Solution
Open the file (in this case Control Structure28.afw) with the old import/export
utility (<Install path>\bin\AfwImportExport_obsolete.exe), search for the aspect
category and manually remove one of the two aspect categories.
3BSE036342R4101 247
Unknown Transaction Error Appendix B Warning and Error Messages
Reason
If this is the only error message, there is probably a problem with some windows
resources.
Solution
Check your windows resources.
Example 2
Mon Jun 28 08:37:08 2004: Loading C:\BACKUP\Full Backup; 2004-06-23; 10-
39\Aspect System Structure0.afw ...
Mon Jun 28 08:37:09 2004: Aspect 'Batch Management Operation' on object 'Batch
Management Documents' failed to unserialize itself.
Mon Jun 28 08:37:09 2004: ObjectId: {814786F8-E6CC-44B0-9A2A-
1787FADDFE6F}
Mon Jun 28 08:37:09 2004: AspectId: {2CE41978-DE94-44AC-9D38-
B216FBA93C3A}
Reason
It is not possible for the Restore function to restore the aspect data.
Solution
No solution available.
248 3BSE036342R4101
INDEX
Numerics Product upgrade
800xA for Harmony SB 2.1/2 to SV 4.1 159
Adding optional Harmony connectivity server Project
nodes 131 SB 2.1/2 to SV 4.1 161
Harmony alarm and event OPC provider 129 Settings
Harmony aspect directory SB 2.1/2 to SV 4.1 160
synchronization 131 Adding optional Harmony connectivity server
800xA for Melody nodes 131
Preparation Advant master
SV 4.0 to SV 4.1 29 Post upgrade
SV 3.1/3 to SV 4.0 128
A SV 4.0 to SV 4.1 57
AC 400 connect Preparation
Document configuration changes SV 3.1/2 to SV 4.0 84
SB 2.1/2 to SV 4.1 180 SV 4.0 to SV 4.1 28
Recreate configuration changes Asset optimization
SB 2.1/2 to SV 4.1 233 Copying files to safe media
AC 400 connect RTA board files SB 2.1/2 to SV 4.1 172
Copying files to safe media Post upgrade
SB 2.1/2 to SV 4.0 171 SV 3.1/2 to SV 4.1 133
Restoring files from safe media SV 4.0 to SV 4.1 63
SB 2.1/2 to SV 4.1 215 Preparation
AC 800M SV 3.1/2 to SV 4.1 86
Considerations SV 4.0 to SV 4.1 31
SB 2.1/2 to SV 4.1 157 Restoring files from safe media
Importing application data SB 2.1/2 to SV 4.1 216
SB 2.1/2 to SV 4.1 187
License upgrade B
SB 2.1/2 to SV 4.1 158 Basic history service
Post upgrade Post upgrade
SV 3.1/2 to SV 4.1 118 SV 3.1/3 to SV 4.0 153
Preparation Basic history service data
SV 3.1/2 to SV 4.1 81, 121 Preparation
SV 4.0 to SV 4.1 27, 53 SV 3.1/2 to SV 4.1 101
SV 4.0 to SV 4.1 38
3BSE036342R4101 249
Index
250 3BSE036342R4101
Index
3BSE036342R4101 251
Index
252 3BSE036342R4101
Index
3BSE036342R4101 253
Index
254 3BSE036342R4101
Index
3BSE036342R4101 255
Index
256 3BSE036342R4101
Index
3BSE036342R4101 257
Index
Batch management 92 T
Calculation service 99 Third party software 235
Central Licensing System 80 Microsoft 237
Engineering studio 86 Operating system 236
External alarm service group 81 Other 240
FOUNDATION Fieldbus 82 Tip icon 13
Harmony connect 85
Information management 94 U
PC, network and software monitoring 89 Upgrade activities
PLC connect 85 SB 2.1/2 to SV 4.1 157, 182
PROFIBUS/HART 84 SV 3.1/2 to SV 4.1 79, 104
Scheduler service 99 Upgrade order
SMS and e-mail messaging 90 SB 2.1/2 to SV 4.1 155
System message and alarm and event
services 80
V
System message service data 100
Verify exported data
SV 4.0 to SV 4.1 26
SB 2.1/2 to SV 4.1 181
800xA for Melody 29
AC 800M 27, 53
Advant master 28 W
Asset optimization 31 Warning and error messages 243
Basic history service data 38 Warning icon 13
Batch management 36 Windows services, stopping 40, 103
Calculation service 38
Engineering studio 30
Harmony connect 29
Information management 38
PC, network and software monitoring 34
PLC connect 29
PROFIBUS/HART 28
RTA board 28
SafeGuard 28
Scheduler service 37
System restore
SV 3.1/2 to SV 4.1 107
System upgrade
SV 3.1/2 to SV 4.1 105
258 3BSE036342R4101
3BSE036342R4101. Printed in Sweden June 2005
Copyright 2003-2005 by ABB. All Rights Reserved
Registered Trademark of ABB.
Trademark of ABB.
http://www.abb.com