Implementing PI webservice using JDBC Lookup

[Former Member]

Are there any performance implications to consider using SAP provided JDBC Lookup API Vs standard JDBC receiver adapter using SQL statements to fetch lookup data. The goal is to develop a web service to host a lookup service within ESR. The data that will be fetched in small in size.

Appreciate any feedback.

PM

[Former Member · Accepted solution]

Mokkarala,

If the size is small then there would be no issue. If your requirement can be done using standard adapter then would suggest using this, so that error handling and maintenance would be easy.

---Satish

[Former Member]

Hi Prasad,

Are there any performance implications to consider using SAP provided JDBC Lookup API Vs standard JDBC receiver adapter using SQL statements to fetch lookup data.

bold ---> Offcourse there will be Prasad....

If you are going to use JDBC receiver adapter the flow will be like this...

Sender ->Adapter Engine (for Sender Communication Channel) ->Integration Engine of XI->Call to Receiver JDBC adapter for look up purpose (In Adapter engine)->Again to Integration engine of XI>Adapter engine for Reciver Communication Channel->Receiver

Don't you think we can simply avoid the the back and forth communication between Adapter engine and Integration Engine for lookup purpose by using "SAP provided JDBC Lookup API"...?

I'll recommend you to go through this blog :

/people/william.li/blog/2007/03/30/using-jdbc-connection-pool-in-xi-message-mapping

bold

--->The goal is to develop a web service to host a lookup service within ESR. The data that will be fetched in small in size.

bold

Small in size is o.k but how frequently that also should be a touch point if considering performance parameter of interface?

bold

Regards,