Previous Contents Index Next |
Sun Java System Message Queue 3.5 SP1 Administration Guide

> ## Appendix C
> HTTP/HTTPS Support (Enterprise Edition)

> Message Queue, Enterprise Edition (see "Product Editions") includes support for both HTTP and HTTPS connections. (HTTPS is HTTP over a Secure Socket Layer—SSL—transport connection.) This support allows client applications to communicate with the broker using the HTTP protocol instead of direct TCP connections. This appendix describes the architecture used to enable this support and explains the setup work needed to allow clients to use HTTP-based connections for Message Queue messaging.

> Note | HTTP/HTTPS support is available for Java clients but not for C clients.

> ##

> HTTP/HTTPS Support Architecture

> Message Queue messaging can be run on top of HTTP/HTTPS connections. Because HTTP/HTTPS connections are normally allowed through firewalls, this allows client applications to be separated from a broker by a firewall.

> Figure C-1 shows the main components involved in providing HTTP/HTTPS support.

> - On the client side, an HTTP or HTTPS transport driver encapsulates the Message Queue message into an HTTP request and makes sure that these requests are sent to the Web server in the correct sequence.
> - The client can use an HTTP proxy server to communicate with the broker if necessary. The proxy’s address is specified using command line options when starting the client. See "Using an HTTP Proxy" for more information.
> - An HTTP or HTTPS tunnel servlet (both bundled with Message Queue) is loaded in the web server and used to pull JMS messages out of client HTTP requests before forwarding them to the broker. The HTTP/HTTPS tunnel servlet also sends broker messages back to the client in response to HTTP requests made by the client. A single HTTP/HTTPS tunnel servlet can be used to access multiple brokers.

> Figure C-1 HTTP/HTTPS Support Architecture

> - On the broker side, the httpjms or httpsjms connection service unwraps and de-multiplexes incoming messages from the corresponding tunnel servlet.
> - If the Web server fails and is restarted, all connections are restored and there is no effect on clients. If the broker fails and is restarted, an exception is thrown and clients must re-establish their connections. In the unlikely case that both the Web server and the broker fail, and the broker is not restarted, the Web server will restore client connections and continue waiting for a broker connection— without notifying clients. To avoid this situation, always restart the broker.

> As you can see from Figure C-1, the architecture for HTTP and HTTPS support are very similar. The main difference is that, in the case of HTTPS (httpsjms connection service), the tunnel servlet has a secure connection to both the client application and broker.

> The secure connection to the broker is provided through an SSL-enabled tunnel servlet—Message Queue’s HTTPS tunnel servlet—which passes a self-signed certificate to any broker requesting a connection. The certificate is used by the broker to set up an encrypted connection to the HTTPS tunnel servlet. Once this connection is established, a secure connection between a client application and the tunnel servlet can be negotiated by the client application and the web server.

> ##

> Enabling HTTP Support

> The following sections describe the steps you need to take to enable HTTP support.

> ##### To Enable HTTP Support

> 1. Deploy the HTTP tunnel servlet on a web server.
> 2. Configure the broker’s httpjms connection service and start the broker.
> 3. Configure an HTTP connection.

> ### Step 1. Deploying the HTTP Tunnel Servlet on a Web Server

> There are two general ways you can deploy the HTTP tunnel servlet on a web server:

> - deploying it as a jar file—for web servers that support Servlet 2.1 or earlier
> - deploying it as a web archive (WAR) file—for web servers that support Servlet 2.2 or later

> #### Deploying as a Jar File

> Deploying the Message Queue tunnel servlet consists of making the appropriate jar files accessible to the host web server, configuring the web server to load the servlet on startup, and specifying the context root portion of the servlet’s URL.

> The tunnel servlet jar file (imqservlet.jar) contains all the classes needed by the HTTP tunnel servlet, and can be found in a directory that depends upon operating system (see Appendix A, "Location of Message Queue Data").

> Any web server with servlet 2.x support can be used to load this servlet. The servlet class name is:

> com.sun.messaging.jmq.transport.
> httptunnel.servlet.HttpTunnelServlet

> The web server must be able to see the imqservlet.jar file. If you are planning to run the web server and the broker on different hosts, you should place a copy of the imqservlet.jar file in a location where the web server can access it.

> You also need to configure the web server to load this servlet on startup, and you might need to specify the context root portion of the servlet’s URL (see "Example 1: Deploying the HTTP Tunnel Servlet on Sun Java System Web Server").

> It is also recommended that you disable your web server’s access logging feature in order to improve performance.

> #### Deploying as a Web Archive File

> Deploying the HTTP tunnel servlet as a WAR file consists of using the deployment mechanism provided by the web server. The HTTP tunnel servlet WAR file (imqhttp.war) is located in the directory containing .jar, .war, and .rar files, and depends on your operating system (see Appendix A, "Location of Message Queue Data").

