We now need to add a new test call into SoapUI. Before we can do this we need to get the URL that will trigger the service. To get this information we should click on the integration's information icon and then click on the metadata URL included in the information. This will launch a new browser window with the metadata information; depending on how you have your browser set up, you may have to provide your normal ICS credentials as part of the process. The metadata screen will look something like the following:

This can be done by selecting a project to hold the test call in, and then right-click on the project in the left-hand tree. In the presented menu of options, click on the New RESTService from URL option. This will pop up a new dialog where we can provide the REST service's URL (this can be derived from the browser's URL by swapping the reference to metadata to the resource name), for example: https://XXXX.oraclecloud.com/integration/flowapi/rest/FILTEREDST_REST_CH7/v01/FlightStatusUpdate/ where XXX represents the domain name and data center of the ICS instance being used. With the URL provided, clicking on the OK button will result in a partially complete test request being displayed.

The request will need to be configured with the security credentials for the service call. The method needs to be set to POST, and we also need a test JSON payload to use. For a test payload we can copy in the sample JSON used while defining the endpoint (that is, the ICSBook-Ch7-FlightProgress-Source-request.json file in the chapter's resources). With that applied, the test call to the integration can be made. With the initial data value type being POS, and ICAORef being BA we get a successful result, as you can see here:

However, if you call the integration with a type changed to DPA, for example, or swap the ICAORef to something that is not BA or KL, then you will receive an error back as the filter has blocked the call.