How to generate an event provider to consume a Web service.
Prerequisites
- An application/class that will call the event provider.
- Typically, a message type (data structure) should also exist before creating an event
proxy.
Context
Event providers can be used instead of standard consumer proxies (service consumers) where
each message from an application needs to be sent to more than one Web service
provider.
The procedure for generating an event provider is basically the same as for a standard
consumer proxy. See Generating a
Consumer Proxy. The main exception is that you currently cannot create an
event proxy by importing a WSDL file (this may be implemented in a future
release).
Procedure
- Create an event provider using the Repository Browser (transaction code
SE80).
- Enter at least one operation.
Before you can activate the event proxy, it must contain at least one
operation. Open the event proxy and go to the External View
tab. Right-click the event name and choose Add operation
Enter a name and click the Continue button.
- Attach a Request message type to the operation.
Request messages are used because communication using event providers is always
asynchronous.
The message type is a data structure (which is usually created by the application
developer), which specifies what types of data can be included in messages for
this operation for this event provider.
- Choose the Activate button to save and activate the event
provider.
Next Steps
You must now define the logical port(s) for the event provider in SOA Manager, to which
messages from this event provider will be sent to. See
Configuring an Event
Provider.
