Administrator s Guide WebWare Server

(1)

Administrator’s Guide

WebWare Server

Version 4.9

Document ID: 3HAC031359-001 Revision: B

(2)

construed as a commitment by ABB. ABB assumes no responsibility for any errors that may appear in this manual.

Except as may be expressly stated anywhere in this manual, nothing herein shall be construed as any kind of guarantee or warranty by ABB for losses, damages to persons or property, fitness for a specific purpose or the like.

In no event shall ABB be liable for incidental or consequential damages arising from use of this manual and products described herein.

This manual and parts thereof must not be reproduced or copied without ABB's written permission, and contents thereof must not be imparted to a third party nor be used for any unauthorized purpose. Contravention will be prosecuted.

Additional copies of this manual may be obtained from ABB at its then current charge.

Robotics Products 721 68 Västerås

(3)

3 3HAC031359-001 Revision: B © Copyri ght 199 9-2006, 2008-2 009 AB B.

Overview . . . 7

What’s New In This Release . . . 9

Glossary . . . 10

1 Welcome to WebWare Server 15 1.1 What is WebWare Server? . . . 15

1.2 WebWare Server Network Topology . . . 17

1.3 Information Flow and Timing . . . 19

2 Get Started with WebWare Server 23 2.1 Get Started . . . 23

2.2 WebWare Server Implementation Plan . . . 24

2.3 WebWare Server Installation Checklist . . . 25

2.4 PC Hardware and Software Requirements . . . 28

2.5 Recommended Software for Performance Enhancement . . . 35

2.5.1 Overview . . . 35

2.5.2 MSMQ . . . 36

2.5.3 Microsoft SQL Server . . . 37

2.6 Installing WebWare Server . . . 38

2.6.1 Overview . . . 38

2.6.2 Upgrading WebWare Server . . . 39

2.6.3 Complete Installation of WebWare Server. . . 41

2.6.4 Custom Installation of WebWare Server . . . 43

2.6.5 License Key Installation . . . 44

2.6.6 How to request and install a license key over the Internet . . . 45

2.6.7 How to request a license key using e-mail . . . 47

2.6.8 How to install a license key received by e-mail . . . 49

2.6.9 Completing the Installation . . . 51

2.6.10 Checking Your Installation. . . 52

2.6.11 Medium and Large System Installations . . . 53

2.6.12 Configure WebWare Server Authentication - Medium & Large Systems. . . 54

2.6.13 Setting Up a Data Collector - Medium & Large Systems . . . 56

2.6.14 Creating Additional WebWare Data Collectors - Medium & Large Systems . . . 60

2.6.15 WebWare Server Database Setup for Microsoft SQL Server . . . 61

2.7 Installing ABB WebWare Client . . . 62

2.7.1 User Security Settings . . . 62

2.7.2 Download the Installation Files . . . 64

2.7.3 Overview . . . 65

2.8 Configuring System Components . . . 66

2.8.1 Overview . . . 66

2.8.2 Enabling the WebWare Interface - Small Systems . . . 67

2.8.3 Determining the IP Address of Robots on Your Network . . . 68

2.8.4 ABB Robot Configuration Procedures . . . 69

2.8.5 Connecting a Robot to a Data Collector. . . 72

2.8.6 Creating a Robot Profile . . . 73

2.8.7 Robot Aliases . . . 74

2.8.8 How to Add S4 Robot Alias . . . 75

2.8.9 How to Add IRC5 Robot Alias . . . 76

2.8.10 Connecting Other Device Types to a Data Collector . . . 78

2.8.11 Plant Model . . . 79

2.8.12 Checking System Status . . . 81

3 WebWare Server Module 85 3.1 Overview . . . 85

(4)

3.2 WebWare Administration . . . 87

3.2.1 Overview . . . 87

3.2.2 Settings Page . . . 88

3.2.3 Devices Page . . . 93

3.2.4 Data Collector Setup Page . . . 96

3.2.5 Database Page . . . 97

3.2.6 How to Restore an Archived Database to a New Database . . . 105

3.2.7 Backup Page. . . 107

3.2.8 How to Configure Backup and Archive File Folder Names . . . 113

3.2.9 How to Configure IIS when Storing the Windows User Name in the Backup Log . . . 115

3.2.10 Reports Page. . . 116

3.3 License Management . . . 118

3.3.1 ABB Robotics License Management . . . 118

3.3.2 WebWare License Priority . . . 121

3.4 User Documentation. . . 122

3.4.1 Help Page . . . 122

3.4.2 Documentation Page . . . 123

3.4.3 How to Add Content to the Documentation Page . . . 124

4 WebWare Report Module 127 4.1 Overview . . . 127

4.2 WebWare Data Collection & Monitoring . . . 129

4.2.1 Info Page . . . 129

4.2.2 Data Page . . . 132

4.2.3 WebWare Server Database . . . 135

4.2.4 Relocating a WebWare Database. . . 139

4.2.5 Creating a New WebWare Server Database . . . 144

4.2.6 Custom Database Tables . . . 145

4.2.7 How to Enable WebWare Reports for Custom Databases. . . 158

4.2.8 Data Events . . . 159

4.2.9 WebWare Data Event Editor . . . 160

4.3 WebWare Reports . . . 165

4.3.1 Reports Page. . . 165

4.3.2 Report Viewer Page . . . 167

4.3.3 Report Manager Page . . . 168

4.3.4 How to Build a Report . . . 169

4.3.5 Report Builder Page . . . 170

4.3.6 How to Edit Reports You've Created . . . 172

4.3.7 How to Run a Report . . . 173

4.3.8 How to Add an Existing Module to Your Report . . . 174

4.3.9 How to Create a Chart/Table Module . . . 175

4.3.10 How to Set Up Chart/Table Parameters . . . 176

4.3.11 How to Build a Database Query. . . 177

4.3.12 How to Use the Query Builder Page . . . 178

4.3.13 How to Apply Design-Time Options . . . 188

4.3.14 How to Apply Chart Options . . . 190

4.3.15 How to Apply Table Options . . . 191

4.3.16 HTML Module Overview . . . 192

(5)

4.3.23 How to configure Service Information System (SIS) for IRC5 . . . 202

4.3.24 Service Information System (SIS) Logs Report . . . 203

5 WebWare Backup Module 205 5.1 Overview . . . 205

5.2 ABB WebWare Server & ABB Network File System . . . 206

5.2.1 Network File System (NFS) Overview . . . 206

5.2.2 How to Configure NFS at the Device Configuration Utility . . . 209

5.2.3 How to Configure an NFS Mount for an S4 Robot . . . 210

5.2.4 How to Configure an NFS Mount for an IRC5 Robot . . . 212

5.2.5 How to Restore Files from an NFS Mount Using the Robot Teach Pendant. . . 214

5.2.6 How to Restore Files from an NFS Mount Using the Robot Flex Pendant . . . 216

