Watson Supply Chain Ideas

Submit new product ideas for Watson Supply Chain solutions. Before you submit, please review existing ideas; if an idea close to yours already exists, it's better to add comments or vote on the existing idea. We will review your ideas and use them to help prioritize our product development. Best of all, the portal will automatically update you when the status of your idea has been changed. Order Management, Store Engagement, Watson Order Optimizer, Inventory Visibility, CPQ and Call Center are now part of Watson Supply Chain

Connect with IBM experts and your peers on the Supply Chain Collaboration Community and the Order Management Interest Group

Submit ideas for other Watson Customer Engagement Products:

Watson Marketing
Watson Campaign Automation
Watson Commerce

Alternative to +SETALL permissions requirement on IBM MQ Adapter connections using -EQN

IBM MQ Adapter connections often use the -EQN facility to designate an alternate queue from the input -QN so that error messages do not get stuck in the input queue and interfere with message processing over time.

 

The use of -EQN requires the +SETALL permission on the IBM MQ server for the given itxuser.  Presumably this is because the -EQN function is using the full -HDR syntax on PUT to preserve all current MQMD settings.  E.g., the message is being copied as is instead of being re-created.

 

Unfortunately, our organization has identified +SETALL as a security risk because the so granted itxuser has the same effective authority level as the MQ administrators.  This elevated access needs to be removed, but in doing so, the -EQN setting no longer works.

 

In discussions with IBM Support the implication was that the current usage of -EQN cannot be altered due to impacts to other clients. 

 

Therefore, I propose a new optional command be added to the IBM MQ Adapter to be used in conjunction with the -EQN command.  Essentially, the new command tells -EQN to either continue using the default behavior of -HDR (preserving current MQMD settings), or to allow -DH on -EQN (effectively putting a new message).

 

This means that users that do not want to use the flag will continue to have the default behavior and require no code changes as long as they accept the usage of +SETALL permissions.  For those that cannot allow the +SETALL permissions, the new command would allow -EQN to continue to work with a minor update to the IBM MQ Adapter connection settings.  While this does create a new message and deletes the current MQMD, our organization has decided this is an acceptable loss.  In general, we are not exploiting those header settings for reprocessing anyway, but rather using message content.

  • Avatar32.5fb70cce7410889e661286fd7f1897de Guest
  • Jun 24 2019
  • Under Consideration
How will this idea be used?

To alleviate an enterprise security concern and still utilize the -EQN function.  Without this enhancement we will have to discontinue usage of the -EQN command and instead use BackUp OnError on the input card to save the message as a file.  This will require the additional rework of the error processing for these processes.  As we have hundreds of queues, or primary adapter, the potential re-work to accommodate the security concern will be large.   

What is your industry? Retail
What is the idea priority? Urgent
DeveloperWorks ID
RTC ID
Link to original RFE
  • Attach files