| Oracle® Retail Integration Bus Installation Guide Release 13.1 |
|
 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 preinstallataion 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.1.0ForAll13.x.xApps_eng_ga.jar) into the workspace and extract its contents.
Change directories to Rib13.1ForAll13xxApps/rib-home. This location will be referred to as <RIB_HOME> for the remainder of this chapter.
|
Note: Using multiple JMS servers allows for the isolation of flows for performance and operational QoS. For more information, see Chapter 7, "JMS Provider Management," in the RIB Operations Guide. |
If your RIB installation will include multiple JMS servers, additional steps are required before you can run the installer.
|
Note: Do not follow these steps if you will be using only one JMS server. |
Change directories to <RIB_HOME>/download-home/bin, and run the check-version-and-unpack.sh script.
Determine the family that needs to be configured for multiple JMS.
Examine the rib-integration-flows.xml to identify all the RIB applications in the full integration flow.
Ensure that a new AQ JMS database server (not a schema) is set up. (For information on how to set up a new AQ JMS, see "Prepare Oracle AQ JMS Provider" in Chapter 3, "Database Installation Tasks".)
Ensure that any additional AQ JMS are not in the same database server. Each new AQ JMS requires a new database server.
|
Note: If this is a first-time installation--or if you are using the installer to rewrite the rib-deployment-env-info.xml--you do not need to complete Step 6. |
Add one or more JMS server(s) by updating rib-deployment-env-info.xml,
In the rib-home, modify the appropriate files for each of the rib-<apps> that participate in the integration flow. Point the adapters to the right JMS server. The following apply to this step:
rib-<app>-adapters.xml
rib-<app>-adapter-resources.properties
For more information on this step, see the RIB Operations Guide.
Once Step 7 is finished, the installer tool does the following to complete preinstallation activities:
Compiles all the rib apps (%$RIB_HOME/application-assembly-home/bin/rib-app-compiler.sh).
Runs prepare-jms for the newly-created JMS server ($RIB_HOME/deployment-home/bin/rib-app-deployer.sh -prepare-jms<mjs2>. This step configures additional JMS servers.
Deploys ($RIB_HOME/deployment-home/bin/rib-app-deployer.sh rib-<app>).
Expand the RIB Kernel distribution as described above.
Download the RIB Functional Artifacts distribution (RibFuncArtifactRelease 13.1ForAllRelease 13.1Apps_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.
Download the RIB Diagnostic and Monitoring Tools (RDMT) package (Rdmt13.1ForAll13.x.xApps_eng_ga.tar) and untar it into the <RIB_HOME>/tools-home directory. Several files will be placed under the rdmt directory when you untar the package. This will allow the installer to run the <RIB_HOME>/tools-home/rdmt/configbuilder.sh script as part of the RIB installation.
For multiple JMS servers only: If your RIB installation will include more than one JMS server, you must complete the additional preinstallation steps listed above.
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.
|
Note: The Oracle Retail OCM Installer packaged with this release does not install the latest version of OCM. Oracle Retail recommends that retailers upgrade to the latest version of OCM from ARU. For more information, see Metalink Note ID # 559539.1. See also the Oracle Configuration Manager Installer Guide, which describes the procedures and interface of the Oracle Retail Oracle Configuration Manager Installer that retailers run near the completion of the installation process: http://www.oracle.com/technology/documentation/ocm.html |
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.
If the installer finds the configbuilder.sh script, it will attempt to run it. However, if the installer is unable to run the RDMT script or if the RDMT setsup failed for some reason, then you should manually run the RDMT at this time 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 the RIB Operations Guide - Diagnostic and Monitoring Tools 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.
|
 Copyright © 2009, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|