1 Introduction

The Integration Gateway Services (IGS) component provides an integration infrastructure for external (third party) connectivity to the Oracle Retail Integration Bus (RIB) in the form of a tested set of Web service providers and the configurations to connect to RIB and to ease the integration to RIB interfaces and RIB payloads.

The IGS component provides the integration to these RIB interfaces through standard request/response Web services using only the standard XSD based RIB message payloads.

There are 19 RIB message family interfaces included in IGS. They are selected as the interfaces most commonly used for custom integration to legacy systems. A Web service corresponds to each of the selected message families. Each service exposes the message types supported by the RIB message family.

The RIB Integration Gateway Services (IGS) component is an optional sub system and should be installed only after the core RIB components have been installed and verified. The following diagram describes the IGS logical architecture.

Prerequisites

The RIB Integration Gateway Service (IGS) component requires Oracle WebLogic Server 12c Release 12.1.3.0.0 and Java 7 64 bit with latest security updates.

Before you install this component, read the Oracle Retail Integration Bus Implementation Guide for the considerations and planning steps needed for the RIB IGS deployment to the WebLogic 12.1.3 Server. You should also make sure the environment variable JAVA-HOME points to Java 7 64 bit with latest security updates.

Prepare Oracle WebLogic 12.1.3 Server

The installation and base configuration of the Oracle WebLogic 12.1.3 Server is beyond the scope of this document. Work with the Oracle WebLogic 12.1.3 Server administration team to determine the physical and logical placement of the RIB IGS component within the WebLogic 12.1.3 Server deployment.

Create the RIB IGS WebLogic 12.1.3 Managed Server

Take the following step to prepare the Oracle WebLogic 12.1.3 Server to install the igs-service-<version>.ear:

Create a new managed server in which to deploy igs-service-<version>.ear. Oracle recommends (but does not require) that the .ear file name be used (without the extension) along with an underscore.

For example, if the .ear file name were igs-service-<version>.ear, the instance name should be igs-service_server.

Add the server start argument for IGS managed server from WLS console where managed server is configured and update the startWeblogic.sh and startManagedWeblogic.sh script under $Domain_Home/bin with below argument. JAVA_ OPTIONS="-Doracle.retail.soa.enabler.service.provider.engine.ServiceProviderImp lLookupFactory.interceptor=com.oracle.retail.igs.integration.service.DynamicServiceProviderImpl