mpos installation guide

8/10/2019 MPOS Installation Guide

1/40

Oracle Retail Mobile Point-of-Service

Installation Guide

Release 13.0

May 2008


2/40

Oracle Retail Mobile Point-of-Service Installation Guide, Release 13.0

Copyright 2007, 2008, Oracle. All rights reserved.

Primary Author: Bernadette Goodman

The Programs (which include both the software and documentation) contain proprietary information; theyare 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 otherindependently 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 inthe 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 thesePrograms may be reproduced or transmitted in any form or by any means, electronic or mechanical, for anypurpose.

If the Programs are delivered to the United States Government or anyone licensing or using the Programs onbehalf of the United States Government, the following notice is applicable:

U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical datadelivered 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. Assuch, use, duplication, disclosure, modification, and adaptation of the Programs, including documentationand 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, CommercialComputer Software--Restricted Rights (June 1987). Oracle USA, Inc., 500 Oracle Parkway, Redwood City, CA94065.

The Programs are not intended for use in any nuclear, aviation, mass transit, medical, or other inherentlydangerous 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 suchpurposes, 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 itsaffiliates. 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 thirdparties. 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 servicesfrom 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 purchasedproducts or services. Oracle is not responsible for any loss or damage of any sort that you may incur fromdealing with any third party.


3/40

Value-Added Reseller (VAR) Language

(i) the software component known as ACUMATEdeveloped and licensed by Lucent Technologies Inc. ofMurray Hill, New Jersey, to Oracle and imbedded in the Oracle Retail Predictive Application Server -Enterprise Engine, Oracle Retail Category Management, Oracle Retail Item Planning, Oracle RetailMerchandise Financial Planning, Oracle Retail Advanced Inventory Planning and Oracle Retail DemandForecasting applications.

(ii) the MicroStrategyComponents developed and licensed by MicroStrategy Services Corporation(MicroStrategy) of McLean, Virginia to Oracle and imbedded in the MicroStrategy for Oracle Retail Data

Warehouse and MicroStrategy for Oracle Retail Planning & Optimization applications.

(iii) the SeeBeyondcomponent developed and licensed by Sun MicroSystems, Inc. (Sun) of Santa Clara,California, to Oracle and imbedded in the Oracle Retail Integration Bus application.

(iv) the Wavelinkcomponent developed and licensed by Wavelink Corporation (Wavelink) of Kirkland,Washington, to Oracle and imbedded in Oracle Retail Store Inventory Management.

(v) the software component known as Crystal Enterprise Professional and/or Crystal Reports Professionallicensed by Business Objects Software Limited ("Business Objects") and imbedded in Oracle Retail StoreInventory Management.

(vi) the software component known as Access Vialicensed by Access Via of Seattle, Washington, andimbedded in Oracle Retail Signs and Oracle Retail Labels and Tags.

(vii) the software component known as Adobe Flexlicensed by Adobe Systems Incorporated of San Jose,California, and imbedded in Oracle Retail Promotion Planning & Optimization application.

(viii) the software component known as Style Reportdeveloped and licensed by InetSoft TechnologyCorp. of Piscataway, New Jersey, to Oracle and imbedded in the Oracle Retail Value Chain Collaborationapplication.

(ix) the software component known as WebLogicdeveloped and licensed by BEA Systems, Inc. of SanJose, California, to Oracle and imbedded in the Oracle Retail Value Chain Collaboration application.

(x) the software component known as DataBeacondeveloped and licensed by Cognos Incorporated ofOttawa, Ontario, Canada, to Oracle and imbedded in the Oracle Retail Value Chain Collaborationapplication.


4/40


5/40

v

Contents

List of FiguresList of Tables

Preface ................................................................................................................................................................. ix

Audience....................................................................................................................................................... ix

Related Documents ..................................................................................................................................... ix

Customer Support....................................................................................................................................... ix

Review Patch Documentation ................................................................................................................... xOracle Retail Documentation on the Oracle Technology Network ..................................................... x

Conventions ................................................................................................................................................. x

1 Pre-Installation Tasks

Check Hardware and Software Requirements ................................................................................... 1-1

Check Java KeyStore Requirement....................................................................................................... 1-2

2 Installation on the Oracle Stack using Windows

Expanding the Mobile Point-of-Service Distribution....................................................................... 2-1

Obtaining Third-Party Library Files Required by Mobile Point-of-Service................................ 2-1Running the Mobile Point-of-Service Application Installer ........................................................... 2-2

