| Oracle® Retail Point-of-Service Installation Guide Release 14.1 E54459-01 |
|
 Previous |
 Next |
This chapter describes the requirements that must be met before Oracle Retail Point-of-Service can be installed.
|
Note: These are the configurations that were tested for this release. While Point-of-Service may work in other configurations, these configurations were tested. |
If you are installing multiple Oracle Retail applications, see Appendix I for a guideline for the order in which the applications should be installed.
If you are unable to find the necessary version of the required Oracle infrastructure software (database server, application server, WebLogic, and so on) on the Oracle Software Delivery Cloud, you should file a non-technical 'Contact Us' Service Request (SR) and request access to the media. For instructions on filing a non-technical SR, see My Oracle Support Note 1071023.1 - Requesting Physical Shipment or Download URL for Software Media.
Table 1-1 lists the general requirements for a database server running Oracle Retail Point-of-Service and the versions supported for this release.
Table 1-1 Database Server Requirements
| Supported on | Stack 1 | Stack 2 |
|---|---|---|
|
Operating System |
Microsoft Windows 2012 Server R2 Standard Edition (64-bit) |
Novell SLEPOS11 SP3 (64-bit) |
|
Database |
Oracle Database 12c Standard Edition 12.1.0.1 (64-bit) Note: Oracle Retail Point-of-Service is not certified with Real Application Clusters (RAC). |
Oracle Database 12c Standard Edition 12.1.0.1.4 (64-bit) Patches:
Oneoff:
Note: Oracle Retail Point-of-Service is not certified with Real Application Clusters (RAC). |
|
Note: It is recommended that separate tablespaces are used for tables and indexes. This may improve performance when accessing the database. |
Table 1-2 lists the general requirements for a store server capable of running Point-of-Service and the versions supported for this release.
Table 1-3 and Table 1-4 list the general requirements for a client capable of running Point-of-Service and the versions supported for this release. A computer mouse is not supported for Point-of-Service. A touch screen may be used, but a keyboard is required for some functions. The configuration tested for this release included touch screens.
|
Note: It is the responsibility of the retailer to select peripheral devices that support the languages the retailer is using. |
Table 1-3 Client Requirements for Stack 1
| Supported on | |||
|---|---|---|---|
|
Register |
NCR 82XRT |
Toshiba TcxWave 6140-E10 |
Dell Venue 11 Pro Tablet |
|
Operating System |
Microsoft Windows Embedded POSReady 7 (32-bit) |
Microsoft Windows Embedded POSReady 7 (32-bit) |
Microsoft Windows 8.1 Mobile (32-bit) |
|
JVM |
Oracle Java 7 JRE or later within the Java 7 code line (32-bit) |
IBM Java 1.7 JRE or later within the Java 1.7 code line (32-bit) |
Oracle Java 7 JRE or later within the Java 7 code line (32-bit) |
|
Persistent Storage |
Apache Derby 10.10.1.1 |
Apache Derby 10.10.1.1 |
Apache Derby 10.10.1.1 |
|
Cash drawer |
NCR 2181 |
4510 Wide Cash Drawer |
APG Cash Drawer |
|
Pole Display |
NCR 2X20 |
IBM PN 96Y4948 |
NA |
|
Keyboard |
NCR Keyboard (compact) |
IBM 93Y1251 |
Dell Keyboard |
|
Scanner |
NCR 9208 |
Symbol Scanner LS4208 |
Symbol Scanner LS4208 |
|
Payment Device (ACI) |
Verifone MX915 |
Verifone MX880 |
Verifone MX915 |
|
Payment Device (AJB) |
Verifone MX915 |
NA |
NA |
|
Payment Locale |
Europay, MasterCard, and Visa (EMV) and non-EMV |
EMV and non-EMV |
non-EMV |
|
Receipt Printer |
NCR Printer (Two-sided thermal printers with form input) |
IBM 4610-2CR Thermal/Impact |
Epson TMH 60000IV |
|
Biometric Device |
Digital Persona U are U 4500 Fingerprint READER v 2.02 |
Included |
NA |
Table 1-4 Client Requirements for Stack 2
| Supported on | |
|---|---|
|
Register |
IBM SurePOS 700 (742/743) |
|
Operating System |
Novell SLEPOS11 SP3 (32-bit) |
|
JVM |
IBM Java 1.7 JRE or later within the Java 1.7 code line (32-bit) |
|
Persistent Storage |
Apache Derby 10.10.1.1 |
|
Cash drawer |
IBM Cash Drawer |
|
Pole Display |
IBM Pole Display |
|
Keyboard |
IBM Keyboard |
|
Scanner |
Symbol Scanner LS2208 and LS4209 |
|
Payment Device (ACI) |
Verifone MX915 and MX880 |
|
Payment Locale |
non-EMV |
|
Receipt Printer |
IBM Printer |
|
Biometric Device |
Digital Persona U are U 4500 Fingerprint READER v 2.02 |
Registers that support a DigitalPersona fingerprint device require the installation of DigitalPersona Windows SDK (uareusdk220.zip).
The installer should be included with your fingerprint readers or can be downloaded from the following web site:
http://www.digitalpersona.com/oracle/biometrics/
After the installation is complete, use the Windows Device Manager to verify that you see the device.
You must update the PATH environment variable to include the pointers to the dynamic link library (dll) files. Following are examples of how to set the PATH variable:
Microsoft Windows:
SET FP_PATH=C:\DigitalPersona\Bin;C:\DigitalPersona\Bin\Java SET PATH=%FP_PATH%;%PATH%
Novell SLEPOS:
FP_PATH=/opt/DigitalPersona/Bin:/opt/DigitalPersona/Bin/Java PATH=$FP_PATH:$PATH; export PATH
Table 1-5 lists the general requirements for the Mobile Point-of-Service server capable of running Mobile Point-of-Service and the versions supported for this release.
Table 1-5 Mobile Point-of-Service Server Requirements
| Supported on | Stack 1 | Stack 2 |
|---|---|---|
|
Operating System |
Microsoft Windows 2012 Server R2 Standard Edition (64-bit) |
Novell SLEPOS11 SP3 (64-bit) |
|
J2EE Application Server |
Oracle WebLogic 10.3.6.0 Standard Edition (32-bit) Note: To install Oracle WebLogic with the supported version, use the Oracle WebLogic generic installer. For more information, see the Oracle WebLogic installation documentation. |
Oracle WebLogic 10.3.6.0 Standard Edition (32-bit) Note: To install Oracle WebLogic with the supported version, use the Oracle WebLogic generic installer. For more information, see the Oracle WebLogic installation documentation. |
|
J2EE Application Server JVM |
Oracle Java 7 or later within the Java 7 code line |
Oracle Java 7 or later within the Java 7 code line |
|
Messaging Provider |
included in Oracle WebLogic Server (32-bit) |
included in Oracle WebLogic Server (32-bit) |
Table 1-6 lists the general requirements for mobile devices capable of running Mobile Point-of-Service and the versions supported for this release. The devices are supported on both stacks.
Table 1-6 Mobile Point-of-Service Device Requirements
| Supported on | Stack 1 and 2 | |||
|---|---|---|---|---|
|
Device |
Apple iPod Touch (5th Generation) |
Apple iPad mini (2nd Generation) |
Motorola MC 40 |
Motorola Tablet (ET1) |
|
Operating System |
Apple iOS 8.1 |
Apple iOS 8.1 |
Android 4.1.1 |
Android 4.1.1 |
|
Sled Note: Mobile Point-of-Service can be run without a sled, but this is not suitable for a production environment. |
Verifone PAYware Mobile e315 |
Verifone PAYware Mobile e335 |
Built-in; for scanning only |
Built-in; for scanning only |
|
Payment Device (ACI) |
NA |
NA |
Verifone MX915 and MX880 Equinox L5300 |
Verifone MX915 and MX880 Equinox L5300 |
|
Payment Device (AJB) |
Verifone MX915 |
Verifone MX915 |
NA |
NA |
|
Payment Locale |
EMV and non-EMV |
EMV and non-EMV |
non-EMV |
non-EMV |
|
Network Printer |
Programmable Logical Control System (PLCS) and Postscript - Epson TM-T88v |
PLCS and Postscript - Epson TM-T88v |
PLCS and Postscript - Epson TM-P60 |
PLCS and Postscript - Epson TM-T88v |
The Mobile Point-of-Service server is accessed through a secure HTTP connection. The installation of an SSL Certificate is required on your WebLogic Server. If the certificate is not installed, Mobile Point-of-Service will not work.
For information on installing the SSL Certificate, refer to your Oracle WebLogic Server documentation.
Table 1-7 lists the Oracle Retail products that are supported.
Table 1-7 Supported Oracle Retail Products
| Integrates with | Version |
|---|---|
|
Oracle Retail Back Office |
14.1 |
|
Oracle Retail Central Office |
14.1 |
|
Oracle Retail Merchandising System |
14.1 |
|
Oracle Retail Price Management |
14.1 |
|
Oracle Retail Returns Management |
14.1 |
|
Oracle Retail Sales Audit |
14.1 |
|
Oracle Retail Store Inventory Management |
14.1 (on Oracle WebLogic Server) |
Table 1-8 lists the Oracle technologies used by Oracle Retail Point-of-Service and the required versions.
If you are using the RSA Data Protection Manager, you must use version 3.5.2.2.
Oracle Retail Point-of-Service requires that a Java Key Manager system is available prior to installation. Specific information for configuring the Key Manager is entered on the Security Setup: Key Manager installer windows.
If you are using the RSA Data Protection Manager, you must obtain specific jar files, obtain the lockbox files for the operating system you are using, and install the Java Cryptography Extension Unlimited Strength Jurisdiction Policy Files 7.0. For Microsoft Windows, see "Obtain the Files Needed for the RSA Data Protection Manager" in Chapter 3. For Novell SLEPOS, see "Obtain the Files Needed for the RSA Data Protection Manager" in Chapter 4.
|
Note: If you are using the simulator key manager, a pass phrase is used to access the Key Manager simulator. The pass phrase is entered in the Key Store Pass Phrase installer window.Use the same pass phrase for all Oracle Retail POS Suite applications in your configuration. |
|
Caution: A simulated key management package is bundled with Oracle Retail Point-of-Service. It is not compliant with either the Payment Application Data Security Standard (PA-DSS) or Payment Card Industry Data Security Standard (PCI-DSS). It is made available as a convenience for retailers and integrators. If you use the simulated key manager, you will not be PCI-DSS compliant. Therefore, the simulated key manager should be replaced with a compliant key manager. |
For information on enabling secure JDBC and RMI on Microsoft Windows, see "Secure Communication" in Chapter 3. For Novell SLEPOS, see "Secure Communication"in Chapter 4.
The hardware requirements for the store server and client depend on different variables.
You need to determine your hardware requirements, based on the variables mentioned here, as well as any additional variables specific to your environment.
Specific hardware requirements for the machines running the Oracle Retail Point-of-Service store server depend on variables including the number of users and other applications running on the same machine.
Please note the following about the hardware requirements:
The CPU requirement depends on variables including the number of Point-of-Service clients and the operating system and middleware selected.
Memory requirements and performance depend on variables including the number of active promotions and best deal calculations.
Disk size can vary based on the operating system and middleware requirements as well as the amount of data storage needed. Data storage depends on variables including the number of items and promotions defined, data retention period, and so on.
Specific hardware requirements for the machines running the Oracle Retail Point-of-Service client depend upon the point-of-sale system/register manufacturer and other applications and utilities running on the client.
JavaPOS is the industry standard for Java compatibility for retail-oriented devices. A committee of prominent retail vendors and end users maintains the standard. Some of the more common devices used with point-of-sale applications include bar code scanners, cash drawers, printers, keyboards, magnetic stripe readers (MSR), wedge keyboards, hard totals, and magnetic ink check readers (MICR). Any JavaPOS-compliant peripheral devices should work with Oracle Retail Point-of-Service, however, some may require software modifications to work properly.
Tender authorization testing was done with ACI PINComm and AJB,. For each payment application, the version used for the testing and the transaction types and messages that were tested are listed below.
For testing done for Mobile Point-of-Service, see "Tender Authorization Testing for Mobile Point-of-Service".
The following ACI versions were used for testing:
PINComm 6.5.0.006 and toolkit 346 (IMSRTRIBSpecSDK-346.jar)
SAF/TOR 6.5.0.010 and toolkit 346 (IMSRTRIBSpecSDK-346.jar)
Table 1-9 shows the transaction types and messages that were tested.
Table 1-9 ACI PINComm Authorization Set Tested with Point-of-Service
| Transaction Type | Transaction Type Message Sent from ACI PINComm to Point-of-Service |
|---|---|
|
Check Tender |
|
|
Credit Card Tender |
|
|
Debit Card Tender |
|
|
Gift Card Issue |
|
|
Gift Card Redeem |
|
|
Gift Card Refund Issue new gift card or reload to existing gift card |
|
|
Gift Card Reload |
|
|
Gift Card Tender |
|
|
House Account Tender |
|
The AJB Fipay software version used for testing was 19444.
Table 1-10 shows the transaction types and messages that were tested.
Table 1-10 AJB Authorization Set Tested with Point-of-Service
| Transaction Type | Transaction Type Message Sent from AJB to Point-of-Service |
|---|---|
|
Check Tender |
|
|
Credit Card Tender |
|
|
Debit Card Tender |
|
|
Gift Card Issue |
|
|
Gift Card Redeem |
|
|
Gift Card Refund Issue new gift card or reload to existing gift card |
|
|
Gift Card Reload |
|
|
Gift Card Tender |
|
|
House Account Inquiry, Temporary Pass, Payment |
|
|
House Account Tender |
|
Tender authorization testing was done with ACI PINComm and AJB. For each payment application, the version used for the testing and the transaction types and messages that were tested are listed below.
|
Note: Testing with ACI PINComm was done only with the Motorola mobile devices. |
The following ACI versions were used for testing:
PINComm 6.5.0.006 and toolkit 346 (IMSRTRIBSpecSDK-346.jar)
SAF/TOR 6.5.0.010 and toolkit 346 (IMSRTRIBSpecSDK-346.jar)
Table 1-11 shows the transaction types and messages that were tested.
Table 1-11 ACI PINComm Authorization Set Tested with Mobile Point-of-Service
| Transaction Type | Transaction Type Message Sent from ACI PINComm to Mobile Point-of-Service |
|---|---|
|
Credit Card Tender |
|
|
Debit Card Tender |
|
|
Gift Card Issue |
|
|
Gift Card Refund Issue new gift card or reload to existing gift card |
|
|
Gift Card Tender |
|
|
Note: Testing with AJB was done only with the Apple mobile devices. |
The AJB Fipay software version used for testing was 19444.
Table 1-11 shows the transaction types and messages that were tested.
Table 1-12 AJB Authorization Set Tested with Mobile Point-of-Service
| Transaction Type | Transaction Type Message Sent from AJB to Mobile Point-of-Service |
|---|---|
|
Credit Card Tender |
|
|
Debit Card Tender |
|
|
Gift Card Issue |
|
|
Gift Card Tender |
|
|
Note: It is recommended that the passwords for key stores and trust stores are changed from the values set by default. If this is not done, the system could be vulnerable to access by any unauthorized user with knowledge of the default passwords. |
For information on implementing security, see the Oracle Retail POS Suite Security Guide. This guide describes specific security features and implementation guidelines for the POS Suite products.
This installation guide details the steps needed to perform a full installation of Oracle Retail Point-of-Service Release 14.1. For migrating from a previous release to 14.1, uptake assistance tools are provided for migrating the database and code.
An uptake of Oracle Retail Point-of-Service from the following releases to Release 14.1 can be done:
Oracle Retail Point-of-Service Release 12.0.0
Oracle Retail Point-of-Service Release 12.0.9
Oracle Retail Point-of-Service Release 13.0.1
Oracle Retail Point-of-Service Release 13.0.2
Oracle Retail Point-of-Service Release 13.1.1
Oracle Retail Point-of-Service Release 13.2.0
Oracle Retail Point-of-Service Release 13.3.0
Oracle Retail Point-of-Service Release 13.4.0
Oracle Retail Point-of-Service Release 14.0.0
Oracle Retail Point-of-Service Release 14.0.1
To assist in the uptake of Oracle Retail Point-of-Service from one of these releases to Release 14.1, tools are available on My Oracle Support.
The following document is available through My Oracle Support. Access My Oracle Support at the following URL:
https://support.oracle.com
Oracle Retail POS Suite Uptake Guide (Doc ID: 1598170.1)
This guide contains the following information:
List of the impacts of the Release 14.1 functional changes on the database schema.
Description of the tools available to assist in the uptake of the database and code.
