BEA WebLogic Server, User Manual, Page: 80 / 294

Understanding Event Functionality
5-2 BEA Systems, Inc.
Understanding Event Functionality
Events are generated as a result of activity on an application system. You can use events to
trigger an action in your application.
Applications or functions within SAP may broadcast processing information at predefined
points, called events. You must configure an event listener if you are to receive events from
SAP. For example, the SAP Business Object, Material, may raise the event status Material,
assigned when a material is created. If you wish to consume this event, you must configure
an event listener to capture this event within SAP and transmit the event notification to
your system.
To create an event, you must create a port and a channel using Application Explorer.
The following is a description of how ports and channels work.
• Port
A port associates a particular business object exposed by an adapter with a particular
disposition. A disposition defines the protocol and location of the event data. The port
defines the end point of the event consumption. For more information, see
Creating,
Editing, or Deleting a Port on page 5-2 .
• Channel
A channel represents configured connections to particular instances of back-end or
other types of systems. A channel binds one or more event ports to a particular listener
managed by an adapter. For more information, see
Creating, Editing, or Deleting a
Channel on page 5-16.
Creating, Editing, or Deleting a Port
The following procedures describe how to create, edit, or delete an event port using Servlet
Application Explorer. You can create a port for an SAP business function from the Service
Adapters tab or from the Event Adapters tab.
When you use Application Explorer with an Integration Business Services Engine (iBSE)
implementation, the following port dispositions are available:
• File
• iBSE
• MSMQ
• JMS queue
• SOAP
• HTTP