2 Full Installation: UNIX Environments

The installation of the server-side RPAS components on UNIX operating systems is accomplished using a Java-based installation program that is included with the installation package.

The RPO Installer automates the following:

• Installation of the RPO configuration

• Installation of the RPO configuration for the RPAS Fusion Client. For more information on installing the RPAS Fusion Client, refer to the Oracle Retail Predictive Application Server Installation Guide.

• Custom configuration of make_domain.rpo script for creating domains

• Creation of sample RPO domain

This document assumes that the RPAS Installer process (from the Oracle Retail Predictive Application Server Installation Guide) has been completed prior to using the RPO Installer.

Preparation

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.

Environment Variable Setup

Before running the solution installer, run the 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

Notes: The preceding period and space (”. ”) must be included at the beginning of the command when running the script. 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.

Note: There are additional Java environment variables that must be set for your particular operation system. These variables are the same for all applications on RPAS. See the ”Java Environment” section of the Oracle Retail Predictive Application Server Installation Guide for these environment variables.

Extracting the RPO Media Pack

Perform the following procedure to extract the installation package.

1. Create a directory to store the RPO media pack and download the media pack to this location. This directory is referred to as [RPO Installation].

2. Extract the media pack to this location. After it is extracted, two directories appear: CDROM and DOCS.

   • The CDROM folder contains the rpo.zip file. This zip file contains the RPO solution.

   • The DOCS folder contains the RPO documentation.

Note: Files contained within the installation package are intended to be used by the installer only.

Installing RPO

Perform the following steps to install RPO.

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 run unset 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.

1. Create a directory to store the RPO media pack on the target server. This directory will be referred to as [RPO Installation]. It is the location where the RPO installation routine is run.

2. Using FTP in binary mode, transfer the RPO media pack to the [RPO Installation] directory on the target server.

3. Extract the package to the [RPO Installation] directory.

   cd [RPO Installation]

   unzip [RPO Media Pack]

4. Extract the RPO Installer.

   cd CDROM

   unzip rpo.zip

5. Change directories to the root of the [RPO Installation] directory and run the RPO Installer:

   cd rpo

   ./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), graphical user interface to the Installer appears. If you are running in console mode through a terminal emulator, the text interface to the Installer appears.

   In both cases, the requested information is identical. In the GUI, you may be shown a check box to signal whether you want a component installed; in text mode, you are prompted for a response of Yes or No.

   
   

   Note: In text mode, the default value appears in square brackets []. To use the default value and continue, press Enter. If you want to use a different value, enter the new value. When prompted to create a directory, respond with Yes and press Enter.

   
   

6. The Regular Price Optimization Installer Window opens and displays the components that are installed during the installation process, as well as the required components.

   Click Next to continue.

   
   

   Note: Oracle Retail Batch Scripting Architecture (BSA) must be installed prior to installing RPO. For information about installing BSA, see the Oracle Retail Batch Script Architecture Implementation Guide.

   
   

   Figure 2-1 Regular Price Optimization Installer Window

   
   

7. The Choose Components to Install Window opens.

   Figure 2-2 Choose Components to Install Window

   
   

   Select the following options:

   • Regular Price Optimization – Select this option to install the RPO server with the domain.

   • RPAS Fusion Client configuration – Select this option to install the RPAS Fusion Client configuration for RPO. For more information on the configuration files included for the RPAS Fusion Client, see Configuration Files for the RPAS Fusion Client.

   
   

   Note: If you do not want to install the RPAS Fusion Client configuration, clear this check box and skip steps 10 and 11.

   
   

   Click Next to continue.

8. The Base Paths for Solution Window opens.

   Figure 2-3 Base Paths for Solution Window

   
   

   Enter the relevant information in the following fields:

   • Dir to store solution - Enter the directory path where your solution should be stored.

   • RegPrice domain path - Enter the directory path where domains for this solution should be stored.

   • Path to retaillogin.ksh script - Enter the path and file name to the retailogin.ksh script created during RPAS installation.

   
   

   Note: Ensure that the installation paths are located outside the installer directory [RPO Installation].

   
   

   Click Next to continue.

9. The Install Tasks Window opens.

   Figure 2-4 Install Tasks Window

   
   

   Select or clear the Create RegPrice Domain check box:

   • If you want to create the RPO domain, select the Create RegPrice Domain option, which is selected by default.

     
     

     Note: Domain builds use the environment specified in the retaillogin.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 retaillogin.ksh script, see the Environment Variable Setup section.

     
     

   • If you want to install all required components to support the RPO domain, but not create the actual RPO domain, clear the check box.

   Click Next to continue.

10. The Fusion Location Information Window opens.

    
    

    Note: The Fusion Location Information windows open 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 12.

    
    

    Figure 2-5 Fusion Location Information Window

    
    

    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 RPO 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 RPO.

    
    

    Click Next to continue.

11. Based on the number of servers you entered, the Fusion Location Information (Details) Window opens.

    Figure 2-6 Fusion Location Information (Details) Window

    
    

    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.

    
    

    Click Next to continue.

    
    

    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.

    
    

12. The Installation Progress Window opens. To start the installation, click Install.

    Figure 2-7 Installation Progress Window

    
    

    This window also displays the progress of the installation routine. Click Show Details to view the log output as the installation is performed. If you do not select to view the details, a graphical representation of the installation steps appears. As each step is completed, the color changes to show you the progress.

    You can toggle between detailed mode at any time during or after the installation.

13. When the installation has finished, the Finished window opens. Click OK.

14. 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 want to view the log again at a later date, a text copy was saved in the directory where you initiated the installation from [RPO Installation]/CDROM/rpo. The log file is named based on the product and a timestamp, followed by the.log extension.

    Created as part of this process is the make_domain.rpo file, located in the [Dir to store configurations] entered previously. This file contains all of the required parameters needed to support the domain installation process. If necessary, this file may be modified if the default parameters are not applicable 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 may also include postinstallation data loading scripts specific to the RPO configuration. These scripts, if present, may also be modified. For additional information on installing RPAS domains manually, see to the Oracle Retail Predictive Application Server Installation Guide.

    
    

15. Click Exit to close the Installer.

Postinstallation Tasks

If you are on AIX and you have re-installed RPO, you must edit a help file to use the RPO 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.

Configuration Files for 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 RPO configuration. If you chose to install the Fusion Client configuration files using the RPO 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 RPO solution and domain, the RPO installation media pack also includes the RPAS Fusion Client configuration and online help files that you must install if you want to use RPO on the RPAS Fusion Client.

These files are available at the following location within the [RPO Installation] directory:

[RPO Installation]/rpo/fusion

<server-name>{RPASServerName}</server-name>

During the RPO 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 RPO 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 RPO installation, you can choose to do one of the following tasks:

• Run the RPO installer again, and select to install only the RPAS Fusion Client configuration.

• Run the RPAS Fusion Client installer again, and specify the RPO 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 RPO manually. For more information, see the ”Configuring Additional Domains” section in the Oracle Retail Predictive Application Server Administration Guide for the Fusion Client.

Taskflow Files

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.