Configure your test environment in the Configuration tab in the Test Client.
Purpose
You can use the Test Client
Configuration tab to alter the settings that are used when you test your message flow.
You
can set the following settings in the
Configuration
tab:
- Message Flows
- Deployment
- MQ Settings
- JMS Settings
- MQ Message Headers
- JMS Message Headers
MQ settings apply to invoke, adding to queue,
and removing from queue events; all other settings apply to invoke
events only.
Select the relevant options in the left pane to
display the properties in the right pane of the Configuration tab.
The following sections describe the properties on the Configuration tab.
Message Flows
- Add or remove Message Flows to be tested
- In this section of the Configuration tab,
the message flow that you have selected to test is listed. You can
add more message flows to the test configuration so that you can test
multiple message flows at the same time; for example, if you have
an output message from one message flow that triggers another message
flow, or if you are using subflows. Click Add to
add message flows to your test configuration. Click Remove to
remove message flows from the configuration.
Deployment
- I will deploy the specified BAR manually
- You can select this option to prevent the Test Client from deploying the message flow before you send a message to test the message flow. Specify the BAR (.bar) file that you want to deploy manually in the Specify BAR file property on the Deployment section of the Configuration tab. Deploy the BAR file to the integration server that is specified in the Deployment Location section.
- Always rebuild and deploy a BAR automatically
- The Test Client always builds and deploys the file irrespective of whether there is a change to the BAR file or its dependents, including message flows.
- You can use this option to force the Test Client to deploy when the Test Client cannot detect changes in the message flow.
- Only rebuild and deploy BAR when changes occur
- The Test Client rebuilds and deploys the BAR file only when there is a change in the content of the message flow. This action is the default option.
- Override configurable properties when rebuilding BAR file
- You can define the configurable properties in the BAR editor. Use this option to specify whether the user-defined value is overridden when the Test Client rebuilds the BAR file.
Click Change to select a
deployment location, see the Deployment Location wizard.
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 WebSphere® MQ Output queue contains a message.
Add one or more conditions. This option is ignored if no MQ queues are being monitored.
The Test Client monitors MQ queues that are defined in the MQOutput nodes in the message flows that are being tested. If you check the option, it instructs the Test Client to stop testing when the message reaches any of the WebSphere MQ queues that are being monitored.
- Select Purge or Browse option
- Use this option to either purge a message from the queue or to
browse the messages on the output queue.
- Queue manager connection parameters
- Enter the character set ID to use for connection to your queue
manager.
JMS Settings
- Stop when first JMS message is received
- Use this option to stop the Test Client receiving events when the first JMS Output destination contains a message.
- Specify JMS Client JARs
- Use this option to add and remove JAR files that are used to create JMS connections.
Select Use preference settings to configure preference settings. This option is a global setting that can be applied to all Test
Clients in the same workbench.
WMQ Message Headers
- WMQ Message Headers
- Use this option to build multiple MQMD header definitions. When you send a message to a message flow that contains an MQInput node, you have the option to select an MQMD with suitable values for your test. Click Add to enter additional MQMD headers. Each new header is listed under 'MQ Message Headers' in the left navigator column. Each MQMD definition name must be unique within the Test Client configuration file.
- MQ Message Header "Default Header"
- This options specifies the default MQ Message Header definition. You can edit the values in this definition for your test configuration, or create a new WebSphere MQ Message Header definition.
If you select MQ
Message Headers or JMS Message Headers,
a Duplicate context menu is displayed. This
context menu gives you the option to create a new message header based
upon one that already exists.
If you
select Include RFH V2 header in the right hand
pane you can specify values in a different folder that are applicable
to the MQRFH2 header.
If you select Include
MCD folder, the MCD folder properties are included in
the MQRFH2 header.
If you select Include
JMS folder, the JMS folder properties are included in
the MQRFH2 header.
If you select Include
USR folder, any additional properties you add are included
in the MQRFH2 header.
Note that if
you have selected Include JMS folder, the MCD
folder is included automatically. Furthermore, changing the Message
type results in a change to the Message domain in
the MCD folder.
When a message containing the MQRFH2 header is received, the header is parsed and the results appear in the Detailed Properties pane of the Test Client. To display all the properties of the MQRFH2 header, expand the Header tab.
For further information on how the MQRFH2
values work, see MQRFH2 header
JMS Message Headers
- JMS Message Headers
- Use this option to enter multiple JMS Message Headers. Click Add to
enter additional headers. Each new header is listed under 'JMS Headers'
in the left navigator column.
Select each JMS Message Header to
view and change the settings.
- JMS Header
- Enter the values for your JMS configuration in the JMS
Header page.