XMS .NET property mapping for administered objects

To enable XMS .NET applications to use IBM® MQ JMS and WebSphere® Application Server connection factory and destination object definitions, the properties that are retrieved from these definitions must be mapped on to the corresponding XMS properties that can be set on XMS connection factories and destinations.

To create, for example, an XMS connection factory with properties that are retrieved from an IBM MQ JMS connection factory, the properties must be mapped between the two.

All property mappings are performed automatically.

Table 1 demonstrates the mappings between some of the most common properties of connection factories and destinations. The properties that are shown in this table are just a small set of examples, and not all properties that are shown are relevant to all connection types and servers.
Table 1. Examples of name mapping for connection factory and destination properties
IBM MQ JMS property name XMS property name WebSphere Application Server service integration bus property name
PERSISTENCE (PER) XMSC_DELIVERY_MODE  
EXPIRY (EXP) XMSC_TIME_TO_LIVE
PRIORITY (PRI) XMSC_PRIORITY
  XMSC_WPM_HOST_NAME serverName
XMSC_WPM_BUS_NAME busName
XMSC_WPM_TOPIC_SPACE topicName
Note: The properties shown in Table 2 are applicable for JMS as well as XMS .NET.
Table 2. XMS .NET properties
Property Object type
CF QCF TCF Queue Topic
APPLICATIONNAME Y Y Y N/A N/A
ASYNCEXCEPTION Y Y Y N/A N/A
CCDTURL Y Y Y N/A N/A
CHANNEL Y Y Y N/A N/A
CONNECTIONNAMELIST Y Y Y N/A N/A
CLIENTRECONNECTOPTIONS Y Y Y N/A N/A
CLIENTRECONNECTTIMEOUT Y Y Y N/A N/A
CLIENTID N/A Y N/A N/A N/A
COMPHDR 1 Y N/A Y N/A N/A
COMPMSG 1 Y Y Y N/A N/A
CONNOPT 1 Y Y Y N/A N/A
CONNTAG 1 Y Y Y N/A N/A
DESCRIPTION 1 N/A Y N/A Y Y
EXPIRY 1 N/A N/A N/A Y Y
FAILIFQUIESCE Y Y Y Y Y
HOSTNAME N/A Y N/A N/A N/A
LOCALADDRESS N/A Y N/A N/A N/A
PERSISTENCE N/A N/A N/A Y Y
PORT N/A Y N/A N/A N/A
PRIORITY 1 N/A N/A N/A Y Y
PROVIDERVERSION 1 N/A Y N/A N/A N/A
QMANAGER Y Y Y Y N/A
QUEUE 1 N/A N/A N/A Y N/A
SHARECONVALLOWED Y Y Y N/A N/A
TOPIC 1 N/A N/A N/A N/A Y
TRANSPORT 1 N/A Y N/A N/A N/A
Note:
  1. These properties do not have application level properties but they can optionally be set using administered properties.
[MQ 9.2.4 Nov 2021]

OutboundSNI property

From IBM MQ 9.2.4, you can set the XMSC_WMQ_OUTBOUND_SNI property, which sets the OutboundSNI property in an application.

The XMSC_WMQ_OUTBOUND_SNI_PROPERTY takes the following values:
  • XMSC_WMQ_OUTBOUND_SNI_CHANNEL, which maps to "CHANNEL"
  • XMSC_WMQ_OUTBOUND_SNI_HOSTNAME, which maps to "HOSTNAME"
  • XMSC_WMQ_OUTBOUND_SNI_ASTERISK, which maps to "*"
Additionally, you can set the OutboundSNI property using the MQOUTBOUND_SNI environment variable, which takes the following values:
  • CHANNEL
  • HOSTNAME
  • *
Note: The property defaults to XMSC_WMQ_OUTBOUND_SNI_CHANNEL if no specific value is set.
The order of precedence for setting the OutboundSNI property in the managed node is:
  1. Application level property
  2. Environment variable

For the OutboundSNI property in unmanaged node, mqclient.ini only is supported.