...
- (Preferred) Create a certificate for the Virtualize server, sign it with a certificate authority that is trusted by the AUT, and issue it for the host where the Virtualize server is installed. With this option, you don’t need to make any changes to the AUT.
- Configure Virtualize Server with a generated (possibly self-signed) certificate and add it to the trust store of the AUT.
- Add your actual server certificate to Virtualize. This option assumes that access to the server certificate and keys is possible and that changes to the AUT are difficult or should be avoided. However, this option may not be possible if the certificate was signed for a hostname other than the hostname where Virtualize is deployed.
- Disable certificate trust in the AUT. The AUT would still connect over SSL but trust any server (such as the Virtualize server) without validating its certificate or its trust paths.
- Set up a frontend like a load balancer that provides SSL and forwards to the Virtualize server.
For the AUT to accept a certificate/private key pair, you generally need—at minimum—a self-signed certificate/private key pair whose common name (CN) parameter matches the fully-qualified name of the server. For example, if your Virtualize server URL is http://myserver.mycompany.com, the CN parameter should be "myserver.mycompany.com".
...
From this panel, you can review and modify settings related to monitoring, server statistics, global JMS and MQ connectionsIBM MQ connections, and user authentication (for remote servers only).
...
If the application under test sends and receives messages through an MQ IBM MQ Queue Manager or JMS provider, click the Connections tab to define connection settings. Assets and proxies deployed to the Virtualize server can be configured to use the connection settings to communicate with the application under test. You can perform the following actions:
- add a new connection (see Adding MQ IBM MQ Queue Manager Connections)
- remove a connection
- modify a connection
- copy the connection configuration from an existing connection to another server (see Copying an IBM MQ Manager Connection)
Adding
...
IBM MQ Queue Manager Connections
Click Add in the MQ Queue Managers section and specify the following configurations. Click Test Connections after configuration to verify proxies and virtual assets on the server will be able to communicate with the Queue Manager. The settings configured in this interface are also used in the virtual asset or proxy configuration panels.
...
- Default: allows you to manually enter connection details, such as host, port, and channel.
- CCDT: allows you to specify a client channel definition table (CCDT) file that provides connection details.
- Bindings: use Bindings mode when the queue manager and connected applications are running on the same system. The IBM WebSphere MQ Java API connects API connects directly to the queue manager using the Java Native Interface (JNI). To use the bindings transport, the IBM MQ classes for JMS must be run in an environment that has access to the IBM MQ Java Native Interface libraries.
Host (Default Mode)
Specify the MQ IBM MQ queue manager host.
Port (Default Mode)
Specify MQ Specify IBM MQ queue manager port.
Channel (Default Mode)
Specify MQ Specify IBM MQ queue manager channel.
CCDT File (CCDT Mode)
...
Specifies the CipherSuite to use for the SSL connection on the specified MQ IBM MQ Channel. Refer to the IBM MQ documentation to determine which CipherSuite to select based on the CipherSpec.
...
Specify the key store file, key store password, and key store type to be used by the queue manager to authenticate virtual assets and message proxies over SSL. If the IBM MQ Channel does not require SSL, then the key store settings are not required. After configuring the key store settings, click Validate to verify that the settings are configured correctly.
...
If using key/trust stores, you will need to download and install the Unlimited Strength Java Cryptography Extension. For details, see JCE Prerequisite.
Copying an
...
IBM MQ Manager Connection
You can copy existing IBM MQ manager connection settings between servers. You can copy settings from a remote server or the local server.
- Open the server settings that contains the connection configuration you want to copy. For example, if you want to copy the connection settings from a remote server to your local instance, open the remote server's configuration panel.
- Click the Connections tab and choose the connection configurations you want to copy. You can copy a single connection or multiple connections by CTRL-clicking or COMMAND-clicking.
- Click Copy and specify destination server for the connection settings from the menu.
- Click OK to copy the settings. Settings will not be copied if they already exist on the destination server.
Using IBM MQ Queue Manager Connection Settings
After you add a connection, you will be able to choose it from the configuration panel as you add and configure proxies and virtual assets hosted on Virtualize Server. For example, this shows how to select a global connection for a proxy using MQIBM MQ:
Adding JMS Connections
Click Add in the JMS Connection settings section and specify the JMS configurations. See JMS Provider Configuration for details on configuring JMS connection settings.
...