SAP Business Connector

Purpose
The SAP Business Connector (SAP BC) enables the extension of business processes across the Internet, and the integration of non-SAP products using an open and nonproprietary technology. The SAP Business Connector covers bi-directional, synchronous, and asynchronous communication with an SAP Server.

Implementation Considerations
The SAP Business Connector is a standalone software component that is installed and administrated independently of the SAP system. You can find the installation files in the Internet at service.sap.com/sbc-download.

Integration
The SAP BC contains a fully functional RFC Server and Client. This enables bidirectional real-time communication (inbound and outbound) with an SAP system. From the perspective of the SAP application, communication with the SAP BC is the same as with any other RFC Server. The SAP RFC format is converted to XML or HTML, so that the system at the other end of the communication channel does not have to be an SAP system. The SAP BC supports synchronous (RFC) and asynchronous (tRFC) communication, and thus supports both BAPI and ALE scenarios. IDocs can be converted into hierarchical structures with access to each individual field. This enables the modification of IDoc content while it is being processed in the SAP BC. The SAP BC enables data exchange via HTTP without affecting the existing security infrastructure. It can also control communication between different SAP releases. Using the SAP Interface Repository (in the Internet at ifr.sap.com), the SAP BC can access the BAPI interfaces provided by SAP and the corresponding documentation.

Features
Synchronous and asynchronous communication with SAP systems using RFC and tRFC Bi-directional communication to and from SAP systems Services for processing IDocs and BAPIs

XML-enabling and Internet-enabling of SAP releases prior to SAP Web AS 6.10 Support of BizTalk XML envelopes for BAPI and RFC Support of integrated error handling of BAPIs and RFCs at XML level

SAP BC Architecture
The graphics below describe the processes and elements involved in communication between the SAP Server and the SAP Business Connector.
Architecture and Components

BAPI Call by the SAP Business Connector Server

Calling a SAP BC Service via the SAP Server

SAP BC Functions
This section contains a detailed description of the functions of the SAP Business Connector. You can use the SAP BC to:

Execute SAP BAPI methods according to the description in the Business Object Repository - BOR). BAPIs (Business Application Programming Interfaces) are interfaces that allow standardized access to SAP applications. Quickly and simply generate XML -based SAP BC services that execute a BAPI. Applications within your organization can then call the SAP BC services to execute a BAPI on the SAP Server. These interfaces can also be used to trigger both synchronous

and asynchronous processing. Asynchronous processing uses the ALE services in the SAP system.

Execute RFC s (Remote Function Calls) from the SAP BC. Using the SAP BC, you have access to all SAP functions that are available using RFC. External applications do not have to understand SAP data formats, ABAP structures, or the RFC protocol to communicate with an SAP system.

Call SAP BC services from a SAP Server. In this way, the SAP BC enables business-to-business integration between business partners by extending the range of their infrastructure.

Configure the routing of SAP business application documents (IDocs) . You can configure the routing (the control of communication) within the SAP BC according to your own criteria. There are several different transport methods for your application documents that are available out of the box (for example, ALE, XML, e-mail). You can use these to send an IDoc to another SAP system, to an electronic marketplace, or simply to an Internet address.

Use ALE services in the SAP system, for example, asynchronous processing, monitoring, or distribution services.

SAP BC Routing
Routing messages using the partner manager
When the SAP Business Connector Server receives a call on the RFC server (Listener) that is not linked to a particular SAP BC Service, the SAP Business Connector Server sends the call to the Partner Manager. The Partner Manager receives:

 IDocs and BAPI calls from an SAP Server or IDoc XML messages from any Web
client

RFCs from an SAP Server, or RFC-XML (XRFC) and bXML messages from any
Web client

Inbound Calls to the Partner Manager

When the Partner Manager receives a message via tRFC or an XML message that contains a TID (transaction ID), this message is registered in the Message Store. The recipient of the message is determined by Routing Rules. Routing Rules contain information about the sender, recipient, and message type. A message can be directed to:

An SAP Server (IDocs, RFCs, and BAPIs) An SAP BC Service on a local or remote server HTTP with a URL as the recipient FTP with recipient An e-mail recipient

Routing Messages Using the Partner Manager