Oracle Fusion Middleware is a comprehensive family of products ranging from application development tools and integration solutions to identity management, collaboration, and business intelligence reporting.
This chapter provides an introduction to Oracle Fusion Middleware and contains the following topics:
This book is an administration quick-start guide that teaches you how to perform day-to-day administrative tasks for Oracle Fusion Middleware. The goal of this book is to help you understand the concepts behind Oracle Fusion Middleware. It teaches you how to perform common administration tasks needed to keep the application server operational, including how to perform basic troubleshooting and performance monitoring activities.
The primary administrative interface used in this book is Oracle Enterprise Manager Fusion Middleware Control.
This book is task oriented. The objective is to describe why and when administrative tasks need to be performed. Where appropriate, it describes the concepts necessary for understanding and completing the task at hand, assuming the reader has no prior knowledge of Oracle Fusion Middleware and the application server.
This book is not an exhaustive discussion of all Oracle Fusion Middleware concepts or administration tasks. For this type of information, refer to Oracle Fusion Middleware Concepts and the Oracle Fusion Middleware Administrator's Guide.
This book is part of a comprehensive set of learning material for administering Oracle Fusion Middleware, including other documentation and Oracle University classes.
At the end of each chapter in this book, you will find pointers to additional information.
Oracle Fusion Middleware is a comprehensive family of products ranging from Java EE and development tools, to integration solutions, to identity management, collaboration, and business intelligence reporting. Oracle Fusion Middleware offers complete support for development, deployment, and management.
Oracle Fusion Middleware provides the following components:
Oracle WebLogic Server, an enterprise-ready Java application server that supports the deployment of mission-critical applications in a robust, secure, highly available, and scalable environment. Oracle WebLogic Server is an ideal foundation for building applications based on service-oriented architecture (SOA).
Oracle SOA Suite, a complete set of service infrastructure components, in a service-oriented architecture, for designing, deploying, and managing composite applications. Oracle SOA Suite enables services to be created, managed, and orchestrated into composite applications and business processes. Composites enable you to easily assemble multiple technology components into one SOA composite application.
Oracle WebCenter Portal, an integrated set of components with which you can create social applications, enterprise portals, collaborative communities, and composite applications, built on a standards-based, service-oriented architecture. Oracle WebCenter Portal combines dynamic user interface technologies with which to develop rich internet applications, the flexibility and power of an integrated, multi-channel portal framework, and a set of horizontal Enterprise 2.0 capabilities delivered as services that provide content, collaboration, presence, and social networking capabilities. Based on these components, Oracle WebCenter Portal also provides an out-of-the-box enterprise-ready customizable application, WebCenter Portal: Spaces, with a configurable work environment that enables individuals and groups to work and collaborate more effectively.
Oracle WebCenter Content, an integrated suite of products designed for managing content. This enterprise content management platform enables you to leverage industry-leading document management, Web content management, digital asset management, and records management functionality to build your business applications. Building a strategic enterprise content management infrastructure for content and applications helps you to reduce costs, easily share content across the enterprise, minimize risk, automate expensive, time-intensive, and manual processes, and consolidate multiple Web sites onto a single platform.
Oracle HTTP Server, which provides a Web listener for Java EE applications and the framework for hosting static and dynamic pages and applications over the Web. Based on the proven technology of the Apache HTTP Server, Oracle HTTP Server includes significant enhancements that facilitate load balancing, administration, and configuration.
Oracle Identity Management, which provides a shared infrastructure for all Oracle applications. It also provides services and interfaces that facilitate third-party enterprise application development. These interfaces are useful for application developers who need to incorporate identity management into their applications.
Oracle Internet Directory, a general purpose directory service that enables fast retrieval and centralized management of information about dispersed users and network resources. It combines Lightweight Directory Access Protocol (LDAP) Version 3 with the high performance, scalability, robustness, and availability of an Oracle Database.
Oracle Virtual Directory, an LDAP version 3 enabled service that provides virtualized abstraction of one or more enterprise data sources into a single directory view. Oracle Virtual Directory provides the ability to integrate LDAP-aware applications into diverse directory environments while minimizing or eliminating the need to change either the infrastructure or the applications. It supports a diverse set of clients, such as Web applications and portals, and it can connect to directories, databases, and Web services.
Oracle Identity Federation, a self-contained federation solution that provides the infrastructure that enables identities and their relevant entitlements to be propagated across security domains—this applies to domains existing within an organization as well as between organizations.
Oracle Web Services Manager, which provides a way to centrally define and manage policies that govern Web services operations, including access control (authentication and authorization), reliable messaging, Message Transmission Optimization Mechanism (MTOM), WS-Addressing, and Web services management. Policies can be attached to multiple Web services, requiring no modification to the existing Web services.
Oracle Platform Security Services (OPSS), which provides enterprise product development teams, systems integrators, and independent software vendors (ISVs) with a standards-based, portable, integrated, enterprise-grade security framework for Java Standard Edition (Java SE) and Java Enterprise Edition (Java EE) applications.
OPSS provides an abstraction layer in the form of standards-based application programming interfaces (APIs) that insulate developers from security and identity management implementation details. With OPSS, developers do not need to know the details of cryptographic key management or interfaces with user repositories and other identity management infrastructures. Using OPSS, in-house developed applications, third-party applications, and integrated applications benefit from the same uniform security, identity management, and audit services across the enterprise.
Oracle Portal, a Web-based tool for building and deploying e-business portals. It provides a secure, manageable environment for accessing and interacting with enterprise software services and information resources. A portal page makes data from multiple sources accessible from a single location.
Oracle Business Intelligence, a complete, integrated solution that addresses business intelligence requirements. Oracle Business Intelligence includes Oracle BI Enterprise Edition, Oracle Business Intelligence Discoverer, Oracle Business Intelligence Publisher, and Oracle Real-Time Decisions.
You can also use Oracle Fusion Middleware with IBM WebSphere. For more information, see the Oracle Fusion Middleware Third-Party Application Server Guide.
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 Portal 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). 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 you install and configure Oracle Fusion Middleware, your Oracle Fusion Middleware environment contains the following:
An Oracle WebLogic Server domain, which contains one Administration Server and one or more Managed Servers. The Administration Server contains Oracle WebLogic Server Administration Console and Oracle Enterprise Manager Fusion Middleware Control. The Managed Servers contain components, such as Oracle WebCenter Portal and Oracle SOA Suite. See Section 1.3.1 for more information about domains.
If your environment includes system components, one or more Oracle instances. See Section 1.3.2 for more information about Oracle instances.
A metadata repository, if the components you installed require one. For example, Oracle SOA Suite requires a metadata repository. See Section 1.3.6 for more information about metadata repositories.
Figure 1-1 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 includes a metadata repository.
Your environment also includes a Middleware home, which consists of the Oracle WebLogic Server home, and optionally, an Oracle Common home and one or more Oracle homes. See Section 1.3.3 for more information about a Middleware home.
An Oracle 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 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. The top-level directory of a domain is referred to as the domain home.
An Oracle WebLogic Server domain is a peer of an Oracle instance. Both contain specific configurations outside of their Oracle homes.
Figure 1-2 shows an Oracle WebLogic Server domain with an Administration Server, three standalone Managed Servers, and three Managed Servers in a cluster.
Oracle Fusion Middleware Understanding Domain Configuration for Oracle WebLogic Server for more information about domain configuration
The following topics describe entities in the domain:
The Administration Server operates as the central control entity for the configuration of the entire WebLogic Server 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 manage and monitor all resources in a domain.
Each Oracle WebLogic Server 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 JMX client. In addition, you can use Fusion Middleware Control for some tasks.
Fusion Middleware Control and the WebLogic Administration Console run in the Administration Server. Fusion Middleware Control is a Web-based administration console used to manage Oracle Fusion Middleware, including components such as Oracle HTTP Server, Oracle SOA Suite, Oracle WebCenter Portal, Oracle Portal, and Oracle Identity Management components. 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.
Section 2.2 for more information about Fusion Middleware Control
Section 2.3, as well as the Oracle Fusion Middleware Introduction to Oracle WebLogic Server and the Oracle WebLogic Server Administration Console Online help, for more information about Oracle WebLogic Server Administration Console
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, 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. That template supports a particular component or group of components, such as 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 Portal, and some Identity Management components), as well as customer-developed applications, are deployed to Managed Servers in the domain.
If you want to add other components, such as Oracle WebCenter Portal, 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 which you want to add. See Section 9.2 for more information.
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 WebLogic 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 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.
Node Manager is a Java utility that runs as a separate process from Oracle WebLogic Server and allows 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.
If you run Node Manager on a computer that hosts Managed Servers, you can start and stop the Managed Servers remotely using the Administration Console or the command line. Node Manager can also automatically restart a Managed Server after an unexpected failure.
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. However, unlike a domain, which can span multiple hosts, an Oracle instance must be located on a single host.
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 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 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.
As an administrator for Oracle Fusion Middleware, you can expect to be involved in the following tasks:
Installing Oracle Fusion Middleware software
Performing the initial configuration of the software
Configuring a metadata repository
Managing administrative accounts
Monitoring the environment
Backing up and recovering your Oracle Fusion Middleware environment
The following are some of the tools and utilities that you can use in administering Oracle Fusion Middleware:
Fusion Middleware Control is a Web-based interface and is one of the primary tools for managing your Oracle Fusion Middleware environment. With it, you can check the status of the components, start and stop components, deploy Java EE applications, and perform other administrative tasks, such as creating clusters and managing log files. See Section 2.2.
Oracle WebLogic Server Administration Console
The Oracle WebLogic Server Administration Console is a Web browser-based, graphical user interface that you use to manage an Oracle WebLogic Server domain. See Section 2.3.
WebLogic Scripting Tool (WLST)
The WebLogic Scripting Tool (WLST) is a command-line scripting environment that you can use to create, manage, and monitor Oracle WebLogic Server domains. See Section 2.4.1.
Oracle Process Manager and Notification Server (OPMN)
Oracle Process Manager and Notification Server (OPMN) manages and monitors a particular type of Oracle Fusion Middleware components, referred to as system components. See Section 2.4.2.
The Repository Creation Utility (RCU) creates a metadata repository in an existing database. You can use it to create a repository for overall configuration information and for configuration information for particular components. Not all Oracle Fusion Middleware components need a database-based metadata repository, but some, like the Oracle SOA Suite, do. See Section 3.2.1 for more information about RCU.
An MBean is a Java object that represents a JMX manageable resource. Each manageable resource within the application server, such as an application or a resource adapter, is managed through an instance of the appropriate MBean. Each MBean exposes a management interface that is accessible through the System MBean Browser in Fusion Middleware Control. You can set MBean attributes, execute operations to call methods on an MBean, subscribe to notifications of errors or specific events, and display execution statistics.
For more information, see the section "Using the Fusion Middleware Control MBean Browser" in the Oracle Fusion Middleware Administrator's Guide.