BEA WebLogic Server User manual

BEA WebLogic Adapter for SAP User’s Guide
DN3501342.0406
April 19, 2006

EDA, EDA/SQL, FIDEL, FOCCALC, FOCUS, FOCUS Fusion, FOCUS Vision, Hospital-Trac, Information Builders, the Information Builders logo,
Parlay, PC/FOCUS, SmartMart, SmartMode, SNAPpack, TableTalk, WALDO, Web390, WebFOCUS and WorldMART are registered trademarks,
and iWay and iWay Software are trademarks of Information Builders, Inc.
Due to the nature of this material, this document refers to numerous hardware and software products by their trademarks. In most, if not
all cases, these designations are claimed as trademarks or registered trademarks by their respective companies. It is not this publisher’s
intent to use any of these names generically. The reader is therefore cautioned to investigate all claimed trademark rights before using any
of these names other than to refer to the product described.
Copyright © 2006, by BEA Systems, Inc. All rights reserved. Patent Pending. This manual, or parts thereof, may not be reproduced in any
form without the written permission of Information Builders, Inc.

BEA WebLogic Adapter for SAP User’s Guide iii
Preface
This document is written for system integrators who develop client interfaces between SAP
and other applications. It describes how to use the BEA WebLogic Adapter for SAP to
integrate SAP IDocs, RFCs, and BAPIs with your BEA WebLogic Server. It is assumed that
readers understand Web technologies and have a general understanding of Microsoft
Windows and UNIX systems.
How This Manual Is Organized
The following table lists the titles and numbers of the chapters and the appendix for this
manual with a brief description of the contents of each chapter or appendix.
Chapter/Appendix Contents
1Introducing the BEA
WebLogic Adapter for SAP
Provides an overview of the BEA WebLogic
Adapter for SAP. Discusses key features and
functionality of the adapter.
2Configuring SAP Inbound
Processing
Describes how to configure your SAP system for
inbound (client) processing.
3Creating XML Schemas for
SAP
Describes how to create XML schemas for SAP
business objects using Servlet Application
Explorer.
4Creating and Publishing
Integration Business Services
Describes how to create and publish Integration
Business Services using Servlet Application
Explorer.
5Configuring the Event
Adapter for SAP
Describes how to create ports and channels to
listen for SAP events using Servlet Application
Explorer.
6Using Integration Business
Services Policy-Based
Security
Describes how to configure Web services policy-
based security using Servlet Application Explorer.
7Management and
Monitoring
Describes how to use the management and
monitoring tools provided by the Integration
Business Services Engine and the JCA Test Tool.
8Understanding SAP Events Describes how to configure and test your SAP
system for event processing.

iv BEA Systems, Inc.
Documentation Conventions
The following table lists and describes the conventions that apply throughout this manual.
9Troubleshooting and Error
Messages
Describes limitations and workarounds when
connecting to SAP. The adapter-specific errors
listed in this chapter can arise whether using the
adapter with a JCA, or with an iBSE configuration.
AUsing Application Explorer in
BEA WebLogic Workshop to
Create XML Schemas and
Web Services
Describes how to use Application Explorer in BEA
WebLogic Workshop to create XML schemas for
SAP BAPIs, RFCs, and IDocs.
BUsing Application Explorer in
BEA WebLogic Workshop for
Event Handling
Describes how to use Application Explorer in BEA
WebLogic Workshop to create events for SAP. In
addition, this section provides information on
using events in a clustered BEA WebLogic
environment.
CUsing WebLogic Workshop
to Access Web Services
Describes how to access Web services created for
an SAP Business Application Programming
Interface (BAPI) and an SAP Remote Function Call
(RFC) using BEA WebLogic Workshop.
DSample Files and Coding
Techniques
Provides sample request and response documents
sent between SAP and the BEA WebLogic Adapter
for SAP as well as a sample RFC module.
Chapter/Appendix Contents
Convention Description
THIS TYPEFACE or
this typeface
Denotes syntax that you must enter exactly as shown.
this typeface Represents a placeholder (or variable) in syntax for a value that
you or the system must supply.
underscore Indicates a default setting.
this typeface Represents a placeholder (or variable), a cross-reference, or an
important term.
this typeface Highlights a file name or command.

