universal data access via sap bw java integration ... · via sap bw java integration functionality...

SAP TechEd ‘03 Las Vegas

© 2003 SAP AG, Germany BW204, Eric Schemer/Rainer Uhle 1

Universal Data Access via SAP BW Java Integration Functionality

Arnd Graf, Dev. Architect BI Analysis PlatformRainer Uhle, Product Management BI SAP AG

SAP AG 2003, TechED Basel 2003, BW204_EMEA; Arnd Graf/Rainer Uhle, 2

Learning Objectives

As a result of this lecture, you will be able to:

Explain the benefits that SAP Business Information Warehouse (BW) derives from the J2EE components that are integrated into SAP Web Application Server 6.40 Understand the architecture of SAP BW’s integration with the SAP Web Application Server Java EnvironmentDescribe which protocols and standards are supported by the BI Java Connectors Describe the concept of data migration and integration in heterogeneous system landscapes using the Universal Data ConnectExplain how the BI Java SDK complements and extends SAP BW’s existing open analysis interfaces




Agenda

OverviewMigration and Integration of diverse data sourcesEnabling J2EE applications to access BW dataSAP NetWeaver & BI Java Connectors

SAP BW 3.5 Universal Data Connect (UDC)ArchitectureApplication ScenariosUDC Details

BI Java SDK for Custom ApplicationsArchitectureApplication ScenariosSDK Details

Outlook

Summary


Agenda




Outlook

Summary




Overview – Diverse Data Sources Quantitatively

Flat files, 81% EAI/Messaging, 12%

XML, 15%

Web, 15%

Replication or CDC, 15%

Packaged applications,

39%

Relational databases, 89%

Mainframe/ legacy, 65%

Excel, 12%

Flat files, 23%

EAI, 5%

XML, 29%

External, 14%

Other, 30%

Packaged applications,

18%

Relational, 34%

Mainframe, 12%

Source: The Data Warehousing Institute (TDWI); based on 756 respondents.

Source: TDWI-Giga Information Group Quarterly Technology Survey, 2/2003, 150 respondents.

Data sources now Data sources in 18 months


SAP NetWeaver - A Broader View of Data Acquisition

Universal Data ConnectIntegrates data for analysis and enables a complete business viewPersistent and transient data handling possibleJava based connectors for different drivers, providers, and protocols available

JDBCOLE DB for OLAPXML for Analysis

BAPI DBConnect File http/

SOAP

A

SAP BW

SAP XIB C

GE F

UDC

D




OLE DB for OLAPbased on COM as protocoldriver installation on clientsWindows platform onlyMDX as query language available since BW 1.2B

OLAP BAPIsBusiness Application Programming interfacebased on RFC as protocolaccess library available on any SAP platformMDX as query languageavailable since BW 2.0A

XML for Analysisbased on XML as exchange formatbased on HTTP/SOAP as protocolany platformMDX as query languageavailable since BW 3.0A

Overview – Enabling Applications to Access BW

BI Java SDK


Overview – Java Connectivity in SAP NetWeaver

Industry standard Connection Architecture (JCA)

Pluggability for 3rd party connectorsUniform connection management, monitoring and foundation for all connectorsPortability and Synergies with other J2EE standards

BI Java Connectors fully leverage the SAP J2EE connection framework and provide integration with diverse data sourcesVisualization of SAP BW and non-SAP BW data via the SAP BW Business Explorer BI Suite and SAP Enterprise Portal

…

SAP NetWeaver

INFORMATION INTEGRATION

Master Data Management

Bus. Intelligence Knowledge Mgmt

Com

posi

te A

pplic

atio

n Fr

amew

ork

PEOPLE INTEGRATION

Multi channel access

Portal Collaboration

APPLICATION PLATFORM

J2EE

DB and OS Abstraction

ABAP

Life Cycle M

anagement

PROCESS INTEGRATION

IntegrationBroker

Business ProcessManagement




Overview - BI Java Connectors

Connectors for diverse data sourcesUsed together with the Universal Data Connector or the BI Java SDK to extract and consume BW or non-BW data.

RelationalBI JDBC Connector

JDBC is the standard Java API for RDBMSConnectivity to over 170 JDBC drivers, supporting data sources such as: Teradata, Oracle, MS SQL Server, MS Access, DB2, Excel, text files (CSV) …

BI SAP Query ConnectorConnectivity to SAP operational applications (4.x)R/3, Ad-Hoc, Operational Reporting

OLAPBI ODBO Connector

Established industry-standard OLAP API for the Windows platformConnectivity to MS Analysis Services, SAS, MS PTS

BI XMLA ConnectorWeb services-based, platform independent access to OLAP providersConnectivity to MS Analysis Services, Hyperion, MicroStrategy, MIS, BW 3.x


Overview – Java Industry Momentum

ADABAS, Clipper, DB2,dBase, FoxPro, IBM AS/400,

