
Overview
8-2
BEA Systems, Inc.
Overview
An event in SAP is defined as an occurrence of a status change in an object. The event is
created when the relevant status change occurs. You or SAP must implement event
creation.
An event is created from a specific application program (the event creator) and then
“published” system-wide. An unlimited number of receivers can respond to the event with
their own “response mechanisms”. An event is usually defined as a component of an object
type.
SAP “pseudo events” are events that are not processed by the SAP Event manager, but are
called from an ABAP program or Remote Function call (using the Destination parameter).
Related Concepts and Terminology
The following topics list and define specific terminology related to SAP and SAP event
handling.
Client and Server Programs
RFC (Remote Function Call) programs for non-SAP systems can function as either the caller
or the called program in an RFC communication. The two types of RFC programs are:
•
RFC Client
•
RFC Server
The RFC client is the instance that calls the RFC to execute the function that is provided by
an RFC server. The functions that can be executed remotely are called RFC functions, and
the functions provided by the RFC API are called RFC calls.
SAP Gateway
The SAP Gateway is a secure BEA WebLogic Server. No connections are accepted unless
they were pre-registered previously from the SAP presentation Client. A server connection
presents itself to the Gateway and exposes a Program Identifier. If the Program Identifier is
found in the list of registered Program IDs, the Gateway server then offers a connection to
the server, which accepts a connection.
The Program ID then is linked with an RFC Destination within SAP, which enables SAP
Function Modules and ALE documents (IDocs or BAPI IDocs) to be routed to the
destination. The RFC Destination functions as a tag to mask the Program ID to SAP users.
An RFC server program can be registered with the SAP Gateway and wait for incoming RFC
call requests. An RFC server program registers itself under a Program ID at an SAP Gateway
and not for a specific SAP system.
Summary of Contents for WebLogic Server
Page 1: ...BEA WebLogic Adapter for SAP User s Guide DN3501342 0406 April 19 2006 ...
Page 8: ...viii BEA Systems Inc ...
Page 22: ...Component Information for the BEA WebLogic Adapter for SAP 1 10 BEA Systems Inc ...
Page 54: ...Creating an XML Schema 3 20 BEA Systems Inc ...
Page 163: ...Management and Monitoring BEA WebLogic Adapter for SAP User s Guide 7 45 ...
Page 164: ...7 46 BEA Systems Inc ...
Page 294: ...Using Staging BAPIs to Retrieve SAP BW Metadata D 14 BEA Systems Inc ...