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


To Deploy the HTTP or HTTPS Tunnel Servlet

  1. Deploy the tunnel servlet:
    1. In the Web-based administration GUI, choose App Server>Instances>appServerInstance>Applications>Web Applications

      where appServerInstance is the application server instance on which you are deploying the tunnel servlet.

    2. Click the Deploy button.
  2. Specify the .war file location:
    1. Enter the location of the tunnel servlet’s Web archive file (imqhttp.war or imqhttps.war) in the File Path text field.

      The file is located in the IMQ_HOME/lib directory.

    2. Click the OK button.
  3. Specify the context root directory:
    1. Enter the /contextRoot portion of the tunnel servlet’s URL.

      The URL has the form




      For example, if the URL for the tunnel servlet is


      the value you enter would be

    2. Click the OK button.

      A confirmation screen appears, showing that the tunnel servlet has been successfully deployed and is enabled by default. The servlet is now available at the URL




      where contextRoot is the context root directory you specified in step a above. Clients can now use this URL to connect to the message service using an HTTP or HTTPS connection.

  4. Modify the server’s security policy file

    Once you have deployed the HTTP or HTTPS tunnel servlet, you must grant it the appropriate permissions by modifying the Application Server’s security policy file, as described in the next procedure.