Inbound Refinery and Inbound Refinery Cluster Concepts Content Server and Inbound Refinery Configuration Inbound Refinery Instances and Oracle HTTP Server

Configuring High Availability for Enterprise Content Management 11-49

11.3.9 Configuration of Inbound Refinery Instances

This section provides configuration information for Inbound Refinery instances.

11.3.9.1 Inbound Refinery and Inbound Refinery Cluster Concepts

Inbound Refinery instances are not clusterable; they operate completely independently. Several Inbound Refinery instances can be added to the same WebLogic domain, but the following restrictions should be observed: ■ No more than one Inbound Refinery per domain per machine can be installed. ■ Inbound Refinery instances that are on separate machines must ensure that their configuration is all local and not on shared disk. The local content requirement is important if you install Inbound Refinery instances on machines that have existing Content Server installations. While configuration in a Content Server cluster must be shared, configuration information of Inbound Refinery instances must not be shared with other Inbound Refinery instances.

11.3.9.2 Content Server and Inbound Refinery Configuration

You can configure a Content Server with one or more Inbound Refinery instances and the same Inbound Refinery can act as a provider to one or more Content Servers. to configure Inbound Refinery instances, see Oracle Fusion Middleware Administrators Guide for Conversion. It is recommended that all of the Inbound Refineries which were created in the preceding Configuration be added to the UCM or URM Cluster. This will create a many-to-many relationship in which all members of the UCMURM cluster can request conversions from any member of the IBR cluster. Inbound Refinery instances can be installed in their own domain or as an extension of an existing domain.

11.3.9.3 Inbound Refinery Instances and Oracle HTTP Server

An Inbound Refinery only needs to be accessed once through HTTP to initialize its configuration. This can be done directly, at the Managed Servers listen address. Do not place an Inbound Refinery behind an HTTP Server. All subsequent access to an Inbound Refinery is through the socket listener. 11-50 Oracle Fusion Middleware High Availability Guide 12 Active-Passive Topologies for Oracle Fusion Middleware High Availability 12-1 12 Active-Passive Topologies for Oracle Fusion Middleware High Availability This chapter describes how to configure and manage active-passive topologies. It contains the following sections: ■ Section 12.1, Oracle Fusion Middleware Cold Failover Cluster Topology Concepts