OpenEdge Integration with Sonic ESB

1
OpenEdge Integration with Sonic ESB
2
Agenda

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

3
What will you learn today?

• There is a choice to be made
• Traditional integration solutions
• Lots of code to write and maintain
• Result works 95 of the time
• Alternative Sonic ESB solution
• Code is generated and then deployed as reusable
  components
• Long term saves time and money
• Result works 100 of the time
• EASY to use from OpenEdge 4GL

4
Typical OE Integration Architecture
C/C Application
OpenEdge 4GL Application
5
Architecture Drawbacks
Todays architectures rigid, costly and difficult
to operate

• Wide-range
• technologies
• skill sets
• Multiple limited
• communications
• Single-use
• implementations
• Costly to build and operate

6
Single-use data integration
High Message Latency Not Reliable, Secure, or
Flexible
7
Single-use real-time integration
Not Reliable, Scalable, Secure, or Flexible
8
Multiple real-time single-use
RPC
RPC
RPC
Progress DB
Tons of code!
9
Traditional integration summary
Technical Pains

• Code Intensive
• Lots of code to write
• Complexity grows with each integration
• Reliability
• RPCs assume everything is running
• Hard-coded dependencies on far-flung applications
  and networks risk

10
Traditional real-time systems
Technical Pains

• Interoperability
• Limited connectivity options and platform
  concerns
• Security
• RPCs assume intra-enterprise communication
• Code your own security

11
Traditional real-time systems
Business Pains

• Revenue generating applications have greater risk
  of catastrophic failure
• Lost revenue
• Poor customer service
• Costly code driven implementation effects bottom
  line
• Higher development costs
• Higher maintenance costs

12
A step forward MOM-based real-time

• Message Oriented Middleware (MOM)
• Improves the integration situation by providing
  out-of-the box reliable communications logic
  which is
• Asynchronous or Synchronous
• Built-in security
• Reliable and and fault tolerant
• Scalable
• Interoperable

13
A step forward MOM-based real-time
Leaves coding and dependencies
14
Agenda

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

15
Introducing Sonic ESB
ESB (Sonic ESB)

• Reliable Communications
• Architecture tools to build and
• configure integration services
• Massive Connectivity to
• connect anything to anything

Progress DB
16
Introducing Sonic ESB

• Intelligent Middleware
• Integration logic leaves applications
• Replaced by generated logic that is part of a
  reliable messaging-based communications conduit
• Benefits
• Less code to write fewer
• Greater code reuse fewer
• Changes by configuration no downtime
• Dependency free applications no downtime

17
Sonic ESB Advantages

• Consolidation
• Dependable, Secure
• Scalable
• Reusable solution
• Lowers costs
• Incremental
• Begin small and work up!

18
Agenda

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

19
Sonic ESB
Intelligent Middleware Implemented

• Standards-based intelligent middleware designed
  to be a platform for integration
• Contains
• Messaging 100 reliable, scalable delivery
• Framework to build/deploy standalone and
  reusable integration logic modules
• Connectivity components
• Wide variety of integration endpoints
• Service-Oriented architectures of tomorrow

20
Sonic ESB Messaging Component

• Sonic ESB is built upon a standards-based (JMS)
  messaging implementation called SonicMQ. It
  provides

21
Sonic ESB Messaging Component

• Reliability and Scalability
• Ensures delivery no matter what the conditions
• Security
• Payload (QoP) or Channel Encryption (SSL)
• Authentication options
• Certificates (SSL)
• Built-in authentication
• Works with 3rd party authentication products

22
Sonic ESB Messaging Component

• Interoperability
• Standards-based messaging (JMS)
• Flexibility
• Supports two calling models
• Synchronous
• Asynchronous
• Contains two communication models
• Point-to-Point
• Publish/Subscribe

23
Sonic ESB Messaging
Sonic ESB
SonicMQ
Broker
Queue
Producer
Consumer
Point-to-Point (11)
24
Sonic ESB Messaging
Sonic ESB
SonicMQ
Broker
Topic
Producer
Publish/Subscribe (1n)
Consumers
25
Sonic ESB Framework

• Provides an architecture which enables the
  configuration and deployment of reusable
  integration services.
• Examples
• XML transformation
• Resolve XML message discrepancies
• Content-based routing
• Peek inside messages to validate and route
• Database Service
• Store messages directly to data store

26
Sonic ESB adds intelligence.
Sonic ESB
SonicMQ
Broker
Service
e.g. An out-of-box transformation
27
Sonic ESB services can be chained.
Sonic ESB
SonicMQ
Broker
Validation Service
Transform Service
for complex business processes
28
Sonic ESB Connectivity

• Massive Connectivity Options
• OpenEdge
• Java
• .Net (C, VB .Net)
• Web Services
• Databases and File Systems
• Application Servers
• Other messaging platforms (WebSphere MQ)
• Adapters to 100s of other pre-packed and legacy
  business applications!

29
Sonic ESB Massive Connectivity
30
OpenEdge integration with Sonic ESB
31
Sonic ESB Massive Connectivity
J2EE App Servers
Email
Sonic ESB
SonicMQ
FTP
MQSeries
Broker
OpenEdge Adapter for Sonic
Other JMS
C/C
JMS Client
Web Services
Service
Service
.Net (C, VB, etc)
Java
HTTP(S)
ESB iWay Adapters
32
(No Transcript)