3 Patch Installation

This chapter describes how to upgrade MFP Retail from a previous release to Release 14.1.2.

Note: If using the standard integration between RMS and MFP, you must perform an additional location hierarchy conversion process if upgrading from MFP 13.2.1.10 or prior versions. See the RMS Integration Update section for more information.

Upgrade Prerequisites

In order to upgrade MFP Retail, 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 retaillogin.ksh script and source it again as previously outlined.

Upgrade Process

The following process outlines how to upgrade MFP Retail to the latest version using the RPAS Configuration Tools.

Upgrade to Key RPAS Versions

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.

1. Upgrade and Patch to RPAS Release 13.2.3

2. Convert for Integer Indexing

3. Upgrade and Patch to RPAS Release 13.3 or Later

Upgrade and Patch to RPAS Release 13.2.3

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.

Convert for Integer Indexing

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.

Upgrade and Patch to RPAS Release 13.3 or Later

The following process outlines how to upgrade MFP Retail 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.

For the PC

Follow these instructions for the PC to upgrade to the current version:

1. Open RPAS Configuration Tools.

2. In RPAS Configuration Tools, load your previous configuration of MFP Retail:

   1. From the Configuration Tools File menu, select Open.

   2. From the Open window, locate the configuration file and click Open.

3. If your configuration requires updating, dialog boxes will prompt you to upgrade. Follow the instructions given in the dialog boxes.

4. In the RPAS Configuration Tools File menu, click Save to save the configuration.

5. Zip the configuration in Cygwin and transfer the.zip file to the RPAS server.

For the Server

Follow these instructions for the server to upgrade to the current version:

1. Upgrade the RPAS Fusion Client configuration by running the installer:

   1. Begin the installer as described in the (UNKNOWN STEP NUMBER) Installing MFP Retail section.

   2. Complete steps 1-5.

   3. At step 6, the Install Tasks Window, clear the Create Retail Domain option.

   4. Finish the remaining steps of the installer.

2. Unzip the updated configuration and note where it is saved.

3. Upgrade your MFP Retail domain to a 14.1.2 domain. For upgrading instructions, see the ”Upgrading and Patching Domains” section in either the Classic Client or Fusion Client version of the Oracle Retail Predictive Application Server Administration Guide.

RMS Integration Update

In MFP 13.2.1.11, positions in the location hierarchy were renamed to ensure unique position names based on the RMS data. Due to these location hierarchy changes, customers upgrading from MFP 13.2.1.10 or prior versions who use the standard integration between RMS and MFP must use the location hierarchy conversion process before integrating with RMS.

Use this conversion process if you are

• Upgrading from MFP version 13.2.1.10 or prior versions

• Using the standard integration between MFP and RMS

Note: If upgrading from MFP version 13.2.1.10 or prior versions, you must follow this process. In the future, if you are already on 13.2.1.11 or later, you do not need to follow this process again.

Required Location Hierarchy Conversion Process

Perform the following steps to rename the positions in the location hierarchy. No data is lost in this process; only internal positions names are changed. This process allows you to maintain and use your existing MFP domain while conforming to the new position names.

Caution: You must perform this process before integrating with RMS, or the integration will not work.

1. Point environment variable RPAS_HOME to the new RPAS_HOME.

2. Run migrateData.ksh with the -a n flag to produce the position rename file and run renamePositions without actually applying the changes.

3. Examine the log file mfp_LocRename.log for errors.

4. When you are ready, run the migrateData.ksh script without the -a y flag to apply the changes.