B Patching CPEM Domains

Before patching an CPEM 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 CPEM Domain

Note: When patching an CPEM domain, you need the same -rf arguments of rpasInstall as a full install of the domain. For example: -rf AppFunctions -rf RdfFunctions

Complete the following steps to patch your CPEM domain.

1. Extract the CPEM patch.

   1. Create a directory to store the RDF/CPEM Media Pack on the target server. This directory will be referred to as [CPEM Installation]. It is the location where the CPEM 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 [CPEM Installation] directory on the target server.

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

      cd [CPEM Installation]

      unzip [CPEM Package]

   4. Extract the CPEM Installer.

      cd CDROM

      unzip CPEM.zip

2. Delete or rename old activities before running regeneration.

   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 to include ”_old”.

3. Using the Configuration Tools on a Windows machine, auto-generate the CPEMsolutions 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 CPEM solution.

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

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

6. To patch the CPEM domain:

   1. Set $CPEM_HOME

      export CPEM_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 buildCPEM.sh parameters, refer to Table B-1.

      
      
      
      

      Note: The case for the script has changed from buildcpem.sh and is now buildCPEM.sh.

      
      

      [Patch]

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

      buildCPEM.sh \

      -c /configPath \

      -i /inputPath \

      -l /logPath \

      -f patch_domain.log \

      -d /domainPath \

      -m 2 \

      -p

      [Build]

      buildCPEM.sh \

      -c /configPath \

      -i /inputPath \

      -l /logPath \

      -f build_domain.log \

      -d /domainPath \

      -m 2

      Table B-1 Flags Descriptions for buildCPEM.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	CPEM
      * Where $PWD is the current directory

      
      
      
      

      Note: The -r parameter which is supported for RDF and other applications, is unavailable for CPEM.

      
      

   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

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

      $ tail -f patch_domain.log