|
Customer
Event May 03 - Report
"Integration
with SAP Netweaver & SAP xi"
20 participants from different Swiss companies
enjoyed a very interesting presentation & discussion
with t2b & SAP's Jan Lemmens.
Please find his presentation slides here - attention:
it's a 9.5MB PDF file! xi_Basel_Mai03.pdf
Our conclusion was, that basically all SAP customers
will have to install Netweaver&Exchange
Infrastructure (xi) in the next 12-36 months in order to
use the new SAP xApps and other new business
functionality provided by SAP.
Because of this, the EAI/Integration teams of SAP
customers will have to define the position of xi within
the companies integration technology framework.
SAP xi
functionality overview by P.Toenz
with xi SAP is doing a fullblown market entry into
the EAI sector. The current version 2.0 provides useful,
though limited functionality, but v.3.0 (GA Dec.03) will
provide most of the commonly required functionality for
EAI. The marketing brand of "Netweaver" is
bundling xi + the WebAppserver + the development
environment.
- Web App server, with parallel ABAP and J2EE server
engines
- Web-GUI on the fly: SAP-GUI - HTML interpreter
(current ITS feature)
- Webservices on the fly: SOAP interpreter for
RFC/BAPI/IDOC APIs
- enhance Eclipse Java development environment
- EAI Master Data: Enhanced System Landscape
Directory (extenable infrastructure documentation
DB)
- EAI Master Data: Integration Repository with CIM
data structure
- EAI Detail Data: Integration Directory to define
& configure the flows between the Repository
(master) elements.
- Adapters: SAP technology + technology adapters
(SOAP+HTTP, native; RDBMS; JMS; File)
- Mapping tool & and dev-time mapping test tool
- Integration server: standard functionality;
additionally a "light" version for simple
msg handling might be distributed to many servers.
- ProcessManagement & Workflow engine with
detailed message logging in xi database
- out-of-the box pre-configured business scenarios
the functionality is lagging behind EAI
"front-runners", specifically the single
repository approach might be a limiting factor for
globally distributed companies.
SAP BusinessConnector will be phased out and might
currently be positioned as the "easy" way for
simple integration requirements, where the requirements
would not justify the setup of the "heavier"
xi infrastructure.
I will develop a technology white paper with more
details based on the knowhow shared at the SAP
integration conference from Berlin, May 7+8.
|