Installation Guide, Volume 2 - IBM Stack Release 2delivered to U.S. Governme nt customers are...

Oracle® Retail Returns ManagementInstallation Guide, Volume 2 - IBM Stack

Release 2.4

E25275-01

December 2011

Oracle Retail Returns Management Installation Guide, Volume 2 - IBM Stack, Release 2.4

E25275-01

Copyright © 2011, Oracle and/or its affiliates. All rights reserved.

Primary Author: Bernadette Goodman

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

If this software or related documentation is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. 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, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms set forth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007). Oracle USA, Inc., 500 Oracle Parkway, Redwood City, CA 94065.

This software is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications which may create a risk of personal injury. If you use this software in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure the safe use of this software. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software in dangerous applications.

Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners.

This software and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.

Value-Added Reseller (VAR) Language

Oracle Retail VAR Applications

The following restrictions and provisions only apply to the programs referred to in this section and licensed to you. You acknowledge that the programs may contain third party software (VAR applications) licensed to Oracle. Depending upon your product and its version number, the VAR applications may include:

(i) the MicroStrategy Components 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.

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

(iii) the software component known as Access Via™ licensed by Access Via of Seattle, Washington, and imbedded in Oracle Retail Signs and Oracle Retail Labels and Tags.

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

You acknowledge and confirm that Oracle grants you use of only the object code of the VAR Applications. Oracle will not deliver source code to the VAR Applications to you. Notwithstanding any other term or condition of the agreement and this ordering document, you shall not cause or permit alteration of any VAR Applications. For purposes of this section, "alteration" refers to all alterations, translations, upgrades, enhancements, customizations or modifications of all or any portion of the VAR Applications including all reconfigurations, reassembly or reverse assembly, re-engineering or reverse engineering and recompilations or reverse compilations of the VAR Applications or any derivatives of the VAR Applications. You acknowledge that it shall be a breach of the agreement to utilize the relationship, and/or confidential information of the VAR Applications for purposes of competitive discovery.

The VAR Applications contain trade secrets of Oracle and Oracle's licensors and Customer shall not attempt, cause, or permit the alteration, decompilation, reverse engineering, disassembly or other reduction of the VAR Applications to a human perceivable form. Oracle reserves the right to replace, with functional equivalent software, any of the VAR Applications in future releases of the applicable program.

v

Contents

List of FiguresList of Tables

Send Us Your Comments ......................................................................................................................... xi

Preface ............................................................................................................................................................... xiii

Audience..................................................................................................................................................... xiiiDocumentation Accessibility ................................................................................................................... xiiiRelated Documents ................................................................................................................................... xivCustomer Support ..................................................................................................................................... xivReview Patch Documentation ................................................................................................................. xvOracle Retail Documentation on the Oracle Technology Network ................................................... xvConventions ............................................................................................................................................... xv

1 Preinstallation Tasks

Check for the Current Version of the Installation Guide................................................................. 1-1Check Supported Database Server Requirements............................................................................. 1-1

Required Settings for Database Installation ................................................................................... 1-2Check Supported Application Server Requirements........................................................................ 1-2

Check for SSL Certificate................................................................................................................... 1-2Check Oracle Retail Software Dependencies ..................................................................................... 1-2Check Third-Party Software Dependencies........................................................................................ 1-2Check Supported Client PC and Web Browser Requirements ....................................................... 1-3Check Java Key Manager Requirement ............................................................................................... 1-3Hardware Requirements ......................................................................................................................... 1-3Implementation Guidelines for Security ............................................................................................ 1-4Uptake Installation .................................................................................................................................. 1-4

2 Secure Configuration

Operating System ..................................................................................................................................... 2-1Additional Resource .......................................................................................................................... 2-2

Infrastructure/Middleware ..................................................................................................................... 2-2Database .............................................................................................................................................. 2-2Application Server ............................................................................................................................. 2-2Messaging............................................................................................................................................ 2-2RSA Key Manager.............................................................................................................................. 2-3Network Considerations ................................................................................................................... 2-3

vi

Oracle Retail POS Suite Application Configuration ........................................................................ 2-3Technology Considerations .............................................................................................................. 2-3

Wireless Technology................................................................................................................... 2-3Application Specific Settings..................................................................................................... 2-3

Application Runtime Settings .......................................................................................................... 2-5Application Parameters.............................................................................................................. 2-5

Temporary Password Length............................................................................................. 2-5Database Configuration ...................................................................................................... 2-5

Integration with Other Applications............................................................................................... 2-5Scripts and Command Line Utilities ............................................................................................... 2-5

Purge Scripts ................................................................................................................................ 2-5

3 Installation of the IBM Stack

Check the WebSphere Application Server Settings .......................................................................... 3-1Authentication Cache Timeout ........................................................................................................ 3-1

Performance Issue During Deployment on AIX ................................................................................ 3-1Create the Database Schema Owner and Data Source Users .......................................................... 3-2Expand the Returns Management Distribution ................................................................................. 3-2Obtain Third-Party Library Files Required by Returns Management .......................................... 3-3Secure the JDBC for the IBM DB2 Database ...................................................................................... 3-4Set up the JMS SSL Key Store ............................................................................................................... 3-4Obtain the Files Needed for RSA Key Manager ................................................................................ 3-4

Obtain the RSA Key Manager Version 3.0 Jar Files ...................................................................... 3-4Install the Java Cryptography Extension (JCE).............................................................................. 3-4

Enable Data Import .................................................................................................................................. 3-5Oracle Configuration Manager.............................................................................................................. 3-5Installation Options ................................................................................................................................. 3-5Database Install Options ........................................................................................................................ 3-6

Manually Create the Database Schema........................................................................................... 3-6Load Return Tickets Data ....................................................................................................................... 3-8Run the Returns Management Application Installer........................................................................ 3-8Resolve Errors Encountered During Application Installation ........................................................ 3-9Configure IBM WebSphere MQ............................................................................................................ 3-9Manual Deployment of the Returns Management Application ..................................................... 3-9Install Parameters .................................................................................................................................. 3-10Import Initial Parameters..................................................................................................................... 3-10

Import Parameters Through the User Interface.......................................................................... 3-11Import Parameters by using an Ant Target................................................................................. 3-11

Load Optional Purge Procedures ....................................................................................................... 3-11Using the Returns Management Application .................................................................................. 3-12

vii

A Appendix: Installer Screens for the IBM Stack

B Appendix: Installer Silent Mode

C Appendix: Reinstalling Returns Management

Reinstalling Returns Management on the IBM Stack ..................................................................... C-1

D Appendix: URL Reference

URLs for the IBM Stack ......................................................................................................................... D-1JDBC URL for a Database ................................................................................................................ D-1JNDI Provider URL for an Application ......................................................................................... D-1

E Appendix: Common Installation Errors

Unreadable Buttons in the Installer .................................................................................................... E-1

F Appendix: Returns Data Loader

Using the Returns Data Loader ............................................................................................................ F-1

G Appendix: Troubleshooting

Apache Axis2 Servlet Not Accessible .................................................................................................. G-1Deployment Failure ................................................................................................................................ G-1

H Appendix: Installation Order

Enterprise Installation Order ................................................................................................................ H-1

viii

List of Figures

A–1 Introduction ................................................................................................................................ A-1A–2 Oracle Customer Information .................................................................................................. A-2A–3 Oracle Customer Information .................................................................................................. A-3A–4 Requirements.............................................................................................................................. A-3A–5 License Agreement .................................................................................................................... A-4A–6 Database Owner ......................................................................................................................... A-5A–7 Data Source User........................................................................................................................ A-6A–8 Enable Secure JDBC ................................................................................................................... A-7A–9 Data Source SSL Configuration ............................................................................................... A-8A–10 Enable DIMP............................................................................................................................... A-9A–11 DIMP Configuration................................................................................................................ A-10A–12 Install Database Option........................................................................................................... A-11A–13 Sample Dataset ......................................................................................................................... A-12A–14 Default Locale........................................................................................................................... A-13A–15 Returns Management Administrator User........................................................................... A-14A–16 Security Setup: Key Store ....................................................................................................... A-15A–17 RSA Key Manager Requirements for RSA Key Manager 3.0 ............................................ A-16A–18 Key Store Details for RSA Key Manager 3.0 ........................................................................ A-17A–19 RSA Key Store Configuration for RSA Key Manager 3.0................................................... A-18A–20 Key Store Details for Simulator Key Manager..................................................................... A-19A–21 Key Store Details for Other Key Manager............................................................................ A-20A–22 Key Store Details ...................................................................................................................... A-21A–23 Deploy Key Store Connector RAR ........................................................................................ A-22A–24 Key Store Connector RAR Details ......................................................................................... A-23A–25 App Server WAS_HOME ....................................................................................................... A-24A–26 Mail Session Details ................................................................................................................. A-25A–27 Application Server Details...................................................................................................... A-26A–28 JMS Server Details.................................................................................................................... A-27A–29 Select JMS SSL Level................................................................................................................ A-28A–30 JMS SSL Keystore Details........................................................................................................ A-29A–31 Filter Based on Distinguished Name .................................................................................... A-31A–32 Distinguished Name Filter ..................................................................................................... A-32A–33 Configure WebSphere MQ Option........................................................................................ A-33A–34 WebSphere MQ Directory ...................................................................................................... A-34A–35 Manual Deployment Option .................................................................................................. A-35A–36 Application Deployment Details ........................................................................................... A-36A–37 Install Parameters Option ....................................................................................................... A-37A–38 Load Returns Test Data........................................................................................................... A-38A–39 Returns Test Data File ............................................................................................................. A-39A–40 Oracle Returns Management Messaging.............................................................................. A-40A–41 Oracle Returns Management WebService Configuration.................................................. A-41A–42 Turn Off the Application Server’s Non-SSL Port ................................................................ A-42A–43 Logging Detail Options........................................................................................................... A-43A–44 Installation Progress ................................................................................................................ A-44A–45 Installation Complete .............................................................................................................. A-44

