Vous êtes sur la page 1sur 118

OperateIT

Process Portal
Version B2.0
Installation
OperateIT
Process Portal
Version B2.0

Installation
NOTICE
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.

In no event shall ABB be liable for direct, indirect, special, incidental or consequential
damages of any nature or kind arising from the use of this document, nor shall ABB be
liable for incidental or consequential damages arising from use of any software or hard-
ware described in this document.

This document and parts thereof must not be reproduced or copied without written per-
mission from ABB, and the contents thereof must not be imparted to a third party nor used
for any unauthorized purpose.

The software or hardware described in this document is furnished under a license and
may be used, copied, or disclosed only in accordance with the terms of such license.

This product meets the requirements specified in EMC Directive 89/336/EEC and in Low
Voltage Directive 72/23/EEC.

Copyright 2004 ABB


All rights reserved.

Release: November 2004


Document number: WBPEEUI220793D0

TRADEMARKS
Registrations and trademarks used in this document include:
Acrobat Reader Registered trademark of Adobe Systems Inc.
ActiveX Registered trademark of Microsoft Corporation.
Adaptec Registered trademark of Adaptec, Incorporated.
Adobe Registered trademark of Adobe Systems, Incorporated.
AdvaBuild Registered trademark of ABB.
Aspect Objects Trademark of ABB.
AutoCad Registered trademark of AutoDesk, Incorporated.
Contronic P Registered trademark of ABB.
Contronic S Registered trademark of ABB.
DirectCD Trademark of Adaptec, Incorporated.
Ethernet Trademark of Xerox Corporation.
Freelance 2000 Trademark of ABB.
FrontPage Registered trademark of Microsoft Corporation.
Industrial IT Enabled Trademark of ABB.
INFI 90 Registered trademark of ABB.
INFI-NET Registered trademark of ABB.
Inform IT Trademark of ABB.
Java Trademark of Sun Microsystems, Incorporated.
Microsoft Registered trademark of Microsoft Corporation.
OPC Trademark of OPC Foundation.
OperateIT Trademark of ABB.
Pentium Registered trademark of Intel Corporation.
Produce IT Trademark of ABB.
Rainbow Registered trademark of Rainbow Technologies, Incorporated.
SentinalSuperPro Trademark of Rainbow Technologies, Incorporated.
SQL Server Trademark of Microsoft Corporation.
Transaction Server Registered trademark of Microsoft Corporation.
Windows Registered trademark of Microsoft Corporation.
Windows NT Registered trademark of Microsoft Corporation.
Windows Server Trademark of Microsoft Corporation.
TABLE OF CONTENTS

About This Book


General ............................................................................................................................13
Use of Warning, Caution, Information, and Tip ..............................................................13
Document Conventions ...................................................................................................14
Related Documentation ...................................................................................................15
Intended User...................................................................................................................16

Section 1 - Planning
Introduction .....................................................................................................................17
Considerations .................................................................................................................17
Installation Types.............................................................................................................17
Client .............................................................................................................18
Server .............................................................................................................18
Standalone ............................................................................................................18
Independent ..........................................................................................................18
Features............................................................................................................................18
Node Requirements .........................................................................................................19
Additional Considerations....................................................................................22
Network Architecture Recommendations .......................................................................23
Redundant System................................................................................................24
Configuration One...............................................................................24
Configuration Two ..............................................................................25
Dual NIC System with a Separate Control Network............................................25
TCP/IP ......................................................................................25
Redundant System Running AC800M Or Melody ..............................................26
Pre-defined User Accounts ..............................................................................................26

WBPEEUI220793D0 7
Table of Contents

Software .......................................................................................................................... 29
Disk Defragmenter............................................................................................... 30
Antivirus ............................................................................................................ 30
Microsoft Office Application............................................................................... 30

Section 2 - Third Party Software


Introduction ..................................................................................................................... 31
Install Operating System ................................................................................................. 31
Windows 2000 Server .......................................................................................... 31
Install Windows 2000 Add-On Components (IIS Software) .............. 33
Windows 2000 Service Pack Four ...................................................... 34
Patches and Hot Fixes ......................................................................... 34
Windows Server 2003 .......................................................................................... 35
Patches and Hot Fixes ......................................................................... 37
Windows XP Professional.................................................................................... 37
Windows XP Service Pack Two.......................................................... 39
Patches and Hot Fixes ......................................................................... 39
Install .NET Framework 1.1............................................................................................ 39
Install Microsoft Office Excel XP or 2003 ..................................................................... 40
Install SQL Server 2000 .................................................................................................. 41
Install SQL Server 2000 Service Pack 3a ............................................................ 43
Install MDAC 2.8 ............................................................................................................ 44
Install Media Player 9.0 .................................................................................................. 45
Other Service Packs ........................................................................................................ 45
DCOM Settings For Windows ........................................................................................ 45
Internet Explorer Configuration .................................................................................... 46
Network Settings ............................................................................................................. 47
NIC Installation Order ........................................................................ 47
Binding Order ..................................................................................... 48

Section 3 - Process Portal Software


Introduction ..................................................................................................................... 49
Install Process Portal ....................................................................................................... 49

8 WBPEEUI220793D0
Table of Contents

Client Setup Type .................................................................................................50


Server Setup Type ................................................................................................51
No Checkboxes ...................................................................................52
Historical Data Server Checkbox ........................................................52
Configuration Server Checkbox..........................................................53
Both Checkboxes selected...................................................................53
Standalone Setup Type .........................................................................................53
Independent Setup Type .......................................................................................54
Client ......................................................................................54
Server ......................................................................................55
Publishing and Distribution Setup........................................................................56
Electronic Documentation....................................................................................57
SQL Database Maintenance .................................................................................58
Complete Installation ...........................................................................................60
Install Process Portal Connect Products ..........................................................................60
Install Process Portal Licenses ........................................................................................61
Predefined Object Configuration Wizard ........................................................................61
Automatic Startup and Verification of Process Portal .....................................................61

Section 4 - Upgrading Process Portal


B1.1 and B1.2
Introduction .....................................................................................................................63
Procedure .........................................................................................................................64
Restarting Upgraded Nodes.............................................................................................68

Section 5 - Adding Process Portal Options


Introduction .....................................................................................................................69

Section 6 - Reinstalling Process Portal


Introduction .....................................................................................................................73

Section 7 - Software License Entry


Introduction .....................................................................................................................77

WBPEEUI220793D0 9
Table of Contents

Obtaining Ethernet Address ............................................................................................ 78


License Entry Program.................................................................................................... 78
Requirements ....................................................................................................... 78
Install ............................................................................................................ 79
Uninstall ............................................................................................................ 79
Running the License Entry Program.................................................................... 79
Selecting a Machine ID ................................................................................................... 79
Requesting Software Keys .............................................................................................. 80
Entering Licenses ........................................................................................................... 81
File Installation .................................................................................................... 82
Manual Installation .............................................................................................. 82
Licensing Troubleshooting.............................................................................................. 84
Locating the License File..................................................................................... 84
Unavailable Machine IDs..................................................................................... 84
Rainbow SentinelSuperPro Dongle .................................................... 84
Ethernet Address................................................................................. 85
Error Codes .......................................................................................................... 85
License Assignment Editor ............................................................................................. 88
Assign Licenses ................................................................................................... 88
License Diagnostics ............................................................................................. 89

Section 8 - Electronic Documentation


Introduction ..................................................................................................................... 93
Navigation............................................................................................................ 93
Bookmarks ...................................................................................... 93
Links ...................................................................................... 93
Acrobat Search..................................................................................................... 93
Search Options ..................................................................................................... 94

Section 9 - Back Up and Restore


Introduction ..................................................................................................................... 95
Backup Procedures.......................................................................................................... 95
Restrictions ...................................................................................... 95

10 WBPEEUI220793D0
Table of Contents

Configuration Data..............................................................................96
Restore Procedures ..........................................................................................................98

Appendix A - Domain Controllers


Introduction ...................................................................................................................103
Domain Networks..........................................................................................................103
Domain Setup ................................................................................................................103

Appendix B - Time Synchronization


Introduction ...................................................................................................................107

Appendix C - User Account/Account Rights Manual


Configuration
Introduction ...................................................................................................................109
Create Accounts, Groups, and Users .............................................................................109
Service Accounts................................................................................................109
Create a New Service Account..........................................................110
Assign Administrative Rights ...........................................................111
Assign User Rights............................................................................111
User Group .........................................................................................................112
Create a New User Group .................................................................113
Assign User Rights............................................................................113
SQL Access Rights........................................................................................................114

WBPEEUI220793D0 11
Table of Contents

12 WBPEEUI220793D0
About This Book

General
This instruction describes how to install software for the Process Portal system. It
provides hardware, software, and third party requirements. It also provides network
settings, upgrade procedures, and backup and restore procedures.
Use this section as a guide to the conventions and terminology used throughout this
book.

Use of Warning, Caution, Information, and Tip


This publication includes Warning, Caution, and Information where appropriate
to point out safety related or other important information. It also includes Tip to
point out useful hints to the reader. The corresponding symbols should be
interpreted as follows:
Electrical warning icon indicates the presence of a hazard which could result in
electrical shock.

Warning icon indicates the presence of a hazard which could result in personal
injury.

Caution icon indicates important information or warning related to the concept


discussed in the text. It might indicate the presence of a hazard which could
result in corruption of software or damage to equipment/property.

Information icon alerts the reader to pertinent facts and conditions.

WBPEEUI220793D0 13
Document Conventions About This Book

Tip icon indicates advice on, for example, how to design your project or how to
use a certain function
Although Warning hazards are related to personal injury, and Caution hazards are
associated with equipment or property damage, it should be understood that
operation of damaged equipment could, under certain operational conditions, result
in degraded process performance leading to personal injury or death. Therefore,
comply fully with all Warning and Caution notices.

Document Conventions
The following conventions are used for the presentation of material:
The words in names of screen elements (for example, the title in the title bar of
a window, the label for a field of a dialog box) are initially capitalized.
Capital letters are used for the name of a keyboard key if it is labeled on the
keyboard. For example, press the ENTER key.
Lowercase letters are used for the name of a keyboard key that is not labeled on
the keyboard. For example, the space bar, comma key, etc.
Press CTRL+C indicates that you must hold down the CTRL key while
pressing the C key (to copy a selected object in this case).
Press ESC E C indicates that you press and release each key in sequence (to
copy a selected object in this case).
The names of push and toggle buttons are boldfaced. For example, click OK.
The names of menus and menu items are boldfaced. For example, the File
menu.
The following convention is used for menu operations: MenuName >
MenuItem > CascadedMenuItem. For example: select File > New > Type.
The Start menu name always refers to the Start menu on the Windows
Task Bar.
System prompts/messages are shown in the Courier font, and user
responses/input are in the boldfaced Courier font. For example, if you enter a
value out of range, the following message is displayed:

14 WBPEEUI220793D0
About This Book Related Documentation

Entered value is not valid. The value must be 0 to30.


You may be told to enter the string TIC132 in a field. The string is shown as
follows in the procedure:
TIC132
Variables are shown using lowercase letters.
sequence name

Related Documentation
The following is a listing of documentation related to the Process Portal software
application.

Category Title Description


Process Portal Base Software Operation WBPEEUI220787??

Configuration WBPEEUI220790??

Grafx Display Editor WBPEEUI340020??

Process Portal OPC Connect Software Installation WBPEEUI220797??

Operation WBPEEUI220794??

Configuration WBPEEUI220795??

Process Portal Harmony Connect Software Installation WBPEEUI220796??

Operation WBPEEUI220788??

Configuration WBPEEUI220791??

Process Portal MOD Connect Software Installation WRPEEUI220003??

Operation WRPEEUI220001??

Configuration WRPEEUI220002??

WBPEEUI220793D0 15
Intended User About This Book

Category Title Description


Process Portal Freelance Connect Software Installation WGPEEUI220003??

Operation WGPEEUI220001??

Configuration WGPEEUI220002??

Process Portal Melody Connect Software Installation 3BBDD011662R???

Operation and Configuration 3BBDD011661R???

Produce IT Batch Installation WBPEEUI270013??

Operation WBPEEUI270013??

Configuration WBPEEUI270013??
NOTE: The ?? marks are place holders for revision levels of each document.

Intended User
This instruction assumes that the software system installation is performed by a
system administrator with comprehensive knowledge of network setup and the
Windows operating system (OS). The following software and system areas will be
installed and configured in the overall support of the Process Portal system. The
additional software/areas are as follows:
Internet Explorer.
SQL Server and its enterprise manager.
Windows user manager.
Control panel services.
Windows explorer.
Microsoft Office XP or 2003.

16 WBPEEUI220793D0
Section 1 Planning

Introduction
This section describes the platform (hardware) and software requirements needed to
successfully run Process Portal software along with general and special
considerations.

Considerations
It is always recommended that server applications be placed on separate nodes.
Combining server and client functionality in one node can result in increased
client functionality response times when bulk configuration changes or large
retrieval requests for historical data are made.
When more than one monitor is configured, 128 megabytes of RAM must be
added for each additional screen.
Refer to the appropriate installation and configuration instruction manuals for
each Connect product to determine the correct control network interface
requirements.
Refer to the appropriate installation and configuration instruction manuals for
each Connect product to determine any specific hardware/software
requirements.

Installation Types
There are four different installation types of Process Portal:
Client.
Server.
Standalone.
Independent.

WBPEEUI220793D0 17
Client Section 1 Planning

Client
The client installation requires Windows 2000 Server, Server 2003, or XP software
to be installed. Client installations cannot run Process Portal servers or mirror sites
and do not require IIS or SQL server software.

Server
The server installation requires Windows 2000 Server, Server 2003, or XP software,
SQL Server 2000, and IIS software to be installed. Server installation is for nodes
running a configuration server, historian server, Real Time Data Server (RTDS), or
mirror database. The Server installation also supports client functionality.

Standalone
The standalone installation is for a single standalone (nonredundant) node. The
standalone installation requires Windows XP, SQL Server 2000, and IIS to be
installed on the node. This node supports running a configuration server, historian,
RTDS, and mirror site on a single node along with client functionality.

