1 Preinstallation Tasks

This chapter explains the tasks required prior to installation.

Note: Oracle Retail assumes that the retailer has applied all required fixes for supported compatible technologies.

Requesting Infrastructure Software

If you are unable to find the necessary version of the required Oracle infrastructure software (database server, application server, WebLogic, etc.) on the Oracle Software Delivery Cloud, you should file a non-technical 'Contact Us' Service Request (SR) and request access to the media. For instructions on filing a non-technical SR, see My Oracle Support Note 1071023.1 - Requesting Physical Shipment or Download URL for Software Media.

Check Supported Database Server Requirements

General requirements for a database server running Oracle Retail Financial Integration Pack include:

Table 1-1 Database Server Requirements

Supported on:	Versions Supported:
Database Server OS	OS certified with Oracle Database 12c Enterprise Edition. Options are: Oracle Linux 6 or 7 for x86-64 (Actual hardware or Oracle virtual machine). Red Hat Enterprise Linux 6 or 7 for x86-64 (Actual hardware or Oracle virtual machine). AIX 7.1 (Actual hardware or LPARs) Solaris 11.x SPARC (Actual hardware or logical domains) HP-UX 11.31 Integrity (Actual hardware, HPVM, or vPars)
Database Server 12c	Oracle Database Enterprise Edition 12c (12.1.0.2) with the following specifications: Components: Enterprise Edition Examples CD Oneoff Patches: 20846438: ORA-600 [KKPAPXFORMFKK2KEY_1] WITH LIST PARTITION 20406840: PROC 12.1.0.2 THROWS ORA-600 [17998] WHEN PRECOMPILING BY 'OTHER' USER 20925154: ORA-39126: WORKER UNEXPECTED FATAL ERROR IN KUPW$WORKER GATHER_PARSE_ITEMS JAVA RAC Only: 21260431: APPSST 12C: GETTING ORA-4031 AFTER 12C UPGRADE 21373473: INSTANCE TERMINATED AS LMD0 AND LMD2 HUNG FOR MORE THAN 70 SECS Other Components: Perl interpreter 5.0 or later X-Windows interface JDK 1.7

Note: By default, JDK is at 1.6. After installing the 12.1.0.2 binary, apply patch 19623450. Follow the instructions on Oracle Database Java Developer's Guide 12c Release 1 to upgrade JDK to 1.7. The Guide is available at: http://docs.oracle.com/database/121/JJDEV/chone.htm#JJDEV01000

Note: Bash Shell is supported and usage of any other shell may have adverse impact on the app functions.

Check Supported ODI Requirements

General requirements for an Oracle Data Integrator running Oracle Retail Financial Integration Pack include:

Table 1-2 Supported ODI Requirements

Supported on	Versions Supported
Data Integrator Server OS	OS supported with Oracle Database 12c Enterprise Edition. Options are: Oracle Linux 6 or 7 for x86-64 (Actual hardware or Oracle virtual machine). Red Hat Enterprise Linux 6 or 7 for x86-64 (Actual hardware or Oracle virtual machine). AIX 7.1 (Actual hardware or LPARs) Solaris 11.x SPARC (Actual hardware or logical domains) HP-UX 11.31 Integrity (Actual hardware, HPVM, or vPars)
Data Integrator 12c	Oracle Data Integrator Release 12c (12.2.1.2) with the following specifications: Oracle Fusion Middleware 12c Release 1 (12.2.1.2) Components: Oracle Data Integrator 12c Release 1 (12.2.1.2)

Check Supported Application Server Requirements

General requirements for an application server capable of running the Oracle Retail Financial Integration application include the following:

Table 1-3 Application Server Requirements

Supported on	Versions Supported
Application Server OS	OS supported with Oracle Fusion Middleware 12.2.1.2. Options are: Oracle Linux 6 or 7 for x86-64 (Actual hardware or Oracle virtual machine). Red Hat Enterprise Linux 6 or 7 for x86-64 (Actual hardware or Oracle virtual machine). AIX 7.1 (Actual hardware or LPARs) Solaris 11.x SPARC (Actual hardware or logical domains) HP-UX 11.31 Integrity (Actual hardware, HPVM, or vPars)
Application Server	Oracle Fusion Middleware 12.2.1.2 Components: Oracle WebLogic Server 12c (12.2.1.2) Java: JDK 8 with latest security updates+ 64 bit Oneoff Patches: 22648025: Java.lang.IllegalStateException. Note: If there is an existing WebLogic installation on the server, you must upgrade to WebLogic 12.2.1.2. All middleware components associated with WebLogic server 10.3.3 or 10.3.4 should be upgraded to 12.2.1.2. Back up the weblogic.policy file ($WL_HOME/ server/lib) before upgrading your WebLogic server, because this file could be overwritten. Copy over the weblogic.policy backup file after the WebLogic upgrade is finished and the post patching installation steps are completed. The installer can fail because of missing .jar in $ORACLE_HOME/utils/ccr/lib. This issue occurs only when the application is being installed on the same WebLogic server on which forms based applications are installed. It is valid only for Linux 64-bit. WebLogic 12c domain for ORFI needs JRF to be installed. Choose the JRF option at the domain creation. JRF needs an RCU schema for its runtime. This schema must be created prior to domain creation using the RCU tool. Weblogic 12.2.1.2 needs OWSM for Policy A and C to work. The owsm template choice while creating the wls domian, will give an option to deploy wsm-pm application to admin server. This app is required for policies to work.

