HTTP proxy servlet is deployed to a servlet container on a machine with its own queue manager

You can configure the HTTP proxy servlet for a deployment where the HTTP proxy servlet is deployed to a servlet container that is on a machine with its own queue manager and an IBM MQ channel link to the integration node queue manager.

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 useClusterMode to true.
  • Set clusterModeQueueManagerName to the queue manager of the Web servlet container.
  • Set clusterModeReplyToQ to a queue that exists on that queue manager.

The HTTP proxy servlet attempts to open the queue SYSTEM.BROKER.WS.INPUT on the specified queue manager by using the queue manager name from the configuration file. Therefore, you must set up channels and transmit queues beforehand to ensure that the messages arrive on the queue manager of the integration node.

You must copy the configuration files from the integration node machine in this scenario.

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: