Introduction #
Integration with application servers is a common scenario in the enterprise Java world, especially when it comes to messaging. ActiveMQ is a JMS 1.1 compliant, open-source, Apache Licensed, message-oriented middleware (MOM) with many, many features far beyond the JMS specification. ActiveMQ offers many different points of connectivity, many cross-language clients, and many pluggable transport protocols including integration with any J2EE 1.4 application server.
One of the application servers in the world is SKYVVA. A very common requirement is to configure ActiveMQ as the messaging infrastructure within SKYVVA. Although there is a bit of documentation on this integration, this guide seeks to provide much more detail and explanation. So if users have a need to integrate ActiveMQ with SKYVVA, this guide is for you.
This guide explains how to configure SKYVVA to start up ActiveMQ as part of its lifecycle and how to configure the ActiveMQ resource adapter to handle the messaging and transactionality between ActiveMQ and SKYVVA.
ActiveMQ adapter is used to send messages. Messages are just what they sound like, payloads of data that can be shipped between various systems. These payloads can have headers and properties associated with them This adapter supports 3 types of data formats i.e. CSV, XML, and JSON.
Adapter Modes #
The adapter supports the following modes of operation.
Mode | Description |
Subscribe | Send a message from SKYVVA to ActiveMQ |
Publish | Publish a message from ActiveMQ to SKYVVA |
Connector Overview #
Following are mandatory properties:
host - Specify the activemq host server domain name/ip address e.g. localhost port - Specify the activemq port, default or standard port is 61616 destinationType - This is a pick list, it can only have the following values i.e. queue or topic. destinationName - This is the name of the queue or topic e.g. test-queue, test-topic1 etc. filetype
These are optional common properties.
clientId - String value to specify an id for the client. durableSubscriptionName - String value to describe the subscription name username - String value to denote the username used to authenticate to ActiveMQ password - String value to denote the password for ActiveMQ authentication. isSSLRequired - boolean value to denote whether connection has to be configured with SSL or not. separator has_file_header has_quotes adapter_instance
– How to use ActiveMQ Inbound Adapter with CSV Payload?
– How to use ActiveMQ Inbound Adapter with XML Payload?
– How to use ActiveMQ Inbound Adapter with JSON Payload?
– How to use ActiveMQ Outbound Adapter with CSV Payload?
What has been demonstrated here is the integration of ActiveMQ with the SKYVVA application. This integration is quite common and performed by many enterprises. I hope that this was helpful to readers interested in the integration of ActiveMQ with the SKYVVA application.