2 Full Installation: UNIX Environment

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 Item Planning Configured for COE Installer automates the following:

• Installation of the Item Planning Configured for COE configuration

• Installation of the Item Planning Configured for COE 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.

• Creation of a sample Item Planning Configured for COE 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 Item Planning Configured for COE 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, source 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 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 sets up the environment variables, such as RPAS_HOME and RIDE_HOME, which are required for RPAS to run properly.

Important: Ensure that you set up the RPAS_JAVA_CLASSPATH environment variable. For more information, see the COE Expression Runtime Environment section in the chapter Item Planning Configured for COE of the Oracle Retail Item Planning Operations Guide. 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 IP COE Media Pack

The following procedure provides information about extracting the Item Planning Configured for COE media pack and its contents.

1. Create a directory to store the Item Planning Configured for COE media pack and download the media pack to this location. This directory is referred to as [IPCOE Installation].

2. Download and extract the media pack to this location. Once extracted, two directories appear: CDROM and DOCS.

   • The CDROM folder contains the itemcoe.zip file, which contains the Item Planning Configured for COE solution.

   • The DOCS folder contains the Item Planning Configured for COE documentation.

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

Installing IP COE

Perform the following steps to install Item Planning Configured for COE.

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. Extract the Item Planning Configured for COE Installer from the [IPCOE Installation] directory.

   cd CDROM

   unzip itemcoe.zip

2. From the [IPCOE Installation]/CDROM directory, run the following commands to run the Item Planning Configured for COE Installer:

   cd itemcoe

   ./install.sh

   
   

   Note: The command must be executed 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 true or false.

   
   

   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.

   
   

3. The Item Plan Configured for COE Installer Window opens and displays the components that are installed during installation process and the required components.

   Click Next to continue.

   
   

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

   
   

   Figure 2-1 Item Plan Configured for COE Installer Window

   
   

4. The Choose Components to Install Window opens.

   Figure 2-2 Choose Components to Install Window

   
   

   Select one or both of the following options:

   • Item Plan for COE Server — Select this option to install the Item Planning Configured for COE server with the domain.

   • RPAS Fusion Client configuration — Select this option to install the RPAS Fusion Client configuration for Item Planning Configured for COE. 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 7 and 8.

   
   

   Click Next to continue.

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

   • Path to existing 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 the installer directory [IPCOE Installation].

   
   

   Click Next to continue.

6. The Install Tasks Window opens.

   Figure 2-4 Install Tasks Window

   
   

   Select or clear the Create Item Plan COE Domain option:

   • To create the IP COE domain, select the Create Item Plan COE 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.

     
     

   • To support the IP COE domain, but not create the actual domain, clear this check box.

   Click Next to continue.

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

   
   

   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 IP COE 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 IP COE.

   
   

   Click Next to continue.

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

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

10. When the installation has finished, the Finished message opens. Click OK.

11. 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 is saved in the directory [IPCOE Installation]. The log file is named based on the product and timestamp, followed by the.log extension.

    Created as part of this process is the make_domain.itemplan file located in [Solution Install Dir] entered previously. This file contains the required parameters needed to support the 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 may also include postinstallation data loading scripts specific to the Item Planning Configured for COE 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.

    
    

12. Click Exit to close the Installer.

Postinstallation Configuration

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

Environment Variables

Set your IP_HOME environment variable.

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

export IP_HOME=[Solution Install Dir]

WebLogic Libraries

IP COE requires the following Java libraries from the WebLogic server as listed in the following table:

• Libraries numbered 1-9 are available after unzipping the $WEBLOGIC_HOME/server/lib/wseeclient.zip file.

• Libraries numbered 10-12 can be copied from the $WEBLOGIC_HOME/server/lib/ directory.

• Library number 13 (wlfullclient.jar) should be built from the $WEBLOGIC_HOME/server/lib/ directory using the command, java -jar wljarbuilder.jar.