Check Supported Client PC and Web Browser Requirements

Table 1-4 Supported Client PC and Web Browser Requirements

Requirement	Version
Operating system	Windows 7 Note: Oracle Retail assumes that the retailer has ensured its Operating System has been patched with all applicable Windows updates.
Display resolution	1024x768 or higher
Processor	2.6GHz or higher
Memory	1GByte or higher
Networking	intranet with at least 10Mbps data rate
Oracle (Sun) Java Runtime Environment	1.8.0+
Browser	Mozilla Firefox 45+

Supported Oracle Retail Products

Table 1-5 Supported Oracle Retail Products

Requirement	Version
Oracle Retail Merchandising System (RMS)	16.0.1
Oracle Retail Sales Audit (ReSA)	16.0.1
Oracle Retail Invoice Matching (ReIM)	16.0.1
Oracle Retail Integration Bus (RIB)	16.0.1

UNIX User Account Privileges to Install the Software

A UNIX user account is needed to install the software. The UNIX user that is used to install the software should have write access to the WebLogic server installation files.

For example, oretail.

Note: Installation steps will fail when trying to modify files under the WebLogic installation, unless the user has write access.

Supported Oracle Applications

Table 1-6 Supported Oracle Applications

Requirement	Version
Oracle E-Business Suite (General Ledger and Accounts Payable)	Oracle E-Business Suite 12.2.4 integration is supported using the Oracle Financial Operations Control Integration Pack for Oracle Retail Merchandising Suite and Oracle E-Business Suite Financials.
PeopleSoft Financials (General Ledger and Accounts Payables)	Oracle PeopleSoft 9.2 integration is supported using the Oracle Financial Operations Control Integration Pack for Oracle Retail Merchandising Suite and Oracle PeopleSoft Financials.

Note on Compatibility of Financial Applications (EBS, PeopleSoft) and ORFI): The release cycle of Oracle E-Business Suite Financials (EBS) and Oracle PeopleSoft Financials does not align with Oracle Retail's Enterprise release cycle. Because of this discrepancy, the certification of newer versions of EBS Financials and PeopleSoft Financials with the Oracle Retail suite of applications can be delayed. Because the Oracle Retail Financial Integration (RFI) product aligns its release with the Oracle Retail Enterprise release cycle, Oracle Retail Development will attempt to certify RFI, and other Oracle Retail applications, with newer versions of EBS and PeopleSoft in every major (.0), not minor (.x), release of Oracle Retail applications. Though they are not officially certified with Oracle Retail applications, the minor version patches of EBS Financials and PeopleSoft Financials (that are higher than that which is certified with Oracle Retail applications) may be compatible and function properly. Oracle Support will attempt to help customers to resolve issues that arise in these implementations that do not include documented, certified versions. Oracle Retail will try to duplicate the issues on certified versions of the integration, and if the issues can be duplicated in the certified versions, Oracle Retail will strive to fix and resolve the issues. If there arises an issue that cannot be resolved in an uncertified implementation, Oracle Retail maintains final discretion on its actions. In such situations, Oracle Support will try to help customers resolve their issues. Note, however, that in an uncertified version combination, SEV-1 escalations would not be allowed.

ORFI and Oracle WebLogic Server Cluster

Because ORFI must preserve the message publication and subscription ordering, ORFI deployed in Oracle WebLogic Server cannot be configured in an active-active cluster mode. In active-active cluster mode, multiple subscribers and publishers will process messages simultaneously and there will be no way to preserve message ordering.

ORFI can be deployed to a single instance of an Oracle WebLogic server that is clustered (active-passive). In this configuration, even though RFO is deployed in a WebLogic cluster, multiple instances of ORFI are not running at the same time, as there is only one WebLogic instance where ORFI is deployed. Therefore, ORFI can still preserve message ordering.

To truly configure ORFI for high availability, the only option is to configure it in active-passive mode.