IBM BJ0NJML - Service And Asset Management Integration Manual page 166

Handlers
CONFACTORYJNDINAM
E Property
DESTINATIONTYPE
Property
DESTJNDINAME
Property
CONTEXTFACTORY
Property
ISCOMPRESS Property
152
The messaging system represents a queue or topic that is available on the local
application server, a remote application server, or a remote dedicated queuing
system such as IBM WebSphere MQ. To use this handler, enable the messaging
systems by using JMS.
The messaging system is distinct from the standard internal queues that are used
by the system. The standard internal queues reside on the local application server
where the system runs.
The JMS handler has the following properties:
This required property specifies a Java object that is used to create connections to
a JMS provider. Before the system can connect to a queue or topic, it must obtain a
reference to a connection factory.
This optional property specifies the JMS destination type; queue or topic.
The following table lists the DESTINATIONTYPE options and their associated
values.
Destination
Topic
Queue
This required property specifies the name by which the JMS queue or topic is
registered in the application server Java Naming and Directory Interface (JNDI)
tree.
This property specifies the initial context factory class name. The property is not
required when the JMS handler is communicating with a JMS provider that
shares the same initial context factory as the application server of the handler.
When the handler and the JMS provider share a WebSphere Application Server,
they share the initial context factory class. The context property value is required
when the handler and the JMS provider do not share a WebSphere Application
Server.
This required property specifies whether the message is compressed before it is
placed it into a queue or topic. Compression is an optimization technique that
delivers smaller messages to a queue or topic.
The following table lists the ISCOMPRESS options and their associated values.
Option
Do not compress data
Compress data
Compressed messages must be decompressed after they are received.
Decompress the messages by creating the appropriate JMS receiver or subscriber
component and placing Java decompression logic within the receiver or
subscriber. Use the standard Java Inflater() class that is part of the java.util.zip
package. The default compression uses the standard Java Deflator() class.
Value
javax.jms.Topic
javax.jms.Queue
Value
0
1
Integration Guide