SOA-08 Real Life Web Services Drew McCarthy, Principal Product Manager Jay Dennis, VP R&D, gomembers...

SOA-08 Real Life Web Services

Drew McCarthy, Principal Product ManagerJay Dennis, VP R&D, gomembersAllan Green, VP CTO, NeoSynergy

2 SOA-08, Real Life Web Services© 2005 Progress Software Corporation

Agenda

Introduction Where are Web services going? Why Web Services?

– Case #1 – Allan Green, VP Chief Technology Officer, NeoSynergy

– Case #2 - Jay Dennis, VP Research and Development, gomembers

Wrap-up


Introduction

In today’s talk you should learn a bit about:– What the analysts are saying

– Where Web services are being used

– How your peers are using Web services

– What you might do with Web services

Time for a quick poll.


App Trends- What the Analysts Are Saying?

Out by 2007 In by 2010

Source: Dave Mitchell Smith, Gartner

Just Coding Architecture and Assembly

Application Expertise Business Process Expertise

Traditional Consulting and SI Infrastructure, Application and Process Utilities

Packaged Applications (as we currently know them)

Service-Oriented Business Applications

SIs as Principal Software Channel

Outsourcers, Utility and Sis as Software Channels

Best of Breed Mass Customization

Startups Vendors of Scale


Where Are Web Services Being Used?

63% of Web services solutions are used for intra-company integration

Average payback for a Web services solution in a business application project = 16 months

68% of Web services engagements involve less than 10 Web services

31% of Web services engagements involve 10 to 100 Web services

A Gartner survey


Web Services Will Grow

Revenue for Web services-enabled software and professional services will grow from $61 billion in 2003 to $316 billion in 2007 (0.7 probability)

41 percent of business software purchased in 2007 will be Web services-enabled (0.8 probability)

Services will grow at a compound annual growth rate of more than 61 percent over the next four years (0.8 probability)

Gartner predicts:


Web Services in OpenEdge™ 10

Applications on OpenEdge 10 can both host and call Web services.

– Logic on the Application Server can be offered as a Web service

– 4GL clients can call out to a Web service


POST(Soap)

Response(Soap)

Web Services Enabled Application Server

BusinessLogic

Web Service Client

HT

TP

L

iste

ner

Web Server/JSE

Web

Ser

vice

s A

dap

ter

WSAD

AppServer

WSDLubroker.properties

OpenEdge 10 - based on Open Client technology


POST(Soap)

Response(Soap)

Accessing a Web Service From the Progress 4GL

Web ServiceOpenEdge Client

4G

L

Ap

plic

atio

n

HT

TP

Tra

nsp

ort

SO

AP

Pro

cess

or

WSDL

OpenEdge 10 - identical to calling an Application Server procedure

