Deploying the HTTP proxy servlet on WebSphere Application Server

Load and install the HTTP proxy servlet file on WebSphere Application Server.

Before you begin

Before you deploy the HTTP proxy servlet, you must complete the following tasks:

Configuring the HTTP proxy servlet
Enabling the integration node listener for SOAP nodes
Identify or install a WebSphere Application Server installation that can host the HTTP proxy servlet.

About this task

Procedure

To deploy the HTTP proxy servlet on WebSphere Application Server, complete the following steps:

Deploy the HTTP proxy servlet file (that you exported from IBM Integration Bus) by following the instructions to deploy a web application in the WebSphere Application Server Version 8.5 product documentation online.

Note: Make sure that you select the correct context root for your HTTP proxy servlet, see Importance of the context root when you configure the HTTP proxy servlet.
To test if the HTTP proxy servlet is active, enter the following URL in a web browser:
```
http://host_name:port/context_root
```
where:

host_name

Specifies the host name of your WebSphere Application Server.

port

Specifies the port number of your WebSphere Application Server.

context_root

Specifies the context root that you assigned to the HTTP proxy servlet.
For example: http://localhost:9080/.
If the HTTP proxy servlet can reach the integration node, then you should get an HTTP Status 404 response with the following error message:
```
URI / does not map to any message flow in integration node integration_node
```
where integration_node is the name of your integration node.

Results

The HTTP proxy servlet is deployed on WebSphere Application Server.

What to do next

The HTTP proxy servlet is now ready to be tested with an integration node that receives HTTP (not HTTPS) requests and passes them to a message flow. For information about how to complete this task, see Testing the HTTP proxy servlet.