Independent
The independent installation requires Windows Server 2003, SQL Server, and IIS
software to be installed for the server node and Windows XP for the client nodes.
The independent server node includes the configuration server, historian server, and
RTDS server software on a single node. Up to seven independent clients are
supported and do not require SQL server or IIS software since they do not support
running servers.
The independent option will automatically create server and alarm and event
configuration objects during the system install.

Features
Refer to Table 1 for different Process Portal features and their characteristics.

18 WBPEEUI220793D0
Section 1 Planning Node Requirements

Table 1. Process Portal Systems

Feature Characteristic/Value
System (servers and / or clients) 60 nodes maximum (only one configuration server per system).
Client Nodes Up to 60 clients per system maximum.
Non-auxiliary (or full) clients Up to 30 per system.
Auxiliary clients It is recommend that all clients be installed as Auxiliary Clients.
Primary RTDS nodes Up to 15 per system.
Primary Historian nodes Up to 5 per system.

Node Requirements
Node requirements for Process Portal applications are intended for new system
purchases or expansions for existing systems. Current users of Process Portal
B1.2 performing software upgrades may continue to use their existing hardware
platforms. However, some system performance decrease may be seen due to
increased system demand from applications such as the Microsoft OS. ABB
requires that client nodes are to be a minimum of 1 Ghz processor and upgraded
to 512 megabytes of ram.

Refer to Table 2 for specific hardware requirements when having a single Process
Portal application on a node.

Table 2. Single Process Portal Application on a Node

Configuration
Client RTDS Historian
Server
CPU 2.x Ghz or faster. 2.x Ghz or faster. 2.x Ghz or faster. 2.x Ghz or faster.
Memory 1 GB. 1 GB (10 or less 1 GB (10 or less 1 GB (10 or less
nodes per system). nodes per system). nodes per system).
2 GB (10 or more 2 GB (10 or more 2 GB (10 or more
nodes per system). nodes per system). nodes per system).

WBPEEUI220793D0 19
Node Requirements Section 1 Planning

Table 2. Single Process Portal Application on a Node (Continued)

Configuration
Client RTDS Historian
Server
OS 2 Windows XP, 2000 Windows XP, 2000 Windows 2000 Windows 2000
Server, or Server Server, Server 2003 Server or Server Server or Server
2003 (Aux. or Full (10 or less nodes per 2003. 2003.
Client). system).
Windows 2000 Windows 2000
Server or Server Server or Server
2003 (when used as 2003 (10 or more
a mirror node). nodes per system).
Hard Disk 20 GB EIDE. 20 GB EIDE/SCSI. 20 GB SCSI 3 (for 20 GB SCSI (for OS
OS & ABB & ABB Software).
Software). 20 GB SCSI (7200
xxx GB SCSI 3 (for RPM) (Backup
Historical, Archive, Data).
and Backup Data).
Peripherals Windows OS Windows OS Windows OS Windows OS
supported keyboard supported keyboard supported keyboard supported keyboard
and pointing device and pointing device and pointing device and pointing device
(mice/trackball). (mice/trackball). (mice/trackball). (mice/trackball).
Network 100BaseTx network 100BaseTx network 100BaseTx network 100BaseTx network
adaptor 4,5 adaptor 4,5 adaptor 4,5 adaptor 4,5
Video 16MB VGA video 16MB VGA video 16MB VGA video 16MB VGA video
adaptor 6 (1280x1024 adaptor 6 (1280x1024 adaptor 6 (1280x1024 adaptor 6 (1280x1024
pixels minimum). pixels minimum). pixels minimum). pixels minimum).

20 WBPEEUI220793D0
Section 1 Planning Node Requirements

Table 2. Single Process Portal Application on a Node (Continued)

Configuration
Client RTDS Historian
Server
Misc. CD Optical Device. CD Optical Device. CD Optical Device. CD Optical Device.
Audio support (on- Audio support (on- Audio support (on- Audio support (on-
board or add-in). board or add-in). board or add-in). board or add-in).
Control Network Available parallel or
Interface 7 USB port.
NOTES:
1. Process Portal Mirror node require Windows 2000 or Windows Server 2003.
2. Windows XP Professional SP2 with Internet Explorer 6.0 SP2, Windows 2000 Server SP4 with Internet Explorer 6.0
SP1, Windows Server 2003 with Internet Explorer 6.0 SP1.
3. Actual hard disk storage should be estimated based on user requirements for on-line and archive storage.
4. Redundant network are supported with ABB recommended network configuration.
5. Static IP addressing is required.
6. Multiple monitors are supported with ABB recommended graphic adaptors.
7. Refer to Process Portal Connect product for specific interface requirements.

Refer to Table 3 for combined Process Portal applications on a node.

Table 3. Combined Process Portal Applications on a Node

Recommended
Process Portal
Additional Hardware Comment
Server Application
Specification

Configuration Server, Refer to Table 2 for


Client specifications.

Historian, Client Refer to Table 2 for


specifications.

RTDS, Client Refer to Table 2 for Maximum of 10,000 total RTDS tags 1.
specifications. Maximum of 3 RTDS types per machine 2.

Configuration Server, Dual Processor Maximum of 5,000 total RTDS tags 1.


RTDS, Client 2 GB Memory. Maximum of 1 RTDS types per machine.

Configuration Server, Dual Processor Maximum of 5,000 total Historian atoms.


Historian, Client 2 GB Memory.

WBPEEUI220793D0 21
Additional Considerations Section 1 Planning

Table 3. Combined Process Portal Applications on a Node (Continued)

Recommended
Process Portal
Additional Hardware Comment
Server Application
Specification

Historian, RTDS, Dual Processor Maximum of 2500 total RTDS tags.


Client 2 GB Memory. Maximum of 1 RTDS type.
Maximum of 5,000 total Historian atoms.

Configuration Server, Dual Processor Maximum of 1,000 total RTDS tags.


Historian, RTDS, 2 GB Memory. Maximum of 1 RTDS type.
Client
Maximum of 200 total Historian atoms.
NOTES:
1. Refer to specific Connect products for maximum number of supported RTDS tags.
2. Refer to Software Combinations table for valid RTDS type combinations.

Additional Considerations
The following applies to all the Process Portal applications:
One other server application, the Function Block Server, is optionally available
for installation in the system. This server application should be installed in
nodes that have the RTDS application installed. Redundant Function Block
Server applications should be installed in nodes that have the Redundant RTDS
application installed. Only one Function Block Server application is needed per
system. Recommendations for RTDS nodes are unaffected by the inclusion of
the Function Block Server application on the same node.
Other ABB applications such as Produce IT Batch and Inform IT as well as
third party applications may apply additional load on the node requiring
additional node resources (CPU speed, RAM, hard disk capacity, etc.).
Therefore, they should be loaded on separate nodes.
Listed hard disk size for the historian is nominal; actual hard disk size will vary
depending upon the amount of historical data and event collection required.
This is a function of storage rate and length of time before archival. Tools for
calculating the required hard disk space size are included on the installation
CD.

22 WBPEEUI220793D0
Section 1 Planning Network Architecture Recommendations

Unless stated differently, the hard disk sizes must include 1 Gbyte free space on
the OS partition and 1 Gbyte free space on the Process Portal partition.
Composer Server can never be installed on the same node along with Process
Portal RTDS and should not be installed on the same node along with Process
Portal Historian Server.
For Process Portal systems using domains, the domain controllers are required
to be machines that do not run Process Portal software.

Network Architecture Recommendations


Process Portal relies on a correct configuration of TCP/IP for its DCOM
communications, especially when the Process Portal configuration includes multiple
networks. The following configurations are fully supported.

Single NIC System


The simplest Process Portal configurations use a single NIC in each system
(Figure 1).

TC05983A

Figure 1. Single NIC Configuration

WBPEEUI220793D0 23
Redundant System Section 1 Planning

Redundant System
A Process Portal system can achieve network level redundancy by using two
separate physical networks and two NICs for each node (Figure 2).

TC05984A

Figure 2. Redundant Portal B System

In order for Process Portal to function correctly, a dual NIC configuration must
make both network connections appear as a singe IP address. It is vital that Intel
cards and Intel PROSet software be used for proper operation. Multiple
configurations are as follows.

Configuration One
Hardware\Software configuration:
Cisco Catalyst XL switches (C3548-XL) with Spanning Tree enabled.
Intel PRO/100 S server adapters (two per machine).
Intel PROSet software (version 6.4.0.0), set to switch fault tolerant mode.
One NIC from each computer needs to be connected to each of two Cisco switches
(Figure 2). In testing, the Cisco switches were connected via an optical uplink cable.
The communication, between the switches and the computers, needs to be
configured for 100 MHz and full-duplex (set on the computer and the switch).

24 WBPEEUI220793D0
Section 1 Planning Dual NIC System with a Separate Control Network

The Intel PROSet software on each computer must be configured to have all NICs
connected to the first switch as Preferred Primary. The NICs connected to the
second switch should be configured as Preferred Secondary.

Configuration Two
Hardware/Software configuration:
Hirschmann Rail Switches (RS2-TX/TX).
Intel PRO/100 S Server Adapters (Two per machine).
Intel PROSet Software (version 6.4.0.0), set to switch fault tolerant mode.
This configuration can use 24 nodes and 10 Hirschmann Rail Switches. Each node
connected to two Hirschmann switches. The Hirschmann switches are connected via
their proprietary optical backbone with multimode cable. The communication
between the switches and the nodes is configured for 100 Mb and full-duplex (set on
the node and the switch). The Intel PROSet software, on each node, is configured to
have the Preferred Primary NIC connected to the Hirschmann switch with the even
numbered IP address. The NICs connected to the odd numbered Hirschmann switch
are configured as Preferred Secondaries.
The Hirschmann switches are connected with multimode optical cable with SC
connectors, and the connectors are to be disassembled to create crossover cabling.
Each switch had its RM and standby switches in the off position.

Dual NIC System with a Separate Control Network


It is possible to have a dual NIC Process Portal system with a separate control
network (Figure 3).

TCP/IP
Each NIC must be configured with a separate fixed/static IP address. It is
recommended that the two cards be on separate subnets. A default gateway for

WBPEEUI220793D0 25
Redundant System Running AC800M Or Melody Section 1 Planning

TC05985A

Figure 3. Dual NIC System

either NIC should be avoided to prevent network traffic on both networks from
being sent out the default gateway.
A redundant Process Portal system requires a single IP address for dual NIC
usage.

Redundant System Running AC800M Or Melody


This configuration involves a combination of setups described in Redundant System
on page 24 and Dual NIC System with a Separate Control Network on page 25.
Refer to (Figure 4) for more information.

Pre-defined User Accounts


When installing Process Portal, the user has the option of creating pre-defined user
accounts. Accounts created depend on whether a domain or a workgroup network
environment is used.
Table 4 shows the local groups automatically created on each node when this option
is selected. Groups are identical in domain and workgroup network environments
except for their membership. Local groups are used to control Process Portal

26 WBPEEUI220793D0
Section 1 Planning Pre-defined User Accounts

TC05986A

Figure 4. Process Portal Redundant System

security and to grant required Windows privileges and rights. Individual user
accounts are granted rights and privileges indirectly by being assigned to these
groups. Table 4 shows each group name and its corresponding access rights.

Table 4. Local Groups

Group Name Process Portal Access Rights


IIT Operators Read
Control
Acknowledge

WBPEEUI220793D0 27
Pre-defined User Accounts Section 1 Planning

Table 4. Local Groups (Continued)

Group Name Process Portal Access Rights


IIT Technicians Read
Control
Tuning
Operating Parameters
Acknowledge
Shutdown
IIT Engineers Full Control

Table 5 shows the accounts created within a workgroup network environment.


Accounts are granted privileges and access rights when they are assigned to the
stated local groups. Accounts are not created within a domain network environment.

Table 5. Local User Accounts Used in a Workgroup

Local User Member of Local


Default Password
Account Name Group
IIT Operator operator Users
IIT Local Users
IIT Operators
IIT Technician technician Users
IT Local Users
IIT Technicians
IIT Engineer engineer Users
IIT Local Users
IIT Engineers

Table 6 shows the domain group accounts created within a domain network
environment. Accounts are mapped to their equivalent local group on each
computer. Accounts are not directly granted any special privileges or access rights,
instead they are granted rights and privileges by being members of the local groups.
Accounts are not created within a workgroup network environment.

28 WBPEEUI220793D0
Section 1 Planning Software

Table 6. Domain Groups

Domain Group Account Name Member of Local Group


IIT Domain Users IIT Local Users
IIT Operators IIT Operators
IIT Technicians IIT Technicians
IIT Engineers IIT Engineers

Table 7 shows the domain user accounts created within a domain network
environment. Accounts are granted their required privileges and access rights by
being members of the stated domain groups. Accounts are not created within a
workgroup network environment.

Table 7. Domain User Accounts

Domain User Account Default Member of Domain


Name Password Group
IIT Operator operator Domain Users
IIT Domain Users
IIT Operators
IIT Technician technician Domain Users
IIT Domain Users
IIT Technicians
IIT Engineer engineer Domain Users
IIT Domain Users
IIT Engineers

Software
The following software recommendations for Process Portal should be considered:
Disk Defragmenter.
Antivirus.
Microsoft Office Application.
Refer to the following topics for more information.

WBPEEUI220793D0 29
Disk Defragmenter Section 1 Planning

Disk Defragmenter
Computer management practices such as Disk Defragmenter, either running on a
scheduled basis or manually started, is recommended. If this is performed on a
scheduled basis, it is recommended that the schedule be limited to low system
demand hours and not during scheduled database backups.

Antivirus
The use of virus protection and detection software must be based on a corporate
security policy that should be reviewed on a regular basis. This risk assessment, as
well as the proper implementation, configuration, installation, operation,
administration, and maintenance is the responsibility of the user of the Process
Portal system.
The selection of virus protection and detection software should be made in
conjunction with the corporate IT responsible group.

Microsoft Office Application


Microsoft Excel XP or 2003 is utilized as part of the reporting functionality of
Process Portal. It supports onscreen and automatic report printing. Excel is also used
as the interface for the Bulk Configuration Manager utility in Process Portal.

