Tivoli Self-Service Terminal Manager User’s Guide - IBMpublib.boulder.ibm.com/tividd/td/SSTM/GC32-0653-00/... · responsibility of the user. Tivoli Systems or IBM may have patents

Tivoli®

Self-ServiceTerminal Manager User’s GuideVersion 1.0

Tivoli®

Self-ServiceTerminal Manager User’s GuideVersion 1.0

Tivoli Self-Service Terminal Manager User’s Guide

Copyright Notice

© Copyright IBM Corporation 2000. All rights reserved. May only be used pursuant to aTivoli Systems Software License Agreement, an IBM Software License Agreement, orAddendum for Tivoli Products to IBM Customer or License Agreement. No part of thispublication may be reproduced, transmitted, transcribed, stored in a retrieval system, ortranslated into any computer language, in any form or by any means, electronic, mechanical,magnetic, optical, chemical, manual, or otherwise, without prior written permission of IBMCorporation. IBM Corporation grants you limited permission to make hardcopy or otherreproductions of any machine-readable documentation for your own use, provided that eachsuch reproduction shall carry the IBM Corporation copyright notice. No other rights undercopyright are granted without prior written permission of IBM Corporation. The document isnot intended for production and is furnished “as is” without warranty of any kind.Allwarranties on this document are hereby disclaimed, including the warranties ofmerchantability and fitness for a particular purpose.

U.S. Government Users Restricted Rights-Use, duplication or disclosure restricted by GSAADP Schedule Contract with IBM Corporation.

Trademarks

IBM, Tivoli, the Tivoli logo, AIX, IBMLink, Tivoli Enterprise Console, and TME aretrademarks or registered trademarks of International Business Machines Corporation or TivoliSystems Inc. in the United States, other countries, or both.

Microsoft, Windows, Windows NT, and the Windows logo are trademarks of MicrosoftCorporation in the United States, other countries, or both.

UNIX is a registered trademark of The Open Group in the United States and other countries.

Other company, product, and service names may be trademarks or service marks of others.Notices

References in this publication to Tivoli Systems or IBM products, programs, or services donot imply that they will be available in all countries in which Tivoli Systems or IBMoperates. Any reference to these products, programs, or services is not intended to imply thatonly Tivoli Systems or IBM products, programs, or services can be used. Subject to validintellectual property or other legally protectable right of Tivoli Systems or IBM, anyfunctionally equivalent product, program, or service can be used instead of the referencedproduct, program, or service. The evaluation and verification of operation in conjunction withother products, except those expressly designated by Tivoli Systems or IBM, are theresponsibility of the user. Tivoli Systems or IBM may have patents or pending patentapplications covering subject matter in this document. The furnishing of this document doesnot give you any license to these patents. You can send license inquiries, in writing, to theIBM Director of Licensing, IBM Corporation, North Castle Drive, Armonk, New York10504-1785, U.S.A.

Contents

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ixWho Should Read This Guide. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix

Prerequisite and Related Documents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix

What This Guide Contains. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x

Conventions Used in This Guide. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi

Terminology. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii

Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii

Accessing Publications Online. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xiii

Ordering Publications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xiii

Providing Feedback about Publications. . . . . . . . . . . . . . . . . . . . . . . . . . . . xiv

Contacting Customer Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiv

Chapter 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1Tivoli Management Framework. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Event Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Distributed Monitors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Inventory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Operations Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Software Distribution. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Chapter 2. Planning and Installing . . . . . . . . . . . . . . . . . . . . . . . . 7Planning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Installation and Configuration Overview. . . . . . . . . . . . . . . . . . . . . . . . 8

XFS Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Tivoli Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Operating Systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Hardware Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

iiiTivoli Self-Service Terminal Manager User’s Guide

Installing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Installing from the Desktop. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Installing from the Command Line. . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Installing with the Software Installation Service. . . . . . . . . . . . . . . . . . 14

Installing Missing Resources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Removing the Product. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Chapter 3. Getting Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Navigating the Desktop. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Configuring Self-service Terminals. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Distributing the SST_XFS_Configuration Profile from the Desktop . . . 23

Distributing the SST_XFS_Configuration Profile from the CommandLine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Accessing Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Opening the SST_XFS_Tasks Task Library. . . . . . . . . . . . . . . . . . . . . 26

Rebooting a Self-service Terminal. . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Chapter 4. Managing Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29Setting Up the Event Server and Event Adapter. . . . . . . . . . . . . . . . . . . . . . 29

Configuring the Event Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Configuring and Distributing the Event Adapter. . . . . . . . . . . . . . . . . . 31

Displaying Events. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Filtering Events. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Filtering Events at the Self-service Terminal. . . . . . . . . . . . . . . . . . . . 37

Filtering Events at the Event Adapter. . . . . . . . . . . . . . . . . . . . . . . . . . 38

Filtering Events at the Event Console. . . . . . . . . . . . . . . . . . . . . . . . . 38

Chapter 5. Monitoring Resources . . . . . . . . . . . . . . . . . . . . . . . 39Using Monitoring Profiles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Using the SST_XFS_Monitors Profile. . . . . . . . . . . . . . . . . . . . . . . . . 40

iv Version 1.0

Creating a New Monitoring Profile and Indicator Collection. . . . . . . . . 41

Adding and Defining Monitors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Adding and Defining Monitors from the Desktop. . . . . . . . . . . . . . . . . 42

Adding and Defining Monitors from the Command Line. . . . . . . . . . . 43

Distributing Monitoring Profiles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Distributing a Monitoring Profile from the Desktop. . . . . . . . . . . . . . . 44

Distributing a Monitoring Profile from the Command Line. . . . . . . . . . 45

Determining Which Monitors Have Been Distributed or Enabled. . . . . . . . . 46

Using the SST_XFS_Indicator Indicator Collection. . . . . . . . . . . . . . . . . . . 46

Viewing Monitor Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Chapter 6. Using Inventory Information . . . . . . . . . . . . . . . . . 51Configuring the Inventory Configuration Repository. . . . . . . . . . . . . . . . . . . 51

Configuring the DB2 Configuration Repository. . . . . . . . . . . . . . . . . . 52

Configuring the Informix Configuration Repository. . . . . . . . . . . . . . . 53

Configuring the MS SQL Configuration Repository. . . . . . . . . . . . . . . 53

Configuring the Oracle Configuration Repository. . . . . . . . . . . . . . . . . 54

Configuring the Sybase Configuration Repository. . . . . . . . . . . . . . . . 54

Moving the SST_XFS_Queries Query Library. . . . . . . . . . . . . . . . . . . . . . . 55

Using Inventory Profiles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Using the SST_XFS_Inventory Profile. . . . . . . . . . . . . . . . . . . . . . . . . 56

Creating a New Inventory Profile. . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Distributing Inventory Profiles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Distributing an Inventory Profile from the Desktop. . . . . . . . . . . . . . . 59

Distributing an Inventory Profile from the Command Line. . . . . . . . . . 60

Querying the Inventory Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Querying All Self-service Terminal Inventory Information. . . . . . . . . . 60

Querying Inventory Information for a Single Self-service Terminal. . . . 61

vTivoli Self-Service Terminal Manager User’s Guide

Chapter 7. Distributing Software . . . . . . . . . . . . . . . . . . . . . . . . 63Creating Software Packages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Distributing Software Packages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

Distributing a File Package from the Desktop. . . . . . . . . . . . . . . . . . . 64

Distributing a File Package from the Command Line. . . . . . . . . . . . . . 65

Appendix A. Event Classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67Monitor Event Classes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

Status Event Classes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Camera Event Classes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

Cash Dispenser Event Classes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

Depository Event Classes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

ID Card Reader Event Classes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

PIN Pad Event Classes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

Printer Event Classes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

Sensor Event Classes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

Vendor-Dependent-Mode Event Classes. . . . . . . . . . . . . . . . . . . . . . . . 78

Event Slots for Status Events. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

Default Event Filtering. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

Appendix B. Monitoring Collection . . . . . . . . . . . . . . . . . . . . . . 81CLI Names. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

Monitor Sources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

General Monitor Sources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

Printer Monitor Sources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

Cash Dispenser Monitor Sources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

Depository Monitor Sources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

Sensor Monitor Sources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

Camera Monitor Sources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

vi Version 1.0

ID Card Reader Monitor Sources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

PIN Pad Monitor Sources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

Text Terminal Unit Monitor Sources. . . . . . . . . . . . . . . . . . . . . . . . . . 94

Check Reader Monitor Sources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

Appendix C. Inventory Tables, Views, and Queries . . . . 97Camera Capabilities and Status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

Cash Dispenser Capabilities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

Cash Dispenser Logical Cash Unit Capabilities and Status. . . . . . . . . . . . . 100

Cash Dispenser Physical Cash Unit Capabilities and Status. . . . . . . . . . . . 101

Cash Dispenser Status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

Check Reader Capabilities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102

Check Reader Status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

Depository Capabilities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

Depository Status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

ID Card Reader Capabilities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

ID Card Reader Status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

PIN Pad Capabilities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

PIN Pad Status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108

Printer Capabilities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

Printer Status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

Sensor Capabilities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110

Sensor Status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

Text Terminal Capabilities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

Text Terminal Status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

Appendix D. Service Classes and Aliases . . . . . . . . . . . . . 115

Appendix E. Finding and Correcting Problems . . . . . . . . 119

viiTivoli Self-Service Terminal Manager User’s Guide

Common Troubleshooting Techniques. . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

Checking a Self-service Terminal. . . . . . . . . . . . . . . . . . . . . . . . . . . . 120

Checking the TMR Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

Checking Connectivity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

Troubleshooting Event Management Problems. . . . . . . . . . . . . . . . . . . . . . 122

Checking Event Management Problems at the Self-service Terminal 122

Checking the Event Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123

Troubleshooting Monitoring Problems. . . . . . . . . . . . . . . . . . . . . . . . . . . . 124

Troubleshooting Inventory Problems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125

Troubleshooting Software Distribution Problems. . . . . . . . . . . . . . . . . . . . 126

Checking RIM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126

Appendix F. Error Codes and Logging . . . . . . . . . . . . . . . . . 127Monitoring Error Codes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127

Event Service Logging. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137

viii Version 1.0

Preface

This document provides information about planning, installing, andusing Tivoli

®

Self-Service Terminal Manager.

Who Should Read This GuideThis guide is for system administrators and others who use TivoliSelf-Service Terminal Manager to manage Windows NT

®

self-serviceterminals that use the eXtensions for Financial Services (XFS)interface specification Release 2.0, referred to in this document asWindows NT XFS self-service terminals.

You should have knowledge of:¶ Windows NT XFS self-service terminals¶ Tivoli Management Framework¶ Tivoli Software Distribution¶ Tivoli Enterprise Console

®

¶ Tivoli Distributed Monitoring¶ Tivoli Inventory¶ Database and Structured Query Language (SQL) concepts

Prerequisite and Related DocumentsFor the latest hardware and software requirements and otherlate-breaking information, refer to theTivoli Self-Service TerminalManager Release Notes.

Related documents include:¶ TME 10 Distributed Monitoring User’s Guide, Version 3.6

(GC31-8382)¶ TME 10 Enterprise Console Adapters Guide, Version 3.6

(SC31-8507)¶ TME 10 Enterprise Console Reference Guide, Version 3.6

(SC31-8505)¶ TME 10 Enterprise Console User’s Guide, Version 3.6

(GC31-8506)¶ TME 10 Enterprise Console Rule Builder’s Guide, Version 3.6

(SC31-8508)

ixTivoli Self-Service Terminal Manager User’s Guide

¶ TME 10 Framework Planning and Installation Guide, Version3.6 (SC31-8432)

¶ TME 10 Framework Reference Manual, Version 3.6 (SC31-8434)¶ TME 10 Framework User’s Guide, Version 3.6 (GC31-8433)¶ TME 10 Inventory User’s Guide, Version 3.6 (GC31-8381)¶ TME 10 Software Distribution Reference Manual, Version 3.6

(SC31-8331)¶ TME 10 Software Distribution User’s Guide, Version 3.6

(GC31-8330)¶ TME 10 Software Installation Service User’s Guide, Version 3.6

(GC31-5121)

For more information about the XFS interface specification, go tothis Web site: http://www.cenorm.be/isss/Workshop/XFS/

Documents that can be used for troubleshooting are:¶ TME 10 Internals and Problem Determination(SG24-2034)¶ Using Databases with Tivoli Applications and RIM(SG24-5112)

For definitions of technical terms, see theTivoli Software Glossaryatthis Web site:http://www.tivoli.com/support/documents/glossary/termsm03.htm

What This Guide ContainsThis guide contains the following sections:

¶ “Introduction” on page 1 describes the self-service terminalmanagement capabilities provided by Tivoli Self-ServiceTerminal Manager.

¶ “Planning and Installing” on page 7 describes planningconsiderations and installation procedures for Tivoli Self-ServiceTerminal Manager.

¶ “Getting Started” on page 19 describes tasks that you mustcomplete before using Tivoli Self-Service Terminal Manager.

¶ “Managing Events” on page 29 describes how to use TivoliSelf-Service Terminal Manager with Tivoli Enterprise Console tomanage self-service terminal events.

x Version 1.0

http://www.cenorm.be/isss/Workshop/XFS/

http://www.tivoli.com/support/documents/glossary/termsm03.htm

¶ “Monitoring Resources” on page 39 describes how to use TivoliSelf-Service Terminal Manager with Tivoli DistributedMonitoring to monitor resources for self-service terminals.

¶ “Using Inventory Information” on page 51 describes how to useTivoli Self-Service Terminal Manager with Tivoli Inventory tocollect and query inventory information for self-serviceterminals.

¶ “Distributing Software” on page 63 describes how to use TivoliSoftware Distribution to distribute software to self-serviceterminals.

¶ “Event Classes” on page 67 describes the event classes forTivoli Self-Service Terminal Manager.

¶ “Monitoring Collection” on page 81 describes the monitoringsources for Tivoli Self-Service Terminal Manager.

¶ “Inventory Tables, Views, and Queries” on page 97 describes theinventory tables, views, and queries provided with TivoliSelf-Service Terminal Manager.

¶ “Service Classes and Aliases” on page 115 describes the use ofnon-XFS-standard service class names.

¶ “Finding and Correcting Problems” on page 119 provides helpon debugging problems.

¶ “Error Codes and Logging” on page 127 describes the messagesand logging for Tivoli Self-Service Terminal Manager.

Conventions Used in This GuideThis guide uses several typeface conventions for special terms andactions. These conventions have the following meaning:

Bold Commands, keywords, flags, and other informationthat you must use literally appear inbold.

Italics Variables and values that you must provide appear initalics. Words and phrases that are emphasized alsoappear initalics.

xiTivoli Self-Service Terminal Manager User’s Guide

Monospace Code examples, output, and system messages appearin monospace.

This guide generally uses the UNIX®

convention for specifyingenvironment variables and for directory notation. When using theWindows NT command line, replace $variable with %variable% forenvironment variables and replace each forward slash (/) with abackslash (\) in directory paths.

Note: When using the bash shell on a Windows NT system, you canuse the UNIX conventions.

These special characters are used to define command syntax:

[ ] Identifies optional arguments. Arguments not enclosed inbrackets are required.

... Indicates that you can repeat the previous argument orspecify multiple values for the previous argument.

| Indicates mutually exclusive information. You can use theargument to the left or to the right of the separator. Youcannot use both arguments in a single use of the command.

{ } Limits a set of mutually exclusive arguments when one ofthe arguments is required. If the arguments are optional, theyare enclosed in [ ] (brackets).

TerminologyTivoli is in the process of changing product names. Products referredto in this document could still be available under their old names,for example, TME

®

10 Enterprise Console instead of TivoliEnterprise Console.

DocumentationDocumentation files are provided on the Tivoli Self-Service TerminalManager CD in the /doc directory. Files containing theTivoliSelf-Service Terminal Manager User’s Guide(sstug.pdf andsstug.htm) and theTivoli Self-Service Terminal Manager Release

xii Version 1.0

Notes(sstrn.pdf and sstrn.htm) are provided. Use Adobe AcrobatReader to view or print the PDF files and a browser to view or printthe HTML files.

