You can create a new server to test your
message flows using the Test Client.
Before you start you must complete:
- Creating a Configuration Manager on Windows
- Create and start a listener for the Configuration Manager
To create a new server for message flow testing:
- Select the New Server button on the Deployment
Location dialog panel.
- The first page, Define a New Server, of
the Test Client server wizard is displayed.
- Either select Choose an existing server and
pick an existing server from those displayed or select Manually
define a server.
- When the Manually define a server option
is selected, enter either the Host name or the IP
address of the machine on which the Configuration Manager is
running (the default is localhost).
- Select how you wish to view the servers:
- Name - name of server.
- Host name - the name of the server host.
- Vendor - Other host owner: the producer
of the server
- Version - the version of the server.
- Select Set server as project default (do not prompt) only if the
selected server is to be used as the default server so that you are not prompted
by the Test Client server wizard in the future.
- The second page, Broker Unit Test Execution Group, of the Test
Client server wizard is displayed.
- Select Use an existing Configuration Manger connection
file, and choose one from the those listed if you want to use
an existing Configuration Manger.
- Select Enter the Configuration Manager connection parameters to
link to a new Configuration Manager.
- Host - The host name or IP address of the
machine on which the Configuration Manager is running (the
default is localhost). This property is mandatory.
- Queue Manager - The name of the WebSphere
MQ queue manager that the Configuration Manager is using.
This property is mandatory.
- Listener port - The TCP port on which the
WebSphere MQ queue manager is listening (the default is 1414). This property
must be a valid positive number.
- HTTP Listener port - The HTTP listener port
where the Webservice message is being sent.
- Security Exit panel
- Class - Optional: The name of the Security
Exit required to connect to the WebSphere MQ queue manager. This property
must be a valid Java class name, but you can leave this box blank if it does
not apply to your connection.
- JAR file location - Optional: The location
of the JAR file for the Security Exit required to connect to the WebSphere
MQ queue manager. Use the Browse button to find the file location. You can
leave this box blank if it does not apply to your domain connection. Note:
The location of the JAR file is required if a Security Exit class is entered.
- SSL Parameters panel
- Cipher suite - Optional: The cipher suite,
distinguished names, CRL name list, key store, and trust store parameters
required when enabling SSL (see Implementing SSL authentication for more information).
The cipher suite field displays available cipher suites. Click More to
configure a custom cipher suite in the Broker Administration preferences window.
If a cipher suite is not specified, all other fields in the SSL section are
unavailable.
- CRL name list - a list of the serial
numbers of certificates that have been revoked and are no longer valid. They
should not be relied upon by any system user.
- Key store - The fully qualified name
of the keystore file. This file is typically called .keystore and
is located in the WebSphere Message Broker home directory.
- Trust store - A keystore that is used
when making decision on what is to be trusted. If you receive data from an
entity that you already trust, and you can verify that that entity is the
one it claims, then one can trust that the data did in fact come from that
entity.
- If the connect fails, a message is displayed in the next page of
the Message flow test server wizard.
- If the connection is successful, the final page of the Message
flow test server wizard is displayed listing the available brokers and execution
groups on the selected broker. If no broker is available, then click New to
create a new connection to a broker using the New Broker wizard.