MPOS Installation Guide
MPOS Installation Guide
MPOS Installation Guide
Installation Guide
Release 13.0
May 2008
Bernadette Goodman
The Programs (which include both the software and documentation) contain proprietary information; they
are provided under a license agreement containing restrictions on use and disclosure and are also protected
by copyright, patent, and other intellectual and industrial property laws. Reverse engineering, disassembly,
or decompilation of the Programs, except to the extent required to obtain interoperability with other
independently created software or as specified by law, is prohibited.
The information contained in this document is subject to change without notice. If you find any problems in
the documentation, please report them to us in writing. This document is not warranted to be error-free.
Except as may be expressly permitted in your license agreement for these Programs, no part of these
Programs may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any
purpose.
If the Programs are delivered to the United States Government or anyone licensing or using the Programs on
behalf of the United States Government, the following notice is applicable:
U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data
delivered to U.S. Government customers are "commercial computer software" or "commercial technical data"
pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As
such, use, duplication, disclosure, modification, and adaptation of the Programs, including documentation
and technical data, shall be subject to the licensing restrictions set forth in the applicable Oracle license
agreement, and, to the extent applicable, the additional rights set forth in FAR 52.227-19, Commercial
Computer Software--Restricted Rights (June 1987). Oracle USA, Inc., 500 Oracle Parkway, Redwood City, CA
94065.
The Programs are not intended for use in any nuclear, aviation, mass transit, medical, or other inherently
dangerous applications. It shall be the licensee's responsibility to take all appropriate fail-safe, backup,
redundancy and other measures to ensure the safe use of such applications if the Programs are used for such
purposes, and we disclaim liability for any damages caused by such use of the Programs.
Oracle, JD Edwards, PeopleSoft, and Siebel are registered trademarks of Oracle Corporation and/or its
affiliates. Other names may be trademarks of their respective owners.
The Programs may provide links to Web sites and access to content, products, and services from third
parties. Oracle is not responsible for the availability of, or any content provided on, third-party Web sites.
You bear all risks associated with the use of such content. If you choose to purchase any products or services
from a third party, the relationship is directly between you and the third party. Oracle is not responsible for:
(a) the quality of third-party products or services; or (b) fulfilling any of the terms of the agreement with the
third party, including delivery of products or services and warranty obligations related to purchased
products or services. Oracle is not responsible for any loss or damage of any sort that you may incur from
dealing with any third party.
Contents
Figures
List of Tables
Preface ................................................................................................................................................................. ix
Audience.......................................................................................................................................................
Related Documents .....................................................................................................................................
Customer Support .......................................................................................................................................
Review Patch Documentation ...................................................................................................................
Oracle Retail Documentation on the Oracle Technology Network .....................................................
Conventions .................................................................................................................................................
ix
ix
ix
x
x
x
Pre-Installation Tasks
Check Hardware and Software Requirements ................................................................................... 1-1
Check Java KeyStore Requirement....................................................................................................... 1-2
2-1
2-1
2-2
2-2
2-2
2-2
2-3
2-3
2-3
2-4
2-5
2-5
2-6
3-1
3-1
3-2
3-2
3-2
3-2
3-3
3-3
3-4
3-4
3-5
3-5
vi
List of Figures
A1
A2
A3
A4
A5
A6
A7
A8
A9
A10
A11
A12
A13
A14
A15
A16
A17
A18
A19
Introduction ................................................................................................................................
Previous MPOS Install ..............................................................................................................
License Agreement ....................................................................................................................
Choose Install Folder.................................................................................................................
Choose Install Set .......................................................................................................................
Default Locale.............................................................................................................................
Supported Locales......................................................................................................................
Server Location...........................................................................................................................
Where is jdk1.5 located?............................................................................................................
jdk1.5 does not exist...................................................................................................................
JBoss Jar Directory .....................................................................................................................
What is the hostname of this mpos server?............................................................................
JRE Vendor..................................................................................................................................
Security Setup:Keystore ............................................................................................................
Security Setup:Keystore ..........................................................................................................
Security Setup:Keystore ..........................................................................................................
Value-Added Tax (VAT).........................................................................................................
Pre-Installation Summary.......................................................................................................
Install Complete .......................................................................................................................
A-1
A-2
A-2
A-3
A-3
A-4
A-5
A-5
A-6
A-7
A-7
A-8
A-8
A-9
A-10
A-11
A-12
A-12
A-13
vii
List of Tables
11
12
21
22
31
32
viii
1-1
1-2
2-5
2-5
3-5
3-5
Preface
Oracle Retail Installation Guides contain the requirements and procedures that are
necessary for the retailer to install Oracle Retail products.
Audience
This Installation Guide is written for the following audiences:
Related Documents
For more information, see the following documents in the Oracle Retail Mobile
Point-of-Service documentation set:
Customer Support
https://metalink.oracle.com
When contacting Customer Support, please provide:
ix
Conventions
The following text conventions are used in this document:
Convention
Meaning
boldface
italic
monospace
1
Pre-Installation Tasks
Oracle Retail Mobile Point-of-Service provides wireless access to Oracle Retail
Point-of-Service functions through the use of a handheld device. It is a separate
product from Oracle Retail Point-of-Service. For information on installing
Point-of-Service, see the Oracle Retail Point-of-Service Installation Guide.
Mobile Point-of-Service runs as a process that accesses resources on the N-Tier Store
Server in the same way as Point-of-Service clients. The N-Tier Store Server is required
by Mobile Point-of-Service. The server process passes Point-of-Service information to
the wireless devices. The wireless devices run a web browser interface and connect to
a specific URL to talk to the server process. The server process does not have a user
interface. For more information, see the Oracle Retail Point-of-Service Installation Guide.
Mobile Point-of-Service transactions propagate the same way as Point-of-Service
transactions. They are stored in a POSlog and can be sent to Oracle Retail Central
Office in an xml file or by queue.
Note: The Oracle stack and IBM stack are the configurations that
were tested for this release. The components required for each stack
are listed in this chapter. For each component, the product and the
version that were used for testing are included. While Mobile
Point-of-Service may work in other configurations, these are the
configurations that are supported for this release.
Component
Oracle Stack
IBM Stack
Hardware
x86-32 bit
x86-32 bit
Operating System
Database
Sun 1.5.x
(included in WRS)
JDK
Pre-Installation Tasks
1-1
Oracle Stack
IBM Stack
System Management
Agents
OEM Agents
OEM Agents
Table 12
Component
Symbol 8146
Printer
Zebra Cameo II
Operating System
Note:
Note:
The installer does not correctly handle jar files stored at the system
root directory.
Specific information for accessing the KeyStore is entered on the Security Setup:
KeyStore installer screens.
WARNING: A simulated key management package is bundled with
Oracle Retail Mobile Point-of-Service. It is not compliant with
either the Visa Payment Applications Best Practices (PABP) 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.
If you use the simulated key management package bundled with Oracle Retail Mobile
Point-of-Service, see Figure A15 in Appendix A for the location of the required
simkeystore.jar file.
2
Installation on the Oracle Stack using
Windows
This chapter provides information about the installation procedures for Oracle Retail
Mobile Point-of-Service on the Oracle stack using Windows.
2.
jboss-4.0.2\lib\jboss-common.jar
jboss-4.0.2\client\jboss-j2ee.jar
jboss-4.0.2\client\jbossmq-client.jar
Do not store the JBoss jar files at the system root directory.
Place the jar files into a folder.
Note:
The installer does not correctly handle jar files stored at the system
root directory.
2-1
Note:
1.
2.
3.
Run the MPOS.exe script. This will launch the installer. After installation is
complete, a detailed installation log file is created at
<mpos_install_directory>\mpos_InstallLog.xml
Copy
<mpos_install_directory>\jre\lib\security\java.security.sun to
$JAVA_HOME$\jre\lib\security\java.security.
Copy <mpos_install_directory>\jre\lib\security\java.policy to
$JAVA_HOME$\jre\lib\security\java.policy.
Execute the following SQL statement once for each device. In this example, 001 are the
last three digits of the actual IP address of the device and 04241 is the store ID.
update as_ws set cd_act=0 where id_ws=001 and id_str_rt=04241
CLASSPATH=%CLASSPATH%;%_360COMMON_PATH%\common\build\oc4j-internal.jar
CLASSPATH=%CLASSPATH%;%_360COMMON_PATH%\common\build\javax77.jar
CLASSPATH=%CLASSPATH%;%_360COMMON_PATH%\common\build\jms.jar
CLASSPATH=%CLASSPATH%;%_360COMMON_PATH%\common\build\optic.jar
Setting Up Files
To set up the .properties files:
1.
If Back Office is installed, set up the file for Back Office. In the "ORACLE" section
of the <mpos_install_directory>\mpos\lib\config\
backoffice.jndi.properties file, uncomment the following commands:
java.naming.provider.url=ormi://localhost:12401
java.naming.factory.initial=
com.evermind.server.rmi.RMIInitialContextFactory
java.naming.security.prinicipal=oc4jadmin
java.naming.security.credentials=oc4jadmin
Note:
If Oracle Application Server does not use the default user ID and
password, change the values for principal and credentials to
the correct user ID and password.
2.
Note:
If Oracle Application Server does not use the default user ID and
password, change the values for principal and credentials to
the correct user ID and password.
2-3
3.
2.
If Oracle Application Server is not using the default user ID and password, change
jmsID and jmsPassword shown in the previous example to the user ID and
password being used.
The value of clientID must match the WorkstationID
specified in the application.properties file.
Note:
If Oracle Application Server does not use the default user ID and
password, change the values for principal and credentials to
the correct user ID and password.
2.
<mpos_install_directory> Subdirectories
Name
Contents
360common
jre
logs
Log files
mpos
Uninstaller Data
<mpos_install_directory\mpos Subdirectories
Name
Description
bin
lib
lib\config
3rd party
logs
2-5
Start the Mobile Point-of-Service server. If it is not running, use the following
script. This script also starts the Apache Tomcat web server.
<mpos_install_directory>\mpos\bin\ulremote.bat
2.
3
Installation on the IBM Stack using Linux
This chapter provides information about the installation procedures for Oracle Retail
Mobile Point-of-Service on the IBM stack using Linux.
2.
To get the required JBoss files, download the jboss application server. You can get
the download at the website:
http://sourceforge.net/project/showfiles.php?group_
id=22866&package_id=16942&release_id=312621
Extract the following files:
jboss-4.0.2/lib/jboss-common.jar
jboss-4.0.2/client/jboss-j2ee.jar
jboss-4.0.2/client/jbossmq-client.jar
Do not store the JBoss jar files at the system root directory.
Place the jar files into a folder.
Note:
The installer does not correctly handle jar files stored at the system
root directory.
2.
Some WebSphere specific files are needed to make use of JMS. Extract the required
files from the following locations:
<WAS_INSTALL_DIR>/AppServer/plugins/
com.ibm.ws.runtime_6.1.0.jar
3-1
<WAS_INSTALL_DIR>/AppServer/runtimes/
com.ibm.ws.admin.client_6.1.0.jar
<MQ_INSTALL_DIR>/java/lib/jms.jar
<WAS_INSTALL_DIR>/AppServer/lib/WMQ/java/lib/
com.ibm.mqjms.jar
<WAS_INSTALL_DIR>/AppServer/lib/WMQ/java/lib/
com.ibm.mq.jar
<WAS_INSTALL_DIR>/AppServer/lib/WMQ/java/lib/dhbcore.jar
Note:
1.
2.
3.
4.
Run the MPOS.bin script. This will launch the installer. After installation is
complete, a detailed installation log file is created at
<mpos_install_directory>/mpos_InstallLog.xml
Copy
<mpos_install_directory>/jre/lib/security/java.security.ibm to
$JAVA_HOME$/jre/lib/security/java.security.
Copy <mpos_install_directory>/jre/lib/security/java.policy to
$JAVA_HOME$/jre/lib/security/java.policy.
Execute the following SQL statement once for each device. In this example, 001 are the
last three digits of the actual IP address of the device and 04241 is the store ID.
update as_ws set cd_act=0 where id_ws=001 and id_str_rt=04241
Configuring Files
To set up the .properties files:
1.
Update the /etc/hosts file with the host names of the Back Office and Central
Office servers and the IP address and host name where Point-of-Service is
installed. This step is required for JMS messaging to work properly.
2.
3.
If Back Office is installed, set up the file for Back Office. In the "WebSphere" section
of the <mpos_install_directory>/mpos/lib/config/
backoffice.jndi.properties file, uncomment the following commands:
java.naming.provider.url=corbaloc:iiop:<Back Office host name>:
<Back Office port number>
4.
5.
3-3
2.
Note:
You must create a UNIX user on the host where Back Office is
installed and add that user to the mqm group. The values for jmsID
and jmsPassword specified in the Password Technician definition
must match the values for the UNIX user and password.
Note:
2.
To write to the EJournal through both the queue and the database, uncomment
both the QueuedJournalManager and DBJournalTech sections.
<mpos_install_directory> Subdirectories
Name
Contents
360common
jre
logs
Log files
mpos
Uninstaller Data
<mpos_install_directory>/mpos Subdirectories
Name
Description
bin
lib
lib/config
3rd party
logs
Start the Mobile Point-of-Service server. If it is not running, use the following
script. This script also starts the Apache Tomcat web server.
<mpos_install_directory>/mpos/bin/ulremote.sh
3-5
2.
A
Appendix: Mobile Point-of-Service
Application Installer Screens
You need the following details about your environment for the installer to successfully
install the Mobile Point-of-Service application. Depending on the options you select,
you may not see some screens or fields.
For each field on a screen, a table is included in this appendix that describes the field.
If you want to document any specific information about your environment for any
field, a Notes row is provided in each table for saving that information.
Figure A1 Introduction
A-1
Note:
Field Description
The directory into which the Mobile Point-of-Service files are copied.
The default for the first directory in the path is OracleRetailStore.
This directory should be the same for all Oracle Retail Strategic Store
Solutions products.
In this guide, <mpos_install_directory> refers to the selected
installation directory.
Files specific to Mobile Point-of-Service are copied to the /mpos
subdirectory of <mpos_install_directory>.
Example
C:\OracleRetailStore
Notes
Figure A5 Choose Install Set
A-3
Field Description
N-Tier
Notes
Figure A6 Default Locale
Field Description
en_US
Notes
Field Description
en_US
Notes
Figure A8 Server Location
A-5
Hostname
Field Description
Example
localhost
Notes
Field Title
Port
Field Description
Port number of the store server used for the communication between
the store server and the host computer.
Example
1300
Notes
Figure A9 Where is jdk1.5 located?
Folder
Field Description
Example
C:\jdk1.5
Notes
Folder
Field Description
Choose the location of the directory that contains the JBoss jar files.
Note: The JBoss jar files cannot be stored at the system root directory.
The jar files must be placed into a folder. The installer does not
correctly handle jar files stored at the system root directory.
Example
C:\jboss-4.0.2\lib
Notes
A-7
Field Description
Example
twriter2
Notes
Figure A13 JRE Vendor
Field Title
JRE Vendor
Field Description
Select the vendor for the JRE entered on the JRE Location screen:
Example
Sun
IBM
Sun
Notes
Figure A14 Security Setup:Keystore
Field Description
Enter the name of the algorithm used by the KeyStore to hash sensitive
data.
Example
SHA-1
Notes
Field Title
Field Description
Example
SunJCE
Notes
Field Title
Field Description
Example
oracle.retail.stores.simkeystore.siminterface.SimKeyStoreEncryptionSer
vice
Notes
A-9
Folder
Field Description
Example
c:\simkeystore
Notes
The fields on this screen are described in the following tables. Up to five KeyStore jar
files may be entered.
Field Title
KeyStore JAR 1
Field Description
Example
simkeystore.jar
Notes
Field Title
KeyStore JAR 2
Field Description
Example
keystoreconnector.jar
Notes
Field Title
KeyStore JAR 3
Field Description
Example
encryptionclient.jar
Notes
Field Title
KeyStore JAR 4
Field Description
Example
simkeystore4.jar
Notes
A-11
Field Title
KeyStore JAR 5
Field Description
Example
simkeystore5.jar
Notes
Figure A17 Value-Added Tax (VAT)
Value-Added Tax
Field Description
Example
No
Notes
Figure A18 Pre-Installation Summary
A-13
B
Appendix: Common Installation Errors
This appendix describes some common errors encountered during installation of
Mobile Point-of-Service.
Solution:
This error usually occurs because the JRE that you are pointing to does not contain the
updated java.security and java.policy files.
B-1