5.2.7 File Management Methods . . . 218

5.3 WebWare Backup . . . 219

5.3.1 Introduction . . . 219

5.3.2 How to Configure WebWare Backup. . . 226

5.3.3 How to Configure WebWare NFS Backup . . . 228

5.3.4 Backup Control Page . . . 229

5.3.5 How to Use On-Demand Backups . . . . 230

5.3.6 Backup Tips . . . 231

5.3.7 Backup Status Messages. . . 232

5.3.8 Backup Schedule Page . . . 236

5.3.9 Schedule Manager Page . . . 237

5.3.10 How to Schedule Backups . . . 239

5.3.11 Backup Results Page . . . 240

5.3.12 How to Display Backup Results. . . 243

5.3.13 Backup Restore Page . . . 244

5.3.14 How to Use the WebWare File Manager . . . 247

5.3.15 How to Use the Restore Page . . . 248

5.3.16 How to Restore a Backup Using WebWare . . . 250

5.3.17 Backup Summary Page. . . 251

5.4 WebWare Ramdisk Mirror . . . 252

5.4.1 Introduction . . . 252

5.4.2 How to Set Up a Data Collector as a Ramdisk Mirror . . . 254

5.5 WebWare Visual SourceSafe Module . . . 255

5.5.1 Overview . . . 255

5.5.2 Configuring WebWare Visual SourceSafe Module . . . 256

5.5.3 WebWare Visual SourceSafe Module Screen Components. . . 257

5.5.4 Retrieving Latest File Version from Visual SourceSafe . . . 259

5.5.5 Retrieving Selected File Version from Visual SourceSafe . . . 260

5.5.6 Viewing File Differences . . . 261

5.5.7 Assigning File Types in Visual SourceSafe . . . 262

6 System Reference 263 6.1 Overview . . . 263

6.2 Custom Web Site Configuration Procedures . . . . 264

6.2.1 Overview . . . 264

6.2.2 General Installation Process . . . 265

6.2.3 Installing Internet Information Services (IIS) . . . 266

6.2.4 Enabling Administrative Tools in Start Menu . . . 269

6.2.5 Accessing the IIS Management Console . . . 270

6.2.6 Configuring IIS to Host WebWare as a Virtual Directory . . . 271

6.2.7 Selecting the Default Document. . . 272

(6)

6.2.9 Running the .Net Installation Utility . . . 274

6.2.10 Configuring IIS with Personal Web Manager . . . 275

6.2.11 Custom Installation Procedures . . . 278

6.2.12 Configuring IIS to Host WebWare as a Default Web Site. . . 279

6.2.13 Installed Files and Folders . . . 284

6.3 Windows Service Pack Issues. . . 286

6.3.1 Overview . . . 286

6.3.2 ABB WebWare Security Settings Utility. . . 287

6.3.3 Windows Firewall Settings . . . 288

6.3.4 DCOM Configuration . . . 289

6.4 WebWare RAPID Module . . . 291

6.4.1 WebWare RAPID Module (WebWare.sys) . . . 291

6.4.2 Controlling WebWare Backup from WebWare.sys. . . 292

6.4.3 RAPID Instructions . . . 296

6.4.4 WWRestore Instruction . . . 297

6.4.5 WebWare RAPID Restore Procedure . . . 299

6.4.6 WWStartBackup Instruction . . . 308 6.4.7 WWIncrCounter Instruction. . . 309 6.4.8 WWStartTimer Instruction. . . 311 6.4.9 WWStopTimer Instruction. . . 313 6.4.10 WWLogTimedEvent Instruction . . . 315 6.4.11 WWSetProgramInfo Instruction . . . 317 6.4.12 WWSetLabels Instruction . . . 318 6.4.13 WWSetField Instruction. . . 319

6.4.14 WebWare Server Link State Heartbeat Function. . . 320

6.5 Return Status Codes . . . 321

6.5.1 Return Status Codes . . . 321

6.5.2 RPC Communications Errors . . . 322

6.5.3 InterLink Module Communication Errors . . . 323

6.5.4 General Error Messages . . . 325

6.5.5 InterLink FTP Error Codes . . . 326

6.5.6 InterLink Error Code Definitions. . . 327

6.5.7 InterLink Monitor Connecting Failure. . . 329

6.5.8 Variable Handling Error Messages . . . 331

6.5.9 Program Handling Error Messages . . . 333

6.5.10 File Handling Error Messages . . . 334

6.5.11 Configuration Handling Error Messages . . . 335

6.5.12 Log Error Messages . . . 336

6.6 WebWare Server Error Codes . . . 338

6.7 Null Modem Cable Diagrams . . . 339

6.7.1 RS-232 Cable Diagrams. . . 339

6.7.2 S4 Controller Diagrams . . . 341

6.8 Installing WebWare Server with RobotStudio, QuickTeach or ProgramMaker. . . 344

(7)

Overview

About This Manual

This manual contains information and procedures to install, configure, administer and use the ABB WebWare Server.

Usage

This manual should be used during installation, configuration, administration and use of the ABB WebWare Server.

Who Should Read This Manual?

This manual is intended for:

• System Administrators

• Network Technicians

• Computer Technicians

• Production Technicians

Prerequisites

The reader should:

• Be familiar with basic robot concepts.

• Have knowledge and understanding of computers and computer networks as well as robots and robot controllers.

• Know generic program handling on a computer with the Windows operating system.

• Know how to administer, configure and install the Microsoft Windows operating system.

Organization of Chapters

The manual is organized in the following chapters:

Chapter Contents

1. Welcome to WebWare Server

Introduction to WebWare Server and network topology.

2. Get Started with WebWare Server

How to install WebWare Server on a PC and connect robot controllers and other devices on the WebWare network to it. It also describes how to install the WebWare Server Web Client. 3. WebWare Server

Module

How to administer WebWare Server.

4. WebWare Report Module

Describes the features of the WebWare Server Report Module that allows you to remotely monitor the state of the devices connected to your WebWare Server network. It also describes how to create custom reports to display production and service status information about devices on the WebWare Server network.

(8)

Overview © Copyri ght 199 9-2006, 2008-2 009 AB B.

References

Revisions

5. WebWare Backup Module

Describes the features of the WebWare Server Backup Module that allows you to move files on and off robot controllers to backup the investment you have made in robot programming, even using popular version control systems such as Microsoft Visual SourceSafe.

6. System Reference Reference information containing detailed information on the rich user interfaces provided by WebWare Server and its components, as well as error code explanations and more.

Chapter Contents Reference Document Id -Revision Description - First release A

B Released with WebWare 4.9.

(9)

What’s New In This Release

Overview

For information about what’s new in this release, please see the release notes (ReadMe.htm) on the installation CD.

(10)

Glossary © Copyri ght 199 9-2006, 2008-2 009 AB B.

Glossary

Important Terms

