BI XI Integration

Know-How Network: SAP BW - SAP XI Integration
Agenda
SAP NetWeaver SAP XI Data Load into SAP BW Distribution of BW Data to other systems using BWs Open Hub and XI
SAP AG 2004, SAP Labs, LLC 2004; Know-How Network: BW XI Integration / 2
Agenda
Integration on Several Levels, is the Key Challenge

Document Mgmt Call Center Market Analysis
Business Drivers
n Extended Value NetWork n Increased Market Dynamics
Integration costs are high

SCM
n Lots of heterogeneous systems n Long integration projects n IT environments become increasingly rigid
ERP
Pressure on IT increases
Trading e-Sales
n Must leverage existing investments n Must support new business processes quicker n Must reduce total cost of ownership (TCO)
Technical systems
E-Procurement PLM
How to Address the Integration Challenge

Document Mgmt Call Center Market Analysis
Reduce complexity
n Minimize the number of connections through hubs n Use only 1 platform to integrate all people, information, and systems
SCM
Reduce custom integration

ERP
n Deliver .NET and J2EE interoperability n Deliver adaptors for ISV products n Deliver products, not projects!
Trading
e-Sales
Increase company performance

Technical systems E-Procurement PLM
n Increase ease of use, scalability and adaptability n Increase business process flexibility by using an Enterprise Services Architecture
SAP NetWeaver
The comprehensive integration and application platform for lower TCO
SAP NetWeaver
People Integration
Multi-Channel Access Composite Application Framework Portal Collaboration Life Cycle Management
Unifies and aligns people, information and business processes

n Integrates across technologies and organizational boundaries n A safe choice with full .NET and J2EE interoperability
Information Integration
Business Intelligence Knowledge Management
Master Data Management
The business foundation for SAP and partners

n Powers business-ready solutions that reduce custom integration n Its Enterprise Services Architecture increases business process flexibility
Process Integration
Integration Broker Business Process Management
Application Platform
J2EE ABAP
DB and OS Abstraction DB and OS Abstraction
.NET
WebSphere
SAP NetWeaver - Integration Between Layers

Focus of this discussion
SAP NetWeaver
People Integration
Multi-Channel Access Composite Application Framework Portal Collaboration Life Cycle Management
Process integration solution extend the reach of information integration solution
Information Integration
Business Intelligence Knowledge Management
n Real time, near real time data updates possible n Pathway for bringing non-SAP data in BI for analysis: integrated, global view of the business n Distribution of data from BI to downstream systems: enable Enterprise Data Warehousing potential & maximize value of data
Master Data Management
Process Integration
Integration Broker Business Process Management
Application Platform
J2EE ABAP
DB and OS Abstraction DB and OS Abstraction
.NET
WebSphere
SAP Business Intelligence
Open Interface a. Web Services
Sources
Data Warehousing
Access
BI Platform
BI Suite
Data Presentation
Data Acquisition
User
SAP Business Intelligence integrates all your corporate information so you can turn information into insight, insight into action, and action into improved business operations.
SAP BI Architecture
SAP XI: Strategic Process & Integration Management

Enterprise Resource Planning Inter-/Intra-Enterprise Co-operation Collaborative Business
Database Integration Integration by single centralized data model
Direct Connections Integration challenge quadratically growing complexity
Integration Engine & Bus Infrastructure Shared central knowledge, Small number of peer-to-peer connections
Overview Exchange Infrastructure
Shared Collaboration Knowledge

Design Configuration
Execute Collaborative Business Processes

3rd Party and Messaging Systems
Runtime
SAP Systems
Integration Server Integration Server Integration Integration Repository Repository Integration Integration Directory Directory
Integration Engine Business Process Engine Additional Integration Services
Marketplaces SOAP Plain HTTP
System Landscape Directory System Landscape Directory
Runtime Workbench
Partner Eco-System (additional 3rd Party Adapters and Industry Standards)
Agenda
General Scenario: XI Data Load into BW

Extended Service Infrastructure
Analysts, Knowledge Workers Info Consumers
Non-SAP system A
Non-SAP system B BW
n Persistence n Presentation n Analytics
Non-SAP system C
Non-SAP system D
XI
n Open Interfaces n Routing & Monitoring n Transformation
BW: Extraction, Transformation and Loading

