Third Party WebService call: SOAP Lookup vs SOAP Adapter Scenario.

[Former Member]

Hello Experts,

What are the pros and cons of using SOAP Look up in Message Mapping for webService call.

Previously my scenario was a standard SOAP Adapter Scenario. But it had BPM, so I have designed it via SOAP look up in Message Map to avoid BPM.

I want to know what are the merits and demerits (In terms of Performance - Payload size:Runtime, Maintanence, Configurability,etc) of using SOAP Look up instead of standard SOAP Scenario.

Regards,

Sudharshan N A

[Former Member · Accepted solution]

HI,

I am assuming that you migth have visted this link

SOAP Lookup - /people/bhavesh.kantilal/blog/2006/11/20/webservice-calls-from-a-user-defined-function

SOAP Look-ups are very much possible and performance wise also its preferrable as compare to BPM.

Its pretty much simple and easy way to handle it with UDFs.

The performance could also depend upon what kind of things you need to achive or replacing with BPM.

If you will be dealing with too many resources in BPM then that creates the performance overloaded issues.

UDFs also have the performance problems nased on the payload size but very minimal.

Thanks

swarup

[Former Member · Accepted solution]

If I understand currectly then Lookup is used to to make a call to external system and get some information. It means we have to send small message to the systems and get the response from there and Map it to the target Message.

No if in your case the message is of high volume, then it does not affect on performance...as compared to BPM. Using BPM is highly time consumable and has performance issue, so in comparision to this Lookup is much better option then using BPM.

Thanks

Farooq