The table below defines terms as we will use them in describing concepts in WebWare products.

Term Definition

Alarms OPC events that indicate a problem with some part of the system. OPC alarms include several conditions, including type, severity, state, name, etc.

Alias The named instance of a robot controller accessed by InterLink.

Backup file set The list of files, robot program modules, log files, etc. that you selected for backup from a robot controller.

BaseWare ABB robot controller operating system software.

Counters Counters count event occurrences over a given time frame. Typical WebWare counters are ideal for counting parts per hour and failures per hour, often set from RAPID robot controller counter functions.

Data Collector Any computer that has InterLink software installed on it. A Data Collector collects data from robot controllers and pushes that data up to WebWare Server.

Data Event The WebWare Data Event Editor allows you to increment WebWare counters or start and stop WebWare timers based on an OPC tag’s state.

Data Source Name (DSN) A data source name (DSN) is a data structure that contains information about a specific database that an Open Database Connectivity (ODBC) driver needs to connect to it. Included in the DSN, which resides either in the registry or as a separate text file, is information such as the name, directory and driver of the database, and depending on the type of DSN, the user ID and password.

Default Web Site A “default” web site is the first site that will appear when a browser is pointed to http://hostname where hostname is the name of the server PC.

Device Configuration Utility (DCU)

Program that allows users to configure robot aliases and profiles for use in the WebWare system.

Event Log File that stores event messages from the robot.

Events Something that happens. In WebWare, typical events include StatusChanged events, Help events etc.

Extensible Markup Language (XML)

XML, a formal recommendation from the World Wide Web Consortium (W3C), is similar to the language of today's Web pages, the Hypertext Markup Language (HTML). XML is a markup language for documents containing structured infor-mation.

Hypertext Transfer Protocol (HTTP)

Protocol used for transferring files (text, graphic images, sound, video, and other multimedia files) on the World Wide Web.

(11)

InterLink Monitor Utility program that allows users to monitor the connection status of devices connected to the WebWare network. InterLink Service The InterLink executable object that is installed in the registry

database maintained by the Service Control Manager. The InterLink service, when installed, allows InterLink to be started at boot time by a boot program, by the system, or it can be started on demand by the Service Control Manager.

IP Address The numeric Internet Protocol address that uniquely identifies each computer on a network that uses TCP/IP. The IP address is a 32-bit identifier made up of four groups of numbers, each separated by a period, such as 123.432.154.12.

License Key A license key allows you to use an application or a feature of an application that you have purchased from ABB. A license key is a data record in a license file. You will receive one or more license files each containing one or more license keys for the various applications that you have purchased from ABB.

License Request A request received either electronically or via mail, for a license key that will allow you to operate a piece of ABB software or a feature of an ABB software product.

Linked Alias An additional application or device connected to the same Robot alias on a WebWare network.

Log messages Individual error or event messages that are grouped into a log file.

Microsoft Message Queue Server (MSMQ)

Microsoft Message Queuing (MSMQ) technology enables applications running at different times to communicate across heterogeneous networks and systems that may be

temporarily offline. Applications send messages to queues and read messages from queues. MSMQ provides

guaranteed message delivery, efficient routing, security and priority-based messaging. It can be used to implement solutions for both asynchronous and synchronous messaging scenarios.

Network File System (NFS) The ABB Network File System (NFS) option was originally designed to provide an alternative method for restoring files to a robot controller via a Teach Pendant.

Open Database Connectivity (ODBC)

An open standard application programming interface (API) for accessing a database.

OLE for Process Controls (OPC)

A standard interface developed by the OPC Foundation. It allows factory floor devices, business information and control systems to communicate with each other using a standard industrial protocol. The OPC specifications are available at http://www.opcfoundation.org.

OPC Device Any Object Linking and Embedding (OLE) for Process Controls (OPC) compliant device. Devices could include PLC’s, HMI devices etc.

OPC Server The OPC Server is an ABB software product that provides an interface to all robot controllers using the OLE for Process Controls (OPC) specification.

Persistent Variables In RAPID, a variable that keeps its value between sessions.

Continued

(12)

Poll delay This field contains the InterLink polling delay in milliseconds. The polling delay is the amount of time the robot interface sleeps between polling cycles. The default polling delay is 200 milliseconds.

Profile A profile is a group of properties and parameters that determine the behavior of a robot alias.

Ramdisk In an ABB robot controller, a memory device located in the controller’s RAM.

Robot Application Protocol (RAP)

Provides an application interface to the ABB Robot Control-lers. RAP provides a set of services that you can use to control and monitor ABB Robots from an external computer. RAPID Programming language used to program ABB robots. Robot Alias The naming device used by InterLink to refer to a designated

device on the WebWare network.

Robot modules RAPID programs consist of one or more modules. There are two types of modules:Program modules - contain the RAPID program statementsSystem modules - configuration parameters and robot settings

Service A program, routine, or process that performs a specific system function to support other programs, particularly at a low (close to the hardware) level.

Simulated Interface An interface that allows InterLink to respond to all functions and methods, even though InterLink is not connected to a real robot controller. Used for application development.

SQL Server The Microsoft program that manages Structured Query Language (SQL) databases. When referring to the product or the server running the product, SQL is pronounced “sequel” and takes the article a when not preceded by Microsoft - for example, “an SQL Server.”

Structured Query Language (SQL)

SQL is a standard interactive and programming language for getting information from and updating a database.

Tags A tag is a name or a label for a piece of data or a data point. WebWare uses tags to label data on various display pages. Task scheduler A Windows utility that can run a script, program or document

at a pre-selected time, either on a one-time or repeating basis. Transfer Control Protocol

(TCP)

A protocol used along with the Internet Protocol (IP) to send data in the form of message units between computers over the Internet.

Timers A software routine that causes the system to trigger an event whenever a specified interval elapsed or at user-defined intervals. Typical timers in WebWare are used to measure cycle time, squeeze time, hold time, etc.

Uniform or Universal Resource Locator (URL)

An address that uniquely identifies a location on the Internet. A URL for a World Wide Web site is preceded with http://, as in the fictitious URL http://www.example.microsoft.com. A URL can contain more detail, such as the name of a page of hypertext, usually identified by the file name extension .html

(13)

Visual SourceSafe (VSS) A source code repository program from Microsoft used to store and maintain version control of software components. WebWare WebWare is a suite of products that provide a web site for

process monitoring, file management, collection of production statistics and diagnostic information. The WebWare family consists of WebWare Server (the web site software) and the WebWare SDK for developing custom factory-floor PC operator stations.

WebWare Backup A WebWare utility that backs up a robot program or selected robot modules.

WebWare Server WebWare Server is a standard software product used to present production data, statistics, and diagnostic information collected from S4 robot controllers, HMI applications, and other factory floor automation equipment.

WebWare Server host machine

