What is the functionality of RFC, SAP Java and Business Connectors?

Here are the brief ideas about RFC, JCo(Java connector) and business connectors:

RFC-REMOTE FUNCTION CALL(RFC) - The RFC is used as interface for communication between SAP systems and between SAP systems and external systems. SAP offers several interfaces that are based on RFC, such as Application Link Enabling (ALE), Business Application Programming Interfaces (BAPIs), and RFC function modules.  Applications can use RFC to call SAP function modules located in other systems.

HOW IT WORKS?

SAP Systems (ABAP Interface) - An ABAP program can call a remote function with the statement CALL FUNCTION... DESTINATION. The DESTINATION parameter indicates the system where the function called is located. This function module must be an ABAP function module, and must be flagged as RFC-enabled in the Function Builder.

- Remote functions can be called either synchronously or asynchronously.
- Remote debugging is possible for connections where an SAP system is the target system.
- External Systems (RFC-API: Communication Interface for External Programs)

If one of the communication partners is not an ABAP program, it must be programmed as an RFC communication partner. The SAP system is delivered with the RFC-API (Application Programming Interface). You can use this library in external systems to develop external RFC-enabled programs that can communicate with SAP Systems.

SAP Java Connector - SAP Java Connector (SAP JCo) is a middleware component that enables the development of SAP-compatible components and applications in Java. SAP JCo supports communication with the SAP Server in both directions: inbound calls (Java calls ABAP) and outbound calls (ABAP calls Java).  SAP JCo can be implemented with Desktop applications and with Web server applications.

SAP JCo is used as an integrated component in the following applications:
- SAP Business Connector, for communication with external Java applications in the Application Server, for connecting the integrated J2EE server with the ABAP environment.
- SAP JCo can also be implemented as a standalone component, for example to establish communication with the SAP system for individual online (web) applications.

SAP BUSINESS CONNECTORS (SAP BC) - SAP Business Connector (SAP BC) is a middleware component. It allows integrating with R/3 via open and non proprietary technology. SAP BC uses the Internet as communication platform and XML/HTML as data format. Thus it seamlessly integrates different IT architectures with R/3. The SAP Business Connector is a main part of the SAP Internet Initiative.  SAP’s Business Connector (SAP BC) is a business integration tool to allow SAP Customers the ability to communicate with other SAP customers or SAP marketplaces. The Business Connector allows integration with R/3 via open and non-proprietary technology. This middleware component uses the Internet as communication platform and XML/HTML as data format thus seamlessly integrating different IT architectures with R/3.

Corporations of all types are searching for the most efficient mechanism for acquiring and selling goods and services at lowest total cost over the Internet. SAP’s response are Business Connectors which interlink the SAP systems with the Internet. The Business Process Connectors for SAP systems supports for the dynamic integration between the application processes and server systems thus facilitating in faster and efficient functioning of SAP R/3, SAP Portals and My SAP solutions.

In the current model, SAP Business Connector Framework uses XML schemas to dynamically generate a JSP that can be assessed from any web browser, so that one can test and deploy integration tools between the application server environment and SAP systems immediately. Convergence of XML schema approach to the SA Business Connector facilitate in adding flexibility to all the SAP standards. Thereby the customers can leverage the power and flexibility of XML into their business documents with an  enhanced efficiency and improved cost-effectiveness.

SAP BC integrates RFC server and the client and provides an XML layer over R/3 functionality. That is, it comes with an XML automation that converts SAP’s RFC format into XML and supports both synchronous RFC and asynchronous RFC protocols such that there is no requirement of SAP R/3 automation at the receiving end. Also, SAP BC has a built in integration support for SAP’s specification of IDOC-XML and RFC-XML standards. Hence, whenever dealing with the messages conforming to the same standards it supports the integration.

Tips by : Madhuuri

SAP Reference Books:
SAP Basis Components, Application Modules, Certification,  ABAP/4 Programming Books

Back to Basis Menu:
SAP BC (Basis Components) Hints and Tips

Return to :-
SAP ABAP/4 Programming, Basis Administration, Configuration Hints and Tips