Administrator s Guide WebWare Server

Transcription

1 Administrator s Guide WebWare Server Version 4.9 Document ID: 3HAC Revision: B

2 The information in this manual 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 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. Copyright , ABB All rights reserved. ABB AB Robotics Products Västerås Sweden

3 Table of Contents Overview What s New In This Release Glossary Welcome to WebWare Server What is WebWare Server? WebWare Server Network Topology Information Flow and Timing Get Started with WebWare Server Get Started WebWare Server Implementation Plan WebWare Server Installation Checklist PC Hardware and Software Requirements Recommended Software for Performance Enhancement Overview MSMQ Microsoft SQL Server Installing WebWare Server Overview Upgrading WebWare Server Complete Installation of WebWare Server Custom Installation of WebWare Server License Key Installation How to request and install a license key over the Internet How to request a license key using How to install a license key received by Completing the Installation Checking Your Installation Medium and Large System Installations Configure WebWare Server Authentication - Medium & Large Systems Setting Up a Data Collector - Medium & Large Systems Creating Additional WebWare Data Collectors - Medium & Large Systems WebWare Server Database Setup for Microsoft SQL Server Installing ABB WebWare Client User Security Settings Download the Installation Files Overview Configuring System Components Overview Enabling the WebWare Interface - Small Systems Determining the IP Address of Robots on Your Network ABB Robot Configuration Procedures Connecting a Robot to a Data Collector Creating a Robot Profile Robot Aliases How to Add S4 Robot Alias How to Add IRC5 Robot Alias Connecting Other Device Types to a Data Collector Plant Model Checking System Status WebWare Server Module Overview

4 Table of Contents 3.2 WebWare Administration Overview Settings Page Devices Page Data Collector Setup Page Database Page How to Restore an Archived Database to a New Database Backup Page How to Configure Backup and Archive File Folder Names How to Configure IIS when Storing the Windows User Name in the Backup Log Reports Page License Management ABB Robotics License Management WebWare License Priority User Documentation Help Page Documentation Page How to Add Content to the Documentation Page WebWare Report Module Overview WebWare Data Collection & Monitoring Info Page Data Page WebWare Server Database Relocating a WebWare Database Creating a New WebWare Server Database Custom Database Tables How to Enable WebWare Reports for Custom Databases Data Events WebWare Data Event Editor WebWare Reports Reports Page Report Viewer Page Report Manager Page How to Build a Report Report Builder Page How to Edit Reports You've Created How to Run a Report How to Add an Existing Module to Your Report How to Create a Chart/Table Module How to Set Up Chart/Table Parameters How to Build a Database Query How to Use the Query Builder Page How to Apply Design-Time Options How to Apply Chart Options How to Apply Table Options HTML Module Overview How to Add an HTML Module to Your Report How to Export a Table to Excel How to Export Reports How to Import Reports How to Enable Log Filtering Service Page

5 Table of Contents How to configure Service Information System (SIS) for IRC Service Information System (SIS) Logs Report WebWare Backup Module Overview ABB WebWare Server & ABB Network File System Network File System (NFS) Overview How to Configure NFS at the Device Configuration Utility How to Configure an NFS Mount for an S4 Robot How to Configure an NFS Mount for an IRC5 Robot How to Restore Files from an NFS Mount Using the Robot Teach Pendant How to Restore Files from an NFS Mount Using the Robot Flex Pendant File Management Methods WebWare Backup Introduction How to Configure WebWare Backup How to Configure WebWare NFS Backup Backup Control Page How to Use On-Demand Backups Backup Tips Backup Status Messages Backup Schedule Page Schedule Manager Page How to Schedule Backups Backup Results Page How to Display Backup Results Backup Restore Page How to Use the WebWare File Manager How to Use the Restore Page How to Restore a Backup Using WebWare Backup Summary Page WebWare Ramdisk Mirror Introduction How to Set Up a Data Collector as a Ramdisk Mirror WebWare Visual SourceSafe Module Overview Configuring WebWare Visual SourceSafe Module WebWare Visual SourceSafe Module Screen Components Retrieving Latest File Version from Visual SourceSafe Retrieving Selected File Version from Visual SourceSafe Viewing File Differences Assigning File Types in Visual SourceSafe System Reference Overview Custom Web Site Configuration Procedures Overview General Installation Process Installing Internet Information Services (IIS) Enabling Administrative Tools in Start Menu Accessing the IIS Management Console Configuring IIS to Host WebWare as a Virtual Directory Selecting the Default Document Enabling Execute Permissions for WWBin

