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

Document Information


Part I Introduction to Message Queue Administration

1.  Administrative Tasks and Tools

2.  Quick-Start Tutorial

Part II Administrative Tasks

3.  Starting Brokers and Clients

4.  Configuring a Broker

5.  Managing a Broker

6.  Configuring and Managing Connection Services

7.  Managing Message Delivery

8.  Configuring Persistence Services

9.  Configuring and Managing Security Services

10.  Configuring and Managing Broker Clusters

11.  Managing Administered Objects

12.  Configuring and Managing Bridge Services

13.  Monitoring Broker Operations

14.  Analyzing and Tuning a Message Service

15.  Troubleshooting

Part III Reference

16.  Command Line Reference

17.  Broker Properties Reference

18.  Physical Destination Property Reference

19.  Administered Object Attribute Reference

20.  JMS Resource Adapter Property Reference

21.  Metrics Information Reference

22.  JES Monitoring Framework Reference

Part IV Appendixes

A.  Distribution-Specific Locations of Message Queue Data

B.  Stability of Message Queue Interfaces

C.  HTTP/HTTPS Support

HTTP/HTTPS Support Architecture

Enabling HTTP/HTTPS Support

Step 1 (HTTPS Only): Generating a Self-Signed Certificate for the Tunnel Servlet

Step 2 (HTTPS Only): Specifying the Key Store Location and Password

To Specify the Location and Password of the Certificate Key Store

Step 3 (HTTPS Only): Validating and Installing the Server's Self-Signed Certificate

To Validate and Install the Server's Self-Signed Certificate

Step 4 (HTTP and HTTPS): Deploying the Tunnel Servlet

To Deploy the HTTP or HTTPS Tunnel Servlet

Modifying the Application Server's Security Policy File

Step 5 (HTTP and HTTPS): Configuring the Connection Service

To Activate the httpjms or httpsjms Connection Service

Step 6 (HTTP and HTTPS): Configuring a Connection

Installing a Root Certificate (HTTPS Only)

Configuring the Connection Factory (HTTP and HTTPS)

Using a Single Servlet to Access Multiple Brokers (HTTP and HTTPS)

Using an HTTP Proxy


Server or Broker Failure

Client Failure to Connect Through the Tunnel Servlet

If a Client Cannot Connect

D.  JMX Support

E.  Frequently Used Command Utility Commands


Installing a Root Certificate in the Trust Store

  1. Import the root certificate.

    Execute the command

    JRE_HOME/bin/keytool -import -trustcacerts -alias certAlias -file certFile -keystore trustStoreFile

    where certFile is the file containing the root certificate, certAlias is the alias representing the certificate, and trustStoreFile is the file containing your trust store.

  2. Confirm that you trust the certificate.

    Answer YES to the question Trust this certificate?

  3. Identify the trust store to the client application.

    In the command that launches the client application, use the -D option to specify the following properties:

Configuring the Connection Factory (HTTP and HTTPS)

To enable HTTP/HTTPS support, you need to set the connection factory’s imqAddressList attribute to the URL of the HTTP/HTTPS tunnel servlet. The URL has the form




where hostName:portNumber is the host name and port number of the application server or Web server hosting the tunnel servlet and contextRoot is the context root directory you specified when deploying the tunnel servlet on the server, as described above under Step 4 (HTTP and HTTPS): Deploying the Tunnel Servlet.

You can set the imqAddressList attribute in any of the following ways:

Using a Single Servlet to Access Multiple Brokers (HTTP and HTTPS)

It is not necessary to configure multiple application or Web servers and tunnel servlets in order to access multiple brokers; you can share a single server instance and tunnel servlet among them. To do this, you must configure the imqAddressList connection factory attribute as follows:




where brokerHostName is the broker instance host name and instanceName is the name of the specific broker instance you want your client to access.

To check that you have entered the correct values for brokerHostName and instanceName, generate a status report for the HTTP/HTTPS tunnel servlet by accessing the servlet URL from a browser:


The report lists all brokers being accessed by the servlet, as shown in Example C-1.

Example C-1 Tunnel Servlet Status Report

HTTP tunnel servlet ready.
Servlet Start Time : Thu May 30 01:08:18 PDT 2002
Accepting secured connections from brokers on port : 7675
Total available brokers = 2
Broker List :

Using an HTTP Proxy

To use an HTTP proxy to access the HTTPS tunnel servlet, set the system properties http.proxyHost and http.proxyPort to the proxy server’s host name and port number. You can set these properties using the -D option to the command that launches the client application.