ix

List of Tables

1–1 Database Server Requirements ................................................................................................ 1-11–2 Application Server Requirements ........................................................................................... 1-21–3 Supported Oracle Retail Products ........................................................................................... 1-2

xi

Send Us Your Comments

Oracle Retail Returns Management Installation Guide, Volume 2 - IBM Stack, Release 2.4

Oracle welcomes customers' comments and suggestions on the quality and usefulness of this document.

Your feedback is important, and helps us to best meet your needs as a user of our products. For example:

■ Are the implementation steps correct and complete?

■ Did you understand the context of the procedures?

■ Did you find any errors in the information?

■ Does the structure of the information help you with your tasks?

■ Do you need different information or graphics? If so, where, and in what format?

■ Are the examples correct? Do you need more examples?

If you find any errors or have any other suggestions for improvement, then please tell us your name, the name of the company who has licensed our products, the title and part number of the documentation and the chapter, section, and page number (if available).

Send your comments to us using the electronic mail address: [email protected]

Please give your name, address, electronic mail address, and telephone number (optional).

If you need assistance with Oracle software, then please contact your support representative or Oracle Support Services.

If you require training or instruction in using Oracle software, then please contact your Oracle local office and inquire about our Oracle University offerings. A list of Oracle offices is available on our Web site at http://www.oracle.com.

Note: Before sending us your comments, you might like to check that you have the latest version of the document and if any concerns are already addressed. To do this, access the Online Documentation available on the Oracle Technology Network Web site. It contains the most current Documentation Library plus all documents revised or released recently.

xiii

Preface

This Installation Guide describes the requirements and procedures to install this Oracle Retail Returns Management release.

AudienceThis Installation Guide is written for the following audiences:

■ Database administrators (DBA)

■ System analysts and designers

■ Integrators and implementation staff

Documentation AccessibilityOur goal is to make Oracle products, services, and supporting documentation accessible to all users, including users that are disabled. To that end, our documentation includes features that make information available to users of assistive technology. This documentation is available in HTML format, and contains markup to facilitate access by the disabled community. Accessibility standards will continue to evolve over time, and Oracle is actively engaged with other market-leading technology vendors to address technical obstacles so that our documentation can be accessible to all of our customers. For more information, visit the Oracle Accessibility Program Web site at http://www.oracle.com/accessibility/.

Accessibility of Code Examples in DocumentationScreen readers may not always correctly read the code examples in this document. The conventions for writing code require that closing braces should appear on an otherwise empty line; however, some screen readers may not always read a line of text that consists solely of a bracket or brace.

Accessibility of Links to External Web Sites in DocumentationThis documentation may contain links to Web sites of other companies or organizations that Oracle does not own or control. Oracle neither evaluates nor makes any representations regarding the accessibility of these Web sites.

Access to Oracle SupportOracle customers have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/support/contact.html or visit http://www.oracle.com/accessibility/support.html if you are hearing impaired.

xiv

Related DocumentsFor more information, see the following documents in the Oracle Retail Returns Management Release 2.4 documentation set:

■ Oracle Retail Returns Management Installation Guide, Volume 1 - Oracle Stack

■ Oracle Retail Returns Management Release Notes

■ Oracle Retail Returns Management User Guide

■ Oracle Retail POS Suite Configuration Guide

■ Oracle Retail POS Suite Data Dictionary

■ Oracle Retail POS Suite Data Model Differences

■ Oracle Retail POS Suite Data Model ERWIN File

■ Oracle Retail POS Suite Data Model Mapping File

■ Oracle Retail POS Suite Entity Relationship Diagrams, Volume 1 - Subject Areas

■ Oracle Retail POS Suite Entity Relationship Diagrams, Volume 2 - Overviews

■ Oracle Retail POS Suite Implementation Guide, Volume 1 - Implementation Solutions

■ Oracle Retail POS Suite Implementation Guide, Volume 2 - Extension Solutions

■ Oracle Retail POS Suite Implementation Guide, Volume 4 - Oracle Retail Point-of-Service to Siebel Integration

■ Oracle Retail POS Suite Licensing Information

■ Oracle Retail POS Suite Operations Guide

■ Oracle Retail POS Suite Security Guide

■ Oracle Retail POS Suite 13.4/Merchandising Products Implementation Guide

Customer SupportTo contact Oracle Customer Support, access My Oracle Support at the following URL:

https://support.oracle.com

When contacting Customer Support, please provide the following:

■ Product version and program/module name

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

■ Detailed step-by-step instructions to re-create

■ Exact error message received

■ Screen shots of each step you take

xv

Review Patch DocumentationWhen you install the application for the first time, you install either a base release (for example, 2.4) or a later patch release (for example, 2.4.1). If you are installing the base release, additional patch, and bundled hot fix releases, read the documentation for all releases that have occurred since the base release before you begin installation. Documentation for patch and bundled hot fix releases can contain critical information related to the base release, as well as information about code changes since the base release.

Oracle Retail Documentation on the Oracle Technology NetworkDocumentation is packaged with each Oracle Retail product release. Oracle Retail product documentation is also available on the following Web site:

http://www.oracle.com/technology/documentation/oracle_retail.html

(Data Model documents are not available through Oracle Technology Network. These documents are packaged with released code, or you can obtain them through My Oracle Support.)

Documentation should be available on this Web site within a month after a product release.

ConventionsThe following text conventions are used in this document:

Convention Meaning

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

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

monospace Monospace type indicates commands within a paragraph, URLs, code in examples, text that appears on the screen, or text that you enter.

1

Preinstallation Tasks 1-1

1 Preinstallation Tasks

This chapter describes the requirements for the IBM stack that must be met before Oracle Retail Returns Management can be installed.

If you will be installing multiple Oracle Retail applications, see Appendix H for a guideline for the order in which the applications should be installed.

Check for the Current Version of the Installation GuideCorrected versions of Oracle Retail installation guides may be published whenever critical corrections are required. For critical corrections, the rerelease of an installation guide may not be attached to a release; the document will simply be replaced on the Oracle Technology Network Web site.

Before you begin installation, check to be sure that you have the most recent version of this installation guide. Oracle Retail installation guides are available on the Oracle Technology Network at the following URL:

http://www.oracle.com/technology/documentation/oracle_retail.html

An updated version of an installation guide is indicated by part number, as well as print date (month and year). An updated version uses the same part number, with a higher-numbered suffix. For example, part number E123456-02 is an updated version of an installation guide with part number E123456-01.

If a more recent version of this installation guide is available, that version supersedes all previous versions. Only use the newest version for your installation.

Check Supported Database Server RequirementsTable 1–1 lists the general requirements for a database server running Oracle Retail Returns Management and the versions supported for this release.

Note: This is the IBM stack configuration that was tested for this release. While Returns Management may work in other configurations, this configuration was tested.

Table 1–1 Database Server Requirements

Supported on Versions Supported

Operating System IBM AIX 6.1 on POWER5, POWER6, or POWER7

Database IBM DB2 version 9.7 (64-bit) from WRS 7.1 Standard Edition

Check Supported Application Server Requirements

1-2 Oracle Retail Returns Management Installation Guide, Volume 2 - IBM Stack

Required Settings for Database InstallationDuring database creation, the database must be set to store data in UTF-8 encoding.

Check Supported Application Server RequirementsTable 1–2 lists the general requirements for an application server capable of running Returns Management and the versions supported for this release.

Check for SSL CertificateOracle Retail Returns Management is accessed through a secure HTTP connection. The installation of an SSL Certificate is required on your application server. If the certificate is not installed, warnings are displayed when trying to access Oracle Retail Returns Management.

For information on installing the SSL Certificate, refer to your application server documentation.

Check Oracle Retail Software DependenciesTable 1–3 lists the Oracle Retail products that Oracle Retail Returns Management is integrated with and the required versions.

Check Third-Party Software DependenciesThe following third-party software must be obtained:

■ The db2jcc.jar and db2jcc_license_cu.jar files must be obtained from your IBM DB2 database server. For more information, see "Obtain Third-Party Library Files Required by Returns Management" in Chapter 3.

■ If you are using the RSA Key Manager, you must download specific jar files. For more information, see "Check Java Key Manager Requirement".

Table 1–2 Application Server Requirements

Component Version Tested

Operating System IBM AIX 6.1 on POWER5, POWER6, or POWER7

J2EE Application Server IBM WebSphere ND 7.0.0.15 from WRS 7.1 Standard Edition

J2EE Application Server JVM IBM JRE 1.6 SR4

Messaging Provider IBM WebSphere MQ 7.0.1.4 from WRS 7.1 Standard Edition

Note: Returns Management does not support a clustered environment.

Table 1–3 Supported Oracle Retail Products

Integrates with Version

Oracle Retail Back Office 13.4

Oracle Retail Point-of-Service 13.4

Hardware Requirements

Preinstallation Tasks 1-3

Check Supported Client PC and Web Browser RequirementsThe general requirements for the client system include Adobe Acrobat Reader or another application capable of rendering Portable Data Format (PDF) files.

The following Web browsers are supported on Microsoft Windows XP SP2:

■ Microsoft Internet Explorer 7

■ Mozilla Firefox 3.6

