| Oracle® Retail Predictive Application Server Installation Guide Release 14.1.2 E70811-01 |
|
 Previous |
 Next |
| Oracle® Retail Predictive Application Server Installation Guide Release 14.1.2 E70811-01 |
|
Previous |
Next |
The rsp_manager (Retail Service Pack Manager) is a Perl script tool that is capable of currently patching the following:
RPAS
Configuration Tools
Domains
Solution Environments (AIP_HOME, SCI_HOME, and so on)
This system will automatically run any creates, scripts, or procedures that need to be run when a patch is applied.
You must have Perl 5.005 or later installed on your system. Most UNIX variants will have this installed by default. On Windows, an installation of Cygwin is required.
The following instructions describe how to install a service pack.
Copy component-ver.os.tar.zip
|
Note: This component will be named-ver.os.zip for Windows. |
The service pack is shipped as a compressed.tar or.zip, depending on the platform. The file will be named based on the release level of the code contained within. Copy the service pack.tar or.zip file to a standard service pack directory that you have previously set up.
Example C-1 Service Pack Directory
Create a service pack directory at:
/files1/service_packs
Then, copy the service pack file to (where /service_packs is a user-created directory for archived service packs):
cp ./ARPOplatform-14.1.2.sun.tar.zip /service_packs
In Windows, this directory would resemble the directory C:\service_packs.
Unpack the service pack from the.tar or.zip file from Step 1.
Example C-2 UNIX Commands
The following are example UNIX commands to unpack the service pack:
cd /service_packs
unzip ARPOplatform-14.1.2.sun.tar.zip
tar -xvf
This creates a subdirectory in your service pack directory named the same as the service patch/pack version, which contains a directory for the platform. In this directory, you will see subdirectories for each of the modules this service pack is updating.
For example, if this service pack has updates to RPAS, domains, and tools, the following module directories could be created:
/service_packs/ARPOplatform/14.1.2/sun/rpas
/service_packs/ARPOplatform/14.1.2/sun/domain
/service_packs/ARPOplatform/14.1.2/sun/tools
Additionally, this document, Release Notes, and a copy of any service pack installation scripts/libraries will be copied to a location such as:
/service_packs/ARPOplatform/14.1.2
|
Note: In Windows, you may use WinZip or a similar unzipping tool for this step. |
Apply the service pack on a staging or production server. After extracting the service pack, you will have to apply the service pack to the installed components and any domains that have been built. Note that the service pack installation should be carried out on the same operating system as that on which the product resides.
The syntax of applying a service pack with rsp_manager is:
rsp_manager –install –sp <sp path> -domain <domain path>
Example C-3 Commands to Apply Service Pack 14.1.2 for ARPO platform and domain
To apply service pack 14.1.2 for ARPO platform and domain /domain1, use the following commands:
cd /service_packs/ARPOplatform/14.1.2/
./rsp_manager –install –sp sun –domain /domain1
Example C-4 Commands to Turn on File Logging
To turn on file logging of the output and store the results of the application in domain1.log, use the following commands:
cd /service_packs/ARPOplatform/14.1.2/
./rsp_manager –install –sp sun –domain /domain1 –log domain1.log
Following installation, a validation process will be run against your patched install.
If you have more than one domain running off the same ARPOplatform, it is possible to create a domain list file and supply that file path, instead of the domain path, as an argument. This will be a text file with a full path to a domain on each line.
The additional syntax of rsp_manager is:
rsp_manager -install -sp <sp path> -domain <domain_list_file>
Example C-5 Applying Service Packs
To install service pack 14.1.2 for ARPOplatform and all domains listed in /files/domain_list.txt, use the following commands:
cd /service_packs/ARPOplatform/14.1.2/
./rsp_manager -install -sp sun -domain /files/domain_list.txt
…where /files/domain_list.txt looks similar to this:
cat /files/domain_list.txt
/domains/domain1
/domains/domain2
/domains/domain3
|
Note: Logging will work with multiple domains, but only one file will be created and written to. This single log will contain the output from all updated modules and domains. |
The rsp_manager has optional arguments that allows you to perform tasks such as an installation version report, install or patch validation, and patch application forcing. The following sections provide details on these arguments.
-no_rpas
This flag stops your RPAS_HOME from being patched. This can be used in conjunction with -no_tools, but still passing domains, in order to upgrade a domain to your RPAS_HOME code level without performing an RPAS upgrade.
-no_tools
This flag stops your RIDE_HOME from being patched. This can be used in conjunction with -no_rpas, but still passing domains, in order to upgrade a domain to your RPAS_HOME code level without performing a tools upgrade.
-no_domain
This flag stops the patch from being applied to any domains.
-log <logfile>
Although logging is done by default, the log will be saved to the current working directory as a date-stamped filename. This flag allows you to change the name of the log file created to the argument you pass.
-force
This flag enforces the application of the patch/pack regardless of the versions that the components report. This allows you to reapply a patch that has already been applied, while also running any update scripts that might have already been run.
Example C-6 -force Flag
To force reinstallation of the 14.1.2 service patch onto your installation and a single domain, with logging:
cd /service_packs/ARPOplatform/14.1.2/
./rsp_manager -install -sp sun -domain /domain1 -log domain1.log -force
-validate
This flag is run by default at the end of all -install processes. The purpose of this flag is to validate components of the service patch/pack against your installation. Currently, this will only check your core binaries and libraries in both RPAS_HOME and RIDE_HOME. Tests include permissions comparisons and file checksum validation, which are represented in the output as P or C respectively upon errors.
Example C-7 -validate Flag
To validate the 14.1.2 Sun service patch against your installation any time after patching:
cd /service_packs/ARPOplatform/14.1.2/
./rsp_manager -validate -sp sun
Validating your updated install against the service pack/patch -
............................................................
Validation complete...
Files Checked: 106
Files Passed: 106
Files Failed: 0
|
Note: The number of files checked might not match the previous number, as it changes quantity based on platform and patch version. If any files fail, a listing of those failed files will be presented, each being preceded by flags (C or P) to indicate which checks failed. |
|
Note: The following process is not a suggested installation process, but Oracle Retail acknowledges that it may be more efficient in some limited cases. |
Since rsp_manager relies on the Retek.pm library, this file must normally be in the same directory as the one you run rsp_manager from. You may use an environment variable to point to the path that contains the library so that they can be split from each other. A useful instance would be setting up a directory in your path and placing rsp_manager inside, while using the RSP_HOME environment variable to point to the directory that contains the Retek.pm file. This would allow you to run rsp_manager from anywhere on the system.
Example C-8 Running rsp_manager
To be able to run rsp_manager from anywhere:
> cd /service_packs/ARPOplatform/14.1.2/
> ls
rsp_manager Retek.pm
> mkdir ~/bin
> cp ./rsp_manager ~/bin/
> export PATH=~/bin:$PATH
> export RSP_HOME=/service_packs/ARPOplatform/14.1.2
At this point, you can change directories to anywhere on the disk and run rsp_manager.
Keep in mind that if you do choose to split these files, when you obtain new copies of the script and library, you will need to place them into the locations you reference in $PATH and $RSP_HOME.