30 WBPEEUI220793D0
Section 2 Third Party Software

Introduction
This section presents information on how to install and configure the third party
software components that have been evaluated for use with Process Portal and are
required before Process Portal can be installed.
Process Portal has been found to be fully compatible and functional with this
software as of the date of this document. Refer to ABB Solutions Bank for an up to
date, comprehensive listing of all software that has been evaluated including service
patches and hot fixes released following the Process Portal release.
1. It is possible to halt the installation process between steps, but do not halt the
installation process part way through a step.
2. Unless otherwise instructed, restart the node when prompted.

Install Operating System


Perform the steps needed to install the appropriate OS:
Windows 2000 Server on page 31.
Windows Server 2003 on page 35.
Windows XP Professional on page 37.

Windows 2000 Server


Perform the following steps to install the Windows 2000 Server OS:
1. Do not use a ghosted node image for installing multiple computers because it
prohibits Process Portal from changing node names.
2. Select Install a new copy of Windows 2000 - U.S. English version (Clean
Install).

WBPEEUI220793D0 31
Windows 2000 Server Section 2 Third Party Software

3. Use the typical setup option.


4. Verify the add-on components are selected to install the IIS by completing
Step 2 through Step 5 under Install Windows 2000 Add-On Components (IIS
Software) on page 33.
5. Verify the file system being used by all partitions of the hard disk drive is
NTFS. This is normally handled through installation choices but it can be set
manually by typing the following at the DOS prompt:
convert [drive] /FS:NTFS ENTER
Where:

drive Designator of the hard disk drive


containing the Process Portal software.

Node names cannot contain any spaces or hyphens.

6. Select a protocol as the primary or only network protocol being used. It is


highly recommended that TCP/IP be the only network protocol because it
provides better performance.
For proper system performance, network communication should be 100BaseT
full duplex or better. In cases where network communication speeds are not
maintained constant, it may be necessary to set the speed/duplex rate at the
network switch, network card, or both.
A single, static IP address is required.
Verify the latest NIC driver is installed. The default NIC drivers supplied with
Windows or with the NIC card may not be the latest available. It is recommended
that the user verify with the computer manufacturer on the NIC card
manufacturer if any additional patches or updates are available.

32 WBPEEUI220793D0
Section 2 Third Party Software Windows 2000 Server

7. Set all Process Portal nodes to work in the same domain or workgroup
environment.
Changing workgroup, domain, or network settings must be avoided once the
system is deployed. Any changes should be effected with the system offline, and
a reboot is required when complete.
If using a Workgroup, set up a host file including the name/IP address of the
Central Licensing Server, or set up a DNS.

8. A display resolution of 1280 x 1024 and 65536 or more colors is required.


Process Portal is optimized for these settings.
9. The property for Applications response must be set to optimize for
applications. Ensure Optimize Performance for Applications is enabled.
10. The Windows server property Maximize data throughput for network
applications must be enabled - Enable Maximize data throughput for network
applications in the File and Printer Sharing for Microsoft Networks Properties
window.
11. Change the Long date format: to MMMM dd, yyyy.
The date format containing day of week is not supported.
The administrative shares (drive letter$ is usually c$ or d$) that are
automatically established when the OS is loaded must not be deleted. Typically,
there is no need to change the permissions on administrative shares since only
members of the local Administrative group have remote access to these shares,
and the shares are hidden from browsing by others on the network.

Install Windows 2000 Add-On Components (IIS Software)


IIS software is required to be installed on the configuration server, historian server,
RTDS server, and mirror database servers. It is not required when choosing the
client installation option.
1. Enable the Internet Information Services (IIS) (if required) and Management
and Monitoring Tools options.
IIS is not required when using the client Process Portal installation options.

WBPEEUI220793D0 33
Windows 2000 Server Section 2 Third Party Software

2. Disable Indexing Service.


3. Highlight Internet Information Services (IIS) and then click Details... for
further configuration.
4. Disable the following components:
File Transfer Protocol (FTP) Server.
FrontPage 2000 Server Extensions.
SMTP Service.
Visual InterDev RAD Remote Deployment Support.
5. Verify that the following components are enabled:
Documentation.
Common Files.
Internet Information Services Snap-In.
Internet Services Manager (Server node).
World Wide Web Server.

Windows 2000 Service Pack Four


Install Windows 2000 service pack four.

Patches and Hot Fixes


Install the following patches and hotfixes:
Internet Explorer 6.0 Service Pack 1.
MS03-023.
MS03-041.
MS03-042.
MS03-043.
MS03-044
MS03-049.
MS04-011.
MS04-012.
MS04-014.
MS04-018.
MS04-019.
MS04-020.
MS04-022.

34 WBPEEUI220793D0
Section 2 Third Party Software Windows Server 2003

MS04-023.
MS04-032.
MS04-036.
MS04-037.
MS04-038.

Windows Server 2003


Perform the following steps to install the Windows Server 2003 OS:
1. Do not use a ghosted node image for installing multiple computers because it
prohibits Process Portal from changing node names.
2. Select Install a new copy of Windows Server 2003 - U.S. English version
(Clean Install).
3. Use the typical settings option when prompted.
4. Enter the name of the node.
Node names cannot contain any spaces or hyphens.

5. From the Manage Your Server window, select Add or remove a role and click
Next in the Preliminary Steps window.
6. From the Configurations Options page, choose Custom Configuration.
a. Select Application server (IIS. ASP.NET,).
b. Click Next.
7. Enable the ASP.NET checkbox and click Next.
8. Click Next.
9. Click Finish.
10. Once installed, deselect the Internet Explorer enhanced security configuration
option by selection Control Panel > Add/Remove Programs > Add/Remove
Windows Components.
11. Click Next.

WBPEEUI220793D0 35
Windows Server 2003 Section 2 Third Party Software

12. Verify the file system being used by all partitions of the hard disk drive is
NTFS. This is normally handled through installation choices but it can be set
manually by typing the following at the DOS prompt:
convert [drive] /FS:NTFS ENTER
Where:

drive Designator of the hard disk drive


containing the Process Portal software.

13. Use the following Network Configurations:


a. For proper system performance, network communication should be
100BaseT full duplex or better. In cases where network communication
speeds are not maintained constant, it may be necessary to set the
speed/duplex rate at the network switch, network card, or both.
b. A single, static IP address is required.
c. Verify the latest NIC driver is installed. The default NIC drivers supplied
with Windows or with the NIC card may not be the latest available. It is
recommended that the user verify with the computer manufacturer on the
NIC card manufacturer if any additional patches or updates are available.
Changing workgroup, domain, or network settings must be avoided once the
system is deployed. Any changes should be effected with the system offline, and
a reboot is required when complete.
If using a Workgroup, set up a host file including the name/IP address of the
Central Licensing Server, or set up a DNS.

14. A display resolution of 1280 x 1024 and 65536 or more colors is required.
Process Portal is optimized for these settings.
15. The Windows server property Maximize data throughput for network
applications must be enabled - Enable Maximize data throughput for network
applications in the File and Printer Sharing for Microsoft Networks Properties
window.

36 WBPEEUI220793D0
Section 2 Third Party Software Windows XP Professional

16. Change the Long date format: to MMMM dd, yyyy.


The date format containing day of week is not supported.
The administrative shares (drive letter$ is usually c$ or d$) that are
automatically established when the OS is loaded must not be deleted. Typically,
there is no need to change the permissions on administrative shares since only
members of the local Administrative group have remote access to these shares,
and the shares are hidden from browsing by others on the network.

Patches and Hot Fixes


Install the following patches and hotfixes:
MS03-023.
MS03-041.
MS03-043.
MS03-044.
MS03-045.
MS04-003.
MS04-006.
MS04-011.
MS04-012.
MS04-014.
MS04-015.
MS04-018.
MS04-023.
MS04-032.
MS04-034.
MS04-035.
MS04-036.
MS04-037.
MS04-038.

Windows XP Professional
Perform the following steps to install the Windows XP Professional OS:
1. Do not use a ghosted node image for installing multiple computers because it
prohibits Process Portal from changing node names.

WBPEEUI220793D0 37
Windows XP Professional Section 2 Third Party Software

2. Select Install a new copy of Windows XP - U.S. English version (Clean


Install).
3. Use the typical setup option.
4. Verify the add-on components are selected to install the IIS by completing
Step 2 through Step 5 under Install Windows 2000 Add-On Components (IIS
Software) on page 33.
5. Verify the file system being used by all partitions of the hard disk drive is
NTFS. This is normally handled through installation choices but it can be set
manually by typing the following at the DOS prompt:
convert [drive] /FS:NTFS ENTER
Where:

drive Designator of the hard disk drive


containing the Process Portal software.

Node names cannot contain any spaces or hyphens.

6. Select a protocol as the primary or only network protocol being used. It is


highly recommended that TCP/IP be the only network protocol because it
provides better performance.

For proper system performance, network communication should be 100BaseT


full duplex or better. In cases where network communication speeds are not
maintained constant, it may be necessary to set the speed/duplex rate at the
network switch, network card, or both.
A single, static IP address is required.
Verify the latest NIC driver is installed. The default NIC drivers supplied with
Windows or with the NIC card may not be the latest available. It is recommended
that the user verify with the computer manufacturer on the NIC card
manufacturer if any additional patches or updates are available.

38 WBPEEUI220793D0
Section 2 Third Party Software Install .NET Framework 1.1

7. Set all Process Portal nodes to work in the same domain or workgroup
environment.
Changing workgroup, domain, or network settings must be avoided once the
system is deployed. Any changes should be effected with the system offline, and
a reboot is required when complete.
If using a Workgroup, set up a host file including the name/IP address of the
Central Licensing Server, or set up a DNS.

8. A display resolution of 1280 x 1024 and 65536 or more colors is required.


Process Portal is optimized for these settings.
9. Change the Long date format: to MMMM dd, yyyy.
The date format containing day of week is not supported.
The administrative shares (drive letter$ is usually c$ or d$) that are
automatically established when the OS is loaded must not be deleted. Typically,
there is no need to change the permissions on administrative shares since only
members of the local Administrative group have remote access to these shares,
and the shares are hidden from browsing by others on the network.

Windows XP Service Pack Two


Install Windows XP service pack two.

Patches and Hot Fixes


Install the following patch and/or hotfix.
MS04-038.

Install .NET Framework 1.1


Do not install this on Windows Server 2003 OSs.

Install .NET Framework 1.1 from the Process Portal CD disk (Microsoft\Dot Net
Framework 1.1\dotnetfx.exe).

WBPEEUI220793D0 39
Install Microsoft Office Excel XP or 2003 Section 2 Third Party Software

Install Microsoft Office Excel XP or 2003


Excel must be installed on all Process Portal nodes requiring the ability to view
reports on screen, triggering reports from a function block server, or using a bulk
configuration manager.
Excel software is not included with the Process Portal software.

Installing Excel with the default installation options can cause the Excel program
to be launched for no apparent reason after installation. This is because a number
of Excel features are set to be installed on first use when the default installation
options are used. To prevent this, install ALL options of Excel.
During installation, select Excel to install, then choose Advanced
Customization of Applications checkbox and click Next. Select Run all from
my Computer for the following applications:
1. Excel.
2. Office Tools.
3. Office Shared Features - DO NOT select Alternative User Input > Speech
Recognition and Alternative User Input > Handwriting Recognition features to
be installed. Disable these features if they were previously enabled by referring to
Microsofts Knowledge Base article 823586 (Office 2003) or 326526 (Office XP).

1. Install either Excel XP or Excel 2003 software.


2. Open Excel and set the security for macros to low
(Tools > Macro > Security).
3. If Process Portal is being installed using a different path than a previous
installation, use Microsoft Search (*.xla) to find all EBReportFunctions.xla
files. Then delete the .xla files.
4. If Office XP was installed, install the following updates and continue to Step 6:
MS03-037.
MS03-050.
MS04-027.
5. If Office 2003 was installed, install the following update:
KB828041.

40 WBPEEUI220793D0
Section 2 Third Party Software Install SQL Server 2000

6. Restart the node.

Install SQL Server 2000


Install SQL Server 2000 software from the Industrial IT Third Party Components
CD disk on all nodes except for client installation options.
Configuration server software must be installed on Windows 2000 Server or Server
2003 nodes and requires the standard edition of SQL Server 2000 software to be
installed. If using the standalone option, configuration server software must be
installed on Windows XP nodes and requires the personal edition of SQL Server
2000 to be installed.
RTDS server, mirror server, and historian server software can be installed on nodes
running either Windows XP software or Windows 2000 Server or Server 2003
software. If running Windows XP software, install the personal edition of SQL
Server 2000 software. If running Windows 2000 Server or Server 2003 software,
install the standard edition of SQL Server 2000 software.
Before installation of SQL Server 2000, set the SystemLocale to English (United
States).

To install the SQL Server 2000 software:


Log on under the administrator account.

An error message may be displayed indicating that at minimum, service pack 2 of


SQL Server must be installed. Acknowledge the message and continue the
installation. Service pack 3a will be installed later on.

1. Run autorun.exe from the SQL 2000 folder if the setup window does not
appear automatically.
2. Select SQL Server 2000 Components.

WBPEEUI220793D0 41
Install SQL Server 2000 Section 2 Third Party Software

3. Select Install Database Server.


A warning dialog will open when SQL Server 2000 is installed on Windows
Server 2003. This dialog states that SQL Server 2000 is not supported on
Windows Server 2003. Click Continue on the dialog and continue the
installation.

4. Click Next.
5. Select the Local Computer installation option.
6. Select Create a new instance of SQL Server, or Install Client Tools.
7. Enter BWQYX-RKXP3-DYC33-DQ7VT-F6FHW when prompted for the SQL
server license key number.
8. Select Server and Client Tools.
9. Select the default for the Instance Name.
10. Select Typical in the Setup Type window (Figure 5).

TC02506B

Figure 5. Setup Type

42 WBPEEUI220793D0
Section 2 Third Party Software Install SQL Server 2000 Service Pack 3a