Check Java Key Manager RequirementOracle Retail Returns Management requires that a Java Key Manager system is available prior to installation. A Key Store connector RAR file is required to enable the connection between Oracle Retail Returns Management and the Key Store. During installation, the RAR file must be deployed to the application server. Specific information for configuring the Key Store and deploying the RAR file is entered on the Security Setup: Key Store installer screens.

If you are using the RSA Key Manager, you must use version 3.0. You must obtain specific jar files for version 3.0 and install the Java Cryptography Extension Unlimited Strength Jurisdiction Policy Files 6.0. See "Obtain the Files Needed for RSA Key Manager" in Chapter 3.

Hardware RequirementsSpecific hardware requirements for the machines running Oracle Retail Returns Management depend on variables including the number of users, number of stores and registers, transaction volume, returns data retention period, and other applications running on the same machine.

Please note the following about the hardware requirements:

■ The CPU requirement depends on variables including the operating system and middleware selected.

■ The memory requirements and performance depend on variables including the operating system and middleware selected.

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 on the Key Store Pass Phrase installer screen.

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 Returns Management. 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.

Implementation Guidelines for Security


■ 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 data retention period and so on.

You need to determine your hardware requirements, based on the variables mentioned here, as well as any additional variables specific to your environment. For more information, contact Customer Support.

Implementation Guidelines for Security

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.

Uptake InstallationThis installation guide details the steps needed to perform a full installation of Oracle Retail Returns Management Release 2.4. An uptake of Oracle Retail Returns Management from the following releases to Release 2.4 can be done:

■ Oracle Retail Returns Management Release 2.0.0



To assist in the uptake of Oracle Retail Returns Management from one of these releases to Release 2.4, tools are available on My Oracle Support.

The following document is available through My Oracle Support. Access My Oracle Support at the following URL:


Oracle Retail Upgrade Guide (Doc ID: 1073414.1)

This guide contains the following information:

■ List of the impacts of the Release 2.4 functional changes on the database schema.

■ Description of the tools available to assist in the uptake of the database and code.

Note: It is recommended that the passwords for key stores and trust stores are changed from the values set by default.

Note: Uptake from Release 2.2.0 is not supported. Installation on the IBM stack was not supported for Release 2.2.0.

2

Secure Configuration 2-1

2 Secure Configuration

This chapter serves as a guide for administrators and people installing the product to securely configure Oracle Retail Returns Management. To see a broader spectrum of security-related best practices for this application, see the Oracle Retail POS Suite Security Guide.

This chapter is intended for security administrators and people installing the products who will deploy and configure the Oracle Retail POS Suite applications. These users perform the following tasks:

■ Install and deploy the applications

■ Configure the applications

■ Apply patches to the applications

It is assumed that the readers of this chapter have a general knowledge of administering the underlying technologies and the application.

The chapter begins with the operating system and moves through the supporting middleware to the application, and its connections with other resources.

Any references to Payment Card Industry Data Security Standard (PCI-DSS) requirements are from PCI-DSS version 2.0.

Operating SystemTo see the operating systems and browsers supported for this release of Returns Management, see Chapter 1.

The Oracle Retail POS Suite applications do not rely on insecure services or protocols. If the retailer or systems integrator customizes or extends the applications, these extensions must not rely on insecure services or protocols.

Note: All the Oracle Retail POS Suite applications should follow the same practices for configuring a secure environment.

Note: The options set by default for the installer are the most secure selection. If you choose to not use any of the default selections, you need to consider the implications of that change on the security of your installed product.

Infrastructure/Middleware


For more information about securing services and protocols, see the Oracle Retail POS Suite Security Guide.

Additional ResourceThe Center for Internet Security has published benchmarks for securing your systems at the operating system level. You can find the benchmark for IBM AIX at the following link:

http://benchmarks.cisecurity.org/en-us/?route=downloads.browse.category.benchmarks.os.unix.aix

Infrastructure/MiddlewareTo see the database and application server supported for this release of Returns Management, see Chapter 1.

DatabaseFor recommendations on securing the database as well as JDBC communications between the POS Suite applications and the database, see the Oracle Retail POS Suite Security Guide.

Do not store sensitive data on Internet-accessible systems. For example, your Web server and database server must not be on the same physical server. Oracle Retail POS Suite applications do not require the database server and Web server to be hosted on the same physical server machine.

For information about secure configuration of IBM DB2, see the IBM DB2 9.7Database Security Guide at the following Web site:

ftp://public.dhe.ibm.com/ps/products/db2/info/vr97/pdf/en_US/DB2Security-db2sece971.pdf

Application ServerFor information about secure configuration of IBM AIX Application Server, see the following documentation available at the following Web site:

■ WebSphere Application Server V7.0 Security Guide:

http://www.redbooks.ibm.com/abstracts/sg247660.html

■ WebSphere Application Server V7 Advanced Security Hardening:

http://www.ibm.com/developerworks/websphere/techjournal/1004_botzum/1004_botzum.html?ca=drs-

http://www.ibm.com/developerworks/websphere/techjournal/1005_botzum/1005_botzum.html

MessagingSecure JMS messaging configuration is specific to the application server. For information about securing the JMS messaging, see the Oracle Retail POS Suite Security Guide.

http://www.redbooks.ibm.com/abstracts/sg247660.html









Oracle Retail POS Suite Application Configuration


The Oracle Retail POS Suite applications do not permit a user to send unencrypted sensitive data by end-user messaging technologies, such as e-mail. If you customize an application to permit sending sensitive data, by end-user messaging technologies, you must use a solution that renders the sensitive data unreadable or implements strong cryptography.

Returns Management can send notifications of the results of a scheduled job to a designated e-mail address. The e-mail contains the job name entered by the end user. Therefore, the user must take care that the scheduled job name does not contain sensitive data.

RSA Key ManagerThe Oracle Retail POS Suite applications are designed to be easily integrated with an external key management service selected by the retailer. The applications perform no encryption, decryption, or key management. Many enterprise applications are available to perform those functions. Because of this, the applications require integration with a key management service in order to start properly.

The applications are designed to plug into a key management service with the addition of a thin layer that wraps the interface to a key manager of your choice, such as RSA and so on. The adaptor can be instantiated by an application framework such as Spring, so that it is easy to write and deploy an adaptor for a different key manager without modifying application code. Returns Management provides an adapter for RSA Key Manager Java Client, version 3.0. See the following file:

oracle.retail.stores.rsakeystore.rsainterface.RSAKeyStoreEncryptionService.java

This does not create a dependency on the RSA product, as a similar adapter could be developed for a different key management product.

For information on installing Point-of-Service with the RSA Key Manager, see "Check Java Key Manager Requirement" in Chapter 1.

Network ConsiderationsFor recommendations on securing the network and other enterprise security considerations, see the Oracle Retail POS Suite Security Guide.

Oracle Retail POS Suite Application ConfigurationThis section covers secure configuration that is recommended for all Oracle Retail POS Suite applications.

Technology ConsiderationsThese technologies should be considered.

Wireless TechnologyOracle Retail POS Suite applications are not designed as wireless applications. If wireless technology is used, you must adhere to PCI-DSS compliant wireless settings, per PCI-DSS Requirements 1.2.3, 2.1.1, and 4.1.1.

Application Specific SettingsThe Release 13.4 Oracle Retail POS Suite applications enable out-of-the-box audit logging by default. These logs should not be disabled.



Application log files are configurable. If you modify the settings, you must ensure they are compliant with PCI-DSS requirements 10.2 and 10.3.

The POS Suite applications implement automated audit trails for all system components to reconstruct the following events:

■ All actions taken by any individual with administrative privileges as assigned in the application

■ Access to application audit trails managed by or within the application

■ Invalid logical access attempts

■ Use of application's identification and authentication mechanisms

■ Initialization of the application audit logs

■ Creation and deletion of system-level objects within or by the application

The Release 13.4 Oracle Retail POS Suite applications implement an automated audit trail logging of various events happening on the system. The audit trail logging is configured in the log4j configuration file maintained for each application. The various events that need to be logged and the file where the audit logging information will be captured are configured in the log4j configuration file.

For each event, the Oracle Retail Audit log service logs the point of Origination of the event. In addition, the audit log framework logs the Initialization of the Audit log itself.

The log files are created with the following names and in following locations:

File Name: ReturnsManagement_audit.log

Location:

$WAS_HOME/profiles/<Profile Name>/logs

The following events should be captured at the system level:

■ Login or logoff

■ Start or stop a process

■ Use of user rights

■ Account administration

■ Change the security policy

■ Restart and shut down the system

■ USB events and Mount andUnmount events

■ Access a file or directory (create a file, remove a file, read a file, or change file descriptors)

Various tools are available to collect audit trail information. Audit trails should be maintained for the applications and for external system events.

Caution: Do not comment out any of the entries or prevent the logging from occurring.



Application Runtime SettingsAfter installation, these settings should be used.

Application ParametersSet these application parameters before running Returns Management.

Temporary Password Length The Temporary Password Length parameter is used to determine the length of system generated temporary passwords. This parameter resides in the application XML parameter file.

Database Configuration Password policy settings are configured through the database. By default, the password policy is compliant with PCI-DSS section 8.5.

Integration with Other ApplicationsThe Oracle Retail POS Suite applications integrate through the use of Web services and Java RMI. For information about securing these interface protocols, see the Oracle Retail POS Suite Security Guide.

Scripts and Command Line UtilitiesThis section covers scripts and utilities used after installation.

Purge ScriptsThe Oracle Retail POS Suite applications come with stored procedures and scripts that permit a DBA to purge the databases of data that the retailer determines are no longer necessary to store. Access to these scripts should be restricted. For more information about the purge scripts, see the Oracle Retail POS Suite Security Guide.

