Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Table of Contents

Introduction

  • A JMSFragment can be used with the configuration of notifications in order to integrate with a Java Message Queue product that is JMS compatible.

JMSFragment

JMSFragment supports the following attributes: 

...

ElementElement descriptionDescription
MessageRequired, only once inside of JMSFragment elementBody of a JMS notification

ConnectionFactory

Specifies use of a JMS ConnectionFactory implementation.

...

ElementElement descriptionDescription
ConstructorArgumentsOptional or only once inside of ConnectionFactory element  

 ConstructorArguments

The following elements can be nested inside a ConstructorArguments element:

...

Code Block
languagexml
titleExample: ActiveMQConnectionFactory with 3 constructor arguments
collapsetrue
...
<ConnectionFactory java_class="org.apache.activemq.ActiveMQConnectionFactory">
    <ConstructorArguments>
        <Argument type="java.lang.String"><![CDATA[my_user_name]]></Argument>
        <Argument type="java.lang.String"><![CDATA[my_password]]></Argument>
        <Argument type="java.lang.String"><![CDATA[tcp://localhost:61616]]></Argument>
    </ConstructorArguments>
</ConnectionFactory>
...

 Argument

 Argument supports the following attributes: 

...

Code Block
languagexml
titleExample
collapsetrue
...
<Argument type="java.lang.String"><![CDATA[tcp://localhost:61616]]></Argument>
...

ConnectionJNDI

Specifies use of a JNDI properties file to create a JNDI InitialContextFactory.

...

Code Block
languagetext
titleExample: content of the JNDI properties file for ActiveMQ
java.naming.factory.initial=org.apache.activemq.jndi.ActiveMQInitialContextFactory
java.naming.provider.url=tcp://localhost:61616 

Message

Body of a JMS notification. Any Monitor Variables can be used with the body.

...