n Open for any source n Flexible set of ETL capabilities n Integration to mySAP.com on application level n Open to third-party tools n Support of open standards
XI Adapter Overview & Relevant Architecture
BW myself DataSource RFC Function Module Push Request (Pull)
Delta Queue
XI Proxy Framework Proxy
RFC Framework
ICF Web Service SOAP/RFC
Status Management
tRFC XI ProxyAdapter RFC-Adapter 3rd Party Application 3rd Party Application
SOAP-Adapter
XI Integration Server
*Non-SAP systems
Adapters hosted in the XI Adapter Engine

The Adapter Engine hosts a set of adapters:
n ABAP Proxy Framework n SAP Adapters
u File / FTP u JDBC (Database) u JMS (MQSeries, SonicMQ, ) u RFC u SOAP u SMTP u SAP BC (header extension for support of Quality of Service) u SAP Marketplace Adapter u RosettaNet (RNIF 2.0) Adapter u CDIX (RNIF 1.1) Adapter
n 3rd Party Adapters

u iWay: UCCnet, more to come u Optional: Adapters developed by partners, certificated by SAP
BW-XI-Integration: Possible Quality of Service Levels

n XI categories of Quality of Service
u BE
(Best Effort): The message is sent synchronously; this means that the sender system waits for a response before it continues processing. Messages are not persisted by the Integration Engine in synchronous message processing. Once a message has been processed in the target system it performs an implicit database commit. No transactional security can be guaranteed. Only one receiver system can be configured. (Exactly Once): The message is sent asynchronously in this case; this means that the sender system does not wait for a response before continuing processing. The Integration Engine guarantees that the message is sent and processed exactly once. (Exactly Once In Order): In addition to Exactly Once, messages with the same queue names (supplied by the application) are delivered in the same sequence that they were sent from the sender system. Message processing is asynchronous in this case.
u EO
u EOIO
Data Load scenarios via Push in BW

n In all Push Scenarios the data is transferred into BW via a generated RFC-enabled function module n Based on that there are the following implementations:
u SOAP-DataSource u Web
(XML-DataSource)
Service u BW-XI-Integration
n BW requirements concerning Quality of Service

consists of After Images (AIM) only: IO (In Order) has to be supported from the source of data up to the BW Inbound Layer; otherwise the wrong Image could be used for update in the data target! u Data contains New Images, Before Images, After Images, Reverse Images (ABR): EO (Exactly Once) has to be supported; otherwise multiple operations would create wrong values (in case that deletions are processed before insertions data targets could have inconsistent states. However, this is not considered to be critical, as this will be fixed with the next load)
u Data
n Conclusion
u EOIO
(Exactly Once In Order) is required to enable the delta load in the most flexible and robust manner
BW-XI-Integration: Adapters & QoS

n RFC-Adapter
u asynchronous:
EO, but not IO (tRFC) u synchronous, BE: No transactional security possible; (Drawback: only one receiver system)
u Result:
Not recommended, as correct processing of delta loads with After Images is not possible; practical however for mass load scenarios with strictly separated updates Guaranteed Delivery In Order, as the serialization on the queue is maintained (stops until delivery is confirmed); in error cases data has to be transferred repeatedly => multiple deliveries possible Not recommended, as EOIO cannot be achieved; extensive configuration effort; However processing of After Images possible asynchronous: EOIO, data is transferred from queue on Integration Engine to queue in application system Result: Recommended without restriction; standard adapter of XI with the highest flexibility concerning error handling
n SOAP-Adapter
u asynchronous:
u Result:
n Proxy
u
XI Adapters and XI data load How-to Architecture