> The WAR file includes a deployment descriptor that contains the basic configuration information needed by the web server to load and run the servlet. Depending on the web server, you might also need to specify the context root portion of the servlet’s URL (see "Example 2: Deploying the HTTP Tunnel Servlet on Sun Java System Application Server 7.0").

> ### Step 2. Configuring the httpjms Connection Service

> HTTP support is not activated for a broker by default, so you need to reconfigure the broker to activate the httpjms connection service. Once reconfigured, the broker can be started as outlined in "Starting a Broker".

> ##### To Activate the httpjms Connection Service

> 1. Open the broker’s instance configuration file.

> The instance configuration file is stored in a directory identified by the name of the broker instance (instanceName) with which the configuration file is associated (see Appendix A, "Location of Message Queue Data"):

> …/instances/instanceName/props/config.properties

> 2. Add the httpjms value to the imq.service.activelist property:

> imq.service.activelist=jms,admin,httpjms

> At startup, the broker looks for a web server and HTTP tunnel servlet running on its host machine. To access a remote tunnel servlet, however, you can reconfigure the servletHost and servletPort connection service properties.

> You can also reconfigure the pullPeriod property to improve performance. The httpjms connection service configuration properties are detailed in Table C-1.

> Table C-1 httpjms Connection Service Properties

> Property Name | Description
> --- | ---
> imq.httpjms.http. servletHost | Change this value, if necessary, to specify the name of the host (hostname or IP address) on which the HTTP tunnel servlet is running. (This can be a remote host or a specific hostname on a local host.) Default: localhost
> imq.httpjms.http. servletPort | Change this value to specify the port number that the broker uses to access the HTTP tunnel servlet. (If the default port is changed on the Web server, then you must change this property accordingly.) Default: 7675
> imq.httpjms.http. pullPeriod | Specifies the interval, in seconds, between HTTP requests made by a client runtime to pull messages from the broker. (Note that this property is set on the broker and propagates to the client runtime.) If the value is zero or negative, the client keeps one HTTP request pending at all times, ready to pull messages as fast as possible. With a large number of clients, this can be a heavy drain on web server resources and the server may become unresponsive. In such cases, you should set the pullPeriod property to a positive number of seconds. This sets the time the client’s HTTP transport driver waits before making subsequent pull requests. Setting the value to a positive number conserves web server resources at the expense of the response times observed by clients. Default: -1
> imq.httpjms.http. connectionTimeout | Specifies the time, in seconds, that the client runtime waits for a response from the HTTP tunnel servlet before throwing an exception. (Note that this property is set on the broker and propagates to the client runtime.) This property also specifies the time the broker waits after communicating with the HTTP tunnel servlet before freeing up a connection. A timeout is necessary in this case because the broker and the tunnel servlet have no way of knowing if a client that is accessing the HTTP servlet has terminated abnormally. Default: 60

> ### Step 3. Configuring an HTTP Connection

> A client application must use an appropriately configured connection factory administered object to make an HTTP connection to a broker. This section discusses HTTP connection configuration issues.

> #### Configuring the Connection Factory

> To enable HTTP support, you need to set the connection factory’s imqAddressList attribute to the HTTP tunnel servlet URL. The general syntax of the HTTP tunnel servlet URL is the following:

> http://hostName:port/contextRoot/tunnel

> where hostName:port is the name and port of the web server hosting the HTTP tunnel servlet and contextRoot is a path set when deploying the tunnel servlet on the web server.

> For more information on connection factory attributes in general, and the imqAddressList attribute in particular, see the Message Queue Java Client Developer’s Guide.

> You can set connection factory attributes in one of the following ways:

> - Using the -o option to the imqobjmgr command that creates the connection factory administered object (see "Adding a Connection Factory"), or set the attribute when creating the connection factory administered object using the Administration Console (imqadmin).
> - Using the -D option to the command that launches the client (see the Message Queue Java Client Developer’s Guide).
> - Using a an API call to set the attributes of a connection factory after you create it programmatically in client code (see the Message Queue Java Client Developer’s Guide).

> #### Using a Single Servlet to Access Multiple Brokers

> You do not need to configure multiple web servers and servlet instances if you are running multiple brokers. You can share a single web server and HTTP tunnel servlet instance among concurrently running brokers. If multiple broker instances are sharing a single tunnel servlet, you must configure the imqAddressList connection factory attribute as shown below:

> http://hostName:port/contextRoot/tunnel?ServerName=bkrHostName:instanceName

