Académique Documents
Professionnel Documents
Culture Documents
for Windows
Release 3.0
User’s Guide
20385a
B005-0000-1634
Issue F
The product described in this book is a licensed product of NCR Corporation.
NCR is a registered trademark of NCR Corporation.
NCR RealPOS,, NCR SelfServ, and NCR SelfServ Checkout are either registered trademarks or trademarks of
NCR Corporation in the United States and/or other countries.
Java and MySQL are trademarks of Sun Microsystems.
It is the policy of NCR Corporation (NCR) to improve products as new technology, components, software, and
firmware become available. NCR, therefore, reserves the right to change specifications without prior notice.
All features, functions, and operations described herein may not be marketed by NCR in all parts of the world.
In some instances, photographs are of equipment prototypes. Therefore, before using this document, consult
with your NCR representative or NCR office for information that is applicable and current.
To maintain the quality of our publications, we need your comments on the accuracy, clarity, organization, and
value of this book.
Address correspondence to:
Manager, Information Products
NCR Corporation
2651 Satellite Blvd.
Duluth, GA 30096
Copyright © 2009
By NCR Corporation
Dayton, Ohio U.S.A.
All Rights Reserved
i
Preface
Audience
This book is written for software installer/service personnel, system
integrators, and field engineers.
Notice: This document is NCR proprietary information and is not to
be disclosed or reproduced without consent.
ii
References
• NCR Retail Systems Manager Software User’s Guide
(B005-0000-1518)
iii
Table of Contents
Alerting..............................................................................................21
Log Event Types ..........................................................................21
Tally Flush Interval .....................................................................22
RSM SNMP Configuration .........................................................23
Critical Events ..................................................................................31
Tally Thresholds...............................................................................35
OS Monitoring..................................................................................38
Data Capture.....................................................................................50
Create Diagnostic File .....................................................................54
Using Peripherals ...................................................................................57
OPOS/JavaPOS Retail Peripherals................................................57
Creating New Profiles.................................................................58
Changing a Profile .......................................................................59
Deleting a Profile .........................................................................60
Diagnostics ...................................................................................61
Platform Devices.....................................................................................62
Power States......................................................................................67
Restrictions ...................................................................................69
v
Revision Record
Introduction
The Retail Platform Software for Windows CD provides a single
Windows Installer executable that can be used to install NCR OPOS,
NCR JavaPOS, NCR RSM LE, and FitClient Agent software, on NCR
terminals that run Windows XP, WindowsXPe, Windows 2000,
WEPOS, or Windows NT operating systems. The Retail Platform
Software for Windows installation is released on a single LPIN, D370-
0782-0100, eliminating the need of separate media for NCR retail
terminal software components.
The Retail Platform Software for Windows CD provides the following
benefits:
• Single CD distribution for all Retail Platform software.
• Auto-detection of terminal type (if it is running on an NCR Gold
Drive or OS Recovery Image).
• Ability to select complete or custom installation of platform
software.
• Complete installation installs NCR Base Platform, NCR OPOS,
NCR JavaPOS, and RSM LE software. The installation requires
minimal customer input, and only one reboot to install all
components.
• RSM LE is installed to provide access to the OPOS Configuration
and diagnostics locally.
• There is no need to know the order in which to install platform
software. The Retail Platform Software for Windows installation
ensures that all required components are installed and configured
properly.
2 Chapter 1: Client Software Installation
Workstation Model
The workstation model defines the type of system where you are
installing the Retail Platform Software for Windows. The retail
systems are automatically detected, and you are shown the class,
model, and service type that was detected. You can change this
information if it is not correct.
The service types are Assisted and Self Service. The only difference
between these two terminal service types is the set of Printer Finite
State Machine definition files (used by State of Health) that are
installed by default. This minimizes the State of Health changes on an
assisted terminal because an operator is present to fix the problem. For
example, a paper low status is generated on a Self-Service system
indicating the printer on the unattended system needs attention. This
type of alert is not necessary, or even undesirable, for systems where a
cashier is present to handle the condition.
4 Chapter 1: Client Software Installation
Custom Setup
NCR OPOS/JavaPOS
• NCR OPOS – An industry standard interface for accessing and
configuring the retail peripherals. NCR OPOS also provides
interactive and non-interactive diagnostics for analyzing problems
with the peripherals.
• NCR JavaPOS – A wrapper application for OPOS which permits
you to write Java applications using the Retail Controls.
If you install the Retail Platform Software for Windows, and install
OPOS 2.2, then you try to install an older release OPOS over it -- the
install will let you. This is because the “product name” has changed
from OPOS to Retail Platform Software for Windows, and the old
installation can’t detect the newer release. The real problem comes if
you then try to upgrade that older version you just installed back to the
newer version -- the install thinks the newer version is already there,
and doesn’t upgrade. If you get into this situation, you have to
uninstall both the older release and the newer release of OPOS, then
reinstall.
Chapter 1: Client Software Installation 7
Unified POS
OPOS
Control Objects
NCR Control Objects - OPOS 1.3 compliant. NCR Controls
are listed individually.
Common Control Objects - Unified POS 1.8 compliant.
Common Control Objects are listed individually.
Service Objects
NCR OPOS 2.5 - Supports all terminals. Updates to this
feature have been capped. This feature is not being
updated as new features are added to the various terminals.
Service Objects are listed individually.
NCR OPOS 3.9 - Supports RealPOS 20 (RP20), 30, 70, 80,
80C and newer terminals. Updates to this feature will
parallel the NCR JavaPOS 3.9 updates.
Service Objects are listed individually.
8 Chapter 1: Client Software Installation
Utilities
Data Capture Viewer - The Data Capture Viewer displays
trace information obtained from the NCR OPOS 2.5
Controls.
UPS Support - Uninterruptable Power Supply support for
the NCR 7452, 7453, 7456, and 7458 terminals. You must
perform a custom install to select this feature. Although not
configured via an OPOS profile, UPS configuration is
supported from RSM.
NCR Wedge Configuration Utility - The Wedge
configuration utility provides a user friendly interface to
configure various devices attached to the keyboard wedge.
Miscellaneous
Development Tools
Form Designer - The Form Designer is an application
that permits you to design forms in conjunction with the
Form Control.
Form
NCR5992.Form – Provides forms for the NCR 5992 Capture device.
Hard Totals
NCRHardTotals - Store totals information on Disk or in CMOS (for
a retail workstation).
Keylock
NCRWedge.Keylock - Controls the keylock on a Wedge device.
Line Display
NCRLineDisplay - Controls various Line Displays.
Motion Sensor
NCRMotionSensor – Detects motion on the NCR 7401, 7403, 7404,
7454, and 7455.
PINPad
NCR5945.PINPad – Controls the PINPad on the NCR 5945 device.
POS Keyboard
NCRPOSKeyboard – Provides keyboard input to an application on
Windows NT 4.0.
POS Printer
NCRPrinter.POSPrinter - Controls the NCR printer with a serial
interface. (Models: 7156, 7193, 7152, 7166, 7140, 7141, 7162, 1001,
2001, 520, 7161, 7194, 7158, 580, 590, 7166-5005, 7167, 7196, 7196-
3205, 7196-5005, 7196-8005, 7197, 2208, and 200.)
Scale
NCR78xx.Scale - Controls a scale on the NCR 7870 or 7880 Scanner
with a serial interface.
Signature Capture
NCR5991.SigCap - Controls the Signature Capture features of the
NCR 5991 Signature Capture device.
Tone Indicator
NCRToneIndicator – Permits tones to be played on the Wedge
speaker.
12 Chapter 1: Client Software Installation
Signature Capture NO
Tone Indicator YES NCR 5932 USB Keyboard,
5953 USB Dynakey, or 5954 USB
Dynakey
14 Chapter 1: Client Software Installation
JavaPOS
A wrapper application for OPOS which permits you to write Java
applications using the OPOS Retail Controls.
Device Controls
JavaPOS Common Controls 1.9.0 - JavaPOS common
controls released by the UPOS committee.
Device Services
NCR JavaPOS 2.0 with NCR Legacy Loading Scheme -
Uses registry entries for peripheral configuration
parameters.
NCR JavaPOS 2.1 with JCL Support - Uses XML file
entries for peripheral configuration parameters.
NCR JavaPOS 3.9 - Supports the NCR RealPOS 20, 30,
70, 80, 80C and newer terminals. Updates to this feature
will parallel the NCR OPOS 3.9 updates.
Utilities
JCL Editor - This is the Java editor released by the UPOS
committee.
Chapter 1: Client Software Installation 15
If you wish to install the JavaPOS 2.1 controls or both JavaPOS 2.1 and
3.8, select UnifiedPOS → JavaPOS → Device Services and then
select the versions that you want. Do not choose the JavaPOS 2.0
feature; it is for legacy support.
18 Chapter 1: Client Software Installation
If this is the initial install and you are using the Windows Installer
version of the Retail Platform Software, you need to install the
ISScript.MSI file first. It is on the installation CD. Once it’s installed
on a client, you don’t need to install it again on future installs or
upgrades. You can install it just like any other application. Upload it
to the RSM web site on the server, and access it from the System’s web
browser. If you run the .EXE version of the Retail Platform Software
for Windows, it automatically installs the ISScript file.
Push installs using RSM can’t be done until the Retail Platform
Software for Windows LPIN (with RSM client software) is installed on
the system terminal. Upgrades of RPSW can be installed remotely
using RSM. Refer to the section on using Packages in the NCR Retail
Systems Manager Software User’s Guide (B005-0000-1518) for additional
information on using RSM to remotely upgrade RPSW.
Note: The first 4 steps are for downloading RPSW from RSM SE
installed with web server support. If you are installing RPSW from a
CD, you will start at step 5.
22 Chapter 1: Client Software Installation
1. If the “Retail Platform Software for Windows” software has not been
uploaded to RSM, you must do that first. At the RSM SE or RSM EE
server, Select Site or Enterprise → Files → Web Downloads → Add
File button. Browse for the “Retail Platform Software for
Windows.exe or .msi” file, provide a title that is used in RSM and
select Upload.
Chapter 1: Client Software Installation 23
2. On the client, select Start → Run, and enter the network path to the
RSM server or enter this line in your browser.
Example: http://<server name>/RSM
3. Select OK to run the RSM web site. You may be asked to install
several .cab files when trying to connect to the RSM web site, select
Yes to install them.
24 Chapter 1: Client Software Installation
4. From the client system that is connected to the RSM web site, select
the Site → Files → Web Downloads, then select the file you wish
to open. You are given the option of opening the file or saving it to
disk. Select Open to install RPSW. Note: If Windows Installer 2.0
is installed on your client system, you can only save the file. Then
you can go to the saved directory and run the install.
5. If you are installing from the Windows Installer (.MSI), restart the
system if prompted. If you are installing from the .exe file, the
Windows Installer is installed, then the Retail Platform Software for
Windows package is installed.
Chapter 1: Client Software Installation 25
The Retail Platform Software for Windows tries to detect the current
configuration. Make sure the configuration is correct and select
Confirm. You can select a different configuration if it isn’t correct.
If you select Standard install, the next question (step 11) is about
using Common vs. NCR OPOS Control Objects. If you select
Custom install, the custom setup screen displays
Chapter 1: Client Software Installation 29
10. The custom setup permits you to choose the options you wish to
install. Refer to the previous sections in this chapter for an
explanation of the various selections on this and the following
installation screens. You can also change the install directory from
this screen. Select Next.
30 Chapter 1: Client Software Installation
11. If you choose the standard setup, you are given the option as to
which OPOS controls to install. If a Custom Install was chosen,
then the choice of Common vs. NCR OPOS Control Objects is made
as part of selecting the Custom Install options and this screen is not
displayed.
Chapter 1: Client Software Installation 31
12. This screen presents the Retail Controls options. The OPOS
profiles are the configuration information associated with each
retail control. On a new installation, you probably want to Install
Default Profiles. If you select Do Not Install Profiles, none of the
OPOS Profiles are installed. This option is commonly used where
the solution provider installs all of the profiles that are needed for a
specific customer. The Use Saved Profiles setting is shown only if
you are upgrading OPOS and you want to use the same profiles
that were being used with the old version of OPOS. When you start
the Retail Platform Software for Windows installation, it checks to
see if there is already a version of OPOS installed on your system.
If there is, you are given the opportunity to save the profiles. These
are the saved profiles that are used with the Use Saved Profiles
option. Select Next.
32 Chapter 1: Client Software Installation
13. If you chose to install the Java version of the OPOS controls, the
following screen displays telling you to install the Java Runtime
Environment which is available from Sun Microsystems. Select
Next.
Chapter 1: Client Software Installation 33
15. This is the password for accessing this system from a remote
location using the RealVNC program. RealVNC is a program that
permits you to access this desktop from a remote terminal. This
screen is only displayed if you selected RealVNC using a custom
install.
Chapter 1: Client Software Installation 35
Blocked Content
In the IE advanced settings, blocked content must be allowed:
A. Go to Internet Explorer, and select Tools → Internet Options
→ Advanced tab → Security section.
B. Check the box to enable “Allow active content to run in files
on My Computer.”
If this option is not set, the user will have to allow the blocked content
manually each time the RSM user interface is initiated.
ActiveX Controls
In the IE security settings, ActiveX controls must be enabled:
A. Go to Internet Explorer, and select Tools → Internet Options
→ Advanced tab → Security tab → Internet Options →
Custom Level button → ActiveX controls and plug-ins
section.
B. Change “Automatic prompting for ActiveX controls” to
Enable.
Chapter 1: Client Software Installation 37
User Interface
TCP 80 UDP 69
User
IE
Topology
Workstations
Remote Management
SSL Appliance (Neoteris)
NCR
Firewall
Internet
VPN Customer
Firewall
TCP 8500 HD Customer
Customer Alerts, Asset Info
TCP 5800 Help Desk
Corporate TCP 5900
Hop-Off Server TCP 8500
TCP 80 (& IIS) HD
SNMP SMTP RA TCP 8500 EE/IIS UDP 69
Remote access
Network Mgt. System SMTP Server RSM Routing Agent RSM EE & Database to RSM EE console
via web-browser
TCP 25 TCP 8500
UDP 162 HD
TCP 8502
PXE
Terminal
• UDP 68 – DHCP client
Server
• UDP 67 – DHCP server or proxy DHCP server
• UDP 4011 – PXE boot server
• UDP 69 – PXE boot server
40 Chapter 1: Client Software Installation
AMT
Terminal
• TCP 16992 – Small business mode – non-secure (http)
• TCP 16993 – Enterprise mode – secure (TLS) (https)
• UDP 68 – DHCP client
Server
• TCP 9971 – AMT provisioning server (RSM SE)
• TCP 2000 – Remote BIOS configuration (AMT SOL)
• UDP 162 – AMT management server (RSM SE)
• UDP 53 – Proxy Domain Name Server (RSM SE)
• UDP 67 – DHCP server
SNMP
• UDP 161 – SNMP agent
• UDP 162 – SNMP manager (to receive traps)
E-mail Alerts
• TCP 25 – SMTP server
VNC
• TCP 5800 – VNC Java web client access
• TCP 5900 – VNC standard client access
18. The Ready to Install screen displays. If you need to make any
changes, you can use the Back button. When you are ready to
install the Retail Platform Software for Windows, select Install.
42 Chapter 1: Client Software Installation
19. During the installation, setup may find files that should be closed
during the installation, such as the following.
MyApp
21. A message displays stating you should reboot the client terminal.
Select Yes.
44 Chapter 1: Client Software Installation
22. After rebooting, if the system and the RSM SE server are connected
in a LAN and you selected Managed Terminal during installation,
the system should automatically become a Managed System.
Open the browser on the system, and type the path to the RSM web
site on the Address line, and then press Enter or select the desktop
icon for RSM LE.
C:\Program Files\NCR\RSM\Website\ConsoleLE.htm
If you run the installation program after the software has been
installed, you are given the option to Modify (Add or Remove
components), Repair (Replace corrupt files), or Remove (removes all
software; RSM, OPOS, JavaPOS, and Base Platform) the current
installation.
Chapter 1: Client Software Installation 45
1. Install RPSW.
2. Install RPSW patches.
3. Configure any RSM LE settings that are common across terminals
such as the system “Custom Tags”.
4. Run the NCRSysPrep utility which is included with RPSW 2.1.1 or
greater. The NCRSysPrep utility can be run for the NCR 7402,
7456, 7457, 7458, and newer terminal images. This utility clears out
the data on the terminal’s hard drive so that the next time the
terminal is loaded or rebooted, the data will be read from the
processor board on the new terminal. The customer can run the
NCRSysPrep on each terminal to clear this error, but the best
solution is to run NCRSysPrep on the terminal being imaged. If
you reboot the terminal after NCRSysPrep is run and the Base
Platform software in RPSW runs again, then the data on the hard
drive will be filled in again and you will have to run NCRSysPrep
again.
5. Run Microsoft SysPrep/fbreseal. Do not reboot after this is done.
Note: It is important that you run NCRSysPrep before you run the
Microsoft sysprep/fbreseal.
RSM LE Functionality
RSM LE provides peripheral configuration, and local out-of-service
diagnostics. Additional functionality is available if RSM LE is licensed.
• RSM LE has Every Unit Item (EUI) functionality if there is no RSM
license or the RSM license has expired.
• EUI functionality permits you to configure peripherals and run
diagnostics only.
• No login prompt is displayed when LE starts up if you are in EUI
mode.
• Additional functionality is available when you have an RSM license
(monitoring and information).
• RSM LE provides SNMP functionality if you are licensed for it.
For additional information on RSM LE, refer to the NCR Retail Systems
Manager Software User’s Guide (B005-0000-1518).
When you start RSM LE in EUI mode, the following screen is
displayed.
2 Chapter 2: Using RSM LE
• Network
• Power States
• Serial Ports
• Touchscreen
• Versioning
Peripherals - The OPOS/Javapos controls selected during installation.
Some examples include:
• Device Assets
• Cash Drawer
• Check Scanner
• Coin Dispenser
• Hard Totals
• Keylock
• Line Display
• MICR
• MSR
• Pin Pad
• POS Keyboard
• POS Printer
• Scale
• Scanner
• Signature Capture
• Tone Indicator
Administration
• RSM Services
• Customer Number
4 Chapter 2: Using RSM LE
Managed RSM LE
If RSM LE is being managed by RSM SE, additional functionality is
provided in RSM LE. The additional information includes; monitoring,
logs and tallies, and alerting. In addition to the options for the
unmanaged RSM LE interface, the Managed RSM LE interface
includes:
Monitor
• State Of Health
• Connectivity
• Event Logs
• Tallies
Chapter 2: Using RSM LE 5
• Processes
• Services
Platform
• Audio
• BIOS
• Disks
• Memory - Not in EUI RSM LE
• Motherboard
• Network
• Operating System - Not EUI RSM LE
• Power States
• Serial Ports
• Software - Not in EUI RSM LE
• Touchscreen
• Versioning
Peripherals - The same as available for EUI RSM LE
Administration
• RSM Services
• Customer Number.
• RSM Managed - Enabled/Disabled. Set to Enabled for a
managed system.
• RSM Server Discovery - Whether this system discovers the RSM
Server dynamically or uses a fixed address.
• Connected RSM Server - The address of the RSM SE Server that
this RSM LE system has connected to.
6 Chapter 2: Using RSM LE
• Tally Thresholds - You can change the tally threshold values for the
various retail peripherals.
• OS Monitoring
• Configure the monitoring of system wide CPU and memory
usage, disks and files, and processes and services.
• Data Capture - The same as available for unmanaged RSM LE.
RSM LE Login
When managed RSM LE with a license is started, you are prompted for
a login. The “Guest” username does not require a password, but it
only gives you read-only privileges. If RSM is operating in Every Unit
Item (EUI) mode, you are not prompted for a login, but you are
automatically logged in with privileges to configure peripherals and
run diagnostics only.
The NCRRetailer login permits access to the features you have
licensed. You obtain this file and password information from NCR.
The NCRRetailer login has a password that changes daily.
The NCRService login is used by NCR personnel, and it has full access
to all the features in the system. The NCRService login has a password
that changes daily.
8 Chapter 2: Using RSM LE
After you have logged into RSM LE with RSM SE installed, the
following screen is displayed.
The following sections show the features available when using RSM
LE.
Note: The functionality present is based on the license file, and
unlicensed features are not available.
Chapter 2: Using RSM LE 9
Monitor Menu
The Monitor Menu section is not included with RSM LE EUI without a
license.
State of Health
The State of Health screen is the first screen shown after you log in.
RSM has the ability to determine the state of health of managed
components. State of health determination is derived using events
logged by managed components. These events are then driven
through a finite state machine to determine the current state of health.
NCR terminals and peripherals have been instrumented to log the
events needed to drive this state machine and allow RSM to determine
their current state of health.
State-of-health is a key component of RSM and therefore is easily
visible from the RSM user interface. At RSM LE, State of Health
monitors the peripherals attached to the system, and reports problems
that are encountered, from the platform devices.
10 Chapter 2: Using RSM LE
Connectivity
The Connectivity screen shows the current connection status to RSM
EE.
Chapter 2: Using RSM LE 11
Event Logs
The Event Logs section shows all the information contained in the
Application, System, and Security logs. One screen of log entries is
displayed at a time and you use the Previous Set or Next Set button
to move through the entries. The logs may also be cleared using the
Clear Logs button.
12 Chapter 2: Using RSM LE
Tallies
Tallies are available when RPSW is installed and licensed with RSM.
Tallies are not available with RSM LE every unit item functionality.
Tallies are maintained for each peripheral. These tallies are counts of
both good and bad information that are incremented until reset by a
user. The good tallies allow comparison of bad to good counts, as well
as assisting in proactive maintenance of devices. Refer to the OPOS
Help file or the NCR Retail Controls 3.x UPOS User's Guide for Windows
(B005-0000-1619) for a listing of the tallies for the various devices.
In addition to the RPSW peripherals, tallies may also be maintained by
any software using the NCR Store Minder tally interface to create and
increment tallies. Refer to the RSM SDK LPIN (G370-2800-0100).
14 Chapter 2: Using RSM LE
Processes
The Processes screen is selected from Monitor → Processes. It shows
the processes that are running and their CPU utilization percentage.
16 Chapter 2: Using RSM LE
Services
The Services screen is selected from Monitor → Services. It shows the
Services that are installed and their Stopped/Started state.
Chapter 2: Using RSM LE 17
Administration
The Administration section is included in all versions of RSM LE. The
features include:
• RSM Services
• Licensing
• Alerting (if licensed)
• Critical Events (if licensed)
• Tally Thresholds (if licensed)
• OS Monitoring (if licensed)
• Data Capture
RSM Services
The Services menu for RSM LE is used with a system that is being
managed by an RSM server. If you are running the RSM LE in an
unmanaged, local environment, you won’t need to use any of these
features.
18 Chapter 2: Using RSM LE
Customer Number
The customer number is used to identify the customer using RSM.
The Customer Number is shown on the contract with NCR.
RSM Managed
Enabled/Disabled - Indicates whether this system is managed by
an RSM SE Server. If this is set to enabled, it is assumed that this
RSM LE system will be managed by a RSM SE Server and the
Customer Number field is not changeable at RSM LE. This is
because the RSM SE system manages the Customer Number.
Custom Tag
Permit you to group systems into various roles such as the
functional area in the store, a region in the country, or any other
grouping you wish.
OS Monitor
Enable/Disable the monitoring of the Operating System.
File Agent
This must be enabled to support file distribution packages
scheduled from RSM SE or RSM EE.
Software Agent
This must be enabled to support software execution in packages
scheduled from RSM SE and EE servers.
Licensing
The licensing section shows the current licensing information. These
are all information fields and cannot be changed on this screen.
Current User
The current user is the user who is currently logged into this
session of RSM LE.
License File
This shows the name of the license file currently in use.
License Expiration
This is the expiration date for the license file.
Chapter 2: Using RSM LE 21
Alerting
The Alerting section permits you to change the settings for the logs and
tallies and permits you to configure the SNMP Agent.
• Failure Audit
Overall Alerts
Overall traps may be sent for changes in the overall status of the
terminal or kiosk. This is a roll up of the statuses of the terminal based
on the status of all devices.
The Overall traps may be filtered by severity. The “Suppress Overall
Alerts with…” setting in the RSM UI allows configuration of which
Overall traps should be sent or suppressed. Checking the alert means
that it will be suppressed. Select Administration → Alerting → SNMP
Agent - Suppress Overall Alerts with.
Device Alerts
Device traps may be sent for changes in the State of Health for a
peripheral or device on a terminal or kiosk. The State of Health for
each device on the system is monitored separately.
The Device traps may be filtered by severity. The “Suppress Device
Alerts with…” setting in the RSM UI allows configuration of which
Device traps should be sent or suppressed. Checking the alert means
that it will be suppressed. Select Administration → Alerting → SNMP
Agent - Suppress Device Alerts with.
Tally Alerts
Traps may be sent when a tally reaches a tally threshold configured
through RSM. Note that Tally Threshold Traps are new in the RSM
SNMP Agent and were not supported in the NCR Retail SNMP Agent.
The Tally Threshold traps may be filtered. The “Suppress Tally Alerts
with…” setting in the RSM UI allows configuration of whether Tally
Threshold traps should be sent or suppressed. Checking the alert
means that it will be suppressed. Select Administration → Alerting
→ SNMP Agent - Suppress Tally Alerts.
Maximum Alerts in Queue defines the length of the internal queue for
TRAP events. If the queue becomes full, TRAP events will be dropped
(based on this value). Possible values are 10 through 1000. Default:
256.
When Full Queue
Select Administration → Alerting → SNMP Agent - When Queue
Full.
This determines the strategy for managing the internal TRAP queue
when the queue becomes full and a new TRAP event is created. The
possible values are:
1 - Discard Old Alerts (overwrite older TRAP events) (Default)
2 - Discard New Alerts (ignore new TRAP events)
Heartbeat Configuration
Heartbeat Interval
The interval (in seconds) between which the RSM SNMP Agent will
send a periodic heartbeat trap. A zero (0) value indicates that no
heartbeat trap should be sent. Possible values are 0 through 86400
seconds (24 hours).
30 Chapter 2: Using RSM LE
Critical Events
In the Critical Events section, you can change and view the threshold
information for the various critical errors that were automatically set
up during the RPSW installation. You can also add your own
additional events.
32 Chapter 2: Using RSM LE
After an event set has been chosen, you can select a specific error and
change the threshold information.
When you select the Add Event button, you select the Group;
Application, Security, or System and then the parameters are the same
as the modify explained above.
If licensed, an additional Message Files tab is provided on this screen.
The message files tab allows viewing the messages in the event
message files registered, for any event source. This is useful for
determining what the critical events mean and for determining what
events the user wants to configure. You can choose the message Group
and then you can choose a source within that group. The message file,
message numbers and descriptions appear for that source.
Tally Thresholds
Tallies are counts of the number of times a certain operation is
performed. For example, the number of track 1 reads on the Magnetic
Stripe Reader. A tally threshold is the number of tallies recorded for a
device when you wish to be notified.
There are multiple ways to set tally thresholds:
36 Chapter 2: Using RSM LE
• Default tally thresholds are installed with RPSW. The default tally
thresholds are based on the default profiles. If the default profiles
are not used, the default tally thresholds should be replaced with
tally thresholds for the peripheral profiles used.
• An alternate set of tally thresholds can be installed with RPSW
using a command line parameter to specify a .reg file containing
tally thresholds.
You can go through the device tallies by selecting Next Set or
Previous Set.
Chapter 2: Using RSM LE 37
OS Monitoring
Operating System (OS) Monitoring provides a display of various
features that can be measured by the operating system. There are three
sections defined for OS Monitoring as shown with the tabs.
• CPU & Memory
• Disks & Files
• Processes & Services
System-wide Monitor
• System-wide monitoring - You can enable/disable monitoring of
the CPU/memory usage for the overall system.
• Monitor Interval - This time (in seconds) determines how often the
system-wide monitoring occurs.
Chapter 2: Using RSM LE 39
CPU Usage
• Maximum CPU Usage - You define the highest reading for CPU
usage of the entire system before an alert of the condition is
generated.
• High Usage Tolerance - This is the amount of time (in seconds) that
the CPU can maintain the “Maximum CPU Usage” level before an
event for the condition is generated.
Memory Usage
• Maximum Memory Usage - This is the amount of memory (in KB)
that can be used before an event for the condition is generated.
Disk Space
• Disk Space Monitoring - You can enable/disable monitoring of the
disk drives.
• Disk Monitor Interval - The number of minutes between checking
of disk free space. If this is zero, disk monitoring is only done at
the startup of NCRLoader.
• Disk Start Up Delay - This permits you to set the monitoring to
start after the system is fully up. The default values are selected so
that all OS monitoring does not start at the same time.
• Monitored Disks - The logical drives to monitor. Only Fixed drives
are monitored. The options include: ”All Disks” or “Specific
Disks”. If “All Disks” is selected, all drives will be monitored.
• Logical Drive… - You can select a logical drive (or all drives) to
monitor.
• Attention Soon Warning - When the disk drive reaches this
(percentage) capacity, an “Attention Soon Warning” alert is sent.
• Attention Now Warning - When the disk drive reaches this
(percentage) capacity, an “Attention Now Warning” alert is sent.
The Attention Now Warning value should be greater than the
Attention Soon Warning.
• Monitor interval… - This time (in minutes) determines how often
the drives are checked.
S.M.A.R.T Drive
• S.M.A.R.T. Drive Monitoring - You can enable/disable monitoring
of the S.M.A.R.T drives.
• S.M.A.R.T. Monitor Interval - This time (in minutes) determines
how often the drives are checked. If this is zero, SMART disk
monitoring will only be done at the startup of NCRLoader.
• S.M.A.R.T. Start Up Delay - This permits you to set the monitoring
to start after the system is fully up. The default values are selected
so that all OS monitoring does not start at the same time.
Chapter 2: Using RSM LE 41
• Drives Monitored - You can select a S.M.A.R.T drive (or all drives)
to monitor. If “All Drives” is selected, all physical disks connected
will be monitored.
File
• File Monitoring - You can enable/disable the monitoring of files.
• Monitor Interval - This time (in minutes) determines how often the
files are checked. If this is zero, the monitoring will only be done at
the startup of NCRLoader.
• File Start Up Delay - This permits you to set the monitoring to start
after the system is fully up. The default values are selected so that
all OS monitoring does not start at the same time.
Files Monitored
You can add files to be monitored by RSM. To do this, select the Add
button.
1. Select File, then OK.
42 Chapter 2: Using RSM LE
To stop the monitoring for a file, select the line containing the name of
the file, and then select Remove. Confirm the removal by selecting
OK.
44 Chapter 2: Using RSM LE
Processes
• Process Monitoring - You can enable/disable the monitoring of
processes.
• Process Monitor Interval - This time (in minutes) determines how
often the processes are checked. It this is zero, process monitoring
will only be done at startup of NCRLoader.
• Process Start Up Delay - The number of minutes before process
monitoring starts after this module is started by NCRLoader.
Chapter 2: Using RSM LE 45
To stop monitoring a Process, select the line containing the name of the
Process, and then select Remove. Confirm the removal by selecting
OK.
Chapter 2: Using RSM LE 47
Services
• Service Monitoring - You can enable/disable the monitoring of
Services.
• Service Monitor Interval - This time (in minutes) determines how
often the Services are checked.
• Service Start Up Delay - The number of minutes before service
monitoring starts after this module is started by NCRLoader.
You can add Services to be monitored by RSM. To do this, select the
Add button, select Service, then OK.
48 Chapter 2: Using RSM LE
To stop monitoring a Service, select the line containing the name of the
Service, and then select Remove. Confirm the removal by selecting
OK.
50 Chapter 2: Using RSM LE
Data Capture
Data Capture is for use by NCR developers when a problem arises
with NCR software. The NCR developer will give you information for
the Trace Mask and the Level Mask, based on the problem he is trying
to solve.
Data Capture information is accessed from Administration
→ DataCapture.
You can configure data capture for either Simple logging or Advanced
(more detailed) Logging by selecting Configuration.
Chapter 2: Using RSM LE 51
If you select Simple configuration, you can then set the default logging
option by selecting Default Setting. Simple configurations permit
easily selecting the most commonly used data capture settings.
52 Chapter 2: Using RSM LE
Then for each module, you can select from the following.
You can set the overall Trace Mask and Level Mask settings (as shown
below) or you can set them for a specific module by selecting the
module.
The Trace Mask settings include:
A utility to create the GDF file is then launched on the system where
the information is to be gathered. The filename is of the following
form so that creating a file does not overwrite the files previously
created:
<product>_<date>_<time>.zip
For example: RPSW_20060810_133314.zip
Using Peripherals
Peripherals consist of OPOS/JavaPOS retail peripherals and the Device
Assets.
When RPSW is installed, the default profiles for the retail peripherals
you chose are installed. These profiles provide some default
configurations for the most common uses of the peripherals. You can
change a profile’s configuration or create new configurations based on
your needs.
58 Chapter 2: Using RSM LE
Changing a Profile
To change a profile, select one of the available profiles from the drop-
down list and select OK.
You can change any parameter that is not grayed out by selecting that
parameter and making the changes. Fields in bold font are changes
that haven’t been saved. After making the changes, select Save.
60 Chapter 2: Using RSM LE
Deleting a Profile
Select the Delete button to remove a profile. Select the profile name to
delete and select Delete.
Chapter 2: Using RSM LE 61
Diagnostics
Two different types of Diagnostics may be performed. Interactive
Diagnostics usually require interaction from the user (swipe a card,
scan an item). Non-interactive Diagnostics usually test the internal
software and/or hardware and do not require user interaction. To run
printer diagnostics, select Peripherals → POS Printer(Desired Profile)
→ Diagnostics button, then Local Attended Diagnostics.
The printer test permits you to select a specific print station and other
parameters associated with that printer. When you press the Print
button, information should be printed on the selected printer.
62 Chapter 2: Using RSM LE
Platform Devices
There are a few system devices that are not controlled by OPOS or
JavaPOS software, and they may provide some configuration
information or other information about the device. The devices that
are not controlled by OPOS or JavaPOS include the following:
Audio
• Audio volume
• Diagnostics button tests Stereo, Left, or Right Speaker
BIOS
BIOS Information
• BIOS Version
• BIOS Release Date
• BIOS Vendor
• BIOS ROM Size
• BIOS OEM String
Chapter 2: Using RSM LE 63
System Information
• NCR Class & Model
• NCR Serial Number
• Manufacturer
• Motherboard ID
• Browser Button (for AMT if installed)
Memory - If licensed
• Physical Memory
• Available Memory
• Memory Usage
• Page File Size
• Available Page File Size
Motherboard
• NCR Class & Model
• NCR Serial Number
• Manufacturer
• Manufacturer ID
• Processor
• System-wide CPU Usage
Network
• Computer Name
• Number of Adapters
• Adapter 1 MAC Address (for each adapter)
Chapter 2: Using RSM LE 65
OS Image
• NCR Part Number
• NCR LPIN
• NCR Version
Serial Ports
• Identifies the COM Ports attached to the system.
• Diagnostics button permits you to choose a COM port, and then a
turnaround test is performed if a turnaround plug is installed on
that port.
Software - If licensed
Lists the software installed on the system.
Touchscreen
• Controller
• Diagnostics button to test a touchscreen
Versioning
Version numbers for the modules in the following categories:
• RSM Version
Common
• Common Kernel Drivers
• Common Libraries
• Common IO Libraries
• Common OSAL Libraries
• Common Utilities
Platform
• Platform Agents
• Platform HAL
Chapter 2: Using RSM LE 67
Retail Controls
• JavaPOS Retail Controls
• Retail Control Models
• OPOS Retail Controls
• RSM
These devices may generate critical events, such as when the disk
becomes full.
Power States
The Power States for a System can be controlled within RSM. The
following control is provided:
• Restart
• Shutdown
• Daily Reset
• Daily Wake Up (wake on alarm)
• Power Switch (on terminals that support power switch disable)
• Reboot Type (cold/warm)
• Boot Order (normal/network)
68 Chapter 2: Using RSM LE
Restrictions
Standby is supported only if the system and the operating system
support ACPI and standby. Standby is not supported on Windows
NT.
Some of the 7402, 7457-4xxx, and 7458-4xxx terminal systems do not
wake (Wake-on-LAN or Daily Wake Up) from the off state (depending
on the BIOS version). All versions do wake from Standby.
Some systems may require OS, network driver configuration, or BIOS
changes to enable Wake-on-LAN.
The Power Switch enabled/disabled setting is supported only on the
following systems:
• 7452
• 7453
• 7456
• 7457-1xxx and 2xxx
• 7458-1xxx and 2xxx
The Reboot Type and Boot Order settings which affect the
corresponding BIOS settings are supported only on the following
systems:
• 7402
• 7403
• 7457-4xxx
• 7458-4xxx
• 7459