The computer that is the WebWare Server host computer. The machine where WebWare Server software is installed. WebWare WebClient Software that allows a remote computer to browse to the

WebWare Server web site. Requires Windows Internet Explorer.

(14)

(15)

1.1. What is WebWare Server? 15 3HAC031359-001 Revision: B © Copyri ght 199 9-2006, 2008-2 009 AB B.

1 Welcome to WebWare Server

1.1. What is WebWare Server?

Overview

WebWare Server is a web-based IT solution tailored to flexible automation. Besides support for ABB robots, WebWare Server incorporates industry-standard protocols and interfaces, such as OPC, thereby supporting a wide variety of automation equipment. In this way, WebWare Server can help you manage and automate many of your common plant floor IT needs. WebWare Server:

• Supports lifecycle management of production software

• Accelerates the fault recovery process

• Provides real-time production feedback

WebWare Server comes with two optional modules, the Backup module and the Report module. The table below provides an overview of the optional modules.

Each of the following sections describes the major capabilities of WebWare Server and its modules.

WebWare Backup Module

Your plant network provides the communication infrastructure that WebWare Server uses for plant-wide file management. Any equipment that supports the FTP file transfer protocol can be included in WebWare Server’s file management & backup system.

WebWare Server’s Backup module features accelerate fault recovery by providing ready access to the archive of production programs, allowing for rapid recovery in the event of equipment substitution or the need for post-repair software reloads. Additionally, version control of programs (available if you have Microsoft Visual SourceSafe) permits online visual review of change history to correlate program changes with quality problems. The ability to perform unattended, scheduled backups is practical for safeguarding critical part programs and tracking program changes. Once your production files are safely archived, you can restore them to the device controller or download them directly to your PC for off-line program maintenance. WebWare Server includes built-in support for Microsoft Visual SourceSafe and NFS; this provides additional capabilities for efficient file handling and secure version control, including change history and version comparison.

Function Server Module Report Module Backup Module Device Information X

Reports & Data Collection X

Backup

Documentation X

Administration X (X) (X)

Login X

Help X

(16)

1.1. What is WebWare Server? © Copyri ght 199 9-2006, 2008-2 009 AB B.

WebWare Report Module

WebWare Server Report module provides access to both live and historical production data. Accessing live data, you can monitor the current status of production equipment that presents its data via OPC.

WebWare Server incorporates the concepts of user-defined Counters and Timers. Counters are data elements that can be used to quantify some measure (e.g., the number of parts produced, the number of defects, the size of a part buffer) during some user-defined repeating interval (e.g. hours, days, weeks). A Timer is a data item that can be repeatedly started & stopped, and used to measure the duration of some state or action (e.g. the amount of time waiting for a part, amount of time taken to perform a process). Counters and Timers, robot Event Log messages, and OPC Alarms & Events message are recorded to a historical relational database.

You access this data through a flexible, self-service reporting system that has the flexibility to allow you to explore data online, in an ad hoc fashion. You can define reports online and save them for future viewing, a practical way to publish standard reports online. Some examples of common data reports include inventory status, fault pareto charts, equipment utilization rates, arc weld quality, and preventive maintenance reminders.

WebWare Server Database

WebWare Server stores data gathered from your system in an SQL database that is automatically created the first time you run WebWare Server. This database stores information such as:

• Log messages generated by the robot

• Persistent variable values from your RAPID program

• Counter and Timer names and values

• OPC alarm tables

For more information, see WebWare Server Database on page 135.

WebWare RAPID Module

You can also create custom tables in your WebWare Server database and populate those tables with information from your RAPID programs. For more information, see Custom Database Tables on page 145.

WebWare SDK Applications

Using the WebWare SDK, you can develop custom applications (gateways to other IT systems, factory devices, etc.) that can provide additional data to WebWare Server for archiving and subsequent access. The WWClientApp control, when embedded in an application that you have developed, can write records to the WebWare Server database, via InterLink.

Remote Diagnostic & Service Information Continued

(17)

1.2. WebWare Server Network Topology 17 3HAC031359-001 Revision: B © Copyri ght 199 9-2006, 2008-2 009 AB B.

1.2. WebWare Server Network Topology

Introduction

The following diagram depicts all of the components of the WebWare network topology. The components shown are defined in the following sections.

xx0500001582

WebWare Server

The WebWare Server is a host computer running WebWare Server software. The host collects and stores the data received from the Data Collectors in the SQL database (devicelog.mdf). WebWare Server uses Microsoft Internet Information Services (IIS) to present the web site. The browser-based user interface provides access to both dynamic and historical data.

Data Collector

In WebWare terminology, a Data Collector is a computer that communicates with one or more WebWare devices (robot controllers, WebWare HMI applications or OPC devices) and feeds that information to WebWare Server. The Data Collector concept was developed to streamline data collection and network traffic in large installations by distributing the data collection task.Typically, a Data Collector is a factory floor PC that may host an operator interface or other factory computer application. Since Data Collectors are usually installed close to robot controllers, they often serve as plant floor operator interfaces or cell controllers in addition to being WebWare Data Collectors.

(18)

1.2. WebWare Server Network Topology © Copyri ght 199 9-2006, 2008-2 009 AB B.

The WebWare Server architecture was designed with scalability in mind. There is no limit to the number of Data Collectors that can be attached to a WebWare Server. For installations that have 1 - 5 WebWare devices, the same PC used to host the WebWare Server site can also function as the Data Collector. Large systems, with 30 or more WebWare devices, must use Data Collectors. For systems of this size, the WebWare network server cannot be configured to act as a Data Collector. Medium size systems, with between 6 and 30 devices, may see a performance improvement if “standalone” Data Collectors are added to the system. Each Data Collector can communicate with up thirty (30) WebWare devices. When the WebWare network server needs to send data to the robot, it uses the Data Collector to perform the work.

For systems that use Data Collectors, it is not necessary to configure the network server as a Data Collector.

For Data Collector hardware and software requirements, see Data Collector Computer Hardware Requirements on page 32.

ABB Robot Controller

WebWare supports any ABB robot controller, that has the PC Interface or FactoryWare option installed. Robot controllers can be connected to Data Collectors using a TCP/IP over Ethernet or SLIP (serial) connection.

WebWare SDK Application

A WebWare Client Application is any PC application that incorporates an instance of the WebWare Client Application ActiveX control (part of WebWare SDK). This control allows an application to provide information about itself to be sent to WebWare Server and displayed on the WebWare Server web site.

OPC Device

WebWare supports any OPC 1.0 or 2.0 Data Access Devices. WebWare also supports Alarm and Event Devices from a OPC 1.0 device.

Local PC

The Local PC depicted in the topology diagram denotes any PC that is connected to the same computer network as the WebWare Server host computer. Local PCs can access the server web site using Microsoft Internet Explorer and then download WebWare web client software to access the WebWare Server web site.

Remote PC