4. BW 3.
RFC Function Module Push myself DataSource Request (Pull)
Delta Queue
2.
XI Proxy Framework Proxy RFC Framework ICF Web Service SOAP/RFC
Status Management
tRFC
XI
ProxyAdapter RFC-Adapter SOAP-Adapter 3rd Party Application 3rd Party Application
XI Integration Server
*Non-SAP systems
1.
XI Data Load: Components of the Technical Solution
Partner Systems
d if
SAP XI HTTP inbound Adapter Delta Queue Interface ABAP Adapter
SAP BW
Business Explorer
fer t en uc s tr ra In f s re tu
ABAP Proxy
BW Staging: InfoCubes, ODS
Delta Queue
WAN WAN
Mapping
Routing
Architecture: data flow for XI data load into BW
BW
InfoProviders
ABAP Adapter Routing
XI
InfoSource
SAP XI
Mapping HTTP inbound Adapter
push XML data
BW DataSource
Delta extraction / load ABAP proxy & ABAP proxy & RFC function RFC function module module
Non-SAP
Delta queue
Data recieved into XI from non-SAP applications

Agenda
General Scenario: BW Open Hub push via XI

Extended Service Infrastructure
BW / Business Planning
n Persistence n Information Delivery n Central Monitoring
XI
n Message Routing n Interfacing n Processing
Non-SAP system A
Non-SAP system B
The Corporate Information Factory Directly supported components of SAP and SAP BW
DSS Applications
Sources lmySAP lOthers

ETL Changed Data Staging Area
Departmental Data Marts

Acctg Finance Marketing Sales
BW
ERP ERP ERP CRM
APO SEM Others
eComm.
EDW
Global ODS local ODS
Oper. Mart Granularity Manager cross media Storage mgr
Bus. Int.
ERP Corporate Applications
Exploration warehouse/ data mining
BW NLS
Near line Storage
E-Analytics
Dialogue Manager Cookie Cognition
Session Analysis
Web Logs
Internet
Preformatted dialogues
Source: Bill Inmon
The Corporate Information Factory SAP BW Open Hub Service

DSS Applications
Open Hub Service
Departmental Data Marts

Acctg Finance Marketing Sales ERP ERP ERP CRM ETL
Changed Data
Staging Area
eComm.
EDW
Global ODS local ODS
Oper. Mart cross media Storage mgr
Bus. Int.
ERP Corporate Applications
Exploration warehouse/ data mining Granularity Manager
Session Analysis Dialogue Manager Cookie Cognition Preformatted dialogues Web Logs
Near line Storage
Internet
Source: Bill Inmon
Open Hub in the SAP Business Intelligence Architecture
SAP BW architecture: the Open Hub
Open Hub Service Definition and Details

Open Hub Service provides a framework for the scheduled and monitored extraction of consolidated and integrated data from SAP BW to external destinations.
Controlled distribution of consistent data Target: file or DB table Central monitoring Filtering Aggregation Scheduling Full or Delta Mode
(Data + Metadata)
Process Chains
SAP BW Open Hub: Concept Overview 2

Data transfer in Open Hub Service 3.x
Open Hub terminology InfoSpoke: An SAP BW object, where the specific properties are configured for the dataset to be extracted.
SAP BW
InfoCubes
DB Table /BI0/OH.
Push Pull ODS Pull Pull Master Data Flat file .csv
Other Data Marts
Open Hub Service

Push
Any Other Application (xyz, etc)
Open Hub
SAP BWs Open Hub does NOT offer functionality for delivery of the datasets from the BW system (its DB or its app server OS) to a receiver.
n Open Hub BAPIs have been delivered for tasks such as notification of 3rd-party ETL of new dataset staging readiness, for reading the DB table where the Open Hub has staged the data, etc.
Bottom Line: SAP customers working with SAP BWs Open Hub must otherwise utilize 3rd-party ETL solutions, or write scripting solutions, to deliver the staged datasets to their receiving applications. Thus, building these interface are a project solution, with general issues relevant when developing and managing interfaces. The Open Hub push scenario leverages the capabilities of SAP BW Open Hub, process chains and SAP XIs messaging functionality to offer an improved, effective and robust architecture for meeting this integration challenge.
Open Hub XI Push Technical Solution Architecture

