Before we start building the services, let's take a look at the WSDLs for the inbound and outbound calls for our first inbound and outbound definitions. Let's start with the inbound or source definition, as shown in the following illustration:

The service payload is defined by a schema within the file and is structured as follows:

The inbound WSDL is available in the downloads as ICSBook-Ch3-FlightProgress-Source.WSDL.

As you can see, the idea of the message is to describe the status of a flight, including its destination and where it is. The first thing of note is that ICS has to offer the implementation URL of the service to be called, so the SOAP:Address location attribute is missing.

However, if you look at the destination WSDL, it has to contain the concrete target address (shown as http://XXXX.mockable.io/FlightServices) so that ICS knows where to call out to. When we set up Mockable, we will need to change this address to our unique account identified mock of the target...