Can web services help integration
Download
1 / 15

Can WEB Services help Integration? - PowerPoint PPT Presentation


  • 64 Views
  • Uploaded on

Can WEB Services help Integration?. Some results from experiments carried in Product development. The Starting Point. SchlumbergerSema is ready to deliver J2EE Components-based products to the market place.

loader
I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
capcha
Download Presentation

PowerPoint Slideshow about ' Can WEB Services help Integration?' - maxine-dyer


An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript
Can web services help integration

Can WEB Services help Integration?

Some results from experiments carried in Product development

A. Zahm


The starting point
The Starting Point

  • SchlumbergerSema is ready to deliver J2EE Components-based products to the market place.

  • These products take benefit of several years of development experience in the Distributed Objects Environments: CORBA FORTE

  • After having worked on the business logic part of the application, as a service oriented company we had to focus on the integration of part. That is where Web Services came into the picture

A. Zahm


Start with a good architecture

Web Server

Generic Servlet

Business Component

Back-Office

Business Process Manager

Page Rendering

Module

Business Component

DB

Context Manager

Business Component

Presentation layer

Process layer

Business layer

Resource layer

Start with a good architecture

A. Zahm


Architecture story

Interface

Interface

Interface

Interface

Object

Object

Object

Object

DB

Architecture Story

  • From Data Centric to Service Oriented

A. Zahm


Architecture story1

Interface

Interface

Interface

Interface

Object

Object

Object

Object

DB

Architecture Story

Business Logic

A. Zahm


Architecture story2

Business Logic

Interface

Interface

Interface

Object

Object

Object

Object

Architecture Story

DB

A. Zahm


And web services

And WEB Services?

Where do they getting used?

A. Zahm


What is our integration need
What is our integration need?

Integrated Business Process

CRM

Rating

Billing

Products

Catalog

A. Zahm


What do we take
What do we take?

ü

ü

A. Zahm


What do we expect
What do we expect?

  • Problems

    • In light of early experiments, Service Description and Registry is not as simple as thought when dealing with complex services.

    • There are « programming » rules to respect in calls sequence.

    • We are not yet in an Open World. We are not building On Demand Managed Services

    • Performance is still an issue there

  • Standards

A. Zahm


Interface design paradox
Interface Design Paradox

  • Object Orientation brought strong typed interface (remember C vs. C++ battle?)

    • Much cleaner

    • Better compile time control

    • Easier to maintain

  • Strong typing means less run-time flexibility

    • Interface modification even though simple to do requires application modification.

  • Our customers do not afford to spend time on minor changes.

  • Lets use format based (XML) data exchange

    • No strong typing anymore

    • Harder to maintain

A. Zahm


Simple interface
Simple Interface

  • Do(Command, Input, Output, Errors)

  • Do(String, String, String, String)

A. Zahm


Simple to define
Simple to define…

  • Everything is formatted strings

    • Very simple concept

    • Simple definition rules

  • EAI integration is facilitated

    • Build connectors by constraining the possible values

    • The missing control at compile time is performed by EAI

  • Simple to debug

    • Print string

A. Zahm


Hard to maintain
…hard to maintain

  • No control at Compile time

    • Everything is one type

    • Typos are not detected by the compiler

  • Error tracking Headache

    • Where is the problem coming from?

      • Configuration?

      • Deployment?

      • Coding?

    • How to trace?

      • DTD/Schema: slow

A. Zahm


So what
So what?

  • Yes it seems an alternative to expansive EAI tools

  • Yes Web Services still need improvement

  • No we don’t deploy them on large scale project

  • But we move forward

    • R&D

    • Friendly partners

A. Zahm


ad