WebSphere Message Broker, Version 8.0.0.7 Operating Systems: AIX, HP-Itanium, Linux, Solaris, Windows, z/OS

See information about the latest product version

Testing the proxy servlet

Test the proxy servlet with a message broker that receives HTTP requests and passes them to a message flow.

To test the proxy servlet, use an existing web services client application or write your own SSL test client application using Java™.

Universal Resource Locators (URLs) play an important role when you use HTTP or HTTPS protocols.

In WebSphere Message Broker, HTTPInput nodes receive requests that specify a URL (or possibly multiple URLs, when wildcards are used). The servlet container also uses the URLs to identify the servlets that process the HTTP/HTTPS requests received by the listener in the container. The proxy servlet passes the requests from the servlet container to WebSphere Message Broker and from WebSphere Message Broker to the servlet container. URLs are used to locate both servlets and HTTPInput nodes, and this dual function affects the format of the URLs used in WebSphere Message Broker.

URLs have the following format: schema://hostname:port/url_path.

  • schema has a value of either http or https.
  • hostname is the host name or IP address of the server on which the servlet container and the broker are running.
  • port is the port number that the servlet container is listening on.
  • url_path consists of a series of tokens separated by forward slashes ("/"), and is used to indicate the location of the servlet and of the HTTPInput nodes.
    Since url_path maps to two different resources, its format changes when the proxy servlet is used. In this case, the format of url_path is context_root/node_url_path.
    • context_root is the URL path that the container allocates to the proxy servlet when the servlet is installed and deployed
    • node_url_path is the part of the URL path that makes the URL unique to a specific HTTP Input node
    The whole url_path must be configured as a property in the HTTPInput node.
    Note: For some servlet containers, you can configure the proxy servlet to receive all of the HTTP or HTTPS requests that the container receives, by setting the value for context_root to /*. In this case, you do not have to change the existing URLs in the HTTP nodes when the proxy servlet is implemented.

To test the proxy servlet, complete the following steps:

  1. Install a client application that can send HTTP or SSL (HTTPS) requests. There are several options that can be used, such as:
    • OpenSSL: Another open source tool available from the Internet at: OpenSSL downloads website that can be used to send SSL (HTTPS) requests to the web servlet container.
    • A broker message flow that has an HTTPRequest or SOAPRequest node can generate and send HTTP requests to an HTTP listener.
    • A web browser using web pages or Java Server Pages (JSP) that can send HTTP POST requests. Most web browsers support HTTP and SSL (HTTPS).
    • A client application that sends requests by using HTTP, or (SSL) HTTPS, or both.
  2. Configure the proxy servlet to access the message broker in the web.xml file.
  3. Configure a message flow with HTTP and SOAP input and reply nodes. The message flow receives the messages from the proxy servlet. If an HTTP and SOAP reply node is configured, responses are sent back to the proxy servlet.

You have now finished testing the proxy servlet.

Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2016Copyright IBM Corporation 1999, 2016.

        
        Last updated:
        
        Last updated: 2016-05-23 14:46:36


Task topicTask topic | Version 8.0.0.7 | ac69460_