6 Table of Contents Running the.net Installation Utility Configuring IIS with Personal Web Manager Custom Installation Procedures Configuring IIS to Host WebWare as a Default Web Site Installed Files and Folders Windows Service Pack Issues Overview ABB WebWare Security Settings Utility Windows Firewall Settings DCOM Configuration WebWare RAPID Module WebWare RAPID Module (WebWare.sys) Controlling WebWare Backup from WebWare.sys RAPID Instructions WWRestore Instruction WebWare RAPID Restore Procedure WWStartBackup Instruction WWIncrCounter Instruction WWStartTimer Instruction WWStopTimer Instruction WWLogTimedEvent Instruction WWSetProgramInfo Instruction WWSetLabels Instruction WWSetField Instruction WebWare Server Link State Heartbeat Function Return Status Codes Return Status Codes RPC Communications Errors InterLink Module Communication Errors General Error Messages InterLink FTP Error Codes InterLink Error Code Definitions InterLink Monitor Connecting Failure Variable Handling Error Messages Program Handling Error Messages File Handling Error Messages Configuration Handling Error Messages Log Error Messages WebWare Server Error Codes Null Modem Cable Diagrams RS-232 Cable Diagrams S4 Controller Diagrams Installing WebWare Server with RobotStudio, QuickTeach or ProgramMaker Overview

7 Overview 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 1. Welcome to WebWare Server 2. Get Started with WebWare Server 3. WebWare Server Module 4. WebWare Report Module Contents Introduction to WebWare Server and network topology. 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. How to administer WebWare Server. 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. Continues on next page 7

8 Overview Continued Chapter 5. WebWare Backup Module Contents 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. References Reference - Document Id Revisions Revision Description - First release A B Released with WebWare

9 What s New In This Release 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. 9

10 Glossary Glossary Important Terms The table below defines terms as we will use them in describing concepts in WebWare products. Term Alarms Alias Backup file set BaseWare Counters Data Collector Data Event Data Source Name (DSN) Default Web Site Device Configuration Utility (DCU) Event Log Events Extensible Markup Language (XML) Hypertext Transfer Protocol (HTTP) Hypertext Markup Language (HTML) InterLink Module Definition OPC events that indicate a problem with some part of the system. OPC alarms include several conditions, including type, severity, state, name, etc. The named instance of a robot controller accessed by InterLink. The list of files, robot program modules, log files, etc. that you selected for backup from a robot controller. ABB robot controller operating system software. 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. 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. The WebWare Data Event Editor allows you to increment WebWare counters or start and stop WebWare timers based on an OPC tag s state. 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. A default web site is the first site that will appear when a browser is pointed to where hostname is the name of the server PC. Program that allows users to configure robot aliases and profiles for use in the WebWare system. File that stores event messages from the robot. Something that happens. In WebWare, typical events include StatusChanged events, Help events etc. 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 information. Protocol used for transferring files (text, graphic images, sound, video, and other multimedia files) on the World Wide Web. The set of markup symbols or codes inserted in a file intended for display on a World Wide Web browser page. The ABB InterLink Module provides the core communications support needed for ABB WebWare products. 10 Continues on next page

11 Glossary Continued Term InterLink Monitor InterLink Service IP Address License Key License Request Linked Alias Log messages Microsoft Message Queue Server (MSMQ) Network File System (NFS) Open Database Connectivity (ODBC) OLE for Process Controls (OPC) OPC Device OPC Server Persistent Variables Definition Utility program that allows users to monitor the connection status of devices connected to the WebWare network. 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. 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 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. 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. An additional application or device connected to the same Robot alias on a WebWare network. Individual error or event messages that are grouped into a log file. 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. 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. An open standard application programming interface (API) for accessing a database. 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 Any Object Linking and Embedding (OLE) for Process Controls (OPC) compliant device. Devices could include PLC s, HMI devices etc. The OPC Server is an ABB software product that provides an interface to all robot controllers using the OLE for Process Controls (OPC) specification. In RAPID, a variable that keeps its value between sessions. Continues on next page 11