11. Configure the autostart properties of the SQL server services using the
following steps:
a. Select Use the same account for each service. Auto Start SQL Server
Service in the Services Account window.
b. Select Use a Domain User Account.
c. Enter the user name and password of the administrator account used for
installation.
12. Use the Windows Authentication Mode when prompted.
13. Select Next in the Start Copying Files window.
14. If installing SQL Server Standard edition, select the per seat license mode and
enter the number of devices (one per Process Portal client purchased). If not
prompted, wait until the SQL software installation completes and change the
licensing mode to Per Seat by using the following steps:
a. Select Start > Settings > Control Panel > SQL Server 2000 Licensing
Setup.
b. Select Per Seat for in the Licensing Mode.
c. Enter the number of devices (total number of nodes to be installed with
Process Portal software).
15. Proceed to Install SQL Server 2000 Service Pack 3a on page 43 when these
steps are complete.

Install SQL Server 2000 Service Pack 3a


To install the SQL server service pack 3a (MS03-031):
1. Run Sql2ksp3a.exe from the SQL 2000 service pack three directory.
2. Select (and record) the name of the directory that will contain the temporary
setup files.
3. Execute Setup.bat (located in the directory specified in Step 2).
4. Click Next.
5. Select Yes.

WBPEEUI220793D0 43
Install MDAC 2.8 Section 2 Third Party Software

6. Select Next in the Instance Name window.


7. Leave the default for authentication and click Next.
8. Enter a SQL Administrator (SA) password and click OK.
9. Enable both checkboxes in the next window and click Continue.
10. Select OK and do not enable any checkbox.
11. In the Copy Files window, click Next.
12. Install the hotfix:
a. Click Next.
b. Click Next.
c. Select the instance update and click Next.
d. Select Windows Authentication and click Next.

Install MDAC 2.8


Do not install this on the Windows XP OS.

To install MDAC 2.8:


1. Run Setup.exe from the MDAC 2.8 directory on the CD.
2. Choose the Accept License checkbox and click Next.
3. Select Finish.
Select I will restart the system myself and click Finish on Client node
installations only.

4. Select Close.
5. Install hotfix MS04-003.

44 WBPEEUI220793D0
Section 2 Third Party Software Install Media Player 9.0

Install Media Player 9.0


To install Windows Media Player 9.0:
1. Run mpsetup.exe from the Windows Media Player directory.
2. Select the checkbox to accept the license agreement and click Next.
3. Ensure no checkboxes are checked and click Next.
4. Choose the file extension to be opened by default with Media Player and click
Finish.

Other Service Packs


1. Install Microsoft service pack MS04-028. This service pack has three parts or
more to apply.
2. Disable font smoothing for proper Process Portal system operation. This must
be done on all nodes:
a. Select Start > Control Panel > Display.
b. Select the Appearance tab on the Display Properties dialog.
c. Select the Effects button on that dialog.
d. Deselect the Use the following method to smooth edges on screen fonts
checkbox from the Effects dialog.
e. Click the OK button from the Effects dialog.
f. Click the OK button from the Display Properties dialog.

DCOM Settings For Windows


DCOM settings must be configured for Process Portal. Perform the following steps:
1. Select:
Start > Run
The Run dialog appears.
2. Enter dcomcnfg in the Run dialog and click OK.

WBPEEUI220793D0 45
Internet Explorer Configuration Section 2 Third Party Software

3. Windows 2000 Server users, proceed to Step Step 6. Windows Server 2003 and
XP users, continue with Step 4.
4. The Component Services dialog appears. Expand:
Component Services > Computers
5. Right Click on My Computer and select Properties from the context menu
that appears.
6. Select the Default Properties tab.
7. Select Enable Distributed COM on This Computer.
8. Set the Default Authentication Level to None.
9. Select the Default Protocols tab.
10. Verify Connection-oriented TCP/IP is the only configured protocol. Delete
any other protocol found.

Internet Explorer Configuration


The following steps vary by OS.

The Internet Explorer application must be configured for all Process Portal users
and all Process Portal service accounts.

Use standard Windows methods to configure the following Internet Explorer


options:
1. Start Internet Explorer.
2. Select Setup in the Connections tab from Internet Options.
3. Choose the desired method of connecting the node to the Internet and click
Next.
4. Enter the desired method of getting an Internet protocol address when a local
area network is being used and click Next.
5. Specify that the Internet mail account should be set up later and click Next.
6. Click Finish.

46 WBPEEUI220793D0
Section 2 Third Party Software Network Settings

7. Select the General tab in the Internet Options window.


8. Click Settings... in the Temporary Internet Files area of the window.
9. Enable Every visit to the page and click OK.
10. Click OK to complete the configuration.
11. Select the Security tab.
12. Set the zone to Local Intranet.
13. Click Custom Level.
14. Enable Initialize and script ActiveX controls not marked as safe.
15. Enable Access data sources across domains under the miscellaneous topic and
click OK.
16. Click Yes when prompted if the security settings for this zone are to be
changed.
17. Select the Advanced tab.
18. Disable Automatically check for Internet Explorer updates under the browsing
topic, if needed.
19. Enable Disable Script Debugging and click OK.
20. Exit Internet Explorer and proceed to Section 3, Process Portal Software.

Network Settings
The following network settings should be applied to Process Portal systems with
multiple networks. This is not needed for a single or redundant network system.

NIC Installation Order


NIC installation order effects how WINS name resolution returns a list of addresses.
The most recently installed NIC has its IP listed first. If WINS is being used, it is
recommended that the installation order of NICs be kept consistent across all
Process Portal nodes.

WBPEEUI220793D0 47
Network Settings Section 2 Third Party Software

The NIC to be used for Process Portal should be installed last. Installation order of
cards can be verified by running the following diagnostic at the command prompt:
Nbtstat -c
The first card listed is the most recently installed (this should be the NIC on which
Process Portal communications will run).

Binding Order
Binding order is critical to the correct function of Process Portal. DCOM
communication only works properly when run on the first card in the binding order.
For this reason the first NIC in the binding order must be the card on which Process
Portal will communicate.
Binding order can be modified via the Adapters and Bindings tab of the Advanced
Settings dialog (available from the Advanced menu option in Network and Dial-up
Connections).

48 WBPEEUI220793D0
Section 3 Process Portal Software

Introduction
This section provides information on how to install the Process Portal software
services on a new node. If upgrading from a prior version, refer to Section 5, Adding
Process Portal Options for more information. Before beginning the installation,
ensure that the following requirements are met:
Verify that Section 2, Third Party Software has been successfully completed
before executing the steps in this section.
It is possible to halt the installation process between steps, but do not halt the
installation process part way through a step.
Unless otherwise instructed, restart the node when prompted to do so.
The installation of Process Portal software on primary or redundant domain
controllers is not supported.
Disable any nonessential applications before upgrading to Process Portal
software.
Only those third party products specifically mentioned in this instruction have
been validated to operate with Process Portal. When any other third party
applications are installed, they must be tested and validated to ensure that no
undesired effects are exhibited in the system.

Install Process Portal


To install Process Portal software:
1. Insert the Process Portal CD into the drive.
2. Use Windows Explorer to locate setup.exe in the following directory:
\ABB\Process Portal

WBPEEUI220793D0 49
Client Setup Type Section 3 Process Portal Software

3. Double-click setup.exe to begin installation.


4. Click Next in the welcome window.
5. Click Yes to accept the licensing agreement.
6. Select the directory that will contain the installation files from the browse list
in the Choose Destination Location window and click Next.
7. Select the setup type option (Figure 6) and click Next.

TC05932A

Figure 6. Setup Type

8. Go to the section that corresponds to the setup type option that was chosen:
Client Setup Type on page 50.
Server Setup Type on page 51.
Standalone Setup Type on page 53.
Independent Setup Type on page 54.

Client Setup Type


1. Select the Electronic Documentation checkbox to install all Process Portal
instructions if so desired and click Next. For nodes requiring access to product
instruction information. Refer to Section 8, Electronic Documentation.

50 WBPEEUI220793D0
Section 3 Process Portal Software Server Setup Type

2. Enter the name and password of the Process Portal services account and click
Next.
3. Enter the name of the Configuration server node and name of the Configuration
server database and click Next.
4. Continue to Electronic Documentation on page 57.

Server Setup Type


1. Make one of four selections from following options and select Next (Figure 7):
No checkboxes selected (as shown in Figure 7).
Historical Data Server.
Configuration Server.
Both checkboxes selected.

TC03425B

Figure 7. Process Portal Server Selection

2. Select the Electronic Documentation checkbox to install all Process Portal


instructions if so desired and click Next. For nodes requiring access to product
instruction information. Refer to Section 8, Electronic Documentation.
3. Select the Process Portal Network Interface to use for Time Synchronization.
This is only shown on systems with multiple NICs.

WBPEEUI220793D0 51
Server Setup Type Section 3 Process Portal Software

4. Enter the name and password of the Process Portal services account and click
Next.
5. Enter the Configuration server and optional database name when prompted.

No Checkboxes
If no checkboxes were selected in Step 1, continue to Electronic Documentation on
page 57; otherwise, continue to Historical Data Server Checkbox.

Historical Data Server Checkbox


If only the Historical Data Server checkbox was selected in Step 1, complete the
following, otherwise, continue to Configuration Server Checkbox:
1. Enter the host name of the Historian server and click Next.
2. Select the disk partition that will contain the SQL server database and click
Next.
The disk partition should be dedicated solely to the historian. Poor performance
may result if the partition is shared with other software. Historian_1 is the default
name of the database in which historian data is collected. The size requirements
of this database are based on many factors. The default size of one gigabyte is
adequate for less than 2,000 slowly changing points for one week and no events.
10 gigabytes is adequate for 5,000 points that change every 15 seconds and a
moderate event rate. A file (Disk Space.xls) is provided on the Process Portal CD
disk that calculates how much memory is required for historical data.

3. Enter the name (Historian_1) and size of the historian database in the Historian
SQL Data Parameters window and click Next.
If the default name of Historian_1 is changed, the default preconfigured historian
objects associated with the database will not work correctly.

4. Continue to Electronic Documentation on page 57.

52 WBPEEUI220793D0
Section 3 Process Portal Software Standalone Setup Type

Configuration Server Checkbox


If only the Configuration Server checkbox was selected in Step 1, complete the
following, otherwise, continue to Both Checkboxes selected:
1. Select the disk partition that will contain the SQL server database and click
Next.
2. Continue to Electronic Documentation on page 57.

Both Checkboxes selected


If both checkboxes were selected in Step 1, complete the following:
1. Enter the host name of the Historian server and click Next.
2. Select the disk partition that will contain the SQL server database and click
Next.
The disk partition should be dedicated solely to the historian. Poor performance
may result if the partition is shared with other software. Historian_1 is the default
name of the database in which historian data is collected. The size requirements
of this database are based on many factors. The default size of one gigabyte is
adequate for less than 2,000 slowly changing points for one week and no events.
10 gigabytes is adequate for 5,000 points that change every 15 seconds and a
moderate event rate. A file (Disk Space.xls) is provided on the Process Portal CD
disk that calculates how much memory is required for historical data.

3. Enter the name (Historian_1) and size of the historian database in the Historian
SQL Data Parameters window and click Next.
If the default name of Historian_1 is changed, the default preconfigured historian
objects associated with the database will not work correctly.

4. Continue to Electronic Documentation on page 57.

Standalone Setup Type


1. Select the Electronic Documentation checkbox to install all Process Portal
instructions if so desired and click Next.

WBPEEUI220793D0 53
Independent Setup Type Section 3 Process Portal Software

2. Enter the name and password of the Process Portal services account and click
Next.
3. Select the disk partition that will contain the SQL server database and click
Next.
The disk partition should be dedicated solely to the historian. Poor performance
may result if the partition is shared with other software. Historian_1 is the default
name of the database in which historian data is collected. The size requirements
of this database are based on many factors. The default size of one gigabyte is
adequate for less than 2,000 slowly changing points for one week and no events.
10 gigabytes is adequate for 5,000 points that change every 15 seconds and a
moderate event rate. A file (Disk Space.xls) is provided on the Process Portal CD
disk that calculates how much memory is required for historical data.

4. Enter the name (Historian_1) and size of the historian database in the Historian
SQL Data Parameters window and click Next.
If the default name of Historian_1 is changed, the default preconfigured historian
objects associated with the database will not work correctly.

5. Continue to Electronic Documentation on page 57.

Independent Setup Type


1. Make one of two selections from following options and select Next (Figure 8):
Client.
Server.

Client
1. Select the Electronic Documentation checkbox to install all Process Portal
instructions if so desired and click Next.
2. Enter the name and password of the Process Portal services account and click
Next.
3. Enter the Configuration server and optional database name when prompted.

54 WBPEEUI220793D0
Section 3 Process Portal Software Independent Setup Type

TC05933A

Figure 8. Client/Server Selection

Server
1. Select the Electronic Documentation checkbox to install all Process Portal
instructions if so desired and click Next.
2. Select the Process Portal Network Interface to use for Time Synchronization.
This is only shown on systems with multiple NICs.
3. Enter the name and password of the Process Portal services account and click
Next.
4. Enter the Configuration server database name.

WBPEEUI220793D0 55
Publishing and Distribution Setup Section 3 Process Portal Software

5. Select the disk partition that will contain the SQL server database and click
Next.
The disk partition should be dedicated solely to the historian. Poor performance
may result if the partition is shared with other software. Historian_1 is the default
name of the database in which historian data is collected. The size requirements
of this database are based on many factors. The default size of one gigabyte is
adequate for less than 2,000 slowly changing points for one week and no events.
10 gigabytes is adequate for 5,000 points that change every 15 seconds and a
moderate event rate. A file (Disk Space.xls) is provided on the Process Portal CD
disk that calculates how much memory is required for historical data.

6. Enter the name (Historian_1) and size of the historian database in the Historian
SQL Data Parameters window and click Next.
If the default name of Historian_1 is changed, the default preconfigured historian
objects associated with the database will not work correctly.

7. Continue to Electronic Documentation on page 57.

Publishing and Distribution Setup