Resolving Errors Encountered During Application Installation .................................................... 2-2

Fixing the Security in your JRE ............................................................................................................. 2-2

Setting Register Accountability............................................................................................................. 2-2

Performing the Manual Integration...................................................................................................... 2-3

Setting the Class Path Entries........................................................................................................... 2-3

Setting Up Files................................................................................................................................... 2-3

Enabling Parameter Updates............................................................................................................ 2-4

Enabling Writing to the EJournal..................................................................................................... 2-5

Results of the Installation....................................................................................................................... 2-5

Running Mobile Point-of-Service ......................................................................................................... 2-6

3 Installation on the IBM Stack using Linux

Expanding the Mobile Point-of-Service Distribution....................................................................... 3-1

Obtaining Third-Party Library Files Required by Mobile Point-of-Service................................ 3-1

Running the Mobile Point-of-Service Application Installer ........................................................... 3-2

Resolving Errors Encountered During Application Installation .................................................... 3-2

Fixing the Security in your JRE ............................................................................................................. 3-2


6/40

vi

Setting Register Accountability............................................................................................................. 3-2

Performing the Manual Integration...................................................................................................... 3-3

Configuring Files................................................................................................................................ 3-3

Enabling Parameter Updates............................................................................................................ 3-4

Enabling Writing to the EJournal..................................................................................................... 3-4

Results of the Installation....................................................................................................................... 3-5

Running Mobile Point-of-Service ......................................................................................................... 3-5

A Appendix: Mobile Point-of-Service Application Installer Screens

B Appendix: Common Installation Errors

"Mpos installer finished with errors".................................................................................................. B-1

"Dispatcher.main, Exception: java.security.AccessControlException: access denied(java.util.PropertyPermission * read,write)" ...................................................................................... B-1


7/40

vii

List of Figures

A1 Introduction ................................................................................................................................ A-1A2 Previous MPOS Install .............................................................................................................. A-2A3 License Agreement .................................................................................................................... A-2A4 Choose Install Folder................................................................................................................. A-3A5 Choose Install Set ....................................................................................................................... A-3A6 Default Locale............................................................................................................................. A-4

A7 Supported Locales...................................................................................................................... A-5A8 Server Location........................................................................................................................... A-5A9 Where is jdk1.5 located?............................................................................................................ A-6A10 jdk1.5 does not exist................................................................................................................... A-7A11 JBoss Jar Directory ..................................................................................................................... A-7A12 What is the hostname of this mpos server?............................................................................ A-8A13 JRE Vendor.................................................................................................................................. A-8A14 Security Setup:Keystore............................................................................................................ A-9A15 Security Setup:Keystore.......................................................................................................... A-10A16 Security Setup:Keystore.......................................................................................................... A-11A17 Value-Added Tax (VAT)......................................................................................................... A-12A18 Pre-Installation Summary....................................................................................................... A-12A19 Install Complete ....................................................................................................................... A-13


8/40

viii

List of Tables

11 Mobile Point-of-Service Server Requirements....................................................................... 1-112 Mobile Point-of-Service Handheld Requirements................................................................ 1-221 Subdirectories .............................................................................. 2-522


9/40

ix

Preface

Oracle Retail Installation Guides contain the requirements and procedures that arenecessary for the retailer to install Oracle Retail products.

Audience

This Installation Guide is written for the following audiences: Database Administrators (DBA)

System analysts and designers

Integrators and implementation staff

Related DocumentsFor more information, see the following documents in the Oracle Retail MobilePoint-of-Service documentation set:

Oracle Retail Mobile Point-of-Service Release Notes

Oracle Retail Mobile Point-of-Service Operations Guide Oracle Retail Mobile Point-of-Service User Guide

Customer Supporthttps://metalink.oracle.com

When contacting Customer Support, please provide:

Product version and program/module name

Functional and technical description of the problem (include business impact)

Detailed step-by-step instructions to recreate

Exact error message received

Screen shots of each step you take
https://metalink.oracle.com/https://metalink.oracle.com/


10/40

x

Review Patch DocumentationFor a base release (".0" release, such as 13.0), Oracle Retail strongly recommends thatyou read all patch documentation before you begin installation procedures. Patchdocumentation can contain critical information related to the base release, based onnew information and code changes that have been made since the base release.

Oracle Retail Documentation on the Oracle Technology NetworkIn addition to being packaged with each product release (on the base or patch level),all Oracle Retail documentation is available on the following Web site:

http://www.oracle.com/technology/documentation/oracle_

