1. From the main menu, select Tools > Options.
2. Click Agents.
3. Under WebSphere MQ, select a configuration.

• For additional important configuration information, see the task Configure the WebSphere MQ agent.

• The WebSphere MQ Agent instance represents a connection to a single WebSphere MQ queue manager. A virtual service can use multiple agent instances if it needs to access queues on multiple queue managers.

• The WebSphere MQ Agent is able to automatically reconnect when a connection to the WebSphere MQ Server is lost.

• You can define multiple configurations for each agent.

Configure agents

Displays the server configured for your project.

Expand the server to display the available agents and configurations.

Enables you to define additional configurations of the agent.

Creates an additional configuration of the agent by copying the selected configuration. You can then modify the configuration settings.

Saves the selected agent configuration as a file. The file is saved in the .agce file format, and can be imported to any Service Virtualization Server.

Enables you to select an exported agent configuration file stored on the file system. The file is saved in the .agce file format, and can be imported to any Service Virtualization Server.

If the configuration file you are importing contains multiple configurations, you can select which configurations you want to import.

If you choose to import an agent configuration that is identical to a configuration that already exists on your server, you can choose to overwrite your existing configuration, or create a new, additional configuration.

If the Service Virtualization Designer or Server is running on the same machine as the WebSphere MQ server, you can use a direct local connection to the MQ queue manager. Using the local connection may have a positive impact on performance and simplifies agent configuration.

Local Connection allows direct connection to the queue manager specified by the Queue Manager Name property

If you select this option, you do not need to configure the Host, Port, Channel Name, or SSL properties.

The name of the queue manager for the agent to connect to. This option is necessary only if Local Connection is used.

The name of the TCP channel for the agent to use to connect to the queue manager.

The name or IP address of the server hosting the queue manager.

The character set used by the host. It may be optional depending on the WebSphere MQ configuration.

The username and password for connecting to the queue manager.

These values may be optional depending on the MQ channel configuration. For details, see MQ authentication.

Path to a certificate file of the Root Certificate Authority which signed the SSL certificate bound to the MQ channel, or to a self-signed MQ channel certificate. Supported formats are Base64 PEM, and binary CRT (supported on Windows only).

This certificate is added to the 'Trusted Root Certificate Authorities' certificate store. If the Service Virtualization Designer and Server are run "as Administrator", it puts the certificate in the Local Machine store; if the Designer is run as a non-admin user, it puts the certificate into the Current User certificate store.

You can leave this property empty if the MQ channel certificate is already trusted by a machine running Service Virtualization.

Options for accessing the MQ queue. See the WebSphere MQ documentation for details.

• None.
• Set Identity. Corresponds to the MQC.MQOO_SET_IDENTITY_CONTEXT property.
• Set All. Corresponds to the MQC.MQOO_SET_ALL_CONTEXT property.

Service Virtualization considers MQ text messages as created by the WriteUTF() method instead of the WriteString() method.

When using an XML service, the message can be either transferred as a string (with a specified character set) or as binary data (UTF). By default, the agent reads and writes messages as a string. Select this option to use binary messages with UTF content instead.

Defines how Service Virtualization opens the response queue.

• Default. The Service Virtualization agent can access a shared queue, and selects messages in the queue according to FIFO methodology.

  Caution: Service Virtualization consumes messages regardless of the correlation mechanism (defined in the Request-Response Matching Mode field below). This can be problematic if the queue is shared. In this case, it is recommended to use the Shared mode.

• Exclusive. Opens the queue in the MQ Exclusive Queue Access mode. Access is limited to Service Virtualization only, enabling the fastest sequential picking from the queue.

• Shared. Opens the queue as an MQ shared queue and selects specific responses according to the IDs used for request-response matching mode (request message ID, request correlation ID, or both). Enables you to run several services with one response queue, or run a virtual service with systems where the response queue is shared with other applications.

  Note: This mode is slower than the other modes, as it is selecting specific responses from the queue and not simply the first response.

The length of time Service Virtualization listens for a response or multi-response. If the response does not arrive within the timeout period, Service Virtualization stops the listening process, even if there are multiple responses expected.

Defines the method used to match a response to the correct request.

• Request Message ID -> Response Correlation ID. The Message ID of the request is copied to the Correlation ID of the response. This is the default behavior of WebSphere MQ.

• Request Correlation ID -> Response Correlation ID. The Correlation ID of the request is copied to the Correlation ID of the response.