1. Click Next in the Configure Publishing and Distribution Wizard window.
2. Select Make... in the Select Distributor window (Figure 9) and click Next.
3. Select a snapshop folder, the default is suggested, and click Next.
4. Select Yes when the warning message appears.
5. Select No, Use The Following Default Settings when prompted to customize
the publishing and distribution settings in the use Default Configuration
window and click Next.
6. Click Finish.
7. Click OK when prompted that this node has been enabled as a distributor.

56 WBPEEUI220793D0
Section 3 Process Portal Software Electronic Documentation

TC03428B

Figure 9. Distributor Selection

Electronic Documentation
If electronic documentation was selected to be installed, proceed with this section. If
electronic documentation was not selected to be installed, proceed to SQL Database
Maintenance on page 58.
1. Click Next in the Process Portal Documentation Setup Program window.
2. The electronic documentation installation program searches for an existing
copy of Adobe Acrobat Reader with Search. If found, proceed to Step 4. If
not found, Acrobat Reader installation begins.
Acrobat Search is needed for proper operation of ABB electronic documentation.
If Acrobat Reader exists but does not include the search plug-in, Acrobat Reader
installation will proceed.

3. Click Yes in the Software License Agreement window.


4. Use the default destination or select a new one for the Acrobat Reader software
and click Next.
5. Click Yes if prompted that the directory does not exist and requested that it be
created.
6. Click OK.

WBPEEUI220793D0 57
SQL Database Maintenance Section 3 Process Portal Software

SQL Database Maintenance


The following steps will only appear for Configuration Server and Historian
Server installations. Continue to Complete Installation on page 60 for all other
installations.

1. Click Next in the Database Maintenance Plan Wizard window.


If a previous maintenance plan exists, configure this maintenance plan to
minimize the redundant saving of data.

2. Select the name of the Historian_Master, Historian_1, and ConfigServer


databases if they are going to be part of the maintenance plan and click Next.
3. Enable Update Statistics Used By Query Optimizer.
4. Set the Database % field to 100.
5. Click Next in the Update Data Optimization Information window.
6. Verify Check Database Integrity, Include Indexes, and Perform These Tests
Before Doing Backups are enabled in the Database Integrity Check window
(Figure 10).

TC02513A

Figure 10. Database Integrity Tests

58 WBPEEUI220793D0
Section 3 Process Portal Software SQL Database Maintenance

7. Verify Attempt To Repair Any Minor Problems is disabled and click Next.
8. Verify Back Up The Database As Part Of The Maintenance Plan and Verify
The Integrity Of The Backup When Complete are enabled in the Specify the
Database Backup Plan window.
9. Select the backup media (hard disk is recommended) and click Change. This
must be a disk drive with sufficient space to contain the backed up material.
10. Select the frequency at which backups are automatically performed in the Edit
Recurring Job Schedule window and click OK.
A weekly frequency might be appropriate for a configuration server node on
which few configuration changes take place but daily might be justified if many
configuration changes are being made. A weekly frequency might be appropriate
for redundant historian nodes or when data is not critical but daily is
recommended for nonredundant historians. Backups should be scheduled for low
load time periods because they do effect performance.

11. Click Next.


12. Verify Use The Default Backup Directory is enabled in the Specify Backup
Disk Directory window.
13. Verify Create A Subdirectory For Each Database is enabled.
14. Verify Remove Files Older Than... is enabled, specify a time period, and click
Next.
Old files can be manually deleted. Either way, it is important to do this step so the
hard disk does not become full.

15. Verify Back Up The Transaction Log As Part of Maintenance Plan is not
enabled and click Next.
16. Verify Write A Report To A Text File In Directory: is enabled and specify the
directory that will hold the report in the Reports to Generate window
(Figure 11).
17. Verify Delete Text Report Files Older Than is enabled, specify a time period,
and click Next.

WBPEEUI220793D0 59
Complete Installation Section 3 Process Portal Software

TC02515B

Figure 11. Report Storage Configuration

18. In the maintenance plan history window, select to write the history to the
msdb.dbo.sysdbmaintplan_history table on this server.
19. Set a limit to the number of rows that each history table can hold, if necessary.
20. Click Next.
21. Enter a maintenance plan name and click Finish.
22. Click OK when prompted that the maintenance plan has been successfully
installed.

Complete Installation
1. Click No if prompted to restart the node.
2. Click Finish.

Install Process Portal Connect Products


Install any Process Portal Connect products that may be required. Refer to the
appropriate installation and configuration instruction manuals for each Connect
product to determine the correct node and server requirements.

60 WBPEEUI220793D0
Section 3 Process Portal Software Install Process Portal Licenses

Install Process Portal Licenses


Enter the Process Portal licenses received from ABB. Refer to Section 7, Software
License Entry for more detailed information.

Predefined Object Configuration Wizard


Run the Object Configuration Wizard on Standalone and Configuration Server
nodes to create basic system objects (System Definition, tags, etc.). Refer to
Section 18 of the Process Portal Configuration instruction for more detailed
information.

Automatic Startup and Verification of Process Portal


It is possible (but not required) to have the navigator part of Process Portal start up
automatically when an authorized user logs in.
Perform the following steps to automatically startup the Navigator:
1. Drag the Start > Programs > ABB Industrial IT > Operate IT Process
Portal > Base Product > Navigator item and place it over the top of Start >
Programs > Startup item.
2. Select Yes and then Create Shortcut.
3. Run gpedit.msc from the Start menu (Start > Run).
4. Expand User Configuration and then Administrative Templates.
5. Click Desktop.
6. Click Dont Save Settings At Exit Policy.
7. Verify the policy is enabled on the Policy tab of the Dont Save Settings At Exit
Policy Properties window and click OK.
8. Once all the Connect products have been installed, verify proper installation:
a. Restart the node.
b. Log in to Windows with the account name and password that the user
created at the beginning of the Process Portal installation.

WBPEEUI220793D0 61
Automatic Startup and Verification of Process Portal Section 3 Process Portal Software

c. Start Process Portal (Start > Programs > ABB Industrial IT > Operate
IT Process Portal > Base Product > Navigator).
d. Open the Configuration Browser and verify it contains data.
e. Open the Operation Browser and verify it contains data.
f. From the configuration server, open the SQL server enterprise manager
and verify that Publications or Publications for ConfigServer snapshots
are present.
g. Click the ABB logo. A list of installed or added components should be
displayed.
h. Open the Server Explorer.
i. Verify that all configured nodes and servers are present.

62 WBPEEUI220793D0
Section 4 Upgrading Process Portal
B1.1 and B1.2

Introduction
A user may upgrade the Process Portal system on a node by node basis without
requiring the entire system to be shutdown all at one time. Refer to the individual
connect products instruction since not all connected system support an online
upgrade.
The online upgrade process requires redundant servers and should be performed
first on the redundant backup servers and last on the primary active servers in
order to avoid interruption in process control.
Upgrades must not be performed while any changes are being implemented or
that may be required in the system.
The upgrade process should only be performed by trained personnel and as in any
controls software upgrade process, there are certain cases where an online
upgrade is not recommended.
These cases include any processes or environments where there are safety
concerns to operation personnel or risk of loss of production during the upgrade
process due to errors encountered during upgrade.
Avoid online upgrades if the system is in heavy demand and cannot be
interrupted, loss of operation to the process is unacceptable, or no manual backup
facilities exist.

It is possible to halt the installation process between steps, but do not halt the
installation process part way through a step.
Unless otherwise instructed, restart the node if prompted to do so.

WBPEEUI220793D0 63
Procedure Section 4 Upgrading Process Portal B1.1 and B1.2

Disable any nonessential applications before upgrading to Process Portal


software.
Online upgrades are supported from version B1.1 and B1.2 (any service pack)
to B2.0. All nodes in the system should be upgraded to the same software level
when upgrading. Nodes should be upgraded in the following order:
Configuration Server.
RTDS
Historian
Mirror Database Server
Client.
Once an online upgrade has begun, version 1.x nodes must not be restarted
until they have been upgraded.
When upgrading a system, all Connect products that were previously installed on
the system must be upgraded to the correct version for Process Portal B2.0. It is
not possible to upgrade and remove previously installed Connects at that time. If
you wish to remove a Connect, the system must be flatlined and reloaded.

Procedure
Upgrade a Process Portal B1.1 or B1.2 node to a Process Portal B2.0 node using the
following steps:
1. Request the software keys required by the new software. Refer to Section 7,
Software License Entry for more detailed information.
Do not proceed with the upgrade until new licenses are received. New licenses
are required to run the software.

2. If upgrading a configuration server, backup the configuration files but do not


migrate it until instructed. Refer to Section 9, Back Up and Restore for more
information.
3. Disable the following services using standard Windows methods:
EbServerBroker.
EbDataSyncService.
ABBDiagnosticService.
SoapSymTagAtomsrv.
4. Restart the node.

64 WBPEEUI220793D0
Section 4 Upgrading Process Portal B1.1 and B1.2 Procedure

5. Close all other applications (especially virus scanners, Windows task manager,
SQL server enterprise manager, etc.).
6. Delete all temporary Internet files for all user accounts using standard
Windows methods.
7. Ensure that the correct software is installed before performing the upgrade
procedure. Refer to Section 2, Third Party Software for more information.
8. Execute the setup.exe file located in the \ABB\Process Portal directory.
9. Click Next in the welcome window.
10. Click Yes to accept the licensing agreement.
11. In the Setup Type window, select Previous Installation Options (and proceed to
Step 23) or New Installation Options (and proceed to the next step).
A dialog window may open stating that there is a file that is locked. Out of the
four options, select Retry and continue with the upgrade installation.

12. If new installation options are being used, select the product to be installed in
the Setup Type window and click Next.
13. Install the Electronic Documentation if desired and follow through the
prompts.
14. If new installation options are being used, select the types of servers to be
installed in the Setup Type window and click Next.
15. Create a service account by entering a name and password.
16. If a configuration server is being installed, select the appropriate answer when
prompted to backup configuration databases, models, and graphics before
continuing. If necessary, abort the installation, backup the database, and save
the desired graphics and submodels and start just the Process Portal part of the
installation. Refer to Section 9, Back Up and Restore for more detailed
information.
If doing an online upgrade, do not initialize the Configuration Server database
when prompted. Doing so may result in blank databases being replicated to the
running nodes and system failure.

WBPEEUI220793D0 65
Procedure Section 4 Upgrading Process Portal B1.1 and B1.2

a. When asked to skip the Initialize of the Configuration Server database,


select Yes if performing an online upgrade. If planning to migrate a prior
database, select No. The installation will now copy files to disk and
upgrade the database.
b. Perform the steps from the initial installation procedure that pertain to the
options being installed (refer to Section 5, Adding Process Portal Options
for more information).
17. If a historian server is present on the node, choose if and when to upgrade the
historian database in the Setup Type window (refer to Section 5, Adding
Process Portal Options). If the upgrade now option was enabled, proceed to the
next step. If the upgrade later option was enabled, proceed to Step 19. When
ready to upgrade choose Programs > ABB Industrial IT > Process Portal >
Historian > Upgrade Manager from the Windows 2000 Start menu.
Resetting the historian databases deletes the databases and requests a name and
size for the Historian_1 database. Proceed to Step 19 if the node does not
contain a historian server.
The historian server database must be either reset or upgraded before the version
of the historian will startup.

18. Select any historian database (Historian_1) in the Available Database field and
click Upgrade in the Historian Upgrade window (refer to Section 5, Adding
Process Portal Options).
19. If a configuration server is being installed on this node, proceed to the next
step. Otherwise, proceed to Step 20.
20. If a maintenance plan already exists on the node, enter N unless there is a need
to create a new one.
If any database names have changed, the maintenance plan should be updated.

21. If no maintenance plan exists and configuration server or historian server


software resides on the node, choose to create a new plan (click Next) or not to

66 WBPEEUI220793D0
Section 4 Upgrading Process Portal B1.1 and B1.2 Procedure

have a plan at all (click Cancel) in the Maintenance Plan Wizard welcome
window.
It is required to have a maintenance plan for optimal performance on the
configuration server.

22. If editing or creating a new maintenance plan, perform SQL Database


Maintenance on page 58 to set up maintenance plans and continue with the
next step. For users installing new options, go to Step 26.
23. Enter the local IIT user name and password in the Services Security Setup
window and click Next.
a. Enter the local IIT user name.
b. Enter the local IIT user group name and click Next.
24. Click Yes when prompted to ensure that the ConfigServer, graphics, and
models have been backed up.
a. Select OK to uninstall the previous version of the Central Licensing
System.
If doing an online upgrade, do not initialize the Configuration Server database
when prompted. Doing so may result in blank databases being replicated to the
running nodes and system failure.

b. When asked to skip the Initialize of the Configuration Server database,


select Yes if performing an online upgrade. If planning to migrate a prior
database, select No. The installation will now copy files to disk and
upgrade the database.
c. Complete the Electronic Documentation setup (refer to Electronic
Documentation on page 57 for more information).
d. Create or modify the database maintenance plan if needed. Refer to SQL
Database Maintenance on page 58 for more information.
25. Click Next in the window that displays the information for add-on products.
26. If the install asks to reboot, select No and select Finish, otherwise, select
Finish.
27. Install any required Connect products.

WBPEEUI220793D0 67
Restarting Upgraded Nodes Section 4 Upgrading Process Portal B1.1 and B1.2

28. If the Configuration database has been initialized, migrate the configuration
database by selecting Start > Programs > ABB Industrial IT > Process
Portal > Configuration > Configuration Upgrade Wizard and completing
the remaining steps of the restore procedure. Refer to Section 9, Back Up and
Restore for more detailed information.
The Process Portal account should be used when migrating a database.

29. Restart the node.


30. Use the SQL server enterprise manager to verify the snapshot
(configserver_name > Replication Monitor > Agents > Snapshot Agents)
has finished.

Restarting Upgraded Nodes


Restart the upgraded nodes in the following order:
Configuration server.
Historian server.
RTDS server.
Mirror Database server.
Client.

68 WBPEEUI220793D0
Section 5 Adding Process Portal Options

Introduction
Adding options to Process Portal software contained in any node after the initial
installation only requires executing the Process Portal segment of this installation
again with the new options selected.
1. It is possible to halt the installation process between steps, but do not halt the
installation process part way through a step.
2. Unless otherwise instructed, restart the node when prompted to do so.