Informix, Ingres,InterBase, LDAP,

MS Access, News Server,OS/390, Paradox,Redbrick, SAS,

Sybase, Teradata,Text (CSV, Tab separated etc.),

TinySQL, VSAM, XML.

177 JDBC

Drivers

available




Agenda




Outlook

Summary


UDC - Architecture

RDBMSDB

WAS

6.4

0B

W 3

.5

FM

InfoSourceGeneric DataSourcewith

JDBC Driver

J2EE Server 6.40

Rules

JDBC Connector

Universal Data Connect

XMLA Connector ODBO Connector

http-URL, port ODBO Prov.

MS AS, SAS, Hyperion

BI Java Integration ...




UDC - Integration Scenario with JDBC

Transient data. No data physically stored in SAP BW.DB access via JDBC driver (from DB provider)Mapping via Transfer Rules in BW, Inversion of Transfer RulesRemoteCube

DB

WAS

6.4

0B

W 3

.5

FM

QueryRemoteCube


JDBC Driver

J2EE Server 6.40

Rules

Web ApplicationEnterprise Portal 6.0

BI Java Integration ...Fi

leSy

st.Supporting JDBC

JDBC Connector

Universal DataConnect


UDC - Extraction Scenario with JDBC

Persistent dataDB access via JDBC driver (from DB provider)Mapping via Transfer Rules in BW, no Inversion of Transfer Rules requiredData load via InfoPackage

DB

WAS

6.4

0B

W 3

.5

FM

EDW LayerInfoPackage


JDBC Driver

J2EE Server 6.40

Rules

Data Mart Layer

File

Syst

.Supporting JDBC

JDBC Connector

Universal DataConnector

BI Java Integration ...




UDC Details – Connector Deployment and Connection Configuration

JNDI: Java Naming Directory Interface


UDC Details - InfoSource Maintenance

Create BW DataSource with UDConnect

Order No.

Patner No.

RC Date

Commission Da

Shipping Date

Lineitem No.




UDC Details – DataSource Wizard

BW InfoSource

Connect Info

Man. Mapping

Autom. Mapping

Fields of tableITEM

in ext. DB

Generate DS


UDC – Feature Summary

ScenariosConnection of diverse data source systems to SAP BW

E.g. Extraction/Remote Access from a relational database via open interface JDBCE.g. Extraction/Remote Access from OLAP source using OLE DB for OLAP and extraction from an OLAP source using XML for Analysis

FeaturesLeveraging SAP WebAS J2EE Connectivity for SAP BWEnhancing SAP BW Openness: Connectivity to virtually all data sources

UDConnect: Universal Data ConnectExtraction to SAP BW and Remote Cube Access via UDConnect

Uses the BI Java ConnectorsJDBC (170+ drivers available for: Adabas, Clipper, DB2, FoxPro, Informix, Ingres, MS Access, Sybase, SAS, Teradata, XML, CSV text files, … ) - see http://java.sun.com for more informationOLE DB for OLAPXML for AnalysisSAP QueryThe set of connectors will be extended in future




Agenda




Outlook

Summary


BI Java SDKBI Java SDK

OLAP APIs

OLAP Metadata API OLAP Query API

Relational APIs

Relational Metadata API Relational Query API

ResultSet A

PI

Connection M

anagement

Logging and Tracing

Documentation (including Javadocs, Developer’s Guide); Examples

BI XMLA ConnectorBI XMLA Connector

OLAP

BI JDBC ConnectorBI JDBC Connector

Relational

BI ODBO ConnectorBI ODBO Connector

OLAP

BI SAPQ ConnectorBI SAPQ Connector

Relational

BI Java SDK - Architecture




BI Java SDK – ScenariosW

AS 6

.40

EP 6

.0

J2EE Server 6.40Java Components

BW XMLA Service

DB

BW

BI XMLA Connector

http-URL, port

Web ApplicationEnterprise Portal

Any

OS

J2SEJ2SE Application

BW XMLA Service

DB

BW

BI XMLA Connector

http-URL, port

Managed Application Scenario Unmanaged Application Scenario


BI Java SDK – Supported Open Standards

CWM (Common Warehouse Metamodel)Describes the exchange of shared, global metadata.Capable of modeling a wide spectrum of OLAP and relational providers.

JMI (Java Metadata Interface)Provides a common Java programming model for accessing metadata.

XMI (XML Metadata Interchange)Standard for exchanging metadata between UML-based modeling tools and MOF-based metadata repositories.

MOF (Meta Object Facility)Standard for the specification of interoperable metamodels, integrated in XMI. MOF can also refer to any metadata service which abides by the MOF specifications.

JCA (J2EE Connector Architecture)Standard architecture for integration of J2EE servers with EISs. The architecture defines a set of contracts that a resource adapter has to support to plug in to an application server.

