Oracle® Fusion Middleware

Glossary

12c (12.2.1.2)

E77932-01

October 2016

A glossary containing terms related to Oracle Fusion Middleware and the definition of those terms.

Oracle Fusion Middleware Glossary, 12c (12.2.1.2)

E77932-01

Copyright © 2013, 2016 Oracle and/or its affiliates. All rights reserved.

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable:

U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

This software or hardware and documentation may provide access to or information about content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.

Contents

Preface

- Audience

- Documentation Accessibility

- Related Documents

- Conventions

Glossary

Preface

This glossary contains definitions of all terms defined in books included in the Fusion Middleware 12c (12.2.1.2) library.

Audience

This document is intended for administrators, developers, business users and end users working with Fusion Middleware products.

Documentation Accessibility

For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.

Access to Oracle Support

Oracle customers that have purchased support have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.

Related Documents

For more information, see the following documents in the Oracle Fusion Middleware 12c (12.2.1.2) documentation set:

- Understanding Oracle Application Development Framework

- Understanding Oracle Fusion Middleware

- Understanding Oracle SOA Suite

- Understanding Oracle Web Services Manager

- Understanding Oracle WebLogic Server

- Understanding WebLogic Web Services for Oracle WebLogic Server

- Understanding Oracle WebCenter Content

- Administering Oracle WebCenter Portal

- Administering Oracle WebCenter Sites

- System Administrator's Guide for Oracle Business Intelligence Enterprise Edition

Conventions

The following text conventions are used in this document:

Convention

Meaning

boldface

Boldface type indicates graphical user interface elements associated with an action, or terms defined in text or the glossary.

italic

Italic type indicates book titles, emphasis, or placeholder variables for which you supply particular values.

monospace

Monospace type indicates commands within a paragraph, URLs, code in examples, text that appears on the screen, or text that you enter.

Glossary

Access Decision

WebLogic Server: Code that determines whether a subject has permission to perform a given operation on a WebLogic resource. The result of an Access Decision is to permit, deny, or abstain from making a decision. An Access Decision is a component of an Authorization provider.

access policy

Identity Management: A list of roles and resources to be provisioned or deprovisioned. Access policies are used to automate the provisioning of target systems to users.

action

Business Intelligence: Provides functionality to navigate to related content or to invoke operations, functions or processes in external systems. You can include actions in analyses, dashboard pages, agents, scorecard objectives, scorecard initiatives, and KPIs. See also action link.

action binding

JDeveloper/ADF: A binding for command components (such as buttons or links) to built-in or custom methods on the data control, or to built-in collection-level operations (such as Create, Delete, Next, or Previous). An action binding object encapsulates the details of how to invoke a method and what parameters (if any) the method is expecting.

Action Framework

Business Intelligence: A component of the Oracle BI EE architecture and includes a J2EE application called the Action Execution Service (AES) and actions-specific JavaScript functionality deployed as part of Oracle BI EE. Also includes client-side functionality for creating actions and invoking certain action types directly from the browser.

action link

Business Intelligence: A link to an action that you have embedded in an analysis, dashboard page, scorecard objective, scorecard initiative, or KPI that, when clicked, runs an associated action. See also action.

Active Data Service (ADS)

JDeveloper/ADF: A server-side push framework that allows you to provide real-time data updates for ADF Faces components. You bind ADF Faces components to a data source, and ADS pushes the data updates to the browser client without requiring the browser client to explicitly request it.

activity

SOA Suite: The building block of a BPEL process service component. Activities enable you to perform specific tasks within a BPEL process service component. Oracle BPEL Designer includes a set of activities that you drag into a BPEL process service component. You then double-click an activity to define its attributes (property values).

adapter data control

JDeveloper/ADF: A data control based on a framework that provides built-in support for features such as validation rules and list of value (LOV) objects. You can use the adapter framework to create a new data control type, or you can extend one of the existing data control types, such as the bean data control type.

addressing

Web Services: See Web Services Addressing (WS-Addressing)

ADF application

JDeveloper/ADF: An application using one or more of the following high-level Oracle ADF technologies: ADF Business Components, ADF Model, ADF Controller, and ADF Faces. In contrast, a Fusion web application uses all of these technologies.

ADF binding

JDeveloper/ADF: An ADF application object that abstracts the details of accessing data from a data collection in a data control and of invoking its operations. ADF bindings are defined in ADF page definition files.

ADF binding container

JDeveloper/ADF: A request-scoped map of a page's bindings based on the page's page definition file. In a JSF application, the binding container is accessible during each page request using the EL expression #{bindings}.

ADF binding context

JDeveloper/ADF: A container object that holds a list of available data controls and data binding objects. The DataBindings.cpx file defines the binding context for the application.

ADF binding filter

JDeveloper/ADF: A servlet filter that ADF web applications use to preprocess any HTTP requests that may require access to the binding context.

ADF Business Component

Business Intelligence: Provides the developer the ability to include Oracle BI Presentation Catalog objects in ADF Applications. This component uses a SOAP connection to access the catalog.

ADF Business Components

JDeveloper/ADF: A framework that simplifies the development, delivery, and customization of business applications for the Java EE platform. You use ADF Business Components to define associations between entity objects, view objects, and application modules to reflect the foreign keys present in the underlying tables.

ADF Business Intelligence Component

Business Intelligence: Provides the ability to include Oracle BI Presentation Catalog objects in ADF Applications. This component uses a SOAP connection to access the catalog.

ADF Controller

JDeveloper/ADF: A mechanism that provides an enhanced navigation and state management model on top of JSF. This mechanism declaratively defines navigation using control flow rules.

ADF data control

JDeveloper/ADF: XML configuration files that describe a service. At design time, JDeveloper uses the metadata to declaratively bind an operation or data collection to a UI component.

ADF Data Visualization components

JDeveloper/ADF: ADF Faces components that are capable of rendering dynamic charts, gauges, and other graphics that provide a real-time view of underlying data.

ADF Data window

JDeveloper/ADF: One of the ADF application debugging windows. Displays a list of data for a given application object selected in the ADF Structure window.

ADF Desktop Integration

JDeveloper/ADF: Provides a framework for Oracle Application Development Framework (Oracle ADF) developers to extend the functionality provided by a Fusion web application to desktop applications. The ADF Desktop Integration framework allows end users to avail themselves of Oracle ADF functionality when they are disconnected from their company network.

ADF Faces

JDeveloper/ADF: A set of standard JSF components that includes built-in AJAX functionality.

ADF Lifecycle Breakpoints window

JDeveloper/ADF: One of the ADF application debugging windows. Displays all ADF lifecycle execution points to set and check application lifecycle breakpoints. When the application is paused at an ADF lifecycle declarative breakpoint, an Execution Point icon appears next to the lifecycle phase in the ADF Lifecycle Breakpoints window.

ADF Model

JDeveloper/ADF: A module of Oracle ADF that implements service abstraction called the data control. Data controls enable a unified approach to bind any user interface to any business service, without the need to write code.

ADF region

JDeveloper/ADF: An ADF Faces component that renders the content of a bounded task flow.

ADF Security

JDeveloper/ADF: A framework that supports declarative, permission-based protection for ADF security-aware resources, such as ADF bounded task flows, top-level web pages that use ADF bindings, and attributes defined by ADF entity objects and their attributes. ADF Security is built on top of the Oracle Platform Security Services (OPSS) architecture, which in turn incorporates the Java Authentication and Authorization Service (JAAS) and Java EE container-managed security.

ADF skin

JDeveloper/ADF: A file that uses the format of CSS to specify CSS properties, ADF skin properties, global selectors, and selectors of the ADF skinning framework to customize the appearance of components that render in an ADF applications user interface.

ADF skinning framework

JDeveloper/ADF: The underlying APIs and parsers that enable the creation and registration of the ADF skins that generate the CSS to customize the appearance of ADF applications.

ADF Structure window

JDeveloper/ADF: One of the ADF application debugging windows (distinct from the JDeveloper Structure window). Displays the runtime structure of the ADF application. Works in combination with the ADF Data window to display a list of data for a given object selected in the ADF Structure window.

ADF task flow

JDeveloper/ADF: A set of ADF Controller activities, control flow rules, and managed beans that interact to allow a user to complete a task.

Adjudication provider

WebLogic Server: A WebLogic security provider that tallies the results that multiple Access Decisions return, resolves conflicts between the Access Decisions, and determines the final PERMIT or DENY decision.

administration port

WebLogic Server: A special, secure port that all WebLogic Server instances in a WebLogic domain use for administration traffic.

Administration Server

WebLogic Server: A WebLogic Server instance that provides a central point for managing a WebLogic domain. All other WebLogic Server instances in a domain are called Managed Servers.

Administration Tool

Business Intelligence: See Oracle BI Administration Tool.

ADS

JDeveloper/ADF: A server-side push framework that allows you to provide real-time data updates for ADF Faces components. You bind ADF Faces components to a data source, and ADS pushes the data updates to the browser client without requiring the browser client to explicitly request it.

agent

Business Intelligence: Enables you to automate your business processes. You can use agents to provide event-driven alerting, scheduled content publishing, and conditional event-driven action execution. Agents can dynamically detect information-based problems and opportunities, determine the appropriate individuals to notify, and deliver information to them through a wide range of devices (email, phones, and so on).

Agent case

Identity Management: A repository for information gathered in the process of examining suspicious sessions and transactions.

aggregate persistence

Business Intelligence: A feature that automates the creation and loading of aggregate tables and their corresponding Oracle Business Intelligence metadata mappings to enable aggregate navigation.

aggregate table

Business Intelligence: A table that stores precomputed results from measures that have been aggregated over a set of dimensional attributes. Each aggregate table column contains data at a given set of levels. For example, a monthly sales table might contain a precomputed sum of the revenue for each product in each store during each month. Using aggregate tables optimizes performance.

aggregation rule

Business Intelligence: In an Oracle BI repository, a rule applied to a logical column or physical cube column that specifies a particular aggregation function to be applied to the column data, such as SUM.In Presentation Services, users can see the rules that have been applied in the repository. Users can also change the default aggregation rules for measure columns.

alias table

Business Intelligence: A physical table that references a different physical table as its source. You can use alias tables to set up multiple tables, each with different keys, names, or joins, when a single physical table must serve in different roles. Because alias table names are included in physical SQL queries, you can also use alias tables to provide meaningful table names, making the SQL statements easier to read.

analysis

Business Intelligence: A query that a user creates on the Criteria tab in Presentation Services. An analysis can optionally contain one or more filters or selection steps to restrict the results. See also filter and selection step.

analysis criteria

Business Intelligence: Consists of the columns, filters, and selection steps that you specify for an analysis. See also analysis.

analysis prompt

Business Intelligence: A prompt that is added to an analysis. When the user selects a prompt value, that value then determines the content that displays in the analysis that contains the prompt, only. See also dashboard prompt and prompt.

Analytics

WebCenter: A WebCenter Portal tool that offers real-time usage and activity reporting for your portal. In WebCenter Portal, users can track and analyze WebCenter Portal traffic and usage.

anchor color

JDeveloper/ADF: A category of global selector alias in an ADF skin that defines base colors for the ADF skin.

annotation

Fusion Middleware Core: An annotation, in the Java computer programming language, is a form of syntactic metadata that can be added to Java source code. Classes, methods, variables, method parameters and packages may be annotated. Unlike Javadoc tags, Java annotations can be reflective in that they can be embedded in class files generated by the compiler and may be retained by the Java VM to be made retrievable at run-time.

Announcements

WebCenter Portal: A WebCenter Portal tool that offers a quick, convenient way to create and widely distribute messages instantly or at a specific time.

Answer Logic

Identity Management: A mechanism to intelligently detect the correct answers in the OAAM challenge response process. It checks if the answers provided by the user matches closely to any provided during registration.

Application

Identity Management: A high-level container for organizing policies (and the Policy Model objects used to create them) that define the requirements for accessing this particular secure resource. An Application may correspond to a single deployed software application, a set of deployed software applications, or components of a software application (such as an Enterprise JavaBeans).

Application Configurator

Identity Management: An administrative role with privileges to configure and manage Oracle Privileged Account Manager Console and servers.

application failover

Coherence Suite: When an application component becomes unavailable for any reason, a copy of the failed object finishes the job. In hardware or other failures, the session state is available to other cluster members that can resume the work of the failed member.

application module

JDeveloper/ADF: A transactional component that Oracle ADF clients use to work with application data defined by Oracle ADF Business Components. It defines an updatable data model and top-level procedures and functions (called service methods) related to a logical unit of work. This unit of work is related to an end-user task.

application module configuration file

JDeveloper/ADF: The general term for the bc4j.xcfg configuration file. Contains metadata about ADF application module names, the database connection used by the application module, and the runtime parameters that the data model project developer has configured for the application module. The configuration allows the ADF application to interact with deployed application modules.

application module data control

JDeveloper/ADF: XML configuration file that describes a service generated from Oracle ADF Business Components. At design time, JDeveloper uses the metadata to declaratively bind an operation or data collection to a UI component.

application module data model

JDeveloper/ADF: Exposes view object instances in the ADF Business Component Model project that users will interact with through the web pages of an ADF application.

application module instance

JDeveloper/ADF: An Oracle ADF Business Components application module definition that has been checked out at runtime from the ADF application module pool for use by a client.

application module nesting

JDeveloper/ADF: Enables services exposed by one Oracle ADF application module to be consumed by multiple application modules. The application module data model may define composite services by nesting desired application modules under a root application module.

application module pool

JDeveloper/ADF: Runtime logic provided by the Oracle ADF Business Components framework that allocates an available unreferenced application module instance to an ADF client. If the client has previously requested an application module, then the application module pool will identify and allocate the instance already used by the client.

Application Overview Checklist

JDeveloper/ADF: Part of the Application Overview, it steps users through the building of a Fusion web application, according to Oracle recommended best practices.

Application Role

Identity Management: Defines criteria for mapping users, groups, External Roles or other Application Roles to a particular Oracle Entitlements Server Application object. The Application Role can be granted to an external user, group, or role in an identity store, or another Application Role in the policy store.

application server-scoped Coherence cluster members

Coherence Suite: (For deployments on non-WebLogic Server application servers) With this configuration, all deployed applications in a container become part of one Coherence member. This configuration produces the smallest number of Coherence members in the cluster (one for each web container JVM) and, because the Coherence library is deployed in the container's class path, only one copy of the Coherence classes is loaded into the JVM.

application specialist

WebCenter Portal: A WebCenter Portal user who works in Portal Composer to develop site structure by planning, creating, and administering portals and their content. At the application level, an application specialist has the permissions granted to the Application Specialist role. In a portal that an application specialist creates, the application specialist can perform the actions available to the Portal Manager role.

application state management

JDeveloper/ADF: Runtime logic provided by Oracle ADF that supports multistep use cases in Fusion web applications. Oracle ADF application modules may passivate (store) their pending transaction state to an XML document, which is stored in the database.

application tier

Coherence Suite: Coherence client instances that are cluster members and are not responsible for cache storage.

assertion template

OWSM: An assertion template defines a policy assertion, which is the smallest unit of a policy that performs a specific action for the request and response operations. Assertion templates can be used to add assertions to web service policies, or to create new policies.

asynchronous web service

SOA Suite: Provides a response to an invocation that can take time to complete. The invoker of the request waits until the web service replies. Asynchronous messaging styles are useful for environments in which a service, such as a loan processor, can take a long time to process a client request.

atomic transaction

Web Services: See Web Services Atomic Transaction

attribute

Business Intelligence: The details of a dimension in an Oracle BI repository. Attributes usually appear as columns of a dimension table.

attribute column

Business Intelligence: In Presentation Services, a column that holds a flat list of values that are also known as members. No hierarchical relationship exists between these members, as is the case for members of a hierarchical column. Examples include ProductID or City. See also hierarchical column.

audit trail

SOA Suite: Displays execution details in Oracle Enterprise Manager about the business flow instance (for example, the activities in a BPEL process). You can scroll through the audit trail to check for errors and expand the payload links to view their contents at a given point in the flow.

Auditing provider

WebLogic Server: A WebLogic Security Framework provider that provides auditing services.

Authentication provider

WebLogic Server: WebLogic Security Framework provider that enables WebLogic Server to establish trust by validating a user.

Autolearning

Identity Management: A set of features in Oracle Adaptive Access Manager that dynamically profile behavior in real time. The behavior of users, devices, and locations is recorded and used to evaluate the risk of current behavior.

back up

Fusion Middleware Core: The process of creating exact duplicates of the files in your environment, so that, in the event of data loss or corruption, host failure, or media failure, you can use those copies to restore your environment. The two types of backup are offline backup and online backup. In offline backup, you must shut down the environment before backing up the files. In online backup, you do not shut down the environment before backing up the files.

backing bean scope

JDeveloper/ADF: ADF-defined scope in the page life cycle. An object in this scope is available from the time an HTTP request is sent until a response is sent back to the client.

bc4j.xcfg

JDeveloper/ADF: The ADF application module configuration file. The bc4j.xcfg file contains metadata about ADF application module names, the database connection used by the application module, and the runtime parameters that the data model project developer has configured for the application module. The configuration allows the ADF application to interact with deployed application modules.

BI Composer

Business Intelligence: A wizard that enables you to create, edit, or view analyses without the complexities of the Analysis editor.

BI domain