To add options to an existing Process Portal installation:


1. Make a backup copy or locate a recent one of the configuration database (if
adding options to a configuration server node). Refer to Section 9, Back Up
and Restore for more detailed information.
2. Disable the following services using standard Windows methods:
EbServerBroker.
EbDataSyncService.
ABBDiagnosticService.
ABB Client License Provider.
SoapSymTagAtomsrv.
3. Restart the node.
4. Close all other applications (especially virus scanners, Windows task manager,
SQL server enterprise manager, etc.) on all nodes.
5. Double-click the setup.exe file located in the \ABB\Process Portal
directory.
6. Click Next in the Welcome window.

WBPEEUI220793D0 69
Introduction Section 5 Adding Process Portal Options

7. Click Yes to accept the licensing agreement.


8. Enter the name and password of the Process Portal service account and click
Next.
Do not deselect any default selection.

9. Verify New Installation Options is enabled in the Setup Type window


(Figure 12).

TC02720B

Figure 12. Installation Options Dialog Box

10. Select the additional products to be installed in the Setup Type window and
click Next.
11. Select the types of additional servers to be installed in the Setup Type window
and click Next.
12. Perform the steps from the initial installation procedure that pertain to the
options being added (refer to Section 3, Process Portal Software).
When following the initial installation steps as indicated in Section 3, Process
Portal Software, depending upon the components previously installed and those
being added, additional steps may be encountered.

70 WBPEEUI220793D0
Section 5 Adding Process Portal Options Introduction

13. If a historian server is present on the node, choose if and when to upgrade the
historian database in the Setup Type window (Figure 13). If the upgrade now
option was enabled, proceed to the next step. If the upgrade later option was
enabled, proceed to Step 20. When ready to upgrade choose Programs > ABB
Industrial IT > Process Portal > Historian > Upgrade Manager. Resetting
the historian databases deletes the databases and requests a name and size for
the Historian_1 database. Proceed to Step 20.
The historian server database must be either reset or upgraded before the
historian will function correctly.

14. Select Historian_1 in the Available Database field and click Upgrade in the
Historian Upgrade window (Figure 14).
15. Click OK when prompted that the upgrade may take a while to complete.
16. Click Done.
17. If a configuration server is being installed on this node, proceed to the next
step. Otherwise, proceed to Step 20.

TC02721A

Figure 13. Historian Upgrade Option Dialog Box

18. Enter the Process Portal services account name and password when prompted
by the COM+ application and click Continue.

WBPEEUI220793D0 71
Introduction Section 5 Adding Process Portal Options

TC02722A

Figure 14. Historian Upgrade Dialog Box

19. Click Continue in the Install Security Roles window.


20. If a maintenance plan already exists on the node, choose to accept or edit the
plan.
21. If no maintenance plan exists and configuration server or historian server
software resides on the node, choose to create a new plan (click Next) of not to
have a plan at all (click Cancel) in the Maintenance Plan Wizard welcome
window.
22. If editing or creating a new maintenance plan, go to and perform SQL Database
Maintenance on page 58.
23. Click Finish in the InstallShield Wizard Complete window.
24. If a configuration server was added, reinstall all previously installed Connect
options.
25. Enter the new license keys for the new options. Refer to Section 7, Software
License Entry for more detailed information.

72 WBPEEUI220793D0
Section 6 Reinstalling Process Portal

Introduction
Reinstalling Process Portal software only requires executing the Process Portal
segment of this installation.

1. It is possible to halt the installation process between steps, but do not halt the
installation process part way through a step.
2. Unless otherwise instructed, restart the node when prompted to do so.

To reinstall Process Portal software:


1. Make a backup copy or locate a recent one of the configuration database (if
reinstalling software to a configuration server node). Refer to Section 9, Back
Up and Restore for more detailed information.
2. Disable the following services (Control Panel > Administrative Tools >
Services):
EbServerBroker.
EbDataSyncService.
ABBDiagnosticService.
ABB Client License Provider.
SoapSymTagAtomsrv.
3. Restart the node.
4. Close all other applications (especially virus scanners, Windows task manager,
SQL server enterprise manager, etc.) on all nodes.
5. Double-click the setup.exe file located in the \ABB\Process Portal
directory.
6. Click Next in the Welcome window.

WBPEEUI220793D0 73
Introduction Section 6 Reinstalling Process Portal

7. Click Yes to accept the licensing agreement.


8. Enter the name and password of the Process Portal service account and click
Next.
9. Enter the name of the IIT User Group and click Next.
10. Enable Previous Installation Options in the Setup Type window (Figure 6).
11. If a configuration server is present on this node, choose if the configuration
server database should be initialized. If the database is initialized, proceed to
Step 16. Proceed to the next step to continue upgrading the database.
Initializing the database will delete the database requiring a backup copy of the
database be restored and migrated into the node.

12. If a historian server is present on the node, choose if and when to upgrade the
historian database in the Setup Type window (Figure 6). If the upgrade now
option was enabled, proceed to the next step. If the upgrade later option was
enabled, proceed to Step 21. When ready to upgrade choose Programs > ABB
Industrial IT > Process Portal > Historian > Upgrade Manager. Resetting
the historian databases deletes the databases and requests a name and size for
the Historian_1 database. The historian server must be reset or upgraded before
the historian will function correctly. Proceed to Step 21.
13. Select Historian_1 in the Available Database field and click Upgrade in the
Historian Upgrade window.
14. Click OK when prompted that the upgrade may take a while to complete.
15. Click Done.
16. If a maintenance plan already exists on the node, choose to accept or edit the
plan.
17. If no maintenance plan exists and configuration server or historian server
software resides on the node, choose to create a new plan (click Next) of not to
have a plan at all (click Cancel) in the Maintenance Plan Wizard welcome
window.
18. If editing or creating a new maintenance plan, perform the steps from the initial
installation procedure that pertain to the setting up of maintenance plans.
19. Click Finish in the InstallShield Wizard Complete window.

74 WBPEEUI220793D0
Section 6 Reinstalling Process Portal Introduction

20. If a configuration server was added, reinstall all previously installed Connect
products.
21. Perform the remaining steps from the initial installation procedure and
continue. Refer to Section 4, Upgrading Process Portal B1.1 and B1.2.

WBPEEUI220793D0 75
Introduction Section 6 Reinstalling Process Portal

76 WBPEEUI220793D0
Section 7 Software License Entry

Introduction
This section provides information for the proper operation of the ABB software
products and features that require licenses. Software is licensed by relating a
software key for each software feature with a unique machine ID. Software keys are
obtained from the ABB software license administration system. Follow all steps for
obtaining machine IDs, requesting software keys, installing software keys, and
installing and running the license entry program.
For the software to run, the machine ID used to generate the software key must be
present on the configuration server node. The machine ID identifies the node where
the ABB software licensing is handled, and the software periodically checks that the
machine ID is still present. A single machine ID supports multiple software keys for
different features and for different applications.
There are two types of machine IDs that the ABB licensing program supports: a
removable hardware key or a fixed Ethernet address of an Ethernet card. Each type
has its advantages and disadvantages. Using the Ethernet address as a machine ID is
generally more convenient. However, if the Ethernet card that was chosen is ever
replaced or permanently removed from the node, the software license will have to be
reapplied for. Refer to Obtaining Ethernet Address on page 78 if this is the type of
machine ID that is to be used.
The Rainbow SentinelSuperPro hardware key or dongle is a copy protection
device that attaches to the parallel port or USB port of the computer. Some
advantages of a dongle are:
Moving it from configuration server node to configuration server node.
However, the software licensed to the dongle can only execute on the
configuration server node that currently has the dongle attached.

WBPEEUI220793D0 77
Obtaining Ethernet Address Section 7 Software License Entry

Other machine IDs may need to be replaced to upgrade the node software. New
software keys must then be requested. However, there is no need to replace the
dongle with another one (unless it breaks).
The dongle must be ordered from ABB, since ABB software can read only
dongles manufactured for ABB.
In most cases, ABB software licensing functions support multiple dongles which
are daisy chained together. The dongle for Process Portal can be anywhere in the
daisy chain.

Obtaining Ethernet Address


To obtain the Ethernet card address:
1. Enter ipconfig /all ENTER from the DOS command prompt. The
Ethernet address can be obtained by choosing any listed Ethernet adapter and
recording the physical address line item. For example:
00-60-08-CC-BB-B8
2. Record this machine ID (without the hyphens) on the ABB licensing
registration form and follow the instructions in Requesting Software Keys on
page 80 to request software licenses from ABB.

License Entry Program


The license entry program is used to activate the software features once the
necessary software keys have been installed.

Requirements
The license entry program must be installed and run on a node that has Process
Portal configuration server services installed.

78 WBPEEUI220793D0
Section 7 Software License Entry Install

Install
The license entry program is normally automatically installed with the software. To
update an earlier version of the license entry program, perform the standalone
installation steps that follow.
1. Insert the CD disk containing the software licensing program into the CD drive.
2. Run: <CD drive>:\license\setup.exe.
3. Follow the prompts to complete the license entry program installation.

Uninstall
This program uses the standard Microsoft uninstall steps:
Select the ABB License Entry program from the list and click Add/Remove.

Running the License Entry Program


After installation, the license entry program can be invoked by selecting Start >
Programs > ABB Industrial IT > ABB Licensing > License Entry.
Some software applications will automatically open the license software at the end
of their installation, or on the initial startup of the software product.

Selecting a Machine ID
1. Select the Available IDs tab of the license entry program (Figure 15).
2. Click Refresh to update the list of machine IDs. The choices for machine IDs
are:
Removable Rainbow SentinelSuperPro.
Physical Ethernet address.
3. Select a machine ID, then click Set Machine ID to make the selected machine
ID the default used in other tabs.

WBPEEUI220793D0 79
Requesting Software Keys Section 7 Software License Entry

TC03317A

Figure 15. Available IDs Tab

Requesting Software Keys


To request software keys:
1. Obtain the machine ID of the node that the software is installed on or going to
be installed on. Refer to Selecting a Machine ID on page 79 to obtain a
machine ID.
2. Locate and have available the license numbers found on the license certificate
form shipped with the software.
3. Complete the license key request form provided with the software. Follow the
instructions found on this form.
4. Otherwise, generate and complete a new request form using the license entry
program. To generate a software key request form:
a. Select the Licenses tab of the license entry program (Figure 16).
b. Select the applicable license group for the product or feature being
licensed.
c. Click Request SWKey.

80 WBPEEUI220793D0
Section 7 Software License Entry Entering Licenses

TC03318A

Figure 16. Licenses Tab

d. Verify that the machine ID is correct. If not, enter a new machine ID. Click
OK to continue.
e. Enter the registration number sent with the software and click OK.
f. Enter the validation number sent with the software and click OK.
g. Edit the form as necessary. Either save the form to a file or print the form.
5. Send the registration form to the ABB software license administrator using one
of the methods described on the registration form.
6. Wait for the software keys to be returned. The method by which the software
keys will be returned is selected on the registration form. The choices are
Internet mail, postal mail, or fax. A mail address or fax number must be
included on the form.

Entering Licenses
To install the software keys:
1. Run the license entry program by selecting Start > Programs > ABB
Industrial IT > ABB Licensing > License Entry.

WBPEEUI220793D0 81
File Installation Section 7 Software License Entry

2. Select the Licenses tab (Figure 16).


3. Select the applicable license group for the product or feature being licensed.
4. Each feature of the software requires a software key to function properly. If the
software key was received as an e-mail message, follow the instructions in File
Installation on page 82 to install it. If the software key is to be installed
manually, follow the instructions in Manual Installation on page 82.

File Installation
To install the software key from a file:
1. Save the e-mail message to a temporary file as a text file.
2. Click Add From File and select the temporary file saved in Step 1.
3. Click Open. The program reads the file and gives the number of licenses found
in the file.
4. Click Yes to proceed with the license installation. The steps prompt to verify
each license before it is installed.

Manual Installation
To manually install a software key:
1. Choose a feature and click Edit License. This opens the Edit License tab.
2. Enter the following license parameters:
Version.
Expiration date.
Licensed quantity.
Software key.
Option/user string.
The option string must be entered if it is provided. The option string is designated
as User String when the software key is sent. In addition, the option string must
be entered in the Option/User String field.

The license parameters can be found on the software keys form received from the
software license administration system. Verify that the parameters match the

82 WBPEEUI220793D0
Section 7 Software License Entry Manual Installation

machine ID shown. Figure 17 shows an example screen with the licensing


information entered.
3. Click Validate to verify that the information entered matches the software key.
Correct any errors found, including failing to enter the option string if it was
provided.
4. Click Save to save the entered license information.
Click Save after entering and validating the information for each feature of the
software. Clicking Validate will only validate the information that was entered,
not save it.

5. Choose another feature, then repeat Step 2 through Step 4.

TC03319A

Figure 17. Edit License Tab

WBPEEUI220793D0 83
Licensing Troubleshooting Section 7 Software License Entry

Licensing Troubleshooting
Licenses are kept in a license file for each license group. Basic troubleshooting steps
are to locate the license file and view its contents.
The most common problem occurs during software key installation if the license
parameter information is validated, but then is not saved. Refer to Entering
Licenses on page 81 to enter, validate, and save the license parameter
information.

Locating the License File


To locate the license file:
1. Select the Licenses tab of the license entry program.
2. Select the desired license group.
3. The expected license file name is displayed by clicking Details (Figure 16).
Use the Windows Explorer to check if the specified directory and file exist.

Unavailable Machine IDs


Sometimes an option is not listed as an available machine ID. The following
describes what to do:

Rainbow SentinelSuperPro Dongle


If the Rainbow SentinelSuperPro dongle is not listed as a machine ID option, verify
the following:
1. Verify that the dongle was supplied by ABB. ABB software can read only ABB
dongles.
2. Verify that the dongle is attached to the parallel port or USB port.
3. Press Refresh on the Available IDs tab to scan for newly inserted IDs.
Verify that the device driver needed to access the dongle is installed:
1. Select Start > Settings > Control Panel > Administrative Tools > Computer
Management > System Tools > System Information > Software
Environment > Drivers.

