2PAA111693-611 A en System 800xa 6.1.1 Installation Update and Upgrade - Post Installation

SYSTEM VERSION 6.1.
ABB Ability™ System 800xA

Installation, Update and Upgrade
Post Installation
SYSTEM VERSION 6.1.1
ABB Ability™ System 800xA

Installation, Update and Upgrade
Post Installation
Document Number: 2PAA111693-611

Document Revision: A
Release: May 2021
Trace back information Main Publication:

Tool version: 5.2.025
Build date: 2021-04-23 at 08:40:22
Domain: ABBPA
Workspace, version, checked in: 800xA Main, a477, 2021-04-23
Master: ix-487371-Post Installation.xml
Recipe: ix-363918-6.1_Post Installation.rcp
PDF stylesheet: ix-470537-PDF-Stylesheet.xml
Customer stylesheet: ix-478118-CustomerStylesheet.xml
Notice
This document contains information about one or more ABB products and may include a description of or a reference
to one or more standards that may be generally relevant to the ABB products. The presence of any such description of
a standard or reference to a standard is not a representation that all of the ABB products referenced in this document
support all of the features of the described or referenced standard. In order to determine the specific features supported
by a particular ABB product, the reader should consult the product specifications for the particular ABB product.
ABB may have one or more patents or pending patent applications protecting the intellectual property in the ABB
products described in this document.
The information in this document is subject to change without notice and should not be construed as a commitment
by ABB. ABB assumes no responsibility for any errors that may appear in this document.
Products described or referenced in this document are designed to be connected, and to communicate information and
data via a secure network. It is the sole responsibility of the system/product owner to provide and continuously ensure
a secure connection between the product and the system network and/or any other networks that may be connected.
The system/product owners must establish and maintain appropriate measures, including, but not limited to, the
installation of firewalls, application of authentication measures, encryption of data, installation of antivirus programs,
and so on, to protect the system, its products and networks, against security breaches, unauthorized access, interference,
intrusion, leakage, and/or theft of data or information.
ABB Ltd and its affiliates are not liable for damages and/or losses related to such security breaches, any unauthorized
access, interference, intrusion, leakage and/or theft of data or information.
ABB verifies the function of released products and updates. However system/product owners are ultimately responsible
to ensure that any system update (including but not limited to code changes, configuration file changes, third-party
software updates or patches, hardware change out, and so on) is compatible with the security measures implemented.
The system/product owners must verify that the system and associated products function as expected in the environment
they are deployed.
In no event shall ABB be liable for direct, indirect, special, incidental or consequential damages of any nature or kind
arising from the use of this document, nor shall ABB be liable for incidental or consequential damages arising from use
of any software or hardware described in this document.
This document and parts thereof must not be reproduced or copied without written permission from ABB, and the
contents thereof must not be imparted to a third party nor used for any unauthorized purpose.
The software or hardware described in this document is furnished under a license and may be used, copied, or disclosed
only in accordance with the terms of such license. This product meets the requirements specified in EMC Directive
2014/30/EU and in Low Voltage Directive 2014/35/EU.
Trademarks
All rights to copyrights, registered trademarks, and trademarks reside with their respective owners.
Copyright © 2021 by ABB. All rights reserved.

Table of Contents
Table of Contents
About this User Manual

User Manual Conventions ................................................................................. 11
Warning, Caution, Information, and Tip Icons ...................................... 12
Terminology ....................................................................................................... 13
Released User Manuals and Release Notes .................................................... 13
1 Post Installation Overview

1.1 System Security ............................................................................................... 15
1.2 800xA Installation User ..................................................................................... 15
1.3 Post Installation Sequence ............................................................................... 16
2 Central Licensing System

3 800xA Base System
3.1 Load Balancing (Affinity) .................................................................................. 19
3.1.1 Overview .............................................................................................. 19
3.1.2 Planning Load Balancing .................................................................... 20
3.1.3 Configuring Affinity ............................................................................... 22
3.2 Configuring Users and Permissions .................................................................. 26
3.3 Time Services .................................................................................................... 26
4 SoftPoint Server
4.1 Configuring SoftPoint Services ......................................................................... 27
5 800xA for AC 800M

5.1 Workflow ............................................................................................................ 31
5.2 AC 800M Controller ........................................................................................... 32
5.2.1 Set the IP Address in the Processor Unit ........................................... 32
2PAA111693-611 A 5
Table of Contents
5.2.2 Verify the Processor Unit IP Addresses ............................................... 36

5.2.3 Download Processor Unit or Communication Interface Firmware using
the Control Network ............................................................................. 37
5.3 AC 800M SoftController .................................................................................... 38
5.3.1 Setup and Configre Secure Download ................................................ 38
5.4 Configure the OPC Server for AC 800M ........................................................... 44
5.4.1 Configuration Planning ........................................................................ 44
5.4.2 Additional Parameters .......................................................................... 47
5.4.3 Connecting to Controllers .................................................................... 48
6 800xA for Advant Master

6.1 Entering License Information for Connected Controllers .................................. 49
7 800xA for AC 100

7.1 System 800xA Configuration ............................................................................. 51
7.1.1 Creation of AC100 AF 100 Network Object Instance .......................... 51
7.1.2 Alarm and Event Server Startup .......................................................... 51
7.2 Configuration and Operation ............................................................................. 54
7.3 Clock Synchronization and Daylight Saving Time ............................................. 54
7.4 Installation Verification (Optional) ...................................................................... 54
7.5 Product Verification ........................................................................................... 57
8 800xA for Symphony Plus Harmony

8.1 Harmony Communication Configuration ........................................................... 61
8.1.1 Harmony API Configuration ................................................................. 61
8.2 OPC Server Network Object Setup ................................................................... 62
8.3 Update Alarm Manager ..................................................................................... 63
8.4 Harmony Uploader ............................................................................................ 63
8.5 Restart Connectivity Server .............................................................................. 64
9 800xA for MOD 300

9.1 Setting Up Clock Synchronization ..................................................................... 65
9.2 Setting Alarm Manager Options ........................................................................ 65
9.3 Setting Up the System Structure ....................................................................... 65
2PAA111693-611 A 6
Table of Contents
10 800xA for DCI

10.1 Configure a Single NIC Interface to the DCU .................................................. 67
11 800xA for Freelance

11.1 On Freelance Connectivity Server Node ........................................................... 69
11.1.1 Re-create OPC Server Resource IDs .................................................. 69
11.1.2 Add Windows Firewall exceptions ....................................................... 69
12 PLC Connect
12.1 Control Network Setup ...................................................................................... 71
13 Asset Optimization
13.1 Web-Enabled Views on Non-800xA Systems ................................................... 73
13.2 Maximo Integration ............................................................................................ 74
13.2.1 Maximo Business Object (Maximo 6.2, Maximo 7.1 and Maximo 7.6) . 74
13.3 SAP/PM Integration ........................................................................................... 76
13.4 Internet Explorer Configuration ......................................................................... 77
13.5 Excel Initialization .............................................................................................. 77
14 Device Library Wizard

14.1 Fieldbus Device Type Preparation (Optional) ................................................... 79
14.1.1 Installing Fieldbus Device Types ........................................................ 79
15 Information Management
15.1 Information Management Setup ........................................................................ 83
15.1.1 Referenced Post Installation Procedures ............................................ 85
15.2 ActiveX Security Settings .................................................................................. 86
15.3 Creating a History Database Instance .............................................................. 86
15.4 Starting Process Administration Supervision (PAS) .......................................... 94
15.5 Configuring the DBA (ADO) Data Provider for Oracle Data .............................. 95
15.5.1 Creating an ODBC Data Source for the Oracle Database ................... 96
15.5.2 Editing the ADO Data Provider Configuration ...................................... 100
15.6 Defining the Users .............................................................................................101
15.6.1 Configuring the Default ACC Users ..................................................... 101
2PAA111693-611 A 7
Table of Contents
15.7 Information Management Profiles Client Post Installation ................................ 102

15.8 Adding the DataDirect Add-Ins in Office ........................................................... 103
15.9 Adding the Inform IT Bulk Import Add-in in Office ............................................. 103
16 800xA History
16.1 800xA History Event Collection Procedure ....................................................... 105
16.1.1 Event Collection based on Vendor Attributes ...................................... 106
16.1.2 Event Collection based on Event Categories ...................................... 107
17 Batch Management
17.1 Batch Redundancy Configuration ..................................................................... 109
17.1.1 Batch Redundancy in Workgroup Environment ................................... 112
17.2 Registry Setting changes (Batch Harmony Connect Users Only) ..................... 113
17.3 Shutdown Script ................................................................................................ 113
17.4 Print BMA Report Configuration ........................................................................ 114
17.5 Batch Management Toolbar .............................................................................. 114
17.6 Set Date and Time for Batch Servers ............................................................... 114
18 PR Batch History
18.1 Batch View Client .............................................................................................. 115
18.1.1 Batch View Installation ......................................................................... 116
18.1.2 Batch View Configuration .....................................................................117
18.2 Batch Analysis Application ................................................................................ 118
18.3 SQL Server Memory Limit ................................................................................. 121
19 IPsec Configuration Tool

19.1 IPsec Configuration Tool ................................................................................... 123
19.1.1 Configuring IPsec for System 800xA ................................................... 123
19.1.2 New Configuration ............................................................................... 124
19.1.3 Edit Configuration ................................................................................ 127
20 800xA Clock Synchronization

20.1 Configuring Windows Time Service .................................................................. 130
20.2 Configuring the 800xA Time Service .................................................................130
2PAA111693-611 A 8
Table of Contents
20.3 Configuring the System Time Server ................................................................ 130

20.4 Configuring the Time Client ...............................................................................131
20.5 800xA for AC 800M ........................................................................................... 131
20.6 800xA for AC 100 .............................................................................................. 132
20.6.1 Clock Synchronization and Daylight Saving Time ............................... 132
20.7 800xA for MOD 300 .......................................................................................... 133
20.7.1 Setting Up Clock Synchronization ....................................................... 133
20.8 Device Management FOUNDATION Fieldbus .................................................. 136
21 Installing additional products

22 xStream Commissioning
22.1 Installation of Field Information Manager .......................................................... 139
22.2 Installation and Configuration of ABB Field Information Manager Bridge 800xA139 .
Appendix A Engineering Repository

A.1 Engineering Repository Web Service Configuration ......................................... 141
A.1.1 Server Operating System .................................................................... 142
A.1.2 Workstation Operating System ............................................................ 150
A.1.3 Common Problems .............................................................................. 157
A.1.4 Configuration Verification ..................................................................... 158
A.2 Client Configuration ...........................................................................................159
A.3 Common Problems ........................................................................................... 159
Revision History ..................................................................................................... 161
Index .......................................................................................................................... 163
2PAA111693-611 A 9
2PAA111693-611 A 10
User Manual Conventions
The System 800xA Safety AC 800M High Integrity Safety Manual (3BNP004865*)
must be read completely by users of 800xA High Integrity. The recommendations
and requirements found in the safety manual must be considered and implemented
during all phases of the life cycle.
Any security measures described in this user manual, for example, for user access,
password security, network security, firewalls, virus protection, and so on, represent
possible steps that a user of an 800xA System may want to consider based on a
risk assessment for a particular application and installation. This risk assessment,
as well as the proper implementation, configuration, installation, operation,
administration, and maintenance of all relevant security related equipment, software,
and procedures, are the responsibility of the user of the system.
The user manual describes manual post installation configurations, which are not
performed automatically during system deployment.
This user manual does not include information on site planning, engineering planning,
software configuration, network design, security measures, tools, maintenance, and so
on that can be found in other 800xA user manuals.
Unless otherwise noted, the procedures described require IndustrialITAdmin and Local
Windows Administrator privileges. It is recommended to use the 800xA Installer account.
Perform the procedures, applicable to the deployed 800xA System with respective node
functions on the nodes in the order presented.

Microsoft Windows conventions as defined in the Microsoft Manual of Style are normally
used for the standard presentation of material when entering text, key sequences,
prompts, messages, menu items, screen elements, and so on.
2PAA111693-611 A 11
Warning, Caution, Information, and Tip Icons

This user manual 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:
Electrical warning icon indicates the presence of a hazard that could result in
electrical shock.
Warning icon indicates the presence of a hazard that 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 that could result in
corruption of software or damage to equipment/property.
Required action icon indicates actions that are required for the product or system
to function as intended.
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.
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, fully comply with
all Warning and Caution notices.
2PAA111693-611 A 12
Terminology
Terminology
A complete and comprehensive list of terms is included in System 800xA Terminology
and Acronyms (3BSE089190*). The listing includes terms and definitions that apply to
the 800xA System where the usage is different from commonly accepted industry standard
definitions.
Table: Terminology
Term/Acronym Description
Backup 800xA Backup: Backup using the 800xA Backup Definition aspect.
Functional Area Backup: Backup through defined tools or copy of
Functional Area configuration and/or data to a location or media which
could accessible later for items not covered by 800xA Backup.
The specific operations called out for the Functional Area within the
Backup/Restore procedure in System 800xA Maintenance
(3BSE046784*) for same version to same version backup and restore.
Restore 800xA Restore: Restore through the Configuration Wizard.
Functional Area Restore: Restore through defined tools or copy of
Functional Area configuration and/or data from the location or media
where backup for items are stored which are not covered by 800xA
Backup.
The specific operations called out for the Functional Area within the
Backup/Restore procedure in System 800xA Maintenance
(3BSE046784*) for same version to same version backup and restore.
Upgrade Moving from one major 800xA release to a later major 800xA release,
whether it be a major or minor release. Moving from System 800xA 5.x
to System 800xA 6.x is an upgrade process.
Update Moving within a major version of 800xA to latest minor versions, rollups
or other patches. Moving within System 800xA 6.x is an update process.
Released User Manuals and Release Notes

A complete list of all User Manuals and Release Notes applicable to System 800xA is
provided in System 800xA Released User Documents (3BUA000263*).
System 800xA Released User Documents (3BUA000263*) is updated each time a
document is updated or a new document is released.
2PAA111693-611 A 13
Released User Manuals and Release Notes
It is in pdf format and is provided in the following ways:

• Included on the documentation media provided with the system and published to
ABB Library and myABB/My Control System portal when released as part of a major
or minor release or System Revision.
• Published to ABB Library and myABB/My Control System portal when a User Manual
or Release Note is updated in between any of the release cycles listed in the first
bullet.
2PAA111693-611 A 14
1.1 System Security
This user manual reflects 800xA System and Functional Area software at the time
of release. All 800xA System and Functional Area Release Notes must be read and
understood before performing any installation, post installation, or upgrade
procedures. The Release Notes contain any last minute changes that must be
performed when installing or upgrading the 800xA System. All Release Notes can
be found on the Release Notes/Documentation media.
Before performing the procedures in this user manual, refer to System 800xA Installation,
Update and Upgrade Getting Started (2PAA111708*) for procedures on installing 800xA
System. All licensing procedures must be completed and the software keys in place as
described in System 800xA Licensing Information (2PAA111691*) in order to complete
the procedures in this user manual.
1.1 System Security

It is very important to have a corporate security policy that is revised on a regular
basis. This is the responsibility of the user of the 800xA System.
This user manual does not contain recommendations on system security, users, user
groups, or user roles and permissions. Refer to System 800xA Administration and Security
(3BSE037410*), System 800xA Network Configuration (3BSE034463*), and System
800xA System Planning (3BSE041389*) for more information.
1.2 800xA Installation User

Unless otherwise specified, perform all procedures in this user manual logged in as the
800xA Installer account
When the system is created, the user currently logged in is added to the system as a
member of the Administrators, Everyone, System Engineer, and Application Engineer
IndustrialIT groups.
2PAA111693-611 A 15
1.3 Post Installation Sequence
1.3 Post Installation Sequence

Perform the procedures, applicable to the deployed 800xA System with respective node
functions on the nodes in the order presented the subsequent sections.
The firewall should always be ON.
Firewall exceptions are added automatically during the system deployment process.
Users shall ONLY add firewall rules manually if it is required as a post installation
step.
2PAA111693-611 A 16
Licenses obtained from the ABB license and Automation Sentinel must be loaded on
the node where the Central Licensing Server function is allocated(typically the Primary
Aspect Server).
Refer to the System 800xA License Information (2PAA111691*) for detailed procedure
to obtain the license and load the 800xA System license
2PAA111693-611 A 17
2PAA111693-611 A 18
3 800xA Base System
3.1 Load Balancing (Affinity)
3 800xA Base System