Business Intelligence: Contains configurable system components (the coreapplication) and Java components (the WebLogic server domain), and includes the web-based management tools and applications that use resources. A BI domain can be a set of middleware homes spread across one or more physical servers. See also BI instance.

BI instance

Business Intelligence: Refers to the system components (coreapplication) of a BI domain. See also BI domain.

BI object

Business Intelligence: A piece of business intelligence content that is created with Presentation Services and saved to the Oracle BI Presentation Catalog. Examples of BI objects include analyses, dashboards, dashboard pages, scorecards, and KPIs.

BI Search

Business Intelligence: A search tool that resides outside of Presentation Services and is available from the Home Page after the administrator adds a link to the BI Search URL. It provides a mechanism for searching for objects in the Oracle BI Presentation Catalog that is similar to a full-text search engine.

bind operation

Identity Management: An operation used to authenticate and specify the LDAP protocol version to an LDAP directory server. There are two basic types of bind operations: * A simple bind operation, which uses simple authentication involving a bind DN and password to authenticate to the server. * A SASL bind operation, which uses the Simple Authentication and Security Layer to authenticate the client, which can use a variety of types of credentials based on the selected SASL mechanism.

bind variable

JDeveloper/ADF: A placeholder variable in a SQL statement that must be replaced with a valid value before the statement can successfully execute.

binding component

SOA Suite: A component that establishes the connection between a SOA composite application and the external world. There are two types of binding components: Services: Provide the outside world with an entry point to the SOA composite application. References: Enable messages to be sent from the SOA composite application to external services in the outside world.

binding container

JDeveloper/ADF: A request-scoped map of a page's bindings based on the page's page definition file. In a JSF application, the binding container is accessible during each page request using the EL expression #{bindings}.

binding context

JDeveloper/ADF: A container object that holds a list of available data controls and data binding objects. The DataBindings.cpx file defines the binding context for the application.

bookmark link

Business Intelligence: Captures the path to a dashboard page and all aspects of the page state. See also prompted link.

bounded task flow

JDeveloper/ADF: A type of ADF task flow that has a single entry point and zero or more exit points. It contains its own set of private control flow rules, activities, and managed beans. A bounded task flow allows reuse, parameters, transaction management, and reentry. When dropped on a JSF page or page fragment, it is wrapped in an ADF Faces region component.

BPEL process

BPEL: A service component that integrates a series of business activities and services into an end-to-end business process flow.

bridge table

Business Intelligence: A table that enables you to resolve many-to-many relationships between two other tables.

briefing book

Business Intelligence: See Oracle BI Briefing Books.

bundle patch

Fusion Middleware Core: An iterative, cumulative patch that is issued between patch sets. Bundle patches usually include only fixes, but some products may include minor enhancements.

business event

SOA Suite: A message sent as the result of an occurrence or situation, such as a new order or completion of an order. You can raise business events when a situation of interest occurs. When an event is published, other applications can subscribe to it. Definitions for business events are published to the Event Delivery Network (EDN).

business flow instance

SOA Suite: Corresponds to an end-to-end business transaction. Business flows consist of a single SOA composite application or multiple SOA composite applications connected together to fulfill a specific business process.

business model

Business Intelligence: An object in the Oracle BI repository that contains the business model definitions and the mappings from logical to physical tables. Business models are always dimensional, unlike objects in the Physical layer, which reflect the organization of the data sources. Each business model contains logical tables, columns, and joins.

Business Model and Mapping layer

Business Intelligence: A layer of the Oracle BI repository that defines the business, or logical, model of the data and specifies the mapping between the business model and the Physical layer schemas. This layer can contain one or more business models.The Business Model and Mapping layer determines the analytic behavior that is seen by users, and defines the superset of objects available to users. It also hides the complexity of the source data models.

business owner

Business Intelligence: The person responsible for managing and improving the business value and performance of a KPI or scorecard object, such as an objective, cause & effect map, and so on.

business process execution language (BPEL)

SOA Suite: Provides enterprises with an industry standard for business process orchestration and execution. Using BPEL, you design a business process that integrates a series of discrete services into an end-to-end process flow. This integration reduces process cost and complexity.

cache configuration file (coherence-cache-config.xml)

Coherence Suite: A file that specifies the various types of caches that can be used within a cluster. This file is also referred to as the cache configuration deployment descriptor.

cache store

Coherence Suite: An application-specific adapter used to connect a cache to an underlying data source. The cache store implementation accesses the data source by using a data access mechanism (for example, TopLink, JPA, application-specific JDBC calls). The cache store understands how to build a Java object using data retrieved from the data source, map and write an object to the data source, and erase an object from the data source.

CacheFactory

Coherence Suite: A Coherence class that is typically used to get and release an instance of a NamedCache object. This class includes methods to obtain a cluster object running Coherence services, shut down all clustered services, and to return an instance of a cache.

catalog

Business Intelligence: See Oracle BI Presentation Catalog.

cause and effect map

Business Intelligence: A component of a scorecard that lets you illustrate the cause and effect relationships of an objective or KPI. See also Oracle Scorecard and Strategy Management.

chronological key

Business Intelligence: A column in a time dimension that identifies the chronological order of the members within a dimension level. The key must be unique at its level.

client-side at-rule

JDeveloper/ADF: An at-rule that the ADF skinning framework passes directly to the user agent to evaluate. The user agent applies the style properties within the at-rule if the condition that the at-rule specifies is satisfied. Examples of this category of at-rule include @media, @keyframes, and @page.

cluster service

Coherence Suite: The cluster service is responsible for the detection of other cluster members, for detecting the failure of a cluster member, and for registering the availability of other services in the cluster. This service is automatically started by a Coherence cluster member; each cluster member always has exactly one service of this type running.

Coherence cache client

Coherence Suite: An application that joins a cluster to access, process, and update cached data. The application is a cluster member that is not responsible for data storage. Types of cache clients include data clients, real-time clients configured as an Extend/TCP client, and real-time clients configured as a compute client.

Coherence cache server

Coherence Suite: A Coherence cluster member that is responsible for storing and backing up cached data.

Coherence cluster

Coherence Suite: A set of Coherence instances (one instance per JVM, with one or more JVMs on each computer). The JVMs automatically join together to form the cluster.

Coherence cluster member

Coherence Suite: A Coherence JVM process that is part of a Coherence cluster. A Coherence cluster member is also referred to as a Coherence cluster node.

Coherence cluster node

Coherence Suite: See Coherence cluster member. Although Coherence cluster node may appear in the Coherence documentation, the preferred term is Coherence cluster member.

Coherence data grid

Coherence Suite: A system composed of multiple servers that work together to manage information and related operations (such as computations) in a distributed environment.

Coherence GoldenGate HotCache

Coherence Suite: A Coherence feature that allows third-party changes to the database to be propagated to objects in the Coherence cache. Coherence GoldenGate HotCache can be added to any Coherence application. Standard JPA is used to capture the mappings from database data to Java objects. The configuration can be captured in XML exclusively or in XML with annotations.

Coherence Incubator

Coherence Suite: A java.net project that contains example implementations (source code, binaries, and documentation) of advanced functionality built on top of Coherence. These examples are intended to: Illustrate how to implement bleeding-edge functionality using the publicly available Coherence releases, preferably the latest versions. Directly address the challenges and investment required when developers attempt to use or construct implementations of standard architectural patterns with Coherence for their applications. Produce a standard library of common enterprise and application pattern/framework implementations, documentation, and training material, to dramatically reduce or eliminate the effort required to adopt and integrate Coherence into nontrivial applications (that is, those that require more than "read caching").

Coherence quorum

Coherence Suite: The minimum number of service members that are required in a cluster before a service action is allowed or disallowed. Quorums are beneficial because they automatically provide assurances that a cluster behaves in an expected way when member thresholds are reached.

Coherence REST

Coherence Suite: Coherence REST provides easy access to Coherence caches and cache entries over the HTTP protocol. It is similar to Coherence*Extend, as it allows remote clients to access data stored in Coherence without being members of the cluster themselves. However, unlike Coherence*Extend, which is a proprietary protocol, Coherence REST uses HTTP as the underlying protocol and can marshal data in both JSON and XML representation formats.

Coherence Service Guardian

Coherence Suite: A mechanism that detects and attempts to resolve deadlocks in Coherence threads.

Coherence Well Known Addresses (WKA)

Coherence Suite: A feature that allows cluster members to discover and join a cluster using unicast instead of multicast. WKA is most often used when multicast networking is undesirable or unavailable in an environment or when an environment is not properly configured to support multicast. All cluster multicast communication is disabled if WKA is enabled.

Coherence*Extend

Coherence Suite: A Coherence feature that allows applications to use a Coherence cluster without becoming cluster members. Coherence*Extend consists of an extend client (Java, C++, or .NET) that connects to a cluster proxy service through a TCP-based protocol.

Coherence*Web

Coherence Suite: An HTTP session management module dedicated to managing session state in clustered environments. It brings Coherence data grid scalability, availability, reliability, and performance to in-memory session management and storage.

CohQL

Coherence Suite: A lightweight syntax (in the tradition of SQL) that is used to perform cache operations on a Coherence cluster. The language can be used either programmatically or from the command line.

collection model

JDeveloper/ADF: An ADF object that extends the JSF DataModel class and adds on support for row keys and sorting. In the DataModel class, rows are identified entirely by index. This can cause problems when the underlying data changes from one request to the next. For example, a user request to delete one row may delete a different row when another user adds a row. To work around this, the CollectionModel is based on row keys instead of indexes.

collection-based components

JDeveloper/ADF: ADF Faces UI components that iterate through and display collections of structured data. Instead of containing a child component for each record to be displayed, and then binding these components to the individual records, these components are bound to a complete collection. They then repeatedly render one component (for example, an outputText component), by stamping the value for each record. Examples include table, tree, and carousel.

column

Business Intelligence: In an Oracle BI repository, columns can be physical columns, logical columns, or presentation columns. In Presentation Services, indicates the pieces of data that an analysis returns. Together with filters and selection steps, columns determine what analyses contain. Columns also have names that indicate the types of information that they contain, such as Account and Contact. See also analysis, attribute column, hierarchical column, and measure column.

column filter

Business Intelligence: See filter.

column prompt

Business Intelligence: A type of filter that enables you to build specific value prompts on a data column to either exist alone on the dashboard or analysis or to expand or refine existing dashboard and analysis filters. See also prompt.

compact domain

Fusion Middleware Core: A WebLogic domain for Oracle Fusion Middleware products in which all or a subset of the application or service groups defined in the product templates are targeted to the Administration Server. Compact domains do not contain Managed Servers or clusters for the Oracle Fusion Middleware products. Also known as a single-instance domain.

Compatibility realm

WebLogic Server: Security realm that is the default (active) security realm if you are using Compatibility security. The Compatibility realm adapts your existing WebLogic Server 6.x Authentication and Authorization providers so that you can use them in WebLogic Server 7.x or later. The only security realm available in Compatibility security is the Compatibility realm.

Compatibility security

WebLogic Server: The capability to run security configurations from WebLogic Server 6.x in later releases of WebLogic Server. By using Compatibility security in WebLogic Server 7.x or later, you configure 6.x security realms; define users, groups, and ACLs; manage protection of user accounts; and install custom auditing providers. The only security realm available in Compatibility security is the Compatibility realm. The Realm Adapter providers in the Compatibility realm allow backward compatibility to the authentication and authorization services in 6.x security realms.

compensation

SOA Suite: Occurs when a BPEL process cannot complete a series of operations after some have completed, and the BPEL process service component must backtrack and undo the previously completed transactions.

complex join

Business Intelligence: A join in the Physical layer of an Oracle BI repository that uses an expression other than equals.

composite sensor

SOA Suite: Implements trackable fields on messages in a SOA composite application. You define sensors on binding components and on service components that have subscribed to business events.

condition

Business Intelligence: Objects that return a single Boolean value based on the evaluation of an analysis or of a key performance indicator (KPI). You use conditions to determine whether agents deliver their content and execute their actions, whether actions links are displayed in dashboard pages, or whether sections and their content are displayed in dashboard pages. See also action, action link, agent and key performance indicator (KPI).

conditional branching

SOA Suite: Introduces decision points to control the flow of execution of a BPEL process service component. You can use switch, if, while, and repeatUntil activities to define conditional branching.

configuration override

OWSM: Ability to override an OWSM policy configuration property on a per-attachment basis.

connection filter

WebLogic Server: A programmable filter that WebLogic Server uses to determine whether the server should allow incoming connections from a network client. In addition to security policies that protect WebLogic resources based on user characteristics, you can add another layer of security by filtering based on network connections.

connection pool

Business Intelligence: An object in the Physical layer of an Oracle BI repository that contains the connection information for a data source. See also Physical layer.

content designer

Business Intelligence: The user who creates business intelligence objects such as analyses, dashboards, and scorecards.

content movement

Fusion Middleware Core: The process of moving all or part of your environment. Content movement includes moving your environment from a test environment to a production environment.

contextual event action

Business Intelligence: A predelivered action that uses the Action Framework to pass content from the business intelligence object to another region on an ADF page. See also action, Action Framework, and action link.

continuous query

Coherence Suite: A feature that combines a query result with a continuous stream of related events to maintain an up-to-date query result in real time. This capability is called continuous query, because it has the same effect as if the desired query had zero latency and the query were being executed several times every millisecond.

control binding

JDeveloper/ADF: A set of value bindings and action bindings that appears in a page definition file. The control bindings are distinct from the iterator bindings that appear in the executables section of the page definition file.

control flow

JDeveloper/ADF: An ADF Controller activity that enables navigation between other activities in an ADF task flow. The control flow links one activity to another in a task flow.

control hint

JDeveloper/ADF: ADF Business Components metadata that defines label text, tooltip, and format mask hints for entity object and view object attributes. Control hints that you define on the business service layer can be used by UI components in ADF clients.

correlation sets

SOA Suite: Correlate asynchronous messages based on message body contents. You can use correlation sets to identify asynchronous messages to ensure that asynchronous callbacks locate the appropriate client.

credential delegation

OWSM: A mechanism that provides services with the ability to access another service or server in order to complete a client request. In order to establish such a connection with the Kerberos protocol, for example, Kerberos requires the first service to be authenticated to the second service or server using the client's user account and authority level.

Credential Mapping provider

WebLogic Server: A WebLogic Security Framework provider that is used to provide credential mapping services and bring new types of credentials into the WebLogic Server environment.

criteria

Business Intelligence: See analysis criteria.

Critical Patch Update (CPU)

Fusion Middleware Core: The name of the program that delivers security patch updates (SPUs). The program is Oracle's program for quarterly release of security fixes. Patches released as part of this program may be patch set updates, security patch updates, and bundle patches. Regardless of the patch type, the patches are cumulative.

cross-component wiring

Fusion Middleware Core: A method for wiring Fusion Middleware components. It automates the wiring process, and provides the ability to diagnose wirings after they are established.

Cross-Domain Single Sign-On

WebLogic Server: WebLogic Server security feature that allows users to authenticate once but access multiple applications, even if these applications reside in different DNS domains. You can use this feature to construct a network of affiliates or partners that participate in a Single Sign-On domain.

cube

Business Intelligence: An OLAP (online analytical processing) data structure that lets data be analyzed more quickly and with greater flexibility than structures in relational databases. Cubes are made up of measures and organized by dimensions. Cubes in multidimensional data sources roughly correspond to star schemas in relational database models.

currency prompt

Business Intelligence: A prompt that enables the user to change the currency type that displays in the currency columns on an analysis or dashboard. See also prompt.

custom security provider

WebLogic Server: A security provider (written by third-party security vendors or security developers) that can be integrated into the WebLogic Security Service. Custom security providers are implementations of the Security Service Provider Interfaces (SSPIs) and are not supplied with the Oracle WebLogic Server product.

custom view

Business Intelligence: A component of a scorecard that lets you show a customized view of your business and strategy data. See also Oracle Scorecard and Strategy Management.

dashboard

Business Intelligence: An object that provides personalized views of corporate and external information. A dashboard consists of one or more pages. Pages can display anything that you can access or open with a web browser, such as results of analyses, images, alerts from agents, and so on.

dashboard prompt

Business Intelligence: A prompt that is added to the dashboard. When the user selects a prompt value, that value then determines the content that displays in all analyses that are included on the dashboard. See also analysis prompt and prompt.

Dashboard URL

Business Intelligence: Used for incorporating or referencing the content of a specific dashboard in external portals or applications. It has several forms and optional arguments that you can use to control its behavior.

data client

Coherence Suite: Data clients are Extend clients that can access (put, get, query) data in the cluster and also make invocation service requests using standard Coherence APIs.

data control

JDeveloper/ADF: XML configuration files that describe a service. At design time, JDeveloper uses the metadata to declaratively bind an operation or data collection to a UI component.

data control definition file

JDeveloper/ADF: A file that contains the definitions for a project's data controls. Typically, it is named DataControls.dcx.

data control structure file

JDeveloper/ADF: An XML file that provides metadata for one of the objects that is encompassed by a data control.

Data Controls panel

JDeveloper/ADF: A panel in JDeveloper that lists all the data controls that have been created for the application's business services and exposes all the collections (row sets of data objects), methods, and built-in operations that are available for binding to UI components.

data source name (DSN)

Business Intelligence: A data structure that contains the information about a specific database, typically used by an ODBC driver to connect to the database. The DSN contains information such as the name, directory, and driver of the database. Connection pool objects in the Physical layer of the Oracle BI repository contain DSN information for individual data sources.

data tier

Coherence Suite: Cache server instances dedicated to caching application data and storing a replicated session state.

database delegator

WebLogic Server: An intermediary class that mediates initialization calls between a security provider and the security provider's database.

database hint

Business Intelligence: Instructions placed within a SQL statement that tell the database query optimizer the most efficient way to execute the statement. Hints override the optimizer's execution plan, so you can use hints to improve performance by forcing the optimizer to use a more efficient plan. Hints are supported only for Oracle Database data sources.

Database Management System Authentication provider

WebLogic Server: A WebLogic Security Framework provider that accesses user, password, group, and group membership information stored in databases for authentication purposes. Optionally, WebLogic Server can be used to manage the user, password, group, and group membership information.

declarative SQL mode

JDeveloper/ADF: The preferred way of creating view objects in the Oracle ADF Business Components project. At design time, Oracle ADF developers can create entity-based view objects that contain no SQL statements. This mode provides an alternative to creating view objects that specify a SQL statement.

default language

WebCenter: At the application level, a display language specified by the system administrator that is used when users log in to WebCenter Portal. The administrator sets the application-level default language on the General tab of the Administration page. Individual users can set their own user-level default language on the General tab of the Preferences dialog. At a user preference, a user-specified display language that is rendered when the user logs in to the WebCenter Portal. This language selection lasts until the user specifies a different default language. It can be overridden by a session language, but returns as the default when the session cookie is purged or expires. This value is set on the General tab of the Preferences dialog.

default realm

WebLogic Server: The active security realm. In WebLogic Server you can configure multiple security realms in a WebLogic domain; however, only one can be the default (active) security realm.

dehydration store

BPEL: A database that automatically maintains long-running asynchronous processes and their current state information while they wait for asynchronous callbacks. Storing the process in a database preserves the process and prevents any loss of state or reliability if a system shuts down or a network problem occurs.

deployment descriptor properties

SOA Suite: BPEL process properties used at runtime by Oracle WebLogic Server, Oracle Enterprise Manager, or both. There are two types: Configuration Partner link binding

derivative color

JDeveloper/ADF: A category of global selector alias that defines color properties for use in an ADF skin. These global selector aliases derive the hue value for their color properties from anchor colors.

device fingerprinting

Identity Management: A process by which OAAM captures information about the device being used in an access request or transaction. A device is a computer, laptop computer, PDA, cell phone, kiosk, or other web-enabled device. Device fingerprinting data is gathered from multiple sources including secure cookies, flash shared objects, user agent strings, custom agents, mobile applications, browser header data, and other data.

diagnostic context

WebLogic Server: Contextual information added by the WebLogic Diagnostics Framework (WLDF) to all requests when they enter the WebLogic Server system. You can use this information to reconstruct transactional events and reconstruct a thread of execution from request to response.

Diagnostic Framework

Fusion Middleware Core: Diagnostic Framework aids in detecting, diagnosing, and resolving problems. It targets critical errors such as those caused by code bugs, metadata corruption, customer data corruption, deadlocked threads, and inconsistent state.

diagnostic patch

Fusion Middleware Core: An interim patch created specifically to diagnose a problem and not to fix a bug.

dimension

Business Intelligence: A hierarchical organization of logical columns (attributes). One or more logical dimension tables might be associated with at most one dimension. A dimension might contain one or more (unnamed) hierarchies. There are two types of logical dimensions: dimensions with level-based hierarchies (structure hierarchies), and dimensions with parent-child hierarchies (value hierarchies). A particular type of level-based dimension, called a time dimension, provides special functionality for modeling time series data. See also hierarchy.

dimension table

Business Intelligence: A logical table that contains columns used by a particular dimension. A dimension table cannot be a fact table. See also fact table.

direct binding

SOA Suite: Enables Java clients to directly invoke composite services, bypassing the intermediate conversion to XML required with web service binding.

direct policy attachment

OWSM: A mechanism for associating an OWSM policy with a single policy subject.

directory information tree (DIT)

Identity Management: The hierarchical structure of data in a directory server. A DIT contains one or more naming context entries, which are the base entries for the server, and every other entry is descended from one of those naming context entries. A naming context entry does not have a parent entry.

disaster recovery

Fusion Middleware Core: The ability to safeguard against natural or unplanned outages at a production site by having a recovery strategy for moving applications and data to a geographically separate standby site.

disconnected property

JDeveloper/ADF: Property on an ADF Faces UI component that can be set on the client, but is not propagated back to the server. These properties have a life cycle on the client that is independent of the life cycle on the server.

distinguished name (DN)

Identity Management: A string that uniquely identifies an entry in the directory server; for example, uid=john.doe,ou=People,dc=example,dc=com. A distinguished name (DN) consists of zero or more relative distinguished name (RDN) components that identify the entry's location in the directory information tree (DIT). An entry's distinguished name is analogous to an absolute path in a file system because it specifies both the name and hierarchical location.

distributed (or partitioned) cache

Coherence Suite: A collection of data that is distributed (or partitioned) across any number of cluster members such that exactly one member in the cluster is responsible for each piece of data in the cache, and the responsibility is distributed (or load-balanced) among the cluster members.

DistributedCache service

Coherence Suite: A service that allows cluster members to distribute (partition) data across the cluster so that each piece of data in the cache is managed (held) by only one cluster member.

distribution

Fusion Middleware Core: A downloadable archive with an installer that installs a predefined set of Oracle Fusion Middleware products and feature sets; customers can obtain distributions through the Oracle Software Delivery Cloud, the Oracle Technology Network (OTN), or My Oracle Support.

Domain Template Builder

Fusion Middleware Core: A tool for creating a template of a WebLogic domain that has been customized and that you want to propagate throughout a target environment.

domain value maps

SOA Suite: A set of value mappings that enables you to associate values from one application with values from another. For example, one value can represent a city with a long name (Boston), while another value can represent a city with a short name (BO). In such cases, you can directly map the values by using domain value maps.

driving table

Business Intelligence: A mechanism used to optimize how the Oracle BI Server processes multi-database joins when one table is very small (the driving table) and the other table is very large.

DSN

Business Intelligence: See data source name (DSN).

durable process

SOA Suite: A type of BPEL process that incurs one or more dehydration points in the database during execution. Dehydration is triggered by the following activities. Receive activity OnMessage branch in a pick activity OnAlarm branch in a pick activity Wait activity Instances of durable processes can be saved in-flight (whether they complete normally or abnormally). These processes are typically long-living and initiated through a one-way invocation. Because of out-of-memory and system downtime issues, durable processes cannot be memory-optimized. The asynchronous process you design in Oracle JDeveloper is an example of both a transient and durable process.

dynamic group

Identity Management: A group in the directory server that defines its membership by using a set of search criteria in the form of an LDAP URL, as opposed to a static group in which the distinguished name of the members are explicitly specified.

dynamic server

WebLogic Server: A server instance that is generated by WebLogic Server when it creates a dynamic cluster. Configuration is based on a shared server template.

EAR-Scoped Coherence cluster members

Coherence Suite: For deployments on non-WebLogic Server application servers: with this configuration, all deployed applications within each EAR file become part of one Coherence member. This configuration produces one Coherence member for each deployed EAR file. Because the Coherence library is deployed in the application's classpath, only one copy of the Coherence classes is loaded for each EAR file.

ECID

Fusion Middleware Core: See Execution Context ID.

EclipseLink

Toplink: An open-source persistence framework from the Eclipse Foundation. EclipseLink includes development tools and runtime capabilities for providing transformation, mapping, data binding, and persistence operations in Java SE and Java EE environments. EclipseLink provides support for a number of persistence standards, plus extensions to those standards. The standards include the Java Persistence API (JPA), Java API for XML Binding (JAXB), Java Connector Architecture (JCA), and Service Data Objects (SDO) The EclipseLink project is led by Oracle, and EclipseLink provides the core functionality in Oracle TopLink.

EclipseLink DBWS

Toplink: A development tool and a runtime for providing Java EE-compliant, client-neutral access to relational database artifacts through a web service. The development tool, DBWS Builder, is a command-line utility that generates the necessary deployment artifacts. (DBWS Builder is integrated into Eclipse Dali Java Persistence toolset and into Oracle JDeveloper.) The runtime provider component takes a service descriptor (along with related deployment artifacts) and realizes it as a JAX-WS 2.0 Web service. The runtime uses EclipseLink to bridge between the database and the XML SOAP messages used by web service clients.

EclipseLink EIS

Toplink: A facility for enabling the use of data stores through Java Connector Architecture (JCA) resource adapters. Using XML metadata, the interactions and their exchanged data are configured and mapped onto a domain model. The interactions data can be mapped from either the Common Client interface (CCI) or by using XML schemas. This use is intended for nonrelational data stores where no JDBC or SQL access is provided.

EclipseLink JAXB

Toplink: The EclipseLink implementation of the Java Architecture for XML Binding (JAXB) specification. It includes EclipseLink extensions to the standard, such as XPath-based mappings and a mapping file. EclipseLink JAXB is the JAXB implementation used by Oracle TopLink.

EclipseLink JPA

Toplink: The EclipseLink implementation of the Java Persistence API (JPA) specification, plus EclipseLink extensions to the standard. EclipseLink JPA is the Reference Implementation of the JPA 2.0 and JPA 2.1 specifications, and the JPA implementation used by Oracle TopLink.

EclipseLink Mapping Workbench

Toplink: A graphical tool (graphical user interface) for configuring descriptors and for mapping between an object model and a data model in an EclipseLink project, using native TopLink. (The Workbench cannot be used for mapping the Java Persistence API (JPA).) EclipseLink Mapping Workbench is a separate component available in EclipseLink distributions. EclipseLink Mapping Workbench is based on Oracle TopLink Mapping Workbench, which is no longer available. However, native TopLink mapping projects are still supported in Oracle JDeveloper.

EclipseLink MOXy

Toplink: EclipseLink Java Architecture for XML Binding (JAXB), and support for JavaScript Object Notation (JSON) as an alternative to XML in JAXB-type operations. EclipseLink supports all object/XML options when reading and writing JSON. MOXy also includes support for the native EclipseLink object/XML API.

EclipseLink Service Data Objects (SDO)

Toplink: The reference implementation of the Service Data Objects (SDO) 2.1.1 specification, including a programming architecture and API for heterogeneous data access. EclipseLink SDO is implemented as a thin layer on EclipseLink's object/XML layer, which is also the base for EclipseLink JAXB. EclipseLink SDO can be used alone or as a means to expose POJOs as Data Objects, so components like EclipseLink JPA and EclipseLink JAXB can be used.

Elastic Data

Coherence Suite: Elastic Data is a Coherence feature which is used to seamlessly store data across memory and disk-based devices. This feature is especially tuned to take advantage of fast disk-based devices such as Solid State Disks (SSD) and enables near memory speed while storing and reading data from SSDs.

embedded LDAP server

WebLogic Server: A server included with WebLogic Server that is the default store for user, group, security role, security policy, and credential information.

enterprise deployment

Fusion Middleware Core: An Oracle best practices blueprint based on proven Oracle high availability and security technologies and recommendations for a particular Oracle product, such as Oracle Fusion Middleware. The best practices described in these blueprints span all Oracle products across the entire technology stack, such as Oracle Database, Oracle Fusion Middleware, and Oracle Enterprise Manager Fusion Middleware Control. An enterprise deployment considers various business service-level agreements (SLA) to make high availability best practices as widely applicable as possible. It provides highly resilient, lower cost infrastructure. It ensures that the high availability architecture is optimally configured to perform and scale to business needs. It enables control over the length of time to recover from an outage and the amount of acceptable data loss from a natural disaster.

entity association

JDeveloper/ADF: An Oracle ADF Business Components object that defines the relation between two ADF entity objects based on the attributes on each side of the associated entity objects. Associations are useful to access the destination entities from a source entity. At runtime, the entity object uses the association to automate working with related sets of entities.

entity object

JDeveloper/ADF: An ADF Business Components object that represents a row in a database table and simplifies modifying its data by handling all data manipulation language (DML) operations for you. It can encapsulate business logic to ensure that your business rules are consistently enforced. You associate an entity object with others to reflect relationships in the underlying database schema to create a layer of business domain objects to reuse in multiple applications.

entity variable

SOA Suite: Used with an Oracle Application Development Framework (ADF) Business Component data provider service using service data object (SDO)-based data. The entity variable enables you to specify BPEL data operations to be performed by an underlying data provider service. The data provider service performs the data operations in a data store behind the scenes and without use of other data store-related features provided by Oracle BPEL Process Manager (for example, the database adapter). This action enhances Oracle BPEL Process Manager runtime performance and incorporates native features of the underlying data provider service during compilation and runtime.

entry aggregator

Coherence Suite: An entry aggregator performs operations against a subset of entries to obtain a single result. Aggregations are performed in a map-reduce manner with local results on each cache server sent to the originating client, which then performs the final reduce step.

entry processor

Coherence Suite: An entry processor can update cache entries in multiple caches within a single process or processAll operation. The caches must be managed by the same service, and the entries must be located in the same partition. An entry processor facilitates a highly efficient, lockless, and highly scalable compute environment where compute is moved to the data rather than moving data to a client application.

Essbase

Business Intelligence: A multidimensional database management system available from Oracle that provides a multidimensional database platform upon which to build business intelligence applications. Also referred to as Oracle's Hyperion Essbase.

event delivery network (EDN)

SOA Suite: Stores the published business events. The EDN runs within every SOA instance. Raised events are delivered by EDN to the subscribing service components.

event interceptor

Coherence Suite: An event interceptor explicitly defines which events to receive and what action, if any, to take. Any number of event interceptors can be created and registered for a specific cache or for all caches managed by a specific partitioned service. Multiple interceptors that are registered for the same event type are automatically linked together and executed in the context of a single event.

event polling table

Business Intelligence: Event polling tables (also called event tables) provide information to the Oracle BI Server about which physical tables have been updated. They are used to keep the query cache up-to-date. The Oracle BI Server cache system polls the event table, extracts the physical table information from the rows, and purges stale cache entries that reference those physical tables.

event root component

JDeveloper/ADF: An ADF Faces UI component that determines boundaries on the page, and so allows the lifecycle to run just on components within that boundary. Certain components are inherently event root components, such as the popup. When an event happens within a popup, only the popup and its children are rerendered, and not the whole page. Additionally, certain events indicate event root components. For example, the disclosure event sent when expanding a showDetail component indicates that the showDetail component is an event root.

events

WebCenter: Provides calendars for scheduling meetings, appointments, and so on. WebCenter Portal provides calendars to record events relevant to the specific portal. You can also integrate events with Microsoft Exchange Server to allow individual users to access their personal calendars in the Home portal.

executable binding

JDeveloper/ADF: One of a category of ADF bindings that includes iterator bindings, which simplify the building of user interfaces that allow scrolling and paging through collections of data and drilling down from summary to detail information, bindings that allow searching and nesting a series of pages within another page, and bindings that cause operations to occur immediately.

Execution Context ID

Fusion Middleware Core: Execution Context ID (ECID) is a globally unique identifier associated with the execution of a particular request. It can be used to correlate events in different components of Fusion Middleware or in different log files as being part of the same request execution flow.

Extend client

Coherence Suite: Runs outside the cluster and communicates with an extend proxy service running in the cluster hosted by one or more storage-disabled cache servers. An Extend client retrieves a Coherence clustered service using a cache factory. After a service is obtained, a client uses the service in the same way as if it were part of the Coherence cluster. Operations sent to a remote cluster member is transparent to the client application.

Extend client tier

Coherence Suite: One or more computers running Coherence*Extend clients.

fact table

Business Intelligence: In an Oracle BI repository, a logical table in the Business Model and Mapping layer that contains measures and has complex join relationships with dimension tables. See also dimension table.

Fast Infoset

Web Services: Compressed binary encoding format that provides a more efficient serialization than the text-based XML format. Fast Infoset optimizes both document size and processing performance.The Fast Infoset specification, ITU-T Rec. X.891 and ISO/IEC 24824-1 (Fast Infoset) is defined by both the ITU-T and ISO standards bodies.

fault policy bindings file

SOA Suite: Associates the policies defined in the fault policy file.

fault policy file

SOA Suite: Defines fault conditions and their corresponding fault recovery actions. Each fault condition specifies a particular fault or group of faults, which it attempts to handle, and the corresponding action for it. A set of actions is identified by an ID in the fault policy file.

feature set

Fusion Middleware Core: A logical grouping of Oracle Fusion Middleware features that can be used as a building block for distributions.

filter

Business Intelligence: Criteria that are applied to attribute and measure columns to limit the results that are displayed when an analysis is run. For measure columns, filters are applied before the query is aggregated and affect the query and thus the resulting values. See also prompt and selection step.

focus node

Business Intelligence: The center circle of a strategy contribution wheel. The focus node represents the starting objective of the diagram. See also strategy contribution wheel and focus trail.

focus trail

Business Intelligence: A series of chained circles that represent the node in the center of the strategy contribution wheel and any of its ancestors that are included in the diagram. Each circle displays the status color of its corresponding node. See also strategy contribution wheel and focus node.

foreign key

Business Intelligence: A column or a set of columns in one table that references the primary key columns in another table.

