Running the WebSphere Service Registry and Repository Connectivity sample

Running the WebSphere Service Registry and Repository Connectivity sample consists of putting each of the messages through the message flow. You can run the sample to find out what happens in the following situations:

The input SOAP message does not contain any information to override the WSRR node properties.
The input SOAP message contains runtime override information to retrieve a new version of the Web service from the Service Registry.
The WSRR node cannot find a matching entry in the Service Registry.

For more information, see About the WebSphere Service Registry and Repository Connectivity sample.

If you have not imported the required .wsdl files into the Service Registry, see Setting up the WebSphere Service Registry and Repository Connectivity sample, 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 previously.

If you have any problems when you run the sample, check the port that the SOAPInput node is listening on by using this command:

mqsireportproperties IB9NODE -e WSRRConnectivitySample 
-o HTTPConnector -n port

If the SOAPInput node is not listening on port 7800 you must change the port specified here in both of the WSDL documents and re-import them into the WebSphere Service Registry and Repository:

	<wsdl:service name="DemoCustomerService">
	<wsdl:port binding="impl:DemoCustomerSoapBinding" 
	name="DemoCustomer">
	<wsdlsoap:address location="http://localhost:
	7800/DemoCustomer_v20/services/DemoCustomer"/>
	</wsdl:port>
	</wsdl:service>

If you still encounter any problems when you run the sample, see Resolving problems when running samples in the IBM Integration Bus documentation.

Running the sample with a SOAP message that does not contain runtime override information

To run the sample with the message that does not contain runtime override information:

In the Application Development view, expand the WSRR Connectivity Message Flows > Flow Tests folder.
Double-click static_version.mbtest to open the file in the Test Client.
Click Enqueue.
Click Send Message. The message that contains the information to retrieve the original Web service version is put on the WSRR_IN queue.
In the Test Client, click Dequeue.
Click Get Message to get the input message from the WSRR_OUT queue. Version 1.0 of the Demo Customer Web service is called and the response is written to the output queue. The following response is received:
```
<updateCustomerReturn>Updated Customer via WebService version 1.0
		</updateCustomerReturn>
```

Running the sample with a SOAP message that contains the runtime override information

To run the sample with the message that contain runtime override information:

In the Application Development view, expand the WSRR Connectivity Message Flows > Flow Tests folder.
Double-click override_version.mbtest to open the file in the Test Client.
Click Enqueue.
Click Send Message. The message that contains the information to retrieve the newer Web service version is put on the WSRR_IN queue.
In the Test Client, click Dequeue.
Click Get Message to get the input message from the WSRR_OUT queue. Version 2.0 of the Demo Customer Web Service is invoked, and the response is written to the output queue. The following response is received:
```
<updateCustomerReturn>Updated Customer via WebService version 2.0 
	</updateCustomerReturn>
```

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

To run the sample with the message that does contain runtime override information:

In the Application Development view, expand the WSRR Connectivity Message Flows > Flow Tests folder.
Double-click no_match.mbtest to open the file in the Test Client.
Click Enqueue.
Click Send Message. The message that contains the information that does not retrieve a matching WSDL document is put on the WSRR_IN queue.
In the Test Client, click Dequeue.
Click Get Message to get the input message from the WSRR_OUT queue. No matching documents are retrieved from the Service Registry and the message is written to the output queue. The following response is received:
```
<ServiceRegistry>No matching services!</ServiceRegistry>
```

Back to sample home