Diebold Nixdorf ProBase Store 1 User manual

USER MANUAL

ProBase Store 1

JavaPOS™, OPOS, POS for .NET and CPOS

January 2023

Systems Group Retail Products 2

Imprint

Mathias Janke

Diebold Nixdorf

Systems Group Retail Products

Wohlrabedamm 31

13629 Berlin

mathias.janke@dieboldnixdorf.com

Systems Group Retail Products 3

Revision history

Version

Date

Author

Comment/Change

1.0

December 2019

Mathias Janke

Initial Version

2.0

January 2020

Mathias Janke

Final version based on ProBase Store 1.0

2.1

March 2020

Mathias Janke

Typos corrected

3.0

April 2020

Denis Kuniß

Version corresponding to ProBase Store 1.1

3.1

June 2020

Mathias Janke

Version corresponding to ProBase Store 1.1 Update

Release 1

3.2

July 2020

Mathias Janke

Version corresponding to ProBase Store 1.1 Update

Release 2

4.0

October 2020

Mathias Janke

Version corresponding to ProBase Store 1.2

4.1

November 2020

Mathias Janke

Version corresponding to ProBase Store 1.2 Update

Release 1

5.0

April 2021

Mathias Janke

Version corresponding to ProBase Store 1.3

5.1

May 2021

Mathias Janke

Version corresponding to ProBase Store 1.3 Update

Release 1

5.2

May 2021

Mathias Janke

Version corresponding to ProBase Store 1.3 Update

Release 2

5.3

July 2021

Mathias Janke

Version corresponding to ProBase Store 1.3 Update

Release 3

6.0

December 2021

Denis Kuniß

Version corresponding to ProBase Store 1.4

7.0

April 2022

Denis Kuniß

Version corresponding to ProBase Store 1.5

7.1

May 2022

Mathias Janke

Version corresponding to ProBase Store 1.5 Update

Release 1

7.2

August

Mathias Janke

Version corresponding to ProBase Store 1.5 Update

Release 2

7.3

September

Mathias Janke

Version corresponding to ProBase Store 1.5 Update

Release 3

8.0

August 2022

Mathias Janke

Version corresponding to ProBase Store 1.6

Systems Group Retail Products 4

8.1

September 2022

Mathias Janke

Version corresponding to ProBase Store 1.6 Update

Release 1

8.2

October 2022

Mathias Janke

Version corresponding to ProBase Store 1.6 Update

Release 2

8.3

November 2022

Mathias Janke

Version corresponding to ProBase Store 1.6 Update

Release 3

9.0

January 2023

Mathias Janke

Version corresponding to ProBase Store 1.7

Systems Group Retail Products 5

Copyright and Trademarks

Microsoft and Windows are registered trademarks of Microsoft Corporation.

Diebold Nixdorf and BEETLE are registered trademarks of Diebold Nixdorf, Inc.

Linux is a registered trademark of Linus Torvalds.

Red Hat and CentOS are registered trademarks of Red Hat, Inc.

JavaPOS is a trademark of Sun Microsystems, Inc.

Oracle and Java are registered trademarks of Oracle and/or its affiliates.

iButton is a registered trademark of Maxim Integrated

All other company names and trademarks mentioned in this documentation are the property of their

respective owners.

 
 
Systems Group Retail Products  6 
Contents 
References ................................................................................................................. 8 
Introduction ............................................................................................................... 9 
General information ................................................................................................ 10 
1 Background ................................................................................................................... 10 
2 Environment at Diebold Nixdorf ..................................................................................... 11 
3 License agreement / rights of use .................................................................................. 11 
Architecture and interfaces .................................................................................... 12 
1 Unified Device Manager ................................................................................................ 12 
2 JavaPOS guideline ........................................................................................................ 14 
3 Product installer ............................................................................................................. 14 
Specifications .......................................................................................................... 18 
1 Released installer versions ............................................................................................ 18 
2 Software requirements ................................................................................................... 18 
3 Supported peripherals ................................................................................................... 25 
4 Supported operating systems ........................................................................................ 28 
5 Supported Java Runtime Environments ......................................................................... 29 
6 Available add-ons .......................................................................................................... 29 
Installation ............................................................................................................... 30 
1 Prerequisites ................................................................................................................. 30 
2 Installation under Windows ............................................................................................ 30 
3 Installation under Linux .................................................................................................. 35 
4 Update installation ......................................................................................................... 35 
5 Upgrade installation ....................................................................................................... 36 
Uninstallation .......................................................................................................... 37 
1 Uninstallation under Windows ........................................................................................ 37 
2 Uninstallation under Linux ............................................................................................. 38 
Configuration ........................................................................................................... 40 
1 JavaPOS configuration .................................................................................................. 40 

 
 
