2 Full Installation on 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 RO Installer automates the following:

Installation of the RO configuration
Custom configuration of make_domain.ro script for creating domains
Creation of a sample RO 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 RO Installer.

Note:

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

Preparation

The RPAS components required prior to this installation process are available from Oracle's E-Delivery Web site, http://edelivery.oracle.com/">>http://edelivery.oracle.com/, and My Oracle Support, https://support.oracle.com.">>https://support.oracle.com.

If you are installing any RPAS solution on HP Itanium or Sun 10, you need to set the 64-bit Configuration Tools environment variable for Java as shown:

export RIDE_OPTIONS=-d64

Environment Variable Setup Script

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

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 executing 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 will set up environment variables, such as RPAS_HOME and RIDE_HOME, which are required for RPAS to run properly.

Additional Required Environment Variables

In addition to the execution of retaillogin.ksh, export the following environment variables prior to starting your installer.

Note:

The commands listed in this section are an example based on common Java installation structures. To ensure that you are adding the correct path, use the Unix find command to locate libjvm.so (find $JAVA_HOME -name libjvm.so) and adjust the paths as appropriate.

All Platforms

Export:

RPAS_JAVA_CLASSPATH="$RPAS_HOME/applib/aaijni.jar:$RPAS_HOME/applib/aaiReplenOpt.jar"

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.

Downloading and Extracting the Replenishment Optimization Media Pack

The following procedure provides information about downloading and extracting the RO media pack and its contents.

Create a directory to store the RO media pack on the target server. This directory is referred to as [RO Installation]. It is the location where the Replenishment Optimization installation routine is run.
Download the RO Media Pack from Oracle E-Delivery, and transfer the archive to the [RO Installation] directory on the target server using FTP. Use binary mode to transfer the archive.
Extract the main package to the [RO Installation] directory.
cd [RO Installation] unzip ro-13_4_0.zip
Extract the RO Installer.

cd CDROM upzip [RO Media Pack]

Note:

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

Installing Replenishment Optimization

Perform the following steps to install RO.

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.

Change to the RO Installer directory and run the following command:

cd ro
./install.sh

Note:

The command must be executed with the preceding period and slash (./).

If this process is performed on an X-Windows emulator (such as Exceed), a graphical user interface to the Installer opens. If you are running in console mode through a terminal emulator, a text interface to the Installer opens.

In both cases, the requested information is identical but displayed differently. 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 true or false.

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 RO Installation 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 RO. For information about installing BSA, see the Oracle Retail Batch Script Architecture Implementation Guide.

Figure 2-1 RO Installation Window

The Choose Components to Install Window opens.

Figure 2-2 Choose Components to Install Window

Select the following options:
- Replenishment Optimization — Select this option to install the RO server with the domain.
- RPAS Fusion Client configuration — Select this option to install the RPAS Fusion Client configuration for RO. 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 6 and 7.

Click Next to continue.

The Base Paths for Solution Window opens.

Figure 2-3 Base Paths for Solution Window

Enter the relevant information in the following fields and click Next to continue:

Field	Description
Dir to store solution	Enter the directory path where your solution should be stored.
Path to retaillogin.ksh script	Enter the path and file name to the `retaillogin.ksh` script created during RPAS installation.

Note:

Ensure that the installation paths are located outside of the installer directory [RO Installation].

The Install Tasks Window opens.

Figure 2-4 Install Tasks Window

Select or clear the Create RO Domain check box:

If you want to create the RO domain, select the Create RO Domain option, which is selected by default.
If you want to install all required components to support the RO domain, but not create the actual domain, clear the check box.

Note:

If you are not installing the RPAS Fusion Client configuration, proceed to step 8.

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, refer to the section: "Environment Variable Setup Script".

Click Next to continue.

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

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

Click Next to continue.

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.

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 Installation Progress Window opens. To start the installation, click Install.

Figure 2-7 Installation Progress Window

This window displays installation progress. Click Show Details if you want to view the log output as the installation is performed. If you choose not to view the details, a graphical representation of the installation steps opens. As each step is completed, the text color changes to indicate installation progress.

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

When the installation process is finished, the Complete window opens. Click OK.

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.

If you viewed the installation through the graphical progress, you can now click Show Details to view the logs.
Once you are finished reviewing the installation, click Exit to close the installer application.
If you wish to view the log at a later date, a text copy was saved in the directory where you initiated the installation from [RO Installation]/CDROM/ro. The log file is named based on the product and a timestamp, followed by the.log extension.

Domain Scripts

Created as part of the installation process is a sample domain creation script, located in the [Dir to store configurations] entered previously. This file is named make_domain.ro. 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:

The domain installation process also includes postinstallation data loading scripts specific to this configuration. These scripts may also be modified.

Postinstallation Tasks

Before starting the DomainDaemon, you must first set the following environment variables and online help files.

Environment Variables

Set your RO_HOME environment variable and source the solution's environment.ksh script. This loads all environment variables required by RPAS to interact with your solution's workbooks.

To do this, either in shell or with an addition to your.profile, add:

export RO_HOME=[Solution Install Dir] . [Solution Install Dir]/bin/ro_environment.sh.

Online Help File

If you are on AIX and you have re-installed RO, you must edit a help file to use the RO 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 RO configuration. Skip this section if you chose to install the Fusion Client configuration files using the RO installer.

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 Replenishment Optimization solution and domain, the Replenishment Optimization installation media pack also includes the RPAS Fusion Client configuration and online help files that you must install if you want to use Replenishment Optimization on the RPAS Fusion Client.

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

[RO Installation]/replen_opt/fusion

During the Replenishment Optimization 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 Replenishment Optimization 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 do not install the Fusion Client configuration files during the Replenishment Optimization installation, you can choose to do one of the following tasks:

Run the Replenishment Optimization installer again, and select to install only the RPAS Fusion Client configuration.
Run the RPAS Fusion Client installer again, and specify the Replenishment Optimization 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 RO 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.