1

We're looking at the choice between implementing an enterprise integration solution in either:

  • Spring/Spring Integration/JMS/Spring Web MVC
  • Websphere Application Server/MDB/Spring

What are the pros/cons?

Especially interested in what WAS/MDB solution is functionally better at.

Cheers

Paul

Brett Kail
  • 33,593
  • 2
  • 85
  • 90
Paul McKenzie
  • 19,646
  • 25
  • 76
  • 120
  • I don't really get what's the equivalent of Spring Integration in the second version? – abalogh May 13 '11 at 20:58
  • a) when you mention above framework/technologies, do u mean only integration you need is for JAVA based application. Because all above systems are JAVA based. b) U mention above WAS, are u trying to include WAS only for just integration purpose or is it already present into your software stack. Remember WAS is expensive application server. c) You seems to be mixing unrelated technologies together. WAS is pure J2EE server which has built in JMS provider. MDB and JMS are J2EE standards. Spring is dependency-injection oriented framework which helps to manage the inter-dependency between objects. – ag112 May 18 '11 at 07:53
  • d) Having said all above, you need to concentrate/elaborate more on your current/future integration requirements. Are you looking only java based modules interaction? Are you looking for asynchronous communication? e) Generally in java based applications, for synchronous communication, web service call is preferred and for asynchronous communication, JMS call is preferred. for both web service and JMS implementation, you got plenty of reliable open source systems like AXIS and Active MQ etc. – ag112 May 18 '11 at 07:53
  • @abologh -- Message driven beans consuming messages off a JMS queue is the integration method in the WAS solution. – Paul McKenzie May 20 '11 at 08:25
  • @ag112 -- our integration methods are JMS (Websphere MQ) and file-based. Spring Integration offers good mechanisms to write event-driven systems using these transports. See http://www.springsource.org/spring-integration – Paul McKenzie May 20 '11 at 08:28
  • @Paul McKenzie- I understand that spring Integration offers functionality over existing integration pattern...however how about this, your applications' communicating application(whether external/internal) may or may not have spring framework or for that matter, may not be implemented in java....so firstly you should concentrate on your integration requirements before zeroing on a particular framework....if you have already done so, then spring integration can be good framework. – ag112 May 20 '11 at 09:58

1 Answers1

0

If the only thing you need in your entire project from the Java EE Specification is to get messages from a JMS provider, I suggest you to not use WebSphere App Server. Go with Tomcat+Basic Spring JMS Template. Simple, free, lightweight.

Websphere will bring a level of complexity you don't need. Stay away from heavy weight app server. But if you need more fancy Transaction management ( XA between JMS and a DB) then get a real Java EE App Server.

Arjan Tijms
  • 37,782
  • 12
  • 108
  • 140
Aerosteak
  • 987
  • 1
  • 11
  • 21