The System Configuration Console can be used in many cases to configure and
perform load balancing (affinity). Refer to System 800xA Tools (2PAA101888*) for
information and instructions on using the System Configuration Console to configure
load balancing.
The description in this topic describes the manual configuration of affinity if the
System Configuration Console is not used.
Affinity is a means to ensure a predictable system configuration. To achieve predictable
load balancing, affinity must be set up correctly. This topic provides a brief overview of
the affinity concept, guidelines for planning affinity, and instructions for configuring affinity
in the system.
Configuring affinity is optional; however, if affinity is not configured, clients will
randomly select providers for their services, which may lead to unpredictable
performance.
3.1.1 Overview
Balancing the client load within a server group will achieve a predictable and stable
running condition. This is especially important for Redundant Connectivity Servers, which
handle large amounts of process data. Without load balancing, the problem can arise
where one server node handles the larger part of the client node load, while the other
server nodes are idling.
Affinity is also an important consideration with respect to Information Management.
Clients should have affinity toward Information Management Servers with history
configurations.
Affinity is configured using an Affinity aspect placed in the Administration Structure.
It specifies the order for which a client should pick servers for a certain service. For
example, Client A must always connect to Connectivity Server A (when available) and
Client B to Connectivity Server B. Refer to Figure 3.1 for an example of load balancing.
2PAA111693-611 A 19
3 800xA Base System
Different services may use different affinity settings. Affinity settings for clients to services
provided by Connectivity Servers differs from the settings for services provided by Aspects
Servers.
The basic steps are:
• Create the Affinity aspect.
• Configure the Affinity aspect.
• Apply affinity settings to desired services.
These steps are described in detail in Configuring Affinity.
Figure 3.1: Configuration example of load balancing
3.1.2 Planning Load Balancing

In the Device Management FOUNDATION Fieldbus Configuration the following
restriction for affinity configuration.
Furthermore configure affinity for all services which use the OPC Server FF ensures
that all clients predictively select the same Connectivity Server node as provider
(from a pair of redundant Connectivity Server nodes running OPC Server FF). For
details on configuration of affinity, refer to Configuring Affinity.
Affinity can be configured for redundant Aspect Servers as well as Connectivity Servers.
Before configuring affinity, plan how to balance the client load between the redundant
servers of the system.
When developing a new load balancing plan it is always recommended to maintain a
triangle-relationship between a particular client, Aspect Server, and Connectivity Server
as shown in Figure 3.2. This is to minimize disturbance.
2PAA111693-611 A 20
3 800xA Base System
Figure 3.2: Triangle relationship for planning affinity
If Client 1 primarily accesses Aspect Server 3 and Connectivity Server 2, then Aspect
Server 3 should also primarily access Connectivity Server 2, in order to maintain the
triangle-relationship between Client 1, Aspect Server 3, and Connectivity Server 2.
Relationships are always planned and drawn from the client point of view. The relationship
between the Aspect Server and the Connectivity Server is bidirectional, as both servers
can act as clients and access the other one.
The triangle relationship is kept only under normal running conditions of the system.
If one server of a triangle fails and the client fails over to the next server, the triangle
relationship is lost. There are no lower prioritized triangle relationship setups for failure
conditions.
The planned affinity settings are then transferred into a load balancing table. This table
is later used as a base reference in the affinity configuration steps in Configuring Affinity.
The numbers within the table indicate the order in which clients fail over to different
servers. All triangle relationships are entered into this table using the highest order
number (1), indicating that this is the preferred access under normal running system
conditions. The remaining cells are filled with lower order numbers, but they do not follow
any triangle relationships.
Figure 3.3 shows an example of a load balancing plan for a system with two clients,
three Aspect Servers, and two Connectivity Servers. Bold numbers in Table 3.1 are
results taken from the corresponding triangle relationships.
It is not always possible to create triangle relationships covering all servers without
producing any conflicts in the load balancing table. The primary goal of planning
load balancing is to define as many conflict free triangles as possible for the preferred
client/server relationships, mainly for the operator stations, under a normal running
system condition.
2PAA111693-611 A 21
3 800xA Base System
Figure 3.3: Load balancing plan example
Table 3.1: Load balancing table for load balancing plan in Figure 3.3
Aspect Aspect Aspect Connectivity Connectivity

Affinity
Server 1 Server 2 Server 3 Server 1 Server 2
Client 1 3 2 1 2 1
Client 2 2 1 3 1 2
Aspect Server 1 1 2 3 2 1
Connectivity Server 3 1 2 1 2
1
Connectivity Server 2 3 1 2 1
2
NOTE:
Bold entries are results taken from the corresponding triangle relationships.
3.1.3 Configuring Affinity

In this example, two Affinity objects are created: CS and AS. This is the recommendation
for a redundant system.
2PAA111693-611 A 22
3 800xA Base System
Recommendations:
• Set up a redundant system and verify it before setting up the affinity.
• Use the following services when using affinity:
– File Set Distribution (FSD) Service.
– Aspect Directory Service.
– Basic History Service.
– Cross Referencing Service.
– Opc_DA Connector Service.
– Alarm Manager Service.
– Event Storage.
– Event History.
– Event Hub
– OPC UA Connect.
For the client node, the affinity should be set in such a way that for all services
running on an Aspect Server, the affinity is pointing to one (the same) Aspect Server
in a 2oo3 setup. Do not point to different Aspect Servers for different services. This
is also true for redundant (parallel) Connectivity Server pairs. The client should point
to all services on one Connectivity Server, rather than mixing affinity settings.
The basic steps are:
• Creating the Affinity Objects.
• Configuring the Affinity Aspects.
• Applying Affinity Settings to the Services .
Creating the Affinity Objects

To create the Affinity objects:
1. Open a Plant Explorer Workplace.
2. Use the Structure Selector to open the Admin Structure.
3. Use the Object Browser to navigate to:
Administrative Objects > Inventory Object> Affinity
4. Right-click the Affinity aspect type object and then click New Object.
2PAA111693-611 A 23
3 800xA Base System
5. The New Object dialog box appears. Create a new object of type Affinity.
6. Specify a name (CS_affinity) for the Affinity object in the Name field.
7. Repeat the procedure to create and name the AS Affinity object.
Configuring the Affinity Aspects

To configure the Affinity aspects:
1. Select the Affinity Definition aspect of an Affinity object in the Aspect List Area.
2. Click the Configuration tab in the Preview Area.
3. Click Add under the Selection Group/Node list to add clients to the list.
4. In the Item Contents list (to the right) specify the server nodes and server node
groups and the order in which the client must connect to the servers. The client
nodes select the server in order from top to bottom.
5. When defining CS_affinity, it is important to include every server that runs Basic
History or OpcDA_Connector in Item Contents for every Selection Group/Node.
This can be achieved by adding All Nodes to every Selection Group/Node as the
last item.
6. Click Apply.
2PAA111693-611 A 24
3 800xA Base System
7. Verify the configuration in the Affinity Summary tab (Figure 3.4). The Affinity
Summary tab lists the configuration performed for all nodes in the system.
Figure 3.4: Affinity Summary Tab
8. Repeat this procedure for the AS affinity.
Applying Affinity Settings to the Services
Make sure that Affinity is not set to Strictly Local (pre-defined Affinity Object) on any
services in the system.
ABB recommends setting up Affinity for services according to Table 3.2.
Table 3.2: Affinity Services
Affinity
Services
Objects
AS_affinity FSD, AspectDirectory, Cross Referencing Server, Alarm Manager,
Event Storage, Event History, Event Hub
CS_affinity Basic History, OpcDA_Connector, OPC UA Connect
When the Affinity aspects have been configured, they must be set up to be used by the
services in the system.
1. Use the Structure Selector to select the Service Structure.
2. Use the Object Browser to select the service to be load balanced.
2PAA111693-611 A 25
3 800xA Base System
3.2 Configuring Users and Permissions
3. Select Service Definition in the Aspect List Area.

5. Select the desired Affinity aspect from the Affinity drop-down box and click Apply.
3.2 Configuring Users and Permissions

The windows users and groups shall be added and configured in the 800xA System.
Refer to System 800xA Installation, Update and Upgrade Getting Started (2PAA111708*)
for creating users and groups and System 800xA Administration and Security
(3BSE037410*) for configuring permissions.
3.3 Time Services

Refer to Section 20 800xA Clock Synchronization for more information to configure Time
Services.
2PAA111693-611 A 26
4 SoftPoint Server
4.1 Configuring SoftPoint Services
4 SoftPoint Server
The SoftPoint Server can be configured to run on any type of 800xA System server node.
The topic describes how to configure the installed SoftPoint Server software using the
Softpoint Generic Control Network Object. This will automatically:
• Configure the SoftPoint Service Group and Service Provider objects.
• Configure the Virtual Control Network by which other system applications (History,
desktop applications, and so on) can access the SoftPoint data on that node.
• Configure the Source Definition aspect for each network. This is used to deploy the
SoftPoints on their respective nodes.
• Integrate the SoftPoint alarm and event messages into the 800xA System Event
Collector Service.
SoftPoint supports redundancy. When installed on a redundant Connectivity Server, it
should follow the rules as established in the connectivity for configuration. For greatest
efficiency between Calculations and SoftPoints, put the Primary Calculation Server on
the same node as the Primary SoftPoint Server.

To configure the SoftPoint services:
2. Use the Object Browser to navigate to Control Structure and right-click:
Root, Domain
and then click New Object.

3. This displays the New Object dialog box. Expand the Object Types category, and
select:
Softpoint Generic Control Network (under Softpoint Basic Object Types).
4. Enter a name to identify the network (for example: Network1) and then click Create.
2PAA111693-611 A 27
4 SoftPoint Server
5. Select the Generic Control Network Configuration aspect of the new object in the
Aspect List Area.
6. Click the Configure tab in the Preview Area to produce the view shown in Figure
4.1.
Figure 4.1: Generic Control Network Configuration Aspect
7. Click Configure in the Server Settings area. This opens the Choose Connectivity
Server Node dialog box.
8. Select the primary Connectivity Server node and click OK.
9. Click OK at the “configuration completed” message.
10. Click Configure in the Server Settings area again if redundant Connectivity Servers
were created. This opens the Choose Connectivity Server Node dialog box again.
a. Select the Node is redundant provider check box.
b. Select the redundant Connectivity Server node where the SoftPoint Server
software is installed and click OK.
2PAA111693-611 A 28
4 SoftPoint Server
11. Click OK at the “configuration completed” message.

12. In order for the System Message Service to collect alarms and events from the
SoftPoints on this network, the OPC Alarm Server for SoftPoint messages must be
added to an Event Collector Service Group. This is done automatically when the
Alarm and Event Settings portion of the Generic Control Network Configuration
aspect is configured.
a. Click Configure in the Alarm and Event Settings area of the Generic Control
Network Configuration aspect.
b. Add providers in the same way as for the server settings.
2PAA111693-611 A 29
2PAA111693-611 A 30
5 800xA for AC 800M
5.1 Workflow
5 800xA for AC 800M
AC 800M is a hardware platform consisting of individual hardware units, which can be

configured and programmed to perform multiple functions.
The hardware units that form the AC 800M Controllers are:
• Processor units
• Communication interfaces for different protocols
• CEX-Bus interconnection units
• Power supply units
• Battery back-up unit (not supported with PM891 Processor Unit)
This topic covers:
• Procedures to set the IP addresses and upgrade the firmware in the processor units.
• Procedures to configure the OPC Server for AC 800M.
5.1 Workflow
The workflow for AC 800M Controllers is shown in Figure 5.1 .
2PAA111693-611 A 31
5 800xA for AC 800M
5.2 AC 800M Controller
Figure 5.1: Workflow for AC 800M Controllers

This topic describes how to initially set the IP addresses in the processor units. It also
describes how to download firmware in the processor unit. The firmware is the basic
runtime software in the processor units and their (optional) communication interfaces.
This topic contains the following subtopics:
• Set the IP Address in the Processor Unit
• Verify the Processor Unit IP Addresses
• Download Processor Unit or Communication Interface Firmware using the Control
Network
5.2.1 Set the IP Address in the Processor Unit

For redundant AC 800M Controllers, perform this procedure only in the primary
(upper) processor unit.
2PAA111693-611 A 32
5 800xA for AC 800M
Each processor unit must have a unique IP address and associated subnet mask before
using it in a Control Network. The IP address can be changed through the Control Network
once it is initially set.
At the first setting of an IP address in a controller, a serial RS-232 tool cable (TK212 or
TK212A) is needed to connect the controller and the Control Builder M node. The Control
Builder M software must be installed on the node.
Check that the Serial Firmware Upgrade tool is not running. If it is, that application
will allocate the COM port.
1. Connect the serial RS-232 tool cable between the Control Builder M node and the
tool port of the controller, as specified in Table 5.1.
Table 5.1: Cable Connection
Controller Tool Port Connector Cable Name

AC 800M COM 4 RJ 45 TK212 or TK212A
If the controller is redundant, the serial line should be connected to the primary CPU
and the power on the backup CPU should be off.
2. Select the appropriate COM port for the Control Builder M node (default COM 1).
No program capable of blocking the selected COM port must be running during the
upgrade procedure.
3. Select:
ABB Start Menu > ABB System 800xA > Engineering > Utilities > IPConfig
For more information on ABB Start Menu, refer to System 800xA Tools
(2PAA101888*).
2PAA111693-611 A 33
5 800xA for AC 800M
4. In the IPConfig tool (Figure 5.2), select:

Settings > Advanced mode
Figure 5.2: IPConfig Tool
5. Click Connect.
6. Hold down the Init/Reset button on the controller for at least 3 seconds until the
green R LED starts to blink.
7. Release the Init/Reset button and the controller will perform a cold test. Wait about
a minute.
a. If the connection procedure succeeds, the current IP settings (the IP Ethernet
address and its associated subnet mask) will be displayed in the IP Config tool
as shown in Figure 5.2.
b. If the connection procedure fails, a time-out message appears. Check the cables
and repeat the steps in this procedure up to this point.
The Enable Autostart check box is normally cleared. Refer to the IPConfig Online
Help for more information.
2PAA111693-611 A 34
5 800xA for AC 800M
8. Enter a unique primary Ethernet interface IP address and subnet mask in the Primary
Ethernet IP-Address and Primary Ethernet Subnetmask boxes. Refer to Acquiring
Installation and Configuration Parameters section in System 800xA Installation and
Upgrade Getting Started (2PAA111708*) for more information on IP Address.
Example: IP address 172.16.0.201, Subnet mask, 255.255.252.0.
9. Click Store in the IPConfig tool to send the new address to the controller.
10. If using a redundant controller, set the addresses as described in Set the IP
Addresses in the Backup (Lower) Processor Unit.
11. Hold down the Init/Reset button on the controller for at least three seconds to restart
it.
Set the IP Addresses in the Backup (Lower) Processor Unit

For an AC 800M Controller with redundant processor units (for example PM861) four
Ethernet IP addresses need to be entered:
• Primary Ethernet port on the primary (upper) processor unit.
• Secondary Ethernet port on the primary (upper) processor unit.
• Primary Ethernet port on the backup (lower) processor unit.
• Secondary Ethernet port on the backup (lower) processor unit.
These four addresses must be known by both the primary (upper) and backup (lower)
processor units; however, it is only necessary to set the IP addresses in the primary
(upper) processor unit. The backup (lower) processor unit will automatically be configured
by the primary (upper) processor unit.
To set the two backup IP addresses using the IPConfig dialog box:
1. When connecting using the IPConfig tool as in Step 5. under Set the IP Address in
the Processor Unit :
a. Disconnect power from the backup (lower) processor unit.
b. Connect the serial RS-232 tool cable to the primary (upper) processor unit.
c. Connect the Redundant Control Unit (RCU) link cable between the RCU Link
ports on the primary (upper) and backup (lower) processor units. Make sure to
connect the end of the cable marked Upper to the primary (upper) processor
unit.
2. Verify that the Primary Ethernet Interface IP address is correct (as set in Step 8.
under Set the IP Address in the Processor Unit ).
2PAA111693-611 A 35
5 800xA for AC 800M
3. Select:
Settings > Set Backup IP Addresses
4. Select Ethernet 1.
5. Select the Obtain an IP address by using default rule check box.
6. Click Store Interface Settings.
7. Click OK when the message appears stating:
“This will update the IP settings for the Backup CPU’s Ethernet interface 1. Continue?”
“Backup CPU’s Ethernet interface 1 stored successfully.”
9. Select Ethernet 2.
10. Select the Obtain an IP address by using default rule check box.
11. Click Store Interface Settings.
“This will update the IP settings for the Backup CPU’s Ethernet interface 2. Continue?”
“Backup CPU’s Ethernet interface 2 stored successfully.”
When connecting power to the backup (lower) processor unit, its IP addresses will be
assigned. All addresses except the one for the secondary Ethernet port on the primary
(upper) processor unit can be set using the IPConfig tool. That IP address is set in the
project created with the Control Builder M.
5.2.2 Verify the Processor Unit IP Addresses

