Progress Appserver

1
Progress Appserver
Marcela Martinez
Partner Boot Camp, Julio 2008
2
Introduction to OpenEdge Integration
Technologies
Marcela Martinez
Partner Boot Camp, Julio 2008
3
Agenda
Introduction to OpenEdge Integration Technologies

• Reasons to Integrate
• Outgoing Integration
• Incoming Integration
• Choosing The Right Approach

4
Business Environment Highly Susceptible to Change

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

5
The IT Reality
Business
Requirements
IT Systems
Time
Constant changes reduces the ability to respond
6
Agenda
Introduction to OpenEdge Integration Technologies

• Reasons to Integrate
• Outgoing Integration
• Incoming Integration
• Choosing The Right Approach

7
Integration (?)
COM / ActiveX
Web service
Flat File
Process
Oracle
MS SQL
ODBC
8
Usability Legend

• Ease of Implementation
• Susceptible to Change
• Future Ready

E
E
E
C
C
C
F
F
F
9
Outgoing Flat File
E
C
F

• ABL Developers
• Interpret File Format
• IMPORT / EXPORT
• INPUT FROM / OUTPUT TO
• PUT
• READ-XML() / WRITE-XML()
• OpenEdge 10.1A

10
Outgoing Process
E
C
F

• ABL Developers
• Interpret Process Input / Output Format
• INPUT THROUGH / OUTPUT THROUGH
• External processes are platform dependant!

11
Outgoing Sockets

• ABL Developers
• Socket Management
• Implement Custom Protocol
• Remote System Developers
• Implement Custom Protocol
• Progress 9.1A / OpenEdge 10.0B

12
Outgoing Flat File
E
C
F

• ABL Developers
• Interpret File Format
• IMPORT / EXPORT
• INPUT FROM / OUTPUT TO
• PUT
• READ-XML() / WRITE-XML()
• OpenEdge 10.1A

13
Outgoing Process
E
C
F

• ABL Developers
• Interpret Process Input / Output Format
• INPUT THROUGH / OUTPUT THROUGH
• External processes are platform dependant!

14
Outgoing Sockets

• ABL Developers
• Socket Management
• Implement Custom Protocol
• Remote System Developers
• Implement Custom Protocol
• Progress 9.1A / OpenEdge 10.0B

15
Outgoing Sockets
E
C
F

• Typical Uses
• FTP
• HTTP
• SMTP
• Special needs
• Performance
• Non-Standard protocol

16
Outgoing COM / ActiveX
E
C
F

• 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

17
Outgoing Web Service
E
C
F

• Web service HTTP SOAP
• ABL Developers
• Connection Management
• Very similar to calling OpenEdge AppServer
• Interpret WSDL
• bprowsdldoc creates sample code

18
Outgoing SonicMQ
E
C
F

• ABL Developers
• JMS Connection Management
• Produce/Consume SonicMQ Messages
• Offers
• Guaranteed Delivery
• Message ordering

19
Outgoing Sonic ESB
E
C
F

• 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

20
Outgoing Data Server
E
C
F

• 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

21
Outgoing Integration Overview

E
C
F
E
C
F
E
C
F
E
C
F
C
F
E
C
F
E
E
C
F
C
F
E
22
Agenda
Introduction to OpenEdge Integration Technologies

• Reasons to Integrate
• Outgoing Integration
• Incoming Integration
• Choosing The Right Approach

23
Incoming Integration
Java
Web service
ODBC / JDBC
24
Incoming .Net /Java
E
C
F

• ABL Developers
• Proxy Gen
• Distribute proxies
• .Net / Java Developers
• Use proxies
• No special coding

25
Incoming Web Services
E
C
F

• ABL Developers
• Proxy Gen
• Distribute WSDL
• Remote System Developers
• Use Web Service
• No Special Coding

26
Incoming Sonic ESB
E
C
F

• ABL Developers
• Create Code
• Directly deployed into Sonic ESB
• Remote System Developers
• Use easiest approach
• SonicMQ, Other JMS, Web service, File Drop, DB
  Event, Email, many more...

27
Incoming ODBC / JDBC
E
C
F

• ABL Developers
• Do Nothing
• Remote System Developers
• Understand Database Schema
• Replicate ABL Logic

28
Incoming Integration Overview

