ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » General IBM MQ Support » Architecture for communicating J2ee Application With Mainfra

Post new topic  Reply to topic
 Architecture for communicating J2ee Application With Mainfra « View previous topic :: View next topic » 
Author Message
subhendu
PostPosted: Thu Mar 07, 2002 6:13 am    Post subject: Reply with quote

Novice

Joined: 05 Mar 2002
Posts: 18

I am developing a banking web application based on J2ee architecture with ejb1.1 in websphere 3.5 . One of our requirement is when user submits some data in web application it will be asyncronosoly transfered to the host(main frame).User should not wait online for this to be done. Host system has one MQseries from where the host will read the data.

Is there any recomonded approach/best practices to do this.

Any solutions will be great.
Thanks,
Subhendu
Back to top
View user's profile Send private message
mrlinux
PostPosted: Thu Mar 07, 2002 6:36 am    Post subject: Reply with quote

Grand Master

Joined: 14 Feb 2002
Posts: 1261
Location: Detroit,MI USA

I suggest you install MQSeries Client on the WebSphere box and client connect to the Mainframe Queue Manager.

_________________
Jeff

IBM Certified Developer MQSeries
IBM Certified Specialist MQSeries
IBM Certified Solutions Expert MQSeries
Back to top
View user's profile Send private message Send e-mail
subhendu
PostPosted: Thu Mar 07, 2002 6:50 am    Post subject: Reply with quote

Novice

Joined: 05 Mar 2002
Posts: 18

IS MQSeriesClient is a separate product to be bought ??
Actually the scenario is when user submits some information(Ten Account Information), We are storing the group as a batch id(For a particular user) and stores all the information in the web application database and returns the screen to online user, so that user need not to wait for the actual transfer of data between the web domain database to Mainframe.

Now the question is who will be responsible to extract the data and send it to host MQ.
My thought:
1. When user submits the data we store the information in the database but send the batch id to the One of the Queue in the webdomain.
2. Listener listening to this queue will pick up the batch id and get the information of all the datas(for example 10 Account information) and put the data in another Queue. And some listener listening to this queue will get the message and put in host queue.

I do not know whether this idea is good or bad. I need suggestion of you people to make it good performing application but in asynchronous way.

Your input is very valuable to me.
Thanks,
Subhendu
Back to top
View user's profile Send private message
mrlinux
PostPosted: Thu Mar 07, 2002 7:01 am    Post subject: Reply with quote

Grand Master

Joined: 14 Feb 2002
Posts: 1261
Location: Detroit,MI USA

MQSeries Client is free for most platforms, the only platform that I know they
charge for is SCO Unixware.

_________________
Jeff

IBM Certified Developer MQSeries
IBM Certified Specialist MQSeries
IBM Certified Solutions Expert MQSeries
Back to top
View user's profile Send private message Send e-mail
mrlinux
PostPosted: Thu Mar 07, 2002 7:03 am    Post subject: Reply with quote

Grand Master

Joined: 14 Feb 2002
Posts: 1261
Location: Detroit,MI USA

Have your application read the database and then connect to the mainframe MQSeries Queue and write it to the Queue

_________________
Jeff

IBM Certified Developer MQSeries
IBM Certified Specialist MQSeries
IBM Certified Solutions Expert MQSeries
Back to top
View user's profile Send private message Send e-mail
subhendu
PostPosted: Thu Mar 07, 2002 7:21 am    Post subject: Reply with quote

Novice

Joined: 05 Mar 2002
Posts: 18

We have designed in a way so that user need not to wait for the data transfer. So we thought we will store the data in web domain database and later transfer it to Mainframe in a asynchronous manner.

So to transfer offline to Mainframe some program will read the data and post it to MQ in MQseries.

So i want how to design the web domain part to take care that. Because the mainframe system has its own MQ and program to read MQ.
Back to top
View user's profile Send private message
subhendu
PostPosted: Thu Mar 07, 2002 9:43 am    Post subject: Reply with quote

