Message queue configuration

The external system defined for the cron task that imports software catalogs uses the default Control Desk queue names and continuous queues.

Table 1. Default queues for Control Desk
Queue name Java™ Naming and Directory Interface (JNDI) name
Sequential queue in jms/maximo/int/queues/sqin
Sequential queue out jms/maximo/int/queues/sqout
Continuous queue in jms/maximo/int/queues/cqin
Continuous error queue jms/maximo/int/queues/cqerr

Configuration of the queues is performed using the console provided by the application server. For detailed information about configuring the queues, see the documentation provided with your application server. If you use WebSphere® Application Server, the installer ensures that these queues are defined. If you use Oracle WebLogic Server, you must manually configure these queues.

The following parameters are important in queue configuration; you can access them using the application server console.
  • Reprocessing Delay: A delay of at least several seconds is desirable so that dependencies are committed to the database before reprocessing occurs.
  • Reprocessing Timeout: The timeout must allow for reprocessing due to dependencies, but eliminate records once the likelihood of a dependency being loaded passes (usually several seconds).
  • Error Destination – Errors can be placed in files on the operating system, discarded, or placed in error queues. If using the continuous queue, messages should not be immediately discarded because some reprocessing is required by design.
In addition, you can also use the Number of retries field in the Add/Modify Queues window in the External Systems application to specify the number of attempts.


Feedback