To fix a problem with MQ connection issue, we were advised to add the following custom properties

to the MQ Activation Specification:

clientID

subscriptionName

providerVersionWhen I tried to execute the below command, the custom properties were not added to the activation spec:

-------------

AdminJMS.createWMQActivationSpec("Node=xxxNode,Server=xxxServer","xxxQueue" ,"jms/xxxQueue",'javax.jms.Queue', [["qmgrName", "xxxQM"], ["qmgrHostname", "xxxHost"], ["qmgrPortNumber", "1414"], ["wmqTransportType", "CLIENT"], ["maxPoolSize","2"], ["failureDeliveryCount", "3"], ["stopEndpointIfDeliveryFails", "false"], ["msgRetention", "YES"], ["clientId", " "], ["subscriptionName", " "],["providerVersion", " "]])

AdminConfig.save()

-----------------

Is the above syntax correct? How can I add the above parameters with NULL values to the activation spec?

Unfortunately, AdminJMS.createWMQActivationSpec() doesn't permit NULL or empty-string values. The solution to this is to create with the non-NULL parameters and add the NULL parameters via the AdminTask.modifyWMQActivationSpec() method. Please try:

ActSpec = AdminJMS.createWMQActivationSpec("Node=xxxNode,Server=xxxServer","xxxQueue" ,"jms/xxxQueue",'javax.jms.Queue', [["qmgrName", "xxxQM"], ["qmgrHostname", "xxxHost"], ["qmgrPortNumber", "1414"], ["wmqTransportType", "CLIENT"], ["maxPoolSize","2"], ["failureDeliveryCount", "3"], ["stopEndpointIfDeliveryFails", "false"], ["msgRetention", "YES"]])

AdminTask.modifyWMQActivationSpec(ActSpec, '[-clientId -providerVersion -subscriptionName]')

AdminConfig.save()

That should create properties with null value.