> Where bkrHostName 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 strings for bkrHostName and instanceName, generate a status report for the HTTP tunnel servlet by accessing the servlet URL from a browser. The report lists all brokers being accessed by the servlet:

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

> #### Using an HTTP Proxy

> If you are using an HTTP proxy to access the HTTP tunnel servlet:

> - Set http.proxyHost system property to the proxy server host name.
> - Set http.proxyPort system property to the proxy server port number.

> You can set these properties using the -D option to the command that launches the client application.

> ### Example 1: Deploying the HTTP Tunnel Servlet on Sun Java System Web Server

> This section describes how you deploy the HTTP tunnel servlet both as a jar file and as a WAR file on the Sun Java System Web Server. The approach you use depends on the version of Sun Java System Web Server: If it does not support Servlet 2.2 or later, it will not be able to handle WAR file deployment.

> #### Deploying as a Jar File

> The instructions below refer to deployment on Sun Java System Web Server 6.1 using the browser-based administration GUI. This procedure consists of the following general steps:

> 1. add a servlet
> 2. configure the servlet virtual path
> 3. load the servlet
> 4. disable the servlet access log

> These steps are described in the following subsections. You can verify successful HTTP tunnel servlet deployment by accessing the servlet URL using a web browser. It should display status information.

> ##### Adding a Servlet

> ##### To Add a Tunnel Servlet

> 1. Select the Servlets tab.
> 2. Choose Configure Servlet Attributes.
> 3. Specify a name for the tunnel servlet in the Servlet Name field.
> 4. Set the Servlet Code (class name) field to the following value:

> com.sun.messaging.jmq.transport.
> httptunnel.servlet.HttpTunnelServlet

> 5. Enter the complete path to the imqservlet.jar in the Servlet Classpath field. For example:

> /usr/share/lib/imq/imqservlet.jar (on Solaris)

> /opt/imq/lib/imqservlet.jar (on Linux)

> IMQ_HOME/lib/imqservlet.jar (on Windows)

> 6. In the Servlet args field, enter any optional arguments, as shown in Table C-2:

> Table C-2 Servlet Arguments for Deploying HTTP Tunnel Servlet Jar File

> Argument | Default Value | Reference
> --- | --- | ---
> servletHost | all hosts | See Table C-1
> servletPort | 7675 | See Table C-1

> If using both arguments, separate them with a comma:

> servletPort=portNumber, servletHost=…

> The servletHost and servletPort argument apply only to communication between the Web Server and broker, and are set only if the default values are problematic. However, in that case, you also have to set the broker configuration properties accordingly (see Table C-1), for example:

> imq.httpjms.http.servletPort

> ##### Configuring a Servlet Virtual Path (Servlet URL)

> ##### To Configure a Virtual Path (Servlet URL) for a Tunnel Servlet

> 1. Select the Servlets tab.
> 2. Choose Configure Servlet Virtual Path Translation.
> 3. Set the Virtual Path field.

> The Virtual Path is the /contextRoot/tunnel portion of the tunnel servlet URL:

> http://hostName:port/contextRoot/tunnel

> For example, if you set the contextRoot to imq, then the Virtual Path field would be:

> /imq/tunnel

> 4. Set the Servlet Name field to the same value as in Step 3 in "Adding a Servlet".

> ##### Loading a Servlet

> ##### To Load the Tunnel Servlet at Web Server Startup

> 1. Select the Servlets tab.
> 2. Choose Configure Global Attributes.
> 3. In the Startup Servlets field, enter the same servlet name value as in Step 3 in "Adding a Servlet".

> ##### Disabling a Server Access Log

> You do not have to disable the server access log, but you will obtain better performance if you do.

> ##### To Disable the Server Access Log

> 1. Select the Status tab.
> 2. Choose the Log Preferences Page.
> 3. Use the Log client accesses control to disable logging

> #### Deploying as a WAR File

> The instructions below refer to deployment on Sun Java System Web Server 6.0 Service
> Pack 2. You can verify successful HTTP tunnel servlet deployment by accessing the servlet URL using a web browser. It should display status information.

> ##### To Deploy the http Tunnel Servlet as a WAR File

> 1. In the browser-based administration GUI, select the Virtual Server Class tab and select Manage Classes.
> 2. Select the appropriate virtual server class name (for example, defaultClass) and click the Manage button.
> 3. Select Manage Virtual Servers.
> 4. Select an appropriate virtual server name and click the Manage button.
> 5. Select the Web Applications tab.
> 6. Click on Deploy Web Application.
> 7. Select the appropriate values for the WAR File On and WAR File Path fields so as to point to the imqhttp.war file, which can be found in a directory that depends on your operating system (see Appendix A, "Location of Message Queue Data").
> 8. Enter a path in the Application URI field.

> The Application URI field value is the /contextRoot portion of the tunnel servlet URL:

> http://hostName:port/contextRoot/tunnel

> For example, if you set the contextRoot to imq, then the Application URI field would be:

> /imq

> 9. Enter the installation directory path (typically somewhere under the Sun Java System Web Server installation root) where the servlet should be deployed.
> 10. Click OK.
> 11. Restart the web server instance.

> The servlet is now available at the following address:

> http://hostName:port/contextRoot/tunnel

> Clients can now use this URL to connect to the message service using an HTTP connection.

> ### Example 2: Deploying the HTTP Tunnel Servlet on Sun Java System Application Server 7.0

> This section describes how you deploy the HTTP tunnel servlet as a WAR file on the Sun Java System Application Server 7.0.

> Two steps are required:

> - deploy the HTTP tunnel servlet using the Application Server 7.0 deployment tool
> - modify the application server instance’s server.policy file

> #### Using the Deployment Tool

> ##### To Deploy the HTTP Tunnel Servlet in an Application Server 7.0 Environment

> 1. In the web-based administration GUI, choose

> App Server > Instances > server1 > Applications > Web Applications.

> 2. Click the Deploy button.
> 3. In the File Path: textfield, enter the location of the HTTP tunnel servlet WAR file (imqhttp.war).

> The location of the imqhttp.war file depends on your operating system (see Appendix A, "Location of Message Queue Data")

> 4. Click OK.
> 5. On the next screen, set the value for the Context Root textfield.

> The Context Root field value is the /contextRoot portion of the tunnel servlet URL:

> http://hostName:port/contextRoot/tunnel

> For example, you could set the Context Root field to:

> /imq

> 6. Click OK.

> The next screen shows that the tunnel servlet has been successfully deployed, is enabled by default, and—in this case—is located at:

> /var/opt/SUNWappserver7/domains/domain1/server1/applications/
> j2ee-modules/imqhttp_1

> The servlet is now available at the following address:

> http://hostName:port/contextRoot/tunnel

> Clients can now use this URL to connect to the message service using an HTTP connection.

> #### Modifying the server.policy File

> The Application Server 7.0 enforces a set of default security policies that unless modified would prevent the HTTP tunnel servlet from accepting connections from the Message Queue broker.

> Each application server instance has a file that contains its security policies or rules. For example, the location of this file for the server1 instance on Solaris is:

> /var/opt/SUNWappserver7/domains/domain1/server1/config/
> server.policy

> To make the tunnel servlet accept connections from the Message Queue broker, an additional entry is required in this file.

> ##### To Modify the Application Server’s server.policy File

> 1. Open the server.policy file.
> 2. Add the following entry:

> grant codeBase
> "file:/var/opt/SUNWappserver7/domains/domain1/server1/ applications/j2ee-modules/imqhttp_1/-”
> {
> permission java.net.SocketPermission "*", “connect,accept,resolve";
> };

> ##

> Enabling HTTPS Support

> The following sections describe the steps you need to take to enable HTTPS support. They are similar to those in "Enabling HTTP Support" with the addition of steps needed to generate and access SSL certificates.

> ##### To Enable HTTPS Support

> 1. Generate a self-signed certificate for the HTTPS tunnel servlet.
> 2. Deploy the HTTPS tunnel servlet on a web server.
> 3. Configure the broker’s httpsjms connection service and start the broker.
> 4. Configure an HTTPS connection.

> Each of these steps is discussed in more detail in the sections that follow.

> ### Step 1. Generating a Self-signed Certificate for the HTTPS Tunnel Servlet

> Message Queue’s SSL support is oriented toward securing on-the-wire data with the assumption that the client is communicating with a known and trusted server. Therefore, SSL is implemented using only self-signed server certificates. In the httpsjms connection service architecture, the HTTPS tunnel servlet plays the role of server to both broker and application client.

> Run the imqkeytool utility to generate a self-signed certificate for the tunnel servlet. Enter the following at the command prompt:

> imqkeytool -servlet keystore_location

> The utility will prompt you for the information it needs. (On Unix systems you may need to run imqkeytool as the superuser (root) in order to have permission to create the keystore.)

> First, imqkeytool prompts you for a keystore password, then it prompts you for some organizational information, and then it prompts you for confirmation. After it receives the confirmation, it pauses while it generates a key pair. It then asks you for a password to lock the particular key pair (key password); you should enter Return in response to this prompt: this makes the key password the same as the keystore password.

> Note | Remember the password you provide—you will need to provide this password later to the tunnel servlet so it can open the keystore.

> Running imqkeytool runs the JDK keytool utility to generate a self-signed certificate and to place it in Message Queue’s keystore file located as specified in the keystore_location argument. (The keystore is in the same keystore format as that supported by the JDK1.2 keytool.)