fragmentation content

Business Intelligence: The portion, or fragment, of the set of data specified in a logical table source when the logical table source does not contain the entire set of data at a given level. Fragmentation content is defined by the logical columns that are entered in the Fragmentation content box in the Content tab of the Logical Table Source dialog.

Fusion Middleware Configuration Wizard

Fusion Middleware Core: A tool that creates the appropriate directory structure for a WebLogic domain, a domain configuration file (config.xml), and scripts you can use to start the servers in the domain.

Fusion Middleware Control

Fusion Middleware Core: A web browser-based, graphical user interface that you can use to monitor and administer your Oracle Fusion Middleware environment.

Fusion web application

JDeveloper/ADF: An application that uses the entire Oracle ADF web stack: ADF Business Components, ADF Model, ADF Controller, and ADF Faces.

GAR file

Coherence Suite: grid archive file. The name of the application module supported by managed Coherence servers. The GAR file contains the artifacts of a Coherence application and includes a deployment descriptor. A GAR file is deployed and undeployed in the same way as standard Java EE modules and the application lifecycle is decoupled from the container.

global header

Business Intelligence: An object in the user interface for Oracle BI Presentation Services that contains links and options that enable the user to quickly begin a task or locate a specific object within the Oracle BI Presentation Catalog. The global header always displays in the Presentation Services user interface, thus enabling users to quickly access links and search the catalog without having to navigate to the Home Page or Catalog page.

global policy attachment

OWSM: A mechanism for associating a policy with a range of policy subjects of the same type, regardless of deployment state. Policies are attached globally using policy sets, which can contain multiple policy references.

Go URL

Business Intelligence: Used to incorporate specific business intelligence results into external portals or applications. The Go URL is used when you add a result to your favorites or add a link to a request to a dashboard or external web site. It has several forms and optional arguments that you can use to control its behavior.

GridLink data source

WebLogic Server: A means to connect WebLogic Server to an Oracle Database service, which may include multiple Oracle RAC clusters.

hierarchical column

Business Intelligence: In Presentation Services, a column that holds data values that are organized using both named levels and parent-child relationships. This column is displayed using a tree-like structure. Individual members are shown in an outline manner, with lower-level members rolling into higher-level members. For example, a specific day belongs to a particular month, which in turn is within a particular year. Examples include Time or Geography. See also attribute column.

hierarchy

Business Intelligence: In an Oracle BI repository, a system of levels in a logical dimension that are related to each other by one-to-many relationships. All hierarchies must have a common leaf level and a common root (all) level. Hierarchies are not modeled as separate objects in the metadata. Instead, they are an implicit part of dimension objects. See also dimension, logical level, and presentation hierarchy.

hierarchy level

Business Intelligence: In Presentation Services, an object within a hierarchical column that either rolls up or is rolled up from other levels. Corresponds to a presentation level in an Oracle BI repository. See also presentation level.

high availability

Fusion Middleware Core: An architecture that ensures that users can access a system without loss of service. Deploying a high availability system minimizes the time when the system is down (unavailable) and maximizes the time when it is running (available).

home page

Business Intelligence: Provides an intuitive, task-based entry way into the functionality of Presentation Services. The Home page is divided into sections that enable you to quickly begin specific tasks, locate an object, or access technical documentation.

host name verifier

WebLogic Server: A class that ensures the host name in the URL to which a client connects matches the host name in the digital certificate that the server sends back as part of the SSL connection.

HTTP Analyzer

JDeveloper/ADF: Allows users to examine the content of HTTP request/response package pairs from within JDeveloper.

idempotent activity

SOA Suite: An activity that can be safely retried. Idempotent activities are applicable to both durable and transient processes. You can manage idempotence at the operation level of a partner link. You define applicable operations as idempotent, which enables these operations to be called multiple times.

Identity Assertion provider

WebLogic Server: WebLogic Security Framework provider that performs perimeter authentication, which is a special type of authentication using tokens. Identity Assertion providers also allow WebLogic Server to establish trust by validating a user. Thus, the function of an Identity Assertion provider is to validate and map a token to a user name.

image prompt

Business Intelligence: A prompt that provides an image with different areas mapped to specific values. The user clicks an image area to select the prompt value that populates the analysis or dashboard. See also prompt.

inbound transaction

SOA Suite: A transaction initiated by an inbound adapter. For example, a transaction entering the SOA system from a JMS system.

initialization block

Business Intelligence: Used to initialize dynamic repository variables, system session variables, and nonsystem session variables. An initialization block contains the SQL statements that are executed to initialize or refresh the variables that are associated with that block.

initiative

Business Intelligence: Used in a scorecard, an initiative is a time-specific task or project that is necessary to achieve objectives. As such, you can use initiatives that support objectives as milestones as they reflect progress toward strategy targets. See also objective and Oracle Scorecard and Strategy Management.

inner graph

Business Intelligence: A nested graph, inside the grid of a trellis graph. Each inner graph has its own dimensionality as specified in the Visualization area of the Layout pane. See also trellis and outer edge.

install

Fusion Middleware Core: The process of populating your system with the Oracle Fusion Middleware software files. These software files are usually contained in a ZIP, JAR, or TAR archive that must be downloaded onto your system. After the contents of the archive file are extracted, an installer program is run to verify your system environment, then create the proper directory structure and place the Oracle Fusion Middleware software files in their proper locations. If needed, the installer also runs scripts to set environment variables and permissions. Installing also includes configuring the system. When the process is complete, Oracle Fusion Middleware components are deployed and ready to use.

interim patch

Fusion Middleware Core: A patch that contains one or more fixes made available to customers who cannot wait until the next patch set or new product release to receive the fix.

invocation service

Coherence Suite: A service that provides clustered invocation and supports grid computing architectures. This service allows applications to invoke agents on any member in the cluster, or any group of members, or across the entire cluster. The agent invocations can be request/response, fire and forget, or an asynchronous user-definable model.

iterator binding

JDeveloper/ADF: A binding to an iterator that iterates over view object collections. There is one iterator binding for each collection used on the page. All of the value bindings on the page must refer to an iterator binding in order for the component values to be populated with data at runtime.

JAAS control flag

WebLogic Server: The JAAS control flag that determines how the login sequence uses the Authentication providers when a security realm has multiple Authentication providers.

Java component

Fusion Middleware Core: 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, Oracle WebCenter Portal, and Oracle WebCenter Content components.

Java components

Business Intelligence: Fusion Middleware Control components that are deployed as one or more Java EE applications (and a set of resources) and are managed by Node Manager. See also Node Manager.

Java EE web service

Web Services: A web service implemented according to the Web Services for Java EE specification that defines the standard Java EE runtime architecture for implementing web services in Java.

JKS keystore

Fusion Middleware Core: The default JDK implementation of Java keystores. All Oracle Fusion Middleware Java components and Java EE applications use the JKS-based keystore and TrustStore.

JTA transaction

SOA Suite: Each step of a process related to transactional adapter operations is executed within the context of a JTA transaction. A JTA transaction ensures that one or more operations execute as an atomic unit of work.

Kerberos

OWSM: A network authentication service that enables computers (clients and servers) communicating over a non-secure network to prove their identity to one another in a secure manner, with the help of shared secrets and a trusted third party. In Kerberos, this trusted third party is the Key Distribution Center (KDC), which contains key information for clients and servers, called principals.

Kerberos ticket

OWSM: A sequence (of a few hundred bytes in length) that is used to control access to physically insecure networks. Kerberos tickets are based on the Kerberos protocol.

Key Performance Indicator (KPI)

Business Intelligence: A measurement that defines and tracks specific business goals and strategic objectives. KPIs often roll up into larger organizational strategies that require monitoring, improvement, and evaluation. KPIs have measurable values that usually vary with time, have targets to determine a score and performance status, include dimensions to allow for more precise analysis, and can be compared over time for trending purposes and to identify performance patterns. See also Oracle Scorecard and Strategy Management.

keystore

Fusion Middleware Core: A repository of objects necessary for security, such as private key certificates, digital certificates, and trusted CA certificates, as well as objects for message security. For example, SSL communication uses keystores.

KPI watchlist

Business Intelligence: A method of distributing KPIs to end users. A watchlist is a collection of KPIs that are built by adding the KPIs that are stored in the Oracle BI Presentation Catalog. After a KPI watchlist is built and saved, it is stored as a catalog object and can be added to dashboards and scorecards. See also key performance indicator (KPI), watchlist, and Oracle Scorecard and Strategy Management.

lazy child creation

JDeveloper/ADF: For ADF Faces UI components, when child components are created only when they are disclosed. Once disclosed and the associated child components are rendered, they remain created in the component tree. Certain components can set their children to be lazily created and then uncached, meaning that once the child component is rendered, if it is subsequently hidden, it is destroyed (it does not remain created in the component tree).

lazy content delivery

JDeveloper/ADF: In ADF Faces, a method of fetching data for a UI component. Initially, the component goes through the standard lifecycle. However, instead of fetching the data during that initial request, a separate partial page rendering (PPR) request is run and the data is then returned. Because the page has just been rendered, only the Render Response phase executes, allowing the corresponding data to be fetched and displayed.

LDAP Authentication provider

WebLogic Server: WebLogic Security Framework provider that uses a Lightweight Directory Access Protocol (LDAP) server to access user and group information, for example, iPlanet's Active Directory and Novell's OpenLDAP.

level

Business Intelligence: See hierarchy level.

Lifecycle Events

Coherence Suite: A set of events that represent the activation and disposal of a ConfigurableCacheFactory instance.

Live Events

Coherence Suite: An event framework that allows your applications to react to operations performed in the data grid. The framework uses an event-based model where events represent observable occurrences of cluster operations. The supported events include partitioned service, cache, and application events. These events can be consumed by registering event interceptors either programmatically or by using the cache configuration.

logical display folder

Business Intelligence: Folders used to organize objects in the Business Model and Mapping layer of an Oracle BI repository. They have no metadata meaning.

logical join

Business Intelligence: Joins that express relationships between logical tables. Logical joins are conceptual, rather than physical, joins. In other words, they do not join to particular keys or columns. A single logical join can correspond to many possible physical joins.

logical layer

Business Intelligence: See Business Model and Mapping layer.

logical level

Business Intelligence: In an Oracle BI repository, a component of a level-based hierarchy that either rolls up or is rolled up from other levels. Parent-child hierarchies have implicit, inter-member levels between ancestors and descendants that are not exposed as logical level objects in the metadata. Although parent-child hierarchies also contain logical level objects, these levels are system generated and exist to enable aggregation across all members only. See also dimension and hierarchy.

Logical SQL

Business Intelligence: The SQL statements that are understood by the Oracle BI Server. The Oracle BI Server Logical SQL includes standard SQL, plus special functions (SQL extensions) like AGO, TODATE, EVALUATE, and others. Clients like Presentation Services send Logical SQL to the Oracle BI Server when a user makes a request. In addition, Logical SQL is used in the Business Model and Mapping layer to enable heterogeneous database access and portability. The Oracle BI Server transforms Logical SQL into physical SQL that can be understood by source databases.

logical table

Business Intelligence: A table object in the Business Model and Mapping layer of an Oracle BI repository. A single logical table can map to one or more physical tables. Logical tables can be either fact tables or dimension tables. See also dimension table and fact table.

logical table source

Business Intelligence: Objects in the Business Model and Mapping layer of an Oracle BI repository that define the mappings from a single logical table to one or more physical tables. The physical to logical mapping can also be used to specify transformations that occur between the Physical layer and the Business Model and Mapping layer, and to enable aggregate navigation and fragmentation.

machine

Fusion Middleware Core: The logical representation of the computer that hosts one or more WebLogic Server instances.

managed Coherence server

Coherence Suite: A means to leverage the WebLogic Management Framework. Managed Coherence servers can be configured and controlled from an Administration Server. Managed Coherence servers can be explicitly associated with a Coherence cluster, or they can be associated with a WebLogic server cluster that is associated with a Coherence cluster. Managed Coherence servers are typically setup in tiers based on their type: a data tier for storing data, an application tier for hosting applications, and a proxy tier for allowing access to external clients.

Managed Server

WebLogic Server: A WebLogic Server instance that hosts business applications, application components, web services, and their associated resources.

Management Pack for Oracle Coherence

Coherence Suite: A feature of Oracle Enterprise Manager that provides comprehensive monitoring and management capabilities for Oracle Coherence. This pack provides complete cluster visibility by supplying detailed metrics of various cluster artifacts and their interdependencies. You can monitor more than one Oracle Coherence cluster from a single console.

Map events

Coherence Suite: Cache events using the JavaBean event model. The implementation allows applications to receive the events when and where they are needed, regardless of where the changes are actually occurring in the cluster.

master-detail relationship

JDeveloper/ADF: A hierarchical relationship in the data model of an ADF application established when a view link is created to associate two view object instances. Usually, but not necessarily, the master-detail relationship is based on a foreign-key relationship between the underlying database tables.

MBean Definition File

WebLogic Server: An XML file used by the WebLogic MBeanMaker to generate files for an MBean type.

MBean implementation file

WebLogic Server: One of several intermediate Java files generated by the WebLogic MBeanMaker utility to create an MBean type for a custom security provider. You edit this file to supply your specific method implementations.

MBean information file

WebLogic Server: One of several intermediate Java files generated by the WebLogic MBeanMaker utility to create an MBean type for a custom security provider. This file contains mostly metadata and therefore requires no editing.

MBean interface file

WebLogic Server: One of several intermediate Java files generated by the WebLogic MBeanMaker utility to create an MBean type for a custom security provider. This file is the client-side API to the MBean that your runtime class or your MBean implementation will use to obtain configuration data, and requires no editing.

MBean JAR file

WebLogic Server: JAR file that contains the runtime classes and MBean types for a security provider. MBean JAR files are created by the WebLogic MBeanMaker.

MBean type

WebLogic Server: A factory for creating the MBeans used to configure and manage security providers. MBean types are created by the WebLogic MBeanMaker.

MDS

Business Intelligence: Oracle Metadata Services. A core technology of the Application Development Framework. MDS provides a unified architecture for defining and using metadata in an extensible and customizable manner. See also MDS XML.

MDS XML

Business Intelligence: An XML format that is compatible with Oracle Metadata Services. MDS XML is a supported format for the Oracle BI repository. It enables integration with third-party source control management systems for offline repository development. MDS XML format is different from the XML format generated by the Oracle BI Server XML API. See also MDS, Oracle BI repository, and Oracle BI Server XML API.

measure column

Business Intelligence: A column that can change for each record and can be added up or aggregated. Typical measures are sales dollars and quantity ordered. Measures are calculated from data sources at query time. Measure columns are displayed in the Oracle BI repository, usually in fact tables, or in Presentation Services.

menu model

JDeveloper/ADF: In ADF Faces, a tree data model that knows how to retrieve the rowKey of the node that has the current focus (the focus node). It allows you to define the hierarchical tree of navigation in XML metadata.

Message Transmission Optimization Mechanism (MTOM)

Web Services: A method for optimizing the transmission of XML data of type xs:base64Binary or xs:hexBinary in SOAP messages, as defined in the SOAP Message Transmission Optimization Mechanism specification.

metadata

Business Intelligence: Data about data. Metadata objects include the descriptions of schemas (such as tables, columns, data types, primary keys, foreign keys, and so on) and logical constructs (like fact tables, dimensions, and logical table source mappings). The Oracle BI repository is made up of the metadata used by the Oracle BI Server to process queries.

metadata dictionary

Business Intelligence: A static set of XML documents that describe metadata objects, such as a column, including its properties and relationships with other metadata objects. A metadata dictionary can help users obtain more information about metrics or attributes for repository objects.

metadata label

Fusion Middleware Core: A means of selecting a particular version of each object from an MDS repository partition. Conceptually, it is a collection of document versions, one version per document, representing a horizontal stripe through the various document versions. This stripe comprises the document versions which were the tip versions (latest versions) at the time the label was created.

Metadata Services (MDS) repository

Fusion Middleware Core: A particular type of repository that contains metadata for certain types of deployed applications. This includes custom Java EE applications developed by your organization and some Oracle Fusion Middleware component applications, such as Oracle B2B. An MDS repository can be file-based or database-based.

method iterator

JDeveloper/ADF: A binding to an iterator that iterates over the collections returned by custom methods in the data control. An iterator binding that is always related to a method action binding object. The method action binding encapsulates the details about how to invoke the method and what parameters the method is expecting. The method action binding is itself bound to the method iterator, which provides the data.

microchart

Business Intelligence: A tiny graph displayed in a grid along with other tiny graphs and numbers, comprising the data cell contents of an advanced trellis view. In Oracle BI EE, a microchart is always a spark graph. See also advanced trellis and spark graph.

migration

Fusion Middleware Core: The process of moving from a third-party (non-Oracle) product to an Oracle product.

mission statement

Business Intelligence: A statement in a scorecard that specifies the key business goals and priorities that are required to achieve your vision. See also vision statement and Oracle Scorecard and Strategy Management.

Monitoring Dashboard

WebLogic Server: WebLogic Diagnostics Framework (WLDF) component that graphically presents the current and historical operating state of WebLogic Server and hosted applications.

monolithic session state model

Coherence Suite: A session state model used by Coherence*Web. This model stores all session state as a single entity, serializing and deserializing all attributes as a single operation.

MTOM

