Session SOA-12 Solving OpenEdge - PowerPoint PPT Presentation

About This Presentation
Title:

Session SOA-12 Solving OpenEdge

Description:

Title: Session ID and Title Author: Your Name Description: Progress Exchange 2005 5 - 8 June, 2005 Orlando, Florida USA Last modified by: psc – PowerPoint PPT presentation

Number of Views:77
Avg rating:3.0/5.0
Slides: 43
Provided by: Your63
Category:

less

Transcript and Presenter's Notes

Title: Session SOA-12 Solving OpenEdge


1
Session SOA-12Solving OpenEdge Integration
Scenarios With Sonic ESB
  • Bob Trabucchi
  • Senior Systems Engineer

2
Purpose of This Presentation
  • Problem too much too fast!
  • And we often leave you to figure out how to
    handle it.
  • Solution Provide more palatable samples of our
    technology
  • Outline recognized OpenEdge integration problem
  • Show directly how Sonic ESB solves it

3
Why Does Integration Seem So Hard?
  • Those who initially ventured out got clobbered!

Integration projects average 20 months to
complete
Fewer than 35 of projects finish on time and on
budget
35 of software maintenance budgetis spent
maintaining point-to-point application links
Statistics from Forrester Research Reducing
Integration Costs
4
What Went Wrong?
  • Many technologists were forced to use integration
    technologies available at the time.
  • Developed for client/server world
  • Dont scale beyond the enterprise
  • Require lots of coding and specialized processes/
    kludges.
  • Proprietary
  • Result in single-use solutions

5
OpenEdge Integration Scenarios
  • File Transfer Systems
  • Pre-packed applications
  • eCommerce
  • Conclusions

6
Application Integration Models
Two typical approaches
Sales
Warehouse
7
Data Integration Model
File transfer systems
  • Term used to describe a group of homegrown
    integration solutions that implement a Data
    Specific Model.
  • Use combinations of
  • multi- step copies
  • merge of database/file data
  • FTP
  • Batch processing
  • Complex maze of scripts, applications, and manual
    processes.

8
File Transfer System Example
Flat file copy
Warehouse
Sales
Fulfillment Application
Order Application
Database
Database
FTP/Batch
Flat File
Flat File
9
File Transfer System Example
Database copy
Load
FTP/Batch
Transform
10
File Transfer Systems
Technical pains
  • Message Latency
  • Information is delivered hours to weeks late
  • Reliability
  • Other applications,networks,copy problems
  • Downtime
  • Databases must be frozen for copies
  • Synchronization
  • Everyone goes live together

11
File Transfer Systems
Business pains
  • Revenue generating applications offline
  • Incredible overhead
  • 24 hour IT staff
  • High cost of extra hardware, software
  • Networks, databases, maintenance
  • Problems that systems encounter using stale data
  • Lost revenue
  • Poor customer service

12
File Transfer Systems
Business pains
Overnight
Overnight
13
File Transfer Systems
Business pains
14
But it doesnt have to be this way!
15
Introducing Sonic ESB
Intelligent middleware implemented
  • Standards-based intelligent middleware platform
    designed to facilitate integration
  • Contains
  • Messaging 100 reliable, scalable secure
    communication delivery system.
  • Framework to build/deploy standalone and
    reusable integration logic modules
  • Connectivity components
  • Wide variety of integration endpoints
  • Service-Oriented architectures of tomorrow

16
Sonic ESB solution
Reliable, real-time, reusable
Out-of-box Service
Sonic ESB
Load
Extract
Transform
17
File Transfer Systems
The Sonic ESB solution
  • Sonic ESBs real-time data integration means
  • Revenue generating apps are constantly running
    increased revenue
  • Elimination of 2nd and 3rd shift IT resources
    lower costs
  • Elimination of hardware and software lower
    costs
  • Resulting solution is reusable

18
OpenEdge Integration Scenarios
  • File Transfer Systems
  • Pre-packaged Integrations
  • eCommerce Integrations
  • Conclusions

19
Application Integration Models
Two typical approaches
Warehouse
20
Real-time Pre-packaged Integrations
Background
  • Business needs require OpenEdge application to
    talk with entrenched pre-packed applications.
  • Traditional solutions use combinations of
  • Synchronous exchange assume 100 up-time
  • Complex and hard-coded data conversions
  • Expertise in 3rd-party applications
  • Solution hard-coded into OpenEdge application