Systems Group Retail Products  7 
2 The JavaPOS Configurator ............................................................................................ 41 
3 OPOS configuration ....................................................................................................... 48 
4 P4DN configuration ....................................................................................................... 50 
5 CPOS configuration ....................................................................................................... 59 
6 UDM configuration ......................................................................................................... 59 
7 D&S Platform T/SOP configuration ................................................................................ 66 
Logging .................................................................................................................... 68 
1 Logging during installation ............................................................................................. 68 
2 Logging during uninstallation ......................................................................................... 69 
3 JavaPOS Logging .......................................................................................................... 69 
4 JavaPOS Configurator logging ...................................................................................... 74 
5 OPOS logging................................................................................................................ 74 
6 P4DN logging ................................................................................................................ 76 
7 CPOS logging ................................................................................................................ 76 
8 UDM logging .................................................................................................................. 77 
9 D&S Platform T/SOP Logging ........................................................................................ 79 
Programming examples.......................................................................................... 81 
1 JPOS ............................................................................................................................. 81 
2 OPOS ............................................................................................................................ 81 
3 CPOS ............................................................................................................................ 81 
4 P4DN ............................................................................................................................. 81 
Tools ........................................................................................................................ 82 
1 ProBase/JavaPOS Tool Center ..................................................................................... 82 
2 OPOS UDM Configuration Updater ............................................................................... 84 
3 Test tools ....................................................................................................................... 84 
4 D&S Platform T/SOP ..................................................................................................... 90 
5 PBReport ....................................................................................................................... 92 
Appendix .................................................................................................................. 93 
1 End-user license agreement .......................................................................................... 93 
 

Systems Group Retail Products 8

1 References

Diebold Nixdorf. (2016). Guide Line Definition for JavaPOS for Linux OS (version 1.6).

Diebold Nixdorf. (2016). Guide Line Definition for JavaPOS for Windows OS (version 1.3).

Diebold Nixdorf. (2017). JavaPOS Unified Device Manager Programmers & User Guide (version 1/14).

Diebold Nixdorf. (2019). ProBase Store 1 Migration Guide (version 1.0).

Diebold Nixdorf. (2022). Diagnostics and Serviceability Platform Integration Manual.

Diebold Nixdorf. (2022). Technical Service and Operation (T/SOP) User Manual.

Diebold Nixdorf. (2023). Installation Guide ProBase Store 1 Linux (version 10.0).

Diebold Nixdorf. (2023). Installation Guide ProBase Store 1 Windows (version 10.0).

National Retail Federation. (2014). UnifiedPOS Retail Peripheral Architecture (version 1.14.1).

Russell, J., & Laan, M. (2019). Inno Setup Help. Retrieved from Inno Setup Help:

https://www.jrsoftware.org/ishelp/

Systems Group Retail Products 9

2 Introduction

ProBase Store, the current middleware product for retail, is the direct successor to the previous

middleware products ProBase Retail 1.x and ProBase POS 2.x and is therefore the middleware product

for all active and future DN Retail products.

The content of ProBase Store largely corresponds to the combination of the two previous products

ProBase POS and ProBase Retail. The UnifiedPOS

1

interfaces JavaPOS

2

, OPOS

3

and P4DN for POS

peripherals and JavaPOS for cash recyclers and security scales are included. Test and configuration

tools (such as the JavaPOS Configurator or SwingSamples), released firmware versions for the

supported cash recyclers and the D&S Platform with the graphical user interface T/SOP are also part of

ProBase Store.

Following the DN JavaPOS guideline, ProBase Store, like ProBase POS before it, offers automated

integration of JavaPOS add-ons, automated generation of customizable JavaPOS configurations and

separation of configuration and log files from the installation location of ProBase Store.

A new feature of ProBase Store is the use and delivery of standardized OpenNames to simplify the

relationship between hardware and OpenNames.

This user manual is intended to provide an overview of the functions and tools provided with ProBase