Accessing Publications OnlineThe Tivoli Customer Support Web site(http://www.tivoli.com/support/) offers a guide to support services(the Customer Support Handbook); frequently asked questions(FAQs); and technical information, including release notes, user’sguides, redbooks, and white papers. Go tohttp://www.tivoli.com/support/documents/ to access Tivolipublications online. The documentation for some products isavailable in PDF and HTML formats. Translated documents are alsoavailable for some products.

To access most of the documentation, you need an ID and apassword. Go to http://www.tivoli.com/support/getting/ to obtain anID for use on the support Web site.

Resellers should refer tohttp://www.tivoli.com/support/smb/index.html for more informationabout obtaining Tivoli technical documentation and support.

Business Partners should refer to “Ordering Publications” for moreinformation about obtaining Tivoli technical documentation.

Ordering PublicationsOrder Tivoli publications online athttp://www.tivoli.com/support/Prodman/html/pub_order.html or bycalling one of the following telephone numbers:¶ U.S. customers: (800) 879-2755¶ Canadian customers: (800) 426-4968

xiiiTivoli Self-Service Terminal Manager User’s Guide

http://www.tivoli.com/support/

http://www.tivoli.com/support/documents/

http://www.tivoli.com/support/getting/

http://www.tivoli.com/support/smb/index.html

http://www.tivoli.com/support/Prodman/html/pub_order.html

Providing Feedback about PublicationsWe are very interested in hearing about your experience with Tivoliproducts and documentation, and we welcome your suggestions forimprovements. If you have comments or suggestions about ourproducts and documentation, contact us in one of the followingways:

¶ Send e-mail to [email protected]

¶ Fill out our customer feedback survey at this Web site:http://www.tivoli.com/support/survey/

Contacting Customer SupportIf you need support for this or any Tivoli product, contact TivoliCustomer Support in one of the following ways:

¶ Submit a problem management record (PMR) electronically fromour http://www.tivoli.com/support/reporting/ Web site. Go tohttp://www.tivoli.com/support/getting/ for information aboutobtaining support through the Tivoli Customer Support Web site.

¶ Submit a PMR electronically through the IBMLink™ system. Forinformation about IBMLink registration and access, refer to thisIBM Web page: http://www.ibmlink.ibm.com

¶ Send e-mail to [email protected]

¶ Customers in the U.S. can call 1-800-TIVOLI8(1-800-848-6548).

¶ Customers outside the U.S. should refer to the Tivoli CustomerSupport Web site at http://www.tivoli.com/support/locations.htmlfor customer support telephone numbers.

When you contact Tivoli Customer Support, be prepared to providethe customer number for your company so that support personnelcan assist you more readily.

xiv Version 1.0

http://www.tivoli.com/support/survey/

http://www.tivoli.com/support/reporting/

http://www.tivoli.com/support/getting/

http://www.ibmlink.ibm.com

http://www.tivoli.com/support/locations.html

Introduction

Tivoli Self-Service Terminal Manager provides a centralized systemmanagement tool on the Tivoli platform for Windows NTself-service terminals that use the eXtensions for Financial Services(XFS) interface specification Release 2.0. These self-serviceterminals, which are referred to in this document as Windows NTXFS self-service terminals, are self-service devices such asautomated teller machines, ticket dispensers, and data terminals.

In providing integration of Windows NT XFS self-service terminalswith the Tivoli Management Framework, Tivoli Self-ServiceTerminal Manager enables:¶ Managing of self-service terminal events (see “Event

Management” on page 2)¶ Centralized monitoring of self-service terminals (see “Distributed

Monitors” on page 3)¶ Collecting and querying of inventory information for self-service

terminals (see “Inventory” on page 4)¶ Rebooting of self-service terminals (see “Operations

Management” on page 5)

You can also distribute software to your self-service terminals (see“Software Distribution” on page 5).

1

1Tivoli Self-Service Terminal Manager User’s Guide

1.Introduction

Tivoli Management FrameworkThe Tivoli Management Framework is a powerful and flexibleframework for developing a comprehensive management system. Itis the foundation for the Tivoli environment, which enablesadministrators to manage the enterprise from one interface and toautomate and delegate routine tasks. The Tivoli ManagementFramework provides task libraries, profiles, a graphical interface (theTivoli desktop), and command line interface (CLI) commands tomanage the resources within an enterprise. The Tivoli ManagementFramework also provides administrative security in the form ofauthorization roles.

Tivoli Self-Service Terminal Manager integrates your self-serviceterminals into this framework and into the Tivoli environment byproviding extensions to existing Tivoli applications to enablecommunication with Windows NT XFS self-service terminals. Inaddition, Tivoli Self-Service Terminal Manager provides policyregions, default profiles and profile managers, a query library, a tasklibrary, and a monitoring indicator collection to help you get started.

For more information about the Tivoli Management Framework,refer to theTME 10 Framework User’s Guide.

Event ManagementTivoli Self-Service Terminal Manager integrates with the TivoliEnterprise Console to provide a consolidated display for yourself-service terminal events. Tivoli Enterprise Console is a powerful,rules-based event management application that integrates network,systems, database, and application management. It offers acentralized, global view of your computing enterprise while ensuringthe high availability of your application and computing resources. Itcollects, processes, and automatically responds to commonmanagement events and acts as a central collection point for alarmsand events from a variety of sources. Event consoles areconfigurable and can be created and configured for any number of

2 Version 1.0

administrators. Tivoli Enterprise Console also provides a rule builderfor developing rules to correlate and provide automated responses toevents.

Tivoli Self-Service Terminal Manager enables you to monitor andretrieve events from self-service terminals. These events areconverted to the Tivoli Enterprise Console event format andforwarded to a centralized event server for display and processing.You can specify events that you do not want forwarded to the eventserver. This filtering prevents the event server from being populatedwith harmless events and enables you to focus on events of interest.

For more information about event management for self-serviceterminals, see “Managing Events” on page 29. For information aboutthe event classes provided with Tivoli Self-Service TerminalManager, see “Event Classes” on page 67.

Note: Tivoli Enterprise Console must be installed to enable theTivoli Self-Service Terminal Manager event managementfunctions. For more information about Tivoli EnterpriseConsole, refer to theTME 10 Enterprise Console User’sGuide.

Distributed MonitorsTivoli Self-Service Terminal Manager integrates with TivoliDistributed Monitoring to provide monitoring of your self-serviceterminal peripheral devices. Tivoli Distributed Monitoring enablescentralized monitoring of remote resources, generation of events andalarms, automated responses to events and alarms, and fullintegration with the Tivoli Enterprise Console event server.

In addition to the standard Windows NT monitors, the TivoliSelf-Service Terminal Manager monitor collection offers a widerange of monitors that check the status of self-service terminalperipheral devices, such as cash dispensers, printers, anddepositories. All of the monitor configuration options, such asseverity levels and thresholds, can be individually selected andcustomized using the Tivoli Distributed Monitoring interface. A


1.Introduction

default profile manager and a monitor indicator collection, whichreside in the Tivoli Self-Service Terminal Manager policy region,enable you to get started quickly.

For more information about monitoring self-service terminals, see“Monitoring Resources” on page 39. For information about themonitoring collection provided with Tivoli Self-Service TerminalManager, see “Monitoring Collection” on page 81.

Note: Tivoli Distributed Monitoring must be installed to enable theTivoli Self-Service Terminal Manager monitoring functions.For more information about Tivoli Distributed Monitoring,refer to theTME 10 Distributed Monitoring User’s Guide.

InventoryTivoli Self-Service Terminal Manager integrates with TivoliInventory to enable you to gather and maintain up-to-date inventoryinformation for your self-service terminals. Tivoli Self-ServiceTerminal Manager enables you to gather inventory information aboutself-service terminal peripheral devices, such as cash dispensers,printers, and depositories. You can store the information in yourcentralized inventory database. By regularly collecting and storinginventory information and by running queries and reports to displaythe information in the database, you can monitor the capabilities andstatus of your self-service terminal peripheral devices from a centralpoint.

Tivoli Self-Service Terminal Manager provides a specialized scannerto collect inventory information for your self-service terminalperipheral devices. The information collected includes both thecapabilities of the self-service terminal peripheral devices and theircurrent supply or accumulation levels. It extends the Inventorydatabase to provide specialized tables and views for the self-serviceterminal resources.

For more information about using inventory information forself-service terminals, see “Using Inventory Information” on page 51.For information about the inventory tables, views, and queries

4 Version 1.0

provided with Tivoli Self-Service Terminal Manager, see “InventoryTables, Views, and Queries” on page 97.

Note: Tivoli Inventory must be installed to enable the TivoliSelf-Service Terminal Manager inventory functions. For moreinformation about Tivoli Inventory, refer to theTME 10Inventory User’s Guide.

Operations ManagementTivoli Self-Service Terminal Manager provides a task in a policyregion on the Tivoli desktop that enables you to reboot a self-serviceterminal. It also provides default profiles and profile managers in thepolicy region to get you started with managing your self-serviceterminals. For more information, see “Getting Started” on page 19.

Software DistributionTivoli Software Distribution, which is required by Tivoli Self-ServiceTerminal Manager, provides an efficient method for distributing,installing, and controlling software across a network. It establishes acentralized software management system through which you caninstall and configure new applications, update existing software withnewer versions, and synchronize software of distributed systems. Youcan use Tivoli Software Distribution to perform remote distributionand installation of software on self-service terminals from acentralized location.

For more information about distributing software to your self-serviceterminals, see “Distributing Software” on page 63. For moreinformation about Tivoli Software Distribution, refer to theTME 10Software Distribution User’s Guide.


1.Introduction

6 Version 1.0

Planning and Installing

This chapter describes how to install Tivoli Self-Service TerminalManager in your Tivoli environment. It includes:

¶ Planning considerations, including software and hardwarerequirements and operating systems (see “Planning”)

¶ Instructions for installing Tivoli Self-Service Terminal Manager(see “Installing” on page 11)

It also includes information about removing the product (see“Removing the Product” on page 16).

Note: Before you install Tivoli Self-Service Terminal Manager,review the information in this chapter and in theTivoliSelf-Service Terminal Manager Release Notesand ensure thatyou have met all the requirements. You can access theRelease Noteson the product CD; for more information, see“Documentation” on page xii. For information about theprerequisite software and hardware, refer to thedocumentation for those products.

PlanningThis section describes:¶ Steps for getting Tivoli Self-Service Terminal Manager ready to

use (see “Installation and Configuration Overview” on page 8)¶ XFS requirements (see “XFS Requirements” on page 8)¶ Required Tivoli software (see “Tivoli Software” on page 9)

2


2.P

lanningand

Installing

¶ Supported operating systems (see “Operating Systems” onpage 11 )

¶ Hardware requirements (see “Hardware Requirements” onpage 11)

Installation and Configuration OverviewThe high-level installation and configuration steps for TivoliSelf-Service Terminal Manager are:

1. Ensure that the Windows NT XFS self-service terminals youwant to manage meet the XFS requirements described in “XFSRequirements”.

2. Prepare the Tivoli environment by installing the appropriatelevels of the required Tivoli software. For more information, see“Tivoli Software” on page 9. For the supported operating systemsand the hardware requirements, see “Operating Systems” onpage 11 and “Hardware Requirements” on page 11.

3. Install Tivoli Self-Service Terminal Manager. For information onwhere to install Tivoli Self-Service Terminal Manager, see“Tivoli Software” on page 9. For the installation steps, see“Installing” on page 11.

4. To manage self-service terminal events for Windows NT XFSself-service terminals, configure the Tivoli Enterprise Consoleevent server and event adapter; for the steps, see “Setting Up theEvent Server and Event Adapter” on page 29.

5. To collect and use inventory information for Windows NT XFSself-service terminals, configure the inventory database with theTivoli Self-Service Terminal Manager tables and views; for thesteps, see “Configuring the Inventory Configuration Repository”on page 51.

6. Configure Tivoli Self-Service Terminal Manager on eachself-service terminal you want to manage; for the steps, see“Configuring Self-service Terminals” on page 23.

XFS RequirementsWindows NT XFS self-service terminals must use the XFS interfacespecification, Release 2.0. For each self-service terminal you want to

8 Version 1.0

manage using Tivoli Self-Service Terminal Manager, ensure that theXFS manager and the service provider software are installed and thatthe logical services for the self-service terminal peripheral devicesare configured. If any of the devices are configured using serviceclass names other than the standard service class names, you need todefine your service class names using an alias file provided withTivoli Self-Service Terminal Manager. For more information, see“Service Classes and Aliases” on page 115.

Tivoli SoftwareThis table shows the minimum requirements for Tivoli software oneach Tivoli resource type.

TivoliResource

Type ComponentMinimum Required

Software Comments

TivoliManagementRegion(TMR) Server

Tivoli Self-ServiceTerminal Manager

Tivoli ManagementFramework 3.6.1

Required forinstallation. See note 1.

Tivoli Software Distribution3.6.1

Required forinstallation

Tivoli Inventory 3.6.1 Optional; required forinventory function. Seenote 2.

Tivoli Distributed Monitoring3.6.1

Optional; required formonitoring function.See notes 2 and 3.

Tivoli Adapter ConfigurationFacility 3.6.1

Optional; required forevent management. Seenote 2.

Event Server Tivoli Self-ServiceTerminal Manager


Optional; required forevent management

Tivoli Enterprise ConsoleServer 3.6.1

Optional; required forevent management. Seenote 2.

EventConsole



Tivoli Enterprise ConsoleConsole 3.6.1



2.P

lanningand

Installing

TivoliResource

Type ComponentMinimum Required

Software Comments

Gateway Tivoli ManagementFramework 3.6.1


Tivoli Software DistributionGateway 3.6.1


Tivoli Inventory Gateway3.6.1

Optional; required forinventory function

Tivoli Adapter ConfigurationFacility 3.6.1


OtherManagedNodes

Tivoli Self-ServiceTerminal Manager


Optional; required formanaging self-serviceterminals

Tivoli Inventory 3.6.1 Optional; required forinventory function

Tivoli Distributed Monitoring3.6.1

Optional; required formonitoring function

Tivoli Software Distribution3.6.1

Optional; required fordistributing software

Endpoint(Self-ServiceTerminal)

Tivoli Endpoint 3.6.1 Required forconfiguring the Tivolisoftware on aself-service terminal

Notes:

1. Tivoli Management Framework patch 3.6.1-TMF-0049 is required. Tivoli patches areavailable at this Web site: http://www.tivoli.com/support/patches/

2. If this software is not installed before Tivoli Self-Service Terminal Manager is installed,some resources will not be installed in the policy region and will not be available on theTivoli desktop. For more information, see “Installing Missing Resources” on page 15.

3. For Tivoli Distributed Monitoring 3.6.1, patches 3.6.1-DMN-0008 and 3.6.1-DMN-0013are required. Patch 3.6.1-DMN-0036, which enables monitoring error conditions to beindicated by an indicator collection, is strongly recommended and requires additionalpatches. If you are using Tivoli Desktop for Windows with Tivoli ManagementFramework 3.6.1, it is recommended that you use Tivoli Desktop for Windows 3.6.3 andinstall patch 3.6.3-TMF-0002.

10 Version 1.0

http://www.tivoli.com/support/patches/

Operating SystemsTivoli Self-Service Terminal Manager supports these operatingsystems on the TMR server and the event server:

Operating Systems Minimum Supported Versions

AIX®

Version 4.3.2

Solaris Version 2.7 (running on Sun SPARC series)

Windows NT Version 4.0 SP4A

Tivoli Self-Service Terminal Manager supports these operatingsystems for Tivoli endpoints on Windows NT XFS self-serviceterminals:

Operating Systems Minimum Supported Versions

Windows NT Version 4.0 SP4A

Hardware RequirementsThe hardware requirements for Tivoli Self-Service Terminal Managerare as follows:

¶ Disk space requirements for Tivoli Self-Service TerminalManager on the TMR server and the event server are:v AIX: 5 MBv Solaris: 5 MBv Windows NT: 5 MB

¶ The disk space requirement for Tivoli Self-Service TerminalManager endpoint software is 1 MB.

InstallingYou can install Tivoli Self-Service Terminal Manager:¶ From the desktop (see “Installing from the Desktop” on page 12)¶ From the command line (see “Installing from the Command

Line” on page 13)¶ Using Tivoli Software Installation Service (see “Installing with

the Software Installation Service” on page 14)


2.P

lanningand

Installing

Notes:

1. If you are using Tivoli Enterprise Console, you must installTivoli Self-Service Terminal Manager first on the TMR serverand then on the event server (or on both at the same time).

2. To install missing Tivoli Self-Service Terminal Managerresources after installation, see “Installing Missing Resources” onpage 15.

3. When you install Tivoli Self-Service Terminal Manager, a policyregion is added. For more information about the new policyregion, see “Getting Started” on page 19.

4. Before you can use Tivoli Self-Service Terminal Manager tomanage your Windows NT XFS self-service terminals, configurethe Tivoli software on the self-service terminals. For informationabout configuration, see “Getting Started” on page 19.

Installing from the DesktopTo install Tivoli Self-Service Terminal Manager from the Tivolidesktop:

1. Start the Tivoli Management Framework at the TMR server.

2. Click Desktop → Install → Install Product , and, if you areinstalling from the product CD, insert the CD-ROM.

3. In the File Browser dialog displayed, type the full path name ofthe installation files, or select the path from the Directories list,and clickSet Media & Close.

12 Version 1.0

4. In the Install Product dialog displayed, selectTivoli Self-ServiceTerminal Manager - XFS 1.0.

5. Specify where you want to install the components by movingclients from the Available Clients scrolling list to the Clients toInstall On scrolling list.

Note: You must install Tivoli Self-Service Terminal Managerfirst on the TMR server and then on the event server (oron both at the same time).

6. Click Install & Close.

7. Click Continue Install.

8. After the installation is complete, clickClose.

Installing from the Command LineTo install Tivoli Self-Service Terminal Manager from the commandline, enter this command:


2.P

lanningand

Installing

winstall –c imagepath–s server–i SSTNTXFS managed_node...

where:

–c imagepathSpecifies the complete path to the CD-ROM or installationimage.

–s serverSpecifies the managed node in the Tivoli management region touse as the installation server.

–i SSTNTXFSSpecifies the index file from which Tivoli Self-Service TerminalManager - XFS is installed.

managed_nodeSpecifies the managed node on which Tivoli Self-ServiceTerminal Manager is to be installed.

Note: You must install Tivoli Self-Service Terminal Manager firston the TMR server and then on the event server (or on bothat the same time).

Installing with the Software Installation ServiceThis section lists the main steps for installing Tivoli Self-ServiceTerminal Manager using Tivoli Software Installation Service (SIS).Refer to theTME 10 Software Installation Service User’s Guideforspecific instructions.

The main steps are:

1. Import the installation images from the CD-ROM to SIS.

2. From the Install Repository-Select Product window, select thecomponents that you want to install.

3. Select the machines on which you want to install thecomponents.

Note: You must install Tivoli Self-Service Terminal Managerfirst on the TMR server and then on the event server (oron both at the same time).

14 Version 1.0

4. From the TME 10 Software Installation Service-Install detailswindow, selectTivoli Self-Service Terminal Manager - XFS1.0.

5. Click Install .

Installing Missing ResourcesIf any of the optional Tivoli applications (Tivoli DistributedMonitoring, Tivoli Inventory, Tivoli Enterprise Console, or TivoliAdapter Configuration Facility) were not installed when you installedTivoli Self-Service Terminal Manager, the corresponding resourceswere not added to the policy region and are not available on theTivoli desktop.

If you install an optional application later, you can add the missingresources as follows:

1. If necessary, set up the Tivoli environment for your session:

¶ For UNIX:

a. Log in to a Tivoli client or the Tivoli server on whichyour Tivoli administrator has an alias with the super rolefor the TMR.

b. Use the environment setup script.

For the Bourne shell, enter:

. /etc/Tivoli/setup_env.sh

For the C shell, enter:

source /etc/Tivoli/setup_env.sh

¶ For Windows NT, enter these three commands:

%SystemRoot%\system32\drivers\etc\Tivoli\setup_env

sh

$SYSTEMROOT/system32/drivers/etc/Tivoli/setup_env.sh

Note: Some Windows NT commands are scripts and must berun with sh.

2. Run this command on the TMR server:

$BINDIR/TME/sst/ntxfs/sstntxfs.init


2.P

lanningand

Installing

Removing the ProductTo uninstall Tivoli Self-Service Terminal Manager from the TMRserver or the event server, you can use thewuninst commandprovided by the Tivoli Management Framework. Refer to theTME10 Framework Reference Manualfor more information about thewuninst command. Enter the command as follows:

wuninst SSTNTXFS_1.0node_name[–rmfiles]

where:

SSTNTXFS_1.0Specifies the registered product tag for Tivoli Self-ServiceTerminal Manager - XFS 1.0.

node_nameSpecifies the node from which to remove the product. If thenode is the TMR server, the product is removed from the entireTivoli management region.

–rmfilesIndicates that all product files are to be removed fromnode_name. If this optional argument is not included,wuninstremoves the database entries only fornode_name. If thisargument is used on the TMR server, all entries for each node inthe Tivoli management region are removed.

Notes:

1. Before you remove Tivoli Self-Service Terminal Manager, ensurethat it is not in use and that the monitors are disabled. Removingthe product while in use can result in an incomplete removal.

2. Any Tivoli Self-Service Terminal Manager resources to whichadditions were made, and any other resources containing thoseresources, are not removed. For example, if queries were addedto the SST_XFS_Queries query library, then theSST_XFS_Queries query library, the SST_XFS policy region(which contains the SST_XFS_Queries query library), and the

16 Version 1.0

Self_Service_Terminal_Manager policy region (which containsthe SST_XFS policy region) will remain after the product hasbeen removed.

3. The SST_XFS event group and the SST_XFS_RULES rule baseare not removed when you use thewuninst command to removeTivoli Self-Service Terminal Manager. To remove the eventgroup, enter this command:

wdeleg SST_XFS

To remove the rule base, use the desktop or enter this command:

wdelrb SST_XFS_RULES

To remove Tivoli Self-Service Terminal Manager endpoint softwarefrom a self-service terminal:

1. Stop the Tivoli Self-Service Terminal Manager event serviceeither from the Services dialog or with this command:

net stop xfseventserv

2. Remove the event service with this command:

%SystemRoot%\tivoli_sst\sstntxfs\sstntxfsevserv –remove

3. If any Tivoli Self-Service Terminal Manager monitors areenabled on the self-service terminal, distribute a monitoringprofile that disables the monitors.

4. Delete the monitoring program file, wsstntxfsmon.exe, from the%SystemDrive%\%LCFDIR%\dat\1\lcf\sentry\w32-ix86 directory.

5. Delete the inventory scanner program (sstntxfsscan.exe) from the%SystemDrive%\Program Files\TIVOLI\lcf\inv\SCANNERdirectory. If you have done an inventory scan, delete these filesfrom the same directory:¶ sstntxfs.mif¶ sstntxfs.bk1¶ sstntxfs.bk2

6. Delete these directories:¶ C:\sstntxfs¶ %SystemRoot%\tivoli_sst


2.P

lanningand

Installing

18 Version 1.0

Getting Started

This chapter helps you get started with Tivoli Self-Service TerminalManager after you install it. It describes the new policy regioncreated during installation and the configuration required formanaging your self-service terminals. For information about the newpolicy region, see “Navigating the Desktop” on page 20.

From the new policy region, you need to configure TivoliSelf-Service Terminal Manager at the Windows NT XFS self-serviceterminals that you want to manage (see “Configuring Self-serviceTerminals” on page 23).

This chapter also describes how to access tasks; see “AccessingTasks” on page 25.

3


3.G

ettingS

tarted

Navigating the DesktopWhen you install Tivoli Self-Service Terminal Manager, a newpolicy region is added to your Tivoli desktop. ClickSelf_Service_Terminal_Managerto display theSelf_Service_Terminal_Manager policy region.

The Self_Service_Terminal_Manager policy region contains a policyregion for managing Windows NT XFS self-service terminals: theSST_XFS policy region. ClickSST_XFSto open the SST_XFS

20 Version 1.0

policy region.

Note: If any of the optional Tivoli applications (Tivoli DistributedMonitoring, Tivoli Inventory, Tivoli Enterprise Console, andTivoli Adapter Configuration Facility) was not installed whenyou installed Tivoli Self-Service Terminal Manager, thecorresponding resources were not added to the policy regionwhen it was created. If you install the optional applicationlater, you can add the missing resources and profile managersto the policy region; for more information, see “InstallingMissing Resources” on page 15.

The SST_XFS policy region contains:

¶ The SST_XFS_Indicator indicator collection, which displays theresults of monitoring Windows NT XFS self-service terminals.This indicator collection is available only if Tivoli DistributedMonitoring is installed. For information on using the indicatorcollection, see “Using the SST_XFS_Indicator IndicatorCollection” on page 46.


3.G

ettingS

tarted

¶ The SST_XFS_Configuration profile manager, which managesthe SST_XFS_Configuration profile. This profile configuresTivoli software on Windows NT XFS self-service terminals. Itdownloads the Tivoli Self-Service Terminal Manager eventservice, event service configuration file, monitoring program,inventory scanner program, alias file, and trace file to one ormore self-service terminals. It also installs and starts the eventservice. For information on using the SST_XFS_Configurationprofile, see “Configuring Self-service Terminals” on page 23.

¶ The SST_XFS_Event_Adapters profile manager, which managesa default adapter configuration profile (ACP) for Windows NTXFS self-service terminals, the SST_XFS_Event_Adaptersprofile. This profile configures and distributes the Windows NTevent adapter and provides the event adapter configuration andformat files needed for processing Tivoli Self-Service TerminalManager events. This profile manager and profile are availableonly if Tivoli Enterprise Console and Tivoli AdapterConfiguration Facility are installed. For information on using theSST_XFS_Event_Adapters profile, see “Configuring andDistributing the Event Adapter” on page 31 and “Filtering Eventsat the Event Adapter” on page 38.

¶ The SST_XFS_Inventory profile manager, which manages adefault inventory profile for Windows NT XFS self-serviceterminals, the SST_XFS_Inventory profile. This profile can beused as a template or can be distributed directly to one or moreWindows NT XFS self-service terminals. This profile managerand profile are available only if Tivoli Inventory is installed. Forinformation on using the SST_XFS_Inventory profile, see“Using the SST_XFS_Inventory Profile” on page 56.

¶ The SST_XFS_Monitors profile manager, which manages adefault monitoring profile for Windows NT XFS self-serviceterminals, the SST_XFS_Monitors profile. This profile providesdefault monitors, thresholds, and actions for Windows NT XFSself-service terminals. This profile can be used as a template orcan be distributed directly to one or more Windows NT XFSself-service terminals. This profile manager and profile areavailable only if Tivoli Distributed Monitoring is installed. For

22 Version 1.0

information on using the SST_XFS_Monitors profile, see “Usingthe SST_XFS_Monitors Profile” on page 40.

¶ The SST_XFS_Queries query library, which contains inventoryqueries that access the inventory tables for Tivoli Self-ServiceTerminal Manager. This query library is available only if TivoliInventory is installed. For information on using theSST_XFS_Queries query library, see “Querying the InventoryInformation” on page 60.

¶ The SST_XFS_Tasks task library enables you to manage yourWindows NT XFS self-service terminals. For information onusing tasks, see “Accessing Tasks” on page 25.

Configuring Self-service TerminalsBefore you can use Tivoli Self-Service Terminal Manager to manageyour Windows NT XFS self-service terminals, configure theself-service terminals by distributing the SST_XFS_Configurationprofile to the self-service terminals.

Before you distribute this profile to a self-service terminal:

¶ Ensure that the XFS requirement described in “XFSRequirements” on page 8 is met and define any non-standardservice class names using the Tivoli Self-Service TerminalManager alias file. For information, see “Service Classes andAliases” on page 115.

¶ Verify that the endpoint is connected and running.

You can distribute the profile:¶ From the Tivoli desktop (see “Distributing the

SST_XFS_Configuration Profile from the Desktop”)¶ From the command line (see “Distributing the

SST_XFS_Configuration Profile from the Command Line” onpage 25)

Distributing the SST_XFS_Configuration Profile fromthe Desktop

To distribute the SST_XFS_Configuration profile from the desktop:


3.G

ettingS

tarted

1. In the SST_XFS policy region, open theSST_XFS_Configuration profile manager, which manages theSST_XFS_Configuration profile.

2. If necessary, add subscribers by clickingProfile Manager →Subscribers. In the Subscribers dialog displayed, moveendpoints or profile managers from the Available to becomeSubscribers scrolling list to the Current Subscribers scrolling listand then clickSet Subscriptions & Close.

3. Do one of the following:

¶ To distribute the profile immediately to a subscriber,drag-and-drop the profile onto the subscriber icon.

24 Version 1.0

¶ To distribute the profile to all the subscribers in theSubscribers group box, clickProfile Manager → Distribute ,and then clickDistribute Now or, to schedule thedistribution, clickSchedule, fill in the schedulinginformation, and clickSchedule Job & Close.

¶ To distribute the profile to selected subscribers, right-clickthe icon for the SST_XFS_Configuration profile and clickDistribute . In the Distribute File Package dialog displayed,move endpoints and profile managers from the AvailableSubscribers scrolling list to the Distribute File Package Toscrolling list. Then clickDistribute & Close or, to schedulethe distribution, clickSchedule, fill in the schedulinginformation, and clickSchedule Job & Close.

Distributing the SST_XFS_Configuration Profile fromthe Command Line

To distribute the SST_XFS_Configuration profile from the commandline, enter:

wdistfp –a @SST_XFS_Configuration @Endpoint:endpoint_name...

where–a indicates that all the files in the configuration profile are tobe sent andendpoint_nameis the name of the self-service terminalto which the profile is to be distributed. Include the@Endpoint:parameter once for each self-service terminal.

For more information about thewdistfp command, refer to theTME10 Software Distribution Reference Manual.

Accessing TasksThis section describes:

¶ How to open the task library (see “Opening the SST_XFS_TasksTask Library” on page 26)

¶ How to reboot a self-service terminal (see “Rebooting aSelf-service Terminal” on page 26)


3.G

ettingS

tarted

For more information on running and scheduling tasks, refer to theTME 10 Framework User’s Guide.

Opening the SST_XFS_Tasks Task LibraryTo open the SST_XFS_Tasks task library, double-click theSST_XFS_Tasks icon in the SST_XFS policy region.

The task library contains:

Configure_Event_Server_for_SST_XFSThis job configures an event server with the TivoliSelf-Service Terminal Manager events. The task and job areavailable only if Tivoli Enterprise Console is installed. Formore information on using this job, see “Configuring theEvent Server Using a Job” on page 30.

Reboot_SST_XFS_UnitThis task restarts one or more Windows NT XFS self-serviceterminals. For information on using this task, see “Rebootinga Self-service Terminal”.

Rebooting a Self-service TerminalAttention: This task reboots the Windows NT operating system oneach target self-service terminal. Use this task with care, as it doesnot check or stop any applications that are running on theself-service terminal before it runs and data can be lost.

To reboot one or more self-service terminals:

26 Version 1.0

1. Double-click the Reboot_SST_XFS_Unit task icon to display theExecute Task dialog.

2. In the Task Options group box, specify the options for this task.

3. In the Execution Targets group box, select the self-serviceterminals to reboot by moving self-service terminals from theAvailable Task Endpoints scrolling list to the Selected TaskEndpoints scrolling list and moving profile managers from theAvailable Profile Managers scrolling list to the Selected ProfileManagers scrolling list.

4. Click Execute & Dismiss.


3.G

ettingS

tarted

28 Version 1.0

Managing Events

You can use Tivoli Self-Service Terminal Manager with TivoliEnterprise Console to manage self-service terminal events. TivoliSelf-Service Terminal Manager uses the event adapter for WindowsNT to convert the self-service terminal events to the TivoliEnterprise Console format.

First, you need to set up Tivoli Enterprise Console (see “Setting Upthe Event Server and Event Adapter”).

Then, you can:¶ Display events (see “Displaying Events” on page 36)¶ Optionally filter events (see “Filtering Events” on page 36)

Tivoli Self-Service Terminal Manager provides two sets of eventclasses that enable you to view and work with the events at theevent console: status event classes and monitor event classes; formore information, see “Event Classes” on page 67. For moreinformation about using Tivoli Enterprise Console, refer to theTME10 Enterprise Console User’s Guide.

Setting Up the Event Server and Event AdapterTo set up Tivoli Enterprise Console, you need to:¶ Configure the event server (see “Configuring the Event Server”

on page 30).¶ Configure and distribute the event adapter (see “Configuring and

Distributing the Event Adapter” on page 31).

4


4.M

anagingE

vents

Configuring the Event Server

Note: Ensure that Tivoli Self-Service Terminal Manager is installedon the event server before you configure the event server.

Configure the event server in one of the following ways:¶ To create a new rule base, configure the event server using a job

(see “Configuring the Event Server Using a Job”).¶ To use an existing rule base, configure the event server manually

(see “Configuring the Event Server Manually” on page 31).

If you are using Tivoli Distributed Monitoring, you can also definethe monitor event classes to the event server (see “Defining theMonitor Event Classes to the Event Server” on page 31).

Configuring the Event Server Using a JobTo define the Tivoli Self-Service Terminal Manager event classes tothe event server in a new rule base, configure the event server usingthe Configure_Event_Server_for_SST_XFS job in theSST_XFS_Tasks task library. This job creates a new rule base fromthe Default rule base, adds the Tivoli Self-Service Terminal Managerevent classes to the new rule base, and compiles and loads the newrule base.

Note: If you want to add the Tivoli Self-Service Terminal Managerevent classes to an existing rule base, you need to configurethe event server manually; see “Configuring the Event ServerManually” on page 31.

Configure the event server:

1. In the SST_XFS policy region, double-clickSST_XFS_Taskstoopen the task library.

2. In the SST_XFS_Tasks window, double-click the jobConfigure_Event_Server_for_SST_XFS. The TivoliSelf-Service Terminal Manager event classes are included in anew rule base, the SST_XFS_RULES rule base, which is nowloaded.

30 Version 1.0

Configuring the Event Server ManuallyTo define the Tivoli Self-Service Terminal Manager event classes tothe event server using an existing rule base, configure the eventserver manually. The Tivoli Self-Service Terminal Manager eventclass definitions are located in the$BINDIR/../generic/TME/sst/ntxfs/sstxfsevents.baroc file. Forinformation about adding event class definitions to an existing rulebase, refer to theTME 10 Enterprise Console Rule Builder’s Guide.

Note: You can also define the event classes for Tivoli DistributedMonitoring when you are defining the event classes for TivoliSelf-Service Terminal Manager; see “Defining the MonitorEvent Classes to the Event Server”

After you add the event class definitions to the rule base, create anevent group that includes the WFS_Event event class. Forinformation about creating event groups, refer to theTME 10Enterprise Console User’s Guide.

Defining the Monitor Event Classes to the Event ServerTo set up Tivoli Distributed Monitoring to send events to TivoliEnterprise Console, add the Tivoli Distributed Monitoring event classdefinitions to your existing rule base. For information, refer to theTME 10 Distributed Monitoring User’s Guide.

Configuring and Distributing the Event AdapterTo configure the Windows NT event adapter on a Windows NT XFSself-service terminal, you need to:¶ Configure the event adapter using the SST_XFS_Event_Adapters

profile (see “Configuring the Event Adapter”).¶ Distribute the SST_XFS_Event_Adapters profile to the

self-service terminal (see “Distributing theSST_XFS_Event_Adapters Profile” on page 34).

Configuring the Event AdapterTo configure the event adapter at a self-service terminal:

1. In the SST_XFS policy region, double-clickSST_XFS_Event_Adaptersto open the


4.M

anagingE

vents

SST_XFS_Event_Adapters profile manager.

2. In the Profile Manager window, double-clickSST_XFS_Event_Adaptersto open the

32 Version 1.0

SST_XFS_Event_Adapters profile.

3. Double-clicktecad_nt.confto open the event adapterconfiguration file.

4. On the Edit Adapter dialog that is displayed, optionally set thefiltering:

¶ Events with the pound sign (#) are not filtered; that is, theyare sent to the event server. To filter an event (prevent itfrom being sent to the event server), select the event and


4.M

anagingE

vents

click Enable Filter. The event will no longer include apound sign and will not be sent to the event server.

¶ Events without pound signs are filtered; that is, they are notsent to the event server. To enable the event to be sent to theevent server, select the event and clickDisable Filter. Theevent will include a pound sign and will be sent to the eventserver.

5. For a Windows NT event server, set the event server port:

a. SelectEnvironment to display the environment variables.

b. In the Unset Variables scrolling list, double-clickServerPortto display the server port environment variable in the left textbox above the Current EIF Environment scrolling list.

c. Type5529 in the right text box above the Current EIFEnvironment scrolling list, and click the check button.

6. To save your changes, clickSave & Close.

Distributing the SST_XFS_Event_Adapters ProfileAfter you change the event adapter configuration file, distribute theSST_XFS_Event_Adapters profile.

34 Version 1.0

Attention: When you distribute the SST_XFS_Event_Adaptersprofile to a self-service terminal, any event adapter format andconfiguration files on the self-service terminal are overwritten.

¶ To distribute the profile from the desktop:

1. If it is not open, open the SST_XFS_Event_Adapters profilemanager in the SST_XFS policy region.

2. If necessary, add subscribers by clickingProfile Manager →Subscribers. In the Subscribers dialog displayed, moveendpoints or profile managers from the Available to becomeSubscribers scrolling list to the Current Subscribers scrollinglist and then clickSet Subscriptions & Close.


v To distribute the profile immediately to a subscriber,drag-and-drop the profile onto the subscriber icon.

v To distribute the profile to all the subscribers in theSubscribers group box, clickProfile Manager →Distribute , and then clickDistribute Now or, to schedulethe distribution, clickSchedule, fill in the schedulinginformation, and clickSchedule Job & Close.

v To distribute the profile to selected subscribers,double-click the icon for the SST_XFS_Event_Adaptersprofile. In the Adapter Configuration Profile dialogdisplayed, clickProfile → Distribute . In the DistributeProfile dialog displayed, move endpoints and profilemanagers from the Don’t Distribute to These Subscribersscrolling list to the Distribute to These Subscribersscrolling list. Then clickDistribute & Close or, toschedule the distribution, clickSchedule, fill in thescheduling information, and clickSchedule Job & Close.

¶ To distribute the configuration profile from the command line,enter this command:

wdistrib over_all @ACP:SST_Event_Adapters@Endpoint:endpoint_name...


4.M

anagingE

vents

whereendpoint_nameis the name of the self-service terminal towhich the profile is to be distributed. Include the@Endpoint:keyword once for each endpoint.

Displaying EventsAfter you have configured Tivoli Enterprise Console, you can viewevents from the Tivoli desktop as follows:

1. Create an event console and assign the SST_XFS event group tothat console. For information on how to do this, refer to theTME10 Enterprise Console User’s Guide.

2. Open the event console. The event console window that isdisplayed contains an icon for each event group that you areauthorized to view.

3. Double-click the SST_XFS icon to display a list of events for theTivoli Self-Service Terminal Manager event group.

4. To view the details of an event, double-click the event or selectthe event and clickView Message. The Event Group MessageView dialog is displayed. Information for each slot (informationfield) of the event is displayed in this dialog.

Filtering EventsYou can filter events that you regard as harmless or unlikely torequire action:¶ At the self-service terminal (see “Filtering Events at the

Self-service Terminal” on page 37)¶ At the event adapter (see “Filtering Events at the Event Adapter”

on page 38)¶ At the event console (see “Filtering Events at the Event

Console” on page 38)

Note: The default event filtering provided by the event adapter andthe Tivoli Self-Service Terminal Manager event service arelisted in “Default Event Filtering” on page 79.

36 Version 1.0

Filtering Events at the Self-service TerminalParent Tivoli Self-Service Terminal Manager events are filtered bythe event service using the event service configuration file(sstntxfsevserv.xml) on the self-service terminal. The LOG tagsetting for each event in the file determines whether the eventservice logs the event. The events specified as<LOG>YES</LOG> arelogged and available for the event adapter to forward to the eventserver. The events specified as<LOG>NO</LOG> are not logged andwill not be available for the event adapter to forward to the eventserver.

To change the logging for events in the event service configurationfile at the endpoint:

1. Stop the event service (Tivoli XFS Event Service) in the Servicesfolder, or use thenet stop xfseventservcommand.

2. Use a text editor to edit the sstntxfsevserv.xml file on theself-service terminal and change the value of the LOG tagsettings for the parent events.

3. Restart the event service. You can also use thenet startxfseventservcommand to start the event service.

Notes:

1. The sstntxfsevserv.xml file is located in the$BINDIR/../generic/TME/sst/ntxfs/w32-ix86 directory on theTMR server and the %SystemRoot%\tivoli_sst\sstntxfs directoryon the self-service terminal.

2. Before you change this file, make a backup copy.

3. If you change the file at the TMR server, your changes are sentto all Windows NT XFS self-service terminals subsequentlyconfigured. To send a changed event service configuration file toa self-service terminal that has already been configured, it isrecommended that you create and distribute a softwaredistribution file package. In the software distribution profile,specify a before script to stop the event service on theself-service terminal and an after script to restart the eventservice.


4.M

anagingE

vents

4. If the event service configuration file on a self-service terminal ismissing or becomes unusable, events are logged based on thedefault values. For a list of the default events filtered by theevent service, see “Default Event Filtering” on page 79.

5. The event service configuration file also specifies a start delay,which determines how long the event service waits afterautostarting before it registers and begins forwarding events tothe event server. Events that occur during the start-delay periodare lost. The start delay is specified in milliseconds, as follows,with an initial setting of 600000 (10 minutes):<STARTUP>

<STARTDELAY>600000</STARTDELAY></STARTUP>

If the event service configuration file is missing or unusable ordoes not contain a start-delay setting, the default start-delaysetting is 600000 milliseconds.

Filtering Events at the Event AdapterYou can filter Tivoli Self-Service Terminal Manager events using theevent adapter configuration file. For the steps, see “Configuring theEvent Adapter” on page 31.

Filtering Events at the Event ConsoleTo filter events at the event console, you can:

¶ Create new rules to exclude an event. In this case, the event isforwarded to the event server but is eliminated by the rulesengine. TheTME 10 Enterprise Console Rule Builder’s Guidedescribes the steps for building and modifying rules.

¶ Exclude classes of events using the Tivoli Enterprise Consoleuser interface. For more information, refer to theTME 10Enterprise Console User’s Guide.

38 Version 1.0

Monitoring Resources

You can use Tivoli Self-Service Terminal Manager with TivoliDistributed Monitoring to monitor your Windows NT XFSself-service terminals. You can:

¶ Set up monitoring profiles (see “Using Monitoring Profiles” onpage 40)

¶ Add or define monitors to a monitoring profile (see “Adding andDefining Monitors” on page 42)

¶ Distribute monitoring profiles to run monitors on yourself-service terminals (see “Distributing Monitoring Profiles” onpage 44)

¶ Determine which monitors have been distributed to or areenabled at a self-service terminal (see “Determining WhichMonitors Have Been Distributed or Enabled” on page 46)

¶ Use the indicator collection to learn more about a condition thathas occurred (see “Using the SST_XFS_Indicator IndicatorCollection” on page 46)

¶ View the monitor information collected from the self-serviceterminals (see “Viewing Monitor Information” on page 47)

For more information about monitoring, refer to theTME 10Distributed Monitoring User’s Guide. For information about themonitoring collection provided with Tivoli Self-Service TerminalManager, see “Monitoring Collection” on page 81.

5


5.M

onitoringR

esources

Using Monitoring ProfilesMonitoring profiles determine what monitors run against WindowsNT XFS self-service terminals. You can use:¶ The default monitoring profile in the SST_XFS policy region

(see “Using the SST_XFS_Monitors Profile”)¶ A new monitoring profile (see “Creating a New Monitoring

Profile and Indicator Collection” on page 41)

Using the SST_XFS_Monitors ProfileIn the SST_XFS policy region, double-clickSST_XFS_Monitors toopen the default monitoring profile manager: theSST_XFS_Monitors profile manager.

40 Version 1.0

This profile manager manages a default Tivoli DistributedMonitoring profile for the Windows NT XFS self-service terminals:the SST_XFS_Monitors profile. This profile provides defaultmonitors, thresholds, and actions for Windows NT XFS self-serviceterminals. This profile includes the Printer Supplies, SST, SST OpenState, and SST Operation Mode monitors. To add monitors, see“Adding and Defining Monitors” on page 42. To distribute theprofile, see “Distributing Monitoring Profiles” on page 44.

The monitors defined in the SST_XFS_Monitors profile change theicon for the SST_XFS_Indicator indicator collection. For moreinformation on using the indicator collection, see “Using theSST_XFS_Indicator Indicator Collection” on page 46.

This monitoring profile can be used as a template to create otherprofiles or can be distributed directly to subscribers. To distribute theprofile, see “Distributing Monitoring Profiles” on page 44.

Creating a New Monitoring Profile and IndicatorCollection

To set up your own profile for monitoring self-service terminals:

1. Create the profile. See “Creating Monitoring Profiles”.

2. Optionally, create an indicator collection and associate it withyour profile. See “Creating an Indicator Collection” on page 42.

Creating Monitoring Profiles

Note: Before you create a monitoring profile or an indicatorcollection, set managed resources in the policy region toinclude SentryProfile and, optionally, IndicatorCollection.

Create the profile as follows:

1. In the profile manager where you want to create the profile(which must be set up in dataless endpoint mode), clickCreate →Profile to display the Create Profile dialog.

2. Type a unique name for the profile and selectSentryProfile inthe Type list.


5.M

onitoringR

esources

3. Click Create & Close.

After you create a monitoring profile, you can:¶ Associate an indicator collection with it (see “Creating an

Indicator Collection”)¶ Add monitors to it (see “Adding and Defining Monitors”)

Creating an Indicator CollectionOptionally, create an indicator collection as follows:

1. In the policy region, clickCreate → IndicatorCollection .

2. Type a unique name for the indicator collection and clickCreate& Close. An icon for the indicator collection appears in thepolicy region.

Then, associate the indicator collection with your profile:

1. Double-click the profile with which you want to associate theindicator collection to display the Distributed Monitoring ProfileProperties window.

2. Click Monitoring → Select Indicator Collection to display theSelect Indicator Collection dialog.

3. Highlight the indicator collection you want to use and clickSet& Close.

Adding and Defining MonitorsYou can add and define monitors:¶ From the desktop (see “Adding and Defining Monitors from the

Desktop”)¶ From the command line (see “Adding and Defining Monitors

from the Command Line” on page 43)

Adding and Defining Monitors from the DesktopAdd monitors to your profile and define them as follows:

1. Double-click the profile to display the Distributed MonitoringProfile Properties window.

42 Version 1.0

2. Click Add Monitor to display the Add Monitor to TME 10Monitoring Profile dialog.

3. SelectSST_XFSin the Monitoring Collections list.

4. Select a monitor from the Monitoring Sources list.

5. If the selected monitor has arguments, specify information inthe fields in the Monitor Arguments group box.

6. Click Add Empty to display the Edit Monitor dialog.

7. Select a response level and specify when the monitor is to betriggered.

8. Specify one or more actions to take place when the conditionsyou have specified are met. You can send a Tivoli notice,display a pop-up window, change the icon for the associatedindicator collection, specify a task, send e-mail, log information,or run a program. If you are using Tivoli Enterprise Consoleand the event server is set up to receive events from TivoliDistributed Monitoring, you can send an event.

9. Optionally, schedule the monitor to capture information atspecific times by clickingSet Monitoring Scheduleandspecifying scheduling information on the Set MonitoringSchedule dialog. The default is to run the monitor every hour.

10. To save your monitor definition, clickChange & Close.

Adding and Defining Monitors from the CommandLine

To add and define monitors from the command line, use thiscommand:

waddmon SST_XFSmonitor [–a argument...] [–t timing] [–d | +d]response_specifier... profile_name

where:

monitorSpecifies the CLI name of the SST_XFS monitor to add to themonitoring profile; see “CLI Names” on page 81.


5.M

onitoringR

esources

–a argumentSpecifies an argument to be added to the monitor. If anSST_XFS monitor has more than one argument, the argumentsmust be specified in the order shown in “Monitor Sources” onpage 83.

–t timingSpecifies the sampling frequency.

–d Enables the monitor.

+dDisables the monitor.

response_specifierSets the response level.

profile_nameSpecifies the name of the profile to which you want to add themonitor.

For information about the SST_XFS monitor sources and for theirCLI names, see “Monitoring Collection” on page 81. For informationabout the response specifier parameter and for more informationabout thewaddmon command, refer to Appendix C of theTME 10Distributed Monitoring User’s Guide.

Distributing Monitoring ProfilesDistribute the monitoring profile to the Windows NT XFSself-service terminals you want to monitor. You can distribute amonitoring profile:¶ From the Tivoli desktop (see “Distributing a Monitoring Profile

from the Desktop”)¶ From the command line (see “Distributing a Monitoring Profile


Distributing a Monitoring Profile from the DesktopTo distribute a monitoring profile from the desktop:

44 Version 1.0

1. If the profile manager that contains the monitoring profile youwant to distribute is not open, double-click the profile managericon to open it.

2. If necessary, add subscribers by clickingProfile Manager →Subscribers. In the Subscribers dialog displayed, moveendpoints or profile managers from the Available to becomeSubscribers scrolling list to the Current Subscribers scrolling listand then clickSet Subscriptions & Close.




¶ To distribute the profile to selected subscribers, double-clickthe icon for the monitoring profile. In the DistributedMonitoring Profile Properties dialog displayed, clickProfile→ Distribute . In the Distribute Profile dialog displayed,select options and move endpoints and profile managers fromthe Don’t Distribute to These Subscribers scrolling list to theDistribute to These Subscribers scrolling list. Then clickDistribute & Close or, to schedule the distribution, clickSchedule, fill in the scheduling information, and clickSchedule Job & Close.

Distributing a Monitoring Profile from the CommandLine

To distribute a monitoring profile from the command line, enter thiscommand:

wdistrib @SentryProfile:profile_name@Endpoint:endpoint_name...


5.M

onitoringR

esources

whereprofile_nameis the name of the profile (SST_XFS_Monitorsfor the default profile) andendpoint_nameis the name of theself-service terminal to which the profile is to be distributed. Includethe @Endpoint: keyword once for each endpoint.

For more information about thewdistrib command, refer to theTME 10 Framework Reference Manual.

Determining Which Monitors Have Been Distributedor Enabled

You can determine which monitors have been distributed to aself-service terminal and which of the monitors are enabled byentering the following command:

wlseng –lendpoint_name

If you see anUnable to start engine dm_ep_engine message,Tivoli Distributed Monitoring is not running on the self-serviceterminal.

If you see output showingTimer, Monitoring probes, andResponses messages, Tivoli Distributed Monitoring is running onthe self-service terminal as follows:

¶ The messages following theTimer message show the monitorsthat have been distributed to the self-service terminal.

¶ The messages following theMonitoring probes message showthe monitors that have been enabled to run on the self-serviceterminal.

Using the SST_XFS_Indicator Indicator CollectionFor monitors running on Windows NT XFS self-service terminalsusing the SST_XFS_Monitors profile, use the SST_XFS_Indicatorindicator collection as follows:

1. To view the contents of the SST_XFS_Indicator indicatorcollection, double-clickSST_XFS_Indicator in the SST_XFS

46 Version 1.0

policy region to display the indicator collection window.

The SST_XFS_Monitors indicator icon reflects the conditions ofthe monitors in the SST_XFS_Monitors profile because thosemonitors have been set to change the icon when a threshold isreached.

2. When the indicator icon indicates that a threshold has beenreached, you can view the indicator log to find out more aboutthe condition. To view the indicator log for theSST_XFS_Monitors indicator, double-clickSST_XFS_Monitors.The log provides the monitor name, the severity level, theself-service terminal on which the condition was detected, andthe time the condition was detected.

3. If the conditions that triggered a change to theSST_XFS_Monitors indicator icon no longer exist, you can clickResetto reset the icon. That will enable you to easily determinewhen the next condition occurs.

Note: To both reset the indicator icon and clear the indicatorlog, click Clear.

Viewing Monitor InformationThe Tivoli Self-Service Terminal Manager monitors can provideoutput information in several forms: Tivoli notices, pop-up dialogs,e-mail, log messages, and Tivoli Enterprise Console events. Thissection describes the information that is provided in monitor output,


5.M

onitoringR

esources

using a pop-up dialog as an example. The example shows the outputfrom the SST_XFS monitor Printer Supplies:

In the example, the fields show the following:

Distributed Monitoring SST_XFS_MonitorsIs the name of the profile.

Printer SuppliesIs the name of the monitor.

tsstm2Is the name of the self-service terminal on which the monitorwas run.

09/02/2000 03:20:03Is the time and date on which the monitor was run, as readfrom the Windows NT system clock.

>>>normal<<<Is the exit code indicating the success or failure of themonitor.

normal is returned only when no severity levels have beenreached or the monitor has been set to always return a value.

E.EXEC is returned if an error occurred while the monitorwas running.

warning, severe, or critical is returned when the criteriahave been met for the configured warning, severe, or criticalresponse level.

PreviousIs the value returned by the preceding run of the monitor.

48 Version 1.0

The first time this monitor is run in any monitoring session,this field is blank. When provided, a keyword, such as(status), indicates what the returned monitor value is.

CurrentIs the value returned by the most recent run of the monitor.


5.M

onitoringR

esources

50 Version 1.0

Using Inventory Information

You can use Tivoli Self-Service Terminal Manager with TivoliInventory to collect XFS-specific inventory information about yourself-service terminals. After you configure the Tivoli Inventoryconfiguration repository for Tivoli Self-Service Terminal Manager(see “Configuring the Inventory Configuration Repository”), youcan:

¶ Use profiles to specify how the self-service terminal inventoryinformation is collected (see “Using Inventory Profiles” onpage 56)

¶ Distribute profiles to collect the inventory information (see“Distributing Inventory Profiles” on page 59)

¶ Query the self-service terminal inventory information youcollected (see “Querying the Inventory Information” on page 60)

For more information about using Tivoli Inventory, refer to theTME10 Inventory User’s Guide. For information about the inventorytables, views, and queries provided with Tivoli Self-Service TerminalManager, see “Inventory Tables, Views, and Queries” on page 97.

Configuring the Inventory Configuration RepositoryBefore you can use inventory information for Tivoli Self-ServiceTerminal Manager, install the Tivoli Self-Service Terminal Managerschema (tables and views) in the Tivoli Inventory database(configuration repository).

6


6.U

singInventory

Information

First, ensure that you have:¶ Chosen a relational database management system (RDBMS)

server and an RDBMS Interface Module (RIM) host¶ Installed the RDBMS and configured it to communicate with the

RIM host¶ Installed Tivoli Inventory on the TMR server¶ Installed Tivoli Inventory Gateway on the managed nodes that

serve as gateways for your self-service terminals¶ Created the Tivoli Inventory configuration repository, including

installing the configuration repository schema

For more information on these, refer to theTME 10 Inventory User’sGuide.

Then, define the tables and views in one of these databases:¶ DB2 (see “Configuring the DB2 Configuration Repository”)¶ Informix (see “Configuring the Informix Configuration

Repository” on page 53)¶ MS SQL (see “Configuring the MS SQL Configuration

Repository” on page 53)¶ Oracle (see “Configuring the Oracle Configuration Repository”

on page 54)¶ Sybase (see “Configuring the Sybase Configuration Repository”

on page 54)

Configuring the DB2 Configuration RepositoryTo configure the DB2 configuration repository:

1. Copy the tivoli_sstxfs_db2_schema.sql script from the$BINDIR/TME/sst/ntxfs/scripts/rdbms directory on the TMRserver to a temporary directory on the RIM host or the DB2server.

2. Create a connection to the DB2 server database with thiscommand:

db2 connect todatabase_nameuser user_nameusing password

where:

database_nameSpecifies the name or alias name of the Tivoli Inventorydatabase

52 Version 1.0

user_nameSpecifies the name of the user who owns the TivoliInventory database

passwordSpecifies the password of the user specified byuser_name

3. From the temporary directory into which you copied thetivoli_sstxfs_db2_schema.sql script, run the script with thiscommand:

db2 –f tivoli_sstxfs_db2_schema.sql –o –t –ztivoli_sstxfs_db2_schema.log

This command installs the DB2 configuration repository schemafor Tivoli Self-Service Terminal Manager, directs the output tothe screen, and logs the output in thetivoli_sstxfs_db2_schema.log file.

Configuring the Informix Configuration RepositoryTo configure the Informix configuration repository:

1. Copy the tivoli_sstxfs_infx_schema.sql script from the$BINDIR/TME/sst/ntxfs/scripts/rdbms directory on the TMRserver to a temporary directory on the RIM host or the Informixserver.

2. Run the tivoli_sstxfs_infx_schema.sql script with this command:

dbaccessdatabase_name@$INFORMIXSERVERtivoli_sstxfs_infx_schema.sql

wheredatabase_nameis the name of the Inventory configurationrepository.

This command installs the Informix configuration repositoryschema for Tivoli Self-Service Terminal Manager.

Configuring the MS SQL Configuration RepositoryTo configure the MS SQL configuration repository:

1. Copy the tivoli_sstxfs_sql_schema.sql script from the$BINDIR/TME/sst/ntxfs/scripts/rdbms directory on the TMRserver to a temporary directory on the RIM host or the RDBMSserver.


6.U

singInventory

Information

2. From the temporary directory, run the script with this command:

isql –U user_name[–P password] –itivoli_sstxfs_sql_schema.sql –o tivoli_sstxfs_sql_schema.log

whereuser_nameandpasswordare the RDBMS user name andpassword for the MS SQL server user.

This command installs the MS SQL configuration repositoryschema for Tivoli Self-Service Terminal Manager, directs theoutput to the screen, and logs the output in thetivoli_sstxfs_sql_schema.log file.

Configuring the Oracle Configuration RepositoryTo configure the Oracle configuration repository:

1. Copy the tivoli_sstxfs_ora_schema.sql script from the$BINDIR/TME/sst/ntxfs/scripts/rdbms directory on the TMRserver to a temporary directory on the RIM host or the RDBMSserver.

2. From the temporary directory, start an SQL *Plus session and login to the RDBMS server using this command:

sqlplus user_name/ password

whereuser_nameandpasswordare the RDBMS user name andpassword for the Oracle user.

3. To specify a file for the log information, use this command:

spool tivoli_sstxfs_ora_schema.log

4. In the SQL *Plus session, run the tivoli_sstxfs_ora_schema.sqlscript using this command:

@tivoli_sstxfs_ora_schema.sql

The script installs the Oracle configuration repository schema forTivoli Self-Service Terminal Manager and logs the results in thetivoli_sstxfs_ora_schema.log file.

Configuring the Sybase Configuration RepositoryTo configure the Sybase configuration repository:

54 Version 1.0

1. Copy the tivoli_sstxfs_sybase_schema.sql script from the$BINDIR/TME/sst/ntxfs/scripts/rdbms directory on the TMRserver to a temporary directory in which you can run isql on theRIM host or the RDBMS server.

2. From the temporary directory, run the script with this command:

isql –U user_name–P password–itivoli_sstxfs_sybase_schema.sql –otivoli_sstxfs_sybase_schema.log

whereuser_nameandpasswordare the RDBMS user namepassword for the Sybase server user.

This command installs the Sybase configuration repositoryschema for Tivoli Self-Service Terminal Manager, directs theoutput to the screen, and logs the output in thetivoli_sstxfs_sybase_schema.log file.

Moving the SST_XFS_Queries Query LibraryThe SST_XFS_Queries query library is installed in the SST_XFSpolicy region. To establish the query library in another policy region,you need to remove it and reinstall it as follows:

1. If necessary, set up the Tivoli environment. For the steps, see“Installing Missing Resources” on page 15.

2. Remove the SST_XFS_Queries query library from the SST_XFSpolicy region with this command, which is located in the$BINDIR/TME/sst/ntxfs directory:

sstxfs_queries_remove.sh[query_library_name]

wherequery_library_nameis the name of the query library. If aname is not specified, SST_XFS_Queries is the default.

3. In the policy region where you want to install theSST_XFS_Queries query library, set managed resources toinclude QueryLibrary.

4. Install the SST_XFS_Queries query library with this command,which is located in the $BINDIR/TME/sst/ntxfs directory:

sstxfs_queries.shregion_name[query_library_name]


6.U

singInventory

Information

whereregion_nameis the name of the policy region where youwant to install the SST_XFS_Queries query library andquery_library_name, if specified, is the name to assign to thequery library. If you do not specify a query library name, it willbe named SST_XFS_Queries.

Using Inventory ProfilesInventory profiles determine what inventory information is collectedfrom Windows NT XFS self-service terminals. You can use:¶ The default inventory profile in the SST_XFS policy region (see

“Using the SST_XFS_Inventory Profile”)¶ A new inventory profile, customized for use with the Windows

NT XFS self-service terminals (see “Creating a New InventoryProfile” on page 58)

Using the SST_XFS_Inventory ProfileIn the SST_XFS policy region, double-clickSST_XFS_Inventory toopen the default inventory profile manager: the SST_XFS_Inventory

56 Version 1.0

profile manager.

This profile manager manages a default Tivoli Inventory profile forthe Windows NT XFS self-service terminals: theSST_XFS_Inventory profile. This profile selects options that run theself-service terminal inventory scanner to collect inventoryinformation for self-service terminals. This profile can be used as atemplate to create other inventory profiles or can be distributeddirectly to subscribers. To distribute this profile, see “DistributingInventory Profiles” on page 59.


6.U

singInventory

Information

Creating a New Inventory ProfileInstead of using the SST_XFS_Inventory profile, you can create aninventory profile. After you create the profile, you need to customizeit for self-service terminals.

Note: Before you create the profile, set managed resources in thepolicy region to include InventoryProfile.

Create the profile:


2. Type a unique name for the profile and selectInventoryProfilein the Type list.


Customize the profile for self-service terminals:

1. Right-click the profile you created and clickCustomize todisplay the Customize Inventory Profile dialog.

2. In the Execute at Target group box, select Hardware Scan anddeselect Software Scan; then, select Script and click the buttonnext to the Script check box. In the dialog displayed, typesstntxfsscan.exeand then clickSave & Close.

3. In the Read Results group box, select Hardware MIF File,deselect Software MIF File, and select Custom MIF File.

4. In the Save Results in Database group box, select either option.

Note: The default setting for Save Results in Database is Updatewith Differences. To minimize the number of records inthe database, setting this to Replace with Current Resultsis recommended.

5. In the Custom MIF Files To Be Read scrolling list, removeuseradd.mif and addsstntxfs.mif.

6. Leave other parameters set to the defaults.

58 Version 1.0

Distributing Inventory ProfilesTo collect inventory information for your self-service terminals,distribute an SST_XFS_Inventory profile to your self-serviceterminals. When you distribute the profile, the self-service terminalinventory scanner gathers the information and saves it in a MIF file.The information is converted to a format that can be saved in anRDBMS database and sent to the TMR server, which sends theinformation to the configuration repository on the RDBMS server.The information is stored in the SST_XFS tables in the configurationrepository.

You can distribute an inventory profile:¶ From the Tivoli desktop (see “Distributing an Inventory Profile

from the Desktop”)¶ From the command line (see “Distributing an Inventory Profile


Distributing an Inventory Profile from the DesktopTo distribute an inventory profile from the desktop:

1. If the profile manager that contains the inventory profile youwant to distribute is not open, double-click the profile managericon to open it.

2. If necessary, add subscribers by clickingProfile Manager →Subscribers. In the Subscribers dialog displayed, moveendpoints or profile managers from the Available to becomeSubscribers scrolling list to the Current Subscribers scrolling list,and then clickSet Subscriptions & Close.





6.U

singInventory

Information

¶ To distribute the profile to selected subscribers, double-clickthe icon for the inventory profile. In the Inventory Profiledialog displayed, move endpoints and profile managers fromthe Available Targets scrolling list to the Selected Targetsscrolling list. Then clickDistribute & Close or, to schedulethe distribution, clickSchedule, fill in the schedulinginformation, and clickSchedule Job & Close.

Distributing an Inventory Profile from the CommandLine

To distribute an inventory profile from the command line, enter thiscommand:

wdistrib @InventoryProfile: profile_name@Endpoint:endpoint_name...

whereprofile_nameis the name of the profile (SST_XFS_Inventoryfor the default profile) andendpoint_nameis the name of theself-service terminal to which the profile is to be distributed. Includethe @Endpoint: keyword once for each endpoint.

For more information about thewdistrib command, refer to theTME 10 Framework Reference Manual.

Querying the Inventory InformationYou can use the queries provided by Tivoli Self-Service TerminalManager in the SST_XFS_Queries query library to look at:¶ All the self-service terminal inventory information collected (see

“Querying All Self-service Terminal Inventory Information”)¶ The inventory information collected for a specific self-service

terminal (see “Querying Inventory Information for a SingleSelf-service Terminal” on page 61)

Querying All Self-service Terminal InventoryInformation

To query the inventory information in the database for allself-service terminals:

60 Version 1.0

1. In the SST_XFS policy region, double-clickSST_XFS_Queriesto open the SST_XFS_Queries window.

2. Right-click on a query, and then clickRun Query. The query isrun with the default values. To see which columns are includedin the query, see the appropriate query in “Inventory Tables,Views, and Queries” on page 97.

3. To change the default values for the supplied queries, right-clickon a query, and then clickEdit Query . The Edit Query dialog isdisplayed. For more information on editing or creating your ownqueries, refer to theTME 10 Inventory User’s Guide.

Querying Inventory Information for a SingleSelf-service Terminal

To query the inventory information in the database for a singleself-service terminal:


6.U

singInventory

Information

1. In the SST_XFS policy region, double-clickSST_XFS_Inventory to open the SST_XFS_Inventory profilemanager.

2. Right-click on the endpoint icon for the self-service terminal inthe Subscribers group box, and clickExecute Query.

3. In the Execute a Query dialog that is displayed, selectSST_XFS_Queriesin the Query Libraries scrolling list. Then,select a query in the Queries scrolling list, and clickExecute.

4. The results for the query are returned in a Run Query dialog.

Note: If no data is found for the query, reasons include:¶ An inventory profile has not been distributed to collect

the inventory information.¶ The self-service terminal does not have the device for

which the query is requesting data.¶ The device does not support the requested data

(capabilities or status).¶ The information could not be retrieved from XFS.¶ The service class for the device is not a standard class

and is not defined in the Tivoli Self-Service TerminalManager alias file.

62 Version 1.0

Distributing Software

You can distribute software to self-service terminals using TivoliSoftware Distribution. This section describes how to:

¶ Create software packages (see “Creating Software Packages”)

¶ Distribute the software packages (see “Distributing SoftwarePackages” on page 64)

For more information about using Tivoli Software Distribution, referto theTME 10 Software Distribution User’s Guide.

Creating Software PackagesBefore you distribute software, you create a software package, whichis a software distribution profile.

Note: Before you create the profile, set managed resources in thepolicy region to include FilePackage.

To create the profile:


2. Type a unique name for the profile and selectFilePackagein theType list.


7


7.D

istributingS

oftware

To define the properties of the file package, follow these generalsteps. For more details about these steps, refer toTME 10 SoftwareDistribution User’s Guide.

1. From the Profile Manager window, double-click the icon for yourfile package.

2. On the File Package Properties window that is displayed, specifythe source host for your file package and the directories and filesthat make up your file package.

3. Optionally, clickEdit → Platform-Specific Options and click theplatform to display the Options dialog, where you can specify thedestination directory path. You can also specify scripts to be runbefore or after the distribution, upon removal, or during commit.After you specify your information, clickSet & Close.

4. Click Save & Closeto save your file package properties andoptions and close the File Package Properties window.

Distributing Software PackagesAfter you create a file package and set its properties and options,you can distribute it to subscribers. You can distribute a file package:¶ From the Tivoli desktop (see “Distributing a File Package from

the Desktop”)¶ From the command line (see “Distributing a File Package from

the Command Line” on page 65)

For more information about distributing file packages, refer to theTME 10 Software Distribution User’s Guide.

Distributing a File Package from the DesktopTo distribute a file package from the desktop:

1. If the profile manager that contains the file package you want todistribute is not open, double-click the profile manager icon toopen it.

2. If necessary, add subscribers by clickingProfile Manager →Subscribers. In the Subscribers dialog displayed, moveendpoints or profile managers from the Available to become

64 Version 1.0

Subscribers scrolling list to the Current Subscribers scrolling list,and then clickSet Subscriptions & Close.


¶ To distribute the file package immediately to a subscriber,drag-and-drop the file package onto the subscriber icon.

¶ To distribute the file package to all the subscribers in theSubscribers group box, clickProfile Manager → Distributeand then clickDistribute Now or, to schedule thedistribution, clickSchedule, fill in the schedulinginformation, and clickSchedule Job & Close.

¶ To distribute the file package to selected subscribers,right-click the file package icon and clickDistribute . In theDistribute File Package dialog displayed, move endpoints andprofile managers from the Available Subscribers scrolling listto the Distribute File Package to scrolling list. Then clickDistribute & Close, or, to schedule the distribution, clickSchedule, fill in the scheduling information, and clickSchedule Job & Close.

Distributing a File Package from the Command LineTo distribute the file package from the command line, enter thiscommand:

wdistfp –a @file_package_name@Endpoint:endpoint_name...

where–a indicates that all the files in the package are to be sent,file_package_nameis the name of your file package, andendpoint_nameis the name of the self-service terminal to which theprofile is to be distributed. Include the@Endpoint: keyword oncefor each endpoint.

For more information about thewdistfp command, refer toTME 10Software Distribution Reference Manual.


7.D

istributingS

oftware

66 Version 1.0

Event Classes

This appendix describes the event classes that the Tivoli Self-ServiceTerminal Manager defines, including:

¶ Events received from the Tivoli Self-Service Terminal Managermonitors (see “Monitor Event Classes” on page 68)

¶ Events received from the event adapter (see “Status EventClasses” on page 69)

¶ Tivoli Enterprise Console event slots for the Tivoli Self-ServiceTerminal Manager status events (see “Event Slots for StatusEvents” on page 78)

¶ Event filtering provided by the event adapter and the eventservice (see “Default Event Filtering” on page 79)

Note: Tivoli Enterprise Console includes a rules engine thatprocesses events according to a set of rules that are providedby applications or added by users. Rules correlate relatedevents or sets of events and, where possible, give automatedresponses. You can write rules that are tailored for yourinstallation. Refer to theTME 10 Enterprise Console RuleBuilder’s Guidefor information about using the TivoliEnterprise Console graphical rule editor to create rules tomatch your specific event-management needs.

A


A.

Event

Classes

Monitor Event ClassesThe following table lists the Tivoli Self-Service Terminal Managermonitor event classes.

Monitor Name Tivoli Enterprise Console ClassName

Camera CAM

Camera Pictures CAMPics

Camera State CAMState

Cash Dispenser CDM

Cash Dispenser Cash Units CDMCashUnits

Cash Dispenser Logical Unit Level CDMLogicalUnitLvl

Cash Dispenser Logical Unit State CDMLogicalUnitState

Cash Dispenser Physical Unit Level CDMPhyUnitLvl

Cash Dispenser Physical Unit State CDMPhyUnitState

Cash Dispenser Safe Door CDMSafeDoor

Check Reader CHK

Check Reader Ink CHKInk

Check Reader Lamp CHKLamp

Check Reader Media CHKMedia

Depository DEP

Depository Container Level DEPContainerLvl

Depository Container State DEPContainerState

Depository Envelope DEPEnv

Depository Printer DEPPtr

Depository Toner DEPToner

ID Card Reader IDC

ID Card Reader Media IDCMedia

ID Card Reader Retain Bin Level IDCRetBinLvl

PIN Pad PIN

PIN Pad Encryption State PINEncryptState

PIN Pad State PINState

68 Version 1.0

Monitor Name Tivoli Enterprise Console ClassName

Printer PTR

Printer Bin Level PTRBinLvl

Printer Lamp PTRLamp

Printer Retract Bin PTRRetBin

Printer Supplies PTRSup

Sensor Ambient Light SIUAmbLight

Sensor Door SIUDoor

Sensor Proximity SIUProximity

Sensor State SIUState

Sensors SIU

SST SST

SST Open State SSTOpenState

SST Operation Mode SSTOpMode

Text Terminal TTU

Text Terminal State TTUState

Status Event ClassesWFS_Event is a superclass that defines the Tivoli Self-ServiceTerminal Manager status events that are forwarded to the eventserver from the NT event adapter running on a Windows NT XFSself-service terminal. It includes event classes for:¶ Camera (see “Camera Event Classes” on page 70)¶ Cash dispenser (see “Cash Dispenser Event Classes” on page 70)¶ Depository (see “Depository Event Classes” on page 71)¶ ID card reader (see “ID Card Reader Event Classes” on page 71)¶ PIN pad (see “PIN Pad Event Classes” on page 72)¶ Printer (see “Printer Event Classes” on page 73)¶ Sensor (see “Sensor Event Classes” on page 73)¶ Vendor-dependent mode (see “Vendor-Dependent-Mode Event

Classes” on page 78)


A.

Event

Classes

Notes:

1. No event classes are defined for check reader or text terminaldevices.

2. Some event classes have one or more levels of subevents. Thetop level event class is known as the parent event. Wheneverpossible, a level 1 or 2 subevent is returned instead of the parentevent. For sensors, a level 3 subevent can also be returned and,when available, is returned in the sst_sensor_state slot in theevent. In the tables in this section, the events are shown asfollows:

Event Class Name Description

Parent event name Description of the parent event

– Level 1 subevent name Description of the level 1 subevent

– – Level 2 subevent name Description of the level 2 subevent.When applicable, level 3 subevents arelisted as follows:– Level 3 subevent name 1– Level 3 subevent name 2...– Level 3 subevent name n

Camera Event ClassesThis table describes the event classes for camera devices.


WFS_USRE_CAM_MEDIATHRESHOLD The camera recording media reached athreshold.

– WFS_CAM_MEDIAFULL The camera recording media is full.

– WFS_CAM_MEDIAHIGH The camera recording media is almostfull.

Cash Dispenser Event ClassesThis table describes the event classes for cash dispenser devices.

70 Version 1.0


WFS_SRVE_CDM_BILLSTAKEN The bills have been removed.

WFS_SRVE_CDM_CASHUNITINFOCHANGED A cash unit was exchanged or added orthe contents of the cash unit weremodified.

WFS_SRVE_CDM_SAFEDOORCLOSED The safe door has been closed.

WFS_SRVE_CDM_SAFEDOOROPEN The safe door has been opened.

WFS_SRVE_CDM_TELLERINFOCHANGED The tallies assigned to a teller havechanged.

WFS_USRE_CDM_CASHUNITTHRESHOLD A cash unit has reached a threshold.

Depository Event ClassesThis table describes the event classes for depository devices.


WFS_SRVE_DEP_CONTINSERTED A depository container has been inserted.

WFS_SRVE_DEP_CONTREMOVED A depository container has been removed.

WFS_SRVE_DEP_ENVTAKEN The envelope has been taken.

WFS_USRE_DEP_DEPTHRESHOLD The depository container has reached athreshold.

– WFS_DEP_DEPFULL The depository container is full.

– WFS_DEP_DEPHIGH The depository container is nearly full.

WFS_USRE_DEP_ENVTHRESHOLD The depository envelope supply hasreached a threshold.

– WFS_DEP_ENVEMPTY The depository envelope supply is empty.

– WFS_DEP_ENVLOW The depository envelope supply is low.

WFS_USRE_DEP_TONERTHRESHOLD The depository toner or ink has reached athreshold.

– WFS_DEP_TONEMPTY The depository toner or ink is empty.

– WFS_DEP_TONLOW The depository toner or ink is low.

ID Card Reader Event ClassesThis table describes the event classes for ID card reader devices.


A.

Event

Classes


WFS_SRVE_IDC_CARDACTION The card was retained or ejected whenthe device was powered on or off.

– WFS_IDC_CARDREADPOSITION The card has been moved to the readposition.

– WFS_IDC_CARDREJECTED The card has been ejected.

– WFS_IDC_CARDRETAINED The card has been retained.

– WFS_IDC_MEDIAENTERING The card is entering the reader.

– WFS_IDC_MEDIAPRESENT The card is present in the reader.

– WFS_IDC_MEDIAUNKNOWN The position of the card cannot bedetermined.

WFS_SRVE_IDC_MEDIAREMOVED The card has been removed.

WFS_USRE_IDC_RETAINBINTHRESHOLD The ID card reader retain bin has reacheda threshold.

– WFS_IDC_RETAINBINFULL The ID card reader retain bin is full.

– WFS_IDC_RETAINBINHIGH The ID card reader retain bin is nearlyfull.

– WFS_IDC_RETAINBINOK The ID card reader retain bin is empty.

PIN Pad Event ClassesThis table describes the event classes for PIN pad devices.


WFS_SRVE_PIN_ILLEGAL_KEY_ACCESS A PIN pad encryption key access errorhas occurred.

– WFS_ERR_PIN_KEYNOTFOUND The specified PIN pad encryption keywas not loaded.

– WFS_ERR_PIN_KEYNOVALUE The specified PIN pad encryption key isnot loaded.

– WFS_ERR_PIN_USEVIOLATION The PIN pad encryption key does notsupport the specified use.

WFS_SRVE_PIN_INITIALIZED The PIN pad encryption module isinitialized.

– WFS_ERR_PIN_ACCESSDENIED The PIN pad encryption module is eithernot initialized or not ready.

72 Version 1.0


– WFS_ERR_PIN_INVALIDID The ID entered on the PIN pad is notvalid.

Printer Event ClassesThis table describes the event classes for printer event classes.


WFS_SRVE_PTR_MEDIAINSERTED The media has been entered in anunsolicited manner.

WFS_SRVE_PTR_MEDIATAKEN The ejected media has been taken.

WFS_USRE_PTR_PAPERTHRESHOLD The printer paper has reached athreshold.

– WFS_PTR_PAPERLOW The printer paper is low.

– WFS_PTR_PAPEROUT The printer paper is out.

WFS_USRE_PTR_RETRACTBINTHRESHOLD The printer retract bin has reached athreshold.

– WFS_PTR_RETRACTBINFULL The printer retract bin is full.

– WFS_PTR_RETRACTBINHIGH The printer retract bin is high.

WFS_USRE_PTR_TONERTHRESHOLD The printer toner or ink has reached athreshold.

– WFS_PTR_TONERLOW The printer toner or ink is low.

– WFS_PTR_TONEROUT The printer toner or ink is out.

Sensor Event ClassesThis table describes the event classes for sensor devices.


WFS_SRVE_SIU_PORT_STATUS The state of a port has changed.

– WFS_SIU_AUXILIARIES The state of the auxiliary indicator porthas changed.


A.

Event

Classes


– – WFS_SIU_UPS The state of the UPS device has changed.Sensor states returned are:– WFS_SIU_AVAILABLE– WFS_SIU_ENGAGED– WFS_SIU_LOW– WFS_SIU_NOT_AVAILABLE– WFS_SIU_POWERING– WFS_SIU_RECOVERED– unknown

– – WFS_SIU_VOLUME The state of the volume control devicehas changed. Sensor states returned are:– WFS_SIU_NOT_AVAILABLE– number (integer from 1 through 1000)

– – unknown An unknown auxiliary indicator portevent has occurred.

– WFS_SIU_DOORS The state of the door sensor port haschanged. Sensor states returned for alldoor events are:– WFS_SIU_AJAR– WFS_SIU_BOLTED– WFS_SIU_CLOSED– WFS_SIU_JAMMED– WFS_SIU_KEYBOARD– WFS_SIU_LOCKED– WFS_SIU_NOT_AVAILABLE– WFS_SIU_OPEN– WFS_SIU_SERVICE– unknown

– – WFS_SIU_CABINET The state of the cabinet doors haschanged.

– – WFS_SIU_SAFE The state of the safe doors has changed.

– – WFS_SIU_VANDALSHIELD The state of the vandal shield haschanged.

– – unknown An unknown door sensor port event hasoccurred.

74 Version 1.0


– WFS_SIU_GUIDLIGHTS The state of the guidance light port haschanged. Sensor states returned for allguidance light events are:– WFS_SIU_CONTINUOUS– WFS_SIU_MEDIUM_FLASH– WFS_SIU_NOT_AVAILABLE– WFS_SIU_OFF– WFS_SIU_QUICK_FLASH– WFS_SIU_SLOW_FLASH– unknown

– – WFS_SIU_BILLACCEPTOR The state of the guidance light for thebill acceptor has changed.

– – WFS_SIU_CARDUNIT The state of the guidance light for the IDcard reader has changed.

– – WFS_SIU_CHEQUEUNIT The state of the guidance light for thecheck unit has changed.

– – WFS_SIU_COINDISPENSER The state of the guidance light for thecoin dispenser has changed.

– – WFS_SIU_ENVDEPOSITORY The state of the guidance light for theenvelope depository has changed.

– – WFS_SIU_ENVDISPENSER The state of the guidance light for theenvelope dispenser has changed.

– – WFS_SIU_NOTESDISPENSER The state of the guidance light for thenote dispenser has changed.

– – WFS_SIU_PASSBOOKPRINTER The state of the guidance light for thepassbook printer has changed.

– – WFS_SIU_PINPAD The state of the guidance light for thePIN pad has changed.

– – WFS_SIU_RECEIPTPRINTER The state of the guidance light for thereceipt printer has changed.

– – unknown An unknown guidance light port eventhas occurred.

– WFS_SIU_INDICATORS The state of the status indicator port haschanged.


A.

Event

Classes


– – WFS_SIU_AUDIO The state of the audio indicator haschanged. Sensor states returned are:– WFS_SIU_CONTINUOUS– WFS_SIU_CRITICAL– WFS_SIU_ERROR– WFS_SIU_EXCLAMATION– WFS_SIU_KEYPRESS– WFS_SIU_NOT_AVAILABLE– WFS_SIU_OFF– WFS_SIU_WARNING– unknown

– – WFS_SIU_FASCIALIGHT The state of the fascia light has changed.Sensor states returned are:– WFS_SIU_NOT_AVAILABLE– WFS_SIU_OFF– WFS_SIU_ON– unknown

– – WFS_SIU_HEATING The state of the heating device haschanged. Sensor states returned are:– WFS_SIU_NOT_AVAILABLE– WFS_SIU_OFF– WFS_SIU_ON– unknown

– – WFS_SIU_OPENCLOSE The state of the open indicator haschanged. Sensor states returned are:– WFS_SIU_CLOSED– WFS_SIU_NOT_AVAILABLE– WFS_SIU_OPEN– unknown

– – unknown An unknown status indicator port eventhas occurred.

– WFS_SIU_SENSORS The state of the input sensors port haschanged.

76 Version 1.0


– – WFS_SIU_AMBLIGHT The state of the ambient light sensor haschanged. Sensor states returned are:– WFS_SIU_DARK– WFS_SIU_LIGHT– WFS_SIU_MEDIUM_LIGHT– WFS_SIU_NOT_AVAILABLE– WFS_SIU_VERY_DARK– WFS_SIU_VERY_LIGHT– unknown

– – WFS_SIU_HEAT The state of the heat sensor has changed.Sensor states returned are:– WFS_SIU_NOT_AVAILABLE– WFS_SIU_OFF– WFS_SIU_ON– unknown

– – WFS_SIU_INTTAMPER The state of the internal tamper sensorhas changed. Sensor states returned are:– WFS_SIU_NOT_AVAILABLE– WFS_SIU_OFF– WFS_SIU_ON– unknown

– – WFS_SIU_OPERATORSWITCH The state of the operator switch haschanged. Sensor states returned are:– WFS_SIU_MAINTENANCE– WFS_SIU_NOT_AVAILABLE– WFS_SIU_RUN– WFS_SIU_SUPERVISOR– unknown

– – WFS_SIU_PROXIMITY The state of the proximity sensor haschanged. Sensor states returned are:– WFS_SIU_NOT_AVAILABLE– WFS_SIU_NOT_PRESENT– WFS_SIU_PRESENT– unknown


A.

Event

Classes


– – WFS_SIU_SEISMIC The state of the seismic sensor haschanged. Sensor states returned are:– WFS_SIU_NOT_AVAILABLE– WFS_SIU_OFF– WFS_SIU_ON– unknown

– – WFS_SIU_TAMPER The state of the tamper sensor haschanged. Sensor states returned are:– WFS_SIU_NOT_AVAILABLE– WFS_SIU_OFF– WFS_SIU_ON– unknown

Vendor-Dependent-Mode Event ClassesThis table describes the event classes for vendor-dependent mode.


WFS_SRVE_VDM_ENTER_MODE_REQ A request has been made to entervendor-dependent mode.

WFS_SRVE_VDM_EXIT_MODE_REQ A request has been made to exitvendor-dependent mode.

WFS_SYSE_VDM_MODEENTERED The system has entered vendor-dependentmode.

WFS_SYSE_VDM_MODEEXITED The system has exited vendor-dependentmode.

Event Slots for Status EventsThe following table describes the event slots for the TivoliSelf-Service Terminal Manager status (WFS_Event) event classes.

Event Slot Description

category The classification of the event (None)

date The date of the event

eventType The type of event (Information)

78 Version 1.0

Event Slot Description

id The user ID on the self-service terminal

sid The system ID of the self-service terminal

sst_device The service class of the device, as listed in“Service Classes and Aliases” on page 115

sst_sensor_state The level 3 subevent for sensors

sub_origin The host name of the self-service terminal

sub_source The event service program (xfseventserv)

Default Event FilteringThe default Tivoli Self-Service Terminal Manager events filtered bythe event service if the event service configuration file is missing orunusable are:¶ WFS_SRVE_CDM_BILLSTAKEN¶ WFS_SRVE_DEP_ENVTAKEN¶ WFS_SRVE_VDM_ENTER_MODE_REQ¶ WFS_SRVE_VDM_EXIT_MODE_REQ¶ WFS_SYSE_VDM_MODEENTERED¶ WFS_SYSE_VDM_MODEEXITED

Note: To make all events available for logging and forwarding tothe event server, specify<LOG>YES</LOG> for these events ina valid event service configuration file.

No Tivoli Self-Service Terminal Manager events are filtered by thedefault event service configuration file. The logging for each of theparent events is set to YES. For information on changing the eventfiltering in the event service configuration file, see “Filtering Eventsat the Self-service Terminal” on page 37.

The Tivoli Self-Service Terminal Manager events filtered by thedefault event adapter configuration file are:¶ WFS_SIU_AUDIO¶ WFS_SIU_BILLACCEPTOR¶ WFS_IDC_CARDEJECTED¶ WFS_IDC_CARDREADPOSITION


A.

Event

Classes

¶ WFS_SIU_CARDUNIT¶ WFS_SIU_CHEQUEUNIT¶ WFS_SIU_COINDISPENSER¶ WFS_SIU_ENVDEPOSITORY¶ WFS_SIU_ENVDISPENSER¶ WFS_SIU_FASCIALIGHT¶ WFS_SIU_GUIDLIGHTS¶ WFS_SIU_HEATING¶ WFS_SIU_INDICATORS¶ WFS_SIU_NOTESDISPENSER¶ WFS_SIU_OPENCLOSE¶ WFS_SIU_PASSBOOKPRINTER¶ WFS_SIU_PINPAD¶ WFS_SIU_RECEIPTPRINTER¶ WFS_IDC_RETAINBINOK¶ WFS_SIU_VOLUME¶ WFS_SRVE_IDC_MEDIAREMOVED

For information on changing the event filtering in the event adapterconfiguration file, see “Configuring the Event Adapter” on page 31.

80 Version 1.0

Monitoring Collection

The Tivoli Self-Service Terminal Manager monitoring collection,SST_XFS, provides monitoring sources for managed self-serviceterminals. This appendix:

¶ Lists the command-line-interface names for each monitoringsource (see “CLI Names”)

¶ Describes the monitoring sources in the monitoring collection(see “Monitor Sources” on page 83)

CLI NamesThis table shows the command-line-interface (CLI) names andarguments for each monitoring source.

GUI Name CLI Name

Camera CAM

Camera Pictures CAMPics

Camera State CAMState

Cash Dispenser CDM

Cash Dispenser Cash Units CDMCashUnits

Cash Dispenser Logical Unit Level CDMLogicalUnitLvl

Cash Dispenser Logical Unit State CDMLogicalUnitState

Cash Dispenser Physical Unit Level CDMPhyUnitLvl

Cash Dispenser Physical Unit State CDMPhyUnitState

Cash Dispenser Safe Door CDMSafeDoor

B


B.

Monitoring

Collection

GUI Name CLI Name

Check Reader CHK

Check Reader Ink CHKInk

Check Reader Lamp CHKLamp

Check Reader Media CHKMedia

Depository DEP

Depository Container Level DEPContainerLvl

Depository Container State DEPContainerState

Depository Envelope DEPEnv

Depository Printer DEPPtr

Depository Toner DEPToner

ID Card Reader IDC

ID Card Reader Media IDCMedia

ID Card Reader Retain Bin Level IDCRetBinLvl

PIN Pad PIN

PIN Pad Encryption State PINEncryptState

PIN Pad State PINState

Printer PTR

Printer Bin Level PTRBinLvl

Printer Lamp PTRLamp

Printer Retract Bin PTRRetBin

Printer Supplies PTRSup

Sensors SIU

Sensor Ambient Light SIUAmbLight

Sensor Door SIUDoor

Sensor Proximity SIUProximity

Sensor State SIUState

SST SST

SST Open State SSTOpenState

SST Operation Mode SSTOpMode

Text Terminal TTU

Text Terminal State TTUState

82 Version 1.0

Monitor SourcesThe collection contains the following kinds of monitor sources:¶ General (see “General Monitor Sources”)¶ Printer (see “Printer Monitor Sources” on page 84)¶ Cash dispenser (see “Cash Dispenser Monitor Sources” on

page 87)¶ Depository (see “Depository Monitor Sources” on page 89)¶ Sensor and indicator (see “Sensor Monitor Sources” on page 90)¶ Camera (see “Camera Monitor Sources” on page 92)¶ ID card reader (see “ID Card Reader Monitor Sources” on

page 93)¶ PIN pad (see “PIN Pad Monitor Sources” on page 94)¶ Text terminal unit (see “Text Terminal Unit Monitor Sources” on

page 94)¶ Check reader and scanner (see “Check Reader Monitor Sources”

on page 95)

Note: For all monitors in the SST_XFS monitoring collection thathave a Logical Name argument, you can specifyDefault asthe logical name of the device to be monitored. SpecifyingDefault results in the monitor running on the first (or only)device in the list of logical service keys in the Windows NTregistry for the service class associated with the configuredmonitor. This is particularly useful in cases where only onedevice of a certain class is defined; in those cases, you cansimply specifyDefault rather than the logical service name ofthe device.

General Monitor SourcesThese monitoring sources provide information about a self-serviceterminal:

SST This monitor reports the overall state of a Windows NT XFSself-service terminal. The state reported combines the SSTOpen State monitor and the overall states of all devicesconfigured for the self-service terminal. Arguments: None.


B.

Monitoring

Collection

SST Open StateThis monitor reports the state of an open indicator on aWindows NT XFS self-service terminal. Arguments:

¶ Logical name: The logical service name of a specificsensor to monitor orDefault to monitor the first or onlysensor device configured.

SST Operation ModeThis monitor reports the operation mode on a Windows NTXFS self-service terminal. The mode reported is the settingof the operator switch. Arguments:

¶ Logical name: The logical service name of a specificsensor to monitor orDefault to monitor the first or onlysensor device configured.

Printer Monitor SourcesThese monitoring sources provide information about a printerattached to a self-service terminal.

Note: The printer monitor sources can monitor journal, receipt,passbook, and document printers.

PrinterThis monitor reports the overall state of a printer on aWindows NT XFS self-service terminal. The state reportedcombines the states of the device, the media, the paper, thetoner, the ink, the lamp, and the retract bin. Arguments:

¶ Logical name: The logical service name of a specificprinter to monitor,All to monitor all printers configured,or Default to monitor the first or only printerconfigured.

Note: If you specify all printers:

¶ A reported state of Up indicates that all theprinters are up.

¶ A reported state of Down indicates that at leastone printer is down.

84 Version 1.0

¶ A reported state of Needs attention indicates acombination of printer states.

Printer Bin LevelThis monitor reports the level of the retract bin for a printeron a Windows NT XFS self-service terminal. The levelreported indicates as a percentage how full the bin is.Arguments:

¶ Logical name: The logical service name of a specificprinter to monitor, orDefault to monitor the first or onlyprinter configured.

¶ Bin: The bin type.

Printer LampThis monitor reports the state of the lamp for a printer on aWindows NT XFS self-service terminal. Arguments:



¶ A reported state of OK indicates that the lampsfor all the printers are OK.

¶ A reported state of Out indicates that the lamp forat least one printer is out.

¶ A reported state of Fading indicates acombination of lamp states.

Printer Retract BinThis monitor reports the state of the retract bin for a printeron a Windows NT XFS self-service terminal. Arguments:



B.

Monitoring

Collection


¶ A reported state of OK indicates that the bins forall the printers are OK.

¶ A reported state of Full indicates that the bin forat least one printer is full.

¶ A reported state of High indicates a combinationof bin levels.

Printer SuppliesThis monitor reports the state of the supplies for a printer ona Windows NT XFS self-service terminal. It monitors thepaper, the toner, and the ink. Arguments:


¶ Supplies: The type of supply, orAll to monitor allsupplies for the specified printer.

Notes:

1. If you specify all printers:

¶ A reported state of OK indicates that the specifiedsupply for all the printers is OK.

¶ A reported state of Empty indicates that the specifiedsupply for at least one printer is empty.

¶ A reported state of Low indicates a combination ofstates for the specified supply.

2. If you specify all supplies for a specific printer:

¶ A reported state of OK indicates that all supplies forthe specified printer are OK.

¶ A reported state of Empty indicates that at least oneof the supplies (paper, toner, or ink) for the specifiedprinter is empty.

86 Version 1.0

¶ A reported state of Low indicates a combination ofOK and Low states for the supplies for the specifiedprinter.

3. If you specify all printers and all supplies:

¶ A reported state of OK indicates that all supplies forall the printers are OK.

¶ A reported state of Empty indicates that at least onesupply for at least one printer is empty.

¶ A reported state of Low indicates a combination ofstates for all supplies for the printers.

Cash Dispenser Monitor SourcesThese monitoring sources provide information about a cash dispenserattached to a self-service terminal:

Cash DispenserThis monitor reports the overall state of a cash dispenser ona Windows NT XFS self-service terminal. The state reportedcombines the states of the device, the safe door, thedispenser, all shutters, and all logical cash units. Arguments:

¶ Logical name: The logical service name of a specificcash dispenser to monitor, orDefault to monitor the firstor only ID cash dispenser configured.

Cash Dispenser Cash UnitsThis monitor reports the state of the logical cash units for acash dispenser on a Windows NT XFS self-service terminal.The state reported is the dispenser state for the cashdispenser. Arguments:


Cash Dispenser Logical Unit LevelThis monitor reports the level of a logical cash unit for acash dispenser on a Windows NT XFS self-service terminal.The level reported indicates as a percentage how full thelogical cash unit is. Arguments:


B.

Monitoring

Collection


¶ Logical cash unit: The logical number for the cash unit.

Cash Dispenser Logical Unit StateThis monitor reports the state of a logical cash unit for acash dispenser on a Windows NT XFS self-service terminal.Arguments:


¶ Logical cash unit: The logical number for the cash unit,or All to monitor all logical cash units for the specifiedcash dispenser.

Cash Dispenser Physical Unit LevelThis monitor reports the number of bills in a physical cashunit for a cash dispenser on a Windows NT XFS self-serviceterminal. Arguments:


¶ Logical cash unit: The logical number for the cash unit.

¶ Physical cash unit: The name of the physical cash unit.

Cash Dispenser Physical Unit StateThis monitor reports the state of a physical cash unit for acash dispenser on a Windows NT XFS self-service terminal.Arguments:


¶ Logical cash unit: The logical number for the cash unit,or All to monitor all logical cash units for the specifiedcash dispenser.

88 Version 1.0

¶ Physical cash unit: The name of the physical cash unit,or All to monitor all physical cash units for the specifiedlogical cash unit. A name can be specified only if alogical number was specified for the logical cash unit.

Cash Dispenser Safe DoorThis monitor reports the state of the safe door for a cashdispenser on a Windows NT XFS self-service terminal.Arguments:


Depository Monitor SourcesThese monitoring sources provide information about a depositoryattached to a self-service terminal.

DepositoryThis monitor reports the overall state of a depository on aWindows NT XFS self-service terminal. The state reportedcombines the states of the device, the container, thetransport, the envelope supply, the envelope dispenser, theprinter, the toner, and the shutter. Arguments:

¶ Logical name: The logical service name of a specificdepository to monitor, orDefault to monitor the first oronly depository configured.

Depository Container LevelThis monitor reports the number of envelopes or bags in thecontainer for a depository on a Windows NT XFSself-service terminal. Arguments:


Depository Container StateThis monitor reports the state of the container for adepository on a Windows NT XFS self-service terminal.Arguments:


B.

Monitoring

Collection


Depository EnvelopeThis monitor reports the state of the envelope supply for adepository on a Windows NT XFS self-service terminal.Arguments:


Depository PrinterThis monitor reports the state of the printer for a depositoryon a Windows NT XFS self-service terminal. Arguments:


Depository TonerThis monitor reports the state of the toner for a depositoryon a Windows NT XFS self-service terminal. Arguments:


Sensor Monitor SourcesThese monitoring sources provide information about sensors andindicators attached to a self-service terminal:

SensorsThis monitor reports the overall state of the sensors on aWindows NT XFS self-service terminal. The state reportedcombines the states of the device, the tamper sensor, theinternal tamper sensor, the seismic sensor, and the heatsensor. Arguments:

¶ Logical name: The logical service name of a specificsensor device to monitor, orDefault to monitor the firstor only sensor device configured.

90 Version 1.0

Sensor Ambient LightThis monitor reports the state of an ambient light sensor on aWindows NT XFS self-service terminal. Arguments:


Sensor DoorThis monitor reports the state of a door sensor on aWindows NT XFS self-service terminal. It monitors thecabinet, safe, and vandal-shield doors. Arguments:


¶ Door: The type of door.

Note: The ajar and jammed states are reported only for avandal-shield door and the bolted state is reportedonly for a cabinet or safe door.

Sensor ProximityThis monitor reports the state of a proximity sensor on aWindows NT XFS self-service terminal. Arguments:


Sensor StateThis monitor reports the state of an individual sensor on aWindows NT XFS self-service terminal. It monitors thetamper, internal tamper, seismic, and heat sensors.Arguments:


¶ Sensor: The type of sensor, orAll to monitor all typesconfigured for the specified sensor.


B.

Monitoring

Collection

Note: If you specify all for the sensor type:

¶ A reported state of on indicates that all of thesensor types for the specified sensor are on.

¶ A reported state of off indicates that at least oneof the sensor types for the specified sensor is off.

Camera Monitor SourcesThese monitoring sources provide information about a cameraattached to a self-service terminal:

CameraThis monitor reports the overall state of a camera on aWindows NT XFS self-service terminal. The state reportedcombines the states of the device, the media, and themonitoring cameras. Arguments:

¶ Logical name: The logical service name of a specificcamera to monitor, orDefault to monitor the first oronly camera configured.

Camera PicturesThis monitor reports the number of pictures that arecurrently stored for a camera on a Windows NT XFSself-service terminal. Arguments:


Camera StateThis monitor reports the state of a camera on a Windows NTXFS self-service terminal. It monitors the room, person, andexit-slot cameras. Arguments:


¶ Camera: The specific monitoring camera, orAll tomonitor all monitoring cameras configured for thespecified camera.

92 Version 1.0

Note: If you specify all monitoring cameras:

¶ A reported state of up indicates that all themonitoring cameras for the specified camera areup.

¶ A reported state of down indicates that at leastone monitoring camera for the specified camera isdown.

ID Card Reader Monitor SourcesThese monitoring sources provide information about an ID cardreader attached to a self-service terminal:

ID Card ReaderThis monitor reports the overall state of an ID card reader ona Windows NT XFS self-service terminal. The state reportedcombines the states of the device, the media, and the retainbin. Arguments:

¶ Logical name: The logical service name of a specific IDcard reader to monitor, orDefault to monitor the first oronly ID card reader configured.

ID Card Reader MediaThis monitor reports the state of the media for an ID cardreader on a Windows NT XFS self-service terminal.Arguments:


ID Card Reader Retain Bin LevelThis monitor reports the level of the retain bin for an IDcard reader on a Windows NT XFS self-service terminal.The level reported indicates as a percentage how full the binis. Arguments:



B.

Monitoring

Collection

PIN Pad Monitor SourcesThese monitoring sources provide information about a PIN padattached to a self-service terminal:

PIN PadThis monitor reports the overall state of a PIN pad on aWindows NT XFS self-service terminal. The state reportedcombines the states of the device and the encryption module.Arguments:

¶ Logical name: The logical service name of a specificPIN pad to monitor, orDefault to monitor the first oronly PIN pad configured.

PIN Pad Encryption StateThis monitor reports the state of the encryption module for aPIN pad on a Windows NT XFS self-service terminal.Arguments:


PIN Pad StateThis monitor reports the device state of a PIN pad on aWindows NT XFS self-service terminal. Arguments:


Text Terminal Unit Monitor SourcesThese monitoring sources provide information about a text terminalunit attached to a self-service terminal:

Text TerminalThis monitor reports the overall state of a text terminal on aWindows NT XFS self-service terminal. The state reportedcombines the states of the device and the keyboard.Arguments:

94 Version 1.0

¶ Logical name: The logical service name of a specifictext terminal to monitor, orDefault to monitor the firstor only text terminal configured.

Text Terminal StateThis monitor reports the state of the keyboard for a textterminal on a Windows NT XFS self-service terminal. Itmonitors the keyboard state and the keyboard lock state.Arguments:

¶ Logical name: The logical service name of a specifictext terminal to monitor, orDefault to monitor the firstor only text terminal configured.

¶ Field: The keyboard item to monitor.

Check Reader Monitor SourcesThese monitoring sources provide information about a check readeror scanner attached to a self-service terminal:

Check ReaderThis monitor reports the overall state of a check reader on aWindows NT XFS self-service terminal. The state reportedcombines the states of the device, the media, the ink, and thelamp. Arguments:

¶ Logical name: The logical service name of a specificcheck reader to monitor, orDefault to monitor the firstor only check reader configured.

Check Reader InkThis monitor reports the state of the ink for a check readeron a Windows NT XFS self-service terminal. Arguments:


Check Reader LampThis monitor reports the state of the lamp for a check readeron a Windows NT XFS self-service terminal. Arguments:


B.

Monitoring

Collection


Check Reader MediaThis monitor reports the state of the media of a check readeron a Windows NT XFS self-service terminal. Arguments:


96 Version 1.0

Inventory Tables, Views, andQueries

This appendix describes the inventory tables, views, and queriesprovided with Tivoli Self-Service Terminal Manager. Inventoryinformation is provided for:¶ “Camera Capabilities and Status” on page 98¶ “Cash Dispenser Capabilities” on page 99¶ “Cash Dispenser Logical Cash Unit Capabilities and Status” on

page 100¶ “Cash Dispenser Physical Cash Unit Capabilities and Status” on

page 101¶ “Cash Dispenser Status” on page 101¶ “Check Reader Capabilities” on page 102¶ “Check Reader Status” on page 103¶ “Depository Capabilities” on page 104¶ “Depository Status” on page 105¶ “ID Card Reader Capabilities” on page 105¶ “ID Card Reader Status” on page 106¶ “PIN Pad Capabilities” on page 107¶ “PIN Pad Status” on page 108¶ “Printer Capabilities” on page 109¶ “Printer Status” on page 109¶ “Sensor Capabilities” on page 110¶ “Sensor Status” on page 111¶ “Text Terminal Capabilities” on page 112¶ “Text Terminal Status” on page 113

C


C.

InventoryTables,

View

s,and

Queries

Notes:

1. Columns denoted by an asterisk (*) are used in the table for theprimary key, which consists of the column or columns thatuniquely identify a row.

2. The TME_OBJECT_LABEL and TME_OBJECT_ID columns inviews and queries are from the Tivoli InventoryCOMPUTER_SYSTEM table.

Camera Capabilities and StatusDefinition

Information about the capabilities and status of a camera fora self-service terminal.

Table NameSST_XFS_CAMERA

View NameSSTXFSV_CAMERA

Query NameXFS_CAMERA_STATUS

Columns

HARDWARE_SYSTEM_ID* (table only)CONFIG_CHANGE_TYPE* (table only)CONFIG_CHANGE_TIME* (table only)TME_OBJECT_LABEL (view and query only)TME_OBJECT_ID (view and query only)DEV_NAME*STATUSMEDIA_STATEROOMPERSONEXIT_SLOTPICTURES_STOREDMAX_PICTURES

98 Version 1.0

Cash Dispenser CapabilitiesDefinition

Information about the capabilities of a cash dispenser for aself-service terminal.

Table NameSST_XFS_CP_CASH_DP

View NameSSTXFSV_CP_CASH_DP

Query NameXFS_CASH_DISPENSER_CAPABILITIES

Columns

HARDWARE_SYSTEM_ID* (table only)CONFIG_CHANGE_TYPE* (table only)CONFIG_CHANGE_TIME* (table only)TME_OBJECT_LABEL (view and query only)TME_OBJECT_ID (view and query only)DEV_NAME*TYPECOMPOUNDMAX_BILLS_DISPENSEMAX_COINS_DISPENSESHUTTERRETRACTDOOR_TIME_LOCKCOIN_DISPENSECASH_BOXCASH_INREFILLAUTO_DEPOSITVANDAL_CHECKSTACKERBILLS_TAKEN_SENSOROUTPUT_POSITIONS


C.

InventoryTables,

View

s,and

Queries

Cash Dispenser Logical Cash Unit Capabilities andStatus

DefinitionInformation about the capabilities and status of a logical cashunit for a self-service terminal.

Table NameSST_XFS_LG_CASH

View NameSSTXFSV_LG_CASH

Query NameXFS_LOGICAL_CASH_UNIT_STATUS

Columns

HARDWARE_SYSTEM_ID* (table only)CONFIG_CHANGE_TYPE* (table only)CONFIG_CHANGE_TIME* (table only)TME_OBJECT_LABEL (view and query only)TME_OBJECT_ID (view and query only)DEV_NAME*LOGICAL_ID*TYPECURRENCY_IDCURRENCY_VALUEINITIAL_COUNTDISPENSED_COUNTMIN_THRESHOLDMAX_THRESHOLDAPP_LOCKDEV_LOCKSTATUS

100 Version 1.0

Cash Dispenser Physical Cash Unit Capabilities andStatus

DefinitionInformation about the capabilities and status of a physicalcash unit for a self-service terminal.

Table NameSST_XFS_PHY_CASH

View NameSSTXFSV_PHY_CASH

Query NameXFS_PHYSICAL_CASH_UNIT_STATUS

Columns

HARDWARE_SYSTEM_ID* (table only)CONFIG_CHANGE_TYPE* (table only)CONFIG_CHANGE_TIME* (table only)TME_OBJECT_LABEL (view and query only)TME_OBJECT_ID (view and query only)DEV_NAME*LOGICAL_ID*PHYSICAL_ID*PHYSICAL_NAME*CURRENT_COUNTOPERATION

Cash Dispenser StatusDefinition

Information about the status of a cash dispenser for aself-service terminal.

Table NameSST_XFS_ST_CASH_DP

View NameSSTXFSV_ST_CASH_DP


C.

InventoryTables,

View

s,and

Queries

Query NameXFS_CASH_DISPENSER_STATUS

Columns

HARDWARE_SYSTEM_ID* (table only)CONFIG_CHANGE_TYPE* (table only)CONFIG_CHANGE_TIME* (table only)TME_OBJECT_LABEL (view and query only)TME_OBJECT_ID (view and query only)DEV_NAME*STATUSSAFE_DOORDISPENSERSTACKERLEFT_SHUTTERLEFT_TRANSPORTLEFT_OUTPUTCENTER_SHUTTERCENTER_TRANSPORTCENTER_OUTPUTRIGHT_SHUTTERRIGHT_TRANSPORTRIGHT_OUTPUT

Check Reader CapabilitiesDefinition

Information about the capabilities of a check reader devicefor a self-service terminal.

Table NameSST_XFS_CP_CHK_RDR

View NameSSTXFSV_CP_CHK_RDR

Query NameXFS_CHECK_READER_CAPABILITIES

Columns

102 Version 1.0

HARDWARE_SYSTEM_ID* (table only)CONFIG_CHANGE_TYPE* (table only)CONFIG_CHANGE_TIME* (table only)TME_OBJECT_LABEL (view and query only)TME_OBJECT_ID (view and query only)DEV_NAME*TYPECOMPOUNDMICROCRAUTO_FEEDPROG_ENDORSERENCODERSTAMP_LOCATIONIMG_CAPTUREPOCKETSFONT_LISTENCODE_LIST

Check Reader StatusDefinition

Information about the status of a check reader device for aself-service terminal.

Table NameSST_XFS_ST_CHK_RDR

View NameSSTXFSV_ST_CHK_RDR

Query NameXFS_CHECK_READER_STATUS

Columns

HARDWARE_SYSTEM_ID* (table only)CONFIG_CHANGE_TYPE* (table only)CONFIG_CHANGE_TIME* (table only)TME_OBJECT_LABEL (view and query only)TME_OBJECT_ID (view and query only)


C.

InventoryTables,

View

s,and

Queries

DEV_NAMESTATUSMEDIAINKAUTO_FEEDLAMP

Depository CapabilitiesDefinition

Information about the capabilities of a depository device fora self-service terminal.

Table NameSST_XFS_CP_DEPOSIT

View NameSSTXFSV_CP_DEPOSIT

Query NameXFS_DEPOSITORY_CAPABILITIES

Columns

HARDWARE_SYSTEM_ID* (table only)CONFIG_CHANGE_TYPE* (table only)CONFIG_CHANGE_TIME* (table only)TME_OBJECT_LABEL (view and query only)TME_OBJECT_ID (view and query only)DEV_NAME*TYPEENVELOPE_SUPPLYTRANSPORTPRINTERTONERSHUTTERPRINT_ON_RETRACTSRETRACT_TO_DEPOSITMAX_CHARS_PRINT

104 Version 1.0

Depository StatusDefinition

Information about the status of a depository device for aself-service terminal.

Table NameSST_XFS_ST_DEPOSIT

View NameSSTXFSV_ST_DEPOSIT

Query NameXFS_DEPOSITORY_STATUS

Columns

HARDWARE_SYSTEM_ID* (table only)CONFIG_CHANGE_TYPE* (table only)CONFIG_CHANGE_TIME* (table only)TME_OBJECT_LABEL (view and query only)TME_OBJECT_ID (view and query only)DEV_NAME*STATUSCONTAINERTRANSPORTENVELOPE_SUPPLYENVELOPE_DISPRPRINTERTONERSHUTTERDEPOSITS

ID Card Reader CapabilitiesDefinition

Information about the capabilities of the identification cardreader for a self-service terminal.

Table NameSST_XFS_CP_CRD_RDR


C.

InventoryTables,

View

s,and

Queries

View NameSSTXFSV_CP_CRD_RDR

Query NameXFS_CARD_READER_CAPABILITIES

Columns

HARDWARE_SYSTEM_ID* (table only)CONFIG_CHANGE_TYPE* (table only)CONFIG_CHANGE_TIME* (table only)TME_OBJECT_LABEL (view and query only)TME_OBJECT_ID (view and query only)DEV_NAME*TYPEREAD_TRACKWRITE_TRACKVENDOR_CHIP_PROTRETAIN_BIN_MAXSEC_TYPEPOWER_ON_ACTIONPOWER_OFF_ACTION

ID Card Reader StatusDefinition

Information about the status of the identification card readerfor a self-service terminal.

Table NameSST_XFS_ST_CRD_RDR

View NameSSTXFSV_ST_CRD_RDR

Query NameXFS_CARD_READER_STATUS

Columns

HARDWARE_SYSTEM_ID* (table only)CONFIG_CHANGE_TYPE* (table only)

106 Version 1.0

CONFIG_CHANGE_TIME* (table only)TME_OBJECT_LABEL (view and query only)TME_OBJECT_ID (view and query only)DEV_NAME*STATUSMEDIARETAIN_BINSECRETAIN_BIN_CARD_CT

PIN Pad CapabilitiesDefinition

Information about the capabilities of a personal identificationnumber keypad (PIN pad) for a self-service terminal.

Table NameSST_XFS_CP_PIN_PAD

View NameSSTXFSV_CP_PIN_PAD

Query NameXFS_PIN_PAD_CAPABILITIES

Columns

HARDWARE_SYSTEM_ID* (table only)CONFIG_CHANGE_TYPE* (table only)CONFIG_CHANGE_TIME* (table only)TME_OBJECT_LABEL (view and query only)TME_OBJECT_ID (view and query only)DEV_NAME*TYPECOMPOUNDENCRYPT_KEY_NUMENCRYPT_DES_EBCENCRYPT_DES_CBCENCRYPT_DES_MACENCRYPT_DES_CFBCENCRYPT_RSA


C.

InventoryTables,

View

s,and

Queries

ENCRYPT_ECMAENCRYPT_TPLDES_EBCENCRYPT_TPLDES_CBCENCRYPT_TPLDES_CFBENCRYPT_TPLDES_MACPIN_FORMATSDERIVE_ALGTHMPRESENT_ALGTHMDISPLAYCONNECTEDID_KEYVALIDATION_ALGTHM

PIN Pad StatusDefinition

Information about the status of a personal identificationnumber keypad (PIN pad) for a self-service terminal.

Table NameSST_XFS_ST_PIN_PAD

View NameSSTXFSV_ST_PIN_PAD

Query NameXFS_PIN_PAD_STATUS

Columns

HARDWARE_SYSTEM_ID* (table only)CONFIG_CHANGE_TYPE* (table only)CONFIG_CHANGE_TIME* (table only)TME_OBJECT_LABEL (view and query only)TME_OBJECT_ID (view and query only)DEV_NAME*STATUSENCRYPTION

108 Version 1.0

Printer CapabilitiesDefinition

Information about the capabilities of a printer for aself-service terminal.

Table NameSST_XFS_CP_PRINTER

View NameSSTXFSV_CP_PRINTER

Query NameXFS_PRINTER_CAPABILITIES

Columns

HARDWARE_SYSTEM_ID* (table only)CONFIG_CHANGE_TYPE* (table only)CONFIG_CHANGE_TIME* (table only)TME_OBJECT_LABEL (view and query only)TME_OBJECT_ID (view and query only)DEV_NAME*PRINTERCOMPOUNDRESREAD_MEDIAWRITE_MEDIASIZE_DETECTMEDIA_CTRLRETRACT_BIN_MAXMEDIA_STACKER_MAX

Printer StatusDefinition

Information about the status of a printer for a self-serviceterminal.

Table NameSST_XFS_ST_PRINTER


C.

InventoryTables,

View

s,and

Queries

View NameSSTXFSV_ST_PRINTER

Query NameXFS_PRINTER_STATUS

Columns

HARDWARE_SYSTEM_ID* (table only)CONFIG_CHANGE_TYPE* (table only)CONFIG_CHANGE_TIME* (table only)TME_OBJECT_LABEL (view and query only)TME_OBJECT_ID (view and query only)DEV_NAME*STATUSMEDIAPAPERTONERINKLAMPRETRACT_BINRETRACT_BIN_LEVELSTACKER_LEVEL

Sensor CapabilitiesDefinition

Information about the capabilities of a sensor for aself-service terminal.

Table NameSST_XFS_CP_SENSOR

View NameSSTXFSV_CP_SENSOR

Query NameXFS_SENSOR_CAPABILITIES

Columns

110 Version 1.0

HARDWARE_SYSTEM_ID* (table only)CONFIG_CHANGE_TYPE* (table only)CONFIG_CHANGE_TIME* (table only)TME_OBJECT_LABEL (view and query only)TME_OBJECT_ID (view and query only)DEV_NAME*SENSORS_PRESENTOPERATORTAMPERINTERNAL_TAMPERSEISMICHEATPROXIMITYAMBIENT_LIGHTCABINET_DOORSSAFE_DOORSVANDAL_SHIELDOPEN_CLOSEFASCIA_LIGHTAUDIOINTERNAL_HEATVOL_LEVEL_RECMDUPS

Sensor StatusDefinition

Information about the status of the sensors and indicators fora self-service terminal.

Table NameSST_XFS_ST_SENSOR

View NameSSTXFSV_ST_SENSOR

Query NameXFS_SENSOR_STATUS

Columns


C.

InventoryTables,

View

s,and

Queries

HARDWARE_SYSTEM_ID* (table only)CONFIG_CHANGE_TYPE* (table only)CONFIG_CHANGE_TIME* (table only)TME_OBJECT_LABEL (view and query only)TME_OBJECT_ID (view and query only)DEV_NAME*STATUSOPERATORTAMPERINTERNAL_TAMPERSEISMICHEATPROXIMITYAMBIENT_LIGHTCABINET_DOORSSAFE_DOORSVANDAL_SHIELDOPEN_CLOSEFASCIA_LIGHTAUDIOINTERNAL_HEATVOL_LEVELUPS

Text Terminal CapabilitiesDefinition

Information about the capabilities of a text terminal devicefor a self-service terminal.

Table NameSST_XFS_CP_TXT_TRM

View NameSSTXFSV_CP_TXT_TRM

Query NameXFS_TEXT_TERMINAL_CAPABILITIES

Columns

112 Version 1.0

HARDWARE_SYSTEM_ID* (table only)CONFIG_CHANGE_TYPE* (table only)CONFIG_CHANGE_TIME* (table only)TME_OBJECT_LABEL (view and query only)TME_OBJECT_ID (view and query only)DEV_NAME*TYPEMAX_RES_XMAX_RES_YNUM_LEDSKEY_TYPESKEYLOCKDISPLAY_LIGHTCURSOR_TYPEFORMS

Text Terminal StatusDefinition

Information about the status of a text terminal device for aself-service terminal.

Table NameSST_XFS_ST_TXT_TRM

View NameSSTXFSV_ST_TXT_TRM

Query NameXFS_TEXT_TERMINAL_STATUS

Columns

HARDWARE_SYSTEM_ID* (table only)CONFIG_CHANGE_TYPE* (table only)CONFIG_CHANGE_TIME* (table only)TME_OBJECT_LABEL (view and query only)TME_OBJECT_ID (view and query only)DEV_NAME*


C.

InventoryTables,

View

s,and

Queries

STATUSKEYBOARDKEYBOARD_LOCK

114 Version 1.0

Service Classes and Aliases

Tivoli Self-Service Terminal Manager enables you to manageself-service terminal devices that are configured using service classnames other than the standard service class names defined in theXFS interface specification.

The standard service class names used by Tivoli Self-ServiceTerminal Manager are:

CAM Camera

CDM Cash dispenser

CHK Check reader

DEP Depository

IDC ID card reader

PIN PIN pad

PTR Printer

SIU Sensor

TTU Text terminal

Note: The standard service class VDM (vendor-dependent mode) isnot recognized by Tivoli Self-Service Terminal Manager.

Using an alias file provided with Tivoli Self-Service TerminalManager, you can map non-standard service class names to the

D


D.

Service

Classes

andA

liases

standard XFS service class names. The alias file, sstxfsalias.xml,contains an element for each of the standard XFS service classnames except VDM, as follows:<xfsaliases>

<class><PTR> PRT,PBK </PTR><IDC> MSR </IDC><CDM> </CDM><PIN> </PIN><CHK> </CHK><DEP> </DEP><TTU> </TTU><SIU> </SIU><CAM> </CAM>

</class></xfsaliases>

A non-standard service class can be mapped to a standard serviceclass. For example, in the default alias file, PRT and PBK aredefined as the PTR service class and MSR is defined as the IDCservice class. As a result, any device configured with the PRT orPBK service class is managed as a PTR device, and any deviceconfigured with the MSR service class is managed as an IDC device.

You can use a text editor to add other non-standard service classnames to the alias file. The sstxfsalias.xml file is located in the$BINDIR/../generic/TME/sst/ntxfs/w32-ix86 directory on the TMRserver and in the %SystemRoot%\tivoli_sst\sstntxfs directory on theself-service terminal.

Notes:

1. Before you change this file, make a backup copy.

2. To define non-standard service class names, include one or morenon-standard class names in the element for the applicablestandard class name. For example, if you have a camera devicethat is configured as the XYZ service class, you can manage it asa standard camera device (service class CAM) if you change<CAM> </CAM> to <CAM> XYZ </CAM> in the alias file.

If you define several names, separate them by commas withoutany blanks or white spaces.

116 Version 1.0

3. If you change the file at the TMR server, your changes are sentto all Windows NT XFS self-service terminals subsequentlyconfigured. To send a changed alias file to a self-service terminalthat is already configured, it is recommended that you create anddistribute a software distribution file package.

4. If the alias file on a self-service terminal is missing or becomesunusable, only devices configured with standard service classnames will be managed.

To check the service class for any of your configured self-serviceterminal devices, look at the logical service key for that device inthe Windows NT registry. For more information about the WindowsNT registry keys, refer to the XFS interface specification.


D.

Service

Classes

andA

liases

118 Version 1.0

Finding and Correcting Problems

This appendix addresses common problems that you could encounterwhile using Tivoli Self-Service Terminal Manager to manage yourself-service terminals. It includes information about:

¶ Common troubleshooting techniques (see “CommonTroubleshooting Techniques”)

¶ Handling event management problems (see “TroubleshootingEvent Management Problems” on page 122

¶ Handling monitoring problems (see “Troubleshooting MonitoringProblems” on page 124)

¶ Handling inventory problems (see “Troubleshooting InventoryProblems” on page 125)

¶ Handling software distribution problems (see “TroubleshootingSoftware Distribution Problems” on page 126)

¶ Checking RIM (see “Checking RIM” on page 126)

Note: Much of the troubleshooting must be done locally at theself-service terminal.

Common Troubleshooting TechniquesThis section describes general troubleshooting techniques for mostTivoli Self-Service Terminal Manager problems. When youencounter a problem, use these techniques first to try to solve theproblem.

E


E.

Finding

andC

orrectingP

roblems

These techniques involve checking:¶ Endpoints (see “Checking a Self-service Terminal”)¶ The TMR server (see “Checking the TMR Server” on page 121)¶ Connectivity (see “Checking Connectivity” on page 121)

Checking a Self-service TerminalTo check a self-service terminal (endpoint):

¶ Ensure that Tivoli Self-Service Terminal Manager has beenconfigured at the self-service terminal. For more information, see“Configuring Self-service Terminals” on page 23.

Also, check the configuration log file, sstntxfs_config.log, in the$BINDIR/../generic/TME/sst/ntxfs/logs directory to see if anyproblems were logged during self-service terminal configuration.

Note: If you changed the log file path in theSST_XFS_Configuration file package, check the log fileyou specified in the File Package Properties window.

¶ Make sure that the endpoint is logged in to a Tivoli gateway.You can check this and other information about the endpoint,including the endpoint log file, using a Web browser. Use theEndpoint Manager to find the IP address and port number for theendpoint, and then point your Web browser at this URL:

http:// endpoint_IP_address:endpoint_port_number

¶ Verify that the XFS manager and the service provider softwareare installed and that the logical services for the self-serviceterminal peripheral devices are configured.

¶ Ensure that any non-standard service class names for yourself-service terminal devices have been mapped to standardservice class names using the Tivoli Self-Service TerminalManager alias file. For more information, see “Service Classesand Aliases” on page 115.

¶ Make sure that file system on the self-service terminal is notfull.

¶ Check the Windows NT application log to see if any problemshave been logged.

120 Version 1.0

¶ If you suspect a problem with the endpoint, set up endpointlogging as follows:

1. In the $LCF_DATDIR/dat/1/last.cfg file, set log_threshold to3, and save the change.

2. Display the log information by pointing your Web browser atthis URL:

http:// endpoint_IP_address:endpoint_port_number

Checking the TMR ServerTo check the TMR server:

¶ Verify that Tivoli Self-Service Terminal Manager is installed onthe TMR server by running thewlsinst –ah command. If it isnot installed, install it as described in “Installing” on page 11.

¶ If resources are missing in the SST_XFS policy region, addthem as described in “Installing Missing Resources” on page 15.If they are still missing, ensure that the associated Tivoliproducts (Tivoli Distributed Monitoring, Tivoli Inventory, TivoliEnterprise Console, and Tivoli Adapter Configuration Facility)are installed.

¶ Ensure that the Tivoli Management Framework authorizationroles are set appropriately.

Checking ConnectivityTo check connectivity:

¶ Ensure the connectivity between the TMR server and theendpoint associated with the problem, for example, bydistributing a profile to the endpoint, by using thepingcommand, or by using this command:

wadminep endpoint_nameview_config_info

For thewadminep command, errors indicate that connectivitydoes not exist and a long string of variables indicatesconnectivity does exist.


E.

Finding

andC

orrectingP

roblems

¶ Ensure the connectivity between the TMR server and thegateway associated with the problem, for example, bydistributing a profile to the gateway or by using thepingcommand.

Troubleshooting Event Management ProblemsIf you are not receiving the Tivoli Self-Service Terminal Managerevents on the event server that you expect, first use the commontroubleshooting techniques (see “Common TroubleshootingTechniques” on page 119); then, check:¶ The self-service terminal (see “Checking Event Management

Problems at the Self-service Terminal”)¶ The event server (see “Checking the Event Server” on page 123)¶ RIM (see “Checking RIM” on page 126)

Checking Event Management Problems at theSelf-service Terminal

To check event management problems at a self-service terminal:

¶ Ensure that the event adapter is installed and configured at theself-service terminal. For more information, see “Configuringand Distributing the Event Adapter” on page 31.

¶ Ensure that the Tivoli Self-Service Terminal Manager eventservice program (sstntxfsevserv.exe) is in the%SystemRoot%\tivoli_sst\sstntxfs directory and that the eventservice is running at the controller by checking the Tivoli XFSEvent Service in the Services folder. If the event service is notactive, start it. (You can also start the event service from thecommand line with thenet start xfseventservcommand.)

¶ Check the Windows NT application log to see if events arebeing logged. Events have the following format in the log file:

service_class:event:subevent_L1:subevent_L2:subevent_L3

where:

service_classSpecifies the service class (see “Service Classes andAliases” on page 115)

122 Version 1.0

subevent_L1Specifies the first-level subevent, if applicable andavailable

subevent_L2Specifies the second-level subevent, if applicable andavailable

subevent_L3Specifies the third-level subevent, if applicable andavailable

Checking the Event ServerTo check the event server:

¶ Ensure that the event server is operational.

¶ Ensure that the event classes are installed and configured on theevent server as follows:

Note: You can also do these steps from the Tivoli desktop.

1. Enter thewlscurrb command to display the name of theactive rule base.

2. Enter thewlsrbclassactive_rulebase_namecommand to listthe defined event classes. Ensure that the Tivoli Self-ServiceTerminal Manager event class WFS_Event is defined.

3. If the Tivoli Self-Service Terminal Manager event class(WFS_Event) is not defined, configure the event server asdescribed in “Configuring the Event Server” on page 30.

¶ Ensure that events are being received at the event server. Enterthe wtdumprl command on the event server to display theevents in the reception log on the event server.

If the events are being received with aparsing_failedmessage and are coming over as class WFS_Event, but are stillnot being processed, configure the event server. See“Configuring the Event Server” on page 30.


E.

Finding

andC

orrectingP

roblems

Troubleshooting Monitoring ProblemsTo troubleshoot monitoring problems, first use the commontroubleshooting techniques (see “Common TroubleshootingTechniques” on page 119); then, do the following:

¶ Check the SentryStatus notification group periodically forinformation about the status of Tivoli Distributed Monitoring andthe Tivoli Self-Service Terminal Manager monitors.

¶ Ensure that the Tivoli Self-Service Terminal Manager monitoringprogram (wsstntxfsmon.exe) is in the%SystemDrive%\%LCFDIR%\dat\1\lcf\sentry\w32-ix86directory.

¶ If you suspect problems with Tivoli Distributed Monitoring, setup logging on the endpoint as follows:

1. Use thewlseng –lendpoint_namecommand to determine ifTivoli Distributed Monitoring is running on the endpoint. Ifyou see anUnable to start engine dm_ep_enginemessage, Tivoli Distributed Monitoring is not running on theendpoint. If it is running, use thewstopengcommand to stopit.

2. In the %SystemDrive%/tmp directory, edit the dm36.ll file.On line 1, specify a logging level from 1 to 4, with 4providing the most detail. A logging level of 3 isrecommended. On line 2, specify the maximum size in KBthe log file (DM36.log) can be before it wraps.

3. Restart Tivoli Distributed Monitoring with thewlsengcommand. The DM36.log file will be created in the$LCF_DATDIR/dat/1 directory.

¶ For more information about troubleshooting monitoringproblems, refer to theTME 10 Distributed Monitoring User’sGuide.

124 Version 1.0

Troubleshooting Inventory ProblemsTo troubleshoot inventory problems, first use the commontroubleshooting techniques (see “Common TroubleshootingTechniques” on page 119); then, do the following:

¶ Verify that RIM is working; see “Checking RIM” on page 126.

¶ Ensure that Tivoli Inventory is working by creating anddistributing to your self-service terminal an inventory profile thatperforms a hardware scan. After distributing the profile, checkthe queries in the INVENTORY_QUERIES query library to seeif they accurately show what is on your self-service terminal. Inparticular, in the INVENTORY_HARDWARE query, check thevalue of COMPUTER_SCANTIME to see if the time reportedmatches the time you distributed the profile. For information oncreating and distributing inventory profiles and queryinginventory information, refer to theTME 10 Inventory User’sGuide.

¶ Ensure that the Tivoli Self-Service Terminal Managerconfiguration repository schema have been installed in theInventory database. See “Configuring the InventoryConfiguration Repository” on page 51.

¶ At the self-service terminal:

v Ensure that the Tivoli Self-Service Terminal Manager scannerprogram (sstntxfsscan.exe) is in the %SystemDrive%\ProgramFiles\Tivoli\lcf\inv\SCANNER directory.

v If you have login access to the self-service terminal, run thescanner program manually from a command prompt andverify that a MIF file is produced.

¶ For more information about troubleshooting inventory problems,refer to theTME 10 Internals and Problem Determination(SG24-2034),Using Databases with Tivoli Applications and RIM(SG24-5112), and theTME 10 Inventory User’s Guide.


E.

Finding

andC

orrectingP

roblems

Troubleshooting Software Distribution ProblemsTo troubleshoot problems with distributing software to self-serviceterminals, first use the common troubleshooting techniques (see“Common Troubleshooting Techniques” on page 119); then, do thefollowing:

¶ If the distribution of a file package fails, go to the Propertieswindow for that file package and specify a log file. Check thelog file for problems with the distribution.

¶ For more information about troubleshooting software distributionproblems, refer to theTME 10 Internals and ProblemDetermination(SG24-2034) and theTME 10 SoftwareDistribution User’s Guide.

Checking RIMTo verify that RIM is working properly:

¶ Check the connectivity to the database for Tivoli Inventory orTivoli Enterprise Console using thewrimtest command. Forinformation about this command, refer to theTME 10Framework Reference Manual.

¶ If necessary, enable RIM tracing with thewrimtrace command.The trace information will be written to the /tmp/rim_db_log fileon the RDBMS server. For information about this command,refer to theTME 10 Framework Reference Manual.

¶ For more information about using RIM, refer toUsingDatabases with Tivoli Applications and RIM(SG24-5112).

126 Version 1.0

Error Codes and Logging

This appendix describes:

¶ Error codes for monitoring (see “Monitoring Error Codes” onpage 127)

¶ Logging for event management (see “Event Service Logging” onpage 132)

Monitoring Error CodesThe error codes that can be returned from Tivoli DistributedMonitoring for Tivoli Self-Service Terminal Manager are:

GST0001

Explanation: Either the XFS manager did not clean up before a restart wasrequested or it did not disconnect from the application.

User Response: Try rerunning the monitor.

GST0002

Explanation: The installed XFS manager software does not offer support for XFSRelease 2.0. It offers support only for greater than Release 2.0.

User Response: Check your XFS manager software.

GST0003

Explanation: The installed XFS manager software does not offer support for XFSRelease 2.0. It offers support only for less than Release 2.0.

F


F.E

rrorC

odesand

Logging

User Response: Check your XFS manager software.

GST0007

Explanation: A problem in the XFS configuration registry was found. Some keysare either missing or corrupted.

User Response: Check the Windows NT registry.

GST0013

Explanation: The target device for the monitor was not available.


GST0014

Explanation: A hardware error occurred on the target device for the monitor.

User Response: Ensure that the device is working correctly.

GST0015

Explanation: An unexpected XFS subsystem problem occurred.


GST0017

Explanation: An internal program error occurred.

User Response: Contact Tivoli Customer Support.

GST0019

Explanation: The service class of the specified device does not match the serviceclass for the monitor.

User Response: Correct the device name and run the monitor again, or run anappropriate monitor for the specified device.

GST0022



128 Version 1.0

GST0026



GST0028



GST0029

Explanation: The associated service provider for the target device is invalid orcorrupted.

User Response: Check your service provider software.

GST0031



GST0041

Explanation: The target device was busy.


GST0042

Explanation: The operating system on the self-service terminal does not haveenough memory to run the monitor.

User Response: Check the memory usage on the self-service terminal.

GST0043

Explanation: Either the device name specified is not recognized or the self-serviceterminal has no devices configured for the service class requested by the monitor.

User Response: Ensure that you have entered a valid name or verify yourself-service terminal configuration.


F.E

rrorC

odesand

Logging

GST0044

Explanation: The service provider interface software is at a higher level thanRelease 2.0.

User Response: Check your service provider interface software.

GST0045

Explanation: The service provider interface software is at a lower level thanRelease 2.0.

User Response: Check your service provider interface software.

GST0046

Explanation: The service provider software is at a higher level than Release 2.0.


GST0047

Explanation: The service provider software is at a lower level than Release 2.0.


GST0048

Explanation: The monitor did not complete because the XFS subsystem timed out.

User Response: Try rerunning the monitor. If the problem persists, contact TivoliCustomer Support.

GST0049

Explanation: The device or the service provider software does not support thestatus or capabilities requested by the monitor.

User Response: None.

GST0051

Explanation: A software mismatch with the service provider software wasdetected.


130 Version 1.0

GST0052



GST0053

Explanation: A software error occurred in the XFS subsystem.


GST0054

Explanation: The connection between the XFS manager and the service providerwas lost.


GST0100



GST0101



GST0102

Explanation: The device name All is not supported by this monitor.

User Response: Check the device name and try rerunning the monitor.

GST0103

Explanation: The expected data was not supplied by the XFS subsystem.


GST0104

Explanation: The number specified for logical cash unit was not recognized.

User Response: Check the logical number of the cash unit and try rerunning themonitor.


F.E

rrorC

odesand

Logging

GST0105

Explanation: The name specified for the physical cash unit was not recognized.

User Response: Check the name of the physical cash unit and try rerunning themonitor.

GST0106

Explanation: The value returned by the XFS subsystem was not valid.


Event Service LoggingThese messages are logged in the Windows NT application log ifevent service problems occur:

ERR:Create Service Fail

Explanation: An operating system service failed. Events are not being posted inthe application log.


ERR:INVALID_DEVICE: device_name

Explanation: The requested device, specified bydevice_name, cannot be foundand registered for. Event management for other devices is still in effect.


ERR:INVALID_EVENT_WINDOW: device_name

Explanation: The event window cannot be registered for the logical devicespecified bydevice_name. Event management for other devices is still in effect.

User Response: Note the information about the error and contact Tivoli CustomerSupport.

ERR:MONITOR_EVENT_CLASS

Explanation: An event type of indeterminate for a device cannot be registered.Event management for other devices is still in effect.

User Response: Note the information about the error and contact Tivoli CustomerSupport.

132 Version 1.0

ERR:Open SC Manager Fail

Explanation: The service control manager cannot be opened. Events are not beingposted in the application log.


ERR:RegisterServiceCtrlHandler Fail

Explanation: An operating system service failed. Events are not being posted inthe application log.


SST_INT_CONFIG_FILE

Explanation: An event service configuration file error occurred. The event servicedefaults for event filtering and for the start delay will be used.

User Response: Check the location and content of the event service configurationfile.

SST_INT_ERROR

Explanation: The system is attempting to resolve an error.


SST_INT_OPEN_FILE

Explanation: The event service configuration file cannot be opened. The eventservice defaults for event filtering and for the start delay will be used.

User Response: Check the location and content of the event service configurationfile.

SST_INT_SHUTDOWN

Explanation: An internal error that cannot be resolved occurred, and the eventservice has stopped.


Tivoli XFS event service continued

Explanation: After being paused, the event service was continued by the servicecontrol manager. Events will be posted to the application log.


F.E

rrorC

odesand

Logging


Tivoli XFS event service installed

Explanation: The event service was installed by the Tivoli installation process buthas not been started.


Tivoli XFS event service log key was not removed

Explanation: A Windows NT registry key was not removed. This does not affectsystem operation.


Tivoli XFS event service paused

Explanation: The event service was paused by the service control manager. Eventsare not being posted to the application log.

User Response:

Tivoli XFS event service started

Explanation: The event service was started by the service control manager.


Tivoli XFS event service stopped

Explanation: The event service was stopped by the service control manager.


Tivoli XFS event service was not removed

Explanation: The event service was not removed during product removal.


Tivoli XFS event service was removed

Explanation: The event service was stopped during product removal orre-installation.


134 Version 1.0

WFS_ERR_CANCELED

Explanation: An internal request was canceled.


WFS_ERR_CONNECTION_LOST

Explanation: An internal connection within the XFS Manager was lost and eventscannot be posted to the application log.

User Response: Reboot the system. If the problem persists, contact TivoliCustomer Support.

WFS_ERR_INTERNAL_ERROR

Explanation: An internal or other unexpected error occurred in the XFSsubsystem.


WFS_ERR_INVALID_EVENT_CLASS

Explanation: The event class specified is not supported by the service.


WFS_ERR_INVALID_HSERVICE

Explanation: The specified service handle is not valid.


WFS_ERR_INVALID_HWND

Explanation: The specified window handle is not valid.


WFS_ERR_INVALID_HWNDREG

Explanation: The specified window handle to be registered is not valid.



F.E

rrorC

odesand

Logging

WFS_ERR_INVALID_POINTER

Explanation: The event service is being stopped and a pointer parameter does notpoint to memory that can be accessed.


WFS_ERR_NOT_REGISTERED

Explanation: The event service is being stopped and the window specified wasnot registered to receive messages for any event classes.


WFS_ERR_NOT_STARTED

Explanation: The event service has not established a connection to the XFSManager.


WFS_ERR_OP_IN_PROGRESS

Explanation: A blocking operation is currently in progress on the thread.


136 Version 1.0

Index

Aalias file

downloading to endpoints 22location 116sending to configured self-service

terminals 117using 115

application log, Windows NTchecking for logged events 122event service messages 132

asterisk in inventory column 98authorization roles

checking 121security provided 2

Bbaroc file, sstxfsevents.baroc 31

Ccameras

event classes 70inventory information 98monitors

overall 92pictures 92state 92

cash dispensersevent classes 70inventory information

capabilities 99logical cash unit 100physical cash unit 101status 101

cash dispensers(continued)monitors

cash units 87logical unit level 87logical unit state 88overall 87physical unit level 88physical unit state 88safe door 89

check readersinventory information 102, 103monitors

ink 95lamp 95media 96overall 95

classes, eventadding to a new rule base 30adding to an existing rule base 31excluding 38for self-service terminals 67monitor 68parent 70subevent levels 70WFS_Event

camera 70cash dispenser 70depository 71description 69ID card reader 71PIN pad 72printer 73sensor 73slots 78vendor-dependent mode 78

CLI names for monitors 81columns, inventory

asterisk 98TME_OBJECT_ID 98


Index

columns, inventory(continued)TME_OBJECT_LABEL 98

command lineinstallation 13monitor names 81

commandsdb2 52, 53dbaccess 53isql

for MS SQL 54for Sybase 55

net start xfseventserv 122net stop xfseventserv 17, 37ping 121, 122setup_env 15setup_env.sh 15spool 54sqlplus 54ssntxfs.init 15sstntxfsevserv -remove 17sstxfs_queries_remove.sh 55sstxfs_queries.sh 55syntax conventions xiiwaddmon 43wadminep 121wdeleg 17wdelrb 17wdistfp 25, 65wdistrib 35, 45, 60wlscurrb 123wlseng 46, 124wlsinst 121wlsrbclass 123wrimtest 126wrimtrace 126wstopeng 124wtdumprl 123wuninst 16

COMPUTER_SCANTIME query 125COMPUTER_SYSTEM table 98configuration

event adapter 31event server

manual 31using a job 30

configuration (continued)inventory database

DB2 52Informix 53MS SQL 53Oracle 54requirements 51Sybase 54

overview 8self-service terminals 23

configuration repository, inventoryDB2 configuration 52Informix configuration 53MS SQL configuration 53multiple records 58Oracle configuration 54requirements 51Sybase configuration 54

Configure_Event_Server_for_SST_XFS jobdescription 26using 30

connectivity troubleshooting 121conventions

command syntax xiidirectory notation xiienvironment variables xiitypeface xi

creation of rules 38customer support

contacting xivhandbook xiiiWeb site xiii

Ddatabase, inventory

configurationDB2 52Infomix 53MS SQL 53Oracle 54requirements 51Sybase 54

multiple records 58

138 Version 1.0

db2 command 52, 53dbaccess command 53Default, used as logical name in monitors 83definitions, technical xdelay, setting for event service start 38depositories

event classes 71inventory information 104, 105monitors

container level 89container state 89envelope 90overall 89printer 90toner 90

desktopinstallation 12resources, missing 15

directory notation convention xiidisk space requirements 11DM36.log file 124documentation

related ixTivoli Self-Service Terminal Manager xii

EE.EXEC status 48endpoints

downloading Tivoli Self-Service TerminalManager software 22

logging 121, 124troubleshooting 120Web site 120

environment, Tivoli, setup 15environment variables

conventions xiievent server port 34

error codes, monitoring 127event adapters

configuration 31configuration file

overwritten 35using 33

event adapters(continued)event filtering

default 79defining 33

format file, overwritten 35event classes

adding to a new rule base 30adding to an existing rule base 31excluding 38for self-service terminals 67monitor 68parent 70subevent levels 70WFS_Event

cameras 70cash dispenser 70depository 71description 69ID card reader 71PIN pad 72printer 73sensor 73slots 78vendor-dependent mode 78

event consolescreating for SST_XFS event group 36filtering of events 38

event groupscreating for WFS_Event event class 31SST_XFS

creating event console 36removing 17

event managementdescription 2troubleshooting

event server 123self-service terminals 122

event serverconfiguration

manual 31using a job 30

installing Tivoli Self-Service TerminalManager 12

port, setting 34troubleshooting 123


Index

event servicedownloading to endpoints 22event filtering


location 122logging 132removing 17start delay 38started during configuration 22starting 122stopping 17, 37

event service configuration filedownloading to endpoints 22event filtering


location 37missing 38sending to configured self-service

terminal 37start delay 38

eventscorrelating 67displaying 36filtering

at event adapters 33at event consoles 38at self-service terminals 37default 79event service 79

managing 2monitor, sending to Tivoli Enterprise

Console 31eXtensions for Financial Services interface

specificationSee XFS specification ix

Ffile packages

creating 63distributing 64

filesalias

downloading to endpoints 22location 116sending to configured self-service


DM36.log 124event adapter configuration

overwritten 35using 33

event adapter format file, overwritten 35event service

downloading to endpoints 22location 122removing 17

event service configurationdownloading to endpoints 22event filtering 37filtering 79location 37missing 38sending to configured self-service


inventory scanner programdownloading to endpoints 22location 125removing 17using 58

last.cfg 121MIF

removing 17using 58verifying 125

monitoring programdownloading to endpoints 22location 124removing 17

rim_db_log 126self-service terminal configuration log 120sstntxfs_config.log 120sstntxfs.mif


140 Version 1.0

files (continued)sstntxfsevserv.exe


sstntxfsevserv.xmldownloading to endpoints 22event filtering 37location 37missing 38sending to configured self-service


sstntxfsscan.exedownloading to endpoints 22location 125removing 17using 58

sstxfsalias.xmldownloading to endpoints 22location 116sending to configured self-service


sstxfsevents.baroc 31tivoli_sstxfs_db2_schema.log 53tivoli_sstxfs_db2_schema.sql 52tivoli_sstxfs_infx_schema.sql 53tivoli_sstxfs_ora_schema.log 54tivoli_sstxfs_ora_schema.sql 54tivoli_sstxfs_sql_schema.log 54tivoli_sstxfs_sql_schema.sql 53tivoli_sstxfs_sybase_schema.log 55tivoli_sstxfs_sybase_schema.sql 55trace, downloading to endpoints 22wsstntxfsmon.exe


filtering of eventsat event adapters 33at event consoles 38at self-service terminals 37default 79

format file, event adapter, overwritten 35

Gglossary, Tivoli xGUI names for monitors 81

Hhandbook, customer support xiiihardware requirements 11

IID card readers

event classes 71inventory information 105, 106monitors

media 93overall 93retain bin level 93

indicator collectionscreating 42SST_XFS_Indicator

description 21using 46

installationcommand line 13desktop 12on the event server 12on the TMR server 12overview 8planning 7Tivoli Software Installation Service 14

inventorydatabase

configuration requirements 51DB2 configuration 52Informix configuration 53MS SQL configuration 53multiple records 58Oracle configuration 54Sybase configuration 54


Index

inventory (continued)information

all self-service terminals 60camera 98cash dispenser 99, 101cash dispenser logical cash unit 100cash dispenser physical cash unit 101check reader 102, 103depository 104, 105description 4ID card reader 105, 106kinds 97PIN pad 107, 108printer 109querying 60sensor 110, 111single self-service terminal 61text terminal 112, 113

profilescreating 58customizing for self-service terminals 58distributing 59See also SST_XFS_Inventory profile 58

queriesSee queries, inventory 97

tablesSee tables, inventory 97

troubleshooting 125views

See views, inventory 97INVENTORY_HARDWARE query 125INVENTORY_QUERIES query library 125inventory scanner program

downloading to endpoints 22location 125removing 17using 58

isql commandfor MS SQL 54for Sybase 55

Jjob, Configure_Event_Server_for_SST_XFS


Llast.cfg file 121levels, event classes 70logging

endpoint for monitoring 124endpoints 121, 124event service 132self-service terminal configuration 120software distribution 126

logical serviceskeys 83, 117required configuration 8

Mmanaged nodes, for managing self-service

terminals 10managing events 2MIF file


monitor event classes 68monitor names

command-line-interface (CLI) 81GUI 81

monitoringE.EXEC status 48error codes 127logging at the endpoint 124profiles

creating 41distributing 44See also SST_XFS_Monitors profile 41

Sentry Status notification group 124

142 Version 1.0

monitoring (continued)starting 124stopping 124troubleshooting 124

monitoring programdownloading to endpoints 22location 124removing 17

monitorsadding 42, 43camera

overall 92pictures 92state 92

cash dispensercash units 87logical unit level 87logical unit state 88overall 87physical unit level 88physical unit state 88safe door 89

check readerink 95lamp 95media 96overall 95

Default as logical name 83defining 42, 43depository

container level 89container state 89envelope 90overall 89printer 90toner 90

distributed, checking 46enabled, checking 46ID card reader

media 93overall 93retain bin level 93

informationexample (pop-up) 48viewing 47

kinds 83

monitors (continued)PIN pad

encryption state 94overall 94state 94

printerlamp 85overall 84printer bin level 85retract bin 85supplies 86

self-service terminalopen state 83operation mode 84overall 83

sensorambient light 91door 91overall 90proximity 91state 91

text terminaloverall 94state 95

multiple records in inventory database 58

Nnet start xfseventserv command 122net stop xfseventserv command 17, 37notification group, SentryStatus 124

Ooperating system requirements 11operations 5overview

installation and configuration 8Tivoli Self-Service Terminal Manager 1


Index

Pparent event classes 70parsing_failed message 123patches

3.6.1-DMN-0008 103.6.1-DMN-0013 103.6.1-DMN-0036 103.6.1-TMF-0049 103.6.3-TMF-0002 10

PIN padsevent classes 72inventory information 107, 108monitors

encryption state 94overall 94state 94

ping command 121, 122planning considerations 7policy regions

missing resources 15Self_Service_Terminal_Manager 20SST_XFS 20

port for event server, setting 34printers

event classes 73inventory information 109monitors

lamp 85overall 84printer bin level 85retract bin 85supplies 86

problems, resolving 119product tag 16profile managers

SST_XFS_Configurationdescription 22using 24

SST_XFS_Event_Adaptersdescription 22using 31

SST_XFS_Inventorydescription 22using 56

profile managers(continued)SST_XFS_Monitors


profilesadapter configuration

See SST_XFS_Event Adapters profile 31file package

creating 63defining properties 64distributing 64

inventorycreating 58customizing for self-service terminals 58distributing 59See also SST_XFS_Inventory profile 56

monitoringcreating 41distributing 44See also SST_XFS_Monitors profile 40

software distributioncreating 63defining properties 64distributing 64

SST_XFS_Configurationdescription 22distributing 23using 23

SST_XFS_Event_Adaptersdescription 22distributing 34using 31

SST_XFS_Inventorydescription 22distributing 59using 56

SST_XFS_Monitorsdescription 22distributing 44using 40

publicationsonline access xiiiordering xiiiproviding feedback xiv

144 Version 1.0

Qqueries, inventory

all self-service terminals 60COMPUTER_SCANTIME 125INVENTORY_HARDWARE 125single self-service terminal 61XFS_CAMERA_STATUS 98XFS_CARD_READER_CAPABILITIES 106XFS_CARD_READER_STATUS 106XFS_CASH_DISPENSER_CAPABILITIES 99XFS_CASH_DISPENSER_STATUS 101XFS_CHECK_READER_CAPABILITIES 102XFS_CHECK_READER_STATUS 103XFS_DEPOSITORY_CAPABILITIES 104XFS_DEPOSITORY_STATUS 105XFS_LOGICAL_CASH_UNIT_STATUS 100XFS_PHYSICAL_CASH_UNIT_STATUS 101XFS_PIN_PAD_CAPABILITIES 107XFS_PIN_PAD_STATUS 108XFS_PRINTER_CAPABILITIES 109XFS_PRINTER_STATUS 110XFS_SENSOR_CAPABILITIES 110XFS_SENSOR_STATUS 111XFS_TEXT_TERMINAL_CAPABILITIES 112XFS_TEXT_TERMINAL_STATUS 113

query librariesINVENTORY_QUERIES 125SST_XFS_Queries

description 23moving 55using 60

RReboot_SST_XFS_Unit task


registry (Windows NT) logical serviceskeys 83, 117

removing the productfrom managed nodes 16from self-service terminals 17

requirementsdisk space 11hardware 11inventory database 51logical service configuration 8operating systems 11service provider 8software 9XFS 8

resolving problems 119resources

missing 15not removed 16

RIM, troubleshooting 126roles, authorization

checking 121security provided 2

rule basesadding event class definitions 31SST_XFS_RULES

creation 30removing 17

rulescorrelating events 67creating 38writing 67

Ssecurity, authorization roles for 2, 121Self_Service_Terminal_Manager policy

region 20self-service terminals

configuring 23downloading Tivoli Self-Service Terminal

Manager software 22event classes 67integration with Tivoli Distributed

Monitoring 3integration with Tivoli Enterprise Console 3integration with Tivoli Inventory 4integration with Tivoli Management

Framework 2


Index

self-service terminals(continued)monitors, general

open state 83operation mode 84overall 83

operations 5rebooting 26removing product 17troubleshooting

event management problems 122general 120

sensorsevent classes 73inventory information 110, 111monitors

ambient light 91door 91overall 90proximity 91state 91

SentryStatus notification group 124service class names

checking 117non-standard, using 116standard 115XFS specification 115

service provider requirement 8setup

product, overview 8Tivoli environment 15

setup_env command 15setup_env.sh command 15slots, event

sst_sensor_state 70WFS_Event event class 78

software distributionfile packages

creating 63defining properties 64distributing 64

logging 126troubleshooting 126

software requirements 9spool command 54sqlplus command 54ssntxfs.init command 15

SST_XFS_CAMERA table 98SST_XFS_Configuration profile

description 22distributing 23using 23

SST_XFS_Configuration profile managerdescription 22using 24

SST_XFS_CP_CASH_DP table 99SST_XFS_CP_CHK_RDR table 102SST_XFS_CP_CRD_RDR table 105SST_XFS_CP_DEPOSIT table 104SST_XFS_CP_PIN_PAD table 107SST_XFS_CP_PRINTER table 109SST_XFS_CP_SENSOR table 110SST_XFS_CP_TXT_TRM table 112SST_XFS_Event_Adapters profile


SST_XFS_Event_Adapters profile managerdescription 22using 31

SST_XFS event groupcreating event console for 36removing 17

SST_XFS_Indicator indicator collectiondescription 21using 46

SST_XFS_Inventory profiledescription 22distributing 59using 56

SST_XFS_Inventory profile managerdescription 22using 56

SST_XFS_LG_CASH table 100SST_XFS_Monitors profile


SST_XFS_Monitors profile managerdescription 22using 40

SST_XFS_PHY_CASH table 101SST_XFS policy region 20

146 Version 1.0

SST_XFS_Queries query librarydescription 23moving 55using 60

SST_XFS_RULES rule basecreation 30removing 17

SST_XFS_ST_CASH_DP table 101SST_XFS_ST_CHK_RDR table 103SST_XFS_ST_CRD_RDR table 106SST_XFS_ST_DEPOSIT table 105SST_XFS_ST_PIN_PAD table 108SST_XFS_ST_PRINTER table 109SST_XFS_ST_SENSOR table 111SST_XFS_ST_TXT_TRM table 113SST_XFS_Tasks task library

description 23opening 26

sstntxfs_config.log file 120sstntxfs.mif file


sstntxfsevserv -remove command 17sstntxfsevserv.exe file


sstntxfsevserv.xml filedownloading to endpoints 22event filtering 37location 37missing 38sending to configured self-service


sstntxfsscan.exe filedownloading to endpoints 22location 125removing 17using 58

sstxfs_queries_remove.sh command 55sstxfs_queries.sh command 55sstxfsalias.xml

sending to configured self-serviceterminals 117

sstxfsalias.xml filedownloading to endpoints 22location 116using 115

sstxfsevents.baroc file 31SSTXFSV_CAMERA view 98SSTXFSV_CP_CASH_DP view 99SSTXFSV_CP_CHK_RDR view 102SSTXFSV_CP_CRD_RDR view 105SSTXFSV_CP_DEPOSIT view 104SSTXFSV_CP_PIN_PAD view 107SSTXFSV_CP_PRINTER view 109SSTXFSV_CP_SENSOR view 110SSTXFSV_CP_TXT_TRM view 112SSTXFSV_LG_CASH view 100SSTXFSV_PHY_CASH view 101SSTXFSV_ST_CASH_CP view 101SSTXFSV_ST_CHK_RDR view 103SSTXFSV_ST_CRD_RDR view 106SSTXFSV_ST_DEPOSIT view 105SSTXFSV_ST_PIN_PAD view 108SSTXFSV_ST_PRINTER view 109SSTXFSV_ST_SENSOR view 111SSTXFSV_ST_TXT_TRM view 113start delay, event service 38status event class

See WFS_Event event class 69support, customer

contacting xivhandbook xiiiWeb site xiii

Ttables, inventory

COMPUTER_SYSTEM 98SST_XFS_CAMERA 98SST_XFS_CP_CASH_DP 99SST_XFS_CP_CHK_RDR 102SST_XFS_CP_CRD_RDR 105SST_XFS_CP_DEPOSIT 104SST_XFS_CP_PIN_PAD 107SST_XFS_CP_PRINTER 109SST_XFS_CP_SENSOR 110


Index

tables, inventory(continued)SST_XFS_CP_TXT_TRM 112SST_XFS_LG_CASH 100SST_XFS_PHY_CASHA 101SST_XFS_ST_CASH_DP 101SST_XFS_ST_CHK_RDR 103SST_XFS_ST_CRD_RDR 106SST_XFS_ST_DEPOSIT 105SST_XFS_ST_PIN_PAD 108SST_XFS_ST_PRINTER 109SST_XFS_ST_SENSOR 111SST_XFS_ST_TXT_TRM 113

tag, product 16task libraries (SST_XFS_Tasks)

description 23opening 26

tasks and jobsConfigure_Event_Server_for_SST_XFS


Reboot_SST_XFS_Unitdescription 26using 26

technical terms, definitions xterminology, Tivoli xiitext terminals

inventory information 112, 113monitors

overall 94state 95

tim_db_log file 126Tivoli Desktop for Windows,

recommendation 10Tivoli Distributed Monitoring

description 3events, sending to Tivoli Enterprise

Console 31integrating self-service terminals 3using 39

Tivoli Enterprise Consoledescription 2event adapter

See event adapters 31event class

See event classes 30

Tivoli Enterprise Console(continued)event console

See event consoles 36event group

See event groups 31event server

See event server 31events for Tivoli Distributed Monitoring 31integrating self-service terminals 3using 29

Tivoli environment setup 15Tivoli glossary xTivoli Inventory

description 4integrating self-service terminals 4using 51

Tivoli Management Frameworkdescription 2integrating self-service terminals 2

Tivoli Software Distributiondescription 5using 63

Tivoli Software Installation Service, installingfrom 14

tivoli_sstxfs_db2_schema.log file 53tivoli_sstxfs_db2_schema.sql file 52tivoli_sstxfs_infx_schema.sql file 53tivoli_sstxfs_ora_schema.log file 54tivoli_sstxfs_ora_schema.sql file 54tivoli_sstxfs_sql_schema.log file 54tivoli_sstxfs_sql_schema.sql file 53tivoli_sstxfs_sybase_schema.log file 55tivoli_sstxfs_sybase_schema.sql file 55TME_OBJECT_ID column 98TME_OBJECT_LABEL column 98TMR server

installing Tivoli Self-Service TerminalManager 12

troubleshooting 121trace file, downloading to endpoints 22troubleshooting 119

common techniques 119connectivity 121endpoints 120event management problems 122event server 123

148 Version 1.0

troubleshooting 119 (continued)inventory problems 125monitoring problems 124RIM 126software distribution 126TMR server 121

typeface conventions xi

Vvendor-dependent mode event classes 78views, inventory

SSTXFSV_CAMERA 98SSTXFSV_CP_CASH_DP 99SSTXFSV_CP_CHC_RDR 102SSTXFSV_CP_CRD_RDR 105SSTXFSV_CP_DEPOSIT 104SSTXFSV_CP_PIN_PAD 107SSTXFSV_CP_PRINTER 109SSTXFSV_CP_SENSOR 110SSTXFSV_CP_TXT_TRM 112SSTXFSV_LG_CASH 100SSTXFSV_PHY_CASH 101SSTXFSV_ST_CASH_DP 101SSTXFSV_ST_CHK_RDR 103SSTXFSV_ST_CRD_RDR 106SSTXFSV_ST_DEPOSIT 105SSTXFSV_ST_PIN_PAD 108SSTXFSV_ST_PRINTER 109SSTXFSV_ST_SENSOR 111SSTXFSV_ST_TXT_TRM 113

Wwaddmon command 43wadminep command 121wdeleg command 17wdelrb command 17wdistfp command 25, 65wdistrib command 35, 45, 60

Web sitescustomer support xiiiendpoint 120Tivoli glossary xTivoli patches 10XFS interface specification x

WFS_Event event classcamera 70cash dispenser 70depository 71description 69ID card reader 71PIN pad 72printer 73sensor 73slots 78vendor-dependent mode 78

Windows NTapplication log

checking for logged events 122event service messages 132

event adapter configuration 31logical services keys in registry 117

Windows NT XFS self-service terminalsdefinition ixdescription 1See also self-service terminals ix

wlscurrb command 123wlseng command 46, 124wlsinst command 121wlsrbclass command 123wrimtest command 126wrimtrace command 126wsstntxfsmon.exe file


wstopeng command 124wtdumprl command 123wuninst command 16


Index

XXFS_CAMERA_STATUS query 98XFS_CARD_READER_CAPABILITIES

query 106XFS_CARD_READER_STATUS query 106XFS_CASH_DISPENSER_CAPABILITIES

query 99XFS_CASH_DISPENSER_STATUS query 101XFS_CHECK_READER_CAPABILITIES

query 102XFS_CHECK_READER_STATUS query 103XFS_CPIN_PAD_STATUS query 108XFS_DEPOSITORY_CAPABILITIES

query 104XFS_DEPOSITORY_STATUS query 105XFS_LOGICAL_CASH_UNIT_STATUS

query 100XFS_PHYSICAL_CASH_UNIT_STATUS

query 101XFS_PIN_PAD_CAPABILITIES query 107XFS_PRINTER_CAPABILITIES query 109XFS_PRINTER_STATUS query 110XFS_SENSOR_CAPABILITIES query 110XFS_SENSOR_STATUS query 111XFS specification

requirement 8service class names 115Web site x

XFS_TEXT_TERMINAL_CAPABILITIESquery 112

XFS_TEXT_TERMINAL_STATUS query 113

150 Version 1.0

Printed in the United States of Americaon recycled paper containing 10%recovered post-consumer fiber.

GC32-0653-00