Web Services: See Message Transmission Optimization Mechanism (MTOM)

multi data source

WebLogic Server: Abstraction around a group of data sources that is bound to the JDNDI tree or local application context just like data sources are bound to the JNDI tree.

multi-database join

Business Intelligence: A join between two tables in an Oracle BI repository, where each table resides in a different database.

named criteria

JDeveloper/ADF: Predefined and reusable WHERE clause definitions that are dynamically applied to an ADF view object query.

NamedCache

Coherence Suite: The Coherence NamedCache object represents a data cache. This object is designed to hold resources that are shared among members of a Coherence cluster. These resources are managed in memory, and are typically composed of data that is also stored persistently in a database, or data that has been assembled or calculated. Thus, these resources are referred to as cached.

native EclipseLink

Toplink: The API underlying EclipseLink JPA and EclipseLink JAXB. It replaces the obsolete native TopLink API. Users can migrate from native TopLink to native EclipseLink through a package renaming utility included in all EclipseLink and TopLink distributions.

native TopLink

Toplink: The APIs, libraries, configuration files, and tools that constituted Oracle TopLink before the Java Persistence API (JPA) specification was written and implemented by TopLink (as TopLink Essentials). Native TopLink provided its own implementations of object/relational (ORM), object/XML (OXM), and other mapping/persistence technologies before the standards-based specifications were developed. Native TopLink is no longer available. However, applications can easily upgrade to native EclipseLink.

near cache

Coherence Suite: A near cache is a hybrid cache; it typically fronts a distributed cache or a remote cache with a local cache. Near cache invalidates front cache entries, using a configured invalidation strategy, and provides excellent performance and synchronization. This feature is intended to provide local access in cache clients for repeated reads.

Node Manager

WebLogic Server: A WebLogic Server utility that enables you to start, shut down, and restart Administration Server and Managed Server instances from a remote location.

object properties

Business Intelligence: Information about an object and attributes that the owner can assign to an object. Examples of properties include name, description, date stamps, read-only access, and do not index flag. See also permissions.

objective

Business Intelligence: A required or desired outcome in a scorecard that forms your corporate strategy. See also initiative and Oracle Scorecard and Strategy Management.

OCI

Business Intelligence: See Oracle Call Interface (OCI).

ODBC

Business Intelligence: See Open Database Connectivity (ODBC).

offline mode

Business Intelligence: In the Oracle BI Administration Tool, a mode where a repository builder can edit a repository that is not loaded into the Oracle BI Server.

online mode

Business Intelligence: In the Oracle BI Administration Tool, a mode where a repository builder can edit a repository while it is available for query operations. Online mode also allows user session monitoring for users connected to the subject areas in the repository.

opaque view

Business Intelligence: A Physical layer table that consists of a SELECT statement. In the Oracle BI repository, opaque views appear as view tables in the physical databases, but the view does not actually exist.

OPatch

Fusion Middleware Core: A Java-based utility used to patch an existing Oracle Fusion Middleware installation It runs on all supported operating systems and requires installation of the Oracle Universal Installer.

Open Database Connectivity (ODBC)

Business Intelligence: A standard interface used to access data in both relational and nonrelational databases. Database applications can use ODBC to access data stored in different types of database management systems, even if each database uses a different data storage format and programming interface.

operational configuration file (tangosol-coherence.xml)

Coherence Suite: A file that provides operational and runtime settings and is used to create and configure cluster, communication, and data management services. This file is also referred to as the operational deployment descriptor.

OptimisticCache service

Coherence Suite: An optimistic-concurrency version of the ReplicatedCache service that fully replicates all of its data to all cluster members and employs an optimization similar to optimistic database locking to maintain coherency. All servers end up with the same current value, even if multiple updates occur at the same time from different servers.

Oracle ADF

JDeveloper/ADF: Oracle Application Development Framework. An end-to-end application framework that builds on Java EE standards and open-source technologies to simplify and accelerate implementing service-oriented applications.

Oracle ADF Model Tester

JDeveloper/ADF: A Java application launched from JDeveloper that allows the ADF Business Components developer to interact with business objects of the data model project. The Oracle ADF Model Tester runs outside of JDeveloper and provides a full UI for testing and examining the data model project.

Oracle Application Development Framework (Oracle ADF)

JDeveloper/ADF: An end-to-end application framework that builds on Java EE standards and open-source technologies to simplify and accelerate implementing service-oriented applications.

Oracle BI Administration Tool

Business Intelligence: A Windows application that is used to create and edit Oracle BI repositories. The Administration Tool provides a graphical representation of the three parts of a repository: the Physical layer, the Business Model and Mapping layer, and the Presentation layer.

Oracle BI Briefing Books

Business Intelligence: A collection of static or updatable snapshots of dashboard pages, individual analyses, and BI Publisher reports. You can download a briefing book in PDF or MHTML format for printing and viewing. You also can update, schedule, and deliver a briefing book using an agent. See also agent.

Oracle BI JavaHost

Business Intelligence: A service that gives Presentation Services the ability to use functionality that is provided in Java libraries to support components such as graphs. The services are provided based on a request-response model.

Oracle BI Logical SQL View Object

Business Intelligence: Provides the developer the ability to create a Logical SQL statement to access the Oracle BI Server and fetch business intelligence data and bind it to native ADF components for inclusion on an ADF page. This view object uses a BI JDBC connection to the Oracle BI Server.

Oracle BI Presentation Catalog

Business Intelligence: Stores business intelligence objects, such as analyses and dashboards, and provides an interface where users create, access, and manage objects, and perform specific object-based tasks (for example, export, print, and edit). The catalog is organized into folders that are either shared or personal.

Oracle BI Presentation Services

Business Intelligence: Provides the framework and interface for the presentation of business intelligence data to web clients. It maintains a Presentation Catalog service on the file system for the customization of this presentation framework. It is a standalone process and communicates with the Oracle BI Server using ODBC over TCP/IP. It consists of components that are known as Answers, Delivers, and Interactive Dashboards. See also Open Database Connectivity (ODBC); Oracle BI Presentation Catalog; Oracle BI Presentation Services server; Oracle BI Server.

Oracle BI Presentation Services server

Business Intelligence: The Oracle BI web server that exchanges information and data with the Oracle BI Server.

Oracle BI Publisher

Business Intelligence: A J2EE application that provides enterprise-wide publishing services in Oracle Business Intelligence. It generates highly formatted, pixel-perfect reports. See also report.

Oracle BI Publisher report

Business Intelligence: See report.

Oracle BI repository

Business Intelligence: The set of Oracle Business Intelligence metadata that defines logical schemas, physical schemas, physical-to-logical mappings, aggregate table navigation, and other constructs. Oracle BI repositories can be in binary (RPD) format, in which repository metadata is contained in a single file with an extension of .rpd, or in a set of MDS XML documents. MDS XML format repositories are used for offline development only and cannot be loaded into the Oracle BI Server. Oracle BI repositories in both formats can be edited using the Oracle BI Administration Tool. See also metadata and Oracle BI Administration Tool.

Oracle BI Scheduler

Business Intelligence: An extensible scheduling application for scheduling results to be delivered to users at specified times. It is the engine behind the Oracle BI Delivers feature. See also results.

Oracle BI Server

Business Intelligence: A standalone process that maintains the logical data model that it provides to Presentation Services and other clients through ODBC. Metadata is maintained for the data model in a local proprietary file called the repository file. The Oracle BI Server processes user requests and queries underlying data sources.

Oracle BI Server XML API

Business Intelligence: Provides utilities to create a generic, XML-based representation of the Oracle BI repository metadata. You can use this XML file version of the repository to programmatically modify the metadata. The Oracle BI Server XML API objects correspond to metadata repository objects in an RPD file. These objects differ from XML objects in the Oracle BI Presentation Catalog. The XML generated by the Oracle BI Server XML API is different from the MDS XML format used for Oracle BI repositories integrated with third-party source control management systems. See also MDS XML.

Oracle BI session-based web services

Business Intelligence: An API that implements SOAP. These web services are designed for programmatic use, where a developer uses one web service to invoke many different business intelligence objects. These web services provide functionality on a wide range of Presentation Services operations. These web services enable the developer to extract results from Oracle BI Presentation Services and deliver them to external applications, perform Presentation Services management functions, and execute Oracle Business Intelligence alerts (known as Intelligent Agents). See also Oracle BI web services for SOA.

Oracle BI web services

Business Intelligence: See Oracle BI session-based web services and Oracle BI web services for SOA.

Oracle BI web services for SOA

Business Intelligence: Contains three web services, ExecuteAgent, ExecuteAnalysis, and ExecuteCondition, which are hosted by the bimiddleware J2EE application. These web services are designed to enable developers to use third-party web services clients (for example, Oracle SOA Suite) to browse for and include business intelligence objects in service oriented architecture components. See also Oracle BI session-based web services.

Oracle Business Intelligence Mobile

Business Intelligence: Oracle Business Intelligence Mobile is an application that enables you to view and interact with Oracle BI content on smartphones and tablets. Using Oracle BI Mobile, you can access and analyze all BI content such as analyses and dashboards, BI Publisher content, scorecard content, and mobile apps created by Oracle BI Mobile App Designer.

Oracle Business Intelligence Mobile App Designer

Business Intelligence: A tool for designing purposeful apps for mobile phones and tablets. The apps you create with Oracle BI Mobile App Designer are platform and device independent. The generated apps are based on the modern HTML5 standard, which means they can run on any modern browser on your mobile device. No client install is required.

Oracle Call Interface (OCI)

Business Intelligence: A connection interface that the Oracle BI Server can use to connect to Oracle Database data sources. You should always use OCI when importing metadata from or connecting to an Oracle Database.

Oracle Common directory

Fusion Middleware Core: The directory that contains the binary and library files that are common to all Oracle Fusion Middleware products and features installed in the Oracle home. In particular, the Oracle Common directory includes the files required for Oracle Enterprise Manager Fusion Middleware Control, WLST, the Configuration Wizard, upgrade tools, and Oracle JRF. There can be only one Oracle Common directory within each Oracle home.

Oracle Diagnostic Logging (ODL)

Fusion Middleware Core: An Oracle standard for the naming of log files and the formatting of the contents of the log files. This is often referred to as ODL.

Oracle Enterprise Manager Fusion Middleware Control

Fusion Middleware Core: A Web browser-based, graphical user interface that you can use to monitor and administer your Oracle Fusion Middleware environment.

Oracle Fusion Middleware Infrastructure

Fusion Middleware Core: A Oracle Fusion Middleware distribution that provides Oracle WebLogic Server and Oracle JRF.

Oracle Fusion Middleware Repository Creation Utility (RCU)

Fusion Middleware Core: A utility used to install the schemas required for specific Oracle Fusion Middleware components into a supported database.

Oracle home

Fusion Middleware Core: The Oracle home that is created for all the Oracle Fusion Middleware products on a host computer. This read-only directory contains binary and library files, the Oracle common directory, and the individual product directories for each Oracle Fusion Middleware product you install.

Oracle Infrastructure web services

Web Services: A category of web services supported in Oracle Fusion Middleware that encompasses SOA, Application Development Framework (ADF), Oracle Service Bus, and Oracle Enterprise Scheduler services.

Oracle JRF

Fusion Middleware Core: Oracle JRF (Java Required Files) consists of those components not included in the Oracle WebLogic Server installation and that provide common functionality for Oracle business applications and application frameworks. Oracle JRF consists of several independently developed libraries and applications that are deployed into a common location. The components that are considered part of Oracle JRF include Oracle Application Development Framework shared libraries and ODL logging handlers.

Oracle Metadata Services

Fusion Middleware Core: A consistent means to define, use, manage, and customize application metadata. Application metadata is characterized by its ability to define the behavior of an application.

Oracle OLAP

Business Intelligence: Oracle Database has an OLAP Option that provides an embedded, full-featured online analytical processing server. Oracle BI supports Oracle OLAP as a data source. When you import metadata from an Oracle OLAP source, the Oracle OLAP objects appear in the Physical layer of the Administration Tool. Oracle OLAP objects include Analytic Workspaces, which are containers for storing related cubes.

Oracle Scorecard and Strategy Management

Business Intelligence: A performance management tool that lets you describe and communicate your business strategy. You can drive and assess your corporate strategy and performance from the top of your organization down, or from the bottom up.

Oracle TopLink

Toplink: A persistence framework including development tools and runtime capabilities for providing transformation, mapping, and persistence operations in Java SE and Java EE environments. The core technology of TopLink is provided by EclipseLink, the open-source persistence framework from the Eclipse Foundation. TopLink includes additional features beyond EclipseLink, including TopLink Grid and TopLink Data Services. TopLink is included in Oracle distributions of Oracle WebLogic Server, Oracle Glassfish, and Oracle JDeveloper.

Oracle Wallet

Fusion Middleware Core: A container that stores your credentials, such as certificates, trusted certificates, certificate requests, and private keys. You can store Oracle wallets on the file system or in LDAP directories such as Oracle Internet Directory. Oracle wallets can be auto-login or password-protected wallets. An Oracle Wallet is a type of keystore.

OTN

Business Intelligence: See Oracle Technology Network (OTN).

OTP Anywhere

Identity Management: A risk-based challenge solution consisting of a server-generated one-time password (OTP) delivered to an end user through a configured out-of-band channel.

outbound transaction

SOA Suite: An outbound transaction from the SOA system (and hence from an adapter). For example, a transaction that is made against a database outside the SOA system.

outer edge

Business Intelligence: The outer edges are the parts of a trellis view that border the inner graphs. These include the column and row headers, the section headers, and so on. See also trellis and inner graph.

OWSM Agent

Identity Management: The OWSM component responsible for policy enforcement, execution, and gathering of run-time statistics. It is available on all Oracle Fusion Middleware Managed servers. The Agent is configured on the same server as the application it protects. It consists of two components: the Policy Access Point (PAP) which communicates with the Policy Manager, and the Policy Interceptor which is responsible for policy enforcement.

OWSM policy

OWSM: A web service policy provided by OWSM. OWSM provides a set of predefined policies based on common best practice policy patterns used in customer deployments.

OWSM Policy Manager

OWSM: The OWSM component responsible for reading and writing OWSM documents, including predefined and custom policies and assertion templates, from the OWSM Repository.

OWSM Repository

OWSM: The OWSM Repository stores OWSM metadata, such as policies, policy sets, assertions templates, and policy usage data. The OWSM Repository is available as a database (for production use) or as files in the file system (for development use in JDeveloper).

page definition file

JDeveloper/ADF: A file that defines the binding objects that populate the data in UI components at runtime. For every page that has ADF bindings, there must be a corresponding page definition file that defines the binding objects used by that page.

page flow scope

JDeveloper/ADF: An ADF-defined scope in the page lifecycle. An object in this scope is available as long as the user continues navigating from one page to another. If the user opens a new browser window and begins navigating, that series of windows will have its own page flow scope.

parallel flow

SOA Suite: Enables a BPEL process service component to perform multiple tasks at the same time. Parallel flow is especially useful when you must perform several time-consuming and independent tasks.

parent-child hierarchy

Business Intelligence: A hierarchy of members that all have the same type. All the dimension members of a parent-child hierarchy occur in a single data source. In a parent-child hierarchy, the inter-member relationships are parent-child relationships between dimension members. See also dimension.

parent-child relationship table

Business Intelligence: A table with values that explicitly define the inter-member relationships in a parent-child hierarchy. Also called a closure table.

partial page rendering (PPR)

JDeveloper/ADF: When the JSF page request life cycle (including conversion and validation) is run only for certain components on a page. The event root component determines on which components the life cycle is run.

partition

SOA Suite: Separate sections of the SOA Infrastructure into which you can deploy SOA composite applications. Deploying to partitions enables you to logically group SOA composites and perform bulk lifecycle management tasks on large numbers of composites.

partition transaction events

Coherence Suite: A set of events that are related to changes that may span multiple caches and are performed within the context of a single request.

partitioned cache events

Coherence Suite: A set of events that represent the operations being performed against a set of entries in a cache. Partitioned cache events include both entry events and entry processor events. Entry events are related to inserting, removing, and updating entries in a cache. Entry processor events are related to the execution of entry processors.

partitioned service events

Coherence Suite: A set of events that represent the operations being performed by a partitioned service. Partitioned service events include both partition transfer events and partition transaction events. Partition transfer events are related to the movement of partitions among cluster members.

partner link

SOA Suite: Characterizes the conversational relationship between two services in a BPEL process by defining the roles played by each service in the conversation and specifying the port type provided by each service to receive messages within the conversation.

pass-through calculation

Business Intelligence: A calculation that is not computed by the Oracle BI Server but instead is passed to another data source. Enables advanced users to leverage data source features and functions without the need to modify the Oracle BI repository.

Password Validation provider

WebLogic Server: WebLogic Security Framework provider that can be configured with an authentication provider to enforce a set of password composition rules.

patch

Fusion Middleware Core: A collection of files usually associated with a particular version of an Oracle product and involves updating from one minor version of the product to a newer minor version of the same product (for example, from version 12.1.2.1.0 to version 12.1.2.2.0).

patch set

Fusion Middleware Core: A single patch that contains a collection of patches designed to be applied together.

patch set update

Fusion Middleware Core: A quarterly patch that contains the most critical fixes for the applicable product, allowing customers to apply one patch to avoid many problems.

patching

