test

Sun Java System Message Queue 3.7 UR1 Administration Guide

Step 1. Deploy the HTTP Tunnel Servlet

You can deploy the HTTP tunnel servlet as a Web archive (.war) file on a Sun Java System Web Server or Sun Java System Application Server.

Deploying the HTTP tunnel servlet as a .war file consists of using the deployment mechanism provided by the Web server/application 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, Platform-Specific Locations of Message QueueTM Data).

The .war file includes a deployment descriptor that contains the basic configuration information needed by the Web server/application server to load and run the servlet. Depending on the Web server/application server, you might also need to specify the context root portion of the servlet’s URL.

Deploying as a Web Archive File

For deployment on a Sun Java System Web Server, see Deploying the HTTP Tunnel Servlet on Sun Java System Web Server.

For deployment on a Sun Java System Application Server, see Deploying the HTTP Tunnel Servlet on Sun Java System Application Server.

Deploying the HTTP Tunnel Servlet on Sun Java System Web Server

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

ProcedureTo 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, Platform-Specific Locations of Message QueueTM 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 :portNumber / contextRoot/tunnel

    For example, if you set the contextRoot to imq, 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:portNumber/
contextRoot/tunnel

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

Disabling a Server Access Log

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

ProcedureTo Disable the Server Access Log

  1. Select the Status tab.

  2. Choose the Log Preferences Page.

    Use the Log client accesses control to disable logging.

Deploying the HTTP Tunnel Servlet on Sun Java System Application Server

This section describes how you deploy the HTTP tunnel servlet as a .war file on the Sun Java System Application Server, and then configure the tunnel servlet to accept connections from a Message Queue broker.

Two steps are required:

Using the Deployment Tool

ProcedureTo Deploy the HTTP Tunnel Servlet in an Application Server 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: text field, enter the location of the HTTP tunnel servlet .war file (imqhttp.war), and click OK.

    The location of the imqhttp.war file depends on your operating system (see Appendix A, Platform-Specific Locations of Message QueueTM Data).

  4. Set the value for the Context Root text field, and click OK.

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

    http://hostName :portNumber / contextRoot/tunnel

    For example, you could set the Context Root field to /imq.

    The confirmation screen that appears confirms that the tunnel servlet has been successfully deployed, is enabled by default, and in this case is located at:


    /var/opt/SUNWappserver8/domains/domain1/server1/applications/
j2ee-modules/imqhttp_1

    The servlet is now available at the following URL:


    http://hostName:portNumber/
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 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/SUNWappserver8/domains/domain1/server1/config/
server.policy

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

ProcedureTo Modify the Application Server’s server.policy File

  1. Open the server.policy file.

  2. Add the following entry:


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