Understanding Event Functionality
Events are generated as a result of activity in an application system. You can an use an event
to trigger an action in your application. For example, SAP R/3 may generate an event when
customer information is updated. If your application must perform when this happens,
your application is a consumer of this event.
After you create a connection to your application system, you can add events using Java
Swing Application Explorer. To create an event, you must create a port and a channel.
•
Port
A port associates a particular business object exposed by the 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 an
Event Port.
•
Channel
A channel represents configured connections to particular instances of back-end
systems. A channel binds one or more event ports to a particular listener managed by
the adapter. For more information, see Creating a Channel on page B-18.
Creating an Event Port
The following procedures describe how to create an event port using Java Swing
Application Explorer. When you use the Application Explorer with an Integration Business
Services Engine (iBSE) implementation, the following port dispositions are available:
•
File
•
iBSE
•
MSMQ
•
JMS queue
•
SOAP
•
HTTP
•
MQ Series
•
MAIL
Note: The MAIL disposition option will be supported in a future release.
The following dispositions are available when using Application Explorer in conjunction
with a JCA connector implementation.
•
File
BEA WebLogic Adapter for SAP User's Guide
Using Application Explorer in BEA WebLogic Workshop for Event Handling
B-3
Need help?
Do you have a question about the WebLogic and is the answer not in the manual?