System Administration - CMICRTI, Dropping/Creating Queues

The CMICRTI process can be configured on more than one JSP server.

Requirements for CMICRTI

  1. Groovy should be installed on the app servers under D:\cm\  path.

  2. The CMICRTI server process must be scheduled to run from the task scheduler, at system startup. Command file to be run in D:\cm\ias\j2ee\ENV\bin\cmicrti_ENV.cmd.

When messages are not processed and they just keep adding to the queue, then we either drop or recreate the queues for them. The customer will have to decide if they want to purge the queue instead of allowing the messages to be processed, as there is no way to recover messages that are purged.

Stop and Drop the Queues

Run the following statements to stop and then drop each RTI queue and queue table:

Copy 
EXECUTE dbms_aqadm.stop_queue(Queue_name => 'RTI_ERROR_Q'); 
EXECUTE dbms_aqadm.drop_queue(Queue_name => 'RTI_ERROR_Q'); 
EXECUTE dbms_aqadm.drop_queue_table(Queue_table => 'RTI_ERROR_Q_T'); 
EXECUTE dbms_aqadm.stop_queue(Queue_name => 'RTI_INBOUND_Q'); 
EXECUTE dbms_aqadm.drop_queue(Queue_name => 'RTI_INBOUND_Q'); 
EXECUTE dbms_aqadm.drop_queue_table(Queue_table => 'RTI_INBOUND_Q_T'); 
EXECUTE dbms_aqadm.stop_queue(Queue_name => 'RTI_OUTBOUND_Q'); 
EXECUTE dbms_aqadm.drop_queue(Queue_name => 'RTI_OUTBOUND_Q'); 
EXECUTE dbms_aqadm.drop_queue_table(Queue_table => 'RTI_OUTBOUND_Q_T'); 
Recreate the Queues

As user UIG, run script rtiqueue.que, which would typically be found on the server at d:\cm\v12\<environment>\uig\sql\. This script creates and enables all queues, nothing else should need to be done.