Only 49 hours left in the trailboss' kickstarter!

New rewards and stretch goals. CLICK HERE!



  • Post Reply Bookmark Topic Watch Topic
  • New Topic

JCA (Java Connector Architecture) or MQ Series to integrate Mainframe legacy?  RSS feed

 
Rogerio Kioshi
Ranch Hand
Posts: 690
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi,

I'd like to know what is the best approach in order to connect to a Mainframe legacy which uses Cobol/IMS.
I've heard JCA and message (JMS with MQ series) can be used, but what are the pros and cons of each strategy?
I also wanted to test something with MQ Series, but are there other alternatives I could use (could be open source) instead of MQ Series to test connection to mainframe?

Thank you.
 
Steve Wink
Ranch Hand
Posts: 225
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Originally posted by Rogerio Kioshi:
Hi,

I'd like to know what is the best approach in order to connect to a Mainframe legacy which uses Cobol/IMS.
I've heard JCA and message (JMS with MQ series) can be used, but what are the pros and cons of each strategy?
I also wanted to test something with MQ Series, but are there other alternatives I could use (could be open source) instead of MQ Series to test connection to mainframe?

Thank you.


Does a JCA adapter to the mainframe exist - has someone already written one? Writing a decent JCA adapter is not trivial and there isn't much documentation on how to do it properly. There is a lot of documentation on how to send and consume MQ messages.

What sort of interactions do you want - MQ will be asynchronous, JCA could be synchronous. What about transactions - this would complicate writing a JCA adapter greatly.

What is the mainframe? Z-series? If so you probably will have access to MQ, so why use something else?
 
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!