Oracle® Retail Analytic Parameter Calculator for Regular Price Optimization Installation Guide Release 14.1.2 E70803-01 |
|
![]() Previous |
![]() Next |
This chapter describes how to upgrade APC-RPO from a previous release to Release 14.1.2.
In order to upgrade APC-RPO, first verify the following criteria for the RPAS system:
Verify that RPAS is currently installed and is at Release 13.3 or later. If not, refer to the section, Upgrade to Key RPAS Versions.
Verify that the UNIX operating system is updated to the currently supported version. Refer to the ”Hardware and Software Requirements” section of the Oracle Retail Predictive Application Server Installation Guide.
Verify that the environment variables are correctly set for both the server and PC; if they are not, follow these instructions to set them:
Change directories to the original RPAS installation directory (such as the one created by the most recent installer), and run retaillogin.ksh
to set all environment variables. For example:
$ cd /retail$ . ./retaillogin.ksh
Notes: After you have run the script, verify that the environment variables all point to the correct locations on your environment.If you have updated Java since the last installation of RPAS, verify that the JAVA_HOME path is correct. If not, update your |
The following process outlines how to upgrade APC-RPO to the latest version using the RPAS Configuration Tools.
Before you upgrade to a post-13.3 release, ensure that you have upgraded and patched to RPAS Release 13.2.3.
This list defines the upgrade process that is described in the following sections.
Upgrading your domain to a 13.3 or later RPAS domain requires that you first upgrade it to a 13.2.3 domain. For instructions, see the ”Upgrading and Patching Domains” section in the 13.2.3 release of either the Classic Client or Fusion Client version of the Oracle Retail Predictive Application Server Administration Guide.
After upgrading, you must run a configuration patch over the domain to ensure compatibility with the RPAS version, regardless of whether there are any configuration changes.
Upgrading to a 13.3 or later RPAS domain requires the use of the convertDomain utility, which may not copy the entire contents of the source domain to the destination domain. For files that are not copied by convertDomain, you may need to copy them manually.
For information about what is and is not copied, see the ”convertDomain” section in the 13.3 release of either the Classic Client or Fusion Client version of the Oracle Retail Predictive Application Server Administration Guide.
The following process outlines how to upgrade APC-RPO to the current version using the RPAS Configuration Tools.
Note: After upgrading, you must run a configuration patch over the domain to ensure compatibility with the latest RPAS version, regardless of whether there are any configuration changes. |
Follow these instructions for the PC to upgrade to the current version:
Open RPAS Configuration Tools.
In RPAS Configuration Tools, load your previous configuration of APC-RPO:
From the Configuration Tools File menu, select Open.
From the Open window, locate the configuration file and click Open.
If your configuration requires updating, dialog boxes will prompt you to upgrade. Follow the instructions given in the dialog boxes.
In the RPAS Configuration Tools File menu, click Save to save the configuration.
Zip the configuration in Cygwin and transfer the.zip
file to the RPAS server.
Follow these instructions for the server to upgrade to the current version:
Upgrade the RPAS server and the RPAS Fusion Client configuration by running the installer:
Begin the installer as described in the Installing Analytic Parameter Calculator for Regular Price Optimization section.
At step 6, the Install Tasks Window, clear the Create APCRPO Domain option.
Finish the remaining steps of the installer.
Unzip the updated configuration and note where it is saved.
Upgrade your APC-RPO domain to a 14.1.2 domain. Run the following command:
buildAPCRPO.sh -d <domain path> -c <config path> -i <input path> -l <log path> -p
Table 3-1 Supported Parameters for buildAPCRPO.sh
Flag | Where: | Is the Path for the: | Default Value* |
---|---|---|---|
-c |
<config path> |
configurations |
$PWD/../config |
-i |
<input path> |
input files |
$PWD/../input |
-l |
<log path> |
log file |
$PWD/../ |
-d |
<domain path> |
domain |
$PWD/../domain |
-m |
<max process#> |
number of max processes for loading measures |
1 |
-f |
<log file > |
log file |
build_domain.log |
-p |
<make patch build > |
domain patching |
none |
-u |
<show usage of this script> |
show usage of this script |
none |
-n |
<configName> |
configuration name |
APCRPO |
-r |
<partionDimension> |
partion dimension |
pgrp |
* Where $PWD is the current directory |
Note: The flag-p must be used for domain patching. |
Note: This script is only a sample script for the APC-RPO domain build or patch. You can write your own script as needed. |