JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Oracle GlassFish Server 3.1 Administration Guide
search filter icon
search icon

Document Information


1.  Overview of GlassFish Server Administration

Default Settings and Locations

Configuration Tasks

Administration Tools

Instructions for Administering GlassFish Server

Part I Runtime Administration

2.  General Administration

3.  Administering Domains

4.  Administering the Virtual Machine for the Java Platform

5.  Administering Thread Pools

6.  Administering Web Applications

7.  Administering the Logging Service

8.  Administering the Monitoring Service

9.  Writing and Running JavaScript Clients to Monitor GlassFish Server

10.  Administering Life Cycle Modules

11.  Extending and Updating GlassFish Server

Part II Resources and Services Administration

12.  Administering Database Connectivity

13.  Administering EIS Connectivity

14.  Administering Internet Connectivity

15.  Administering the Object Request Broker (ORB)

16.  Administering the JavaMail Service

17.  Administering the Java Message Service (JMS)

About the JMS Service

JMS Service High Availability

Updating the JMS Service Configuration

Setting Message Queue Broker Properties in the JMS Service Configuration

Administering JMS Hosts

About JMS Host Types

Configuring Embedded and Local JMS Hosts

To Create a JMS Host

To List JMS Hosts

To Update a JMS Host

To Delete a JMS Host

Administering JMS Connection Factories and Destinations

To Create a Connection Factory or Destination Resource

To List JMS Resources

To Delete a Connection Factory or Destination Resource

Administering JMS Physical Destinations

To Create a JMS Physical Destination

To List JMS Physical Destinations

To Purge Messages From a Physical Destination

To Delete a JMS Physical Destination

Special Situations When Using the JMS Service

Troubleshooting the JMS Service

Using the Generic Resource Adapter for JMS to Integrate Supported External JMS Providers

Configuring GenericJMSRA for Supported External JMS Providers

To Deploy and Configure GenericJMSRA

GenericJMSRA Configuration Properties

Connection Factory Properties

Destination Properties

Activation Spec Properties

Using GenericJMSRA with WebLogic JMS

Deploy the WebLogic Thin T3 Client JAR in GlassFish Server

Configure WebLogic JMS Resources for Integration

Create a Resource Adapter Configuration for GenericJMSRA to Work With WebLogic JMS

Deploy the GenericJMSRA Resource Archive

Configuring an MDB to Receive Messages from WebLogic JMS

Accessing Connections and Destinations Directly

Limitations When Using GenericJMSRA with WebLogic JMS

Configuration Reference of GenericJMSRA Properties for WebLogic JMS

Using GenericJMSRA with IBM WebSphere MQ

Preliminary Setup Procedures for WebSphere MQ Integration

Configure the WebSphere MQ Administered Objects

Create a Resource Adapter Configuration for GenericJMSRA to Work With WebSphere MQ

Deploy the GenericJMSRA Archive

Create the Connection Factories and Administered Objects in GlassFish Server

Configuring an MDB to Receive Messages from WebSphere MQ

18.  Administering the Java Naming and Directory Interface (JNDI) Service

19.  Administering Transactions

Part III Appendixes

A.  Subcommands for the asadmin Utility


Special Situations When Using the JMS Service

As mentioned earlier, Message Queue, through the built-in jmsra resource adapter, is tightly integrated with GlassFish Server to provide JMS messaging managed through a rich set of asadmin subcommands and Administration Console pages to simplify JMS messaging administration tasks. In most instances, this tight integration is transparent and automatic, requiring no special effort on the part of an administrator. In certain special situations, though, an administrator must perform a task such a setting a Message Queue broker property or a GlassFish object attribute to enable or disable a capability of the integration. The topics in this section describe these situations.

Restarting an Embedded or Local Broker That Has Failed

Because the JMS service, not Message Queue, manages the lifecycle of brokers acting as Embedded and Local JMS hosts, do not use the imqbrokerd Message Queue utility to start such a broker that has failed. Instead, restart the GlassFish instance that the broker is servicing.

Changing the Admin User Password for an Embedded or Local Broker

Follow these steps to change the admin user password for an Embedded or Local broker:

  1. Make sure the broker is running.

  2. Use the imqusermgr Message Queue utility to change the password of the admin user.

  3. Edit the configuration of the JMS host, changing the password of the admin user to the new password.

  4. Restart the GlassFish instance that the broker is servicing.

When changing the password for the brokers in a broker cluster, first perform steps 1 and 2 on each broker. Then, perform step 3. Finally, perform step 4 on each broker.

Using SSL to Connect to an Oracle Internet Directory (OID) or Oracle Virtual Directory (OVD) User Respository

When using SSL to connect to an OID or OVD user repository, you must set the imq.user_repository.ldap.ssl.socketfactory Message Queue broker property to