> Note | The HTTPS tunnel servlet must be able to see the keystore. Make sure you move/copy the generated keystore located in keystore_location to a location accessible by the HTTPS tunnel servlet (see "Step 2. Deploying the HTTPS Tunnel Servlet on a Web Server").

> ### Step 2. Deploying the HTTPS Tunnel Servlet on a Web Server

> There are two general ways you can deploy the HTTPS tunnel servlet on a web server:

> - deploying it as a jar file—for web servers that support Servlet 2.1 or earlier
> - deploying it as a web archive (WAR) file—for web servers that support Servlet 2.2 or later

> In either case, you should make sure that encryption is activated for the web server, enabling end to end secure communication between the client and broker.

> #### Deploying as a Jar File

> Deploying the Message Queue tunnel servlet consists of making the appropriate jar files accessible to the host web server, configuring the web server to load the servlet on startup, and specifying the context root portion of the servlet’s URL.

> The tunnel servlet jar file (imqservlet.jar) contains all the classes needed by the HTTPS tunnel servlet, and can be found in a directory that depends upon operating system (see Appendix A, "Location of Message Queue Data").

> Any web server with servlet 2.x support can be used to load this servlet. The servlet class name is:

> com.sun.messaging.jmq.transport.
> httptunnel.servlet.HttpsTunnelServlet

> The web server must be able to see the imqservlet.jar file. If you are planning to run the web server and the broker on different hosts, you should place a copy of the imqservlet.jar file in a location where the web server can access it.

> You also need to configure the web server to load this servlet on startup, and you might need to specify the context root portion of the servlet’s URL (see "Example 3: Deploying the HTTPS Tunnel Servlet on Sun Java System Web Server").

> Make sure that the JSSE jar files are in the classpath for running servlets in the web server. Check the web server’s documentation for how to do this.

> An important aspect of configuring the web server is specifying the location and password of the self-signed certificate to be used by the HTTPS tunnel servlet to establish a secure connection with a broker. You have to place the keystore created in "Step 1. Generating a Self-signed Certificate for the HTTPS Tunnel Servlet" in a location accessible by the HTTPS tunnel servlet.

> It is also recommended that you disable your web server’s access logging feature in order to improve performance.

> #### Deploying as a Web Archive File

> Deploying the HTTPS tunnel servlet as a WAR file consists of using the deployment mechanism provided by the web server. The HTTPS tunnel servlet WAR file (imqhttps.war) is located in a directory that depends on your operating system (see Appendix A, "Location of Message Queue Data").

> The WAR file includes a deployment descriptor that contains the basic configuration information needed by the web server to load and run the servlet. Depending on the web server, you might also need to specify the context root portion of the servlet’s URL (see "Example 4: Deploying the HTTPS Tunnel Servlet on Sun Java System Application Server 7.0").

> However, the deployment descriptor of the imqhttps.war file cannot know where you have placed the keystore file needed by the tunnel servlet (see "Step 1. Generating a Self-signed Certificate for the HTTPS Tunnel Servlet"). This requires you to edit the tunnel servlet’s deployment descriptor (an XML file) to specify the keystore location before deploying the imqhttps.war file.

> ### Step 3. Configuring the httpsjms Connection Service

> HTTPS support is not activated for a broker by default, so you need to reconfigure the broker to activate the httpsjms connection service. Once reconfigured, the broker can be started as outlined in "Starting a Broker".

> ##### To Activate the httpsjms Connection Service

> 1. Open the broker’s instance configuration file.

> The instance configuration file is stored in a directory identified by the name of the broker instance (instanceName) with which the configuration file is associated (see Appendix A, "Location of Message Queue Data"):

> …/instances/instanceName/props/config.properties

> 2. Add the httpsjms value to the imq.service.activelist property:

> imq.service.activelist=jms,admin,httpsjms

> At startup, the broker looks for a web server and HTTPS tunnel servlet running on its host machine. To access a remote tunnel servlet, however, you can reconfigure the servletHost and servletPort connection service properties.

> You can also reconfigure the pullPeriod property to improve performance. The httpsjms connection service configuration properties are detailed in Table C-3.

> Table C-3 httpsjms Connection Service Properties

