Synchronous performance issues

[Former Member]

Hi all,

We've a scenario that can developed using PI 7.1, but the 90% of interfaces will be synchronous (ATM, Internet Banking accessing SAP Banking functions).

Does anybody have some references, cases to similar scenarios?

I'm thinking about to developer SOAP -> RFC or HTTP -> RFC. The interfaces must be called by Java Clients, somebody have another issue about this scenarios. Any tip about how to get more performance, let me know.

Best regards

[VijayKonam · Accepted solution]

As long as ECC is responding in little time.. sync scenarios are good to go with..!! Purely depends on the complexity on the ABAP side..!!

VJ

[sunil_singh13]

Hi Isaias,

Well I would say you develop your Graphical User Interface(GUI) using Web Dynpro and call the RFC directly from it(It is possible) In other words I am advicing you not to use PI 7.1 if you are concern about the performance issue.

However if you still want to use PI 7.1 then you can use Message Packaging to improve the performance.

You use SOAP coz as you have to build Banking scenario that require extensive error handling that can be easly achived by using SOAP.

With HTTP performance will be good but you won't get good error handling.

You Develop Proxy in R/3 instead of going for RFC.

Thanks

Sunil Singh

[Former Member]

Hi,

I will need to make call from Web Dynpro, Generic Web Applications, Swing Applications. I've thought about to use simple calls to RFC. Using direct call to RFC i think that i will have more performance but i will need to develop a layer to provide monitoring, logging for message exchange, and so.

I think that i could do a Proof of Concept using two possibilities.

Best regards and thanks for all responses

[Former Member]

Hi,

As far as error handling is concerned, you may have fault message mapping in either case HTTP/SOAP.

As Receiver will be RFC or proxy, you can map application error.

In case of system error, you will get soap fault or http error. In any case you need to handle the error in sender application.

You will get http error using getErrorStream() method of class HttpURLConnection class.

Thanks,

Beena.

[prateek]

At sender, you may use http adapter to send data to Integration Engine directly (reducing the time taken by usual soap call to adapter engine) Or you may use Soap call directly to Integration Engine.

At receiver, Abap proxy would provide adapterless communication. So it could be better as compared to an RFC call.

Performance would largely depend upon the size of messages transferred and time taken at the receiver to process and send the response back to sender.

Regards,

Prateek

[agasthuri_doss]

Hi,

>I'm thinking about to developer SOAP -> RFC

If Standard RFC available & less load you can try this.

Cheers

Agasthuri Doss

[SudhirT]

While developing BAPI's, make them as efficient possible. also consider the load on R3 system on peak load times. you may have to set up sync time outs in VA of XI according to the performance of BAPI response.

thanks.

[Former Member]

For every Synch interface...all systems/services should be active/up. i.e. sender, xi/pi as well as receiver.

Also as far as time/performance is concern, then it matter lots on XI performance and receiver request/response processing time. It will be good if you will go with soap-proxy. HTTP does not support Fault message (but SOAP does), so it can be a drawback for interfaces.

Thanks

Farooq