E
C
F
C
F
E
E
C
F
E
C
F
29
Common Business Logic
AppServer is a fundamental component of SOA

• AppServer Center of the business logic universe
• Ways to access business logic
• OpenEdge Clients (GUI, TTY, Batch)
• WebClient
• WebSpeed Clients
• Microsoft .NET Open Clients
• Java Open Clients
• Web Service Clients
• OpenEdge Adapter for SonicMQ and Sonic ESB

Clients may include either a user interface or a
service interface
30
OpenEdge Application Server Clients
Accessing the AppServer from Anywhere and
Everywhere
Web Service
31
New Application (Services and Open Edge Reference
Architecture - OERA)

• The OpenEdge Reference Architecture is a Service
  Oriented Architecture (SOA)

Enterprise Services
Presentation
Business Components
Common Infrastructure
Data Access
Data Sources
32
Calls from Business Components out to other
services
Enterprise Services
Presentation
Somebodys Web service
Business Components
Common Infrastructure
Data Access
Data Sources
33
Service Interface in OERA

• Create a procedure for each operation to expose
  as a wrapper for a Web service
• Package any code needed for the service to be
  called from that Service Interface

Service Manager
Enterprise Services
Presentation
INPUTs and OUTPUTs
Security Manager
Business Components
Common Infrastructure
Data Access
Data Sources
34
Applications already created
Stages of creating services in your application

• Think about the goal of loosely-coupled services
• Right-size your services for reuse potential
• Learn by picking key areas for initial services
• Move on to more robust architected services
• Use services to transform and optimize the nature
  of your business

35
Services !

• Extend the value of your application with
  services
• Take advantage of OpenEdge support for Web
  services
• Package key parts of your application as reusable
  services

36
Agenda
Introduction to OpenEdge Integration Technologies

• Reasons to Integrate
• Incoming Integration
• Outgoing Integration
• Choosing The Right Approach

37
IT Dilemma The Accidental Architecture
Inability to Respond

• Proprietary technologies
• and skill sets
• Multiple communication
• infrastructures
• High cost of license,
• consulting and operation
• Lots of turf control and
• organizational issues

ORDERENTRY
CRM
ERP
PARTNER SYSTEMS
FINANCE
38
IT Architecture Requirements

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

Built to Change
39
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.
40
It Has Been Tried Before
Easier for Programmers API Focused

• CORBA
• Microsoft DCOM
• Java RMI
• .NET Remoting
• DCE
• EJB

41
How is SOA Different?
Easier for Business Analysts Document Focused

• 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.

42
SOA Its Not a Thing
Its not a

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

An Approach for Building Agile and Flexible
Business Applications
43
The Typical Path with OpenEdge
Everyone needs integration.Some will need
integrationmanagement.

• Assumes that ESB or messaging opportunity exists
• Assumes reasonable ability to control competition

44
Paths without OpenEdge
StandardSonicCentricOpportunity.
Special application-specific use case
Leveraging account access and relationship only
Standard integration needs covered, butqualified
use case for semantic integration
45
Facing the Trends
Expressing Value in a Question

• What if you could have the ability to share
  business processes throughout your company
  reducing redundancy and improving agility?
• What if you could seamlessly share information
  across your organization?
• What if you could monitor and control business
  events as they happen?

46
Benefits of SOA
Revenue

• New markets, channels, new value from existing
  systems

• Support flexible business models enabled by
  services and technology- agnostic approach

Flexibility

• Reuse pre-built and next generation service
  components for rapid deployment in response to
  market opportunity

Speed

• Integrate disparate systems from legacy, mergers
  / acquisitions
• Automate key business processes
• Resources working toward the same strategic IT
  agenda

Efficiency

• Offer new services to customers and partners
  leveraging existing IT infrastructure

Service

• Eliminate duplicate systems, build once and
  leverage

Cost
Risk

• Improve visibility into business operations

47
Why is Sonic ESB a better choice?

• An OpenEdge/Sonic ESB integration features
• Real-time integration that works all the time
• Just like you never touched the application!
• One-time and standardized ABL coding gets you
  started
• Reused for all future integrations.
• New integrations added incrementally without
• Redeploying applications
• Bringing the systems down

48
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

49
?
Questions
50
Thank You
51
(No Transcript)