Running the SOAP Nodes sample

Running the SOAP Nodes sample consists of putting a message through the consumer message flow. To run this sample you can use the Test Client to put input messages to the message flow.

Before you run the sample, verify that your Web services consumer is configured correctly for HTTP flows and that JNDI administered objects are configured for JMS flows, see Setting up the JMS part of SOAP Nodes sample.

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

Verifying that the consumer has the correct properties for the provider

SOAP over HTTP:
If you want to verify that your Web services consumer is configured correctly, complete all of the following steps. If you have set up a TCP/IP Monitor, you have already checked which port the Web services provider is using, but you must still configure the consumer to send the messages to your TCP/IP Monitor and then build and redeploy the broker archive (BAR) file.

The default port that Web services use is 7800, and the SOAPRequest node is set up to use this port. However, if this port is already in use, the port number is incremented by one.

To check which port your provider execution group is using, issue the following mqsireportproperties command:
```
mqsireportproperties IB9NODE -e sampleExecutionGroup -o HTTPConnector -n port
```
Where sampleExecutionGroup is the execution group for your sample.

To verify that the port that the SOAPRequest node is using is the correct port to call the provider flow, change the port of the SOAPRequest node to the port that the provider execution group is using by completing the following steps:
1. Open the message flow located in the integration project.
2. Open the HTTP Transport tab in the Properties view. If the port is already correct, you have finished setting up the sample. If the port is not correct, change the port in the Web service URL property to the correct port for your Web services provider or for your TCP/IP Monitor.
3. Save the message flow. You must now rebuild and redeploy the BAR file.
SOAP over JMS:
Ensure that JNDI Administered objects are created as described in Setting up the SOAP Nodes sample to use JMS transport. Also ensure that JNDI properties are set on the SOAPInput and SOAPRequest nodes. Verify that the following WebSphere MQ queues are created either through the WebSphere MQ Explorer or the WebSphere MQ command console.
- JMSREQUESTQ
- JMSREPLYQ
The sample has the SOAPInput node Enable support for ?wsdl check box selected; by default, it is not selected. No WSDL information is returned if the check box is cleared. This check box is on the HTTP Transport tab.
To verify that the flow is configured by using the expected WSDL, send an HTTP GET request to the endpoint exposed by the flow, suffixed with ?wsdl. For example, you can enter a URL of the following form in the address bar of a browser:
```
http://brokerHost:brokerPort/pathSuffixFromNode?wsdl
```
The WSDL returned includes import or include elements of the form:
```
<xsd:import namespace="..."</xsd:import>
```
```
schemaLocation="http://brokerHost:brokerPort/pathSuffixFromNode?xsd=xsd0" />
```
These references can in turn be entered into the address bar of the browser to retrieve subsequent parts of the definition. Some vendors provide tools that automatically follow such a chain of references to build up the complete WSDL definition.

Running the sample

In the Application Development view, expand the SOAPNodesSampleFlows project.
Under Flow Tests, double-click SOAPNodesSampleConsumerFlow.mbtest to open the file in the Test Client.
Click Send Message.

Select Dequeue in the Message Flow Test Events pane, then click Get Message.

If the sample ran successfully, the following message is retrieved from the SOAPSAMPLE_OUT queue:

	<NS1:submitPOResponse xmlns:NS1="http://www.acmeOrders.com/OrderService">
	<orderStatus>AVAILABLE</orderStatus>
	<orderAmt>50</orderAmt>
	<partNo>Some Part</partNo>
	<partQuantity>1</partQuantity>
	</NS1:submitPOResponse>

Back to sample home