BEA WebLogic Adapter for SAP User’s Guide v
Contact Us!
Your feedback on the BEA WebLogic Adapter for SAP documentation is important to us.
Send us e-mail at docsuppor[email protected] if you have questions or comments. Your
comments will be reviewed directly by the BEA professionals who create and update the
BEA WebLogic Adapter for SAP documentation.
In your e-mail message, please indicate that you are using the documentation for BEA
WebLogic Adapter for SAP and the version of the documentation.
If you have any questions about this version of BEA WebLogic Adapter for SAP, or if you
have problems using the BEA WebLogic Adapter for SAP, contact BEA Customer Support
through BEA WebSUPPORT at www.bea.com. You can also contact Customer Support by
using the contact information provided on the Customer Support Card which is included in
the product package.
When contacting Customer Support, be prepared to provide the following information:
• Your name, e-mail address, phone number, and fax number
• Your company name and company address
• Your machine type and authorization codes
• The name and version of the product you are using
• A description of the problem and the content of pertinent error messages
Key + Key Indicates keys that you must press simultaneously.
{ } Indicates two or three choices; type one of them, not the
braces.
|Separates mutually exclusive choices in syntax. Type one of
them, not the symbol.
... Indicates that you can enter a parameter multiple times. Type
only the parameter, not the ellipsis points (…).
.
.
.
Indicates that there are (or could be) intervening or additional
commands.
Convention Description

vi BEA Systems, Inc.
Help Us to Serve You Better
To help our consultants answer your questions effectively, please be prepared to provide
specifications and sample files and to answer questions about errors and problems.
The following tables list the specifications our consultants require.
The following table lists components. Specify the version in the column provided.
The following table lists the types of Application Explorer. Specify the version (and platform,
if different than listed previously) in the columns provided.
In the following table, specify the JVM version and vendor in the columns provided.
Platform
Operating System
OS Version
Product List
Adapters
Adapter Deployment For example, JCA, or Integration Business Services Engine.
Container Version
Component Version
Adapter
EIS (DBMS/APP)
HOTFIX / Service Pack
Application Explorer Type Version Platform
Swing
Servlet
ASP
Version Vendor

BEA WebLogic Adapter for SAP User’s Guide vii
The following table lists additional questions to help us serve you better.
The following table lists error/problem files that might be applicable.
Request/Question Error/Problem Details or Information
Provide usage scenarios or summarize the
application that produces the problem.
Did this happen previously?
Can you reproduce this problem
consistently?
Any change in the application
environment: software configuration, EIS/
database configuration, application, and so
forth?
Under what circumstance does the problem
not occur?
Describe the steps to reproduce the
problem.
Describe the problem.
Specify the error message(s).
XML schema
XML instances
Other input documents (transformation)
Error screen shots
Error output files
Trace and log files
Log transaction

viii BEA Systems, Inc.

BEA WebLogic Adapter for SAP User’s Guide ix
Contents
1. Introducing the BEA WebLogic Adapter for SAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-1
Features of the BEA WebLogic Adapter for SAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-2
SAP Certification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-2
Supported Versions and Platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-3
SAP Business Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-4
Integrating With SAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-5
Understanding Web Services and Java Connector Architecture Functionality . . . . . . . . . . . . . . . . . . .1-6
Web Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-6
Java Connector Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-6
Component Information for the BEA WebLogic Adapter for SAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-7
Component Information Roadmap . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-7
Application Explorer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-7
Integration Business Services Engine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-8
Enterprise Connector for J2EE Connector Architecture (JCA) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-9
2. Configuring SAP Inbound Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-1
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-2
Configuring a Logical System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-3
Configuring a Distribution Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-6
Defining a Partner Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-9
3. Creating XML Schemas for SAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-1
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-2
Starting Servlet Application Explorer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-2
Establishing a Target for SAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-3
Creating a New Target . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-4
Connecting to a Target . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10
Disconnecting From a Target . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-11
Modifying a Target . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-12
Deleting a Target . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-13
Viewing Application System Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-14
Creating an XML Schema . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-17
4. Creating and Publishing Integration Business Services . . . . . . . . . . . . . . . . . . . . . .4-1
Understanding Integration Business Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-2
Creating Integration Business Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-2
Creating Business Services With Application Explorer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-2
Generating WSDL From a Web Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-11
Identity Propagation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-24

xBEA Systems, Inc.
5. Configuring the Event Adapter for SAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-1
Understanding Event Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-2
Creating, Editing, or Deleting a Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-2
Creating, Editing, or Deleting a Channel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-16
Synchronous Event Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-26
6. Using Integration Business Services Policy-Based Security . . . . . . . . . . . . . . . . . . .6-1
Integration Business Services Policy-Based Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-2
Configuring Integration Business Services Policy-Based Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-3
7. Management and Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-1
Managing and Monitoring Services and Events Using iBSE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-2
Managing and Monitoring Services and Events Using the JCA Test Tool . . . . . . . . . . . . . . . . . . . . . . 7-16
Setting Engine Log Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-20
Configuring Connection Pool Sizes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-22
Migrating Repositories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-23
File Repositories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-23
iBSE Repositories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-24
JCA Repositories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-28
Migrating Event Handling Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-28
Exporting or Importing Targets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-33
Retrieving or Updating Web Service Method Connection Information . . . . . . . . . . . . . . . . . . . . . . . . 7-37
Starting or Stopping a Channel Programmatically . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-41
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-45
8. Understanding SAP Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-1
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-2
Related Concepts and Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-2
Client and Server Programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-2
SAP Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-2
Program IDs and Load Balancing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-3
Registering Your Program ID in SAPGUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-3
Testing the SAP Event Adapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-6
Application Link Enabling Configuration for the Event Adapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-8
Collected IDocs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-13
Testing the SAP ALE Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-16
Usage Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-17
Multiple Events Using Identical Program IDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-17
9. Troubleshooting and Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-1
Troubleshooting Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-2
Error Messages in Application Explorer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-2
Error Messages in SAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-5
Error Messages in JCA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-6

BEA WebLogic Adapter for SAP User’s Guide xi
Error Messages in iBSE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-6
General Error Handling in iBSE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-6
Adapter-Specific Error Handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-7
A. Using Application Explorer in BEA WebLogic Workshop to Create XML Schemas
and Web Services A-1
Starting Application Explorer in BEA WebLogic WorkShop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2
Creating a New Configuration for iBSE or JCA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-3
Connecting to SAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-5
Creating and Connecting to a Target . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-5
Managing a Target . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-10
Viewing an Application System Object and Creating an XML Schema . . . . . . . . . . . . . . . . . . . . . . . . . A-12
Creating an Integration Business Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-17
Exporting WSDL for Use in BEA WebLogic WorkShop Workflows . . . . . . . . . . . . . . . . . . . . . . . . A-21
Identity Propagation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-23
Adding a Control for a Resource in BEA WebLogic Workshop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-26
Adding a Web Service Control to a BEA WebLogic Workshop Application . . . . . . . . . . . . . . . A-26
Extensible CCI Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-27
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-27
Using the Extensible CCI Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-27
B. Using Application Explorer in BEA WebLogic Workshop for Event Handling . . .B-1
Starting Application Explorer in BEA WebLogic WorkShop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .B-2
Understanding Event Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .B-3
Creating an Event Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .B-3
Modifying an Event Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-16
Creating a Channel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-18
Modifying a Channel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-22
Deploying Components in a Clustered BEA WebLogic Environment . . . . . . . . . . . . . . . . . . . . . . . . . . B-25
C. Using WebLogic Workshop to Access Web Services . . . . . . . . . . . . . . . . . . . . . . . . . .C-1
Using WebLogic Workshop to Access an SAP BAPI or an SAP RFC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .C-2
Accessing an SAP BAPI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .C-2
Calling a New Web Service for a BAPI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .C-4
Accessing an SAP RFC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .C-8
Calling a New Web Service for an RFC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-10
Running the JWSNAME Web Service From WebLogic Workshop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-14
Confirming WebLogic Server is Running . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-14
Running the JWSNAME Web Service for a BAPI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-15
Calling Complex Operations in a Workflow for a BAPI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-17
Running the JWSNAME Web Service for an RFC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-18
Calling Complex Operations in a Workflow for an RFC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-20

xii BEA Systems, Inc.
D. Sample Files and Coding Techniques . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-1
Sample RFC Request Document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-2
Sample RFC Response Document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-2
Sample IDoc XML for Message Type DEBMAS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-3
Collected IDocs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-9
Sample RFC Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-9
Sample Wrapper Module to Call Functions on Remote Destinations (Service) . . . . . . . . . . . . . . . . . D-10
Using Staging BAPIs to Retrieve SAP BW Metadata . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-12

BEA WebLogic Adapter for SAP User’s Guide 1-1
CHAPTER 1
Introducing the BEA WebLogic Adapter for SAP
Topics:
• Features of the BEA WebLogic Adapter for SAP
• SAP Certification
• SAP Business Components
• Integrating With SAP
• Understanding Web Services and Java
Connector Architecture Functionality
• Component Information for the BEA
WebLogic Adapter for SAP
The following section provides an overview of the
BEA WebLogic Adapter for SAP.