Store. Installation and uninstallation, configuration of the individual software layers as well as logging are

dealt with separately.

Supported operating systems, peripherals, and cash recycler as well as requirements regarding the

Java runtime environment, system and device drivers, firmware versions and other software frameworks

are also covered in this manual. However, this information may change slightly for each ProBase Store

version. Therefore, please refer to the release notes of the corresponding ProBase Store version, as

they will provide more up-to-date information in this regard.

1

https://www.omg.org/retail/unified-pos.htm

2

www.javapos.com

3

OPOS - OLE for Retail POS

Systems Group Retail Products 10

3 General information

3.1 Background

The increasing use of Microsoft operating systems on retail market systems as well as the associated

standard OPOS in 1994 had at that time led to the first module-based provision of the peripheral drivers

according to the OPOS standard.

With the emerge of the Java technology to be usable for retail branch solutions and the introduction of

this programming language into the POS application world in 1997, it became necessary for Diebold

Nixdorf to provide the corresponding JavaPOS drivers.

Based on evaluation results on Java, a close cooperation between Diebold Nixdorf and its retail

customers developed in the realization of projects based on Java technology. In the past, JOWE

4

(Java

OPOS Wrapper) was the first available software / abstraction layer for controlling retail peripherals from

Java applications under Microsoft Windows operating systems.

At the same time, the standard JavaPOS developed under the proactive cooperation of Diebold Nixdorf

in the relevant committees for this technology approach. On the background of the progress in the

international JavaPOS standardization, the retail market could now also be offered a pure JavaPOS

adapted to the current requirements of the market.

About two years later, the standardization committee decided to meet the requirements for the

synchronization of OPOS and JavaPOS and the standard UnifiedPOS was created. UnifiedPOS is an

acronym for Unified Point of Service (UPOS), which is used to unify the OPOS and JavaPOS interfaces.

UPOS is not really a driver implementation, but rather an abstract interface definition. The conversion of

the definition into usable code as driver for POS applications is OPOS (as ActiveX or ATL objects in the

Microsoft world) and JavaPOS (as JAR modules in the Java world and thus for Windows and Linux

operating systems).

Since 2002, with the introduction of the .NET Framework on Microsoft Windows operating systems,

there has been another technology for application programming and starting 2003 there were requests

for a further implementation of UPOS for .NET based POS applications. This POS for .NET (P4DN)

implementation of the UPOS standard is based on the .NET technology of the Microsoft Windows

operating systems.

The provision of these three driver stacks, which have all been implemented according to the same

design principles, has led to ProBase POS/ProBase Retail and now to ProBase Store. The peripheral

interfaces JavaPOS, OPOS and P4DN will be delivered with ProBase Store in the future.

As a further interface, Diebold Nixdorf also offers the interface CPOS for applications, which were

developed in the programming language C. This is also an implementation according to the UPOS

standard; here the access takes place via the usual methods in the C programming world.

The basis of ProBase Store is the implementation of the UPOS standard for JavaPOS, which is always

the interface to the peripheral devices. The interfaces OPOS and P4DN are supported with

simultaneous use of the so-called Unified Device Manager (UDM).

4

no longer supported

Systems Group Retail Products 11

3.2 Environment at Diebold Nixdorf

ProBase Store can be used on all released DN Retail systems under the ProBase Store approved

operating systems.

The approved operating systems for each DN Retail system can be found within the current configurator

in the DN intranet portal (go to Intranet > Portfolio > Our Portfolio > Services > Configurator/Price list). In

case no access is granted to that site, a Diebold Nixdorf account manager must be contacted.

Details about the supported systems and peripherals as well as dependencies regarding driver and

firmware versions can generally be found in in chapter 5 - Specifications as well as the respective

ProBase Store Release Notes.

3.3 License agreement / rights of use

The software ProBase Store 1 is subject to license and usage conditions. The exact wording of the End

User License Agreement can be found in the appendix, chapter 12.1 - End-user license agreement.

Systems Group Retail Products 12

4 Architecture and interfaces

ProBase Store 1 provides the well-known interfaces JavaPOS, OPOS and POS for .NET (P4DN) as well

as CPOS, an interface for C-based applications, for Windows and Linux based operating systems.

These interfaces are all implementations based on the UnifiedPOS specifications with the following

versions:

