WebWare Server Database - 4 WebWare Report Module

4 WebWare Report Module

4.2.3. WebWare Server Database

135 3HAC031359-001 Revision: B

4.2.3. WebWare Server Database

Introduction

WebWare Server preserves historical data in the WebWare Server database. The database is a Microsoft SQL database that is automatically built the first time WebWare Server is started.

For more information on the differences between the MSDE and SQL 2000 Server, see Microsoft SQL Server on page 37.

The database contains a list of all of the attached robot controllers and WebWare Client applications. This information is used to populate the WebWare Client user interface navigation tree. The database also contains several types of information specific to WebWare Server. The following sections describe the different types of information stored in the WebWare Server database.

WebWare Server automatically creates a system ODBC Data Source Name (DSN) labeled

“WebWare Database”. The DSN allows custom web pages to connect to the WebWare Database.

Log Messages

WebWare Server saves events and errors messages received from robot controllers and WebWare Client Applications as log messages. The fields that make up a log message are described as follows:

Field Definition

Robot Name This is the name of the WebWare device generating the log message.

Log This is the number that identifies which log triggered the event. These are the log numbers used by both the S4 control and the WebWare ActiveX controls.

For more information on error codes generated by WebWare Server see WebWare Server Error Codes on page 338.

LogType This is the number that identifies the type of the log event. The possible types are as follows:

1. State Change 2. Warning 3. Error

Continues on next page

4.2.3. WebWare Server Database

Counters

The WebWare Server database includes a generic counter. WebWare counters are used to count event occurrences over a given time frame. RAPID programs and WebWare SDK Applications create counter records by calling a counter increment function with the counter name. WebWare creates counter records for each counter and increments the value given.

Counter resolution must be considered very carefully in relation to several factors. Setting a counter resolution to a low number may result in fast database growth. The default, recommended resolution value is 60 minutes. The time frame for counters is set from the Counter Resolution panel of the Reports Page on page 116 of the WebWare Server web site.

Counter records are ideal for counting things like Parts Per Hour or Failures Per Hour. The counter data can also be summed in a database query to produce reports like Parts Per Shift or Part Per Week.

The WebWare Server database counter fields are described as follows:

See also WWIncrCounter Instruction on page 309.

Timers

The WebWare Server database includes a generic timer record concept. WebWare timers are used to time events such as cycle time, squeeze time, hold time, etc. RAPID programs and WebWare SDK Applications create timer records by calling the StartTime, StopTime, and LogTimedEvent functions specifying the timer name used to identify the timer record.

Each timer record represents a single timed event. If you are tracking Cycle Time, you’ll get a new timer record for each recorded cycle.

The WebWare Server database timer fields are described as follows:

LogNumber This is the log event number. The log events numbers vary with every logging function.

LogText This is a string containing lines of text used to identify the log event.

Field Definition

Robot Name This is the name of the WebWare device managing the counter.

Counter Name This is the name of the counter.

Value This is the current counter value for the specified time frame.

Time This is the time and date for a given counter record. Counter times are always specified as the starting time of a specified time frame. e.g. 1/11/00 2:00:00 PM.

Field Definition

Robot Name This is the name of the WebWare device writing the timer record.

Continued

4.2.3. WebWare Server Database

137 3HAC031359-001 Revision: B

See also WWStartTimer Instruction on page 311, WWStopTimer Instruction on page 313 and WWLogTimedEvent Instruction on page 315.

OPC Alarm Tables

WebWare tracks the following OPC alarms and conditions:

Backup Log

WebWare tracks the following backup system events:

Alias Backup Log

WebWare tracks the state of the backup status according to the aliases in the system as shown below.

Duration MS This is the duration of the timed event in milliseconds. This is only calculated when the End Time field is written.

Field Definition

Source This is the name of the alarm.

Message This is the event notification message sent along with the alarm.

Time This is the time that the alarm occurred.

Event Type 1. Simple event

2. Tracking event

3. Condition-related event

Event Category Displays whether the event is standard or vendor specific.

Severity Displays a severity range from 0 to 1000, with 0 being the most severe.

State This is the new state of an OPC condition.

Name This is the OPC condition name.

SubName This is the name of the current sub-condition, for multi-state conditions.

Quality This is the quality associated with the condition state.

Active Time This is the time that the OPC condition became active.

Field Definition

User Name Name of the user who started the backup.

Scheduled If the schedule process started the backup.

Start Time The time the backup was started.

Type 1. Backup all devices

2. Backup selected devices

Field Definition

Device Name Name of device

Backup ID Backup Identification

Result The result of the backup attempt for the given device. For complete information on these states see Backup Status Messages on page 232.

Continued

Continues on next page

4.2.3. WebWare Server Database

Push Result Indicates whether InterLink was able to pass backup file set to WWService, see Return Status Codes on page 321.

Project Name The project that was backed up.

User Cancel The name of the user who cancelled the backup.

Date Complete The time and date that the backup requested completed.

Full Program Request 0/1 whether backup configuration had“ Standard backup”

checked.

Full Program Status Indicate whether full program request was successful. See Return Status Codes on page 321.

Program Request 0/1 whether backup configuration had RAPID checked Program Status Indicates whether Program backup was successful. See

Return Status Codes on page 321.

Modules Total The number of Modules backup configuration had set when

“RAPID” was checked.

Modules Written Number of Modules written.

System Params Total The number of System Params backup configuration had set when “Parameters” checked.

System Params Written Number of System Parameters written.

Ramdisk Whether backup configuration had “Ramdisk” checked.

Ramdisk Total Total number of files on Ramdisk.

Ramdisk Written Number of Ramdisk files backed up.

Log Total The number of Log backup configuration had set when “Event Logs” is checked.

Log Written Number of Log Files backed up.

Device Name The name of the device that had the error.

Backup ID Backup Identification.

File Name The name of the file that failed.

File Type A number indicating the type of backup the file was included in:

0. Unknown Error

1. Error backing up programs 2. Error during full backup

3. Error backing up program modules 4. Error backing up system parameters 5. Error backing up log files

6. Error during file push

7. Error backing up robot ramdisk Result Code See Return Status Codes on page 321.

Date The time and date the error occurred.

Field Definition

Continued

In document Administrator s Guide WebWare Server (Page 135-139)