Number	Java Library	Location
1	com.bea.core.descriptor.wl.binding_1.3.0.0.jar	$WEBLOGIC_HOME/server/lib/wseeclient.zip
2	com.bea.core.descriptor.wl_1.3.0.0.jar	$WEBLOGIC_HOME/server/lib/wseeclient.zip
3	com.bea.core.xml.beaxmlbeans_1.1.0.0_2-4-1.jar	$WEBLOGIC_HOME/server/lib/wseeclient.zip
4	com.bea.core.xml.staxb.buildtime_1.4.1.0.jar	$WEBLOGIC_HOME/server/lib/wseeclient.zip
5	com.bea.core.xml.xmlbeans_1.1.0.0_2-4-1.jar	$WEBLOGIC_HOME/server/lib/wseeclient.zip
6	com.bea.core.xml.weblogic.xpath_1.4.0.0.jar	$WEBLOGIC_HOME/server/lib/wseeclient.zip
7	glassfish.jaxws.rt_1.1.0.0_2-1-4.jar	$WEBLOGIC_HOME/server/lib/wseeclient.zip
8	javax.xml.bind_2.1.1.jar	$WEBLOGIC_HOME/server/lib/wseeclient.zip
9	javax.xml.ws_2.1.1.jar	$WEBLOGIC_HOME/server/lib/wseeclient.zip
10	weblogic.jar	$WEBLOGIC_HOME/server/lib/ directory
11	webservices.jar	$WEBLOGIC_HOME/server/lib/ directory
12	xqrl.jar	$WEBLOGIC_HOME/server/lib/ directory
13	wlfullclient.jar	$WEBLOGIC_HOME/server/lib/ directory using java -jar wljarbuilder.jar

Assume the Weblogic Java libraries are copied into IP_HOME/javatools/lib directory.

Then the RPAS_JAVA_CLASSPATH environment variable which is used to provide the classpath for the classes used by the Java special expression should be set as:

export RPAS_JAVA_CLASSPATH="$RPAS_HOME/lib/oracleRpasUtils.jar;$IP_HOME/java/lib/coeexpression_owl.jar;$IP_HOME/javatools/lib/com.bea.core.descriptor.wl.binding_1.4.0.0.jar;$IP_HOME/javatools/lib/com.bea.core.descriptor.wl_1.4.0.0.jar;$IP_HOME/javatools/lib/com.bea.core.xml.beaxmlbeans_2.5.0.0_2-5-1.jar;$IP_HOME/javatools/lib/com.bea.core.xml.staxb.buildtime_1.6.0.0.jar;$IP_HOME/javatools/lib/com.bea.core.xml.xmlbeans_2.2.0.0_2-5-1.jar;$IP_HOME/javatools/lib/glassfish.jaxws.rt_1.3.0.0_2-1-5.jar;$IP_HOME/javatools/lib/javax.xml.bind_2.1.1.jar;$IP_HOME/javatools/lib/javax.xml.ws_2.1.1.jar;$JAVA_HOME/lib/tools.jar;$IP_HOME/javatools/lib/weblogic.jar;$IP_HOME/javatools/lib/webservices.jar;$IP_HOME/javatools/lib/wlfullclient.jar;$IP_HOME/javatools/lib/xqrl.jar;$IP_HOME/javatools/lib/com.bea.core.xml.weblogic.xpath_1.5.0.0.jar;$IP_HOME/retailpublicsecurityapi/lib/retail-public-security-api.jar;$IP_HOME/java/lib/ant.jar;$RPAS_JAVA_CLASSPATH"

Online Help File

If you are on AIX and you have re-installed IP COE, you must edit a help file to use the IP COE 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 IP COE configuration. If you chose to install the Fusion Client configuration files using the IP COE 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 Item Planning Configured for COE solution and domain, the IP COE installation media pack also includes the RPAS Fusion Client configuration and online help files that you must install if you want to use IP COE on the RPAS Fusion Client.

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

[IPCOE Installation]/itemplancoe/fusion<server-name>{RPASServerName}
</server-name>

During the Item Planning Configured for COE 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 Item Planning Configured for COE 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 IP COE installation, you can choose to do one of the following tasks:

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

• Run the RPAS Fusion Client installer again, and specify the IP COE 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 IP COE 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