Integrating STOMP Clients into an Enterprise Middleware Architecture
STOMP stands for Simple (or Streaming) Text Orientated Messaging Protocol. It is supported by many languages amongst others by Perl, PHP, Ruby, Python, C, C++, C# and even Objective C (overview see: STOMP implementations). This makes STOMP very interesting to integrate the users and developers of all theses languages into the jWebSocket infrastructure.
Apache's ActiveMQ comes with an STOMP interface and since ActiveMQ is fully supported by the jWebSocket JMS Gateway all STOMP clients automatically can interact with the jWebSocket services. To make STOMP available in ActiveMQ simply add the STOMP connectors to the ActiveMQ configuration file. In apachemq.xml add the STOMP transportConnector:
<transportConnectors> <!-- DOS protection, limit concurrent connections to 1000 and frame size to 100MB --> <transportConnector name="openwire" uri="tcp://0.0.0.0:61616 ?maximumConnections=1000&wireformat.maxFrameSize=104857600"/> <transportConnector name="stomp" uri="stomp://localhost:61613 ?maximumConnections=1000&wireformat.maxFrameSize=104857600"/> <transportConnector name="amqp" uri="amqp://0.0.0.0:5672 ?maximumConnections=1000&wireformat.maxFrameSize=104857600"/> </transportConnectors>
Apache ActiveMQ 5.8.0 supports STOMP 1.0, 1.1 and 1.2 clients.
Copyright © 2013 Innotrade GmbH. All rights reserved.