This topic describes access by Version 5 and Version 6
application clients to Java™ Message
Service (JMS) resources provided by the default messaging provider.
Both J2EE application clients and thin application clients can
access JMS resources provided by the default messaging provider:
- A J2EE application client supports the client container that provides
easy access to services. The J2EE application client has the advantage
of performing a simple Java Naming
and Directory Interface (JNDI) namespace lookup to access the desired
service or resource.
- A thin application client must use the
JMS API to explicitly create the JMS destination objects for each
resource coded in the client application. This is equivalent to the
JNDI lookup step
In addition to both types of WebSphere® Application
Server Version 6 application clients, WebSphere Version 5 J2EE application clients
can use their existing Version 5-style JMS resources to access service
integration bus destinations for the default messaging provider. The
link between Version 5 J2EE application clients and a Version 6 application
server is defined by a WebSphere MQ
client link object. One or more Version 5 clients can use the
same WebSphere MQ client
link.
As for other types of resources, a J2EE application client can
use resource environment references and resource references to use
logical names to lookup JMS resources.
- If you configure your J2EE application client to use resource
environment references (to resources bound into the server JNDI namespace),
you use the administrative console to define the resources.
- If you configure your J2EE application client to use resource
references (to local resources), you use the Application Client Resource
Configuration Tool (ACRCT) to define the resources. For
more information about ACRCT, see Starting the
Application Client Resource Configuration Tool and opening an EAR
file
Figure 1. Message flows between Version 5 and Version 6 J2EE application
clients and a Version 6 application server