Migration Guide
ProBase Store 2.0
Diebold Nixdorf Public Use
Version 2.3.10
Table of Contents
1. Document Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê1
1.1. Document Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê1
1.2. Document History. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê1
1.3. Copyright and Trademarks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê1
2. Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê2
2.1. Purpose of This Document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê2
2.2. Target Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê2
2.3. Professional Service Contact Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê2
3. Specifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê3
3.1. Supported Operating Systems and Constraints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê3
3.2. Supported Java Runtime Environments and Constraints. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê3
3.3. Product Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê4
3.4. Conflicting Software Packages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê4
3.5. Dependent Software Packages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê4
3.6. System Driver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê5
3.7. Device Firmware. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê5
4. New Product Features and Breaking Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê6
4.1. Installation profiles Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê6
4.2. Changes To Deployment Artifacts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê6
4.3. Changed Installation Directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê6
4.4. Modified Permissions And Ownership . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê7
4.5. No Longer Supported Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê7
4.6. Removed Logical Name Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê9
4.7. Changes To Configuration Concepts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê14
4.7.1. Logger Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê14
4.7.2. CIMAdapter Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê14
4.7.3. JavaPOS Configuration Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê15
5. Upgrading Procedure from ProBase Store 1.X . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê16
References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê20
Chapter 1. Document Information
1.1. Document Status
Version: 2.3
Date: 2023/07/24
Responsible: Mathias Janke
Editors: Ragnar Seedorf, Denis Kuniß
Document Status: Draft
Protection Status: Public
1.2. Document History
Version Date Changes
2.3 2023/06/22 initial release
1.3. 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.
© Copyright 2023 by Diebold Nixdorf Systems GmbH
Migration Guide
Diebold Nixdorf Public Use 1
Chapter 2. Introduction
ProBase Store is the platform software or middle-ware product for Diebold Nixdorf retail systems
and peripherals. It provides UnifiedPOS [UPOS] library implementation for those peripherals and
targets applications based on the programming platforms JavaPOS, OPOS, POS for .NET and CPOS.
ProBase Store 2.0 is the direct functional successor of ProBase Store 1.7.
2.1. Purpose of This Document
This document describes what have to be considered when migrating from ProBase Store version 1
to ProBase Store version 2.
The intention is to provide guidance on how to migrate
•when depending on the installation artifacts and their installation structure
•working configurations
•accumulated runtime data
The document is not guiding a new installation of ProBase Store 2 from the scratch. For this please
refer to the ProBase Store 2 User Manual. [PBS2UM]
There is a separate Migration Guide that covers D&S and T/SOP related migration hints, see
[TR1MG].
For a migration of former legacy products ProBase POS version 2 or from ProBase Retail version 1.2
to ProBase Store 2 please refer to the ProBase Store 1 Migration Guide V1.0 first. [MG].
2.2. Target Audience
This guide is for integrators and professional service staff which are operating or maintaining a
ProBase Store 1 installation.
A deeper knowledge of JavaPOS configuration is required. If OPOS, POS for .NET is in use, according
knowledge about those platform’s configuration concepts is required.
2.3. Professional Service Contact Information
Pre-sales customers should contact their responsible sales / account manager. Customers who are
supported in a professional service project should contact the professional service project team /
project manager. Customers who have been in a professional service project should contact the
professional service M&S organization (Maintenance and Service). Currently, professional service
support is limited to Vynamic Checkout customers.
Migration Guide
Diebold Nixdorf Public Use 2
Chapter 3. Specifications
3.1. Supported Operating Systems and Constraints
ProBase Store 2 is released for the following operating systems:
•Microsoft Windows® 7™ Professional x86
•Microsoft Windows® 7™ Professional x64
•Microsoft Windows® 10™ IoT Enterprise x64
•Diebold Nixdorf WNLPOS 4
•Diebold Nixdorf DNL1
The following operating systems supported by predecessor ProBase Store releases are no longer
supported by ProBase Store 2:
•Microsoft Windows® Embedded POSReady 2009 x86
•Microsoft Windows® XP Professional x86
•Microsoft Windows® Embedded POSReady 7™ x86
•Microsoft Windows® Embedded POSReady 7™ x64
•Microsoft Windows® Embedded 8.1™ Industry Professional x86
•Microsoft Windows® Embedded 8.1™ Industry Professional x64
•Diebold Nixdorf WNLPOS 3
3.2. Supported Java Runtime Environments and
Constraints
The minimum required Java version for the Java Runtime Environment is Java 8.
Any of our JavaPOS Device Service or tools implementations are compiled with Java 8 target
compatibility and will not run with any Java version smaller than 8.
However, newer version of Java above version 8 are supported as well, see also ProBase Store 2
Release Notes [PBS2RN].
NOTE A JRE is already required during installation time.
NOTE
The product installers are JRE architecture specific, not really operating system
architecture specific! This means, the 64-bit ProBase Store product is only able to
run on a 64-bit Java runtime. While, the 32-bit ProBase Store product is only able to
run on a 32-bit Java runtime. However, both 32-bit product variants may be
installed on a corresponding 64-bit operating system if the 32-bit sub system is
installed (this is almost the case for Windows and WNLPOS4, but not the case for
DNL1).
Migration Guide
Diebold Nixdorf Public Use 3
3.3. Product Installer
ProBase Store 2 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:
•ProBase-Store-MAJOR.MINOR.BUILD-x64.exe
•ProBase-Store-MAJOR.MINOR.BUILD-x86.exe
Linux:
•dn-probase-store-MAJOR.MINOR.BUILD-i386.rpm
•dn-probase-store-MAJOR.MINOR.BUILD-x86_x64.rpm
The released ProBase Store 2 product installer are:
Windows:
•ProBaseStore-2.0.95-x86.exe (for 32-bit Java VM)
•ProBaseStore-2.0.95-x64.exe (for 64-bit Java VM)
Linux:
•dn-probase-store-2.0.74-i386.rpm (for 32-bit Java VM)
•dn-probase-store-2.0.74-x86_64.rpm (for 64-bit Java VM)
3.4. Conflicting Software Packages
ProBase Store 2 conflicts with any predecessor of ProBase Store 2.0, including ProBase Store 1.X,
ProBase POS, and ProBase Retail. Due to architectural changes and the composition of the installers,
an update installation is neither intended nor possible. If installed, any of those conflicting
packages have to be uninstalled before ProBase Store 2 installation is possible.
Additionally, on Linux only, the product dn-loadutil version ⇐ 3.6 conflicts with ProBase Store 2
and must be uninstalled before ProBase Store 2.0 can be installed. This is caused by changed
permissions and ownership settings of shared folders. These conflicts got solved with dn-loadutil
version >= 4.0.
NOTE It is recommended to do a cleanup after uninstallation of conflicting packages, see
also Upgrading Procedure from ProBase Store 1.X.
3.5. Dependent Software Packages
Migration Guide
Diebold Nixdorf Public Use 4
POS for .NET (Windows only)
In case component POS for .NET 1.14 or POS for .NET 1.12 has been selected for installation,
ensure the appropriate Microsoft Point of Service for .NET and Microsoft .NET Framework has
been installed. See also ProBase Store 2 User Manual [PBS2UM].
3.6. System Driver
The JavaPOS Device Service implementations are relying on system drivers. Normally, those are
coming preinstalled on Diebold Nixdorf maintained Beetle system. They are not part of the ProBase
Store 2 distribution. However, all required drivers, their versions and which particular devices
required them are documented in the ProBase Store 2.0 User Manual [PBS2UM].
It is recommended to check whether system drivers required are installed in appropriate versions.
3.7. Device Firmware
For some device there is a tightly bounding of JavaPOS or JDD implementation to firmware version
the device is running with. Minimum and recommended device firmware versions are documented
in Probase Store 2 User Manual [PBS2UM].
Migration Guide
Diebold Nixdorf Public Use 5
Chapter 4. New Product Features and
Breaking Changes
4.1. Installation profiles Windows
Installation profiles on Windows has been renamed or merged. The POS for .NET 1.12 profile has
been dropped but still is available via profile Expert Installation. Refer to ProBase Store 2 User
Manual [PBS2UM] for details.
4.2. Changes To Deployment Artifacts
The ProBase Store 2 product consists of versioned components which are aggregated and provided
through the product installer. This concept did not change and the components and their versions
may be investigated through their change notes files
(<installdir>/doc/history/<componentName>.changes.txt).
However, the set of components, their names and their contents has been changed partially but this
should not imply some action to be done during migration as long as not stated otherwise in this
document and as long as propagated JavaPOS Configurator output is being used for setting up
applications runtime environment.
One probably significant change is, that the current set of components will not provide a log4j.jar
anymore. An application that relied on log4j provided by ProBase Store will need to provide this
artifact by their own.
4.3. Changed Installation Directories
The installation structure of ProBase Store 2 is similar to its predecessor but has been changed in
detail as new naming conventions were applied.
Windows:
The main installation directory has not been changed and still is, depending on chosen installer
(ProBase Store 32 bit vs. ProBase Store 64 bit), either
C:\%ProgramFiles%\javapos\ProBase-Store\
or
C:\%ProgramFiles(x86)%\javapos\ProBase-Store\.
JavaPOS Configurator genarated artifact location also has not been changed and still is found in
C:\%ProgramData%\javapos\.
However, the location of JavaPOS related log files has been changed from
C:\%ProgramData%\javapos\wn\ to
C:\%ProgramData%\javapos\dn\.
Linux:
The installation structure is according to Linux Standard Base [LSB], so the installation location of
Migration Guide
Diebold Nixdorf Public Use 6
the artifacts depends on their purpose. With ProBase Store 2 in those paths wn consequently has
been renamed to dn:
main installation location:
/opt/wn/javapos/ >> /opt/dn/javapos/
JavaPOS related log files location:
/var/log/wn/javapos/ >> /var/log/dn/javapos/
JavaPOS related data files location:
/var/opt/wn/ >> /var/opt/dn/
JavaPOS related configuration files location:
/etc/opt/wn/javapos/ >> /etc/opt/dn/javapos/
The installation location are still compliant to the Diebold Nixdorf JavaPOS Guidelines [GL-Lin] and
[GL-Win].
4.4. Modified Permissions And Ownership
During installation, ProBase Store 2 will create a group with name dndev and is setting up
permissions and ownership of installed artifacts so that a member of that group is able to access all
required resources and to run provided tools properly.
Previous release created a group with name wndev instead. That’s why a non-root user that intends
to use ProBase Store 2 needs to join the group dndev, e.g. by:
usermod -a -G dndev <user-name>
4.5. No Longer Supported Devices
Comparing to ProBase Store 1.7 release the following devices have reached end of life and are not
supported anymore:
Belt:
•PortalScanner-Belt 1 (JavaPOS logicalName = DN_Belt_DEV1_PortalScanner_X7)
•PortalScanner-Belt 2 (JavaPOS logicalName = DN_Belt_DEV2_PortalScanner_X7)
•PortalScanner-Belt 3 (JavaPOS logicalName = DN_Belt_DEV3_PortalScanner_X7)
CashChanger:
•iCash50 (JavaPOS logicalName = DN_CashChanger_iCash50)
•iCash100 (JavaPOS logicalName = DN_CashChanger_iCash100)
CashDrawer:
•CashDrawer via ND77 (JavaPOS logicalName = DN_CashDrawer_DEV1_POSPrinter_ND77_COM,
DN_CashDrawer_DEV2_POSPrinter_ND77_COM, DN_CashDrawer_POSPrinter_ND77_COM)
Migration Guide
Diebold Nixdorf Public Use 7
•CashDrawer via ND210 (JavaPOS logicalName =
DN_CashDrawer_DEV1_POSPrinter_ND210_COM,
DN_CashDrawer_DEV2_POSPrinter_ND210_COM,
DN_CashDrawer_POSPrinter_ND210_Asia_COM, DN_CashDrawer_POSPrinter_ND210_COM )
•CashDrawer via TH250 LAN (JavaPOS logicalName =
DN_CashDrawer_DEV1_POSPrinter_TH250_LAN,
DN_CashDrawer_DEV2_POSPrinter_TH250_LAN, DN_CashDrawer_POSPrinter_TH250_LAN)
•CashDrawer via FFC-TH230 IT (JavaPOS logicalName =
DN_CashDrawer_FiscalPrinter_IT_FFCTH230_COM,
DN_CashDrawer_FiscalPrinter_IT_FFCTH230_USB)
FiscalPrinter:
•FFC-TH230 IT (JavaPOS logicalName = DN_FiscalPrinter_IT_FFCTH230_COM,
DN_FiscalPrinter_IT_FFCTH230_USB)
HardTotals:
•HardTotals-Disc (JavaPOS logicalName = DN_HardTotals_Disk)
ItemDispenser:
•PortalScanner-ItemDispenser (JavaPOS logicalName =
DN_ItemDispenser_BaggingArea_PortalScanner_X7)
Keylock:
•iButton USB (FTDI) (JavaPOS logicalName = DN_Keylock_Olitronic_iButton_USB)
•iButton RS232 (JavaPOS logicalName = DN_Keylock_iButton_COM)
•iButton iPos+ (JavaPOS logicalName = DN_Keylock_iPOSPlus_iButton)
•WaiterKeylock vi PS2 Keyboard (JavaPOS logicalName =
DN_Keylock_POSKeyboard_WKL_PS2_Systemhook)
LineDisplay:
•LineDisplay via ND77 (JavaPOS logicalName = DN_LineDisplay_BA63_POSPrinter_ND77,
DN_LineDisplay_BA66_POSPrinter_ND77)
•LineDisplay via ND210 (JavaPOS logicalName = DN_LineDisplay_BA63_POSPrinter_ND210,
DN_LineDisplay_BA66_POSPrinter_ND210)
•LineDisplay via FFC-TH230 IT (JavaPOS logicalName =
DN_LineDisplay_BA63_FiscalPrinter_IT_FFCTH230_COM,
DN_LineDisplay_BA63_FiscalPrinter_IT_FFCTH230_USB,
DN_LineDisplay_BA66_FiscalPrinter_IT_FFCTH230_COM,
DN_LineDisplay_BA66_FiscalPrinter_IT_FFCTH230_USB)
•LineDisplay iPos+ (JavaPOS logicalName = DN_LineDisplay_iPOSPlus_COM)
MotionSensor:
•MotionSensor RS232 (JavaPOS logicalName = DN_MotionSensor_COM)
MSR:
Migration Guide
Diebold Nixdorf Public Use 8
•MSR ICM330 USB (JavaPOS logicalName = DN_MSR_ICM330_USB)
•MSR iPos+ (JavaPOS logicalName = DN_MSR_iPOSPlus)
POSPrinter:
•ND77 (JavaPOS logicalName = DN_POSPrinter_ND77_COM)
•ND210 (JavaPOS logicalName = DN_POSPrinter_ND210_COM, DN_POSPrinter_ND210_Asia_COM)
Scale:
•Mettler VIVA pipe (JavaPOS logicalName = DN_Scale_CODialog06_Mettler_Viva_PIPE)
•Bizerba CS315KF USB via CheckoutDialog 11 (JavaPOS logicalName =
DN_Scale_CODialog11_Bizerba_CS315KF_USB)
Scanner:
•PortalScanner (JavaPOS logicalName = DN_Scanner_PortalScanner_X7)
ToneIndicator:
•SEL V4 (JavaPOS logicalName = DN_SEL_V4_USB)
•SEL V4 MotorElectronic (JavaPOS logicalName = DN_SEL_MotorElectronic)
•SEL PoleLight LEDStatusBox COM (JavaPOS logicalName =
DN_SEL_PoleLight_LEDStatusBox_COM)
•SEL PoleLight RG COM (JavaPOS logicalName = DN_SEL_PoleLight_RG_COM)
NOTE In case any of the devices listed here is still in use in your project, please go in
contact with your Diebold Nixdorf representative.
4.6. Removed Logical Name Configurations
Comparing to ProBase Store 1.7 release the following logicalName’s in the JavaPOS configuration
file templates has been removed. This possibly implies a need to change the application vendor
provided JavaPOS Configurator input properties as they directly reference dedicated logicalName’s.
The related hardware either has reached end of life and is not supported anymore, or there is an
alternative available that is to be referenced instead. This alternative may be just a renamed
logicalName configuration, but it may be also an alternative implementation.
See also JavaPOS Configurator documentation [JPOSCFG].
Belt:
•DN_Belt_DEV1_PortalScanner_X7 → not supported anymore
•DN_Belt_DEV2_PortalScanner_X7 → not supported anymore
•DN_Belt_DEV3_PortalScanner_X7 → not supported anymore
CashChanger:
•DN_CashChanger_iCash50 → not supported anymore
•DN_CashChanger_iCash100 → not supported anymore
Migration Guide
Diebold Nixdorf Public Use 9
CashDrawer:
•DN_CashDrawer_BeetleSystem_DEV1 → replaced by DN_CashDrawer_BeetleSystem
•DN_CashDrawer_BeetleSystem_DEV2 → replaced by DN_CashDrawer_BeetleSystem
•DN_CashDrawer_DEV1_POSPrinter_ND77_COM → not supported anymore
•DN_CashDrawer_DEV2_POSPrinter_ND77_COM → not supported anymore
•DN_CashDrawer_DEV1_POSPrinter_ND210_COM → not supported anymore
•DN_CashDrawer_DEV2_POSPrinter_ND210_COM → not supported anymore
•DN_CashDrawer_DEV1_POSPrinter_TH200_COM → replaced by
DN_CashDrawer_POSPrinter_TH200_COM
•DN_CashDrawer_DEV2_POSPrinter_TH200_COM → replaced by
DN_CashDrawer_POSPrinter_TH200_COM
•DN_CashDrawer_DEV1_POSPrinter_TH200_PARPORT → replaced by
DN_CashDrawer_POSPrinter_TH200_PARPORT
•DN_CashDrawer_DEV2_POSPrinter_TH200_PARPORT → replaced by
DN_CashDrawer_POSPrinter_TH200_PARPORT
•DN_CashDrawer_DEV1_POSPrinter_TH200_USB → replaced by
DN_CashDrawer_POSPrinter_TH200_USB
•DN_CashDrawer_DEV2_POSPrinter_TH200_USB → replaced by
DN_CashDrawer_POSPrinter_TH200_USB
•DN_CashDrawer_DEV1_POSPrinter_TH210_COM → replaced by
DN_CashDrawer_POSPrinter_TH210_COM
•DN_CashDrawer_DEV2_POSPrinter_TH210_COM → replaced by
DN_CashDrawer_POSPrinter_TH210_COM
•DN_CashDrawer_DEV1_POSPrinter_TH210_USB → replaced by
DN_CashDrawer_POSPrinter_TH210_USB
•DN_CashDrawer_DEV2_POSPrinter_TH210_USB → replaced by
DN_CashDrawer_POSPrinter_TH210_USB
•DN_CashDrawer_DEV1_POSPrinter_TH230_Asia_COM → replaced by
DN_CashDrawer_POSPrinter_TH230_Asia_COM
•DN_CashDrawer_DEV2_POSPrinter_TH230_Asia_COM → replaced by
DN_CashDrawer_POSPrinter_TH230_Asia_COM
•DN_CashDrawer_DEV1_POSPrinter_TH230_Asia_USB → replaced by
DN_CashDrawer_POSPrinter_TH230_Asia_USB
•DN_CashDrawer_DEV2_POSPrinter_TH230_Asia_USB → replaced by
DN_CashDrawer_POSPrinter_TH230_Asia_USB
•DN_CashDrawer_DEV1_POSPrinter_TH230_COM → replaced by
DN_CashDrawer_POSPrinter_TH230_COM
•DN_CashDrawer_DEV2_POSPrinter_TH230_COM → replaced by
DN_CashDrawer_POSPrinter_TH230_COM
Migration Guide
Diebold Nixdorf Public Use 10
•DN_CashDrawer_DEV1_POSPrinter_TH230_USB → replaced by
DN_CashDrawer_POSPrinter_TH230_USB
•DN_CashDrawer_DEV2_POSPrinter_TH230_USB → replaced by
DN_CashDrawer_POSPrinter_TH230_USB
•DN_CashDrawer_DEV1_POSPrinter_TH250_COM → replaced by
DN_CashDrawer_POSPrinter_TH250_COM
•DN_CashDrawer_DEV2_POSPrinter_TH250_COM → replaced by
DN_CashDrawer_POSPrinter_TH250_COM
•DN_CashDrawer_DEV1_POSPrinter_TH250_USB → replaced by
DN_CashDrawer_POSPrinter_TH250_USB
•DN_CashDrawer_DEV2_POSPrinter_TH250_USB → replaced by
DN_CashDrawer_POSPrinter_TH250_USB
•DN_CashDrawer_DEV1_POSPrinter_TH250_LAN → not supported anymore
•DN_CashDrawer_DEV2_POSPrinter_TH250_LAN → not supported anymore
•DN_CashDrawer_DEV1_POSPrinter_TH320_COM → replaced by
DN_CashDrawer_POSPrinter_TH320_COM
•DN_CashDrawer_DEV2_POSPrinter_TH320_COM → replaced by
DN_CashDrawer_POSPrinter_TH320_COM
•DN_CashDrawer_DEV1_POSPrinter_TH320_USB → replaced by
DN_CashDrawer_POSPrinter_TH320_USB
•DN_CashDrawer_DEV2_POSPrinter_TH320_USB → replaced by
DN_CashDrawer_POSPrinter_TH320_USB
•DN_CashDrawer_DEV1_POSPrinter_TH420_COM → replaced by
DN_CashDrawer_POSPrinter_TH420_COM
•DN_CashDrawer_DEV2_POSPrinter_TH420_COM → replaced by
DN_CashDrawer_POSPrinter_TH420_COM
•DN_CashDrawer_DEV1_POSPrinter_TH420_USB → replaced by
DN_CashDrawer_POSPrinter_TH420_USB
•DN_CashDrawer_DEV2_POSPrinter_TH420_USB → replaced by
DN_CashDrawer_POSPrinter_TH420_USB
•DN_CashDrawer_FiscalPrinter_IT_FFCTH230_COM → not supported anymore
•DN_CashDrawer_FiscalPrinter_IT_FFCTH230_USB → not supported anymore
•DN_CashDrawer_IOHub_ASeries_DEV1 → replaced by DN_CashDrawer_IOHub_ASeries
•DN_CashDrawer_IOHub_ASeries_DEV2 → replaced by DN_CashDrawer_IOHub_ASeries
•DN_CashDrawer_ModularPOS_DEV1 → replaced by DN_CashDrawer_BeetleSystem
•DN_CashDrawer_ModularPOS_DEV2 → replaced by DN_CashDrawer_BeetleSystem
•DN_CashDrawer_POSPrinter_ND210_Asia_COM → not supported anymore
•DN_CashDrawer_POSPrinter_TH250-II_COM → replaced by
DN_CashDrawer_POSPrinter_TH250_COM
Migration Guide
Diebold Nixdorf Public Use 11
•DN_CashDrawer_POSPrinter_TH250-II_USB → replaced by
DN_CashDrawer_POSPrinter_TH250_USB
•DN_CashDrawer_SMBus_DEV1 → replaced by DN_CashDrawer_BeetleSystem
•DN_CashDrawer_SMBus_DEV2 → replaced by DN_CashDrawer_BeetleSystem
FiscalPrinter:
•DN_FiscalPrinter_IT_FFCTH230_COM → not supported anymore
•DN_FiscalPrinter_IT_FFCTH230_USB → not supported anymore
HardTotals:
•DN_HardTotals_Disk → not supported anymore
ItemDispenser:
•DN_ItemDispenser_BaggingArea_PortalScanner_X7 → not supported anymore
Keylock:
•DN_Keylock_Olitronic_iButton_USB → not supported anymore
•DN_Keylock_POSKeyboard_PS2_Processhook → replaced by DN_Keylock_POSKeyboard_PS2
•DN_Keylock_POSKeyboard_PS2_Systemhook → replaced by DN_Keylock_POSKeyboard_PS2
•DN_Keylock_POSKeyboard_USB_Processhook → replaced by DN_Keylock_POSKeyboard_USB
•DN_Keylock_POSKeyboard_WKL_PS2_Systemhook → not supported anymore
•DN_Keylock_iButton_COM → not supported anymore
•DN_Keylock_iPOSPlus_iButton → not supported anymore
LineDisplay:
•DN_LineDisplay_BA63_FiscalPrinter_IT_FFCTH230_COM → not supported anymore
•DN_LineDisplay_BA63_FiscalPrinter_IT_FFCTH230_USB → not supported anymore
•DN_LineDisplay_BA63_POSPrinter_ND210 → not supported anymore
•DN_LineDisplay_BA63_POSPrinter_ND77 → not supported anymore
•DN_LineDisplay_BA64-2_USB_DEV1 → replaced by DN_LineDisplay_BA64-2_USB
•DN_LineDisplay_BA64-2_USB_DEV2 → replaced by DN_LineDisplay_BA64-2_USB
•DN_LineDisplay_BA66_FiscalPrinter_IT_FFCTH230_COM → not supported anymore
•DN_LineDisplay_BA66_FiscalPrinter_IT_FFCTH230_USB → not supported anymore
•DN_LineDisplay_BA66_POSPrinter_ND210 → not supported anymore
•DN_LineDisplay_BA66_POSPrinter_ND77 → not supported anymore
•DN_LineDisplay_iPOSPlus_COM → not supported anymore
MotionSensor:
•DN_MotionSensor_COM → not supported anymore
MSR:
Migration Guide
Diebold Nixdorf Public Use 12
•DN_MSR_ICM330_USB → not supported anymore
•DN_MSR_POSKeyboard_PS2_Processhook → replaced by DN_MSR_POSKeyboard_PS2
•DN_MSR_POSKeyboard_PS2_Systemhook → replaced by DN_MSR_POSKeyboard_PS2
•DN_MSR_POSKeyboard_USB_Processhook → replaced by DN_MSR_POSKeyboard_USB
•DN_MSR_iPOSPlus → not supported anymore
POSKeyboard:
•DN_POSKeyboard_PS2_Processhook → replaced by DN_POSKeyboard_PS2
•DN_POSKeyboard_PS2_Systemhook → replaced by DN_POSKeyboard_PS2
•DN_POSKeyboard_USB_Processhook → replaced by DN_POSKeyboard_USB
•DN_POSKeyboard_USB_Systemhook → replaced by DN_POSKeyboard_USB
POSPrinter:
•DN_POSPrinter_ND210_Asia_COM → not supported anymore
•DN_POSPrinter_ND210_COM → not supported anymore
•DN_POSPrinter_ND77_COM → not supported anymore
•DN_POSPrinter_TH250-II_COM → replaced by DN_POSPrinter_TH250_COM
•DN_POSPrinter_TH250-II_USB → replaced by DN_POSPrinter_TH250_USB
•DN_POSPrinter_TH250_LAN → not supported anymore
•DN_POSPrinter_TH250_TSOP → replaced by DN_POSPrinter_TH250_USB
Scale:
•DN_Scale_CODialog06_Mettler_Viva_PIPE → not supported anymore
•DN_Scale_CODialog11_Bizerba_CS315KF_USB → not supported anymore
•DN_Scale_Mettler_Spider_SW → replaced by DN_Scale_MTSICS_SecurityScale_COM
•DN_Scale_ZEBRA_MP7001_OEMHID_JNA_USB → replaced by
DN_Scale_ZEBRA_MP7001_OEMHID_USB
Scanner:
•DN_Scanner_EL64_Datalogic_Magellan_9800i_EFC_USB → replaced by
DN_Scanner_EL64_Datalogic_Magellan_9800i_USB
•DN_Scanner_EL67_Datalogic_QuickScan_QD2430_EFC_USB → replaced by
DN_Scanner_EL67_Datalogic_QuickScan_QD2430_USB
•DN_Scanner_EL69_Datalogic_Magellan_9300i_EFC_USB → replaced by
DN_Scanner_EL69_Datalogic_Magellan_9300i_USB
•DN_Scanner_EL70_Datalogic_Magellan_9400i_EFC_USB → replaced by
DN_Scanner_EL70_Datalogic_Magellan_9400i_USB
•DN_Scanner_EL75_ZEBRA_MP7000_EFC_USB → replaced by
DN_Scanner_EL75_ZEBRA_MP7000_USB
•DN_Scanner_EL76_DATALOGIC_Magellan_3400_EFC_USB → replaced by
Migration Guide
Diebold Nixdorf Public Use 13
DN_Scanner_EL76_DATALOGIC_Magellan_3400_USB
•DN_Scanner_EL80_Datalogic_Gryphon_GD4590_EFC_USB → replaced by
DN_Scanner_EL80_Datalogic_Gryphon_GD4590_USB
•DN_Scanner_EL81_ZEBRA_DS4608_EFC_USB → replaced by
DN_Scanner_EL81_ZEBRA_DS4608_USB
•DN_Scanner_Generic_HandHeld_EFC_USB → replaced by DN_Scanner_Generic_HandHeld_USB
•DN_Scanner_Generic_HandHeld_JNA_USB → replaced by DN_Scanner_Generic_HandHeld_USB
•DN_Scanner_Generic_TableTop_EFC_USB → replaced by DN_Scanner_Generic_TableTop_USB
•DN_Scanner_Generic_TableTop_JNA_USB → replaced by DN_Scanner_Generic_TableTop_USB
•DN_Scanner_PortalScanner_X7 → not supported anymore
•DN_Scanner_S1210_ZEBRA_MS4717_EFC_USB → replaced by
DN_Scanner_S1210_ZEBRA_MS4717_USB
ToneIndicator:
•DN_ToneIndicator_POSPrinter_TH250-II_COM → replaced by
DN_ToneIndicator_POSPrinter_TH250_COM
•DN_ToneIndicator_POSPrinter_TH250-II_USB → replaced by
DN_ToneIndicator_POSPrinter_TH250_USB
•DN_ToneIndicator_POSPrinter_TH250_LAN → not supported anymore
•DN_SEL_MotorElectronic → not supported anymore
•DN_SEL_PoleLight_LEDStatusBox_COM → not supported anymore
•DN_SEL_PoleLight_RG_COM → not supported anymore
•DN_SEL_V4_USB → not supported anymore
4.7. Changes To Configuration Concepts
There is no general change in any of ProBase Store’s configuration concepts but some configuration
files and their properties were renamed or relocated.
4.7.1. Logger Configuration
The JavaPOS Logger component has been renamed and its configuration file was renamed from
wn-logger.properties to dn-logger.properties.
Configuration keys with name prefix 'wn' were renamed and the prefix was replaced by 'dn'.
On Linux the location of the logger configuration file has been changed to /opt/dn/javapos/config/.
4.7.2. CIMAdapter Configuration
The JavaPOS CIMAdapter configuration files has been renamed from
com.wn.rdbd.dmi.JavaCIMAdapter.properties to com.dn.retail.cim.properties. On Linux the location
of the configuration file has been changed to /opt/dn/javapos/config/.
Migration Guide
Diebold Nixdorf Public Use 14
4.7.3. JavaPOS Configuration Files
The JavaPOS configuration file name schema as introduced in ProBase Store 1 is still valid. But
single open name configurations has been moved into different JavaPOS configuration file
templates to follow this approach more consequently.
Note that open names and related open name configurations has been changed. Therefore the
application specific JavaPOS Configurator properties as provided by application vendors must be
reviewed to still point to available devices devices. Furthermore, it must be validated that
configuration keys names referenced still exist and have valid values.
E.g. the configuration key getDmiInfo has been replaced by cimConnectorEnabled.
The best way to achieve validation of actual JavaPOS Configurator properties is by running the DN
JavaPOS Configurator and examine the log file
%ProgramData%\javapos\dn\log\generate_javapos_configuration.bat.log respectively
/var/log/dn/javapos/generate_javapos_configuration.sh.log looking out for warnings and errors.
The actually available configuration key names and their values are documented in related device
service documentations.
See also JavaPOS Configurator Documentation [JPOSCFG] for details.
NOTE
New naming conventions were applied to class names as well. So any class that is
being addressed in any kind of configuration file may be affected. This especially
applies to factory classes, service classes, dcal classes, and others as mentioned in
JavaPOS open name configurations.
NOTE In case of any problem that is observed after migration for one of the devices as
listed above, please go in contact with your Diebold Nixdorf representative.
Migration Guide
Diebold Nixdorf Public Use 15
Chapter 5. Upgrading Procedure from
ProBase Store 1.X
This document does not describe an upgrade of a system running ProBase Retail or ProBase POS.
Refer to ProBase Store 1.X Migration Guide [MG] if this is intended.
In case T/SOP Retail is to be installed as well refer to T/SOP Retail Migration Guide [TR1MG] as this
document does not fully cover T/SOP retail related aspects.
The subsequent sections describe the steps required and recommended when upgrading a system
running ProBase Store 1.X. The migration is quite easy and contains the following steps. Note there
is no direct update installation possible and former ProBase Store release has to be uninstalled
during the procedure described below.
1. Backup Configuration Files and Runtime Data
The current ProBase Store configuration files and runtime data should be preserved for a later
inspection. The simplest way to preserve all configuration files is to copy all files under
•C:\%ProgramFiles%\javapos\ProBase-Store\config,
•C:\%ProgramData%\javapos,
•C:\%ProgramData%\Diebold Nixdorf\JDD, and
•C:\%ProgramData%\Diebold Nixdorf\RSS
resp.
•/etc/opt/wn/javapos/config/,
•/etc/opt/javapos,
•/etc/opt/dn/jdd
•/var/log/dn/javapos/,
•/var/opt/dn/, and
•/var/opt/wn/
to a location that does not interfere with ProBase Store 2 installation locations.
2. Uninstall ProBase Store 1.X
Uninstall ProBase Store 1.X as described in ProBase Store 1 Installation Guides [IG-Lin] and [IG-
Win].
3. Uninstall Conflicting Software Packages
If installed, also uninstall ProBase Store related software packages. This is required as there are
potential conflicts, especially on Linux, caused by introduction of group dndev and by modified
permissions.
•ProBase POS
Migration Guide
Diebold Nixdorf Public Use 16
•ProBase Retail
•Loadutil ⇐ 3.6. (applies to Linux only)
4. Cleanup
After uninstallation of ProBase Store 1.X some artifacts in the ProBase Store 2 installation folder
may still exist and it is recommended to remove those files manually as it is not guaranteed they
will not interfere with consecutive installations. This usually applies to data or log files created
during runtime, file that were modified after installation, or that has been copied manually into
these locations.
4.1. Cleanup Windows
•if exists, delete C:\%ProgramFiles%\javapos\ProBase-Store
•if exists, delete C:\%ProgramFiles(x86)%\javapos\ProBase-Store
•if exists, delete C:\%ProgramFiles(x86)%\Diebold Nixdorf\Diagserv
•if exists, delete C:\%ProgramFiles%\Diebold Nixdorf\Diagserv
•if exists, delete C:\%ProgramData%\Diebold Nixdorf\RSS\diagserv
4.2. Cleanup Linux
•if exists, delete /opt/dn/diagserv
•if exists, delete /var/log/dn/diagserv
5. Install ProBase Store 2
Run the ProBase Store 2 installer as described in ProBase Store 2 User Manual [PBS2UM].
6. Install or Update Related Products
If needed install further ProBase Store related products, such as:
•T/SOP Retail
•Loadutil ( version >= 4.0 )
Additionally if already installed also update the following products as they have indirect
dependencies to ProBase Store 2:
•ProBase STM >= 2.2
•DNUT Recorder
•Harvester Retail
7. Configure ProBase Store 2
Configure ProBase Store 2 as needed.
7.1. Review JavaPOS Configuration Inputs
If relevant, application vendors (VSS, VC, and others) need to review their provided JavaPOS
Configurator Input Properties. As logicalNames has been removed or renamed, and as the set of
configuration key names and their valid values potentially has been changed, it is important to do a
review in order to validate the JavaPOS Configurator generated JavaPOS Configuration for the
Migration Guide
Diebold Nixdorf Public Use 17
vendor’s application still will be correct.
If needed, adapt the template open names in related javapos.config.properties files to the new ones.
The mapping list of old to new template open names can be found in section Removed Logical
Name Configurations.
8. Run JavaPOS Configurator
Run the JavaPOS Configurator from the ProBase Store’s Windows start menu (entry
Configuration→Generate JavaPOS configuration) and check your application configuration at the
ProBase Store’s Windows start menu entry "Configured Devices", a HTML browser with a table of
configured open names will open.
Examine the log file %ProgramData%\javapos\dn\log\generate_javapos_configuration.bat.log
respectively /var/log/dn/javapos/generate_javapos_configuration.sh.log and look out for warnings
and errors.
9. Recover User Data
During uninstallation and system cleanup persisted data got lost. That is also the case for cash
changer counter that are stored on hard disc. There are two options to recover these counter:
Either do full stock check (empty and refill), or recover the persisted counter by using that backed
up files.
9.1. CM3SR (coin recycler component of C1030)
•merge C:\%ProgramData%\Diebold
Nixdorf\RSS\CM3SRCoinEngine\data.coin_engine\HopperLevel.properties
•merge C:\%ProgramData%\Diebold
Nixdorf\RSS\CM3SRCoinEngine\data.coin_engine\backup\HopperLevel.properties
•merge C:\%ProgramData%\Diebold
Nixdorf\RSS\CM3SRCoinEngine\data.coin_engine\OverFlowBox.properties
•merge C:\%ProgramData%\Diebold
Nixdorf\RSS\CM3SRCoinEngine\data.coin_engine\backup\OverFlowBox.properties
9.2. iCash40 (note recycler)
During runtime a C:\%ProgramData%\Diebold
Nixdorf\JDD\JCMID003\jddjcmid003.counter.<SerialNumber>.properties is being created that persists
the iCash40 CollectBox counter. Just copy related backed up file(s)
jddjcmid003.counter.<SerialNumber>.properties file(s) into C:\%ProgramData%\Diebold
Nixdorf\JDD\JCMID003\ to restore the previous counter.
9.3. iCash65 (coin recycler)
During runtime a C:\%ProgramData%\Diebold
Nixdorf\JDD\ICASH65\jddCrv.counter.sn<SerialNumber>.properties is being created that persists the
iCash65 CollectBox counter. Just copy related backed up file(s)
jddCrv.counter.sn<SerialNumber>.properties file(s) into C:\%ProgramData%\Diebold
Nixdorf\JDD\ICASH65\ to restore the previous counter.
10. Add user to group dndev
If non-root user is intended to operate ProBase Store, let it join group dndev.
Migration Guide
Diebold Nixdorf Public Use 18
Page is loading ...
Page is loading ...
/