Caution: This parameter can be set to generate passwords to have a length between 7 and 12 characters. In order to comply with PCI-DSS section 8.5.10, the Oracle Retail POS Suite applications must not be modified to allow fewer than 7 characters.

Caution: If you change the password policy, ensure the modified settings comply with the PCI-DSS.

3

Installation of the IBM Stack 3-1

3

Installation of the IBM Stack

Before proceeding, you must install the database and application server software. For a list of supported versions, see Chapter 1.

During installation, the Returns Management database schema will be created and the Returns Management application will be deployed. The Java JDK that is included with the IBM WebSphere Application Server will be used to run the application.

Check the WebSphere Application Server SettingsSome application server settings affect Returns Management processing and deployment. Verify that these settings are set correctly for your installation.

Authentication Cache TimeoutThe Authentication Cache Timeout setting for the IBM WebSphere application server must be set correctly for Returns Management password processing. For information on how to determine the value you should use for this setting and how to set the value for the application server, refer to your IBM WebSphere documentation.

Performance Issue During Deployment on AIXIf you want IPv6 configured and your host and network are not configured to support it, you need to set a custom property in the JVM settings for your WebSphere application server. Significant performance degradation is possible during deployment if this property is not set. To set the property:

1. From the WebSphere Administration Console, select Application servers. Select your <servername>. Then select Process Definition and Java Virtual Machine.

2. Create the following JVM custom property.

java.net.preferIPv6Stack=true

3. Delete the /tmp/javasharedresources directory.

4. Restart the application server.

Create the Database Schema Owner and Data Source Users


Create the Database Schema Owner and Data Source UsersThe following recommendations should be considered for schema owners:

■ Database administrators should create an individual schema owner for each application, unless the applications share the same data. In the case of Oracle Retail Back Office and Point-of-Service, the database schema owner are the same because these applications share a database.

■ The schema owners should only have enough privileges to install the database.

For information on best practices for passwords, see the Oracle Retail POS Suite Security Guide.

To create the database schema owner and data source users:

1. Log in using the database administrator user ID.

2. Create the schema owner user.

CREATE SCHEMA <schema_name> AUTHORIZATION <schema_username>

3. Grant the privileges, shown in the following example, to the user.

GRANT CREATETAB, BINDADD, CONNECT, IMPLICIT_SCHEMA ON DATABASE TO USER <schema_username>

4. Grant the following object level privileges to the schema owner user.

GRANT CREATEIN, DROPIN, ALTERIN ON SCHEMA <schema_name> TO USER <schema_username> WITH GRANT OPTION

5. Create the data source user.

CREATE SCHEMA <data_source_schema_name> AUTHORIZATION <data_source_username>

6. Grant the privileges, shown in the following example, to the data source user.

GRANT CONNECT, IMPLICIT_SCHEMA ON DATABASE TO USER <data_source_username>

7. Grant the following object level privileges to the data source user.

GRANT CREATEIN ON SCHEMA <data_source_schema_name> TO USER <data_source_username> WITH GRANT OPTION

The installer grants the data source user access to the application database objects. If you choose No on the Manual Deployment Option screen, you need to grant the access after the installer completes. For more information, see "Manual Deployment of the Returns Management Application".

Expand the Returns Management DistributionTo extract the Returns Management files:

1. Extract the Returns Management 2.4 distribution zip file.

2. Log in to the UNIX server as the user who owns the WebSphere AS installation. Create a new staging directory for the Returns Management application distribution (ORRM-2.4.zip), for example, /tmp/orrm-staging.

Note: The staging directory (<staging_directory>) can exist anywhere on the system. It does not need to be under tmp.

Obtain Third-Party Library Files Required by Returns Management


3. Copy or upload ORRM-2.4.zip to the staging directory and extract its contents. The following files and directories should be created under <staging_directory>/ORRM-2.4:

ant\ant-ext\antinstall\connectors\external-lib\installer-resources\ocm-integration\returnsmgmt\.postinstall.cmd.postinstall.sh.preinstall.cmd.preinstall.sh.preinstall-oas.cmd.preinstall-oas.sh.preinstall-was.cmd.preinstall-was.sh.preinstall-wl.cmd.preinstall-wl.shantinstall-config.xmlbuild.xmlbuild-common.xmlbuild-common-backoffice.xmlbuild-common-easpi.xmlbuild-common-oas.xmlbuild-common-retailinv.xmlbuild-common-was.xmlbuild-common-webapps.xmlbuild-common-wl.xmlbuild-test.cmdcheckdeps.cmdcheckdeps.shinstall.cmdinstall.shprepare.xmlretail-OCM-stores.zipwallet.xml

For the remainder of this chapter, <staging_directory>/ORRM-2.4 is referred to as <INSTALL_DIR>.

Obtain Third-Party Library Files Required by Returns ManagementThe Returns Management application uses the DB2 drivers from IBM. Before running the Returns Management application installer, you must obtain the DB2 files from your database server.

1. Obtain the db2jcc.jar and db2jcc_license_cu.jar files from your database server at <IBM_DB2_INSTALL_DIR>.

2. Copy the jar files into <INSTALL_DIR>/external-lib/.

Note: The db2jcc_license_cu.jar file is needed to permit JDBC/SQLJ connectivity to the IBM DB2 database. The file is the standard license included with all editions of the IBM DB2 database.

Secure the JDBC for the IBM DB2 Database


Secure the JDBC for the IBM DB2 DatabaseOn the Enable Secure JDBC screen, you select whether secure JDBC will be used for communication with the database. See Figure A–8. If No is selected and you want to manually set up the secure JDBC after the installer completes, see the Oracle Retail POS Suite Security Guide.

Set up the JMS SSL Key StoreSelecting US Strength or Export Strength on the Select JMS SSL Level screen requires that a CA certificate and Key Store are used for IBM WebSphere Application Server and WebSphere MQ. You can manually deploy the CA certificate and Key Store for IBM WebSphere Application Server and WebSphere MQ or you can have the installer perform the deployment.

The default alias is myalias.

To have the installer do the deployment, enter the details on the JMS SSL Keystore Details screen. See Figure A–30.

If Yes is selected on the Filter Based on Distinguished Name screen, you enter the filter name on the Distinguished Name Filter screen. See Figure A–31 and Figure A–32. It is recommended that SSL certificates contain a distinguished name which follows the retailer’s naming convention.

Obtain the Files Needed for RSA Key ManagerIf you are using the RSA Key Manager, you must do the following:

■ "Obtain the RSA Key Manager Version 3.0 Jar Files"

■ "Install the Java Cryptography Extension (JCE)"

Obtain the RSA Key Manager Version 3.0 Jar FilesYou must obtain the required jar files from your RSA Key Manager provider.

1. Obtain the following jar files from your RSA Key Manager provider:

■ cryptoj.jar

■ kmsclient.jar

■ sslj.jar

2. Copy the jar files into <INSTALL_DIR>/external-lib.

Install the Java Cryptography Extension (JCE)If you are using RSA Key Manager or US Strength for the JMS SSL level, you must update the security for your JRE. You need to obtain version 1.4.2+ of the Java Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy Files. The 1.4.2+ version for the JCE Unlimited Strength Encryption is compatible with the IBM Java6 JRE.

1. Make a backup copy of local_policy.jar and US_export_policy.jar.

cd <WAS_INSTALL_DIR>/java/jre/lib/securitymv local_policy.jar local_policy.jar.bakmv US_export_policy.jar US_export_policy.jar.bak

Installation Options


2. Download version 1.4.2+ of JCE.

a. Go to the following Web site:

http://www.ibm.com/developerworks/java/jdk/security/50/

b. Click IBM SDK Policy Files. You are prompted to log in. You need an IBM ID, which you can request from the Sign in screen, in order to log in to this Web site.

c. After you log in, follow the instructions to download the JCE.

3. Copy the local_policy.jar and US_export_policy.jar files into the JRE security directory. The files are bundled as unrestricted.zip.

Enable Data ImportData Import (DIMP) is used by external systems to send data bundles to Returns Management for routine data loading of certain types of data. To use DIMP, you need to create a directory for the incoming bundles and a directory where the bundles are archived after being processed.

On the Enable DIMP installer screen, you select whether DIMP will be used. See Figure A–10. If Yes is selected on the screen, you then provide the paths to the directories on the DIMP Configuration installer screen. See Figure A–11.

For detailed information on DIMP, see the Oracle Retail POS Suite/Merchandising Products Implementation Guide.

Oracle Configuration ManagerThe Oracle Retail OCM Installer packaged with this release installs the latest version of OCM.

The following document is available through My Oracle Support. Access My Oracle Support at the following URL:


Oracle Configuration Manager Installer Guide (Doc ID: 1071030.1)

This guide describes the procedures and interface of the Oracle Retail Oracle Configuration Manager Installer that a retailer runs near the completion of its installation process.

Installation OptionsDuring installation, there are options that enable you to select whether the installer completes parts of the installation or if you want to complete those parts manually. For information on the available options, see the following sections:

■ "Database Install Options"

■ "Configure IBM WebSphere MQ"

■ "Manual Deployment of the Returns Management Application"

■ "Install Parameters"

http://www.ibm.com/developerworks/java/jdk/security/50/

Database Install Options


Database Install OptionsThe database schema must be created and populated before configuring the application server. On the Install Database Option screen, you select whether the installer creates and populates the database schema or if you want to do this manually. See Figure A–12.

■ If you choose Create schema with sample dataset, the installer creates and populates the database schema with sample data. This is the default selection on the screen. The sample dataset includes the minimum dataset. If you want data available to use for demonstrating Returns Management functionality after installation, you can select this option.

To use this option, you must provide the location of the zip file containing the sample dataset on the Sample Dataset installer screen. See Figure A–13. You can obtain the sample-dataset-13.4.zip file from Oracle Software Delivery Cloud.