Open Hub Service provides a framework for the scheduled and monitored extraction of consolidated and integrated data from SAP BW to external destinations. XI extends the reach of the Open Hub by delivering the datasets to receivers.
SAP XI
Non-SAP systems
ABAP proxy inbound Adapter
JDBC & File Adapters
Custom process type
XI Mapping Routing
Non-SAP systems
(Data + Metadata)
Receiver Systems Examples in Current How to Paper
A. XML doc/ async. send (proxy) D. async msg return (proxy) note: different interface than send for return msg
nc B. asy
. s e nd
ad ap t (J D B C
er)
MS-SQL DB table
C. as
yn c s e nd
SAP BW 3.5
SAP XI 3.0
( f il e
ad a p
t er)
Server
XML file to remote server file system
Sequence: Open Hub push to MS-SQL DB via XI (1)

A. XML doc/ async. send (proxy)
SAP BW 3.5
1. START process chain (e.g. daily job) 2. Open hub staging to flat DB table 3. Custom process type runs (async.), execute ABAP code to read DB table & send data (XML format) via proxy; also sends log id for running process; process then goes into suspend mode (RSPC monitor shows yellow status)
SAP XI 3.0
Remote (non-SAP) MS-SQL DB

A. XML doc/ async. send (proxy) B. async send (JDBC Adapter)
SAP BW 3.5
SAP XI 3.0
4. XML message received via proxy; mapping routes message to receiver 5. XI queues message; async framework sends message to JDBC adapter

