| Author |
Message
|
| mworsham |
 Posted: Mon Oct 20, 2008 9:19 am Post subject: Transition to Websphere MQ |
 |
|
Novice
Joined: 12 Sep 2002
Posts: 19
Location: Augusta, GA
|
I would like to utilize the Websphere MQ platform to replace an aging internal file-transfer application upon the Linux and HP-UX platform. What would be the best route to go for setting up an environment with a multiple client agents setup with a central server location along with channels and local/remote queues?
I am looking to do simple file data transfers and utilize triggers for dumping the information from the queue and converting the data transferred to a file (i.e. XML, jpg, gif, etc).
The last time I worked with MQ Series was version 5.2.1 for Windows and HP-UX. By my understanding, Websphere MQ 5.3 and above is now all Java-based in relation, which is a problem for me as I have absolutely no skill under Java and I am the only one locally that is working on this project.
-- Michael |
|
| Back to top |
|
 |
| mqjeff |
| Posted: Mon Oct 20, 2008 9:26 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
You do not need to know any Java at all to work with MQ v6 or v7.
You just have to know MQ.
Most of your experience from v5.2 is still applicable - although you should spend a good bit of time in review - particularly in the quick beginnings guide and the system administration guide - as a lot of things are much better in v6 and v7. |
|
| Back to top |
|
|
| mworsham |
| Posted: Mon Oct 20, 2008 9:44 am Post subject: |
|
|
Novice
Joined: 12 Sep 2002
Posts: 19
Location: Augusta, GA
|
So it is possible to create queues, channels, etc via command line and not through some gui/interface -- i.e. strmqm, crtmqm like back in MQ 5.x?
-- Michael |
|
| Back to top |
|
|
| mqjeff |
| Posted: Mon Oct 20, 2008 10:09 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| Through *the same* command line. |
|
| Back to top |
|
|
| mworsham |
| Posted: Mon Oct 20, 2008 11:31 am Post subject: |
|
|
Novice
Joined: 12 Sep 2002
Posts: 19
Location: Augusta, GA
|
| Do I need to install the Websphere MQ server instance on every server that needs it _or_ just on the main server and have a client software on the servers that will talk via the channels to the queues, etc? |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Mon Oct 20, 2008 1:02 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
Although v6 and v7 are much improved, the fundamentals remain the same as you recall from v5.
You need to install a server (queue manager) instance on the platform(s) where you intend to run local applications, and need the services of a qmgr (like hosting queues, point-to-point channels, clusters, etc.). You need to install the client on platforms where you intend to run blient-bound applications that contact a server instances across a network .
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| gbaddeley |
| Posted: Mon Oct 20, 2008 5:10 pm Post subject: Re: Transition to Websphere MQ |
|
|
Jedi Knight
Joined: 25 Mar 2003
Posts: 2538
Location: Melbourne, Australia
|
|
| Back to top |
|
|
| mworsham |
| Posted: Tue Oct 21, 2008 3:37 am Post subject: |
|
|
Novice
Joined: 12 Sep 2002
Posts: 19
Location: Augusta, GA
|
bruce2359: Okay, that statement just confused me. Say I have 10 servers that need to transfer these different types of data files between one another (i.e. some are just basic point to point data transfers, while others are going to multiple server locations). Are you saying that I would have to install a WMQ server instance on each of the 10 servers as well as 10 WMQ clients agents?
gbaddeley: I looked at the WMQ File Transfer Edition, but since it's more of an announcement rather than a having a demo available, it's worthless at this point of time.
-- M |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Tue Oct 21, 2008 5:20 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
Client vs. Server. Do you intend to execute your applications on a platform that has no queue manager instance? If so, you will need to install the WMQ Client. The client software shippes the MQI calls to the server for execution. The server ships the CC/RC back to the client application. Additional network flows are involved with client (MQI) channels.
If you intend to execute your applications on the same o/s instance where a qmgr runs, then you need a queue manager.
To move messages from qmgr to qmgr, you need either explicitly defined channels (sender-receiver, server-requester), OR create a queue manager cluster.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| mworsham |
| Posted: Fri Oct 24, 2008 11:41 am Post subject: |
|
|
Novice
Joined: 12 Sep 2002
Posts: 19
Location: Augusta, GA
|
Right now we have an in-house application called 'fileman'. Its purpose is to transfer data files from one system to another. The problem with the software is that the original developer that made it has left the company many years ago, so the support for it has moved from one person to the next and 'supporting' how it exactly works is becoming a bit of a mystery to those that have to support it now.
From my understanding of the 'fileman' application -- fileman is installed on every system that needs to be part of the 'group' -- it seems to just be a sort of client/parser that picks up files from a directory and pipes the file over to another system via a configuration file. If the remote system was down, however, the sent data would be /dev/null'd, thus lost.
I looked over the Apache's ActiveMQ package, but found that it was lacking the same setup as IBM's MQ for channels, local and remote queues. It seems under the Apache version, you have to design your own queue and trigger system, which made for an understanding of XML and Java code.
So now I am just looking for the best solution to replace this aging code, which will be easily supported and configurable for sending and receiving data streams and supporting triggers from dumping the messages out of the queues and into a configurable directory location.
-- M |
|
| Back to top |
|
|
| mqjeff |
| Posted: Fri Oct 24, 2008 12:23 pm Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
So you probably want to go with clients on each machine, and a server somewhere.
You can look at things like MA7K for starting up client programs to receive files, and a directory scanner program to send files.
There are some very hard problems you are going to have to solve, though - particularly around knowing exactly when a file is ready to be picked up...
If you have the source code for this aging 'fileman' thing, you may want to review very carefully what it is doing in that respect to decide if a file is ready - and then reimplement the same logic in Java or etc. |
|
| Back to top |
|
|
|
|