• JavaPOS 1.13 or higher

• OPOS 1.13

• P4DN 1.12 or 1.14

• CPOS 1.14

The base of ProBase Store is the JavaPOS of Diebold Nixdorf. The interfaces OPOS, CPOS and P4DN

are supported if the UDM is used at the same time.

The interfaces OPOS 1.3, JavaPOS 1.7 and 1.5 as well as RDI and LRDI are not supported by ProBase

Store and cannot be operated in parallel with the interfaces of ProBase Store.

Note: OPOS and P4DN are reserved for the Windows operating systems, since the basic technology is

only available under Windows.

Note: ProBase Store contains the JavaPOS controls based on UnifiedPOS 1.14 and supports the POS

for .NET Frameworks 1.12 with the functionality specified with UnifiedPOS 1.12 and the POS for

.NET Framework 1.14 with the functionality specified with UnifiedPOS 1.13.

4.1 Unified Device Manager

The UnifiedPOS standard describes the device interfaces independently to the implementation.

Normally, this is done with a Unified Modeling Language (UML). However, different technologies and

implementations are used in the retail sector, for which some separate appendices have been added to

the UnifiedPOS specification. The most important implementations of the standard are:

• OPOS (since 1994)

• JavaPOS (since 1998)

• POS for .NET (since 2006)

Hardware manufacturers needs to offer all three implementations to support the entire UnifiedPOS

standard. Differences in the implementation technologies and therefore in the methods, properties, and

events, as well as differences between Windows and Linux operating systems, can lead to different

behavior of the addressed hardware although the implementations all follow the same standard. Further

requirements of the application developers to support other technologies (for example in the Linux area

further non-Java based API) have not been considered yet.

Normally, there is no way to allow an application written in one technology to access a UnifiedPOS

device interface written in another technology. This usually requires an adapter or wrapper.

Diebold Nixdorf has developed the Unified Device Manager based on the different implementation

technologies, the different operating system types (Windows and Linux) as well as the different

implementations of the UnifiedPOS standard.

The Unified Device Manager provides a socket-based client-server construct, which uses JavaPOS for

the communication with the hardware and provides all other implementation technologies according to

Systems Group Retail Products 13

the UnifiedPOS standard via generic service objects. This approach is also important for JavaPOS as

soon as the UDM client and the UDM server are to be used on different devices (e.g., mobile POS).

The following figure shows the UDM architecture as it is provided for Windows.

Figure 1: UDM architecture under Windows

The generic service objects convert the method calls of the application into corresponding JavaPOS

calls, just as the answers from JavaPOS are converted back into the target implementation for the

application. For the application itself, the UDM and the shared JavaPOS are presented transparently.

This results in the following advantages for the customer:

• An identical behavior of the device services under OPOS, JavaPOS, POS for .NET and CPOS

• In the OPOS area, the common controls can be used again

• Coexistence of Diebold Nixdorf device services or service objects with those of third-party

manufacturers is possible

• UnifiedPOS remains the standard long-term constant

• A common software stack for POS peripherals, SCO and ACO systems

• Harmonized interfaces for applications such as Vynamic™ Checkout, VSS and retail partner

applications

Systems Group Retail Products 14

4.2 JavaPOS guideline

By working with the UPOS standard, it turned out that not everything has been standardized or that

there are no guidelines for the implementation. As a result, Diebold Nixdorf, together with selected

partners and customers, developed a JavaPOS guideline

56

that includes the following topics:

• Packaging and delivery of JavaPOS components

• Configuration of the JavaPOS modules to the desired hardware

• Handling additional functions for firmware and device settings

• Handling of additional inventory and statistic data by JavaPOS

• Integration of JavaPOS components from different manufacturers

Focus of this guideline is to simplify the integration of JavaPOS components from different

manufacturers through uniform installation routines. The integration is not done by copying individual

JAR files, but by referencing them. By embedding the JAR files into compliant installers, they are

automatically updateable without manual adaptation.

Starting with ProBase POS 2 and now with ProBase Store 1 also, Diebold Nixdorf follows this DN

JavaPOS guideline.

The biggest differences to the previous architecture, which was implemented in the ProBase POS 1.1

and ProBase Retail 1.2 versions, can be seen in the various installation paths, the folder structures

contained in them and the locations of files and user data such as JAR files, dynamic link libraries,

