Add the value httpjms or httpsjms to the imq.service.activelist property: for example,

imq.service.activelist=jms,admin,httpjms

or

imq.service.activelist=jms,admin,httpsjms

Set any other HTTP/HTTPS-related
configuration properties as needed.

At startup, the broker looks
for an application server or Web server and an HTTP or HTTPS tunnel servlet running on its local host machine. If necessary,
you can reconfigure the broker to access a remote tunnel servlet instead,
by setting the servletHost and servletPort properties
appropriately (see Table C–2):
for example,

imq.httpjms.http.servletHost=heliosimq.httpjms.http.servletPort=7675

You can also improve performance by reconfiguring the connection service’s pullPeriod property. This specifies the interval, in seconds, at
which each client issues HTTP/HTTPS requests
to pull messages from the broker. With the default value of -1, the
client will keep one such request pending at all times, ready to pull messages
as fast as possible. With a large number of clients, this can cause a heavy
drain on server resources, causing the server to become unresponsive. Setting
the pullPeriod property to a positive value configures
the client’s HTTP/HTTPS transport
driver to wait that many seconds between pull requests, conserving server
resources at the expense of increased response times to clients.

The connectionTimeout property specifies the interval,
in seconds, that the client runtime waits for a response from the HTTP/HTTPS tunnel servlet before throwing an exception, as well as the
time the broker waits after communicating with the tunnel servlet before freeing
a connection. (A timeout is necessary in this case because the broker and
the tunnel servlet have no way of knowing if a client that is accessing the
tunnel servlet has terminated abnormally.)