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


HTTP/HTTPS Support Architecture

Message Queue’s support architecture is very similar for both HTTP and HTTPS support, as shown in Figure C-1:

Figure C-1 HTTP/HTTPS Support Architecture

image:Diagram showing how an HTTP proxy and HTTP tunnel servlet enable messages to go through firewalls. Figure explained in text.

The main difference between HTTP and HTTPS connections is that in the HTTPS case (httpsjms connection service), the tunnel servlet has a secure connection to both the client application and the broker. The secure connection to the broker is established by means of the Secure Socket Layer (SSL) protocol. Message Queue’s SSL-enabled HTTPS tunnel servlet passes a self-signed certificate to any broker requesting a connection. The broker uses the certificate to establish an encrypted connection to the tunnel servlet. Once this connection is established, a secure connection between the client application and the tunnel servlet can be negotiated by the client application and the application server or Web server.