Features of the BEA WebLogic Adapter for SAP
1-2 BEA Systems, Inc.
Features of the BEA WebLogic Adapter for SAP
The BEA WebLogic Adapter for SAP is a remote function call adapter that provides a means
to exchange real-time business data between SAP R/3 systems and other application,
database, or external business partner systems. The adapter enables external applications
for inbound and outbound processing with SAP.
The adapter uses XML messages to enable non-SAP applications to communicate and
exchange transactions with SAP using one of the following two methods.
•Event Adapter. Applications use this capability if they require access to SAP data only
when an SAP business event occurs.
•Request/response. Applications use this capability when they must initiate an SAP
business event.
If the request is for retrieving data from SAP, then the adapter sends the application a
response message in the form of an XML document with the data embedded.
The BEA WebLogic Adapter for SAP provides:
• Support for bidirectional message interactions.
• The Servlet Application Explorer, a GUI tool that uses SAP object repository metadata to
build XML schemas and Web services to handle adapter requests or event data.
• Support for Remote Function Calls (RFC), Business Application Programming Interfaces
(BAPI), and Intermediate Documents (IDoc) interfaces to SAP.
SAP Certification
The BEA WebLogic Adapter for SAP provides state-of-the-art middleware solutions for SAP
Basis and SAP Web application server-based systems. The adapter has earned the following
three interface certifications which demonstrate that it promotes cost-effective and
low-risk solutions.
•CA-ALE certification. Enhances electronic data interchange (EDI) subsystem interface
with SAP Basis and SAP Web Application Server. Using direct program-to-program
remote communication and transformation from non-SAP systems to SAP
solution-based systems, the adapter expedites the conversion, import, and export of
critical intermediate documents (IDocs).
•CA-AMS certification. Rapidly bridges SAP Basis and SAP Web Application Server data
exchange with other applications through pure message delivery. As an ALE
(Application Link Enabling)Message Handler, the adapter sends IDoc messages
without a requirement for conversion from one or more SAP solution-based systems.

Introducing the BEA WebLogic Adapter for SAP
BEA WebLogic Adapter for SAP User’s Guide 1-3
•CA-XML certification. Eases the communication between external middleware with
SAP Basis and SAP Web Application Server over the Internet using XML, HTTP, or HTTPS.
The adapter immediately transforms SAP solution specifications into XML for straight
transfer into application subsystem repositories. The adapter directly receives and
converts messages to be pulled or pushed into XML formats to or from SAP
solution-based systems over the Internet.
Supported Versions and Platforms
The BEA WebLogic Adapter for SAP supports R/3 and R/3 Enterprise. The following SAP R/3
versions are supported by the BEA WebLogic Adapter for SAP:
•4.6C
•4.6D
• SAP R/3 Enterprise 47x100
SAP R/3 Enterprise Version 47x100 is supported on the SAP Web Application Server
Versions 6.20 and 6.40.
• SAP R/3 Enterprise 47x200
SAP R/3 Enterprise Version 47x200 is supported on the SAP Web Application Server
Versions 6.20 and 6.40.
• SAP Java Connector (SAP JCo) 2.1.6
Note: For the current release status of the SAP Java Connector, refer to SAP Note
#549268 in the SAP Service Marketplace.
In addition, the BEA WebLogic Adapter for SAP supports those SAP versions that are on the
mainstream maintenance track as defined by the SAP Service Marketplace release strategy.
To access this document, use the following URL:
http://service.sap.com/releasestrategy/
If the SAP R/3 version you are looking for is not listed in this table, please consult your BEA
Customer Service Representative.
The following 32-bit platforms are supported by the BEA WebLogic Adapter for SAP:
• MS Windows 2000 with SP2, MS Windows 2003
• Sun Solaris 8 and Sun Solaris 9
• HP-UX 11
• IBM AIX 5
• Red Hat Enterprise Linux ES version 3.0
•TRU64

