To Be Spoilt For Choice – Connecting EP to R/3
To be spoilt by choice. Connect your SAP ecosystem to Enterprise Portal.
Did you ever think about, how to connect best to your SAP ecosystem? Well, there is no “all-in-one” solution.
Consider the following different possibilities and make your decision according to your business case.
1. Webservices on the server systems. Connecting Enterprise Portal via webservice client. Available for EP 6.0 and R/3 Kernel 6.20 and higher.
Attention: Until EP6.0 SP2 patch 4 or EP6.0 SP5 there is only limited support for ABAP document literal webservices
Advantages: Truly platform independent and web enabled. Full control over the response content.
Disadvantages: No integrated transaction support, complex API on server and client side and protocol overhead. Approximately double run-time for the call, but the call duration is normally just about 5-10% of the overall cycle time.
2. JCO, native: Write a Java portal component and call a BAPI via JCO.
Disadvantages: Connection Management has to programmed by your own. Quite difficult for high load.
3. SAP Connector Framework based on Java Connectivity Architecture (JCA). From EP6.0 and WebAS 6.40 up.
Advantages: SAP CF handles the connection management and pooling.
Disadvantages: Still RFC with its limitations.
4. Integrate Business Server Pages as external iview into the portal.
Advantages: For those who already use an SAP kernel 4.6D or higher, SAP ABAP offers a http server and client and its Business Server Pages as well. If you are familiar with ABAP OO and JSP – you know BSP!. Its a good choice, however for tight integration into the Enterprise Portal it has some limitations if you render your pages in the server.
Disadvantages: No tight integration into the portal. Cross site scripting is not possible. Interact with BSP via parameters (styles and so on).
5. Integrate an ITS-WebGUI, ITS IACs into the portal.
Adv./Disadvantages: Not very fast, but try to find a semantic input check on any other web page instead 😉
6. Integrate the SAP WinGui directly into the portal (needs local installation of Wingui).
Adv./Disadvantages: Who says the SAP WinGui is not webish? I say the Web is not WinGuish ! ;-).
7. Integrate the IE-Plugin ActiveX WinGui into the Portal (needs local installation of Wingui). Only for those who love their SAP WinGui at any place :).
8. Use Citrix or Terminal Server for WinGUI and integrate it in your page.
Adv./Disadvantages: For all of you, who never understood this whole internet hype at all. Zero client administration.