Fusion Middleware Core: Copying a small collection of files over an existing installation.

peer

JDeveloper/ADF: In the ADF Faces framework, an intermediary between a client component and the document object model (DOM). Peers interact with the DOM generated by the Java renderer and handle updating that state and responding to user interactions.

per domain Node Manager

WebLogic Server: The version of Node Manager that controls all WebLogic Server instances belonging to the same domain. The server instances need not reside on the same machine. Note that this is the default Node Manager type that is configured in a domain.

per host Node Manager

WebLogic Server: The version of Node Manager that controls all WebLogic Server instances configured on a particular machine. The server instances need not all be members of the same domain.

performance tile

Business Intelligence: A view type that displays a single aggregate measure value in a manner that is both visually simple and prominent, yet it immediately reveals summary metrics to the user that will likely be presented in more detail within a dashboard view. A performance tile view communicates status through simple formatting by using color, labels, and limited styles, or through conditional formatting of the background color or measure value to make the tile visually prominent.

permissions

Business Intelligence: Specify which users can access an object, and limit how users can interact with an object. Examples of permissions include write, delete, and change permissions. See also object properties.

persistent attribute

JDeveloper/ADF: An attribute of an ADF Business Components entity object or view object that is derived from the underlying data source, such as a database table.

personally identifiable information (PII)

OWSM: PII refers to Social Security numbers, addresses, bank account numbers, and other similar information that is typically associated with one specific user and must generally be protected.

perspective

Business Intelligence: A category in your organization with which to associate initiatives, objectives, and KPIs in a scorecard. A perspective can represent a key stakeholder (such as a customer, employee, or shareholder) or a key competency area (such as time, cost, or quality). See also initiative, key performance indicator (KPI), objective, and Oracle Scorecard and Strategy Management.

physical catalog

Business Intelligence: An object in the Physical layer of an Oracle BI repository that groups different schemas. A catalog contains all the schemas (metadata) for a database object.

physical display folder

Business Intelligence: Folders that organize objects in the Physical layer of an Oracle BI repository. They have no metadata meaning.

physical join

Business Intelligence: Joins between tables in the Physical layer of an Oracle BI repository.

Physical layer

Business Intelligence: A layer of the Oracle BI repository that contains objects that represent physical data constructs from back-end data sources. The Physical layer defines the objects and relationships available for writing physical queries. This layer encapsulates source dependencies to enable portability and federation.

physical schema

Business Intelligence: An object in the Physical layer of an Oracle BI repository that represents a schema from a back-end database.

physical table

Business Intelligence: An object in the Physical layer of an Oracle BI repository, usually corresponding to a table that exists in a physical database. See also Physical layer.

PII

OWSM: See personally identifiable information (PII)

POF (Portable Object Format)

Coherence Suite: A proprietary data format for high-performance serialization. POF format is significantly faster than the standard Java Serializable interface format and the serialized result set is smaller.

POF configuration file (coherence-pof-config.xml)

Coherence Suite: Custom data types when using Portable Object Format (POF) to serialize objects. This file is also referred to as the POF configuration deployment descriptor.

point of view area

Business Intelligence: An area within KPIs and scorecards that shows data of specific interest to you, such as the area of business for which you are responsible. The point of view area displays controls for the dimensions of KPIs that are used in the scorecard to measure the progress and performance of initiatives and objectives. See also initiative, key performance indicator (KPI), and objective.

policy assertion

OWSM: The smallest unit of a policy that performs a specific action for the request and response operations. Assertions, like policies, are grouped into categories, such as Reliable Messaging, Management, WS-Addressing, Security, Configuration, and MTOM.

policy subject

OWSM: The target resource to which OWSM policies are attached. As defined in the Web Services Policy 1.5 - Framework, a policy subject is an entity (for example, an endpoint, message, resource, or operation) with which a policy can be associated.

portal manager

WebCenter Portal: A WebCenter Portal user who is responsible for managing a particular portal. A portal manager can add and remove members, invite new members, enable self registration, provide and update portal metadata, and manage the tools and services available to the portal. The Portal Manager role was referred to as the Moderator role in previous releases.

PPR

JDeveloper/ADF: partial page rendering. When the JSF page request life cycle (including conversion and validation) is run only for certain components on a page. The event root component determines on which components the life cycle is run.

predefined assertion template

OWSM: A read-only document included with your OWSM installation consisting of policy assertions that can be used to construct OWSM policies.

predefined policy

OWSM: OWSM policy provided with your Fusion Middleware installation that can be used to secure and configure your environment. Predefined policies are read only and cannot be modified.

presentation hierarchy

Business Intelligence: An object in the Presentation layer of an Oracle BI repository that provides an explicit way to expose the multidimensional model in Presentation Services and other clients. Presentation hierarchies expose analytic functionality such as member selection, custom member groups, and asymmetric queries. Users can create hierarchy-based queries using presentation hierarchies. In Presentation Services, presentation hierarchies are displayed as hierarchical columns. See also hierarchical column and presentation level.

Presentation layer

Business Intelligence: Provides a way to present customized, secure, role-based views of a business model to users. It adds a level of abstraction over the Business Model and Mapping layer in the Oracle BI repository. The Presentation layer provides the view of the data seen by users who build analyses in Presentation Services and other client tools and applications. See also Business Model and Mapping layer.

presentation level

Business Intelligence: In the Oracle BI repository, a component of a presentation hierarchy that either rolls up or is rolled up from other levels. Presentation levels are displayed as levels within hierarchical columns in Presentation Services. See also hierarchy level and presentation hierarchy.

Presentation Services

Business Intelligence: See Oracle BI Presentation Services.

Presentation Services server

Business Intelligence: See Oracle BI Presentation Services server.

presentation table

Business Intelligence: An object in the Presentation layer of an Oracle BI repository that is used to organize columns into categories that make sense to the user community. A presentation table can contain columns from one or more logical tables. The names and object properties of the presentation tables are independent of the logical table properties.

primary key

Business Intelligence: A column (or set of columns) where each value is unique and identifies a single row of a table.

process instance

Business Intelligence: A unique process on an individual workstation that is associated with a BI instance. See also BI instance.

producer

WebCenter: A communication link between portlet consumers (such as a portal). When a consumer application renders a portlet, it calls the producer of that portlet, which in turn executes the portlet and returns the results as portlet content. A producer can contain one or more portlets. A portlet can be contained by only one producer. WebCenter Portal supports two types of producers: Oracle PDK-Java producers: Deployed to a Java EE application server, often remote, communicates through Simple Object Access Protocol (SOAP) over HTTP. Web Services for Remote Portlets (WSRP): A web services standard that enables the plug-and-play of visual, user-facing web services with portals or other intermediary web applications. Being a standard, WSRP enables interoperability between a standards-enabled container based on a particular language (such as JSR 286, .NET, Perl) and any WSRP portal.

product directory

Fusion Middleware Core: A directory within the Oracle home that contains the binary files associated with a logical product or feature set. The name of each product directory within the Middleware Oracle home is predefined by the installer and cannot be changed.

prompt

Business Intelligence: A type of filter that enables the content designer to build and specify data values or the end user to choose specific data values to provide a result set for an individual analysis or multiple analyses included on a dashboard or dashboard page. A prompt expands or refines existing dashboard and analysis filters. The types of prompts are column prompts, currency prompts, image prompts, and variable prompts. See also column prompt, currency prompt, filter, image prompt, and variable prompt.

prompted link

Business Intelligence: Captures the path to a dashboard page and a simplified presentation of the dashboard prompt. See also bookmark link.

proxy authorization control

Identity Management: A type of control that can be used to request that the associated operation be performed under the authorization of another user.

proxy service

Coherence Suite: A service that allows connections (using TCP) from clients that run outside the cluster. While many applications are configured so that all clients are also cluster members, there are many use cases that have clients running outside the cluster. Remote clients are especially useful in cases where there are hundreds or thousands of client processes, where the clients are not running on the Java platform, or where there is a greater degree of decoupling.

proxy tier

Coherence Suite: One or more computers running Coherence*Extend proxy servers.

push replication

Coherence Suite: The ability to replicate cache operations from one cluster to another by using an external protocol (TCP/IP or JMS). Operations are optimistically replicated, and in the event that communication between the clusters breaks down, they are queued up until communication is reestablished.

query

Business Intelligence: Contains the underlying SQL statements that are issued to the Oracle BI Server. You do not have to know a query language to use Oracle Business Intelligence.

query cache

Business Intelligence: A facility to store query results for use by other queries.

ragged hierarchy

Business Intelligence: See unbalanced hierarchy.

range paging

JDeveloper/ADF: An access mode set on Oracle ADF view objects when a large result set is possible. The range paging mode fetches and caches only the current page of rows in the view object and allows the Oracle ADF application to page back and forth through data more efficiently than if the application used scrollable access.

RDBMS security store

WebLogic Server: An external RDBMS containing a data store that, when configured in a domain, is used by select security providers for storing security data.

read-through caching

Coherence Suite: A technique of updating the cache: When an application asks the cache for an entry that is not in the cache, Coherence automatically delegates to the cache store to load the entry from the underlying data source. If the entry exists in the data source, then the cache store loads it and returns it to Coherence. Coherence then places it in the cache for future use and finally returns the entry to the application code that requested it.

read-write-backing-map scheme

Coherence Suite: A map that provides a size-limited cache of a persistent store, such as a relational database.

real time client configured as a compute client

Coherence Suite: A server-class client that provides key manageability, monitoring, Quality of Service, and performance capabilities. See also real time cluster member client.

real time clients configured as Extend/TCP clients