■ If you choose Create schema with minimum dataset, the installer creates and populates the database schema with the minimum amount of data needed to launch and run Returns Management. If you want to load your own data after installation, you can select this option.

■ If you choose Skip schema creation and data loading, the installer does not create and populate the database schema. You choose this option if you want to create and populate the database schema manually. For information on manually creating and populating the database schema, see "Manually Create the Database Schema".

Manually Create the Database SchemaTo create and populate the database schema:

1. Change to the <INSTALL_DIR>/returnsmgmt/configured-output/db directory.

2. Set the JAVA_HOME and ANT_HOME environment variables. You can use the JDK and Ant that are installed with the IBM WebSphere Application Server.

JAVA_HOME=<WAS_INSTALL_DIR>/Java; ANT_HOME=<INSTALL_DIR>/ant; export JAVA_HOME ANT_HOME

3. Add $JAVA_HOME/bin and $ANT_HOME/bin to the front of the PATH environment variable.

PATH=$JAVA_HOME/bin:$ANT_HOME/bin:$PATH; export PATH

Note: If Returns Management is being installed for the first time and a clean schema is being used, do not select the Skip schema creation and data loading option. The installer will fail at some point if there is no data available in the database. You must populate the database schema before running the installer by selecting one of the other options.

If the schema is already populated and you want to manually restore or update the data, select the Skip schema creation and data loading option.

Database Install Options


4. Modify db.properties.

a. Uncomment the DB2 properties and comment out the properties for the other vendors such as Oracle and MS-SqlServer.

b. Set the following properties with your database settings. The values to be set are shown in bold in the examples.

Set the hash algorithm, for example, to SHA-256.

# Hash Algorithminst.hash.algorithm=HASH_ALGORITHM

Enter the values for the users shown in bold in the following example:

inst.app.admin.user=my-rm-admin-userinst.app.admin.password-encrypted=my-encrypted-rm-admin-password db.user=DB_USER_IDdb.password-encrypted=DB_PASSWORD_ENCRYPTED db.owner.user=DB_OWNER_USER_IDdb.owner.password-encrypted=DB_OWNER_PASSWORD_ENCRYPTED

The ant target will prompt for the passwords. Run the following ant target to encrypt the passwords:

ant -f db.xml encrypt-webapp-passwordsEnter the values for the URL used by the Returns Management application to access the database schema. See Appendix D for the expected syntax:

db.jdbc-url=jdbc:db2://DB_HOST_NAME:50001/DB_NAME

Enter the value for the store ID shown in the following example:

configured.store.id=04241

Enter the value for the supported locales shown in the following example:

gen.locales=fr,zh

c. Set the host name and port number for the parameter.apphost property to point to your Returns Management installation.

parameters.apphost=corbaloc:iiop:<hostname>:<iiop listenport>

d. In the parameters.classpath property, replace the semicolons used as separators with colons. This is needed to run with UNIX systems.

e. If loading sample data, replace FILE_DATASET_SAMPLE with the full path and file name for the sample dataset zip file.

dataset.sample.zip=FILE_DATASET_SAMPLE

5. Run one of the available Ant targets to create the database schema and load data:

■ load_sample: creates the database schema containing the sample dataset. The sample dataset includes the minimum dataset.

To use this option, you must provide the location of the zip file containing the sample dataset. You can obtain the sample-dataset-13.4.zip file from the Oracle Software Delivery Cloud.

■ load_minimum: creates the database schema containing the minimum dataset.

For example: ws_ant load_sample

Load Return Tickets Data


Load Return Tickets DataOn the Load Returns Test Data screen, you select whether the installer loads sample return tickets data. See Figure A–38.

To use this option, you must provide the location of the zip file containing the sample tickets data on the Returns Test Data installer screen. You can obtain the sample-tickets-13.4.zip file from Oracle Software Delivery Cloud.

Run the Returns Management Application InstallerThe installer will configure and deploy the Returns Management application. Before running the installer, verify that a profile has been created and the IBM WebSphere application server is running.

1. Change to the <INSTALL_DIR> directory.

2. Set the JAVA_HOME environment variable to point to the Java in the IBM WebSphere application server, that is, <WAS_INSTALL_DIR>/java.

3. If you are using an X server such as Exceed, set the DISPLAY environment variable so that you can run the installer in GUI mode (recommended). If you are not using an X server, or the GUI is too slow over your network, unset DISPLAY for text mode or use the install.sh script.

4. Run the installer.

a. Log into the UNIX server as a user who is authorized to install software.

b. Change the mode of all .sh files to executable.

c. Run the install.sh script. This will launch the installer.

After installation is complete, a detailed installation log file is created: orrm-install-app.<timestamp>.log

The installer leaves behind the ant.install.properties and cwallet.sso files for repeat installations.

Note: To see details on every screen and field in the application installer, see Appendix A.

Note: The installer is not compatible with versions of Java earlier than 1.6.

Caution: Password fields are masked in GUI mode, but in text mode your input is shown in plain text in the console window.

Note: The usage details for install.sh are shown below. The typical usage for GUI mode does not use arguments.

install.sh [text | silent websphere]

Manual Deployment of the Returns Management Application


Resolve Errors Encountered During Application InstallationIf the application installer encounters any errors, it will halt execution immediately. You can run the installer in silent mode so that you do not have to reenter the settings for your environment. For instructions on silent mode, see Appendix B.

For a list of common installation errors, see Appendix E.

Since the application installation is a full reinstall every time, any previous partial installs will be overwritten by the successful installation.

Configure IBM WebSphere MQIBM WebSphere MQ must be configured with a queue manager and the JMS queues and topics required by Returns Management, before Returns Management can be deployed. On the Configure MQ Series Option screen, you select whether the installer configures IBM WebSphere MQ or if you manually configure it.

Typically, when IBM WebSphere MQ is installed, a special user ID (usually mqm), and a user group (also mqm) are created in the operating system. The MQ installation files and directories have their owner and group set to the IBM WebSphere MQ user ID and group ID.

The user ID used for the Returns Management installation, must be made a member of IBM WebSphere MQ's user group, before attempting to create the Returns Management queue manager, queues, and topics. For example, if Returns Management is installed as user root, then root must be made a member of the mqm group.

Use the runmqsc command to configure IBM WebSphere MQ. Set up the following variable in the <INSTALL_DIR>/returnsmgmt/appserver/was/createq.dat file before running the command:

■ @mq.port@

In the following command, MQ_Install_Dir is the directory where IBM WebSphere MQ was installed. The value for <input.jms.server.queue> comes from the ant.install.properties file.

<MQ_Install_Dir>/bin/runmqsc <input.jms.server.queue> < <INSTALL_DIR>/returnsmgmt/appserver/was/createq.dat

Manual Deployment of the Returns Management ApplicationSkip this section if you chose the default option of allowing the installer to complete installation to the application server on the Manual Deployment Option screen. See Figure A–35.

Note: If IBM WebSphere MQ is installed on a different machine than IBM WebSphere Application Server, you must manually configure it.

Install Parameters


The installer includes the option to configure the application locally and skip deployment to the application server. If this option is chosen, the installer will make the configured application files available under <INSTALL_DIR>/returnsmgmt/configured-output/.

If you chose this installer option, you can deploy the Returns Management ear file by following these steps:

■ To deploy using the ant target:

1. Check that the Key Store connector JNDI name in the <WAS_PROFILE_DIR>/installedApps/<hostnameNodeNNCell>/applib/spring.properties file matches the JNDI name of the Key Store connector deployed on the application server.

2. Update the following property in the ant.install.properties file.

input.install.to.appserver = true

3. Run the following ant target:

install.sh ant init app-ear-deploy -propertyfile ant.install.properties

■ To deploy from the application server console, manually deploy the ear file from the following location:

<INSTALL_DIR>/returnsmgmt/returnsmgmt.ear

Install ParametersThe application parameters must be installed before the Returns Management application is fully operational. On the Install Parameters screen, you select whether the installer completes installation of the parameters or if you want to do this manually.

■ If you chose Yes, you do not need to perform any further steps to install the parameters. This is the default selection on the screen.

■ If you chose No, the installer did not install the parameters. For information on installing the parameters, see "Import Initial Parameters".

Import Initial Parameters

Note: When deploying the ear file, provide the same application name and context root you gave to the installer. These values were stored in the <INSTALL_DIR>/ant.install.properties file by the installer.

Note: If you did not choose to have the installer set the initial parameters, you must import an initial set of parameters before you can use Returns Management. For more information on parameters, see the Oracle Retail POS Suite Configuration Guide.

Load Optional Purge Procedures


This section provides an overview of the procedures for importing an initial set of parameters. You can import the parameters through the Returns Management user interface or by using an Ant target after the installation is complete. You only need to use one of the procedures. The procedure for importing parameters through the application user interface is described in more detail in the Oracle Retail Returns Management User Guide.

Import Parameters Through the User InterfaceTo import the initial parameters through the user interface:

1. Open the Returns Management application in a Web browser. The address is provided at the end of the installer output and in the log file.

http://<your host name>:<your port number>/<context root>

2. Log in to the application with a user ID that has full administrative rights.

3. Click the Data Management tab. The Available Imports screen appears.

4. To import the initial set of Returns Management application parameters, click the File link in the Import Application Parameters row. Follow the instructions to import returnsmgmt.xml from the <INSTALL_DIR>/returnsmgmt/configured-output/db directory.

Import Parameters by using an Ant TargetTo import parameters using an Ant target:

1. Change to the <INSTALL_DIR>/returnsmgmt/configured-output/db directory.

