IBM BJ0NJML - Service And Asset Management - Creating and Configuring a Queue

Creating and Configuring a Queue
164
Integration Guide
Creating and Configuring a Queue
You can use separate queues, one for each external system that you use. Queues
can be configured for use with publish channels and enterprise services that
integrate with one or more external systems. Queue creation and configuration
involves multiple steps.
1 Create and configure the message queue on the application server.
2 In the External Systems application, add properties to the queue.
The following properties are available for each queue.
You can create additional queues to meet system needs. If you do not use the
default queues, use an application server provider for your queue
configuration.
Use the System and Enterprise Services tabs in the External Systems
application.
Property Description
Queue JNDI Name References the Java Naming and Directory Interface (JNDI) name that
is configured on the application server. A default value is provided.
Queue Connection Factory Name References the Connection Factory name that is configured on the
application server. A default value is provided.
Initial Context Factory A value that you must configure when you do not to use the default
queues and do not use a provided application server.
Provider URL A value that you must configure when you do not to use the default
queues and do not use a provided application server.
User ID The user ID that you configure when the queue is secured on the
application server.
Password The password that is configured when the queue is secured in the
application server for the user ID.
Inbound Identifies whether the queue is used for inbound processing. If the
inbound value is null, the system uses the queue for outbound
processing.
Sequential Identifies whether the queue is a sequential queue. If the sequential
value is null, the system uses the queue for continuous queue
processing.
Compress Identifies whether the messages are compressed when they are written
to the queue and decompressed when they are pulled from the queue.
Compression provides significantly reduced message sizes. The
standard Java Inflater and Deflater APIs (java.util.zip) are used for
compression.
Maximum Try Count Identifies how many times the integration framework attempts to
reprocess a message after it encounters an error. The system continues
to retry the message until the count value is met. The value of this
property must be set to zero when an error queue is implemented.