administration and security 800xa system... · 2011. 11. 25. · section 2 - 800xa license handling...

IndustrialIT800xA - SystemSystem Version 4.1

Administration and Security

NOTICEThe information in this document is subject to change without notice and should not beconstrued as a commitment by ABB. ABB assumes no responsibility for any errors thatmay appear in this document.

In no event shall ABB be liable for direct, indirect, special, incidental or consequentialdamages of any nature or kind arising from the use of this document, nor shall ABB beliable 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 usedfor any unauthorized purpose.

The software or hardware described in this document is furnished under a license andmay 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 LowVoltage Directive 72/23/EEC.

Copyright © 2003 - 2005 by ABB. All rights reserved. Release: June 2005Document number: 3BSE037410R4101

TRADEMARKSAll rights to trademarks reside with their respective owners.

TABLE OF CONTENTS

Section 1 - GeneralIntended User...................................................................................................................15

Document Conventions ...................................................................................................16

Use of Warning, Caution, Information, and Tip Icons ....................................................17

Terminology.....................................................................................................................18

Related Documentation ...................................................................................................23

Section 2 - 800xA License HandlingLicensing Software ..........................................................................................................25

Software Keys..................................................................................................................25

Central Licensing Service System Extension..................................................................25

Enabling License Usage Monitoring Functionality .............................................25

License Expansion...........................................................................................................29

Section 3 - Security PlanningRisk Management............................................................................................................31

Physical Security .............................................................................................................32

Read the Manual ..................................................................................................32

Backup .............................................................................................................32

Destruction of Data Media and Computers..........................................................32

Computer Room ...................................................................................................32

UPS .............................................................................................................32

Cables .............................................................................................................32

Process Equipment ...............................................................................................33

Inventory Spare Parts ...........................................................................................33

Computer Security...........................................................................................................33

3BSE037410R4101 5

Table of Contents

Virus Check..........................................................................................................33

Services ............................................................................................................ 33

Firewall ............................................................................................................ 33

Servers ............................................................................................................ 33

Personnel Security........................................................................................................... 34

Assigning Permissions .........................................................................................34

Password Security ................................................................................................ 34

Root Accounts...................................................................................................... 34

User Accounts...................................................................................................... 34

Security Testing ...................................................................................................35

Contractors........................................................................................................... 35

Training Program ................................................................................................. 35

Section 4 - SecurityConcept ...........................................................................................................................37

800xA Security Description............................................................................................ 37

Users and Groups ............................................................................................................ 38

Adding Users ....................................................................................................... 38

Windows Workgroups.......................................................................................... 40

Windows User Groups in Domain Controller......................................................44

How to Change User Permissions........................................................................49

How to Restrict the User Interface.......................................................................91

How do I see... ................................................................................................... 100

Advanced Security Configuration ................................................................................. 106

The Access Evaluation Algorithm ..................................................................... 106

The Evaluation Search Order............................................................................. 107

Audit Logging.................................................................................................... 114

Audit Trail Configuration .................................................................................. 115

Security Audit Config ........................................................................................ 117

Windows Audit Function ................................................................................... 124

Critical Operation Authentication Support ........................................................ 129

Log Over .......................................................................................................... 136

Digital Signature ................................................................................................ 143

6 3BSE037410R4101

Table of Contents

Confirmed Write ................................................................................................156

Section 5 - Process SectioningSecurity Setting by Structuring in Plant Explorer .........................................................163

Setting the Security Definition Aspects in the Example ....................................165

Section 6 - Configuration of System ServicesUnique Naming of Service Groups ...............................................................................169

History ...........................................................................................................................169

History Source....................................................................................................169

Alarm and Event ............................................................................................................172

Alarm Services ...................................................................................................172

Redundant Services .......................................................................................................185

Configuration of Redundant Services ................................................................185

Redundant Aspect Servers .................................................................................186

Change from Redundant to Single Configuration..............................................186

Restart Redundant Configuration.......................................................................187

Recovering from Read-only Mode.....................................................................187

Section 7 - Import/ExportThe User Interface..............................................................................................191

How to use the Import/Export Tool....................................................................191

The Main Menu, Toolbar and Context Menus ...................................................196

Additional Information..................................................................................................229

Upgrading Files ..................................................................................................229

Dependencies .....................................................................................................229

Resolving Errors.................................................................................................230

Audit Trail ..........................................................................................................231

Precautions when Importing/Exporting Aspects................................................231

Section 8 - Backup and RestoreSV 4.1 Backup and Restore...........................................................................................233

Introduction ........................................................................................................233

3BSE037410R4101 73BSE037410R4101 7

Table of Contents

Precautionary Issues...................................................................................................... 236

Save Function-Specific Information ............................................................................. 237

FOUNDATION Fieldbus ................................................................................... 237

Asset Optimization ............................................................................................ 238

PC, Network and Software Monitoring ............................................................. 240

SMS and e-mail Messaging ............................................................................... 240

PLC Connect...................................................................................................... 242

800xA for Advant Master and Safeguard .......................................................... 243

Control IT for AC 800M.................................................................................... 244

800xA for Harmony........................................................................................... 245

Information Management .................................................................................. 249

Batch Management ............................................................................................ 253

System Message Service Data and Basic History Service Data ........................ 254

800xA for Melody ............................................................................................. 258

800xA System Backup.................................................................................................. 259

Requirements ..................................................................................................... 259

Procedure .......................................................................................................... 259

800xA System Restore .................................................................................................. 260

Requirements ..................................................................................................... 260

Procedure .......................................................................................................... 260

Recover Function-Specific Information........................................................................ 263



PC, Network and Software Monitoring ............................................................. 266

SMS and e-mail Messaging ............................................................................... 266

PLC Connect...................................................................................................... 266

800xA for Advant Master and Safeguard .......................................................... 268

Control IT for AC 800M.................................................................................... 268

800xA for Harmony........................................................................................... 269



System Message Service Data and Basic History Service Data ........................ 278

8 3BSE037410R4101

Table of Contents

800xA for Melody..............................................................................................280

How to make a Full Backup ..........................................................................................280

Backup Object ....................................................................................................281

Backup Service...................................................................................................283

Scheduling a Backup..........................................................................................284

How to make a Restore..................................................................................................285

Preparing the Restoring Process.........................................................................285

Finding the Backup Files ...................................................................................287

Upgrade Older Versions .....................................................................................290

System Configuration Version ...........................................................................291

Warning and Error Messages.........................................................................................293

Failed to serialize aspect ....................................................................................293

ASO object class xxxx did not implement IAfwAspectSystemObject. Failed to create ASO. Forgot to register dll? ..............................................................293

UnplacedObjects.afw .........................................................................................294

The system cannot find the path specified .........................................................294

System Extension ´xxxx´ with id ´Guid` is not installed on this node...............295

Timeout by External Service ..............................................................................295

Graphic aspect = xxx cannot be imported..........................................................296

Too many aspects of category ............................................................................297

Aspect category is missing.................................................................................297

Unknown transaction error.................................................................................298

Section 9 - System CheckSystem Check List .........................................................................................................301

System Status Viewer ....................................................................................................303

Interface ...........................................................................................................303

System Status Viewer Configuration .................................................................304

Section 10 - Single Node ReplacementIntroduction ...................................................................................................................307

Recovery Paths ..............................................................................................................307

Reinstall Like New.............................................................................................307

3BSE037410R4101 93BSE037410R4101 9

Table of Contents

Reinstall and Restore ......................................................................................... 308

Recover Node..................................................................................................... 309

Disk Image .................................................................................................................... 309

Combined Node Types .................................................................................................. 309

Aspect Server ................................................................................................................ 310

Connectivity Servers ..................................................................................................... 311

AC 800M .......................................................................................................... 312


HART and PROFIBUS ...................................................................................... 329

800xA for Advant Master .................................................................................. 339

800xA for Harmony........................................................................................... 341

800xA for Melody ............................................................................................. 342

800xA for MOD 300.......................................................................................... 344

800xA for SafeGuard......................................................................................... 346

800xA for DCI ................................................................................................... 348

Application Servers and Software................................................................................. 350

Common Application Software ......................................................................... 350




Manufacturing Management.............................................................................. 363

Section 11 - Operating System UpdateWindows and 800xA System Updates .......................................................................... 367

Section 12 - Scheduling ReportsPrerequisites .................................................................................................................. 369

Scheduling..................................................................................................................... 369

Creating Service Group/Service Provider Objects ............................................ 369

Scheduling Reports via the Application Scheduler ........................................... 374

Section 13 - Configuration WizardConfiguration Wizard.................................................................................................... 385

10 3BSE037410R4101

Table of Contents

General ...........................................................................................................385

System Software User Settings ..........................................................................387

Create System.....................................................................................................390

Connect Node.....................................................................................................396

System Administration.......................................................................................397

Start Server .........................................................................................................425

Stop Server .........................................................................................................427

Restore System...................................................................................................429

Maintenance .......................................................................................................430

Applog ...........................................................................................................435

Disconnect Client ...............................................................................................438

Appendix A - Default Security Settings for Process Objects .441

Appendix B - Additions in Windows added by 800xARecommended Windows Configuration........................................................................443

Appendix C - System Alarm and Event MessagesSystem Alarm Message Descriptions ............................................................................445

System Events for Data Access Functions ....................................................................448

OPC DA Client - AdvDsOPCHandler ...............................................................448

OPC DA Client - AdvDsOPCServerAdapter .....................................................449

Upload - AfwUploadServer ...............................................................................449

Property Transfer - AfwPropertyTransfer ..........................................................450

Appendix D - Security ExamplesDefault Security Setting of the Admin Structure...........................................................451

The Default Security Setting of a System Object..........................................................451

Security Setting on an Aspect Object Basis ..................................................................456

Different settings of Structure in Authority Range ............................................458

Appendix E - Secured Server Configuration ....................................461

3BSE037410R4101 113BSE037410R4101 11

Table of Contents

Appendix F - Security Checklists and Fault SearchSecurity Checklists........................................................................................................ 465

Fault Search of 800xA Security .................................................................................... 466

Fault - Configuration Wizard only shows System Software Icon...................... 466

Fault - Permission granted for modify ............................................................... 467

Fault - Permission not granted for modify......................................................... 467

Fault - Permission not granted for OPC Write................................................... 468

Fault - The default permission does not apply to the wanted behavior ............. 469

Appendix G - Troubleshooting in 800xA WorkgroupsProblem with Hostname Lookup .................................................................................. 471

Fail to add Client or Server to a 800xA System ................................................ 472

Log Over does not work .................................................................................... 473

Invalid Account encountered during System Software User Settings ............... 476

Appendix H - Diagnostics Collection ToolIntroduction ................................................................................................................... 479

Terminology .................................................................................................................. 479

Supported Diagnostics Information ................................................................... 480

800xA System Products..................................................................................... 480

Microsoft Related Information .......................................................................... 481

Grouping Plug-ins ......................................................................................................... 481

Help and Information .................................................................................................... 482

Quick Start .................................................................................................................... 482

The Collecting Diagnostics Information Dialog ........................................................... 486

Open Manifest.................................................................................................... 487

Viewing Diagnostics Data.................................................................................. 487

Node Panel ......................................................................................................... 488

Collection Panel ................................................................................................. 489

Collection Part Panel.......................................................................................... 490

Cabinet File ................................................................................................................... 496

DCT Configuration ....................................................................................................... 497

12 3BSE037410R4101

Table of Contents

Configuration of ABB Result Folder .................................................................497

Configuration of Specific Plug-in Data Using IITConfig.xml...........................498

Configuration of Command Files for Diagnostics Collection ...........................501

DCT Configuration Settings...............................................................................503

ABB Node Interrogator Service Settings ...........................................................507

Node Master Configuration................................................................................507

Functional description ...................................................................................................508

800xA System Related Functions ......................................................................508

Batch Management.............................................................................................508

Control Builder M Diagnostics Data..................................................................509

OPC Server for AC 800M Diagnostics Data......................................................511

Custom Event Logs ............................................................................................511

800xA for Harmony ...........................................................................................512

License Information ...........................................................................................512

PLC Connect and SoftPoint Server ....................................................................512

PPA Diagnostics Data ........................................................................................513

Windows Related Functions ..........................................................................................514

DLL List ...........................................................................................................514

Dr. Watson..........................................................................................................515

Dump Registry Data...........................................................................................515

Handle List .........................................................................................................516

Installed Software Version Information .............................................................516

Process Information List ....................................................................................517

Service Information............................................................................................518

SQL Diagnostic ..................................................................................................518

System Event Logs.............................................................................................519

System Information ............................................................................................520

Task Manager .....................................................................................................521

User Dump .........................................................................................................521

3BSE037410R4101 133BSE037410R4101 13

Table of Contents

Appendix I - Basic Computer MonitoringIntroduction ................................................................................................................... 523

Overview ....................................................................................................................... 523

Alarm State ........................................................................................................ 524

Normal State ...................................................................................................... 525

PNSM System Status Viewer Aspect ................................................................ 525

Installation..................................................................................................................... 526

Configuration ................................................................................................................ 527

Basic Computer Monitoring Configuration Tool............................................... 527

Specifying the Computer Node to Monitor ....................................................... 528

Specifying the Hard Drives to Monitor.............................................................. 529

Modifying Alarm Limits.................................................................................... 529

Adding or Removing 800xA System Computer Nodes .................................... 531

Manually Adding Computer Nodes................................................................... 532

IT Assets and IT Device Library................................................................................... 533

Basic Computer Asset........................................................................................ 533

IT General Properties Aspect............................................................................. 534

Basic Computer Alarm Device .......................................................................... 534

INDEX ........................................................................................................................ 535

14 3BSE037410R4101

Section 1 General

This instruction describes IndustrialIT 800xA functions to administrate and set up security for your system.

The instruction describes for example:

• license handling (Section 2, 800xA License Handling)

• user handling and permissions (Section 4, Security)

• how to move applications (Section 7, Import/Export)

• how to make a complete backup and restore of an 800xA System (Section 8, Backup and Restore)

• how to check the status of the system (Section 9, System Check)

• security updates (Section 11, Operating System Update)

• description of the Configuration Wizard (Section 13, Configuration Wizard).

Intended UserThis instruction is intended for system administrators. As a system administrator you should have a thorough knowledge of using and maintaining Windows software and hardware. In general, Microsoft Windows functions are not described in this instruction.

The Start menu paths are taken from installations on Windows XP and Windows 2003 Server. The look of the Start menu will differ slightly on Windows 2000 installations.

Note that you must have Windows Administrator privileges to perform most tasks in this instruction.

3BSE037410R4101 15

Document Conventions Section 1 General

Document ConventionsThe 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.

• 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

16 3BSE037410R4101

Section 1 General Use of Warning, Caution, Information, and Tip Icons

Use of Warning, Caution, Information, and Tip IconsThis publication includes Warning, Caution, and Information where appropriate to point out safety related or other important information. It also includes Tip to point out useful hints to the reader. The corresponding symbols should be interpreted as follows:

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.

Electrical warning icon indicates the presence of a hazard which could result in electrical shock.

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.

Tip icon indicates advice on, for example, how to design your project or how to use a certain function

3BSE037410R4101 17

Terminology Section 1 General

TerminologyThe following is a list of terms associated with the IndustrialIT 800xA, System, Administration and Security instruction that you should be familiar with. The list contains terms and abbreviations that are unique to ABB or have a usage or definition that is different from standard industry usage.

Term/Acronym Description

Aspect An aspect is a description of some properties of a real world entity. The properties described could be mechanical layout, how the object is controlled, a live video image, name of the object etc.

Aspect Category A specialization of an aspect type. For example, the aspect type Graphic Display includes the categories Overview, Group and Object Display.

Aspect Object Type An Aspect Object type defines certain characteristics that are shared between several Aspect Object instances, such as a basic set of common aspects. This makes it possible to create and efficiently re-use standardized solutions to frequently recurring problems. For example, rather than building an Aspect Object from scratch for every valve in a plant, you can define a set of valve types, and then create all valve objects as instances of these types.

Aspect Objects A computer representation of a real world entity like a pump, a valve, an order or a virtual object like a service. This computer representation is implemented by the 800xA System. An Aspect Object works like an information container for it’s aspects.

Aspect Server A server that runs the central functions of the Aspect Object architecture, such as Aspect Directory, Structure and Name Server, Cross Referencing, File Set Distribution, etc.

Aspect System A software system, which implements one or several aspect types by providing one or several aspect system objects.

18 3BSE037410R4101

Section 1 General Terminology

Client Client is a part of a software that subscribes data from a server.

Client/Server Network A client/server network is used for communication between servers, and between workplaces and servers.

Composite Aspect Object Type

A composite Aspect Object type describes a set of Aspect Objects organized in a structure, with a parent object and one or several child objects. The children in a composite object type are called formal instances, because they inherit from object types defined elsewhere in the Object Type Structure, but they are not actual instances. When a composite object is instantiated actual instances are created for these child objects.

Connectivity Server A server that provides access to controllers and other sources for real-time data, historical data, and alarm and event data. A Connectivity Server runs services related to OPC/DA, OPC/AE, OPC/HDA.

Faceplate A faceplate is an aspect that provides a graphical representation of a certain aspect object, with presentation of certain properties related to the object, and mechanism for operator interaction such as on/off, increase/decrease, etc. Aspect Object types often include several faceplate aspects, providing different presentation and interaction possibilities.

Graphic Display A graphic display is an aspect that provides a visual presentation. It consists of static graphics representing for example tanks, pipes etc., and graphic elements that present dynamic information. Graphic displays are often used to present the state of a process or a part of a process, but are useful in any context where dynamic graphical information is needed.

IndustrialIT ABB’s vision for enterprise automation.

IndustrialIT 800xA System

A computer system that implements the IndustrialIT

vision.


3BSE037410R4101 19


Node A computer communicating on a network e.g. the Internet, Plant, Control or IO network. Each node typically has a unique node address with a format depending on the network it is connected to.

OPC/DA An application programming interface defined by the standardization group OPC Foundation. The standard defines how to access large amounts of real-time data between applications. The OPC standard interface is used between automation/control applications, field systems/devices and business/office application.

OCS Integration Package

OCS Integration components, up-loader, supporting aspect systems (e.g for the configuration), and graphical elements, faceplates, Aspect Object Types, etc., bundled together to provide the integration of a certain type of devices into the IndustrialIT 800xA System.

Permission A permission groups a set of operations that require the same authority. For each operation defined for an aspect, the aspect category specifies the permission needed to use that interface.

Plant Explorer An application that is used to create, delete and organize Aspect Objects and Aspects within the 800xA System. The plant explorer organizes the Aspect Objects in structures according to functionality, location etc. You can also use it to browse and search the structures of the plant.

Process Object A process concept/equipment e.g. valve, motor, conveyor or tank.

Property A data field on an aspect of an Aspect Object that can be accessed through OPC using the standard Aspect Object reference syntax.

A data field on an ActiveX control accessible from the Visual Basic editor.


20 3BSE037410R4101

Section 1 General Terminology

Security Security controls a user’s authority to perform different operations on Aspect Objects, depending on several parameters:

• The user’s credentials, as provided by Windows

• The node where the user is logged in. This makes it possible to give a user different authority depending on where he/she is located, e.g. close to the process equipment, in a control room, or at home accessing the system through Internet.

• The object the user wants to perform the operation on.

Server A node that runs one or several Afw Services.It is the part of the software that supply data to a subscriber.

Service Provider A service provider is a Windows process that runs on a specified server node using the Industrial IT service account. A service provider implements a part of a service for the 800xA system. Service providers may be redundant and all service providers within the same service group implements the same function. A service provider is configured in the Service Structure.

Structure A structure is a hierarchical tree organization of Aspect Objects, comparable to Windows ExplorerTM.A structure is used to store and define a certain context of Aspect Objects. For example the functional structure defines how a function can be divided into sub functions, the location structure defines how different objects are located relative to each other and the control structure defines how functions are executed in applications. An Aspect Object can be located in several structures, for example both in a functional structure and in a location structure. Structures may be user defined.


3BSE037410R4101 21


System Application A software component, based on the Aspect Object architecture, which provides functionality. System applications cooperate according to rules defined be the Aspect Object architecture. They are normally bundled into the system products or system extensions. System applications are implemented as client applications or services. To participate in Aspect Object operations, an application must present itself as one (or several) aspect system.

When there is no risk for confusion with user application, the term application may be used instead of system application.

System Extension A system Extension consists of one or more applications that are bundled as an extension to one or several existing System Product(s). A System extension can only be installed if (one of) the corresponding System Product(s) has been installed previously.

System Product A system product consists of applications bundled together with relevant parts of the 800xA System. Several System Products can be installed on the same physical node.

Uploader An upload is used to import a configuration from devices, to load and build a set of Aspect Objects from information present in the devices.

User application A configuration of software and hardware components that applies to a specific problem, e.g. a specific process control problem. A user application consists of a set of simple and composite Aspect Object instances, with parameter values and other configuration data for the aspects, e.g control logic, graphics, alarm and event specifications, reports etc.


22 3BSE037410R4101

Section 1 General Related Documentation

Related Documentation

The following is a listing of documentation related to the IndustrialIT 800xA, System, Administration and Security instruction.

View An Aspect can have several ways to be presented depending on the task performed, like viewing or configuration. Each presentation form is called a view.

Workplace 1. User interactive functions that are combined for a particular use, e.g, Operator Workplace.

2. A node that runs one or several workplace applications.

Table 1. Related Documentation

Category Title Description

Hardware IndustrialIT 800xA, Control and I/O, Basic Control Software, Introduction and Configuration.

Introduction to working with Control Builder M Professional in the Engineering Workplace and describes control module and function block based application programming strategy and design topics.

System Administration

IndustrialIT 800xA, System, Installation

Contains installation procedures for800xA System Version 4.0.

IndustrialIT 800xA, System, Post Installation Setup

Contains post installation procedures for800xA System Version 4.0.

IndustrialIT 800xA, System, Automation System Network,Design and Configuration

Describes how to set up networks and domains for the 800xA System.

IndustrialIT 800xA, System,Upgrade

Describes how to make an upgrade from an earlier version of 800xA to an 800xA System Version 4.0.


3BSE037410R4101 23

Related Documentation Section 1 General

Software IndustrialIT 800xA, System, Configuration

Contains an overview on engineering and configuration of the 800xA System in the context of an engineering project.

IndustrialIT 800xA, System, Operator Workplace, Configuration

Describes configuration of the Operator Workplace and Plant Explorer.

Options IndustrialIT 800xA, Information Management, Operation

Provides instructions for using Information Management (Excel Data Access) and Desktop Trends for data access. Also provides instructions for setting up, scheduling, and managing reports.

IndustrialIT 800xA, Information Management, Configuration

Describes configuration of Information Management applications.

IndustrialIT 800xA, Fieldbus, Foundation Fieldbus Device Integration, Configuration

Describes configuration of Foundation Fieldbus Device Integration applications.

IndustrialIT 800xA, Asset Optimization,Configuration

Describes configuration of Asset Optimization applications.

IndustrialIT 800xA, System,PLC Connect,Configuration

Describes how to engineer and maintain PLC Connect.

Table 1. Related Documentation (Continued)

Category Title Description

24 3BSE037410R4101

Section 2 800xA License Handling

Licensing SoftwareCertain 800xA System functions must be licensed before you can use them. These functions will not operate until the applicable licenses are installed. The software is licensed by relating a software key for each software feature with a unique machine identifier. Software keys are obtained from the ABB software license administration system. This section describes how to expand the licensing software and then use the licensing tool to apply for software keys as required by your system.

Software KeysBefore you can install the 800xA software keys you must have installed the licensing software on the designated license server and all license clients, and you must have applied for and received your software keys.

Central Licensing Service System ExtensionBelow follows a description on how to enable the License Usage Monitoring functionality.

Enabling License Usage Monitoring Functionality

To enable the License Usage Monitoring functionality, add the License Usage aspect needs to be added to the Root object in the Control Structure.

1. Open a Plant Explorer Workplace.

2. Use the Structure Selector to open the Control Structure.

3. Use the Object Browser to select the Root object.

3BSE037410R4101 25

Central Licensing Service System Extension Section 2 800xA License Handling

4. Right-click on the root object and select New Aspect from the context menu that appears.

5. The New Aspect dialog appears as shown in Figure 1.

Go to Central License Server > Central License Server > License Usage and click Create.

6. Select the newly created License Usage aspect in the Aspect List area.

7. The License Usage aspect appears in the Preview Area as shown in Figure 2. It shows a list of license features and the current usage.

Figure 1. New Aspect Dialog Box

26 3BSE037410R4101

Section 2 800xA License Handling Central Licensing Service System Extension

8. The License Usage aspect also maintains a set of General Properties in the

Root object. Select the General Properties in the Aspect List area to produce a view of the General Properties aspect in the Preview area as shown in Figure 3. These properties can be used to construct alarm expressions to monitor when licensed quantities are running low.

Figure 2. License Usage Aspect

3BSE037410R4101 27

Central Licensing Service System Extension Section 2 800xA License Handling

9. To monitor alarm usage, create an Alarm Expression aspect in the root object.

a. Use the Object Browser to select the Root object.

b. Right-click on the root object and select New Aspect from the context menu that appears.

Figure 3. General Properties Aspect

28 3BSE037410R4101

Section 2 800xA License Handling License Expansion

c. The New Aspect dialog appears. Go to Alarms and Events > Alarm Expression > Alarm Expression and click Create.

10. Select the newly created Alarm Expression aspect in the Aspect List area to produce the view in the Preview Area like the one shown in Figure 4.

11. Fill out the Alarm Expression aspect according to the requirements of the system and click Apply.

License ExpansionWhen you have ordered and received new software, you need to request new keys to expand the license.

Install your new software and follow the same steps as when requesting software keys for the first time. These steps are described below:

Figure 4. Alarm Expression Aspect

3BSE037410R4101 29

License Expansion Section 2 800xA License Handling

1. Obtain the machine ID of the computer that the Central Licensing System software is installed on, or going to be installed on.

2. Have the registration license numbers, found on the license certified form, available.

3. Complete the license key request form provided with the software. Follow the instructions found on this form. Be sure to enter your e-mail address on the form.

4. Fill in the form as necessary.

5. Send the registration to the ABB software license administrator using one of the methods described on the registration form.

6. Wait for the feature keys to be returned. The method by which the feature keys will be returned is selected on the registration form. The choices are Internet mail, postal mail or fax.

Internet mail is recommended. This way, the software keys will be returned as an attached .sla file. This is the format required by the license entry tool. In this case you simply need to detach the file and save it to a location on the license server where it may be accessed by the license entry tool.

If you choose to have the keys returned by mail, or fax, a mail address or fax number must be included on the form.

When you have received your new software keys, install them on the license server. For more information about Installing Licence Software, Requesting Software Keys and Installing Licenses on the Server, see the IndustrialIT 800xA System, Installation and IndustrialIT 800xA, System, Post Installation Setup instructions.

An alternative is to generate and complete a new request form using the license entry program. To do this:

• Select the License tab on the license entry tool.

• Click Request SWKey.

30 3BSE037410R4101

Section 3 Security Planning

When planning for the data security of a plant installation, take the total security into consideration. It is not enough to provide a strong firewall if there is free access to the control room in the plant.

Risk ManagementEstablish a detailed risk management program which covers the complete spectrum of risks. Make a crash plan. Make plans for how to recover and how to restore.

Create and implement testing procedures to ensure that the security plans act as planned. Inform your employees about the security plans for the plant and train them to act accordingly. Update the plan requirements once per year.

The risk management may include:

• Recovery from destruction of data information

• Destruction of data media and computers

• Crash planning

• External personnel - do consultants have to see passwords etc.

• Security backup of data

• Virus protection

• Password

• User identity

• Internet access

• Screen locking

3BSE037410R4101 31

Physical Security Section 3 Security Planning

Physical Security

Read the Manual

Before using the PC-equipment and installing the 800xA software products, read the PC’s manual and test that all installed software, like Windows, runs without problem.

Backup

Make a written backup plan for programs and data. Test this plan by making a backup and restoring the data.

Destruction of Data Media and Computers

When data media (disks, CD’s, or tapes) or computer hardware are discarded, there is a risk of information being stolen. Destroy all information on these items before trashing or recycling.

Computer Room

Minimize the number of people who have access to the facilities in order to prevent unauthorized access.

UPS

Use a UPS (Uninterrupted Power Supply) of sufficient capacity that will allow the 800xA System to be shutdown in an orderly manner during power outages. Place the UPS system on a regular maintenance schedule.

Cables

Make sure that it is not possible to tap data from the cables inside and outside the control room.

Protect computer facilities with a smoke/fire detection system. If feasible, connect all alarms to a manned guard station or fire station.

32 3BSE037410R4101

Section 3 Security Planning Computer Security

Process Equipment

If something is protected in the control room, the same physical or other protection shall be implemented against manual changes in the plant.

Inventory Spare Parts

Maintain an accurate inventory of all hardware and software. If the plant uses items that are critical and hard to acquire, consider stocking spare parts. Store them in a safe place.

Computer Security

Virus Check

Run a virus check daily or according to the security plan.

Update the virus protection frequently.

Services

Do not start up services that are not needed (like FTP and Telnet).

Firewall

Filtering:

• filter out unnecessary services at the router - only allow those services that are needed.

• if on the Internet, for example when using the Web Browser aspect,use a firewall.

Servers

Security configuration of the server is important. For details see Appendix E, Secured Server Configuration.

3BSE037410R4101 33

Personnel Security Section 3 Security Planning

Personnel Security

Assigning Permissions

Ensure that all personnel positions have been assigned security level designations.

Password Security

When establishing a reasonable password security scheme, consider the following:

• all accounts MUST have a password

• passwords must not be hard to remember. (If they are, there is a risk that they will be written down on a piece of paper and kept where they could be discovered.)

• passwords must not be easily guessed (for example do not use the name of a spouse, children or pet). Use a combination of letters and numbers instead

• passwords must not be written down

• do not leave papers on your desk containing your password or clues to your password

• passwords grow old and should be periodically changed

• accounts should be disabled when there are several bad logins in a row.

Root Accounts

When creating root accounts, take into consideration to:

• limit the number of users

• use a strong password, a combination of letters and numbers.

User Accounts

When you creating user accounts, take into consideration:

• accounts should be removed when an employee leaves the company or moves into a different role within the company.

• accounts should NOT be shared.

34 3BSE037410R4101

Section 3 Security Planning Personnel Security

Security Testing

To make the security as good as possible, always remember to:

• have the latest by ABB approved security patches installed on the system. See Section 11, Operating System Update.

• subscribe to security mailing lists/newsgroup.

Contractors

Ensure that all personnel, including contractors, have received appropriate clearances and training.

Training Program

Security Awareness and Training

• Establish an employee security awareness and training program

• Provide specialized security training.

3BSE037410R4101 35

Personnel Security Section 3 Security Planning

36 3BSE037410R4101

Section 4 Security

ConceptThe 800xA Security model is based on extensions to Windows security model. The extensions make it possible to set permissions for users or user groups on an 800xA System, a structure or part of a structure, or an Aspect ObjectTM.

The security setting can also be limited to a single node, or all nodes. This feature makes it possible to require an operation to be performed from a node within sight of the area it controls.

Related to the security is the usage settings are roles. Roles adapt the user interface for different types of users, i.e. user groups. Some operations require an application engineer or system engineer role to be performed.

However, having the correct role does not give the user the permission to perform the operation. The permission is completely controlled by the security configuration of the system.

800xA Security DescriptionSecurity and auditing in an 800xA System are set with the Security Definition aspects, which are added to Aspects Objects.

Note that there is a difference between role and permission. A role defines what you can see while permission defines what you can do.

As an administrator you have all permission because the security is turned off. By default a user does not have all roles and some structures, configuration tabs etc., are hidden.

3BSE037410R4101 37

Users and Groups Section 4 Security

The security is set by changing the Authority Range, Permissions (related to User Identity/Group and Node) and Search Option of a Security Definition aspect. By using these settings, the desired security level for your plant is defined.

The Audit function is setup more or less in the same way as security. Audit logging will allow the administrator to track security related events - for example attempts to access secured objects etc.

Users and Groups

Adding Users

The Users icon in the Configuration Wizard activates the User Administration dialog box.

1. Open the Configuration Wizard (Start > All Programs > ABB Industrial IT 800xA > System > Configuration Wizard).

2. Select System Administration and click Next.

3. Select the system in which you want to configure users to and click Next. See Figure 5.

Make sure there is a valid and current Windows backup of your domain server(s).

If you are running the Domain Server on a Windows 2003 Server, you must add the user that should be able to add other users to the PPA system to the Windows group Pre-Windows 2000 Compatible Access.

38 3BSE037410R4101

Section 4 Security Users and Groups

4. Select Users, see Figure 5. Now the User Configuration dialog box is displayed.

The top window shows the IndustrialIT 800xA System users. Users can be added and deleted. To delete a user select the user in the top window and click Delete User. An easy way to move all groups in the Not member of text field to the Member text field, is to click the Reset User button.

To add a Windows user to an IndustrialIT 800xA System group follow the steps:

1. Click the Add Windows Accounts... button.

Figure 5. User Configuration Dialog Box

You have to be both System Engineer and Application Engineer to delete a user.

3BSE037410R4101 39

Windows Workgroups Section 4 Security

2. The next dialog box (Figure 6) shows the Windows users of the domain that is selected in the drop-down menu. Select the Windows users you want to add to the IndustrialIT 800xA System users and click Add.

3. Repeat until all Windows users you want to add are added to the Add Names area then click OK.

4. In the User Configuration dialog box, Figure 5, it is possible to select the IndustrialIT 800xA groups of which a Windows user must be member. Select Windows user in the top window and use the Remove and Add buttons to move IndustrialIT 800xA groups to the Member of field.

Windows Workgroups

For a small system a workgroup can be an alternative to using a Windows domain.

A “small system” configuration is intended as a low cost entry point for small applications. The Aspect Server and Connectivity Server functionality reside in the same server, and Windows Professional is used in all servers where possible.

Figure 6. Assign Windows Account Dialog Box

40 3BSE037410R4101

Section 4 Security Windows Workgroups

The maximum system size for this configuration is limited by Microsoft licensing rules to 9 PC nodes in total.

A “small system” can be implemented either as a domain with a separate domain server, or as a workgroup, in which case a domain server is not needed. When implemented as a workgroup, the maximum system size for this configuration is decreased due to Microsoft licensing rules.

Preparation and Configuration

Below follows a short description of needed preparation and an instruction on how to configure the System Software User Settings during installation of the Process Portal software in a Windows workgroup environment.

5. As local administrator, setup all machines as members of a workgroup.

a. From the Start menu select: Start > My Computer.

b. Select Properties from the context menu.

c. Select the Computer Name tab and click the Change button.

d. Type the computer name in the Computer name area, see .

e. Mark the Workgroup radio button in the Member of area and give the workgroup a name, see Figure 7.

f. Click OK.

For troubleshooting workgroups see Troubleshooting in 800xA Workgroups.

3BSE037410R4101 41

Windows Workgroups Section 4 Security

6. Restart all machines.

7. Log in as local administrator and install the Process Portal software on all the machines, which are members of the workgroup.

8. When the installation has reached the System Software User Settings dialog box, configure it according to Figure 8. Use the local machine name as domain name. The IndustrialITAdmin, IndustrialITUser groups and a Service Account will be created.

Figure 7. Computer Name Changes dialog Box

42 3BSE037410R4101

Section 4 Security Windows Workgroups

9. Add users and user groups in Windows, according to the requirements of the

system but make sure that the set of users and user groups included passwords (empty passwords are not allowed) are identical on every node in the workgroup. For recommended user groups see How to Restrict the User Interface on page 91.

Figure 8. Configuration Wizard - System Software User Settings dialog box

3BSE037410R4101 43

Windows User Groups in Domain Controller Section 4 Security

Windows User Groups in Domain Controller

Before creating 800xA users and user groups, create a domain that contains all workstations on the 800xA network.

There are two scenarios when creating user groups:

• The account that you are logged onto when running the Configuration Wizard has permission to add user groups in the domain. The wizard will create the groups.

• The account that you are logged onto when running the Configuration Wizard has NO permission to add user groups in the domain.

User Groups Setup in the Domain Server

If the installer is not a Windows Domain Administrator, the IndustrialITAdmin and IndustrialITUser groups must be created manually in the Windows domain before any 800xA software is installed by a Windows Domain Administrator.

Use the Administrator’s Tools to make a folder and install the users in Windows as shown below (to do this you have to be a domain administrator):

1. Select Start > Control Panel > Administrative Tools > Active Directory Users and Computers.

In the last case the groups must be set up manually in the domain server before you install the 800xA System.Contact the domain administrator.

44 3BSE037410R4101

Section 4 Security Windows User Groups in Domain Controller

2. Select the domain root object. Open the context menu and select New > Group.

3. A new dialog box opens (see Figure 10). In this dialog input, the user group name.

Figure 9. Creation of User Groups

3BSE037410R4101 45


Set the Group Scope to Global and Group Type to Security and click on the OK button.

Now add users to these groups:

• To the IndustrialITAdmin group you must add the persons who have full access to the 800xA System. This group always has at least one but no more than a limited number of users!

• To the IndustrialITUser group add all users of 800xA.

Add users to the groups for the IndustrialITAdmin group as shown below:

1. Select the user group (IndustrialITAdmin in this example).

Figure 10. New Object - Group dialog

You may freely change the name of this groups as well as adding more groups to fit your needs.

Each group may then be associated with an 800xA group according to information given in the subsection Associating a Windows group to an 800xA group on page 47.

46 3BSE037410R4101

Section 4 Security Windows User Groups in Domain Controller

2. Open the context menu and select Properties. A dialog window opens (see Figure 11).

3. Click on the Add button and browse to the user you want to add.If you want to remove a member, select the user and click on the Remove button.

4. Add all users you want to add to the group in a similar way.

Associating a Windows group to an 800xA group

To associate a Windows group with an 800xA group follow the description below:

1. Open the User Structure in the Plant Explorer.

Figure 11. Including Users in User Groups

3BSE037410R4101 47


2. Select the User Group Definition aspect of a User Group (see Figure 12).

3. Select the User Group Configuration tab.

4. Click on the Associate Windows Group button.

5. A dialog window opens. See Figure 13.

Figure 12. The User Group Definition Aspect of a User Group

48 3BSE037410R4101

Section 4 Security How to Change User Permissions

6. Select the local or domain group you want to associate to and click on theOK button.

7. The Associate Windows group window closes, and the group is associated.

8. Click on the Apply or OK button on the User Group Definition aspect view.

How to Change User Permissions

Security Definition Aspect

The Security Definition aspect is used to set security in an 800xA System.By adding these aspects to Aspect Objects and modifying their settings, the security of a system, structure or an object level can be set.

Figure 13. Group Selection

The Operators’ group of your 800xA System has now been associated with the Operators’ group in Windows.Run a synchronization to make the members of the System and Windows group the same. All users must be members of the Everyone group.

Domain or Node

3BSE037410R4101 49

How to Change User Permissions Section 4 Security

Security settings are customized by adding and setting Security Definition aspects to Aspect Objects. The location of the aspect (object, structure or domain) as well as the aspect settings give determines the required security.

To create and configure a Security Definition aspect the user needs Security Configure permission. If the Range is set to or from Structure the user also needs permission to change the structure aspect, normally Configure permission.

The general principle when configuring 800xA Security is to keep it as simple as possible. A complicated security configuration is, in itself, a security problem, since it will be difficult to maintain and will encourage shortcuts.

For a small installation it may be enough to change the Default Security Definition (an aspect in the 800xA System).

A larger installation may have several operator groups with allowed permissions on different areas in the Functional Structure.

Only exceptionally should a Security Definition be put on individual Aspect Objects.

It is recommended to establish security settings based on groups instead of individual users.

The owner of the security aspect has permission to edit the security aspect even if the current permission prohibits editing. This prevents changes to the security aspect from becoming irreversible.

If a user belongs to the Administrators group, and thus has full access, a warning icon appears as shown below (in the icon bar of the Plant Explorer and Workplace windows).

Warning Icon

50 3BSE037410R4101


A Security Definition aspect specifies (see Figure 14):

• the authority range for which the aspect is valid

• the required permission, the user identity or group, node, and

• the search option order.

Figure 14. Security Definition Aspect Dialog Box

Aspect Object

Security Definition Aspect

Authority Range Setting

Setting of PermissionPermission Type User or Group

Node Search Option

3BSE037410R4101 51


Configure the Security Definition by setting the following:

• Authority RangeThe range for which the Security Definition aspect is valid, can be set to one of the following values:

– Nonedefault - means that the Security Definition aspect is disabled.

– Structure (in which the object resides)means that the permission set in this Security Definition aspect is valid in the structure on and below the object, to which the aspect is added.

– Objectmeans that the permission set in this Security Definition aspect is valid for the Aspect Object, to which the aspect is added.

– Domain (only on system objects)can only be found in a Security Definition aspect added to a system object. Means that the permission set is valid for the whole system.

• Set Permissions in the Permission area (see Figure 14)Define the user identity or group, location, and permission granted or denied.

– PermissionSee 800xA Permissions on page 62.

– TypeSpecify if the Permission is Allowed or Denied.Double-clicking on Allowed/Deny toggles the setting.

– User or GroupThe User or User Groups allowed or denied by the permission.

– NodeChoose if the settings are valid for one, more than one, or all nodes.

An object can have several Security Definition aspects, but with different ranges.

52 3BSE037410R4101


• Search Option. This can be set to:

– Continue SearchThe default setting, Continue Search, means that all structures, of which the Aspect Object is a member, are searched according to the evaluation order followed by a search in the system default.

– Terminate SearchTerminate Search means that no other Security Definition is read. This means that all permissions not granted up to the termination of Security Definition are denied.

For information about the evaluation search order, please see The Evaluation Search Order on page 107.

The search for Permission in a Structure goes from the “bottom” object in the structure and upwards and the search stops as soon as a Security Definition is found that allows or denies a permission for the user.

The search stops as soon as a Security Definition is found that allows or denies a permission for the user.

Double-clicking on a row anywhere but in the Access column opens the Edit dialog.

Domain object must have read permission!Do NOT set Denied for Everyone group Read permission in the Security Definition aspect on the domain-object (that is the object with the same name as the created system) in the Admin Structure.The system must have Read access to a lot of information to be able to at least start the Plant Explorer.

3BSE037410R4101 53


Default Settings

By default the following permissions are given to the different groups in the system:

How to Set Permission

To set permission the user must have Security Configure permission.

Set the permission as described below:

1. Add a Security Definition aspect to the Aspect Object being considered.

Group Permission

Everyone Read

Operators Operate

System Engineers Shutdown, Security Configure, Administrate, Supervise

Application Engineers Configure, Tune, Enter, Download, Force I/O, Approve, Modify History, First Signature, Second Signature, Create synchronization package, Load synchronization package.

54 3BSE037410R4101


2. Select this aspect and click on the Add button. See Figure 15.

Figure 15. The Security Definition Aspects Dialog Box - Permissions

3BSE037410R4101 55


3. A new dialog window opens, see Figure 16.

4. Select Permission and mark the Allowed or Denied check box to select the permission for the users and groups located in the window below. You can select several Permissions at the same time by using multiple selections.

Figure 16. Permission Configuration Dialog Box

56 3BSE037410R4101


For information about the Audit Allow and Audit deny check boxes see Security Audit Config on page 117.

5. Click on the Add button for Users and Groups. A new dialog box opens.

– In this dialog box add groups of users on selected domain(s). Select the group and click Add followed by the OK button.

Figure 17. Add Users and Groups Dialog Box

User Groups inthe System

3BSE037410R4101 57


– If you want to see all users in a specific group, click on the group and then on the Members... button. A new dialog opens with the names of the members of this group, and then select one or more users. See Figure 18.

6. When all selections are complete, click on the Add button.You can add several Users and Groups of users at the same time.

7. Next, set the nodes from which the permissions are valid.

– If you want to set it for all nodes, just click on the OK button.

Figure 18. Group Members Dialog Box

58 3BSE037410R4101


– If you want to set the permission for a specific node (a specific operator’s workstation), click on the dialog’s Add button. A new dialog opens.

8. Select the desired node and click Add. Click on the OK button. The dialog now looks like what is shown in Figure 20.

Figure 19. Add Node and Groups of Nodes Dialog Box

3BSE037410R4101 59


9. Click on the OK button. The permission is now allowed. “Deny” is done in the

same way.

10. Re-authentication is required to apply permission changes if Advanced Access Control is activated.

The selections made in the steps above have resulted in security configuration where Operate permission is allowed for the group Operators for the node SEAPRT001. This means that user members of the Operators’ group can operate the Functional Structure (to which the Security Definition aspect is added) from the equipment with node name SEAPRT001.

Figure 20. Configuration Dialog Box

60 3BSE037410R4101


800xA Permissions

The required permission is set per Aspect Category and OPC property.

The required permission for Read and Modify operations are displayed for that category. In the example in Figure 21 notice that for the selected Aspect Category is Read permission required to read and Configure permission to modify.

The security setting in 800xA is based on the Security Definition aspect. Add this to the Aspect Object to set the wanted security.

Figure 21. Required Permission

3BSE037410R4101 61


The security for an Aspect Object may be defined by one or more Security Definition aspects.

A user or group is allowed or denied access to an object based on the Granted Permission compared to the Required Permission:

• Required permissionRequired permission is given per Aspect Category, and defines the permission necessary to perform an operation like Read or Modify of aspects in the category. For an OPC server the required permission for Read or Write is set per property.

• Granted permissionDefines the permission for a user or group on the complete system, on a structure or on an object.

Predefined User Permissions. The 800xA System contains the following predefined permissions:

• ReadPermits a user to read information.

• ConfigurePermits a user to configure an aspect.

• OperatePermits a user to operate the system. Normally given to the Operator Group.

• TunePermits a user to tune a process.

• ShutdownPermits a user to shutdown an area. Not used in the default setting.

• Security ConfigurePermits a user to change/add permission on Aspect Objects.

• Batch ConfigurePermits a user to configure a batch operation.

62 3BSE037410R4101


• AdministratePermits a user to do administration of the Aspect Object System itself, for example add new 800xA users.

• ApproveAllows approval of an activity.

• SupervisePermits a user to supervise the process.

• EnterPermits a user to enter an environment.

• DownloadAllows download to a controller or other equipment.

• Force I/OAllows a user to force the value of an I/O.

• Modify HistoryAllows modification of version history.

• First signaturePermission to make the first digital signature for an aspect.

• Second signaturePermission to make the second digital signature for an aspect.

• Create synchronization packagePermission to create a synchronization package.

• Load synchronization package Permission to load or roll back a synchronization package.

• Modify Alarm HidingPermission to modify alarm hiding configuration.

Modification of 800xA Permissions for Process Objects

In order to modify permissions for process objects you can change the default required user permissions or set your own user permissions. This can be done on an

There may be additional permissions depending on installed system extensions.

3BSE037410R4101 63


object type level or on the object instance level. In both cases you must use the Property Attribute Override Aspect.

The Property Attribute Override is an aspect that allows you to override existing property permissions and authentication flags on both object types and objects, inside libraries. The Property Attribute Override aspect can be placed on an Aspect Object Type (Function Block Type, Control Module Type); thus affecting all Objects of that type.

It can also be placed on a single Aspect Object (Function block, Control Module); thus only affecting that particular object.

User defined permissions make it possible to raise the granularity of the security setting for special operations.

Change of Process Object Type/Object Instance Required Permission

Figure 22 shows a released library (ValveLib) that contains an object type (ValveTemplate). Its property permissions are presented in the Control Module aspect (aspect preview pane).

In order to change the property settings for variable (A) (see Figure 22) you need to do the following:

• Create a Property Override aspect

and

• set the new properties for (A).

The example given in Figure 22, will change the property for variable (A), Write permission, from Tune to Administrate, and the Authenticate level from None to Reauthenticate.

Then, these two aspects will merge together, with the new override settings for (A), but the original settings for (B) still intact. The new override permissions will be inherited by all objects of that type.

64 3BSE037410R4101


To create a Property Attribute Override aspect follow the steps below:

1. Make sure you are in the Object Type Structure and browse to the released library.

2. Right-click the type and select New Aspect.

3. Check Show all and scroll down to Property Attribute Override.

Figure 22. Property Override Attribute on Object Types

3BSE037410R4101 65


4. Click Create. A Property Attribute Override aspect will be created in the aspect pane.

You can also override property permission settings for objects. Figure 22 showed how the type ValveTemplate had the property (A) changed from None to Reauthenticate, by adding a Property Attribute Override aspect. Valve 100 received the new override setting, but so will the next object, Valve 101, and the next etc. (they all have the same object type), see Figure 23.

Suppose you need to apply an additional override setting for Valve102, for example, you want to change property (A) from Reauthenticate to Double authenticate:

1. Select Valve102 in the Control Structure and create an additional Property Attribute Override aspect for Valve102.

2. Select Double authenticate. The new aspect setting (Double authenticate) for Valve 102 will override the previous setting (Reauthenticate).

The other two objects, Valve100 and Valve101, will still have the old property authentication Reauthenticate.

Figure 23. Property Override Aspect on Objects

66 3BSE037410R4101


In this example, Valve102 is the only object that has Double Authenticate for variable (A), but the same inherited permissions (B) as the other two valves.

How to Add Your Own Permissions

In a plant all operators have permission for operating all valves. Some of those valves are used for emergency shutdown. Operating the emergency shutdown valves requires specific education which only a few operators have. These operators should have their own permission to operate the emergency shutdown valves. How is this accomplished? Add a new permission ‘Emergency Shutdown’, follow the steps below.

To add a new permission to the system follow the steps below:

1. Go to the Admin Structure and expand the Inventory Object.

2. Expand the Permission object. All default Permissions are listed below. See Figure 25.

Figure 24. Property Override (A) in Valve102

3BSE037410R4101 67


3. Right-click on the Permission object and select New Object from the context

menu.

4. Select the Permission object of type Permission according to Figure 26, and give it the name of the permission to add.

Figure 25. Permission Object

68 3BSE037410R4101


5. Click Create.

6. Select the Name aspect in the aspect list.

7. Type a description in the Description field, see Figure 27. This description will show up as a tooltip for the permission.

Figure 26. New Object - Permission

3BSE037410R4101 69


8. Click Apply.

9. Define in the Security Definition aspect for the system, if there are additional user groups that should have the given permission Emergency Shutdown in order to operate these valves.

Figure 27. Name Aspect of Emergency Shutdown Object

70 3BSE037410R4101


10. Add a Property Attribute Override Aspect to the valve instances (object

instances) which are used for emergency shutdown.

11. Change the required permission Operate (for the operation Write) to the newly created permission Emergency Shutdown.

Modification of 800xA Permissions for Aspect Categories

If, for example, there are two groups of operators, normal operators and advanced operators, the normal operators have the permission to operate and the advanced operators have the permission to tune. You want to give the advanced operators possibility to configure a trend display.

Figure 28. Emergency Shutdown Permission for Selected Operators

The new permission (Emergency Shutdown) must be exported together with the object that has been given the Property Attribute Override aspect.

3BSE037410R4101 71


Then there are two alternatives:

Alternative 1

Set the given permission for the Trend Display Aspect Category in the Aspect System Structure to Tune, see Figure 29Make sure that normal operators have the permission to operate and the advanced operators have the permission to operate and to tune.

Alternative 2

1. Create your own permission ‘TrendConfig’. See How to Add Your Own Permissions on page 67.

2. Give the permission to the advanced operator group. See How to Set Permission on page 54.

Figure 29. Aspect System Structure - Trend Display Aspect Category

72 3BSE037410R4101


3. Change the required permission Configure (for the operation Modify) to the newly created permission TrendConfig for the Trend Display Aspect Category in the Aspect System Structure., see Figure 29

4. Define in the Security Definition aspect for the system, which user groups that should have the permission TrendConfig. If this is not done the consequence will be that the user group application engineer (who has the permission Configure) can not modify a trend display. Set the given permission TrendConfig for the application engineer group.

Aspect Categories permission cannot be changed on an Aspect Instance level it can only be changed on an Aspect Category level.

3BSE037410R4101 73


Windows Restrictions for Operators

Windows Group Policy can be used to restrict users from accessing other Windows applications. National authorities can, for example, demand such limitations.

Figure 30. Configure Required Permission

74 3BSE037410R4101


The Group Policy described here also simplifies the startup of an Operator Workplace. The workplace is directly up and running as an Operator Workplace without any manual work by the operator.

Follow the steps below to set up a secure Operator Workplace:

1. On the Domain Controller: Select Start > Control Panel > Administrative Tools > Active Directory Users and Computers.

2. Create an Operators organizational unit, on the domain root object. Open the context menu and select New > Organizational Unit. See Figure 31.

Figure 31. Creation of Organizational Units

3BSE037410R4101 75


3. Move the automatically created user groups to the Operators organizational unit. See Figure 32.

4. Create the user Operator in the corresponding organizational unit:

a. Select the organizational unit Operators and open the context menu.

b. Select New > User.

Figure 32. Move User Groups

76 3BSE037410R4101


c. Give the user the name Operator, click Next.

d. Type the password and confirmation of password in the next dialog box, click Next.

e. Confirm the user creation by clicking Finish.

5. Make the user Operator member of the Users group:

a. Select Operator and open the context menu. Select Add members to a group..., see Figure 33.

b. Select the Users group, see Figure 34.

Figure 33. Add Member to Group

3BSE037410R4101 77


6. The result of the settings made above are displayed in Figure 35.

7. Add the user Operator to the 800xA System and to the IndustrialITOperator group:

Figure 34. Select Group

Figure 35. Operators Organizational Unit

78 3BSE037410R4101


a. Open the Configuration Wizard and select System Administration.

b. Select Users.

c. In the User Configuration dialog box click the Add Windows Accounts... button.

d. Select Domain in the Show members of drop-down menu and select the user Operator in the list. See Figure 36.

e. Click Add and then OK.

8. Log on as the new user Operator on a client and configure desktop:

a. Add a Shortcut to My ePlant in the Startup folder, see Figure 37.


3BSE037410R4101 79


9. Create a Group Policy by the name GeneralLockedOut:

a. Select the organizational unit Operators on the Domain Controller.

b. Open the context menu and select Properties.

c. Select the Group Policy tab.

d. Click the New button.

e. Give the new group policy a name, e.g.‘GeneralLockedOut’.See Figure 38.

Figure 37. Startup Folder

80 3BSE037410R4101


10. Configure the User Configuration:

a. Click the Edit button under the Group Policy tab.

b. A new dialog box will appear. Expand the GeneralLockedOut structure according to Figure 39.

Figure 38. Group Policy Tab

3BSE037410R4101 81


c. Make the policy settings according to the tables below. You configure the

settings by double clicking on the first policy in the right pane for each folder. A new dialog will appear in which you can choose Not Configured, Enabled or Disabled, see Figure 40.

Figure 39. Group Policy Dialog Box

82 3BSE037410R4101


For the Windows Explorer folder, configure the Policies according to Table 2.

Figure 40. Policy Tab

Table 2. Windows Explorer

Policy Setting

Turn on/Enable Classic Shell Disabled

Removes the Folder Options menu item from the Tools menu Enabled

Remove File menu from the Windows Explorer Enabled

Remove ‘’Map Network Drive’’ and ‘’Disconnect Network Drive’’

Enabled

Remove Search button from Windows Explorer Enabled

Remove/Disable Windows Explorer’s default context menu Enabled

3BSE037410R4101 83


For the Start Menu & Taskbar folder, configure the Policies according to Table 3.

Hides the Manage item on the Windows Explorer context menu Enabled

Only allow approved Shell extensions Not configured

Do not track Shell shortcuts during roaming Enabled

Hide these specified drives in My Computer Enabled

Prevent access to drives from My Computer Enabled

Remove/Hide Hardware tab Enabled

Disable UI to change menu animation setting Enabled

Disable UI to change keyboard navigation indicator setting Enabled

Disable DFS tab Enabled

No ‘’Computer Near Me’’ in My Network Places Enabled

No ‘’Entire Network’’ in My Network Places Enabled

Maximum number of recent documents Not configured

Do not request alternate credentials Not configured

Request credentials for network installations Not configured

Table 3. Start Menu & Taskbar

Policy Setting

Remove user’s folders from the Start Menu Enabled

Disable and remove links to Windows Update Enabled

Remove common program groups from Start Menu Enabled

Remove My Documents icon from Start Menu Enabled

Remove Documents from Start Menu Enabled

Table 2. Windows Explorer (Continued)

Policy Setting

84 3BSE037410R4101


Disable programs on Settings menu Enabled

Remove Network & Dial-up Connections from Start Menu Enabled

Remove Favorites menu from Start Menu Enabled

Remove Search menu from Start Menu Enabled

Remove Help menu from Start Menu Enabled

Remove Run menu from Start Menu Enabled

Add Logoff to the Start Menu Not configured

Disable Logoff on the Start Menu Not configured

Disable and remove the Shut Down command Enabled

Disable drag-and-drop context menus on the Start menu Enabled

Disable changes to Taskbar and Start Menu Settings Enabled

Disable context menus for the taskbar Enabled

Do not keep history of recently opened documents Enabled

Clear history of recently opened documents on exit Not configured

Disable personalized menus Enabled

Disable user tracking Enabled

Add ‘’Run in Separate Memory Space’’ check box to Run dialog box

Not configured

Do not use the search-based method when resolving shell shortcuts

Not configured

Do not use the tracking-based method when resolving shell shortcuts

Not configured

Gray unavailable Windows Installer programs Start Menu shortcuts

Not configured

Table 3. Start Menu & Taskbar (Continued)

Policy Setting

3BSE037410R4101 85


For the Desktop folder, configure the Policies according to Table 4.

For the Control Panel folder, configure the Policies according to Table 5.

Table 4. Desktop

Policy Setting

Hide all icons on desktop Enabled

Remove My Documents icon from desktop Not configured

Remove My Documents icon from Start Menu Not configured

Remove Properties from the My Documents context menu Not configured

Remove Properties from the My Computer context menu Not configured

Hide My Network Places icon on desktop Not configured

Hide Internet Explorer icon on desktop Not configured

Do not add shares of recently opened documents to My Network Places

Not configured

Prohibit user from changing My Documents path Not configured

Disable adding, dragging, dropping, and closing the Taskbar’s toolbars

Enabled

Disable adjusting desktop toolbars Enabled

Don’t save settings at exit Enabled

Table 5. Control Panel

Policy Setting

Disable Control Panel Enabled

Hide specified control panel applets Not configured

Show only specified control panel applets Not configured

86 3BSE037410R4101


For the System folder, configure the Policies according to Table 6.

Table 6. System

Policy Setting

Don’t display welcome screen at logon Enabled

Century interpretation for Year 2000 Not configured

Code signing for device drivers Not configured

Custom user interface Not configured

Disable the command prompt Enabled

Disable registry editing tools Enabled

Run only allowed Windows applications Not configured

Don’t run specified Windows applications Not configured

Disable Autoplay Enabled

Download missing COM components Enabled

3BSE037410R4101 87


11. Configure the Operator Workplace:

a. Log on as Administrator on a client and go to the User Structure in the Plant Explorer.

b. Expand the Operators group, and select the user Operator.

c. Select the Workplace Profile Values aspect in the aspect list.

d. For the DefaultWorkplace mark the Local radio button and a default workplace setting in the ObjectName field, see Figure 41. Click Apply.

Table 7. Log On/Log Off

Policy Setting

Disable Task Manager Enabled

Disable Lock Computer Enabled

88 3BSE037410R4101


e. For the WorkplaceMode mark the Local radio button and select

Operator Workplace Mode in the Workplace Mode field, see Figure 42. Click Apply.

Figure 41. Default Workplace

3BSE037410R4101 89


f. For the WorkplaceStartObject mark the Local radio button and select a

default object name in the ObjectName field, see Figure 43. Click Apply.

Figure 42. Workplace Mode

90 3BSE037410R4101

Section 4 Security How to Restrict the User Interface

12. Log on as Operator on the client and test the settings you have made.

How to Restrict the User Interface

User roles help to customize the environment to suit the needs of each user. This means that the operations which the user needs to take act on are visible for him/her. The user role is used to adapt the user interface to work typical for 800xA groups. For example configuration dialogs are removed from users with an Operator Role.The user roles are associated with the 800xA groups. By adding a Windows user to an 800xA group he/she is assigned a role.

The following User Roles exist:

• Operator Role - must be held by all operators in a plant. The role makes it possible to use process control dialogs, acknowledge alarms etc.

Figure 43. Workplace Start Object

3BSE037410R4101 91

How to Restrict the User Interface Section 4 Security

• Application Engineer Role - allows a user to do engineering operations and work with objects and applications built for objects (programs, graphics etc.)

• System Engineer Role - must be held by a user that works with service, node or user administration.

The default security configuration (permission and roles) is provided with the assumption that different users typically do different tasks. The assumption is that users with the role Operator control the process, but do not tune or configure. The role Application Engineer tunes the process and makes all application configurations. Finally the role System Engineer handles the physical configuration like server configurations, adding users, and setting up security.

The figure below is an example of what the three different user roles can see in a context menu for the same object.

92 3BSE037410R4101


It is possible to have an Operator that is allowed to make application configuration changes by giving the Operator the additional role of Application Engineer and the permissions associated for the Application Engineer group. Another alternative is to change the granted permission for that individual directly.

Figure 44. Example of Context Menus for the three different User Roles

Application Engineer

System Engineer

Operator

3BSE037410R4101 93


User Role Default Settings

In the User Structure the User Groups and the Users must be defined. For each User Group there is a User Group Definition aspect.

The Role a user has is set per User Group and defines what User Interfaces he/she will have. By assigning a user different roles, you give him/her a means to interact with more or less of the system’s values, settings etc.

Note that an Application Engineer does not have an Operator Role by default.This means that there are tasks an Operator can perform, that an Application Engineer can not.

It is recommended to add the System Engineer to the Application Engineer group. It is also recommended to add the Application Engineer to the Operator group.

94 3BSE037410R4101


Occupying a role, like Operator, System Engineer, does not mean that the 800xA user unconditionally has permission to perform a task. Permissions have nothing to do with the users role. Permissions are defined by the Security Definition aspects and Windows user identity only. For default permission settings see 800xA Permissions on page 61.

There are five predefined user groups in the 800xA System:

• EveryoneA group that contains all the 800xA users.

• AdministratorsA group with the security system disabled, i.e. a member of this group have full access to everything in the aspect system.

Figure 45. The User Group Definition Aspect

The User Roles Tab

In the Members Tab you can seethe members of the User Group(the same as you see if you expand the structure)

Given Role

User Group in the User Structure

The User Group Definition Aspect

3BSE037410R4101 95


• OperatorsA group of all Operators. Performs process operations.

• Application EngineerA group of all application engineers. Performs application engineering.

• System EngineersA group for all system engineers. Performs system engineering.

The role(s) for a group, or a user, is set under the tab Roles in the User Structure.

Guest. If you access 800xA and are not a member of the Everyone group you will have no role. You are a Guest in 800xA and have a very limited access to information. However, you need to be a member of the Windows group IndustrialITUser to be able to start a workplace.

To remove a Guest account follow the steps below:

1. Go to User Structure in the Plant Explorer.

2. Expand the user group Everyone.

It simplifies the user handling if all groups above are associated with the corresponding Windows groups.

You can add/delete User Groups according to the information in the Adding Users on page 38.

During configuration, commissioning and operation, avoid using a user’s identity who is also a member of the Administrators group. All members of the Administrators group are running the system with the security system disabled.

The default security configuration only allows a guest to read aspects.

96 3BSE037410R4101


3. Right-click on Guest and select Delete.

To add a Guest account follow the steps below:

1. Select Start > All Programs > ABB Industrial IT 800xA > System > Configuration Wizard > System Administration > Users.

Figure 46. Remove Guest

The Guest account may be removed using the Configuration Wizard. See Section 13, Configuration Wizard.

3BSE037410R4101 97


2. Click the Add Guest button. See Figure 47.

3. Click Next.

4. Click Finish in the Apply Settings dialog box.

Figure 47. Add Guest

98 3BSE037410R4101


5. The Guest account is now created, see Figure 48.

User Role Configuration

The Aspect Category Definition aspect for an aspect Category object in the Aspect System Structure contains a Role tab used to configure the Role required for an operation.

This definition may be changed to meet you requirements.

Figure 48. Guest Account

Do not change the Role definitions before you are very familiar with 800xA and its security model.

3BSE037410R4101 99

How do I see... Section 4 Security

The selected user role controls the required Role for the different operations.If, for example, an Application Engineer role is necessary to Read the category,a user with an Operator Role will not even see that the category exists.

How do I see...

A Security Report?

In the system you will find a Security Report aspect. You can use this aspect to get a printed report showing the security settings of the system and to compare a new

Figure 49. The Role Definition Tab of an Aspect Category

Aspect Category

The Roles related to this CategoryNote! No User Role written (blank)means that everybody can accessthis type of information.

100 3BSE037410R4101

Section 4 Security How do I see...

security report with an old one so that you can see changes in the security settings of the system.

To add a Security Report aspect follow the step below:

1. Add a Security Report to any object in any structure by opening the context menu in the aspect list and select New Aspect. Select a Security Report aspect in the list and click Create. See Figure 50

If you press the Update button you get an updated security report, in which you can see if any changes in the security settings for the system has been made since the last security report was made.

If you click the Print button you get the security report printed.

Figure 50. Security Report Aspect

By checking the Include categories check box information about required permission, required role, required authentication and required signature for the different Aspect Categories is displayed.

3BSE037410R4101 101


What can you see in the Security Report?

• System SecurityIn the first section you can see the security settings for the complete system.

• Groups and UsersIn the second section you can see the different user groups and the users in each group. See Figure 51

Figure 51. Groups and User

102 3BSE037410R4101


• Audit ConfigurationIn the third section you can see the audit configuration of the system. See Figure 52.

For information about Audit Events see Audit Trail Configuration on page 115.

My granted permission for an object?

To see your granted permission for an object, go to the object in the Plant Explorer and select it. Open the context menu for the object and select

Figure 52. Audit Configuration

3BSE037410R4101 103


Properties. Select the Permission tab and you can see what is allowed and denied to you. See Figure 53

My granted permission for an aspect?

You see the permission in the same way as you see it for an object. The Permission tab shows the operations that require a permission. It also shows whether the permission is granted.

Figure 53. Aspect/Context/Properties/Permission

The person for whomthe granted permissionis shown

104 3BSE037410R4101


Granted permission for another user?

When making the security configuration in a system it might be convenient to see how the security for an object is set for a specific person or group. You can easily do this in the following way:

1. Select the object in Plant Explorer.

2. Open the context menu and select Properties.

3. A dialog window opens, see Figure 54. Select the Permissions tab.

You need to have the permission Security Configure to use this method.

Figure 54. Object Properties Dialog Box - Permissions Tab

3BSE037410R4101 105

Advanced Security Configuration Section 4 Security

4. Click on the Change User... button.

5. Select a user in the same way you do as when you want to configure the Security.

Advanced Security Configuration

The Access Evaluation Algorithm

Several Security Definition aspects can define the security for the same Aspect Object. When an access is validated, the security aspects are evaluated in a certain order until the access is granted or denied.

The evaluation order is as follows:

• within a Security Definition aspect entries for a specific node are evaluated before entries for all nodes. “Deny” entries are evaluated before “Allow” entries.

• a Security Definition aspect that has only the object as its range is evaluated before the security aspects associated with structure aspects.

Figure 55. Select User

106 3BSE037410R4101

Section 4 Security The Evaluation Search Order

• Security Definition aspects associated with structures are evaluated in a configured order. This order is configured globally for the system so that the security for one structure always has precedence over one another.

• if the access is neither granted nor denied by any of the security aspects that directly control the authority for the object, the Security Definition aspect that sets the default for the user created system is evaluated.

• if no Security Definition aspect allows or denies a permission, the permission is denied.

The evaluation order of structures and which structures to be searched are configured in the Security Definition aspect that sets the system default security.

When you access an Aspect Object in a structure, the system searches for a Security Definition aspect added to the object. If it does not find the aspect, the system goes “upwards” to the parent structures in the evaluation order and looks for this aspect. It does so until it finds a Security Permission aspect which is valid.

When a Security Definition aspect is found, the system analyzes its information:

• which person or group of persons is allowed to do which action (Permission, Type, User of Group and Node)?

• (Permission, Type, User or Group and Node)?

• what range is set (Authority Range)?

• what node(s) can access the object(s)?

• must the search go on or not (Search Option for...)?

Based on this information the granted permission is set.

The Evaluation Search Order

When an object is accessed, and the Search Order is set to Continue Search the system goes into every structure where the object is present. The search will go on according to the order in the Evaluation Search Order list.

If a user is a member of two groups, one of which is granted permission and one which is denied permission, the result will always be denied, since “deny” entries are evaluated before “allow” entries.

3BSE037410R4101 107

The Evaluation Search Order Section 4 Security

From top to bottom. When a Security Definition is found that gives security information about the user, the search stops. For example, if a member of the Operator group is accessing an Aspect Object, and this object has a Security Definition aspect with a Permission for Operators, this Permission is valid.

If no valid security setting is found in the structures in the Evaluation Search Order list, the system goes on to the Default Settings in the System Object in the Adman structure.

Initially, the Evaluation Order List has a default setting as shown in Figure 56. You may easily change this to meet your demands by selecting the structure you want to move and then click on the left/right arrow.

Figure 56. Evaluation Order List in the Admin Structure

Admin Structurewith the system object(every time you createa new system in the Configuration Wizarda new system object iscreated in the Admin Structure)

Structures includedin the search

Structures excludedfrom search

The Evaluation Order Tab

The Security Definitionaspect for the system

Eva

luat

ion

Ord

er

108 3BSE037410R4101


If you click on the double arrow to the left, all structures are moved to the left Evaluation Order window, and the system will go through all structures when setting the security.

If you click on the double arrow to the right, you get a question dialog as shown in Figure 57, warning you that all Security Definitions with Structure Range will be disabled.

For example, if there is a structure in Location Structure and Functional Structure according to Figure 58 and Figure 59, the object Object “A” (occurring in both structures) will have the permission to operate denied to the group Operators,

Figure 57. Excluding All Structures Warning

3BSE037410R4101 109


despite the fact that the Security Definition on the object itself says that Operate is Allowed.

Figure 58. Security Setting for the Location Structure and its Aspect Objects

110 3BSE037410R4101


The reason for this is; When you access Object “A”, the system looks on the added Security Definition aspect. It finds that the Search Option is Structure. This means that the evaluation order for structures should be used.

Next the system looks for what Structure aspects are added to the Aspect Object, in order to evaluate which structure must be examined first. The system finds two structure aspects: the Location Structure aspect and the Functional Structure aspect.

According to the Evaluation Order list (see The Evaluation Search Order on page 112) the Location Structure should be examined first.

The Object “A” has no Security Definition aspect valid for the Location Structure, and therefore the search goes on to the object’s parent in the Location Structure - Object “B”. This object has a Security Definition aspect with a Location Structure setting. This aspect has the permission denied to the group Operators.

A Security Definition aspect for the group Operators that has a valid permission is found.

Figure 59. Security Setting for the Functional Structure and its Aspect Objects

3BSE037410R4101 111


The Security Definition aspect added to Object “B” in the Location Structure is set to Location Structure, and therefore the setting in it is also valid for Object “A”. For this reason the permission Operate on Object “A” is denied to the group Operators.

The result is that the settings for Operation on object Object “A” is denied to Operators, despite the fact that the Security Definition on the object itself says that it is allowed.

Always take the above information into account when checking the security of an object.

The easiest way to see the permissions of an object is to select its properties in the context menu and look in the Permission tab.

Figure 60. Evaluation Order

The Location Structurein the Evaluation OrderTab is above theFunctional Structure andmust therefore beevaluated first.

112 3BSE037410R4101


Access Example for Object with Structure Authority Setting

This is an example of how the system searches for the security setting when accessing an object. The text is related to Figure 61.

Suppose that object T33 is accessed in the Functional Structure. The system goes to the Security Definition aspect and indicates that the Authority Range is the Functional Structure.

The next step is for the system to analyze the Structure aspects to find out in which structures the object resides. It finds one Functional and one Location structure aspect. (Arrow #I in Figure 61.)

The next step is to analyze the Evaluation order. In this example the system will find that the Location Structure shall be evaluated before the Functional Structure. (Arrow #II.)

The system queries the Location Structure and looks for a Security Definition. If no valid Security Definition is found in the Location Structure for this particular user, the search will be repeated in the Functional Structure. (Arrow #III and #IV.)

If for example you have a Security Definition aspect on the Aspect Object for the Objects Functional Structure and one for the Aspect Objects Location Structure, the system will first go through the Aspect Object parent in the Location Structure looking for valid Security Definition settings for the user.

The object authority range setting to a structure in the Security Definition aspect gives the system the information that it has to go and look in all Security Definition settings for the object in all structures according to the Evaluation Order.

The ranking order between the structures must be considered. If a user accesses an object in the Functional Structure, its Security Definition settings for the Location Structure can be valid for the accessing user.

3BSE037410R4101 113

Audit Logging Section 4 Security

Audit Logging

The Security and Access Control System allows audit of operator actions and security.

The audit logs can be viewed in the alarm and event list. This makes it possible to see the effect of an operation. The audit log contains the following information:

Figure 61. The Security Search Order when Accessing a Security Definition Aspect with Authority Range Setting for the Functional Structure.

I II

IIIIV

114 3BSE037410R4101

Section 4 Security Audit Trail Configuration

• date and time for the operation

• node from which the operation was performed

• user name of the individual performing the operation

• type of operation

• object, property or aspect affected by the operation

• additional information from the involved aspect system.

Audit Trail Configuration

The Audit trail function is controlled with the Audit Trail Configuration aspect that allows filtering of the audit event categories to suit the desired audit requirements in the system. The Audit Trail Configuration controls the audit settings for the entire system. Filtering is not possible on object level.

There can only be one Audit Trail Configuration aspect in a system. It is placed in the Admin Structure. You must have the Security Configure permission to be able to configure the settings for the Audit Trail Configuration aspect.

To configure the Audit Trail Configuration aspect follow the steps below:

1. Open the Admin Structure in the Plant Explorer and expand Administrative Objects.

2. Expand Domains and select the object with the name of the system. By default this is <server node name>System.

3. Double-click on the Audit Trail Config aspect to open the configuration view. See Figure 62.

4. Mark the Audit Trail active check box and the Audit Event filtering area will become active.

5. If you select the Log generic audit events check box all the audit events which are predefined in the system without details will be logged.

Audit Logging is not possible if using the Service Account.

3BSE037410R4101 115

Audit Trail Configuration Section 4 Security

If you select the Log selected audit event classes check box, you will be allowed to choose which audit event message classes to include.

The following message classes can be used for the audit trail:

• AuditEvent_ConfigurationChange - Generated when a change is persistently stored in the system.

• AuditEvent_ForcedChange - A forced change substitutes the real-time value with a user defined value that is subsequently used instead of the actual change.

• AuditEvent_DeleteAlarm - Generated when an operator deletes an alarm in the alarm list.

• AuditEvent_Calibration - Generated for different calibration events.

• AuditEvent_ConfigurationViewChange - Changes the way a configuration is displayed, but does not change the process.

• AuditEvent_Import - Event generated when import/export start and stop.

Figure 62. Audit Trail Configuration Dialog Box

116 3BSE037410R4101

Section 4 Security Security Audit Config

• AuditEvent_System - Generated during start or stop of services.

• AuditEvent_Acknowledge - Generated when an operator acknowledges an alarm in the alarm list.

• AuditEvent_Security - Generated when a user is allowed/denied access to an object.

• AuditEvent_ CMMS - Document changes to a work order tracked in a Computerized Maintenance Management System.

• AuditEvent_AspectDirectory - Used for generic events from the Aspect Directory. Only for internal system use.

• AuditEvent_Restore - Generated during a restore of a backup.

• AuditEvent_OperatorAction - An operator sets a variable that is not a configuration parameter. For Process Objects these changes is valid for all writable properties

• AuditEvent_Upload - Events generated during upload of OPC properties.

• AuditEvent_Backup - Generated when making a backup.

6. Click Apply.

7. Re-authentication is required to apply changes in the Audit Trail Configuration if Advanced Access Control is activated.

Security Audit Config

The procedure to audit the Security Definition aspect with the audit function is described below:

1. Click on the Security Definition aspects Permissions tab.

There may be additional classes depending on the system extensions installed.

3BSE037410R4101 117

Security Audit Config Section 4 Security

2. Click on the Add button, see Figure 63.

3. Mark the Audit allow and/or the Audit deny check box to set audit for the different permissions settings. See Figure 64.

Figure 63. Security Definition Aspect Configuration View

118 3BSE037410R4101


4. Click on the OK button.

Figure 64. Audit Configuration

3BSE037410R4101 119


5. Click the Apply button, and the line (since Full Audit was chosen by selecting both Allowed and Denied when configuring) is divided into two lines; one for Allowed and one for Denied. See Figure 65.

You have now set an audit for Configure on this object. See Figure 66.

Figure 65. The Audit Configure

Figure 66. An Example of an Audit List

See IndustrialIT 800xA, System, Configuration on how to change message description for a Generic OPC Property. See IndustrialIT 800xA, Control and I/O, Basic Control Software, Introduction and Configuration on how to change message description for AC 800M properties.

120 3BSE037410R4101


Audit List

The Audit List displays audit logs of operator actions and security.It can be a useful help to, for example, see what changes the last operator on shift made in the system.

How to Create an Audit List. To add an Audit List to an object follow the steps below:

1. Add an Alarm and Event List aspect to the object in the Plant Explorer.

2. Name it for example Operator Actions List, see Figure 67.

3. Right-click on the Operator Actions List in the aspect list and select Config View.

Note that the Audit List audits the entire system, not one single object.The Audit List can be placed on any object, but it still shows activities for the whole system.

For the audit logging to work in the list, the audit trail must be activated. See Audit Trail Configuration on page 115.

Figure 67. New Aspect - Operator Actions List

3BSE037410R4101 121


4. In the Configuration area select Common Audit List, see Figure 68.

5. Click Apply.

Accessing the Audit List. The Audit List is accessible via the context menu for the object, on which the list is placed. The name of the list may differ depending on configuration. In the example the list is named Operator Actions List, see Figure 69

Figure 68. Select Configuration Name

122 3BSE037410R4101


Figure 69. Context Menu

3BSE037410R4101 123

Windows Audit Function Section 4 Security

The audit logs are viewed in the Audit List. See Figure 70

The list contains the following information:

• date and time for the operation

• node from which the operation was performed

• user name of the individual performing the operation

• type of operation

• object, property or aspect affected by the operation

• additional information from the involved aspect system.

Windows Audit Function

In Windows you will find an audit function, which gives you the means to create reports regarding log-on, log-off etc. As a Windows Domain Administrator you can set this function to support your security level.

The result of Windows audit is presented in the Event Viewer.

The settings are shown below:

Figure 70. Example of an Operator Actions List

124 3BSE037410R4101

Section 4 Security Windows Audit Function

1. Start the Domain Controller Security Policy according to Figure 71.

2. When you click on the Domain Controller Security Policy line a window opens as is shown in Figure 72.

Figure 71. Start of Domain Controller Security Policy from Start Button

3BSE037410R4101 125


Select the path Windows Setting > Security Settings > Local Policy > Audit Policy.

3. You now have the means to make a lot of settings. As an example, if you want to log all accesses to the system that Fail, double-click on the line “Audit account logon events” as shown in Figure 73 and the dialog box opens. In this

Figure 72. Settings for Audit Policy in Windows

126 3BSE037410R4101

Section 4 Security Windows Audit Function

dialog you can set that all connection attempts to the system that result in a Failure will be logged.

4. Further you can set the log size and other log declarations. Follow the path Windows Settings > Security Settings > Event Log > Settings for Event Log (see Figure 74).

Figure 73. Audit Account Logon Events

Figure 74. Settings for Event Log in Windows

3BSE037410R4101 127


5. Double-click on the line “Maximum security log size” and a dialog box opens as shown in Figure 75. In this dialog you can set how many kilobytes you want to allocate to the security log function.

6. Double-click on the line “Retain security log”. This will bring up a dialog box as in Figure 76. In this dialog you can set how many days a log must be stored in the log file, for example 7 days.

You can also give the retention methods for the log. If you, for example, double-click on the “Retention method for application log” line, a dialog box opens

Figure 75. Maximum Security Log Size

Figure 76. Retain Security Log

128 3BSE037410R4101

Section 4 Security Critical Operation Authentication Support

as in Figure 77. In this dialog you can set the rules for the log according to the text in the dialog box.

Critical Operation Authentication Support

For process critical operations, an aspect category may be configured to require an explicit authentication operation before the operation can be performed. Two different authentication operations are supported:

• Re-authentication is used to guarantee that an operation is performed by the correct person. Requiring a re-authentication immediately before a change can be performed guarantees that no one can use a workplace if an operator temporarily leaves it.

• Double-authentication is used for operations critical to the quality of the product or required by regulation. It is used where the knowledge of an operator is limited or where it is required that another operator verifies the change before it is implemented.

Figure 77. Retention Method for Application Log

For further information about the Audit function in Windows, please see the relevant Microsoft documentation.

3BSE037410R4101 129

Critical Operation Authentication Support Section 4 Security

Re-authentication

The re-authentication dialog box is used to guarantee that the correct person performs each operation. When a change is made to an OPC property or aspect that requires a re-authentication, the dialog box pops up.

The user must type his/her User ID (with domain if it differs from the default domain) and password and select a reason from the Reason drop-down menu before pressing OK. Optionally, to type a comment in the Approval Comment text field. If the provided information is accepted the dialog box disappears and the operation proceeds.

If authentication fails a pop-up error message appears which must be acknowledged before making a new attempt. If it fails three times in a row the dialog box will be terminated and the administrator will be notified about the failure with a system event.

Figure 78. Approval dialog

130 3BSE037410R4101


Double-authentication

The double-authentication dialog box is used to guarantee that the correct persons perform an operation. When a change is made to an OPC property that requires double-authentication, the dialog box pops up.

The user must type his/her User ID (with domain if it differs from the default domain) and password and select a reason from the Reason drop-down menu in the First Approval area before pressing Apply. It is optional to type a comment in the Approval Comment text field.

Figure 79. Double Approval Dialog

3BSE037410R4101 131


If the information provided by the user as the primary authenticator is accepted the Second Approval area is activated.

If it fails a pop-up error message is displayed which must be acknowledged before making a new attempt. If it fails three times in a row the dialog box will be terminated and you will be notified about the failure.

In the Second Approval area a secondary authenticator, which must have Approve permission granted on the object, shall type his/her User ID (with domain if it differs from the default domain) and password and reason before pressing OK. It is also here optional to type a comment in the Approval Comment text field.

If the provided information is accepted the dialog box disappears and the operation proceeds.

If it fails a pop-up error message appears which must be acknowledged before a new attempt can be made. If it fails three times in a row the dialog box will be terminated and you will be notified about the failure with a system event.

How to Configure Authentication

To configure authentication for an aspect category follow the steps below:

1. Open the Aspect System Structure in the Plant Explorer.

2. Expand the Aspect System and Aspect Type of the aspect category to configure.

3. Select the aspect category for which authentication is to be configured.

4. Select the Aspect Category Definition aspect in the aspect list.

5. Select the Configuration tab in the configuration view.

6. Mark the Single Authentication Required check box if re-authentication for the aspect category. If double-authentication is required for the aspect category mark the Double Authentication Required check box.

The global System Setting for Advanced Access Control must be True for authentication to work. See Configuration of Advanced Access Control on page 133 for information about the global System Setting.

132 3BSE037410R4101


Configuration of Advanced Access Control

Before you can activate the re- and double authentication can be activated it must be configured by an overall system setting so that the activation can take affect. You must hold the System Engineer role and have Security Configure permission to do this.

To do this follow the steps below:


2. Expand Domains and select the object with the name you gave to your system. By default this is <server node name>System.

3. Select the System Settings aspect in the aspect list.

4. Change the value for the Advanced Access Control property to True in the Value drop-down menu.

Note that the Advanced Access Control feature requires a license. If no license is obtained the value field will be disabled.

3BSE037410R4101 133


5. Click Apply.

To activate authentication follow the steps below:

1. Open the Admin Structure in the Plant Explorer and expand the Inventory Object.

2. Open the object Aspect Category.

3. Select the aspect category that you require authentication for.

Figure 80. System Settings Aspect - Advanced Access Control

134 3BSE037410R4101


4. Select the Aspect Category Definition aspect in the aspect list. See Figure 81.

5. Select the Configuration tab in the configuration view to set re-and double authentication for the aspect category.

6. Click Apply.

Figure 81. Aspect Category Definition Aspect - Configuration Tab

3BSE037410R4101 135

Log Over Section 4 Security

System Alarm

When a user fails to re-authenticate/log over, sign an aspect, or gets access denied there is a possibility to generate a system alarm. This is done by creating a System Alarm aspect and configure the message that should generate a system alarm. The recommendation is to place the System Alarm aspect on the Message object in the Library Structure.

The following messages can be set to generate system alarms:

Log Over

The log over function enables a fast and temporary switch between users in a running workplace. For example if an operation requires a permission not held by an operator, another user (e.g. an administrator) that holds the required permission, can log on to perform that operation. The log over changes the permissions and user roles but keeps all open windows with their present contents. The permitted actions in the open windows are controlled by the permissions of the logged over user.

LogoverFailure When log over fails.

AspectReauthenticationFailure When re-authentication of an aspectfails.

ReAuthenticationFailure When re-authentication of an OPC property fails.

AuditEvent_AccessDenied When a user gets access denied.

SignatureFailure When a user fails to sign an aspect.

136 3BSE037410R4101

Section 4 Security Log Over

It is also possible to configure an inactive user, who is a user with limited permission (read) that the system automatically will revert to after a certain amount of inactive time, see Additional Log over Settings on page 139.

Figure 82. Log Over

The log over only affect the System permission. Windows security is still the same as the user logged in. This means that the access to files is still controlled by the user logged in.

3BSE037410R4101 137


Configure Log Over

To configure Log Over follow the steps below:



3. Select the Logover Settings aspect in the aspect list.

4. Check the Enable Logover check box.

5. Click Apply.

Figure 83. Log Over Settings Aspect

138 3BSE037410R4101


Additional Log over Settings. To configure the inactive user follow the steps below:

1. Add a user which should be the inactive user by using the Configuration Wizard. See Users on page 418.



4. Select the Logover Settings aspect in the aspect list, see Figure 83.

5. Check the Enable Multiple Logover check box.

6. Select which user that should be the inactive user in the Inactivity User drop-down menu.

7. Set password for the inactive user in the Password text field.

8. Set the time for automatic revert to inactive user in the Revert to Inactivity User drop-down menu.

9. Click Apply.

Log Over Critical Aspect Views. Aspect views that do not support log over can be configured so that they must be closed before the user is allowed to perform a log over operation. This is configured per aspect category.

To make this configuration follow the steps below:

1. Open the Admin Structure in the Plant Explorer and expand the Inventory Object.


3. Select the aspect type that you want to configure.


5. Select the Configuration tab in the configuration view and mark the Close At Logover check box. See Figure 84.

3BSE037410R4101 139


6. Click Apply.

How to use Log over

To change user right-click on the user name and select Change User. See Figure 85.

Figure 84. Configure Critical Aspect Views

Figure 85. Change User

140 3BSE037410R4101


If a log over critical aspect view is open when the user selects Change User, a Close Views dialog box appears. See Figure 86. In this dialog box the user can close the log over critical views.

When the views are closed click Retry to proceed with the log over operation.

Figure 86. Close Views Dialog Box

3BSE037410R4101 141


A Change-user authentication dialog box appears and the new user must enter his/her User ID (with domain if it differs from the default domain) and password. See Figure 87.

If the User ID with domain and password are accepted the dialog box disappears and the new user can operate the workplace.

If the User ID with domain and password fail, a pop-up error message appears which must be acknowledged before a new attempt can be made. After three failed attempts in a row the dialog box will be terminated and you will be notified about the failure. A system event is also created.To return to the first user right-click on the user name again and select Revert User, see Figure 87. The revert user operation requires authentication in order to change back to the original user.

Some applications will start and run as the logged on user, even if a log over is done.The following applications do not support log-over:

– AfwImportExport.exe

– AfwConfigWizard.exe

– Afw.NLS.TranslationTool.exe

– AfwSetVariable.exe

– AfwUhOp.exe

– PgDisplayTool.exe

Figure 87. Change User Authentication Dialog Box

142 3BSE037410R4101

Section 4 Security Digital Signature

– AfwWorkplaceApplication.exe

Digital Signature

The digital signature function allows a user to electronically sign an aspect (a requirement for some industries and /or countries).The Digital Signature Server is also used to verify the identity of signed aspects, when it was signed, and if the aspect is unchanged since it was signed.

The global System Setting for Signatures Required must be set to True for the Digital Signature to work. See Configuration of Digital Signature on page 152 for information about the global System Setting.

To be able to sign an aspect the user must have the permission configured for the First and/or Second Signature operations.

To sign an aspect follow the steps below:

1. Select the aspect to be signed.

Use Windows File security to protect the applications above from being launched by unauthorized users.

The Log Over function will not work properly when Windows 2000 server or 2003 server is used for other users than those with Windows administrator rights.

To resolve the problem assign the “Impersonate a client after authentication” user right to the user or user group that should use the logover function. To do this, follow the steps below:

1.Go to Start > Programs > Administrative Tools and the select Local Security Policy.

2.Expand Local Policy, and click User Rights Assignment.

3.In the right panel, double-click Impersonate a client after authentication.

4.In the Local Security Policy Setting dialog box, click Add.

5.In the Select Users or Group dialog box, click the user account the you want to add, click Add and then OK.

6.Click OK.

3BSE037410R4101 143

Digital Signature Section 4 Security

2. Open the context menu and select Add Signature.

3. The authentication dialog appears, see Figure 88. Type a User ID with domain and a password and select a reason from the Reason drop-down menu before you press OK. It is optional to type a comment in the Approval Comment text field.

4. Click OK. This will create a Signatures aspect containing the signature. See Figure 89. An audit trail will also be generated if the audit function is active.

5. To verify the signature double click on the Signatures aspect.

6. Click Verify in the Signatures dialog box.

Figure 88. Authentication Dialog for Digital Signature

144 3BSE037410R4101


7. A Signatures Verification dialog appears, click OK.

8. The column Result shows if the signature is valid. The signature is Invalid if the signed aspect is changed in any way since its signing.

Figure 89. Signatures

Figure 90. Signature verification

3BSE037410R4101 145


9. If you click on the Details button (see Figure 89) a dialog box appears with detailed information about the signature, you also have the possibility to copy information from this dialog box, such as the Public Key and Signature.

Adding a new Reason

You can add a new Reason for the Authentication Dialog if you feel that the default reasons not are adequate.

The default Reasons are:

To add a new Reason follow the steps below:

1. Go to the Admin Structure and expand the Inventory Object.

2. Expand the Authenticate Reason object. All default Reason objects are listed below. See Figure 91.

Reason Description

Approval Approval of action or document.

Danger Danger to personal or machinery.

Disturbance Process disturbance.

Maintenance Equipment maintenance.

Optimization Process optimization.

Order Supervising order.

There may be more reasons depending on installed system extensions.

146 3BSE037410R4101


3. Right click on the Authenticate Reason object and select New Object from the

context menu.

4. Select the Reason object according to Figure 92, and give it a proper name.

5. Click Create.

Figure 91. Authenticate Reason Object

3BSE037410R4101 147


6. Select the Name aspect in the aspect list.

7. Type a description in the Description text field. This text will appear as tool tip when placing the cursor over the Reason in the Authentication Dialog. See Figure 93.

Figure 92. Reason Object

To change the description for a default Reason, change it in the Name aspect of the Reason object that is to be changed.

148 3BSE037410R4101


8. Click Apply.

Finding Signature Aspect

The Find Tool can be used for finding signed and unsigned aspects. For example, an object for which you want to sign all the unsigned aspects,do this by running a search of all unsigned aspects for that specific object.

Finding signed and unsigned aspects

1. Click on the Find Tool icon in the Plant Explorer, see .

Figure 93. Name Aspect of Verification Object

3BSE037410R4101 149


2. Select the Aspect Signature in the Add attribute drop-down menu,

see Figure 95.

3. Select Objects or Aspects depending on search, see Figure 96. If you select Objects you will find all objects which have signed/unsigned aspects. If you want to make a search for signed/unsigned aspects of a certain object, you must type the name of the object in the Name text field. If you select Aspects you will find all signed/unsigned aspects.

Figure 94. Find Tool Icon

Figure 95. Add Attribute

150 3BSE037410R4101


4. You can search for signed aspects, unsigned aspects, or both by checking the

check boxes in the status field, see Figure 97.

Figure 96. Objects/Aspects

Figure 97. Status Field - Signed/Unsigned

3BSE037410R4101 151


5. When your selections are made click the Search button to begin the search. The result is displayed in the right pane, see Figure 98.

Configuration of Digital Signature

The first and second signatures are mainly used by system synchronization. The system synchronization verifies the digital signatures (first/second) that are applied on the aspect types, belonging to the system synchronization scope. Given that the system setting for digital signature is set to True.

The first signature is given to aspect types that hold important information and therefore need to be digitally signed. The sec4ond signature is given to aspect types that also hold important information but need an additional authentication, i.e. two digital signatures.

Before you can activate the first and second signatures you have to configure an overall system setting so that the activation can take affect.

Figure 98. Search Result

152 3BSE037410R4101


You must hold the System Engineer role and have Security Configure permission to do this.

To do this follow the steps below:



3. Select the System Settings aspect in the aspect list.

4. Change the value to True in the Value drop-down menu. See Figure 99.

5. Click Apply.

Note that the Digital Signature feature requires a license. If no license is obtained the value field will be disabled.

Figure 99. System Settings Aspect - Signatures Required

3BSE037410R4101 153


6. Re-authentication is required to apply this change, given that Advanced Access Control is set to True.

To activate the first/second signature follow the steps below:

1. Open the Aspect System Structure in the Plant Explorer and expand the Aspect Directory Aspects, Aspect Systems.


3. Select the aspect type that you require digital signature for.

4. Select the Aspect Category Definition aspect in the aspect list. See Figure 100.

154 3BSE037410R4101


5. Select the Configuration tab in the configuration view to set first/second signature for the aspect category.

6. Click Apply.

Required Permission for Signing. The default setting in the system is that everyone can sign an aspect. You can easily change that by configuring the required permission for the first and second signature. Follow the steps below:

Figure 100. Aspect Category Definition Aspect - Configuration Tab

3BSE037410R4101 155

Confirmed Write Section 4 Security

1. Open the Aspect System Structure in the Plant Explorer.

2. Expand the Basic Property Aspects object.

3. Select the aspect category that you want to configure the required permission to do a first/second signature for.


5. Select the Permissions tab in the configuration view and select the operation that you want to set permission for.

6. Select permission for the operation in the Permission drop-down menu, see Figure 101. Click Apply.

Confirmed Write

When operating a SIL application, all operations on writable OPC properties must be confirmed by the operator. The operator is responsible for checking that the operation performed, in for example, a faceplate, corresponds to the operation indicated in the Confirm Operation dialog. The content of the Confirm Operation dialog is the system's interpretation of the operation. To be able to do this, the texts

Figure 101. Permission for Signing

156 3BSE037410R4101

Section 4 Security Confirmed Write

displayed in the Confirm Operation dialog must uniquely identify the operation performed, see Figure 102.

Confirmed Write also enables two-step operations for faceplates. In this case the Confirm Operation dialog gives the operator the possibility to verify that the initiated operation is the wanted operation.

Property Name column shows to the addressed property, and the Value column shows the value to be written to this property. Each property that is enabled for writing in SIL applications must be configured to identify corresponding faceplate operations.

Confirmed Write Support Configuration

Confirmed Write is preconfigured for all SIL classified control module types and function block types in AC 800M. It can also be configured manually for other control module types and function block types. This is described below.

Figure 102. Confirmed Write Support Configuration

3BSE037410R4101 157


Adding a Confirmed Write Support Aspect

1. Right-click the type and select New Aspect. A New Aspect window opens.

2. Click the Common tab in the New Aspect window, then check Show all and List presentation.

3. Scroll down the aspect list and select Confirmed Write Support.

4. Click Create. A Confirmed Write Support aspect has been created (located at the top of the aspect pane).

158 3BSE037410R4101


Figure 103. Configuration of the Confirmed Write Support Aspect

1 3 6 72 4 5

3BSE037410R4101 159


Confirmed Write Support Aspect Description

The following numbers correspond to the balloon marks in Figure 103:

1. Property Select. The property to be configured is selected either in the Property drop-down menu, or by selecting a property in the Property column.

2. Value Configuration. Operation controls in a faceplate. For example pressing the Start button which writes a Boolean value true to the controller, the Confirm Operation dialog should show the text Start in the Value column, not the Boolean value true. See also Value Configuration on page 160.

3. Select NLS Id. The NLS Id text field shows the selected NLS ID, which will be associated with the selected property if the Apply button is pressed.

4. Configured Property Name. The Confirm Name NLS Id column displays the configured NLS Id for each property.

5. NLS Resource Manager Select. The NLS Resource Manager to be used for text that has been selected in the NLS Selection drop-down menu.

6. Configured Value. The Confirm Value NLS Id column displays the NLS Id for any values that have been assigned texts (see Value Configuration No. 2).

7. NLS Id Select. The NLS Selection list displays all NLS identities defined in the selected NLS Resource Manager. The text to be assigned to the selected property is selected in the NLS Selection list.

Value Configuration. The association between the value written to the controller, and the text shown in the Value column is configured under the Confirm Value tab, see Figure 104.

160 3BSE037410R4101


1. Value Select. The value to be configured is selected from the Property drop-

down menu.

2. Select NLS Id. The NLS Id text field shows the selected NLS id, which will be associated with the selected property/value.

Figure 104. Value Configuration Dialog under the Confirm Value Tab.

For more information about Confirmed Online Write see IndustrialIT 800xA, Control and I/O, Basic Control Software, Introduction and Configuration.

Select NLS IdValue Select

3BSE037410R4101 161


162 3BSE037410R4101

Section 5 Process Sectioning

Security Setting by Structuring in Plant ExplorerA very useful method to set security is to build structures for the plant, and set Security Definition aspects with Structure range. Create typical structures in the Location Structure by putting process equipment in buildings and rooms, or dividing the Functional Structure into process sections.

We have a production process in the A3,Area which produces in two similar production lines - Line A and Line B. In the Plant Explorer we have provided each line with its own production steps according to Figure 105.

Figure 105. Production Procedure Structuring in Plant Explorer

3BSE037410R4101 163

Section 5 Process Sectioning

Basically each line has its own operator (operator Opr1 for Line A and operator Opr2 for line B). The security must be set in such a way that the operators are only able to operate their “own” line. We set a System Engineer as an Operator for both lines.

This is easily done by using the structure settings and three Security Definition aspects. We add one Security Definition aspect to the “top” Aspect Object A3,Area and one each to the objects “Production Line A” and “Production Line B”.

164 3BSE037410R4101

Section 5 Process Sectioning Setting the Security Definition Aspects in the Example

Setting the Security Definition Aspects in the Example

Security Definition Aspect for the A3, Area Aspect Object

On the “top” object for the two production lines, the A3,Area object, we configure the security setting so the System Engineers can operate both lines. We also set Read permission for a lot of groups.

We terminate search, because we do not want the default settings to be valid.

Ending the Terminate Search means that access is denied to anyone not specified in this Security Definition aspect.

Figure 106. Security Definition Aspect Setting in the “top” Object A3,Area?

3BSE037410R4101 165

Setting the Security Definition Aspects in the Example Section 5 Process Sectioning

Security Definition Aspect for the Production Line A Object

In each structure we set a Security Definition aspect that defines persons/groups that must have a permission in one structure but not in the other.

For example, in a security aspect added to the Production Line A object we define the permissions in that structure. In this case we give operator Opr1 the permission to operate the objects in this structure.

By setting Continue Search, the security search goes upwards in the structure.

Figure 107. Security Definition Aspect Setting in Production Line A Object

166 3BSE037410R4101

Section 5 Process Sectioning Setting the Security Definition Aspects in the Example

Security Definition Aspect for the Production Line B Object

The security aspect added to the Production Line B object defines the permissions in this structure. In this case we give operator Opr2 the permission to operate the objects in this structure.

By setting Continue Search, the security search goes upwards in the structure.

Figure 108. Security Definition Aspect Setting in Production Line B Object

3BSE037410R4101 167

Setting the Security Definition Aspects in the Example Section 5 Process Sectioning

168 3BSE037410R4101

Section 6 Configuration of System Services

A service provides a function in the system, for example, the Aspect Directory service and the Alarm and Event service. One or more services can run on a server node.

A service consists of one or more non-overlapping service groups. Each service group is further divided into service providers i.e. server nodes. Each provider in a group provides exactly the same function, that is, if there is more than one service provider in a service group the service is redundant or parallel. Redundant or parallel service providers always run on different server nodes.

A client of a service does not see the service as a division of groups and providers but one uniform function to which its addresses its request.

Unique Naming of Service GroupsIf several Service Groups belonging to the same Service Type are used, make sure that each Service Group has a unique name. This simplifies troubleshooting in the System Status Viewer and during configuration.

History

History Source

The History Source aspect is used to define the service group that shall handle a subset of logs, i.e. the Log Configurations on all child objects. This functionality enables distribution of the History Service among the service group in the system.It is possible to have one group handling one control network and another handling different control network.

3BSE037410R4101 169

History Section 6 Configuration of System Services

In the History Source aspect view it is permissible to select one of the configured service groups.

The history source will impact logs that are configured as children objects of the parent log as described in Figure 109.

Figure 109. History Source for Different Log Configurations

Please note that if no history source has been defined no logging will occur.

It is recommended to include the History Source aspect and choose Service Group as early as possible in the engineering process. Updating of the History Server for a Service Group change can take long time for large configurations. All logged data will be lost during change of Service Group for associated log configurations.

170 3BSE037410R4101

Section 6 Configuration of System Services History

The special configuration (Service Structure > Basic History, Service > Service Definition > Special Configuration tab) of the History Service is used to specify in which structures objects shall be logged. A History Source aspect can be placed in any structure that has been defined to support log configuration. It is also possible to specify the priority order for the different structures.

If an object exists in several structures, the priority order specified in the special configuration of the History Service will be used to locate the History Source aspect.

Figure 110. History Source dialog box

It is recommended to specify history sources in the control structure if the objects exist in that structure.

3BSE037410R4101 171

Alarm and Event Section 6 Configuration of System Services

Alarm and Event

Alarm Services

The services for Alarm and Event are found in the Service Structure. See Figure 111

Alarm Manager Service

Under the Special Configuration tab (found in the Service Structure, see Figure 112) you can configure the structure for the storage of alarm and event items, and the system message log.

Figure 111. Service Structure

172 3BSE037410R4101

Section 6 Configuration of System Services Alarm and Event

Figure 112. Alarm Manager - Special Configuration Tab

3BSE037410R4101 173


Alarm Handling. If the check box Make new alarm entry each time a condition gets active is marked, each inactive to active state change will result in a new alarm.

Event Logging Configuration. In the Event Logging area, you can set the system message log configuration, see Figure 114.

You have four options:

• Log AcknowledgeIf marked - the acknowledgement of alarms will be logged to the System Message Server as an event.

• Log Active -> Inactive ChangeIf marked - the active to inactive state changes of alarms will be logged to the System Message Server as an event.

• Log Enable/DisableIf marked - the enabling and disabling of alarms will be logged to the Systems Message Server as an event.

Figure 113. Alarm Handling

174 3BSE037410R4101


• Log Hidden -> Not Hidden changeIf marked - the hidden status for an alarm from hidden to not hidden will be logged to the System Message Server as an event.

Alarm Storage Configuration.

By clicking the Edit button in the Alarm Storage area you can configure the alarm storage.

You can set the following(see Figure 116):

• Maximum number of alarms in storageGives the maximum number of alarms which can be stored in the Alarm Manager.

Figure 114. Event Logging Configuration

All alarms are stored, by default, in the main storage. The Alarm Server is capable to save the 10000 (default) most recent alarms. Alarms belong to different categories, and some categories are more important than others. Less important alarms are therefore capable to cut out the more important ones. It is possible to define the most important alarms (of a certain category) to be excluded from the main storage and to be stored in a special storage instead.

Figure 115. Alarm Storage

3BSE037410R4101 175


• Reserve number of alarmsGives the number of alarms that are stored for each category. When the check box is unchecked and ‘Auto’ is indicated the alarms of that category are stored in the main storage.It is possible to give the maximum number of alarms that are stored for each category by marking the check box and type the number in the edit field.The sum of all maximum alarms for the categories cannot exceed the maximum number of alarms in the Alarm Manager.

Event Collector Service

The Event Collector service handles the connected OPC Alarm & Event Servers. There are one service group for each connected OPC Alarm & Event Server.

Configuration data is stored in the Service Group Definition aspect of each Event Collector Service Group object.

Figure 116. Alarm Storage Configuration Dialog Box

176 3BSE037410R4101


OPC A&E Server.

• Alarm ServerHere you select to which OPC Alarm & Event Server the Event Collector group will collect events from.

Collection Mapping.

• Collection DefinitionHere you select which Collection Definition to use for the selected OPC Alarm & Event Server.

To bring up the Alarm Collection Definition dialog and edit the selected Collection Definition click on the Edit button.

Figure 117. Event Collector Service - Special Configuration Tab

3BSE037410R4101 177


There are four options:

• Supports RefreshIf marked - when a refresh is issued towards the collector, then all alarms not included in the refresh are removed.

• Supports DisablingIf marked - the possibility to disable alarms are enabled.

• Supports Disabling On ConditionIf marked - the possibility to disable individual conditions is enabled.

• Inhibit Event LoggingIf marked - no System Messages will be generated for this Event Collector. Note that this will override the settings in the Alarm Manager.

Figure 118. Alarm Collector Definition Dialog Box

178 3BSE037410R4101


Alarm Logger Service

No configuration is needed for the Alarm Logger Service.

External Alarm Service

No configuration is needed for the External Alarm Service.

Soft Alarm Service

No configuration is needed for the Soft Alarms Service.

System Message Configuration

The System Message server handles messages from the server, connected systems, and workplace clients.

Normally you do not need to alter the defaults of the System Message Server. However, this section describes how to do it.

Configuration data is stored in the Service Definition aspect of the System Message Service object in the Service Structure, that is Service Structure > Services > SystemMessage, Service > Service Definition aspect. The System Message Configuration appears on the Special Configuration tab for Service Definition aspect.

Special Configuration. Each priority within a message class has its own storage.

The Special Configuration tab shows a tree with two root folders, see Figure 119:

• Storage Classes

• Default Sizes

3BSE037410R4101 179


You can also manipulate storage information for different message classes through Edit String dialog.

• Storage Classes

Under the Storage Classes folder, each defined message class is listed. If a message is unregistered, (that is not yet defined), it is stored in the Default Class/Storage with priority 1. This can happen during a startup phase, when an alarm or event message is sent to the operator before the corresponding message is registered. In Figure 119, Network Messages have storage for messages with priority 200. The list to the right shows the storage information for this storage.

• Default Sizes

The Default Sizes folder defines the storage information for storages that have not been defined. By default, those storages will get the size specified under this folder. See Figure 119.

Figure 119. System Message Configuration - Special Configuration

180 3BSE037410R4101


Edit String. The list to the right shows the storage information for different storages. The values can be modified by double clicking the Name field. The following dialog will be displayed. Make changes in the Value Data field and then click OK.

Click the Apply button on the Special Configuration tab to save the changes.

Values. The special configuration for System Message is shown in Figure 119. The storage Network Messages with priority 200 is selected in the tree view. The list view, to the right, shows the configuration settings for the selected storage.

The following values for every priority are specified under the Special Configuration tab:

• File Count

• File Size

• Message Count

• Max File Count

Figure 120. Edit String Dialog Box

3BSE037410R4101 181


File Size and File Count specify the storage size on the disk that is pre-allocated for the storage. Message Count specifies the number of messages that the message server tries to hold.

If the specified storage size (File Size * File Count) is too small to hold the specified number of messages, the message server will allocate more files on the disk.

Max File Count is the maximum limit of the number of files that can be stored. The number of files allocated on disk will not exceed Max File Count.

The values that can be configured for each storage are listed in Table 8.

The two reasons to change the default values for the system message configuration are to increase/decrease the number of stored messages, or make sure the system messages do not overflow the disc. By increasing the Message Count together with the Max File Count the total number of stored messages increase. The File Size and File Count should be adapted to the Message Count set.

A mean sized message is 150 bytes. This means that the File Size * File Count should be close to Message Count * 150. Max File Count larger than File Count means that more files can be allocated. The recommendation is to keep the default File Count and instead change the File Size.

Message sizes may vary, which means that the number of messages that can be stored is not guaranteed by a certain amount of allocated disk space.

Table 8. Values that can be configured on the Special Configuration Tab

File CountNumber of files that are pre-allocated on disk for the selected storage.

File SizeThe size of the files that are pre-allocated on disk for the selected storage.

Message CountThe number of messages that the selected storage should hold.

Max File CountThe maximum number of files that are allocated on disk for the selected storage.

182 3BSE037410R4101


You can set the Max File Count to the same value as the File Count to be sure that no extra disc space for the system messages is needed after startup.

• Setting FileCount

These settings are made by bringing up the Edit String dialog, by double clicking the configuration settings for the selected storage in the list view to the right.

• Setting the File Size


The Message Count is a hard limit. Independent of the size and number of files used Message Count is the upper limit for number of messages stored.

Table 9. File Count Settings

Increase

NewFileCount > FileCount

New files will be allocated if the actual number of files is less than the new FileCount so that the actual number of files will be NewFileCount.

Decrease

NewFileCount < File Count

The oldest files will be deleted if they are not needed to hold MessageCount number of messages. Otherwise the files remain.

This is due to the fact that the MessageCount has higher precedence than FileCount.

Table 10. File Size Settings

IncreasenewFileSize > FileSize

All files will be resized to the new size.

Decrease

newFileSize < FileSize

Files with no message data at a position greater than the new size will be resized to the new file size. Other files will be resized as messages are written to them.

3BSE037410R4101 183


• Setting MessageCount


• Setting MaxFileCount


Working with System Messages. System Messages are events created internally by the 800xA System. System messages can be informational but can also report about error states.

There is a predefined list in the system that presents system messages. You can bring this list up by pressing the System Message List button in the Operator Workplace application bar. Details on how to use and configure the user interface for system messages can be found in the IndustrialIT 800xA, System, Operator Workplace Configuration instruction.

Table 11. Message Count Settings

IncreaseNewMessageCount > MessageCount

Sets the MessageCount to the new value.

DecreaseNewMessageCount < MessageCount

Sets the MessageCount to the new value.

Table 12. Max File Count Settings

IncreaseNewMaxFileCount > MaxFileCount

The new MaxFileCount will allow the storage to grow to the new value of MaxFileCount.

DecreaseNewMaxFileCount < MaxFileCount

If the actual number of files is larger than maxFileCount, the number of files will be reduced to MaxFileCount files.

184 3BSE037410R4101

Section 6 Configuration of System Services Redundant Services

Redundant ServicesThis section describes how to handle problems that might occur when running redundant systems. For more information about configuration of redundant services, see the IndustrialIT 800xA System, Post Installation Setup instruction.

Configuration of Redundant Services

At least two servers are required in order to be able to configure a redundant service. The set up of all redundant services is done automatically by the Configuration Wizard when adding a redundant server.

If a service has to be set up and configured manually, it should be done in the Service Structure. Open the service that should be redundant and select the Service Group. The Configuration tab of the Service Group Definition aspect shows the list of Service Providers. See Figure 121.

Figure 121. Configuration of Service Providers

3BSE037410R4101 185

Redundant Aspect Servers Section 6 Configuration of System Services

Click Add to add a new service provider to the service group. The order determines which node will be the Master, as well as in which order the client will search for a service provider.

Redundant Aspect Servers

For aspect directories, being the central storage mechanism, special rules for redundancy apply. These rules are based on a majority-minority scheme where the minority always goes to a read-only mode, e.g. no updates are accepted. For example if three redundant aspect servers are configured all updates are always replicated to all three servers. If one of these servers at any tine cannot find its cooperating servers, regardless of reason (node shutdown, network problems), it finds itself being in minority and goes to read-only mode. If the other two servers still are up and can communicate with each other they find themselves being in majority and continue accept updates. If an even number of aspect directory servers is configured they consider themselves to be in majority if they are in contact with at least half of the servers and continue to accept updates. This mean that in a configuration of two redundant aspect servers any of the servers that cannot find its cooperating server will continue to accept updates anyhow.

Change from Redundant to Single Configuration

The following steps shows how to go from a redundant Aspect Directory configuration of three servers, to a single Aspect Directory Configuration.

1. Stop the third Aspect Server using the Configuration Wizard. See Stop Server on page 427.

2. Remove the third Aspect Server using the Configuration Wizard. See Nodes on page 410.

3. Repeat step 1 and 2 for the second Aspect Server.

Without configuration of affinity, the service provider is randomly selected and will serve all clients, and the remaining service providers will be on standby only.

186 3BSE037410R4101

Section 6 Configuration of System Services Restart Redundant Configuration

Restart Redundant Configuration

Follow the steps below to return from single Aspect Directory to redundant Aspect Directory of three servers.

1. Use the Configuration Wizard to start the Service Provider again. Select Start Server.

The Aspect Directory service will go into error an state when trying to start up.

2. Start Plant Explorer Workplace by selecting Start > All Programs > Industrial IT 800xA > System > Workplace. Select Plant Explorer.

3. Go to the Service Structure, select the Aspect Directory and the third service provider.

4. Select the Service Provider Definition aspect and Configuration tab. Give the command Cold Reset. Wait until the Aspect Directory service has come into service state. (Can take some time depending on size of the system.)

5. Repeat the previous step to start the Aspect Directory service on the second service provider.

Recovering from Read-only Mode

If there are not enough Aspect Directory servers running (that is only one in a 2 out of 3 redundancy network) the Aspect Directory will enter read-only mode.

The first step to recover from read-only mode is to start up the remaining servers and everything should work properly again. However, in some cases this may not be possible (for example permanent loss of a redundant server).

The solution is to run a NewSession command on the Aspect Directory service provider of the only remaining aspect server node as described in Change from Redundant to Single Configuration on page 186.

Locate the Service Provider object in the Service Structure (Service Structure > Services > Aspect Directory > Basic > AspectDirectory_Basic_NodeName).

When a new system is created and large import-files will be loaded, it is recommended to import before redundant aspect directories are created.

3BSE037410R4101 187

Recovering from Read-only Mode Section 6 Configuration of System Services

Open the Service Provider Definition aspect and select NewSession in the Command drop-down menu and click Run. See Figure 122. This will change the node to run as a single Aspect Server node.

Figure 122. NewSession Command

If the previous lost redundant Aspect Servers would recover and start up again, their Aspect Directory Service Provider must then be forced to resynchronize (Cold Reset) to join the new single Aspect Server again.To Cold Reset, run the following commands (in sequence): Suspend, Cold Reset Run.

188 3BSE037410R4101

Section 7 Import/Export

The Import/Export tool allows you to move applications (i.e. import and export data) to and from any IndustrialIT System. The data is saved as objects and aspects in archive files. The tool allows you to store and restore objects and aspects. They are stored in structured afw-files. It is also possible to view the contents of an archive file.

The Import/Export tool is a powerful instrument for storage and distribution of objects and aspects. You may save an object and aspect structure and then import it in the same or another part of the structure.

The Import/Export tool should be used to transport small applications in the form of object types and/or object instances between configurations. For backup and restore actions, use the Backup/Restore tool described in Section 8, Backup and Restore.

The Import/Export tool is also a strong safekeeping instrument. If you, for example, are about to make an upgrade of the System software, you can save all your company specific objects and aspects in an afw-file. If the objects and/or aspects, for some reason, are lost during the upgrade, you can import them into the structure again.

Do not export or import very large amounts of aspect objects at the same time. Operational disturbances might then occur because the Import/Export tool loads the system significantly.

An upper limit of about 50 000 objects at a time is recommended.

Remember to make an import and upload/mirroring in the right order, first import the afw files and then do the upload/mirroring.

3BSE037410R4101 189

Section 7 Import/Export

Three common ways of using the Import/Export Tool are:

1. Use the tool to import data from scratch. See How to use the Import/Export Tool on page 191.

2. Save user defined objects and aspects and use Import/ Export to update the system, or update saved data with new data from the system.

3. Use the Find Tool in Plant Explorer and Export the result. See Quick Find on page 229.

Close your Plant Explorer when making a large import. If that is not possible, close the application that you are importing to. For example, if you are importing a control application, make sure the Control Structure in Plant Explorer is closed.

190 3BSE037410R4101

Section 7 Import/Export The User Interface

The User Interface

The user interface is designed to resemble the Plant Explorer as much as possible. It consists of two main areas; the object browser and the aspect list, see Figure 123

The figure above shows the Import/Export tool with a file opened and an object selected. The aspects of the selected object are shown in the aspect list.

How to use the Import/Export Tool

Exporting objects and aspects are done by drag-and-drop from the Plant Explorer.

Figure 123. The Import/Export User Interface - Main View

Dragging an object or aspect from the Import/Export Tool to Plant Explorer is not the same thing as doing an Import/Export. It will only make a copy of the object or aspect.

Object Browser Aspect List

Main Menu

Tool Bar

3BSE037410R4101 191

How to use the Import/Export Tool Section 7 Import/Export

After a drop has been made, from Plant Explorer to the Import/Export tool, the Add dialog is displayed. This dialog has three available selections, the first one is Add Items, see the figure below:

Figure 124. The Add Dialog - Add Items

192 3BSE037410R4101

Section 7 Import/Export How to use the Import/Export Tool

The second selection is Add Settings (see Figure 125 below).

In the Add detail area two check boxes are available. If the Include Dependencies box is checked, dependencies will be added automatically. If the Include Children box is checked the application will add the dropped object’s children.

In the Overwrite Existing Data area, the following four radio buttons are available.

• Yes - Always overwrite old data with new data, never bother the user with questions about overwriting existing data.

• No - Never overwrite old data with new data and do not bother the user with questions about overwriting existing data.

• Prompt if Different - Prompt the user if new data is different than existing data.

• Prompt Always - Always prompt the user before overwriting any existing data.

Figure 125. The Add Dialog - Add Settings

3BSE037410R4101 193

How to use the Import/Export Tool Section 7 Import/Export

The third selection is the Advanced Selection, see Figure 126. In this dialog it is possible to filter out unwanted aspects or objects from the export. It is also possible to filter out aspects of a certain type or category as well as certain dependencies.

Click the Reset link to reselect the out filtered aspects again.

In Figure 126, all aspects of the Trend Display aspect category, have been excluded from the Export.

The Include Dependencies option means that all dependent objects and aspects will be included together with the selected object and/or aspect. For example, the Alarm List is dependent on the Alarm List Configuration aspect. When an alarm-list is exported, it is important that the Alarm List Configuration is included. Otherwise the Alarm List aspect will not work correctly when imported later on.

Figure 126. The Add Dialog - Advanced Selection

194 3BSE037410R4101

Section 7 Import/Export How to use the Import/Export Tool

Click Finish to start the Export.

In this dialog it is possible to cancel the Export by clicking the Cancel button. Use the Messages button to toggle the message view on and off during and after the export.

Figure 127. Process Dialog - Adding Nodes

3BSE037410R4101 195

The Main Menu, Toolbar and Context Menus Section 7 Import/Export

The Main Menu, Toolbar and Context Menus

An action or option can be available from more than one place in the User Interface, like the toolbar or the context menu. The action or option is described in the Menu description.

The File Menu

The File menu includes the following options:

New - Click New to create an empty archive. If a file is already open and changes have been made, the user will get a question about saving the file before closing it.

Open - Click Open to open an archive file. If a file is already open and changes have been made, the user will get a question about saving the file before closing it, then the new file will be opened.

Save - Click Save to save the file to disk.

Save As - Click Save as to save the file with a new name.

Figure 128. The Main Menu and Toolbar

File Menu

Edit Menu

View Menu

Tools Menu

Actions MenuHelp Menu

Quick-Find Update Import Messages Dependencies

196 3BSE037410R4101

Section 7 Import/Export The Main Menu, Toolbar and Context Menus

Properties - Select Properties from the menu to bring up the Properties dialog. In this dialog it is possible to set the properties that will be saved with the file.

With every archive file, the following properties are saved:

• Source - System name

• Source - System id

• Creator

• Short description of file (optional)

• Name

• Path

• Version

When an afw-file is saved, the Import/Export tool makes sure that the entire contents of the new file can be successfully written to the file-system. This before it actually save the new contents to a temporary file and overwrites the old file. When the disc does not have enough space for the entire new file, a Save As dialog will be presented, so that a new location with enough space can be selected.

3BSE037410R4101 197


Close - Select Close to close the file. You will get a prompt to save the file if there are unsaved changes.

Exit - Select Exit to exit the tool. You will get a prompt to save the file if there are unsaved changes.

The Edit Menu

The Edit menu includes the following options:

Undo - Click here to undo the latest change. The application supports unlimited number of steps of undo. Example of operations that can be undone are: adding aspects/objects, cut, paste and delete.

Redo - Click here to redo the latest Undo operation.

Delete - The selected item is deleted.

Cut - The selected item is moved to the Clipboard.

Copy - The selected item is copied to the Clipboard.

Paste - This options is only available if you previously have done a cut or copy. The following destinations exist for the paste operation:

Figure 129.The Archive Properties Dialog Box

198 3BSE037410R4101


• The Object Browser - Available if the item is an object and no object has been selected in the browser.

• An Object in the Object Browser - Available if an object has been selected in the Object Browser. If the pasted item is an object, this object will become a child to the selected object.

• The Aspect List - Available if an object has been selected in the object browser and the pasted item is an aspect.

Select all - This option selects all objects (if you are in the object browser) and all aspects (if you are in the aspect browser).

Find - Select Find in the Edit Menu to bring up the Find Tool dialog. In this dialog it is possible to search for objects and aspects within the archive file.

Figure 130. The Find Dialog Box

3BSE037410R4101 199


The example above shows a search for all objects starting with the “a” letter of the Area object type. The result is displayed in the list to the right.

The View Menu

The View menu includes the following options:

• Report - The Report Wizard dialog is used to get a report of a file. This can be printed or saved to a text file.

1. Select one of the Source radio buttons.

2. Click Next to go on.

Figure 131. The Report Wizard - Step One

Figure 132. The Report Wizard - Step Two

200 3BSE037410R4101


3. Select the content in the report by checking the boxes in Figure 132

4. Click Next.

In step three(Figure 133), select additional information for all objects and aspects that will be included in the report.

5. Mark one or several of the check boxes in the dialog.

6. Click Next.

The last step of the Archive Report, displays a summary of the actual report. It includes information about File Properties, Archive contents.

Figure 133. The Report Wizard - Step Three

3BSE037410R4101 201


It consists of four sections; Summary, Contents, Dependencies outside and Dependencies inside. See the Summary section in the figure below (Figure 134).

Figure 134. Archive Report - The Summary Section

202 3BSE037410R4101


• Differences - In the Show Differences dialog, differences between two afw-files, two items in the same file, or the opened file and the system is displayed.

The dialog is launched from the View Menu. You can select to view differences between two archive files, two items in the same file, or the opened file and a system.

The Differences dialog is also available from the context menu of both aspects and objects. When the dialog is launched in this way, it is possible to set what kind of differences between for example two files, that are of interest. You can also decide whether the comparison should include objects/aspects in the same file, another archive file or the system.

Figure 135. The Show Difference Dialog Box

If the System radio button is selected, uncheck the Show items that are in the “target” location check box. Otherwise the capacity of the system might be decreased.

Check the Exclude Aspect Structure check box to skip all structure aspects when comparing objects.

3BSE037410R4101 203


After selecting Show Differences from the context menu (see Figure 136 above), another dialog will be displayed. See the Show Differences for Aspects dialog below.

Figure 136. Show Differences

204 3BSE037410R4101


In this example, the target is a running system, and the selected aspect is the Trend Aspect on the A1 object.

Figure 137. Show Differences for aspect - Trend dialog

3BSE037410R4101 205


Click the OK button and the Difference Report figure is displayed.

From this dialog (Figure 138) you can see details that differ two aspects. The aspect in the system has a different description.

Click the Advanced button to open a second dialog. This one also includes id’s.

Figure 138. Difference Report Dialog Box

206 3BSE037410R4101


Figure 139. Difference Report - Advanced View

3BSE037410R4101 207


After selecting show differences from the context menu of an object, a dialog with object differences is displayed. In the example below, the source object is the Plant object in the archive file.

The target is a running system and the Plant object is placed in the Functional Structure. The Exclude Nonexportable Aspects check box is checked. It means that aspects which never will be exported, like inherited aspects, will be excluded.

Figure 140. Show Difference Dialog Box - Objects

208 3BSE037410R4101


Click OK to go on. The following dialog is displayed.

As can be seen in the figure above, the Alarm and Event List aspect on the A2 object is present in the system, but not in the file. An aspect on the A3 object has an aspect present only in the file. The Alarm and Event List aspect (on the A1 object) is changed.

Double-click on any aspect (or click the Details button) to see the aspect details for the source and target aspects.

Figure 141. Difference Report Between two Objects

3BSE037410R4101 209


The following dialog appears:

It shows that the description has been changed on the target aspect. Click the Back button to see the previous figure. Click the Advanced button to see details.

Figure 142. Difference Report - Aspect Details

Figure 143. Difference Report - Advanced View

210 3BSE037410R4101


• Messages

Select Messages in the View Menu or click the Messages button to show/hide the message window. The window displays all messages that have been generated within a session. See Figure 144:

For some type or errors it is possible to navigate from the message context menu, see Figure 144,to the aspect or object that caused the error. Select Goto Aspect or Goto Object.

Select Clear Messages in the context menu to remove all messages in the list. It is also possible to print and save the messages from this view.

• Dependencies

Select Dependencies from the View Menu or click the Dependencies button to toggle between the Aspect view and Dependency view. The Dependency view

Figure 144. The Message Window

3BSE037410R4101 211


shows the dependencies for each aspect. Dependencies can also be listed from the context menu for aspects and objects.

It is possible to navigate through the dependencies for each aspect.

The Area Sample Type Reference aspect is dependent on the Area Sample object type, which in turn is dependent on the Navigation Element and the Object Type Structure aspect categories.

All dependencies in the figure above are members of the Process Portal A System Extension.

Figure 145. The Dependency View

Dependencies for each aspect

212 3BSE037410R4101


• Aspect Details - If you want extended information for one or several aspects, select it/them, right click and select Show Details from the context menu.

The following information is displayed in the Aspect Details dialog: Name, Description, Creation date, Creator, Modification date, Modifier and Aspect Category.

Figure 146. The Aspect Details Dialog Box

3BSE037410R4101 213


Click the Advanced button to open a second dialog. This one includes id’s of the aspect, aspect category, creator and modifier, see the figure below.

• Object Details - To view extended information for an object; select the object and select Show Details from its context menu.

Figure 147. Aspect Details - Advanced View

214 3BSE037410R4101


The following information is displayed in the Object Details dialog: Name, Description, Creation date, Creator, Modification date, Modifier and Object Type. See Figure 148 below.

Click the Advanced button to open a second details dialog, see Figure 149 below. This one also includes id’s of the object, object type, creator and modifier.

Figure 148. The Object Details Dialog Box

3BSE037410R4101 215


The Restore Path and Translated Restore Path areas are for fault finding. The Restore Path is information about the object’s location during the export. It is represented by a list of structure nodes.

The Restore Path area contains the GUID’s of the structure nodes (<object-id> : <aspect-id>). The Translated Restore Path area also includes the restore-path, but translated in the selected system.

Figure 149. The Object Details - Advanced View

216 3BSE037410R4101


In the figure below the restore path is found in the system and is able to import the object to the same location that it was exported from.

The Tools Menu

From the Tool menu the following options are found:

• Select System - Brings up the Select System dialog. The dialog displays the system which the application is connected to by default.

The information is the Object Details dialog is possible to copy. For example the ID/GUID number.

Figure 150. The Select System Dialog Box

3BSE037410R4101 217


• Option - This button brings up the Options dialog. In this dialog you can set application wide options of different kind. The dialog consists of five different selections. The first one is the Column Options selection (Figure 151 below).

Figure 151. The Options Dialog - Column Options

218 3BSE037410R4101


Select the column names to be visible in the aspect list. The second selection is Find Options, see the figure below.

Check the Objects and/or the Aspects boxes, to make them sensitive to the Quick Find.

Figure 152. The Options Dialog - Find Options

3BSE037410R4101 219


Operations Options is the third selection, see Figure 153.

When the Enabled box in the Drag from Import/Export area is checked, it is possible to drag an object or aspect from the application to the Plant Explorer.

The check boxes in the Add Detail area operate in the same way as in the Add dialog (See Add Settings, Figure 125 on page 193).

In the Overwrite Existing Data area, the following four radio buttons are available.

• Yes - Always overwrite old data with new data, never bother the user with questions about over writing existing data.

Figure 153. The Options Dialog - Operation Options

220 3BSE037410R4101


• No - Never overwrite old data with new data and do not bother the user with questions about over writing existing data.

• Prompt if Different - Prompt the user if new data is different than existing data.

• Prompt Always - Always prompt the user before overwriting any existing data.

The next selection is the Presentation Options selection. See the figure below:

The Display Wizards check box in the Presentation Settings area is checked by default. If you uncheck it, the Add, Update, Import and Options dialogs will not be shown as wizards anymore. Some users prefer not to have the wizard behavior. To go back to the wizards, check the Display Wizards check box again.

Figure 154. The Options Dialog Box - Presentation Options

3BSE037410R4101 221


The last selection in the Options dialog is the Reset Options selection (see Figure 155).

The Actions Menu

The Actions menu includes the following actions:

• Import / Import all

Select the Import/Import all from the Actions menu or click the Import button to bring up the Import dialog.

The dialog has three selections. The first one is the Import Items selection, see Figure 156.

Figure 155. The Options Dialog Box - Reset Options

222 3BSE037410R4101


• Import Items

In the Import to System drop-down menu, the system set by the System Selector is displayed. (See Select System - Brings up the Select System dialog. The dialog displays the system which the application is connected to by default.) This is the system to which the import will be made. In the Import area it is possible to select whether the import will include all objects/aspects or only the currently selected one.

Figure 156. The Importing Dialog Box - Import Items

3BSE037410R4101 223


• Import Settings

If the Include Dependencies box is checked, the tool will import the selected items in dependency order.

If the Include Children box is checked the application will import the selected object’s children.

These boxes are enabled only if an object is selected when making an import. If Import All is selected at the import, the items will always be imported in dependency order.

The four radio buttons in the Overwrite Existing Data area, operate in the same way as in the Add Dialog and in the Options dialog(Figure 125 on page 193 and Figure 153 on page 220).

When importing objects and aspects, information about the creation and modification user is the same as in the afw-file. For example, if you create a new object and make an export, the object will get your creation user information.

Figure 157. The Importing Dialog Box - Import Settings

224 3BSE037410R4101


When this file is imported, the object will retain the user information stored in the afw-file, and therefore you will still be the imported object’s creation user.

In some cases, the user-information in the afw-file is not valid, e.g. the creation user is a system extension, and you don't want this information to be imported into the system. When the Force User Info option is enabled, the Import/Export will change the creation and modification user to the user doing the import.

The structure of objects and aspects in an afw-file is used only when objects are imported for the first time. If an imported object and structure node already exists in the system, the position of the object will be retained. This happens even if the user says Yes to overwrite the existing object. By checking the Rearrange Nodes option, the Import/Export tool will rearrange existing objects so that the layout of the structure becomes identical to the structure layout in the afw-file.

• Advanced Selection

Figure 158. The Importing Dialog Box - Advanced Selection

3BSE037410R4101 225


The last selection is the Advanced Selection. In this view certain objects/aspects, types or categories from the Import can be filtered out. The Advanced view operates in the same way as the Advanced Selection view in the Add dialog., see Figure 126 on page 194

Update Archive

Brings up the Update dialog. In this dialog objects/aspects in the file can be updated with new ones from the system. The dialog is divided into three selection. The three selections in the Update Dialog operate in the same way as the selections in the Export dialog. (see Figure 156, Figure 157 and Figure 158)

The first one is Update Archive, see Figure 159 below.

Figure 159. The Update Dialog Box - Update Archive

226 3BSE037410R4101


The second selection is the Update Settings selection, see Figure 160 below.

Figure 160. The Update Dialog Box - Update Settings

3BSE037410R4101 227


The third selection in the Update dialog is the Advanced Selection. See Figure 161 below.

The Help Menu

The Help menu includes:

• Contents

Click here to launch the online help for the Import/Export tool.

• About

This dialog displays the current tool version and file format.

Figure 161. The Update Dialog Box - Advanced Selection

228 3BSE037410R4101

Section 7 Import/Export Additional Information

Quick Find

The Quick Find Tool allows you to navigate to an aspect or object by writing the name of the aspect or the object in the quick-find text box. In the Options dialog (see The Options Dialog - Column Options), it is possible to choose whether quick-find should search for aspects, objects or both. By default it searches for objects.

Additional Information

Upgrading Files

The application supports old file formats through a conversion scheme that is used when performing the actual load.

Dependencies

The Import/Export function is dependency aware. This behavior can be switched on or off by the user (see Dependencies).

Dependency aware export means that dependencies are brought in automatically and exported to the same file as the dependant aspect. If an aspect depends on another aspect or object that is part of a system extension; a note is made in the file, but the aspect/object is not exported.

To view dependencies for an aspect, select the aspect and click the Dependencies button in the tool bar. The aspect list view will be replaced by a dependency tree view.

The imported file might be dependent on a specific version of the System, a System Extension or a Library. In this case, it is necessary to resolve the dependencies by installing them - before continuing the import.

A notification of missing dependencies will be displayed at the time of import.

Figure 162. The Quick Find Tool

3BSE037410R4101 229

Resolving Errors Section 7 Import/Export

Resolving Errors

While importing, there might be situation where you have to make a decision for the import to be able to continue. One common situation is that the parent of the object that's being imported, does not exist in the system. In such a case the following dialog will be presented.

In the example above we have tried to import an object named B, but its parent (named A) is not present in the system.

Another example is if you have imported an aspect that already exists; you need to resolve this by choosing whether to replace that aspect or skip it and continue with the rest of the import. It is possible to let the application make the same decision every time a similar incident occurs.

Figure 163. The Import/Export Placement Dialog Box

Figure 164. Replace Object Dialog Box

230 3BSE037410R4101

Section 7 Import/Export Audit Trail

Every decision you make is logged and visible in the message window (see Messages).

Audit Trail

The Import/Export components support Audit Trail. It means that all operations performed by these components are published in the Audit Trail log. Information about when the operation occurred and which user performed it will also be visible here.

Precautions when Importing/Exporting Aspects

The Import/Export tool can be used to restore graphic aspects, and produce copies of exported aspects. When restoring graphic aspects there are restrictions for both Import and Export.

Import Aspects

You probably want to restore the graphic elements and hence preserve existing unique identities, i.e you want the graphic display to look the same as it did.

If the graphic element is created with a new unique identity, previous references to the aspect will not work.

When a graphic aspect is exported, the object the aspect belongs to needs to exported as well to keep all identities intact.

The object can in turn belong to a hierarchy of objects, and in this case the whole structure needs to be available when the graphic aspect is imported. This means that the entire object structure needs to be exported, though not necessarily in the same afw-file.

When exporting a graphic element to another system, it is important that the systems have the same logical color definitions.

3BSE037410R4101 231

Precautions when Importing/Exporting Aspects Section 7 Import/Export

232 3BSE037410R4101

Section 8 Backup and Restore

This section describes how a complete backup and restore of the 800xA System is performed. The backup and restore procedure consists of two different parts; backup of standard Windows system and backup of the System application data.

SV 4.1 Backup and Restore

Introduction

The purpose of this section is to describe the procedures that must be performed in order to save and restore a complete SV 4.0 800xA system (including all functional area information). Figure 165 is a flowchart that outlines the steps required to save and backup a complete system. Figure 166 outlines the restore and recover process. The procedures must be performed in case the upgrade procedure will not be successful and you will be required to return to the previous system state. It is recommended that the save procedures also are performed on a regular basis.

The procedures required are:

• Save function-specific information using various tools and utilities.

• Use the 800xA backup and restore utility to save the Aspect directory and other 800xA system information.

3BSE037410R4101 233

SV 4.1 Backup and Restore Section 8 Backup and Restore

Figure 165. Save and Backup Process

SAVE FOUNDATIONFIELDBUS

INFORMATION

START

T05236A

DONE

SAVEASSET OPTIMIZATION

INFORMATION

SAVEPLC CONNECTINFORMATION

SAVE 800xA FORADVANT MASTER

INFORMATION

SAVE CONTROL ITFOR AC 800MINFORMATION

SAVE800xA FOR HARMONY

INFORMATION

SAVE ENGINEERINGSTUDIO

INFORMATION

SAVE INFORMATIONMANAGEMENTINFORMATION

SAVE BATCHMANAGEMENTINFORMATION

SAVE SYSTEMMESSAGE SERVICE

INFORMATION

SAVE BASICHISTORY SERVICE

INFORMATION

BACKUP800xA SYSTEM

SAVE PC,NETWORK AND

SOFTWAREMONITORING

SAVE800xA FOR MELODY

INFORMATION

234 3BSE037410R4101

Section 8 Backup and Restore SV 4.1 Backup and Restore

Figure 166. Restore and Recover Process

RECOVERFOUNDATION

FIELDBUSINFORMATION

START

T05237A

DONE

RECOVERASSET OPTIMIZATION

INFORMATION

RECOVERPLC CONNECTINFORMATION

RECOVER 800xAFOR ADVANT MASTER

INFORMATION

RECOVER CONTROLIT FOR AC 800MINFORMATION

RECOVER 800xAFOR HARMONYINFORMATION

RECOVERENGINEERING

STUDIOINFORMATION

RECOVER INFORMATIONMANAGEMENTINFORMATION

RECOVER BATCHMANAGEMENTINFORMATION

RECOVER SYSTEMMESSAGE SERVICE

INFORMATION

RECOVER BASICHISTORY SERVICE

INFORMATION

RESTORE800xA SYSTEM

RESTORE PC,NETWORK AND

SOFTWAREMONITORINGINFORMATION

RECOVER 800xAFOR MELODYINFORMATION

3BSE037410R4101 235

Precautionary Issues Section 8 Backup and Restore

Precautionary IssuesA software or data can become corrupted of some reason. In that case there are third party backup/restore and hard drive clone/image utilities that could be used.

A limited number of hardware failures can also be compensated when using these utilities. It is important to understand the limitations associated with these utilities.

In some cases (e.g. corrupted data, corrupted software, or hard disk failures), these utilities can be useful, while in other cases (such as replacing a workstation), these utilities may be of limited use.

It is recommended that cloning/imaging software are used to save (and restore if necessary) an image of the workstation hard drives, after installation of third party software and/or after installation of software.

The 800xA import/export utility can be used to save 800xA information in smaller parts at a time. The 800xA 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 parts of 800xA information can be imported back into the original system or into a completely different system, while backed up 800xA information only can be used to restore a whole system. Read more about 800xA Backup and Restore in How to make a Full Backup on page 280.

It is very important to understand that the following procedures are written to save the entire 800xA system and restore the 800xA system exactly as it was saved. Thoroughly understand the following critical restoration limitations before saving the system:

• The 800xA system can only be restored and recovered to an equivalent 800xA system.

• All 800xA software must be of the same level (version, service pack, roll up, etc.) as when the backup was made.

• The same system extension, as when the backup was made, must be installed.

• The Domain server must contain the same configuration as when the backup was made.

Refer to Requirements on page 260 for a complete list of the restoration requirements and limitations.

236 3BSE037410R4101

Section 8 Backup and Restore Save Function-Specific Information

Save Function-Specific InformationSome information specific to certain functional areas, is not saved during an 800xA system backup. The information that must be saved manually is detailed in the following subsections.

FOUNDATION Fieldbus

If user-made modifications have been made to library objects, use the following procedure to save the changes:

1. Save user-made changes to function block classes of the FF Block Library:

a. Open the Plant Explorer Workplace.

b. Use the Structure Selector to open the Object Type Structure.

c. Use the Object Browser to right-click on the FFLibraries node and select Open Library in Fieldbusbuilder FF from the pop-up menu. This opens the FF Block Library.

d. To save the parameter set for each user-modified function block:

– Right click and select Parameters from the pop-up menu.

– Right click into the grid and select Export all from the pop-up menu.

– Store the parameter set by entering the type's name as a file name and choosing a safe folder on disk for storage.

e. To save the dialog editor settings for each user-modified function block:

– Right click and selecting Dialog editor from the pop-up menu.

– Click Export.

– Store the dialog settings by entering the type's name as a file name and choosing a safe folder on disk for storage.

If FFLibraries and HSESubnets have been synchronized successfully, saving the user-made changes of function block classes can be done from an HSESubnet library as well. For details on how to do synchronization, refer to the section on Integration in Plant Explorer in IndustrialIT 800xA, Fieldbus FOUNDATION, Fieldbus Device Integration, Configuration.

3BSE037410R4101 237

Asset Optimization Section 8 Backup and Restore

2. Save user-made changes of the library's Object Types.

a. For safety reasons, make a copy from the Plant Explorer Workplace, using the import/export utility.

b. From the Object Type Structure, export the FFLibraries Object Type Group Open Add Settings and enable the Include Dependencies and Include Children options.

c. Save the copy in a safe media.

Asset Optimization

Use the following procedure to back up Asset Optimization information (perform only the steps applicable to the system):

1. Asset Monitoring:

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 the following directory:

...\Program Files\ABB Industrial IT\Optimize IT\Asset Optimization\AssetMonitorEnvironment\Bin

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 the following directory:


Asset Monitoring directories will be found on every Asset Optimization Server node and any other node defined as an Asset Monitoring Server.

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.

238 3BSE037410R4101

Section 8 Backup and Restore Asset Optimization

2. Maximo Integration:

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. If the directories <server_name>\<app_server> exist, located in:

...\Program Files\ABB Industrial IT\Optimize IT\Asset Optimization\ABBAO\Services\MOM\MxDefs

Backup the files in the <server_name>\<app_server> directory to a safe media.

3. SAP/PM Integration:

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.

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

The Maximo Integration information can be found on Asset Optimization Server nodes. Reference the Service Structure for the name of the Asset Optimization Server.

The SAP/PM Integration information can be found on Asset Optimization Server nodes. Reference the Service Structure for the Asset Optimization Server.

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.

3BSE037410R4101 239

PC, Network and Software Monitoring Section 8 Backup and Restore

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 User’s Guide for information about saving the DMS Server data.

PC, Network and Software Monitoring

Use the following procedure to save PC, Network and Software Monitoring information:

1. If there are user defined Script, Resource, and Assembly file, they need to be backed up. Assuming the default directory was selected during PC, Network and Software Monitoring installation, the user files are located in:

...\Program Files\ABB Industrial IT\Optimize IT\PC, Network and Software Monitoring\bin\Configuration\Scripts\User

...\Program Files\ABB Industrial IT\Optimize IT\PC, Network and Software Monitoring\bin\Configuration\Assemblies\User

...\Program Files\ABB Industrial IT\Optimize IT\PC, Network and Software Monitoring\bin\Configuration\Resources\User directory

Copy the files in these directories to a safe location.

SMS and e-mail Messaging

Save all GSM Device hardware information. Record information for the GSM device on the SMS and e-mail Messaging GSM Hardware Setup Worksheet shown in Table 13.

Asset Optimization DMS Calibration Integration SV 4.1 functions with DMS software Version 2.2.

This procedure is only necessary if there are user defined Script, Resource, and Assembly files in the 800xA System.

240 3BSE037410R4101

Section 8 Backup and Restore SMS and e-mail Messaging

Table 13. SMS and e-mail Messaging GSM Hardware Setup Worksheet

Item Setting/Value

Spooler Settings

Activate Outbox Spooler Checked (check and leave checked)

Activate Inbox Spooler Checked (check and leave checked)

Interval for Checking for Incoming Messages

Value: _____ Seconds Minutes (circle 1)

Port Settings

COM Port Value: COM _____

Baud Rate Value: _____

Data Bits Value: _____

Parity Value: _____

Stop Bits Value: _____

PIN and Properties

Query PIN Checked or Unchecked (circle one)

PIN (only if Query PIN is checked) Value: ___________________

Save PIN (only if Query PIN is checked) Checked or Unchecked (circle one)

Own Number (telephone number of SIM card (including Country Code) in GSM hardware)

Value: ___________________

Initialization String for GSM Hardware Value:_______________________________

_____________________________________________________________________________________________

3BSE037410R4101 241

PLC Connect Section 8 Backup and Restore

PLC Connect

To backup PLC Connect information:

1. If the PLC Connect IEC60870 feature is installed and configured, the IEC configuration must be saved. Refer to IndustrialIT 800xA, System, PLC Connect, Configuration for more information.

General Service Properties

Name (GSM service provider) Value: ___________________

Port Value: COM _____

SMSC Value: ___________________

Default Country Code Value: ___________________

Default Prefix Value: ___________________

Number of Attempts Value: ___________________

Splitting Service Properties

Splitting Checked or Unchecked (circle one)

Optimize Splitting Checked or Unchecked (circle one)

Enumerate Splitting Checked or Unchecked (circle one)

Narrowband Sockets Checked or Unchecked (circle one)

Messaging Service Properties

Add Before Message Blank (verify and do not change)

Use for Delivery Notification Only Unchecked (verify and do not change)

Default Option 0 (verify and do not change)

Message General Properties

Replace CR LF for Incoming Messages Checked or Unchecked (circle one)

Table 13. SMS and e-mail Messaging GSM Hardware Setup Worksheet (Continued)

Item Setting/Value

242 3BSE037410R4101

Section 8 Backup and Restore 800xA for Advant Master and Safeguard

2. If the PLC Connect Communication Server Pre Treatment function is being used in the application (refer to IndustrialIT 800xA, System, PLC Connect, Configuration for more information), make a backup of the PreTreat2.dll and PreTreat3.dll files. Pretreat2.dll and PreTreat3.dll are located in the \ABB Industrial IT\Operate IT\PLC Connect\Bin folder on the PLC Connect Connectivity Server.

3. Make a backup of the VB application projects for PreTreat2.dll and PreTreat3.dll.

4. If the Event Server Pre Treatment function is being used in the application (refer to IndustrialIT 800xA, System, PLC Connect, Configuration for more information), make a backup of PreEvent.dll. PreEvent.dll is located in the \ABB Industrial IT\Operate IT\PLC Connect\Bin folder on the PLC Connect Connectivity Server.

5. Make a backup of the VB application projects for PreEvent.dll.

800xA for Advant Master and Safeguard

Make an RTA Board backup.

Save the following files in the \Program Files\ABB Industrial IT\OperateIT\AC400CI\AdvantBase\Data\RTA\Init\ folder and record which files belong to which workstation:

• DATH01.CD• DATH02.CD• DATH03.CD

The following registry settings must be documented for reconfiguration.• Time synchronization keys in registry.• MB300 node and network address for RTA board in RTA board Configuration

Aspect.

The path is the default location of these files. If they have been placed somewhere else, make a backup from that location.

The path is the default location of the file. If it has been placed somewhere else, make a backup from that location.

3BSE037410R4101 243

800xA for Advant Master and Safeguard Section 8 Backup and Restore

Control IT for AC 800M

Use the following procedure to save the Control IT for AC 800M information:

1. Record the memory setting for OPC Server and Control Builder found in the Setup Wizard for each product.

2. Control Builder stores its settings (systemsetup.sys) on disk. Copy this file, located in the Control Builder working folder, to a safe media.

3. Save OPC configurations by selecting File > Save Configuration in the OPC Server Panel.

4. The OPC Server stores configuration files (*.cfg) and settings (systemsetup.sys) on disk. Copy these files to a safe media. The systemsetup.sys file is located in the OPC Server working folder. The configuration files are stored in the Files folder in the same location.

Perform the following procedure for each project that includes user-made Hardware Definition (HWD) files. The procedure stores the HWD-files in the Aspect Directory. This makes them available on all Engineering Workplaces and available for the import/export utility.

1. Open the project from a Plant Explorer Workplace.

2. A Hardware Definitions Problem window appears for each HWD-file used in the project.

3. Go to the Control Builder Project Explorer.

4. Select File > Insert Hardware Definitions. The Insert Hardware Definition window is displayed.

5. Select the HWD-files (multiselect is possible) to be used and click Open. This closes the Insert Hardware Definition window and saves the selected HWD-files in the Aspect directory.

6. Repeat Step 4 and Step 5 if necessary.

Backup all Control Builder projects using the ordinary 800xA System backup/restore utility. This utility also includes cold retain files stored by the OPC Server.

244 3BSE037410R4101

Section 8 Backup and Restore 800xA for Harmony

800xA for Harmony

The following is general information about the Harmony Configuration Backup and Restore:

1. The sessions on screen status entries are appended to a backup or restore log file. The user must manually erase any unwanted entries or Rename/Delete the log file to start a fresh log. The log file is initially created in the Windows 2000/2003 account’s temporary directory location. The screen form contains a log file icon that opens the log file in a Notepad application window for viewing, printing, or editing of the log file.

2. Must be run on the Server containing the configuration database for the Harmony INFI 90 feature while logged in to the Service Account for this product.

3. If you are restoring a database Backup file from a previous version of 800xA for Harmony, or one based on an older database schema, its version numbers will not match the system version. Such a Backup will be saved to a temporary database in the SQL Server and then be migrated to the Configuration Server database.

4. Recommendations: Typically, run the Backup option after creating a database for the first time. Run the Backup option before doing an upgrade or making significant changes the system configuration. Run the Restore option when the system becomes corrupt or after and upgrade takes place.

5. Do not use a SQL Server generated backup done through a Maintenance Plan or manually through the SQL Enterprise Manager for the restore operation. The Harmony Connect backup/restore utility does not support this format. Ensure that your Maintenance Procedures include a Harmony Connect backup utility generated backup each and every time you do a backup of your Aspect System. These two backups must be synchronized at the time of a restore operation.

3BSE037410R4101 245

800xA for Harmony Section 8 Backup and Restore

Access

This feature is accessed through the Start > Programs > ABB Industrial IT 800xA > 800xA for OCS Systems > Harmony > Configuration only on the Configuration Server node. (Figure 167)

Function

The Harmony INFI 90 Backup or Restore feature allows the user to manually initiate a backup or restore that supports either the full backup or full restore of the SQL Harmony INFI 90 configuration contained in its SQL database.

TCO4446A

Figure 167. Harmony Configuration Backup/Restore

246 3BSE037410R4101


The backup or restore operation sequences through all steps required to complete the operation requested.

The user backup process consists of the user selecting an aspect system name and file location to contain a standard SQL backup set and initiating the backup. The user restore process consists of the user selecting an existing SQL backup set filename and initiating the restore operation.

Backup

Use the following steps to back up an existing configuration:

1. Select Start > Programs > ABB Industrial IT 800xA > 800xA for OCS Systems > Harmony > Configuration > Backup Configuration.

2. The Connect button manually initiates the connection to the configuration database using the current Windows 2000/2003 account security. This account must have Administrative access to the system and Configuration Server database (Harmony Service Account).

3. The filename is auto generated using the Configuration Server name, date and time (ConfigServer_20020521_1034.bak for example).

4. The Backup button manually initiates the SQL database backup operation. Only one single backup is stored per file. If the backup file already exists it is overwritten.

5. If completed successfully, the Exit button is activated and the user can then exit to quit.

Restore

Use the following steps to restore an existing configuration:

1. Restore Configuration is launched from the Start menu. The path is as follows: Start > Programs > ABB Industrial IT 800xA > 800xA for OCS Systems > Harmony > Configuration > Restore Configuration.

2. The Connect button manually initiates the connection to the configuration database using the current Windows 2000/2003 account security. This account

Refer to the MSSQL file folders for the .bak files generated upon successful backup.

3BSE037410R4101 247

800xA for Harmony Section 8 Backup and Restore

must have Administrative access to the system and Configuration Server database (Harmony Service Account).

3. The Restore button initiates the restore operation.

4. The EbServerBroker and EbDataSync services are selected. If both are stopped, the restore operation continues. If either one is not stopped, reboot the system and run the restore operation again.

5. If the database version of the target Backup is the same as the system version, then it is restored directly to the Configuration Server database. The restore operation overwrites the current database if it exists.If it is not the same version, then the Backup is first restored to a temporary database within the SQL server. Its contents are then migrated to the Configuration Server database. If there are running System Nodes, Event Concentrators, or Harmony Servers on this source Backup that already exist in running state on the Configuration Server database, and they use the same host name or computer name, and are migrated over based on migration rules, then their destination counterparts are put out of service. Also, all destination process tags assigned to such destination Harmony Servers are put out of service. This action is required to prevent duplicate server tags or duplicate process tags from appearing after a migration.

6. The EbServerBroker and EbDataSync service startup modes are changed to Automatic.

7. The user is prompted to reboot the system.

The last successful backup name is pre loaded into the screens Backup/Restore file name field.

If the database version of this Backup file does not match the current system version, the user will be prompted with notification that this Backup will first be restored to a temporary SQL database and then migrated to the Configuration Server database.

The user will be prompted when to do this step.

Reboot after the installation.

248 3BSE037410R4101

Section 8 Backup and Restore Information Management

8. If completed successfully, Exit button is activated and the user manually exits the application.

Information Management

Use the History Backup and Restore utility to create all the backup files that are required to completely restore the Information Management History database. This includes all configuration data, log data from both file-based and Oracle-based logs, and the Aspect System definition file.

During a backup operation, all data in the Oracle database owned by the Oracle History user is exported to the specified destination and compressed into a zipped archive, along with any files that have been created to store file-based property log entries (called flat files).

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

3BSE037410R4101 249

Information Management Section 8 Backup and Restore

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.

Running the Backup Utility

To make a backup:

1. Select Start > All Programs > ABB Industrial IT 800xA > Information Management > History > Backup and Restore.

2. Verify the Create Backup Files of Current Configuration option is enabled in the IM Historian Backup/Restore Utility window.

3. Click Next. A window for setting up the backup operation is displayed.

4. Specify the location where the backup files is to be created in the New Directory Path for the Backup field.

Trend log configurations will only be backed up by this utility when they exist in a property log structure in combination with an Information Management-based log.

250 3BSE037410R4101


This path must already exist and the directory must be empty. If necessary, click Browse to create a new directory. Refer to Figure 168.

5. Verify the Only Generate Aspect Definition File option is disabled.

6. Click Next. The HsBAR Output Window is displayed.

7. Enable the Automatically Close Upon Completion option.

Figure 168. Setting Up the Backup Operation

3BSE037410R4101 251


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.

Saving Other Information Management Related Files

There are several other files related to Information Management that need saved as part of total system backup.

• 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.

• 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.

If a message stating that there are inconsistencies between the log configurations in the Aspect System and the log configurations in Oracle is displayed:

1) Stop all PAS services (Refer to the Information Management Configuration instruction for more information).

2) Run the hsDBMain -clean function (Refer to the Information Management Configuration instruction for more information).

3) Start all PAS services.

4) Re-run the backup utility.

More detailed instructions for this procedure can be found in the section on backing up individual Information Manager applications in the appropriate Information Management instruction.

252 3BSE037410R4101

Section 8 Backup and Restore Batch Management

Batch Management

To archive batch history, select the batch history archive aspect. By default a Batch History Overview aspect is located in Library Structure\Batch Management\Overviews. The Batch History Archive window contains the Batch Selection and Archive Destination tabs. However, this aspect can be added to any 800xA system object.

During the course of each batch process run, data that documents details about that specific batch is gathered and stored by the system in the batch database until manually removed. Data that has been archived can still be retained in the batch database. However, once data associated with a batch has been archived 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.

3BSE037410R4101 253

System Message Service Data and Basic History Service Data Section 8 Backup and Restore

System Message Service Data and Basic History Service Data

To backup the System Message Service Data or the Basic History Service Data, follow the steps below:

1. Go to the Maintenance Structure and select the Backup Definition Root object.

2. Create a new System Message Backup object and/or Basic History Backup object. See example in Figure 169 below.

3. Select the created object and its Backup Definition aspect. It has three tabs: Scope, Storage and Summary and Start Backup tab. See Figure 170.

It is possible to make a backup for the System Message Service Data and a backup for the Basic History Service Data at the same time.

Figure 169. System Message Backup object

254 3BSE037410R4101

Section 8 Backup and Restore System Message Service Data and Basic History Service Data

4. Select External Services in the Backup Type drop-down menu.

See Figure 170.

5. Check the System Message check box and/or the Basic History check box in the Configuration area.

6. Click Apply.

The Storage tab (see below) includes information about the backup.

Figure 170. The Scope tab

3BSE037410R4101 255


7. Go to the Summary and Start Backup tab. Click the Start Backup button.

See Figure 172 below.

Figure 171. The Storage tab

256 3BSE037410R4101


The backup will now be started. A dialog will appear, confirm the backup with OK. You can see the backup progress in another dialog. See Figure 173.

Figure 172. The Summary and Start Backup tab

3BSE037410R4101 257

800xA for Melody Section 8 Backup and Restore

800xA for Melody

To save 800xA for Melody information:

1. Log in to the 800xA for Melody local service account on the Configuration Server node.

2. Use the 800xA for Melody configuration backup/restore utility to create a backup of the Melody Configuration Server database:

a. Select Start > All Programs > ABB Industrial IT 800xA > System > 800xA for Melody > Configuration > Backup Configuration.

b. Click Connect in the 800xA for Melody Configuration Backup/Restore window.

c. Click Backup.

d. Click Exit when the backup is complete.

Figure 173. Backup in progress

258 3BSE037410R4101

Section 8 Backup and Restore 800xA System Backup

800xA System BackupThe backup/restore utility supports manual and scheduled backup of 800xA system information. For scheduled backups, the ABB Inform IT Scheduler must be installed.

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 shall be made (especially to the Aspect directory) during the online backup process.

Procedure

The following steps outline the 800xA system backup procedure. Refer to How to make a Full Backup on page 280 for more detailed information.

1. Create a Full Backup Definition object in the Maintenance Structure, and configure the Scope and the Storage tabs.

2. Check disk space and path in the Storage tab of the Backup Definition aspect. A large configuration could require a minimum of five gigabytes of free space.

3. Start the backup process.

4. In case of any warning or error messages (refer to How to make a Full Backup on page 280), take the appropriate measure and create a new backup.

5. Record the number of aspects and objects in the system.

a. Select the Admin Structure\Adminstrative Objects\Domains\system_name, Domain\Domain Definition aspect.

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.

Note that the number of aspects and objects can differ between the Backup system and the Restore system.

3BSE037410R4101 259

800xA System Restore Section 8 Backup and Restore

d. Select Properties on the pop-up menu.

e. Select the Statistics tab.

f. Record the number of objects listed.

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.

800xA System RestoreThe backup/restore utility supports the restoring of 800xA system information.

Requirements

The following restrictions apply when a backup is used to restore a system:

• The backup can only be restored to an 800xA system that is equivalent to the 800xA system from which the backup was taken.

• All 800xA software must be installed and of the same level (version, service pack, rollup, etc.) as when the backup was taken.

• The Domain server must contain the same configuration as when the backup was taken.

Procedure

The following steps outline the 800xA system restore procedure. Refer to How to make a Restore on page 285 for more detailed information.

Do not manually import or edit any information in backup files.

260 3BSE037410R4101

Section 8 Backup and Restore Procedure

1. Minimize the system to a single node Aspect Server using the following procedure:

a. Disconnect and shut down all clients.

b. Stop the 800xA system.

c. For each Connectivity Server and Aspect Server node:

– Restart node (frees links to file system and processes).

– Stop the server.

– Delete the system.

– Open the Configuration Wizard and 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.

2. Start the restore procedure on the same node the backup was taken.

3. Check for messages in the log file. Refer to How to make a Full Backup on page 280 to resolve any received warning or error messages.

4. 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.

5. 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.

Use the following guidelines while connecting nodes:

– Set the current system as the default system when connecting nodes to the system.

– In some cases, problems may be encountered when connecting nodes to the system. Verify that the system software user settings are correct using

3BSE037410R4101 261

Procedure Section 8 Backup and Restore

the Configuration Wizard. Restarting the node again may also solve the problem.

– Wait until all services in the newly connected node are up and running before connecting the next node. Select the Node Administration Structure\connected_node_name\System Status Viewer aspect to monitor the status of services. If some services will not start up, restarting the node may help.

– Restart each node after it has been connected to the system.

6. Record the number of aspects and objects in the system and compare these values to those recorded when the system was backed up.

a. Select the Admin Structure\Adminstrative Objects\Domains\system_name, Domain\Domain Definition aspect.

b. Record the number of objects and aspects listed in the System Size Information area of the window. (The number of objects and aspects before and after the restore can differ.)

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.

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.

l. Verify that number of objects and aspects recorded during system backup is the same as that recorded after system restoration.

262 3BSE037410R4101

Section 8 Backup and Restore Recover Function-Specific Information

Recover Function-Specific InformationInformation specific to certain functional areas that was saved during an 800xA system backup can be recovered using the information in the following subsections.

FOUNDATION Fieldbus

If user-made modifications to library objects have been saved, use the following procedure to restore the changes:

1. Import user-made changes to function block classes of the FF Block Library:

a. Open the Plant Explorer Workplace.

b. Use the Structure Selector to open the Object Type Structure.

c. Use the Object Browser to right-click on the FFLibraries node and select Open Library in Fieldbusbuilder FF from the pop-up menu. This opens the FF Block Library.

d. To import the parameter set for each user-modified function block:

– Right click and select Parameters from the pop-up menu.

– Right click into the grid and select Import all from the pop-up menu.

– Enter the name of the file containing the saved parameter set.

e. To import the dialog editor settings for each user-modified function block:

– Right click and select Dialog editor from the pop-up menu.

– Click Import.

– Enter the name of the file containing the saved windows settings.

2. Import user-made changes of the library's Object Types:

a. Import user-made changes to the object types from the Plant Explorer Workplace, using the import/export utility.

– From the Object Type Structure, import the FFLibraries Object Type Group Open Add Settings and enable the Include Dependencies and Include Children options.

3BSE037410R4101 263

Asset Optimization Section 8 Backup and Restore

Asset Optimization

Use the following procedure to restore Asset Optimization information:

1. Asset Monitoring:

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:


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 during Asset Optimization installation, the XY_Reference_Profiles directory must be restored to the following directory:


2. Maximo Integration:

Asset Monitoring directories MUST be restored on every Asset Optimization Server node and any other node defined as an Asset Monitoring Server.

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.

The Maximo Integration information MUST be restored on all Asset Optimization Server nodes. Reference the Service Structure for the Asset Optimization Server.

264 3BSE037410R4101

Section 8 Backup and Restore Asset Optimization

a. If using Maximo Integration, create 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

b. Copy thefiles to a safe media to that directory.

3. SAP/PM Integration:

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 User’s Guide for information about restoring the DMS Server data.

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 Optimization 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

The SAP/PM Integration information MUST be restored on all Asset Optimization Server nodes. Reference the Service Structure for the Asset Optimization Server.

Asset Optimization DMS Calibration Integration SV 4.1 functions with DMS software Version 2.2.

3BSE037410R4101 265

PC, Network and Software Monitoring Section 8 Backup and Restore

indicate Loaded for all Asset Monitors assigned to the Asset Monitoring Engine for this node.


Use the following procedure to restore PC, Network and Software Monitoring information:

1. If user defined Script, Resource, and Assembly files were backed up, copy the saved files from the safe media to the following directories (assuming the default directory was selected during installation):

...\Program Files\ABB Industrial IT\Optimize IT\PC, Network and Software Monitoring\bin\Configuration\Scripts\User

...\Program Files\ABB Industrial IT\Optimize IT\PC, Network and Software Monitoring\bin\Configuration\Assemblies\User

...\Program Files\ABB Industrial IT\Optimize IT\PC, Network and Software Monitoring\bin\Configuration\Resources\User

SMS and e-mail Messaging

Restore all GSM Device hardware information. Configure the GSM device per the information recorded on the SMS and e-mail Messaging GSM Hardware Setup Worksheet during backup.

PLC Connect

If either the IEC60870 or Basic Project Objects features were installed:

1. Use standard Windows procedures to access Add/Remove Programs in Windows Control Panel.

2. Select ABB PLC Connect.

This procedure is only necessary if there are user defined Script, Resource, and Assembly files in the 800xA System.

It may be necessary to stop and start the Messenger Server Service in the Service Structure after the SMS and e-mail Messaging restore operation.

266 3BSE037410R4101

Section 8 Backup and Restore PLC Connect

3. Select Change/Modify.

4. The InstallShield Wizard for PLC Connect appears. Refer to IndustrialIT 800xA, System, Installation and IndustrialIT 800xA, System, Post Installation Setup and continue install the desired features.

5. If the IEC60870 feature is installed refer to IndustrialIT 800xA, System, PLC Connect, Configuration and reload the saved IEC configuration.

To restore the PreTreat2.dll and PreTreat3.dll files:

1. If the PLC Connect Communication Server Pre Treatment function is being used in the application, copy PreTreat2.dll and PreTreat3.dll from the backup location to the same folder as they were 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 and PreTreat3.dll files (refer to IndustrialIT 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 projects for PreTreat2.dll and PreTreat3.dll.

To restore the PreEvent.dll file:

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 ...\ABB Industrial IT\Operate IT\PLC Connect\Bin.

2. Register the PreEvent.dll file (refer to IndustrialIT 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.

To redeploy the PLC Connect configuration:

1. Use the Structure Selector to open the Control Structure in the Plant Explorer Workplace.

2. Use the Object Browser to navigate to the first Generic Control Network object.

3BSE037410R4101 267

800xA for Advant Master and Safeguard Section 8 Backup and Restore

3. Select Deploy in the Aspect List area.

4. Click Deploy in the Aspect Preview area.

The deploy begins and the progress is displayed in the Aspect Preview area. The deploy is completed when Deploy ended is displayed.

5. Repeat the procedure for any additional Generic Control Network objects.

800xA for Advant Master and Safeguard

Restore the following files from the saved ...\Program Files\ABB Industrial IT\OperateIT\AC400CI\AdvantBase\Data\RTA\Init\ folder to the workstation in which they belong:

• DATH01.CD• DATH02.CD• DATH03.CD

Control IT for AC 800M

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. Replace the existing file with the file saved on the safe media. The systemsetup.sys file is located in the Control Builder working folder.

3. The OPC Server stores configuration files (*.cfg) and settings (systemsetup.sys) on disc. Replace these existing files with the files saved on the safe media. The systemsetup.sys file is located in the OPC Server working folder. The configuration files are stored in the Files folder in the same location.

4. Restore OPC configurations by selecting File > Load Configuration in the OPC Server Panel.

Properly backed up user-made Hardware Definition (HWD) files are stored in the Aspect Directory. Restoring the Aspect Directory wilsl restore these files.

268 3BSE037410R4101


Restore of Control Builder projects is done by using the ordinary 800xA System backup/restore utility. This function also includes cold retain files stored by the OPC Server.

800xA for Harmony

Use the following procedure to restore 800xA for Harmony information:

1. Log in to the 800xA for Harmony local service account on the node where the Configuration Server is located.

2. Use the 800xA for Harmony Configuration backup/restore utility to restore the Harmony Configuration information from a saved backup that was generated with the backup/restore utility.

a. Select Start > Programs > ABB Industrial IT 800xA > System > 800xA for Harmony > Configuration > Restore Configuration.

b. Click Connect in the 800xA for Harmony 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 prompted that the system version does not match the backup version, click OK.

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.

Do not use a SQL Server generated backup done through a Maintenance Plan or manually through the SQL Enterprise Manager for the restore operation. The Harmony Connect backup/restore utility does not support this format. Ensure that your Maintenance Procedures include a Harmony Connect backup utility generated backup each and every time you do a backup of your Aspect System. These two backups must be synchronized at the time of a restore operation.

3BSE037410R4101 269



Use the History backup and restore utility to restore the Information Management History database and synchronize the Aspect Directory contents with the current Information Management History database configuration.

During the restore, the existing database is dropped, and a new one is created. Mount points and additional table spaces are created based on the database being restored.

Oracle data is imported, and the file-based property logs are copied back into the system. Unless a different mount point is specified, the History database will be restored to its original location (its location prior to being backed up).

The History database can be restored from any drive on the machine, including any mapped network drives. The restore utility will first search a specified location for zipped archives matching a specific name and fitting the form name-drive.zip (such as hist-C.zip, hist-A.zip, and hist-D.zip), and will then restore the compressed database files contained within the archives to their respective original locations (their locations prior to being backed up).

Considerations

When restoring the History database, make sure the disk is ready and available on the machine 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.

Running the Restore Utility

To restore a backed up History database:

1. Stop all PAS processes (Refer to the IndustrialIT 800xA, Information Management, Configuration instruction for more information).

For any object in the original database that had more than one Log Configuration aspect, the contents of those aspects will be merged into one Log Configuration aspect per object.

Trend log configurations will only be backed up by this utility when they exist in a property log structure in combination with an Information Management-based log.

270 3BSE037410R4101


2. Ensure that no third-party applications access the Oracle database during the restore operation.

3. Stop the Inform IT History Service Provider:

a. Select the Inform IT History Service Provider object 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.

4. Select Start > All Programs > ABB Industrial IT 800xA > Information Management > History > Backup and Restore.

5. Verify that the Restore Configuration from the Backup File option, is enabled in the IM Historian Backup/Restore Utility window.

6. Click Next. A window for setting up the restore operation is displayed.

7. Specify the location of the backup files in the Path of IM Historian Backup field.

8. Click Next. The HsBAR Output Window is displayed.

9. Enable the Automatically Close Upon Completion option.

10. After the HsBAR Output Window closes, monitor the progress in the Progress Status area of the IM Historian Backup/Restore Utility window. Ignore the error messages indicating errors deleting aspect.

11. Click Next when the button becomes available. The synchronizer part of the restore process starts now.

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.

3BSE037410R4101 271


12. Verify the Update Using IM Aspect System Definition File option is enabled and the field lists the AspectSysDef.xml file. Refer to Figure 174.

13. Click Next.

14. Click Next in the window that allows the mapping of controller object locations.

15. Click Next to continue.

Figure 174. Synchronizer

272 3BSE037410R4101


16. Select the imported group in the Imported Service Groups area. Refer to Figure 175.

17. Verify that the entries in the Imported Service Providers and Current Service Providers area are identical. If necessary, refer to Adjusting Service Group Mapping on page 275 to correct the problem.

18. Repeat Step 16 and Step 17 for all the imported groups listed in the Imported Service Groups area.

19. Click Next.

20. Click Next again.

21. Click Finish when a message stating that the execution is complete, is displayed.

22. Start all processes under PAS supervision.

Figure 175. Checking Service Groups

3BSE037410R4101 273


23. Start the Inform IT History Service Provider:




d. Enable the Enabled option.

e. Click Apply.

24. 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.




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.

• History Archive Data: For each archive device, copy the appropriate folders from the safe media to the location specified by the Device Filename.

• Reports: Restore any report template files created in Microsoft Excel, DataDirect, and/or Crystal Reports. Also restore report output files created as a result of running these reports via the Scheduling Services.

• Desktop Trends: Restore trend display, ticker display, and tag explorer files.

More detailed instructions for this procedure can be found in the section of restoring individual Information Manager applications, in the appropriate Information Management instruction.

274 3BSE037410R4101


• Display Services: Restore the directories for custom users, as well as display and user element definitions.

• DataDirect: Restore custom text files for object, object type, and attribute menus used on the DataDirect windows.

Adjusting Service Group Mapping

During the restore or synchronization of a history database configuration, the service group definitions in the configuration being restored or synchronized, are matched to their corresponding service groups in the Aspect directory. The service group mapping window (Figure 176) is used to verify that all service groups are properly matched, and correct any mapping error that may occur. This window can also be used to make adjustments. For instance, two restored service group configurations can be merged into one available service group.

In this window, service group definitions being restored or synchronized are called imported service groups. The actual service groups that are available in the Aspect directory are called current or available service groups. The backup/restore utility automatically maps imported service groups to an available service group by matching the host name for each imported service group with the host name for an available service group. (The host name is specified in the service provider configuration of the service group.)

If service group configurations in the Aspect directory have changed since the creation of the history database configuration now being restored or synchronized, some imported service groups may not be mapped to any available service group.

3BSE037410R4101 275


This condition is illustrated in Figure 176 where the Current Service Group column for imported service group eng38 is blank. If this occurs use the dialog to manually map the imported service group to an available service group.

Follow the steps below to manually map an imported service group to an available service group:

1. Select the imported service group which mapping is to be changed in the Imported Groups column of the Imported Service Groups area.

2. Select the current service group that is to be mapped to the selected imported service group in the Available Service Groups area. The host name for the service provider for the selected available service group, is indicated in the Current Service Providers area (bottom center of the window).

3. Click <<. This puts the name of the selected available service group in the Current Groups column for the imported service group.

4. Verify that the host names in the Imported Service Providers area and the center Current Service Providers area are set correctly.

Figure 176. Adjusting Service Group Mapping

276 3BSE037410R4101

Section 8 Backup and Restore Batch Management

5. If necessary, repeat this procedure to map additional imported service groups to the same available service group.

To change the currently mapped service group for an imported service group:

1. Unmap current service group:

a. Select the imported service group.

b. Click >> to remove the name of the currently mapped service group. At this point the imported service group is not mapped to any available service group.

2. Manually map an imported service group to an available service group.

Batch Management

Batch data can be reloaded to the batch database from wherever it was archived. Once the restored data is placed in the batch database, it can be viewed using the Batch History Overview window.

Do not restore directly from CDs or DVDs. Restore from hard disk drives which can be restored from CDs or DVDs using commercially available software.

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.

To restore batches:

1. Click Pick Files.

2. Select the batch files to be restored in the standard Windows Open window.

3. Click OK.

4. Repeat Step 1 through Step 3 until all wanted batch files have been 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.

3BSE037410R4101 277


System Message Service Data and Basic History Service Data

To restore System Message Data and/or Basic History Data, follow the steps below:

1. Go to the Maintenance Structure and select the System Message Backup object and/or the Basic History Backup object under the Backups, Backup Root object.

2. Select the Backup Info aspect, see Figure 177.

It is possible to restore both the System Message Data and the Basic History Data at the same time provided that you made the backup for them at the same time.

Figure 177. Backup Info aspect

278 3BSE037410R4101


3. Select the Restore tab. See Figure 178 below.

– If you are doing a restore on a System Message Backup object, check the System Message check box and select the categories that you want to include in the restore. See figure below.

– If you are doing a restore on a Basic History Backup object, check the Basic History check box.

– If you are doing a restore for both, check both the System Message check box and the Basic History check box.

4. Click Apply.

5. The Restore button to the left in the dialog will be enabled. Click the button and then OK to start the restore.

Figure 178. The Restore tab

3BSE037410R4101 279

800xA for Melody Section 8 Backup and Restore

800xA for Melody

To restore 800xA for Melody information:

1. Log in to the 800xA for Melody local service account on the COnfiguration Server node.

2. Use the 800xA for Melody configuration backup/restore utility to restore the Melody Configuration information from a saved backup:

a. Select All Programs > ABB Industrial IT 800xA > System > 800xA for Melody > Configuration > Restore Configuration.

b. Click Connect in the 800xA for Melody Configuration Backup/Restore window.

c. Enter the name of the 800xA for Melody Configuration Server database backup file in the Backup File field

d. Click Restore.

e. If promoted that the system version does not match the backup version, click OK.

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.

How to make a Full BackupFollow the recommendations below to make a Full Backup.

1. Create a Full Backup Definition object with definitions of scope and storage settings.

2. Configure the Backup Definition aspect.

3. In the aspect, select the Summary and Start Backup tab and click the Start Backup button to start the backup.

280 3BSE037410R4101

Section 8 Backup and Restore Backup Object

4. A new Full Backup object is created when the Full Backup is running. It will be created in the Maintenance Structure under the Backups object. It will be called <Backup Definition Name>; <Date>; <Time>. For an example of the path, see Figure 175 on page 273.

A backup consists of a BackupInfo.xml file, and a set of files containing actual backup data. The backup object has a Backup Info aspect, with Scope, Storage, and Status tabs.

Backup Object

The Storage tab shows the node on which the backup was made. It also displays the backup path and the size of the backup.

<Backup Definition Name> is the name of the Backup Definition object the backup was created from. <Date> it the date when the backup was started. <Time> is the time when the backup was started.

3BSE037410R4101 281

Backup Object Section 8 Backup and Restore

If the backup is copied to a media, for example a CD or DVD, the media code can be entered in this dialog as well. See Figure 179 below.

The Status tab displays the progress and status of an ongoing backup as well as the status of a finished backup. The log file can be displayed on a finished backup.

Figure 179.The Storage Tab of the Backup Info Aspect

Aspects and objects are restored from the Configuration Wizard,and not from this tab.

282 3BSE037410R4101

Section 8 Backup and Restore Backup Service

Backup Service

The Backup Service runs on each aspect directory server node in a service group. The Backup Service is not redundant, but the different backup service providers enable backups to be run on different nodes.

Backup Service Provider Definition Aspect

It is possible to make specific configurations of the Backup Service Provider object. Select the object in the Service Structure. Go to the Service Provider Definition aspect and select the Special Configuration tab. See the figure below.

In the Path definition area a root directory (Backup Path) for all backups can be set. It is made by the Backup Service provider. The default value for the path is set in the Storage Path area under the Configuration tab of the Service Definition aspect.

Figure 180. The Service Provider Definition aspect - The Special Configuration Tab

The disc that the backup runs on should be on the local computer.

3BSE037410R4101 283

Scheduling a Backup Section 8 Backup and Restore

It is also possible to specify a Free disk space limit. The backup service guarantees that this amount of disk space is free after any backup is made.

If the limit is passed during a backup, the backup operation will fail and an error, as a system message and an audit trail, will be issued.

A low disk space warning limit can also be specified in this tab. If there is less disk space available than the limit, a warning is issued as a system message and an audit trail is issued.

The Identification, Configuration and Status tabs are standard tabs available for all service providers.

Scheduling a Backup

Full Backup Definition objects can be scheduled. Select the Scheduling Structure and configure what to schedule in an action aspect. Scheduling is a System Extension which has to be installed.

Figure 181. The Action Aspect

284 3BSE037410R4101

Section 8 Backup and Restore How to make a Restore

In the example above, a Backup Definition object called Aspect Data 2 is selected to be scheduled.

For more information about scheduling, read Section 12, Scheduling Reports.

How to make a RestoreIt is important to follow the instructions and recommendations below before starting a restore procedure. The restore will recreate an equivalent system, after a computer failure. It is also a recommended way to transfer data between one version of the system to another during an upgrade.

Preparing the Restoring Process

A restore of a 800xA System is performed from the Configuration Wizard. The same or a later version of the 800xA system and all System Extensions that was installed when the backup was done, need to be installed when the system is being restored. Make sure the right processes are running and that no system exists.

Restoring a Backup Containing Aspect Data

1. Open the Configuration Wizard.

The processes are AfwTrayIcon.exe, AfwSMClient.exe and AbbClientLicenseProvider.exe

3BSE037410R4101 285

Preparing the Restoring Process Section 8 Backup and Restore

2. Select Restore System and click Next in the Configuration Wizard. See the figure below.

The restore functionality is used to restore backups containing Aspect Data. It is available from the Configuration Wizard, see Figure 182. The Configuration Wizard is the only way to restore Aspect Data.

Figure 182.The Configuration Wizard - Restore System

286 3BSE037410R4101

Section 8 Backup and Restore Finding the Backup Files

Backups with only Service Data, on the other hand, can be restored from the Backup Info aspect when the system is running.

You need to specify the path to a location of the backup. Specify the root directory and the application will search for backups below the root. Available backups will be shown in a tree structure, where dependencies to other backups are shown in the same way as in the Plant Explorer when running a backup.

Finding the Backup Files

1. Click the Select Path button (Figure 183) to enter the path for available backups.

2. Click OK to close the dialog and the tree will display available backups. If the same backup is found more than once you will get a warning and the first one found will be used.

Figure 183.The Restore Selection in the Configuration Wizard

3BSE037410R4101 287

Finding the Backup Files Section 8 Backup and Restore

To get more detailed information about the selected backup in the tree, click the View Info button and an Information dialog will be displayed.

Selecting a Backup to Restore

Select one backup to be restored in the tree view to and click Next. From the selected backup, the aspect directory is restored. During the restore it is possible to generate a new system id and System Name for the restored system. This is not needed if no changes will be made. Click Next, see the figure below.

Figure 184. Configuration Wizard - Restore to New System

If a backup will be restored to the same network as the original system is running on, it is necessary to generate a new system id and name during restore. Two systems with the same id and name can not exist in the same network.

288 3BSE037410R4101

Section 8 Backup and Restore Finding the Backup Files

If the restore runs in a different system than the backup was made in, a primary node in the backup system must be remapped to the node your are running the restore on.

You remap a node by right-clicking the node in the restored system, and changing the node name. See the figure below.

3. Click Next.

Figure 185. Node Configuration - Other Node

3BSE037410R4101 289

Upgrade Older Versions Section 8 Backup and Restore

4. Click Finish to complete the restore.

The Restore is not completed until the Aspect Directory is restored. The system is running when restore is finished.

Upgrade Older Versions

Backups of older versions of the 800xA System will show up in the backup tree in the Restore Selection dialog, (Figure 183), in the same way as backups from a system of the same version.

Figure 186.Apply Settings

290 3BSE037410R4101

Section 8 Backup and Restore System Configuration Version

It is possible to restore backups from an earlier version to a later version of the system. After the restore an upgrade procedure will be performed to convert data. See also the IndustrialIT 800xA System, Upgrade instruction.

System Configuration Version

The System Configuration Version is created in the same way as a full backup. The only difference is that the object type name is System Configuration Object Type. The System Configuration Version is not configurable.

1. Select the System Configuration Version Definition object in the Maintenance Structure.

Before the restore is started you will get a report of what your restore will include. It also includes information about restoring from an older version i.e. doing an upgrade.

3BSE037410R4101 291

System Configuration Version Section 8 Backup and Restore

2. Select the Backup Definition aspect and set a version identity in the Summary and Start Backup tab by clicking the Create System Configuration Version.. button. See the figure above.

3. The tab includes information about Scope, Services, Node and Path etc.

4. Click the Create System Configuration Version button. A dialog is displayed where you enter the version. Click OK.

5. There is now a complete version of the system with an ID.

Figure 187. System Configuration Version Definition

292 3BSE037410R4101

Section 8 Backup and Restore Warning and Error Messages

The restore process for a System Configuration Version works in an ordinary way, see Restoring a Backup Containing Aspect Data on page 285.

Warning and Error MessagesThe warning and error messages that can be generated by the 800xA backup/restore utility are described in the following topics. Suggested solutions are also provided.

Failed to serialize aspect

Example

Tue Jul 01 08:41:03 2003 [Error]: Failed to serialize aspect 'Operator Messages Link Display' on object 'Web System Workplace'

Reason

It is not possible for the Backup function to save the aspect data.

Solution

Check in the system for the behavior of this aspect.

ASO object class xxxx did not implement IAfwAspectSystemObject. Failed to create ASO. Forgot to register dll?

Example

Tue Jun 10 19:02:17 2003 [Error]: ASO object class {7B7A13B3-8BB4-42A3-8289-987C579797C2}did not implement IAfwAspectSystemObject Failed to create ASO. Forgot to register dll?

Reason

This often occurs when a system extension is used, but not installed on the node from where the backup is taken. It can also happen if an update of a system extension has been installed, but not added to the system.

3BSE037410R4101 293

UnplacedObjects.afw Section 8 Backup and Restore

Solution

Install and add 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 placed in UnplacedObjects.afw and write a warming in the backup log, therefore, UnplacedObjects.afw is used for all objects which miss 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.

The system cannot find the path specified

Example

Error detected for aspect 'Empty A3P' of object 'Document Manager Templates/Document Manager File Templates/Drawings'

Tue Jun 08 00:43:30 2004 The system cannot find the path specified.

EbServiceHandler: Object Id = {9AFACBA5-6B6A-462A-9EDF-78765740CD52}, Aspect Id = {89F8A8C4-10F7-4874-B77D-A8E6445D5C93}

EbServiceHandler: Failed to load document into stream!

294 3BSE037410R4101

Section 8 Backup and Restore System Extension ´xxxx´ with id ´Guid` is not installed on this node

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).

System Extension ´xxxx´ with id ´Guid` is not installed on this node

Example

System extension 'Engineering Base' with id {B775BEA4-7859-4649-AE16-901790822886} is not installed on this node.

System extension 'AC800M Con 31SP1' with id {6F388AEC-E4FF-4614-AF80-1D37EC3B141F} is not installed on this node.

Reason

There is a system extension, which is not available in the node where the backup is taken, or which is not properly removed. The latter can be the case if AC800 Connect has been upgraded and the old version is still registered in Industrial IT 800xA.

Solution

Use a backup node where all system extensions are installed.

Timeout by External Service

Example

Thu Mar 04 02:34:55 2004 #1: Receiving files



3BSE037410R4101 295

Graphic aspect = xxx cannot be imported Section 8 Backup and Restore

Thu Mar 04 02:34:57 2004 #1: Finishing

Thu Mar 04 02:34:58 2004

Thu Mar 04 02:35:08 2004 TimeOut by External Service

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.

Graphic aspect = xxx cannot be imported

Example

Mon Mar 29 19:52:32 2004 [Error]: Object = WI Mezzanine Deck, graphic aspect = Page Prev cannot be imported. Source directory = d:\OperateITData\Temp\ActiveGraphics\{800BA917-3D7F-44B6-B647-90C4B06A98FA}.restore.2.

Reason

Could be different reasons.

Solution

Check the source directory specified in the error message. The log file in this directory should give some hints of what caused the problem.

296 3BSE037410R4101

Section 8 Backup and Restore Too many aspects of category

Too many aspects of category

Example

Sat Jun 05 17:04:33 2004: Too many aspects of category 'Name' on object '{82416BDF-5464-4422-A443-35E08E1065BE}'

Sat Jun 05 17:04:34 2004: Import/Export Error: Object {82416BDF-5464-4422-A443-35E08E1065BE} ({82416BDF-5464-4422-A443-35E08E1065BE}) - E_AFW_AD_TOO_MANY_ASPECTS (0x8abb081b) To many aspect of a specific type.

Sat Jun 05 17:04:34 2004: Failed to restore file C:\BWSC\BWSC Full Backup; 2004-06-03; 03-00\Control Structure28.afw. The importer returned hr = 0x8abb081b

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.

Aspect category is missing

Example

Sat Jun 05 16:41:27 2004: Aspect '{506D9D24-E22A-4EDB-AFB0-0753B6DB6990}' on object 'SoftPoint Object Types' cannot be restored because the aspect category is missing

Sat Jun 05 16:41:27 2004: ObjectId: {9574CC3B-0E5E-4B14-A83E-F483CCDE6E44}

3BSE037410R4101 297

Unknown transaction error Section 8 Backup and Restore

Sat Jun 05 16:41:27 2004: AspectId: {506D9D24-E22A-4EDB-AFB0-0753B6DB6990}

Reason

One or more aspect category has been removed, while there are aspects of that category still in the system. This inconsistency was present in the system when the backup was taken.

Solution

If the aspect category has been removed then these aspects may not be of interest any more. Check if the aspects are needed. If not, ignore this message.

Unknown transaction error

Example 1

Mon Apr 19 13:39:40 2004: Unknown transaction error

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}

298 3BSE037410R4101

Section 8 Backup and Restore Unknown transaction error

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.

3BSE037410R4101 299

Unknown transaction error Section 8 Backup and Restore

300 3BSE037410R4101

Section 9 System Check

System Check ListTo get full benefit of the system, it needs to be inspected on regular basis.Some useful recommendations are listed below:

On an 800xA System node:

• Look at the system alarm, system event, and operator message lists for information from the 800xA System.

• Open the System Status Viewer for the Service Structure or the Node Administrator Structure to see if any 800xA System service is not in service or standby state.

On all 800xA System nodes:

• Open the Service Connection view to see the status of the service provider connections for the node.

• Open the Task Manager and add following process columns to the default: Peak Memory Usage, USER Objects, Virtual Memory Size, Handle Count, Thread Count and GDI Objects.

• Make a window dump of the Task Manager Processes tab when the system is started and use this dump as reference to compare later on to see if there are any significant deviations.

• While in the task manager switch to the performance tab. Look in the Commit Charge square in the lower left corner. There are three values:

– Total - Sum of all memory currently allocated by your processes.

– Peak - Highest total value achieved during the session.

– Limit - Total amount of memory, physical and virtual, available.

3BSE037410R4101 301

Section 9 System Check

It is recommended that the Total/Commit Charge always are kept below the total physical memory; i.e., more physical memory is added when necessary.

Allocating more virtual memory can give you additional problems. Too much virtual memory will result in a case where process data will need to be swapped back and forth between disk and actual memory which will decrease performance significantly.

If Peak/Commit Charge, at any time, reaches the Limit/Commit Charge value you have an insufficient memory problem that might cause the processes to crash or just stop working.

• Go to Start > Settings > Control Panel > Administrative Tools > Event Viewer and check for Errors Messages in the Application Log and the System Log.

• Go to Start > Settings > Control Panel > Administrative Tools > Computer Management > Disk Defragmenter to see if defragmentation is required.

• Go to Start > Settings > Control Panel > Administrative Tools > Computer Management > Device Manager and check that no hardware errors are indicated.

• Open the Windows Explorer and search for PPA crash dump files (*exception.txt).

If there is inconsistency or strange behavior in the system, close and reopen a Workplace, restart a service or, in the worst case, restart a whole node.

It is also very important to do these inspections after a major disturbance in the system such as lost main part of the communication or many servers have been down (power, restart…). After a disturbance, check the Workplaces if there are red crosses over alarm bands or alarm sequence bars (suspect that the alarm and event list not updates properly), or white crosses on red background in process displays or that trend displays not updating. In these cases, return to operation by closing and reopening the Workplace.

302 3BSE037410R4101

Section 9 System Check System Status Viewer

System Status Viewer

Interface

The System Status Viewer shows status of different parts in the 800xA System. System status information can be available for both software processes and hardware units. The System Status Viewer aspect can be located on objects on different levels in all structures.

The System Status Viewer shows all objects that provide system status information. It reflects the structure of the Control System. All status information in the System Status Viewer is updated dynamically when a change of status occurs.

Figure 188. System Status Viewer - An Overview

Next ErrorPrevious Error

Find Child ErrorShow Details

View Mode ButtonShow All Errors

Refresh Alarm and Event

Help Button Propagated

3BSE037410R4101 303

System Status Viewer Configuration Section 9 System Check

System Status Viewer Configuration

Configuration of the viewer can be made in two ways. Some settings are made locally for a specific instance of the System Status Viewer. The rest of the settings are made per user and affects all System Status Viewers.

The local settings for a specific System Status Viewer are:

• Default StructureIf the object that holds the System Status Viewer aspect is a member of several structures, it is possible to select which structure that will be displayed first.

• Initial expansion of Object TreeBy configuring the initial expansion of tree, it is possible to control how the object tree in the viewer should be expanded.

Figure 189. Configuration View

304 3BSE037410R4101

Section 9 System Check System Status Viewer Configuration

When Enable local expand level is checked, the settings for expansion done in the Config View are effective, otherwise the default settings done in User Profiles are effective.

The settings per user is made on the Status Viewer Profile Values aspect, located in the User Structure.

Configuration can only be made if the System Status Viewer aspect is not inherited from an object type.

3BSE037410R4101 305

System Status Viewer Configuration Section 9 System Check

306 3BSE037410R4101

Section 10 Single Node Replacement

IntroductionThis section describes the general procedures that must be performed in order to recover from a node failure in complete SV 4.0, 3.1 SP2, and 2.1 800xA systems (including all functional area information). These procedures will be expanded to include additional information as it becomes available.

Recovery PathsThe three possible recovery paths discussed in this section are:• Reinstall Like New.• Reinstall and Restore.• Recover Node (detailed in this document).

The path chosen depends on the amount of information available for the node and hardware being replaced.

Reinstall Like New

This is the recommended path when no acceptable disk image or backup of system function information is available.

Software will need to be installed on the replacement node like it is being installed for the first time. In SV 4.0 and 3.1 SP2 systems, use the existing system planner file and the System Installation Program to simplify the installation process.

The general installation procedure is:

1. Clean (format) the repaired or replacement computer.

2. Install the appropriate Windows operating system.

3. Install the removable media containing the system planner file for this node.

3BSE037410R4101 307

Reinstall and Restore Section 10 Single Node Replacement

4. Install the System Installation Program.

5. Start the System Installation Program.

6. Following the instructions to load the:

a. Remaining Windows software.

b. Required third party software.

c. Required 800xA software.

Refer to the IndustrialIT 800xA System, Automated Installation, the IndustrialIT 800xA System, Installation or the IndustrialIT 800xA System, Post Installation Setup instruction for more detailed information.

Reinstall and Restore

This is the recommended path when:

• No acceptable disk image exists but an acceptable backup of the system function information resident to the failed node is available. Use the Backup and Restore functions and/or the Import and Export functions to recover the required information

- or -

• An acceptable disk image is available but the whole computer needs to be replaced and the replacement is not identical (hard disk drives are too small) to the failed computer. Use the disk imaging software to recover the required information from the disk image.

Software will need to be installed on the repaired or replaced node like it is being installed for the first time (Refer to Reinstall Like New on page 307). In SV 4.0 and 3.1 SP2 systems, use the existing system planner file and the System Installation Program to simplify the installation process.

Refer to the IndustrialIT 800xA System, Automated Installation, the IndustrialIT 800xA System, Installation or the IndustrialIT 800xA System Post Installation Setup instruction, for more detailed information. Refer to the appropriate 800xA System instruction (IndustrialIT 800xA System, Configuration or IndustrialIT 800xA System, Operator Workplace Configuration) for detailed information about Backup, Restore, Import, and Export functions.

308 3BSE037410R4101

Section 10 Single Node Replacement Recover Node

Refer to the documentation provided with the disk imaging software for detailed information about recovering data from a disk image.

Recover Node

This is the recommended path when:

• An acceptable disk image is available.

- and -

• An identical computer (hard disk drives may be larger) is used to replace the failed computer or only the hard disk drive needs to be replaced.

Use the following information and procedures to recover the node.

Disk ImageA node specific disk image should be taken after the 800xA system software has been installed and the post installation setup procedures have been performed. The creation of this image is discussed in the 800xA System Installation instruction. Restoration of this disk image will recover all the information and software components that were installed when the image was taken. These components are the operating system, third party software, 800xA software, some function specific information, etc.

Combined Node TypesThe following combinations of node type, connectivity software, and application software are allowed in 800xA systems.

• Aspect Server and connectivity server software.

• Aspect Server, connectivity server software, and Asset Optimization server software.

• Batch, Manufacturing, and Information Management software.

When replacing these nodes, restore the base node type first and then restore connectivity and application specific information.

3BSE037410R4101 309

Aspect Server Section 10 Single Node Replacement

Aspect ServerThe Aspect Server is the central part of an 800xA system. Most 800xA systems are engineered to contain redundant Aspect Servers because recovering fully from losing the only Aspect Server in a single Aspect Server system is very complicated. Optimally, the Aspect Server should not contain other connectivity server or application server software with the exception of Central Licensing System, Engineering Studio, and PNSM (PC, Network, and Software Monitoring) software.

Use the following procedures to restore a failed redundant Aspect Server in System Version 3.1 SP2 and 4.0 systems.

To restore a redundant Aspect Server:

1. Repair or replace the failed node.

2. Remove the failed node from the Domain Server files:

a. Select Start > Programs > Administrative Tools > Active Directory Users and Computers on the primary (or only) Domain Server node.

b. Select the active domain.

c. Select Computers.

d. Right click the name of the failed computer.

e. Select Delete on the pop-up menu.

f. Select Start > Programs > Administrative Tools > DNS.

g. Select DNS\primary_domain_controller_name\Forward Lookup Zones\domain_name.

h. Right click the failed node.

i. Select Delete on the pop-up menu.

j. Select DNS\primary_domain_controller_name\Reverse Lookup Zones\1st_three_segments_of_IP_address_in_reverse_order.

k. Right click the failed node (listed as last segment of IP address).

l. Select Delete on the pop-up menu.

3. Remove the failed node from the network.

310 3BSE037410R4101

Section 10 Single Node Replacement Connectivity Servers

4. Restore a previously saved disk image.

5. Remove the node from the domain on the node itself.

6. Connect the node to the network and to the Windows domain.

7. Open the Configuration Wizard on the node being restored and select Connect Node.

8. Select the appropriate Aspect Server. This will connect the restored node to the 800xA system.

9. Verify connection with the Service Connection Viewer (use the appropriate tray icon).

10. Check CPU load using the Task Manager utility. When the processor load settles, the connection is finished.

11. When restoring a CLS Client node, it may be necessary to reselect the CLS Server node using the License Status Viewer window.

Connectivity ServersThe following types of connectivity servers are described in this replacement procedure.• AC 800M.• Foundation Fieldbus.• PROFIBUS and HART.• 800xA for Advant Master.• 800xA for Harmony.• 800xA for Melody.• 800xA for MOD 300.• 800xA for SafeGuard.• 800xA for DCI.

Verify the reverse and forward lookup zone for the DNS are correct. Also verify that the DNS name and IP address of the node are still correct.

3BSE037410R4101 311

AC 800M Section 10 Single Node Replacement

AC 800M

AC 800M nodes can contain the following software:• AC 800M Connect (on all AC 800M nodes).• OPC Server for AC 800M.• Control Builder M.

AC 800M Connect

To restore individual SB 2.1, SV 3.1 SP2, and SV 4.0 AC 800M Connect Connectivity Server nodes:

1. Remove the failed computer from the domain.

2. Disconnect the failed computer from the network.

3. Restore the saved disk image to the replacement computer.











If an error message is received while trying to login after the node is restored, remove the node from the domain and then add it to the domain.

Verify the reverse and forward lookup zone for the DNS are running.

312 3BSE037410R4101

Section 10 Single Node Replacement AC 800M


k. Right click the failed node which is listed as last segment of IP address.


5. Connect the replacement computer to the network.

6. Configure the name of the replacement computer to be the same as the failed computer.

7. Add the replacement computer to the domain.

8. Confirm that the name and IP address are correct for the replacement computer.

9. Verify that the System Software User Settings action (within the Configuration Wizard) is correctly applied to the node.





14. Reset any objects, programs, etc. that were left in an undesirable state to a state that will allow normal operation. Refer to the appropriate functional area documentation for more information.

15. Stop all processes that were left incomplete by the failed node. Refer to the appropriate functional area documentation for more information.

OPC Server For AC 800M

If OPC Server for 800M software was installed on the repaired/replaced node:

1. Start the OPC Server Setup Wizard on the repaired/replaced node.

3BSE037410R4101 313


2. Configure the appropriate OPC Server for AC 800M settings (listed in Table 14) to the same values used on the repaired/replaced node.

3. Copy the backed up OPC Server configuration files (*.cfg file extension) to the working directory (C:\ABB Industrial IT Data\Control IT Data\OPC Server for AC 800M 4.0 for example).

4. Copy the backed up system setup file (systemsetup.sys) to the working directory (C:\ABB Industrial IT Data\Control IT Data\OPC Server for AC 800M 4.0 for example).

Control Builder M

If Control Builder M software was installed on the failed node:

1. Start the Control Builder M Setup Wizard on the repaired/replaced node.

2. Configure the appropriate OPC Server for AC 800M settings (listed in Table 15) to the same values used on the repaired/replaced node.

3. Copy the backed up system setup file (systemsetup.sys) to the working directory. The working directory is usually C:\ABB Industrial IT Data\Engineer IT Data\Control Builder M Professional 4.0 (SV 4.0), 3.4/3 (SV 3.1 SP2), or 3.2 (SV 2.1).

4. Copy the backed up privclasses.sys and privusers.sys files to the working directory (typically C:\ABB Industrial IT Data\Control IT Data\OPC Server for AC 800M 3.2) for SV 2.1 systems.

Table 14. OPC Server for AC 800M Settings

System Version Settings

4.0 MemoryService Account

3.1 SP2 MemoryService AccountRNRP

2.1 MemoryRNRP

314 3BSE037410R4101

Section 10 Single Node Replacement AC 800M

Control Source Code. Control Builder source code must be manually restored after a node failure in SV 2.1 systems. The source code is stored in the Aspect Directory in SV 4.0 and SV 3.1 SP2 systems

PROFIBUS-DP Hardware Definition Files. Some Control Projects (not all) contain user-defined Hardware Definition (.hwd) files. These files must be manually copied from another Control Builder client to the restored/replaced Control Builder M node. The .hwd files are typically located in the Control Builder M Projects directory (usually C:\ABB Industrial IT Data\Engineer IT Date\Control Builder M Professional 3.2\Projects\project_name\).

Recover Source Code Server. To recover from a failed Source Code Server:

1. Temporarily designate a Source Code Client (which holds valid source code) as the Source Code Server:

a. Open the Project Explorer on the Source Code Client node.

b. Select Tools > Setup > Station > Source Distribution.

c. Enable the Function as Source Server option.

d. Click OK.

2. Temporarily designate the repaired/replaced node as a Source Code Client:

a. Open the Project Explorer on the repaired/replaced node.


c. Disable the Function as Source Server option.

Table 15. Control Builder M Settings

System Version Settings

4.0 MemoryLanguage

3.1 SP2 and 2.1 MemoryLanguageRNRP

3BSE037410R4101 315


d. Enter the IP address of the client currently functioning as the Source Code Server in the Source Server Identity field.

e. Click OK.

3. Recover the source code from the current Source Code Server:


b. Select File > Distributed Projects > Open Project From Server.

c. Select the appropriate project.

d. Click OK.

4. Designate the current Source Code Server as a Source Code Client:

a. Open the Project Explorer on the current Source Code Server node.


c. Disable the Function as Source Server option.

d. Click OK.

5. Designate the repaired/replaced node as the Source Code Server:



c. Enable the Function as Source Server option.

d. Click OK.

Recover Source Code Client. To recover source code from the Source Code Server to the Source Code Client:

1. Open the Project Explorer.

2. Select File > Distributed Projects > Open Projects From Server.

3. Select the appropriate project.

4. Click OK.

316 3BSE037410R4101

Section 10 Single Node Replacement FOUNDATION Fieldbus

FOUNDATION Fieldbus

Use the following procedures to restore FOUNDATION Fieldbus nodes.

SV4.0 Procedures

Nonredundant Aspect Server Containing Local HSE Subnet Configuration. To restore an individual nonredundant Aspect Server node:




4. Restore the saved disk to the replacement computer.














3BSE037410R4101 317

FOUNDATION Fieldbus Section 10 Single Node Replacement



6. Configure the node to have the same DNS name and IP address as the failed node.








14. Stop all processes that were left incomplete by the failed server. Refer to the appropriate functional area documentation for more information.

15. Restore application-specific information from the most recent node backup.

Nonredundant Aspect Server (HSE Subnet Configuration on different node).

Simply restoring a recent 800xA system backup can possibly overwrite actual HSE Subnet configuration changes.


318 3BSE037410R4101


To determine whether the 800xA system backup contains the latest configuration changes and restore a nonredundant Aspect Server:

1. Open a Plant Explorer workplace on another node containing the HSE Subnet configuration.

2. Select the Control Structure.

3. Select the HSE Subnet\FFUpload aspect.

4. Select the HSE Upload tab.

5. Check the time found in the Version Information\HSE Subnet field.

6. Determine if any changes have been made from the time the backup was made.

7. If the 800xA system backup does contain the latest configuration changes, proceed to the next step. If the 800xA system backup does not contain the latest configuration changes, copy all files (*.pro, *.bak, *.log files and the libraries.hwm file) from HSE Subnet configuration folder to a temporary folder and then proceed to the next step.













3BSE037410R4101 319



















320 3BSE037410R4101


22. Restore the most recent 800xA system backup.

23. If the 800xA system backup did not contain the latest configuration changes, copy all files (*.pro, *.bak, *.log files and the libraries.hwm file) from temporary folder to the HSE Subnet configuration folder. Overwrite the existing files.

Redundant Aspect Server (or Any Node) Containing Local HSE Subnet Configuration. The general restore procedure restores only 800xA System data of the node (e.g. for a redundant aspect server). The HSE Subnet configuration data must be restored manually.
















3BSE037410R4101 321















15. Restore HSE Subnet configuration manually from a recent 800xA system backup:

a. Create and share the folder for the HSE Subnet configuration of Fieldbus Builder FF according to the instructions in the 800xA - System, Post Installation Setup instruction.


322 3BSE037410R4101


b. Select directory of the most recent 800xA system backup. The node and path of the backup is shown on the Maintenance Structure\Backup object\Storage tab in the Plant Explorer Workplace.

c. Verify that the directory contains a folder with the name 1B0397BA-124C-4A0A-B3FE-AEE68E8EDF96. The number is the GUID of the FBBFF system extension and is identical for all system versions.

d. Copy all *.pro files from that folder to the HSE Subnet configuration folder.

e. Remove the ReadOnly attribute from all the *.pro files copied to the HSE configuration folder.

Redundant Aspect Server (HSE Subnet Configuration on different node).

Refer to SV4.0 Procedures on page 317.

FOUNDATION Fieldbus Connectivity Server (OPC Server FF), Redundant FOUNDATION Fieldbus Connectivity Server (OPC Server FF), FOUNDATION Fieldbus Connectivity Server as part of any combined server (CS + AS, CS + AS + AO). To restore a FOUNDATION Fieldbus Connectivity Server:











3BSE037410R4101 323




















324 3BSE037410R4101



15. Restore manually any system setting changes done after last node backup (e.g. DCOM settings).

16. Restore user changed registry settings of OPC FF if applicable (as documented in the 800xA - Device Management FOUNDATION Fieldbus, Configuration instruction)

17. Download project data into the OPC Server FF node with Fieldbus Builder FF:

a. Open the HSE Subnet project that was affected by the repair/replacement action.

b. Go into commissioning mode.

c. Select the OPC Server FF node.

d. Execute command Object\Download.

Client nodes (Fieldbus Builder FF engineering nodes). To restore a client node:












3BSE037410R4101 325



















326 3BSE037410R4101



15. Manually restore any additional user specific FF configuration data exported from Fieldbus Builder FF by copying these export files back to the desired location.

Configuration data from Fieldbus Builder FF may be:

– Partial exports of FBB FF configuration (Linking Device nodes, H1 Link nodes, Function Block Application Diagrams etc.).

– Parameter values of block instances, HSE Subnet objects, HSEHostCI860 objects.

SV3.1 Procedures

If the system has been updated to SV3.1/2 and FOUNDATION Fieldbus Device Integration Version 3.1.0/2 Rollup 1 and Rollup 2, use the SV4.0 replacement procedures.

If the system has not been updated to SV3.1/2 and FOUNDATION Fieldbus Device Integration Version 3.1.0/2 Rollup 1 and Rollup 2, the HSE Subnet configuration files (*.pro files) do not exist separately in the Backup folder and the project files are implicitly contained in the afw files of the 800xA system backup.

In this case, the scenarios described in section of SV4.0 procedures cannot be applied to the following nodes:

• Redundant aspect server with local HSE Subnet configuration folder failed.

• Any node type with local HSE Subnet configuration folder failed.

Instead apply the following procedure to these nodes:






3BSE037410R4101 327






















328 3BSE037410R4101

Section 10 Single Node Replacement HART and PROFIBUS





15. Create and share the folder for the HSE Subnet configuration of Fieldbus Builder FF according to the instructions in the 800xA - System, Post Installation Setup instruction.

16. Import (using the Export / Import tool) the HSE Subnet Upload aspect to restore the contained HSE Subnet configuration files (*.pro files) with the exception of the file libraries.pro. If the time stamp is identical, use the Force option during the import to overwrite the existing files.

17. When the import is finished, a file libraries_TEMP.pro is created in the HSE Subnet configuration folder. Rename this file to libraries.pro.

18. Remove the ReadOnly attribute from all *.pro files if necessary.

HART and PROFIBUS

Use the following procedures to restore HART and PROFIBUS nodes.

SV4.0 and 3.1 SP2 Procedures

Nonredundant Aspect Server Containing HART/PROFIBUS Connectivity Server. To restore an individual nonredundant Aspect Server node:




3BSE037410R4101 329

HART and PROFIBUS Section 10 Single Node Replacement





















330 3BSE037410R4101








15. Perform the following actions as detailed in the PROFIBUS/HART Device Integration - Configuration instruction:

– Install all required DTMs.

– Configure DCOM settings for device integration and DTMs.

– Configure the required shared folder.

– Start the configure OPC Server process from the Fieldbus Management aspect.

Redundant Aspect Server Containing HART/PROFIBUS Connectivity Server.

To restore an individual redundant Aspect Server node:






3BSE037410R4101 331






















332 3BSE037410R4101










– Start the synchronization process from the Fieldbus Management aspect (SV 4.0 only).

– Start the configure OPC Server process from the Fieldbus Management aspect (SV 3.1 SP2 only).

Redundant PROFIBUS/HART Connectivity Server. To restore a redundant PROFIBUS/HART Connectivity Server:








3BSE037410R4101 333





















334 3BSE037410R4101









– Start the synchronization process from the Fieldbus Management aspect (SV 4.0 only).

– Start the configure OPC Server process from the Fieldbus Management aspect (SV 3.1 SP2 only).

Client Nodes (Fieldbus Builder PROFIBUS/HART Engineering Nodes). To restore a client node:









3BSE037410R4101 335





















336 3BSE037410R4101




15. Perform the following actions as detailed in the PROFIBUS/HART Device Integration - Configuration instruction:– Install all required DTMs.– Configure DCOM settings for device integration and DTMs.

SB2.1 Procedures

To restore a PROFIBUS/HART Connectivity Server or Client node:














3BSE037410R4101 337



















338 3BSE037410R4101

Section 10 Single Node Replacement 800xA for Advant Master

– Install all required DTMs.– Configure DCOM settings for device integration and DTMs.

800xA for Advant Master

To restore individual SB 2.1, SV 3.1 SP2, and SV 4.0 800xA for Advant Master Connectivity Server nodes:


















3BSE037410R4101 339

800xA for Advant Master Section 10 Single Node Replacement













16. Copy the three backed up RTA Board configuration files to the \..\Program Files\ABB Industrial IT\Operate IT\AC 400 Connect\AdvantBase\Data \RTA\Init folder. Be sure to overwrite any existing files.

17. Restore network configuration settings by setting network and node numbers to those recorded during backup.

Before restoring these files, make sure the node being restored is running the same character conversion language used by the node from which the files were backed up.

340 3BSE037410R4101

Section 10 Single Node Replacement 800xA for Harmony

18. Restore time server settings by changing the REVERSED_SYNC_MODE registry parameter to the value recorded during backup.

800xA for Harmony

Use the following procedures to restore Harmony Client, Harmony Configuration Server, Primary Harmony Connectivity Server, and Secondary Harmony Connectivity Server nodes.

To restore an individual node:














Do not use a SQL Server generated backup done through a Maintenance Plan or manually through the SQL Enterprise Manager for the restore operation. The Harmony Connect backup/restore utility does not support this format. Ensure that your Maintenance Procedures include a Harmony Connect backup utility generated backup each and every time you do a backup of your Aspect System. These two backups must be synchronized at the time of a restore operation.

3BSE037410R4101 341

800xA for Melody Section 10 Single Node Replacement








9. Verify connection with Service Connection Viewer (use the appropriate tray icon).


11. If the node being restored contains the Configuration Server:

a. Log into the local service account.

b. Select Start > All Programs > ABB Industrial IT 800xA > 800xA for OCS Systems > Harmony > Configuration > Restore Configuration.

c. Click Connect.

d. Choose the backup file to restore.

e. Click Restore.

800xA for Melody

Use the following procedures to restore a System Version 4.0 Melody Operator Workplace, Connectivity Server, and Configuration Server node:

To restore an individual node:


342 3BSE037410R4101

Section 10 Single Node Replacement 800xA for Melody



















If the node being restored is the Melody Configuration Server node, stop the Server Aspect Controller in the Service Structure to avoid automatic synchronization of the obsolete Configuration Server database of the restored disk image.


3BSE037410R4101 343

800xA for MOD 300 Section 10 Single Node Replacement

7. Open the Configuration Wizard on the node being restored and select Connect Node. This step is not required for Melody Configuration Server nodes.

8. Select the appropriate Aspect Server. This will connect the restored node to the 800xA system. This step is not required for Melody Configuration Server nodes.

9. Verify connection with Service Connection Viewer (use the appropriate tray icon). This step is not required for Melody Configuration Server nodes.


11. If the node being restored is the Melody Configuration Server node:

a. Log into the local service account.

b. Select Start > All Programs > ABB Industrial IT 800xA > 800xA for Melody > Configuration > Restore Configuration.

c. Click Connect.

d. Choose the backup file to restore.

e. Click Restore and follow the instructions of the Backup and Restore tool.

f. After successful restoration of the Melody Configuration Server, reboot all Melody Connectivity Servers one at a time.

g. Restart the Server Aspect Controller in the Service Structure.

800xA for MOD 300

Use the following procedures to restore a MOD 300 Connectivity Server node. The MOD 300 function is only available for SV 4.0 systems.

The MOD 300 Connectivity Server does not have any configuration or process data that must be restored. If the MOD 300 Connectivity Server must be replaced:



The amount of time it takes to connect to the 800xA system depends on the type of node (Melody Connectivity Server or Melody Operator Workplace) being restored.

344 3BSE037410R4101

Section 10 Single Node Replacement 800xA for MOD 300





















3BSE037410R4101 345

800xA for SafeGuard Section 10 Single Node Replacement


11. Confirm settings for time synchronization, communications settings for DCN address and omf shared memory, redundant connectivity server name, and Hyper Terminal installation are correct according to the 800xA System Post Installation Setup instruction.

800xA for SafeGuard

To restore individual System Version 3.1 SP2 and 4.0 800xA for Safeguard Connectivity Server nodes:
















346 3BSE037410R4101

Section 10 Single Node Replacement 800xA for SafeGuard















16. Copy the three backed up RTA Board configuration files to the \..\Program Files\ABB Industrial IT\Operate IT\AC 400 Connect\AdvantBase\Data\ RTA\Init folder. Be sure to overwrite any existing files.

Before restoring these files, make sure the node being restored is running the same character conversion language used by the node from which the files were backed up.

3BSE037410R4101 347

800xA for DCI Section 10 Single Node Replacement

17. Restore network configuration settings by setting network and node numbers to those recorded during backup.

18. Restore time server settings by changing the REVERSED_SYNC_MODE registry parameter to the value recorded during backup.

800xA for DCI

Use the following procedures to restore System Version 4.0 DCI Connectivity Server and Composer CTK Engineering Nodes.

DCI Connectivity Server

Replacing the DCI Connectivity Server requires reloading the system from a saved disk image. All configuration information is kept in the Windows Registry or on the Aspect System Server and is restored with that node (or nodes).

To restore a DCI Connectivity Server node:














348 3BSE037410R4101

Section 10 Single Node Replacement 800xA for DCI










Composer CTK Engineering Node

The Composer CTK Engineering node is not an 800xA node but has backup procedures defined in the 800xA for DCI Configuration instruction that need to be performed regularly.

To restore a Composer CTK Engineering node:







3BSE037410R4101 349

Application Servers and Software Section 10 Single Node Replacement

5. Restore Composer backup information. Refer to the Composer CTK Configuration instruction for more information.

Application Servers and SoftwareThe following types of application servers and software are detailed in this replacement procedure.• Central Licensing System.• Engineering Studio.• PC, Network, and Software Monitoring.• Batch Management.• Information Management.• Asset Optimization.• Manufacturing Management.

Common Application Software

All 800xA System nodes (except the domain server) contain Central Licensing System (CLS) client, Engineering Studio, and PNSM software.

Central Licensing System

The Aspect Server is usually the license server and all other nodes contain CLS client software. Just restore these other nodes based on the type of node it is and the CLS client software will automatically be restored.

Engineering Studio

Engineering Studio software is loaded during the system installation process. There are no designated Engineering Studio nodes. Therefore, just restore the node based on the type of node it is and the Engineering Studio software will automatically be restored. Refer to the appropriate instruction for more detailed information.


Use the following procedures to restore a failed node that contained PC, Network and Software Monitoring (PNSM) client or server node in System Version 3.1 SP2 and 4.0 systems.

350 3BSE037410R4101

Section 10 Single Node Replacement Common Application Software

To restore a PNSM node:





















3BSE037410R4101 351

Batch Management Section 10 Single Node Replacement




11. When restoring a PNSM Connectivity Server node:

a. Restore any user defined assemblies, scripts, and resource files.

b. Restore and reload any Management Information Base files (MIBs) that were not part of the standard MIBs loaded with the software.

c. Restart the node.

Batch Management

Use the following procedures to restore a failed Batch Management client or server node.

Clients and Redundant Servers (SV 4.0, SV 3.1 SP2, and SB 2.1)

To restore an individual Batch client or redundant server node:

1. Remove the failed computer (or computer containing failed operating system hard disk drive or corrupted operating system) from the domain.








352 3BSE037410R4101

Section 10 Single Node Replacement Batch Management




















14. Restart the secondary Batch Server.

3BSE037410R4101 353

Batch Management Section 10 Single Node Replacement

15. Restart the primary Batch Server.

All necessary information will be deployed to the new node and all services configured for the failed node are started on the replacement node.

Nonredundant Servers (SV 4.0, SV 3.1 SP2, and SB 2.1)

Nonredundant servers (and single node system) can be restored however, some information will be lost. How much data is lost depends on when the node was last backed up. In some cases, failure of a nonredundant server node will leave parts of the system in an incomplete state. Some manual actions may be required to clean up the system before it will function correctly.

To restore an individual Batch nonredundant server node:











Any running batch control recipes will be lost when the node fails. Be sure to restore the batch (SQL Server) database along with the rest of the batch information.



354 3BSE037410R4101

Section 10 Single Node Replacement Batch Management


















16. Restore application-specific information from the most recent node backup.

3BSE037410R4101 355

Information Management Section 10 Single Node Replacement

The server is now ready for normal operation.


Use the following procedures to restore a failed Information Management client or server node.

To restore individual SV 3.1 SP2 and 4.0 Information Management nodes:


















356 3BSE037410R4101

Section 10 Single Node Replacement Information Management











14. Reset any objects, programs, etc. that were left in an undesirable state to a state that will allow normal operation. In particular, review the SoftPoints, Scheduler, Calculations, Archive Services, and History Service services located in the Node Structure to determine if all objects and properties are operating as expected and set to the proper state. Refer to the appropriate functional area documentation for more information.


16. Verify that PAS services are running:

a. Enter PASGUI at a command prompt.

b. Verify all services listed in the Process Administration Services dialog have been started.

17. Select Start > All Programs > ABB Industrial IT 800xA > Information Mgmt > Configuration Assistant.

3BSE037410R4101 357


18. Select Create History Database under Information Management Configuration in the ABB 800xA - Information Management Configuration Assistant dialog.

19. Click Run Selected Configuration Tool.

20. Use the configuration wizard to recreate the necessary databases. Refer to the information used during initial installation to replicate database sizes, locations, memory space allocations, etc.

21. Select Create ODBC Data Source for the Oracle Database under Information Management Configuration.

22. Click Run Selected Configuration Tool.

23. Execute the instructions listed in the Configuration Instructions area of the dialog.

24. Select Set ADO Data Provider Startup Mode to AUTOMATIC under Information Management Configuration.

25. Execute the instructions listed in the Configuration Instructions area of the dialog.

26. Close the dialog.

27. ‘If a backed up History database is available, use PAS to stop all Information Management processes. If no History database backup is available, proceed to Step 41.

a. Enter PASGUI at a command prompt.

b. Click Stop All in the PAS dialog.

28. Ensure that no third-party applications access the Oracle database during the restore operation.

29. Stop the Inform IT History Service Provider:



Stopping PAS will stop the Inform IT History Service Provider; however, it is a good idea to perform the following to confirm it is stopped.

358 3BSE037410R4101

Section 10 Single Node Replacement Information Management



e. Click Apply.

30. Select:

Start > All Programs > ABB Industrial IT 800xA > Information Mgmt > History > Backup and Restore.

31. Verify Restore configuration from a backup file(s) is enabled in the Welcome to IM Historian Backup and Restore Utility dialog.

32. Click Next. The IM Historian Database Restore dialog appears.

33. Specify the location of the backup files in the Path of IM historian backup: field.

34. Click Next. The HsBAR Output Window appears.

35. Enable the Automatically close upon completion check box.

36. 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.

37. Click Finish when a message stating the execution is complete is displayed.

If the Progress Status dialog has warning messages with possible solutions, 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.

38. Start all processes under PAS supervision.

If you need to specify new mount points for file-based logs and/or a new Oracle tablespace definition file, click Browse.

3BSE037410R4101 359


39. Start the Inform IT History Service Provider:




d. Enable the Enabled option.

e. Click Apply.

40. 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.




e. Click Apply.

f. Enable the Enabled option.

g. Click Apply.

41. Restore other Information Management related files:

a. History Archive Data: For each archive device, copy the appropriate folders from the safe media to the location specified by the Device Filename.

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.

Starting PAS will start the Inform IT History Service Provider; however, it is a good idea to perform the following to confirm it is started.

360 3BSE037410R4101

Section 10 Single Node Replacement Asset Optimization

b. 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.

c. Reports: Restore any report template files created in Microsoft Excel, DataDirect, and/or Crystal Reports. Also restore report output files created as a result of running these reports via the Scheduling Services.

d. Desktop Trends: Restore trend display, ticker display, and tag explorer files.

e. Display Services: Restore the directories for custom users, as well as display and user element definitions.

f. DataDirect: Restore custom text files for object, object type, and attribute menus used on the DataDirect windows.

Asset Optimization

Use the following procedures to restore a failed Asset Optimization client or server node in System Baseline 2.1, System Version 3.1, and System Version 4.0 systems.

Backup Service Providers Configuration

Before the Asset Optimization node is removed from the 800xA system, be sure to export the service providers configured to run on the node. Export the service providers from another node in the system. If an Asset Optimization node is removed from an 800xA system, all the service providers assigned to such node will be automatically removed from the Service Structure.

Asset Optimization Services are:• AssetMonitoring Service (AO version 4.0)• Messenger Service• OptAOStartup Service (AO version 3.1)

To export the Service Providers running in a node:

1. Open Plant Explorer workplace.

3BSE037410R4101 361

Asset Optimization Section 10 Single Node Replacement

2. Navigate to the Service Structure.

3. Identify all the service providers running in the node to be removed.

4. Drag and drop the identified service providers objects in the Import/Export tool.

5. Save the resulting AFW file with the other files in your backup media.

Restore Procedure

To restore an Asset Optimization node:

















362 3BSE037410R4101

Section 10 Single Node Replacement Manufacturing Management





9. Verify connection with Service Connection Viewer (use the appropriate tray icon).


11. Import service provider configuration information from the AFW file using the Import/Export tool (select Import All from the Action menu).

12. Restore Asset Optimization backup information. Refer to the Backup and Restore information in the 800xA System Administration and Security instruction for details.

Manufacturing Management

Use the following procedures to restore a failed System Version 4.0 Manufacturing Management client or server node.

Client

To restore a Manufacturing Management client node:





The amount of time it takes to connect to the 800xA system depends on the type of node (Aspect Server, Connectivity Server or client) being restored.

3BSE037410R4101 363

Manufacturing Management Section 10 Single Node Replacement





















364 3BSE037410R4101

Section 10 Single Node Replacement Manufacturing Management



Server

To restore a Manufacturing Management server node:


















3BSE037410R4101 365

Manufacturing Management Section 10 Single Node Replacement









14. Verify that SQL Server and Internet Information Server (IIS) are functioning correctly.

15. Verify the EBRWEB application is configured in IIS.

366 3BSE037410R4101

Section 11 Operating System Update

Windows and 800xA System UpdatesIt is increasingly important to keep the automation systems abreast with available security updates. However, before an update is installed, it needs to be verified that it does not interfere with the operation of the automation system.

ABB validates security updates from Microsoft with respect to relevance to and compatibility with System 800xA. For relevant updates that Microsoft classify as "critical", the goal is to communicate to customers within 24 hours the plan for validating each update, and within 7 days the result of the validation. For this communication we use ABB SolutionsBank SolutionsBank/Field Alert, 3BSE038278, Microsoft Security Updates Validation Status (continuously updated), which also provides possibilities for customers to subscribe for e-mail notification on updates.

By properly upgrading an automation system installation with security updates, it is possible to avoid or mitigate damage from attacks by certain types of malicious software. However, the fact that a virus or worm at all finds it way into a system indicates, that there is an underlying security problem in the installation or in how it is managed. It is important to understand how a system becomes infected, and to take measures to prevent it. The white paper IndustrialIT Integrated Automation System - Network Security Considerations gives advice on security measures that should be considered by users of automation systems.

3BSE037410R4101 367

Section 11 Operating System Update

368 3BSE037410R4101

Section 12 Scheduling Reports

With the Scheduler it is possible to schedule and run jobs for IndustrialIT 800xA System applications. For example, you can run reports, event-driven data collection, and consolidation of Production Data Logs (PDLs) and message logs. In this section scheduling of reports are described. Jobs can be scheduled and run at different times and under different conditions as specified through aspects related to a job definition object.

PrerequisitesAs a prerequisite a Report must have been created. How to create a report are described in IndustrialIT 800xA System, Operator Workplace Configuration.

SchedulingSetup of scheduling is done in two steps:

• Creation of Service Group and Service Provider

and

• scheduling of the report.

Creating Service Group/Service Provider Objects

The first step is to create a Service Group and a Service Provider for the Scheduler. To do this follow the steps below:

1. Create the Service Group object under the applicable service container in the Service Structure, in this case Scheduler, Service.

To be able to run this function make sure that the Application Scheduler system extension is installed.

3BSE037410R4101 369

Scheduling Section 12 Scheduling Reports

a. Select Scheduler, Service, open the context menu and select New Object... See Figure 190.

Figure 190. Creating a new Service Group Object for Scheduler

370 3BSE037410R4101

Section 12 Scheduling Reports Scheduling

b. Assign a name to the new Service Group object. , see Figure 191.Click Create.

2. Create the Service Provider object under the new Service Group object.

Figure 191. Naming the Service Group Object

3BSE037410R4101 371


a. Select the new Service Group object, open the context menu and select New Object..., see Figure 192.

b. Assign a name to the new Service Provider object, see Figure 193. Click Create.

Figure 192. Creating a New Service Provider Object

372 3BSE037410R4101


3. Configure the Service Provider object to point out the node where the service (in this case Scheduler) must run (see Figure 194).

a. Select the Service Provider object.

b. Select the Service Provider Definition aspect in the aspect list.


d. Select the node where the service will run in the Node drop-down menu.

e. Check the Enabled check box.

Figure 193. Naming the Service Provider Object

3BSE037410R4101 373


f. Click Apply.

Scheduling Reports via the Application Scheduler

Adding a Job and Specifying the Schedule

To add a job follow the steps below:

1. Select the Scheduling Structure in the Plant Explorer, and expand Schedules and Jobs.

2. Select the Job Descriptions object and open the context menu. See Figure 195.

Figure 194. Service Provider Definition - Configuration Tab

374 3BSE037410R4101


3. Select New Object....

4. Select Job Description and assign the new Job Description object a name. See Figure 196.

Figure 195. Creating a New Job Description Object

Figure 196. Naming of the Job Description Object

3BSE037410R4101 375


5. Click Create. This creates the new job under the Job Description branch, and adds the Schedule Definition aspect to the aspect list.

6. Click on the Scheduling Definition aspect in the aspect list to display the configuration view. Choose schedule alternative by clicking on the Schedule drop-down menu. There are six scheduling alternatives. For all alternatives the Service Group must be chosen in the Service Group drop-down menu.

– Cyclic Schedule - a specific time interval.

Figure 197. Cyclic Schedule

376 3BSE037410R4101


– Periodic Schedule - a specific time interval between two specific dates.

– Weekly Schedule - a specific day of the week at a specific time.

Figure 198. Periodic Schedule

Figure 199. Weekly Schedule

3BSE037410R4101 377


– Monthly Schedule - a specific day of the month (for example 1st, 12ht 31st, or every day) at a specific time.

– List Schedule - a list of scheduled date and times.

Figure 200. Monthly Schedule

Figure 201. List Schedule

378 3BSE037410R4101


– Expression Schedule - the evaluation of an expression.

Figure 202. Expression Schedule

3BSE037410R4101 379


7. In this example (Figure 203) the scheduling is configured to run as a periodic schedule. Executed every hour starting July 2th at 17:00 (5:00PM), and continuing until July 9th at 17:00.

Adding and Configuring the Report Action

Actions are implemented as aspects on an object which is on or under a Job Description in the Scheduling Structure.

To add an action follow the steps below:

Figure 203. Scheduling Definition Aspect Configuration View - Periodic Schedule

380 3BSE037410R4101


1. Select the newly created job (in this case Report) and open the context menu. Select New Aspect.... See Figure 204.

2. Select Action Aspect and assign the new Action aspect a name. See Figure 205. Click Create.

Figure 204. Creating a New Action Aspect

Figure 205. Naming of the Action Aspect

3BSE037410R4101 381


3. Click on the Report Action aspect in the aspect list to display the configuration view.

4. Select Report Action in the Action drop-down menu. See Figure 206.

5. Select your template report in the Report Template Path text field. Browse to it by clicking the button with three dots.

6. Select in what way you want to have the output of the report, for example printed or in a log file, in the Output Options area.

7. Click Apply. The referenced report will execute according to the schedule defined in the associated job description object.

Figure 206. Report Action Aspect - Configuration View

382 3BSE037410R4101


For more information on how to use the Scheduler, see IndustrialIT 800xA, Information Management, Operation.

3BSE037410R4101 383


384 3BSE037410R4101

Section 13 Configuration Wizard

This section contains information about the Configuration Wizard tool.

Configuration Wizard

General

The Configuration Wizard is used for performing all the configuration and administration after a completed installation of the Operator Workplace. The Configuration Wizard handles both the server and client configuration.

The Configuration Wizard is started from the Start menu: Start > All Programs > ABB Industrial IT 800xA > System > Configuration Wizard.

You can browse through the steps by clicking the Back and Next buttons at the bottom of each dialog box. You can always return to a previous dialog box and make changes before applying the configuration data. No data will be applied until the last dialog box of each wizard task is reached, and you click Apply.

Configuration Wizard Start-up Window

When the Configuration Wizard is started it shows a start-up window from which all wizard tasks are started. The mandatory tasks are:

• System software User settings, configuration of the user groups

• System Administration, start, stop, delete and maintenance of systems

• Start Server, starts all manually started systems on a server

• Stop Server, stops all systems running on a server

• Create System, creation and initialization of systems

3BSE037410R4101 385

Configuration Wizard Section 13 Configuration Wizard

• Restore System, restores a saved system

• Maintenance, maintenance of the system

• Applog, applog configuration

• Connect Node, connect a client or server node to an existing system

• Disconnect Client, disconnect a client from a system.

Additional tasks may be added depending on connect families used. They are documented in product specific manuals.

Figure 207. Configuration Wizard Start-up Dialog Box

386 3BSE037410R4101

Section 13 Configuration Wizard System Software User Settings

System Software User Settings

The user administration is based on Windows user administration. To register a user as a Windows user, see Microsoft documentation.

When selecting the task System software User Settings, the dialog box shown in Figure 208 appears.

The first time the Configuration Wizard is started, only the System software User setting, Create System, Restore System, Applog and Connect Node tasks are visible. The System Administration, Start Server, Stop Server tasks are shown, on a server, when the system is created. The Disconnect Client task is shown on the client when you have connected it to a system.

If only System software User settings is visible, make sure you are a member of the IndustrialITAdmin group and have the right to administrate users on the local machine or on the Domain Controller, and repeat the task System software User settings.

3BSE037410R4101 387

System Software User Settings Section 13 Configuration Wizard

• System Admin, group

Members of this group have full rights in the System. Very few should be members of this group. By default this Windows group is named IndustrialITAdmin.

• System User, groupAll IndustrialIT 800xA System users must belong to this group. By default this Windows group is named IndustrialITUser.

• Service Account, used by System softwareAll System services run under this account. At startup the default account name is displayed. The Service Account must be local administrator on all machines.

Figure 208. System Software User Settings Dialog Box

388 3BSE037410R4101

Section 13 Configuration Wizard System Software User Settings

The entered groups are added to the Windows system if they do not already exist.If you want to register the System Administrator and System User groups in a domain other than the local machine, you have to enter the domain in the Domain field.

The windows groups created by the system are:

• IndustrialITAdmin (may be renamed during installation in the installation wizard)A member of this group runs all the services and has full access to the system.

• IndustrialITUser (may be renamed during installation in the installation wizard)All IndustrialIT 800xA users.

The user identity of the installer is added to the Windows groups IndustrialITUser and IndustrialITAdmin.

After the new Windows groups are created, users can be added to the groups.

Use the NetBIOS name of the domain, eg “PTTDOMAIN” and not the fully qualified domain name “pttdomain.abb.com”.

All users of the IndustrialIT 800xA System must be members of the System User group, which by default is, the Windows group IndustrialITUser.

Members of the System Admin group is running the system with full access, i.e. with the Security system disabled.

To deploy graphics you must belong to the IndustrialIT 800xA group Application Engineer and the Windows group Power User, or higher. You are thus recommended to give the Application Engineers that are expected to work with Graphics Builder the Windows Power User privilege.

Do not perform any configuration or administration work as 800xA Service user (the account reserved for use by 800xA system services). Major functions like system synchronization, audit trail and import/export will not work properly if configuration is performed while logged in as the Service user. It is recommended to disable the interactive login possibility for the Service user. It is also recommended that each person using the 800xA System has a user account with the appropriate user roles defined for this. This enables the possibility to synchronize or export the modifications performed by a certain person.

3BSE037410R4101 389

Create System Section 13 Configuration Wizard

Create System

When the system is created, using the Create System in the Configuration Wizard, the user currently logged in is added to the system as member of the IndustrialIT 800xA groups Everyone, System Engineer and Application Engineer. It is recommended that the same user account that installed the Operator Workplace also shall create the system.

1. Start the Configuration Wizard: Start > All Programs > ABB Industrial IT 800xA > System > Configuration Wizard.

System Software User Settings is part of the product installation but can, if needed, also be applied after the installation.

If a wrong setting, regarding to the windows accounts is detected, a padlock is shown in the tray icon (shown in the lower right corner of the screen). This is to prevent the user windows account to be locked.

See the padlock in the figure below.

In most cases the padlock is a result of an account verification that is not permitted by the domain controller. To remove the padlock symbol and release the lock state, reapply the System Software User Settings with the settings used when installing the product.

If you want the system to be in another language than US English, you should install the translation of the wanted language before you create a new system. Otherwise you must add the translation using Add System Extension. US English should be used when creating the system.

390 3BSE037410R4101

Section 13 Configuration Wizard Create System

2. Select Create System, and click Next.

3. The Create New System dialog box is displayed. It is used to create an IndustrialIT 800xA System on the Aspect Server node. Enter aName and a Description for the system, then select one of the radio buttons in the Server Type area.

Figure 209. Configuration Wizard - Create System

3BSE037410R4101 391


Server type Aspect Server is used for medium and large configurations when it is recommended to run Aspect Server and Connectivity Server on separate nodes. The Connectivity Server must then be added later on, see Nodes on page 412..

Server type Aspect Server and Connectivity Server is used for small configurations such as a Single node configuration. If this Server Type is marked the Aspect and Connectivity Server will run on the same node.

Figure 210. Create System Dialog Box

392 3BSE037410R4101


4. In the next dialog box you specify data directories, see Figure 211.

5. If not using RNRP click Next in the next dialog box. This will take you directly to Step 7. If using RNRP mark the Using RNRP check box. Enter the number of network areas used in the Number of areas text field. Click Next.

For more information about RNRP and areas see IndustrialIT 800xA System,Automation System Network, Design and Configuration.

Figure 211. Define Data Directories

Use a local disc on the Aspect Server node. Using a network disc will severely decrease the performance of the server and risk the entire system availability.

Figure 212. Configure RNRP - Using RNRP

3BSE037410R4101 393


6. In the next dialog box specify the primary and secondary network address for the first network area. If more than one network area was specified in the previous dialog box, one dialog box for each area will appear. Click Next.

Figure 213. Configure RNRP - Network Area Address

394 3BSE037410R4101


7. Now it is time to verify your settings in the Apply Settings dialog box, see Figure 214.

8. If the settings are ok, click Finish. The system will now be created and started. It may take some time.

Change of Password

If a system has not yet been created and the service account owner changes the Windows password, the first user who tries to start the Configuration Wizard has to known the new password. Only after the new password has been entered in the System software User settings dialog box, a system can be created.

Figure 214. Apply Settings Dialog Box

3BSE037410R4101 395

Connect Node Section 13 Configuration Wizard

Connect Node

A client has the possibility to work towards several systems. Before a client can work with a system, you must connect it to the system. This can be done in the Connect Node dialog box, in the Configuration Wizard on the client node.

In the Connect Node dialog box, go to the Connect to another System on Node drop-down menu and select the node, then click Next.

In the Connect to System dialog box (Figure 215), mark the Set as default system check box. This changes the default system for the client to be the same as the default system on the connected server.

Before a client is able to connect to a system, the Workplace client must be enabled from the server. This is done in the Add Client dialog box described in Nodes on page 406.

Figure 215. Connect to System Dialog Box

You can connect a client, and set up its default system from the server node, with the Add Client task, without having to go to the client node physically.

396 3BSE037410R4101

Section 13 Configuration Wizard System Administration

System Administration

General

To enter the Configuration Wizard task for system administration select the System Administration task in the Configuration Wizard and click Next, see Figure 207.In the Select System dialog box, Figure 216, select the system you want to administrate and click Next.

Figure 216. Select System Dialog Box

In this version only one system is supported.

3BSE037410R4101 397

System Administration Section 13 Configuration Wizard

The Configuration Wizard task for system administration appears.

The following administrative tasks are performed with this Configuration Wizard task:

• Systems

– Start, start of the services for a system

– Stop, stop of the services for a system

– Delete, delete a system

– Set Default, setting the default system

• Nodes

Figure 217. System Administration Dialog Box

398 3BSE037410R4101


– Remove Client, remove client nodes from a system

– Add Client, add client nodes to a system

– Remove Server

– Add Connectivity Server

– Add Redundant Server

• RNRP, configure RNRP addresses

• Users, add and remove users to/from a system

• System Extensions, add system extensions to a system

• Synchronize System, loads a synchronization package

• Rollback Synchronization, removes the last synchronized package

Systems

Start System. To start a system follow the steps below:

1. Go to the Configuration Wizard and select System Administration, click Next.

2. Mark the system you want to start and click Next.

3. Select Systems, click Next.

3BSE037410R4101 399


4. Select Start in the Systems dialog box and click Next.

5. Select the system that shall be started and click Next.

Figure 218. Systems Dialog Box

400 3BSE037410R4101


6. Click Finish in the Apply Settings dialog box. The system is now started.

Stop System. To stop a system follow the steps below:


2. Mark the system you want to stop and click Next.

3. Select Systems, and click Next.

4. Select Stop in the Systems dialog box and click Next, see Figure 220.

Figure 219. Start System - Apply Settings Dialog Box

3BSE037410R4101 401


5. In the next dialog box, select system and click Next.

6. Click Finish in Figure 221.

Figure 220. Configuration Wizard - Systems Dialog Box

Figure 221. Stop System - Apply Settings Dialog Box

402 3BSE037410R4101


Delete System.

To delete a system follow the steps below:

1. Go to the Configuration Wizard and select System Administration,and click Next.

2. Mark the system you want to delete. Click Next.

3. Select Systems and click Next.

4. Select Delete (see Figure 220), click Next.

When the system is deleted all application data is also deleted. If you want to save the data, you have to export it using the Import/Export tool, or you can perform a backup, see Section 7, Import/Export.

When making an upgrade from one version of the system to another you use the Backup and Restore function, see Section 8, Backup and Restore.

The following does not apply to a system running with redundant Aspect and/or parallel Connectivity Servers. Then you first have to stop the servers by choosing Stop Server in the Configuration Wizard Startup window before deleting the system. For more information about stopping the system see Systems on page 401.

3BSE037410R4101 403


5. Select one of the servers. Click Next, then click Finish.

6. Wait a few minutes, and when the Configuration Wizard appears again with the System dialog box the deletion of the system is completed.

7. Click Exit.

Set Default . If you want to have a certain system as default system follow the steps below

1. Select Set Default in the Systems dialog box.

Figure 222. Delete System - Apply Settings Dialog Box

404 3BSE037410R4101


2. In the next dialog box, choose which system that shall be the default system,

then click Next.

Figure 223. Systems Dialog Box

Figure 224. Default System Dialog Box

3BSE037410R4101 405



The selected system is now the default system, and the System Administration dialog box will appear.

Nodes

Remove Client. To remove a client follow the steps below:

1. In the System Administration dialog box(see Figure 217, select Nodes and click Next.

Figure 225. Set Default - Apply Settings Dialog Box

406 3BSE037410R4101


2. Select Remove Client, see Figure 226, and click Next.

3. Select the client that shall be removed. It is recommended to check the Update remote node check box, see Figure 227. If it is checked services will be stopped in the remote node. Click Next.

Figure 226. Nodes Administration Dialog Box

3BSE037410R4101 407


4. Click Finish when the Apply Settings dialog box is shown. The client is now

removed and the System Administration dialog box will appear.

Add Client. The Add Client dialog box is used to add client nodes to a server. You must run this command on the server node. Only nodes added this way can connect to the server.

To add a client follow the steps:

Figure 227. Remove Client Node Dialog Box

Before adding a client, make sure that the node to be added has 800xA System installed. It must also have the same system extensions as the Aspect Server.

408 3BSE037410R4101


1. In System Administration dialog box, Figure 217, select Nodes and click Next.

2. Select Add Client in Figure 228, click Next.

3. Select the node to add in the Client Node drop-down menu. , see Figure 229. Click Next.

Figure 228. Nodes Administration Dialog Box

Figure 229. Client Administration Dialog Box (Extract)

3BSE037410R4101 409


4. If the Update remote node check box is marked, this server will be added to the clients lists of servers. If the Set as default system check box is selected, the default system on the server will be set as the default system on the added node as well.

5. In the next dialog box, click Finish.

Remove Server.

1. Go to System Administration > Nodes and select Remove Server.

You can enable several clients without updating the remote node or set the default system. This makes it possible to later on connect the client to the server from the client node without having to do any work on the server node.

Note that clients do not give status information. This means that the System Status Viewer in the Node Administration Structure, only gives status from servers. See also System Status Viewer on page 303.

To stop and remove a Connectivity Server, begin with stopping the server, see Stop Server on page 427.

The remove server wizard task is also used if you shall change from a redundant configuration to a single configuration. See Change from Redundant to Single Configuration on page 186.

410 3BSE037410R4101


2. Select the server node to be removed in the Remove Server Node dialog box,

see Figure 231, and click Next.

Figure 230. Remove Server

Figure 231. Remove Server Node Dialog Box

3BSE037410R4101 411



Add Connectivity Server.

Perform the following steps to add a Connectivity Server:

1. In System Administration dialog box (Figure 217, select Nodes and click Next.

Figure 232. Remove Server - Apply Settings Dialog Box

Before adding a Connectivity Server, make sure that the node to be added has Operator Workplace installed. It must also have the same system extensions as the Aspect Server.

412 3BSE037410R4101


2. Select Add Connectivity Server and click Next.

3. Finally select Connectivity Server node from the drop-down menu in the Add Server Node dialog box. Click Next.

Figure 233. Nodes Administration Dialog Box - Add Server

It is recommended to check the Update remote node check box. If it is checked the server will be updated and activated.

3BSE037410R4101 413



Add Redundant Server.

Follow the steps below to add a redundant server:

1. In System Administration dialog box (Figure 217, select Nodes and click Next.

Figure 234. Add Server Node Dialog Box

Before adding a redundant server, which could be a Connectivity Server or an Aspect Server, make sure that the node to be added has Operator Workplace installed. It must also have the same system extensions as the primary Aspect Server.

414 3BSE037410R4101


2. Select Add Redundant Server, see Figure 233, and click Next.

3. In the next dialog box, a list of server nodes, both Aspect and Connectivity Servers, are shown. Select the server node to be duplicated, click Next.

Figure 235. Add Redundant Server Node - 1

3BSE037410R4101 415


4. In the Add Redundant Server Node dialog box select node in the Client Node drop-down menu and click Next.


RNRP

Follow the steps below to configure RNRP addresses:


2. Mark the system you want to start and click Next.

3. Select RNRP, click Next.

Figure 236. Add Redundant Server Node - 2

It is recommended to check the Update remote node check box. If it is checked the server will be updated and activated.

416 3BSE037410R4101


4. If using RNRP mark the Using RNRP check box. Enter the number of network areas used in the Number of areas text field. Click Next.

For more information about RNRP and areas see IndustrialIT 800xA, System, Automation System Network, Design and Configuration.

Figure 237. Configure RNRP - Using RNRP

3BSE037410R4101 417


5. In the next dialog box specify the primary and secondary network address for the first network area. If more than one network area was specified in the previous dialog box, one dialog box for each area will appear. Click Next.

6. Verify your settings in the Apply Settings dialog box, if the settings are ok, click Finish.

Users

For more detailed information about user administration refer to Microsoft documentation and/or Section 4, Security.

Operator Workplace User Administration. The Users icon in the Configuration Wizard activates the User Administration dialog box.

1. Open the Configuration Wizard.

2. Select System Administration and click Next.

Figure 238. Configure RNRP - Network Area Address

418 3BSE037410R4101


3. Select the system in which you want to configure users to and click Next. See Figure 216.

4. Select Users, see Figure 217. Now the User Configuration dialog box is displayed, see Figure 239.

The top window shows the IndustrialIT 800xA System users. Users can be added and deleted. To delete a user select the user in the top window and click Delete User. The Reset button is used to reset the group membership for a user to the state it was before any changes were made.

To add a Windows user to an IndustrialIT 800xA System group follow the steps:

1. Click the Add Windows Accounts... button.

Figure 239. User Configuration Dialog Box

You have to have both System Engineer and Application Engineer role to delete a user.

3BSE037410R4101 419


2. The next dialog box (Figure 240) shows the Windows users of the domain that is selected in the drop-down menu. Select the Windows users you want to add to the IndustrialIT 800xA System users and click Add.

3. Repeat until all Windows users you want to add are added to the Add Names area then click OK.

4. In the User Configuration dialog box, Figure 239, it is possible to select the IndustrialIT 800xA groups of which a Windows user must be member. Select Windows user in the top window and use the Remove and Add buttons to move IndustrialIT 800xA groups to the Member of field.

System Extensions

The System Extension dialog box is used to add a function to a system after its creation.

1. Open the System Extension dialog box by selecting System Extensions.in Figure 217


420 3BSE037410R4101


2. Select extension by checking the box for the wanted extension, see Figure 241.

3. Click Next.

4. A message box is displayed, showing system configuration specifications. Check the settings and click Finish if the settings are ok. The System Extensions will be added to the system and started.

Synchronize System

This task loads a synchronization package from a source system into a selected system.

Figure 241. System Extension Dialog Box

Installed system extensions are displayed in Figure 241

3BSE037410R4101 421


1. In the System Administration dialog box, Figure 217, select Synchronize System and click Next.

2. Select the system where the Synchronization package was created in the Select the source system drop-down menu. See Figure 242.

3. Select the desired synchronization package in the list and click Next.

4. In the difference report, verify that the objects and aspects that you want to synchronize are created, modified or deleted. See Figure 243. Click Next.

Figure 242. Select Synchronization Package Dialog Box

422 3BSE037410R4101



Rollback Synchronization

1. If you wish to remove the last synchronized package select Rollback Synchronization in the Configuration Wizard, see Figure 244.

Figure 243. Synchronize System - Difference Report

For detailed information see IndustrialIT 800xA System, Configuration.

3BSE037410R4101 423


2. Verify that the difference report is correct and click Next.

Figure 244. Configuration Wizard - Rollback Synchronization

424 3BSE037410R4101

Section 13 Configuration Wizard Start Server


Start Server

To start a server follow the steps below:

Figure 245. Rollback Synchronization

3BSE037410R4101 425

Start Server Section 13 Configuration Wizard

1. Select Start Server in the Configuration Wizard and click Next.

2. Select the server that shall be started. See Figure 247

Figure 246. Configuration Wizard - Start Server

Figure 247. Start Server Dialog Box

426 3BSE037410R4101

Section 13 Configuration Wizard Stop Server


Stop Server

To stop a server follow the steps below:

1. Select Stop Server in the Configuration Wizard and click Next.

Figure 248. Start Server - Apply Setting Dialog Box

3BSE037410R4101 427

Stop Server Section 13 Configuration Wizard

2. Select the server that shall be stopped in the Shut-down Server dialog box, and

click Next.

Figure 249. Configuration Wizard - Stop Server

Figure 250. Shut-down Server Dialog Box

428 3BSE037410R4101

Section 13 Configuration Wizard Restore System


Restore System

The restore will recreate an equivalent system, after a computer failure. It is also a recommended way to transfer data between one version of the system to another during an upgrade. A restore of a system is performed from the Configuration Wizard. The same or a later version of 800xA System and any System Extension that was installed when the backup was done, need to be installed before the system is being restored.

For more information about the task Restore System in the Configuration Wizard see 800xA System Restore on page 260.

Figure 251. Stop Server - Apply Setting Dialog Box

3BSE037410R4101 429

Maintenance Section 13 Configuration Wizard

Maintenance

Available under the Maintenance wizard task are functions to use when upgrading. You can also change the Service Account password. See Figure 252.

Figure 252. Configuration Wizard - Maintenance

If you want to change the Service Account when you already have a created system, there might become problems when starting the system. In that case make sure the new Service Account is correctly configured and added to the 800xA system.

To change password when you already have a created system, see Change Service Account Password on page 433.

430 3BSE037410R4101

Section 13 Configuration Wizard Maintenance

Stop all Processes

1. When upgrading all processes must be stopped. Mark the Stop all processes associated with the Process Portal A and click Next. See .

2. If you wish to restart Windows Explorer and Windows Filebrowser, click Yes in the next dialog box. See Figure 254.

Figure 253. Maintenance - Stop All Processes

3BSE037410R4101 431



Set Default Drive

When adding a server you might not want to have the installation files of the system on the same drive as the Workplace Data. You can change this by selecting Set Default Driver for remote actions, and select your own drive. See Figure 255.

Figure 254. Information Dialog Box

You must change the drive locally in the server before you can add it to the system.

432 3BSE037410R4101

Section 13 Configuration Wizard Maintenance

Change Service Account Password

After a change of the Service Account Password in the domain it is also necessary to change it in the Configuration Wizard.

1. Mark the Change Service Account Password radio button. See Figure 256.

Figure 255. Maintenance - Set Default Drive

3BSE037410R4101 433


2. The service account name is shown by default.

3. Type the new password (the password set in the domain) in the Password text field. Click Next.

4. Click Finish in the next dialog box. See Figure 257.

Figure 256. Maintenance - Change Service Account Password

434 3BSE037410R4101

Section 13 Configuration Wizard Applog

Applog

AppLog is a tool for getting information of an IndustrialIT 800xA System and for examining how the system is working.

Start AppLog

To configure the AppLog manually follow the steps below:

1. Select Applog in the Configuration Wizard and click Next.

2. Mark the Enable AppLog Service check box in the Applog configuration dialog box. Type the User ID with domain and password in the AppLog service settings area.

Mark the Autostart service on Windows startup check box. AppLog will then be started when Windows is started. Select Start in the Action area. See Figure 258.

Figure 257. Maintenance - Change Service Account Password - Apply Settings

The Applog tool is mainly used by ABB service engineers.

3BSE037410R4101 435

Applog Section 13 Configuration Wizard

3. Click Next.

4. Click Finish in the Apply Settings dialog box, see Figure 259.

Figure 258. Applog Configuration Dialog Box

436 3BSE037410R4101

Section 13 Configuration Wizard Applog

Stop AppLog

To stop the AppLog server follow the step below:


2. Select Stop in the Actions area, see Figure 260.

3. Click Next then click Finish. The AppLog server is now stopped.

Figure 259. Apply Settings Dialog Box

Figure 260. Actions Area - Stop

3BSE037410R4101 437

Disconnect Client Section 13 Configuration Wizard

Restart AppLog

To restart the AppLog server follow the steps below:


2. Select Restart in the Actions area, see Figure 261.

3. Click Next then click Finish. The AppLog server is now restarted.

Disconnect Client

This task is only available on a client node when the client is connected to a system. To disconnect a client follow the steps below:

Figure 261. Actions Area - Restart

438 3BSE037410R4101

Section 13 Configuration Wizard Disconnect Client

1. Select Disconnect Client in the Configuration Wizard, click Next.

2. Choose the system from which the client shall be disconnected, click Next.

Figure 262. Configuration Wizard Dialog Box

3BSE037410R4101 439

Disconnect Client Section 13 Configuration Wizard

3. Click Finish. The client is now disconnected from the system and the Configuration Wizard window will appear.

Figure 263. Disconnect from System Dialog Box

Figure 264. Disconnect Client - Apply Settings Dialog Box

440 3BSE037410R4101

Appendix A Default Security Settings forProcess Objects

AC 800M standard objects uses two default permissions as follows:

• Operateis used for settings which are expected to be used in the daily running of a plant. Examples are mode changes such as start, stop, go to auto mode, and go to manual mode. This also applies to parameters that are changed often such as a PID manual output value or a PID set point.

• Tuneis used for tuning parameters. Examples are PID parameters (gain, offset) filter time, and alarm levels.

Note, however, that the default behavior could have been changed by an engineer using the Property Attribute Aspect.This is an aspect that makes it possible to override existing permissions.The property Attribute Aspect can be placed on an Aspect Object Type; thus affecting all Objects of that type. It can also be placed on a single Aspect Object; thus only affecting that particular object. See Modification of 800xA Permissions for Process Objects on page 63 for further information.

3BSE037410R4101 441

Appendix A Default Security Settings for Process Objects

442 3BSE037410R4101

Appendix B Additions in Windowsadded by 800xA

Recommended Windows ConfigurationWindows User Groups:

• Everyonea global user group for All Users.

• Administratorsusers with complete and unrestricted access to the computer/domain.

• Power Usersusers with the authority to add and delete programs as well as run all programs, but they are restricted from making any system changes.

When installing an 800xA product, the following user groups are added to the Windows user groups if the installer is a member of Windows Administrator’s group (if the installer is NOT a Windows Administrator, see Windows User Groups in Domain Controller on page 44:

• IndustrialITAdmin (may be renamed during installation in the installation wizard). A member of this group runs all the services and has full access to the system. Restrict the number of users in this group.

• IndustrialITUser (may be renamed during installation in the installation wizard, (all 800xA users)).

Power User authority is required to build graphics.

3BSE037410R4101 443

Appendix B Additions in Windows added by 800xA

444 3BSE037410R4101

Appendix C System Alarm and EventMessages

System Alarm Message DescriptionsThe most important system alarms are described in the table below:

• The Component column lists from where the system alarm originates. (The corresponding function area is listed within parenthesis).

• The Message Description column lists short descriptions of system alarms. Text within % signs is replaced with the current data at run-time.

• The Extended description column explains system alarms further.

Component Message Description Extended Description

AdvDsOPCServerAdapter (Data Subscription)

OPC Connect Failed The Data Subscription service failed to connect to an OPC Data Server. This indicates that no OPC Data will be available from this node.


OPC Server Stopped The Data Subscription service has lost contact with an OPC Data Server. This indicate that no OPC Data will be available from this node.


OPC Server Error The Data Subscription service has received a message from an OPC Data Server that it is in error. This indicate that no OPC Data will be available from this node.

3BSE037410R4101 445

Appendix C System Alarm and Event Messages

AfwAlarmEvent (Alarm and Event)

Connection to OPC AE Server lost

The Alarm and Event service has lost contact with an OPC Alarm and Event Server in the specified node.

AdvExtAlarm, AdvExtAIEngine (External Alarm)

Init of AE subscr. failed The External Alarm service failed to connect to an OPC Alarm&Event Server. This indicates that the External Alarm function in this node is not working.


Connection of AE subscr. failed

The External Alarm service failed to connect to an OPC Alarm&Event Server. This indicates that the External Alarm function in this node is not working.


Initiation failed Could not start the External Alarm Server due to severe problems in the system. This indicates that the External Alarm function in this node is not working.

AdvHtHistorySrv (Historian)

Exception caught in %APARTMENT% apartment object

An unexpected error has occurred in the specified function (APARTMENT). The History Server consists of several functions that run individually. Contact maintenance personnel for further investigations if this problem is indicated.

AfwAspDirSrv (Aspect Server/Aspect Directory)

Failed to open the aspect directory database files in %WORKDIR%.

Could not open the aspect directory database files. This indicates that the Aspect Directory in this node is not working.

AfwAspDirSrv (Aspect Server/Aspect Directory)

Failed to synchronize database, reason=%HRESULT%

Failed to synchronize a backup Aspect Directory to the master Aspect Server. This indicates that the Aspect Directory in this node is not working.


446 3BSE037410R4101

Appendix C System Alarm and Event Messages

AfwFsdServer (File Set Distribution)(1)

FileSystemError A file system operation failed. The operations could be open, remove, find, create and rename. The files involved are fileset files either on the client (in the FSD cache) or on the server.

AfwFsdServer (File Set Distribution)(2)

ServiceStartupError Unable to start up the File Set Distribution Service. This can be caused by a file system error.

AfwPropertyTransfer (Property Transfer)

Write to property %PROPERTY% failed

The data point (PROPERTY) will not be updated

AfwServiceManager (Service Manager)

Service provider stopped

This indicates that the service provider on the specified node is not working


Service provider entered error state

This indicates that the service provider on the specified node is not working.


Failed to update registry in client node %NODENAME%

This indicates that it will be problems for the specified client node to get in contact to a service provider.

AfwSMClient(RNRP)

RNRP connection down to %NodeName% path %NetworkPath%

This indicates that the RNRP connection to the specified node is down.

AfwSMClient(RNRP)

RNRP connection up node %NodeName% path %NetworkPath%

This indicates that the RNRP connection to the specified node is up.

AfwSMClient(RNRP)

RNRP node %Nodename% unreachable

This indicates that the specified node is unreachable.


3BSE037410R4101 447

System Events for Data Access Functions Appendix C System Alarm and Event Messages

System Events for Data Access FunctionsThis appendix describes System Events for Data Access functions. The messages are sectioned in function areas and submitting component.

OPC DA Client - AdvDsOPCHandler

Write failed

A write operation to an OPC Item failed. The error description is included in the event text. The property name can be found in the long description of the event.

Invalid OPC DA Data Source configuration

The service group in the data source aspect is invalid. Check the configuration of the data source aspect and that the service group exists.

No OPC DA Data Source for OPC DA Item

No data source could be found for an OPC Item that was added. Check that there is a data source aspect in the tree above that object that defines the OPC Item and that the data key is correct.

AfwSysMsgSrv (System Message)

Resize failed: Unknown Error

The System Message Server has failed to resize a storage. This indicates that no more system messages will be stored.

AfwSysMsgSrv (System Message)

Resize failed: Disk Full The System Message Server has failed to resize a storage, because there was not enough space on disk. This indicates that no more system messages will be stored.

(1) File set distribution (FSD) is typically used for distribution of Graphic Displays and Graphic Elements to all 800xA nodes. Problems with FSD will in some cases result in that Graphic Displays (or the latest version of these) are not available as expected on client nodes.

(2) See footnote (1).


448 3BSE037410R4101

Appendix C System Alarm and Event Messages OPC DA Client - AdvDsOPCServerAdapter

OPC DA Client - AdvDsOPCServerAdapter

OPC DA Connect Failed

Failed to connect to a remote OPC DA server. Check that the remote computer is reachable from the connectivity server and that it is possible to connect to the remote OPC DA server with a stand-alone OPC DA client.

OPC DA server shutdown

The target OPC DA server was stopped by manual shutdown.

OPC DA server stopped

The target OPC DA server has stopped unexpectedly. Check error logs for the target OPC DA server.

OPC Server Error

An internal error occurred in the target OPC DA Server. The error code is included in the long description of the event. Check error logs for the target OPC DA server.

OPC Server prog id is not valid.

The OPC DA server id configured for the OPC DA Connector service provider is invalid. Check the configuration and that the OPC DA server is properly installed.

Upload - AfwUploadServer

Upload operation started

An upload operation, retrieve or append was started.

Upload operation completed successfully (Append/Retrieve)

An upload operation, retrieve or append completed successfully ended.

3BSE037410R4101 449

Property Transfer - AfwPropertyTransfer Appendix C System Alarm and Event Messages

Upload operation was aborted by the user

An upload operation was aborted by request of user.

Upload operation failed

An upload operation failed due to an internal error. The error code is included in the event text.

Property Transfer - AfwPropertyTransfer

Bad Property Transfer Record

The Property Transfer Service discovered a bad configuration in a Property Transfer Definition aspect.

Write to property <name> failed

An error occurred when writing to the property <name>. A reason could be that the destination OPC server received too many write requests. Check error logs for the destination OPC DA server.

Transaction lost for property <name>

A write to property <name> was not completed before a new write was started. Reasons could be that the load in the connectivity server, destination OPC server or controller is too high. Try to change the update rate in the Property Transfer Definition aspect.

450 3BSE037410R4101

Appendix D Security Examples

Default Security Setting of the Admin StructureThe Admin Structure is protected by a Security Definition aspect added to the root object “Administrative Objects”. The settings in this aspect are done to protect the Admin Structure. See the settings on delivery in Figure 265. For example all members of the IndustrialITUser group defined in Windows are by default given the permission to Read.

As a member of the Administrators group in 800xA System you can change the default settings in the Admin Structure.

The Default Security Setting of a System ObjectFor each created system there is a system object. Its name is by default <nodename> system, but the name can be freely chosen when the system is created.

Figure 265. The Security Definition Aspect for the Admin Structure

Changes in the Admin Structure affect the security. Allow only a limited number of people permission to change this structure.

3BSE037410R4101 451

The Default Security Setting of a System Object Appendix D Security Examples

In the Security Definition aspect for this object, default security is set for the created system. After creation of a system the default settings are as shown in Figure 266.

Below is an example of how to reconfigure the Default Security Settings.

First access the system’s security definition aspect and reconfigure it:

Figure 266. The Default Security Settings in the System Root Object in the Admin Structure

You need Security Configuration permission to be allowed to change the Default Security Settings.

452 3BSE037410R4101

Appendix D Security Examples The Default Security Setting of a System Object

1. Go to the Admin Structure in Plant Explorer and select the created system. Its name is the name of the server node, or the name given when the system was created.

2. Select the Security Definition aspect.

3. In the Permission tab you can see and reconfigure the security settings.

4. The next step is to set Allowed only for personnel that must perform that type of operation. In this system only three persons must have Operate permission, so delete the Operate line by selecting it and clicking on the Remove button. Then you click Add and insert the group of persons, that are allowed to Operate the system.

Figure 267. The Predefined Default Security Setting

3BSE037410R4101 453

The Default Security Setting of a System Object Appendix D Security Examples

As you can see from Figure 268, there are two groups that have Operate permission from a specific node (Workstation) and one operator (jensa) that can operate from all nodes.

5. By making changes as above, the end result will be as seen in Figure 269.

Figure 268. Changed Default Security Definition Setting

454 3BSE037410R4101

Appendix D Security Examples The Default Security Setting of a System Object

These changes have set the following security for the whole 800xA System (the default security setting for this system):

Figure 269. Final Security Definition Setting in Our Example

• Read is allowed all members of IndustrialITUser group

• Operate is allowed the Opr1 and Opr2 groups from the PPAID11 System node and the user “jensa” from all nodes

• Enter is allowed all members of IndustrialITUser group

• Batch Configure is denied to all IndustrialITUsers

• Tune is denied to all IndustrialITUsers

• Administrate only allowed a member of the IndustrialITAdmin group

3BSE037410R4101 455

Security Setting on an Aspect Object Basis Appendix D Security Examples

According to this example you can redefine the Default Security aspect setting in such a way, that your basic demands on security are met.

Security Setting on an Aspect Object BasisYou can very easily set protection for a specific Aspect object in 800xA. You only have to add a Security Definition aspect to the object and set Authority Range to Object. This means that this aspect setting is valid only for the object.Every setting of permission will be valid only for the object.

If you then set the Search Option for Object to:

• Configure is only allowed a member of the IndustrialITAdmin group

• Security Configure is only allowed the user “jensa”

• Shutdown is allowed a member of the IndustrialITAdmin group.

• Force I/O is denied to all IndustrialITUsers

• First Signature is only allowed the group AppEng1

• Second Signature is only allowed the group AppEng2

• Download is denied to all IndustrialITUsers

• Approved is only allowed the user “jensa”

• Modify History is only allowed the user “jensa”

• Supervise is only allowed the user “jensa”

• Create synchronization package

is denied to all IndustrialITUsers

• Load synchronization package

is denied to all IndustrialITUsers

• Modify Alarm Hiding is only allowed the user “jensa”

456 3BSE037410R4101

Appendix D Security Examples Security Setting on an Aspect Object Basis

• Continue SearchFor groups of persons and persons that have no setting for the permission checked, the search will go on in other structures according to the Evaluation Order setting.

• Terminate Search (as shown in the image)For groups of persons and persons that have no setting for the checked permission, everything is denied regarding this object.

Figure 270. Security Definition Aspect Setting for an Aspect Object

If Read permission is omitted in this security definition everyone is denied access by the implicit deny rule.

AuthorityRange

Permission

Search Option

3BSE037410R4101 457

Different settings of Structure in Authority Range Appendix D Security Examples

Different settings of Structure in Authority Range

If an object is inserted twice in a structure, ensure that the structure setting is valid for each insertion and has different security and settings.

Observe that you must select the right Functional Structure object in the Authority Range to get the desired function. If you select the one according to Figure 271, you set the “other” users permissions to the Emergency Valve. according to Figure 272“Other” users are those users not explicitly granted permissions in the Security Definition.

Figure 271. Functional Structure - Authority Range

Note that these twoicons represents thesame Aspect Object!

458 3BSE037410R4101

Appendix D Security Examples Different settings of Structure in Authority Range

If choosing the upper Alarm object instead, according to Figure 273, other users’ permissions to the Emergency Valve will be as shown in Figure 274.

Figure 272. Permission for Guest Users

Observe that the two Alarm Aspect Objects shown in the Functional Structure are the SAME OBJECT inserted twice in the structure!

Figure 273. Functional Structure - Authority Range

3BSE037410R4101 459

Different settings of Structure in Authority Range Appendix D Security Examples

As you can see changing the position of the object in the Functional Structure within the Authority Range completely changes the authority.

When the Functional Structure object for the upper object is set, the Operator permission is denied to other users. When the lower is selected, the Operator permission is allowed.

Figure 274. Permission for Guest Users

460 3BSE037410R4101

Appendix E Secured Server Configuration

Virus attacks are a real threat for networks connected to the Internet. However, there are some changes that can be done to make it harder for an intruder to get access to your servers. In the table below are some suggestions.

Do not apply any changes to your servers before confirming the changes with your IT department. Some suggestions may contradict your company’s IT policy.

Setting Description

All partitions formatted to NTFS NTFS partitions offer access controls and protections that are not available with the FAT, FAT32 or FAT32x file systems.

Install anti-virus software Install latest anti-virus engine and make sure you are using the latest virus definition file. Consult IndustrialIT 800xA System, Installation instruction for restriction in usage.

Install latest approved service pack Note. Approved means assessed and tested outside the production environment.

Remove additional OS installation if present

Remove other installed operating system except Windows NT Server.

Disable all unnecessary services Review Services and disable those that are not used by the server's function.

3BSE037410R4101 461


Unbind unnecessary protocols If you are not using a particular protocol on a server, like IPX/SPX or NetBIOS, unbind it from the network adapter's it's bound to. This prevents denial-of-service attacks against that protocol, improves your overall server performance, and safe-guard you against protocol-specific exploits.

Change "Access this computer from Network" from Everyone to Authenticated users.

This only allows users having an account in the domain or on the machine to access shares on the server.

Disable IP-routing If routing is enabled, you run the risk of passing data between the Intranet and the Internet.

Disable/delete all unnecessary accounts Disable any non-active accounts and delete accounts that are no longer required.

Rename Administrator account Rename the account to a non-obvious name.

Disable Guest account Make sure Guest account is disabled.

Create a "decoy" account with no privileges and name it Administrator

Scan the event log regularly looking for evidence looking for evidence of attempts to use this account.

Enable auditing Make sure to turn on auditing on these events:Logon and Logoff: Success, FailureUser of User Rights: FailureSecurity Policy Changes: Success, FailureRestart, Shutdown, and System: Success, Failure

Remove all unnecessary file shares All unnecessary file shares on the server should be removed to prevent possible information disclosure.

Set appropriate Access Control Lists (ACL's) on files, directories and shares

See Windows documentation.

Setting Description

462 3BSE037410R4101


Hide last logon user name To enable this, edit these registry setting: Hive: HKEY_LOCAL_MACHINE_SOFTWAREKey: Microsoft\WindowsNT\CurrentVersion\WinlogonValue: DontDisplayLastUserName

Protect registry from unauthorized access

To restrict network access to the registry, make sure this entry exists:Hive: HKEY_LOCAL_MACHINE\SYSTEMKey: CurrentControlSet\Control\SecurityPipeServersValue: RestrictAnonymous

Setting Description

3BSE037410R4101 463


464 3BSE037410R4101

Appendix F Security Checklists andFault Search

Security ChecklistsUse the checklist below to make a major security check of your plant. Make sure that:

• All users have individual password protected accounts

• All users of 800xA are members of Windows IndustrialITUser group

• Only a few are members of the IndustrialITAdmin and Administrators groups

• Default security on the system is changed to deny the Everyone group all permissions except Read.

• Security definitions setup on structures are correct

• Backup routines are in place and checked

• Firewall correctly configured

• All by ABB approved security updates installed.

3BSE037410R4101 465

Fault Search of 800xA Security Appendix F Security Checklists and Fault Search

Fault Search of 800xA SecurityIn this section you will find questions and answers to guide you to find common problems in the 800xA Security system.

Fault - Configuration Wizard only shows System Software Icon

If the Configuration Wizard is activated and only the “System Software and user settings” icon is visible, check the following:

Question Is the current user member of IndustrialITUser group in the domain?

Answer Add the current user to the group.

Question Is the current user member of IndustrialITAdmin group in the domain?

Answer Add the current user to the group.

Question Is there a local IndustrialITUser or IndustrialITAdmin group defined on the node?

Answer Remove the local groups.

Question Is the password of the Service Account correct?

Answer Redo the user settings.

Question Is the current user member of Local Admin or Domain Admin group?

Answer Add the current user to one of the groups.

466 3BSE037410R4101

Appendix F Security Checklists and Fault Search Fault - Permission granted for modify

Fault - Permission granted for modify

When an operation is granted even when the configuration of security should deny this operation, check the following:

Fault - Permission not granted for modify

When an operation is denied even if the security configuration should allow it:

Question Is current user member of the Administrators group?

Answer All members of the Administrators group have full access to the system. Log in as another user.

Question What is the required permission?

Answer Check the Category definition aspect of the aspect involved in the Aspect System Structure, or look in the permission tab of aspect property.

Question What is the granted permission for the current user?

Answer Check granted permissions on the object with the Object Property dialog Permission tab. Then check all security definitions in all structures where the object is placed. End the check by checking the default security in the Admin Structure domain object.

Question Is current user member of the IndustrialITUser and Everyone groups?

Answer Add the user to the groups.

Question Does the current user have the correct role?

Answer Check the role of the current user in the User Structure, User Definition aspect.

Question What is the required permission for the operation?

3BSE037410R4101 467

Fault - Permission not granted for OPC Write Appendix F Security Checklists and Fault Search

Fault - Permission not granted for OPC Write

When an OPC write operation on a property is denied even if the security configuration should allow it, check the following:

Answer Check the Category Definition aspect of the aspect involved in the Aspect System Structure.


Answer Check granted permissions on the object with the Object Property dialog Permission tab. Then check all Security Definitions in all structures where the object is placed. End the check by checking the default security in the Admin Structure domain object.

Question Is current user member of the IndustrialITUser and Everyone groups?

Answer Add the user to the groups.

Question Does the current user have the correct role?

Answer Check the role of the current user in the User Structure, User Definition aspect.

Question What is the required permission for the OPC property?

Answer Check the required permission in the Object Type Structure for the involved OPC property.


Answer Check granted permission on the object with Object Property dialog Permission tab. Then check all Security Definitions in all structures where the object is placed. End the check by checking the default security in the Admin Structure domain object.

468 3BSE037410R4101

Appendix F Security Checklists and Fault Search Fault - The default permission does not apply to

Fault - The default permission does not apply to the wanted behavior

Question Is it possible to define your own permissions for groups of operators?

Answer Yes. Add your own permission, according to Modification of 800xA Permissions for Process Objects on page 63, then use the Property Attribute Override aspect for the Function block type or Control Module typeThen you configure the default system security to include the new permission.

3BSE037410R4101 469

Fault - The default permission does not apply to the wanted behavior Appendix F Security

470 3BSE037410R4101

Appendix G Troubleshooting in 800xAWorkgroups

Problem with Hostname LookupThere may be problem with getting the IP address for other hosts at boot time or when the primary connection of a redundant network fails. As a workaround to this problem, the addresses should be entered into the hostfile (C:\Windows\system32\drivers\etc\hosts) for all hosts.

Figure 275. Host file

3BSE037410R4101 471

Fail to add Client or Server to a 800xA System Appendix G Troubleshooting in 800xA Workgroups

Fail to add Client or Server to a 800xA System

If there is a problem with adding a node when configuring the 800xA system and the node is using Windows XP, the solution can be to disable the simple file sharing.

From the Start menu select: Start > Control Panel > Folder Options, choose the View tab and configure it according to Figure 276.The Use simple file sharing (Recommended) check box shall be unmarked.

Figure 276. Folder Options Dialog Box

472 3BSE037410R4101

Appendix G Troubleshooting in 800xA Workgroups Log Over does not work

Log Over does not work

Case 1

If a local machine is a Windows 2000 workstation with SP4 (or higher) installed, the following Windows setup is needed.

Follow the steps below:

1. From the Start menu select: Start > Settings > Control Panel > Administrative Tools > Local Security Policy.

2. Expand Local Policies and double-click on the User Rights Assignment, see Figure 277.

Figure 277. Local Security Settings

3BSE037410R4101 473

Log Over does not work Appendix G Troubleshooting in 800xA Workgroups

3. Double-click on Impersonate a Client after authentication in the right windowpane.

4. Add the users and user groups that should use the log over function, see Figure 278.

5. Repeat step 1-4 on all nodes in the workgroup.

Figure 278. Local Security Policy Setting

474 3BSE037410R4101

Appendix G Troubleshooting in 800xA Workgroups Log Over does not work

Case 2

If you get “Invalid User ID” when using the Change User dialog box(see Figure 279), the reason could be to have missed typing the machine name before the user name.

During some conditions it is necessary to give the full name of the user on the form “Machine name\Username”.The machine name is the name of the machine on which the 800xA user was created. For convenience, do always the association from the same machine and note on which machine it was done.

Figure 279. Change User Dialog Box - Illegal User ID

Figure 280. Change User Dialog Box

3BSE037410R4101 475

Invalid Account encountered during System Software User Settings Appendix G Troubleshooting in

Invalid Account encountered during System Software User Settings

Under some conditions the default DCOM Security might not be properly set. It is then necessary to set it manually. Below follows a description on how to do it.

1. From the Start menu select: Start > Run and type dcomcnfg and click OK.

2. Expand Component Services, Computers and select My Computer.

3. Select Properties from the context menu.

4. Select the Default COM Security tab and click the Edit Default... button in the Access Permissions area (see Figure 282). Give the IndustrialITAdmin and IndutrialITUser access permissions.

5. Click the Edit Default... button in the Launch Permissions area (see Figure 282) and give the IndustrialITAdmin and the IndustrialITUser launch permissions.

Figure 281. Component Services

476 3BSE037410R4101

Appendix G Troubleshooting in 800xA Workgroups Invalid Account encountered during System

6. Click Apply.

Figure 282. My Computer Properties Dialog Box

3BSE037410R4101 477

Invalid Account encountered during System Software User Settings Appendix G Troubleshooting in

478 3BSE037410R4101

Appendix H Diagnostics Collection Tool

IntroductionABB Diagnostics Collection Tool (DCT) is used to gather diagnostic data from nodes configured on a network. The data is packaged into compressed cabinet (cab) files that are attached to the reported problem.

In order to be able to collect all diagnostics data you must be logged in as a user with administrative privileges when launching DCT. If not, certain types of diagnostics data will not be possible to view or collect.

TerminologyThe following is a list of terminology used for DCT:

• Cabinet File: For each selected node a cabinet file is created to store the collected data. A cabinet file is compressed and its format is compliant with WinZip. The name of a cabinet file consists of the name of the selected node and the timestamp. It has an extension of .cab, for example:

ABBSECRC4588_02_23_05_12_46_19.cab is a cabinet file for the node ABBSECRC4588 and started 022305 at 12:46:19.

The generated data files may consume large quantities of disk space, and may cause a significant load on the CPU. Use caution when collecting information from the workstations involved.

A cabinet file is also referred to as a Collection Part, as a cabinet file can be a part of an entire collection. If the user wants to collect information from two nodes, ABB4441 and ABB Diagnostics Collection Tool 4442, the two cabinet files generated are parts of the entire collection, and therefore called Collection Parts. The entire collection contains, in this case, two Collection Parts.

3BSE037410R4101 479

Supported Diagnostics Information Appendix H Diagnostics Collection Tool

• Collection: A collection is the result of collecting activity. When collecting diagnostics data, a user can select several nodes. A cabinet file is created for each file; therefore, a collection may consist of several cabinet files for the selected nodes.

• Collection Part: A part of an entire collection, requested when the user clicks Collect Data.

• Manifest File: The manifest file describes the progress made when collecting the diagnostics data, i.e. the job done when the user clicks Collect Data. The manifest file contains messages written by the plug-ins that can be of different levels of importance: Information, Warning, Error, and Exception. The file is of type HTML and can be viewed in a Web Browser, such as Internet Explorer. There is one manifest for each Collection Part and the file is included in the cabinet file. The name of the manifest file is _Manifest.html.

• Command File: This file contains the settings made when the user clicks Collect Data, i.e. the nodes, plug-ins, and the settings of the plug-in that the user wanted to be performed. There is one manifest for each Collection Part and the file is included in the cabinet file. The name of the command file that is created for each plug-in is __CommandManifest.xml.

Supported Diagnostics Information

DCT supports various 800xA System products as well as Microsoft related information.

800xA System Products

DCT supports the following 800xA System products:

• Batch Management.• OPC Server for AC 800M.• Control Builder M.• Custom Event Log.• 800xA for Harmony.• License Information.• PLC Connect and SoftPoint Server.• Process Portal A 4.1.0.

A command file can be created by the user and loaded into DCT in the Command File Menu, as shown in 2.3.

480 3BSE037410R4101

Appendix H Diagnostics Collection Tool Microsoft Related Information

Microsoft Related Information

DCT supports the following Microsoft related information:

• DLL List.• Dr. Watson.• Dump Registry Data.• Handle List.• Installed Software Version Information.• Process Information List.• Service Information.• SQL Diagnostics.• System Event Logs.• System Information.• Task Manager.• User Dump.

Grouping Plug-insThe tool organizes plug-ins into two groups distinguished by colors, which makes it easy for users to collect different diagnostics data. The two groups are Microsoft related plug-ins and 800xA System related plug-ins. Figure 283 illustrates this feature.

TC08051A

Figure 283. Grouping Plug-ins

3BSE037410R4101 481

Help and Information Appendix H Diagnostics Collection Tool

Help and InformationDCT shows help symbols and information symbols as shown in Figure 284 (help symbol) and Figure 285 (information symbol).

Selecting a symbol causes a pop-up window to appear with help or information pertaining to the object it represents. Figure 286 shows an example of an information pop-up for Dump Registry data.

Quick Start1. To access the Diagnostics Collection Tool, select:

Start > All Programs > ABB Industrial IT 800xA > System > Diagnostics Collection Tool > Diagnostics Collection Tool

-or-

double-click the desktop icon.

TC08052A

Figure 284. Help Symbol

TC08053A

Figure 285. Information Symbol

TC08054A

Figure 286. Information Pop-up for Dump Registry Data

482 3BSE037410R4101

Appendix H Diagnostics Collection Tool Quick Start

2. Select one of the locations from the drop-down list box shown in Figure 287:

– Local Nodes.– 800xA.– Network.

Selecting one of these locations will only extract information from the nodes that are on that location.

3. Select the node from which to collect diagnostic data (Figure 288).

TC05465C

Figure 287. Selecting a Location

TC05466C

Figure 288. Select Nodes

3BSE037410R4101 483

Quick Start Appendix H Diagnostics Collection Tool

4. Enter a description of the problem in the text area as shown in Figure 289. If the field is empty an error message will appear when trying to gather data.

5. Check only the relevant diagnostic data for the reported problem as shown in Figure 290.

TC05467C

Figure 289. Description for Diagnostic Data

TC05468C

Figure 290. Selection of Relevant Diagnostic Data

484 3BSE037410R4101

Appendix H Diagnostics Collection Tool Quick Start

6. Select the Copy Locally check box (Figure 290) to generate the cab file in the Local ABBResults directory share, or deselect the check box to generate the cab file in the Remote ABBResults directory share.

7. Click Collect Data.

8. The Collecting Diagnostics Information dialog (Figure 291) appears and displays the current status of the collection.

9. When all items in the Collecting Diagnostics Information dialog is complete, click Close to complete the collection process. The generated cab file is found in the ABBResults directory share. (The default location is Install Drive:\ABBResults).

10. From the Collecting Diagnostics Information dialog it is also possible to open the manifest of the collected data for a specific node or open the Collection Results dialogs. These two options are available either via the right-click context menu or via the icons on the right-hand side of the dialog (Figure 292).

TC08055A

Figure 291. Collecting Diagnostics Information Dialog

3BSE037410R4101 485

The Collecting Diagnostics Information Dialog Appendix H Diagnostics Collection Tool

The Manifest and the Collection Results dialog are described in more detail in the next section.

The Collecting Diagnostics Information DialogThis dialog displays the progress of configured collections. Once the collection of a specific collection is complete the Progress will be marked as Finished and more detailed information can be obtained from either the collection manifest or by viewing the Collection Results dialog.

TC08056A

Figure 292. Collecting Diagnostics Information Dialog Context Menu

486 3BSE037410R4101

Appendix H Diagnostics Collection Tool Open Manifest

Open Manifest

Select Open Manifest in the Collecting Diagnostics Information dialog to open the Manifest File in a separate window (Figure 293).

The information that is shown in the Manifest File depends on the filter selections made (Debug, Information, Status, Warnings, Errors, and Exceptions) at the top of the dialog.

Viewing Diagnostics Data

Selecting Show in Results window from the context menu in the Collecting Diagnostics Information dialog brings up the Collection Results dialog. The nodes that are displayed depend on the specified location (800xA System nodes, Network node, or Local node) selected in the Main Menu.

TC08057A

Figure 293. Manifest File

3BSE037410R4101 487

Node Panel Appendix H Diagnostics Collection Tool

The Collection Results window is divided into three panels, as shown in Figure 294:

• Node panel.• Collection panel.• Collection part panel.

Node Panel

The Node Panel shows the nodes found in the current selected network type (Figure 295). The name of the node is shown together with progress information and a message. A specific node can be selected in order to view further information

TC08058A

Figure 294. Collection Results Dialog

488 3BSE037410R4101

Appendix H Diagnostics Collection Tool Collection Panel

for the collections that are found on that node (refer to Collection Panel on page 489 and Collection Part Panel on page 490).

To update the information of the nodes, click .

Collection Panel

The Collection Panel (Figure 296) displays a list of the collections for the selected node (highlighted) in the Node Panel. The first column displays the time when the collection gathering was done and the second column gives a description of the collection.

TC08059A

Figure 295. Selecting a Specific Node in the Node Panel

TC08060A

Figure 296. Collection Panel

3BSE037410R4101 489

Collection Part Panel Appendix H Diagnostics Collection Tool

Right-clicking on a collection provides the option to view the properties of the

selected collection, delete the selected collection, or download the

collection to the local machine.

Select View Properties from the context menu to launch the Collection Property dialog (Figure 297). The Node columns contains the nodes included in this collection, together with the start and stop time for each Collection Part.

Collection Part Panel

The Collection Part Panel (Figure 298) displays the content of each Collection Part. The following information for the collection is displayed graphically:

• Nodes for the selected Collection Part ( , first level).

• Plug-ins selected for the node ( , second level).

TC08061A

Figure 297. Collection Property Dialog

490 3BSE037410R4101

Appendix H Diagnostics Collection Tool Collection Part Panel

• Data collected by the corresponding plug-ins ( , third level).

The selected Collection Part may be marked with (warning), (error) or

(exception), as shown in Figure 299.

For further information about warning, error, or exception messages, view the manifest file as follows.

TC08062A

Figure 298. Collection Part Panel

TC08063A

Figure 299. Exception Occurred for Collection Part

3BSE037410R4101 491


Different operations can be performed by right-clicking on the node for each element in the Node Panel, as shown in Figure 301.

These operations are:

• View File : Opens the selected file. If the Collection Part that contains the file is not on the local node, the file is first downloaded before viewing the file. The program that is used to open the file is the same as used when the file is opened in the File Explorer (associated program that is set as default for that file extension). If no program is defined for the selected file type, an Open With… dialog appears allowing the user to select a program to be used to open the file. This option is only available when a file is selected. As an example

TC08071A

Figure 300. Collection Part Panel Context Menu

492 3BSE037410R4101


Figure 301 shows that Windows Notepad is used to display the ListDLL.txt file.

• Open Collection Part in File Explorer : Opens the selected Collection Part in the file explorer. i.e. the File Explorer will be opened and the cabinet file will be selected as shown in Figure 302. If a file is selected in the Collection Part Panel, the selection found in the pop-up menu will be Open File in

TC08064A

Figure 301. View Selected File

Changing the program associated with the file can be done in two ways:

Use the File Explorer menu: Tools > Folder Options… > File Types.

Right-click the file in File Explorer and choose Open With > Choose Program…. Do not forget to end the dialog with the option Always use the selected program to open this kind of file selected.

3BSE037410R4101 493


File Explorer. When selected, the File Explorer will be opened with the file selected, as shown in Figure 303.

TC08065A

Figure 302. Opening Collection Part in File Explorer

TC08066A

Figure 303. Opening File in File Explorer

494 3BSE037410R4101


• Download Collection Part : Downloads the Collection Part (cabinet file) to the local node, as shown in Figure 304.

• View Manifest : View the manifest file for the Collection Part as shown in Figure 305. This option is only available when a node is selected.

TC08067A

Figure 304. Downloading Collection Part to Local Node

TC08068A

Figure 305. Viewing Manifest File

3BSE037410R4101 495

Cabinet File Appendix H Diagnostics Collection Tool

Cabinet FileTo view the content of the cabinet (.cab) file directly from File Explorer, select the appropriate folder (Figure 306) and double-click on the cabinet file. The associated program will open the file and present the content.

Figure 307 shows an example of opening the cabinet file using WinZip.

TC08069A

Figure 306. Opening a Cabinet File from File Explorer

TC08070A

Figure 307. Opening a Cabinet File Using WinZip

496 3BSE037410R4101

Appendix H Diagnostics Collection Tool DCT Configuration

DCT ConfigurationThis section explains how to use different configuration files to configure DCT; for instance, the default directory for collected data can be changed; log files can be configured for one specific 800xA product plug-in; commands for a particular collection can be configured, and some security settings can be configured for a particular environment.

Configuration of ABB Result Folder

The ABB Diagnostics Results Directory, abbreviated ABBResults Folder, is where generated Collections (cabinet files) are found, as shown in Figure 308. The default location is:

Install Drive:\ABBResults

The name of the folder for the cabinet files and the file are created according to the date and time at the moment when the data was gathered.

To change the location of the ABB Results folder:

1. Run the ABB Results Directory Configuration program by clicking on the following:

Start > Programs > ABB Industrial IT 800xA > System > Diagnostics Collection Tool > Result Folder Configuration

TC08072A

Figure 308. ABB Results Folder

3BSE037410R4101 497

Configuration of Specific Plug-in Data Using IITConfig.xml Appendix H Diagnostics Collection Tool

2. The Result Folder Configuration dialog appears showing the current location of the ABB Result Folder. Enter or browse to the desired folder for the ABBResults. Once the folder is selected, click Change.

3. The Confirm Folder Change dialog appears. Click Yes to accept the change or No to decline.

4. The folder changed dialog appears. Click OK to continue.

5. Restart the Diagnostics Collection Tool.

Configuration of Specific Plug-in Data Using IITConfig.xml

The IITConfig.xml file can be used for configuration of some of 800xA System specific plug-in data (Figure 309). The IITConfig.xml is organized to group log files for each 800xA System product. Each log file is defined with an alias (a user friendly name), the filename, and the file path.

The IITConfig.xml file is not used for the plug-ins created with the SDK.

498 3BSE037410R4101

Appendix H Diagnostics Collection Tool Configuration of Specific Plug-in Data Using IITConfig.xml

It is possible to change or add log files to the plug-ins configured in IITConfig.xml. To add a log file:

1. Copy one of the existing log file configurations.

2. Change the log file alias, name, and path.

3. Save the file and return to the tool.

4. Select a new network type, and then select the same network type as the one of interest.

5. Select the node and the newly configured plug-in to see the added log file.

If an alias for a log file contains the string All logs (not case sensitive) as the first log file selection in the list, then DCT interprets this selection to include all other selections in the list (in the check box list). When this selection (check box) is

TC08073A

Figure 309. IITConfig.xml

3BSE037410R4101 499

Configuration of Specific Plug-in Data Using IITConfig.xml Appendix H Diagnostics Collection Tool

selected, the rest of the selections will be disabled. When it is not selected, the other selections will be enabled.

Aliases

An alias tag has been added for each log file to present more user friendly names of the log files. Figure 310 illustrates the aliases for the log files possibly existing in Control Builder M.

The information available to be collected in the file system is configurable regarding file names and paths. The configuration file is in XML format. Figure 311 shows an example.

The current implementation supports a number of 10 log file names per plug-in, in the configuration file IITConfig.xml.

TC08074A

Figure 310. Aliases for Log Files in Control Builder M

TC08075A

Figure 311. Configuration File for Installed Products

500 3BSE037410R4101

Appendix H Diagnostics Collection Tool Configuration of Command Files for Diagnostics Collection

Check Boxes for Fetching All Files

Control Builder M and OPC Server for AC 800M plug-ins can handle the wildcard to retrieve all files under a specific directory, which can simplify the complexity of maintaining the configuration files. To achieve this function a wildcard must be added in the file name for a log file in the configuration file.

Configuration of Command Files for Diagnostics Collection

DCT contains a feature that allows the user to load a specified command file (in xml format) that will set up DCT with the nodes and corresponding plug-ins specified in the command file. The plug-ins also have selections specified in the command file. For more information about the format of the command files, refer to Command File Format on page 502.

1. Clicking Show command file menu in the DCT Main Menu (Figure 312) allows the Command File Menu to be viewed.

2. The Command File Menu is shown in Figure 313. It allows a predefined command file to be selected and loaded into DCT. The command file sets up the nodes and corresponding plug-ins.

To select a command file, choose the file from the Select command file to load drop-down list box and click Load. The selected nodes and plug-ins will be the same as specified in the command file.

TC08076A

Figure 312. DCT Main Menu

TC08077A

Figure 313. Command File Menu

3BSE037410R4101 501

Configuration of Command Files for Diagnostics Collection Appendix H Diagnostics Collection Tool

3. To save the current command configuration, i.e. the nodes selected with their corresponding plug-ins and plug-in selections, enter a name of the file (without .xml extension) and click Save.

Command File Format

The command file is an xml file that must be well formed and validated with the schema CommandManifest.xsd. This file is found in the Command Files folder. Figure 314 shows the element flow in a command configuration file.

The well documented command configuration file example_network.xml (found in Command Files folder and shown in Figure 315) describes how to use the xml syntax according to the schema when creating a new command configuration file.

The command configuration files will be saved to the Command Files folder that can be found in the DCT installation directory.

TC08079A

Figure 314. Schema Flow of Command Configuration File

502 3BSE037410R4101

Appendix H Diagnostics Collection Tool DCT Configuration Settings

When creating a new configuration file, it is recommended to take a copy of the file example_network.xml, rename it, and edit it based on the descriptions in the file.

DCT Configuration Settings

When a user runs the DCT client, it communicates with the server-side executables on the different nodes under those conditions described in the configuration files for each client and server-side executable. The configurations are set in Diagnostics

Collection Tool.exe.config

-and-

ABB.DiagnosticsCollection.NodeInterrogator.Service.exe.config

It is strongly recommended to use an xml editing tool when writing configuration files.

TC08078A

Figure 315. example_network.xml File

3BSE037410R4101 503

DCT Configuration Settings Appendix H Diagnostics Collection Tool

respectively. Both files are located in the installation folder. After installation, the default setting for DCT is to use a secure conversation and authenticating the user to belong to an administrative group. However, there are cases where it may be desirable to modify what user group should be allowed to collect diagnostic data, and in those cases the configuration files must be modified on all installed nodes.

To change the user group authorized to collect diagnostic data, locate the configuration files for the server-side

ABB.DiagnosticsCollection.NodeInterrogator.Service.exe.config

on each node, and then modify the Authentication.Request setting to state the name of the accepted Windows group. The example in Figure 316 shows how to only allow users that belong to the windows group DCTUsers to use DCT.

TC08080A

Figure 316. Example of Using DCT Settings

504 3BSE037410R4101

Appendix H Diagnostics Collection Tool DCT Configuration Settings

DCT Client Settings

Figure 317 is an example of a configuration file that uses simple DCT settings. The first part in configSections is needed to declare the abb.dct.settings section.

The settings are divided into groups: NodeMaster settings and Authentication settings.

NodeMaster Settings. Determines if a node-master should be used, and the name or IP address to be used. If left empty (or removed from the config-file), the Node Interrogator on the same node will be used, otherwise the Node Interrogator of the node stated will be used.

NodeMaster.ForwarderMode. Determines to what extent that Node Master should be used. A node master must be specified in the NodeMaster setting for this setting to apply. The NodeMaster.ForwarderMode can have one of the following values:

• NodeList: This is the default value and means that DCT will only contact the Node Master to get the list of nodes that should be contacted. Any communication between DCT and the Node Interrogator is direct.

• Auto: This is a superset of the NodeList mode. DCT will contact the Node Master to get the list of nodes to talk to. DCT will then try to communicate directly with the nodes but if it is unable to contact the node directly, it then tries to forward the message via the Node Master before reporting a failure.

TC08081A

Figure 317. DCT Settings

3BSE037410R4101 505

DCT Configuration Settings Appendix H Diagnostics Collection Tool

• Always: This setting means that DCT will always forward all messages via the Node Master.

Authentication Settings. This setting determines if authentication should be used and can have the following values:

• Yes: Means that authentication will be used and the user will be prompted to enter a username and password that will be sent to the Node Interrogator.

• No: Authentication will not be used.

• <User Credentials>: This is short for having authentication enabled for the specified user. This is primarily used for testing but could have other purposes. The username and password specified will always be used and the user will not be requested to enter a username and password when running DCT.

<add key="Authentication" value="DOMAIN\username:password" /><add key="Authentication" value="MyHome\Franky:Secre8" />

Authentication.Request. Determines the authentication filter and can be a comma-separated list of users or user groups that are accepted. User groups should be prefixed UserGroup and users should be prefixed User.<add key="Authentication.Request" value="UserGroup:DCTUsers" /><add key="Authentication.Request" value="UserGroup:DCTUsers, User:Franky" />

Authentication.Response. This setting can have the same values as Authentication.Request but it determines the authentication filter for responses. This setting is currently not used.

Authentication.Request.Signature. This setting determines what type of signature should be used when verifying the caller and can have the following values:

• Usernametoken: The message will be signed using a Username Token. When this value is used, the user of DCT will be prompted to enter the username and password of a user that will be authenticated by the ABB Node Interrogator Service.

506 3BSE037410R4101

Appendix H Diagnostics Collection Tool ABB Node Interrogator Service Settings

• Internal: The message will be signed by the built-in (shared) RSA key. The Node Interrogate simply authenticates that the message was sent by the Node Manager, while it does not check what user is running the Node Manager.

• Policy: The policy definition determines the type of authentication and encryption to use. See the WSE Policy description for more information.

Authentication.Response.Signature. This setting can have the same values as Authentication.Response.Signature and affects how response messages are authenticated. Typically, the settings for Authentication.Request.Signature and Authentication.Response.Signature are the same, i.e. if the setting internal is used for the request, it should also be used for the response:

• Usernametoken: The response-message will be encrypted using the Security Context Token that was used to encrypt the UsernameToken in the request.

• Internal: The message will be signed by the built-in (shared) RSA key. The Node Manager simply verifies that the response originates from the Node Interrogator.

• Policy: The policy definition determines the type of authentication and encryption to use. Refer to the WSE Policy description for more information.

ABB Node Interrogator Service Settings

The Node Interrogator has some additional settings that are stated in the same configuration section as the previous settings.

Node Master Configuration

When DCT is used for remote access to an external network, e.g. via VPN, DCT, etc., it must be configured to retrieve information from the remote network in order to work properly. This typically happens when the client node, i.e. the node where the DCT user interface is running, does not belong to the same network as those nodes that you want to collect diagnostics data from. In this special case, first assign a so called Node Master. The Node Master is the name or IP address of one of the remote nodes where DCT is installed, and when specified, that node is used to discover the nodes to collect diagnostic data from instead of the local network.

3BSE037410R4101 507

Functional description Appendix H Diagnostics Collection Tool

The Node Master node is specified by assigning the value NodeMaster in the configuration file for DCT:

Diagnostics Collection Tool.exe.config

The example in Figure 318shows how the configuration for DCT has been changed to use a different machine to list the nodes in the network. For this setting to take effect, any running instance of DCT must be closed and a new one opened.

FUNCTIONAL DESCRIPTIONThis section is divided into 800xA System related functions and Windows related functions.

800xA System Related Functions

Batch Management

This plug-in collects system log files generated by Batch Management.

TC08082A

Figure 318. Configuring the Node Master for Using DCT Remotely

508 3BSE037410R4101

Appendix H Diagnostics Collection Tool Control Builder M Diagnostics Data

Control Builder M Diagnostics Data

This plug-in (Figure 319) collects log files generated by Control Builder M.

System Log File

The System Log file is created the first time Control Builder M is started (or if there is no log file) and is used to store general information concerning Control Builder M. Examples of information logged are: Starting/stopping of Control Builder M, users logging on and out, changes in system privileges, and changes in the setup of Control Builder M made in the Tools menu.

Session Log Files

The OPC Server for AC 800M automatically creates a SessionLog file on the hard disk at startup. This file contains information generated during one session, that is from the time the product is started until it is stopped. A new file will be created for each new startup.

At startup, information about the hardware and software versions, and later, information on system events, such as mode changes and error printouts, will be logged in the Session Log. The log is continuously updated in a running system, and whenever a problem occurs it is a good idea to look at the log to see if there are any printouts.

Session Logs are saved from the previous three sessions. It is important to save a file containing information about a problem, with a new name before it is overwritten.

TC08084A

Figure 319. Control Builder M Diagnostics Data

3BSE037410R4101 509

Control Builder M Diagnostics Data Appendix H Diagnostics Collection Tool

Start Log

Control Builder M creates a Start Log file for logging the last offline to online transfer. Information, such as warnings and error messages, will be logged. The Start Log is useful when investigating errors that occur during or just after an Offline -> Online transition. Sometimes the Start Log will give an explanation of what at first looks like an error (e.g., lost Cold Retain values).

Heap Statistics Log

Every time a memory full message occurs in Control Builder, the system software automatically generates a Heap Statistics log file containing information about the content of the heap. If memory full occurs in a situation that cannot be explained as normal then this file should be included in an error report.

When a system is not able to store more information in the heap, an error message will be displayed. In most cases (at least 98 percent), the reason is simply an attempt to store too much information in too small a heap. If this occurs for a product running on an engineering station, increase the heap size using the Setup Wizard for that product.

Controller System Logs

The AC 800M controller has a circular log buffer (size 16 kb) that can hold a certain amount of information, normally all information that has been generated during the last five to eight startups. The Controller System log is never deleted provided that the battery backup is working properly. It retains information during power failure. This function makes it possible to restart a faulty system immediately regaining control of the process, without losing vital information about the error.

System Information Report

The System Information Report is a list of hardware, software and setup information for an engineering station. This information is generated by a menu command and presented in a text editor. It is important to generate a new file containing information that was valid at the time the problem occurred.

510 3BSE037410R4101

Appendix H Diagnostics Collection Tool OPC Server for AC 800M Diagnostics Data

OPC Server for AC 800M Diagnostics Data

This plug-in (Figure 320) collects log files generated by the OPC Server for AC 800M.

Session Log Files and Heap Statistics Log are identical to those under Control Builder M Diagnostics Data.

Custom Event Logs

This plug-in (Figure 321) collects the custom event logs that have been created by the ABB applications. The custom event logs have the extension .evt and are found in the

%SystemRoot%/system32/config

directory. The event logs can be viewed with eventvwr.exe.

The custom event logs do not include the Application, Security and System event logs. These logs can be viewed by the System Event Logs plug-in (refer to System Event Logs on page 519).

TC08085A

Figure 320. OPC Server for AC 800M Diagnostics Data

TC08110A

Figure 321. Custom Event Logs

3BSE037410R4101 511

800xA for Harmony Appendix H Diagnostics Collection Tool

800xA for Harmony

800xA for Harmony (ABBDiagnosticDump.exe) dumps the current state information maintained by the ABB Diagnostic Service for the server broker, datasync service, and RTDS servers.

License Information

The License Information plug-in (Figure 322) gathers comprehensive report data from the node that has the ABB Central Licensing System server installed. The report contains all the available features, their installed attributes, and how they are currently being used. The plug-in also gathers the error log file from the Licensing server, CLSError.log.

To view the CLSErrors log, click View CLSErrors.log. To view the feature usage, click View Feature Usage.

PLC Connect and SoftPoint Server

This plug-in (Figure 323) gathers the log files for the PLC Connect and the SoftPoint Server which share the same log files. PLC Connect is a connectivity option to the 800xA System that makes it possible to connect and integrate any type of remote or locally installed PLC, RTU, or other type of device.

TC08086A

Figure 322. License Information

PLC Connect and SoftPoint Server are two different products that are installed separately, one by one or both.

512 3BSE037410R4101

Appendix H Diagnostics Collection Tool PPA Diagnostics Data

PPA Diagnostics Data

This plug-in (Figure 324) collects log files generated by Process Portal A (PPA). It collects data generated by Applog and System events.

Config Wizard Log

AfwConfigWizard.log lists all loaded files upon creation and startup of a system.

Applog Messages

Application log (Applog) is the primary debug and diagnostics tool of PPA. The tool supports logging and state report operations.

To use Applog, it has to be enabled by using the Configuration Wizard. Open the Configuration Wizard and choose Applog to start the Applog service.

To configure Applog, start ApplogViewer and choose which applications to trace log information from.

An Applog message contains the following attributes:

• Message time.• Application name.• Message node.• PID.

TC08088A

Figure 323. PLC Connect and SoftPoint Server

TC08089A

Figure 324. PPA Diagnostics Data

3BSE037410R4101 513

Windows Related Functions Appendix H Diagnostics Collection Tool

• Thread.• Log.• Log level.• Tag.• Message text.

System Messages

A system message is intended for a user of the system. A stored message contains the following attributes:

• Message Id.• Message Class.• Message Source.• Source Object.• Node.• Time.• Priority.• Parameters.

Windows Related Functions

DLL List

DLL List (Listdlls.exe) (Figure 325) is able to show the full path names of loaded modules - not just their base names. In addition, DLL List will flag loaded DLLs that have different version numbers than their corresponding on-disk files (which occurs when the file is updated after a program loads the DLL), and can show which DLLs were relocated because they are not loaded at their base address.

514 3BSE037410R4101

Appendix H Diagnostics Collection Tool Dr. Watson

To view the DLL List, click View DLL List.

Dr. Watson

Dr. Watson (drwatson.exe) (Figure 326) is an error-handling application for Windows systems. It detects and diagnoses program errors, then logs the resulting diagnostic information. The drwtsn32.log and the user.dmp files maintain the diagnostic information.

To view the Dr. Watson log, click View Dr. Watson Log.

Dump Registry Data

Dump Registry Data (Figure 291) dumps the registry data under either:

HKEY_LOCAL_MACHINE\SOFTWARE

-or-

HKEY_LOCAL_MACHINE\Software\ABB

TC08090A

Figure 325. DLL List

TC08092A

Figure 326. Dr. Watson Log

3BSE037410R4101 515

Handle List Appendix H Diagnostics Collection Tool

The information is reported in a text file (NT5 format).

Handle List

Handle List is a utility that displays information about open handles for any process in the system (Figure 328). It can be used to see the programs that have a file open, or to see the object types and names of all the handles of a program.

To view the Handle List, click View Handle List.

Installed Software Version Information

Installed Software Version information (Figure 329) is a small application that lists all installed products including 800xA System products and their versions.

TC08094A

Figure 327. Dump Registry Data

TC08095A

Figure 328. Handle List

516 3BSE037410R4101

Appendix H Diagnostics Collection Tool Process Information List

To view the installed software version information, click View Installed Software Version Information.

Process Information List

The Process Information List (pslist.exe) shows information from all the processes that are currently running on a system (Figure 330). This information includes the time of execution, amount of time the process has executed in user and kernel modes, and the amount of physical memory the OS has assigned the process.

To view one or more of the following lists: Threads; Memory detail; Processes, Memory, Threads; or Process ID, select them in the Process Information List dialog.

Threads

Shows statistics for all active threads on the system.

Memory Detail

Shows memory-oriented information for each process, rather than the default of CPU-oriented information.

TC08097A

Figure 329. Installed Software Version Information

TC08099A

Figure 330. Windows Process Information

3BSE037410R4101 517

Service Information Appendix H Diagnostics Collection Tool

Processes, Memory, Threads

Shows CPU, memory and thread information for each of the processes specified.

Process ID

Instead of listing all of the running processes in the system, this parameter narrows the scan to those processes that begin with the name of the process or match a specific process ID.

Process ID numbers can be obtained from the PID column of the Task Manager.

After making the desired selections, click View PSList Log to view the Process Information List log.

Service Information

Service Information (srvinfo.exe) gathers information about a target server running Windows, such as server name, version, domain, drive information, services and state, and system up time. There are three options available: Show service and service drivers, Get version info for Exchange, IIS, SQL, and Show shares (Figure 331).

SQL Diagnostic

SQL Diagnostics (sqldiag.exe) gathers diagnostics and current state information within SQL server. This utility generates a file in the:

...\Program Files\Microsoft\SQL Server\MSSQL\LOG

directory called sqldiag.txt.

TC08101A

Figure 331. Service Information

518 3BSE037410R4101

Appendix H Diagnostics Collection Tool System Event Logs

This utility can be run anytime, whether or not SQL Server is started. If SQL Server is running, SQLDiag gathers these items:

• Text of all error logs.• Registry information.• DLL version information.• Output from:

– sp_configure.– sp_who.– sp_lock.– sp_helpdb.– xp_msver.– sp_helpextendedproc.– sysprocesses.

• Input buffer SPIDs/deadlock information.• Microsoft Diagnostics Report for the server, including:

– Contents of <servername>.txt file.– Operating System version Report.– System Report.– Processor List.– Video Display Report.– Hard Drive Report.– Memory Report.– Services Report.– Drivers Report.– IRQ and Port Report.– DMA and Memory report.– Environment Report.– Network Report.

• The last 100 queries and exceptions.

System Event Logs

The System Event Log (eventvwr.exe) records system and hardware events as log entries on a server. Application, security, and system event logs may be viewed (Figure 332).

3BSE037410R4101 519

System Information Appendix H Diagnostics Collection Tool

The Custom Event logs can be viewed by using the Custom Event Logs plug-in (refer to Custom Event Logs on page 511).

Application Events Log

The application events log contains events logged by applications or programs.

Security Events Log

The security events log can record security events such as valid and invalid logon attempts as well as events related to resource use such as creating, opening, or deleting files. An administrator can specify what events are recorded in the security log.

System Events Log

The system events log contains events logged by the Windows system components. For example, the failure of a driver or other system component to load during startup is recorded in the system log. The event types logged by system components are predetermined by Windows.

System Information

Microsoft System Information (MsInfo32.exe) provides hardware and software information about system configuration and status, gathered from the registry. Two

TC08105A

Figure 332. System Event Logs

520 3BSE037410R4101

Appendix H Diagnostics Collection Tool Task Manager

different formats are offered. One is TXT and the other is NFO (uses standard Microsoft System Information format) (Figure 333).

Task Manager

Task Manager provides information about programs and processes and applications running on the selected node. It also displays the most commonly used performance measures for processes (Figure 334).

To view the Task Manager log, click View Task Manager Log.

User Dump

User Dump (userdump.exe) (Figure 335) displays a list of all running processes and their process IDs recorded in a text file called User Dump.txt. User dump can

TC08106A

Figure 333. System Information

TC08107A

Figure 334. Task Manager Log

3BSE037410R4101 521

User Dump Appendix H Diagnostics Collection Tool

capture the state of a process and can be very useful when troubleshooting servers that have stopped responding, and unresponsive processes.

TC08109A

Figure 335. User Dump

522 3BSE037410R4101

Appendix I Basic Computer Monitoring

IntroductionThe PC, Network and Software Monitoring (PNSM) extension provides a way to monitor IT Assets in an 800xA System. A number of different asset types can be monitored to detect potential problems. These assets include computers, SNMP devices (switches, printers etc.), networks etc. PNSM allows for early detection of these problems, so they can be rectified before they affect the overall 800xA System.

Basic Computer Monitoring builds upon this framework to simplify the process of monitoring the computer nodes in an 800xA System. Computer nodes are monitored for key indicators of computer health and alarms are generated if monitored values deviate from expected limits.

This appendix contains all information required to install, configure, and operate Basic Computer Monitoring; however, read the PNSM documentation if a full understanding of PNSM is required.

Basic Computer Monitoring consists of a set of predefined 800xA System objects and a configuration tool that together provide the functionality required for configuration and monitoring.

OverviewBasic Computer Monitoring, after being installed and configured, automatically monitors all 800xA System computer nodes and alerts the operator to potential computer resource problems via alarm messages.

3BSE037410R4101 523

Alarm State Appendix I Basic Computer Monitoring

Alarm State

When a computer goes into a low resource state an alarm will appear on the Alarm and Event list. It will indicate the computer that has the problem and will indicate a Computer Problem of type Resource Alarm, as shown in Figure 336.

The operator will then need to call up the faceplate for the specific asset to see the exact cause of the problem. Figure 337 shows an example alarm faceplate.

TC08133A

Figure 336. Alarm and Event List Showing Resource Alarms

TC08131A

Figure 337. Alarm Faceplate

524 3BSE037410R4101

Appendix I Basic Computer Monitoring Normal State

While a computer is in the low resource alarm state, the faceplate will indicate in red, the type of resource problems and the actual value of the resource. Depending on the resource it will indicate the amount free (memory and disk space) or the amount used (non-paged pool and CPU load).

Normal State

The faceplate has two ways to indicate that the resource is normal, i.e. not in alarm:

• Computer nodes that have never been in an alarm state: These indicate Normal in green.

• Computer nodes that have returned to normal from an alarm state: In addition to the word Normal there is additional text with details about the previous alarm state. The additional text has the format:

Normal (Last State: previous alarm state)

For example:

Normal (Last state: CPU Overload)

PNSM System Status Viewer Aspect

PNSM has a System Status Viewer aspect the can be used to see the status of all computer nodes being monitored in a single display.

This aspect is found in the Control Structure under the IT Server object. Selecting this aspect calls up the viewer as shown in Figure 338.

The details of the alarm are also sent to the NT Application log. The event contains the time the error occurred, and the computer node and the resource that caused the alarm. The source for the events in the log is VBRuntime.

TC08138A

Figure 338. PNSM System Status Viewer

3BSE037410R4101 525

Installation Appendix I Basic Computer Monitoring

All computer nodes being monitored appear under the Basic Computer Monitoring subdirectory. Under the Description column they indicate OK if the resource is healthy or Basic Computer Device-ResourceAlarm if the computer node is in a low resource state. Right-clicking in the row for the computer node in alarm will call up a context menu that allows the faceplate to be launched.

InstallationThe installation scenarios are as follows:

• 800xA Systems running only PNSM Basic Computer Monitoring: It is recommended that the PNSM Server (the Complete selection during installation) be installed on a Connectivity Server node. It does not have to be on its own Connectivity Server node but it simplifies the upgrade procedure if the system extension is installed on a node other than the Aspect Server node. The footprint of Basic Computer Monitoring is small and should not affect the other software running on the Connectivity Server.

If the PNSM Server is installed on an Aspect Server node, then a complete maintenance shutdown of the 800xA System is required to install a PNSM Service Packs that replace the PNSM system extension.

• 800xA Systems with additional PNSM assets besides those used for Basic Computer Monitoring: Always install PNSM on its own Connectivity Server node per the PNSM installation recommendations.

Basic Computer Monitoring components are part of the standard PNSM SV 4.1 installation. The installation procedures are described in Industrial IT, 800xA - System, Installation.

If PNSM is already installed and running: PNSM SV 4.1 replaces the standard PNSM SV 4.0 asset types. If these basic types have been modified, export them prior to performing the upgrade. After the PNSM SV 4.1 installation is complete and the new system extension is added, import the old asset types back into the Aspect System.

526 3BSE037410R4101

Appendix I Basic Computer Monitoring Configuration

ConfigurationSet up Basic Computer Monitoring according to the standard PNSM documentation. This involves installing the PNSM system extension and configuring the OPC Data Source Definition aspect in the IT Server object in the Control Structure.

Basic Computer Monitoring Configuration Tool

In order to create and configure the Basic Computer Monitoring functionality the Basic Computer Monitoring Configuration Tool must be run.

1. Select:

Start > All Programs > ABB Industrial IT 800xA > Asset Optimization > PC, Network and Software Monitoring > Basic Computer Monitoring Configuration Tool

to launch the Basic Computer Monitoring Configuration Tool.

2. Click Start. The application will automatically close when it is completed.

Normally only minor configuration changes are required after the software is installed and the Basic Computer Monitoring Configuration Tool is run. The default alarm limits are expected to be suitable in most situations. In some cases it may be necessary to modify the hard drives that require monitoring.

Run the Basic Computer Monitoring Configuration Tool once on all computer nodes that will form the 800xA System and have been added and identified to the 800xA System (i.e. added as Aspect Server, Connectivity Servers or Clients in the Configuration Wizard). If new 800xA System computer nodes are added or removed after the Basic Computer Monitoring Configuration Tool has been run, then it will be necessary to run the Basic Computer Monitoring Configuration Tool again to ensure that the correct assets are being monitored.

3BSE037410R4101 527

Specifying the Computer Node to Monitor Appendix I Basic Computer Monitoring

Changing the alarm limits and the hard drives being monitored is done in the Basic Computer Device aspect shown in Figure 339.

Specifying the Computer Node to Monitor

The computer node to be monitored is normally automatically configured by the Basic Computer Monitoring Tool. It should only be changed in exceptional cases, such as when computer nodes are added manually. Manually adding computer nodes is covered in Manually Adding Computer Nodes on page 532.

1. Go to the specific computer node to modify under the Control Structure\Root\ITServer\Basic Computer Monitoring object.

2. Select the IT General Property aspect.

3. Modify the Host token as required. The computer name or IP address can be used. Click Accept and Apply.

4. Populate by clicking Populate in the IT Device Manager aspect in the same object.

TC08134A

Figure 339. Basic Computer Device Aspect

528 3BSE037410R4101

Appendix I Basic Computer Monitoring Specifying the Hard Drives to Monitor

Specifying the Hard Drives to Monitor

Basic Computer Monitoring allows the free disk space of two hard drives to be monitored. By default the first is set to c: and the second is not specified. It is possible to modify both of these if required. The most important hard drives should be monitored, such as the drive hosting the operating system and the drive where either the 800xA System is installed or the drive being used to store the data that the 800xA System is using.

1. Go to the specific computer node with hard drives to modify under the Control Structure\Root\ITServer\Basic Computer Monitoring object.

2. Select the Basic Computer Device aspect.

3. Modify the first (FirstDriveLetter) or second (SecondDriveLetter) drive token as required. There is no restriction as to what drives are monitored with which token. Click Accept and Apply.


Modifying Alarm Limits

The default level at which specific resources are considered to be in alarm is set to a level appropriate for most cases. These alarm limits were chosen at a level so that false alarms are minimized but also where the computer node is still operational so that corrective steps can be taken.

In rare cases it may be necessary to override these default alarm limits to account for unusual behavior. It may be desired to lower an alarm limit to increase the warning period, providing more time to correct the issue (e.g. increasing the hard drive disk space limit on computer nodes with applications, such as Information Management, that make extensive use of the hard drive).

Determining the appropriate value for an alarm limit is a complex undertaking. Setting an incorrect value may nullify the benefits of Basic Computer Monitoring. Modifying alarm limits should only be undertaken under the direction of the ABB support organization.

3BSE037410R4101 529

Modifying Alarm Limits Appendix I Basic Computer Monitoring

Table 16 lists and describes the resource alarm limits, their token names, default values, and acceptable modification ranges.

Table 16. Resource Alarm Limits

Resource

Alarm Limit Description

Token NameDefault Value

Modification Range

Memory Total free virtual memory as a percentage of the total available virtual memory. An actual value less than or equal to this limit will cause an alarm.

VMWarningLimit 10% This should not be increased as this will decrease the time to respond to the problem before the computer fails; however, it can be increased up to about 25%. A higher limit may cause spurious alarms.

Non-Paged Pool

The total non-paged pool for a computer in Megabytes. An actual value greater than or equal to this limit will cause an alarm.

NPPWarningLimit 115 MB Can be lowered to 85 MB if a more conservative alarm limit is required. This limit should not be increased

Hard Drive Disk Space

The free hard drive space in Megabytes. An actual value less than or equal to this will cause an alarm.

DiskSpaceWarningLimit 500MB This limit should not be set less than 200 MB. The upper limit is set by the available disk space, but too large a number will cause spurious alarms.

CPU Load The sustained 2-minute average total CPU load as a percentage. An actual value greater than or equal to this limit will cause an alarm.

CPUWarningLimit 99% It may be set between 90% and 100%. Lowering the limit may cause spurious alarms.

530 3BSE037410R4101

Appendix I Basic Computer Monitoring Adding or Removing 800xA System Computer Nodes

Modifying Alarm Limits for Individual Computer Nodes

The alarm limits for an individual 800xA System node can be changed by modifying the appropriate limit in the Basic Computer Monitoring Device aspect for that node.

1. Select the Basic Computer Monitoring object for the computer of interest.


3. Modify the appropriate limit, click Select and then Apply.


Modifying Alarm Limits for all Computer Nodes

The alarm limits for all computer nodes can be modified by changing the Basic Computer Monitoring IT Device Configuration.

1. Go to Basic Computer Monitoring IT Asset in the Object Type Structure.


3. Modify the appropriate limit, click Select and then Apply.

4. Delete the Basic Computer Monitoring object level under the Control Structure/IT Server object.

5. Select Yes if asked to confirm deletion of object and its children.

6. Run the Basic Computer Monitoring Configuration Tool (refer to Basic Computer Monitoring Configuration Tool on page 527).

Adding or Removing 800xA System Computer Nodes

Computer nodes can be added or removed from the 800xA System via the Configuration Wizard (e.g. to add 800xA Clients). When this has been done, synchronize Basic Computer Monitoring with the 800xA System to ensure that the correct computer nodes are being monitored.

Modifying alarm limits for all computer nodes is an advanced feature that should only be undertaken with care. Consult the ABB support organization for help if required.

3BSE037410R4101 531

Manually Adding Computer Nodes Appendix I Basic Computer Monitoring

Run the Basic Computer Monitoring Configuration Tool (refer to Basic Computer Monitoring Configuration Tool on page 527) to modify what is being monitored:

• New nodes will be monitored.• Removed nodes will be removed from monitoring.

Manually Adding Computer Nodes

Use the Basic Computer Monitoring Configuration Tool to identify and add 800xA System computer nodes that are to be monitored by Basic Computer Monitoring. If 800xA System computer nodes are added or removed, running the Basic Computer Monitoring Configuration Tool again will modify what is being monitored to match the new setup.

The Basic Computer Monitoring Configuration Tool identifies computer nodes that are part of the 800xA System (those that were added or removed using the 800xA Configuration Wizard).

It may be required to monitor computer nodes that are not part of an 800xA System. These computer nodes must be added manually.

There is a dialog during the PNSM installation in which to specify the account that PNSM will run under. PNSM is typically configured to use the 800xA Service account. For PNSM to operate correctly, it must be able to access the remote computer nodes using its account. This is not normally an issue with 800xA System computer nodes. If the 800xA System is configured to use the domain Service account, it will be available to all computer nodes on the domain. If the 800xA System is running as a Workgroup, the same identical Service account will be configured on all 800xA System nodes. However, if additional computer nodes that are not part of the 800xA System are added, and they are part of a Workgroup, the identical Service account (username and password) will need to be added.

1. Make sure the computer node to be added is configured and running.

Do not add computer nodes that are not part of the 800xA System under the Basic Computer Monitoring subdirectory, since this is controlled by the Basic Computer Monitoring Configuration Tool. Manually added nodes will be removed from this subdirectory if the Basic Computer Monitoring Configuration Tool is run again.

532 3BSE037410R4101

Appendix I Basic Computer Monitoring IT Assets and IT Device Library

2. Select the IT Server object in the Control Structure. Do not add under the Basic Computer Monitoring subdirectory.

3. Add the Basic Computer Monitoring object from the list of available IT Asset types.

4. Configure the Host field in the IT General Property aspect with the computer name or IP address.

5. If the hard drive being monitored is not correct then modify the first (FirstDriveLetter) or second (SecondDriveLetter) drive token as required. There is no restriction as to what drives are monitored with which token. Click Accept and then Apply.


IT Assets and IT Device LibraryThis section describes the Basic Computer Asset and the IT Device aspect it contains.

Basic Computer Asset

Description: This Basic Computer Asset (Table 17) monitors the five core indicators of the health of a computer node running Microsoft Windows. It monitors the virtual memory, the non-paged pool, the CPU load, and the hard drive space on two drives.

Table 17. Basic Computer Asset

Device Name IT Device Description

Basic Computer Device

Basic Computer Device

This device provides the complete alarm and the alert functionality for the Basic Computer Device.

3BSE037410R4101 533

IT General Properties Aspect Appendix I Basic Computer Monitoring

IT General Properties Aspect

The item in Table 18 can be modified in the IT General Properties aspect.

Basic Computer Alarm Device

The tokens listed in Table 19 can be modified in the Basic Computer Alarm Device aspect.

Table 18. IT General Properties Aspect

Name Default Value Description

Host localhost Change this to the name or IP address of the computer to monitor

Table 19. Basic Computer Alarm Device Aspect

Modifiable TokensDefault Value

Description

Common Tokens::VMWarningLimit

10% The total computer free virtual memory as a percentage of the total available virtual memory. An actual value less than or equal to this limit will cause an alarm.

Common Tokens::NPPWarningLimit

115MB The total non-paged pool for a computer in Megabytes. An actual value greater than or equal to this limit will cause an alarm.

Common Tokens::FirstDriveLetter

c: The first hard drive to be monitored. A drive letter must be specified.

NOTE: The colon (:) after the drive letter is required.

Common Tokens::SecondDriveLetter

The optional second hard drive to be monitored. A blank indicates no drive to be monitored.

NOTE: The colon (:) after the drive letter is required.

Common Tokens::DiskSpaceWarningLimit

500MB The free hard drive space in Megabytes. An actual value less than or equal to this will cause an alarm.

Common Tokens::CPUWarningLimit

99% The sustained 2-minute average total CPU load as a percentage. An actual value greater than or equal to this limit will cause an alarm

534 3BSE037410R4101

INDEX

Numerics800xA

User groups 95

AAC 400 connect RTA board files

Copying files to safe mediaSV 3.1 SP1 to SV 3.1 SP2 243

AC 800MPreparation

SV 3.1 SP1 to SV 3.1 SP2 244, 268Access evaluation algorithm 107afw-files 189Application events 520AppLog 435Applog messages 513Aspect Category Definition 61Aspect Category OPC property

Required permission 61Assigning Permissions 34Associate Windows Group button 48Audit Trail Configuration 115Authority range 51 to 52

BBackup 32Batch history restore window 277Batch management 508

CCables 32Client 408Computer Room 32Config wizard log 513Configuration Overview 385

Configuration Wizard 385Confirmed Write 156Connectivity Server 412Continue search

Search option 53, 457Contractors 35Copying files to safe media

AC 400 connect RTA board filesSV 3.1 SP1 to SV 3.1 SP2 243

DDestruction of Data Media and Computers 32Digital Signature 143DLL list 514Domain Definition aspect 259Double-authentication 129Dr. Watson 515

EEvaluation search order 107

An example 111

FFirewall 33FOUNDATION fieldbus

PreparationSV 3.1 SP1 to SV 3.1 SP2 237

FSD 448

GGranted permission 62

3BSE037410R4101 535

IndexIndex

HHandle list 516Hardware definition files

Post upgradeSV 3.1 to SV 3.1 SP2 244

Harmony connectPreparation

SV 3.1 to SV 3.1 SP2 269History Source 169

IImport aspects 231Import/Export

The Actions Menu 222The Edit Menu 198The File Menu 196The Help Menu 228The Tools Menu 217The View Menu 200

IndustrialITAdminWindows 2000 User Groups 44

IndustrialITUserWindows 2000 User Groups 44

InterfaceRole 94

Inventory Spare Parts 33

LLog over 136Log over problem 143

MMaximum security log size 128Microsoft system information 520

PPassword Security 34PC, network and software monitoring

Post upgrade

SV 3.1/3 to SV 4.0 266Permission 51 to 52

Granted 62Required 62

Permission tab 104PLC connect

PreEvent.dll 243Preparation

SV 3.1 SP1 to SV 3.1 SP2 242PreTreat2.dll 243

Post upgradeSV 3.1 to SV 3.1 SP2

Hardware definition files 244SV 3.1/2 to SV 4.0

PC, network and software monitoring 266PPA diagnostics data 513

Applog messages 513Config wizard log 513System messages 514

PreEvent.dll 243PreTreat2.dll 243Process Equipment 33Property Attribute Override Aspect 66Protection of Admin Structure 451

RReading the Manual 32Reason 146Re-authentication 129Remote diagnostics

Description of gathered data 484Selecting nodes 483Selecting relevant diagnostic data 484

Required permission 62for Aspect Category OPC property 61

Retain security log 128Retention method for application log 128Role 95

Interface 94Root Accounts 34

536 3BSE037410R4101536 3BSE037410R4101

Index

SScheduling Reports 369Search option 51, 53

Continue search 53, 457Terminate search 53, 457

SecurityReport 100testing 35

Security Definition aspect 37, 61Security events 520Servers 33Service information 518Services 33Special Configuration tab 179SQL dialog 518Status Viewer Profile Values 305SV 3.1 SP1 to SV 3.1 SP2

Copying files to safe mediaAC 400 connect RTA board files 243

System preparation and shutdownAC 800M 244, 268FOUNDATION fieldbus 237PLC connect 242

SV 3.1 to SV 3.1 SP2Post upgrade

Hardware definition files 244System preparation and shutdown

Harmony connect 269SV 3.1/2 to SV 4.0

Post upgradePC, network and software monitoring 266

System BackupScheduling 284

System event logs 519Application events 520Security events 520System events 520

System events 520System Extensions 420System Message Server 179

System MessagesDefault Sizes 180Edit String 181File Count 183File Size 183Max File Count 184Message Count 184Storage Classes 180

System messages 514System preparation and shutdown

SV 3.1 SP1 to SV 3.1 SP2AC 800M 244, 268FOUNDATION Fieldbus 237PLC connect 242

SV 3.1 to SV 3.1 SP2Harmony connect 269

TTask manager 521Terminate search

Search option 53, 457Training Program 35

UUPS 32User Accounts 34User Administration on IndustrialIT System 418User dump 521User groups

800xA 95Windows 2000 443

VView of Audit Logs 114Virus Check 33

3BSE037410R4101 537

IndexIndex

WWindows 2000

User groups 443Windows 2000 audit

Presentation in the Event Viewer 124Windows related functions 514

538 3BSE037410R4101538 3BSE037410R4101

3BSE037410R4101. Printed in Sweden June 2005Copyright © 2003-2005 by ABB. All Rights Reserved® Registered Trademark of ABB.™ Trademark of ABB.

Automation Technology ProductsMannheim, Germanywww.abb.de/controlsystems

Automation Technology Products Wickliffe, Ohio, USAwww.abb.com/controlsystems

Automation Technology ProductsVästerås, Swedenwww.abb.com/controlsystems

http://www.abb.com