C2: Introduction to OpenEdge ® Integration Technologies Chris James Senior Consultant.

Post on 26-Mar-2015

216 Views

Category:

Documents

0 Downloads

Preview:

Click to see full reader

Transcript

C2: Introduction to OpenEdge® Integration Technologies

Chris JamesSenior Consultant

© 2008 Progress Software Corporation2

Agenda

Reasons to Integrate Outgoing Integration Incoming Integration Choosing The Right Approach

Introduction to OpenEdge Integration Technologies

© 2008 Progress Software Corporation3

Business Environment Highly Susceptible to Change

Customer Demands Competition Mergers & Acquisitions Divestitures Business Partners Technology Business Expansion Drive for Cost Efficiency

© 2008 Progress Software Corporation4

The IT RealityR

equ

irem

ent

s

Time

IT Systems

Business

Constant changes reduces the ability to respond

© 2008 Progress Software Corporation5

Agenda

Reasons to Integrate Outgoing Integration Incoming Integration Choosing The Right Approach

Introduction to OpenEdge Integration Technologies

© 2008 Progress Software Corporation6

Outgoing Integration

OpenEdge App

DBDB

ABLABL

UI

Web service

ODBCODBCOracle®Oracle® MSSQLMS

SQL

COM / ActiveX

SonicMQ®/Sonic™ ESB

Process

FlatFile

© 2008 Progress Software Corporation7

Usability Legend

Ease of Implementation

Suseptible to Change

Future Ready

E E E

C C C

F F F

© 2008 Progress Software Corporation8

Outgoing – Flat File

ABL Developers Interpret File Format

IMPORT / EXPORT

INPUT FROM / OUTPUT TO

PUT

READ-XML()* / WRITE-XML()*

* OpenEdge 10.1A

E C F

© 2008 Progress Software Corporation9

Outgoing – Process

ABL Developers Interpret Process Input / Output Format

INPUT THROUGH / OUTPUT THROUGH

External processes are platform dependent!

E C F

© 2008 Progress Software Corporation10

Outgoing – Sockets*

ABL Developers Socket Management Implement Custom Protocol

Remote System Developers Implement Custom Protocol

* Progress 9.1A / OpenEdge 10.0B

© 2008 Progress Software Corporation11

Outgoing – Sockets

Typical Uses• FTP

• HTTP

• SMTP

• Special needs:– Performance– Non-Standard protocol

E C F

© 2008 Progress Software Corporation12

Outgoing – COM / ActiveX*

ABL Developers Instantiate & Use COM objects Embed ActiveX component in GUI

• Program for each event / method

Typical Uses• Custom GUI Objects

• Word Processing, Spreadsheets, Email

*Primarily Windows – otherwise very limited support

E C F

© 2008 Progress Software Corporation13

Outgoing – .Net*

ABL Developers Embed existing .Net components Requires a little OOABL programming

Typical Uses Custom GUI Objects Custom .Net Objects

*Supported only on Windows

*Requires OpenEdge 10.2A (not yet released)

E C F

© 2008 Progress Software Corporation14

Outgoing – Web Service

Web service = HTTP + SOAP

ABL Developers Connection Management

• Very similar to calling OpenEdge AppServer™

Interpret WSDL• bprowsdldoc creates sample code

E C F

© 2008 Progress Software Corporation15

Outgoing – SonicMQ

ABL Developers JMS Connection Management Produce/Consume SonicMQ Messages

Offers Guaranteed Delivery Message ordering

E C F

© 2008 Progress Software Corporation16

Outgoing – Sonic ESB

ABL Developers Produce/Consume SonicMQ Messages Call ESB hosted Web service

Offers Application independant connection to basically

anything*

*JMS, WebService, FTP, Email, HTTP, 100+ Apps

E C F

© 2008 Progress Software Corporation17

Outgoing – Data Server

ABL Developers Either: Tweak data access

• Existing code will just work...

• ...but maybe not efficiently

Or: Reimplement foreign business logic

Oracle, MS/SQL, other ODBC

E C F

© 2008 Progress Software Corporation18

Outgoing Integration Overview

ImplementationApproach

Ease ofImplementation

Suseptibility toChange

Future Ready

Flat File

Process

Sockets

COM / ActiveX

.Net

Web Services

SonicMQ

Sonic ESB

Data Server

E C F

E C F

E C F

E C F

E C F

