SOA-8: Orchestrate your OpenEdge® Applications with Sonic OpenEdge and the Bus... Jiri De Jagere Product Consultant

SOA-8: Orchestrate your OpenEdge® Applications with Sonic

OpenEdge and the Bus ...

Jiri De JagereProduct Consultant

© 2006 Progress Software Corporation2SOA-8: Orchestrate your OpenEdge Applications with Sonic

Session Goals

Introduction of Sonic products How can the ABL interact with Sonic? What advantages do Sonic technologies

offer?

Orchestrate your OpenEdge Applications with Sonic


Sonic Integration Suite

TransportationTransportation IntegrationIntegration OrchestrationOrchestration


Java Message Service

Industry-standard messaging specification• Developed by Sun and other leading vendors• Required component in J2EE 1.3

Common set of APIs and semantics• Publish and Subscribe• Point-to-Point• Synchronous and Asynchronous message delivery

Message delivery Quality of Service (QoS)• Guaranteed• Once-and-only-once• At-most-once

Deployment architecture not addressed• Vendor implementations not created equal

What is JMS?


Messaging Domains

Reservations

Ticketing

Order fulfillment

Online trading

Point to Point

SenderSenderSenderSenderPotentialPotentialReceiverReceiver

PotentialPotentialReceiverReceiver



QueueQueueQueueQueue

Stock ticker

Price changes

Catalog updates

Data replication

Publish and Subscribe

PublisherPublisherPublisherPublisher TopicTopicTopicTopic

SubscriberSubscriberSubscriberSubscriber

SubscriberSubscriberSubscriberSubscriber


SonicMQ

1-SubscribePublisherPublisher

Inventory

7-Publish()method returns

2-Disconnect

5-Message retained in persistent store

8-Connect

10-Receive

4-Persist

6-Ack

3-Send

9-Retrieve

SubscriberSubscriber

Retail

Ensures Reliable Messaging

Guaranteed Delivery

RecoveryLog

RecoveryLog


Infrastructure in Detail

Reliability• Once and only once• 2-phase transactions• High connection availability

Scalability• Multi-threaded architecture• Clusters• Dynamic Routing

Architecture™• Connection Management

Manageability• Manage and configure centrally• Pluggable security • Extensive connectivity

Sonic Infrastructure Messaging

Architected for high capacity*• Connections > 2000• Destinations > 80,000• Messages > 8,000/s

(persistent)• Latency < 10ms

Actual figures depend on environment

Encryption

• Built-in payload encryption

– Secure messaging without performance cost of SSL

• Channel encryption

– SSL with up to 168-bit keys Authentication

• Built-in username/password authentication

• Supports digital certificates for user authentication

Authorization

• Specify rights of authenticated users

• Exploit destination hierarchies and groups of users to simplify administration

Firewall-friendly

• HTTP, SSL, HTTPS, TCP Range of deployment options

• Hardened for deployment in DMZ

• Deploy internally in conjunction with proxy servers

SonicMQ JMS Client APIs

• Java™/J2EE, COM/.NET™, C/C++ and Progress ABL

DRA

• Connection will be established when needed

• Flexible Security Scheme

• Not only for WAN but also inter-department


Continuous Availability Architecture (CAA™)

When communication broker fails

SHARED STORAGE

CONVENTIONAL FAILOVER

HARDWARECLUSTER SP

CLIENT

– Minutes to rebuild and recover– Client rolls back failed TXN– Expensive 3rd-party SW & HW– High cost to build and admin

CLIENT

SP

SONIC CAA

REAL-TIMEREPLICATION

– Seconds to resume– Transparent to client– No 3rd-party HA products needed– Simple and flexible

CLIENTS


OpenEdge with SonicMQ

ABL Client

ABL Client

ABL BL

ABL BL

SonicMQSonicMQ®®

Asynchronous Availability?

• What if Appserver™ goes down while processing?

• What if Appserver is down while making request?

• What if ... ? Unreliable Network

• Network crashes while Appserver is processing?

Management/monitoring?

• Monitor traffic?

• Logging? Other Client (non-progress)? Server to (many) clients?

OpenEdge Adapter for SonicMQ


OpenEdge with SonicMQ

OpenEdge SonicMQ Adapter prior to OpenEdge 10.1A

• Needed to be configured as a service• All 4GL clients need to use this server process

for sending messages

4GL Client

4GL Client

OpenEdge Adapter

for SonicMQ

SonicMQ Broker


OpenEdge 10.1A with SonicMQ

OpenEdge Adapter for SonicMQ ClientConnect

• No need to configure this as a service• Greater scalability and flexibility• Fault tolerance, client persistence, ...

SonicMQ Broker

ABL Client

ABL Run-time

ABL Client Library

“-SMQConnect”

Adapter for Sonic MQ sub-process


OpenEdge 10.1A with SonicMQ

OpenEdge Adapter for SonicMQ ServerConnect

• Same as ClientConnect• Better resource sharing

SonicMQ Broker

OE AppServer

ABL Engine

ABL Server Library

“-SMQConnect”

Adapter for Sonic MQ sub-process

ABL Client

ABL Run-time

ABL Client Library





Example of accidental architecture

ABL Sales

Application

ABL Inventory

Application

XML ASCII


What if it gets a little more complex?

XML ASCII

