BI Java Connectors
Purpose
The BI Java Connectors are a group of four JCA (J2EE Connector Architecture)-compliant resource
adapters that implement the BI Java SDK's APIs and allow you to connect the applications you build
with the SDK to heterogeneous data sources. You can also use the BI Java Connectors to make
these data sources available in SAP BI systems via UD Connect, or to create systems in the portal to
use in BEx Web or Visual Composer scenarios.
The following diagram outlines the potential usage scenarios for the BI Java Connectors:
As illustrated, you can use the BI Java Connectors to create systems for use in four different
scenarios. Since the BI Java Connectors are distributed as part of SAP Universal Data Integration
(UDI), these are often referred to as UDI scenarios:
Scenario 1: UD Connect
On the BI platform, you can use UD Connect to make data from systems based on the BI Java
Connectors available in SAP BI. For more information, see Transferring Data with UD Connect.
To configure the BI Java Connectors for this scenario, refer to the following path in the SAP
Customizing Implementation Guide: SAP NetWeaver Business Intelligence UDI Settings
by Purpose UD Connect Settings, and follow the instructions in Configuring the BI Java
Connectors to configure the connector properties.
Scenario 2: BEx Web
You can use data from systems based on the BI Java Connectors in BEx Web Applications. For
more information, see BEx Web and Access to External Data Sources.
To configure the BI Java Connectors for this scenario, refer to the following path in the SAP
Customizing Implementation Guide: SAP NetWeaver Business Intelligence UDI Settings
by Purpose Integration in BEx Web, and see Running the System Landscape Wizard and
Editing Systems to configure the systems on the portal.
Scenario 3: Visual Composer
You can use data from systems based on the BI Java Connectors in Visual Composer, the
portal-based visual modeling application. For more information, see the SAP NetWeaver
Visual Composer Modeler’s Guide.
To configure the BI Java Connectors for this scenario, see the SAP NetWeaver Visual
Composer Installation & Configuration Guide, and see Running the System Landscape
Wizard and Editing Systems to configure the systems on the portal.
Scenario 4: BI Java SDK
You can build custom Java applications based on data in systems created with the BI Java
Connectors. For more information, see BI Java SDK.
To configure the BI Java Connectors for this scenario, see Configuring the BI Java Connectors.
Features
Four BI Java Connectors are available:
1. BI JDBC Connector, for connecting to relational JDBC data sources
2. BI ODBO Connector, for connecting to OLE DB for OLAP-compliant data sources
3. BI SAP Query Connector, for connecting to data from SAP operational applications
4. BI XMLA Connector, for connecting to XMLA-compliant data providers such as SAP BI
Systems
Connector Overview
Connector Access To Technology Based System
On Requirements
BI JDBC Connector Relational data Sun's JDBC (Java JDBC driver for your
sources: over 170 Database data source
JDBC drivers Connectivity) -- the
Examples: standard Java API for
Relational Database
Teradata, Oracle,
Management Systems
Microsoft SQL Server,
(RDBMS)
Microsoft Access,
DB2, Microsoft Excel,
text files such as CSV
BI ODBO Connector OLAP data sources: Microsoft's OLE DB Microsoft Windows
OLE DB for OLAP- for OLAP -- the 2000 / NT / XP
compliant data established industry- or greater
sources standard OLAP API Microsoft Data
Examples: for the Windows Access
platform Components
Microsoft Analysis
Services, SAS, (MDAC) 2.6 or
Microsoft PivotTable greater
Services ODBO driver for
your data
source
BI SAP Query SAP operational SAP Query -- a SAP JCo
Connector applications NetWeaver
Examples: component that allows
you to create custom
Data in transactional
reports without any
systems such as Ad-
ABAP programming
Hoc, and Operational
knowledge
Reporting
BI XMLA Connector XMLA-compliant Microsoft's XMLA none
OLAP data sources (XML for Analysis) --
Examples: Web services-based,
MS Analysis Services, platform-independent
Hyperion, access to OLAP
MicroStrategy, and providers. Exchanges
SAP BW 3.x analytical data
between a client
application and a data
provider working over
the Web, using a
SOAP-based XML
communication API.
See also:
To configure a BI Java Connector on the server using the Visual Administrator, see Configuring the
BI Java Connectors.
To create a system on the portal using a BI Java Connector, see Creating Systems.
For more information about the J2EE Connector Architecture (JCA), see
[Link]
For information about the BI Java SDK and its connection architecture, refer to the [Link] file
inside of the SDK distribution package
Read about the BI Java SDK