12 Glossary Continued Term Poll delay Profile Ramdisk Robot Application Protocol (RAP) RAPID Robot Alias Robot modules Service Simulated Interface SQL Server Structured Query Language (SQL) Tags Task scheduler Transfer Control Protocol (TCP) Timers Uniform or Universal Resource Locator (URL) Virtual Directory Definition 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. A profile is a group of properties and parameters that determine the behavior of a robot alias. In an ABB robot controller, a memory device located in the controller s RAM. Provides an application interface to the ABB Robot Controllers. RAP provides a set of services that you can use to control and monitor ABB Robots from an external computer. Programming language used to program ABB robots. The naming device used by InterLink to refer to a designated device on the WebWare network. 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 A program, routine, or process that performs a specific system function to support other programs, particularly at a low (close to the hardware) level. 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. 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. SQL is a standard interactive and programming language for getting information from and updating a database. 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. A Windows utility that can run a script, program or document at a pre-selected time, either on a one-time or repeating basis. A protocol used along with the Internet Protocol (IP) to send data in the form of message units between computers over the Internet. 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. An address that uniquely identifies a location on the Internet. A URL for a World Wide Web site is preceded with as in the fictitious URL A URL can contain more detail, such as the name of a page of hypertext, usually identified by the file name extension.html or.htm. A virtual directory is addressed as where vdir is the name of the virtual directory created by the site administrator. 12 Continues on next page

13 Glossary Continued Term Visual SourceSafe (VSS) WebWare WebWare Backup WebWare Server WebWare Server host machine WebWare WebClient Definition A source code repository program from Microsoft used to store and maintain version control of software components. 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. A WebWare utility that backs up a robot program or selected robot modules. 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. The computer that is the WebWare Server host computer. The machine where WebWare Server software is installed. Software that allows a remote computer to browse to the WebWare Server web site. Requires Windows Internet Explorer. 13

14 Glossary 14

15 1 Welcome to WebWare Server 1.1. What is WebWare Server? 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. 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 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 offline 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. Continues on next page 15

16 1 Welcome to WebWare Server 1.1. What is WebWare Server? Continued 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 WebWare continuously monitors connected equipment, logging diagnostic information. By storing this information external to the equipment, it is readily available to local and remote users. Even if the production system is down, remote experts have access to the information through their web browser. 16

17 1 Welcome to WebWare Server 1.2. WebWare Server Network Topology 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. WebWare Server Data Collector xx 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. 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. Continues on next page 17

18 1 Welcome to WebWare Server 1.2. WebWare Server Network Topology Continued 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 Local PC Remote PC 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. 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 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. File Device The File Device depicted in the topology diagram denotes any FTP server or NFS mount that can be accessed by WebWare Server for example. 18

19 1 Welcome to WebWare Server 1.3. Information Flow and Timing 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 realtime 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. xx The following diagram depicts the key functional blocks needed to understand the WebWare Server communication architecture. xx 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. Continues on next page 19

20 1 Welcome to WebWare Server 1.3. Information Flow and Timing Continued 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 work if the Data Collector is currently connected to the server. If the Data Collector is not connected, WebWare Server does not attempt to address the robot controller. 20 Continues on next page

21 1 Welcome to WebWare Server 1.3. Information Flow and Timing Continued 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. 21

22 1 Welcome to WebWare Server 1.3. Information Flow and Timing 22

23 2 Get Started with WebWare Server 2.1. Get Started 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. 23

24 2 Get Started with WebWare Server 2.2. WebWare Server Implementation Plan 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. 7. Configure the devices in the system to communicate with WebWare Server. 24

25 2 Get Started with WebWare Server 2.3. WebWare Server Installation Checklist 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 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: Continues on next page 25