ABL Sales

Application

ABL

InventoryApplication

Other ABL Application

CSV

FTP

Visual Basic Application

COBOL JAVAApplication

.NET Application


We’re not there yet...

• User security & Maintenance?

• Guaranteed availability of your application (SLA)

• How much time to implement a new interface?

• I have a new end user interface (HTML) that wants an immediate response

• I need centralized logging...

• I need REAL-TIME information

ABL Sales

Application

ABL

InventoryApplication

XML ASCII

Other ABL Application

CSV

FTP

Visual Basic

Application

COBOL JAVAApplicatio

n

.NET Applicatio

n


Accidental Architecture

Proprietary technologies and skill sets Multiple communication infrastructures High cost of license, consulting and ownership Complexity of inter-organizational collaboration

Rigid, Costly and Difficult to Operate Islands of integration


Use XML where you can

Eliminates fixed formats

Makes files self-describing

Can be extended without breaking

Universally understood

Start with Best Practices from Traditional Integration


Define an interface for your service

Provides standards-based services interface

Hides implementation details

Enables reuse

Add New Standards-based (Web) Services


Get process logic out of your app

Provides standards-based services interface

Designed for distributed functionality

Hides implementation details

Enables reuse

Add New Standards-based (Web) Services


Deploy an Enterprise Service Bus

Reliably Connect and Coordinate Services

Reliable communications backbone Service-oriented architecture (SOA) Intelligent routing XML transformation Extensible network


ESB - an evolutionary project model

Use an evolutionary project model Use the ESB as it was designed - for incremental integration Deploy only what you need Re-use as much as feasible Avoid political and ownership issues Multiple ESB Projects


Demonstration

OpenEdge on the bus …


Sample Scenario Part 1

We have an existing company that is capable of sending information on Media Titles to different applications.

Titles will be displayed in the application depending on their type.

We implemented this on the ESB because we wanted to avoid the Accidental Architecture.

CBR



Our Partner wants to re-use the end application• It is a French company which results in different XML

• They only make files available through the FTP protocol

Challenge• Re-use the existing software

• Easy deployment

• FTP Adapter

FTP CBRXSLT



A second partner wants to use the same end applications• Customer is only willing to communicate over e-Mail• Customer is sending 1 file with multiple titles and types

Challenge• Re-Use the end application• Connect to a mail system• Split the message into multiple messages

E-Mail CBRXSLT



A third partner wants to use the same end applications• Customer is only willing to use IE.

• Customer is calling a post on the IE Form

Challenge• Re-Use the end application

• Communicate using HTTP

• Convert the message from IE format to XML

CBRHTTP



We would like to have all the transmitted titles and media-types in a database

The database represents a client implementation at the receiving level

Challenge

• The database service environment is not always on-line

• The data needs to be reachable from the web through an OpenEdge service

CBR

RDBMS

DB Service





Sonic ESB® (enterprise service bus)


Sonic Orchestration Server®


OrchServer

PoS

SFAERP

SCM

Front Office

Sonic Orchestration Server

ESB-enabled Process Modeling Process Execution Business Process Monitoring

Finance

SCM

AdapterCRM

TrackingService

Adapter

Orchestrate and Monitor Sophisticated Business Processes

PartnerBack Office

Field CRM

Right Front Corner

Note to designer...this linerepresents the break

between the two sections ofthe orchestration layer (right

side starts here)

Note to designer...this linerepresents the break

between the two sections ofthe orchestration layer (left

side starts here)



SONIC ORCHESTRATION SERVER

Call

Finish

Finish

Join

Decision

Process

BackOrder

Reject

SplitFinish

Priority

Credit

Availability

Process Model



Finish

Finish

Join

Decision

Process


BackOrder

Reject

SplitCallFinish

Priority

Credit

Availability



Finish

Finish

Join

Decision

Process


BackOrder

Reject

SplitCallFinish

Priority

Credit

Availability



Finish

Finish

Join

Decision

Process


BackOrder

Reject

SplitCallFinish

Priority

Credit

Availability


Demonstration

Orchestrate your OpenEdge Apps …


In Summary

SOA is a process…you can take it step by step…BUT you have to start stepping!

ESB provides you with lot’s of things OUT-OF-THE-BOX. Don’t try to reinvent the wheel...

This is proven technology! We have programs and design patterns to migrate to SOA / ESB architectures.


For More Information, go to…

OpenEdge Integration Portfolio• http://www.progress.com/products/integrate/index.ssp

Sonic Product Suite• http://www.sonicsoftware.com/


Relevant Exchange Sessions

SOA-1 Fundamentals of an SOA

Rob Straight

SOA-2 OpenEdge 10.1A Adapters for Sonic MQ

Cheryl Labarge

SOA-4 Introducing Sonic SOA Suite 7.0

Paul Moxon

SOA-7 Designing Sonic ESB services and processes for the OpenEdge Developer

Dave Cleary


Education References

XML Essentials 4GL Development with XML OpenEdge Development with Sonic ESB What’s new in OpenEdge 10.1A: Sonic

Integration Opening 4GL Applications to Web Services

Clients


Questions?


Thank you foryour time


Documents

SOA-8: Orchestrate your OpenEdge® Applications with Sonic OpenEdge and the Bus... Jiri De Jagere Product Consultant