A. XML doc/ async. send (proxy) B. async send (JDBC adapter)
SAP BW 3.5
SAP XI 3.0
4. XML message received via proxy; mapping routes message to receiver 5. XI queues message; async framework sends message to JDBC adapter 7. queue for JDBC adapter holds delivery status (note: if delivery fails, queue agent will retry x # of times)
6. JDBC adapter service receives incoming message. Java class within config specifies DB update commands. MS-SQL RDBMS completes insert of dataset into DB table.

A. XML doc/ async. send (proxy) B. async send (JDBC adapter) C. async msg return (proxy)
SAP BW 3.5
note: different interface than send for return msg
SAP XI 3.0
1. START process chain (e.g. daily job) 2. Open hub staging to flat DB table 3. Custom process type runs (async.), execute ABAP code to read DB table & send data (XML format) via proxy; also sends log id for running process; process then goes into suspend mode (RSPC monitor shows yellow status) 4. XML message received via proxy; mapping routes message to receiver 5. XI queues message; async framework sends message to JDBC adapter 7. queue for JDBC adapter holds delivery status (note: if delivery fails, queue agent will retry x # of times) 9. Proxy methods send success msg back to suspended process. Upon success, update process status to green. If no success msg is received in x hours, process timeout changes status to red. END 8. Message carrying successful delivery status routed back to original sender (process chain) via proxy
6. JDBC adapter service receives incoming message. Java class within config specifies DB update commands. MS-SQL RDBMS completes insert of dataset into DB table.
SAP BW Open Hub push possibilities: SAP XI Extended Scenario

p ro PI ( x y) xy (p ro )
u B 1.
pda
te a
c. s yn
BA
Future
mySAP ERP
B 2.
A. XML doc/ async. send (proxy) F. async msg return (proxy) note: different interface than send for return msg
ac
wl k no
m dge
e nt
C1. update async. BAPI (RFC)
Future
C2. async. return msg. (RFC)
D. a
Server
SAP BW 3.5
SAP XI 3.0
E.
syn
SAP R/3 4.x

c. u pda te (JD BC
as
ad a pte
yn cs
r)
en d
( fi
le a
MS-SQL DB table
da p t er )
XML file
Important! Locations of How to Guides & Further Info
SAP Service Marketplace:

http://service.sap.com/bw
l How to Guides > BW 3.5 > How to Integrate XI and BW l How to Guides > BW 3.0 > How to Load XML Data into BW
http://service.sap.com/netweaver
l Media Library > Cross Application > How to Push Data from BI to XI (including receiver examples)
SAP Developer Network

http://www.sdn.sap.com > Business information Warehouse; > NetWeaver
Questions?
Q&A
Copyright 2004 SAP AG. All Rights Reserved

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, Outlook, and PowerPoint 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, and Informix are trademarks or registered trademarks of IBM Corporation in the United States 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, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered
trademarks of Citrix Systems, Inc.

n HTML, XML, XHTML and W3C 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 MaxDB is a trademark of MySQL AB, Sweden. n 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.
n 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.

BI XI Integration

Hochgeladen von

Dokumentinformationen

Originalbeschreibung:

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

BI XI Integration

Hochgeladen von

Copyright:

Verfügbare Formate

Know-How Network: SAP BW - SAP XI Integration

SAP AG 2004, SAP Labs, LLC 2004; Know-How Network: BW XI Integration / 2

SAP AG 2004, SAP Labs, LLC 2004; Know-How Network: BW XI Integration / 3

Integration on Several Levels, is the Key Challenge

Integration costs are high

SAP AG 2004, SAP Labs, LLC 2004; Know-How Network: BW XI Integration / 4

How to Address the Integration Challenge

Reduce custom integration

Increase company performance

SAP AG 2004, SAP Labs, LLC 2004; Know-How Network: BW XI Integration / 5

The comprehensive integration and application platform for lower TCO

Unifies and aligns people, information and business processes

Master Data Management

The business foundation for SAP and partners

DB and OS Abstraction DB and OS Abstraction

SAP AG 2004, SAP Labs, LLC 2004; Know-How Network: BW XI Integration / 6

SAP NetWeaver - Integration Between Layers

Process integration solution extend the reach of information integration solution

Master Data Management

DB and OS Abstraction DB and OS Abstraction

SAP AG 2004, SAP Labs, LLC 2004; Know-How Network: BW XI Integration / 7

SAP Business Intelligence

Open Interface a. Web Services

SAP AG 2004, SAP Labs, LLC 2004; Know-How Network: BW XI Integration / 9

SAP XI: Strategic Process & Integration Management

Database Integration Integration by single centralized data model

Direct Connections Integration challenge quadratically growing complexity

SAP AG 2004, SAP Labs, LLC 2004; Know-How Network: BW XI Integration / 10

Overview Exchange Infrastructure

Shared Collaboration Knowledge

Execute Collaborative Business Processes

Marketplaces SOAP Plain HTTP

System Landscape Directory System Landscape Directory

Partner Eco-System (additional 3rd Party Adapters and Industry Standards)

SAP AG 2004, SAP Labs, LLC 2004; Know-How Network: BW XI Integration / 11

SAP AG 2004, SAP Labs, LLC 2004; Know-How Network: BW XI Integration / 12

General Scenario: XI Data Load into BW

SAP AG 2004, SAP Labs, LLC 2004; Know-How Network: BW XI Integration / 13

BW: Extraction, Transformation and Loading

SAP AG 2004, SAP Labs, LLC 2004; Know-How Network: BW XI Integration / 14

XI Adapter Overview & Relevant Architecture

BW myself DataSource RFC Function Module Push Request (Pull)

XI Proxy Framework Proxy

ICF Web Service SOAP/RFC

tRFC XI ProxyAdapter RFC-Adapter 3rd Party Application 3rd Party Application

SAP AG 2004, SAP Labs, LLC 2004; Know-How Network: BW XI Integration / 15

Adapters hosted in the XI Adapter Engine

n 3rd Party Adapters

SAP AG 2004, SAP Labs, LLC 2004; Know-How Network: BW XI Integration / 16

BW-XI-Integration: Possible Quality of Service Levels

SAP AG 2004, SAP Labs, LLC 2004; Know-How Network: BW XI Integration / 17

Data Load scenarios via Push in BW

n BW requirements concerning Quality of Service

SAP AG 2004, SAP Labs, LLC 2004; Know-How Network: BW XI Integration / 18

BW-XI-Integration: Adapters & QoS

SAP AG 2004, SAP Labs, LLC 2004; Know-How Network: BW XI Integration / 19

XI Adapters and XI data load How-to Architecture

SAP AG 2004, SAP Labs, LLC 2004; Know-How Network: BW XI Integration / 20

XI Data Load: Components of the Technical Solution

SAP XI HTTP inbound Adapter Delta Queue Interface ABAP Adapter

BW Staging: InfoCubes, ODS

Architecture: data flow for XI data load into BW

ABAP Adapter Routing