BEA manual How the BEA WebLogic Adapter for SAP Works

Ad

Page 15

How the BEA WebLogic Adapter for SAP Works

from the physical connection data, which is stored in the WebLogic Integration repository. This shields users from the details of executing SAP IFR XML, IDoc, BAPIs, and RFCs.

The deployed application view from BEA WebLogic Adapter for SAP has the following features:

Support for Remote Function Calls (RFC), Business Application Programming Interfaces (BAPI), and Intermediate Documents (IDoc) interfaces to SAP. RFCs and BAPIs are called synchronously by the adapter and always return data (either technical error information or a well-formed response document). IDocs are processed asynchronously.

Consistent data representation—a standard XML representation of event and service request/response documents for SAP. The developer is freed from the specific details of the SAP interface (BAPI, RFC, IDoc, IFR XML) and the specific configuration details of the target SAP system.

XML validation. The schemas used by WebLogic Integration are validated against SAP Business Object Repository (BOR) to ensure that each message conforms to the correct configuration of the target SAP system. Since the schemas are built dynamically from the target SAP system, this all but eliminates the possibility of errors in formatting or executing SAP requests.

Adheres to SAP ABAP serialization rules and SAP Interface Repository standards published by SAP AG.

Besides being able to run SAP IFR XML, IDocs, BAPIs, and RFCs from WebLogic Integration, the adapter can also receive RFCs and IDocs directly from SAP and make them available to WebLogic Integration. The SAP system can be configured to send an IDoc or RFC out to a logical system when a certain event occurs. The output sent by SAP can be in any of these forms:

An RFC request—for example, RFC_CUSTOMER_GET.

A BAPI request—for example, BAPI_COMPANYCODE_GETLIST.

An IDoc as an XML document—for example, DEBMAS01.

An IDoc in raw data form.

BEA WebLogic Adapter for SAP User Guide

1-5

Image 15

Contents BEA WebLogic Adapter for SAP Copyright Table of Contents Sending SAP Events Using Abap Programs About This Document Related Information What You Need to KnowContact Us Convention Documentation ConventionsConvention Item BEA WebLogic Adapter for SAP User Guide SAP Introducing the BEA WebLogic Adapter for SAP WebLogic Integration WebLogic IntegrationHow the BEA WebLogic Adapter for SAP Works How the BEA WebLogic Adapter for SAP Works 6BEA WebLogic Adapter for SAP User Guide Overview Creating Schemas for SAP Business ObjectsCreating Schemas for SAP Business Objects Generating Schemas Using the BEA Application Explorer Generating Schemas Using the BEA Application ExplorerBEA Application Explorer Window Selecting Session from File BEA Application Explorer Window Selecting New Connection SAP Logon Window System Tab BEA Application Explorer Selecting Application Components Creating Schemas for SAP Business Objects 10 BEA Application Explorer Displaying the BAPI’s Schemas 11 Explorer Window Directory Structure for an SAP connection 13 Sample Request Schema 12BEA WebLogic Adapter for SAP User Guide Creating an Application View Folder WebLogic Integration Application View Console Window Configuring the BEA WebLogic Adapter for SAPEvent Adapter Application Views Event Adapter Application ViewsCreating the Event Adapter Application View Define New Application View Window Configure Connection Parameters Window Application View Administration Window Creating an SAP Remote Destination RFC Destinations Windows RFC Destination for BEA Event Adapter for SAP Window RFC Destination Beaeventdest Window 10 Destination Menu Window 11 Gateway Options Window Configuring the Event Adapter Application View 13 Application View Console Administration Window Configuring the BEA WebLogic Adapter for SAP 14 Application View Administration Window 15 Deploy Application View Window 16 WebLogic Server Log Window 17 Application View Console Window Testing the Event Adapter in the Application View Console 19 Test Event Window 20 Function Builder Initial Window 21 Test Function Module Initial Window 22 Test Result for ListCustomer Window Testing the Event Adapter in Studio 23 New Template Window 24 Start Properties Form Window Service Adapter Application Views Service Adapter Application Views25 Define New Application View Window 26 Configure Connection Parameters Window Configuring the Service Adapter Application View 27 Application View Console Administration Window 28 Add Service Window 29 Deploy Application View Window Testing the Service Adapter Rfccustomerget 31 Test Service Window 32 Test Results Window Listing 3-1 Full Response Document from ListCustomer BEA WebLogic Adapter for SAP IDocs BEA WebLogic Adapter for SAP and IDocs Defining a Logical PortSAP Main Window / Creating a tRFC port Defining a Logical PortCreating a Logical System SAP Main Window / Display Structure Creating a Logical SystemSAP Main Window / New Entries Overview of Added Entries Creating a Partner Profile Creating a Partner ProfileSAP Window / Partner Profiles Outbound Parameters SAP Window / Partner Profiles Summary To create a distribution model called Beamod SAP Window / Distribution Model Changed SAP Window / Add Message Type SAP Window / Distribution Model Changed New Model View Manually Sending an IDoc SAP Window / Send Customers Manually Sending an IDoc10 SAP Window / Master IDocs Set Up for Message Type Debmas Sending SAP Events Using Abap Programs Writing an RFC Module Sending SAP Events Using Abap ProgramsSample RFC Request Document Sample FilesSample Files Sample RFC Response DocumentSample IDoc XML for Message Type Debmas Sample IDoc XML for Message TypeSTKZA/STKZA STKZU/STKZU STKZN/STKZN TXLW2/TXLW2 KUNN20000000001/KUNN2 PARVWWE/PARVW