Summary
The focus of this chapter was to cover in detail two different methods of modernizing your SOAP-based legacy assets. Method one was about exposing these assets via a SOAP proxy. Method two was about exposing them as a REST proxy. The techniques discussed in this chapter helped you quickly expand your company's API repository while making it easier for your existing customers to make use of your SOAP-based business functionality.
There are other legacy assets or non-SOAP assets that can be modernized too. These non-SOAP assets could be your messaging infrastructure (MQ) or your databases. You can use advanced APIC policies such as the GatewayScript policy to make connections to your backend servers.
Though it is now easier, with all the tools and flexibility at our disposable, to create APIs, the question that you should answer before embarking on your API'fication is if the functionality that you intend to make available as an API is even qualified to be one...
