## 4 StoRfm v2
### Example
#### 4.5.3 Ontology Example
Thus, the strong positive correlation between the amount of parsing to be performed by the adapter and the response times is once again confirmed. In fact, with the extra level of nesting, the correlation is slightly stronger. Figure 14: Performance–increased nesting, static file sizes, via adapter. Figure 13: Performance–increased nesting, static file sizes, via adapter. Listing 9 below shows the XPath expressions evaluated by the adapter in the generation of the results for Figure 14. They are listed in order, from 1 to 10, delimited by \"/\". The extra level is encapsulated by the element _inputData_. **Listing 9. ** XPath expressions evaluated. ## 6 Evaluation

Our hypothesis was that SWS technologies could be leveraged to automate the previously manual configuration element of StoRIm v1. In addition, Internet based latency tests of the protocol adapter element were required. ### Configuration Wizard

The wizard prompts the user for the names of the SAWSDL, MicroWSMO and ontology files. The user selects OK. The SOAP operations and associated input parameters' model references will be parsed from the SAWSDL file. The equivalent concepts will be located in the MicroWSMO and ontology files using the model references. Data from all three input files is then used to populate the CSV file. ### Protocol Adapter

There is a 4-8% penalty for inserting the adapter into an infrastructure. Statistically speaking, the average time taken to route these SOAP requests via the adapter to their RESTful Web Service equivalents is significantly longer than the average time taken to issue these requests directly to the SOAP Server. Performance measurements demonstrated that increasing the size of the request files while maintaining a constant parsing requirement does not impact negatively. Conversely, increasing the parsing requirement across static file sizes, does impact performance. ## 7 Conclusions and Future Work

We have implemented, tested and demonstrated an automated configuration wizard. The configuration wizard is automated in line with SWS technologies best practice. The protocol adapter has been tested in an Internet based setting. There is a 4-8% time penalty involved in using the adapter which is statistically significant. This time penalty is dependent on the amount of parsing the adapter must perform. The following areas outline where we wish to focus next:

* One of the constraints imposed by the architecture is that, in situations where the target HTTP verb to be used is PUT or POST, the entity body of the request is sent on untouched. Typically, the outer element of the SOAP Body element contains the operation to be executed e.g., the WSDL wrapped document-literal pattern enforces this. However, this \"operation\" element is not needed by RESTful HTTP implementations as the \"operation\" is identified by the URI coupled with the verb. In order to address this, research is required on XSLT transformations to cater for scenarios as described above, where the XML content to be passed on differs from the XML content received. * This paper is not centered on performance and consequently the performance tests carried out are indicative rather than extensive. The latency performance of the adapter could be extended. This would include: the performance impact of message reliability and the effect of multiple similar requests with efficiencies such as caching and Conditional GET in place. * The architecture enables SOAP clients to access pre-existing RESTful HTTP Web Services. The adapter is a client-side migration enabler. Research could be conducted to extend the framework to focus on the server _i.e._, provide a server-side migration enabler from SOAP WS to RESTful WS. Should an enterprise wish to migrate from SOAP WS to RESTful WS, this new extension would be executed first to migrate the server. With the server migrated, the current framework would then be used to enable the enterprise to gradually migrate the clients. ## References

* [1] Resource Description Framework specification.