Introduction

• JS7 - Notification Notifications - Configuration is performed from the Configuration->Notification sub-view of the JOC Cockpit and includes setting up the configuration for the JS7 - Monitor Service.

• The JMSFragment element is used to integrate with a JMS compatible Java Message Queue product and to parameterize messages from JS7 - Notification - Configuration, Monitor Variables.

JMSFragment

JMSFragment supports the following attributes: 

...

Body of a JMS notification. Any JS7 - Notification - Configuration, Monitor Variables can be used with the body.

Example for Apache ActiveMQ

Configuration

For use with Apache ActiveMQ a JMSFragment configuration can look like this:

<JMSFragment acknowledge_mode="Session.CLIENT_ACKNOWLEDGE" delivery_mode="DeliveryMode.PERSISTENT" destination="Queue" destination_name="js7" name="js7_on_failure" priority="4" time_to_live="0">
    <MessageRef ref="command_on_failure"/>
    <ConnectionFactory java_class="org.apache.activemq.ActiveMQConnectionFactory" password="admin" user_name="admin">
        <ConstructorArguments>
            <Argument type="java.lang.String"><![CDATA[tcp://activemq-5-15:61616]]></Argument>
        </ConstructorArguments>
    </ConnectionFactory>
</JMSFragment>

Client Libraries

The JS7 does not ship with client libraries for specific JMS server products such as Apache ActiveMQ, Apache Kafka and others.

Instead, users have to provide a version of the libraries that match their JMS server product. 

• Download
  • As an example for ActiveMQ 5.15 the following Java libraries are used:
    • Download: https://repo1.maven.org/maven2/org/apache/activemq/activemq-client/5.15.15/activemq-client-5.15.15.jar
    • Download: http://www.java2s.com/Code/JarDownload/javax.management/javax.management.j2ee-3.1.2.2.jar.zip
      • From the archive extract the javax.management.j2ee-3.1.2.2.jar library.
    • Download: https://repo1.maven.org/maven2/org/fusesource/hawtbuf/hawtbuf/1.11/hawtbuf-1.11.jar
      • This library is required due to bug https://issues.apache.org/jira/browse/AMQ-6600
  • The resulting Java libraries are
    
    • activemq-client-5.15.15.jar
    • hawtbuf-1.11.jar
    • javax.management.j2ee-3.1.2.2.jar
• Deployment
  • If JOC Cockpit is used on premises then store the .jar files in the JETTY_BASE/lib/ext/joc directory.
  • If JOC Cockpit is operated from a Container the store the .jar files in the JETTY_BASE/resources/joc/config/patches directory.
• Restart
  • JOC Cockpit has to be restarted to make use of the Java libraries.