E C F

E C F

E C F

C FE

© 2008 Progress Software Corporation19

Agenda

Reasons to Integrate Outgoing Integration Incoming Integration Choosing The Right Approach

Introduction to OpenEdge Integration Technologies

© 2008 Progress Software Corporation20

Incoming Integration

OpenEdge App

DBDB

AppServerApp

Server

UI

Web service

Java™

SonicMQ / ESB

ODBC / JDBC

© 2008 Progress Software Corporation21

Incoming – .Net /Java

ABL Developers Proxy Gen Distribute proxies

.Net / Java Developers Use proxies No special coding

E C F

© 2008 Progress Software Corporation22

Incoming – Web Services

ABL Developers Proxy Gen Distribute WSDL

Remote System Developers Use Web Service No Special Coding

E C F

© 2008 Progress Software Corporation23

Incoming – Sonic ESB

ABL Developers Insert Code Annotation Directly deployed into Sonic ESB

Remote System Developers Use easiest approach:

• SonicMQ, Other JMS, Web service, File Drop, DB Event, Email, many more...

E C F

© 2008 Progress Software Corporation24

Incoming – ODBC / JDBC

ABL Developers Do Nothing

Remote System Developers Understand Database Schema Replicate ABL Logic

E C F

© 2008 Progress Software Corporation25

Incoming Integration Overview

ImplementationApproach

Ease ofImplementation

Suseptibility toChange

Future Ready

.Net / Java

Web Services

Sonic ESB

ODBC / JDBC E C F

E C F

E C F

E C F

© 2008 Progress Software Corporation26

Agenda

Reasons to Integrate Incoming Integration Outgoing Integration Choosing The Right Approach

Introduction to OpenEdge Integration Technologies

© 2008 Progress Software Corporation27

IT Dilemma: “The Accidental Architecture”

Proprietary technologies

and skill sets

Multiple communication

infrastructures High cost of license,

consulting and operation

Lots of turf control and

organizational issues

CRM ERP

PARTNER SYSTEMS FINANCE

ORDERENTRY

Inability to Respond

© 2008 Progress Software Corporation28

IT Architecture Requirements

Simplicity Agility and flexibility Reusability Technology independent Promote integration Software that reflects business needs

Built to Change

© 2008 Progress Software Corporation29

Service-Oriented Architecture

An approach for building distributedcomputing systems based on encapsulating

business functions as services that can be easily accessed in a loosely coupled fashion.

© 2008 Progress Software Corporation30

It Has Been Tried Before

CORBA Microsoft® DCOM Java RMI .NET Remoting DCE EJB

Easier for Programmers – API Focused

© 2008 Progress Software Corporation31

How is SOA Different?

Uses established distributed computing and messaging concepts

Scales-up as well as down• Department• Enterprise• Extended enterprise

Incorporates multiple communication models – events and request/reply

Driven by standards and well-known protocols, e.g. Web Services, XML, HTTP, etc.

Easier for Business Analysts – Document Focused

© 2008 Progress Software Corporation32

SOA: It’s Not a Thing

Product A specific technology An application A specific standard A specific set of rules

It’s not a:

An Approach for Building Agile and Flexible Business Applications

© 2008 Progress Software Corporation33

For More Information, go to…

C1: Applied SOA – Building Out Your SOA Environment with OpenEdge

C6: Introducing Native Invocation with the OpenEdge Adapter for Sonic ESB

Relevant OpenEdge Integration Sessions

© 2008 Progress Software Corporation34

For More Information, go to…

A3: Application Architecture Made Simple

A4: Introduction to the OpenEdge GUI for .NET

A7: Architecting Your Application in OpenEdge 10

…and many more

Relevant OpenEdge Integration Sessions

© 2008 Progress Software Corporation35

PSDN – Just some topics...

SOA Overview and Business Drivers Principles of a SOA Identifying Services in your App Access Web services from OpenEdge Patterns for Async Web service calls Building Services in OpenEdge (Overview) Exposing ABL as Web Services Messaging Patterns for OpenEdge

© 2008 Progress Software Corporation36

Documentation

OpenEdge• Installation and Configuration Guides• Application and Integration Services• Core Business Services• Messaging and ESB• Application Server Administration

© 2008 Progress Software Corporation37

Questions?

© 2008 Progress Software Corporation38

Thank You

© 2008 Progress Software Corporation39

top related