RE: FW: [ebsoa] [ebsoa]: FW: the Versatile B2B gateway

["David RR Webber \(XML\)" <david@drrw.info>]

Joe,

 

I guess the obvious parallels are to CORBA all over again.

 

The key here for me - is the use of open XML mechanisms with flexiblity that are *not* dependent on Java or platform specific solutions from a particular vendor.

 

Just because you could architect things that way - replacing ebMS with JMS-style Java-based exchanges - does not necessarily mean that is ultimately the optimum solution.  Of course people can choose to do that internally between their own systems, but that should not lead to external partners having to also march to that same drum.

 

The architecture pattern we are using at NIH is highly instructive in this regard - showing how to blend web services, ebMS and queuing (Oracle JMS) to effect - to deliver a very flexible and scalable architecture.

 

I should be able to share more on that once its been formally verified and sanctioned in the New Year.

 

DW

> -------- Original Message --------
> Subject: FW:
> [ebsoa] [ebsoa]: FW: the Versatile B2B gateway
> From: "Chiusano
> Joseph" <chiusano_joseph@bah.com>
> Date: Fri, December 23, 2005
> 12:59 pm
> To: <goran.zugic@semantion.com>
> Cc: "Monica J
> Martin" <Monica.Martin@Sun.COM>, "Hamid Ben
> Malek"
> <HMalek@us.fujitsu.com>,
> <ebsoa@lists.oasis-open.org>, "Jacques
> Durand"
> <JDurand@us.fujitsu.com>, "John Hardin"
> <john@maphin.net>,
> <vasco.drecun@cpd-associates.com>
>
> Forwarding
> at the request of Monica Martin, who is an Observer and
> therefore
> cannot post. Please see "mm1" below. 
>
> Joe
>
> Joseph
> Chiusano
> Associate
> Booz Allen Hamilton
>
> 700 13th St. NW,
> Suite 1100
> Washington, DC 20005
> O: 202-508-6514  
> C:
> 202-251-0731
> Visit us online@
> http://www.boozallen.com
>
> -----Original Message-----
> From:
> Monica J Martin [mailto:Monica.Martin@Sun.COM] 
> Sent: Friday,
> December 23, 2005 12:53 PM
> To: goran.zugic@semantion.com
> Cc:
> Chiusano Joseph; Hamid Ben Malek;
> ebsoa@lists.oasis-open.org;
> Jacques Durand; John Hardin;
> vasco.drecun@cpd-associates.com
> Subject: Re: [ebsoa] [ebsoa]: FW:
> the Versatile B2B gateway
>
> goran.zugic@semantion.com
> wrote:
>
> >There are ESB-based and other SOA related products on
> the market
> supporting services orchestration and choreography and
> referencing some
> open standard-based components (WSBPEL, UDDI,
> etc,). The question is
> what level of support they provide and how
> open these solutions are. I
> do not want to argue about it
> now.
> >
> >ESB by itself is a proprietary SOA related
> component that provides
> message exchanges, message transformation
> and message routing.
> FERA-based SOA is a complete semantically-based
> SOA reference
> architecture that supports all SOA layers from message
> exchanges to
> complex service orchestrations. We recommend ESB to be
> used for some
> FERA-based SOA Gateway component functions as long as
> ESB products
> support open standard-based communications. Some people
> prefer
> combination of open-standard and proprietary protocols in
> which case ESB
> products could also be a choice for the Gateway
> support.
> >
> >Goran
> >
> mm1: Goran, I am afraid I have
> to correct / add to these statements. 
> These comments are mine
> individually (as I am only an observer to this
> list). I felt it was
> appropriate to comment on the patterns as they have
> been provided to
> ebxml-jc.
>
>   1. There is a standard ESB infrastructure, it's
> called Java Business
>      Integration (JSR-208). I
> think we can anticipate (regardless of
>      the
> forum) a next generation of JBI for a distributed integration
>  
>    model, further enabling this space.
>   2. ESB is
> targeted to provide a flexible ecosystem where functions
>  
>    such as orchestration and choreography may be used. ESB
> provides
>      operational underlying infrastructure
> support where those
>      functions can be effectively
> used. This brings up a general point
>      that
> allowing federation, process, policy and other capabilities
>  
>    to be available and effectively used but loosely coupled
> to the
>      infrastructure is very important.
>
> In addition, since Java One this summer, Sun has provided the
> open-esb
> on java.net.  So, the support via standards has begun
> and is evolving. 
> And, as Joe said, there are other standards that
> support processes
> (whether as procedural languages or as actual
> collaborative or
> distributed computing models).  For example,
> expect more service
> engines, that are JBI-compliant, to become
> available. Thank you.