Configure message-queue Transports
Configure inbound or outbound Microsoft Message Queuing (MSMQ) or IBM MQ exchange against an administrator-provisioned test queue.
Scope
| Family | Verified configuration controls |
|---|---|
| MSMQ | Host, Queue Name, Queue Visibility, Delivery Method, authentication, transaction and direct-format-name choices; inbound also has Read Timeout |
| IBM MQ | Connection Manager, Queue Name and direction-specific server/channel or buffer controls shown by Designer |
Queue names, transaction modes, delivery methods and client libraries are infrastructure contracts. Obtain them from the queue administrator; do not invent or copy production values.
Controlled setup
- Confirm the required client/runtime components are installed on the Velox host and compatible with the target queue manager.
- Create the correct inbound or outbound Transport and leave Active clear.
- Enter the approved host/manager, queue and channel or visibility settings.
- Configure authentication and transaction/delivery options exactly as agreed with the queue administrator.
- Use Test with... and a unique sanitised message. Verify queue depth, message identity and consuming-system outcome independently.
- Save and link the Transport only after confirming that failure and duplicate handling are safe.
Constraints and failure behaviour
- The active configuration screens do not establish compatibility with every MSMQ/IBM MQ version or deployment mode.
- A send return value, queue presence and consumer completion are separate checkpoints.
- Transactional and non-transactional queues are not interchangeable.
- A receive failure can leave a message available, removed or uncertain depending on the queue transaction boundary. Inspect the queue and logs before replay.
- Increasing message/buffer sizes can affect memory and truncation behaviour; test with the largest approved payload.