Configure the WebSphere MQ Agent
Supported for: Windows and Linux
This task describes how to configure the WebSphere MQ Agent.
The WebSphere MQ Agent uses the IBM WebSphere MQ Client internally. This enables you to use all diagnostic tools and logs provided by the client if you need to investigate any issues with WebSphere MQ communication between HPE Service Virtualization and the IBM WebSphere MQ Server.
The WebSphere MQ Agent is not installed by default. The agent is dependent on the IBM WebSphere MQ Client 188.8.131.52 or later (
amqmdnet.dll library with version 184.108.40.206 and its dependencies). The IBM WebSphere MQ Client full installation places the required library in the Global Assembly Cache (GAC), making the agent available. If you install the client while the Service Virtualization Server or Designer is running, you must restart the application prior to enabling the agent.
The WebSphere MQ Agent uses the IBM WebSphere MQ Client internally. This enables you to use all diagnostic tools and logs provided by the client if you need to investigate any issues with WebSphere MQ communication between Service Virtualization and the IBM WebSphere MQ Server.
Use the following links to download the desired WebSphere MQ client:
|MQ Client version||Link|
Note: An individual IBM ID is required for the downloads.
Configure the agent settings
From the main menu, select Tools > Options. On the Agents Page, select WebSphere MQ. For user interface details, see the WebSphere MQ Agent Settings.
Optional: Perform additional global configuration
You can configure additional settings using the Service Virtualization configuration files.
Open the appropriate file:
Standalone Server configuration file:
Designer configuration file:
You can define the following element in the appSettings section of the configuration files. This configuration element sets up global behavior for processing WebSphere MQ messages.
<add key="MQAgent.DefaultCharacterSet" value="0"/>
Configures the default character set for simulated XML responses. Use this configuration if the character set is not recorded as message metadata. If the value is set to 0 the character set is not set.
The WebSphere MQ Agent instance can only use queues from a single Queue manager.
The WebSphere MQ Agent instance can only use a single TCP channel to connect to the Queue manager.
CCSID configuration in the WebSphere MQ Agent instance requires an application restart.
CCSID configuration is global for whole the application. There cannot be two agents with different CCSIDs.