> Property Name | Description
> --- | ---
> imq.httpsjms.https. servletHost | Change this value, if necessary, to specify the name of the host (hostname or IP address) on which the HTTPS tunnel servlet is running. (This can be a remote host or a specific hostname on a local host.) Default: localhost
> imq.httpsjms.https. servletPort | Change this value to specify the port number that the broker uses to access the HTTPS tunnel servlet. (If the default port is changed on the Web server, then you must change this property accordingly.) Default: 7674
> imq.httpsjms.https. pullPeriod | Specifies the interval, in seconds, between HTTP requests made by each client to pull messages from the broker. (Note that this property is set on the broker and propagates to the client runtime.) If the value is zero or negative, the client keeps one HTTP request pending at all times, ready to pull messages as fast as possible. With a large number of clients, this can be a heavy drain on web server resources and the server may become unresponsive. In such cases, you should set the pullPeriod property to a positive number of seconds. This sets the time the client’s HTTP transport driver waits before making subsequent pull requests. Setting the value to a positive number conserves web server resources at the expense of the response times observed by clients. Default: -1
> imq.httpsjms.https. connectionTimeout | Specifies the time, in seconds, that the client runtime waits for a response from the HTTPS tunnel servlet before throwing an exception. (Note that this property is set on the broker and propagates to the client runtime.) This property also specifies the time the broker waits after communicating with the HTTPS tunnel servlet before freeing up a connection. A timeout is necessary in this case because the broker and the tunnel servlet have no way of knowing if a client that is accessing the HTTPS servlet has terminated abnormally. Default: 60

> ### Step 4. Configuring an HTTPS Connection

> A client application must use an appropriately configured connection factory administered object to make an HTTPS connection to a broker.

> However, the client must also have access to SSL libraries provided by the Java Secure Socket Extension (JSSE) and must also have a root certificate. The SSL libraries are bundled with JDK 1.4. If you have an earlier JDK version, see "Configuring JSSE," otherwise proceed to "Importing a Root Certificate."

> Once these issues are resolved, you can proceed to configuring the HTTPS connection.

> #### Configuring JSSE

> ##### To Configure JSSE

> 1. Copy the JSSE jar files to the JRE_HOME/lib/ext directory.

> jsse.jar, jnet.jar, jcert.jar

> 2. Statically add the JSSE security provider by adding

> security.provider.n=com.sun.net.ssl.internal.ssl.Provider

> to the JRE_HOME/lib/security/java.security file (where n is the next available priority number for security provider package).

> 3. If not using JDK1.4, you need to set the following JSSE property using the -D option to the command that launches the client application:

> java.protocol.handler.pkgs=com.sun.net.ssl.internal.www.protocol

> #### Importing a Root Certificate

> If the root certificate of the CA who signed your web server's certificate is not in the trust database by default or if you are using a proprietary web server certificate, you have to add that certificate to the trust database. If this is the case, follow the instruction below, otherwise go to "Configuring the Connection Factory."

> Assuming that the certificate is saved in cert_file and that trust_store_file is your keystore, run the following command:

> JRE_HOME/bin/keytool -import -trustcacerts
> -alias alias_for_certificate -file cert_file
> -keystore trust_store_file

> Answer YES to the question: Trust this certificate?

> You also need to specify the following JSSE properties using the -D option to the command that launches the client application:

> javax.net.ssl.trustStore=trust_store_file

> javax.net.ssl.trustStorePassword=trust_store_passwd

> #### Configuring the Connection Factory

> To enable HTTPS support, you need to set the connection factory’s imqAddressList attribute to the HTTPS tunnel servlet URL. The general syntax of the HTTPS tunnel servlet URL is the following:

> https://hostName:port/contextRoot/tunnel

> where hostName:port is the name and port of the web server hosting the HTTPS tunnel servlet and contextRoot is a path set when deploying the tunnel servlet on the web server.

> For more information on connection factory attributes in general, and the imqAddressList attribute in particular, see the Message Queue Java Client Developer’s Guide.

> You can set connection factory attributes in one of the following ways:

> - Using the -o option to the imqobjmgr command that creates the connection factory administered object (see "Adding a Connection Factory"), or set the attribute when creating the connection factory administered object using the Administration Console (imqadmin).
> - Using the -D option to the command that launches the client application (see the Message Queue Java Client Developer’s Guide).
> - Using an API call to set the attributes of a connection factory after you create it programmatically in client application code (see the Message Queue Java Client Developer’s Guide).

> #### Using a Single Servlet to Access Multiple Brokers

> You do not need to configure multiple web servers and servlet instances if you are running multiple brokers. You can share a single web server and HTTPS tunnel servlet instance among concurrently running brokers. If multiple broker instances are sharing a single tunnel servlet, you must configure the imqAddressList connection factory attribute as shown below:

> https://hostName:port/contextRoot/tunnel?ServerName=bkrHostName:instanceName

> Where bkrHostName 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 strings for bkrhostName and instanceName, generate a status report for the HTTPS tunnel servlet by accessing the servlet URL from a browser. The report lists all brokers being accessed by the servlet:

> HTTPS tunnel servlet ready. Servlet Start Time : Thu May 30 01:08:18 PDT 2002 Accepting secured connections from brokers on port : 7674 Total available brokers = 2 Broker List : jpgserv:broker2 cochin:broker1

> #### Using an HTTP Proxy

> If you are using an HTTP proxy to access the HTTPS tunnel servlet:

> - Set http.proxyHost system property to the proxy server host name.
> - Set http.proxyPort system property to the proxy server port number.

> You can set these properties using the -D option to the command that launches the client application.

> ### Example 3: Deploying the HTTPS Tunnel Servlet on Sun Java System Web Server

> This section describes how you deploy the HTTPS tunnel servlet both as a jar file and as a WAR file on the Sun Java System Web Server. The approach you use depends on the version of Sun Java System Web Server: If it does not support Servlet 2.2 or later, it will not be able to handle WAR file deployment.

> #### Deploying as a Jar File

> The instructions below refer to deployment on Sun Java System Web Server 6.1 using the browser-based administration GUI. This procedure consists of the following general steps:

> 1. add a servlet
> 2. configure the servlet virtual path
> 3. load the servlet
> 4. disable the servlet access log

> These steps are described in the following subsections. You can verify successful HTTPS tunnel servlet deployment by accessing the servlet URL using a web browser. It should display status information.

> ##### Adding a Servlet

> ##### To Add a Tunnel Servlet

> 1. Select the Servlets tab.
> 2. Choose Configure Servlet Attributes.
> 3. Specify a name for the tunnel servlet in the Servlet Name field.
> 4. Set the Servlet Code (class name) field to the following value:

> com.sun.messaging.jmq.transport.
> httptunnel.servlet.HttpsTunnelServlet

> 5. Enter the complete path to the imqservlet.jar in the Servlet Classpath field. For example:

> /usr/share/lib/imq/imqservlet.jar (on Solaris)

> /opt/imq/lib/imqservlet.jar (on Linux)

> IMQ_HOME/lib/imqservlet.jar (on Windows)

> 6. In the Servlet args field, enter required and optional arguments, as shown in Table C-4.

> Table C-4 Servlet Arguments for Deploying HTTPS Tunnel Servlet Jar File

> Argument | Default Value | Required? | See Also
> --- | --- | --- | ---
> keystoreLocation | none | Yes | Table 8-8
> keystorePassword | none | Yes | Table 8-8
> servletHost | all hosts | No | Table C-3
> servletPort | 7674 | No | Table C-3

> Separate the arguments with a comma, for example:

> keystoreLocation=keystore_location,keystorePassword=keystore_password, servletPort=portnumber

> The servletHost and servletPort argument apply only to communication between the Web Server and broker, and are set only if the default values are problematic. However, in that case, you also have to set the broker configuration properties accordingly (see Table C-3), for example:

> imq.httpsjms.https.servletPort

> ##### Configuring a Servlet Virtual Path (Servlet URL)

> ##### To Configure a Virtual Path (servlet URL) for a Tunnel Servlet

> 1. Select the Servlets tab.
> 2. Choose Configure Servlet Virtual Path Translation.
> 3. Set the Virtual Path field.

> The Virtual Path is the /contextRoot/tunnel portion of the tunnel servlet URL:

> https://hostName:port/contextRoot/tunnel

> For example, if you set the contextRoot to imq, then the Virtual Path field would be:

> /imq/tunnel

> 4. Set the Servlet Name field to the same value as in Step 3 in "Adding a Servlet".

> ##### Loading a Servlet

> ##### To Load the Tunnel Servlet at Web Server Startup

> 1. Select the Servlets tab.
> 2. Choose Configure Global Attributes.
> 3. In the Startup Servlets field, enter the same servlet name value as in Step 3 in "Adding a Servlet".

> ##### Disabling a Server Access Log

> You do not have to disable the server access log, but you will obtain better performance if you do.

> ##### To Disable the Server Access Log

> 1. Select the Status tab.
> 2. Choose the Log Preferences Page.
> 3. Use the Log client accesses control to disable logging

> #### Deploying as a WAR File

> The instructions below refer to deployment on Sun Java System Web Server 6.0 Service
> Pack 2. You can verify successful HTTPS tunnel servlet deployment by accessing the servlet URL using a web browser. It should display status information.

> Before deploying the HTTPS tunnel servlet, make sure that JSSE jar files are included in the web server’s classpath. The simplest way to do this is to copy the jsse.jar, jnet.jar, and jcert.jar to IWS60_TOPDIR/bin/https/jre/lib/ext.

> Also, before deploying the HTTPS tunnel servlet, you have to modify its deployment descriptor to point to the location where you have placed the keystore file and to specify the keystore password.

> ##### To Modify the HTTPS Tunnel Servlet WAR File

> 1. Copy the WAR file to a temporary directory.

