MQSeries Priority Header Value On The MQ Message Is Not Set When Using EAI JMS Transport Send Method

(Doc ID 2238338.1)

Last updated on FEBRUARY 27, 2017

Applies to:

Siebel Financial Services CRM - Version 15.3 [IP2015] and later
Information in this document applies to any platform.

Symptoms

PRODUCT VERSIONS:
------------------------------
SIEBEL VERSION: Siebel 15.0 + PatchSet 3
SIEBEL APP O/S: Microsoft Windows x64 (64-bit)

ISSUE STATEMENT:
----------------------------

When using Siebel EAI JMS Tranport business service Send method to send a message to MQ queue, the JMSPriority argument was set to a value of 9. However, when the message arrived into MQ queue and viewing the message, the Priority header shows value of 0.

WHERE IT HAPPENED:
-------------------------------
The issue happens in Development environment.

STEPS TO REPRODUCE:
---------------------------------
The behaviour occurs as follows:

1. Launch Siebel Client application.

2. Navigate to Siebel Web Client > Business Service Simulator View > simulate business service EAI JMS Transport Send method and provide arguments like the following:

The inputs for the Send method are:

Value field:

Property Name mvg:

SendUsername:       <provide correct username>
SendPassword:        <provide correct password>
ConnectionFactory:   <provide correct connection factory name>
JMSPriority:              9 <or provide whatever value you wish here>
SendQueue:             <provide correct queue name>

3. Check the message on the MQ queue, the Priority header shows value of 0.

EXPECTED BEHAVIOR:
-------------------------------
The expected behaviour is that the JMSPriority value passed in the message would be set on the message itself once it arrives into MQ queue.

WHAT IS WORKING:
------------------------------
Another header JMSType was set to a value of MQSTR and it shows up in the message with Msg.format = MQSTR.

LOSS OF FUNCTIONALITY / BUSINESS IMPACT:
--------------------------------------------
There are some issues with how fast the messages are processed for certain transactions, some transactions need to be processed ahead of others and not necessarily based on their arrival onto the queue, thus the messages need to have a Priority to ensure the other system is processing the message according to the Priority level set on the message. Since Siebel is not setting the Priority level as desired, the messagse are not processed in the desired order/priority.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms