In this blog, I just want to share how dynamic configuration can be used in synchronous scenarios. This might be useful especially in BPM scenarios where we might need to send synchronous system response along with the some or whole request fields to some other business system. So we can avoid extra transformation step. This will improve the overall performance.
As usual for BPM sender we need one Synchronous abstract interface and for the Synchronous business system we require synchronous inbound interface.
Synchronous Abstract Interface:
O/P Message: RequestMessage_BPM_MT
I/P Message: CustomResponseMessageAlongwithReqFields_MT
Synchronous Inbound Interface:
I/P Message: RequestMessage_MT
O/P Message: ResponseMessage_MT
So in the request message mapping (outside BPM), use the following generic Dynamic configuration UDF code to preserve the required fields along with the count. The count will be very useful while retrieving the field values from Dynamic Configuration header in the response message mapping. So, here I am providing the very basic code stuff for both storing and retrieving field values. You can extend this logic according to your requirements.
UDFToStoreValuesAsDC (Should be used in synchronous request message mapping)
UDFToGetValuesFromDC (Should be used in synchronous response message mapping)
MONI Screen shot for Dynamic Configuration Header