| BI Java Software Development Kit Glossary | ||||||||||||||||||||||||||
|
Browse the SDK Glossary alphabetically:
ActiveX Data Objects (ADO)A logical object model for programmatically accessing a variety of data sources through OLE DB interfaces. ADO, provided by Microsoft, is the foundation for Microsoft's ADO MD extension, upon which the BI ODBO Connector is based.
ActiveX Data Objects Multidimensional (ADO MD)A logical object model provided by Microsoft that facilitates easy access to multidimensional data by extending ADO with objects specific to multidimensional data, such as cubes and cellsets. Like ADO, ADO MD uses an underlying OLE DB provider to gain access to data. The BI ODBO Connector uses ADO MD to support connectivity to OLAP data sources.
ADOAcronym for ActiveX Data Objects.
ADO MDAcronym for ActiveX Data Objects Multidimensional.
BI Java ConnectorOne of a set of four JCA (J2EE Connector Architecture)-compliant resource adapters that allow you to connect applications built with the BI Java SDK to heterogeneous data sources:
You can also use the Connectors to make external data sources available
in BW, via BW's UD Connect.
BI Java SDKAbbreviation for SAP's Business Intelligence Java Software Development Kit.
BI JDBC ConnectorA resource adapter for the Business Intelligence domain based on Sun's Java Database Connectivity (JDBC), which is the standard Java API for Relational Database Management Systems (RDBMS). The BI JDBC Connector may be deployed into SAP's Web Application Server, and allows you to connect applications built with the BI Java SDK to over 170 JDBC drivers, supporting data sources such as Teradata, Oracle, Microsoft SQL Server, Microsoft Access, DB2, Microsoft Excel, and text files such as CSV. You can also use the BI JDBC Connector to make these data sources available in BW, via BW's UD Connect. The JDBC Connector implements the BI Java SDK's IBIRelational interface.
BI ODBO ConnectorA resource adapter for the Business Intelligence domain based on Microsoft's OLE DB for OLAP (ODBO), which is the established industry-standard OLAP API for the Windows platform. The BI ODBO Connector may be deployed into SAP's Web Application Server, and allows you to connect applications built with the BI Java SDK to ODBO-compliant OLAP data sources such as Microsoft Analysis Services, SAS, and Microsoft PivotTable Services. You can also use the BI ODBO Connector to make these data sources available in BW, via BW's UD Connect. The ODBO Connector implements the BI Java SDK's IBIOlap interface.
BI SAP Query ConnectorA resource adapter for the Business Intelligence domain based on SAP Query, which is a component of SAP's Web Application Server that allows you to create custom reports without any ABAP programming knowledge. The BI SAP Query Connector uses SAP Query to allow applications created with the BI Java SDK to access data from these SAP operational applications. You can also use the BI SAP Query Connector to make these data sources available in BW, via BW's UD Connect. The SAP Query Connector implements the BI Java SDK's IBIRelational interface.
BI XMLA ConnectorA resource adapter for the Business Intelligence domain based on Microsoft's
XML for Analysis (XMLA), that facilitates Web services-based, platform-independent
access to OLAP providers. The BI XMLA Connector may be deployed into SAP's
Web Application Server, and enables the exchange of analytical data between
a client application and a data provider working over the Web, using a
SOAP-based XML communication API. You can also use the BI XMLA Connector to make these data sources available in BW, via BW's UD Connect. The BI XMLA Connector implements the BI Java SDK's IBIOlap interface.
Business Intelligence Java Software Development Kit (BI Java SDK)A Java software development kit with which you can build analytical applications that access, manipulate, and display both multidimensional (Online Analytical Processing, or OLAP) and tabular (relational) data. The BI Java SDK consists of:
columnAn element of a table that describes its structure and the types of its rows. A column has a name, a data type, and an implicit order (ordinal) based on the order chosen when defining the table. Columns can also belong to indexes, which are used to ensure uniqueness (set property) of rows in the table.
command processorPart of each of the BI Java SDK's query APIs, interfaces that make it easier to use the underlying query models by hiding the complexity of these models. With the command processors, you can create and manipulate complex queries with simple commands. You can think of the individual methods of the command processors in terms of macros that consist of several method calls manipulating the structures of queries. The SDK provides two command processors:
Common Client Interface (CCI)An API defined by Sun's JCA specification that is common across heterogeneous EISs. It is designed to be "toolable" -- that is, it leverages the Java Beans architecture so that development tools can incorporate the CCI into their architecture. Note that the BI Java Connectors implement only the connection interfaces defined by the CCI. The CCI's interaction interfaces, data interfaces, and metadata interfaces, however, are not implemented by the BI Java SDK. BI-specific client APIs that are tailored for OLAP interactions are provided by the BI Java Connectors.
Common Warehouse Metamodel (CWM)An Object Management Group (OMG) standard that provides for a common understanding of metadata in order to exchange it between heterogeneous systems. CWM describes the exchange of metadata in the data warehousing and analysis, business intelligence, knowledge management, and portal technologies domains. CWM is MOF is the modeling language for CWM, UML is its modeling notation, and XMI is used to interchange the metadata. CWM is capable of modeling a wide spectrum of OLAP and relational providers. The SDK uses CWM to represent relational and OLAP data in the Relational and OLAP Metadata Models. For more information about CWM, see http://www.omg.org/cwm/.
connectorSynonym for resource adapter. See more at BI Java Connector.
Connector GatewayAn SAP Enterprise Portal service that provides instances of connections to Portal components.
cubeIn the OLAP domain, set of data organized as a multidimensional structure defined according to dimensions and measures. Related BW concepts include InfoCube and query.
CWMAcronym for Common Warehouse Metamodel.
deployment descriptorAssists in deploying a resource adapter (known as connector in the SDK) by defining the contract between a resource adapter provider and a deployer. The deployment descriptor file contains information about which classes implement the interfaces with which the application server interacts.
dimensionIn the OLAP domain, a collection of similar data which, together with other such collections, forms the structure of a cube. Typical dimensions include time, product, and geography. Each dimension may be organized into a basic parent-child hierarchy or, if supported by the data source, a hierarchy of levels. For example, a geography dimension might include levels for continent, country, state, and city. Note that in BW, InfoObject (characteristic) is a related term, but "dimension" means something entirely different in BW than it does in the OLAP domain.
Enterprise Information System (EIS)A system such as an ERP (Enterprise Resource Planning), database, or mainframe transaction processing system which forms the information infrastructure of an enterprise system.
filterA set of criteria that restricts the set of records returned as the result of a query. With filters, you define which subset of data appears in the result set.
hierarchyA logical tree structure that organizes the members of a dimension into a parent-child relationship. If supported by the data source, the hierarchy consists of levels, where the top level is an aggregate of all members and each subsequent level has zero or more child members.
IBIOlapAn interface provided by the BI Java SDK and implemented by all OLAP connectors which serves as an entry point to interfaces that support access to multidimensional metadata and queries.
IBIRelationalAn interface provided by the BI Java SDK and implemented by all relational connectors which serves as a point of entry to a set of interfaces that provide access to relational metadata and queries.
INativeAn optional interface defined in the Portal Connection Framework API which can be implemented by a connector. INative enables you to access the connected EIS via an API that is tailored specifically for that underlying EIS. The interface returned depends on the connected EIS.
J2EE Connector Architecture (JCA)A standard architecture from Sun designed for connecting J2EE servers with EISs. The architecture defines a set of contracts, such as transactions, security, and connection management, that a connector has to support to plug in to an application server. JCA provides an API for connecting to heterogeneous data sources in a consistent manner. The BI Java Connectors are JCA-compliant.
Java Metadata Interface (JMI)An extensible metadata service for the Java platform that provides a common Java programming model for accessing metadata. JMI defines a Java mapping for the Meta Object Facility (MOF) specification from the Object Management Group (OMG). The SDK uses JMI mapping to render its query and metadata models into Java APIs. For more information, see http://jcp.org/jsr/detail/40.jsp.
JCAAcronym for J2EE Connector Architecture
JCo (SAP Java Connector)SAP's toolkit that allows a Java application to communicate with any SAP system. It is used by the BI SAP Query Connector to interact with SAP Web Application Server instances. For more information about JCo, visit the SAP Service Marketplace at:
JDBC (Java Database Connectivity)Provides an API that lets you access relational databases using the Java programming language. It provides cross-DBMS connectivity to a wide range of SQL databases, and also provides access to tabular data sources such as spreadsheets or flat files. For more information, see http://java.sun.com/products/jdbc/index.html.
JMIAcronym for Java Metadata Interface.
JMI service (Java Metadata Interface Service)Any system that provides a JMI-compliant API to access its public metadata. The BI Java Connectors expose metadata of the underlying EIS via JMI services.
levelA set of nodes (members) in a tree hierarchy in supporting data sources that are at the same distance from the root of the tree. For example, in a geography hierarchy, the top level might be all places, the second level might be continents, the third level might be countries, and the fourth level might be cities.
MDX (Multidimensional Expressions)Microsoft's SQL-like query language used to retrieve and manipulate multidimensional data.
measureOne category of values -- usually numeric -- used to define a cube. These values are derived from one or more columns in the cube's fact table and are the basis for aggregation and analysis. In BW, related terms include key figure and structure element.
memberAn element of a dimension that represents one or more occurrences of data. A member can be unique (it occurs only once) or non-unique (it may occur more than once in its dimension). For example, in a geography dimension that includes cities in the US, the member Portland could be non-unique, since there is a city called Portland in the state of Oregon and in the state of Maine. In BW, members are referred to as instances of characteristics.
Meta Object Facility (MOF)An OMG (Object Management Group) standard for the specification of interoperable metamodels. MOF defines language rules (syntax and semantics) for constructing metamodels and provides programming tools for saving and accessing metadata in repositories. The MOF standard is integrated in XMI, and CWM uses MOF as its modeling language. MOF can also refer to any metadata service which abides by the MOF specifications. CWM is a MOF-compliant metamodel.
metadata APIA set of interfaces provided by the BI Java SDK which expose the metadata of a given data source. The SDK includes two metadata APIs, both generated via JMI from their respective metadata models:
metadata modelAn abstract language for expressing metadata. The BI Java SDK leverages CWM metadata models (metamodels), and the following two CWM packages in particular:
The SDK's metadata models also rely upon reference classes from CWM's Foundation and Objectmodel layers.
metadata repositoryContains the different classes of metadata and is capable of persisting and retrieving MOF-compliant objects, resulting in a consistent and homogeneous data model across all source systems. Metadata repository is a general term used by the Object Management Group (OMG).The Metamodel Repository is SAP's implementation of the metadata repository.
Metamodel Repository (MMR)SAP's implementation of a metamodel and metadata repository. It is named after the metamodel layer (the meta-meta-data, or m2 layer) of the OMG's Meta Object Facility (MOF), which is the main focus in SAP BI.
MOFAcronym for Meta Object Facility
multidimensional dataData in dimensional models suitable for business analytics. In this documentation, we use the term "multidimensional data" synonymously with "OLAP data."
Object Linking and Embedding Database (OLE DB)Microsoft's set of Component Object Model (COM) interfaces that provide applications with uniform access to data stored in diverse information sources. OLE DB also provides the ability to implement additional database services.
Object Management Group (OMG)An open membership, not-for-profit consortium that produces and maintains computer industry specifications for interoperable enterprise applications. For more information, see http://www.omg.org/.
ODBOAcronym for OLE DB for OLAP.
OLAPAcronym for online analytical processing.
OLAP Command ProcessorPart of the OLAP Query API, an interface that makes it easier to use the API by hiding the complexity of the underlying OLAP Query Model. With this interface, you can create and manipulate complex multidimensional queries with simple commands.
OLAP data provider (ODP)Provides data in multidimensional views and metadata compatible with the OLAP Metadata Model.
OLAP Metadata APIA set of interfaces provided by the BI Java SDK for accessing the metadata of an OLAP data source. Generated via JMI from the SDK's OLAP Metadata Model.
OLAP Metadata ModelA model provided by the BI Java SDK that exposes business data in a multidimensional format which specifically supports data analysis. Based on the CWM OLAP package.
OLAP Query APIA set of interfaces provided by the BI Java SDK that let you define queries against an OLAP server. The API is generated via JMI from the OLAP Query Model, based on metadata provided by the OLAP Metadata Model, and includes the simplified OLAP Command Processor.
OLAP Query ModelAn abstraction layer, or model, in the BI Java SDK designed for formulating OLAP queries independently of data source-specific query APIs. The model is based on the CWM-compliant metadata provided by the OLAP Metadata Model.
OLAP Table ModelA companion to the BI Java SDK's ResultSet API that facilitates the rendering of a multidimensional dataset into a two-dimensional matrix.
OLE DBAcronym for Object Linking and Embedding Database.
OLE DB for OLAP (ODBO)Microsoft's set of objects and interfaces that extend the ability of OLE DB to provide access to multidimensional data sources on the Windows platform. Providers of OLAP data can implement the interfaces described with OLE DB for OLAP to allow all OLAP clients to access their data.
OLTPAcronym for online transactional processing.
OMGAcronym for Object Management Group.
online analytical processing (OLAP)A system of organizing data in a multidimensional model that is suitable for decision support. OLAP is the analytical counterpart of OLTP, or online transactional processing. SAP's BW is an OLAP system.
online transactional processing (OLTP)A system of organizing data in a highly normalized relational model that is suitable for transactional support with frequent update operations. SAP's R/3 is an OLTP system.
Portal Connection FrameworkPart of SAP's Enterprise Portal, provides a set of APIs which extend the standard JCA interfaces and are used to build Portal-compliant connectors. The BI Java Connectors are compliant with the Portal Connection Framework.
query APISets of interfaces provided by the BI Java SDK for creating queries against data sources. They are generated via JMI from the SDK's query models, providing methods to create and execute complex OLAP or relational queries based on the metadata in the SDK's CWM-based metadata models. The SDK provides two query APIs:
query modelAn object-oriented abstraction layer, or model, upon which to formulate queries on a variety of resources without being tied to a specific protocol or query language, such as MDX or SQL. The query models are the basis of their respective query APIs. Two query models are provided by the SDK:
RDBMSAcronym for relational database management system.
Relational Command ProcessorPart of the SDK's Relational Query API, an interface that makes it easier to use the API by hiding the complexity of the underlying Relational Query Model. With this interface, you can create and manipulate complex relational queries with simple commands.
relational dataData stored in tables, and hence often also referred to as tabular data. Synonymous with tabular data.
relational data provider (RDP)Provides data in relational, or tabular, views and metadata compatible with the Relational Metadata Model.
relational databaseA repository for typically large amounts of information, structured in accordance with the relational model, in tables with columns. A relational database is created and administered by a relational database management system (RDBMS).
relational database management system (RDBMS)A system that allows you to create and administer relational databases. With an RDBMS, you define storage structures for data and mechanisms for its manipulation and retrieval (typically via SQL). An RDBMS must also provide a system for safeguarding in case of events such as system crashes and unauthorized access.
Relational Metadata APIA set of interfaces provided by the BI Java SDK for accessing the metadata of a relational data source. Generated via JMI from the SDK's Relational Metadata Model.
Relational Metadata ModelA model provided by the BI Java SDK that describes data accessible through a relational interface such as JDBC. Based on the CWM Relational Package.
Relational Query APIA set of interfaces provided by the BI Java SDK that let you define queries against a relational data source. The API is generated via JMI from the Relational Query Model, based on metadata provided by the Relational Metadata Model, and includes the simplified Relational Command Processor.
Relational Query ModelAn abstraction layer, or model, in the BI Java SDK designed for formulating relational queries independently of data source-specific query APIs. The model is based on the CWM Expressions package and the CWM-compliant metadata provided by the Relational Metadata Model.
resource adapterAs defined by the JCA specification, a system-level software driver component used to connect to an EIS. The BI Java SDK and UD Connect use resource adapters called BI Java Connectors.
resource adapter archive (RAR)Complete resource adapter modules, which as defined by the JCA specification consist of the required Java classes, documentation, native libraries, and deployment descriptors necessary to distribute a given resource adapter (connector). The BI Java Connectors are distributed in RAR files.
resource adapter moduleA complete resource adapter which, as specified by the JCA, is represented physically by a RAR file.
ResultSet APIA set of interfaces that provide applications created with the BI Java SDK with access to the results of a query. The ResultSet API provides access to a relational result set from a relational data source, and an OLAP result set from an OLAP data source.
rowA set of fields within a table that contains the data for one specific entry in the table. Each row in a given table has the same structure, predefined for a particular table.
SAP QueryA component of SAP's Web Application Server that allows you to create custom reports without any ABAP programming knowledge. The BI SAP Query Connector uses SAP Query to allow applications created with the BI Java SDK to access data from these SAP operational applications. For more information about SAP Query, refer to the SAP Help Portal documentation:
SDKSoftware development kit. As applied throughout this documentation, the term "SDK" refers specifically to the BI Java SDK, unless otherwise specified.
Service Provider Interface (SPI)Defined by the JCA, a standard interface for integrating the transaction, security, and connection management facilities of an application server with those of a transactional resource manager.
System LandscapeA service of the SAP Enterprise Portal that provides the functionality to persist connection information.
tableA set of rows, also known as a relation. The table is the central object of the relational model.
tabular dataSynonym for relational data.
UD Connect (UDC)Component of SAP BW that, together with the SAP Web AS J2EE server, provides connectivity to virtually all relational and multidimensional data sources. UDC uses the BI Java Connectors as resource adapters for establishing connections to data sources. The data can either be loaded into BW, or accessed directly via a RemoteCube. Read about UD Connect on the SAP Help Portal at:
XML Metadata Interchange (XMI)OMG's XML-based standard for interchanging metadata between UML-based modeling tools and MOF-based metadata repositories in distributed, heterogeneous development environments. The exchange takes place in the form of data streams or files, essentially formally mapping MOF to XML. XMI, together with UML and MOF, forms the core of the OMG's metadata repository architecture and allows developers of distributed systems to share object models and other metadata over the Internet. The SDK supports XMI to interchange and persist metadata objects in a platform independent manner. For more information, see http://www.omg.org/technology/documents/formal/xmi.htm.
XML for Analysis (XMLA)An XML-messaging-based protocol specified by Microsoft for exchanging analytical data between client applications and servers (for example, OLAP providers) using HTTP and SOAP as a service on the Web. XMLA advances OLE DB concepts such as schema rowsets and MDX by providing standardized universal data access without the need to deploy client components that expose COM interfaces. XML for analysis is not restricted to any particular platform, application, or development language. For more information, see http://www.xmla.org/.
Copyright © 2004-2005 by SAP
AG. All Rights Reserved. |