Software AG Products 10.7 | Integrating On-Premises and Cloud Applications | Service Development | webMethods Query Language | Usage Notes on REST | Configuring a REST Resource Using the Legacy Approach | Setting Up a REST Application on Integration Server | Converting an Existing Application to a REST Application
 
Converting an Existing Application to a REST Application
When using the the legacy approach, consider one of the following approaches to transform the existing application to a REST application:
*Refactor your existing services into _get, _put, _post, _patch and _delete services.
*Use the invoke directive, as shown in the following example:
For existing applications that use the invoke directive, you can update a service to call the pub.flow:getTransportInfo service and then perform a branch on /transport/http/method to execute the appropriate portions of your existing code, as in the following example:
Note:
If you use the invoke directive, you cannot use the $resourceID and $path pipeline variables. In addition, you cannot use the _default service.