2. In db.properties, set the host name and port number for the parameters.apphost property to point to your Returns Management installation.

parameters.apphost=corbaloc:iiop:<hostname>:<iiop listenport>

3. Set the JAVA_HOME and ANT_HOME environment variables.

JAVA_HOME=<WAS_INSTALL_DIR>/java/jreANT_HOME=<INSTALL_DIR>/ant

4. Execute the following command:

$ANT_HOME/bin/ant load_parameters

Load Optional Purge ProceduresFor information on the procedures provided for purging aged data, see the Oracle Retail POS Suite Operations Guide.

To load the purge procedures:

1. Run the available Ant target to load the procedures.

ws_ant load_purge_procedures

2. Log in as the database schema owner, <schema_username>.

3. Create a user for running the purge procedures. This user should only have the privileges required to run the purge procedures.

Using the Returns Management Application


Using the Returns Management Application

After the application installer completes and you have run the initial parameter load, you should have a working Returns Management application installation. To launch the application, open a Web browser and go to https://<servername>:<portnumber>/<context root>

For example, https://myhost:9443/returnsmanagement

Note: When you are done installing Returns Management, log out and close the browser window. This ensures that your session information is cleared and prevents another user from accessing Returns Management with your login information.

Note: The installer created and started the MQ queue manager. If you restart WebSphere, you must also restart the MQ queue manager.

A

Appendix: Installer Screens for the IBM Stack A-1

A Appendix: Installer Screens for the IBMStack

You need the following details about your environment for the installer to successfully deploy the Returns Management application on the IBM stack. 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.

Figure A–1 Introduction

A-2 Oracle Retail Returns Management Installation Guide, Volume 2 - IBM Stack

Figure A–2 Oracle Customer Information

This screen sets up the information needed for Oracle Configuration Manager (OCM). The OCM collector must be registered with your My Oracle Support account so that the uploaded configuration information can be stored properly and be readily available during the resolution of a service request.

After the Returns Management installer completes, the OCM installer runs if OCM is not already installed. For information on OCM, see "Oracle Configuration Manager" in Chapter 3.

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

Field Title Email

Field Description Email address to use for OCM installation.

Field Title I wish to receive security updates via My Oracle Support.

Field Description To receive security updates, check the box.

Field Title My Oracle Support Password

Field Description Password for the My Oracle Support user to receive security updates.


Figure A–3 Oracle Customer Information

This screen is only displayed if No is selected on the previous Oracle Customer Information screen.

Figure A–4 Requirements


Figure A–5 License Agreement

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


Figure A–6 Database Owner


Field Title Schema Username

Field Description Schema user name that manages the objects in the schema. This user has Create, Drop, and Alter privileges in the schema, that is, Data Definition Language (DDL) execution privileges. For information on creating this user, see "Create the Database Schema Owner and Data Source Users" in Chapter 3.

Note: This user creates the database objects used by Returns Management.

Example DBOWNER

Field Title Schema Password

Field Description Password for the database owner.

Field Title Confirm Password

Field Description Reentered Schema Password used to confirm the password.

Note: The passwords in the Schema Password and Confirm Password fields must match.


Figure A–7 Data Source User


Field Title JDBC URL

Field Description URL used by the Returns Management application to access the database schema. See Appendix D for the expected syntax.

Example jdbc:db2://[host]:[tcpPort]/[dbname]

Field Title Data Source Username

Field Description Database user name that can access and manipulate the data in the schema. This user can have Select, Insert, Update, Delete, and Execute privileges on objects in the schema, that is, Data Manipulation Language (DML) execution privileges. For information on creating this user, see "Create the Database Schema Owner and Data Source Users" in Chapter 3.

Note: This schema user is used by Returns Management to access the database.

Example DBUSER

Field Title Data Source Password

Field Description Password for the data source user.


Figure A–8 Enable Secure JDBC

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


Field Description Reentered Data Source Password used to confirm the password.

Note: The passwords in the Data Source Password and Confirm Password fields must match.

Field Title Enable Secure JDBC?

Field Description Select whether secure JDBC is to be used for communication with the database.

Example Yes


Figure A–9 Data Source SSL Configuration

This screen is only displayed if Yes is selected on the Enable Secure JDBC screen.


Field Title Data Source SSL Port

Field Description SSL port used to access the database.

Example 20397


Figure A–10 Enable DIMP


Field Title Enable DIMP?

Field Description Select whether DIMP will be used. For information on DIMP, see "Enable Data Import" in Chapter 3.

Example Yes


Figure A–11 DIMP Configuration

This screen is only displayed if Yes is selected on the Enable DIMP screen.


Field Title DIMP Incoming Path

Field Description Directory where the incoming data import bundles arrive.

Example /tmp/dataimport/incoming

Field Title DIMP Archive Path

Field Description Directory where the incoming data import bundles are archived after processing.

Example /tmp/dataimport/archive


Figure A–12 Install Database Option


Field Title Select database installation option

Field Description The database schema must be created and populated before starting Returns Management. This screen gives you the option to have the installer create and populate the database schema or leave the database schema unmodified.

■ To have the installer leave the database schema unchanged, select Skip schema creation and data loading.

■ To have the installer create and populate the database schema with the minimum dataset, select Create schema with minimum dataset.

■ To have the installer create and populate the database schema with the sample dataset, select Create schema with sample dataset.

For more information, see "Database Install Options" in Chapter 3.

Example Yes


Figure A–13 Sample Dataset

This screen is only displayed when Create schema with sample dataset is selected on the Install Database Option screen.


Field Title Sample dataset file

Field Description Enter the path to the sample dataset to be loaded into the database schema.


Example /oracle/retail/samples/sample-db.zip


Figure A–14 Default Locale


Field Title Please select the Default Locale

Field Description Limited locale support in Returns Management enables the date, time, currency, and calendar to be displayed in the format for the selected default locale.

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

Example English - United States


Figure A–15 Returns Management Administrator User


Field Title Returns Management Admin Username

Field Description User name used for performing Returns Management administrative functions.

Example pos

Field Title Returns Management Admin Password

Field Description Password for the administrator user.


Field Description Reentered Returns Management Administrator Password used to confirm the password.

Note: The passwords in the Returns Management Administrator Password and Confirm Password fields must match.


Figure A–16 Security Setup: Key Store

This screen is used to configure the Encryption Key Store provider.


Field Title Key Store Hash Algorithm

Field Description Name of the algorithm used by the Key Store to hash sensitive data.

Example SHA-256

Field Title Select Key Store Provider

Field Description Provider for Key Store management.

■ To use the RSA key management package, select RSA Key Manager v3.0. The next screen displayed is Figure A–17.

■ To use the simulated key management package, select Simulator. The next screen displayed is Figure A–20.

■ To use a different key management provider, select Other. The next screen displayed is Figure A–21.

Example Simulator

Field Title Key Store JNDI Name

Field Description Name of the Key Store JNDI.

Example eis/keystoreconnector


Figure A–17 RSA Key Manager Requirements for RSA Key Manager 3.0

This screen is only displayed if RSA Key Manager v3.0 is selected for the Key Store provider on the Security Setup: Key Store screen. This informational screen explains the requirements to use the RSA Key Manager. Verify that you meet the requirements and then click Next.


Figure A–18 Key Store Details for RSA Key Manager 3.0

This screen is only displayed if RSA Key Manager v3.0 is selected for the Key Store provider on the Security Setup: Key Store screen.


Field Title Key Store Implementation Class

Field Description Enter the class that invokes the RSA Key Manager interface.

Example oracle.retail.stores.rsakeystore.rsainterface.RSAKeyStoreEncryptionService


Figure A–19 RSA Key Store Configuration for RSA Key Manager 3.0

This screen is only displayed if RSA Key Manager v3.0 is selected for the Key Store provider on the Security Setup: Key Store screen.


Field Title Server Host Address

Field Description Enter the IP address of the RSA server host.

Field Title Server Host Port

Field Description Enter the port number for the RSA server host.

Example 443

443 is the default used by the RSA Key Manager.

Field Title Cipher Key Class

Field Description Enter the RSA Key Manager cipher key class.

Field Title RSA Server SSL Certificate

Field Description Select the location of the RSA Key Manager server SSL certificate.

Field Title Client Key Store File

Field Description Select the location of the RSA Key Manager client Key Store file.


Figure A–20 Key Store Details for Simulator Key Manager

This screen is only displayed if Simulator is selected for the Key Store provider on the Security Setup: Key Store screen.


Field Title Client Key Store Password

Field Description Enter the password used to access the RSA Key Manager client Key Store.


Field Description Reentered Key Store Password used to confirm the password.

Note: The passwords in the Key Store Password and Confirm Password fields must match.

Field Title Cache Password

Field Description Enter the password used to access the RSA Key Manager cache.

Field Title Confirm Cache Password

Field Description Reentered Cache Password used to confirm the password.

Note: The passwords in the Cache Password and Confirm Cache Password fields must match.


Figure A–21 Key Store Details for Other Key Manager

This screen is only displayed if Other is selected for the Key Store provider on the Security Setup: Key Store screen.


Field Title Pass Phrase

Field Description Enter the pass phrase used to access the Key Store simulator.

Note: Use the same pass phrase for all Oracle Retail POS Suite applications in your configuration.

Field Title Confirm Pass Phrase

Field Description Reentered Pass Phrase used to confirm the pass phrase.

Note: The pass phrases in the Pass Phrase and Confirm Pass Phrase fields must match.

Field Title Key Store Implementation Class

Field Description Enter the class that invokes the key manager interface.

Field Title Key Store Provider

Field Description Enter the name of the provider for the Key Store.


Figure A–22 Key Store Details