Connection ManagementJCA provides an API for connecting to heterogeneous data sources in a consistent way. Supports pluggability of connectors into multiple J2EE engines. The SDK’s connectors are JCA-compliant.

Why’s this important?

Metadata IntegrationCommon Metamodel (CWM)

You need a common understanding of metadata to be able to exchange it between different, heterogeneous systems. The SDK uses CWM to represent metadata.

Common Access API (JMI)Provides a common access API. The SDK uses JMI mapping to render its metadata models into Java APIs.

Common Exchange Format (XMI)The SDK supports XMI to exchange and persist metadata objects in a platform-independent manner.




BI Java SDK - Developer’s Documentation Set

Features:

Complete set of Javadocs

Developer’s Guide

Code Examples

Integrated CWM Documentation

Navigable UML Diagrams

Features:

Complete set of Javadocs

Developer’s Guide

Code Examples

Integrated CWM Documentation

Navigable UML Diagrams


BI Java SDK – Feature Summary

ScenariosJava developers will use the SDK to create custom BI applications and deploy them on the SAP NetWeaver’s J2EE serverFor accessing SAP (BW) or non-SAP data Access to diverse sources (SAP or non-SAP) supported by the BI Java Connectors (JDBC, XMLA, OLE DB for OLAP, SAP Query)

FeaturesEasy to use and learn

Simplified command interfaces hide the complexity of underlying low-level data access protocols (MDX, SQL, HTTP, JNI …)Leverages resources, skills, and infrastructure customers already have Provides complete documentation on an API level (Javadocs), tutorials, and examples

Based on open and accepted standards for interoperabilityCommon access APIs (JMI)Common meta models (CWM)Common interchange format (XMI)Connection management (JCA)




Agenda




Outlook

Summary


Outlook – BEx and Portal Integration

BEx Integration (BW 4.0)BEx as an XMLA, ODBO, JDBC consumerAd-hoc reporting on non-SAP OLAP and relational data sourcesData ready for reporting without modeling

Portal Integration (Availability tbd)

Visual tool (GUI Machine) to enable code-free development of portal contentDesigned for content experts and content managersBI Extension for creation of BI content




Summary

SAP NetWeaver supports an industry standard pluggable connector architecture

SAP BW leverages and integrates with this architecture via BI Java Connectors

SAP BI Java Connectors enable integration of diverse data sources based on JDBC, XMLA and OLE DB for OLAP

SAP BI Java SDK, based on BI Java Connectors, enables rapid development of custom Java applications with access to BW


Internet:J2EE Connector Architecture (JCA): http://www.jcp.org/en/jsr/detail?id=16

Java Database Connectivity (JDBC): http://java.sun.com/products/jdbc/

XML for Analysis (XMLA): http://www.xmla.org/

Java Metadata Interface (JMI): http://java.sun.com/products/jmi/

OLE DB for OLAP (ODBO): http://msdn.microsoft.com/library/default.asp?url=/library/en-us/oledb/htm/olprpart3.asp

Related Workshops/Lectures at SAP TechEd 2003BW 253: XML for Analysis; 2-hour hands-on:

Sept. 30, 2003, 4:00 PM - 6:00 PM, H11

Further Information




Q&A

Questions?


Please complete your session evaluation anddrop it in the box on your way out.

Feedback

Thank You !

The SAP TechEd ’03 Basel Team




No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice.

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.

Microsoft®, WINDOWS®, NT®, EXCEL®, Word®, PowerPoint® and SQL Server® are registered trademarks of Microsoft Corporation.

IBM®, DB2®, DB2 Universal Database, OS/2®, Parallel Sysplex®, MVS/ESA, AIX®, S/390®, AS/400®, OS/390®, OS/400®, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere®, Netfinity®, Tivoli®, Informix and Informix® Dynamic ServerTM are trademarks of IBM Corporation in USA and/or other countries.

ORACLE® is a registered trademark of ORACLE Corporation.

UNIX®, X/Open®, OSF/1®, and Motif® are registered trademarks of the Open Group.

Citrix®, the Citrix logo, ICA®, Program Neighborhood®, MetaFrame®, WinFrame®, VideoFrame®, MultiWin® and other Citrix product names referenced herein are trademarks of Citrix Systems, Inc.

HTML, DHTML, XML, XHTML are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology.

JAVA® is a registered trademark of Sun Microsystems, Inc.

JAVASCRIPT® is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape.

MarketSet and Enterprise Buyer are jointly owned trademarks of SAP AG and Commerce One.

SAP, R/3, mySAP, mySAP.com, xApps, xApp and other SAP products and services mentioned herein as well astheir 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.

Copyright 2003 SAP AG. All Rights Reserved


SAP TechEd `03 EMEAOnline

WATCH THE REPLAYS, DOWNLOAD THE SLIDES, AND READ THE TRANSCRIPTS.

www.sap.com/community

universal data access via sap bw java integration ... · via sap bw java integration functionality...

Documents