Novice

Joined: 05 Mar 2002
Posts: 18

Basically i want to know how to design the Listener. I want to make one connection and reuse that connection rathere than creating individual connection for each request.

Any Idea?
Back to top
View user's profile Send private message
muralidhar
PostPosted: Thu Mar 07, 2002 3:55 pm    Post subject: Reply with quote

Acolyte

Joined: 28 Feb 2002
Posts: 50

If you have a MQSeries client on the machine on which websphere is running, you can directly submit all the messages(assuming you want to create a message for each operation) to the queue on the server through MQSeries client application. Even for submitting 10 messages, it should not take more than 1 sec. Once if you submitted messages it is asynchronous. Your web application can work independently without depending on message processing. Or you can also do the way you want by storing all the user operations in the database and submit only one message on to the queue on the server.

In either of the cases you should define a trigger on the MQ Server which is associated with a process. If you define a trigger and if trigger moniter is running, it triggers the process and then the application associated with the process. That application can retrive the messages from the queue and process the messages and can also work with the database. You can write this application in any of the mqseries supported languages viz., java.
Back to top
View user's profile Send private message Send e-mail
jfluitsm
PostPosted: Fri Mar 08, 2002 12:55 am    Post subject: Reply with quote

Disciple

Joined: 24 Feb 2002
Posts: 160
Location: The Netherlands

As your processing is asynchronous, you should also consider using MQSeries server and a queue-manager on the WebShpere box and putting the messages direct on this box. In this scenario the users can submit their info without the mainframe available as opposed to using a client where the mainframe must be available.

_________________
Jan Fluitsma

IBM Certified Solution Designer WebSphere MQ V6
IBM Certified Solution Developer WebSphere Message Broker V6
Back to top
View user's profile Send private message Send e-mail
subhendu
PostPosted: Mon Mar 11, 2002 4:40 pm    Post subject: Reply with quote

Novice

Joined: 05 Mar 2002
Posts: 18

Hi jfluitsm
Could you give me some more detail what you talking about ,so that i can consider this option as well.

Thanks,
Subhendu
Back to top
View user's profile Send private message
jfluitsm
PostPosted: Tue Mar 12, 2002 1:44 am    Post subject: Reply with quote

Disciple

Joined: 24 Feb 2002
Posts: 160
Location: The Netherlands

Hi Subhendu,

In short, what you can do is setting up 2 queue managers, one on the whebSphere box (say QMWS) and one on the mainframe (say QMMF1) and the communication between them. Your application puts the messages on QMWS and this queue manager takes care of sending the message to QMMF1. In case QMMF1 can't be reached from QMWS, the later will save those messages in a transmission queue until QMMF1 is available again.

This is still a bit vague, this is becaus you can do this in 2 ways.
- The old fashiond way, you have to define channels between the two queue managers, the queue definition (Q1) will be on QMMF1, on QMWS you have to define a remote queueu (RQ1), pointing to Q1 on QMMF1, and stating which transmission queue to use.
- With a cluster, both queue managers should participate in a cluster. Q1 is defined on QMMF and also shared in the cluster. Your application can put a message Q1 on QMWS as if it was defined on QMWS, the message will be send to QMMF1. Don't define Q1 on QMWS, as the message will stay in Q1 on QMWS instead of being send to Q1 on QMMF1.
Advantage of the later solution is that it is possible to use parallel processing and load-balancing.

This is in short what you can do. For more info please read the MQSeries Intercommunication and MQSeries Queue Manager Clusters manuals.

I hope this will help you.

_________________
Jan Fluitsma

IBM Certified Solution Designer WebSphere MQ V6
IBM Certified Solution Developer WebSphere Message Broker V6
Back to top
View user's profile Send private message Send e-mail
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » General IBM MQ Support » Architecture for communicating J2ee Application With Mainfra
Jump to:  



You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.