Oracle GlassFish Server 3.0.1 Application Development Guide

Administration of the JMS Service

To configure the JMS Service and prepare JMS resources for use in applications deployed to the GlassFish Server, you must perform these tasks:

For more information about JMS administration tasks, see Chapter 19, Administering the Java Message Service (JMS) , in Oracle GlassFish Server 3.0.1 Administration Guide and the Oracle GlassFish Message Queue 4.4.2 Administration Guide.

Configuring the JMS Service

The JMS Service configuration is available to all inbound and outbound connections pertaining to the GlassFish Server instance. You can edit the JMS Service configuration in the following ways:

You can override the JMS Service configuration using JMS connection factory settings. For details, see Chapter 19, Administering the Java Message Service (JMS) , in Oracle GlassFish Server 3.0.1 Administration Guide.

Note –

The GlassFish Server instance must be restarted after configuration of the JMS Service.

The Default JMS Host

A JMS host refers to a Message Queue broker. A default JMS host for the JMS service is provided, named default_JMS_host. This is the JMS host that the GlassFish Server uses for performing all Message Queue broker administrative operations, such as creating and deleting JMS destinations.

If you have created a multi-broker cluster in the Message Queue software, delete the default JMS host, then add the Message Queue cluster’s brokers as JMS hosts. In this case, the default JMS host becomes the first JMS host in the AddressList. For more information about the AddressList, see JMS Connection Features. You can also explicitly set the default JMS host; see Configuring the JMS Service.

When the GlassFish Server uses a Message Queue cluster, it executes Message Queue specific commands on the default JMS host. For example, when a physical destination is created for a Message Queue cluster of three brokers, the command to create the physical destination is executed on the default JMS host, but the physical destination is used by all three brokers in the cluster.

Creating JMS Hosts

You can create additional JMS hosts in the following ways:

For machines having more than one host, use the Host field in the Administration Console or the ---–mqhost option of create-jms-host to specify the address to which the broker binds.

Checking Whether the JMS Provider Is Running

You can use the asadmin jms-ping command to check whether a Message Queue instance is running. For details, see the Oracle GlassFish Server 3.0.1 Reference Manual.

Creating Physical Destinations

Produced messages are delivered for routing and subsequent delivery to consumers using physical destinations in the JMS provider. A physical destination is identified and encapsulated by an administered object (a Topic or Queue destination resource) that an application component uses to specify the destination of messages it is producing and the source of messages it is consuming.

If a message-driven bean is deployed and the Queue physical destination it listens to doesn’t exist, the GlassFish Server automatically creates the physical destination. However, it is good practice to create the Queue physical destination beforehand.

You can create a JMS physical destination in the following ways:

To purge all messages currently queued at a physical destination, use the asadmin flush-jmsdest command. This deletes the messages before they reach any message consumers. For details, see the Oracle GlassFish Server 3.0.1 Reference Manual.

To create a destination resource, see Creating JMS Resources: Destinations and Connection Factories.

Creating JMS Resources: Destinations and Connection Factories

You can create two kinds of JMS resources in the GlassFish Server:

In either case, the steps for creating a JMS resource are the same. You can create a JMS resource in the following ways:

Note –

All JMS resource properties that used to work with version 7 of the GlassFish Server are supported for backward compatibility.