El menú Acciones

Oracle Fusion Middleware is a collection of standards-based software products that spans a range of tools and services: from Java EE and developer tools, to integration services, identity management, business intelligence, and collaboration. Oracle Fusion Middleware offers complete support for development, deployment, and management.

Oracle Fusion Middleware Components

Middleware is a term used to describe computer software that connects software components or applications. Middleware is used most often to support complex, distributed business software applications. Middleware includes Web servers, application servers, content management systems,

and similar tools that support application development and delivery. Middleware is especially integral to information technology based on Extensible Markup Language (XML), Simple Object Access

Protocol (SOAP), Web services, and Service-Oriented Architecture (SOA).

Oracle Fusion Middleware is a collection of standards-based software products that spans a range of tools and services, from a Java Enterprise Edition 5 (Java EE)–compliant environment and developer tools to integration services, business intelligence, collaboration, and content management. Oracle Fusion Middleware offers complete support for development, deployment, and management.

Oracle Fusion Middleware offers solutions and support to support complex, distributed business software applications. It includes Web servers, application servers, content management systems, and similar tools that support application development and delivery.

Oracle Weblogic

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.

Design and Development Tools:

Is a single integrated, but modular, design tool to build a complete application (rather than too many specialized tools). The design tool includes a single design environment for user interface, business logic, service composition, business process or workflow, business rules, and business intelligence. The design tool enables you to simplify design and debugging and improve productivity.

Application Server:

Is a standards-based Java EE application server to run enterprise applications and provide the Web Services infrastructure for interoperability

User Interaction:

Is a single, end-user environment that allows users to access their enterprise applications, business processes, and business intelligence and share information with each other. This end-user

environment is multichannel, so it can be accessed from a variety of different clients (mobile clients, desktop clients, Voice-over IP clients, and so on).

Business Intelligence:

Is a suite of business intelligence tools from extract, transform, and load (ETL) to integrate data into warehouses; query, analysis, and reporting tools for decision support; and scorecards to compare how the business is doing against key performance indicators and alerting to drive notifications to users based on problems in the business

Enterprise Content Management:

Is a repository within which to manage documents, digital assets, scanned images, and other forms of content to integrate this content with a company’s enterprise applications, Web sites, and business processes

Security and Identity Management:

Lowers the cost of security administration across multiple applications and systems in an enterprise by centralizing how you create and provision users, their identities, and roles and enable them to have single sign-on access

Enterprise Management:

Lowers the cost of operations and administration by running middleware on a grid architecture with grouping, backup, and other high availability technologies and integration with Oracle Enterprise Manager for systems management

Oracle Identity and Access Management

Enables you to centralize identity and access management Requires a Java EE environment for operation

Can be easily configured as the central system for use in the WebLogic environment

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 Portal, Forms, and Reports Portal:

Is a Web-based interface that uses wizards Requires Oracle Database

Uses a Portal Developer Kit to extend via programming

Portal offers a complete and integrated framework for building, deploying, and managing enterprise portals. Oracle Portal delivers a unified and secure point of access to all enterprise information and services to improve business visibility and collaboration, reduce integration costs, and ensure investment protection.

Common installation/configuration steps:

Install Database (if needed).

Install Repository Creation Utility (if needed). Install WebLogic Server.

Configure all software.

Common operations:

The components run in a Java EE Container such as WebLogic Server.

Common administration:

Enterprise Manager oversees all the products at a high level. Each component has its own administration console for finer detail.

Java components:

Java components are 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.

System components:

This 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) Server. Some of the system components are Oracle HTTP Server, Oracle Web Cache, Oracle Internet Directory, Oracle Virtual Directory, Oracle Forms Services, and so on.

The arrows indicate that data from the two components (Java and System/OPMN) may have database dependencies as well. For instance, SOA and OID require a Metadata Repository, whereas Forms and OHS do not. Customer Java apps has customer data, whereas OHS does not. SOA is managed through the Admin interfaces, whereas OID is managed through the OPMN interfaces (this is a slight oversimplification, but good

enough for an overview). And, the database management can be Oracle or anything (for example, DB2, Sybase, Microsoft, and so on) and therefore is outside the control of the FMW environment as such.