OFM Components

Oracle Fusion Middleware provides two types of components:
■ A Java component, which is an Oracle Fusion Middleware component that is
deployed as one or more Java EE applications and a set of resources. Java
components are deployed to an Oracle WebLogic Server domain as part of a
domain template. Examples of Java components are the Oracle SOA Suite and
Oracle WebCenter components.



■ A system component, which is a manageable process that is not deployed as a
Java application. Instead, a system component is managed by the Oracle Process
Manager and Notification (OPMN). System components include Oracle Internet
Directory, Oracle HTTP Server, Oracle Web Cache, and Java Standard Edition
(JSE) components, such as Oracle BI Enterprise Edition.
A Java component and a system component are peers.

SOA 11g: Cluster installation

This article is a summary of the document you can download that describes in detail how to install and configure an Oracle SOA Suite11g installation.This installation is a straight forward cluster installation that assumes the following components.

on the in a clustered environment.

• Load balancer
• Server node #1
• Server node #2
• Database

I assume that the database is high available, using Oracle RAC for example. This is shown in the next diagram.








The goal is to install the Oracle SOA Suite 11g software in a cluster on a such way that it is easy to configure, maintain and efficient in usage. We will install the following components based on release 11g, patch set 1 (ps1):

• Oracle Weblogic Server
• Oracle SOA Suite 11g

A few assumptions have been made:

The software is already installed:

• Oracle Weblogic Server 11g
• Oracle SOA Suite 11g
• Oracle HTTP Server (Linux)
• Oracle Repository Creation Utility (RCU) (Linux)

A database is available and configured with the SOA 11g repository schema's; such as DEV_SOAINSTA; DEV_MDS; etc.

We will install this software on each node. On each node we create a cluster and within that cluster two managed servers; soa_server and bam_server. On one of each server, node #1, we configure the admin server. On each server we install the Oracle HTTP Server that will route the requests to the two servers.

The approach of the installation is as follows.

1. Configure Weblogic Server cluster domain definition.
2. Pack and unpack cluster domain.
3. Apply Java Object Cache
4. Apply Oracle Coherence for cluster deployment
5. Start environment
6. Configure Oracle HTTP Server on each node

This article and the document could not be created without the following documents.

• Oracle Fusion Middleware Enterprise Deployment Guide for Oracle SOA Suite, 11g Release 1, E12036-02
• Chapter 4: Creating a domain
  
• Chapter 5: Extending the Domain for SOA Components

The document can be download here.

Have fun.

What Is an Oracle WebLogic Server Domain?

A WebLogic Server administration domain is a logically related group of Java
components. A domain includes a special WebLogic Server instance called the
Administration Server, which is the central point from which you configure and
manage all resources in the domain. Usually, you configure a domain to include
additional WebLogic Server instances called Managed Servers. You deploy Java
components, such as Web applications, EJBs, and Web services, and other resources to
the Managed Servers and use the Administration Server for configuration and
management purposes only.



Managed Servers in a WebLogic Server domain can be grouped together into a cluster.The directory structure of a WebLogic Server domain is separate from the directory
structure of the WebLogic Server home. It can reside anywhere; it need not be within the Middleware home directory.

Troubleshooting and Workarounds

1	Transaction Management Use Bpelx:rollback
2	Connection pooling configurations not working as per expectations. If the pool was set to 10 at ra.xml level, there was still latency observed at process level when establishing connection The max connection settings at pool level were less than the max connection setting at ra.xml level.Connection Configurations at ra.xml level should be less than the configuration at the data source level
3	Enqueuing and dequeuing failed at times     Having separate Resource Providers for Enqueuing and Dequeuing a message from AQ JMS queues/topics resolved the problem
4	The deployment plan file replaced host names post compilation. This caused issues as some of the host names still pointed to an earlier server where the wsdls' xsds' were not up to date. Changed the Deployment script to not use the plan file, and perform the search and replace task prior to compilation
5	FOTY Error -  There is no detailed explaination why this error occurs. It can occur due to multiple reasons.The error log also does not provide any clarity on the error. It typical happens when an xpath expression within an XSLT cannot be evaluated or there is a namespace issue. Devised a set of steps to followed using elimination by trial and error to find the cause of the error.