hdl:CONNECT(“-wsdl http://api.google.com/GoogleSearch.wsdl”)


A Quote

Allan Green,NeoSynergy

“I am actually very impressed with the way in which Progress has implemented Web Services in the development environment. We as a company had no experience at all in this arena, and Progress certainly made it a very simple task to expose our application to Web Services. .”


Case #1

Allan Green, VP Chief Technology Officer, NeoSynergy


Web Services Outline

Introduction to NeoSynergy Business Drivers Technology Alternatives

Considered Architecture & Technical

Considerations Benefits & Lessons Learned


Darwin XE Application

Complete Dealer Management System (DMS) including financials, parts and vehicle inventory, service costing and embedded CRM

Numerous integration points into the OEM’s and other 3rd parties using Sonic

B2B and B2C applications for wholesale parts ordering and vehicle sales on the internet


The Business Problem We Faced

Existing application used WebClient™ and AppServer™ (18 months development).

Move functionality from the dealership showroom to the internet

Develop and deploy a complex application – Consumer could purchase a vehicle

entirely on the internet.

– Very stringent business rules.


The Business Problem We Faced

Allow 3rd party web sites that do vehicle sales access to our application

Integrate 3rd party payroll module Solve asynchronous integration issues

with our Sonic application Access 3rd Party Data suppliers.

– VIN decoding and vehicle options

– Used car valuations


Architecture and Technology

Used ProxyGen to expose AppServer procedures as Web Services– Extract live vehicle data– Process consumer offers and counter

offers– Finalize the deal

Other Web services from within the 4GL – Validate address information – Process credit card payments


Architecture and Technology

Exposed other procedures as a Web Service to Sonic – process inbound messages from integration

partners– parts order and warranty claim

Exposed the General Ledger update routines to Payroll On-Line for payroll integration

Use other Web Services from within the 4GL – extended VIN decoding and Vehicle options (Jato

Data and Chrome) – used car valuations (NADA)


Benefits and Lessons Learned

We worked on the assumption that Progress would deliver what they said they would with Web Services, and everything just fell into place when they did

With the new applications our customers are deriving benefits from areas they never thought possible


Case #2 Introduction

Jay Dennis, VP Research and Development, gomembers


gomembers Outline

Introduction to gomembers Business Drivers Technology Alternatives

Considered Architecture & Technical

Considerations Benefits & Lessons Learned


Introduction

25 Yrs Practicing Software Development – Pre-IBM PC (1980)– Mini-Computer Environment

Homogonous hardware and O/S Minimal integration required CRM, ERP, Logistics and EDI

applications

– To MEI / gomembers – 1992 Unix Netscape


Company & Application

gomembers, Inc. – 25+ yr history – Acquisition of 4 companies with 4 legacy applications (2001)

Application – Integrated CRM - e-Commerce –

Accounting


Company & Application

Product Tool / Architecture History – Wang hardware, O/S and development

environment – 1980’s– IBM–Redback, COBOL, Pervasive SQL,

Cynergy, Btrieve – 1980’s– Progress tools

Character-based - 1990 Client Server (C/S) - 1994 C/S with Cold Fusion / Java Business

Objects e-Commerce – 1999 Web Services, Open Edge, Microsoft .NET -

2003


Business Drivers

External – Customer Need for Updated Enterprise Application

New technology – industry standard Better integration

– Competitor Product Offerings .NET Time to Market - need to catch and pass competitors

quickly Internal

– Cost of R&D and to Support 4 Legacy Products Combine legacy functionality from 4 products Replace legacy technologies

– Cost of Sales


Other Business Drivers

Microsoft-Centric Vertical Market

– Trade and professional association customers

– Microsoft office suite widely used Word, Excel, Exchange

Need to Integrate with Best-of-Breed Products

– 3rd party accounting, 3rd party broadcast Email and many others

Risk Adverse – Late Adopters of Technology Co-Development Clients


Technology Alternatives Considered

Sun – Java– Limited expertise– Not widely used in our vertical market

IBM – WebSphere– No expertise – Cost of Sales issues

Microsoft - .NET™ – Some ASP and VB experience– Widely used in our vertical market – Compatible with legacy Progress code with some revision

Progress - OpenEdge– Extensive Progress 4GL experience– Ability to reuse Progress legacy code with some

modification– Extensions and integration Microsoft .NET


Technology SelectedThe Intersection of ………..

Progress - OpenEdge – Reuse Progress business logic– C# Proxies for Microsoft

integration – Web Services– Pro Data Sets– Progress database – Progress schema holder for SQL

Server use Microsoft - .NET

– C# and Visual Studio .NET development environment

– Web Services – Data Sets– SQL Server database

&


Architecture & Technical Considerations

Reusable Development – Core application – Q – Integrated e-Commerce

elements– Building blocks for

customizations – Co-Development by

customers User Definable User

Interface (UIB) Metadata layer

– Simplify very large and complex database

– Object definition

AnalyticalProcessing

ClientProcessing

BusinessProcessing

Dev

elo

pm

ent

En

viro

nm

ent

Data Management

Application Server

Integration

Application Framework

Ap

pli

cati

on

Man

agem

ent

Applications

XML

(SOAP)

Business Logic Layer Data Access Layer

Common Components

Q Proxies• Retrieve• QCommit

Progress

Database

SQL Server

Database

App Server

Business Objects• Person• Organization• Address• etc

Peripheral Objects• QField• Search Result• etc.

Data Layer

Business Data(DataSet Wrapper)

Data Access Agent

• Retrieve Data (Call QRetrieve)

• Save/Insert Data (Call QCommit)

Web Services

QCommerce Web Service

Office Web Service

Browser

MS Office Applications

QCommerce

IIS

IIS

Sec

uri

ty L

ayer

Security Layer

Pro-DataSet

DataSet

• Message Levels• Select Criteria Operators• User Info

XML

(SOAP)

HTML

HTTP Request

Q Architecture Diagram (Web Services)

HT

ML

HT

TP

Req

uest

XML

(SOAP)

UI Layer Business Logic Layer Data Access Layer

Common Components

Q Proxies• QRetrieve• QCommit

Progress

Database

SQL Server

Database

App Server

Business Objects• Person• Organization• Address• etc

Peripheral Objects• QField• Search Result• etc.

Data Layer

Web Controls• Q Form• View Grid• Lookup Grid

Business Data(DataSet Wrapper)

Data Access Agent

• Retrieve Data (Call QRetrieve)

• Save/Insert Data (Call QCommit)

Web Services

QCommerce Web Service

Office Web Service

Browser

MS Office Applications

QCommerce

IIS

IIS

Sec

uri

ty L

ayer

Security Layer

Pro-DataSet

DataSet

IIS

XML UL DefinitionFiles• Form XML• View XML• Lookup XML• Metadata XML

HTML Resources• Javascript• Style Sheet• Images

Web Pages (aspx pages)• Maintenance Page• Home Page• Search Page

• Message Levels• Select Criteria Operators• User Info

HTML

HT

ML

HT

TP

Req

uest

XML

(SOAP)

HTML

HTTP Request

Q Architecture Diagram (Web Services and Core Application)

HT

ML

HTTP Request

HT

TP

Req

uest


Rapid Development: Major Success!

July Oct Jan March April

Demo at User Conference

Build Beta

Progress Open Edge Release

2003 2004 2005

1st Q Production Release

Live Customers


Benefits & Lessons Learned

Reusable Business Logic - Web Service– E-Commerce – Customizations – Co-Development

Easy Integration – Microsoft office suite (Word, Excel,

Exchange) – 3rd party accounting, broadcast

email and other products Ability to Create Hybrid application –

Q – Progress 4GL (C/S) – Progress OpenEdge – Microsoft .NET


In Summary

Progress has made using Web Services easy to do

Customers are using them now Analysts are predicting rapid growth You should consider if they are right

for your business and start planning now


Questions?


Thank you for your time!

SOA-08 Real Life Web Services Drew McCarthy, Principal Product Manager Jay Dennis, VP R&D, gomembers...

Documents

Transcript of SOA-08 Real Life Web Services Drew McCarthy, Principal Product Manager Jay Dennis, VP R&D, gomembers...