SAP Business Components
1-4 BEA Systems, Inc.
•OS/400
•Z/OS
For additional platform or operating system support information for the BEA WebLogic
Adapter for SAP, contact Customer Support.
SAP Business Components
The BEA WebLogic Adapter for SAP is designed to provide standard access to SAP business
components such as Remote Function Call (RFC) modules, BAPIs (Business Application
Programming Interfaces), and IDocs (Intermediate Documents), that are used to support
existing business processes.
These business components and methods are available to the adapter as requests of SAP
and to the event adapter when SAP invokes its remote requests and work in the following
ways:
Business Application Programming Interfaces (BAPIs) are interfaces within the business
framework that are used to link SAP components to one another or to third-party
components. BAPIs are called synchronously and return information.
Remote Function Call (RFC) Modules are SAP application interfaces that enable clients to
invoke SAP technologies and receive responses.
Note: Depending on the release or service pack installed, certain RFCs may not exist in your
particular SAP system. Therefore, the examples included in this documentation may not be
relevant to your system. If this is the case, you should use the examples as a general
reference for adapter functionality and choose an RFC that exists within your SAP
application environment.
As described in SAP Release Note 109533, SAP Function Modules (RFCs) can be delivered
with different release statuses. SAP supports only RFCs that are awarded with the Released
for Customer status. There is no claim to the release independencies of the interfaces and
the continued existence/functionality of the modules. For more information on the status
of a specific function module, consult your SAP Service Marketplace.
Intermediate Documents (IDocs) are the “logical messages” that correspond to different
business processes. They enable different application systems to be linked by a
message-based interface. The IDoc type indicates the SAP format to use to transfer the data
for a business transaction. An IDoc is a real business process in the form of an IDoc type that
can transfer several message types. An IDoc type is described by the following
components:
•Control records. A control record contains data that identifies the sender, the receiver,
and the IDoc structure. An IDoc contains one control record.

Introducing the BEA WebLogic Adapter for SAP
BEA WebLogic Adapter for SAP User’s Guide 1-5
•Data records. A data record consists of a fixed administration part and a data part
(segment). The number and format of the segments can be different for each IDoc type.
•Status records. A status record describes the processing stages through which an IDoc
passes.
The following scenario is an example of IDoc functionality and its components:
Purchase order number 4711 was sent to a vendor as IDoc number 0815. IDoc number
0815 is formatted in IDoc type ORDERS01 and has the status records “created” and
“sent.” The purchase order corresponds to the “logical” message ORDERS.
Integrating With SAP
You can use the BEA WebLogic Adapter for SAP to invoke an SAP business process, for
example, add/update account, or you can use the adapter as part of an integration effort to
connect SAP and non-SAP systems.
BAPIs and RFCs are called synchronously by the adapter and always return data (either
technical error information or a well-formed response document). IDocs are processed
asynchronously.
The adapter is bidirectional and can process an event in SAP by receiving RFCs and IDocs
directly from SAP. The SAP system can be configured to send an IDoc or RFC to a logical
system when a certain event occurs, in this case to the adapter. The output sent by SAP can
be in any of the following forms:
• An RFC request, for example, RFC_SYSTEM_INFO.
• A BAPI request, for example, BAPI_COMPANYCODE_GETLIST.
•AnIDoc.
For request processing, the BEA WebLogic Adapter for SAP can send requests to SAP using
the BAPI, RFC, or IDoc interfaces.
The adapter quickly and easily integrates your SAP IDocs, RFCs, and BAPIs with mission
critical SAP system applications and other enterprise applications. The benefits of the
adapter include:
• Elimination of the requirement for custom coding.
• Consistent data representation.
Provides a standard XML representation of event data and request/response
documents for SAP.
The developer is freed from the specific details of the SAP interface (BAPI, RFC, IDoc)
and the specific configuration details of the target SAP system.

Understanding Web Services and Java Connector Architecture Functionality
1-6 BEA Systems, Inc.
• Adherence to SAP ABAP serialization rules and SAP Interface Repository standards
published by SAP AG.
Understanding Web Services and Java Connector Architecture
Functionality
The following section describes how the BEA WebLogic Adapter for SAP can incorporate
Web services and Java Connector Architecture technology.
Web Services
Web services allow SAP calls to be made across the Internet or an intranet, using specialized
versions of the XML language that allow a developer to specify the parameters,
connections methods, and remote calls and store them for reference in a repository. At
runtime, a person, an interface, or another function, can read this repository and
automatically invoke the service. Web services currently do not have industry standards for
transactional behavior. Web services are useful when your function calls must be made
across firewall boundaries. Using Web services, you can use functions provided by external
providers, as long as you know the function interface.
Web Services Example
A Web service exposes the “cup” interface, which provides a teacup. The Acme Company
exposes the “tea” Web service, which provides a brown liquid when the correct parameter
“money” is provided. A cup of tea can be received by invoking the “tea” Web service and
passing the “money” parameter. Additional components are not required to receieve tea
via the “tea” Web service.
Java Connector Architecture
Java Connector Architecture (JCA) provides a reusable component model to build and
deploy multi-tier applications that are platform and vendor-independent. JCA acts as a
type of envelope or “container” that will allow the adapter to run inside the BEA WebLogic
Server and connect to SAP and immediately return the results. JCA is useful when your SAP
system resides within a local intranet or is accesed directly. JCA implements JAVA
Connection and Transaction models. JCA requires a resource adapter to be physically
deployed on the host application server to access the remote EIS system.
Using combinations of JCA and Web services is possible. For example, a JCA application can
be invoked via a Web service or a Web service may be implemented inside a JCA container.
The standards and protocols are still evolving.

