Start of change
WebSphere Message Brokers
File: af52181_
Writer: Kate Hostler

Reference topic

This build: July 31, 2007 21:29:34

Test Client configuration panel

Define the test message-flow environment configuration using the Test Client configuration panel.

Purpose

When Test Client is launched, a default test configuration is created and the selected message flow added to the configuration. The test configuration categorization settings are changed as required.

A test configuration is locked, having Read-Only status, once a test message flow configuration is started and used in testing. The test configuration is unlocked once the tests have been completed.

The configuration categories are:

When each category is selected the available functions and options are displayed in the right panel

Message Flows

Add/Remove Message Flows to be executed on the Test Client
The current test-message flow is listed. Click Add to select more message flows for testing from the displayed Resource panel.

Deployment

Never deploy, use Broker Archive specified below
The test message flow are not deployed by the Test Client. A Broker Achive file must be specified before launching a test.
Only rebuild and deploy broker archive when changes occur
The Test Client will only rebuild and deploy the Broker Archive file when ther is a change int he Broker Archive file or in or a dependent. This is the most commonly used option.
Always deploy
Test Client always builds and deploys teh file irrespective of whether there is a change ot teh Broker Archive file or its dependents inclulding message flows.
You can use this option to force the Test Client to test and deploy when for some reason the Test Client cannot detect changes in the BAR file.
Override configuration properties when rebuilding Broker Archive file
You can define the configurable properties in the Broker Archive editor. Use this to specify whether the user-defined value is overridden then the Test Client rebuilds the Broker Archive file.
Always use same deployment location
The Deployment Location dialog is shown every time a test message is sent if this option is not checked.

MQ Settings

Stop when first MQ message is received
Use this option if you want the test client to stop receiving events when the first MQ Output queue contains a message.
Use this option to control whether the test client should be left running to keep gathering events or to stop waiting for events after a message is received from the MQOutput queues when the message flow contains a mixture of HTTP and MQ nodes.
Select Purge or browse option
Use to either purge a message from the queue or to browse the messages on the output queue.

JMS Setting

Use JMS Settings to specify the JMS client JAR files

Stop when first JMS message is received
Use to stop the test client receiving events when the first JMS Output destination contains a message.
User Authentication
Use to define user authentication details to access the JAVA destination connection.
Specify JMS Client JARs
Use to add and remove JAR that are used to create JMS connections.
Select Use preference settings to configure preference settings.
MQ Message Headers
Use to enter multiple MQMD headers. Click Add button to enter additional headers. Each new header is listed under MQMD Headers in the left navigator column.
You are not allowed to enter duplicated header names.
MQ Message Header (Default Header)
Use this to define the details of the default MQ message header.
JMS Message Headers
Use to enter multiple JMS headers. Click Add button to enter additional headers. Each new header is listed under JMS Headers in the left navigator column.
select each JMS Mesage Header to see and change the settings.
Related concepts
Testing message flows using the Test Client
Related reference
Test Client Events page
Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2007Copyright IBM Corporation 1999, 2007. All Rights Reserved.
This build: July 31, 2007 21:29:34

af52181_ This topic's URL is:
End of change