Running the WSRR Connectivity sample

Running the WSRR Connectivity sample consists of putting each of the messages through the message flow. You can run the sample to learn what happens in the following situations:

• The input SOAP message does not contain any information to over-ride the WSRR node properties.
• The input SOAP message contains runtime over-ride information to retrieve a new version of the WebService from the Service Registry.
• The WSRR node cannot find a matching entry in the Service Registry.

For more information, see About the WSRR Connectivity sample.

If you have not imported the required wsdl files into the Service Registry as described in the setup instructions, you cannot observe the effects of retrieving entries from the Service Registry. However, you can still explore the configuration of the node properties and see the "No match" situation described above.

If you have any problems when you run the sample, see Diagnosing problems.

Running the sample with a SOAP message that does not contain runtime over-ride information

To run the sample with the message that does not contain runtime over-ride information:

1. In the Message Brokers Toolkit, switch to the Broker Application Development perspective.
2. In the Broker Development view, expand the "WSRR Connectivity Message Flows > Flow Tests" folder and double-cick static_version.mbtest. The static_version.mbtest file opens in the Test Client.
3. In the Test Client, click Enqueue.
4. Click Send Message. The message that contains the information to retrieve the original WebService version is put on the WSRR_IN queue.
5. In the Test Client click Dequeue.
6. Click Get Message to get the input message from the WSRR_OUT queue. Version 1.0 of the Demo Customer WebService has been invoked and the response has been written to the output queue. Note the response: <updateCustomerReturn>Updated Customer via WebService version 1.0</updateCustomerReturn>

Running the sample with a SOAP message that contains the runtime over-ride information

To run the sample with the message that does contain runtime over-ride information:

1. In the Message Brokers Toolkit, switch to the Broker Application Development perspective.
2. In the Broker Development view, expand the "WSRR Connectivity Message Flows > Flow Tests" folder and double-cick override_version.mbtest. The override_version.mbtest file opens in the Test Client.
3. In the Test Client, click Enqueue.
4. Click Send Message. The message that contains the information to retrieve the newer WebService version is put on the WSRR_IN queue.
5. In the Test Client click Dequeue.
6. Click Get Message to get the input message from the WSRR_OUT queue. Version 2.0 of the Demo Customer WebService has been invoked and the response has been written to the output queue. Note the response: <updateCustomerReturn>Updated Customer via WebService version 2.0</updateCustomerReturn>

Running the sample with a message that will not match any entry in the Service Registry

To run the sample with the message that does contain runtime over-ride information:

1. In the Message Brokers Toolkit, switch to the Broker Application Development perspective.
2. In the Broker Development view, expand the "WSRR Connectivity Message Flows > Flow Tests" folder and double-cick no_match.mbtest. The no_match.mbtest file opens in the Test Client.
3. In the Test Client, click Enqueue.
4. Click Send Message. The message that contains the information that does not retrieve a matching wsdl document is put on the WSRR_IN queue.
5. In the Test Client click Dequeue.
6. Click Get Message to get the input message from the WSRR_OUT queue. No matching documents have been retrieved from the Service Registry and the message has been written to the output queue. Note the response: <ServiceRegistry>No matching services!</ServiceRegistry>

Back to sample home