Sun Java System Application Server Enterprise Edition 8.1 2005Q2 Developer's Guide

- Previous: Message Queue Resource Adapter
- Next: Restarting the JMS Client After JMS Configuration

# Administration of the JMS Service

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

- Configuring the JMS Service

- The Default JMS Host

- Creating JMS Hosts

- Checking Whether the JMS Provider Is Running

- Creating Physical Destinations

- Creating JMS Resources: Destinations and Connection Factories

For more information about JMS administration tasks, see the Sun Java System Application Server Enterprise Edition 8.1 2005Q2 Administration Guide and the Sun Java System Message Queue 3 2005Q4 Administration Guide.

## Configuring the JMS Service

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

- To edit the JMS Service configuration using the Administration Console, open the Java Message Service component under the relevant configuration. For details, see the Sun Java System Application Server Enterprise Edition 8.1 2005Q2 Administration Guide.

- To configure the JMS service, use the `asadmin set` command to set the following attributes:

      server.jms-service.init-timeout-in-seconds = 60
      server.jms-service.type = LOCAL
      server.jms-service.start-args =
      server.jms-service.default-jms-host = default_JMS_host
      server.jms-service.reconnect-interval-in-seconds = 60
      server.jms-service.reconnect-attempts = 3
      server.jms-service.reconnect-enabled = true
      server.jms-service.addresslist-behavior = random
      server.jms-service.addresslist-iterations = 3
      server.jms-service.mq-scheme = mq
      server.jms-service.mq-service = jms

  You can also set these properties:

      server.jms-service.property.instance-name = imqbroker
      server.jms-service.property.instance-name-suffix =
      server.jms-service.property.append-version = false

  You can use the `asadmin get` command to list all the JMS service attributes and properties. For details, see the Sun Java System Application Server Enterprise Edition 8.1 2005Q2 Reference Manual.

You can override the JMS Service configuration using JMS connection factory settings. For details, see the Sun Java System Application Server Enterprise Edition 8.1 2005Q2 Administration Guide.

Note –

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

## The Default JMS Host

A JMS host refers to a Sun Java System Message Queue broker. A default JMS host for the JMS service is provided, named `default_JMS_host`. This is the JMS host that the Application Server instance starts when the JMS Service type is configured as `LOCAL`.

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 Application 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:

- Use the Administration Console. Open the Java Message Service component under the relevant configuration, then select the JMS Hosts component. For details, see the Sun Java System Application Server Enterprise Edition 8.1 2005Q2 Administration Guide.

- Use the `asadmin create-jms-host` command. For details, see the Sun Java System Application Server Enterprise Edition 8.1 2005Q2 Reference Manual.

## Checking Whether the JMS Provider Is Running

You can use the `asadmin jms-ping` command to check whether a Sun Java System Message Queue instance is running. For details, see the Sun Java System Application Server Enterprise Edition 8.1 2005Q2 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 physical destination it listens to doesn’t exist, the Application Server automatically creates the physical destination and sets the value of the property `maxNumActiveConsumers` to `-1` (see Load-Balanced Message Inflow). However, it is good practice to create the physical destination beforehand.

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

- Use the Administration Console. Open the Resources component, open the JMS Resources component, then select Physical Destinations. For details, see the Sun Java System Application Server Enterprise Edition 8.1 2005Q2 Administration Guide.

- Use the `asadmin create-jmsdest` command. This command acts on the default JMS host of its target. For details, see the Sun Java System Application Server Enterprise Edition 8.1 2005Q2 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 Application Server:

- Connection Factories: administered objects that implement the `ConnectionFactory`, `QueueConnectionFactory`, or `TopicConnectionFactory` interfaces.

- Destination Resources: administered objects that implement the `Queue` or `Topic` interfaces.

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

- To create a JMS resource using the Administration Console, open the Resources component, then open the JMS Resources component. Click Connection Factories to create a connection factory, or click Destination Resources to create a queue or topic. For details, see the Sun Java System Application Server Enterprise Edition 8.1 2005Q2 Administration Guide.

- To create a JMS resource, use the `asadmin create-jms-resource` command. For details, see the Sun Java System Application Server Enterprise Edition 8.1 2005Q2 Reference Manual.

Note –

When a `Queue` is automatically created for a message-driven bean deployed to an Application Server cluster, the value of the property `maxNumActiveConsumers` is set to `-1` so that multiple consumers can access the `Queue` at the same time. For more information, see Load-Balanced Message Inflow.

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

- Previous: Message Queue Resource Adapter
- Next: Restarting the JMS Client After JMS Configuration

- © 2010, Oracle Corporation and/or its affiliates