Comments on: WebSphere ESB 6.2

By: Remy

Remy — Mon, 06 Jul 2009 12:27:25 +0000

Hi,

Thanks a lot for these clarifications. The external JMS provider
is investigated because
the ESB will be distributed over the WAN.

Rémy

By: Dave

Dave — Fri, 03 Jul 2009 20:13:46 +0000

Hi Rémy,

You are certainly correct in thinking that the system bus used by the SCA implementation for asynchronous invocations is not the “Bus” in ESB. This is merely implementation detail. The “Bus” is more of a logical concept that combines both connectivity and inter-mediation. In your case, you are choosing to use an external JMS provider to provide the connectivity, which is certainly a valid decision if that provides the necessary means for producers and consumers to connect from their environments. Equally, for other customers, WebSphere’s default messaging provider might suffice.

Regards,
David

By: remy

remy — Thu, 02 Jul 2009 09:01:33 +0000

Hi,

I’m working on the definition of an ESB based on Websphere-ESB. My references to do this is the book of David A. Chappell “Enterprise Service Bus”.

My proposal to do this is to used an external JMS provider that will be the core MOM of the ESB. Mediation components will be used to implement the ESB service container plugged into the JMS-based Core MOM.

For me, the Bus of the ESB is really different from the internal bus used by the SCA Mediation components.

What are your opinions , advices about these?

Thanks a lot,

Rémy

By: Dave

Dave — Mon, 30 Mar 2009 21:30:12 +0000

Apologies for the delay in responding. There is currently nothing out of the box that is going to help you in these scenarios. I am, however, aware of projects which have implemented a custom mediation primitive that performs for UDDI much the same functionality as the existing EndpointLookup primitive does for WebSphere Service Registry and Repository. It is relatively easy to achieve as, once the primitive has retrieved the necessary endpoint information, it just sets the target address (or alternate targtets) in the SMO header as documented.

By: Sivaraman

Sivaraman — Mon, 23 Mar 2009 18:54:41 +0000

Hi,
For quite sometime, I’ve been developing PoC’s in Websphere Business Services Fabric for potential customer engagements. Off late the service implementation has grown up extensively such that I am looking to use a service registry to add flexibility to the endpoints.

These endpoints represents communication to the various legacy systems(wrapped inside a process/module with a common interface & BO).

My question is is there any way I can use the Sun service registry or other opensource offerings like JUDDI in the websphere integration developer/Process Server/ESB?

Your comments are highly appreciated.

By: Jim Valencia

Jim Valencia — Tue, 16 Dec 2008 14:49:23 +0000

Thanks a lot! A compressive description of some welcome new features in ESB. I’m downloading the 6.2 version to test it. Good job.

By: WebSphere ESB v6.2 Available « SOA Tips ‘n’ Tricks

WebSphere ESB v6.2 Available « SOA Tips ‘n’ Tricks — Tue, 16 Dec 2008 10:23:24 +0000

[...] ESB v6.2 Available December 16, 2008 — andrewferrier Dave has already beaten me in laying out the details, but it’s worth pointing out that WebSphere ESB 6.2 (together with its tooling environment, [...]

By: Google #1 for WebSphere ESB 6.2 « log.illsley.org

Google #1 for WebSphere ESB 6.2 « log.illsley.org — Sun, 14 Dec 2008 12:05:06 +0000

[...] “WebSphere ESB 6.2″ this weekend appears to get a tweet from me and a rather more in depth discussion from my colleague David [...]