Remote PCs can access WebWare Server using either a dialup modem connection or via the Internet. Once a remote PC has established a connection with the web server, authorized users can view the WebWare web site with Microsoft Internet Explorer and the WebWare Server web client.

(19)

1.3. Information Flow and Timing 19 3HAC031359-001 Revision: B © Copyri ght 199 9-2006, 2008-2 009 AB B.

1.3. Information Flow and Timing

Distributed Software Structure

The WebWare architecture is scalable such that the data collection task can be distributed across any number of plant floor PCs to streamline network traffic. Data Collectors pull real-time data from plant-floor devices and push that data up to the WebWare Server host machine. WebWare Server uses Microsoft Messaging Queue (MSMQ) to provide local data buffering in the event of temporary network disconnects. Once on the server, all data are consolidated into an SQL database.

In addition, Data Collectors are capable of backing up the file systems of plant floor devices on a scheduled basis. These data are then cataloged in a structured archive on the server, or they can be automatically entered into a version control system. These capabilities are critical for safeguarding device programs and configuration files, as well as capturing changes made in production.

xx0500001583

The following diagram depicts the key functional blocks needed to understand the WebWare Server communication architecture.

xx0500001584

The fact that the InterLink Module is installed on the WebWare Server host computer means that we can think of the host as a Data Collector as well as a server.

The various communications paths are described in the following sections.

(20)

1.3. Information Flow and Timing © Copyri ght 199 9-2006, 2008-2 009 AB B.

InterLink Module to ABB Robot Controller

The InterLink Module polls the robot constantly to track the state of the robot controller. InterLink tracks the current robot operational state, attached digital and analog signal states, selected persistent variable states, and the contents of the robot controller’s ramdisk. The amount of data collected and the frequency of the collection is configured using the Device Configuration Utility (DCU).

When a robot encounters an error or executes an SCWRITE RAPID instruction, it sends asynchronous messages to InterLink describing the event. The timing of these asynchronous message deliveries is independent of the InterLink polling engine configuration.

InterLink also performs all robot file access functions such as backup, mirroring, etc. For more information, see Understanding and Optimizing the Polling Engine in the Device Configuration Utility help file.

InterLink Module to WebWare SDK Application

InterLink does not poll WebWare client applications. A client application sends information to InterLink when it makes sense to do so in the application. WebWare Client Applications do this by calling methods and writing to properties in the WebWare SDK WWClientApp control.

The WWClientApp control sends two types of data to the InterLink: dynamic data and historical data. Dynamic data are used to display the current state of the client application on the web site. Historical data are written into the WebWare Server database.

WebWare client applications should refrain from sending dynamic data too frequently. The information sent should be paced so that InterLink has time to relay the information to WebWare Server. Dynamic data should be updated no faster than once per second. If this information is sent more frequently, only the most recent information is displayed in the browser interface.

The historical data can be sent as often as it makes sense for the application. WebWare places all of the historical information it receives in the WebWare Server database.

InterLink Module to WebWare Server

The InterLink Module pushes information to WebWare Server. InterLink collects all the information from the attached robot controllers and WebWare client applications.

In terms of delivery timing, InterLink handles dynamic data in a different way than historical data. InterLink stores all of the dynamic states in local structures. Every second InterLink checks for a change in the dynamic state. If any changes are detected, InterLink sends these changes to WebWare Server. On a busy Data Collector, InterLink sends dynamic state updates every second.

Any time InterLink receives new historical data, this data is immediately passed to WebWare Server.

When WebWare Server needs to communicate with an attached robot controller, it sends messages to the Data Collector responsible for the work. WebWare Server only performs this

(21)

1.3. Information Flow and Timing 21 3HAC031359-001 Revision: B © Copyri ght 199 9-2006, 2008-2 009 AB B.

WebWare WebClient to WebWare Server

The WebWare WebClient is a set of controls that allows you to browse the WebWare Server web site via Microsoft Internet Explorer. Each page of the web site includes ActiveX components that update themselves dynamically by polling WebWare Server. This is how the WebWare site pages dynamically update themselves as the state of the attached devices change.

The WebWare WebClient is not the same as an application that you develop using the WebWare SDK WWClientApp control! See the WebWare SDK documentation for more information on the WWClientApp control.

InterLink Module to OPC Device

InterLink can be configured to receive data from OPC Data Access Devices as well as OPC Alarms and Events Devices.

InterLink does not poll OPC Data Access Devices for data. Instead, an OPC Device sends updated tag data that InterLink has subscribed to after the initial subscription or when the tag data has changed. The Data Access OPC Device uses Event Syncs (i.e., Connection Points) to send this data to InterLink. The Device Configuration Utility (DCU) is used to subscribe to the desired OPC Data Access Device tags (i.e., data). The tag data is viewable from the WebWare Server Data page.

Alarms and Events OPC Devices send alarms and events to InterLink in a similar fashion. InterLink is configured using the DCU to subscribe to the desired OPC Alarms and Events Devices. The DCU allows InterLink to specify or “filter” the types of alarms and events (e.g., Alarm Severity) OPC devices send to InterLink. These alarms & events are logged in the WebWare Database and are accessible from the WebWare Server Data page.

(22)

1.3. Information Flow and Timing © Copyri ght 199 9-2006, 2008-2 009 AB B.

(23)

2.1. Get Started 23 3HAC031359-001 Revision: B © Copyri ght 199 9-2006, 2008-2 009 AB B.

2 Get Started with WebWare Server

2.1. Get Started

Overview

This chapter describes system requirements, suggested implementation plan, installation checklist and installtion and configuration procedures that will help you to sucessfully setup a WebWare Server system.

(24)

2.2. WebWare Server Implementation Plan © Copyri ght 199 9-2006, 2008-2 009 AB B.

2.2. WebWare Server Implementation Plan

Introduction

The following chapter assumes that:

• Phases 1 through 5 of the procedure beloware completed and all system components are confirmed to be in good working order. Since each installation will be different, we cannot supply detailed information on the tasks that must be completed during the early phases of the project. Before you install WebWare Server, you should have installed the necessary network infrastructure (cabling, routers, switches, etc.).

• The computer hardware and software for the WebWare Server host computer and any Data Collectors in the system meet the minimum requirements as shown in section PC Hardware and Software Requirements on page 28.

Typical Implementation

The table below lists the major phases of a WebWare Server installation project.

1. Determine your system design based on the number of devices you will connect to the

WebWare Server system.

2. If necessary, install and configure the PC Interface on each robot that will be connected

to the WebWare Server system.

3. Install the plant network infrastructure.

4. Install any external Data Collectors and connect them to the plant network. 5. Connect any other plant devices to the plant network.

6. Install the WebWare Server software on the host computer, and install the Data Collector

software on any Data Collectors in the WebWare Server system.

(25)

2.3. WebWare Server Installation Checklist 25 3HAC031359-001 Revision: B © Copyri ght 199 9-2006, 2008-2 009 AB B.

