| Oracle® Retail Integration Bus Installation Guide Release 13.0 |
|
 Previous |
 Next |
The RIB application installer can be used to perform any of the tasks below. For a new install, all tasks are recommended.
Run the Preparation Phase to unpack files, prepare the workspace, and perform pre-install verifications.
Generate the rib-deployment-env-info.xml file, which configures the RIB install.
Run the Assembly Phase to build the EAR and WAR files for the rib-<app> applications.
Configure the Advanced Queuing JMS topics for RIB.
Run the Deployment Phase to deploy the EAR and WAR files to the Application Server(s).
For more information about the Preparation, Assembly and Deployment Phases, see the RIB Operations Guide.
Log in to the UNIX server as the user who will own the RIB development workspace. Create a new directory for the workspace. There should be a minimum of 800 MB of disk space available.
Copy the RIB Kernel package (RibKernel13.0.0ForAll13.x.xApps_eng_ga.tar) into the workspace and extract its contents.
Change directories to Rib1300ForAll13xxApps/rib-home. This location will be referred to as <RIB_HOME> for the remainder of this chapter.
Expand the RIB Kernel distribution as described above.
Download the RIB Functional Artifacts distribution (RibFuncArtifact13.0.0ForAll13.0.0Apps_eng_ga.tar), and copy it into the <RIB_HOME>/download-home/rib-func-artifacts directory. Do not untar the file.
Download the tar file distributions for each rib-<app> application that you will install. Copy the files into the <RIB_HOME>/ download-home/all-rib-apps directory. Do not untar the files.
Set the JAVA_HOME environment variable. The JAVA_HOME must be set to a Java 1.5 JDK. If the <RIB_HOME> workspace is located on the same server as the Application Server, then it is recommended to set the JAVA_HOME to $ORACLE_HOME/jdk.
If you are using an X server, such as Exceed, set the DISPLAY environment variable so that you can run the installer in GUI mode (recommended). If you are not using an X server, or the GUI is too slow over your network, unset DISPLAY for text mode.
Make sure that all OC4J instances that you intend to deploy to are currently running.
Change directories to the <RIB_HOME> directory.
Run the rib-installer.sh script. The RIB installer appears.
After the RIB installation is complete, it will launch the Oracle Configuration Manager (OCM) installer if possible. If you wish to install OCM at this time, please refer to Metalink Note ID # 559539.1 for instructions.
Restart the rib-<app>-oc4j-instances. During the installation process a shared library is created that contains the JDBC Driver update. For PL/SQL applications, it is necessary to bounce the oc4j instance.
Run the RIB Diagnostic and Monitoring Tools (RDMT) to verify the installation.
The RIB Diagnostic and Monitoring Tools (RDMT) should be used at this time to verify the RIB installation. Please refer to 999 for instructions to configure and use the RDMT tools.
The RIB application installer creates the following backup and log files:
Each time the installer is used to generate a new rib-deployment-env-info.xml, a backup of the existing file will be created in: <RIB_HOME>/deployment-home/conf/archive/rib-deployment-env-info.xml.<timestamp>
Each time the installer is run, the output of the installer script will be written to a log file. The installer's log file will be located in: <RIB_HOME/.retail-installer/rib/log/rib-install-app.<timestamp>.log.
Each time the installer is run, the user inputs will be recorded in: <RIB_HOME/.retail-installer/rib/log/ant.install.properties.<timestamp>. This file should only be used during troubleshooting to verify the exact inputs that were given to the installer. It is not recommended to modify this file as it is a record of the inputs at the time the installer was run.
If an error is encountered while running the installer, the cause of the error must be corrected before making another attempt to run the installer. The installer's log file may contain helpful information for determining the cause of the error. After you have examined the log files, please refer to the troubleshooting guide in Appendix D for a list of commonly encountered errors.
When you are ready to attempt another installation, keep in mind that you may be able to avoid re-entering all your inputs if the previous installation process was far enough along to configure the rib-deployment-env-info.xml. If the installer has already generated the rib-deployment-env-info.xml file, or if you have manually edited the rib-deployment-env-info.xml file, then it is not necessary to re-enter all the inputs in the installer. Verify that the rib-deployment-env-info.xml contains the correct settings, and run the installer with the "Use existing rib-deployment-env-info.xml" option.
