HTTP proxy servlet is deployed to a servlet container that is on a different machine to IBM App Connect Enterprise

You can configure the HTTP proxy servlet for a deployment where the HTTP proxy servlet is deployed to a servlet container on a different machine to IBM App Connect Enterprise, with an IBM MQ client link to the integration node queue manager.

In the following figure, the HTTP proxy servlet is running on a remote machine to the integration node. The HTTP proxy servlet connects to the integration node queue manager by using an IBM MQ client connection, the HTTP proxy servlet can be configured to access HTTP or SOAP nodes, and the HTTP or SOAP node configuration is retrieved from the SYSTEM.BROKER.WS.ACK queue.

The diagram is described in the text.

In this configuration example, you must configure the following HTTP proxy servlet configuration parameters. For information about configuring the HTTP proxy servlet, see Configuring the HTTP proxy servlet.

  • Set useClientMode to true.
  • Set useQueueManagerDataInsteadOfConfigFile to * or the integration node queue manager name.
  • Set clientModeHostname, clientModeChannelName, and clientModePortNumber to the correct values as detailed in HTTP proxy servlet configuration parameters.

The HTTP proxy servlet attempts to connect to the remote queue manager for the integration node by reading the required configuration data from the IBM MQ client connection. For the client connection to succeed, you must start the SYSTEM.DEFAULT.LISTENER.TCP listener in the queue manager. For more information, search for START LISTENER in the IBM MQ product documentation.

Before you configure, deploy, and test the HTTP proxy servlet, ensure that you understand the following concepts: When you have gained an understanding of the HTTP proxy servlet concepts, read the following topics to help you configure, deploy, and test the HTTP proxy servlet: