| Oracle® Retail Demand Forecasting Installation Guide Release 14.1.2 E70806-01 |
|
 Previous |
 Next |
| Oracle® Retail Demand Forecasting Installation Guide Release 14.1.2 E70806-01 |
|
Previous |
Next |
This document provides instructions on installing Oracle Retail Demand Forecasting. It provides detailed instructions on how to install a Demand Forecasting (RDF) domain using a configuration created through the RPAS Configuration Tools. This document does not describe how to create the actual configuration.
|
Note: Supplemental installation guides are referenced in this document. The Oracle Retail Predictive Application Server Installation Guide and Oracle Retail Predictive Application Server Configuration Tools User Guide must be obtained before beginning the installation process. Read these documents in their entirety before starting the installation. |
Read through this document completely before performing the installation steps.
Table 1-1 provides information on the hardware and software requirements for RDF, Curve, and Grade:
Table 1-1 Hardware and Software Requirements
| Requirement | Details |
|---|---|
|
Supported RPAS Version |
14.1.2 |
|
Oracle Retail Batch Script Architecture (BSA) |
14.1.2 |
|
Required Software |
Java Development Kit (JDK) 1.7u91 Note: There are specific JDK versions needed for each of the supported operating systems for the Oracle Retail Predictive Application Server (RPAS). For the list of JDK versions, see the Oracle Retail Predictive Application Server Installation Guide. Note: When installing Java, avoid enabling AutoUpdate because it may update the Java version without prompting. |
|
Note: RPAS applications, such as RDF, run on the Oracle Retail Predictive Application Server (RPAS) platform. For information about the hardware and software requirements for RPAS, see the supported RPAS version of the Oracle Retail Predictive Application Server Installation Guide. |
This sections lists the supported Oracle Retail products for RDF, Curve, and Grade.
Table 1-2 provides information about the supported Oracle Retail products for RDF.
Table 1-2 RDF Supported Oracle Retail Products
| Product | Version |
|---|---|
|
Oracle Retail Advanced Inventory Planning |
14.1.2 |
|
Oracle Retail Analytic Parameter Calculator for Replenishment Optimization (APC-RO) |
14.1.0 |
|
Oracle Retail Analytic Parameter Calculator for Regular Price Optimization (APC-RPO) |
14.1.2 |
|
Oracle Retail Merchandising System (RMS) |
14.1.2 |
|
Oracle Retail Replenishment Optimization (RO) |
14.1.2 |
|
Oracle Retail Regular Price Optimization (RPO) |
14.1.2 |
Table 1-3 provides information about Oracle Retail products that are supported for Curve.
Table 1-4 provides information about Oracle Retail products that are supported for Grade.
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.
|
Note: Oracle Retail Batch Scripting Architecture (BSA) must be installed prior to installing RDF. For information about installing BSA, see the Oracle Retail Batch Script Architecture Implementation Guide. |
The installation of the server-side RPAS components on UNIX operating systems is accomplished using Java-based installation programs that are included with the installation package.
The RPAS Installer automates the following tasks:
Installs the RPAS server components
Installs Configuration Tools on the server
Defines the DomainDaemon port
The RDF Installer automates the following tasks:
Installs the RDF configuration
Installs RDF plug-ins for the Configuration Tools
Installs Language Translation files
Creates a sample RDF domain
|
Note: Refer to chapter, ”Creating a Multi-solution Taskflow” in the Oracle Retail Predictive Application Server Configuration Tools User Guide for information about the Multi-solution Taskflow. |
|
Note: This document assumes that the RPAS Installer process (from the Oracle Retail Predictive Application Server Installation Guide) has been completed prior to using the RDF Installer. |
The RPAS server components required prior to this installation process are available from Oracle's E-Delivery web site, http://edelivery.oracle.com, and My Oracle Support, https://support.oracle.com.
|
Note: Before installing RDF, confirm that RPAS and all subsequent patches have been successfully applied. |
Before running the solution installer, source your retaillogin.ksh script. The script is located in the root of the base directory where RPAS was installed unless the default was overwritten when specifying directory paths.
Source the script from inside the directory where the script is located:
. ./retaillogin.ksh
or
Include the full path after the period and space ”.”:
. /<base_directory>/retaillogin.ksh
|
Note: The preceding period and space (”. ”) must be included at the beginning of the command when running the script. |
|
Note: Include this path and script in the.profile in your home directory (~/.profile) if you want to have this environment setup script run during login. |
This script sets up environment variables, such as RPAS_HOME and RIDE_HOME, which are required for RPAS to run properly.
The following procedure provides information about extracting the RDF/CPEM media pack and its contents:
Create a directory to store the RDF/CPEM media pack and download the media pack to this location. This directory will be referred to as [RDF Installation].
Extract the media pack to this location. Once extracted, two directories appear, CDROM and DOCS.
The CDROM folder contains the following ZIP files:
RDF.zip - This file contains the RDF solution.
CPEM.zip - This file contains the CPEM solution.
The DOCS folder contains the RDF documentation. Within the DOCS you can find the RDF Guides, including:
Release Notes - This folder contains the Oracle Retail Demand Forecasting Release Notes.
Installation Guide - This folder contains the Oracle Retail Demand Forecasting Installation Guide.
|
Note: Files contained within the installation package are intended to be used by the installer only. |
Complete these steps to extract the installation package:
Create a directory to store the RDF/CPEM media pack on the target server. This directory will be referred to as [RDF Installation]. It is the location where the RDF installation routine is run.
Using FTP in binary mode, transfer the RDF/CPEM media pack to the [RDF Installation] directory on the target server.
Extract the package to the [RDF Installation] directory.
cd [RDF Installation]
unzip [RDF Package]
Extract the RDF Installer.
cd CDROM
unzip RDF.zip
Perform the following steps to install RDF.
|
Note: This product's installer includes Ant. If Ant is already installed on your system and is version 1.6.5 or earlier, then you must rununset ANT_HOME on the command line to ensure that the installer uses the included version. The unset ANT_HOME command must be run before ./install.sh. |
Begin the Installer by first changing to the root of the [RDF Installation] directory and running the following command:
./install.sh
|
Note: The command must be run with the preceding period and slash (./). |
If this process is being run on an X-Windows emulator (such as Exceed), a GUI to the Installer appears. If you are running in console mode through a terminal emulator, a text interface to the Installer appears.
In both cases, the requested information is identical, but displayed differently. In the GUI, a check box may appear to signal whether or not you want a component installed. In text mode, a response of yes or no may be required.
|
Note: In text mode, the default value appears in square brackets. To use the default value and continue, click Enter. If you want to use a different value, enter the new value. When prompted to create a directory, respond with Y or yes and click Enter. |
The RDF Installer Window opens and shows the components that are installed during installation process as well as other required components. Click Next to continue.
|
Note: Oracle Retail Batch Scripting Architecture (BSA) must be installed prior to installing RDF. For information about installing BSA, see the Oracle Retail Batch Script Architecture Implementation Guide. |
|
Note: When logging is on and the verbose setting is used for the new 3rd party approved version of Java Secure Channel (JSch), the following message displays, ”Caught an exception, leaving main loop due to Socket closed”.This message has no impact on the installer and should be ignored. |
The RDF Choose Components to Install Window opens.
Select one or both of the following options:
RDF – Select this option to install the RDF solution with the domain.
RPAS Fusion Client configuration – Select this option to install the RPAS Fusion Client RDF configuration.
| If You Are... | Then.... |
|---|---|
| Not installing the RPAS Fusion Client RDF configuration. | Clear the RPAS Fusion Client configuration check box and skip steps 6 and 7. |
| Not installing the RDF solution, but are installing the RPAS Fusion Client RDF configuration. |
|
Click Next to continue.
The RDF Base Paths for Solution Window opens.
|
Note: Ensure that the installation paths are located outside of the installer directory [RDF_Installer]. |
Enter the following path information and click Next:
Dir to store configurations - Enter the target directory to store the configurations.
Dir to store created domains - Enter the target directory used to store created domains.
Path and file name to the retaillogin.ksh script - Enter the path and file name where the retaillogin.ksh script was created during RPAS installation.
The RDF Install Tasks Window opens.
| If You Want to.... | Then.... |
|---|---|
| Create the RDF domain | Select Create RDF Domain and click Next. |
| Install all required components to support the RDF domain, but not create the actual RDF domain | Clear the Create RDF Domain check box and click Next. |
|
Note: Domain builds use the environment specified in theretaillogin.ksh environment setup script. If you change any environment details, edit the retaillogin.ksh script and any subsequent scripts called by retaillogin.ksh.
For more information about the |
The RDF Fusion Location Information Window opens.
Enter the relevant information in the following fields:
| Field | Description |
|---|---|
| Enter the number of RPAS Fusion Client servers to install these configurations on: (1-4) | Enter the number of servers running the RPAS Fusion Client where you want to install the RDF configuration. In case the RPAS Fusion Client is running on a single server, enter 1. If you have a clustered installation, you can enter up to four servers |
| Enter the RPAS server hostname: | Enter the hostname of the RPAS server. |
| Enter the RPAS server port: | Enter the port number of the RPAS server. |
| RPAS Solution Path | Enter the location of the RPAS domain for RDF. |
|
Note: The RDF Fusion Location Information Window opens when you select the RPAS Fusion Client configuration check box on the Choose Components to Install Window.If you are not installing the RPAS Fusion Client configuration, proceed to step 8. |
Click Next to continue.
Based on the number of servers you entered, the RDF Fusion Location Information (Details) Window opens.
Enter the server details in the following set of fields for each configuration:
| Field | Description |
|---|---|
| Hostname or IP | Enter the host name or IP address of the server where the RPAS Fusion Client is installed. |
| Configuration Directory | Enter the location of the config directory available at the location where the RPAS Fusion Client is installed. |
| Login username | Enter the user name to log on to the server where the RPAS Fusion Client is installed. |
| Login password | Enter the password associated with the user name. |
| Login username alias | Specify an alias name for the administrative user. Specifying an alias name for the administrative user enhances the security for the application. When left blank, the alias name defaults to the administrative user name. |
|
Note: Information such as user credentials for the RPAS Fusion Client is encrypted and stored in a secure location in the application installation directory. This location is called the Oracle Wallet.When the installation starts, the administrative user credentials are retrieved from the Oracle Wallet based on the alias name specified in this window. |
Click Next to continue.
The RDF Installation Progress Window opens.
To display the progress of the components and tasks being performed by the Installer, click Show Details. Click Install to start the installation process.
You can view the detailed mode at any time during or after the installation.
|
Note: If you chose to create the RDF global domain, installation time might take 30 to 60+ minutes depending on server specifications. |
When the installation process is complete, the RDF Complete Window opens a Message dialog box. Click OK to close the dialog box.
To view the installation details, click Show Details. The window displays two tabs, the Output tab and the Error tab. It is recommended that you review these tabs for any issues that may have occurred during the installation process.
If you wish to view the log again at a later date, a text copy was saved in the directory [RDF Installation]. The log file is named based on the product and time installer, followed by the.log extension.
The make_domain.rdf file, located in the [Configurations Install Dir] entered during the install, is created during the installation process. This file contains all of the required parameters needed to support domain installation. If necessary this file may be modified if the default parameters are not appropriate for your particular environment.
|
Note: When reviewing Installer output or logs, you may see the following message: [scp] Caught an exception, leaving main loop due to Socket closed. This message is harmless and does not indicate failure. |
|
Note: The domain install process also includes postinstallation data loading scripts specific to the RDF configuration. These scripts may also be modified. |
Click Exit to close the Installer.
After you have installed RDF, perform the following postinstallation tasks.
Start the DomainDaemon.
If you are on AIX and you have re-installed RDF, you must edit a help file to use the RDF online help in the RPAS Fusion Client. Manually edit the [fusion client installation dir]/config/Help/ohwconfig.xml file by removing the following duplicate line:
<helpSet xmlns="" id="<shortProductName>" location="<shortProductName>/<shortProductName>-help.hs"/>
|
Caution: If this duplicate line is not removed, a ”500 Page Not Found” error occurs when attempting to access the online help in the RPAS Fusion Client. |
This section describes the optional installation method that involves setting up the RPAS Fusion Client configuration and online help for the RDF configuration. If you chose to install the Fusion Client configuration files using the RDF installer, you can skip this section.
|
Note: Before proceeding, ensure that you have appropriate access privileges on the server running the RPAS Fusion Client. |
Along with the files to install the RDF solution and domain, the RDF/CPEM installation media pack also includes the RPAS Fusion Client configuration and online help files that you must install if you want to use RDF on the RPAS Fusion Client.
These files are available at the following location within the [RDF Installation] directory:
[RDF Installation]/rdf/fusion<server-name>{RPASServerName}</server-name>
During the RDF installation, these files are automatically copied over to the configuration directory where the RPAS Fusion Client is installed. The installation also ensures that the following RPAS Fusion Client configuration files are updated to reflect the RDF installation:
Foundation.xml - Located in the [RPAS Fusion Client Installation]/ config/rpas directory, this XML file includes the domain configuration available for use with the RPAS Fusion Client.
ohwconfig.xml - Located in the [RPAS Fusion Client Installation]/config/Help directory, this XML file includes the online help configuration for the RPAS Fusion Client.
If you did not install the Fusion Client configuration files during the RDF installation, you can choose to do one of the following tasks:
Run the RDF installer again, and select to install only the RPAS Fusion Client configuration.
Run the RPAS Fusion Client installer again, and specify the RDF domain configuration. For more information on the RPAS Fusion Client installation, refer to the Oracle Retail Predictive Application Server Installation Guide.
Configure the RPAS Fusion Client for RDF manually. For more information, refer to the ”Configuring Additional Domains” section in the Oracle Retail Predictive Application Server Administration Guide for the Fusion Client.
This section provides information about the files needed for taskflow configuration.
If you selected the option to build a domain, you will find two taskflow files (taskflow.xml and the taskflowBundle.properties resource file) in the fusionClient subdirectory within the domain. For information about how to use these files to configure the Multi-solution Taskflow, refer to the section, ”Postinstallation Configuration” in the Oracle Retail Predictive Application Server Administration Guide for the Fusion Client.
If you selected the option to install the fusion client configuration, the translation files for the taskflow have been copied to [RPAS Fusion Client Installation]/resources. For information about how to use these files with the Multi-solution Taskflow, refer to the section, ”Creating a Multi-solution Taskflow” in the Oracle Retail Predictive Application Server Configuration Tools User Guide.
