|
This page introduces the BI Java Connectors, and includes a brief
overview of each of the connectors and their supported systems,
in the following sections:
Note: The BI Java Connectors are distributed separately
from the BI Java SDK, deployed by default together with the Web
Application Server.
What are BI Java Connectors?
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. The BI Java Connectors
may be deployed onto SAP NetWeaver '04 - Web Application Server
version 6.40.
The BI Java SDK contains the JAR files you need to develop applications
using any of the BI Java Connectors and to use them in an unmanaged
scenario, but to use your application with a data source in the
managed environment of the J2EE server, you need to deploy the appropriate
BI Java Connector. The connectors themselves are distributed separately.
The BI Java Connectors are packaged in resource adapter archives,
or RAR files. Each RAR file includes class libraries and dependencies,
a deployment descriptor, and documentation in the form of a howto.html
file. General system guidelines are listed below in the Connector
Overview section, but always refer to the howto.html
file inside of each RAR file for additional system or configuration
information specific to that particular connector. The howto.html
file also contains instructions on how to deploy the connector into
the Web Application Server.
For your reference, we've provided links to each connector's howto.html
file in the table below.
Connector Overview
Four BI Java Connectors are available, listed below with the name
of the resource adapter archive in which they are deployed:
- BI JDBC Connector :
bi_sdk_jdbc.rar
- BI ODBO Connector :
bi_sdk_odbo.rar
- BI SAP Query Connector :
bi_sdk_sapq.rar
- BI XMLA Connector :
bi_sdk_xmla.rar
The following table provides an overview of each connector and
a link to its howto.html file:
| Connector |
Access to |
Technology
based on |
System requirements |
BI JDBC Connector
howto.html |
Relational data sources:
over 170 JDBC drivers
Examples:
Teradata, Oracle, Microsoft SQL Server, Microsoft Access, DB2,
Microsoft Excel, text files such as CSV |
Sun's JDBC (Java Database Connectivity)
-- the standard Java API for Relational Database Management
Systems (RDBMS). |
JDBC driver |
BI ODBO Connector
howto.html |
OLAP data sources:
OLE DB for OLAP-compliant data sources
Examples:
Microsoft Analysis Services, SAS, Microsoft PivotTable Services |
Microsoft's OLE DB for OLAP --
the established industry-standard OLAP API for the Windows platform.
|
Microsoft Windows 2000 / NT / XP |
BI SAP Query Connector
howto.html |
SAP operational
applications
Examples:
data in transactional systems such as R/3, Ad-Hoc, and Operational
Reporting |
SAP Query -- a component
of SAP's Web Application Server that allows you to create custom
reports without any ABAP programming knowledge. |
SAP JCo |
BI XMLA Connector
howto.html
|
OLAP data
sources
Examples:
MS Analysis Services, Hyperion, MicroStrategy, and BW 3.x |
Microsoft's XMLA (XML
for Analysis) -- Web services-based, platform-independent access
to OLAP providers. Exchanges analytical data between a client
application and a data provider working over the Web, using
a SOAP-based XML communication API. |
none |
For Additional Information
- For connector configuration and deployment information, refer
to the howto.html file inside the resource adapter
archive (RAR file)
- For the SDK's connection architecture API documentation, refer
to the Connection
Interfaces Javadoc package
- For more on the SDK's connection architecture, see the Developer's
Guide.
- For BI Java Connector licensing information, contact your Global
Account Manager
Copyright © 2004-2005 by SAP
AG. All Rights Reserved.
SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, and other
SAP products and services mentioned herein as well as their respective
logos are trademarks or registered trademarks of SAP AG in Germany
and in several other countries all over the world. All other product
and service names mentioned are the trademarks of their respective
companies. Data contained in this document serves informational
purposes only. National product specifications may vary.
These materials are subject to change without notice. These materials
are provided by SAP AG and its affiliated companies ("SAP Group")
for informational purposes only, without representation or warranty
of any kind, and SAP Group shall not be liable for errors or omissions
with respect to the materials. The only warranties for SAP Group
products and services are those that are set forth in the express
warranty statements accompanying such products and services, if
any. Nothing herein should be construed as constituting an additional
warranty.
|