Hi All,

This is regarding acknowledgement in DataPower.

Request Flow: - External system --> Public Zone DataPower --> Access Zone DataPower --> IIB.

Response Acknowledgement Flow: - IIB --> Access Zone DataPower --> Public Zone DataPower --> External System.

Queries: -

1) In DataPower communication, once the Public Zone transmits data to the Access Zone, the transaction should be considered complete without requiring an acknowledgment from the Access Zone. Similarly, the Access Zone's transmissions to the IIB should not necessitate acknowledgment for transaction closure. --> Can we set any property/setting/code level in DataPower that transaction should close once data transmit further and don't wait for acknowledgement.

2) DataPower is sending acknowledgments that contain unnecessary information beyond the standard HTTPS 200 OK response. Since the external system only requires the 200-status code, these additional properties should be removed to optimize the communication. --> Can we set any property/setting/code level in DataPower.
Properties Like below: -
HTTPS: 200 Ok
content type
Connection
Body
etc....

Thank you.
VamshiSai Kalangi.

I used this many years ago for MPGW with SOAP request type, is still documented:
https://www.ibm.com/docs/en/datapower-gateway/10.5.x?topic=variables-varservicesoap-oneway-mep

I was able to see in packet capture that connection to client got closed before backend processing against intentionally slow backend was complete.

------------------------------
Hermann Stamm-Wilbrandt
Compiler Level 3 support, IBM DataPower Gateways
IBM
Boeblingen Germany
------------------------------

If I understand correctly, you're just wanting a fire & forget.  So, the external system hits the public zone DP which sends a request to the access zone DP, which sends a request to IIB.  You're also not wanting to wait for a response?   Correct?

This can vary dramatically based upon what service you are using and how you prefer to do things, such as configuration or code based processing. 

For an XML FW, you can just do a loopback proxy and, at some point in the processing policy, invoke the back end either with a results action (configuration based) or XSLT or GWC url open type call (code based).  In fact, you can execute the XSLT transform, GWS or Results action asynchronously, build the 200 response to the requestor (in the public zone) and return.

For MPGW or WSPs, you have the extra step of setting the skip-backside variable to 1, and then configure similar processing for fire and forget.

You'll do the same in the access zone, but at that point, it seems, it really doesn't matter what return code you use.  The same with IIB.  It won't matter how IIB responds.

I am curious, though, how the external system is to manage error handling/exceptions. 

Joseph,

the idea with asynchronous results action is not bad, but does not work.
FSH connection gets closed only when complete transaction is finished, including all asynchronous stuff.
So the HTTP response will be sent to client too late - the variable I pointed to is the only DP option for return response fast.

------------------------------
Hermann Stamm-Wilbrandt
Compiler Level 3 support, IBM DataPower Gateways
IBM
Boeblingen Germany
------------------------------