This screen is only displayed if Other is selected for the Key Store provider on the Security Setup: Key Store screen.


Field Title archive name

Field Description Name of the archive which contains the Key Store within the RAR.

Example oracle.stores.rsakeystore.jar


Figure A–23 Deploy Key Store Connector RAR


Field Title Deploy a Key Store RAR?

Field Description Select whether a Key Store RAR is to be deployed.

Example Yes


Figure A–24 Key Store Connector RAR Details

This screen is only displayed if Yes is selected on the Deploy KeyStore Connector RAR screen.


Field Title Key Store Deployment Name

Field Description Name to which the Key Store connector will be deployed.

Example keystoreconnector

Field Title Key Store Connector RAR File

Field Description Path name to the Key Store connector RAR file.

Example /opt/connectors/keystoreconnector-rar.rar


Figure A–25 App Server WAS_HOME


Field Title WAS_HOME

Field Description Base directory for the IBM WebSphere Application Server installation.

Example /opt/IBM/SIF/WebSphere/AppServer


Figure A–26 Mail Session Details


Field Title SMTP host

Field Description Host where the SMTP server is running.

Example mail.example.com

Field Title From Address

Field Description From address in e-mails generated by Returns Management.

Example [email protected]


Figure A–27 Application Server Details


Field Title Server Name

Field Description Name of the IBM WebSphere server.

Example server1

Field Title Node Name

Field Description Name of the IBM WebSphere node.

Example myhostNode01

Field Title Cell Name

Field Description Name of the IBM WebSphere cell.

Example myhostNode01Cell

Field Title IIOP port

Field Description IIOP/BOOTSTRAP_ADDRESS port of the IBM WebSphere server. This port can be found in the following file: <WAS_PROFILE_DIR>/logs/AboutThisProfile.txt

Example 2809


Figure A–28 JMS Server Details


Field Title Server Profile

Field Description Name of the IBM WebSphere profile.

Example AppSrv01

Field Title Timezone

Field Description Time zone where this server is running.

Example America/Chicago

Field Title JMS Host Name

Field Description Name of the JMS server.

Note: Always use the actual host name and not the IP address or "localhost". There may be problems integrating with Point-of-Service if the actual host name is not used.

Example myhost

Field Title JMS Port

Field Description Port number used by the JMS server.

Example 1415


Figure A–29 Select JMS SSL Level

The field on this screen is described in the following table. For more information, see "Set up the JMS SSL Key Store" in Chapter 3.

Field Title JMS Username

Field Description User name for the JMS server. This user must exist in the Returns Management schema.

Example myuser

Field Title JMS Password

Field Description Password for the JMS server.


Field Description Reentered JMS Password used to confirm the password.

Note: The passwords in the JMS Password and Confirm Password fields must match.

Field Title JMS Queue Manager

Field Description Name of the JMS queue manager.

Example rm.queue.manager


Figure A–30 JMS SSL Keystore Details

This screen is only displayed if US Strength(TRIPLE_DES_SHA_US) or Export Strength(RC4_MDS_EXPORT) is selected on the Select JMS SSL Level screen.


Field Title Select JMS SSL Level

Field Description JMS SSL level to be used.

■ To use US strength, select US Strength(TRIPLE_DES_SHA_US).

■ To use export strength, select Export Strength(RC4_MDS_EXPORT).

■ To not use ssl support, select No SSL Support.

Example US Strength(TRIPLE_DES_SHA_US)

Field Title Corporate CA Certificate File

Field Description Location of the corporate certificate file.

Example /tmp/root-cert.pem

Field Title MQ Keystore Password

Field Description Key Store password for WebSphere MQ.



Field Description Reentered MQ Key Store Password used to confirm the password.

Note: The passwords in the MQ Keystore Password and Confirm Password fields must match.

Field Title MQ Source Keystore

Field Description Location of the source Key Store for WebSphere MQ.

Example /tmp/mq-keystore.jks

Field Title Password for MQ Source Keystore

Field Description Key Store password for MQ source.


Field Description Reentered Password for MQ Source Keystore used to confirm the password.

Note: The passwords in the Password for MQ Source Keystore and Confirm Password fields must match.

Field Title WebSphere Keystore Password

Field Description Key Store password for the WebSphere Application Server.


Field Description Reentered WebSphere Key Store Password used to confirm the password.

Note: The passwords in the WebSphere Keystore Password and Confirm Password fields must match.

Field Title WebSphere Source Keystore

Field Description Location of the source Key Store for WebSphere.

Example /tmp/was-keystore.jks

Field Title Password for WebSphere Source Keystore

Field Description Key Store password for WebSphere.


Field Description Reentered Password for WebSphere Source Key Store used to confirm the password.

Note: The passwords in the Password for WebSphere Source Keystore and Confirm Password fields must match.


Figure A–31 Filter Based on Distinguished Name

This screen is only displayed if US Strength(TRIPLE_DES_SHA_US) or Export Strength(RC4_MDS_EXPORT) is selected on the Select JMS SSL Level screen.


Field Title Filter based on Distinguished Name?

Field Description This screen gives you the option to filter based on the distinguished name.

Example Yes


Figure A–32 Distinguished Name Filter

This screen is only displayed if Yes is selected on the Filter based on Distinguished Name screen.


Field Title Filter Value

Field Description Distinguished name for the JMS SSL filter.

Example CN=rm.server.example.com


Figure A–33 Configure WebSphere MQ Option


Field Title Configure WebSphere MQ?

Field Description IBM WebSphere MQ must be configured with a queue manager and the queues and topics required by Returns Management before Returns Management can be deployed. This screen gives you the option to configure IBM WebSphere MQ manually. If you choose No, there are manual steps you need to perform after the installer completes. Se "Configure IBM WebSphere MQ" in Chapter 3.

Example Yes


Figure A–34 WebSphere MQ Directory

This screen is only displayed if Yes is selected on the Configure WebSphere MQ Option screen.


Field Title WebSphere MQ Dir

Field Description Base directory for IBM WebSphere MQ.

Example /opt/mqm


Figure A–35 Manual Deployment Option


Field Title Install files to app server?

Field Description By default, the installer will deploy the ear file. This screen gives you the option to configure the application in the staging area for use in a manual installation at a later time. This option can be used in situations where modifications to the deployed files must be reviewed by another party before being applied

If you choose No, see "Manual Deployment of the Returns Management Application" in Chapter 3 for the manual steps you need to perform after the installer completes.

Example Yes


Figure A–36 Application Deployment Details


Field Title App Deployment Name

Field Description Name by which this Returns Management application will be identified in the application server.

Example ReturnsManagement

Field Title Context Root

Field Description Path under the HTTP URL that will be used to access the Returns Management application. For example, a context root of 'returnsmanagement' will result in the application being accessed at https://<host>:<port>/returnsmanagement/index.jsp.

Example returnsmanagement


Figure A–37 Install Parameters Option


Field Title Install the parameters?

Field Description The application parameters must be set up before Returns Management can be used. This screen gives you the option to set up the parameters manually. If you choose No, see "Install Parameters" in Chapter 3 for the manual steps you need to perform after the installer completes.

Example Yes


Figure A–38 Load Returns Test Data


Field Title Load Returns Test Data?

Field Description Select whether sample return tickets are loaded after Returns Management is installed.

Example Yes


Figure A–39 Returns Test Data File

This screen is only displayed when Yes is selected on the Load Returns Test Data screen.


Field Title Sample Returns Tickets file

Field Description Enter the path to the sample return tickets data to be loaded into the database schema.


Example /oracle/retail/samples/sample-tickets.zip


Figure A–40 Oracle Returns Management Messaging

This screen is only displayed if Yes is selected on the Load Returns Test Data screen.


Field Title Select result messaging option

Field Description Choose the method to use to send return result messages to Returns Management.

■ If you want messages sent to a JMS queue, choose JMS Queue.

■ If you want to use a Web service to send the messages, choose Web Service.

Example Web Service


Figure A–41 Oracle Returns Management WebService Configuration


Field Title ORRM Host Name

Field Description Enter the host name of the Web Service to use to send return result messages to Returns Management.

Example localhost

Field Title Webservice HTTP Port

Field Description Enter the port number of the Web Service to use to send return result messages to Returns Management.

Example 9080


Figure A–42 Turn Off the Application Server’s Non-SSL Port


Field Title Disable non-SSL port?

Field Description Sets whether connecting to the application server requires a secured connection.

Note: It is recommended that you disable the non-SSL port in order to increase the security of your environment.

■ To disable the use of a non-SSL port, choose Yes.

■ To enable using a non-SSL port, choose No.

Example Yes


Figure A–43 Logging Detail Options


Field Title Logging Detail Options

Field Description Choose the level of logging.

■ To only log some of the messages, choose Standard Logging.

■ To log all of the messages, choose Verbose Logging.

Example Standard logging


Figure A–44 Installation Progress

Figure A–45 Installation Complete

After the installer completes, the Oracle Configuration Manager (OCM) installer runs if OCM is not already installed. For information on OCM, see "Oracle Configuration Manager" in Chapter 3.

B

Appendix: Installer Silent Mode B-1

B Appendix: Installer Silent Mode

In addition to the GUI and text interfaces of the Returns Management installer, there is a silent mode that can be run. This mode is useful if you wish to run a repeat installation without reentering the settings you provided in the previous installation. It is also useful if you encounter errors during an installation and wish to continue after resolving them.

The installer runs in two distinct phases. The first phase involves gathering settings from the user. At the end of the first phase, a properties file named ant.install.properties is created with the settings that were provided and the cwallet.sso file is created. In the second phase, this properties file is used to provide your settings for the installation.