Before connecting an AC 800M Controller to a Control Network, the IP addresses in the
processor units can be verified by connecting to the processor unit using the IPConfig
tool.
To verify the controller IP address and connect status:
1. Connect a network cable between CN1 on the controller and the Control Network.
2. Open a Command Prompt window on a node connected to the Control Network.
3. At the command prompt, type ping <IP address>.
where: <IP address> is the IP address of the processor unit in question.
4. Press Enter.
2PAA111693-611 A 36
5 800xA for AC 800M
5. The controller should properly answer the ping command.

6. Repeat the procedure for all controllers to be connected to the control network.
5.2.3 Download Processor Unit or Communication Interface Firmware

using the Control Network
After the initial setting of the IP addresses, further upgrades can be done through the
Control Network. This also includes downloading or upgrading the firmware in
communication interfaces that are a part of the AC 800M controller (for example,
PROFIBUS DP - CI854).
The download is done through the Control Builder M running on a node connected to
the same Control Network as the AC 800M Controller. Firmware can only be upgraded
when the controller has no application program.
In case Control Network does not work, there are couple of methods to update the
firmware.
The firmware can be upgraded using a serial RS-232 tool cable, refer to Firmware
Upgrade in System 800xA Control AC 800M Getting Started (3BSE041880*).
It can also be made using a Compact Flash image. A serial RS-232 tool cable is
then not needed. Refer to Upgrading Controller Firmware using Backup Media
in System 800xA Control AC 800M Configuration (3BSE035980*).
Download procedure:
1. Make sure that the controller(s) are reset i.e. being empty of all application
information, by pressing the init button until the (R)un LED blinks (>3 seconds).
2. In Control Builder M, open a project containing the controller. Alternatively, create
a new AC 800M project and enter the correct system identity (IP address) for the
processor unit.
3. Make sure the relevant libraries are connected under Libraries > Hardware, and
also that they are connected to the controller.
4. Select Show Remote System in the controller shortcut menu.
5. Select Show Firmware Information.
6. Evaluate the information for the current firmware in the processor unit and other
units. Firmware available in libraries is presented in the combo boxes.
Both processor units in a redundant controller can be upgraded simultaneously.
Connect the power to both and wait for the yellow DUAL LED to be lit. Else update
each processor unit individually (connect power to one and disconnect power from
the other).
2PAA111693-611 A 37
5 800xA for AC 800M
5.3 AC 800M SoftController
7. Choose the new alternative (or the same) firmware for each unit and select the
corresponding Download check box to the right.
8. Click Download Firmware for selected units to start downloading.
9. The new firmware is downloaded after the old version has been removed. When
the upgrade is complete, the controller restarts automatically. During this sequence
it is not possible to communicate with the controller.
10. To verify, confirm that the upgrade is complete by testing the firmware, or by reading
the controller system log. If the upgrade program in the controller detects any errors
while performing the upgrade, they are written to the controller system log.

This topic describes how to enable secure download between Control Builder and AC
800M SoftController.
5.3.1 Setup and Configre Secure Download

Secure download between Controller Builder and AC 800M SoftController can be enabled
by using certificates. The Control Builder will sign the downloaded configuration during
download and the SoftController will verify the downloaded configuration is created from
a trusted source.
The following steps needs to be followed to enable the secure download.
Step 1: Copy Help Tools

Copy the folder Tools/Security from the installation media to the machine running the
Control Builder and to all machines that will run a soft controller that should be able to
accept secure downloads.
Step 2: Create Certificate

On the machine running the Control Builder, run the tool CBCertTool.exe in the
Tools/Security folder. The tool must be run with administrator privileges. The tool creates
• A self signed certificate containing the private and public key.
• A root trust certificate containing only the public key.
2PAA111693-611 A 38
5 800xA for AC 800M
The certificates (both the self signed and the root trust) are named
CBSelfSigned@<computer name> and are registered in the Windows Certificate Store.
The root trust certificate is also exported to a file named CBSelfSigned@<computer
name>-Root.cer located in C:\ProgramData\ABB.
A log file showing the result of operation is created and stored in

C:\ProgramData\ABB\Logs.
Step 3: Give the Control Builder Access to the Private Key

For the Control Builder to be able to use the certificate to add a digital signature, the
user that runs the Control Builder must have access to the private key.
On the machine running the Control Builder, launch the Manage Computer Certificates
from the Windows button.
2PAA111693-611 A 39
5 800xA for AC 800M
Locate the certificate containing the private key in the Personal/Certificates folder.
Right-click on the certificate and select All Tasks ->Manage Private Keys. Click on Add
and add the user running the Control Builder, in this example a local user named CBUSer.
The Control Builder user should be assigned rights to at least read the certificate.
Click Apply and then OK.
Step 4: Enable Signed Downloads on Control Builder Machine

From the Tools/Security folder, start the application Securing Application Download with
administrator privileges. Opening of this tool will create the required registry folder if not
existing.
2PAA111693-611 A 40
5 800xA for AC 800M
Check the Sign Application Downloads checkbox and select the certificate to be used
from the list. If a soft controller that should be able to accept signed downloads will run
on the same machine, also check the Require Signed Downloads checkbox. Then click
Apply.
Step 5: Distribute the Root Trust Certificate

If the Control Builder is supposed to perform secure download to SoftControllers running
on different machines than the Control Builder, the root trust certificate must be installed
on all those machines. Copy the file CBSelfSigned@<computer name>-Root.cer to
each soft controller machine. On each machine right-click on the copied certificate file
and select Install certificate….
Select Local Machine and click Next.
2PAA111693-611 A 41
5 800xA for AC 800M
Select Place all certificates in the following store.

Select Trusted Root Certification Authorities, as the following describes.
Select OK.
2PAA111693-611 A 42
5 800xA for AC 800M
Select Next.
Select Finish.
2PAA111693-611 A 43
5 800xA for AC 800M
5.4 Configure the OPC Server for AC 800M
Step 6: Enable Signed Downloads on SoftController Machine

From the Tools/Security folder, start the application Securing Application Download with
administrator privileges. Opening of this tool will create the required registry folder if not
existing:
Check the Require Signed Downloads checkbox and click Apply.

It is important to plan the OPC Server for AC 800M configuration before performing the
OPC Server for AC 800M configuration procedures.
5.4.1 Configuration Planning

The OPC Server for AC 800M must be configured to specify which controllers will provide
the OPC Data Access and OPC Alarm and Event data, and to make other settings
necessary for the operation of the OPC Server for AC800M. The OPC Server for AC
800M is set up through an OPC Server Configuration panel.
Each connected controller, the OPC server has access to all relevant data, both Data
Access and Alarm & Event. The OPC Server Configuration Panel shows all connected
controllers.
2PAA111693-611 A 44
5 800xA for AC 800M
Figure 5.3: OPC Server Configuration Panel
At startup the OPC Server loads automatically the connection configuration. The
configuration is stored automatically when it is modified.
2PAA111693-611 A 45
5 800xA for AC 800M
There are a number of settings that can be set in the OPC Server Configuration Panel
• Update Rate setting: The cache update rate, set in milliseconds, controls how often
the OPC Data Access Server updates its internal cache with data from a certain
controller. To distinguish between fast and slow update rates there are five categories
for simple values (integer, real, bool) and a separate category for strings.
To ensure that subscribing OPC clients can access changed values at their requested
update rate, the time (value) for cache update rate should be set shorter than the
fastest OPC group update rate. Example: the OPC client creates an OPC group
with an update rate of 1000ms. This means that items added to this OPC group will
be reported to the OPC client once every second. In the OPC server, the MMS
communication for this group is put in the High category, which means that items
in this category will be read from the controller every 500ms.
2PAA111693-611 A 46
5 800xA for AC 800M
• Cold retain values: The OPC Server for AC800M can periodically save the Cold
Retain values of the controllers. It will transfer them from the controllers and save
the values into the Aspect Directory. In the dialog for Cold Retain values, the Offset
determines the first time the Cold Retain values should be stored, after this the
interval time determines when to store the cold retain values. The purpose of the
Offset is to prevent the situation that two (or more) OPC Servers fetch Cold Retain
values from the same controller at the same time.
For more information about the the different settings please refer to 3BSE035983 AC800M
OPC Server, Chapter 3.
5.4.2 Additional Parameters

If changes are required to the OPC Server for AC 800M default settings as described in
Configuration Planning:
1. Open the Configuration dialog box (normally on the Connectivity Servers). Select:
ABB Start Menu > ABB System 800xA > OPC Server for AC 800M
2. Select Settings and select the menu item to change.
2PAA111693-611 A 47
5 800xA for AC 800M
3. Make the desired changes. Changes are automatically stored

4. If additional parameters require changes:
a. Run the Setup Wizard (on the Engineering Station). Select:
ABB Start Menu > ABB System 800xA > Setup Wizard OPC Server for AC
800M
b. Enter the required configuration parameters under Product.
If the Service Account (800xA Service User as entered in the System Software
User Settings dialog box) has not been specified, do this now. To get the Service
Account information, start the Configuration Wizard:
ABB Start Menu > ABB System 800xA > Configuration Wizard, then select the
System Software User Settings dialog box.
5.4.3 Connecting to Controllers

To connect to controllers:
1. Open the Configuration dialog box (on Connectivity Servers and other nodes where
the OPC Server for AC 800M is installed). Select:
ABB Start Menu > ABB System 800xA > OPC Server for AC 800M
2. In the main window of the OPC Server Configuration Panel enter the IP address of
the controller and specify whether or not AE should also be included, then press
Connect
To disconnect to a controller, highlight the controller in list of connected controllers and
right-click on it to get the context menu, then select Delete controller.
2PAA111693-611 A 48
6.1 Entering License Information for Connected Controllers
This topic describes post installation procedures for 800xA for Advant Master. Refer to
800xA for Advant Master Configuration (3BSE030340*) for more information on
configuration issues.
Alarms that are received from the controllers before an upload is performed will be
created as objects in Lost and Found in the Control Structure. To minimize the
risk of this happening, it is recommended to not connect the Connectivity Server to
the MB300 Network until an upload is performed.
6.1 Entering License Information for Connected

Controllers
All controllers, such as MasterPiece 200/1, Advant Controller 410, Advant Controller
450, Advant Controller 450RMC, and Safeguard 410, connected to the 800xA System
should be documented in the Advant Master Controller Licenses.txt file.
The Licenses.txt (Figure 6.1) file can be opened using notepad and is found in the
following directory on the Primary Aspect Server after installation of 800xA for Advant
Master:
<Installation path>\AC 400 Connect\
Licenses\Advant Master Controller Licenses.txt
The installation path is typically C:\Program Files(x86)\ABB 800xA.

Enter License information, network, and node numbers, and the product being used in
the respective column. Repeat this for all controllers being connected to the 800xA
System.
2PAA111693-611 A 49
6.1 Entering License Information for Connected Controllers
Figure 6.1: Advant Master Controller Licenses Text File
2PAA111693-611 A 50
7 800xA for AC 100
7.1 System 800xA Configuration
7 800xA for AC 100
This topic describes post installation procedures for 800xA for AC 100. Refer to 800xA
for AC 100 Configuration and Operation (3BDS013989*) and AC 100 OPC Server
Configuration and Operation (3BDS013988*) for more information on configuration and
operation issues.

7.1.1 Creation of AC100 AF 100 Network Object Instance
1. Open the Plant Explorer Workplace and select Control Structure.
2. Create an instance of the AC 100 AF100 Network object type.
In the Additional Arguments dialog, click Add and select the correct provider (that
is, the name of the server where the requested AC 100 OPC Server is installed).
Select the ProgID as ABB.AC100.1.
3. For a redundant OPC Server, create a new Service Provider object in the existing
service group.
7.1.2 Alarm and Event Server Startup

The System 800xA Alarm and Event Server in is not started automatically when 800xA
for AC 100 is added to the system. To start the Alarm and Event Server in the 800xA
System, perform the following steps:
2. Use the Structure Selector to open the Service Structure.
3. Use the Object Browser to navigate to and select (Figure 7.1):
Event Collector, Service > AC 100 Alarm Server, Service Group
2PAA111693-611 A 51
7 800xA for AC 100
4. Create a Service Provider:

a. Right-click AC 100 Alarm Server, Service Group and then click New Object.
b. The New Object dialog box appears.
c. Select Service Provider and enter a name in the Name box, such as AC 100
Alarm Provider 1.
d. Click Create.
5. Use the Object Browser to select the newly created Service Provider
6. Select Service Provider Definition in the Aspect List Area.
7. Click the Configuration tab in the Preview Area (if not already selected).
8. Select the node where the AC 100 Alarm Provider will run in the Node drop-down
list and click Apply.
Figure 7.1: AC 100 Alarm and Event Service Provider Configuration
2PAA111693-611 A 52
7 800xA for AC 100
9. Use the Object Browser to navigate to and select:

Event Collector, Service > AC 100 Alarm Server, Service Group
10. Select Service Group Definition in the Aspect List Area.

11. Select the Special Configuration tab.
12. Select ABB AC 100 OPC Alarm Server in the Alarm Server drop-down list and
click Apply.
Figure 7.2: AC 100 Alarm and Event Service Group Configuration
13. For a redundant AC 100 OPC Server, repeat Step 3. through Step 12., except choose
a different name in Step 4., such as AC 100 Alarm Provider 2.
2PAA111693-611 A 53
7 800xA for AC 100
7.2 Configuration and Operation
7.2 Configuration and Operation

All software products for using the Advant Controller 100 Series in an 800xA System are
now installed and ready to use. Refer to 800xA for AC 100 Configuration and Operation
(3BDS013989*) for more information on configuration and operation; for example,
procedures to connect an 800xA System to an AC 100 OPC Server. Refer to the Data
Access topic in System 800xA Configuration (3BDS011222*) to connect via DCOM,
and to use the DCOMCNFG tool to set the DCOM security setting.
7.3 Clock Synchronization and Daylight Saving Time

Refer to 800xA for AC 100 in Section 20 800xA Clock Synchronization for more
information to configure 800xA for AC 100 Clock Synchronization.
7.4 Installation Verification (Optional)

After performing the software and hardware installation, it is recommended that you
verify that the AC 100 OPC Server has been properly installed. To accomplish this:
1. Check that the AC 100 OPC Server utilities are available from the Start menu. Select:
ABB Start Menu > ABB System 800xA > 800xA for OCS Systems > AC 100 >
About AC 100 OPC Server
(2PAA101888*).
2. Select:
Control Panel > Programs and Features
to view if ABB AC 100 OPC Server is properly listed here.
3. Check the Windows Device Manager (Figure 7.3) and make sure that the CI527A
device and driver are working properly. The Device Manager is started by:
Control Panel > Device Manager
2PAA111693-611 A 54
7 800xA for AC 100
4. To find the CI527A Driver select:

View > Devices by type
and expand the AF100 icon.
Figure 7.3: Device Manager
5. Right-click ABB AF100 CI527A - PNP and then click Properties to open the ABB
AF100 CI527 - PnP Properties dialog box.
2PAA111693-611 A 55
7 800xA for AC 100
6. Click the Details tab (Figure 7.4) to find the correct version of the CI527A Hardware
IDs: This must contain DEV_0862 as shown in Figure 7.4.
Figure 7.4: CI527A Version Information
7. Verify that the services

