3 Technical Specifications

RSB has several dependencies on Oracle Retail Application installations, as well as on the Oracle WebLogic servers. This section covers these requirements.

Server Requirements

Supported On	Versions Supported
Database Server OS	OS certified with Oracle Database 11gR2 Enterprise Edition. Options are: Oracle Linux 6 for x86-64 (Actual hardware or Oracle virtual machine). Red Hat Enterprise Linux 6 for x86-64 (actual hardware or Oracle virtual machine) IBM AIX 7.1 (actual hardware or LPARs) Solaris 11 Sparc (actual hardware or logical domains)
Database Server 11gR2	Oracle Database Enterprise Edition 11gR2 (11.2.0.3) with the following specifications: Components: Oracle Partitioning Examples CD (formerly the companion CD) Oneoff Patches 13036331: ORA-01031 INSUFFI-CIENT PRIVILEGES WHEN GRANTING EXECUTE ON DBMS PACKAGES. Other Components: Perl Compiler 5.0 or later X-Windows interface
Application Server OS	OS certified with Oracle Fusion Middleware 11g Release 1 (11.1.1.6). Options are: Oracle Linux 6 for x86-64 (Actual hardware or Oracle virtual machine). Red Hat Enterprise Linux 6 for x86-64 (actual hardware or Oracle virtual machine) IBM AIX 7.1 (actual hardware or LPARs) Solaris 11 Sparc (actual hardware or logical domains)
Application Server	Oracle Fusion Middleware 11g Release 1 (11.1.1.6) Components: Oracle WebLogic Server 11g Release 1 (10.3.6) Java: JDK 1.7.0+ 64 bit
Minimum required JAVA version for all operating systems	JDK 1.7.0+ 64 bit

Important

If there is an existing WebLogic installation on the server, you must upgrade to WebLogic 10.3.6. All middleware components associated with WebLogic server should be upgraded to 11.1.1.6.

Back up the weblogic.policy file ($WLS_HOME/wlserver_10.3/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.

Additional Requirement for Retail Integration Console (RIC)

The RIC model and view components require ADF runtime to run properly. Verify that ADF runtime 11.1.1.6 or higher is available in the WebLogic Application Server (10.3.6) and applied to the domain where RIC will be installed.

Other Resources

For information about WebLogic Application Server 11g, see the Oracle WebLogic Server Documentation Library.

WebLogic Application Server 11g - Index http://download.oracle.com/docs/cd/E15523_01/index.htm
WebLogic Application Server 11g - Documents http://download.oracle.com/docs/cd/E15523_01/wls.htm.

Note:

See also the Oracle Database Administrator's Guide 11g Release 2 (11.2) and the Oracle WebLogic Application Server 11g (10.3.6) documentation.

Supported Oracle Retail Products

Retail Product	Version Supported
Oracle Retail Warehouse Management System (RWMS) 14.0.0	RIB 14.0.0
Oracle Retail Merchandising System (RMS) 14.0.0	RIB 14.0.0
Oracle Retail Price Management (RPM) 14.0.0	RIB 14.0.0
Oracle Retail Store Inventory Management (SIM) 14.0.0	RIB 14.0.0
Oracle Retail Advanced Inventory Planning (AIP) 14.0.0	RIB 14.0.0
Integration Gateway Services (IGS) 14.0.0	RSB 14.0.0
Oracle Retail Financial Integration (ORFI) 14.0.0	RSB 14.0.0
Oracle Retail Returns Management (RM) 14.0.0	RSB 14.0.0
Oracle Retail Invoice Matching (ReIM) 14.0.0	RSB 14.0.0
POS Suite 14.0.0	RSB 14.0.0
Rib4OMS 14.0.0	RSB 14.0.0

The RSB and Oracle WebLogic Server Cluster

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 high-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:

ALSB Cluster Singleton Marker Application
ALSB Domain Singleton Marker Application
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.