My understanding given a couple dog-and-pony shows from IBM:
MQIAC - or "My-ack" is a CICS adapter for scripting "micro-flow" 3270
interactions on the host and exposing those interactions via MQ, TDQ, or
JCA. Many moons ago, Early Cloud had a FEPI (Front-End Programming
Interface) component for
John,
We attempted clustering a while back (I believe under 5.1) and we had 2
primary issues, both we attempted to address through PMRs with no
resolution. The first was having to do with the repositories getting
corrupted for no apparent reason, and the second had to do a network
failure caused
Even if you don't need routing or transformation services today, I believe
the broker at the hub is still a good idea. If you have applications that
maintain multiple point-to-point configurations, the broker would still add
value by giving the requesting application a single point of access (as
Dave - Great to hear it. I don't know what the proper etiquette here is,
but would you mind conferencing with some folks around here? I should
probably try to arrange that through IBM with your permission. What do you
think? I can't imagine there is too much "conflict of interest" between
Marr
Thanks - that helps
Chuck Brasfield <[EMAIL PROTECTED]>@AKH-WIEN.AC.AT> on 08/13/2002
01:11:20 PM
Please respond to MQSeries List <[EMAIL PROTECTED]>
Sent by: MQSeries List <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc:
Subject: Re: Quick clustering question...
This transmiss
Has anybody out there successfully implemented MQ clustering in a high
volume production environment? Mainframe and/or distributed. If so, has
your experience been positive?
The feeling here right now is that it is more trouble than it's worth, and
is not quite "ready for prime time". I'm stil
I hope this isn't related to my other post...
We have a websphere application that is client channel connected to a
remote queue manager (both client and mgr are 5.2). This application has a
servlet (agent) that is scheduled to inspect a queue for incoming work and
process those messages. The s
Can anyone point me to some documentation regarding best practices around
the use of MQ and WAS? Clients versus server connections (java bindings)?
I believe I read somewhere that it was recommended to run MQ locally on a
WAS server as opposed to client channel connections to a remote server, but
We have been coding Java/MQ frameworks for about 3 years now, and our
handywork has gone through quite an evolution. In a high volume
environment with a lot of synchronous messaging, we ran into some problems
with the methods on the queue manager object being synchronized causing
contention betwe
