TsgcWSPClient_STOMP_ActiveMQ

This is the Client Protocol STOMP Component for ActiveMQ Broker. You need to drop this component in the form and select a TsgcWebSocketClient Component using Client Property.

 

Destinations

The STOMP specification does not prescribe what kinds of destinations a broker must support, instead the value of the destination header in SEND and MESSAGE frames is broker-specific. The Active STOMP adapter supports a number of different destination types:

 

• Topic: SEND and SUBSCRIBE to transient and durable topics.
• Queue: SEND and SUBSCRIBE to queues managed by the STOMP gateway.

 

Publish Options

Note that STOMP is designed to be as simple as possible - so any scripting language/platform can message any other with minimal effort. STOMP allows pluggable headers on each request such as sending & receiving messages. ActiveMQ has several extensions to the Stomp protocol, so that JMS semantics can be supported by Stomp clients. An OpenWire JMS producer can send messages to a Stomp consumer, and a Stomp producer can send messages to an OpenWire JMS consumer. And Stomp to Stomp configurations, can use the richer JMS message control.

 

STOMP supports the following standard JMS properties on SENT messages:

 

• CorrelationId: Good consumers will add this header to any responses they send.

• Expires: Expiration time of the message.

• JMSXGroupID: Specifies the Message Groups.

• JMSXGroupSeq: Optional header that specifies the sequence number in the Message Groups.

• Persistent: Whether or not the message is persistent.

• Priority: Priority on the message.

• ReplyTo: Destination you should send replies to.

• MsgType: Type of the message.