21
Real-time Pre-packaged Integrations
Background
Sales
Transform
OE Application
SAP API
Transport
RPC
Database
Solution is hard-coded into the application
22
Real-time Pre-packaged Integrations
Background
Warehouse
Transform
SAP Application
Sales
OE API
Transport
OE Application
Database
Database
Somebody has to take the hit!
23
Real-time Pre-packaged Integrations
Technical pains
  • Reliability
  • Synchronous transfer assumes 100 up-time
  • Complexity
  • Limited expertise with prepackaged app means
    costly experts or lengthy training
  • Mountains of code to write/maintain
  • Synchronization
  • Slightest change means redeploying

24
Real-time Pre-packaged Integrations
Business pains
  • Problems that systems encounter when a component
    goes down
  • Lost revenue
  • Poor customer service
  • Business needs dictate quickly delivered and
    reliable integration solution just to survive!
  • Managers want solution now, not in 6 months when
    it is too late

25
But it doesnt have to be this way!
26
Sonic ESB Alternative
A better way
  • Adapter-based solution
  • Pre-built adapters map proprietary APIs to
    standards (XML)
  • Solution built on Standards-based messaging
  • Insulates applications from downtime
  • Scalable and flexible
  • All participants are blissfully unaware
  • Integration modules exist outside the business
    critical applications

27
Sonic ESB Adapter-based Solution
Reliability and interoperability solved
Sonic ESB
1
3
2
  • Component Breakdown
  • OpenEdge Sonic Adapter
  • Transformation Service (resolve mismatches)
  • SAP Adapter for Sonic ESB

1
2
3
28
Real-time Prepackaged Applications
The Sonic ESB solution
  • Sonic ESBs real-time application integration
    means
  • Revenue generating apps are constantly running
    increased revenue
  • Solution is built using out-of-box components
    lower costs
  • Resulting solution is reusable
  • Prepackaged applications now
  • HTTP, Java, C/.Net, Web Services next

29
OpenEdge Integration Scenarios
  • File Transfer Systems
  • Pre-packed applications
  • eCommerce applications
  • Conclusions

30
Real-time eCommerce Integration
Background
  • Business needs require OpenEdge application share
    data over the Internet
  • Traditional solutions use combinations of
  • Synchronous exchange assume 100 up-time
  • Complex, hard-coded, non-standard transforms
  • Expertise in HTTP(S)
  • Security expertise

31
Real-time eCommerce Integration
Background
Warehouse
Head Office
Java Application
OE Application
Internet
HTTP(S)
Database
Database
Each codes Security, Transform, and Transport
Logic
32
Real-time eCommerce Integration
Technical pains
  • Reliability
  • Synchronous transfer assumes 100 up-time
  • Complexity
  • Mountains of code to write/maintain
  • Synchronization
  • Slightest change means redeploying
  • Security
  • Security is your domain

33
But it doesnt have to be this way!
34
Sonic ESB Alternative
A better way
  • Solution built on standards-based messaging with
    native HTTP(S) support
  • Insulates applications from downtime
  • Scalable, flexible, built-in security
  • All participants are unaware of each other
  • Integration modules exist outside the business
    critical applications and are built using
    reusable components.

35
Sonic ESB eCommerce Solution
Secure, resilient, and reusable!
Sonic ESB
1
2
HTTP(s)
  • Component Breakdown
  • OpenEdge Sonic Adapter
  • Transformation Service (resolve mismatches)

1
2
36
Real-time eCommerce
The Sonic ESB solution
  • Sonic ESBs real-time eCommerce application
    integration means
  • OpenEdge applications are shielded from failures
    higher revenue
  • Result Reusable Solution
  • HTTP(s) Now
  • Same solution for pre-packaged applications, FTP,
    Java applications, etc.

37
OpenEdge Integration Scenarios
  • File Transfer Systems
  • Pre-packed applications
  • eCommerce applications
  • Conclusions

38
In Summary
  • Avoid costly mistakes
  • Build the smarter solution first!
  • Get on the Bus!

39
Where To Go From Here?
Get some specifics!
  • SOA-03 Open Up Access to your 4GL Applications
    Using Web Services
  • SOA-05 Building an Enterprise SOA Using ESB
  • SOA-06 Get on the Bus with the OpenEdge Adapter
    for Sonic ESB
  • SOA-09 Conducting Business with OpenEdge and
    Sonic

40
Questions?
41
Thank you for your time!
42
(No Transcript)
Write a Comment
User Comments (0)
About PowerShow.com