JobScheduler Monitoring Configuration Reference - NotificationJMS

Diagram

Elements

NotificationJMS
References Configuration and Use Cases: NotificationJMS Schema: NotificationJMS, NotificationJMS Release: Availability starting with 1.12: JITL-280 Notes JMS Interface to be executed for System Monitor notification. client_id The client identifier for this connection. destination Queue - creates a Queue object which encapsulates a specified provider-specific queue name. Topic - creates a Topic object which encapsulates a specified provider-specific topic name. acknowledge_mode Session.AUTO_ACKNOWLEDGE - with this acknowledgment mode, the session automatically acknowledges a client's receipt of a message either when the session has successfully returned from a call to receive or when the message listener the session has called to process the message successfully returns. Session.CLIENT_ACKNOWLEDGE - with this acknowledgment mode, the client acknowledges a consumed message by calling the message's acknowledge method. Session.AUTO_ACKNOWLEDGE - this acknowledgment mode instructs the session to lazily acknowledge the delivery of messages. delivery_mode The delivery modes supported by the JMS API are PERSISTENT and NON_PERSISTENT. DeliveryMode.NON_PERSISTENT - this is the lowest-overhead delivery mode because it does not require that the message be logged to stable storage. DeliveryMode.PERSISTENT - this delivery mode instructs the JMS provider to log the message to stable storage as part of the client's send operation. priority The JMS API defines ten levels of priority value, with 0 as the lowest priority and 9 as the highest. Clients should consider priorities 0-4 as gradations of normal priority and priorities 5-9 as gradations of expedited priority. time_to_live Sets the default length of time in milliseconds from its dispatch time that a produced message should be retained by the message system. Time to live is set to zero by default. Possible values: <n> - duration in milliseconds, e.g.: 60000 <n>s - duration in seconds, e.g.: 30s <n>m - duration in minutes, e.g.: 30m <n>h - duration in hours, e.g.: 24h <n>d - duration in days, e.g.: 30d <n>w - duration in weeks, e.g.: 4w Combined values (with blank as separator): e.g.: 1w 1d 1h plugin Java class of the plugin implementation. Extends com.sos.jitl.notification.plugins.notifier.SystemNotifierCustomPlugin Default: com.sos.jitl.notification.plugins.notifier.SystemNotifierSendJMSPlugin
Element	Type	Required	Description
Attribute: client_id	anySimpleType	Optional	The client identifier for this connection.
Attribute: destination	None	Optional	Queue - creates a Queue object which encapsulates a specified provider-specific queue name. Topic - creates a Topic object which encapsulates a specified provider-specific topic name.
Attribute: acknowledge_mode	None	Optional	Session.AUTO_ACKNOWLEDGE - with this acknowledgment mode, the session automatically acknowledges a client's receipt of a message either when the session has successfully returned from a call to receive or when the message listener the session has called to process the message successfully returns. Session.CLIENT_ACKNOWLEDGE - with this acknowledgment mode, the client acknowledges a consumed message by calling the message's acknowledge method. Session.AUTO_ACKNOWLEDGE - this acknowledgment mode instructs the session to lazily acknowledge the delivery of messages.
Attribute: delivery_mode	None	Optional	The delivery modes supported by the JMS API are PERSISTENT and NON_PERSISTENT. DeliveryMode.NON_PERSISTENT - this is the lowest-overhead delivery mode because it does not require that the message be logged to stable storage. DeliveryMode.PERSISTENT - this delivery mode instructs the JMS provider to log the message to stable storage as part of the client's send operation.
Attribute: priority	None	Optional	The JMS API defines ten levels of priority value, with 0 as the lowest priority and 9 as the highest. Clients should consider priorities 0-4 as gradations of normal priority and priorities 5-9 as gradations of expedited priority.
Attribute: time_to_live	NMTOKEN Fixed: 0	Optional	Sets the default length of time in milliseconds from its dispatch time that a produced message should be retained by the message system. Time to live is set to zero by default. Possible values: <n> - duration in milliseconds, e.g.: 60000 <n>s - duration in seconds, e.g.: 30s <n>m - duration in minutes, e.g.: 30m <n>h - duration in hours, e.g.: 24h <n>d - duration in days, e.g.: 30d <n>w - duration in weeks, e.g.: 4w Combined values (with blank as separator): e.g.: 1w 1d 1h
Attribute: plugin	string	Optional	Java class of the plugin implementation. Extends com.sos.jitl.notification.plugins.notifier.SystemNotifierCustomPlugin Default: com.sos.jitl.notification.plugins.notifier.SystemNotifierSendJMSPlugin
ConnectionFactory	Occurrence: 1	Required	References Configuration and Use Cases: ConnectionFactory Schema: ConnectionFactory, ConnectionFactory Notes Using of a JMS ConnectionFactory implementation. java_class Java class of the JMS ConnectionFactory. e.g.: org.apache.activemq.ActiveMQConnectionFactory user_name The caller's user name. password The caller's password.
ConnectionJNDI	Occurrence: 1	Required	References Configuration and Use Cases: ConnectionJNDI Schema: ConnectionJNDI, ConnectionJNDI Notes Using of a JNDI properties file to create a JNDI IntialContextFactory. Sample content of the JDNI properties file for ActiveMQ: java.naming.factory.initial=org.apache.activemq.jndi.ActiveMQInitialContextFactory java.naming.provider.url=tcp://host:61616 file Path to the JNDI properties file. lookup_name Name to lookup JMS connection factory objects.
Message	string Min: 1 Whitespace: preserve Occurrence: 1	Required	References Configuration and Use Cases: Message Schema: Message Notes Body of an JMS notification.

Space shortcuts

Page tree