> cp /usr/share/lib/imq/imqhttps.war /tmp (on Solaris)

> cp /opt/imq/lib/imqhttps.war /tmp (on Linux)

> cp IMQ_HOME/lib/imqhttps.war /tmp (on Windows)

> 2. Make the temporary directory your current directory.

> $ cd /tmp

> 3. Extract the contents of the WAR file.

> $ jar xvf imqhttps.war

> 4. List the WAR file’s deployment descriptor.

> $ ls -l WEB-INF/web.xml

> 5. Edit the web.xml file to provide correct values for the keystoreLocation and keystorePassword arguments (as well as servletPort and servletHost arguments, if necessary).
> 6. Re-assemble the contents of the WAR file.

> $ jar uvf imqhttps.war WEB-INF/web.xml

> You are now ready to use the modified imqhttps.war file to deploy the HTTPS tunnel servlet. (If you are concerned about exposure of the keystore password, you can use file system permissions to restrict access to the imqhttps.war file.)

> ##### To Deploy the https Tunnel Servlet as a WAR File

> 1. In the browser-based administration GUI, select the Virtual Server Class tab. Click Manage Classes.
> 2. Select the appropriate virtual server class name (for example, defaultClass) and click the Manage button.
> 3. Select Manage Virtual Servers.
> 4. Select an appropriate virtual server name and click the Manage button.
> 5. Select the Web Applications tab.
> 6. Click on Deploy Web Application.
> 7. Select the appropriate values for the WAR File On and WAR File Path fields so as to point to the modified imqhttps.war file (see "To Modify the HTTPS Tunnel Servlet WAR File".)
> 8. Enter a path in the Application URI field.

> The Application URI field value is the /contextRoot portion of the tunnel servlet URL:

> https://hostName:port/contextRoot/tunnel

> For example, if you set the contextRoot to imq, then the Application URI field would be:

> /imq

> 9. Enter the installation directory path (typically somewhere under the Sun Java System Web Server installation root) where the servlet should be deployed.
> 10. Click OK.
> 11. Restart the web server instance.

> The servlet is now available at the following address:

> https://hostName:port/imq/tunnel

> Clients can now use this URL to connect to the message service using a secure HTTPS connection.

> ### Example 4: Deploying the HTTPS Tunnel Servlet on Sun Java System Application Server 7.0

> This section describes how you deploy the HTTPS tunnel servlet as a WAR file on the Sun Java System Application Server 7.0.

> Two steps are required:

> - deploy the HTTPS tunnel servlet using the Application Server 7.0 deployment tool
> - modify the application server instance’s server.policy file

> #### Using the Deployment Tool

> ##### To Deploy the HTTPS Tunnel Servlet in an Application Server 7.0 Environment

> 1. In the web-based administration GUI, choose

> App Server > Instances > server1 > Applications > Web Applications.

> 2. Click the Deploy button.
> 3. In the File Path: textfield, enter the location of the HTTPS tunnel servlet WAR file (imqhttps.war).

> The location of the imqhttps.war file depends on your operating system (see Appendix A, "Location of Message Queue Data")

> 4. Click OK.
> 5. On the next screen, set the value for the Context Root textfield.

> The Context Root field value is the /contextRoot portion of the tunnel servlet URL:

> https://hostName:port/contextRoot/tunnel

> For example, you could set the Context Root field to:

> /imq

> 6. Click OK.

> The next screen shows that the tunnel servlet has been successfully deployed, is enabled by default, and—in this case—is located at:

> /var/opt/SUNWappserver7/domains/domain1/server1/applications/
> j2ee-modules/imqhttps_1

> The servlet is now available at the following address:

> https://hostName:port/contextRoot/tunnel

> Clients can now use this URL to connect to the message service using an HTTPS connection.

> #### Modifying the server.policy file

> The Application Server 7.0 enforces a set of default security policies that unless modified would prevent the HTTPS tunnel servlet from accepting connections from the Message Queue broker.

> Each application server instance has a file that contains its security policies or rules. For example, the location of this file for the server1 instance on Solaris is:

> /var/opt/SUNWappserver7/domains/domain1/server1/config/
> server.policy

> To make the tunnel servlet accept connections from the Message Queue broker, an additional entry is required in this file.

> ##### To Modify the Application Server’s server.policy File

> 1. Open the server.policy file.
> 2. Add the following entry:

> grant codeBase
> "file:/var/opt/SUNWappserver7/domains/domain1/server1/ applications/j2ee-modules/imqhttps_1/-”
> {
> permission java.net.SocketPermission "*", “connect,accept,resolve";
> };

> Previous Contents Index Next

> Copyright 2003 Sun Microsystems, Inc. All rights reserved.