1-10 Oracle Fusion Middleware Enterprise Deployment Guide for Oracle WebCenter
If you are also running SOA components in this topology, SOAHOST1 and SOAHOST2 run WebLogic Server configured with the WLS_SOA and WLS_WSM
managed servers, which run SOA components. These components are configured in an active-active manner.
Oracle Web Services Manager Oracle WSM provides a policy framework to manage and secure Web services in the Enterprise Deployment topology. WSM Policy Manager
also runs in active-active configuration in two additional WebLogic Servers.
On the firewall protecting the application tier, the HTTP ports, OAP port, and proxy port are open. The OAP port is for the WebGate module running in Oracle HTTP
Server in the web tier to communicate with Oracle Access Manager. Applications requiring external HTTP access use Oracle HTTP Server as the proxy. The proxy on
the Oracle HTTP Server must be enabled to allow this access.
1.5.4 Data Tier
Nodes in the data tier are located in the most secured network zone the intranet. In this tier, an RAC database runs on the nodes CUSTDBHOST1 and CUSTDBHOST2.
The database contains the schemas needed by the SOA Oracle WebCenter components. The WebCenter and SOA components running in the application tier
access this database.
On the firewall protecting the data tier, the database listener port typically, 1521 is required to be open. The LDAP ports typically, 389 and 636 are also required to be
open for the traffic accessing the LDAP storage in the IDM Enterprise Deployment.
1.5.5 What to Install
Table 1–2 identifies the source for installation of each software component. For more
information, see Oracle Fusion Middleware Installation Guide for Oracle SOA Suite and Oracle Fusion Middleware Installation Guide for Oracle WebCenter.
1.5.6 Unicast Requirement
Oracle recommends that the nodes in the myWCCompany topology communicate using unicast. Unlike multicast communication, unicast does not require
cross-network configuration and it reduces potential network errors that can occur from multicast address conflicts as well.
Table 1–2 Components and Installation Sources
Component Distribution Medium
Oracle Database 10g or 11g Oracle Database CD in 10g series, 10.2.0.4 or higher; in 11g series, 11.1.0.7 or
higher Repository Creation Utility RCU
Oracle Fusion Middleware Repository Creation Utility 11g 11.1.1.4.0 DVD Oracle WebLogic Server WLS
Oracle Weblogic Server 11g R1 10.3.3 DVD Oracle HTTP Server
Oracle Fusion Middleware WebTier and Utilities 11g 11.1.1.4.0 DVD Oracle SOA Suite
Oracle SOA Suite 11g 11.1.1.4.0 DVD Oracle Business Activity Monitor BAM
Oracle Fusion Middleware 11g 11.1.1.4.0 DVD Oracle Access Manager 10g Webgate
Oracle Access Manager 10g Webgates 10.1.4.3.0 DVD ; OAM OHS 11g webgates per platform
Oracle Virtual Directory OVD Oracle Identity Management 11g 11.1.1.4.0 DVD
Enterprise Deployment Overview 1-11
The following considerations apply when using unicast to handle cluster communications:
■
All members of a WebLogic cluster must use the same message type. Mixing between multicast and unicast messaging is not allowed.
■
Individual cluster members cannot override the cluster messaging type.
■
The entire cluster must be shut down and restarted to change the message modes from unicast to multicast or from multicast to unicast.
■
JMS topics configured for multicasting can access WebLogic clusters configured for unicast because a JMS topic publishes messages on its own multicast address
that is independent of the cluster address. However, the following considerations apply:
– The router hardware configurations that allow unicast clusters may not allow
JMS multicast subscribers to work.
– JMS multicast subscribers need to be in a network hardware configuration that
allows multicast accessibility. That is, JMS subscribers must be in a muticast-enabled network to access multicast topics.
1.6 How to Use This Guide
This section covers the following topics:
■
Section 1.6.1, Installation and Configuration Procedure
■
Section 1.6.2, Overview of Installation Strategies
1.6.1 Installation and Configuration Procedure
Table 1–3 summarizes the process by which you install and configure WebCenter.
Follow the procedures indicated in the first column, in the order shown, for the chosen configuration.
Note: This document focuses on enterprise deployments in Linux
environments, but enterprise deployments can also be implemented in UNIX and Windows environments.
Table 1–3 WebCenter Installation Procedures
Perform the steps in... To configure a domain
with only Admin Server and WSM-PM
To configure a domain with Admin Server,
WSM-PM, and to extend a domain with
a SOA cluster
To configure a domain with Admin Server,
WCM-PM, SOA cluster, and WebCenter
Chapter 2, Database and Environment Preconfiguration
Yes Yes
Yes Chapter 3, Installing Oracle
HTTP Server Yes
Yes Yes
Chapter 4, Creating a Domain Yes
Yes Yes
Chapter 5, Extending the Domain for SOA Components
No Yes
Yes Chapter 6, Extending the Domain
for WebCenter Components No
No Yes
