IBM MQ objects on the IBM MQ Appliance
Some objects on the IBM® MQ Appliance have different behavior than objects on an IBM MQ installation.
Listeners
When creating listeners on the IBM MQ Appliance, you
should configure the listener to start and stop with the queue manager. You can set the listener by
using the CONTROL(QMGR)
argument to the DEFINE LISTENER MQSC
command (see DEFINE LISTENER in the IBM MQ documentation). Alternatively, you can use the IBM MQ Console (see
IBM MQ Console: Working with listeners).
Even if you leave the control property of a listener set to manual, note that it will automatically stop when the queue manager stops on the appliance.
Channels
The default client channel definition table (CCDT) for a queue manager is not automatically available on the IBM MQ Appliance. Use the rcrmqobj command to generate a CCDT file for a queue manager. The generated CCDT file can be downloaded from the appliance from the mqbackup:// URI (see Creating and downloading a CCDT file).
For more information about client channel definition tables see Client channel definition table in the IBM MQ documentation.
XA transactions
Queue managers on an IBM MQ Appliance cannot act as XA transaction managers.
Queue managers on the appliance can participate in global transactions as resource managers, but they cannot act as transaction managers and coordinate external services.
An IBM MQ client that connects to a queue manager on an appliance is not able to issue an MQBEGIN API call. The means that the client cannot start a transaction with the queue manager acting as transaction manager. For more information, see Configuring an extended transactional client and MQBEGIN - Begin unit of work in the main IBM MQ documentation.