How to prioritize messages in XI

[Former Member]

How to prioritize messages in XI

   

      Some scenarios require processing messages with priority;        these situations can be managed by sending them to a queue of        higher priority.     

   

      The following transactions will be used:      

SXMB_ADM - Configure Sender/Receiver ID

     

SXMB_ADM - Configure Filter for Queue Prioritization

     

SXMB_MONI - Monitor for Processed XML Messages

       

      The process to prioritize a message goes as follows:      

Configure sender/receiver IDs

     

Configure the filter criteria

     

Activate the filter

       

      So first we need to configure IDs for the sender service and/or for the       receiver service. After creating a new entry we'll need       to define at least the following fields:      

Service. Either source or destination service

     

Interface Name. Either sender or receiver interface

     

Interaface Namespace. Automatically assigned

       

      In this weblog I'll show how to prioritize a message in an outbound        queue, so a sender and a receiver must be defined. When using an       inbound queue just the sender is needed. The following image       shows the configuration:    

             

             

   

      Next we'll configure the filter to prioritize all the messages which       come from the Sender ID and which are send to the Receiver ID       that we defined.     

             

             

   

      After adding the filter we should have a table like the following:    

             

             

   

      Finally the filter has to be activated; therefore the row should show       the "active" status.    

             

             

   

      In order to check whether the message is being sent to the right        queue we can monitor the messages in SXMB_MONI. The messages should be sent to the        right queue after the activation.     

             

             

   

      The queue XBTL, which handles large messages, can't be deactivated or deleted because        it is in charge of maintaining the processor workload stable. The parameter        EO_MSG_SIZE_LIMIT can be configured to define what a large message size is.        Please read carefully the       XI Tuning Guide      if you are planning to change this criteria.