Oracle® Retail Predictive Application Server Installation Guide Release 14.1.2 E70811-01 |
|
![]() Previous |
![]() Next |
Welcome to the Oracle® Retail Predictive Application Server Installation Guide. This chapter outlines the contents of this guide, discusses the updated components with respect to the previous version, lists hardware and software requirements, and defines commonly used notations and terms.
This document contains information for full and patch installations:
Full Installation. Refer to this section if you are performing a full installation of RPAS 14.1.2.
Patch Installation. Refer to this section if you are performing a patch installation of RPAS 14.1.2.
Note: Only RPAS base releases have installers. Patch releases and hotfixes do not have installers. If you are installing a base release, refer to Full Installation for installer instructions. If you are installing a patch, refer to Patch Installation for patch instructions. |
Read this entire guide before beginning the installation process to ensure you understand the installation process and have all the necessary documentation, hardware, and software available.
Table 1-1 describe the hardware and software requirements for the RPAS Server, RPAS Configuration Tools, and ODBC and JDBC servers and clients.
For information on installing the RPAS Server, refer to either Chapter 3, "Installing on UNIX and Linux Environments" or Chapter 4, "Installing on a Windows Environment".
Table 1-1 RPAS Server and Components Hardware and Software Requirements
Component | Details |
---|---|
Supported Operating Systems for the RPAS Server, Compilers, ODBC Server, and ODBC Client |
AIX 7.1 TL3 SP1 IBM XLC 12.1 (64 bit) |
Oracle Enterprise Linux 6.5. Red Hat Enterprise Linux 6.5 Linux Compiler: gcc 4.4.6 (ships standard with Oracle Linux 6.5) |
|
Oracle Solaris 11.1 (SPARC) Solaris Studio 12.3 |
|
HP-UX Itanium 11.31 HP-UX Compiler: aCC A.06.20 |
|
Note: The RPAS ODBC Client is supported on the previously listed operating systems, as well as 32-bit Windows or 64-bit Windows. Note: The C++ compilers are only needed for building custom extension libraries, and not for using base RPAS Platform and Application functionality. Note: The ksh shell is required on all operating systems for the RPAS server. |
|
Supported Operating Systems for RPAS Configuration Tools |
Microsoft Windows 7 Microsoft Windows 8.1 |
Note: The server aspect of the RPAS Configuration Tools (rpasInstall, which is used to install and patch domains) is supported on the same operating systems as the previously listed RPAS Server. |
|
Required Software |
Java 7 is required to support the RPAS Configuration Tools, server machines, and JDBC Client. There are specific Java versions supported for each of the following operating systems:
Note: A full JDK installation is required only if building Java-based custom extensions for RPAS. For running RPAS, only the JRE is required. |
Table 1-2 describe the hardware and software requirements for the RPAS Classic Client. For information on installing the RPAS Classic Client, refer to Chapter 6, "Installing and Configuring the RPAS Classic Client". For information about Single Sign-On, refer to .
Table 1-2 RPAS Classic Client Hardware and Software Requirements
Component | Details |
---|---|
Supported Operating Systems |
Microsoft Windows 7 Professional with Microsoft Office 2010 or 2013 |
Client System Requirements |
All components are required:
|
RPAS Classic Client Web Deployment and Single Sign-On (SSO) Requirements |
Note: Classic Client Web Deployment, along with SSO, is optional. |
Server options (only one of these options is required):
|
|
Web browser requirements:
|
|
Single Sign-On (SSO) WebLogic requires both of these components:
|
|
RPAS Classic Client Web Deployment is certified for SSO using Oracle Access Manager 11g (OAM). This is available in the Oracle Identity and Access Management 11g package (11.1.2.2). |
|
OAM works with a wide variety of LDAP-based identity stores. RPAS Classic Client Web Deployment has been verified to work with Oracle Internet Directory 11g (OID 11.1.1.7). |
|
OAM-based SSO needs a web server. RPAS Classic Client Web Deployment has been verified to work with Oracle HTTP Server (OHS) 12.1.3. |
|
A web server plug-in (OAM Webgate) communicates with an OAM instance and to create the SSO cookie. OAM Webgate 11.1.2.2 is required. |
|
In summary, the following Oracle Fusion Middleware packages are utilized in the solution:
|
Table 1-3 describe the hardware and software requirements for the RPAS Fusion Client. For information on installing the RPAS Fusion Client, refer to Chapter 5, "Installing the RPAS Fusion Client".
Table 1-3 RPAS Fusion Client Hardware and Software Requirements
Component | Details |
---|---|
Supported Operating Systems for the Fusion Client |
Microsoft Windows 7 Professional with Microsoft Office 2010 or 2013 |
Supported Web Browsers |
Note: All browsers must have Adobe Flash Player 9.0 (or later). |
Microsoft Windows 7
|
|
Oracle Database |
Oracle 12c Database Note: The WebLogic Server 12c (Release 12.1.3) and ADF use Oracle Platform Security Services (OPSS); use by the Oracle 12c Database is not required of the Fusion Client application. |
Application Server Requirements |
All components required:
|
Supported Operating Systems for the Application Server |
Note: The operating systems you choose for the RPAS server and the application server for the RPAS Fusion Client do not need to be the same. |
AIX 7.1 TL3 SP1 |
|
Oracle Linux 6.5 (64 bit) Red Hat Enterprise Linux 6.5 |
|
Oracle Solaris 11.1 (SPARC) Solaris Studio 12.3) |
|
HP-UX Itanium 11.31 |
|
Required Software |
Java 7 is required to support the Fusion Client on an application server. There are specific JDK versions supported for each of the following operating systems:
Note: A full JDK installation is required only if building Java-based custom extensions for RPAS. For running RPAS, only the JRE is required. |
Supported Oracle Software for Single Sign-On (SSO) |
Note: SSO is optional. |
RPAS Fusion Client is certified for SSO using Oracle Access Manager 11g (OAM). This is available in the Oracle Identity and Access Management 11g package (11.1.2.2). |
|
OAM works with a wide variety of LDAP-based identity stores. RPAS Fusion Client in SSO deployment has been verified to work with Oracle Internet Directory 11g (OID 11.1.1.7). |
|
OAM-based SSO needs a web server. RPAS Fusion Client has been verified to work with Oracle HTTP Server (OHS) 12.1.3. |
|
A web server plug-in (OAM Webgate) communicates with an OAM instance and to create the SSO cookie. OAM Webgate 11.1.2.2 is required. |
|
In summary, the following Oracle Fusion Middleware packages are utilized in the solution:
|
The following notes pertain to the RPAS hardware and software requirements:
Once the RPAS server and client are installed, you must build and set up an RPAS domain or install an RPAS solution. For more information on setting up an RPAS domain, refer to either the Classic Client or Fusion Client version of the Oracle Retail Predictive Application Server Administration Guide. For more information on installing an RPAS solution, refer to the relevant installation guide included with the RPAS solution package.
If you are installing only the Oracle RPAS Fusion Client without any additional applications supported by the Oracle Application Development Runtime, you still need to install the Oracle Database repository schema specified by the Oracle Application Development Runtime installation instructions.
If you are installing the RPAS Server on Windows, you must install Cygwin to emulate UNIX commands (required for starting the RPAS Server on Windows). You can find more information about downloading this product at http://www.cygwin.com
. If running the RPAS Server on Windows, use Windows 7. Perl is an interpreted language that is included on all supported UNIX platforms (included with Cygwin for Windows). Perl is used by the patch sets, which are used to install an RPAS patch.
An application for unzipping (.zip
) components on UNIX must be installed and used for extracting the RPAS Configuration Tools. Unzip is an open source software package that can be used for this process.
Table 1-4 indicates which software components are needed for each task. The reference to Windows refers to Windows 7.
Table 1-4 Software Requirements Notes
Task | Typical User | Platforms | RPAS Server | RPAS Clients | Configuration Tools | Java |
---|---|---|---|---|---|---|
Log in to an existing (built) RPAS domain for the primary purpose of building workbooks |
End User |
Windows |
No |
Yes |
No |
No |
Use the Configuration Tools to create or modify solutions. |
Solution/ Product Administrator |
Windows |
Yes |
No |
Yes |
Yes |
Use the Configuration Tools to build configured solutions. |
Solution/ Product Administrator |
Windows UNIX Linux |
Yes |
No |
Yes |
Yes |
Java can be acquired from www.java.com
for Oracle Solaris and Microsoft Windows or from the respective vendor's Web site for IBM and HP.
Environment variables are automatically set when using the Oracle Retail Installer to install the RPAS components on a UNIX environment.
Array corruption can occur if arrays are truncated due to lack of disk space. To prevent such array corruptions, the following setup is recommended:
Setup an alert to monitor free space available on the disk. If the available disk space falls below a certain threshold, an alert needs to be triggered. These alerts can be setup using simple shell scripts.
For information on the version of the RPAS platform that an RPAS application uses, refer to that application's documentation.
If you are unable to find the necessary version of the required Oracle infrastructure software (database server, application server, WebLogic, and so on.) on the Oracle Software Delivery Cloud, you should file a non-technical ’Contact Us' Service Request (SR) and request access to the media. For instructions on filing a non-technical SR, see My Oracle Support Note 1071023.1 – Requesting Physical Shipment or Download URL for Software Media.
The following table lists terms that are used in this guide.
Term | Definition |
---|---|
RPAS | The Oracle Retail Predictive Application Server provides the foundation for Oracle Retail solutions such as Oracle Retail Demand Forecasting (RDF), Merchandise Financial Planning (MFP), and Advanced Inventory Planning (AIP). RPAS does not include any business logic, but it enables the solutions to store, manipulate and retrieve data. It provides the solutions with a standard interface based on wizards, templates, workbooks, and batch processes. |
RPAS solution | The software that uses RPAS. RPAS solutions are added on to RPAS domains as separate modules. All the business logic is encapsulated in the solution. An RPAS domain can support multiple solutions. |
RPAS domain | The collection of server-side directories and files containing data and procedures that comprise the RPAS solution. For additional information, refer to the Oracle Retail Predictive Application Server Configuration Tools User Guide and the Classic Client and Fusion Client versions of the Oracle Retail Predictive Application Server Administration Guide. |
RPAS Classic Client | The Windows-based client interface for end users and system administrators of an RPAS domain. An administrator may perform maintenance work in a domain using the RPAS Classic Client, server-side RPAS utilities. |
RPAS Fusion Client | The Web-based Rich Client for end users and system administrators of an RPAS domain. An administrator may perform maintenance work in a domain using the RPAS Fusion Client in a browser. This Retail Predictive Application Server (RPAS) platform is developed using the Oracle Application Development Framework (ADF). |
RPAS Configuration Tools | The tools used to configure an RPAS solution. For more information, refer to the Oracle Retail Predictive Application Server Configuration Tools User Guide. |