BEA manual How the BEA WebLogic Adapter for SAP Works

Page 14

1 Introducing the BEA WebLogic Adapter for SAP

How the BEA WebLogic Adapter for SAP Works

The paradigm that the BEA WebLogic Adapter for SAP uses includes application views, event adapters, and services adapters. An application view is a standard self-describing interface to an application. The BEA WebLogic Adapter for SAP services are exposed in WebLogic Integration Studio using design elements, or plug-ins, known as nodes. These include Task nodes, which specify the operations to be performed by a BEA WebLogic Adapter for SAP, and Event nodes, which set the business processes that occur when a specific event is “pushed” from the adapter.

For outbound processing, the BEA WebLogic Adapter for SAP is invoked from the Action node and will, in turn, perform a transaction against SAP using the IFR XML, BAPI, RFC, or IDoc interfaces. For inbound processing, the adapter converts the specific SAP event into an XML document that triggers the start of a business process.

The BEA WebLogic Adapter for SAP interfaces are exposed as application views, providing the XSD XML schemas for event, request, and response document schemas that are imported into the WebLogic Integration repository. Once WebLogic Integration knows of these documents, they can be used in WebLogic Integration Studio and other WebLogic Integration tools. In addition, since application views are supported by the WebLogic Server strategy, the same BEA WebLogic Adapter for SAP can be leveraged by other WebLogic Server JCA-based applications to increase ROI.

The BEA WebLogic Adapter for SAP enables users to execute SAP IFR XML, IDocs, BAPI calls, and custom RFCs from WebLogic Integration as application views. To do this, the user creates the event, request, and response XML document schemas using BEA Application Explorer, which is implemented as a stand-alone Java Swing GUI. This GUI exposes all the components of your SAP system and enables you to select the ones for which you want to create an application view. By connecting the BEA Application Explorer to your SAP system, you can ensure that all the necessary communication and security information is gathered using SAP calls, and then stored in a WebLogic Integration Connection Factory database, to be used at execution time by the BEA WebLogic Adapter for SAP. This allows the application views to separate the business logic—contained in the XML event, request, and response documents—

1-4BEA WebLogic Adapter for SAP User Guide

Page 13 Page 15
Image 14
Page 13 Page 15
Contents BEA WebLogic Adapter for SAP Copyright Table of Contents Sending SAP Events Using Abap Programs About This Document What You Need to Know Related InformationContact Us Documentation Conventions ConventionConvention 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 Creating Schemas for SAP Business Objects OverviewCreating 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 Configuring the BEA WebLogic Adapter for SAP WebLogic Integration Application View Console WindowEvent 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 Defining a Logical Port BEA WebLogic Adapter for SAP and IDocsDefining a Logical Port SAP Main Window / Creating a tRFC portCreating a Logical System Creating a Logical System SAP Main Window / Display StructureSAP 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 Manually Sending an IDoc SAP Window / Send Customers10 SAP Window / Master IDocs Set Up for Message Type Debmas Sending SAP Events Using Abap Programs Sending SAP Events Using Abap Programs Writing an RFC ModuleSample Files Sample RFC Request DocumentSample RFC Response Document Sample FilesSample IDoc XML for Message Type Sample IDoc XML for Message Type DebmasSTKZA/STKZA STKZU/STKZU STKZN/STKZN TXLW2/TXLW2 KUNN20000000001/KUNN2 PARVWWE/PARVW
Top Page Image Contents