shared objects, log files and configuration files defined by the policy. The requirements for the paths to

be used correspond to the usual standards of the operating systems (e.g., Linux -> LSB) plus the

necessary extensions for using the JavaPOS architecture.

To minimize the integrational effort, Diebold Nixdorf provides with the JavaPOS Configurator in ProBase

Store 1 a tool, which generates a common system configuration from the individual JavaPOS

components of several manufacturers generated according to the directive. Using application-specific

configuration files, this system configuration can be further customized by the JavaPOS Configurator.

4.3 Product installer

4.3.1 Variants

ProBase Store 1 product installer are available as 32-bit and 64-bit versions for Windows and Linux

based operating systems. The installer variants (32 or 64-bit) are based on the process architecture of

the application respectively on the Java Virtual Machine (Java VM) architecture to be used. This means

that e.g., when using a 32-bit application / Java VM on a 64-bit operating system, the 32-bit ProBase

Store installer needs to be used anyway.

The provided product installers follow the naming scheme:

Windows

• ProBaseStore-MAJOR.MINOR.BUILD-x64.exe

• ProBaseStore-MAJOR.MINOR.BUILD-x86.exe

Linux

5

JavaPOS General Requirements for Linux; Diebold Nixdorf; Peter Duellings; version 1.6

6

JavaPOS General Requirements for Windows; Diebold Nixdorf; Peter Duellings; version 1.3

Systems Group Retail Products 15

• dn-probase-store-MAJOR.MINOR.BUILD-i386.rpm

• dn-probase-store-MAJOR.MINOR.BUILD-x86_x64.rpm

Example: ProBaseStore-1.0.48-x86.exe

For a detailed listing of supported operating systems, see chapter 5.4 - Supported operating systems.

The currently available ProBase Store installer are listed in chapter 5.1 - Released installer versions.

4.3.2 Installation profiles

Windows

The current product installer for Windows operating systems is based on Inno Setup, which offers the

concept of installation profiles and can be used interactively as well as remotely, silent, or unattended.

In case of the ProBase Store installer, a profile is connected to a certain implementation technology,

which allows the programmatic access to peripheral devices. This allows the user to select the

technology that fits the application. The installer ensures that all components for the selected profile are

installed correctly and completely.

If necessary, the user can also make changes to the selection of the components specified by the

preselected profile by further selecting or deselecting components in the Custom Installation profile.

However, the installer cannot perform a consistency check of the components in the modified profile, so

the user must ensure that all required components are installed. Otherwise, the application may not or

may work in a limited way.

The following table shows the currently defined installation profiles:

Profile Name

Profile Meaning

JavaPOS Installation

(ACO)

Installation profile for JavaPOS based applications.

Supports all Cash recycler and POS peripherals, including D&S

T/SOP.

Note: Installer default profile

JavaPOS Installation

(POS)

Installation profile for JavaPOS based applications.

Note: Supports POS peripherals only.

OPOS Installation

(POS)

Installation profile for OPOS based applications.

Forwards OPOS calls to DN’s JavaPOS implementation using the

UDM technology.

Note: Supports POS peripherals only.

POS for .NET 1.12 Installation

(POS)

Installation profile for POS for .NET 1.12 based applications.

Forwards POS for .NET calls to DN’s JavaPOS implementation using

the UDM technology.

Note: Supports POS peripherals only.

Systems Group Retail Products 16

Profile Name

Profile Meaning

POS for .NET 1.14 Installation

(POS)

Installation profile for POS for .NET 1.14 based applications.

Forwards POS for .NET calls to DN’s JavaPOS implementation using

the UDM technology.

Note: Supports POS peripherals only.

CPOS Installation

(POS, for C-applications)

Installation profile for C based applications.

Forwards C calls to DN’s JavaPOS implementation using the UDM

technology.

Note: Supports POS peripherals only.

Custom Installation

Installation profile for customizing the component selection,

preselected by the previously chosen installation profile.

Note: It is recommended to use the predefined profiles and to perform a customized installation only

after consultation with the Diebold Nixdorf support team

7

.

Linux

The current product installer for Linux operating systems bases on the Red Hat Package Manager

(RPM) and does not provide any profiles. All dependencies to other packages will be checked by the

Package Manager and, if possible, automatically resolved.

4.3.3 Default paths

Windows

