REST proxy deployment scenario

You can use a DataPower® Gateway as a proxy to provide centralized monitoring and traffic management.

When used as a proxy, the DataPower Gateway intercepts all requests that a client sends to the application server. The DataPower Gateway forwards the request directly to the application server or sends the request to another server for auditing or accounting purposes. Typically, there is minimal message transformation.
Figure 1. DataPower Gateway as a proxy
Shows a client that sends a request to the application server. The request is intercepted by the DataPower Gateway, which sends the request to another server and then forwards the request to the application server.

Message flow

The figure shows a typical proxy implementation.

  1. The client sends a Request A (1) to the DataPower Gateway.
  2. The DataPower Gateway receives Request A (1) and sends a Request B (2) to a RESTful accounting web service.
  3. The Accounting Services receive Request B (2) and sends a Response B (3) back to the DataPower Gateway.
  4. The DataPower Gateway forwards the Request A (4) to the application server.
  5. The application server receives the Request A (4) and sends a Response A (5) to DataPower Gateway.
  6. The DataPower Gateway forwards Response A (6) to the client.

Implementation details

There are many ways to implement a proxy with a RESTful service for your DataPower Gateway. One way to implement a proxy is as follows.
  1. Configure your service.
  2. Configure a processing policy with a fetch or results action.
  3. Change the HTTP method to support your Accounting Service.
  4. Add a remote web service IP address and port.