Win a copy of The Java Performance Companion this week in the Performance forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Mainframe to SOA

 
L.Mohan Arun
Greenhorn
Posts: 5
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I have a hypothetical case study wherein the case on hand is a mainframe to SOA migration.

Mainframe application is to be accessible through the web as a web app.

The web services will be asynchronous, so there would be a JMS queue to keep track of service requests and replies.
Moderate security is to be enforced, as the mainframe will contain some financial transaction data (auditing and logging may be required)

I have created a rough draft of an architecture diagram and I would request folks to critique on the same.
(attached diagram)
Primarily I am looking for feedback on:
a) Is it correct first of all.
b) How would you change it.

Thanks,

Scanned at 3-3-2013 16-11 PM.jpg
[Thumbnail for Scanned at 3-3-2013 16-11 PM.jpg]
 
Jeanne Boyarsky
author & internet detective
Marshal
Posts: 34681
367
Eclipse IDE Java VI Editor
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
What happens when the user clicks to submit a request and the async request never comes back? This is something you will need to account for in your design.
 
L.Mohan Arun
Greenhorn
Posts: 5
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Thanks thats a thoughtful question. Since the async requests are made to the ESB, there should eventually always be some kind of response in the queue, and the web service client
will poll the queue until some sort of response is received. Is this answer correct.
 
Jeanne Boyarsky
author & internet detective
Marshal
Posts: 34681
367
Eclipse IDE Java VI Editor
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
The nice thing about architecture is that there isn't only one correct answer.

That said, I wonder about your answer. The webs ervice client may get a response eventually, but what about the browser. Or is the user on some thick client?
 
L.Mohan Arun
Greenhorn
Posts: 5
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Thanks for the response..
The idea is that the browser invokes the web service, and the web service client returns response from the web service to the browser.
User is on thin cllient - browser
How do I represent the case where the async request from the browser never comes back?
Please let me know
I can add your response to be part of the diagram, or I can add a note attached to the diagram.
 
Jeanne Boyarsky
author & internet detective
Marshal
Posts: 34681
367
Eclipse IDE Java VI Editor
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
You can add comments as notes in the diagram or text below/above it. I had a number of text comments in addition to the diagram to show I considered assorted things.
 
L.Mohan Arun
Greenhorn
Posts: 5
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Ok I will do that
Do you think, I can use ExtJS framework for the message que, in lieu of using an ESB?
 
Sergey Vlasov
Greenhorn
Posts: 25
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
L.Mohan Arun wrote:I have a hypothetical case study wherein the case on hand is a mainframe to SOA migration.

Mainframe application is to be accessible through the web as a web app.

The web services will be asynchronous, so there would be a JMS queue to keep track of service requests and replies.
Moderate security is to be enforced, as the mainframe will contain some financial transaction data (auditing and logging may be required)

I have created a rough draft of an architecture diagram and I would request folks to critique on the same.
(attached diagram)
Primarily I am looking for feedback on:
a) Is it correct first of all.
b) How would you change it.

Thanks,



I'd like to suggest to look at license agreements related to the MF stack, as there may be certain legal constraints, which may limit your options.
 
L.Mohan Arun
Greenhorn
Posts: 5
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi Thanks, the situation is hypothetical, so MF stack licenses is okay I believe ..

please guide me, whether I should remove the ESB component in favor of using a JMS provider implementation
which can take care of reliable message delivery? Also, if the browser front-end is using some javascript framework
which support reliable asynchronous messaging?

It is because ESBs are expensive and add another layer of complexity to maintain.
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic