This chapter describes Oracle Fusion Middleware key concepts. It includes the following sections:
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 Oracle Process Manager and Notification (OPMN). The system components are:
Oracle HTTP Server
Oracle Web Cache
Oracle Internet Directory
Oracle Virtual Directory
Oracle Forms Services
Oracle Business Intelligence Discoverer
Oracle Business Intelligence
A Java component and a system component are peers.
After installing and configuring Oracle Fusion Middleware, the environment contains the following:
An Oracle WebLogic Server domain, which contains one Administration Server and one or more Managed Servers. The Administration Server contains the Oracle WebLogic Server Administration Console and Oracle Enterprise Manager Fusion Middleware Control. The Managed Servers contain components, such as Oracle WebCenter and Oracle SOA Suite.
If the environment includes system components, one or more Oracle instances.
Figure 2-1 shows an Oracle Fusion Middleware deployment topology.
As shown in Figure 2-1, this topology represents a multi-tiered architecture. Users access the system from the client tier. Requests go through a hardware load balancer, which then routes them to a Web server cluster, running Oracle HTTP Server. Web servers route the requests to the WebLogic cluster. Applications running on the WebLogic cluster then interact with the database cluster to service the request.
After installation, a typical Oracle Fusion Middleware environment contains the following (Figure 2-2):
One Oracle WebLogic Server domain, which contains one Administration Server and one or more Managed Servers. See Section 2.4, "What Is an Oracle WebLogic Server Domain?".
If system components are installed, they are configured in an Oracle Instance. See Section 2.5, "What Is an Oracle Instance?".
A metadata repository, if the installed components require one. For example, Oracle SOA Suite requires a metadata repository. See Section 3.2, "Oracle Metadata Repository".
A Middleware home, which contains product binary files. See Section 2.6, "What Is a Middleware Home?". Note that the product binary files will change as a result of patching. The configuration of the product binaries change as you configure and create a new data source.
Figure 2-2 shows an Oracle Fusion Middleware environment with an Oracle WebLogic Server domain that contains an Administration Server, two Managed Servers, and an Oracle instance. The environment also contains a metadata repository.
An Oracle WebLogic Server domain is a logically related group of Java components. A domain includes a special Oracle WebLogic Server instance called the Administration Server, which is the central point from at which configuration and management of all resources in the domain occur. Usually, you configure an additional domain to include additional Oracle WebLogic Server instances called Managed Servers. You can deploy Java components, such as Web applications, Enterprise Java Beans (EJB), and Web services, and other resources to the Managed Servers and uses the Administration Server for configuration and management purposes only.
Managed servers in a domain can be grouped together into a cluster.
A domain is a peer of an Oracle instance. Both contain specific configurations outside of their Oracle homes.
Figure 2-3 shows a domain with an Administration Server, three standalone Managed Servers, and three Managed Servers in a cluster.
For more information about domain configuration see the Oracle Fusion Middleware Understanding Domain Configuration for Oracle WebLogic Server.
The following topics describe entities in the domain:
The Administration Server operates as the central control entity for the configuration of the entire domain. It maintains the domain's configuration documents and distributes changes in the configuration documents to Managed Servers. The Administration Server serves as a central location from which to monitor all resources in a domain.
Each domain must have one server instance that acts as the Administration Server.
To interact with the Administration Server, you can use the Oracle WebLogic Server Administration Console, Oracle WebLogic Scripting Tool (WLST), or create your own Java Management Extension (JMX) client. In addition, you can use Fusion Middleware Control Console for some tasks.
Oracle WebLogic Server Administration Console and Fusion Middleware Control run in the Administration Server. Oracle WebLogic Server Administration Console is the Web-based administration console used to manage the resources in an Oracle WebLogic Server domain, including the Administration Server and Managed Servers. Fusion Middleware Control is a web-based administration console used to manage Oracle Fusion Middleware, including components such as Oracle HTTP Server and Oracle Portal and product suites such as Oracle SOA Suite, Oracle WebCenter, and Oracle Identity Management.
Managed Servers host business applications, application components, Web services, and their associated resources. To optimize performance, Managed Servers maintain a read-only copy of the domain's configuration document. When a Managed Server starts up, it connects to the domain's Administration Server to synchronize its configuration document with the document that the Administration Server maintains.
When you create a domain, you create it using a particular domain template. The domain template contains all of the information you would like to include in your domain configuration. The template can then be used for additional installations. That template supports a particular component or group of components, such as the Oracle SOA Suite. The Managed Servers in the domain are created specifically to host those particular Oracle Fusion Middleware components.
Oracle Fusion Middleware Java components (such as Oracle SOA Suite, Oracle WebCenter, and some Oracle Identity Management components), as well as customer-developed applications, are deployed to Managed Servers in the domain.
Managed servers are Java Virtual Machine (JVM) processes.
If you want to add other components, such as Oracle WebCenter, to a domain that was created using a template that supports another component, you can extend the domain by creating additional Managed Servers in the domain, using a domain template for the component that you want to add. For more information, see "Extending A Domain to Support Additional Components" in the Oracle Fusion Middleware Administrator's Guide.
For production environments that require increased application performance, throughput, or high availability, you can configure two or more Managed Servers to operate as a cluster. A cluster is a collection of multiple Oracle WebLogic Server server instances running simultaneously and working together to provide increased scalability and reliability. In a cluster, most resources and services are deployed identically to each Managed Server (as opposed to a single Managed Server), enabling failover and load balancing. A single domain can contain multiple Oracle WebLogic Server clusters, as well as multiple Managed Servers that are not configured as clusters. The key difference between clustered and non-clustered Managed Servers is support for failover and load balancing. These features are available only in a cluster of Managed Servers.
For more information see"Understanding WebLogic Server Clustering" in Oracle Fusion Middleware Using Clusters for Oracle WebLogic Server
Node Manager is a Java utility that runs as a separate process from Oracle WebLogic Server and enables you to perform common operations for a Managed Server, regardless of its location with respect to its Administration Server. While use of Node Manager is optional, it provides valuable benefits if your Oracle WebLogic Server environment hosts applications with high-availability requirements. The Node Manager performs some of the following operations:
If you run Node Manager on a computer that hosts Managed Servers, you can start and stop the Managed Servers remotely using the Fusion Middleware Control Console or the command line. Node Manager can also automatically restart a Managed Server after an unexpected failure.
For more information about Node Manager see the Oracle Fusion Middleware Node Manager Administrator's Guide for Oracle WebLogic Server.
An Oracle instance contains one or more system components, such as Oracle Web Cache, Oracle HTTP Server, or Oracle Internet Directory. The system components in an Oracle instance must reside on the same computer. An Oracle instance directory contains updatable files, such as configuration files, log files, and temporary files.
An Oracle instance is a peer of an Oracle WebLogic Server domain. Both contain specific configurations outside of their Oracle homes.
The directory structure of an Oracle instance is separate from the directory structure of the Oracle home. It can reside anywhere; it need not be within the Middleware home directory.
A Middleware home can reside on a local file system or on a remote shared disk that is accessible through as network file system (NFS).
A WebLogic Server home contains installed files necessary to host a WebLogic Server. The WebLogic Server home directory is a peer of Oracle home directories and resides within the directory structure of the Middleware home.
An Oracle home contains installed files necessary to host a specific component or software suite. For example, the SOA Oracle home contains a directory that contains binary and library files for Oracle SOA Suite.
An Oracle home resides within the directory structure of the Middleware home. Each Oracle home can be associated with multiple Oracle instances or Oracle WebLogic Server domains. There can be multiple Oracle homes within each Middleware home.
The Oracle Common home contains the binary and library files required for Fusion Middleware Control and Java Required Files (JRF). There can be only one Oracle Common home within each Middleware home. The Oracle Common home is installed as part of a typical Fusion Middleware component installation. It is important to note, however, that a domain created with the WebLogic standard Configuration Wizard does not include the Fusion Middleware (EM) Control or Java Required Files (JRF). To manually add the JRF files to a managed server or cluster-only installation, see "Applying Oracle JRF to a Managed Server or Cluster" in Oracle Fusion Middleware Administrator's Guide.
The Oracle Metadata Repository contains metadata for Oracle Fusion Middleware components, such as Oracle BPEL Process Manager, Oracle B2B, and Oracle Portal. It can also contain metadata about the configuration of Oracle Fusion Middleware and metadata for your applications.
A metadata repository can be database-based or file-based. If it is database-based, you can create it in an existing database using the Repository Creation Utility (RCU).
Oracle Fusion Middleware supports multiple repository types. A repository type represents a specific schema or set of schemas that belong to a specific Oracle Fusion Middleware component (for example, Oracle SOA Suite or Oracle Internet Directory.)
A particular type of repository, the Oracle Metadata Services (MDS) repository, contains metadata for most Oracle Fusion Middleware components, such as Oracle B2B, and for certain types of applications.
A farm is a collection of components managed by Fusion Middleware Control. It can contain Oracle WebLogic Server domains, one Administration Server, one or more Managed Servers, and the Oracle Fusion Middleware components that are installed, configured, and running in the domain.
This section includes the following topics:
The top-level directory for all Oracle Fusion Middleware products is called the Middleware home; this directory is created when Oracle WebLogic Server is installed. The WebLogic home directory is inside the Middleware home, and is also created when Oracle WebLogic Server is installed. Figure 2-4 shows the directory structure after a Oracle WebLogic Server installation.
The Oracle home directories (in this case, the SOA Oracle home) for each product must reside inside an existing Middleware home directory (see Figure 2-5).
Before running the installation, you can create your Oracle home directory on your system. Remember that the Oracle home must reside inside the Middleware home directory, and it must also be an empty directory. Then, when you run the installer and are asked to provide the location of your Oracle home, you can specify the directory you have created.
While running the installer, you can specify the name of a new directory. This directory are automatically be created for you by the installer and will be located inside the Middleware home directory.
After a product is installed, it can be configured into an Oracle WebLogic Server Domain (see Section 2.4, "What Is an Oracle WebLogic Server Domain?".
The User Projects directory is created when you create or configure a domain (in this case, a SOA domain). By default, new domains are created inside the Domains folder, but you can choose to create these elsewhere.
If you install multiple products and choose to create a separate domain for each product, then your directory structure would look something like the one shown in Figure 2-7.
Each product has its own Oracle home directory. To differentiate among all the product Oracle home directories, the installation guides typically refer to each Oracle home by product name; for example, the Oracle home for Oracle SOA Suite is referred to as the SOA Oracle home, while the Oracle home for Oracle WebCenter Suite is referred to as the WebCenter Oracle home.
If you choose to create multiple domains on a single computer, ensure that each domain has a unique name.
For more information about multiple products and multiple domains, see the following documentation:
During installation and configuration, you may choose to create an existing domain rather than to create a new domain. Extending a domain means that you add products and functionality to an existing domain. If, for example, you first install Oracle SOA Suite to create a new domain, then install Oracle WebCenter Suite while choosing to extend the existing Oracle SOA Suite domain, then your topology would look like the one shown in Figure 2-8.
In essence, you are adding the products and functionality of Oracle WebCenter Suite to the existing Oracle SOA Suite domain.
Figure 2-9 shows the directory structure when two products are installed, but one product (Oracle SOA Suite) is configured in a Oracle WebLogic Server domain (because it consists of Java components) while the other products (Oracle HTTP Server and Oracle Web Cache) is configured in an Oracle Instance (because it consists of system components):