Installing the JMS Connectors to Create JMS Listeners and Web Services with SOAP Over JMS¶
The first time you create a JMS listener or the first time you create a SOAP web service with the feature SOAP over JMS enabled, follow these steps (you only have to do this once):
Obtain the JMS connector from the installation of your JMS broker.
This connector has to implement the Jakarta Messaging API. Old JMS connectors implement the Javax JMS API, which is not supported. For example, to connect to ActiveMQ use the ActiveMQ 6.x connector (not an older connector) because this one does use the new Jakarta Messaging API.
Deploy this connector in your installation of Denodo. The process is different depending on what you are going to do:
To create JMS listeners, first follow these steps:
Log in to Design Studio with an administrator account.
Click the menu File > Extensions management.
Click the tab Libraries and then, click Import.
In the new dialog, in Resource type, select jar.
Click Add and select the file(s). To select more than one file, hold the key Ctrl and select each file.
Click Ok to upload the file(s) to Virtual DataPort.
To create web services with the feature *SOAP over JMS* enabled, first copy the .jar files of the JMS connector to the directory
<DENODO_HOME>/resources/apache-tomcat/lib
.If you are going to deploy the web services with the feature SOAP over JMS enabled in an external application server, copy these .jar files to the
/WEB-INF/lib
directory of the generated war file, before deploying it.
JMS Client Jars¶
The jars required from the connector installation depends on each vendor. The following table shows an example on the most common used JMS vendors:
Vendor |
Location of these Jars in the Installation of the Vendor |
Jars you Have to Upload to Virtual DataPort |
---|---|---|
Apache ActiveMQ |
<ACTIVE_MQ_HOME>/lib |
activemq-broker.jar activemq-client.jar activemq-openwire-legacy.jar hawtbuf.jar |