| Oracle® Retail Service Backbone Installation Guide Release 15.0.3 F18452-01 |
|
 Previous |
 Next |
RSB has several dependencies on Oracle Retail Application installations, as well as on the Oracle WebLogic servers. This section covers these requirements.
|
Note: Oracle Retail assumes that the retailer has applied all required fixes for supported compatible technologies. |
If you are unable to find the necessary version of the required Oracle infrastructure software (database server, application server, WebLogic, etc.) on the Oracle Software Delivery Cloud, you should file a non-technical 'Contact Us' Service Request (SR) and request access to the media. For instructions on filing a non-technical SR, see My Oracle Support Note 1071023.1 - Requesting Physical Shipment or Download URL for Software Media.
| Supported On | Versions Supported |
| Database Server OS | OS certified with Oracle Database 12c Enterprise Edition. Options are:
|
| Database Server 12c | Oracle Database Enterprise Edition 12c (12.1.0.2) with the following specifications:
Components:
Oneoff Patches:
Other Components:
|
| Application Server OS | OS certified with Oracle Fusion Middleware 12c. Options are:
|
| Application Server | Oracle Fusion Middleware 12c (12.2.1.3)
Components:
|
| Minimum required JAVA version for all operating systems | JDK 1.8.0+ latest security updates 64 bit |
|
Note: By default, JDK is at 1.6. After installing the 12.1.0.2 binary, apply patch 19623450. Follow the instructions on Oracle Database Java Developer's Guide 12c Release 1 to upgrade JDK to 1.7. The Guide is available at:http://docs.oracle.com/database/121/JJDEV/chone.htm#JJDEV01000. Follow-through to complete the post-patch operation. |
|
Important: If there is an existing WebLogic installation on the server, you must upgrade to WebLogic 12.2.1.3. All middleware components associated with WebLogic server should be upgraded to 12.2.1.3.Back up the weblogic.policy file ($WLS_HOME/wlserver/server/lib) before upgrading your WebLogic server, because this file could be overwritten. Restore the weblogic.policy from backup file after the WebLogic upgrade is finished and the post patching installation steps are completed. |
The RIC model and view components require ADF runtime to run properly. Verify that ADF runtime 12.2.1.3 or higher is available in the WebLogic Application Server (12.2.1.3) and applied to the domain where RIC will be installed.
Other Resources
For information about WebLogic Application Server 12.2.1.3, see the Oracle WebLogic Server Documentation Library.
WebLogic Application Server 12c - Index http://docs.oracle.com/middleware/1213/index.html
WebLogic Application Server 12c - Documents http://docs.oracle.com/middleware/1213/wls/index.html.
|
Note: See also the Oracle Database Administrator's Guide 12c (12.1) and the Oracle WebLogic Application Server 12c (12.2.1.3) documentation. |
JSIT requires WebLogic Application Server 12c (12.2.1.3). Before installing JSIT, verify that the WebLogic Application Server 12c (12.2.1.3) is available in your environment. For more information on installing JSIT, see Install JSIT.
| Retail Product | Version Supported |
| Oracle Retail Warehouse Management System (RWMS) 15.0.3 | RIB 15.0.3 |
| Oracle Retail Merchandising System (RMS) 15.0.3 | RIB 15.0.3 |
| Oracle Retail Price Management (RPM) 15.0.3 | RIB 15.0.3 |
| Oracle Retail Store Inventory Management (SIM) 15.0.3 | RIB 15.0.3 |
| Oracle Retail Advanced Inventory Planning (AIP) 15.0.3 | RIB 15.0.3 |
| Integration Gateway Services (IGS) 15.0.3 | RSB 15.0.3 |
| Oracle Retail Financial Integration (ORFI) 15.0.3 | RSB 15.0.3 |
| Oracle Retail Returns Management (RM) 14.1 | RSB 15.0.3 |
| Oracle Retail Invoice Matching (ReIM) 15.0.3 | RSB 15.0.3 |
| POS Suite 14.1 | RSB 15.0.3 |
| Rib4OMS 15.0.3 | RSB 15.0.3 |
Oracle Service Bus (OSB) supports three types of topologies: Admin-only topology, Admin + Managed Server topology and Cluster topology. The first two topologies are non-clustered topologies which are not highly-available; therefore it is recommended that you use Cluster topology.
Clustering allows OSB to run on a group of servers that can be managed as a single unit. An OSB deployment can use clustering and load balancing to improve scalability by distributing the workload across nodes. A WebLogic server clustered domain consists of only one Admin Server, and one or more managed servers. The managed servers in an OSB domain can be grouped in a cluster. When OSB resources are configured, resources are targeted to the named cluster. The advantage of specifying a cluster as the target for resource deployment is that it makes it possible to dynamically increase capacity by adding Managed Servers to the cluster.
Singleton Resources
While most resources used by OSB are deployed homogeneously across the cluster, there are a few resources that must be pinned to a single Managed Server in order to operate correctly. The following table lists these components:
Service Bus Cluster Singleton Marker Application
Service Bus Domain Singleton Marker Application
Service Bus Message Reporting Purger
configwiz-jms service
Load balancing in an OSB cluster
Load balancing distributes the workload proportionately across all the servers in a cluster so that each server can run at full capacity. Web services (SOAP or XML over HTTP) can use HTTP load balancing. External load balancing can be accomplished through the WebLogic HttpClusterServlet, a WebServer plug-in or a hardware router. In the steps described in this document, it uses a HTTP proxy server which is a managed server in the same domain and is not a part of the cluster.