retail.html

Documentation should be available on this Web site within a month after a productrelease. Note that documentation is always available with the packaged code on therelease date.

ConventionsThe following text conventions are used in this document:

Convention Meaning

boldface Boldface type indicates graphical user interface elements associatedwith an action, or terms defined in text or the glossary.

italic Italic type indicates book titles, emphasis, or placeholder variables forwhich you supply particular values.

monospace Monospace type indicates commands within a paragraph, URLs, codein examples, text that appears on the screen, or text that you enter.
http://www.oracle.com/technology/documentation/oracle_retail.htmlhttp://www.oracle.com/technology/documentation/oracle_retail.htmlhttp://www.oracle.com/technology/documentation/oracle_retail.htmlhttp://www.oracle.com/technology/documentation/oracle_retail.html


11/40


12/40


13/40

Installation on the Oracle Stack using Windows 2-1

2Installation on the Oracle Stack usingWindows

This chapter provides information about the installation procedures for Oracle RetailMobile Point-of-Service on the Oracle stack using Windows.

Expanding the Mobile Point-of-Service DistributionTo extract the Mobile Point-of-Service files:1. Extract the ORMPOS-13.00.zipfile from the Mobile Point-of-Service distribution

ORMPOS-13.00_EPD.zipfile.

2. Copy or upload ORMPOS-13.00.zipto the installation directory and extract itscontents. In this installation guide, is used for that directory.

Obtaining Third-Party Library Files Required by Mobile Point-of-ServiceThe Mobile Point-of-Service application uses JBoss specific files. You can download the

jboss application server to get access to the required files. 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

Note: Do not store the JBoss jar files at the system root directory.

Place the jar files into a folder.The installer does not correctly handle jar files stored at the systemroot directory.
http://sourceforge.net/project/showfiles.php?group_id=22866&package_id=16942&release_id=312621http://sourceforge.net/project/showfiles.php?group_id=22866&package_id=16942&release_id=312621http://sourceforge.net/project/showfiles.php?group_id=22866&package_id=16942&release_id=312621http://sourceforge.net/project/showfiles.php?group_id=22866&package_id=16942&release_id=312621


14/40


15/40

Performing the Manual Integration


Performing the Manual IntegrationThere following steps need to be completed manually to enable MobilePoint-of-Service to communicate with Back Office and Central Office. These stepsenable Mobile Point-of-Service to receive parameter updates and to send EJournal dataup to Central Office.

Setting the Class Path EntriesAdd the following class path entries to the\mpos\bin\ulenv.batfile:

SET CLASSPATH=%CLASSPATH%;%_360COMMON_PATH%\common\build\oc4j-internal.jar

SET CLASSPATH=%CLASSPATH%;%_360COMMON_PATH%\common\build\javax77.jar

SET CLASSPATH=%CLASSPATH%;%_360COMMON_PATH%\common\build\jms.jar

SET CLASSPATH=%CLASSPATH%;%_360COMMON_PATH%\common\build\optic.jar

Setting Up Files

To set up the .propertiesfiles:

1. If Back Office is installed, set up the file for Back Office. In the "ORACLE" sectionof the \mpos\lib\config\backoffice.jndi.propertiesfile, 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

2. In the "ORACLE" section of the \mpos\bin\jndi.propertiesfile, 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 Retail Back Office is installed on a different host orBack Office does not use the default RMI port of 12401, change theURL to the correct value.

If Oracle Application Server does not use the default user ID andpassword, change the values for principaland credentialstothe correct user ID and password.

Note: If Oracle Retail Back Office is installed on a different host orBack Office does not use the default RMI port of 12401, change theURL to the correct value.



16/40


2-4 Oracle Retail Mobile Point-of-Service Installation Guide

3. Set up the \mpos\bin\comm.propertiesfile.In the "ORACLE" section, uncomment the following commands:

comm.jms.topicConnectionFactory.name=jms/ApplicationTCF

comm.jms.queueConnectionFactory.name=jms/ApplicationQCF

comm.jms.topicConnectionFactory.name.backoffice=

jms/ApplicationTCF

com.jms.queueConnectionFactory.name.backoffice=

jms/ApplicationQCF

Enabling Parameter Updates

You can apply parameters to multiple registers by creating parameter sets in BackOffice and then distributing the parameter sets. Parameter updates are sent to aspecific Mobile Point-of-Service register. The updates are then shared by all MobilePoint-of-Service registers.

To distribute updated parameters from Back Office to Mobile Point-of-Service:1. Specify a Mobile Point-of-Service register number.

