IT37206: IMPROVE DOCUMENTATION FOR THE QUEUEMANANGERNAME ESQL PROPERTY

APAR status

• Closed as documentation error.

Error description

• The existing documentation for the QueueManagerName property in
  ESQL does not make it clear enough that this value only applies
  to the local default queue manager configured on the integration
  node or independent integration server (e.g. the
  defaultQueueManager setting in the node.conf.yaml and
  server.conf.yaml files). The QueueManagerName property will be
  set to the empty string in other circumstances, such as when a
  default MQEndpoint policy is configured.
  
  When using an integration node or independent integration server
  with a local default queue manager configured will not start if
  this queue manager is not available, and will shutdown if the
  queue manager becomes unavailable at any point. The queue
  manager becomes a key part of the integration node or server's
  configuration and as such is available through the
  QueueManagerName property in ESQL.
  
  On the other hand, a default MQEndpoint policy specifies the
  default connection details to use when using various aspects of
  the product which can talk to queue managers other than the
  default queue manager. The lifecycle of the integration node or
  server is not tied to this queue manager being available all the
  time and as such is not a key component of the configuration and
  is not reflected in the QueueManagerName property.
  

Local fix

• N/A
  

Problem summary

• ****************************************************************
  USERS AFFECTED:
  All users of the QueueManagerName property in ESQL,
  iib:getQueueManagerName() Mapping node function, or
  MbNode.getBroker().getQueueManagerName() function in Java
  Compute nodes in IBM App Connect Enterprise v11 or v12 running
  in an independent Integration Server with a remote default queue
  manager specified.
  
  
  Platforms affected:
  MultiPlatform
  
  ****************************************************************
  PROBLEM DESCRIPTION:
  The existing documentation for the QueueManagerName property in
  ESQL does not make it clear enough that this value only applies
  to the local default queue manager configured on the integration
  node or independent integration server (e.g. the
  defaultQueueManager setting in the node.conf.yaml and
  server.conf.yaml files). The QueueManagerName property will be
  set to the empty string in other circumstances, such as when a
  default MQEndpoint policy is configured.
  
  When using an integration node or independent integration server
  with a local default queue manager configured it will not start
  if this queue manager is not available, and will shutdown if the
  queue manager becomes unavailable at any point. The queue
  manager becomes a key part of the integration node or server's
  configuration and as such is available through the
  QueueManagerName property in ESQL.
  
  On the other hand, a default MQEndpoint policy specifies the
  default connection details to use when using various aspects of
  the product which can talk to queue managers other than the
  default queue manager. The lifecycle of the integration node or
  server is not tied to this queue manager being available all the
  time and as such is not a key component of the configuration and
  is not reflected in the QueueManagerName property.
  

Problem conclusion

• The documentation has been updated to reflect that these values
  all refer to the defaultQueueManager setting in the
  server.conf.yaml files. It never refers to the name of a remote
  default queue manager as specified by an MQEndpoint policy.
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels