A Patching RDF Domains

Before patching an RDF domain, confirm that the necessary RPAS client, server and Configuration Tools patch updates have been successfully applied. Refer to the Oracle Retail Predictive Application Server Installation Guide for RPAS installation instructions.

Patching an RDF Domain

Note: When patching an RDF domain, you need the same -rf arguments of rpasInstall as a full install of the domain (For example: -rf AppFunctions -rf RdfFunctions -rf LostSaleFunctions -rf ClusterEngine)

Complete the following steps to patch your RDF domain.

Note: The RDF plug-in now supports changing forecast level intersections in patching. This enhances the currently existing ability to change forecast data sources. However, the RDF plug-in does not support addition or removal of forecast or promotion levels.

1. Extract the RDF patch.

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

   2. Download the package from My Oracle Support (https://support.oracle.com). Using FTP in binary mode, transfer the RDF/CPEM media pack to the [RDF Installation] directory on the target server.

   3. Extract the package to the folder [RDF Installation] directory.

      cd [RDF Installation]

      unzip [RDF Package]

   4. Extract the RDF Installer.

      cd CDROM

      unzip RDF.zip

2. Copy the RDF plug-in to the Configuration Tools.

   The RDF plug-in enables the RDF solution to be configured using the RPAS Configuration Tools. It also supports the domain installation process.

   1. Locate the plug-in directory by changing to the root of the [RDF Patch Install] directory.

   2. Navigate to [RDF Patch Install]/CDROM/rdf/rdf/plugin/ and copy the resources directory to the Configuration Tools installation ($RIDE_HOME).

3. Delete or rename old activities before running regeneration.

   The RDF plugin regeneration generates task flow activities with the same label as the old activities. So either delete or rename the old activities before running regeneration so that RDF can distinguish the old activities from the new ones.

   1. Locate the taskflow in the Configuration Tools.

   2. In the Taskflow Manager, right-click on each taskflow and change the name for each one as shown in the following images.

      Figure A-1 Taskflow Name Change Before

      
      

      Figure A-2 Taskflow Name Change After

      
      

4. Using the Configuration Tools on a Windows machine, auto-generate the RDF, Curve, Promote, or Grade solutions that are implemented.

   It is necessary to open the configuration in the patched version of the RPAS Configuration Tools and autogenerate each of the existing solution extension configurations on a Windows machine. This auto-generation step is also required if you are making a change to your existing configuration of a RDF, Curve, Promote, or Grade solution.

5. Copy the configuration files to the domain server.

   • Copy the updated configuration files from the Windows machine to the domain server. The location on the domain server should have the same structure as the Windows machine used to autogenerate the solution extensions.

   • If you are using WinZip to archive the configuration files, you must use unzip -a to unzip the archive on the UNIX server.

6. If you do not specify domain paths during the RPAS patching process, then run the RPAS upgradeDomain utility.

   For information on the upgradeDomain utility, refer to either the Classic Client or Fusion Client version of the Oracle Retail Predictive Application Server Administration Guide.

7. To patch the RDF domain:

   1. Set $RDF_HOME

      export RDF_HOME=$RPAS_HOME

   2. Verify BSA/bsa folder exists within $RPAS_HOME/bin

   3. Edit the following path parameters, then copy/paste entire section on the command line (selecting either patch or build).

      
      

      Note: Run the script from the $RPAS_HOME/bin directory. For additional information about the buildRDF.sh parameters, refer to Table 2-2.

      
      

      [Patch]

      (m = # of maxProcesses) (p = indicates patchInstall)

      buildRDF.sh \

      -c /configPath \

      -i /inputPath \

      -l /logPath \

      -f patch_domain.log \

      -d /domainPath \

      -m 2 \

      -p

      [Build]

      buildRDF.sh \

      -c /configPath \

      -i /inputPath \

      -l /logPath \

      -f build_domain.log \

      -d /domainPath \

      -m 2

   4. CD to BSA log file path, then tail to verify running successfully

      /home/user/temp/logs

   5. Verify that the rpasInstall script is called within the BSA log

      Ex: 10:45:39: INFORMATION : buildRDF.sh[202] - _call run command 'rpasInstall -patchinstall -ch /vol.nas/rpas_qc/qc_testing/RDF/aix61/13.4/Rahman/patch/config -cn RDF -in /vol.nas/rpas_qc/qc_testing/RDF/aix61/13.4/Rahman/input -log /vol.nas/rpas_qc/qc_testing/RDF/aix61/13.4/Rahman/patch/domains/1323_1340/patch_domain.log -dh

      /vol.nas/rpas_qc/qc_testing/RDF/aix61/13.4/Rahman/patch/domains/1323_1340 -verbose -p pgrp -rf AppFunctions -rf RdfFunctions -rf ClusterEngine -rf LostSaleFunctions -rf ASOExpressions'

   6. CD to log file specified in script parameters, then tail to verify successful run

      $ tail -f patch_domain.log