bi xi integration
Post on 18-Apr-2015
36 Views
Preview:
TRANSCRIPT
Know-How Network: SAP BW - SAP XI Integration
SAP AG 2004, SAP Labs, LLC 2004; Know-How Network: BW – XI Integration / 2
Agenda
SAP NetWeaver
SAP XI Data Load into SAP BW
Distribution of BW Data to other systems using BW’s Open Hub and XI
SAP AG 2004, SAP Labs, LLC 2004; Know-How Network: BW – XI Integration / 3
Agenda
SAP NetWeaver
SAP XI Data Load into SAP BW
Distribution of BW Data to other systems using BW’s Open Hub and XI
SAP AG 2004, SAP Labs, LLC 2004; Know-How Network: BW – XI Integration / 4
Integration on Several Levels, is the Key Challenge
Business Driversn Extended Value NetWorkn Increased Market Dynamics
Integration costs are highn Lots of heterogeneous systemsn Long integration projectsn IT environments become
increasingly rigid
Pressure on IT increasesn Must leverage existing
investmentsn Must support new business
processes quickern Must reduce total cost of
ownership (TCO)
CallCenter
ERP
Technical systems
PLM
Market Analysis
Trading
SCM
Document Mgmt
e-Sales
E-Procurement
SAP AG 2004, SAP Labs, LLC 2004; Know-How Network: BW – XI Integration / 5
How to Address the Integration Challenge
Reduce complexityn Minimize the number of
connections through hubsn Use only 1 platform to integrate all
people, information, and systems
Reduce custom integrationn Deliver .NET and J2EE
interoperabilityn Deliver adaptors for ISV productsn Deliver products, not projects!
Increase company performancen Increase ease of use, scalability
and adaptability n Increase business process
flexibility by using an Enterprise Services Architecture
CallCenter
ERP
Technical systems
PLM
Market Analysis
Trading
SCM
Document Mgmt
e-Sales
E-Procurement
SAP AG 2004, SAP Labs, LLC 2004; Know-How Network: BW – XI Integration / 6
SAP NetWeaver™The comprehensive integration and application platform for lower TCO
Unifies and aligns people, information and business processesn Integrates across technologies
and organizational boundariesn A safe choice with full .NET and
J2EE interoperability
The business foundation for SAP and partnersn Powers business-ready
solutions that reduce custom integration
n Its Enterprise Services Architecture increases business process flexibility
DB and OS Abstraction
.NET WebSphere…
People Integration
Com
posi
te A
pplic
atio
n Fr
amew
ork
Process IntegrationIntegration
BrokerBusiness Process
Management
Information IntegrationBusiness
IntelligenceKnowledge
Management
Life Cycle M
anagement
Portal Collaboration
J2EE ABAP
Application Platform
Multi-Channel Access
SAP NetWeaverSAP NetWeaver™™
DB and OS Abstraction
Master Data Management
SAP AG 2004, SAP Labs, LLC 2004; Know-How Network: BW – XI Integration / 7
SAP NetWeaver™ - Integration Between Layers
Process integration solution extend the reach of information integration solution
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
DB and OS Abstraction
.NET WebSphere…
People Integration
Com
posi
te A
pplic
atio
n Fr
amew
ork
Process IntegrationIntegration
BrokerBusiness Process
Management
Information IntegrationBusiness
IntelligenceKnowledge
Management
Life Cycle M
anagement
Portal Collaboration
J2EE ABAP
Application Platform
Multi-Channel Access
SAP NetWeaverSAP NetWeaver™™
DB and OS Abstraction
Master Data Management
Focus of this discussion
SAP AG 2004, SAP Labs, LLC 2004; Know-How Network: BW – XI Integration / 8
SAP Business Intelligence
Sources DataWarehousing
BI Platform BI Suite
Dat
a A
cqui
siti
on
Acc
ess
Ope
n In
terf
ace
a. W
eb S
ervi
ces
Dat
a P
rese
ntat
ion
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 AG 2004, SAP Labs, LLC 2004; Know-How Network: BW – XI Integration / 9
SAP BI Architecture
SAP AG 2004, SAP Labs, LLC 2004; Know-How Network: BW – XI Integration / 10
SAP XI: Strategic Process & Integration Management
Integration Engine &Bus Infrastructure
Shared central knowledge,
Small number of peer-to-peer connections
Direct Connections
Integration challengequadratically
growing complexity
Database Integration
Integration by single centralized data
model
Enterprise ResourcePlanning
Inter-/Intra-EnterpriseCo-operation
CollaborativeBusiness
SAP AG 2004, SAP Labs, LLC 2004; Know-How Network: BW – XI Integration / 11
Overview Exchange Infrastructure
IntegrationRepositoryIntegrationRepository
IntegrationDirectory
IntegrationDirectory
Configuration
Execute CollaborativeBusiness Processes
Design
System Landscape DirectorySystem Landscape Directory
Shared CollaborationKnowledge
Runtime Workbench
Runtime
Integration ServerIntegration ServerIntegration
EngineAdditional Integration Services
SAP Systems
3rd Party and Messaging Systems
SOAP Plain HTTP
Marketplaces
Partner Eco-System (additional 3rd Party Adapters and Industry Standards)
Business Process Engine
SAP AG 2004, SAP Labs, LLC 2004; Know-How Network: BW – XI Integration / 12
Agenda
SAP NetWeaver
SAP XI Data Load into SAP BW
Distribution of BW Data to other systems using BW’s Open Hub and XI
SAP AG 2004, SAP Labs, LLC 2004; Know-How Network: BW – XI Integration / 13
Extended Service Infrastructure
General Scenario: XI Data Load into BW
BW
XI Non-SAP system C
Non-SAP system A
Info Consumers
Non-SAP system D
Non-SAP system B
Analysts, Knowledge Workers
n Persistencen Presentationn Analytics
n Open Interfacesn Routing & Monitoring n Transformation
SAP AG 2004, SAP Labs, LLC 2004; Know-How Network: BW – XI Integration / 14
BW: Extraction, Transformation and Loading
n Open for any sourcen Flexible set of ETL capabilities n Integration to mySAP.com on
application leveln Open to third-party toolsn Support of open standards
SAP AG 2004, SAP Labs, LLC 2004; Know-How Network: BW – XI Integration / 15
XI Adapter Overview & Relevant Architecture
myselfDataSource
Delta QueueRFC Function Module
Request („Pull“)
ICF
Web Service
3rd Party Application
SOAP/RFC
XI Proxy Framework
Proxy
XI Integration Server
3rd Party Application
„Push“
Proxy-“Adapter“
RFC-Adapter
BW
XI
SOAP-Adapter
RFC Framework
Status Management
*Non-SAP systems
tRFC
SAP AG 2004, SAP Labs, LLC 2004; Know-How Network: BW – XI Integration / 16
Adapters hosted in the XI Adapter Engine
The Adapter Engine hosts a set of adapters:n ABAP Proxy Frameworkn SAP Adapters
u File / FTPu JDBC (Database)u JMS (MQSeries, SonicMQ, …)u RFCu SOAPu SMTPu SAP BC (header extension for support of Quality of Service)u SAP Marketplace Adapteru RosettaNet (RNIF 2.0) Adapteru CDIX (RNIF 1.1) Adapter
n 3rd Party Adaptersu iWay: UCCnet, more to come …u Optional: Adapters developed by partners, certificated by SAP
SAP AG 2004, SAP Labs, LLC 2004; Know-How Network: BW – XI Integration / 17
BW-XI-Integration: Possible Quality of Service Levels
n XI categories of Quality of ServiceuBE (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.
uEO (Exactly Once): The message is sent asynchronously in this case; this means that the sender system does not wait for a response beforecontinuing processing. The Integration Engine guarantees that the message is sent and processed exactly once.
uEOIO (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.
SAP AG 2004, SAP Labs, LLC 2004; Know-How Network: BW – XI Integration / 18
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:uSOAP-DataSource (XML-DataSource)uWeb ServiceuBW-XI-Integration
n BW requirements concerning Quality of ServiceuData 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!
uData 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 areprocessed 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)
n ConclusionuEOIO (Exactly Once In Order) is required to enable the delta load in the
most flexible and robust manner
SAP AG 2004, SAP Labs, LLC 2004; Know-How Network: BW – XI Integration / 19
BW-XI-Integration: Adapters & QoS
n RFC-Adapteru asynchronous: EO, but not IO (tRFC)u synchronous, BE: No transactional security possible; (Drawback: only one
receiver system)uResult: Not recommended, as correct processing of delta loads with “After
Images” is not possible; practical however for mass load scenarios with strictly separated updates
n SOAP-Adapteru asynchronous: „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
uResult: Not recommended, as EOIO cannot be achieved; extensive configuration effort; However processing of “After Images” possible
n Proxyu asynchronous: EOIO, data is transferred from queue on Integration Engine
to queue in application systemu Result: Recommended without restriction; standard adapter of XI with the
highest flexibility concerning error handling
SAP AG 2004, SAP Labs, LLC 2004; Know-How Network: BW – XI Integration / 20
XI Adapters and “XI data load How-to” Architecture
myselfDataSource
Delta QueueRFC Function Module
Request („Pull“)
ICF
Web Service
3rd Party Application
SOAP/RFC
XI Proxy Framework
Proxy
XI Integration Server
3rd Party Application
„Push“
Proxy-“Adapter“
RFC-Adapter
BW
XI
SOAP-Adapter
RFC Framework
Status Management
*Non-SAP systems
tRFC
2.
3.
4.
1.
SAP AG 2004, SAP Labs, LLC 2004; Know-How Network: BW – XI Integration / 21
XI Data Load: Components of the Technical Solution
WANWAN
Partner Systems
different Infrastructures
HTTP inbound Adapter
SAP XI
Mapping
Routing
ABAP Adapter
ABAP Proxy
Delta Q
ueue Interface D
elta Queue
SAP BW
BW
Staging:InfoC
ubes, OD
S
Business Explorer
SAP AG 2004, SAP Labs, LLC 2004; Know-How Network: BW – XI Integration / 22
Architecture: data flow for XI data load into BW
XI
Non-SAP
BWDataSource
BW
Delta queue
InfoSource
Data recieved into XI from non-SAP applications
Delta extraction / load
pushXML data
ABAP proxy & RFC function
module
ABAP proxy & RFC function
module
HTTP inbound Adapter
SAP
XI
Mapping
Routing
ABAP Adapter
InfoProviders
SAP AG 2004, SAP Labs, LLC 2004; Know-How Network: BW – XI Integration / 23
Agenda
SAP NetWeaver
SAP XI Data Load into SAP BW
Distribution of BW Data to other systems using BW’s Open Hub and XI
SAP AG 2004, SAP Labs, LLC 2004; Know-How Network: BW – XI Integration / 24
Extended Service Infrastructure
General Scenario: BW Open Hub “push” via XI
BW / Business Planning XI
n Persistencen Information Deliveryn Central Monitoring
n Message Routingn Interfacingn Processing
Non-SAP system A Non-SAP system B
SAP AG 2004, SAP Labs, LLC 2004; Know-How Network: BW – XI Integration / 25
The Corporate Information Factory –Directly supported components of SAP and SAP BW
DSS Applications Departmental Data Marts
EDW
MarketingAcctg Finance
Sales ERPERP
ERPCRM
eComm.
Bus. Int.
ETL
GlobalODS
Oper.Mart
Exploration warehouse/ data mining
Source: Bill Inmon
Stag
ing
Area
localODS
DialogueManager Cookie
Cognition
Preformatteddialogues
cross mediaStorage mgr
Near lineStorage
Web Logs
SessionAnalysis
Internet
ERPCorporate
Applications
ChangedData
GranularityManager
SourceslmySAPlOthers
APOSEMOthers
E-Analytics
BW
BW NLS
SAP AG 2004, SAP Labs, LLC 2004; Know-How Network: BW – XI Integration / 26
The Corporate Information Factory –SAP BW Open Hub Service
DSS Applications Departmental Data Marts
EDW
MarketingAcctg Finance
Sales ERPERP
ERP
CRM
eComm.
Bus. Int.
ETL
GlobalODS
Oper.Mart
Exploration warehouse/data mining
Source: Bill Inmon
Stag
ing
Area
localODS
DialogueManager
CookieCognition
Preformatteddialogues
cross mediaStorage mgr
Near lineStorage
Web Logs
SessionAnalysis
Internet
ERPCorporate
Applications
ChangedData
GranularityManager
Open Hub Service
SAP AG 2004, SAP Labs, LLC 2004; Know-How Network: BW – XI Integration / 27
Open Hub in the SAP Business Intelligence Architecture
SAP BW architecture: the Open Hub
SAP AG 2004, SAP Labs, LLC 2004; Know-How Network: BW – XI Integration / 28
§ Controlled distribution of consistent data
§ Target: file or DB table § Central monitoring§ Filtering§ Aggregation§ Scheduling§ Full or Delta Mode§ Process Chains
(Data + Metadata)
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.
SAP AG 2004, SAP Labs, LLC 2004; Know-How Network: BW – XI Integration / 29
SAP BW Open Hub: Concept Overview 2
Data transfer in Open Hub Service 3.x
SAP BWDB Table/BI0/OH….
Open HubService
InfoCubes
Flat file.csv
Other Data Marts
Any Other Application(xyz, etc)
Push
Push
Master Data
ODSPull
Pull
Pull
Open Hub terminology –InfoSpoke: An SAP BW object, where the specific properties are configured for the dataset to be extracted.
SAP AG 2004, SAP Labs, LLC 2004; Know-How Network: BW – XI Integration / 30
Open Hub
SAP BW’s Open Hub does NOT offer functionality for delivery of the datasets from the BW system (it’s DB or it’s 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 BW’s 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 XI’s messaging functionality to offer an improved, effective and robust architecture for meeting this integration challenge.
SAP AG 2004, SAP Labs, LLC 2004; Know-How Network: BW – XI Integration / 31
(Data + Metadata)
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.
Non-SAP systems
XI
ABAP proxy inbound Adapter
SAP XI
Mapping
Routing
JDB
C &
File Adapters
Non-SAP systems
Custom process
type
SAP AG 2004, SAP Labs, LLC 2004; Know-How Network: BW – XI Integration / 32
Receiver Systems Examples in Current “How to” Paper
Server
SAP BW 3.5
A. XML doc/ async. send (proxy)
SAP XI 3.0
D. async msg return (proxy)
MS-SQL DB table
XML file to remote server file system
B. async. send (JDBC adapter)
C. async send (file adapter)note: different interface than
send for return msg
SAP AG 2004, SAP Labs, LLC 2004; Know-How Network: BW – XI Integration / 33
Sequence: Open Hub push to MS-SQL DB via XI (1)
SAP BW 3.5
A. XML doc/ async. send (proxy)
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)
Remote (non-SAP) MS-SQL DB
SAP AG 2004, SAP Labs, LLC 2004; Know-How Network: BW – XI Integration / 34
Sequence: Open Hub push to MS-SQL DB via XI (2)
SAP BW 3.5
A. XML doc/ async. send (proxy)
SAP XI 3.0
B. async send (JDBC Adapter)
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
Remote (non-SAP) MS-SQL DB
SAP AG 2004, SAP Labs, LLC 2004; Know-How Network: BW – XI Integration / 35
Sequence: Open Hub push to MS-SQL DB via XI (3)
SAP BW 3.5
A. XML doc/ async. send (proxy)
SAP XI 3.0
B. async send (JDBC adapter)
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)
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.
Remote (non-SAP) MS-SQL DB
SAP AG 2004, SAP Labs, LLC 2004; Know-How Network: BW – XI Integration / 36
Sequence: Open Hub push to MS-SQL DB via XI (4)
SAP BW 3.5
A. XML doc/ async. send (proxy)
SAP XI 3.0
C. async msg return (proxy)B. async send (JDBC adapter)
note: different interface than send for return msg
1. START process chain (e.g. daily job)
2. Open hub staging to flat DB table
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
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)
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.
Remote (non-SAP) MS-SQL DB
SAP AG 2004, SAP Labs, LLC 2004; Know-How Network: BW – XI Integration / 37
SAP BW Open Hub “push” possibilities: SAP XI Extended Scenario
Server
SAP BW 3.5
A. XML doc/ async. send (proxy)
SAP XI 3.0
F. async msg return (proxy)
C1. update async. BAPI (RFC)
C2. async. return msg. (RFC)
mySAP ERP
MS-SQL DB table
XML file
D. async. update (JDBC adapter)E. async send (file adapter)
note: different interface than send for return msg
SAP R/3 4.x
B1. update async. BAPI (proxy)
B2. acknowledgement (proxy) Future
Future
SAP AG 2004, SAP Labs, LLC 2004; Know-How Network: BW – XI Integration / 38
è SAP Service Marketplace:
http://service.sap.com/bwlHow to Guides > BW 3.5 > “How to Integrate XI
and BW”lHow to Guides > BW 3.0 > “How to Load XML
Data into BW”
http://service.sap.com/netweaverl Media Library > Cross Application > “How to
Push Data from BI to XI (including receiver examples)”
Important! Locations of “How to” Guides & Further Info
è SAP Developer Networkhttp://www.sdn.sap.com > Business information Warehouse; > NetWeaver
SAP AG 2004, SAP Labs, LLC 2004; Know-How Network: BW – XI Integration / 39
Q&A
Questions?
SAP AG 2004, SAP Labs, LLC 2004; Know-How Network: BW – XI Integration / 40
nNo 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.nSome software products marketed by SAP AG and its distributors contain proprietary software components of other
software vendors.nMicrosoft, 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.nOracle is a registered trademark of Oracle Corporation.nUNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.nCitrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered
trademarks of Citrix Systems, Inc.nHTML, 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. nMaxDB is a trademark of MySQL AB, Sweden.nSAP, 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.nThese 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.
Copyright 2004 SAP AG. All Rights Reserved
top related