ProBase Store 1 will be installed in C:\Program Files\javapos\ProBase-Store for architecture identical

installations (e.g., 32-bit on 32-bit Windows) and in C:\Program Files (x86)\javapos\ProBase-Store for

architecture-non-identical installations (32-bit on 64-bit Windows) (in the document further referred to as

<ProBase Store installation directory> or <PBS installation directory>).

User data such as configuration files and log files are stored in subdirectories under

C:\ProgramData\javapos according to the DN JavaPOS guideline.

In the Windows Start menu, the ProBase Store installer adds all links and subfolders in the directory

Diebold Nixdorf ProBase Store (xx JVM) by default. Here xx is equal to 32-bit or 64-bit, depending on

the ProBase Store installer.

Note: Windows 10 does not know multiple level of sub folder within the Start menu.

Linux

On Linux, ProBase Store 1 will be installed in the directory /opt/wn/javapos.

Configuration files are stored in subdirectories under /etc/opt and log files are stored in /var/log/wn

according to the DN JavaPOS guideline.

7

GSE; mail to retailsws[email protected]m

Systems Group Retail Products 17

4.3.4 Special features

ProBase Store 1 not only consist of UnifiedPOS implementations such as JavaPOS, OPOS and P4DN

or the Unified Device Manager, but also offers a range of tools for diagnosis, configuration, testing, and

logging purposes. Further information can be found in the chapter 8 - Configuration, 9 - Logging and 11 -

Tools.

In the last stages of the setup the product installer runs per default some of these tools to configure the

previously installed components, creates scheduled respectively auto start tasks or sets up services for

these tools.

Windows

If the OPOS profile or the OPOS UDM adapter in the Custom Installation profile has been selected, the

product installer will call the OPOS UDM Configuration Updater once and set up a permanent task for

the OPOS UDM Configuration Updater in Windows. By default, this task will be executed at each system

start and user login. Further information can be found in chapter 11.2 - OPOS UDM Configuration

Updater.

Note: It is recommended to restart the system after the installation, since the final configuration takes

place in the start phase.

 
 
Systems Group Retail Products  18 
5 Specifications 
5.1  Released installer versions 
Windows 
•  ProBaseStore-1.7.32-x86.exe  (for 32-bit Java VM) 
•  ProBaseStore-1.7.32-x64.exe  (for 64-bit Java VM) 
Linux 
• dn-probase-store-1.7.32-i386.rpm  (for 32-bit Java VM) 
• dn-probase-store-1.7.32-x86_64.rpm  (for 64-bit Java VM) 
5.2  Software requirements 
5.2.1  Installation requirements 
The conditions described in this chapter apply to the installation process only. The requirements at 
runtime, such as additional system drivers for the devices to be addressed, can be found in chapter 
5.2.2 - Runtime requirements or within the ProBase Store release notes. 
Note:  The installation of ProBase Store requires administrator permissions. 
Note:  ProBase Store, as the successor to ProBase POS and ProBase Retail, conflicts with these 
predecessors, which must be uninstalled in advance. For more details regarding the migration of 
an older DN Middleware product to ProBase Store, please refer to the ProBase Store migration 
guide. 
5.2.1.1  Minimum precondition 
The following software must already be installed on the target computer to run the ProBase Store setup 
successfully: 
•  Java Virtual Machine (version 8) 
For further information, see chapter 5.5 - Supported Java Runtime Environments. 
5.2.1.2  POS for .NET preconditions (Windows only) 
In case the POS for .NET 1.12 Installation profile (see chapter 4.3.2 - Installation profiles) or 
corresponding POS for .NET components have been selected (see chapter 6.2.1 - Interactive 
installation), ensure that the following software has already been installed on the target machine: 
•  Microsoft Point of Service for .NET (version 1.12) 
•  Microsoft .NET Framework (at least version 2.0 up to 4.0) 
 
In case the POS for .NET 1.14 Installation profile (see chapter 4.3.2 - Installation profiles) or 
corresponding POS for .NET components have been selected (see chapter 6.2.1 - Interactive 
installation), ensure that the following software has already been installed on the target machine: 
•  Microsoft Point of Service for .NET (version 1.14) 
•  Microsoft .NET Framework (at least version 4.0) 

Systems Group Retail Products 19

5.2.2 Runtime requirements

The conditions described in this chapter only apply to the runtime of ProBase Store components. The