Coherence Suite: Clients that connect to the Coherence cluster over TCP/IP through specially configured cluster members that are called extend proxies. Real time extend/TCP clients are multilanguage clients and currently Java, .NET (C#) and C++ real time extend/TCP clients are available. In contrast to data clients, real time extend/TCP clients can sign up for notifications for events taking place in the grid and can take advantage of Coherence near caches and continuous queries.

real time cluster member client

Coherence Suite: Possibly a part of the Grid Edition cluster with all the capabilities of the Grid Edition except those associated with managing partitioned data and those associated with being an extend proxy. Real time cluster member clients may be Grid Edition members configured to have all their partitioned cache services storage-enabled attributes set to false, but unable to host connections from extend/TCP clients. Real time cluster member clients are always Java clients and cannot be configured as extend proxies for other real time clients (only Server Edition members can be configured as proxy servers for use by multilanguage data clients and real time extend/TCP clients). Real time cluster member clients are free in Grid Edition but must be paid for in Enterprise Edition.

recovery

Fusion Middleware Core: The process of recovering your environment in the event of data loss or corruption, host failure, or media failure, by restoring files that you previously backed up.

refresh-ahead caching

Coherence Suite: A technique of updating the cache. Coherence lets you configure a cache to automatically and asynchronously reload (refresh) any recently accessed cache entry from the cache loader before its expiration. The result is that after a frequently accessed entry has entered the cache, a read against a potentially slow cache store when the entry is reloaded due to expiration has no effect on the application. The asynchronous refresh is triggered only when an object that is sufficiently close to its expiration time is accessed. If the object is accessed after its expiration time, then Coherence performs a synchronous read from the cache store to refresh its value.

region

JDeveloper/ADF: An ADF Faces component that renders the content of a bounded taskflow.

reliable messaging

Web Services: See Web Services Reliable Messaging (WS-ReliableMessaging).

RemoteCache service

Coherence Suite: A means of routing cache operations to a cache on the cluster.

RemoteInvocation service

Coherence Suite: A service that executes tasks on the remote Coherence cluster. At runtime, a connection is made to an extend proxy service and an InvocationService implementation is returned that executes synchronous Invocable tasks within the remote cluster JVM to which the client is connected.

replicated cache

Coherence Suite: Data that is replicated to each of the application server members in the cluster. This type of cache is recommended if faster read access is required but it is not suitable for write operations, because the data must be written to each of the members. The drawback of replicated caches is that they require a large amount of memory because every member has a copy of every object.

ReplicatedCache service

Coherence Suite: A synchronized replicated cache service that fully replicates all of its data to all cluster members that run the service. Replicated caches are often used to manage internal application metadata.

replication

Identity Management: A form of data synchronization used to ensure that changes in the directory environment are reflected in each instance of the server. That is, whenever a change is made in one directory server instance, that same change is also made in every other instance.

report

Business Intelligence: The response returned to the user from the execution of a query created using Oracle BI Publisher. Reports can be formatted, presented on a dashboard page, saved in the Oracle BI Presentation Catalog, and shared with other users. See also analysis.

report configuration file

Coherence Suite: A report definition that results in the creation of a report file that displays management information for a particular set of metrics. Report configuration files must be referenced in a report group configuration file to be used at run time. The default report configuration files are located in the /reports directory of the coherence.jar file and are referenced by the default report group configuration file.

report group configuration file (report-group.xml)

Coherence Suite: List of the name and location of report definition files and the output directory where reports are written.

repository

Business Intelligence: See Oracle BI repository.

repository variable

Business Intelligence: See variable.

Representational State Transfer (REST)

Fusion Middleware Core: REST is an architectural style that provides a set of design rules for creating stateless services that are viewed as resources, or sources of specific information (data and functionality). Each resource can be identified by its unique Uniform Resource Identifiers (URIs). REST is a simple interface that transmits data over a standardized interface (such as HTTP) without an additional messaging layer, such as SOAP.

resource scope

Identity Management: For global policy attachments in OWSM, the resource scope identifies the location within the resource where the policy set containing policies should be applied. It is mapped to the attachTo attribute of the policy set and is used for conflict resolution when multiple policy sets exist.

resource type

OWSM: For global policy attachments in OWSM, the resource type, or subject type, identifies the type of endpoint to which the policy set applies.

Resources window

JDeveloper/ADF: A manager of resources available through application server, database, and file system connections.

REST

Web Services: See Representational State Transfer (REST).

results

Business Intelligence: The output returned from the Oracle BI Server for an analysis. See also analysis.

Role Mapping provider

WebLogic Server: WebLogic Security Framework provider that determines what security roles apply to the principals stored in a subject when the subject is attempting to perform an operation on a WebLogic resource. Because this operation usually involves gaining access to the WebLogic resource, Role Mapping providers are typically used with Authorization providers.

root application module

JDeveloper/ADF: An Oracle ADF application module that contains (logically) one or more other application module instances, as well as view object instances. The outermost application module is referred to as the root application module. At runtime, the root application module defines the Transaction object.

row set iterator

JDeveloper/ADF: The manager of the current object and current range information in the Oracle ADF application. Iterator bindings directly bind to the default row set iterator of the default row set of any view object instance.

SAAJ

Web Services: See SOAP with Attachments API for Java (SAAJ).

SAML

Fusion Middleware Core: See Security Assertion Markup Language (SAML).

SAML Token Profile

Web Services: The SAML Token profile, defined in the Security Assertion Markup Language (SAML) Token Profile 1.1 specification, is part of the core set of WS-Security standards. It specifies how SAML assertions can be used for web services security.

SAR file

SOA Suite: A SOA archive deployment unit. A SAR file is a special JAR file that requires a prefix of sca_. (For example, sca_OrderBookingComposite_rev1.0.jar). The SAR file packages binding components and service components, such as BPEL processes, business rules, human tasks, and mediator routing services, into a SOA composite application.

scorecard

Business Intelligence: See Oracle Scorecard and Strategy Management.

secure conversation

Web Services: See Web Services Secure Conversation Language (WS-SecureConversation)

secure property

JDeveloper/ADF: A property on an ADF Faces UI component that must not ever be set on the client.

Security Assertion Markup Language (SAML)

Web Services: An XML standard for exchanging authentication and authorization data between security domains as defined in the Security Assertion Markup Language (SAML) specification.

security patch update

Fusion Middleware Core: An iterative, cumulative patch consisting of security fixes.

security provider database

WebLogic Server: A database that contains the users, groups, security policies, roles, and credentials used by some types of security providers to provide security services. The security provider database can be the embedded LDAP server (as used by the WebLogic Server security providers), a properties file (as used by the sample security providers), or a production-quality database that you may already be using.

security realm

WebLogic Server: An entity that acts as a scoping mechanism. Each security realm consists of a set of configured security providers, users, groups, roles, and security policies. You can configure multiple security realms in a domain; however, only one can be the default (active) security realm.

Security Service Provider Interfaces (SSPIs)

WebLogic Server: A set of WebLogic Server packages that enables custom security providers to be developed and integrated with the WebLogic Server Security Service. These interfaces are implemented by the WebLogic security providers and custom security providers. The WebLogic Security Framework calls methods in these interfaces to perform security operations.

seeded search

JDeveloper/ADF: In ADF Faces, a search whose criteria are already determined and from which the user can choose, or you can allow the user to add criteria and then save those searches.

selection step

Business Intelligence: A choice of values that is applied after the query is aggregated that affects only the members displayed, not the resulting aggregate values. Along with filters, selection steps restrict the results for an analysis. See also analysis and filter.

Selector Tree

JDeveloper/ADF: A feature in the ADF Skin Editor that displays the list of style classes, global selector aliases, selectors, and at-rules for which you can configure properties to change the appearance of ADF Faces and ADF Data Visualization components.

server-side at-rule

JDeveloper/ADF: An at-rule that the ADF skinning framework evaluates and then determines the style properties to render. Examples of this category of at-rule include @agent, @accessibility-profile, and @locale.

service component

SOA Suite: A component that implements the business logic or processing rules of a SOA composite application. Service components are the basic building blocks of SOA composite applications. Service components include BPEL processes, business rules, human tasks, BPMN processes, mediator routing services, and spring.

service component architecture (SCA)

SOA Suite: Provides the service details and their interdependencies to form composite applications. SCA enables you to represent business logic as reusable service components that can be easily integrated into any SCA-compliant application. The resulting application is known as a SOA composite application.

service engine

SOA Suite: Executes the business logic of the respective service component within the SOA composite application (for example, a BPEL process). There are service engines for a BPEL process, human workflow, decision service, Oracle Mediator, BPMN process, and spring.

Service Infrastructure

SOA Suite: Provides the internal message transport infrastructure for connecting components and enabling data flow. The service infrastructure is responsible for routing messages along the wire connections between services, service components, and references.

service request

Coherence Suite: The round-trip required to complete a task. A request begins the moment a client starts a task and includes the following: The time it takes to deliver the request to an executing member (server), the interval between the time the task is received and placed into a service queue until the task starts, the task execution time, and the time it takes to deliver a result back to the client.

service table

Fusion Middleware Core: A database table that provides a way for service providers to publish endpoint information about their services, and for clients of these services to query and bind to these services. A service table is a single table in a database schema. There is one row for every endpoint that is published to it. The service table schema is initially created by the Oracle Fusion Applications Repository Creation Utility.

service task

Coherence Suite: A called object that executes on one or more members. The objects include filters, invocation agents (entry processors and aggregators), or single-pass agents (Invocable objects).

service-enabled application module

JDeveloper/ADF: An ADF application module published with a service interface connection to make it available as an external web service in an Oracle Fusion web application. The service interface makes view object instances of the application module available to service consumers.

service-oriented architecture (SOA)

SOA Suite: Provides an enterprise architecture that supports building connected enterprise applications to provide solutions to business problems. SOA facilitates the development of enterprise applications as modular business web services that can be easily integrated and reused, creating a flexible, adaptable IT infrastructure.

Service-oriented architecture (SOA) bundle

SOA Suite: A ZIP file that includes multiple SOA archive (SAR) profiles that you can deploy to an application server at the same time.

Servlet Authentication filter

WebLogic Server: A unique implementation of the Java EE filter object that replaces container-based authentication. Servlet Authentication filters control the authentication conversation with the client by redirecting to a remote site to execute the login, extracting login information out of the query string, and negotiating a login mechanism with the browser.

Session Reaper

Coherence Suite: In Coherence*Web, the means of ending a session. The Session Reaper provides a service similar to the JVM Garbage Collection (GC) capability: the Session Reaper is responsible for destroying any session that is no longer used, which is determined by when that session times out.

session variable

Business Intelligence: See variable.

shared application module

JDeveloper/ADF: A grouping of view object instances when reuse of static data across the Oracle ADF application is required. For example, a shared application module can group view instances that access lookup data, such as a list of countries.

Simple and Protected GSS-API Negotiation Mechanism (SPNEGO)

OWSM: A standard that enables a client and a service to negotiate a method to use for authentication.

simple trellis

Business Intelligence: A trellis view that displays inner visualizations that are all the same type, such as all scatter graphs. The inner visualizations all use a common axis, also known as a synchronized scale. See also synchronized scale; trellis; visualization.

skin

WebCenter: In WebCenter Portal, a resource that defines colors, fonts, and other aspects of components used on the pages of a portal. A skin changes the way the user interface appears, and not how the application functions. You can use skins to give individual portals a distinct personality or to apply specific branding, achieving the appearance that best suits an organization.

skip-level hierarchy

Business Intelligence: A hierarchy where some members do not have a value for a particular ancestor level. For example, in the United States, the city of Washington in the District of Columbia does not belong to a state. The expectation is that users can still navigate from the country level (United States) to Washington and below without the need for a state. See also hierarchy.

smart list

JDeveloper/ADF: A subset of the drop-down list of values of an inputComboboxListOfValues component. It is an additional filter applied to the full list to display only the most likely choices.

smart watchlist

Business Intelligence: A smart watchlist is a view into a particular scorecard based on criteria that you specify. For example, a smart watchlist might show the top ten KPIs in a scorecard based on best performance or all the objectives, initiatives, and KPIs in a scorecard that are owned by a specific business owner. See also watchlist and Oracle Scorecard and Strategy Management.

snowflake schema

Business Intelligence: A dimensional schema where one or more of the dimensions are partially or completely normalized.

SOA composite application

SOA Suite: An assembly of service binding components, service components, and reference binding components designed and deployed in a single application. Wiring between the components enables message communication. The details for a composite are stored in the composite.xml file.

SOA Infrastructure

SOA Suite: A Java EE-compliant application running in Oracle WebLogic Server. The application manages SOA composite applications and their lifecycle, service engines, and binding components. You deploy SOA composite applications to a partition of your choice on the SOA Infrastructure.

SOAP over JMS transport

Web Services: Typically, web services and clients communicate using SOAP over HTTP/S as the connection protocol. Using SOAP over JMS transport, web services and clients communicate using JMS destinations instead of HTTP connections, offering the following benefits: reliability, scalability, and quality of service. As with web service reliable messaging, if the server goes down while the method invocation is still in the queue, it will be handled as soon as server is restarted. When a client invokes a web service, the client does not wait for a response, and the execution of the client can continue.

SOAP with Attachments API for Java (SAAJ)

Web Services: Implementation that developers can use to produce and consume messages conforming to the SOAP 1.1 specification and SOAP with Attachments notes, as defined in SOAP with Attachments API for Java (SAAJ) specification.

spark graph

Business Intelligence: An embedded mini-graph that, in conjunction with other mini-graphs and numbers, illustrates a single trend. Spark graphs are also known as sparks. Sparks do not include axes or labels; they get their context from the content that surrounds them. Each type of spark graph has only one measure, which is hidden; the scale is relative to itself only. A spark graph can be of the graph subtype Spark Line, Spark Bar, or Spark Area. See also microchart.

speciality color

JDeveloper/ADF: A category of global selector alias that define color properties for ADF skins. The global selector aliases in this category do not derive the hue value from anchor colors and are not anchor colors for other colors.

Split session state model

Coherence Suite: A session state model used by Coherence*Web. This model extends the traditional model, but separates the larger session attributes into independent physical entities.

SPNEGO

OWSM: See Simple and Protected GSS-API Negotiation Mechanism (SPNEGO)

spring framework

SOA Suite: Integrates components that use Java interfaces instead of WSDL files into SOA composite applications.

SQL

Business Intelligence: See structured query language (SQL).

SSPIs MBean

WebLogic Server: The interfaces used by Oracle to generate MBean types for the WebLogic security providers, and from which you generate MBean types for custom security providers. Security Service Provider Interface (SSPIs) MBeans may be required (for configuration) or optional (for management).

standalone domain

Fusion Middleware Core: A container for system components, such as Oracle HTTP Server. It has a directory structure similar to an Oracle WebLogic Server domain, but it does not contain an Administration Server or a Managed Server. It can contain one or more instances of system components of the same type, such as Oracle HTTP Server, or a mix of system component types. WebLogic Management Framework, which includes tools, such as the Configuration Wizard, pack and unpack, WLST, and Node Manager, can operate on standalone domains.

star schema

Business Intelligence: A relational schema that allows dimensional analysis of historical information. Star schemas have one-to-many relationships between the logical dimension tables and the logical fact table. Each star consists of a single fact table joined to a set of denormalized dimension tables.

static group

Identity Management: A group in the directory server that defines its membership by explicitly specifying a set of distinguished names of members in the group.

strategy contribution wheel

Business Intelligence: A component of a scorecard that makes it easy to see the contribution (or impact) a specific objective or KPI has on a parent objective in a series of concentric rings (or wheel diagram). You use the strategy contribution wheel diagram to hierarchically view an objective and its supporting child objectives and KPIs. See also Oracle Scorecard and Strategy Management.

strategy map

Business Intelligence: A component of a scorecard that shows how the objectives that have been defined for a scorecard and the KPIs that measure their progress are aligned by perspectives. It also shows cause-and-effect relationships. See also Oracle Scorecard and Strategy Management.

strategy tree

Business Intelligence: A component of a scorecard that shows an objective and its supporting child objectives and KPIs hierarchically in a tree diagram. See also Oracle Scorecard and Strategy Management.

Structure view

WebCenter Portal: In WebCenter Portal, a page editor view that provides access to layout components in a tree structure to fine-tune the design of page templates, system pages, and tasks flows.

Structure window

JDeveloper/ADF: A display of a structural view of the data in the document currently selected in the active Oracle JDeveloper window of those windows that participate in providing structure. These windows include the diagrams, the editors and viewers, and the Properties window.

structured attribute

JDeveloper/ADF: In a data control, a returned object that is neither a Java primitive type (represented as an attribute) nor a collection of any type. An example of a structured attribute would be a domain, which is a developer-created data type used to simplify application maintenance.

structured query language (SQL)

Business Intelligence: A standard programming language for querying and modifying data. See also Logical SQL.

subject area

Business Intelligence: In an Oracle BI repository, an object in the Presentation layer that organizes and presents data about a business model. It is the highest-level object in the Presentation layer and represents the view of the data that users see in Presentation Services. Oracle BI repository subject areas contain presentation tables, presentation columns, and presentation hierarchies. In Presentation Services, subject areas contain folders, measure columns, attribute columns, hierarchical columns, and levels.

synchronization

Identity Management: A mechanism that keeps track of changes in the directory environment and allows them to be reflected elsewhere.

synchronized scale

Business Intelligence: (Applicable to simple trellis only) A synchronized scale means that all of the visualizations within the trellis are viewed on the same scale, that is, they share a common axis. Having a common axis makes all graph markers easy to compare across rows and columns. See also simple trellis and visualization.

synchronous web service

SOA Suite: Provides an immediate response to an invocation. A BPEL process service component can connect to synchronous web services through a partner link, send data, and then receive the reply in the same synchronous invocation.

system component

Fusion Middleware Core: A manageable process that is not deployed in a Java application container. A system container does not run in an application server such as Oracle WebLogic Server. Oracle HTTP Server is an example of a system component.

system components

Business Intelligence: Server processes (not Java applications) that are managed by the Common Administration Model (CAM).

Tangosol Cluster Management Protocol (TCMP)

Coherence Suite: An IP-based protocol that is used to discover cluster members, manage the cluster, provision services, and transmit data. The default TCMP configuration uses a combination of UDP/IP unicast and multicast. However, TCMP can be configured to use UDP/IP unicast only, TCP/IP, SDP/IP, and SSL over TCP/IP or SDP/IP. Moreover, on Exalogic systems, TCMP can be configured to use reliable message bus transport protocols such as IMB, LWMB, TMB, TMBS, SDMB, or SDMBS.

target component

JDeveloper/ADF: In ADF Faces, the UI component that is rerendered when any event occurs on another component, referred to as the trigger component.

TCMP

Coherence Suite: Tangosol Cluster Management Protocol. An IP-based protocol that is used to discover cluster members, manage the cluster, provision services, and transmit data. The default TCMP configuration uses a combination of UDP/IP unicast and multicast. However, TCMP can be configured to use UDP/IP unicast only, TCP/IP, SDP/IP, and SSL over TCP/IP or SDP/IP. Moreover, on Exalogic systems, TCMP can be configured to use reliable message bus transport protocols such as IMB, LWMB, TMB, TMBS, SDMB, or SDMBS.

test to production

Fusion Middleware Core: The process of copying your environment from a source environment, such as a test environment, to another environment, such as a production environment. It does not move transactional data.

TopLink Data Services

Toplink: A Java Persistence API for RESTful Services (JPA-RS), plus additional functionality and integration.

TopLink Essentials

Toplink: The Reference Implementation of the EJB 3.0 Java Persistence API (JPA), developed by Oracle and contributed to the open source community. TopLink Essentials provided the JPA 1.0 functionality for the EJB 3.0 Reference Implementation. It is superseded by TopLink's implementation of JPA, provided by EclipseLink.

TopLink Grid

Coherence Suite: An integration between Oracle Coherence and Oracle TopLink that allows some or all of a domain model to be stored in a Coherence data grid and also allows Coherence to be used as the TopLink level 2 cache.

Toplink: A facility for integrating the TopLink JPA implementation, provided by EclipseLink, with Oracle Coherence, an In-Memory Data Grid. TopLink Grid provides the means for scaling JPA applications using Oracle Coherence. Applications can be scaled in a number of ways, ranging from using Coherence as a distributed shared (L2) cache to directing Java Persistence query language (JPQL) queries to Coherence for parallel execution across the grid to reduce database load.

traditional session state model

Coherence Suite: A model used by Coherence*Web that stores all session states as a single entity, but serializes and deserializes attributes individually.

transformation

Business Intelligence: Work that is performed on data when moving from a database to another location (sometimes another database). Some transformations are typically performed on data when it is moved from a transaction system to a data warehouse system.

SOA Suite: The process of mapping source schema elements to target schema elements in an XSL map file with the XSLT Map Editor.

transient attribute

JDeveloper/ADF: An attribute of an ADF Business Components entity object or view object that is not derived from the underlying data source, such as a database table. The value of a transient attribute is derived from other attributes either by using Groovy expressions or through Java code. Transient attributes are used as temporary value holders and to implement business logic.

transient process

SOA Suite: A type of BPEL process that does not incur any intermediate dehydration points during process execution. If there are unhandled faults or there is system downtime during process execution, the instances of a transient process do not leave a trace in the system. Instances of transient processes cannot be saved in-flight (whether they complete normally or abnormally). Transient processes are typically short-lived, request-response style processes. The synchronous process you design in Oracle JDeveloper is an example of a transient process.

transition component

JDeveloper/ADF: In ADF Faces, with regard to geometry management of the components, a component that can be stretched but does not stretch its children. A transition component must always be used between a component that stretches its children and a component that does not stretch.

trellis

Business Intelligence: Displays multidimensional data shown as a set of cells in a grid, where each cell represents a subset of data using a particular graph type. Data can be represented with graphs, microcharts, and numbers. The trellis view has two subtypes: simple trellis and advanced trellis. See also advanced trellis; simple trellis; visualization.

trigger component

JDeveloper/ADF: In ADF Faces, the UI component whose event causes another component (referred to as the target component) to be rerendered.

trinidad-config.xml file

JDeveloper/ADF: A configuration file that determines the ADF skin for a Fusion web application. It can also configure other application features such as, for example, accessibility and localization.

trinidad-skins.xml file

JDeveloper/ADF: The registry of ADF skins available for use in an Oracle Fusion web application.

UDDI

Web Services: See Universal Description, Discovery, and Integration (UDDI).

UI hint

JDeveloper/ADF: ADF Business Components metadata that defines label text, tooltip, and format mask hints for entity object and view object attributes. UI hints that you define on the business service layer can be used by UI components in Oracle ADF clients. This is sometimes referred to as a control hint.

unattended account

Identity Management: An account that is never used by an end user.

unbalanced hierarchy

Business Intelligence: A hierarchy where the leaves do not have the same depth. For example, an organization might choose to have data for the current month at the day level, data for the previous year at the month level, and data for the previous five years at the quarter level. See also hierarchy.

unbounded taskflow

JDeveloper/ADF: A set of activities, Oracle ADF control flow rules, and managed beans that interact to allow a user to complete a task. An unbounded taskflow has one or more points of entry.

unit test

SOA Suite: Automates the testing of SOA composite applications by simulating the interaction between a SOA composite application and its web service partners before deployment to a production environment. You can also create test cases for testing BPEL process service components included in the SOA composite application. This testing helps to ensure that a process interacts with web service partners as expected by the time it is ready for deployment to a production environment.

Universal Description, Discovery, and Integration (UDDI)

Web Services: Standard for describing a web service; registering a web service in a well-known registry; and discovering other registered web services as defined in the Universal Description, Discovery, and Integration (UDDI) specification.

upgrade

Fusion Middleware Core: The process of moving from a previous major version to a new major version. For example, an upgrade would be required to move from Oracle Fusion Middleware 11g to Oracle Fusion Middleware 12c.

Upgrade Assistant

Fusion Middleware Core: A utility used to upgrade schemas and configuration information from one major version to another, such as Oracle Fusion Middleware 11g to Oracle Fusion Middleware 12c.

value binding

JDeveloper/ADF: A binding used by UI components that display data. Value bindings range from the most basic variety that work with a simple text field to more sophisticated list and tree bindings that support the additional needs of list, table, and tree UI controls. Types of value bindings include: attribute, list, table, tree, graph, and button bindings.

value extractor

Coherence Suite: A means of accepting as input a value object and returning an attribute of that object.

value hierarchy

Business Intelligence: See parent-child hierarchy.

value iterator

JDeveloper/ADF: An ADF Model iterator pointing to a collection that contains only one data object whose attributes are the binding container variable.

variable

Business Intelligence: Objects in an Oracle BI repository that are used to streamline administrative tasks and dynamically modify metadata content to adjust to a changing data environment. Variables are of the following types: Repository variables have a single value at any point in time. There are two types of repository variables: static and dynamic. Session variables are created and assigned a value when each user logs on. There are two types of session variables: system and nonsystem.

variable iterator

JDeveloper/ADF: A binding to an iterator that exposes all the variables in the binding container to the other bindings. While there is an iterator binding for each collection, there is only one variable iterator binding for all variables used on the page.

variable prompt

Business Intelligence: Enables the user to select a value specified in the variable prompt to display on the dashboard. A variable prompt is not dependent upon column data, but enables you to manipulate, for example add or multiply, the column data on an analysis. See also prompt.

view accessor

JDeveloper/ADF: An ADF Business Components object that points from an entity object attribute (or view object) to a destination view object or shared view instance in the same application workspace. The view accessor returns a row set that by default contains all the rows from the destination view object.

view criteria

JDeveloper/ADF: An ADF Business Components object that allows developers to adapt a query to a particular usage by filtering the row set of the view object instance in an Oracle ADF application.

view link

JDeveloper/ADF: An Oracle ADF Business Components object that represents the relationship between two view objects, which is usually, but not necessarily, based on a foreign-key relationship between the underlying database tables.

view link accessor

JDeveloper/ADF: An Oracle ADF Business Components object that identifies an accessor attribute that the master collection uses at runtime to return the detail collection row set in an Oracle ADF application.

view link consistency

JDeveloper/ADF: Runtime logic provided by the Oracle ADF Business Components framework. This logic ensures when a new row created in one view object instance will be automatically added to the row sets of others view instances based on the same entity object. This behavior ensures that the Oracle ADF client consistently reflects new rows in different application pages for a pending transaction.

view object

JDeveloper/ADF: An ADF Business Components object that represents a SQL query and simplifies working with its results. The SQL query is used to join, project, filter, sort, and aggregate data into the shape required by the end-user task being represented in the user interface.

view scope

JDeveloper/ADF: An ADF-defined scope in the page life cycle. An object in this scope is available until the ID for the current view changes. Use view scope to hold values for a given page. Unlike the JavaServer Faces view scope, objects stored in the ADF Faces view scope will survive page refreshes and redirections to the same view ID.

virtual authentication device

Identity Management: A personalized device for entering a password or PIN or an authentication credential entry device to protect users while interacting with a protected web application. The virtual authentication devices harden the process of entering and transmitting authentication credentials and provide users with verification that they are authenticating on the valid application.

virtual physical table

Business Intelligence: A physical table that is made from a stored procedure or a SELECT statement. Creating virtual tables can provide the Oracle BI Server and the underlying databases with the proper metadata to perform some advanced query requests.

virtual static group

Identity Management: A special type of group that appears to be static to external clients, but obtains its membership information from another group (such as a dynamic group) in the server.

virtualization

Identity Management: A process that enables users and applications to view, retrieve, and manipulate large amounts of data from various sources without moving the data or exposing technical details about how it is stored.

vision statement

Business Intelligence: A short statement in a scorecard that describes what your organization wants to become sometime in the future. For example, it might be to become the most successful business in the South American polypropylene market. See also mission statement and Oracle Scorecard and Strategy Management.

visualization

Business Intelligence: In the context of Oracle BI EE, a visualization is the choice of graph that appears within a data cell in a trellis view. There are many visualizations from which to choose when creating a trellis view, including bar graphs, scatter graphs, and spark graphs. See also trellis.

WADL

Web Services: See Web Application Description Language (WADL)

WAR-scoped Coherence cluster members

Coherence Suite: For deployments on non-WebLogic Server application servers, each deployed web application becomes its own Coherence member. This configuration produces the largest number of Coherence members in the cluster (one for each deployed WAR file that uses Coherence) and because the Coherence library is deployed in the web application's class path, there will be as many copies of the Coherence classes loaded as there are deployed WAR files.

watchlist

Business Intelligence: A table that lists scorecard objects (that is, initiatives, objectives, and KPIs) that are related to a particular aspect of a scorecard or that are grouped together for a particular purpose. There are different types for watchlists, for example: KPI watchlists or smart watchlists. See also KPI watchlist, smart watchlist, and Oracle Scorecard and Strategy Management.

waterfall graph

Business Intelligence: A graph type that lets you visualize how a value increases or decreases sequentially and cumulatively. A waterfall graph focuses the user's attention on how each measure contributes to the overall total, and communicates through simple formatting by using color.

Web Application Description Language (WADL)

Web Services: An XML-based file format that describes a RESTful web services application.

web service

Web Services: Web services are loosely coupled, distributed environments that allow companies to integrate heterogeneous applications within the enterprise or expose business functions to their customers and partners over the Internet. Because you access web services using standard Web protocols such as XML or HTTP, the diverse and heterogeneous applications on the Web (which typically already understand XML and HTTP) can automatically access web services and communicate with each other.

web service endpoint

Web Services: The web service address, specified by a Uniform Resource Identifier (URI), that may be used to communicate with an instance of a web service.

web service port

Web Services: See web service endpoint.

Web Services Addressing (WS-Addressing)

Web Services: Transport-neutral mechanisms to address web services and messages as described in the Web Services Addressing (WS-Addressing) specification. In particular, the specification defines a number of XML elements used to identify Web service endpoints and to secure end-to-end endpoint identification in messages.

Web Services Atomic Transaction

Web Services: The web services atomic transaction framework enables interoperability with other external transaction processing systems, such as WebSphere, Microsoft .NET, and so on through the support of the following specifications: Web Services Atomic Transactions (WS-Atomic Transaction) and Web Services Coordination (WS-Coordination). These specifications define an extensible framework for coordinating distributed activities among a set of participants.

Web Services Definition Language (WSDL)

Web Services: An XML-based language providing a model for describing SOAP-based web services as described in the Web Services Description Language (WSDL) 1.1 document submission.

Web Services Federation Language (WS-Federation)

Web Services: Mechanisms that allow different security realms to federate, such that authorized access to resources managed in one realm can be provided to security principals whose identities and attributes are managed in other realms. This includes mechanisms for brokering of identity, attribute, authentication and authorization assertions between realms, and privacy of federated claims as defined in the Web Services Federation Language (WS-Federation) Version 1.2 specification.

Web Services Inspection Language (WS-Inspection)

Web Services: Provides an XML format for assisting in the inspection of a site for available services as described in the Web Services Inspection Language (WS-Inspection) 1.0 specification.

Web Services Metadata Exchange (WS-MetadataExchange)

Web Services: Part of the WS-Federation roadmap which allows retrieval of metadata about a web service endpoint as described in the Web Services Metadata Exchange (WS-MetadataExchange) specification.

web services policy

Web Services: An XML document that defines the capabilities and requirements of a web service such as whether and how a message must be secured, whether and how a message must be delivered reliably, and so on. A policy is expressed as one or more policy assertions representing a Web service's capabilities or requirements. For example, a policy assertion may stipulate that a request to a Web service be encrypted.

Web Services Policy Attachment (WS-PolicyAttachment)

Web Services: Mechanisms for associating policies with the subjects to which they apply as defined in the Web Services Policy 1.5 - Attachment and the Web Services Policy 1.2 - Attachment (WS-PolicyAttachment) specifications.

Web Services Policy Framework (WS-Policy)

Web Services: General purpose model and corresponding syntax to describe and communicate the policies of a Web service as described in the Web Services Policy 1.5 - Framework and Web Services Policy 1.2 - Framework (WS-Policy) specifications.

Web Services Reliable Messaging (WS-ReliableMessaging)

Web Services: Implementation that enables two endpoints (web service and client) running on different server instances to communicate reliably in the presence of failures in software components, systems, or networks. WS-ReliableMessaging is defined in the Web Services Reliable Messaging (WS-ReliableMessaging) 1.1 and Web Services Reliable Messaging Protocol (WS-ReliableMessaging) 1._0 specifications.

Web Services Reliable Messaging Policy Assertion (WS-RM Policy)

Web Services: Policy assertion for reliable messaging for use with WS-Policy and WS-ReliableMessaging, as defined in Web Services Reliable Messaging Policy Assertion (WS-RM Policy) specification.

Web Services Secure Conversation Language (WS-SecureConversation)

Web Services: Standard built on top of the WS-Security and WS-Policy models to provide secure communication between services. The Web Services Secure Conversation Language (WS-SecureConversation) specification defines mechanisms for establishing and sharing security contexts, and deriving keys from security contexts, to enable a secure conversation.

Web Services Security (WS-Security)

Web Services: Standard set of SOAP [SOAP11, SOAP12] extensions that can be used when building secure Web services to implement message content integrity and confidentiality, as described in the WS-Security 1.1 OASIS standard.

Web Services Security Policy (WS-SecurityPolicy)

Web Services: Set of security policy assertions for use with the WS-Policy framework, as defined in Web Services Security Policy (WS-SecurityPolicy) 1.3, 1.2, and 1.1 specifications.

WebLogic component

WebLogic Server: One of a number of Java EE component technologies, which include servlets, JavaServer Pages, and Enterprise JavaBeans. To build a WebLogic Server application, you must create and assemble components, using the service APIs when necessary. Components are executed in the WebLogic Server web container or EJB container. Web components provide the presentation logic for browser-based Java EE applications. EJB components encapsulate business objects and processes.

WebLogic container

WebLogic Server: A WebLogic Server component that provides the lifecycle support and services defined by the Java EE specifications so that the components you build do not have to handle underlying lifecycle details.

WebLogic domain

Fusion Middleware Core: A logically related group of Oracle WebLogic Server resources, which include an Administration Server and, typically, one or more Managed Servers and logically related resources and services that are managed collectively as one unit.

WebLogic home directory

WebLogic Server: The root directory of the WebLogic Server installation.

WebLogic Java EE service

WebLogic Server: One of a number of Java EE services, which include access to standard network protocols, database systems, and messaging systems. To build a WebLogic Server application, you must create and assemble components, using the service APIs when necessary. Web applications and EJBs are built on Java EE application services, such as JDBC, Java Messaging Service (JMS), and Java Transaction API (JTA).

WebLogic JDBC data source

WebLogic Server: A means of database access and database connection management. Each data source contains a pool of database connections that are created when the data source is created and at server startup.

WebLogic Management Framework

Fusion Middleware Core: A framework that provides heterogeneous management capabilities for Oracle Fusion Middleware products that require basic administrative capabilities. Its capabilities include start, stop, configuration settings, and other such basic product lifecycle operations through a common command line, API, and user interface. WebLogic Management Framework includes specific WebLogic Server and Coherence features. WebLogic Management Framework manages both WebLogic Server domains, which can contain Java components and system components, and standalone domains, which contain system components.

WebLogic MBeanMaker

WebLogic Server: A command-line utility that takes an MBean Definition File (MDF) as input and output files for an MBean type.

WebLogic Messaging Bridge

WebLogic Server: A forwarding mechanism that provides interoperability between WebLogic JMS implementations, and between JMS and other messaging products.

WebLogic resource

WebLogic Server: An entity that is accessible from WebLogic Server, such as events, servlets, JDBC connection pools, JMS destinations, JNDI contexts, connections, sockets, files, and enterprise applications and resources, such as databases.

WebLogic Scripting Tool

WebLogic Server: A command-line scripting interface used for managing and monitoring active or inactive WebLogic Server domains.

WebLogic Security Framework

WebLogic Server: Interfaces in the weblogic.security.service package that unify security enforcement and present security as a service to other WebLogic Server components.

WebLogic security provider

WebLogic Server: Software modules that can be used by a WebLogic Server security realm to provide security services (such as authentication, authorization, auditing, and credential mapping) to applications. A security provider consists of runtime classes and MBeans, which are created from SSPIs and MBean types, respectively. Security providers are WebLogic security providers (provided with WebLogic Server) or custom security providers.

WebLogic Security Service

WebLogic Server: A WebLogic Server subsystem that implements the security architecture that comprises three major components: the WebLogic Security Framework, the Security Service Provider Interfaces (SSPIs), and the WebLogic security providers.

WebLogic Server

WebLogic Server: A scalable, enterprise-ready Java Platform, Enterprise Edition (Java EE) application server. The WebLogic Server infrastructure supports the deployment of many types of distributed applications and is an ideal foundation for building applications based on service-oriented architecture (SOA).

WebLogic Server Administration Console

WebLogic Server: A web application hosted by the Administration Server that is used for managing and monitoring an active domain.

WebLogic server domain

Business Intelligence: Contains Java components that are configured to participate in the servicing of SOAP, HTTP, and other forms of requests.

WebLogic Store-and-Forward

WebLogic Server: A means of delivering messages reliably between applications that are distributed across WebLogic Server instances.

WebLogic web service policy

Web Services: A web service policy provided by Oracle WebLogic Server. It is recommended that you use OWSM policies over WebLogic web services whenever possible. You cannot mix your use of OWSM and WebLogic web service policies on the same web service.

weblogic.Deployer

WebLogic Server: A Java-based deployment tool that provides administrators and developers command-line deployment operations.

wildcarded host name verifier

WebLogic Server: A class that works the same as the default WebLogic Server host name verifier; however, the wildcarded host name verifier also accepts the asterisk character in the host name that is obtained from the certificate's Subject CommonName attribute; and SubjectAlternativeName dnsName (SAN) certificates.

Windows NT Authentication provider

WebLogic Server: WebLogic Security Framework authentication provider that uses Windows NT users and groups for authentication purposes

wire

SOA Suite: Wires connect service binding components, service components, and reference binding components into a complete SOA composite application.

WKA

Coherence Suite: Coherence Well Known Addresses. A feature that allows cluster members to discover and join a cluster using unicast instead of multicast. WKA is most often used when multicast networking is undesirable or unavailable in an environment or when an environment is not properly configured to support multicast. All cluster multicast communication is disabled if WKA is enabled.

WLST

WebLogic Server: WebLogic Scripting Tool

write-behind caching

Coherence Suite: A technique of updating the cache. Modified cache entries are asynchronously written to the data source after a configured delay. Note that this applies only to cache inserts and updates. Cache entries are removed synchronously from the data source.

write-through caching

Coherence Suite: A technique of updating the cache. When the application updates a piece of data in the cache, then the operation does not complete until Coherence has gone through the cache store and successfully stored the data to the underlying data source.

WS-Addressing

Web Services: See Web Services Addressing (WS-Addressing).

WS-Federation

Web Services: See Web Services Federation Language (WS-Federation)

WS-Inspection

Web Services: See Web Services Inspection Language (WS-Inspection)

WS-MetadataExchange

Web Services: See Web Services Metadata Exchange (WS-MetadataExchange)

WS-Policy

Web Services: See Web Services Policy Framework (WS-Policy).

WS-PolicyAttachment

Web Services: See Web Services Policy Attachment (WS-PolicyAttachment).

WS-ReliableMessaging

Web Services: See Web Services Reliable Messaging (WS-ReliableMessaging).

WS-RM Policy

Web Services: See Web Services Reliable Messaging Policy Assertion (WS-RM Policy)

WS-SecureConversation

Web Services: See Web Services Secure Conversation Language (WS-SecureConversation)

WS-Security

Web Services: See Web Services Security (WS-Security).

WS-SecurityPolicy

Web Services: See Web Services Security Policy (WS-SecurityPolicy).

WS-Trust

Web Services: Extensions that build on [WS-Security] to provide a framework for requesting and issuing security tokens, and to broker trust relationships as defined in the WS-Trust specification.

WSDL

Web Services: See Web Services Definition Language (WSDL)

XA transaction support

SOA Suite: Enables multiple resources (such as databases, application servers, message queues, transactional caches) to be accessed within the same transaction.

XML API

Business Intelligence: See Oracle BI Server XML API.

XML Encryption

Web Services: Process for encrypting data and representing the result in XML as defined in the XML Encryption Syntax and Processing specification.

XML Signature

Web Services: Rules and syntax for processing XML digital signatures as described in the XML Signature Syntax and Processing specification.

Oracle Legal Notices

Copyright Notice

Copyright © 1994-2018, Oracle and/or its affiliates. All rights reserved.

License Restrictions Warranty/Consequential Damages Disclaimer

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

Warranty Disclaimer

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

Restricted Rights Notice

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable:

U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.

Hazardous Applications Notice

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Trademark Notice

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

Third-Party Content, Products, and Services Disclaimer

This software or hardware and documentation may provide access to or information about content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.

Pre-General Availability Draft Documentation Notice

If this document is in public or private pre-General Availability status:

This documentation is in pre-General Availability status and is intended for demonstration and preliminary use only. It may not be specific to the hardware on which you are using the software. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to this documentation and will not be responsible for any loss, costs, or damages incurred due to the use of this documentation.

Private Pre-General Availability Draft Documentation Notice

If this document is in private pre-General Availability status:

The information contained in this document is for informational sharing purposes only and should be considered in your capacity as a customer advisory board member or pursuant to your pre-General Availability trial agreement only. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described in this document remains at the sole discretion of Oracle.

This document in any form, software or printed matter, contains proprietary information that is the exclusive property of Oracle. Your access to and use of this confidential material is subject to the terms and conditions of your Oracle Master Agreement, Oracle License and Services Agreement, Oracle PartnerNetwork Agreement, Oracle distribution agreement, or other license agreement which has been executed by you and Oracle and with which you agree to comply. This document and information contained herein may not be disclosed, copied, reproduced, or distributed to anyone outside Oracle without prior written consent of Oracle. This document is not part of your license agreement nor can it be incorporated into any contractual agreement with Oracle or its subsidiaries or affiliates.

Documentation Accessibility

For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.

Access to Oracle Support

Oracle customers that have purchased support have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.