• ABB AC 100 CI52X Manager
• ABB AC 100 OPC Server
• ABB AC 100 VFI Server
are listed and running by selecting:
Control Panel > Administrative Tools > Services
8. Use the Details tab in Windows Task Manager to verify that the following processes
are running, and that the User name is 800xA Service account:
• wiaopc.exe
• wiaci526.exe
• wivserver.exe
2PAA111693-611 A 56
7 800xA for AC 100
7.5 Product Verification

After performing the initial configuration of the AC 100 OPC Server, it is recommended
that you verify that the software has been properly configured and that the system has
contact with the Advant Fieldbus 100 network. To do this:
1. Verify that the About OPC Server box is shown correctly by starting the About AC
100 OPC Server dialog box (Figure 7.5):
About AC 100 OPC Server
Figure 7.5: About AC 100 OPC Server Dialog Box
2PAA111693-611 A 57
7 800xA for AC 100
2. Verify that the board is operational and all stations are reachable by viewing the AF
100 Diagnostics dialog box (Figure 7.6). For more information about the Diagnostics
function, refer to AC 100 OPC Server Configuration and Operation (3BDS013988*).
Select:
AF 100 Diagnostics
Figure 7.6: AF 100 Diagnostics Dialog Box
2PAA111693-611 A 58
7 800xA for AC 100
3. Check Windows Event Viewer to ensure that no fatal errors are reported from the
ABB AC 100 OPC Server. Select:
Control Panel > Administrative Tools > Event Viewer >
Windows Logs > Application
4. If the recommended verifications show problems, check the hardware of the CI527A
by doing the following:
a. Check that the green P (power) is lit.
b. Check that the yellow RX (receive) LED is lit (if other stations on the Advant
Fieldbus 100 network are up and running).
c. When the Advant Fieldbus 100 Interface is started, check that the yellow TX
(transmit) LED starts to blink.
2PAA111693-611 A 59
2PAA111693-611 A 60
8.1 Harmony Communication Configuration
This topic describes post installation procedures for 800xA for Symphony Plus Harmony.
8.1 Harmony Communication Configuration

The Harmony communication configuration consists of Harmony API Configuration.
8.1.1 Harmony API Configuration

Run the Harmony API Configuration utility on each Harmony Connectivity Server node.
1. Double-click the shortcut on the Windows Application Screen created during
installation. It is listed in ABB Symphony Plus.
2. Click Help to view the ICI to Computer Interface Setup guide provided with the
HarmonyAPI. Follow the instructions in the guide to configure the Harmony API for
the ICI type present on the node.
2PAA111693-611 A 61
8.2 OPC Server Network Object Setup
Figure 8.1: Harmony API Configuration Dialog Box
8.2 OPC Server Network Object Setup

Create an OPC Server Network object for each Primary Harmony Connectivity Server
node.
2. Use the Structure Selector to open the Control Structure.
3. Right-click on Root, Domain and then click New Object.
4. Select the List Presentation check box.
5. Select Harmony OPC Server Network from the list of objects.
6. Enter a name and click Next.
7. Click Add.
8. Select the node that contains the Connectivity Server and click OK.
Redundant Connectivity Server nodes are listed in addition to Primary Connectivity

Server nodes. Select both Primary and Redundant Connectivity Server nodes.
2PAA111693-611 A 62
8.3 Update Alarm Manager
9. In the Harmony OPC Server, ProgID field, select ABBMaestroNT.OPCServer.1

from the drop-down list.
10. Click Create. The new OPC Server Network object is created and appears under
Root, Domain in the Control Structure.
11. Select ServerConfig Aspect of the newly created OPC Server Network Object.
12. Assign the Primary and Backup Hosts as appropriate in the Connectivity Server
Nodes. Note that if there is no redundant server, the Backup Host can be left
unassigned.
13. Click Apply.
8.3 Update Alarm Manager

Update Alarm Manager to Harmony recommended settings.
Clearing the Make new alarm entry each time a condition gets active is a system
wide setting. This is only a recommendation for 800xA for Symphony Plus Harmony.
It may conflict with other applications.
Services > Alarm Manager, Basic, Service Group
2. Select the Special Configuration tab in the Preview Area.
3. Clear the Make new alarm entry each time a condition gets active check box
and click Apply.
8.4 Harmony Uploader

Upload Harmony Tags from a .mdb file exported from the S+ Engineering for Harmony
engineering tool (or generated from the Standalone ConfigServer Export Tool if
upgrading) using the Uploader aspect (if it has not been performed in previous
procedures).
2. Use the Structure Selector to select the Control Structure.
3. Use the Object Browser to select the Harmony OPC Server Network object.
4. Select the Uploader aspect in the Aspect List Area.
5. Select the Import Tab.
2PAA111693-611 A 63
8.5 Restart Connectivity Server
6. Use the Browse button to navigate to and select the .mdb file to import from in the
File Path.
7. Use the Tag Table pick list to select the table containing the Tag Configurations to
import.
8. Select Start Import.
Refer to 800xA for Symphony Plus Harmony Configuration (3BUA000157*), for

more information.
8.5 Restart Connectivity Server

After the upload of the 800xA for Symphony Plus Harmony Configuration Server
Information, perform the following procedure to restart the Connectivity Servers:
1. Open Plant Explorer and navigate to Service Structure > Services > Harmony
Executive, Service > Basic, Service Group > Harmony Executive Service
Provider.
2. Select the Service Provider Definition aspect.
3. Click the Configuration tab and clear the Enabled check box.
4. Click Apply and wait for the current status to change to Undefined.
5. Select the Enabled check box, click Apply, and wait for the current status to change
to Service.
2PAA111693-611 A 64
9 800xA for MOD 300
9.1 Setting Up Clock Synchronization
9 800xA for MOD 300
This topic provides post installation procedures for 800xA for MOD 300.
9.1 Setting Up Clock Synchronization

Refer to 800xA for MOD 300 in Section 20 800xA Clock Synchronization for more
information to configure 800xA for MOD 300 Clock Synchronization.
9.2 Setting Alarm Manager Options

Clear the Make new alarm entry each time a condition gets active check box:
Clearing the Make new alarm entry each time a condition gets active check box
is a system wide setting. This is only a recommendation for 800xA for MOD 300. It
may conflict with other applications.
Services > Alarm Manager, Basic, Service Group

4. Clear the Make new alarm entry each time a condition gets active check box
and click Apply.
9.3 Setting Up the System Structure

Refer to the Set Up System Structure topic in Section 2 - Administration in 800xA
for MOD 300 Configuration (3BUR002417*) to set up the System Structure.
2PAA111693-611 A 65
2PAA111693-611 A 66
10 800xA for DCI
10.1 Configure a Single NIC Interface to the DCU
10 800xA for DCI
This topic describes post installation procedures for 800xA for DCI.

The DCI control network must be Class A (127.0.0.0 or less) and must have a subnet
mask of 255.0.0.0.
Any NIC used for communicating on the DCI control network must be configured to
10Mbps half-duplex and must have promiscuous mode enabled.
ABB DCI Select Network modifies the registry. You must have Administrative rights
to use this program.
Most 800xA for DCI installations will use the ABB ECC MUX to communicate with DCU
controllers in order to take advantage of the redundant network. However, a single NIC
may be used to communicate with the DCUs if redundancy is not an issue. If a single
NIC is used, then it must be designated as the one used for the DCI Control Network
(CNET) as follows:
If the ABB ECC MUX Redundant Ethernet driver has not been installed, configure the
path for the network services by performing the following steps:
1. Select:
ABB Start Menu > ABB System 800xA > DCI > ABB DCI Select Network
(2PAA101888*).
The ABB DCI Select Network dialog box will appear (Figure 10.1). The X in the
first row indicates that no network is selected.
2PAA111693-611 A 67
10 800xA for DCI
Figure 10.1: ABB DCI Select Network Dialog Box
2. Choose the network that 800xA for DCI will use by clicking on the row of the desired
network adapter.
Choose the network by IP address. The physical name is provided for help in the
Description column.
3. Click OK. The network is now selected.

4. Restart the node to activate the selection.
The next time the network service is run, it will automatically default to the last chosen
network. If desired, repeat Step 1. through Step 4. to choose a new network.
2PAA111693-611 A 68
11.1 On Freelance Connectivity Server Node
This topic describes post installation procedures for 800xA for Freelance. Refer to 800xA
for Freelance Configuration (3BDD011812*) for more information on configuration.

11.1.1 Re-create OPC Server Resource IDs
1. Note down all the existing OPC Server resource IDs and then delete them using
Freelance Configure/Settings tool
2. Re-create all the OPC Server resouce IDs again with the help of Freelance
Configure/Settings tool
3. Restart Freelance OPC Server
11.1.2 Add Windows Firewall exceptions

Normally all the required firewall exceptions are added automatically when the Freelance
Engineering software is installed. It has been observed that in some exceptional cases,
the required firewall exceptions are not getting added. In those exceptional cases, firewall
exceptions for OPCSRV.EXE and TMSYNC.EXE needs to be added manually.
To add required firewall exceptions for Freelance Software, the steps involved are:
1. Launch Windows Firewall (available in Windows Control Panel)
2. Click on "Advanced Settings" in the Firewall window
2PAA111693-611 A 69
3. Click on "Inbound Rules"

