Download - CBT Tape

Real time JMS server implementation on WMQ
INTRODUCTION
This article illustrates the use of JMS (Java Messaging System),
in a WMQ environment, for large-scale file replication in a crossplatform, cross-vendor environment. I will discuss the advantages
and potential pitfalls and provide practical instructions for
successfully implementing WMQ as a JMS server.
BACKGROUND
When we think of messaging solutions we probably envision a
system that integrates different applications within the enterprise
or even outside the enterprise (partner/customer applications)
by a remote message invocation mechanism. Classic examples
are homogeneous interfaces to heterogeneous backends and
portals that delegate back-end processing of user requests and
then reformat them for end-user presentation, or provide backoffice details for a customer on front-office applications to
provide a 360 degree view during customer interactions.
The common thread in messaging methods is the assumption
that the messaging solution, while providing robust, highly
available communication between systems, is fundamentally
inefficient and should be used only as a last resort when
communication to an outside system cannot be avoided. This
view of messaging has prevailed from the onset of remote
method calls (RMC) to more modern messaging solutions such
as CORBA and DCOM, and it has limited the type of problem that
messaging solutions are usually applied to.
Over the last decade there has been an increased understanding
of the requirements of distributed systems. Emerging
technologies, such as Java and .NET, have included code
distribution as part of their fundamental programming model. In
doing so, these technologies have incorporated high availability
© 2003. Reproduction prohibited. Please inform Xephon of any infringement.
3