To configure the STOMP bridge, you specify several imq.bridge.stomp broker properties in the broker hosting the bridge. These properties, which control the various features of the STOMP bridge, are listed in Table 12–10.
Table 12–10 Broker Properties for the STOMP Bridge Service
Property |
Type |
Default Value |
Description |
---|---|---|---|
imq.bridge.stomp.tcp.enabled |
Boolean |
true |
Does the STOMP bridge accept TCP connections? |
imq.bridge.stomp.tcp.port |
Integer |
7672 |
The port on which the STOMP bridge listens for TCP connections, provided that imq.bridge.stomp.tcp.enabled is true. |
imq.bridge.stomp.tls.enabled |
Boolean |
false |
Does the STOMP bridge accept SSL/TLS connections? If true, a keystore must be created using the imqkeytool utility before starting the broker. |
imq.bridge.stomp.tls.port |
Integer |
7673 |
The port on which the STOMP bridge listens for SSL/TLS connections, provided that imq.bridge.stomp.tls.enabled is true. |
imq.bridge.stomp.tls.requireClientAuth |
Boolean |
false |
Do SSL/TLS connections require client authentication? |
imq.bridge.stomp.consumerFlowLimit |
Integer |
1000 |
The maximum number of unacknowledged messages that the STOMP bridge will deliver on a transacted STOMP subscription. The STOMP client must then acknowledge the messages and commit the transaction. |
imq.bridge.stomp.messageTransformer |
String |
None |
The fully qualified class name of a class that extends the Message Queue bridge MessageTransformer abstract class (with formal type parameters as javax.jms.Message). Place this class under the IMQ_HOME/lib/ext directory. |
imq.bridge.stomp.logfile.limit |
Integer |
0 |
The approximate maximum number of bytes the STOMP bridge writes to any one log file. A value of 0 (zero) indicates that there is no maximum limit. |
imq.bridge.stomp.logfile.count |
Integer |
1 |
The number of log files the STOMP bridge cycles through. |