4. Under "Inbound Rules", look for "Freelance OPC Server TCP" and "Freelance OPC
Server UDP". If these entries are available move to Step 5. If these entries are not
available, add these entries with the following steps:
a. Click "New Rule..." under "Action" column on the right hand side
b. Select "Rule Type" as "Program"
c. Select radio button "This program path" and specify the path of the Freelance
OPC Server EXE (most likely "C:\Program Files
(x86)\ABB\Freelance\exe\opcsrv.exe")
d. Click NEXT
e. Choose "Allow the connection" and click NEXT
f. Make sure all three "Domain", "Private" and "Public" are selected and then click
NEXT
g. Give the rule a name, e.g. "Freelance OPC Server" and click FINISH
2PAA111693-611 A 70
12 PLC Connect
12.1 Control Network Setup
12 PLC Connect
This topic provides post installation procedures for PLC Connect.

The SoftPoint Server is a subset of PLC Connect. Both use the same server processes
and share a common real-time database (RTDB). PLC Connect and the SoftPoint Server
can coexist in the same system, but the setup differs depending on whether PLC Connect
and the SoftPoint Server are installed on the same node, or on separate nodes. Refer
to Figure 12.1 for an example.
Figure 12.1: PLC Connect and SoftPoint Server Coexistence
Refer to System 800xA PLC Connect Configuration (3BSE035041*) (only if needed)

for information on how to configure PLC Connect specific server processes. For
example, to use a customer generated program with the 800xA System.
12.1 Control Network Setup

For each control network, a connection between the control network and its PLC Connect
Connectivity Server must be established (a Connectivity Server node with the PLC
Connect system extension). This is necessary in order to gain access to the dynamic
process data that the Connectivity Servers provide. For more information, refer to System
800xA PLC Connect Configuration (3BSE035041*).
2PAA111693-611 A 71
2PAA111693-611 A 72
13.1 Web-Enabled Views on Non-800xA Systems
This topic describes post installation procedures for Asset Optimization.

The initial trust is not established between client and server after installation.
Distributing the certificate is a manual step, see System 800xA Administration and
Security (3BSE037410*) for more details.
13.1 Web-Enabled Views on Non-800xA Systems

The software requirements on non-800xA systems required to support web-enabled
Asset Optimization views are:
• Internet Explorer.
• MS XML 3.0 with Service Pack 2 or later.
• Microsoft Visual C++ 2008 SP1 Re-distributable Package (x86). (vcredist_x86.exe
available for download from Microsoft.
The maximum security settings on non-800xA systems required to support web-enabled
Asset Optimization views are:
• Set Local Intranet security to High.
• Select Custom Level and set the following:
– Download signed ActiveX controls: Prompt.
– Run ActiveX controls and plug-ins: Enable.
– Script ActiveX controls marked for safe scripting: Enable.
– Active scripting: Enable.
Accessing the Asset Optimization thin client interface always requires user
authentication for Asset Optimization web pages.
2PAA111693-611 A 73
13.2 Maximo Integration

This section describes the configuration and setup information required for Maximo
Server.
ABB Enterprise Connectivity (ECS) must be installed in order to access Maximo

Server.
The Maximo Server name and IP address must be entered in the Windows hosts
file on the node where ECS is installed.
13.2.1 Maximo Business Object (Maximo 6.2, Maximo 7.1 and Maximo 7.6)
Table 13.1 and Table 13.2 displays the web services that need to be configured on the
Maximo Server. Configure the following web services on the Maximo Server. Contact
Maximo technical support for detailed procedure.
Table 13.1: Maximo Business Object (Maximo 6.2)
Integration
AO Function Interface
Object Name
MXWO Submit Work Order MXWOInterface
MXWO View Active Work Order, Work Order MXWorkOrderQuery
History
MXASSET View Equipment Status MXASSETQInterface
SPAREPART View Spare Parts MXSparePartQInterface
PM Vier Prev Maint Schedule MXPMQInterface
MXINVENTORY Spare Part Availability (This function is SPAVAILQ
called from View Spare Part aspect)
Table 13.2: Maximo Business Object (Maximo 7.1 and Maximo 7.6)
Integration Object Object

Name Structure
WORKORDER MXWO Submit Work Order, View MXWO
Active Work Order, Work
Order History
ASSET MXASSET View Equipment Status MXASSET
2PAA111693-611 A 74
Table 13.2: Maximo Business Object (Maximo 7.1 and Maximo 7.6)
(Continued)
Integration Object Object
Name Structure
SPAREPART MXSPAREPART View Spare Part MXSPAREPART
PM MXPM View Preventive MXPM
Maintenance
INVENTORY MXINVENTORY View Spare Part MXINVENTORY
Availability (This function
is called from View Spare
Part aspect)
Do not change the interface names in the Table 13.1 and Table 13.2. Modifying the
interface names involves additional engineering effort.
2PAA111693-611 A 75
13.3 SAP/PM Integration
13.3 SAP/PM Integration

ABB Enterprise Connectivity (ECS) must be installed in order to access SAP Server.
The Asset Optimization integration with the SAP/PM module requires that the SAP
administrator install ABAP code on the SAP/PM production server where the PM module
is installed.
1. Navigate to the directory where Asset Optimization software is installed.
2. Use Windows Explorer to locate the following directory:
...\Asset Optimization\SAPConnectivity\SAP-ABAP
3. This directory contains the source for the ABB ABAP integration code and
documentation that describes the ABAP code integration.
The ABB ABAP integration code source files are:
• Z_ABB_EQUIPMENT_DETAIL.ABAP.doc
• Z_ABB_MS_LIST.ABAP.doc
• Z_ABB_NOTIFICATION_CREATE.ABAP.doc
• Z_ABB_NOTIFICATION_LIST.ABAP.doc
• Z_ABB_OBJECTSTATUS_LIST.ABAP.doc
• Z_ABB_WORKORDER_LIST.ABAP.doc
• Z_ABB_WORKORDER_HIST1.ABAP.DOC
Reference documents include the following:
• SAP RTAO Development.doc
• - Z_ABB_PM_FunctionGroup-Modules.doc
Refer to the SAP/PM Basis and ABAP integration personnel for details involving the
addition of ABAP-enabled interfaces in SAP.
ECS SAP Plugin uses the Librfc32.dll and Librfc32u.dll to communicate with
the SAP System. This version of the dll is specific to SAP Server.
Copy the dll from SAP Server to the following folder:
<InstallDirectory>\Program Files\ABB Industrial IT\cpmPlus Enterprise
Connectivity\Service
2PAA111693-611 A 76
13.4 Internet Explorer Configuration
13.4 Internet Explorer Configuration

To configure Internet Explorer for use with Asset Optimization:
1. Use standard Windows procedures to access the Local Area Network (LAN)
Settings dialog box.
2. If proxy configuration is selected, select the Automatically detect settings check
box.
13.5 Excel Initialization

The following procedure is necessary if using the XY Profile Deviation Asset Monitor.
Failure to perform the required Microsoft Excel user setup when using the XY Profile
Deviation Asset Monitor may cause the AO Server startup to fail.
1. Use the 800xA Service User account to open Microsoft Excel at least once.
2. Perform the required user setup (first time execution installation user initials).
2PAA111693-611 A 77
2PAA111693-611 A 78
14.1 Fieldbus Device Type Preparation (Optional)
This topic describes post installation procedures for the Device Library Wizard.

Perform the following steps at the point of time the Device Types to be used in the 800xA
System are known.
14.1.1 Installing Fieldbus Device Types

The following steps for Device Types need to be carried out on system nodes where
Device Management PROFIBUS HART or Device Management FOUNDATION
Fieldbus functionality is used. The following steps are not required to be performed
on thin client nodes and separate Domain Controller nodes. Perform the install
Device Types procedure on the nodes in the following sequence:
Install the Device Types on the Primary Aspect Server node before starting to install
them on other system nodes (DLW Client nodes). Do not run parallel installations
of Device Types on other system nodes unless all Device Types are installed on
the Primary Aspect Server node. Installation of Device Types on other system nodes
can be done in parallel after they are installed on the Primary Aspect Server node.
DLW Client nodes:
• Redundant Aspect Server.
• Connectivity Servers (including redundant Connectivity Servers).
• Application Servers.
• Clients.
2PAA111693-611 A 79
Perform the following on Primary Aspect Server:

1. Start the Device Library Wizard:
ABB Start Menu > ABB System 800xA > Device Mgmt > Device Library Wizard
2. Navigate to the Device Library Wizard main dialog box and select:
Extract Device Types > Extract Device Types via Manual Selection.
3. Click Browse and navigate to the System 800xA media.
4. In the Browse dialog box, select all Device Types required for system engineering
and start extracting.
If the installation media does not contain all Device Types, the missing Device Types
may be available for download from ABB Library and myABB/My Control System
portal.
Continue with this procedure after extracting all required Device Types.
5. Navigate back to the Device Library Wizard main dialog box after a successful
extraction.
6. Select:
Device Type Administration > Install Device Types > (required protocol
(FOUNDATION Fieldbus, HART or PROFIBUS)
7. Each listed Device Type includes a Release Note for the corresponding Device Type
object. Right-click on the listed Device Type to open the Release Note. Read the
Release Note carefully for detailed installation and engineering information or
limitations.
8. Select the Device Types required for engineering in the system and follow the install
procedure.
9. Exit the Device Library Wizard.
Perform the following on DLW Client nodes:
1. Start the Device Library Wizard:
ABB Start Menu > ABB System 800xA > Device Mgmt > Device Library Wizard
When Device Library Wizard is started the Device Types installed on Primary Aspect
Server automatically copied.
2. Select:
Device Type Administration > Install Device Types > (required protocol
(FOUNDATION Fieldbus, HART or PROFIBUS)
2PAA111693-611 A 80
3. Select the Device Types required for engineering in the system and follow the install
procedure.
4. Exit the Device Library Wizard.
2PAA111693-611 A 81
2PAA111693-611 A 82
15.1 Information Management Setup
This topic describes post installation procedures for Information Management.

Some procedures in this topic require administrator-level user privileges. The user
must be a domain user with Administrator privileges if the Information Management
Server resides in a domain. Use the 800xA Installing User account.
Verify HistoryAdmin user group is available after oracle instance creation.

800xAService and 800xAInstaller must be part of this group.
The initial trust is not established between client and server after installation.
Distributing the certificate is a manual step, see System 800xA Administration and
Security (3BSE037410*) for more details.

Use the post installation configuration assistant installed with the Information Management
software to ensure that installation and post installation procedures are completed in the
correct sequence.
To start the configuration assistant, select:
ABB Start Menu > ABB System 800xA >
Information Mgmt > IM Configuration Assistant
(2PAA101888*).
The Configuration Assistant, Figure 15.1, lists the installation and post installation
requirements in the order in which they must be completed.
Each procedure has a dedicated row. The row indicates whether the procedure is required
or optional, whether or not the procedure has been completed, the action to be performed
when the procedure is started from the assistant, and any special considerations and
guidelines that apply to the procedure.
2PAA111693-611 A 83
The rows are also color-coded. Procedures that have been completed are black.
Uncompleted required procedures are red, and uncompleted optional procedures are
brown. Some rows are headings for multistep procedures; for example, step 4.0
Configuring the DBA (ADO) Data Provider for Oracle. These rows do not have
an associated action, since the actions are performed in the steps following them. The
associated steps are sequentially numbered, for example 4.1, 4.2, and so on. Instructions
for the selected procedure (or step) are indicated in the Instructions box in the upper
right corner of the display.
Figure 15.1: Information Management Configuration Assistant
2PAA111693-611 A 84
Use the procedures in this topic and the Configuration Assistant for:
• Creating a History Database Instance (required).
• Initializing communication settings and Starting Process Administration Supervision
(PAS) (required).
• Configuring the DBA (ADO) Data Provider for Oracle Data (optional) Oracle data
access is required for PDL access for Batch management, and/or history message
log access. It is also required for general SQL functionality offered in DataDirect
and SQLBrowser. In this revision, the System Installer defines the AID users when
the IM node is added to the system planner. One of the users must be used to
initialize the ACC Setup.
15.1.1 Referenced Post Installation Procedures

When completed with the configuration assistant, refer to the following list to determine
whether any other post installation is required to set up the system and make it ready
for application building. These procedures are covered in the referenced instructions.
• One or more History Source aspects must be configured to support operator trend
and historical data collection. Refer to Section 5 - Configuring History Database
in System 800xA Information Management Configuration (3BUF001092*).
• Add-in tools for DataDirect and Information Management History Bulk Configuration
are added into Microsoft Excel on a user basis.
– If it is intended to use the 800xA Application Scheduler to run reports created
with DataDirect (Excel Data Access). Before running a report, DataDirect Add-ins
must be added manually from User Account where Inform IT Scheduler Service
(AfwScheduler.exe) runs to load the add-ins into Excel and complete its first
time settings and close. This is required for Scheduled Excel reports functionality.
– For the steps on Adding the DataDirect Add-ins manually; Refer Section 9 -
Historical Process Data Collection, refer the topic Installing Add-ins in
Microsoft Excel in System 800xA Information Management Configuration
(3BUF001092*), or Section 2 - General Information for DataDirect, refer the
topic Manually adding the DataDirect Add-in from System 800xA Information
Management Data Access and Reports (3BUF001094*).
– For any other users, the Add-ins must be added for the specific user who will
be using the functionality as mentioned above.
2PAA111693-611 A 85
15.2 ActiveX Security Settings
15.2 ActiveX Security Settings

If the default security ActiveX settings are not changed, a prompt appears asking whether
or not to allow access of blocked controls every time an attempt is made to use a tool
that includes an ActiveX control. This affects the Desktop tools and the Profile client
applications.
To allow the controls to load without intervention, perform the following steps:
1. Start Internet Explorer.
2. Select: Tools > Internet Options.
3. Click the Advanced tab.
4. In the Security section, enable the following check boxes:
• Allow active content from CDs to run on My Computer.
• Allow active content to run in files on My Computer.
15.3 Creating a History Database Instance

Use the DB Instance wizard to create a History database instance. This will determine
the Oracle tablespace and disk space requirements and where History related files will
be stored. If installing Information Management software for an end user, the History
database requirements may not be known at this time. In this case, the wizard default
values can be used to create a default instance sized to fit most History applications. If
it is determined later that the default instance is not large enough, the end user can
remove this instance and create a new one.
Disable the dynamic Ip address network adapter or network adapter configured with
DHCP configuration on IM Server node before starting the IM update and also during
oracle database instance creation.
Enable the same after oracle database instance creation completion only if required.
To create the default database instance:
1. Start the History Database Maintenance wizard by selecting:
ABB Start Menu > ABB System 800xA > Information Mgmt > History > IM Oracle
Instance Wizard
2. Click Next in the Welcome dialog box.
2PAA111693-611 A 86
3. Select the I will enter the information manually and save it to a new
configuration file option and click Next in the Configure File Options dialog box.
Perform only the following procedures applicable to the needs of the installed 800xA
System.
4. Message Logs.
a. Determine if message logs will be used, select the appropriate option, and click
Next.
b. Enter the required OPC and DCS message log information (Figure 15.2).
Figure 15.2: Message Logs Information
2PAA111693-611 A 87
5. Numeric Logs.
a. Determine if numeric logs will be used, select the appropriate option, and click
Next.
b. Enter the required numeric log information (Figure 15.3). Click + or - (not shown
in Figure 15.3) to add or remove a group of logs.
Figure 15.3: Numeric Logs Information
2PAA111693-611 A 88
6. Profile Logs.
a. Determine if profile logs will be used, select the appropriate option, and click
Next.
b. Enter the required profile log information (Figure 15.4). Click + or - (not shown
in Figure 15.4) to add or remove a group of logs.
Figure 15.4: Profile Logs Information
c. Determine if profile PDL logs will be used, select the appropriate option, and
click Next.
2PAA111693-611 A 89
d. Enter the required profile PDL log information (Figure 15.5).
Figure 15.5: Profile PDL Logs Information
2PAA111693-611 A 90
7. Batch Management PDL Logs.

a. Determine if a Batch Management PDL logs will be used, select the appropriate
option, and click Next.
b. Enter the required Batch Management PDL log information (Figure 15.6).
Figure 15.6: Batch Management PDL Log Information
2PAA111693-611 A 91
8. Unarchived Reports.
a. Determine if reports will be stored online (unarchived reports), select the
appropriate option, and click Next.
b. Enter the number of reports to be stored online.
9. Specify the disk drives that will contain the Oracle system files, history data files,
and history indexes, and click Next.
10. Click Advanced to access the advanced version of this dialog box (Figure 15.7)
that allows the disk drive, initial memory size, and maximum memory size of each
type of file to be specified.
11. Specify the amount of flat file space to allocate and on which disk drives it should
be allocated (Figure 15.8) and click Next. Be sure to allocate enough memory space
so that the Flat File Space Left To Reserve number is equal to zero.
12. Click Next when notified that the Oracle Instance Wizard has all the information it
needs to configure the history Oracle instance.
13. Click OK when notified that the Oracle instance has been successfully created.
14. Click Next in the Configuring Oracle window.
15. Determine if the accounts of Oracle system users are allowed to use the default
passwords or they all should use the same new password and click Next.
16. If all the accounts are to use the same new password, enter and then re-enter the
new password.
2PAA111693-611 A 92
17. Click Finish when notified that the Oracle configuration process is complete.
Figure 15.7: Advanced Database File Locations Information
Figure 15.8: Flat File Space Allocation Information
To secure the Information Management database, ensure to set the oracle instance
users password once the database is created. Refer to System 800xA Information
Management Configuration (3BUF001092*) for more details to set the oracle instance
users password.
2PAA111693-611 A 93
15.4 Starting Process Administration Supervision (PAS)
15.4 Starting Process Administration Supervision (PAS)

PAS manages all Information Management services. PAS must be started after the
software has been installed. When PAS is started for the first time the communication
settings must be initialized. This is required for History Services to run. These settings
only need to be initialized at this time. They do not need to be configured to their final
values.
When the History Service is started under PAS, the following History setup occurs:
• The Service Group/Service Provider structure for the Information Management node
will be created in the Service Structure.
• The OPC Alarm Server for History will be added in the Alarm and Event Service
Group under the Alarm and Event Services category for this node in the Service
Structure.
• The Information Management History, Information Management Archive, and
Information Management Importer links will be added to the Basic History Service
Group for this node in the Service Structure.
To start PAS and initialize the communication settings, from the configuration assistant,
select Enable PAS, then click Run Selected Configuration Tool. This starts the
Communication Settings dialog box shown in Figure 15.9.
These settings can be configured to their final values at this time if the required information
is available, or they can be initialized now, and configured later. This topic describes
how to initialize the settings. For further guidelines on configuring the settings, refer to
Appendix A - Extending OMF Domain to TCP/IP in System 800xA Information
Management Configuration (3BUF001092*).
2PAA111693-611 A 94
15.5 Configuring the DBA (ADO) Data Provider for Oracle Data
Figure 15.9: Communication Settings Dialog Box
1. To initialize the current settings, click OK in the Communication Settings dialog

box.
2. A prompt appears asking whether or not to restart the computer. A restart is not
required at this time. A restart is only required when the OMF Memory or TCP/IP
enabled setting is changed. After responding to the Restart Inquiry prompt, the
processes will automatically be restarted by PAS and the Communication Settings
dialog box will close.
15.5 Configuring the DBA (ADO) Data Provider for Oracle

Data
The Information Management installation provides two default ADO data providers.
The second ADO data provider supports the PDL browser for Batch Management, and
Oracle data access via DataDirect, Display Services, and Desktop Trends.
The first data provider is configured to support data access for the demonstration displays
provided with Display Services. Refer to Appendix A - A Demonstration of Display
Services in System 800xA Information Management Configuration for Display Services
(3BUF001093*) for more information. This data provider does not require any further
configuration.
2PAA111693-611 A 95
The second ADO data provider supports the PDL browser for Batch Management, and
Oracle data access via DataDirect, Display Services, and Desktop Trends.
This data provider requires some configuration to make it operational at the site.
Specifically, a local Net service name must be configured and an ODBC data source
must be created for the Oracle database. The StartUpMode of the ADO data provider
must then be changed. Follow these basic steps and refer to the referenced pages for
details:
• Creating an ODBC Data Source for the Oracle Database.
• Editing the ADO Data Provider Configuration.
15.5.1 Creating an ODBC Data Source for the Oracle Database

IM software uses the x86 version of the oracle ODBC driver.
On the Start screen type Set up ODBC. Figure 15.10 displays both the 32- and 64-bit
tools. Select the 32-bit tool to add the ODBC driver.
Figure 15.10: Start Screen Search
2PAA111693-611 A 96
The following are the Oracle ODBC drives available for the different Oracle installation
types:
• Oracle in OraDb19c_ADVAC: Present in all Oracle Client installations. This version
is always an x86 version of the ODBC driver.
• Oracle in OraDb19C_ADVA: Present in all Oracle Server installations. On the
Workstation Operating System (x64) or the Server Operating System, the x86 Data
Sources utility must be used to configure ODBC.
• Oracle in OraDb19C_ADVA64: Present only in x64 versions of Windows with
Information Management Server installed. The driver is not used in the product,
because all the clients are x86 based. The x86 versions of Microsoft Office and
Crystal Reports must be used with 800xA. The x64 versions are not supported.
On Information Management Servers, the Configuration Assistant starts the correct

Data Source utility to configure ODBC.
This procedure explains how to install and configure an Oracle ODBC driver for the
Information Management Oracle database.
1. From the configuration assistant, select Create ODBC Data Source for the Oracle
Database, then click Run Selected Configuration Tool. This displays the ODBC
Data Source Administrator dialog box shown in Figure 15.11.
2. Select the System DSN tab.
Figure 15.11: ODBC Data Source Administrator Dialog Box
2PAA111693-611 A 97
3. Click Add to display the Create New Data Source dialog box shown in Figure
15.12.
Figure 15.12: Create New Data Source Dialog Box
4. Select Oracle in OraDb19c_ADVA and click Finish. This starts the Oracle ODBC
Driver Configuration dialog box (Figure 15.13).
2PAA111693-611 A 98
5. Perform the following step for Domain or Workgroup setup:

• For Workgroup Setup: Enter Data Source Name as localhost and select
TNS Service Name as localhost from the drop-down list, as shown in Figure
15.13.
Figure 15.13: Oracle ODBC Driver Configuration Dialog Box
• For Domain Setup: Enter Data Source Name as localhost and select TNS
Service Name as localhost.domainname from the drop-down list.
For long running queries or slow oracle server response "Enable Query Timeout"
should be unchecked. There is an impact on performance due to this change ,since
there is no time out some wrong query request may run forever.
6. Click OK when finished to return to the System DSN tab on the ODBC Data Source
Administrator dialog box. The new driver will be added to the System Data Source
list.
7. Click OK to exit the ODBC Data Source Administrator dialog box.
2PAA111693-611 A 99
15.5.2 Editing the ADO Data Provider Configuration

This procedure describes how to change the StartupMode for the ADO data provider
from MANUAL to AUTOMATIC. To edit the ADO data provider:
1. From the configuration assistant, select Configure ADO Data Provider, then click
Run Selected Configuration Tool. This displays the ABB Data Service
Supervision dialog box.
2. Click the plus (+) symbol next to Supervision to expand the navigation tree and
show the available data providers.
3. Select the ADO data provider as shown in Figure 15.14.
Figure 15.14: Selecting the Existing ADO Data Provider
The data provider must be stopped to configure its attributes. This is the default
state. If the data provider is started, click Stop to stop the data provider.
4. Click the plus (+) symbol next to the ADO data provider to show the data provider
attributes.
5. Select the StartupMode for this data provider.
2PAA111693-611 A 100
15.6 Defining the Users
6. Set the Argument Value field to AUTOMATIC, as shown in Figure 15.15.
Figure 15.15: Changing StartupMode to Automatic
7. Click Save to save the changes.

8. To start the ADO data provider, select it and click Start.
9. Click Close to exit the dialog box.
The ADO-DEMO data provider supports demonstration displays. This data provider
may be stopped, and its StartupMode may be changed to MANUAL, if the
demonstration displays are not being used.
15.6 Defining the Users

Click Run Selected Configuration Tool, and two dialog boxes appear. Use Windows
Explorer to locate the default users profiles folder (UserExamples) and the folder to
define the users (Data). The CreatePassword dialog box is used to encrypt the password
for new users. Perform the procedure in the section Managing Users for Display
Services from System 800xA Information Management Configuration (3BUF001092*).
15.6.1 Configuring the Default ACC Users

After starting the ACC Setup tool, use one of the defined Display Service user/password
combinations for ACC Setup (Figure 15.16).
2PAA111693-611 A 101
15.7 Information Management Profiles Client Post Installation
Figure 15.16: ACC Setup Tool
15.7 Information Management Profiles Client Post

Installation
The Profiles Client application runs independent of the Information Management System
Services or 800xA System software. To access the Information Management Server, all
Profiles Client nodes can be in the same domain as the Information Management Server
and then no post installation changes are required. To access the Information
Management Server from a node outside the domain/workgroup, it is necessary to create
the 800xA Service User account on the Profile Client. The 800xA Service User account
name can be found on the domain controller. Verify that the name is the same case and
the passwords are identical.
2PAA111693-611 A 102
15.8 Adding the DataDirect Add-Ins in Office
15.8 Adding the DataDirect Add-Ins in Office

For the steps on Adding the DataDirect Add-ins manually; Refer Section 9 - Historical
Process Data Collection, refer the topic Installing Add-ins in Microsoft Excel in
System 800xA Information Management Configuration (3BUF001092*), or Section 2 -
General Information for DataDirect, refer the topic Manually adding the DataDirect
Add-in from System 800xA Information Management Data Access and Reports
(3BUF001094*).
15.9 Adding the Inform IT Bulk Import Add-in in Office

For detailed steps on adding the Inform IT Bulk Import add-in see the topic Installing
Add-ins in Microsoft Excel in System 800xA Information Management Configuration
(3BUF001092*). If familiar with the procedure details, the file is located in
%HS_HOME%\bin\Inform IT Bulk Import.xlam
2PAA111693-611 A 103
2PAA111693-611 A 104
16 800xA History
16.1 800xA History Event Collection Procedure
16 800xA History
This topic provides post installation procedures for the 800xA History components.

800xA History Event Collection procedure is performed based on the following:
• Event Collection based on Vendor Attributes
• Event Collection based on Event Categories
2PAA111693-611 A 105
16 800xA History
16.1.1 Event Collection based on Vendor Attributes

Perform the following to include the vendor specific attribute information as part of the
event collection:
1. Go to Service Structure > Services > 800xA History Event Collector, Service
> Service Group.
2. In Aspect List, select Service Group Definition as shown in Figure 16.1.
Figure 16.1: Aspect List with Specific Attribute
3. In Special Configuration tab, go to Attribute tab > Attributes & Expressions

section and select all or required attributes.
4. Click Add to include them in Attributes - Forwarded to 800xA History pane.
5. Click Apply.
2PAA111693-611 A 106
16 800xA History
16.1.2 Event Collection based on Event Categories

Perform the following to include the event categories as part of the event collection:
1. Go to Service Structure > Services > 800xA History Event Collector, Service
> Service Group.
2. In Aspect List, select Service Group Definition as shown in Figure 16.2.
Figure 16.2: Aspect List with Event Categories
3. In Special Configuration tab, under Event Categories section. All the event
categories check boxes are cleared by default for event collection.
4. Select the event categories check box to exclude the event categories for event
collection.
5. Click Apply.
2PAA111693-611 A 107
2PAA111693-611 A 108
17 Batch Management
17.1 Batch Redundancy Configuration
17 Batch Management
This section provides post installation procedures for Batch Management.

The batch redundancy can be activated using ABB Batch Mirroring Utility.
This utility can be launched only from Primary batch server by navigating to ABB Start
Menu > ABB System 800xA > Production Management > ABB Batch Mirroring
Utility. Perform the following procedure to activate the mirroring:
1. Provide the Mirror Node Name (Secondary Server) and Witness Node Name (Node
configured as witness during Installation) and then click Activate as shown in Figure
17.1.
Figure 17.1: Batch Redundancy Configuration
2PAA111693-611 A 109
17 Batch Management
2. Click Yes to continue as shown in Figure 17.2.
Figure 17.2: Confirm Activation Window
2PAA111693-611 A 110
17 Batch Management
3. Figure 17.3 shows the Batch Redundancy Activation in progress.
Figure 17.3: Batch Redundancy Activation In-progress Window
2PAA111693-611 A 111
17 Batch Management
4. Figure 17.4 shows that redundancy is activated and displayed.
Figure 17.4: Batch Redundancy Activation Completion Status Window
5. Activate mirroring on Batch Primary Server and wait untill Batch icon status shows
Green on all the nodes.
Deactivate and Activate mirroring on Batch Primary Server only after Offline or
Online update and wait untill Batch icon status shows Green on all the nodes. The
user can retry the operation more than once on a need basis.
The Upgrade button will remain enabled at all times. The user needs to click on the
Upgrade button only after Offline or Online update to upgrade the SQL Server to
the higher version. The user can retry the operation more than once on a need
basis.
17.1.1 Batch Redundancy in Workgroup Environment

Perform the following steps after mirroring is activated in the workgroup environment:
1. Login with a user account having administrative privilege on the batch primary server.
2. Launch Microsoft SQL Server Management Studio and Connect to
BATCH_INSTANCE.
2PAA111693-611 A 112
17 Batch Management
17.2 Registry Setting changes (Batch Harmony Connect Users Only)
3. Navigate to the Users folder under SymFlexDB. The users will be able to view only
Batchprimary Nodename\IndustrialITAdmin and Batchprimary
Nodename\IndustrialITUser groups.
4. Add a New Users with BatchSecondary Nodename\IndustrialITAdmin and
BatchSecondary Nodename \IndustrialITUser groups under the Users folder as
follows:
a. Right Click on the Users and select New User… from the context menu.
b. Select Windows user under User type and enter Batch Secondary
Nodename\IndustrialITAdmin under Username.
c. Navigate to Membership and enable db_owner check box.
d. Click Ok.
e. Repeat step 1 to step 4 to add BatchSecondary Nodename\IndustrialITUser
group.
The Batch Redundancy Status is described in the System 800xA Batch Management
Operation (3BUA000145*).
17.2 Registry Setting changes (Batch Harmony Connect

Users Only)
Perform the following steps to change the registry settings in Batch Servers:
1. Browse to the installation folder and then extract the Harmony registry settings.zip
to a folder.
2. Click Harmony Registry settings.reg to run the file.
17.3 Shutdown Script

The batch_shutdown.bat script shuts down the Batch application properly and must be
installed on all Batch Servers. To install this script:
1. Click Start and type gpedit.msc in the text box and then click OK.
2. Select Computer Configuration > Windows Settings > Scripts
(Startup/Shutdown).
3. Double-click Shutdown.
4. Click Add and then Browse.
2PAA111693-611 A 113
17 Batch Management
17.4 Print BMA Report Configuration
5. Select: <DRIVE>:\Program Files(x86)\ABB Industrial IT\Produce

IT\Batch\bin\batch_shutdown.bat
in the Script Name field and click Open.

6. Click OK twice to complete the installation and close the Group Policy dialog box.
17.4 Print BMA Report Configuration

The Batch Print BMA Report tool is installed in all nodes in the system. This tool should
be run in any one node in the system.
A Default physical Printer should be configured in that node.
17.5 Batch Management Toolbar

Batch Management provides a Toolbar that contains buttons for the Batch Overview,
Batch History Overview, and Equipment Overview dialog boxes. If desired, refer to
System 800xA Batch Management Configuration (3BUA000146*) for information about
enabling this Toolbar.
17.6 Set Date and Time for Batch Servers

Batch Primary and Redundant servers require a specific time format for the service
account. All other users on the batch server and other nodes can keep the US - English
defaults.
Perform the following to verify/modify the formats for the <800xA Service Account> on
the batch servers:
1. Login to the <800xA Service Account> on the Primary/Secondary Batch server.
2. Open Windows Control Panel.
3. Double-click Region, Region dialog appears. Perform the following to set the formats
for Date and Time:
a. Click the Format tab.
b. The default value for the Short Date format is M/d/yyyy. Change the Short Date
format to MM/dd/yyyy and click Apply.
c. The default Short time format is hh:mm tt. Change the value to HH:mm and
click Apply.
4. Click Apply.
2PAA111693-611 A 114
18 PR Batch History
18.1 Batch View Client
18 PR Batch History
This section provides the post installation and post configuration of PR Batch History.

This will describe on how to install and configure the Batch View client using ABB AbilityTM
MOM Services. A small part of MOM Server element will be installed on the control
system to support PR Batch History for data collection and Batch View access tool.
ABB Ability™ MOM Configurator is not a replacement of the entire ABB Ability™
MOM Services Server. This supplies a support for 800xA PR Batch History data
collection and visualization only.
2PAA111693-611 A 115
18 PR Batch History
18.1.1 Batch View Installation

Follow the below procedure to install ABB AbilityTM MOM Services:
1. Launch Internet Explorer.
2. Provide http://localhost/sds/ in the internet explorer address bar. ABB AbilityTM
MOM Services window will startup.
Replace localhost with the IP address of the machine where PR Batch History is
installed.
Figure 18.1: ABB AbilityTM MOM Services – Startup Window
3. Click on Microsoft Surface 2.0 Runtime.

4. Select the checkbox “I accept the terms in the License Agreement”.
5. Click Next.
6. Click on Install.
7. Click on Finish.
8. Click on ABB AbilityTM MOM Services.
2PAA111693-611 A 116
18 PR Batch History
9. Click on Install.
10. Finally, ABB AbilityTM MOM Services – Launchpad window will appear.
Figure 18.2: ABB AbilityTM MOM Services – Authentication
18.1.2 Batch View Configuration

Follow the below procedure to configure ABB AbilityTM MOM Services:
1. Provide the Login and Password in the respective fields.
2. Provide the Server address as wss://localhost:10940/sds
Replace localhost with the IP address of the machine where PR Batch History is
installed.
Figure 18.3: ABB AbilityTM MOM Services – Login
2PAA111693-611 A 117
18 PR Batch History
18.2 Batch Analysis Application
3. Click on Login.
4. Now, the user should be able to login to ABB AbilityTM MOM Services - Launchpad.
Figure 18.4: ABB AbilityTM MOM Services – Add Group
The user must login to ABB Ability™ MOM Services- Configurator atleast once,
before login to ABB AbilityTM MOM Services - Launchpad

This will describe on how to configure an item in the Batch Analysis Application.
1. Open the ABB MOM Service application. MOM Services - Launchpad appears.
2. Click on Add Group to create a new group.
2PAA111693-611 A 118
18 PR Batch History
3. Click Add Item (see Figure 23) in the new group to create the BatchAnalysis
application within MOM Service.
Figure 18.5: BatchAnalysis - Add Item
4. Select BatchAnalysis from the Startup drop-down list.
Figure 18.6: BatchAnalysis - Configuration
2PAA111693-611 A 119
18 PR Batch History
5. Select an icon to represent BatchAnalysis and a preferred background color to

indicate on the dashboard.
Figure 18.7: BatchAnalysis - Startup
6. Click Save to view the BatchAnalysis item on the dashboard.
Figure 18.8: BatchAnalysis - Icon and Background Color
2PAA111693-611 A 120
18 PR Batch History
18.3 SQL Server Memory Limit
7. Now, the MOM Services - Launchpad is created with a BatchAnalysis item.
Figure 18.9: BatchAnalysis Configured
18.3 SQL Server Memory Limit

Perform the following procedure across all the SQL Server database on all the storage
nodes:
1. Launch the SQL Server Management Studio to connect to the Instance.
2. Right-click on the Instance and select Properties from the context menu.
3. Select the Memory Settings in the Server Properties dialog.
4. Change the Maximum Server Memory (in MB) field to be equal to 50 percent of
the physical RAM of the PR Batch History.
5. Restart SQL Services.
6. The above steps must be performed on all the storage nodes where SQL Server is
installed.
2PAA111693-611 A 121
2PAA111693-611 A 122
19.1 IPsec Configuration Tool
The Internet Protocol Security (IPsec) is a protocol suite for securing Internet Protocol
(IP) communications by authenticating and encrypting each IP packet of a communication
session. The purpose of IPsec Configuration Tool is not primarily to encrypt the
communication, but to ensure through strong authentication, that only legitimate nodes
connect to the 800xA System.
The IPsec Configuration Tool, allowing secure communication, can also exempt the
nodes which are outside the 800xA System or the nodes that are not the Domain
members.

The System 800xA IPsec Configuration Tool is used to configure the Connection security
rules in Windows Firewall with the Advanced Security console through a Group Policy
on the Active Directory.
The tool can be used only in a Domain Environment to protect the internal communication
between the client and the server on the network.
The tool doesn't support a system that is using a combined Domain Controller and
Aspect Server.
Windows Firewall must be turned ON when appliying changes to the nodes.
19.1.1 Configuring IPsec for System 800xA

The System 800xA IPsec Configuration Tool (Figure 19.1) folder located on System
800xA Media must be executed on the Domain Controller node.
2PAA111693-611 A 123
To configure the IPsec on System 800xA perform the following:

1. Navigate to the below path in the 800xA media
Tools\ABB 800xA IPsec Configuration Tool\
2. Run the ABB 800xA IPsec Tool.exe to launch the System 800xA IPsec
Configuration Tool.
Figure 19.1: IPsec Configuration Tool
Create IPsec rules.

The New Configuration page will allow the user to protect the secure communication on
the client server network by creating connection security rules in the Active Directory
Group Policy. Refer to New Configuration for more information.
Edit IPsec rules.
The Edit Configuration page will allow the user to view and edit the existing connection
security rules in Active Directory Group Policy. Refer to Edit Configuration for more
information.
19.1.2 New Configuration

To configure the communications that cannot be protected, add the exemptions for the
relevant communications in the specific 800xA System as follows:
1. From the Rule Type sections select the applicable connection security rule:
2. Domain Controller and provide the IP address of the Domain Controllers present
in this network to exempt from a secure communication and click Add.
2PAA111693-611 A 124
3. NTP Time Synchronization Protocol and provide the IP address or Subnet and
click Add.
4. AC 800M Controllers and provide the subnet address of the AC 800M Control
Network or the IP addresses of all the individual AC 800M Controllers.
If the individual addresses are provided, ensure that the IP addresses of the backup
CPUs are also provided.
Select Use Webserver for PROFIBUS/PROFINET to allow usage of the Web Server
for PROFIBUS/PROFINET.
For collapse networks where control network and plant network are combined
controller IPs should be provided. Do not provide subnet.
5. AC 800M Soft Controllers and privide the IP adressess if all the individual AC
800M Soft Controllers and click Add.
6. Advant Master with PU410 or MOD 300 with PU410 or PU412 and provide the
IP address of the PU410 RTA Unit and click Add.
7. Multisystem Integration and provide the Subnet address and click Add.
8. Foundation Fieldbus HSE Device and provide the Subnet address and click Add.
9. IEC61850 IED and provide the IP address or Subnet and click Add.
10. PLC Connect with Modbus TCP Slaves and provide the Subnet or IP addresses
for Modbus TCP slaves and click Add.
11. PLC Connect with SattBus on TCP and provide the Subnet or IP addresses for
SattBus and click Add.
12. DCI HDCU Controller and provide the IP address or Subnet and click Add.
13. Harmony IET800 Modules and provide the IP address or Subnet and click Add.
14. Harmony Time Synchronization Module and provide the IP address or Subnet
and click Add.
15. Batch Management and select To All Addresses option and click Add.
16. Desktop Tools Client Node outside 800xA System and provide the IP address
or Subnet and click Add.
17. IM Consolidation and provide the IP address or Subnet and click Add.
18. 800xA History Server and provide the IP address or Subnet and click Add.
Use user defined protocol option and provide the IP address of the 800xA History
Server. In “Port on node in 800xA Domain” field provide “Any” and in “Port on node
outside 800xA Domain” field provide “443”. The TCP protocol should be used.
2PAA111693-611 A 125
19. AC 900F Controller and provide the IP address or Subnet and click Add.
22. Network Switch and provide the IP address or Subnet and click Add.
23. User Defined Protocol and provide the Subnet or IP address, Protocol (UDP or
TCP), Port on node in the 800xA domain, Port on node outside 800xA domain and
click Add.
24. ICMP Ping and select To All Addresses option and click Add.
25. SAP Server and provide the IP address and click Add.
26. Maximo Server and provide the IP address and click Add.
27. Remote Desktop Protocol and provide the IP address or Subnet and click Add.
28. Networks and provide the Subnet or IP addresses and click Add.
29. Mail Server and provide the IP address or Subnet and click Add.
PC, Network and Software Monitoring is used for monitoring virtual environment. It
is required to define the exemptions for ESXi servers as described in the Step 28..
For Melody controllers, the IP address of the Melody controllers should be exempted
completely.
While the individual exemptions are added by clicking the Add button, the exemption
is added to the Connection Security Rules table.
To delete a rule in the Connection Security Rules table, select the specific rule and
click Remove.
30. Click the Configure button to create an Active Directory Group Policy and add
all the relevant connection security rules as defined in Step 1..
Verify all the security connections before creating the Active Directory Group Policy.
31. Open the command prompt window on all the domain members and run the
gpupdate/force command to update the group policy settings on the individual
nodes.
2PAA111693-611 A 126
19.1.3 Edit Configuration

To edit an existing Active Directory Group Policy, launch ABB 800xA IPsec Configuration
Tool. The tool displays existing connection security rules configured in the Active
Directory Group Policy:
1. The existing connection security rules appears in the Connection Security Rules
table.
2. Select an existing connection security rule and click Remove to delete the rule from
the policy.
3. Select the Applicable connection security rule in order to add a new connection
security rule and to exempt a communication from the security policy. Provide the
required inputs and click Add to add the exemption to the Summary table.
4. Click Configure to update the group policy with the changes made.
5. Open the command prompt window on all the domain members and run the
gpupdate/force command to update the group policy settings on the individual
nodes.
2PAA111693-611 A 127
2PAA111693-611 A 128
Many functions in System 800xA require the local clocks in the different system nodes
to be synchronized including Domain Controllers. How the Clock Synchronization is best
done differs between systems.
Refer to System 800xA Network Configuration (3BSE034463*) manual for description
on different recommended Clock Synchronization schemes for the most common
configurations, different configuration parameters in controllers, different protocols, and
Clock Synchronization components. Use the required Clock Synchronization scheme
based on the system configuration.
Make sure that the time on all the 800xA nodes including domain controllers are
synchronized after the selected Clock Synchronization scheme is implemented.
If virtualization is used, make sure that any Clock Synchronization used between
the VMware host and the VMware does not conflict with the System 800xA selected
time scheme.
This section describes the steps needed to setup the Clock Synchronization in Local
Time Source scheme (refer to System 800xA Network Configuration (3BSE034463*)
for more information).
The following procedures must be performed to configure the Time Services:
• Configuring Windows Time Service.
• Configuring the 800xA Time Service.
• Configuring the System Time Server.
• Configuring the Time Client.
2PAA111693-611 A 129
20.1 Configuring Windows Time Service
20.1 Configuring Windows Time Service

Windows Time Service is disable on all nodes during node preparation.
Note that specific system / node functions in combination with selected Clock
Synchronization scheme would need Windows Time Service to be enabled. Enable
Windows Time Service on specific nodes only when recommended in the specific
Clock Synchronization scheme selected.
20.2 Configuring the 800xA Time Service

To configure the 800xA Time Service:
3. Use the Object Browser to navigate to and select:
Services > Time, Service
4. Select Service Definition in the Aspect List Area.

6. Verify that the Server Running check box is selected. If it is not, select it.
7. Verify that the Clients allowed to set time check box is cleared. If it is not, clear it.
8. Verify that the Enable external clock master function check box is cleared. If it
is not, clear it.
9. Click Apply.
20.3 Configuring the System Time Server

To configure the System Time Server:
3. Use the Object Browser to navigate to and expand:
Services > Time, Service > Time, Service Group
4. Select the Connectivity Server designated to act as the Time Server.

5. Select Service Provider Definition in the Aspect List Area.
2PAA111693-611 A 130
20.4 Configuring the Time Client

7. For all nodes acting as a Time Server (primary or redundant):
a. Verify that the Enabled check box is selected. If it is not, select it.
b. Click Apply.
8. For all other nodes not acting as a Time Server:
a. Disable the Service Provider by clearing the Enabled check box.
b. Click Apply.
-or-
Delete the Service Provider.
9. Configure a method for the time servers to receive time from some external source.
When using an AC 800M control network as time source the AC 800M Time Adaptor
needs to be installed.
20.4 Configuring the Time Client

To configure the Time Client:
2. Use the Structure Selector to open the Node Administration Structure.
3. Use the Object Browser to navigate to and select a node in the list under:
Node Administration > All Nodes, Node Group
4. Select Time Server Client Configuration in the Aspect List Area.

5. Select the Allowed to set time check box, only if desired.
6. Select the Time Sync Running check box for all nodes.
7. Set the Deviation Limit to 1000 msec.
8. Click Apply.
9. Repeat Step 3. through Step 8. for every node in the system.
20.5 800xA for AC 800M

Refer to the System 800xA Network Configuration (3BSE034463*) manual for description
on Clock Synchronization schemes and procedures related to AC 800M controllers and
connectivity servers.
2PAA111693-611 A 131
20.6 800xA for AC 100
20.6 800xA for AC 100

20.6.1 Clock Synchronization and Daylight Saving Time
There are a number of ways to configure the clock synchronization for an Advant Fieldbus
100 network along with a network of System 800xA products. The Advant Fieldbus 100
network has its own clock synchronization. Refer to Advant Fieldbus User Manual
(3BSE000506*) for functionality and configuration details, and in the corresponding
reference manual for the data base elements of each controller (Data Base Elements
Advant Controller 70 Reference Manual (3BSE009456*), Data Base Elements Advant
Controller 110 Reference Manual (3BDS100594*), Data Base Elements Advant Controller
160 Reference Manual (3BDS005556*), and Data Base Elements Advant Controller 400
Series Reference Manual (3BSE014819*)).
A System 800xA network consists of one or several servers and a number of clients
connected via TCP/IP. Synchronization of that network of servers and clients in itself is
supported by the 800xA System. This is described in System 800xA Network Configuration
(3BSE034463*). One clock server synchronizes the other servers and clients in the
network.
The AC 100 OPC Server can function as the time master or as a slave versus the Advant
Fieldbus 100 network.
The information in the remainder of this topic represents the recommended Configuration.
All servers and clients in an Advant Fieldbus 100 network must be configured to the
same time zone and must be time synchronized.
It is recommended that you set-up an 800xA Connectivity Server, that hosts the AC 100
OPC Server, as time master. It will be time master both for the System 800xA network
as well as for the Advant Fieldbus 100 network.
Any adjustment of the network time is done (from the time server) using the Windows
Date and Time dialog box in the Windows Control Panel.
To set up the 800xA System for such a configuration:
1. Set up the selected server node as the time server. If there are several server nodes,
set up the others to request the correct time from the time server.
2. Set up all the workstation nodes to accept the clock synchronization.
3. Make sure that the Automatically adjust clock for Daylight Saving Time setting
is selected is set on all server and workstation nodes.
4. Set the Clock Synchronization of the AC 100 OPC Server to Master according to
the instructions in AC 100 OPC Server Configuration and Operation (3BDS013988*).
2PAA111693-611 A 132
20.7 800xA for MOD 300
5. Set the Clock Synchronization of other Advant OPC Servers for Advant Fieldbus 100
to None according to the instructions in AC 100 OPC Server Configuration and
Operation (3BDS013988*).
6. Those nodes will collect their time from the time server.
The result of this solution is as follows for time tagged data:
• Alarm data and Historical data are stored according to UTC time. The local time
does not matter.
• Alarm and History data presentation manages the presentation of data with the local
time.
20.7 800xA for MOD 300

20.7.1 Setting Up Clock Synchronization
Perform the following to set up Clock Synchronization:
• 800xA System as the Master Timekeeper.
• MOD 300 System as the Master Timekeeper.
800xA System as the Master Timekeeper

When the 800xA System is the master timekeeper, follow the instructions for setting up
time on the 800xA System and then set the 800xA for MOD 300 Connectivity Server so
reverse Clock Synchronization is enabled. This will allow Windows clock to set the
Real-Time Accelerator (RTA) clock and give the RTA the ability to update the MOD 300
system if it is made the master timekeeper (refer to the AdvaBuild Administrator User
Guide 3BUR001977* for additional information).
1. Select:
ABB Start Menu > ABB System 800xA > PAS Management > PAS Control
(2PAA101888*).
2. Click Advanced, advanced options dialog appears.

3. Select Comm Settings to open a new window.
4. Select Enabled from the drop-down menu for Reverse Time Sync.
2PAA111693-611 A 133
20.7 800xA for MOD 300
5. Click OK.
6. Reboot the node.
MOD 300 System as the Master Timekeeper

Clock Synchronization on the Windows side of a Connectivity Server node can be set
so Reverse Clock Synchronization (RTS) is disabled. This allows the host Connectivity
Server to constantly be updated by the RTA clock that gets its time from the MOD 300
System Master Timekeeper over the Distributed Communications Network (DCN). The
host node then broadcasts this time to the other MOD 300 nodes on the 800xA System
as well as the Domain Controller.
MOD 300 Connectivity Servers, Clients, and the associated Domain Controller all need
to be set up to handle getting time from the MOD 300 system through the RTA on the
Connectivity Servers.
Clock Synchronization on the MOD 300 Connectivity Server. Reverse Clock

Synchronization is disabled on these nodes to allow the MOD 300 system to update the
RTA clock on the Connectivity Server. In addition, these servers act as a Simple Network
Time Protocol (SNTP) server for the Domain Controller.
1. Select:
ABB Start Menu > ABB System 800xA > PAS Management > PAS Control
2. Click Advanced, advanced options dialog appears.
3. Select Comm Settings to open a new window.
4. Select Disabled from the drop-down menu for Reverse Time Sync.
5. Click OK.
• Set the Windows Time (W32Time) in the Services window via:
Control Panel > Administrative Tools > Services
as follows:
– Startup Type is Automatic.
– Status is Started.
• Set the SNTP to fetch the time from itself. From the command prompt enter:
net time /setsntp:a.b.c.d
where a.b.c.d is the IP address of the Connectivity Server itself.
2PAA111693-611 A 134
20.7 800xA for MOD 300
Clock Synchronization on the Domain Controller. The Connectivity Servers act as a

SNTP server for the Domain Controller that then distributes time to all nodes in the
domain. This is handled with the default settings for W32Time.
Set the following:
• Set the Windows Time (W32Time) in the Services window as follows:
– Startup Type is Automatic.
– Status is Started.
• SNTP Registry parameter:
Be extremely careful when making changes in the registry. Do not make any changes
in the registry without first making a backup copy of the registry. Refer to the online
help for the registry editor on how to create a backup.
NtpServer = time.windows.com,0x1
Registry Location: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\
W32Time\Parameters
• SNTP Configuration, from the command prompt enter:
– If there is a single time server:
net time /setsntp:a1.b1.c1.d1 a2.b2.c2.d2
– If there are multiple time servers:

net time /setsntp:"a1.b1.c1.d1 a2.b2.c2.d2 "
where a1.b1.c1.d1 and a2.b2.c2.d2 are the IP addresses of the Connectivity

Servers.
Clock Synchronization on the MOD 300 Client. Client nodes get their time from the
Domain Controller and are set up as SNTP clients.
2PAA111693-611 A 135
20.8 Device Management FOUNDATION Fieldbus
Set the following:

• Set the Windows Time (W32Time) in the Services window as follows:
– Startup Type is Disabled.
– Status is Stopped.
• SNTP Registry parameter default:
Be extremely careful when making changes in the registry. Do not make any changes
in the registry without first making a backup copy of the registry. Refer to the online
help for the registry editor on how to create a backup.
NtpServer = time.windows.com,0x1
Registry Location: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\
W32Time\Parameters
20.8 Device Management FOUNDATION Fieldbus

Device Management FOUNDATION Fieldbus requires active Clock Synchronization on
HSE net for appropriate alarm time stamping. Windows Time Service (W32Time) must
be activated on each FOUNDATION Fieldbus Connectivity Server. Refer to the Clock
Synchronization topic in System 800xA Network Configuration (3BSE034463*).
2PAA111693-611 A 136
Recommendation is to utilise the system installer functionality to install the additional

products not part of the System 800xA media. Follow the instructions provided with the
additional products for installation and configuration.
2PAA111693-611 A 137
2PAA111693-611 A 138
22.1 Installation of Field Information Manager
This topic describes post installation procedures for xStream Commissioning, which is
installed as part of Ethernet I/O Field Kit. Field Information Manager (FIM) and ABB FIM
Bridge 800xA have to be installed, a License has to be loaded into FIM and the FIM
800xA Connectivity has to be configured, in order to start working with xStream
Commissioning.
22.1 Installation of Field Information Manager

ABB Field Information Manager (FIM) is a field device configuration tool based on
FDI-Technology. The supported version of Field Information Manager is to be installed.
Refer to Field Information Manager User Guide (2PAA117322*) or
https://new.abb.com/control-systems/fieldbus-solutions/fim/faq/installation to get
instructions and support to install Field Information Manager.
22.2 Installation and Configuration of ABB Field

Information Manager Bridge 800xA
Ensure that Field Information Manager 800xA Connect Service is running and
Certificates are installed on Ethernet IO Field Kit nodes.
ABB Field Information Manager Bridge 800xA is a communication bridge for connectivity
to ABB Ability™ System 800xA. The supported version of ABB Field Information Manager
Bridge 800xA software is to be installed and configured. Refer to User Guide Bridge
800xA (2PAA122884*) or get more information on
https://new.abb.com/control-systems/fieldbus-solutions/fim/connectivities/system800xa.
2PAA111693-611 A 139
2PAA111693-611 A 140
A Engineering Repository
A.1 Engineering Repository Web Service Configuration
Appendix A Engineering Repository
The Engineering Repository is a simple source control system for:

• Storing engineering solutions.
• Moving engineering solutions between Engineering and Production systems.
• Comparing engineering solutions.
The Engineering repository web services relies on unsecure communication, and
it's not recommended to use this functionality. For more details, see the System
800xA Aministration and Security (3BSE037410*)

The Web service can be installed stand-alone and is independent of 800xA Base
installation.
2PAA111693-611 A 141
A.1.1 Server Operating System

1. Install IIS.
a. Open the Server Manager (Computer > Manage).
b. Select the Manange item from the Dashboard and click on Add Roles and
Features.
c. Choose Installation Type - Role-based or feature-based installation and click
Next.
d. Choose Server Selection - Select a server from the server pool, click Next.
e. Choose Server roles.
f. Check Web Server (IIS).
g. If asked Add features required for Web Server (IIS)?, click Add Required
Features.
h. Click Next.
i. Select .NET Framework 3.5 Features and .NET Framework 4.6 Features. If
not already installed, check ASP.NET 4.6 and .NET Framework 4.6.
j. If asked Add role services and features required for ASP.NET?, click Add
Required Role Services.
k. Select IIS Management Console, IIS Management Scripts and Tools and
Management Service.
l. Click Confirm and Install (This may take some time).
2. WCF is installed as standard, HTTP activations aren’t by default. To activate these,
on your machine, open Control Panel / Programs and Features, Turn Windows
Features on or off / Install, Windows Communication Foundation HTTP Activation.
a. Open the Server Manager (Computer ->Manager).
b. Select the Manage item from the Dashboard and click on Add Roles and
Features.
c. Select .NET Framework 4.6 Features.
d. Select WCF Services (check all Services).
e. Ensure that .NET Framework 3.5 Features are selected.
f. Click Next.
g. Click Install. (This may take some time)
2PAA111693-611 A 142
3. Install the Engineering Repository Web service.

a. Copy the directory “ERService” that is located in “C:\Program Files (x86)\ABB
800xA\Base” on a computer where 800xA Base is installed, to
“C:\Inetpub\wwwroot\ERService” on the computer where the service shall run
(can be the same computer).
b. In the Internet Information Services (IIS) Manager, create a new Virtual
Application by right-clicking on the Default Web Site and select Add
Application
Follow any of the below procedures to start Internet Information Services (IIS)
Manager:
• To start IIS Manager from the Run dialog box, perform the following steps:
i. Open Run dailog by right-clicking on Windows icon and select Run.
ii. In the Open box, type inetmgr and then click OK.
• To start IIS Manager from the Administrative Services console, perform for the
following steps:
i. Open Control Panel (Classic View) > Administrative Tools > Internet
Information Services.
Figure A.1: Add Application
2PAA111693-611 A 143
c. In the Alias field enter “AfwDistEngWcfServices” and for the Physical path
browse to the ERService folder. Connect as Application User (pass-through
authentication).
Figure A.2: Add Application Window
d. Click OK.
e. Select AfwDistEngWcfServices in the connection pane and click on Edit
Permission in the Actions pane.
2PAA111693-611 A 144
f. In the ERService folder property dialog select the security tab. Click on Edit to
change permissions. For the user NETWORK SERVICE set Allow permissions
for Read & execute, List folder contents, Read and Write. If NETWORK
SERVICE does not exist in the Groups or user names windows it must be
added.
Figure A.3: ERService Permissions
2PAA111693-611 A 145
g. In the Internet Information Services (IIS) Manager, select

AfwDistEngWcfServices and open the Authentication feature. Enable Windows
Authentication and disable all others.
If the Windows Authentication isn't installed, follow these steps prior enabling
it:
i. On the taskbar, click Server Manager.
ii. In Server Manager, click the Manage menu, and then click Add Roles
and Features.
iii. In the Add Roles and Features wizard, click Next. Select the installation
type and click Next. Select the destination server and click Next.
iv. On the Server Roles page, expand Web Server (IIS), expand Web Server,
expand Security, and then select Windows Authentication. Click Next.
v. On the Select features page, click Next.
vi. On the Confirm installation selections page, click Install.
vii. On the Results page, click Close.
h. Create a new application pool by right-clicking on the Application Pool and
select Add Application Pool.
i. Enter a name (For example: DistributedEng). Click OK.
Figure A.4: Add Application Pool
2PAA111693-611 A 146
j. In the list of application pools, right-click on the newly created application pool.
Select Advanced Settings.
k. On the Advanced Settings window navigate to Process Model pane and General
Pane.
l. On the Application Pool General window set Enable 32-Bit Applications to
True.
m. On the Application Pool Identity window change the Built-in account: to
NetworkService. Click OK.
Figure A.5: Changing the Application Pool Identity
n. Click OK on the Advanced Settings window to save the changes.
2PAA111693-611 A 147
o. On the Default Web Site, select the new virtual application

AfwDistEngWcfServices created.
p. On the Action Pane, select Advanced Settings.

q. On the Advanced Settings, select application pool and change to the newly
created application DistributedEng. Click OK.
Figure A.6: Select Application Pool
2PAA111693-611 A 148
r. Click OK on the Advanced Settings window to save the changes.

s. Verify that the service is working by opening up Internet Explorer and navigate
to http://localhost/AfwDistEngWcfServices/DistEngService.svc. If the service is
working this page will be displayed.
Figure A.7: Service Display
2PAA111693-611 A 149
A.1.2 Workstation Operating System

1. Install IIS.
a. Open the Program and Features in the Control Panel.
b. Click on Turn Windows features on or off.
c. Select ASP.NET 3.5 and 4.X.
Figure A.8: Windows Features Dialog - Application Development Features
2PAA111693-611 A 150
d. Select Basic Authentication, Request Filtering and Windows Authentication.
Figure A.9: Windows Features Dialog - Security
2PAA111693-611 A 151
e. Select IIS Management Console, IIS Management Scripts and Tools and
IIS Management Service.
Figure A.10: Windows Features Dialog - Web Management Tools
2PAA111693-611 A 152
f. Select Windows Communication Foundation HTTP Activation and Windows

Communication Non-HTTP Activation.
Figure A.11: Windows Features Dialog - Windows Communication
g. Click OK (This may take some time).
2PAA111693-611 A 153
2. Install the Engineering Repository Web service.

a. Copy the directory “ERService” that is located in “C:\Program Files (x86)\ABB
800xA\Base” on a computer where 800xA Base is installed, to
“C:\Inetpub\wwwroot\ERService” on the computer where the service shall run
(can be the same computer).
b. In the Internet Information Services (IIS) Manager, create a new Virtual
Application by right-clicking on the Default Web Site and select Add
Application.
Follow any of the below procedures to start Internet Information Services (IIS)
Manager:
• To open IIS Manager from the Start menu, perform the following steps:
1. Click Start, and then click Control Panel.
2. Click System and Security, and then click Administrative Tools.
3. In the Administrative Tools window, double-click Internet Information Services
(IIS) Manager.
• To open IIS Manager from the Search box, perform for the following steps:
1. Click Start.
2.In the Start Search box, type inetmgr and press Enter.
Figure A.12: Add Application - Workstation Operating System
2PAA111693-611 A 154
c. In the Alias field enter “AfwDistEngWcfServices” and for the Physical path
browse to the ERService folder. Connect as Application User (pass-through
authentication).
Figure A.13: Add Application Window - Workstation Operating System
d. Click OK.
e. Select AfwDistEngWcfServices in the connection pane and click on Edit
Permission in the Actions pane.
2PAA111693-611 A 155
f. In the ERService folder properties dialog select the security tab. Click on Edit
to change permissions. For the user NETWORK SERVICE set Allow permissions
for Read & execute, List folder contents, Read and Write. If NETWORK
SERVICE does not exist in the Groups or user names window it must be
added.
Figure A.14: ERService Permissions - Workstation Operating System
2PAA111693-611 A 156
g. In the Internet Information Services (IIS) Manager, select

AfwDistEngWcfServices and open the Authentication feature. Enable Windows
Authentication and disable all others.
h. Verify that the service is working by opening up Internet Explorer and navigate
to http://localhost/AfwDistEngWcfServices/DistEngService.svc. If the service is
working this page will be displayed.
Figure A.15: Service Display - Workstation Operating System
A.1.3 Common Problems

1. The user cannot connect the client to the server and you get a security message:
Make sure that the UTC-time between the client and the server does not differ more
that 5 minutes.
2. The user cannot connect the client to the server: Try using the IP-address instead
of the computer name when connecting.
2PAA111693-611 A 157
3. Login Dialog: If a user other than the current Windows user is used to log in to the
server, the password must be entered every time the Engineering Repository Browser
is started.
4. The user may experience the following error:
HTTP Error 404.3 - Not Found
Description: The page requested by the user cannot be served because of the
Multipurpose Internet Mail Extensions (MIME) map policy that is configured on the Web
server. The requested page has a file name extension that is not recognized, and is not
allowed.
To resolve this issue, you need to take the following steps:
1. Run a command prompt window as administrator. Start, cmd as normal then press
CTRL+SHIFT+ENTER.
2. Navigate to c:\windows\Microsoft.Net\Framework\v3.0\Windows Communication
Foundation\.
3. Run the command ‘ServiceModelReg -i’ - The user should receive the results below.
4. Exit.
A.1.4 Configuration Verification

Verify that the Engineering Repository Web Service is correctly configured by performing
the following:
1. Start Internet Explorer.
2. Enter the following address in the Address bar:
http://localhost/AfwDistEngServices/
DistributedEngineering.asmx
A web page should display which operations are provided by the Engineering
Repository Web Service.
2PAA111693-611 A 158
A.2 Client Configuration
A.2 Client Configuration

When starting the Engineering Repository user interface for the first time, enter the
name of the server if it is located on a different workstation. If it's on a different node,
make sure to open the port 80 in the firewall on the server node.
The Engineering Repository user interface can be started from the toolbar in the Plant
Explorer or from a context menu:
1. Start the Plant Explorer.
2. Navigate to an Entity (such as Control Project) and right-click on it to display the
context menu. The context menu has an item called Engineering Repository.
A.3 Common Problems

Some common problems associated with the configuration of the Engineering Repository
are described in Table A.1.
Table A.1: Common Problems
Problem Solution
Cannot connect Make sure that the UTC time between the client and the server does
the client to the not differ more that 5 minutes. If the time difference is considered
server and a impossible to correct, it is possible to increase to maximum allowed
security time difference. To increase the time difference tolerance,
message is modifications in the configuration file for both the service and the
displayed clients must be performed. The configuration file for the service is
called Web.config and is located in the directory where the service
is installed. The configuration file for the client is called
AfwEngineeringRepository.exe.config and is located in the bin
directory of 800xA. Similar modification shall be done in both files.
The time difference tolerance should be set as low as possible.
Cannot connect Use the IP address instead of the computer name when connecting
the client to the or ensure that Microsoft WSE 3.0 is installed on both the client and
server the server.
Login dialog If a user other than the current Windows user is used to log in to the
server, the password must be entered every time the Engineering
Repository Browser is started
2PAA111693-611 A 159
A.3 Common Problems
Table A.1: Common Problems

(Continued)
Problem Solution
Validation of Select Start > Run and enter aspnet_regiis.exe -i in the command
Engineering window to register ASP.NET 3.0 with IIS.
Repository Web aspnet_regiis.exe is placed in
Service from %Systemroot%\Microsoft.NET\Framework\2.0.x.
Internet Explorer
fails if ASP.NET
2.0 is not
registered with
IIS
Logon to Ensure ASP.NET 2.0 is an “Allowed” Engineering Repository Web
Engineering Service Extension. This only applies if the Web Service is running on
Repository the Server Operating System.
failed To set this:
1. Right-click on the My Computer icon from the desktop.
2. Select Manage.
3. Select Web Service Extensions.
3. Click Allow.
2PAA111693-611 A 160
Revision History
Revision History
Revision History
This section provides information on the revision history of this User Manual.
The revision index of this User Manual is not related to the System 800xA Revisions.
Revision History
The following table lists the revision history of this User Manual.
Revision
Description Date
Index
A Published for 800xA System 6.1.1 release April 2021
Updates in Revision Index A

The following table shows the difference compared to the previous release
2PAA111693-610 Revision A.
Updated Section / Subsection Description of Update

General New functionality included: Soft controller
secure download configuration, PR Batch
History, xStream commissioning.
Information Management Initial trust is required to be established
manually.
Batch Management Redundancy description for workgroup
environment.
2PAA111693-611 A 161
2PAA111693-611 A 162
Index
Index
Numerics
800xA for AC, 51 D
800xA for Advant Master, 49 Database, 86
800xA for DCI, 67 DBA (ADO) data provider, 95
800xA for Symphony Plus Harmony, 61 Defining users, 26
Device library wizard, 79
A Device library wizard , 79
About this book, 11 Device management and fieldbuses
AC 800M Device library wizard, 79
Downloading AC 800M controller firmware, 32 Device management FOUNDATION Fieldbus
Setting IP address, 32 Clock Synchronization, 136
ADO provider, 100
Affinity, 19 F
Configuration, 22 FOUNDATION Fieldbus
Load balancing and system performance, 19 Clock Synchronization, 136
Planning load balancing, 20
Asset Optimization I
SAP/PM Integration, 76 Information Management, 83
Web-enabled views, 73 Creating database instance, 86
DBA (ADO) data provider, 95
B Edit ADO data provider configuration, 100
Batch Analysis Application, 118 ODBC data source, 97
Batch Management, 109 Setup, 83
Shutdown script, 113 Starting PAS, 94
Toolbar, 114
Batch Management Toolbar, 114 L
Batch Redundancy Configuration, 109 Load balancing, 20
Batch View Client, 115 Load balancing and system performance, 19
Batch View Configuration, 117
Batch View Installation, 116 O
Oracle, 95
C Oracle , 97
CI862 TRIO interface, 114
Clock Synchronization, 134, 136 P
Compact flash, 37 PAS, 94
Configuration PLC Connect, 71
Affinity, 22 PR Batch History, 115
2PAA111693-611 A 163
Index
Print BMA Configuration, 114 T

Time client
S Configuring, 131
SAP/PM Integration, 76 Time server
Set Data and Time for Batch Servers, 114 Configuring, 130
Setting IP address, 32 Time services, 129
Shutdown script, 113 Configuring, 130
Shutdown Script, 113 Toolbar, 114
SQL Server Memory Limit, 121
System level tasks U
Affinity, 19 Users
Configuration, 22 Defining, 26
Configuring the time client, 131
Configuring the time server, 130 W
Defining users, 26 Web-enabled views on non-800xA systems, 73
Time services, 129
Configuring, 130
2PAA111693-611 A 164
solutions.abb/800xa 800xA is a registered or pending trademark We reserve all rights to this document and
of ABB. All rights to other trademarks reside the items and images it contains. The
solutions.abb/controlsystems with their respective owners. reproduction, disclosure to third parties or
the use of the content of this document –
We reserve the right to make technical including parts thereof – are prohibited
changes to the products or modify the without ABB’s prior written permission.
2PAA111693-611 A
contents of this document without prior

notice. With regard to purchase orders, the Copyright © 2021 ABB.
agreed particulars shall prevail. ABB does All rights reserved.
not assume any responsibility for any errors
or incomplete information in this document.

2PAA111693-611 A en System 800xa 6.1.1 Installation Update and Upgrade - Post Installation

Uploaded by

Copyright:

Available Formats

2PAA111693-611 A en System 800xa 6.1.1 Installation Update and Upgrade - Post Installation

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

2PAA111693-611 A en System 800xa 6.1.1 Installation Update and Upgrade - Post Installation

Uploaded by

Copyright:

Available Formats

SYSTEM VERSION 6.1.

ABB Ability™ System 800xA

ABB Ability™ System 800xA

Document Number: 2PAA111693-611

Trace back information Main Publication:

Copyright © 2021 by ABB. All rights reserved.

About this User Manual

1 Post Installation Overview

2 Central Licensing System

5 800xA for AC 800M

5.2.2 Verify the Processor Unit IP Addresses ............................................... 36

6 800xA for Advant Master

7 800xA for AC 100

8 800xA for Symphony Plus Harmony

9 800xA for MOD 300

10 800xA for DCI

11 800xA for Freelance

14 Device Library Wizard

15.7 Information Management Profiles Client Post Installation ................................ 102

19 IPsec Configuration Tool

20 800xA Clock Synchronization

20.3 Configuring the System Time Server ................................................................ 130

21 Installing additional products

Appendix A Engineering Repository

Revision History ..................................................................................................... 161

Index .......................................................................................................................... 163

About this User Manual

User Manual Conventions

Warning, Caution, Information, and Tip Icons

Caution icon indicates important information or warning related to the concept

Information icon alerts the reader to pertinent facts and conditions.

Released User Manuals and Release Notes

It is in pdf format and is provided in the following ways:

1 Post Installation Overview

1.1 System Security

1.2 800xA Installation User

1.3 Post Installation Sequence

2 Central Licensing System

3 800xA Base System

3.1 Load Balancing (Affinity)

Figure 3.1: Configuration example of load balancing

3.1.2 Planning Load Balancing

Figure 3.2: Triangle relationship for planning affinity

Figure 3.3: Load balancing plan example

Aspect Aspect Aspect Connectivity Connectivity

3.1.3 Configuring Affinity

Creating the Affinity Objects

Configuring the Affinity Aspects

Figure 3.4: Affinity Summary Tab

8. Repeat this procedure for the AS affinity.

Applying Affinity Settings to the Services

ABB recommends setting up Affinity for services according to Table 3.2.

Table 3.2: Affinity Services

3. Select Service Definition in the Aspect List Area.

3.2 Configuring Users and Permissions

3.3 Time Services

4.1 Configuring SoftPoint Services

and then click New Object.

Figure 4.1: Generic Control Network Configuration Aspect