s apb w universal data in te

7/28/2019 s Apb w Universal Data in Te

http://slidepdf.com/reader/full/s-apb-w-universal-data-in-te 1/31

SAP NetWeaver Know-HowCall

Oliver J. Mayer SAP NetWeaver RIG - BI

SAP BW -

Universal DataIntegration



© SAP AG 2004, Universal Data Integration / Oliver J. Mayer / 2

Learning Objectives

As a result of this lecture, you will

be able to:

n Explain the benefits that SAP Business Information

Warehouse (BW) derives from the J2EE components that are

integrated into SAP Web Application Server 6.40

n Understand the architecture of SAP BW’s integration with the

SAP Web Application Server Java Environment

n Describe which protocols and standards are supported by the

BI Java Connectors

n Scenarios: Data migration and integration in heterogeneous

system landscapes using UD Connect

n Scenarios: Explain how the BI Java SDK complements and

extends SAP BW’s existing open analysis interfaces




Agenda

Overview

SAP BW 3.5 UD Connect

BI Java SDK

Q&A




Universal Data Integration

Significant customer demand for more integration with SAP BW

q Scenarios

n BI Staging from a broader range of sources

(DB Connect is restricted to SAP supported DBs, ETL Tools not

available)

n Access to multidimensional and relational DB Systems

n Transient and persistent data scenarios

n Integration of external data into SAP BW queries via direct access

q Challenges

n Technical prerequisites

n How to model in SAP BW

n Mapping aspects

n Master Data treatment

n Performance Issues




BI Java Integration

Key ObjectivesOpenness

n Integration of diverse data sources

n Visualization of SAP BW and non-SAP

BW data via the SAP BW Business

Explorer BI Suite and SAP Enterprise

Portal

Standards Basedn Metadata (Models, Access API):CWM, JMI

n Connectivity: JCA

n Portability and Synergies with other J2EE

standards

Model Driven

n Architecture and Development Process

n Model, Code, Documentation in synch

n Code generation based on JMI templates

SAP NetWeaver™

C o

m p o s i t e A p p l i c a t i o n F r a m e w o r k

PEOPLE INTEGRATION

Multi channel access

Portal Collaboration

INFORMATION INTEGRATION

Bus. Intelligence

Master Data Mgmt

Knowledge Mgmt

PROCESS INTEGRATION

Integration

Broker

Business

Process Mgmt

APPLICATION PLATFORM

J2EE

DB and OS Abstraction

ABAP

L i f e C y cl eM gm t




SAP BW Architecture with Release 3.5

UDI

Implementation






n BI Java Connectors to provide access to any data (relational, OLAP)

n Based on industry standards for interoperability (JDBC, XMLA, ODBO)

n Universal Data Connect to integrate data into the BW platform

n BI Java SDK for custom built Java Applications

SAP

OLTP

nonSAP

SAP

Query

XMLA

JDBC

ODBO

BI

Java

SDK

OL AP

Custom-builtApplications

S AP

E n t er pr i s eP o

r t al

UniversalData

Connect

1. BI Java ConnectorsJDBC, XMLA, ODBO, SAP Query

2. Universal Data ConnectSAP BW Integration

3. BI Java SDKJava API, Examples, Documentation

BE x

BW S t a gi n gSAP

BW




Overview - BI Java Connectors

Connectors for diverse data sourcesn Relational

§ BI JDBC Connector

§ JDBC is the standard Java API for RDBMS

§ Connectivity to over 200 JDBC drivers, supporting data sources such as:Teradata, Oracle, MS SQL Server, MS Access, DB2, Excel, text files (CSV)

§ BI SAP Query Connector

§ Connectivity to SAP operational applications§ Ad-Hoc and Operational Reporting for mySAP components

n OLAP

§ BI ODBO Connector

§ Established industry-standard OLAP API for the Windows platform

§ Connectivity to MS Analysis Services, SAS

§ BI XMLA Connector

§ Web services-based, platform independent access to OLAP providers

§ Connectivity to MS Analysis Services, Hyperion, MicroStrategy, BW 3.x,Business Objects




Agenda

Overview


BI Java SDK

Q&A







n Based on industry standards for interoperability (JDBC, XMLA, ODBO)

n Universal Data Connect to integrate data into the BW platform


SAP

OLTP

nonSAP

SAP

Query

XMLA

JDBC

ODBO

BI

Java

SDK

OL AP


S AP


r t al

UniversalData

Connect




BE x

BW S t a gi n gSAP

BW




BAPIDB

ConnectFile

http/

SOAP

B

SAP BW DataSource

SAP XIC D

HF G

Service

API

A

SAP NetWeaver - A Broader View of Data Acquisition

Universal Data Connector

n Integrates data for analysis and enables a complete business view

n Persistent and transient data handling possible

n Java based Adaptors for different drivers, providers, and protocols available

§ JDBC

§ OLE DB for OLAP

§ XML for Analysis

§ SAP Query

UD

Connect

E




UDC - Architecture

RDBMSData

Storage

W

e b A S 6 . 4 0

B W 3 . 5

FM

InfoSource

Generic DataSource

of type Function Module

JDBC Driver

J2EE Server 6.40

Rules

JDBC Connector

Java UD Connect Interface

XMLA Connector ODBO Connector SAP Query Connector

HTTP-URL, port ODBO Prov. SAP RFC, API, BAPI

MS AS, SAS, Hyperion R/3

BI Java Integration ...

UDC DataSource

ABAP UD Connect Interface




UDC - Integration Scenario with JDBC – Front End

RDBMS

W

e b A S 6 . 4 0

B W 3 . 5

FM

InfoSource

Rules

JDBC Connector

Java UDC Interface

BI Java Integration

UDC DataSource

ABAP UDC Interface

D B

JDBC Driver

J2EE Server 6.40

QueryRemoteCube

Web

Application

SAP Enterprise Portal 6.0

• Query definition based on Remote

Cube Handling

• Remote Cube can be part of a

MultiProvider

• Transactional data is NOT

persistently stored in SAP BW

F i l e

S y s t .

Supporting JDBC




RDBMS

W

e b A S 6 . 4 0

B W 3 . 5

FM

InfoSource

Rules

JDBC Connector

Java UDC Interface

BI Java Integration

UDC DataSource

ABAP UDC Interface

D B

JDBC Driver

J2EE Server 6.40

QueryRemoteCube

Web

Application


F i l e

S y s t .

Supporting JDBC

UDC - Integration Scenario with JDBC – Back End

Connect information for a specific

source system:

• URL, IP-Address

• DB User, Authorizations

• DB Schema

• Installation of drivers (JDBC,

ODBO) or XMLA components

• Provided by the vendor

• Licensed by the customer




RDBMS

W A S 6 . 4 0

B W 3 . 5

FM

InfoSource

Rules

JDBC Connector

Java UDC Interface

BI Java Integration

UDC DataSource

ABAP UDC Interface

D B

JDBC Driver

J2EE Server 6.40

QueryRemoteCube

Web

Application


F i l e

S y s t .

Supporting JDBC

• Modeling Steps in SAP BW

• Selection of table or view fromremote DB

• Typesave Field Mapping

• Transformation in both directions

is possible

UDC - Integration Scenario with JDBC




RDBMS

W A S 6 . 4 0

B W 3 . 5

FM

InfoSource

Rules

JDBC Connector

Java UDC Interface

BI Java Integration

UDC DataSource

ABAP UDC Interface

D B

JDBC Driver

J2EE Server 6.40

F i l e

S y s t .

Supporting JDBC

UDC – Master Data Handling

• Master data can be extracted and

persistently stored in SAP BW viathe same channel

• This is recommended for

performance reasons and

navigational aspects in the Query

Master Data

InfoPackage




UDC Details - InfoSource Maintenance

Create BW DataSource with UDConnect

Order No.

Patner No.

RC Date

Commission Da

Shipping Date

Lineitem No.




UD Connect vs. DB Connect – Which way to go?

BAPI Filehttp/

SOAP

A

SAP BW DataSource

SAP XIB C

GE F

Rules of thumb

n Use DB Connect for BI Staging whenever possible

n If DB Connect cannot be used for BI Staging there are two options:

n Ascential or other ETL Tools

nUDI/UDC Implementation

n DB Connect restrictions (i.e. table and fieldnames have to be in capital letters) do not

apply to UD Connect

nFor Direct Access needs, DB Connect cannot be used, but there are other differentoptions

§ UDI/UDC provides connectivity to nearly any platform/source

§ within the SAP World SAP RemoteCubes can give access to SAP data as well

Service

API

DB

Connect

UD

Connect




Agenda

Overview


BI Java SDK

Q&A







n Based on industry standards for interoperability (JDBC, XMLA, ODBO)n Universal Data Connect to integrate data into the BW platform


SAPOLTP

nonSAP

SAP

Query

XMLA

JDBC

ODBO

BI

JavaSDK

OL AP


S AP


r t al

UniversalData

Connect




BE x

BW S t a gi n gSAP

BW




BI Java SDK - Feature Summary

Scenarios

n Java developers use the SDK to create custom BI applications anddeploy them onto SAP NetWeaver’s J2EE server

n For accessing SAP BW or non-SAP data

n Access to diverse sources (SAP or non-SAP) supported by the BI JavaConnectors (JDBC, XMLA, OLE DB for OLAP, SAP Query)

Featuresn Easy to use and learn

u Simplified command interfaces hide the complexity of underlying low-leveldata access protocols (MDX, SQL, HTTP…)

u Leverages resources, skills, and infrastructure customers already have

u Provides complete documentation on an API level (Javadocs), tutorials, andexamples

n Based on open and accepted standards for interoperability

u Common access APIs (JMI)

u Common meta models (CWM)

u Connection management (JCA)




BI Java SDK - API Architecture (I)

BI Java SDK’s API components diagram

BI Java SDKBI Java SDK

OLAP APIs

OLAP Metadata API OLAP Query API

Relational APIs

Relational Metadata API Relational Query API

R e s u

l t S e t AP I

C onn e c t i onM an a g em en t

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

BI XMLA Connector BI XMLA Connector

OLAP

BI JDBC Connector BI JDBC Connector

BI ODBO Connector BI ODBO Connector

BI SAPQ Connector BI SAPQ Connector

Relational OLAP Relational




BI Java SDK - Architecture (II)

W e b A S 6 . 4 0

J2EE Server 6.40

Java Components

BW XMLA Service

D B

BW

BI XMLA Connector

HTTP-URL, port

E P 6 . 0 Web Application

Enterprise Portal

A n y O S

J2SE

J2SE

Application

BW XMLA Service

D B

BW

BI XMLA Connector

HTTP-URL, port

Managed Application Scenario Unmanaged Application Scenario




BI Java SDK – Usage Scenario

n Custom Portal Application that pulls data from a SAP BW query

and applies some complex calculations that could not have beenmodeled with SAP BW standard means

n Integration with an existing Java application

n Benefits

n Shorter implementation time, less cost

n Leverage expert knowledge

n Extract data for further manipulation




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.

Standard

Metadata Integration

ü Common Metamodel (CWM)

You need a common understanding of metadata to be able toexchange 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 metadataobjects in a platform-independent manner.

Allows for use of JMI

MOF is what allows CWM to use JMI. CWM is a MOF-

compliant metamodel.

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.

Importance




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




Availability

BI Java SDK

n Download from the SAPDeveloper Network (SDN);

View full documentation set

on the SAP Developer

Network

n Zip file on the NetWeaver '04

Developer's Studio CD:.../eclipse/tools/bi_sdk/ bi_sdk.zip

n Integrated into the

Developer's Studio

environment

BI Java Connectors

n Deployed to the Web

Application Server 640 by

default with BW 3.5




Agenda

Overview


BI Java SDK

Q&A




Q & A

Question and Answer Session




n 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.

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

software vendors.

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

Microsoft Corporation.

n 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 Server TM are trademarks of IBM Corporation in USA and/or other countries.

n ORACLE® is a registered trademark of ORACLE Corporation.

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

n Citrix®, the Citrix logo, ICA®, Program Neighborhood®, MetaFrame®, WinFrame®, VideoFrame®, MultiWin® and

other Citrix product names referenced herein are trademarks of Citrix Systems, Inc.

n HTML, DHTML, XML, XHTML are trademarks or registered trademarks of W3C®, World Wide Web Consortium,

Massachusetts Institute of Technology.

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

n JAVASCRIPT® is a registered trademark of Sun Microsystems, Inc., used under license for technology invented

and implemented by Netscape.

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

n SAP, R/3, mySAP, mySAP.com, xApps, xApp 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.

Copyright 2004 SAP AG. All Rights Reserved

s apb w universal data in te

Documents