Introducing the BEA WebLogic Adapter for SAP
BEA WebLogic Adapter for SAP User’s Guide 1-7
JCA Example
An application server,“Table” implements the “tea” container, which contains “tea, gas heat,
water, and cup”. A JCA container can be deployed that contains tea in the “Table”
application server. If any of the elements of “tea” container are missing, for example, “gas
heat”, then no tea is produced. The container must physically possess the “tea, gas heat,
water, and cup” components to receive the tea.
Component Information for the BEA WebLogic Adapter for SAP
The BEA WebLogic Adapter for SAP works in conjunction with one of the following
components:
• Integration Business Services Engine (iBSE)
• Enterprise Connector for J2EE™ Connector Architecture (JCA)
Component Information Roadmap
The following table lists the deployment component and the location of component
information for the BEA WebLogic Adapter for SAP. A description of Application Explorer,
the Integration Business Services Engine (iBSE), and the Enterprise Connector for J2EE
Connector Architecture (JCA) follows the table
Application Explorer
Application Explorer uses an explorer metaphor to browse the SAP system for metadata.
The explorer enables you to create XML schemas and Web services for the associated
object. In addition, you can create ports and channels to listen for events in SAP. External
applications that access SAP through the BEA WebLogic Adapter for SAP use either XML
schemas or Web services to pass data between the external application and the adapter.
Deployed Component For more information, see
Application Explorer Chapters 3, 4, and 5 of this guide
Appendix A of this guide when using
Application Explorer inside WebLogic
Workshop
BEA WebLogic ERP Adapter Installation and
Configuration
Integration Business Services Engine
(iBSE)
BEA WebLogic ERP Adapter Installation and
Configuration
Enterprise Connector for J2EE
Connector Architecture (JCA)
BEA WebLogic ERP Adapter Installation and
Configuration

Component Information for the BEA WebLogic Adapter for SAP
1-8 BEA Systems, Inc.
The following versions of Application Explorer are available when deploying the adapter
with BEA WebLogic Server:
•Servlet. Deployed as a Web application, this version is accessible through a Web
browser. In addition, the servlet Application Explorer can be used with Integration
Business Services Engine (iBSE) and Enterprise Connector for J2EE Connector
Architecture (JCA). For more information, see the following chapters:
•Chapter3,Creating XML Schemas for SAP
•Chapter4,Creating and Publishing Integration Business Services
•Chapter5,Configuring the Event Adapter for SAP
•Integrated Java Swing. Tightly integrated within the BEA WebLogic toolset, the
integrated Java Swing Application Explorer can be accessed directly from WebLogic
WorkShop, where WSDL (Web Services Description Language) files generated from
Integration Business Services and XML schemas can be shared as resources within a
WebLogic WorkShop application. For more information, see Appendix A, Using
Application Explorer in BEA WebLogic Workshop to Create XML Schemas and Web Services.
Note: To use Application Explorer within WebLogic WorkShop, you must deploy the
Integration Business Services Engine (iBSE). For more information, see the BEA
WebLogic ERP Installation and Configuration documentation.
Integration Business Services Engine
The Integration Business Services Engine (iBSE) exposes—as Web services—enterprise
assets that are accessible from adapters regardless of the programming language or the
particular operating system.
iBSE simplifies the creation and execution of Web services when running:
• Custom and legacy applications.
• Database queries and stored procedures.
• Packaged applications.
• Terminal emulation and screen-based systems.
• Transactional systems.
Web services is a distributed programming architecture that solves Enterprise Application
Integration (EAI) hurdles that other programming models cannot. It enables programs to
communicate with one another using a text-based, platform and language independent
message format called XML.