To define the register number, set the WorkstationID parameter in the\mpos\lib\config\

applications.propertiesfile. Any valid Mobile Point-of-Service register canbe used.

2. Edit the \mpos\lib\com\extendyourstore\unleashed\services\main\ntierdispatcher.xml file.

The ParameterTechnician section should look like the following example:

If Oracle Application Server is not using the default user ID and password, changejmsIDand jmsPasswordshown in the previous example to the user ID andpassword being used.

Note: If there are additional comm.propertiesfiles under\mposdirectory, delete the files.

Note: The value of clientIDmust match theWorkstationIDspecified in the application.propertiesfile.



17/40

Results of the Installation


Enabling Writing to the EJournal

Define whether Mobile Point-of-Service writes to the EJournal through the queue orthe database or both.

To define how Mobile Point-of-Service writes to the EJournal:

1. Edit the \mpos\lib\com\extendyourstore\unleashed\services\main\ntierdispatcher.xml

file in one of the following ways:

To write to the EJournal through the queue, uncomment theQueuedJournalManager section.

To write to the EJournal through the database, uncomment the DBJournalTechsection.

To write to the EJournal through both the queue and the database, uncommentboth the QueuedJournalManager and DBJournalTech sections.

2. Edit the \mpos\lib\config\manager\PosJournalManager.xmlfile. To write to the EJournal through the queue,uncomment the JMSJournalTech section.

Results of the InstallationThe default root directory for the application is c:\OracleRetailStore. In thisguide, these directories are referred to as . Thesubdirectories listed in Table 21are created.

Important subdirectories of the \mposdirectory are shown in Table 22.

Table 21 Subdirectories

Name Contents

360common Files shared by multiple Oracle Retail Strategic Store Solutionsapplications including 360Platform, Domain, and third-party jarfiles

jre Java runtime environment security files

logs Log files

mpos Mobile Point-of-Service files

Uninstaller Data Files for uninstalling Mobile Point-of-Service

Table 22


18/40

Running Mobile Point-of-Service


Running Mobile Point-of-ServiceRun the Mobile Point-of-Service system by executing batch files, found in yourinstallation bindirectory.

Before running Mobile Point-of-Service, the store server must be running. Also, thestore must be open before transactions can be completed with Mobile Point-of-Service.If the store server is not running, use the following script:

\pos\bin\StoreServerConduit.bat

To run Mobile Point-of-Service:

1. Start the Mobile Point-of-Service server. If it is not running, use the followingscript. This script also starts the Apache Tomcat web server.

\mpos\bin\ulremote.bat

2. Open a browser. Enter the following for the URL, whereis the hostname or IP address of the machinerunning the store server and the Mobile Point-of-Service process:

http:\\\unleashed\WebServerCRFServlet


19/40

Installation on the IBM Stack using Linux 3-1

3Installation on the IBM Stack using Linux

This chapter provides information about the installation procedures for Oracle RetailMobile Point-of-Service on the IBM stack using Linux.

Expanding the Mobile Point-of-Service DistributionTo extract the Mobile Point-of-Service files:

1. Extract the ORMPOS-13.00.zipfile from the Mobile Point-of-Service distributionORMPOS-13.00_EPD.zipfile.

2. Copy or upload ORMPOS-13.00.zipto the installation directory and extract itscontents. In this installation guide, is used for that directory.

Obtaining Third-Party Library Files Required by Mobile Point-of-ServiceThe Mobile Point-of-Service application uses specific files from JBoss and WebSphere.To obtain the necessary files:

1. To get the required JBoss files, download the jboss application server. You can getthe 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

2. Some WebSphere specific files are needed to make use of JMS. Extract the requiredfiles from the following locations:

/AppServer/plugins/

com.ibm.ws.runtime_6.1.0.jar

Note: Do not store the JBoss jar files at the system root directory.Place the jar files into a folder.

The installer does not correctly handle jar files stored at the systemroot directory.
http://sourceforge.net/project/showfiles.php?group_id=22866&package_id=16942&release_id=312621http://sourceforge.net/project/showfiles.php?group_id=22866&package_id=16942&release_id=312621http://sourceforge.net/project/showfiles.php?group_id=22866&package_id=16942&release_id=312621http://sourceforge.net/project/showfiles.php?group_id=22866&package_id=16942&release_id=312621


20/40


21/40


22/40



Enabling Parameter Updates

