1, Oracle Fusion Middleware Products
1.1 Integrated development Environment (IDE): Oracle JDeveloper, Oracle Enterprise Pack for Eclipse
1.2 Application Development Framework: Application Development Framework (ADF)
1.3 Application grid: WebLogic Server
1.4 Identity Management: Directory services, access management, identity Federation, fraud detection, entitlement services, identity management, identity analysis
1.5 Service-Oriented Architecture (SOA): Oracle SOA Suite, Oracle Service Bus (OSB)
1.6 User experience: Oracle Application Development Framework (ADF), Oracle Webcenter
1.7 Content Management: General content management, general records management, image and process management, Information Rights Management
1.8 Integration: Oracle Data Integrator (ODI), Oracle Golden Gate
1.9 Commercial Intelligence: Business Intelligence Enterprise Edition (OBIEE), Biz Intelligence Publisher
2, Oracle WebLogic Server
2.1 Structure: WebLogic Server domain ==> Management Server (admin servers), managed server (for deploying Java EE applications), Node Manager
2.2 Application Container
2.2.1 Web container: HTTP servlet and Java Server Page (JSP)
2.2.2 Enterprise Java Bean (EJB) Container: stateless/stateful Session Beans, Message driven Beans (SFSB/SLSB provides an interface, Can be used to configure local calls and remote calls, for MDB, to receive messages from their destination)
2.2.3 Web Services Container: The most common transport protocol for Web Services is HTTP
2.3 Application Deployment: Enterprise Archive (EAR) = Web Archive (WAR) + Java Archive (JAR) (War:web container and Web service container, JAR:JPA container and EJB container)
2.4 Management features: WebLogic Server Scripting Tool (WLST): Scripting tools that contain a number of pre-packaged operations for domain management.
The 2.4.1 WebLogic Java Management Extension MBean server:jmx is the backbone for building the WebLogic Server Configuration Foundation, which can be managed at runtime by the JMX MBean server configuration.
2.4.2 Each managed server has two Mbean servers: Runtime server and Platform server. The runtime server resides in two types of Mbean, the first of which is the configuration Mbean, which is used for the initialization of the managed server. The second class is the runtime MBean, which is initialized by the server. The platform server resides on the JVM's platform Mbean.
The 2.4.3 Management Server also has two additional Mbean servers: the Domain runtime server and the edit server.
2.5 Authentication and Authorization services
2.5.1 Embedded LDAP, Weblogic server contains an embedded LDAP server for identity identification and role mapping and authorization policy repositories.
2.6 JDBC Service: Java EE applications deployed to WebLogic server require access to the database through a JDBC data source. WebLogic Server JDBC Data source encapsulates the JDBC driver, connection information.
2.7 JMS Service: The JMS server is responsible for managing the destination by receiving messages sent by the JMS client sender, logging the properties and destination of the message, and finally ensuring that the message is sent to the consumer and/or subscribers of the destination.
2.8 WebLogic Server Request Management: Work Manager: Used to control the entities that assign requests to threads.
2.9 Use case: JMS message [queue] ===> ; Web Service Interface (Web service container) ===> DB (update data with JPA)
Web Application (JSP, Servlet, SLSB) ===> deployed in WebLogic Server Web container/EBJ container ===> Embedded LDAP save group and User (Security Service)
SLSB====================>JDBC data source ===> JNDI ===>db
3,fusion Middleware Public infrastructure
3.1 Opmn:oracle Process Manager and Notification, Oracle processes manager and notifications. Used to start, stop, and automatically restart the system components, allow the status, metrics and log information of the mobile system components, and provide access points for the information, and provide bridge junctions for Fusion middleware instance and domain integration.
3.2 Enterprise Manager Fusion Middleware Control: is a Web-based application that allows you to centrally manage all the components of the Fusion middleware specified farm.
3.2.1 Component Startup and shutdown: Start and stop Fusion Middleware Farm deployed Java EE applications, domain servers, and system components. EM uses the underlying WebLogic server Mbean to start and stop applications and WebLogic server instances. For stopping and starting the system components, EM calls the OPMN process directly, performing the stop and start system component operations through OPMN.
3.2.2 Indicator Monitoring: The performance indicator of EM is obtained through the JRF layer component of the dynamic monitoring Service (DMS).
3.2.3 Log Management: The log management function of EM is provided through the JRF Layer component Oracle Diagnostic Logging (ODL).
3.3 Meta Data repository services: Metadata Repository Service (MDS), MDS metadata content is stored in a file-based or database-based repository. The schema-based MDS Repository is created with RCU, and the file-based repository can be any file system directory.
3.4 Oracle Web Services Manager (OWSM, Oracle Web Service Manager) is able to create, manage, and implement security and management policies related to WEB services deployed in the WebLogic server domain.
3.5 Use Cases: Web services ====> Domain ====> extensions for Oracle SOA Suite ====> SOA-based application domains ====> WEB applications [frontend] <==== Oracle HTTP Ser Ver (OHS) (Send message)
Enterprise Manager Management
==>oracle Web Services Manager (OWSM)-Secure the application Web service
4, Platform security services and identity management (LDAP is typically used for authentication management, RDBMS is typically used to store data)
4.1 Platform Security Service: Oracle Platform Security Services, OPSS, OPSS is built on WebLogic Server security services and provides a rich API for application security integration.
4.1.1 Identity Store: The domain identity store must be configured for OPSS to recognize all end users. Create users and groups through an embedded LDAP server. Executed through the WebLogic Server Management console and Wlst.
4.1.2 Policy Store: Supports file-based, LDAP-based, and RDBMS-based policy storage.
4.1.3 Credential Store: Two types of credentials, one is the password credential consisting of a user name and password, and the other is a generic credential that encapsulates all custom data or any token (such as a symmetric key).
4.2 apm:authorization policy manager for managing OPSS-based authorization policies. It is designed for managing enterprise applications that use services.
4.3 Oracle Identity Management: The Oracle Identity Management product suite can create a service-oriented security architecture.
4.3.1 Oracle Internet Directory (OID): An LDAP directory server built on top of an oracle RDBMS. Enterprise Manager and Wlst provide a UI and command-line interface for the daily management of the product.
4.3.2 Directory Integration Platform (DIP): Dip supports synchronizing LDAP data with other directories and also supports RDBMS integration with identity data.
4.3.3 Oracle Directory Server Enterprise Edition (odsee): An LDAP directory server with a core directory services architecture built on top of an embedded database.
4.3.4 Oracle virtual directory (OVD), a directory virtualization solution that enables multiple LDAP directory information to be presented in a single directory or schema. Provides a virtualized layer on top of existing identity stores and provides a unique, unified view of the data through the LDAP interface. OVD integrates Enterprise Manager and WLST for system management.
4.3.5 Oracle Access Manager (OAM) centralizes Web Access control by providing authentication, authorization, and single sign-on solutions, as well as comprehensive policy management, session management, and agent management capabilities. It is easy to integrate with some well-known LDAP servers (OID, Odsee, OVD).
4.3.6 Oracle Enterprise single sign-on (ESSO): Provides a workaround that enables end users to access all of these resources in one-sign-on basis.
4.3.7 Oracle Adaptive Access Manager (OAAM): Oracle Adaptive Access Manager provides a next-generation access management solution that goes beyond user authentication. Including fingerprint identification, virtual identity authentication device, one-time password problem. The OAM can be integrated directly.
4.3.8 Oracle Identity Manager (OIM): An identity manager that manages the user's lifecycle and controls how access is provided to the user.
4.4 Use case: OAM Single Sign-on ===> Oracle HTTP Server location installation webgate ===> [Access] Configure identity store (Configure an LDAP identity authenticator) OID <==== User & Role AP I provide retrieving user and group information for the application
The application needs access to the RDBMS to obtain the data, and in order to better manage the database access credentials, the credentials are created in the domain credential store.
5, Oracle SOA Suite Introduction
5.1 Oracle Service-oriented Architecture (SOA) suite products provide a platform for enterprises to adopt a unified service-oriented IT infrastructure. The infrastructure enables businesses to manage IT services more efficiently and flexibly, and to create new value-added services more efficiently.
The core components of the 5.1.1 SOA suite are the SOA infrastructure, Business Activity Monitoring (BAM), and the User messaging Service (UMS).
5.2 SOA infrastructure components are comprised of an environment-based service component Architecture (Services Component Architecture SCA), including business Process Execution Language (BPEL), Business process Modeling notation (BPMN), mediation, user tasks, business rules, Spring Serviced components.
5.2.1 Service Component Architecture, SCA, a component is a module that encapsulates all of the semantic-related logic and provides an explicit interface that contains all the information that external entities have access to internal functionality. SCA is a specification used to define a metadata-driven model (XML) that describes a software application consisting of loosely coupled components, each of which can be implemented by different technologies.
5.2.2, the so-called combination of SCA, all application business logic developed for the SOA infrastructure exists in the form of an SCA combination.
5.2.3 Deployment Mix: The SOA mix is packaged into a jar file called the SOA archive, the SAR, for deployment to the SOA server. In order to deploy the SAR file in the SOA server, you can use the Jdeveloper,em, Wlst command. The SOA Suite portfolio is deployed directly in the SOA infrastructure container, not by using WebLogic Server.
5.2.4 Combined Services and references, a deployed combination can expose its services to enable external entities to use their functionality. A combination can also depend on services that are exposed by external entities. Available SOA Suite services, Web services, HTTP services, ADF BC Services, Java Connector Framework (JCA), EJB, direct service (dedicated Oracle interface).
5.3 Oracle Business Activity Monitoring (BAM): A component of the SOA suite that captures data from runtime applications and their processing, aggregates, and renders as real-time business reports.
5.3.1 Oracle BAM Data Objects are data structures defined by technical users through the [Oracle BAM Architect Web application] to identify application information that needs to be collected and presented to business users. Once the Oracle BAM object is defined, the business user is able to define the report using [Oracle BAM Active Studio Web application], which is a Web page, and once the report is defined, other business users can go through the [Oracle BAM Active V Iewer WEB application] to view report results.
The 5.3.2 Oracle BAM functionality is split into two tiers: the Oracle BAM Server tier and the Oracle BAM Web tier.
The 5.3.3 Oracle BAM server tier contains all the components that are used to gather information from different sources and map this information to specific data objects. Information update requests that are mapped to data objects are sent by an external source as an Oracle BAM command to the Oracle BAM server.
5.3.4 Oracle BAM Web: Contains a collection of Web applications, including Oracle BAM active Studio, Oracle BAM active Viewer, Oracle BAM Architect, Oracle BAM Administrator.
5.4 User Message Service (UMS): Through UMS, applications can interact directly with end users using different types of message protocols. The UMS consists of two main components: the UMS server and the UMS driver. The UMS server provides interaction between the Java EE program and the corresponding application, as well as the UMS driver. UMS drivers include instant messaging, Email, voicemail,sms, and SOA Suite human Task worklist.
5.5 Use case: ERP system ====> update message file ===> worklist ===> [UPDATE request command] ===> Oracle BAM Server ====> user Terminal application
SOA Server (SOA Mix) ===> Human Task component <==== OPSS
Application WebLogic Server domain <==== embedded LDAP server ===> [set users, groups and roles]
6, Oracle ADF
6.1 ADF Architecture: The Oracle Application Development framework in the ADF is based on an MVC architecture designed to decouple business logic, navigation, and user interfaces.
6.1.1 Model layer: The ADF business component, which is used to establish service and salesman logic. Also known as the Business Services layer, can be implemented through Ejb,pojo or Web services.
6.1.2 View layer: Use the user interface components in ADF faces to be used in Web applications created by JSF. The ADF binding layer enables declarative data and modulo binding to provide a view and controller with an abstraction above the business layer.
6.1.3 Control layer: Adfcontroller for input processing, navigation and control.
6.2 ADF metadata and customization: The Core Infrastructure component in Fusion Middleware, which provides a single, unified metadata repository. This repository is used to deploy and manage metadata for all components and applications in fusion middleware.
6.2.1 MDS supports customizing these features by providing a common framework for metadata customization, which is stored as a separate incremental document in the MDS repository and merged with the seed artifacts at run time.
6.3 Use case: ERP system ====> update message file ===> SOA server (update <===> worklist apps) ====> user Terminal application
MDS Database (worklist [provides different user interface],OWSM, ... ）
7, Oracle Webcenter
7.1 Webcenter is Oracle's portal, user interaction and Enterprise2.0 product suite.
7.1.1 Portal Technology presents relevant information and services from multiple applications to targeted users in an efficient and customizable manner.
7.1.2 Webcenter Composer: Provides an easy-to-use, browser-based user interface for business users. All pages that are integrated in Webcenter composer have two modes: view mode and edit mode. The faces component in composer technology provides a mechanism for editing pages. Composer provides two mechanisms to provide custom functionality, and one mechanism is to support user gestures that generate personalization through the composer component in view mode. The other is to support more complex changes in edit mode.
7.1.3 Customizable components: features provided by ADF technology for implicit personalization: such as reordering the columns of a table, persisting it as personalization persisted in the MDS repository. Also webcenter composer can provide this functionality, and add-ons that provide this functionality are called customizable components.
7.1.4 webcenter Enterprise 2.0 services: Services include social computing services, personal tags, ADF task flow, data controls, APIs, and expression language El expressions.
7.2 Webcenter Portal Technology: Portal applications showcase information and services from multiple applications to targeted users in an efficient, customizable way. , and portal technology can build this portal application. A portal is a reusable Web component that can display content from many different sources.
7.2.1 Portal Producer: The application that hosts and renders the portal
7.2.2 Portal Consumer Applications: Also known as portals, use portals from other enterprise applications that are producers of portals.
Two types of 7.2.3 portal producers are based on implementation technology: remote portal producer's Web Service (WSRP) and Java Producer's Portal Development Kit (JPDK).
7.2.4 Portal Customizations and personalization: You can customize the settings portal properties so that these customizations can affect all users of a certain portal instance. At the same time, authenticated users can personalize portal properties so that the logic or appearance of the portal is personalized for that user.
7.3 Webcenter Space: space is a Java EE application built using the ADF and Webcenter frameworks. The application inherits the Webcenter Enterprise2.0 service, Webcenter Portal technology, and Webcenter Composer.
7.4 Use case: ERP system ===> update message file ====> SOA server (update <===> worklist apps) ====> user Terminal application
MDS Database (worklist [provides different user interface],OWSM, ... ）
ERP <==== webcenter Domain (Portal application ===> discussions Server [discussions application]) ====> Portal
Oracle Fusion Middleware Basics Summary