84 WBPEEUI220793D0
Section 7 Software License Entry Error Codes

2. Verify the Sentinel service is running.


The installation of the Sentinel driver requires logging in as a member of the
Windows administrator group. There are two methods of installing the driver from
the license entry program:
Method 1 - Run the license entry program and select File > Load SPRO driver
from the menu bar.
Method 2 - From a subdirectory of the license entry program directory, run
...\SPRO\Win_NT\setupx86.exe.
To verify whether the Sentinel driver is installed or not, select the Configure
Sentinel Driver function. A message will appear if the driver is not installed.

Ethernet Address
If the Ethernet address is not listed as a machine ID option:
Verify the TCP/IP protocol was properly configured during the installation of
the product being licensed.
Verify the Ethernet circuit card is functioning correctly.

Error Codes
Table 8 lists and describes license software error messages.

Table 8. Licensing Error Codes, Messages, and Descriptions

Code Message Description/Action


0 Success
-1 Cannot find license Determine the expected location of the license file. Verify
file the file does not exist. Install the product.
-2 License file corrupted Delete the license file, then reinstall the product.
-3 No machine IDs None of the valid machine IDs could be found. Purchase
found any of the valid machine ID types, or install the software
on a machine with a valid machine ID type.

WBPEEUI220793D0 85
Error Codes Section 7 Software License Entry

Table 8. Licensing Error Codes, Messages, and Descriptions (Continued)

Code Message Description/Action


-4 Maximum number of Purchase additional licenses.
users reached
-5 No such feature Occurs when checking out a feature that has not been
exists licensed.
-6 No licenses checked Not an error. This message may occur if the software
out attempts to check in a license when it has not checked out
a license yet.
-7 Format of feature line Indicates an invalid license has been found in the license
is invalid file. This may be due to a program other than the license
entry program being used to edit the license file.
Delete the license for the feature, using the license entry
program Licenses tab. Then add the feature.
-8 Bad encryption code Indicates an invalid license has been found in the license
file.
Reenter the software key.
-9 Feature found but A license for the feature was found, but not for this node.
machine ID mismatch Get a license for this computer. Use the license entry
program (Available IDs tab) to view the machine IDs found
on this node.
-10 Feature found but A license for the feature was found, but for a different
wrong version version of the software. Obtain a license for this version of
the product.
-11 Feature found but A license for the feature was found, but for a different
wrong option string option string of the software. Obtain a license for this
option string of the product. Not all products utilize an
option string.
-12 Software expired The license for the feature was a temporary license, which
has since expired. Ensure the date on your node is
correct, or obtain a current license.
-13 Bad date The license entered had an invalid date.

86 WBPEEUI220793D0
Section 7 Software License Entry Error Codes

Table 8. Licensing Error Codes, Messages, and Descriptions (Continued)

Code Message Description/Action


-14 Duplicate license When adding a new license, an existing license for the
entry same feature, version, number of users and machine ID
was found.
-15 Software key does Occurs with an invalid license entry. The software key
not match entered does not match the features, version, etc. Check
parameters all fields in the license; one or more parameters must be
incorrect.
-16 License entry not When the license entry program deleted a license, the
found specified feature was not found.
-17 Cannot write to Determine the expected location of the license file. Verify
license file the file does not exist or is not read-only. Install the
product.
-18 Too many licenses A program requested more licenses than were available.
requested This error indicates that licenses for the desired feature
are available, but not in the quantity requested. Request
fewer licenses, if possible, or obtain more licenses.
-19 Cannot read license Determine the expected location of the license file. Verify
file the file does not exist or is not read-only. Install the
product.
-20 Start date for feature
not reached
-21 Machine ID not found A license was found, but for a machine ID that is not
present in this node. Get a license for this node. Use the
license entry program (Available IDs tab) to view the
machine IDs found on this node.
-22 Machine ID type not A request for a specific machine ID type was made, but
found that machine ID type could not be found on this node.
-23 Machine ID Type not
supported

WBPEEUI220793D0 87
License Assignment Editor Section 7 Software License Entry

Table 8. Licensing Error Codes, Messages, and Descriptions (Continued)

Code Message Description/Action


-24 Could not read Check the Ethernet card.
machine Ethernet
address
-25 Could not open
network device
-28 Error in registry for Ensure the user has administrator privileges on the
license file computer.
Reinstall the product.
-29 Error in registry for
machine ID

License Assignment Editor


Process Portal utilizes a central licensing mechanism. The configuration server
contains the central licensing service which dynamically distributes the available
licenses as they are needed by to all the nodes in the Process Portal system.
However, the license assignment editor utility allows licenses to be permanently
assigned to a particular node.

Assign Licenses
To assign a license to a particular node:
1. Select Start > Programs > ABB Industrial IT > ABB Licensing > License
Assignment Editor on the configuration server.
2. Enter the name of the node in the Select a Node or Application field. Use the
browse button if desired. Refer to Figure 18.
3. Click Add. The node name will appear in the Assigned Features field.
4. Select the node name in the Assigned Features field.
5. Select the type of license to be assigned in the Available Licenses field.
6. Enter the number of licenses (of the type selected) that will be assigned to the
node in the Number field.

88 WBPEEUI220793D0
Section 7 Software License Entry License Diagnostics

7. Click Assign.
8. Click Save. This will cause the licenses to be allocated as specified.
If necessary, licenses will be removed from existing nodes to meet the specified
license allocation.

9. Repeat these steps as required.

License Diagnostics
To display a complete listing of all the nodes in the project (and all the available
information about each node), click Diagnostics. Refer to Figure 19.
To create a copy (XML format) of this information:
1. Click Export.
2. Select the destination directory. The file name is
LicenseEditorDiagnostics.xml.
3. Click OK.

WBPEEUI220793D0 89
License Diagnostics Section 7 Software License Entry

TC03527A

Figure 18. License Assignment Editor

90 WBPEEUI220793D0
Section 7 Software License Entry License Diagnostics

TC03528A

Figure 19. Diagnostic System Information

WBPEEUI220793D0 91
License Diagnostics Section 7 Software License Entry

92 WBPEEUI220793D0
Section 8 Electronic Documentation

Introduction
A complete set of Process Portal instructions is included on the installation CD disk
in electronic form. All instructions are in portable document format (PDF) viewable
with an Adobe Acrobat viewer (3.0 and later). Acrobat Reader Version 5.0 with
Search is provided for viewing the electronic documentation.

Navigation
Bookmarks and links are two ways of quickly moving around documents.

Bookmarks
Navigation bookmarks are used to quickly go to a heading, figure, or table within a
section. Bookmarks are enabled in all instruction sections.
The bookmark list appears at the left side of the viewer window. Click a bookmark
to go to that topic. Click the + sign next to a bookmark to expand the bookmark list
and view sublevel headings.
All figures in a section are listed under the Figures bookmark. All tables are listed
under the Tables bookmark. Click the + sign to view the list of figures or tables.

Links
Red or light blue text in any section of an instruction identifies a link to a section,
heading, figure, or table. Click any red or light blue text to activate a go-to link.

Acrobat Search
The Acrobat viewer installed by running the electronic documentation setup
procedure provides a full-text search capability. Use Acrobat Search to quickly

WBPEEUI220793D0 93
Search Options Section 8 Electronic Documentation

locate information contained in electronic documents. Documents can be searched


by single term, phrase, and document information fields.
Each document has a search index associated with it that is automatically enabled
when the instruction is called up in the viewer. Multiple search indexes can be
enabled. Optionally, search indexes can be manually enabled. Search indexes have
a .pdx file extension and are located in the individual instruction directories under
the \document directory.
To search a single instruction, call up that instruction. This will automatically enable
the search index for that particular instruction. To search multiple instructions, call
up each instruction to be searched.
Refer to the Acrobat Search help for the steps to set up the search engine, for
information about how to perform and refine searches, and for the procedures to
manually select search indexes.

Search Options
All search options such as word stemming, sounds like, and thesaurus are enabled
for the electronic documents. These options, when selected, can help refine a search.
All instruction sections have title, subject, and keyword document information
fields defined. A search can be performed on any of these fields.
Refer to the Acrobat Search help for an explanation of using these options and
search fields.

94 WBPEEUI220793D0
Section 9 Back Up and Restore

Introduction
This section provides information on how to back up and restore system data for the
purpose of an upgrade. These databases should be part of the maintenance plan and
scheduled to be backed up automatically at a convenient time interval, but it can be
manually backed up. This data should be saved to avoid loss of data due to node
problems and to be able to use the same data after a software upgrade.

Backup Procedures
Configuration server nodes contain all the Process Portal system configuration data
and backing them up will preserve the data. Historian server nodes must also be
backed up to prevent the loss of collected data that has not yet been saved. The
databases can be backed up while the node is offline or online (with the following
restrictions):

Restrictions
Do not use the Create Database or Alter Database statements during backup
operations.
Do not create indexes during backup operations.
Do not perform any nonlogged operations (bulk loading of data, Select...Into
statement, Writetext statement, Updatetext statement, etc.) during backup
operations.
Adhere to standard SQL server naming conventions when naming databases.

WBPEEUI220793D0 95
Backup Procedures Section 9 Back Up and Restore

Configuration Data
The SQL server configuration database contains all the configuration data. In
addition to the configuration database, other files must also be saved in order to have
a complete set of information. To completely back up the configuration data of a
configuration server manually:
1. Open the SQL server enterprise manager.
2. Expand the SQL server group that represents the configuration server node
(Figure 20).

TC3687A

Figure 20. SQL Server Enterprise Manager Folders

3. Expand the Databases folder.

96 WBPEEUI220793D0
Section 9 Back Up and Restore Backup Procedures

4. Right click the ConfigServer database.


5. Select All Tasks > Backup Database... from the pop-up menu.
6. Select ConfigServer in the Database field of the General tab (Figure 21).

TC02706B

Figure 21. Backup Dialog Box - General Tab

7. Enable Database - complete as the Backup type.


8. Specify a destination from the list to receive the backup information. If
necessary, configure a new destination using the following steps:
a. Click Add.
b. Select the file name or backup device to receive the backup information in
the Select Backup Destination window.
c. Click OK.
9. Enable Verify backup upon completion on the Options tab.

WBPEEUI220793D0 97
Restore Procedures Section 9 Back Up and Restore

10. Complete any other section of the general and options tabs deemed necessary.
11. Click OK.
12. Repeat Step 4 through Step 11 for the Historian_Master, Archive_Master, and
Historian_1 databases.
Check that sufficient space is available to back up the Historian_1 database, it
may be very large. The backup is needed only to recover any Historical data that
has not been archived.

13. After the backup operation completes, save the contents of the following
\Program Files\ABB Industrial IT subdirectories to a safe storage media that
will not be affected by node hardware failures:
\Operate IT\Base\Reports\Templates.
\Conductor\lib\models\graphics.
\Conductor\lib\models\submodels.
\Conductor\lib\models\config\graphics.
\Conductor\lib\models\config\submodels.
\ABBWeb\default\Machine.
\ABBWeb\<language> Machine.
\ABBWeb\default\User.
\ABBWeb\<language>\User.
\ABBWeb\default\Project.
\ABBWeb\<language>\Project.
\ABBWeb\default\AddOns.
Refer to the specific backup procedures for any Connects installed to verify
additional files that must be stored.

Restore Procedures
These steps restore configuration and historian data. Skip the steps that do not
apply to this node.

To restore backed up information after an update:


1. Open the SQL server enterprise manager.
2. Expand the SQL server group that represents the configuration server node.

98 WBPEEUI220793D0
Section 9 Back Up and Restore Restore Procedures

3. Right click Databases (Figure 20).


4. Select New Database... from the pop-up menu.
5. Enter a new name for the database that will receive the stored configserver data
and click OK.
6. Right click the new database.
7. Select All Tasks... > Restore Database... from the pop-up menu.
8. Select ConfigServer in the Show Backups of Database field (Figure 22).

TC02708B

Figure 22. Restore Dialog Box - General Tab

9. Select the Restore... type. Enable Database when restoring from a backup of
this actual database. Enable From device when restoring from a backup file
unknown to this node.
10. If database restore was enabled, select the appropriate backup to restore from
and verify the restore from path is correct.
11. If From Device restore was enabled:
a. Choose Select Devices.
b. Click Add to define the device name.

WBPEEUI220793D0 99
Restore Procedures Section 9 Back Up and Restore

c. Click OK.
d. Verify Restore backup set and Database - complete is enabled.
e. On the options tab, verify the original file name field reflects the present
location of the backup information.
12. Enable Force restore over existing database and Leave database operational on
the Options tab (Figure 23) and click OK.
An Error dialog box may appear stating that the database is not published. If this
occurs, select OK and then Cancel in the Restore Database window.

TC02710A

Figure 23. Restore Dialog Box - Options Tab

13. Select Start > Program Files > ABB Industrial IT > Operate IT Process
Portal > Configuration > Configuration Upgrade Wizard.
14. Click Next in the Configuration Migration Wizard window.
15. Verify Upgrade from a previous Operate IT Configuration version is enabled
and click Next.
16. Specify that Both the source and destination databases are on the local
computer and click Next.

100 WBPEEUI220793D0
Section 9 Back Up and Restore Restore Procedures

17. Enter the names of the source and destination databases in the appropriate
fields of the Migrate Local window and click Next.
18. Click Finish. A message window will show the progress of the migration.
19. After the backup operation completes, save the contents of the following
\Program Files\ABB Industrial IT subdirectories to a safe storage media that
will not be affected by node hardware failures:
\Operate IT\Base\Reports\Templates.
\Conductor\lib\models\graphics.
\Conductor\lib\models\submodels.
\Conductor\lib\models\config\graphics.
\Conductor\lib\models\config\submodels.
\ABBWeb\default\Machine.
\ABBWeb\<language> Machine.
\ABBWeb\default\User.
\ABBWeb\<language>\User.
\ABBWeb\default\Project.
\ABBWeb\<language>\Project.
\ABBWeb\default\AddOns.
20. Restart the node.
21. Open the SQL server enterprise manager.
22. Expand the SQL server group as follows:
configserver_node_name > Replication Monitor > Agents > Snapshot
Agents
23. Verify the status of ConfigServer is Succeeded. Do not proceed until this
status is achieved.
24. Open the SQL server enterprise manager.
25. Verify no red icons (indicate problems or errors) are present.
The backed up configuration server information is now restored and migrated into
the Process Portal node.

