OpenEdge and Sonic ESB in Action

1
OpenEdge andSonic ESB in Action

• Theory meets practice

2
Demo Whats installed and running!

• OpenEdge 10.0B
• OpenEdge Adapter for Sonic
• Sonic ESB
• Transformation Services
• SonicMQ
• Messaging Broker

3
OpenEdge components in the demo
Design/ Implement
Test/Debug
Staging/QA
Production
OE Client
Develop 4GL code
Progress Explorer
Configure, and manage OE components Runs
OpenEdge Adapter for Sonic
4
Sonic ESB components in the demo
Design/ Implement
Test/Debug
Staging/QA
Production
ESB Explorer
Configure services, endpoints, and connections
5
Demo Scenario

• Company
• Books R Us (BRU)
• Business
• Publisher of books and magazines
• Integration Goals
• Publish new book and magazine titles daily to
  interested parties.

6
Demo Scenario

• Interested parties that will be notified in a
  phased approach.
• Phase 1 Internal system sales dept.
• Phase 2 New partner GBD book distributor
• Phase 3 Magazine distribution house
• Phase 4 Freds book distribution service

7
Phase 1

• Problem
• Data delay inherent in current batch system
  causes customer service issues for direct phone
  sales.
• Solution
• Add real-time integration channel between
  inventory system and sales system
• No negative impact to either application
• Minimal code solution (lowers costs)
• Same system used for this and all future
  integrations.

8
Phase 1 Replace batch system
OpenEdge Inventory Application
OpenEdge Sales Application
9
Phase 1 Solution Summary

• A few lines of code in each application to open
  the communications channel.
• ESB messaging backbone does the rest!

RUN jms/pubsubsession.p PERSISTENT. RUN
setBrokerURL IN pubsubsession. RUN SETUSER IN
pubsubsession . RUN setPassword IN pubsubsession
. RUN beginSession IN pubsubsession. RUN PUBLISH
IN pubsubsession (MyPartners.
10
Phase 1 Demo
11
Phase 1 Review

• Real-time conversion accomplished
• Trivial coding effort got us on the ESB
• No impact to application availability
• Reliable messaging backbone
• Asynchronous
• Same system used for this and all future
  integrations? Lets see..

12
Phase 2

• Problem
• Expand the integration to support BRUs new
  direct-to-customer outlet stores. Chain
  headquarters needs new data!
• Solution
• Add real-time integration channel to outlet
  stores
• Support their already existing XML book
  information format

13
Phase 2
XML
14
Phase 2 Solution Summary

• Connect OpenEdge GBD application to the Sonic
  ESB.
• A few lines of 4GL code
• ESB does transport and transformation
• Configure new service to transform
• No code changes to the BRU inventory application
  (publisher)
• Once you are on the ESB, no more coding is
  required!

15
Anatomy of an ESB Service
Fault Endpoint
RejectedEndpoint
Exit Endpoint
Entry Endpoint
Service
Input
16
Phase 2 Demo
17
Phase 2 Review

• Real-time integration with outlet stores head
  office accomplished!
• New application gets the bus!
• Minor code changes
• Support their XML format
• Deploy ESB out-of-box transformation
• SAME system used for both integrations
• NO changes to BRU inventory application.

18
Phase 3

• Problem
• Expand the integration to support BRUs new
  partner who distributes magazines.
• Solution
• Add real-time integration channel to magazine
  distribution center.
• Support their already existing magazine specific
  XML information format.

19
Phase 3
XML
XML
XML
T MyPartners
XML
20
Phase 3 Solution Summary

• Java-based Linux application will use JMS client
  to connect to Sonic ESB.
• ESB does transport and transformation between
  OpenEdge application and new magazine
  distribution center.
• NO CODE changes in the OpenEdge application.

21
Phase 3 Demo
22
Phase 3 Review

• Real-time integration with magazine distributor
  accomplished!
• Current Java application gets the bus!
• Minor code changes
• Supported their own XML format
• Deploy ESB out-of-box transformation
• Re-used architecture for the integration
• NO changes to BRU inventory application.

23
Phase 4

• Problem
• Expand the integration to support an other Book
  distributor, Freds.
• Solution
• Add real-time integration channel to book
  distribution center.
• Support their already existing specific XML
  information format.
• Re-use Freds existing HTTP interface.

24
Phase 4
XML
XML
XML
T MyPartners
XML
XML
25
Phase 4 Solution Summary

• Windows application will use HTTP to talk with
  Sonic ESB.
• ESB does transport and transformation
• AGAIN! NO CODE changes in the OpenEdge
  application.

26
Phase 4 Demo
27
Phase 4 Review

• Real-time integration with Freds book
  distribution service accomplished!
• Reused HTTP application to get on the bus!
• No Sonic client code required
• Supported their own XML format
• Deploy ESB out-of-box transformation
• Re-used BRU architecture for the integration
• NO changes to BRU inventory application.

28
BRU integration futures/options

• Using their integration platform, BRU now has the
  ability to add connectivity to hundreds of other
  applications like
• Pre-packaged applications
• SAP, Oracle, Siebel
• Technologies
• Web services (HTTP/SOAP)
• FTP, Email
• .Net Applications

29
Agenda

• Current Integration Landscape
• Sonic ESB Integration Solution
• Sonic ESB Nuts and Bolts
• Demonstration OE and Sonic ESB
• Conclusions

30
Summary
What have you seen today?

• Sonic ESB
• Intelligent Messaging Implemented!
• OpenEdge and Sonic ESB
• Easily used together using existing
• Resources
• Knowledge

31
Summary
What have you seen today?

• Unlike traditional integration solutions
  OpenEdge/Sonic ESB integration is
• Reliable, scalable and secure
• Reusable solution
• Enables incremental OE integration
• Connecting from OE is easy!
• Once you are on the ESB, integration is
  configuration, not coding.

32
(No Transcript)