requirements for the installation process can be found in chapter 5.2.1 - Installation requirements or

within the ProBase Store release notes.

5.2.2.1 Minimum precondition

The following software must be installed on the target system to use ProBase Store:

• Java Virtual Machine (version 8)

For further information, see chapter 5.5 - Supported Java Runtime Environments.

5.2.2.2 POS for .NET preconditions (Windows only)

In case the POS for .NET 1.12 Installation profile or corresponding POS for .NET components have

been selected during the installation of ProBase Store, the following software must be installed on the

target machine to use the POS for .NET 1.12 API:

• Microsoft Point of Service for .NET (version 1.12)

• Microsoft .NET Framework (at least version 2.0 up to 4.0)

In case the POS for .NET 1.14 Installation profile or corresponding POS for .NET components have

been selected during the installation of ProBase Store, the following software must be installed on the

target machine to use the POS for .NET 1.14 API:

• Microsoft Point of Service for .NET (version 1.14)

• Microsoft .NET Framework (at least version 4.0)

5.2.2.3 T/SOP preconditions

To use T/SOP from the D&S platform, the following software must be installed on the target system:

• Java Virtual Machine (version 8 or 11)

• Visual C++ Redistributable Packages in version 2015 is required to be installed (Windows

only). The redistributable package may be downloaded from the official Microsoft sites. On

Beetle pre-installations an installer for it may already be available.

Note: Depending on the function to be used, a user verification via CrypTA stick or smartcard is

required.

Windows

For more information, see the Diagnostics and Serviceability Platform Integration Manual with

INTEGRATIONMANUAL.pdf at <Diagserv installation directory>\doc.

Note: The <Diagserv installation directory> depends on the architecture of the ProBase Store

installer and can either be %ProgramFiles%\Diebold Nixdorf\Diagserv or

%ProgramFiles(x86)%\Diebold Nixdorf\Diagserv.

Linux

Systems Group Retail Products 20

For more information, see the Diagnostics and Serviceability Platform Integration Manual with

INTEGRATIONMANUAL.pdf at <Diagserv installation directory>/doc.

Note: The <Diagserv installation directory> is currently defined as /opt/dn/diagserv.

5.2.2.4 Driver dependencies

Some devices require additional system driver installed on the target system, which are not part of this

product.

Note: Further information regarding the correct driver version for each ProBase Store version can be

found at the related ProBase Store release notes. The table below may not be actual.

Note: The system drivers are aligned to the bit architecture of the underlying operating system.

Whereas the product is aligned to the bit architecture of the used JRE. This means, the ProBase

Store for 32-bit JVM still requires 64-bit drivers on a 64-bit Windows.

Driver

Operating System

Affected Devices

probase_fo_usb_drivers_cineo_32bit.msi

(version 1.4.31)

32-bit of

Windows® XP™,

Windows® POSReady 2009™,

Windows® 7™,

Windows® POSReady 7™,

Windows® 8.1™

CINEO C6010, C6020; iButton,

Special Electronics at ACO and

kiosk systems

probase_fo_usb_drivers_cineo_64bit.msi

(version 1.4.31)

64-bit of

Windows® 7™,

Windows® POSReady 7™,

Windows® 8.1™

CINEO C6010, C6020; iButton,

Special Electronics at ACO and

kiosk systems

BNR_USB_Driver_2.1.0.zip

Windows® XP™ SP2,

Windows® 7™,

Windows® 8.1™,

Windows® POSReady 7™

iCash20

WN_POSUSB_Driver-2.50.0.0-44-setup.exe

Windows® XP™ (32-bit only),

Windows® POSReady 2009™ (32-

bit only),

Windows® 7™,

Windows® POSReady 7™,

Windows® 8.1™

non-HID, non-cash USB devices

DN_POSUSB_Driver-3.10.0.0-7-setup.exe

Windows® 7™,

Windows® POSReady 7™,

Windows® 8.1™

Windows® 10™

non-HID, non-cash USB devices

CINEO C6010, C6020; iButton,

Special Electronics at ACO and

Kiosk systems, Retail Control Box,

Retail IO Controller, iCash45, DN

USB Security Scale SC500W

Page is loading ...

Diebold Nixdorf ProBase Store 1 User manual

Diebold Nixdorf ProBase Store 1 User manual

Related papers

Other documents