You can apply parameters to multiple registers by creating parameter sets in BackOffice and then distributing the parameter sets. Parameter updates are sent to aspecific Mobile Point-of-Service register. The updates are then shared by all MobilePoint-of-Service registers.

To distribute updated parameters from Back Office to Mobile Point-of-Service:

1. Specify a Mobile Point-of-Service register number.

To define the register number, set the WorkstationID parameter in the/mpos/lib/config/

applications.propertiesfile. Any valid Mobile Point-of-Service register canbe used.

2. Edit the /mpos/lib/com/extendyourstore/unleashed/services/main/ntierdispatcher.xml file.

Update the ParameterTechnician section. Comment out the entries in the "Oracle"section and uncomment the entries in the "WebSphere" section.

The ParameterTechnician section should look like the following example:

Enabling Writing to the EJournal

Define whether Mobile Point-of-Service writes to the EJournal through the queue orthe database or both.

To define how Mobile Point-of-Service writes to the EJournal:

1. Edit the /mpos/lib/com/extendyourstore/unleashed/services/main/ntierdispatcher.xml file in one of the following ways:

To write to the EJournal through the queue, uncomment theQueuedJournalManager section.

To write to the EJournal through the database, uncomment the DBJournalTechsection.

Note: The value of clientIDmust match theWorkstationIDspecified in the application.propertiesfile.

Note: You must create a UNIX user on the host where Back Office isinstalled and add that user to themqmgroup. The values for jmsIDand jmsPasswordspecified in the Password Technician definitionmust match the values for the UNIX user and password.


23/40


Installation on the IBM Stack using Linux 3-5

To write to the EJournal through both the queue and the database, uncommentboth the QueuedJournalManager and DBJournalTech sections.

2. Edit the /mpos/lib/config/manager/PosJournalManager.xmlfile. To write to the EJournal through the queue,uncomment the JMSJournalTech section.

Results of the InstallationThe default root directory for the application is /opt/OracleRetailStore. In thisguide, these directories are referred to as . Thesubdirectories listed in Table 31are created.

Important subdirectories of the /mposdirectory are shown in Table 32.

Running Mobile Point-of-ServiceRun the Mobile Point-of-Service system by executing shell scripts, found in yourinstallation bindirectory.

Before running Mobile Point-of-Service, the store server must be running. Also, thestore must be open before transactions can be completed with Mobile Point-of-Service.If the store server is not running, use the following script.

/pos/bin/StoreServerConduit.sh

To run Mobile Point-of-Service:

1. Start the Mobile Point-of-Service server. If it is not running, use the followingscript. This script also starts the Apache Tomcat web server.

/mpos/bin/ulremote.sh

Table 31 Subdirectories

Name Contents

360common Files shared by multiple Oracle Retail Strategic Store Solutionsapplications including 360Platform, Domain, and third-party jarfiles

jre Java runtime environment security files

logs Log files

mpos Mobile Point-of-Service files

Uninstaller Data Files for uninstalling Mobile Point-of-Service

Table 32 /mpos Subdirectories

Name Description

bin Startup batch files and shell scripts

lib Mobile Point-of-Service application and resource .jarfiles

lib/config XML configuration files, .propertiesfiles and .datfiles

3rd party Third-party source .jarfiles

logs Log files (additional log files are in the bin directory)


24/40



2. Open a browser. Enter the following for the URL, whereis the hostname or IP address of the machinerunning the store server and the Mobile Point-of-Service process:

http:///unleashed/WebServerCRFServlet


25/40


26/40

A-2 Oracle Retail Mobile Point-of-Service Installation Guide

Figure A2 Previous MPOS Install

Figure A3 License Agreement

Note: You must choose to accept the terms of the license agreementin order for the installation to continue.


27/40

Appendix: Mobile Point-of-Service Application Installer Screens A-3

Figure A4 Choose Install Folder

The field on this screen is described in the following table.

Figure A5 Choose Install Set

Field Title Where Would You LIke to Install?

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 StoreSolutions products.

In this guide, refers to the selectedinstallation directory.

Files specific to Mobile Point-of-Service are copied to the /mpossubdirectory of .

Example C:\OracleRetailStore

Notes


28/40



Figure A6 Default Locale


Field Title Server Tier Type

Field Description Choose the server tier type for this installation.

To run the N-tier version, choose N-Tier.

Note:Standalone is not supported.

Example N-Tier

Notes

Field Title What is the default locale?

Field Description Limited locale support in Mobile Point-of-Service enables the date,time, and currency to be displayed in the format for the selected defaultlocale.