WBPEEUI220793D0 101
Restore Procedures Section 9 Back Up and Restore

102 WBPEEUI220793D0
Appendix A Domain Controllers

Introduction
This section provides information on how to set up a new Windows domain
controller. These steps should be performed before installing Process Portal
software. A domain network requires two domain controllers (primary and
secondary) to provide redundancy. Domain controllers require the Windows 2000
Server or Server 2003 OS. A domain controller should not contain Process Portal
software (especially Configuration Server software).

Domain Networks
Domain networks can be isolated from or linked to (through a router) other domain
networks. Where necessary, the steps in this section provide specific information
about the unique settings required by both isolated and linked network domains.

Domain Setup
Perform this procedure at the computer that you have designated to be the domain
controller/DNS server.
Before you set up a new domain, verify that the node you are using as the domain
controller has Windows 2000 Server or Windows Server 2003 installed. You
cannot use Windows XP Professional for a domain controller or DNS server.
Ensure TCP/IP protocol is correctly installed on the computer.

Create a new domain by setting up a new domain controller and DNS server using
the Active Directory Installation wizard. Run this wizard on the node designated to
be the domain controller.

WBPEEUI220793D0 103
Domain Setup Appendix A Domain Controllers

To set up a new domain:


1. Configure the IP-addresses of the domain controller node if this is not already
done.
a. Set the IP address of this computer as the Preferred DNS Server on the
Primary Network Interface.
b. If you are (or will be) using two Domain Controllers set the IP address of
the other Domain Controller as the Alternate DNS Server on the Primary
Network Interface.
c. If you are using redundant network set the DNS settings on the Secondary
Network interface opposite to the settings on the primary network
interface.
2. Select Start > Programs > Administrative Tools and then click Configure
Your Server.
3. Click Active Directory and then Start to start.
4. Click Next.
5. In the Domain Controller Type dialog, select Domain controller for new
domain. Click Next.
6. In the Create Tree or Child Domain dialog, select Create a new domain tree.
Click Next.
7. In the Create or Join Forest dialog, select Create a new forest of domain
trees. Click Next.
8. In the New Domain Name dialog, choose a proper name for the (still non-
existing) domain. Click Next.
9. In the NetBIOS Domain Name dialog, choose name and click Next.
10. In the Database and Log Locations dialog, click Next.
11. In the Shared System Volume dialog, click Next.The Active Directory
Installation wizard will automatically recognize a missing DNS server and
install and configure the DNS service on the domain controller computer for
you. For Active Directory, DNS is required.
12. Click OK.

104 WBPEEUI220793D0
Appendix A Domain Controllers Domain Setup

13. In the Configure DNS dialog, select Yes install and configure DNS on the
computer.
14. Click Next.
15. In the Permissions dialog, choose compatible only with Windows 2000 (this is
to maximize security).
16. Click Next.
17. In the Directory Service Restore Mode Admin Password dialog, specify a
password.
Remember this password. This is the password of the local Administrator on this
node that will be used if the Domain Controller is later demoted from being a
Domain Controller to be a normal domain member node.

18. Click Next.


19. In the Summary dialog, click Next. The installation wizard now executes the
Configuring Active Directory procedure.
20. At completion of Active Directory Installation, click Finish.
21. Choose to Restart Windows.
22. Check the DNS settings made by the Active Directory Wizard. Only the
forward lookup zone has been created
23. Delete the entry with just a dot (.).
24. Add a reverse lookup zone for the Primary Network. In the DNS configuration
window mark Reverse Lookup Zones. From the Action menu select New
Zone... to start in the New Zone Wizard.
25. Click Next.
26. In the Reverse Lookup Zone dialog, enter the Network ID for the primary
network for this computer; for example: 172.16.4. Click Next.
27. In the Reverse Lookup Zone box, enter the Network ID for the primary
network for this computer; for example: 172.16.4.0. Click Next.
28. Click Finish to complete the New Zone Wizard.

WBPEEUI220793D0 105
Domain Setup Appendix A Domain Controllers

29. Mark the new zone and right click to select Properties. Change Allow
Dynamic Updates? to either Yes or Only Secure Updates. Then click OK.
30. If there is a redundant network, repeat Step 23 through Step 28 to add a
Reverse Lookup Zone for the secondary network. Enter the network ID for the
secondary network; for example: 172.17.4.0.
If you are configuring just one Domain Controller the configuration is finished here.
For redundant domain controllers repeat Step 1 through Step 19 on a second
Windows Server node except that in Step 5, you must choose to install an
Additional domain controller for an existing domain.

106 WBPEEUI220793D0
Appendix B Time Synchronization

Introduction
Any non-Process Portal node (domain controller) must be synchronized with
Process Portal. To do this, enable the SNTP Server on a Process Portal node
(LocalNTP = 1) that is not the Domain Controller by performing the following
steps:
1. Using standard Windows procedures, run regedit.
2. Locate HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\
W32Time\Parameters.
3. Check whether there is a value called LocalNTP or not and create it if it is not
there using the following Value Names:
LocalNTP.
Data Type: REG_DWORD.
Value Data: 0 = disabled, 1 = enabled.
4. Set the value of LocalNTP to 1.
5. Set the W32Time service to Automatic in the Windows Service Manager.
6. Restart the node for changes to be implemented.
7. Next, reconfigure the Windows Time Service in one of the nodes that will be
synchronized from the Control Network system so that it acts as an SNTP
server or install an SNTP server on the same subnet as the non-Process Portal
nodes (domain controller).
8. Reconfigure the Windows Time Service in the Domain controller so that it
fetches the time from the SNTP server.
To configure a Domain Controller to find the time from a specific SNTP server,
perform the following steps:

WBPEEUI220793D0 107
Introduction Appendix B Time Synchronization

1. Start a Windows Command Prompt on the Domain Controller.


2. Stop Win32Time, reconfigure it, and restart it by the following commands:
C:\>net stop w32time.
C:\>net time /setsntp: x.x.x.x
C:\>net start w32time.
x.xx.x is the IP address of the appointed SNTP server. If more than one
SNTP server is to be used in order to get server redundancy, type the
addresses separated with blank space(s): x.x.x.x y.y.y.y
3. To synchronize once to verify that the configuration worked and that the SNTP
server works type:
C:\>w32tm -once.
This should not generate any errors. It is a good idea to check that there are no error
messages from w32Time in the System Log in the Event Viewer in Administrative
Tools.

108 WBPEEUI220793D0
Appendix C User Account/Account Rights
Manual Configuration

Introduction
The creation of accounts, groups, and users and the configuration of access rights is
automatically completed as part of the installation. This sections provides steps on
how to those configurations and creations manually if necessary.

Create Accounts, Groups, and Users


Figure 24 shows the account structure.
Read and execute this section if Process Portal is being installed for the first time.

Service Accounts
These accounts must be local accounts on all nodes in the system. The same name
and password must be used on all nodes. The Process Portal service accounts must
be members of the local administrator group and have Act as part of the operating
system and Log on as a service user rights.
When using a domain, create a domain Process Portal service account with the same
name, password, and user rights as the local Process Portal service account. Make

WBPEEUI220793D0 109
Service Accounts Appendix C User Account/Account Rights Manual Configuration

OT H E R LO C A L
U S E R A C C O U N TS

LO C A L D O M A IN
P R O C E S S P O R TA L P R O C E S S P O R TA L
USER G ROUPS USER G ROUPS

P R O C E S S P O R TA L P R O C E S S P O R TA L
OTH E R D O M A IN
S E RV IC E S E RV IC E
U S E R A C C O U N TS
AC C O U N T AC C O U N T
(L O C A L AC C O U N T) (D O M A IN A C C O U N T)

LO C A L
A D M IN IS T R ATO R S
GRO UP
T 04443 B

Figure 24. Account Structure

the domain Process Portal service account a member of the local Process Portal
administrator group on every node.
Once established, change the name and password of the Process Portal service
account if required by using the Service Account Maintenance Utility. Refer to
Section 15 of the Process Portal Operation instruction for a more detailed
instruction.

Create a New Service Account


1. Select Start > Settings > Control Panel > Administrative Tools > Computer
Management > System Tools > Local Users and Groups.
2. Right click the Users folder and select New User... from the pop-up menu.
3. Enter the appropriate information in the User name, Full name (optional),
Description (optional), Password (required), and Confirm password (required)
fields (Figure 25).
4. Disable User must change password at next logon.

110 WBPEEUI220793D0
Appendix C User Account/Account Rights Manual Configuration Service Accounts

TC02503C

Figure 25. Process Portal Service Account

5. Enable User cannot change password and Password never expires.


6. Click Create.

Assign Administrative Rights


7. From the Computer Management window, select the Groups folder.
8. Right click Administrators from the list of names and select Add to Group.
9. Click Add.
10. In the Select Users or Groups window, set the Look in field to the local
computer name (a domain controller defaults to the name of the domain).
11. Highlight the name of the user account created previously.
12. Click Add.
13. Click OK.

Assign User Rights


14. Select Local Security Policy from the Administrative Tools folder.
15. Select the Local Policies folder.

WBPEEUI220793D0 111
User Group Appendix C User Account/Account Rights Manual Configuration

16. Select User Rights Assignment.


17. Select Act as part of the OS from the Policy list.
18. Click Add.
19. Set the Look in field to the local computer name (a domain controller defaults
to the name of the domain).
20. Highlight the name of the user account created previously.
21. Click Add.
22. Click OK.
23. Select Generate Security Audits from the Policy list.
24. Click Add.
25. Set the Look in field to the local computer name (a domain controller defaults
to the name of the domain).
26. Highlight the name of the user account created previously.
27. Click Add.
28. Select Log on as a service from the Policy list.
29. Set the Look in field to the local computer name (a domain controller defaults
to the name of the domain).
30. Highlight the name of the user account created previously.
31. Click Add.
32. Click OK.

User Group
Every user must have the ability to generate audits on all nodes in the system. Create
a user group on all nodes. Assign the generate security audits right to this group.
Make the local and domain Process Portal service accounts a member of this group
on all nodes. Make all local Process Portal users members of this group on all nodes.
When using a domain, create a domain Process Portal user group. Make the domain
Process Portal user group a member of all local Process Portal user groups on all

112 WBPEEUI220793D0
Appendix C User Account/Account Rights Manual Configuration User Group

nodes. Make all domain Process Portal users members of the domain Process Portal
user group.

Create a New User Group


1. Select Start > Settings > Control Panel > Administrative Tools > Computer
Management > System Tools > Local Users and Groups.
2. Right click the Groups folder and select New Group... from the menu.
3. Enter the appropriate information in the Group name and Description
(optional) fields.
4. Click Add.
5. Set the Look in field to the local computer name (a domain controller defaults
to the name of the domain).
6. Highlight the name of the service account created previously.
7. Click Add.
8. Click OK.
9. Click Create.
10. Repeat Step 5 through Step 9 for each local Process Portal user account.

Assign User Rights


11. Select Local Security Policy from the Administrative Tools folder.
12. Select the Local Policies folder.
13. Select User Rights Assignment.
14. Select Generate Security Audits from the Policy list.
15. Set the Look in field to the local computer name (a domain controller defaults
to the name of the domain).
16. Highlight the name of the local group created previously and click Add.
Log out and then log in to the Process Portal service accounts. Use the Process
Portal service accounts during all phases of all installation processes (unless
otherwise instructed).

WBPEEUI220793D0 113
SQL Access Rights Appendix C User Account/Account Rights Manual Configuration

SQL Access Rights


All nodes containing a configuration server, historian server, or a mirror web site
need read access (for all Process Portal users) to the ConfigServer and SQL server
databases.
To configure access rights for read access:
1. Open the SQL server enterprise manager.
2. Register the SQL server using the provided wizard, if it has not already been
registered.
This must be done for each node with a database.

3. Select Console Root > Microsoft SQL Servers > SQL Server Group and
right click on SQL Server Group.
4. Select New SQL Server Registration.
5. Click Next.
6. Enter the SQL server name.
7. Click Add and then Next.
8. Select the first option in the Select an Authentication Mode window and click
Next.
9. Select the first option in the Select SQL Server Group window and click Next.
10. Click Finish.
11. Expand the listing to the view the Microsoft SQL Servers\SQL Server
Group\node_name\Security directory. Refer to Figure 26.
12. Right click Logins.
13. Select New Login... from the menu.
14. Select the button to the right of the empty Name: field in the SQL Server Login
Properties - New Login window.
15. Select the local Process Portal user group name and click Add Name.

114 WBPEEUI220793D0
Appendix C User Account/Account Rights Manual Configuration SQL Access Rights

TC02517A

Figure 26. SQL Server Enterprise Manager

16. Click OK.


17. Select Windows 2000 Authentication and Grant access.
18. Specify the Domain to use to validate a logon's network security attributes.
19. Select the Database Access tab.
20. Enable access to the Model database.
21. Enable db_datareader in the Database roles for Model: window.
22. Repeat Step 20 and Step 21 for the following Model databases:

ConfigServer
Historian_Master
Archive_Master
Historian_1 (The name of the historian database selected upon installation.)
Harmony_Import

WBPEEUI220793D0 115
SQL Access Rights Appendix C User Account/Account Rights Manual Configuration

OPC_Import
NOTE: Not all databases will appear on every node.

23. Click OK.

116 WBPEEUI220793D0
WBPEEUI220793D0 Litho in U.S.A. November 2004
Copyright 2004 by ABB. All Rights Reserved
Registered Trademark of ABB.
Trademark of ABB.

http://www.abb.com/control

Automation Technology Products Automation Technology Products Automation Technology Products


Wickliffe, Ohio, USA Vsters, Sweden Mannheim, Germany
www.abb.com/processautomation www.abb.com/processautomation www.abb.de/processautomation
email: industrialitsolutions@us.abb.com email: processautomation@se.abb.com email: marketing.control-products@de.abb.com

Vous aimerez peut-être aussi