WebSphere MQ Agent Settings
This dialog box enables you to configure the Service Virtualization WebSphere MQ Agent. The agent handles communication between a client and a real or virtual service.
|See also||Service Virtualization Agents|
User interface elements are described below (unlabeled elements are shown in angle brackets):
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.
|Delete||Deletes the selected configuration.|
Creates an additional configuration of the agent by copying the selected configuration. You can then modify the configuration settings.
Note: By default, the configuration is created with a sequential unoccupied port number.
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.
|Export All||Exports all agent configurations on the selected server. 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.
|Agent State||The current status of the agent. Values include Running, Not Running.|
|Test Configuration link||Tests the configuration based on the settings you select. If Service Virtualization identifies any problems in your configuration, the details are displayed.|
|Is Enabled||Turns the agent on and off. To enable the agent, the prerequisites must first be met.|
|Name||Enter a name for the configuration or accept the default name.|
|Queue Manager Name||
The name of the queue manager for the agent to connect to.
Note: The WebSphere MQ Agent instance can only use queues from a single Queue manager.
If the Service Virtualization Designer or Server running the SV WebSphere MQ Agent is installed 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.
If you select this option, you do not need to configure the Host, Port, Channel Name or SSL properties.
The name of the TCP channel for the agent to use to connect to the Queue Manager.
Note: The WebSphere MQ Agent instance can only use a single TCP channel to connect to the Queue Manager.
|Host||The name of the server hosting the queue manager.|
|Port||The TCP port where the channel listens for client connections.|
The character set used by the host.
The username and password for connecting to the queue manager.
Note: When you create a new virtual service, you can search WebSphere MQ queues and select a destination, provided the virtual agent has sufficient permissions.
To browse MQ destinations, the specified user must be able to perform the following in the WebSphere MQ client:
To create or delete a virtual destination, the specified user requires additional permissions, such as administrator permissions.
For details, see Browse Destinations Dialog Box.
The algorithm used for secure SSL communication.
Enter a value or select a value from the list. The CipherSpec value must be the same as the value specified in the WebSphere MQ channel configuration.
The path of the WebSphere MQ SSL key repository, which contains the WebSphere MQ Queue Manager certificate. If you are using mutual authentication, it also contains the certificate and private key of the Service Virtualization MQ agent.
Enter the path to the WebSphere MQ key database file (.kdb), but without the file extension. This file is similar to the file specified in the key repository parameter in WebSphere MQ Queue Manager configuration.
|Max. Connections||The maximum number of cached connections to Queue Manager allowed for sending messages. More connections enable more messages to be sent concurrently.|
|Message Context Mode||
Options for accessing the MQ queue.
|Strip XML Declarations||Removes XML declarations (<?xml ...>) from text messages before processing in Service Virtualization. Text messages are in Unicode.|
|Use UTF Methods||
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.
|Response Queue Access Mode||
Defines how Service Virtualization opens the response queue.
|Listening Timeout (ms)||
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.
|Maximum Responses per Request||Defines the number of response messages that are expected for each request message. Relevant when the Service Virtualization agent is configured to use Shared Response Queue Access Mode only. When the maximum responses per request are reached, Service Virtualization stops the listening process.|
|Request-Response Matching Mode||
Defines the method used to match a response to the correct request.