2.3. WebWare Server Installation Checklist

Introduction

The information in this section is provided as a checklist when installing WebWare Server.

Important

Always restart the system when prompted to do so.

Administrative priveliges are required to install and configure WebWare.

Regularly use the Windows Update service to ensure that you have installed the latest security updates.

Regularly maintain your virus protection software to ensure that you are protected against computer viruses.

Hardware Requirements

Check that the minimum hardware requirements are fulfilled. For details, see the following information:

• Small System Server Hardware Requirements on page 28.

• Medium System Server Hardware Requirements on page 30.

• Large System Server Hardware Requirements on page 32.

• Data Collector Computer Hardware Requirements on page 32.

Software Requirements

Check that you have installed the required service packs. For details about downloading service packs, see Operating System Service Packs on page 34.

Check that you have installed Internet Information Services. For details, see the following information:

• Installing IIS on Windows 2000 Systems on page 266.

• Installing IIS on Windows XP Professional on page 266.

• Installing IIS on Windows Server 2003 Systems on page 266.

Check that Microsoft Internet Explorer 6.0 is installed. You can download it from http:// www.microsoft.com/windows/ie/default.mspx.

System Configuration Requirements

Check that the Administrative Tools folder is available in the Start-menu of your Windows operating system. For details, see the following information:

• Enabling Administrative Tools on Windows 2000 Professional on page 269.

• Enabling Administrative Tools on Windows XP Professional on page 269.

Check your domain name and computer name. Open the Control Panel and then click System. The System Properties property sheet appears. Select the Computer Name tab and write down the following information for future reference.

• Full Computer Name:________________________________

• Domain:__________________________________________

(26)

2.3. WebWare Server Installation Checklist © Copyri ght 199 9-2006, 2008-2 009 AB B.

Check your IP address. Open a command prompt and type: ipconfig

• IP Address:_______________________________________

Network Domain Configuration Requirements

Check that all Data Collectors and the WebWare Server has valid trust relationships established in the domain. If not, the system might not operate properly. Contact your server administrator to set up the proper trust relationships.

WebWare Server Installation

Install WebWare Server. For further details, see Installing WebWare Server on page 38. Request a license key. For further details, see License Key Installation on page 44. Reboot the machine when prompted to do so.

Data Collector Installation

Install the Data Collectors. For more information, see the following information:

• Setting Up a Data Collector - Medium & Large Systems on page 56.

• Creating Additional WebWare Data Collectors - Medium & Large Systems on page 60.

Data Collector Configuration

Enable the WebWare Server Interface. For more information, see How to Configure the

WebWare Server Interface in the Device Configuration Utility help file.

Check that ABB InterLink Monitor has started. The ABB InterLink Monitor icon will be visible in the notification area. If not, start InterLink Monitor by clicking Start, point to Programs or All Programs, ABB Industrial IT, Robotics IT, WebWare Server, and then click InterLink Monitor.

WebClient Installation

Check that Microsoft Internet Explorer 6.0 is installed. You can download it from http:// www.microsoft.com/windows/ie/default.mspx.

Check that the security settings allow you to download and run ActiveX controls. For more information, see User Security Settings on page 62.

Install WebWare Server WebClient. For more information, see Overview on page 65.

Robot Configuration

