Queue Utilities
JMS Queue Configuration
173
Applying selectors splits a queue into smaller queues, each of which contains a
subset of data that each cron task or message-driven bean uses. An error in one
subset of the data does not stop processing in the others in a sequential queue.
While selectors provide flexibility in separating the processing of transactions,
they impair the performance of poll processing. Depending on the volume of
transactions, you might prefer to implement multiple queues instead of one
queue with multiple selectors. Multiple queues typically provide better
performance.
You can add the following statement to the SELECTOR property of the SEQQIN
instance of the JMSQSEQCONSUMER to instruct the cron task to process the
MXPOInterface and MXPRInterface transactions from the corresponding external
system:
SENDER=’EXTSYS1’ and INTERFACE in (‘MXPOInterface’,
‘MXPRInterface’)
Add the following content to the message bean configuration (ejb-jar.xml) to
instruct the message-driven bean to process the MXPOInterface and
MXPRInterface transactions from the corresponding external system:
<message-selector> SENDER=’EXTSYS1’ AND INTERFACE IN
(‘MXPOInterface’, ‘MXPRInterface’)</message-selector>
If two external systems send data to an inbound sequential queue, an error in any
record stops the processing of all transactions in that queue to maintain a
first-in-first-out processing order. Create multiple instances of a cron task, each
with a selector that processes a different external system, to prevent an error in
one system from stopping transactions from the second system.
Ensure that the where clauses in the selectors identify the mutually exclusive sets
of transactions in a sequential queue. Include all the transactions that are inserted
into the queues to ensure that all messages are processed in a first-in-first-out
order.
Queue Utilities
You can see the properties and the number of messages in a queue, but not the
content of the messages. The system provides the following utilities for viewing
and deleting messages in the queues.
The viewqueue utility places the data in the view folder under the integration
global directory.
Use the deletequeue utility in a test or development environment. The Message
Reprocessing application provides a mechanism for deleting individual messages
from the production queues.
Utility
File
viewqueue
viewqueue.bat and viewqueue.sh
deletequeue
deletequeue.bat and deletequeue.sh
Summary of Contents for BJ0NJML - Service And Asset Management
Page 12: ...xii Integration Guide ...
Page 14: ...xiv Integration Guide ...
Page 16: ......
Page 31: ...Integration Framework for User Interface Integration Integration Framework Architecture 17 ...
Page 32: ...Integration Framework for User Interface Integration 18 Integration Guide ...
Page 60: ...Synchronous Inbound Integration Processing 46 Integration Guide ...
Page 122: ...Configuring External Systems 108 Integration Guide ...
Page 142: ...Non queue Error Management 128 Integration Guide ...
Page 154: ...Integration Components 140 Integration Guide ...
Page 156: ......
Page 172: ...Writing Custom Handlers 158 Integration Guide ...
Page 176: ...Queue Tables 162 Integration Guide ...
Page 190: ...IBM WebSphere MQ 176 Integration Guide ...
Page 212: ...Inbound Message Receipt 198 Integration Guide ...
Page 226: ...Integration Controls 212 Integration Guide ...
Page 252: ...Predefined External System Modifications 238 Integration Guide ...
Page 263: ...Web Service Queries Integration Queries 249 ...
Page 264: ...Web Service Queries 250 Integration Guide ...
Page 272: ...Integration Web Service Invocations 258 Integration Guide ...
Page 276: ...Multilanguage Attributes 262 Integration Guide ...
Page 293: ...Integration Module Invocation Integration Modules 279 ...
Page 294: ...Integration Module Invocation 280 Integration Guide ...
Page 302: ...Associating a Condition with a Signature Option 288 Integration Guide ...
Page 320: ...Work Order Collaboration Switches 306 Integration Guide ...
Page 324: ...310 Integration Guide ...