To select the locale for Canada, choose en_CA.

To select the locale for Great Britain, choose en_GB.

To select the local for the United States, choose en_US.

Note:The only language currently supported is United States English.

Example en_US

Notes


29/40


30/40


31/40


Figure A10 jdk1.5 does not exist

Installation of jdk1.5 is required.

Figure A11 JBoss Jar Directory


Field Title 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 notcorrectly handle jar files stored at the system root directory.

Example C:\jboss-4.0.2\lib

Notes


32/40


Figure A12 What is the hostname of this mpos server?


Figure A13 JRE Vendor


Field Title Corporate Server Name

Field Description Enter the host name for the Mobile Point-of-Service server.

Example twriter2

Notes


33/40


Figure A14 Security Setup:Keystore

The fields on this screen are described in the following tables.

Field Title JRE Vendor

Field Description Select the vendor for the JRE entered on the JRE Location screen:

Sun

IBM

Example Sun

Notes

Field Title KeyStore Hash Algorithm

Field Description Enter the name of the algorithm used by the KeyStore to hash sensitivedata.

Example SHA-1

Notes

Field Title KeyStore Provider Name

Field Description Enter the provider for the KeyStore.

Example SunJCE

Notes

Field Title KeyStore Implementation Class

Field Description Enter the class that enables Point-of-Service to access the KeyStore.

Example oracle.retail.stores.simkeystore.siminterface.SimKeyStoreEncryptionService

Notes


34/40




Field Title Folder

Field Description Choose the location of the KeyStore jar files.

Note:If you are using the simulated key management package bundledwith Point-of-Service, the KeyStore jar file is found in the\360common\libdirectory.is the name of the directory you choseon the Choose Install Folder screen. Enter this path for the folder.

Note:The KeyStore jar files cannot be stored at the system rootdirectory. The jar files must be placed into a folder. The installer doesnot correctly handle jar files stored at the system root directory.

Example c:\simkeystore

Notes


35/40



The fields on this screen are described in the following tables. Up to five KeyStore jarfiles may be entered.

Field Title KeyStore JAR 1

Field Description Enter the name of a KeyStore jar file.

Note:If you are using the simulated key management package bundledwith Point-of-Service, enter simkeystore.jar.

Example simkeystore.jar

Notes



Example keystoreconnector.jar

Notes



Example encryptionclient.jar

Notes



Example simkeystore4.jar

Notes


36/40


Figure A17 Value-Added Tax (VAT)


Figure A18 Pre-Installation Summary



Example simkeystore5.jar

Notes

Field Title Value-Added Tax

Field Description Choose whether Value Added Tax is used.

Example No

Notes


37/40


Figure A19 Install Complete


38/40



39/40

Appendix: Common Installation Errors B-1

BAppendix: Common Installation Errors

This appendix describes some common errors encountered during installation ofMobile Point-of-Service.

"Mpos installer finished with errors"If you see this error message, there could be some settings incorrectly set or problems

with the installer itself. For more information, check theOracleRetailStore/mpos/logs/installer_log.txt file.

"Dispatcher.main, Exception: java.security.AccessControlException:access denied (java.util.PropertyPermission * read,write)"

Symptom:

The application dies when starting up:

[java] Dispatcher.main, Exception: java.security.AccessControlException: access

denied (java.util.PropertyPermission * read,write)

[java] java.security.AccessControlException: access denied

(java.util.PropertyPermission * read,write) [java] at java.security.AccessControlContext.checkPermission(Unknown

Source)

[java] at java.security.AccessController.checkPermission(Unknown Source)

[java] at java.lang.SecurityManager.checkPermission(Unknown Source)

[java] at java.lang.SecurityManager.checkPropertiesAccess(Unknown Source)

[java] at java.lang.System.getProperties(Unknown Source)

[java] at

com.extendyourstore.foundation.tour.conduit.Dispatcher.(Dispatcher.java:461)

[java] at

com.extendyourstore.foundation.tour.conduit.Dispatcher.getDispatcher(Dispatcher.ja

va:1301)

[java] at

com.extendyourstore.foundation.tour.conduit.Dispatcher.main(Dispatcher.java:2439)

[java] atcom.extendyourstore.foundation.config.TierLoader.main(TierLoader.java:359)

Solution:

This error usually occurs because the JRE that you are pointing to does not contain theupdated java.securityand java.policyfiles.


40/40

"Dispatcher.main, Exception: java.security.AccessControlException: access denied (java.util.PropertyPermission * read,write)"