NOTE: The robot must have the BaseWare Option "FactoryWare Interface" (S4-systems) or "PC Interface" (IRC5-(S4-systems) installed.

Check that the IP address is configured in the robot. TCP/IP is configured using an X-start. On the TeachPendant select Service, File, Restart + 159.

Check that you have a connection to the robot. Open a command prompt and ping the IP address of the robot.

Check that you have a list of IP addresses for all your robots for future reference.

(27)

2.3. WebWare Server Installation Checklist 27 3HAC031359-001 Revision: B © Copyri ght 199 9-2006, 2008-2 009 AB B.

Verify System Connectivity

At the Data Collector, use the Device Configuration Utility to create an Alias name and connect a robot. For more information, see How to Add S4 Robot Aliases or How to Add IRC5

Robot Aliases in the Device Configuration Utility help.

• For S4 profiles, you need to clear the Simulate Interface check box that is selected by default. If you do not clear this check box, you can not communicate with the robot. For more information, see S4 Profile Editor Interface Property Page in the Device Configuration Utility help.

At the Data Collector, check that ABB InterLink Monitor has started. The ABB InterLink Monitor icon will be visible in the notification area. If not, start InterLink Monitor by clicking Start, point to Programs or All Programs, ABB Industrial IT, Robotics IT, WebWare Server, and then click InterLink Monitor.

At the Data Collector, use the Device Configuration Utility to check that WebWare Server is running. In the WebWare Server Interface Configuration dialog the WebWare Current Connection Status will state Running. For more information, see How to Configure the

WebWare Server Interface in the Device Configuration Utility help.

(28)

2.4. PC Hardware and Software Requirements © Copyri ght 199 9-2006, 2008-2 009 AB B.

2.4. PC Hardware and Software Requirements

Introduction

We divide WebWare Server networks along the lines of small, medium and large systems. The following sections will detail what size a system is and what hardware and software is required to maximize performance and reliability.

NOTE: Please read the Release Note on the installation CD for the latest information on hardware and software requirements.

Small Systems (1 - 5 Devices)

A small system typically connects 1 - 5 devices to a WebWare Server, as shown in the illustration below.

xx0500001585

By configuring the system so the WebWare Server host machine is set up to also function as the Data Collector, you save the expense of an additional computer to handle data collection duties.

Small System Server Hardware Requirements

The list below details the hardware requirements for the network server computer.

• Late Model Intel Processor (Pentium 4 or newer)

• 512 megabytes RAM

• 20 gigabytes available hard disk space plus enough hard disk space to store one backup for each robot system in the plant

• SVGA compatible display (1280 x 1024 resolution recommended)

(29)

Small System Server Software Requirements

The list below details the software requirements for a small-system WebWare Server host computer.

• Microsoft Windows Server 2003 Standard Edition and Web Edition, or

• Microsoft Windows 2000 Server and Advanced Server, or

• Microsoft Windows XP Professional, or

• Microsoft Windows 2000 Professional

• Microsoft Internet Information Services (IIS)

• Microsoft Internet Explorer 6.0

For service pack download information, see Operating System Service Packs on page 34.

Medium Systems (6 - 30 Devices)

The diagram below shows a medium-sized WebWare Server network.

xx0500001586

A medium size WebWare network requires a more robust server computer, especially if the server will also act as a Data Collector. For more information, see Data Collector on page 17. Normally, Data Collector computers are required on large systems. If your system will generate a large volume of network traffic, however, a separate Data Collector will improve performance significantly on a medium-sized system.

Continued

(30)

Medium System Server Hardware Requirements

The list below details the server computer hardware requirements for a medium-sized WebWare Server network.

• 1 gigabyte RAM

• Microsoft compatible mouse

• Network adapter configured for TCP/IP

• CD drive

• Backup system (Recommended)

• Uninterruptable Power Supply (Recommended)

Medium System Server Software Requirements

The list below details the software requirements for a medium-sized WebWare Server network.

• Microsoft Windows 2000 Server and Advanced Server

• Microsoft Internet Information Services (IIS), see Installing Internet Information Services (IIS) on page 266.

• Microsoft SQL Server 2000 or later. Microsoft SQL Server is required to handle the performance required for the database writes that will occur on an active system. For details, see Microsoft SQL Server on page 37.

• Microsoft Visual SourceSafe 6.0 (Recommended). For details about configuring and using Microsoft Visual SourceSafe on your system, see WebWare Visual SourceSafe Module on page 255.

(31)

Large Systems (30 + Devices)

The diagram below shows a large system. Each cluster of robots in the illustration represents a line or cell containing up to 30 devices (robots, HMI applications, OPC devices, etc.). Large systems require Data Collectors - the WebWare Server host computer cannot be configured as a Data Collector.

xx0500001587

The following sections detail hardware and software requirements for the WebWare Server host computer and the Data Collector computers.

Continued

(32)

Large System Server Hardware Requirements

The list below details the hardware requirements for the WebWare Server host computer.

• 1 gigabyte RAM

• 100 gigabytes available hard disk space

• Network adapter configured for TCP/IP

• CD drive

• RAID 5 with fast SCSI hot-swappable disk drives and fast SCSI interface cards (Recommended)

• Backup system (Recommended)

• Uninterruptable Power Supply (Recommended)

Large System Server Software Requirements

The list below details the software requirements for the WebWare Server host computer:

• Microsoft Windows 2000 Server and Advanced Server

• Microsoft Internet Information Services (IIS)

• Microsoft SQL Server 2000 or later. Microsoft SQL Server is required to handle the performance of the database writes that will occur on an active system. For details, see

Microsoft SQL Server on page 37.

• Microsoft Message Queuing (MSMQ) version 2.0 or later, installed and configured, see MSMQ on page 36.

• Microsoft Visual SourceSafe 6.0. For details about configuring and using Microsoft Visual SourceSafe on your system, see WebWare Visual SourceSafe Module on page 255.

Data Collector Computer Hardware Requirements

The Data Collector hardware requirements are listed below.

• Late model Intel processor (Pentium 4 or newer)

• 512 megabytes RAM

(33)

Data Collector Computer Software Requirements

The minimum software requirements for a Data Collector are listed below:

• Microsoft Windows 2000 (any version)

Data Collector Software Recommendations

For best performance, especially in large systems, we recommend the following components, above and beyond the minimum requirements listed above:

• Microsoft Message Queuing 2.0 or later - especially for large (5+ robot) systems, see

MSMQ on page 36. Requires no additional configuration.

How Many Data Collectors Are Needed?

Determining how to dimension and set up your WebWare network depends on the robot application and use, amount of generated data traffic, polling cycle time, the network architecture, and of course, the number and physical location of robots on the network. Currently, we recommend that you install one Data Collector for every 30 robots on the network. Even for medium-sized systems, unless the server computer is a robust system with a large amount of memory and fast hard drives, you should seriously consider installing Data Collector computers for maximum system performance and reliability. The Data Collector is

not required to be devoted only to WebWare Server tasks.

Web Client Computer Requirements

The web client computer is any computer that has the capability of browsing to the WebWare Server web site.

Hardware

There are no minimum hardware requirements for a web client computer. We recommend, however, a SVGA compatible display (1280 x 1024 resolution recommended).

Software

• Microsoft Windows 2000 (any version)

For Service Pack Download information, see Operating System Service Packs on page 34.

Administrative and Network Requirements

To install WebWare Server, you must be a system administrator with an administrator password.

IMPORTANT: All Data Collectors and the WebWare Server host computer must have valid trust relationships established in the domain in order to operate properly. Contact your server administrator to set up the proper trust relationships.

Continued

(34)

Computer Name Requirements

A computer that will be used as a WebWare Server or a Data Collector must have a valid computer name. If the computer name is changed, the software will fail to function properly.

Operating System Service Packs

See the Readme file on the WebWare Server installation CD for details about service packs for Windows operating systems.

We recommend that you follow best practices in regards to keeping your WebWare Server host computer operating system up-to-date. As of this writing, Service Packs can be downloaded from:

Windows Server 2003

http://www.microsoft.com/windowsserver2003/default.mspx Windows 2000 Server and Advanced Server

http://www.microsoft.com/windows2000/default.asp Windows XP Professional http://www.microsoft.com/windowsxp/pro/default.mspx Windows 2000 Professional http://www.microsoft.com/windows2000/professional/default.asp Continued

(35)

2.5 Recommended Software for Performance Enhancement

2.5.1. Overview

Introduction

This section explains why you should install the recommended software components on your WebWare system and how these components will maximize your system performance.

(36)

2.5.2. MSMQ

Overview

At the server, Microsoft Message Queuing (MSMQ) provides data preservation if the database connection is lost. Likewise at the Data Collector, MSMQ preserves data if the connection to the server is lost.

If you do not install MSMQ, the WWService.exe and InterLink demand larger amounts of memory.

MSMQ writes the message queue in transit between senders and receivers to disk, rather than to the RAM, thereby protecting it and providing a place for receivers to look for messages when the receivers are ready to receive them.

Applications use MSMQ to send messages and continue processing regardless of whether the receiving application is running or reachable over the network. The receiving application may be unreachable because of a network problem, or because of natural disconnection, as in the case of mobile users that only connect to the network periodically. When applications use the transactional delivery mode in MSMQ, MSMQ also makes sure that messages are delivered exactly one time, and that messages are delivered in the order that they were sent.

Configuring MSMQ on the WebWare Server

To properly configure MSMQ, you need to start WWService with a dependency on MSMQ using the -serviceMSMQ switch.

1. Unregister WWService as a service, as follows:

C:\Program Files\Common Files\ABB Automation\WebWare Server\WWService.exe -unregServer

2. Since unregistration removes the DCOM settings, configure the security settings by

following the procedure in ABB WebWare Security Settings Utility on page 287.

3. Re-register WWService as a service, as follows:

C:\Program Files\Common Files\ABB Automation\WebWare Server\WWService.exe -serviceMSMQ

This setting creates a dependency allowing MSMQ to start before WWService. The dependency can be verified by opening the Services dialog (Control Panel,

Administrative Tools), right-clicking the ABB WebWare Server and selecting Properties, and then clicking the Dependencies tab.

(37)

2.5.3. Microsoft SQL Server

Microsoft SQL Server

During installation, WebWare Server checks the system to determine if Microsoft SQL Server is installed on the target server computer. If Microsoft SQL Server is not detected, the WebWare Server install program installs the Microsoft Data Engine (MSDE) to allow communication between WebWare Server and the storage database that contains the network data.

Microsoft SQL Server provides the following advantages to your WebWare Server network:

• Microsoft SQL Server can handle a larger number of transactions than MSDE. This is important in medium and large systems where the database access rate is higher.

• Microsoft SQL Server can handle a larger database than MSDE. MSDE has a 2-gigabyte database size limit. Microsoft SQL Server has no database size limitations. This is important for larger systems with more robots transmitting data at one time. To properly configure Microsoft SQL Server, you will need the following information:

• Database User Name and Password with read/write access in Microsoft SQL Server

(38)

2.6 Installing WebWare Server

2.6.1. Overview

Standard Installations

The “complete” installation will install WebWare Server as a virtual directory. This is the recommended installation for most users. For more information and a step-by-step guide that will guide you through the installation process, see Complete Installation of WebWare Server on page 41.

Custom Installations

NOTE: We do not recommend that you customize your WebWare Server installation unless you have expertise in Internet Information Services (IIS), and general expertise in installing and configuring web sites.

If you plan to customize your web site configuration, make sure you have the information you need to complete the installation by reading the applicable information in chapter Custom Web Site Configuration Procedures on page 264.

You can customize your installation by changing the following default settings:

• The name of the web site

• The type of site - virtual directory or default web site (Microsoft Windows 2000 Server, Windows 2000 Advanced Server, Windows Server 2003 Standard Edition only)

• The location of the default web site folder

(39)

2.6.2. Upgrading WebWare Server

Overview

WebWare Server upgrades require that you uninstall the old version of the software from the server computer before installing the new version.

If you have created a number of reports, the uninstall process removes those files along with the rest of the old WebWare Server version.

There is a fairly painless way to preserve your reports so that you won't have to recreate them after upgrading WebWare Server.

Before uninstalling the older WebWare Server version, copy your existing report

configuration files to a safe location. You can then complete the required installation tasks and restore the report configuration to the correct location, so that they will be available after the newer version is installed.

Backup Report Configuration Files Procedure

Follow the steps below to backup your report configuration files before uninstalling WebWare Server.

1. Copy the report configuration folder to a safe location away from the WebWare server

installation. The folder is normally located at e.g.

C:\Inetpub\wwwroot\WebWare\Data\Contents\Reports.

2. Uninstall the old WebWare Server installation according to the procedure in Uninstall Procedure on page 39.

3. After completing the installation of WebWare Server, copy the report configuration folder

to e.g. C:\Inetpub\wwwroot\WebWare\Data\Contents\Reports.

NOTE: Overwrite the existing reports folder.

4. Open your browser to http://localhost/webware/update.aspx. 5. Click Update.

6. When you run WebWare Server, your reports will appear in the Report Viewer page, the

same as in the old web site.

Uninstall Procedure

To install a new version of WebWare Server, you must first uninstall the older version. Follow the steps below to unistall the old version of WebWare Server.

1. Click Start and select Control Panel. Click Add/Remove Programs. 2. Select WebWare Server from the program list. Click Remove. 3. A WebWare Server installation dialog appears. Click Next. 4. The Remove the Program dialog appears.

• If you wish to retain your existing WebWare Server database and the data stored locally on the host hard drive. Click Remove.

• If you wish to delete the existing WebWare Server database and the data stored locally, select Remove WebWare Application Data checkbox.

5. Click Remove.

(40)

6. The uninstall process starts. A dialog box appears, asking you to confirm whether you

want to delete all of the application data.

• Click Yes to complete the uninstall and delete the application data.

• Click No to complete the uninstall without deleting application data.

7. Click Finish to close the Setup Program Completed dialog.

8. Go on to install the new version of the WebWare Server software. For details, see Complete Installation of WebWare Server on page 41.

(41)

2.6.3. Complete Installation of WebWare Server

Procedure

Follow the steps below to install the software.

1. Insert the ABB WebWare Server installation CD in your CD-drive. If the Setup program

does not start automatically, go on to Step 2. Usually, the Welcome dialog (see Step 3) will appear.

2. Start the Setup program. There are three methods available, select one of the below: • Click Start on the task bar and select Run. In the dialog box that appears asking for the

name of the file to run, type D:\SETUP, or

• Open a Windows Command Prompt and type D:\SETUP, or

• Use Windows Explorer to navigate to the setup.exe file on the installation CD. Double-click setup.exe to start the installation.

NOTE: The instructions above assume the drive letter for the CD-drive you are loading from is your D: drive. If you are using a different drive, substitute your drive letter in place of D: in the instructions. For example, if your CD-drive is E:, enter E:\SETUP.

3. The Welcome dialog will appear. Click Next to continue.

4. The License Agreement dialog will appear. Select I accept. Click Next.

5. The Customer Information dialog will appear. Enter the name of your company in the Organization field. Click Next.

6. The ABB WebWare Server modules dialog appears. Select the WebWare modules to

install. Available modules are:

• WebWare Backup Module

• WebWare Report Module

After you have made your selection, click Next.

7. The Setup Type dialog appears. Click:

• Complete - to install all features. This is the recommended installation.

• Custom - to choose which features are installed and their installation locations. The

Custom Setup dialog will appear. For more information, see Custom Installation of WebWare Server on page 43.

After you have made your selection, click Next.

8. The Ready to Install dialog will appear. Select:

• Use this PC - to set up the PC as a Data Collector. Use this setting only for small

(1-5 devices) or medium (6 - 30 devices) systems. For more information, see Data Collector on page 17.

• Install Support for S4 Controllers - to set up WebWare Server to support ABB S4

robot controllers.

• Install Support for IRC5 Controllers - to set up WebWare Server to support ABB

IRC5 robot controllers.

• Create Desktop Shortcuts - to install desktop shortcuts to the Device Configuration

Utility and InterLink Monitor on the WebWare Server desktop.

(42)

After you have made your selection, click Install to start the installation.

9. The Installing Microsoft .NET Framework dialog will appear, followed by the Installing Microsoft SQL Desktop Engine (MSDE) dialog.

IMPORTANT: If you are prompted to reboot the computer after the Microsoft SQL Desktop Engine (MSDE) installation completes, click No to continue.

10. The Adobe Reader Setup dialog will appear. Click Next and follow the instructions in

the dialogs. Click Finish to continue the installation.

11. The Installing ABB WebWare Server dialog will appear.

If you have installed Windows XP SP2/SP3 or Windows Server 2003 SP1/SP2, you will be asked if the installation should configure the necessary security settings. Click Yes to continue. For more information, see Windows Service Pack Issues on page 286. Note that the Windows Firewall service must be started when the security setting utility is run or else the firewall settings will not be configured.

When the installation is complete, the Finish dialog will appear. Click Finish.

12. Continue with License Key Installation on page 44.