Get documents about "EAI_Tech_Us
Document Sample
Presented by
Dipl. Ing. Dirk Hanke
CEO EAI One Integration -WWW.EAIONE.COM-
Berlin • Dresden • Hannover
Berlin • Phone +49 (0) 172 325 9879 • eMail dirk_hanke@eaione.com
History : 2 Years Siemens Development of High Speed Communication Systems,
16 Years IBM senior IT Architect Working for Five Different Verticals
Setup EAIONE's Architecture and Development at IBM in 1995
Typical customer environment
SAP R/3
• FI
• SD
• MM
• CO
• ISU
• ISH
Poor , function oriented
I/F techniques
Communication
Server / Links
GUI
WORKFLOW B+C+D WORKFLOW A
The problem of final definition
Portals ITV - Weather - Assets - Schedules - Financials - Patient Movement - Modeling …..
Visualization Tools
TOOLA TOOLB TOOLC TOOLD TOOLE TOOLF TOOLG TOOLF TOOLG TOOLH
Corporate Data Environment XML
WORKFLOW B+C+D
WORKFLOW A
Databases and other sources
SOURCE SOURCE SOURCE SOURCE
DB1 DB2 DB3 DB4 DB5 DB6 DB7
A B D E
DTS Migration systems, C2, Transportation Financial, Simulation /Modeling, and Administrative Databases
Typical customer environment
KIS System
Patient
Lab System
Admin
System
Controlling Surgery
SAP R/3
What is common over all System
Systems ?
Billing
Patient
Finance Radialogy
System
OutPatient
Material System
Competitors Workflow strategies
Reusability ? , Efforts ? Transparency ? Complex or Complicated ?
Topology usually leads to:
•Classical implementation approach Individual, non standardized mappings
•“per Interface”,
Vendor solution or ?
• considering all 1:n possible relations
... Creating the classical spaghetti...
The central idea behind competitors products
Application A Application B
Technology related
mapping & logic
Technology Layer cross protocols Technology
Layer
Internet Http(s) XML RFC SAP
Application Transport Protocol Protocol Application
ACK ACK
ACK
Technology
EDIFACT Layer
Protocol
ACK
Competitors Insurance
Business Process Application
View Application C
( Standard ? Re-Use ? )
Competitors neverending effort
Process of one single attribute
Application 1
Protocol
Single
Conversion Information
e.g. Name
Conversion #ID 66
Conversion
Application A
Application 2
Single Protocol
Information Action
e.g. Name Action
#ID 66 Protocol
Action
Single
Information
e.g. Name
#ID 66
Default
Default Application X
Default
Effort : Protocol
(Single Attribute + Single
Referenced Attributes) Single Activity
Information
e.g. Name
* Protocol (Mapping) #ID 66
* Individual Logic
* (n:n) Applications
* Customers
Goals for the Architecture ...
» Workflow independent Interfaces
» Customizable , no coding, generic adapter approach
» Application dependent , not Interface dependent
» Reusability : Customizing an application once, whenever it is used by an interface
» Technical system (application) Interface : Online / bi-directional / functionless
» „Release independent“ I/F technique, scalable , load balancing
» Usage of a neutral Object Standard to cover all application communication standards
» One runtime code for all business areas & countries
» One skill to cover projects over multiple business areas
» Open for all new technologies ( e.g. “.NET” , Java Beans )
» Minimum TCO on maximum ROI
EAIONE ’s physical view of an application
Application
DB
API Layer
Protocol Layer
e.g. Transport
Outside world ( EAI World )
EAIONE ’s logical view of interfacing
Applicat Applica
ion DB tion DB
API Layer API Layer
Protocol Layer Protocol Layer
e.g. Transport
e.g. Transport
Outside world ( EAI World ) Outside world ( EAI World )
What is common ?
An application independent definition
• No API have common structures
of single process must be defined to have
• Protocol structures as framework are common (e.g XML)
a common business process definition
• Content of protocol depends mostly on single application,
• (otherwise the applications are common, customizing ? )
The central idea behind EAIONE (Object Layer)
EAIONE Application SAP R/3 V4.6 EAIONE Application Navision Axapta
OBJECT ORDER OBJECT ORDER
OBJECT MATERIAL Conversion Conversion OBJECT MATERIAL
Action Action
OBJECT DEBTOR Default Default OBJECT DEBTOR
Single CHARACTER Single CHARACTER
Information LENGTH 35 Information LENGTH 40
e.g. Name DEFAULT e.g. Name DEFAULT
#ID 66 LOGIC #ID 66 LOGIC
Xfer no Mapping
Single Single Single Single Single
Information Information Information Information Information
Object Template e.g. Name e.g. Street e.g. City e.g. Zip Code e.g. Country
#ID 66 #ID 67 #ID 68 #ID 69 #ID 70
The central idea behind EAIONE
Sample : EAIONE's Application SAP R/3 V4.6
Object Technology
Layer Layer
Standard Object Access (Method) RFC
CHARACTER
EAIONE LENGTH 35
Conversion SAP RFC Adapter KNA1-NAME1
#ID 66
OBJECT DEBTOR
OBJECT DEBTOR
Single CHARACTER Access (Method) IDOC
Action
Information LENGTH 35
e.g. Name DEFAULT Single
#ID 66 LOGIC Information
EAIONE NUMERIC
e.g. Name
LENGTH 35
#ID 66 SAP IDOC Adapter
E2KNA1M002::NAME1
Default #ID 66
#ID 67
#ID 68 EAIONE
SAP BAPI Adapter Access (Method) BAPI
#ID 69
#ID 200 Access (Method) CAPI
EAIONE
SAP CAPI Adapter
Preparing the object attributes to standard Mapping once the physical attributes of a
content with Conversion, Actions , Defaults specific protocol to the standard object
attributes
The central idea behind EAIONE
Application A Standard Objects Application B
Technology Layer Object Layer Technology
Layer
#ID 66 #ID 66
HANDLE
Internet Http(s) XML HANDLE RFC SAP
Objects
Application Transport Protocol Objects Protocol Application
HANDLE
ACK ACK Objects
ACK ACK ACK
#ID 66
Gen. Adapter Behavior
ACK
(1)
(2)
EDIFACT
(3) Protocol
Multiple Threads
TCP/IP data (parallel processing)
(in) TCP/IP data
ACK
(out)
Insurance
EAIONE's Application
database Application CBalancing,Fail over
Load
Architecture of EAIONE
1st Layer 2nd Layer
Samples of
Transport & Protocol Adapter Standard Objects
Vendor Applications
XML
SSL SQL
SAP
Customizing
EDI
Http Module
EDIFACT
CRM File
DEBTOR
DEBTOR
HL7 DEBTOR
DEBTOR
SMTP
RFC / IDOC MATERIAL
MATERIAL
MATERIAL
Axapta MATERIAL
FTP
BAPI
ORDER
ZIP ORDER
X12N ORDER
ORDER
ORDER
.NET Conversion Action Default Mapping
(Web Services)
EAIONE’s Relational Database ( SQL Entry Level 92 )
The Benefit structure of EAIONE
Pre Built
(Project entry)
Competitors
Effort /Errors EAI ONE
PreTest Unit Test System Final Test Quality
Test Assurance
Standard development process versus Pre built scenarios starting at Final Test
=
TCO + ROI
Total effort of project
Projectstep EAI ONE Links to projectsteps* Individual Competitor
People- Programming
days Professional Customer
Service Partner
SAP-Worflow 10 XX
EAI ONE Phase IV (Setup) 2 (x) (x)
EAI ONE Phase I ( Objectdefinition) 1 XX X ** **
EAI ONE Phase II (Methoddefinition) 12 XX X
EAI ONE Phase III 3 XX X
( Defaults,Logik,Konv.) Sum 170 Sum 50
EAI ONE Phase V (Test,Confirmation) 3 X XX 15 8
EAI ONE Phase VI (Initial data) 5 XX 25 15
EAI ONE License
Tota 36 PD + ca. 20-25 >= 210 PD + > 73 PD
License PD 35 PD + License
Customer + Customer
* The distribution based on own knowledgde ,
referenced to the knowledgde of customer / partner
** single effort cannot be referenced
EAI One’s and competitors market area
TCO
Maintenance
Enterprise Market
( moving from expensive to medium/low cost )
Services
• Projects > min 6 weeks
• Expensive Service Org
• (IBM,HP,SIEMENS)
• Programmer,Consultant
• No Reuse Maintenance
SMB Market Services
(low cost) • Pre-Built
• Only Consultant
• “Five a Life”
• SMB for SMB+Enterprise
License License
Big “5” Competitors TCO EAI One’s TCO
Part of current EAI ONE project
SAP R/3
Debtors Debtors
Material Material
ROUTING
Oracle based
PPS
System
BOM BOM
Invoice Delivery
Communication with EAI ONE ( totaly 15 – 20 different processes , SAP I/F IDOC ,
PPS I/F RMDBS with trigger / alerts)
The BICEPS <> SAP IF with EAIONE
BICEPS Standard Objects SAP R3 V4.6
Technology Layer Object Layer Technology
Layer
#ID 66 #ID 66
HANDLE
BICEPS Trigger SQL HANDLE IDOC SAP
Objects
Application Transport Protocol Objects Protocol Application
ACK ACK
ACK ACK ACK
Gen. Adapter Behavior
(1)
(2)
(3)
Multiple Threads
TCP/IP data (parallel processing)
(in) TCP/IP data
(out)
EAIONE's
database
Load Balancing,Fail over