To skip the first phase and re-use the ant.install.properties and cwallet.sso files from a previous run, follow these instructions:

1. Edit the ant.install.properties file and correct any invalid settings that may have caused the installer to fail in its previous run.

2. If the previous install was successful, the cwallet.sso file is found in the installation directory for that install. Copy the cwallet.sso file to <INSTALL_DIR> for this silent install.

3. Run the installer again with the silent argument.

install.sh silent websphere

B-2 Oracle Retail Returns Management Installation Guide, Volume 2 - IBM Stack

C

Appendix: Reinstalling Returns Management C-1

C Appendix: Reinstalling ReturnsManagement

Returns Management does not provide the capability to uninstall and reinstall the application. If you need to run the Returns Management installer again, perform the following steps.

Reinstalling Returns Management on the IBM StackTo reinstall:

1. Stop the WebSphere application server in the profile that contains Returns Management.

2. Delete the profile.

3. Stop the WebSphere MQ queue manager (for example, rm.queue.manager) and listener.

4. Delete the queue manager.

5. Recreate the profile.

6. Start the WebSphere application server in the profile.

7. Run the Returns Management installer. For more information, see "Run the Returns Management Application Installer" in Chapter 3.

Reinstalling Returns Management on the IBM Stack

C-2 Oracle Retail Returns Management Installation Guide, Volume 2 - IBM Stack

D

Appendix: URL Reference D-1

D Appendix: URL Reference

Both the database schema and application installers for the Returns Management product will ask for several different URLs. These include the following.

URLs for the IBM StackThe following URLs are used for the IBM stack.

JDBC URL for a DatabaseUsed by the Java application and by the installer to connect to the database.

Syntax: jdbc:db2://<dbhost>:<dbport>/<dbname>

■ <dbhost>: hostname of the database server

■ <dbport>: database listener port

■ <dbname>: system identifier for the database

For example, jdbc:db2://myhost:50000/mydatabase

JNDI Provider URL for an ApplicationUsed for server-to-server calls between applications.

Syntax: corbaloc:iiop:<host>:<iioport>

■ <host>: hostname of the WebSphere server

■ <iioport>: IIOP/BOOTSTRAP_ADDRESS port of the WebSphere server. This can be found in the <WAS_HOME>/profiles/<profile_name>/properties/portdef.props file.

For example, corbaloc:iiop:myhost:2809

URLs for the IBM Stack

D-2 Oracle Retail Returns Management Installation Guide, Volume 2 - IBM Stack

E

Appendix: Common Installation Errors E-1

E Appendix: Common Installation Errors

This appendix describes some common errors encountered during installation of Returns Management.

Unreadable Buttons in the InstallerIf you are unable to read the text within the installer buttons, it probably means that your JAVA_HOME needs to be set to a version 1.6 JDK. Set JAVA_HOME to a Java development kit of version 1.6 or later and run the installer again.

Unreadable Buttons in the Installer

E-2 Oracle Retail Returns Management Installation Guide, Volume 2 - IBM Stack

F

Appendix: Returns Data Loader F-1

F Appendix: Returns Data Loader

The Oracle Retail Returns Management installation includes return ticket data, in XML format, which you can optionally load into the Returns Management database. There are several reasons why you would want to load this data:

■ Once return tickets are loaded into the database, you can use the data to get familiar with those parts of the user interface that deal with return tickets, such as, searching for return tickets.

■ Loading the return tickets acts as an end-to-end test of the Oracle Retail Returns Management software installation, from the web services interface up to the back-end database.

■ The return ticket data is good sample data that can be used as a starting point for customization and experimentation with data relevant to your organization.

Using the Returns Data LoaderTo use the returns data loader:

1. Change to the db directory. For Oracle Application Server, change to the <INSTALL_DIR>/returnsmgmt/db directory.

2. If the returnsManagementDBInstall.jar file was not expanded as part of the installation, that jar file must be expanded to access the files needed to run the loader.

jar xvf returnsmgmtDBInstall.jar

3. Edit the part of the db.properties file that deals with the returns data loader.

Set the values of the properties as needed. Replace the host name My_RM_Server shown in the following example.

############################################################################# Properties for Returns Seed Data Loading############################################################################

# the host name where the seed data should be loadeddataLoader.host=My_RM_Server

# the port number where the seed data should be loaded# WebSphere App Server 6.x normally uses 9080, JBoss is 8080dataLoader.port=9080

# The URL shouldn't need to be modified unless the deployment location movesdataLoader.url=http://${dataLoader.host}:${dataLoader.port}/retwebsvc/services/ReturnsManager

Using the Returns Data Loader

F-2 Oracle Retail Returns Management Installation Guide, Volume 2 - IBM Stack

4. Execute the following command:

ws_ant load_returns_data

About 100 sample return requests and final result messages are sent to the Returns Management server. This step may take several minutes to complete.

This command sends some output to DataTools.log in the current directory. Ignore the warning message about attachment support, as the DataLoader does not need it to operate properly.

You can view the contents of the submitted XML messages in the returns-data/tickets directory. You can also modify the messages and resubmit them by repeating this step.

G

Appendix: Troubleshooting G-1

G Appendix: Troubleshooting

This appendix has information that can be used to troubleshoot problems after the installation of Returns Management.

Apache Axis2 Servlet Not AccessibleTo workaround the problem:

1. Stop the WebSphere application server in the profile that contains Returns Management.

2. Under InstallApps, navigate to /ReturnsManagement.ear/retwebsvc-webapp.war/WEB-INF/modules.

3. Copy the addressing-1.5.mar module to ReturnsManagement.ear/retwebsvc-webapp.war/WEB-INF/lib.

4. Rename addressing-1.5.mar to addressing-1.5.jar under ReturnsManagement.ear/retwebsvc-webapp.war/WEB-INF/lib.

5. Start the WebSphere application server in the profile.

For more information, see the following Web site:

http://www-01.ibm.com/support/docview.wss?uid=swg21315686

Deployment FailureIf the deployment of the application fails, see the following Web site for information about setting the ulimit option:

https://www-304.ibm.com/support/docview.wss?uid=swg21380114

http://www-01.ibm.com/support/docview.wss?uid=swg21315686

https://www-304.ibm.com/support/docview.wss?uid=swg21380114

Deployment Failure

G-2 Oracle Retail Returns Management Installation Guide, Volume 2 - IBM Stack

H

Appendix: Installation Order H-1

H Appendix: Installation Order

This section provides a guideline for the order in which the Oracle Retail applications should be installed. If a retailer has chosen to use only some of the applications, the order is still valid, less the applications not being installed.

Enterprise Installation Order1. Oracle Retail Merchandising System (RMS), Oracle Retail Trade Management

(RTM), Oracle Retail Sales Audit (ReSA), Optional: Oracle Retail Fiscal Management (ORFM)

2. Oracle Retail Service Layer (RSL)

3. Oracle Retail Extract, Transform, Load (RETL)

4. Oracle Retail Active Retail Intelligence (ARI)

5. Oracle Retail Warehouse Management System (RWMS)

6. Oracle Retail Invoice Matching (ReIM)

7. Oracle Retail Price Management (RPM)

8. Oracle Retail Allocation

9. Oracle Retail Central Office (ORCO)

10. Oracle Retail Returns Management (ORRM)

11. Oracle Retail Back Office (ORBO) or Back Office with Labels and Tags (ORLAT)

Note: The installation order is not meant to imply integration between products.

Note: ORFM is an optional application for RMS if you are implementing Brazil localization.

Note: During installation of RPM, you are asked for the RIBforRPM provider URL. Since RIB is installed after RPM, make a note of the URL you enter. If you need to change the RIBforRPM provider URL after you install RIB, you can do so by editing the remote_service_locator_info_ribserver.xml file.

Enterprise Installation Order

H-2 Oracle Retail Returns Management Installation Guide, Volume 2 - IBM Stack

12. Oracle Retail Store Inventory Management (SIM)

13. Oracle Retail Predictive Application Server (RPAS)

14. Oracle Retail Demand Forecasting (RDF)

15. Oracle Retail Category Management (CM)

16. Oracle Retail Replenishment Optimization (RO)

17. Oracle Retail Analytic Parameter Calculator Replenishment Optimization (APC RO)

18. Oracle Retail Regular Price Optimzation (RPO)

19. Oracle Retail Merchandise Financial Planning (MFP)

20. Oracle Retail Size Profile Optimization (SPO)

21. Oracle Retail Assortment Planning (AP)

22. Oracle Retail Item Planning (IP)

23. Oracle Retail Item Planning Configured for COE (IP COE)

24. Oracle Retail Advanced Inventory Planning (AIP)

25. Oracle Retail Integration Bus (RIB)

26. Oracle Retail Point-of-Service (ORPOS)

27. Oracle Retail Markdown Optimization (MDO)

28. Oracle Retail Clearance Optimization Engine (COE)

29. Oracle Retail Analytic Parameter Calculator for Markdown Optimization (APC-MDO)

30. Oracle Retail Analytic Parameter Calculator for Regular Price Optimization (APC-RPO)

31. Oracle Retail Promotion Intelligence and Promotion Planning and Optimization (PI-PPO)

32. Oracle Retail Analytics

33. Oracle Retail Workspace (ORW)

Note: During installation of SIM, you are asked for the RIB provider URL. Since RIB is installed after SIM, make a note of the URL you enter. If you need to change the RIB provider URL after you install RIB, you can do so by editing the remote_service_locator_info_ribserver.xml file.

Installation Guide, Volume 2 - IBM Stack Release 2delivered to U.S. Governme nt customers are...

Documents

Transcript of Installation Guide, Volume 2 - IBM Stack Release 2delivered to U.S. Governme nt customers are...