Skip to Content

SOAP(async) - SOAP (sync) - FIle(async)without BPM / sync SOAP resp fed to file with async SOAP req

Jun 11, 2017 at 04:30 PM


avatar image
Former Member

Hi gurus

I have scenario where a SOAP1 (async) data is coming to PI that includes data and attachment as well.

then only the SOAP1 data and not attachment is fed to the SOAP2 (sync) system and it returns a unique response code.

this response code from SOAP2(sync) along with the async SOAP1 attachment from the initial request is to be mapped to an async File that stores it into another system.

is this possible without BPM.


10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

1 Answer

Best Answer
Evgeniy Kolmakov Jun 11, 2017 at 04:35 PM

Hi Neha!

If I understand your requirement right it's just a simple async scenario with SOAP lookup in message mapping. In order to use attachments at receiver's side you should use SFTP adapter.

Regards, Evgeniy.

Show 5 Share
10 |10000 characters needed characters left characters exceeded
Former Member

ok Evgeniy but the question is SOAP sender is aync and SOAP receiver is sync

SOAP(sender async)- SOAP (receiver sync returning unique ID as response) here receiver SOAP will expect that its response is consumed by SOAP sender but it wont

how will this workout

do u hve any good link for SOAP lookup related to my scenario



This is how your Scenario will work:

SOAP(Aysnc)-------Request----->PIMapping(Use SOAP Lookup and get ID back)----ID & Attachment--->File Server

For implementing soap lookup:




Hi Manoj!

Thanks for clarification!

Regards, Evgeniy.

Former Member
Manoj K

hi manoj

thanks for your input.

my question is if I go with this approach how will I monitor this soap lookup in PI.

it will be like a black box right as there is not much tracing and logging we can do for UDFs




You can use the lookup channel which you call in UDF , but as it is sync you need to enabled logging to check the request and response payload in channel monitoring.