The structure of an event notification business object is
similar to the structure of a request business object in that they
both require attributes for a URL, MIME type, BOPrefix, response
business object, and request business object. The only difference
in business object processing is how the connector handles the
contents of the response business object. For event notification,
the connector expects the response business object to contain child
business objects that represent events.
When defining an event notification business object, keep the
following in mind:
- The top-level business object needs to have both a request and
a response attribute. They both need to be required, and they need
to be of different types.
- Place the request business object before the response business
object.
- A response business object can return multiple child business
objects of the same type. For example, you can design the response
business object to return only customer events.
- A response business object can return multiple child business
objects of different types. For example, you can design the
response business object to return order and customer events.
- All unsubscribed child business objects are archived to the
archive directory.
- The business object must have the 'DefaultVerbName'
verb added to the Supported Verb column along with the default verb
in the Application-Specific Information column of the business
object definition. The default verb is the verb to be used for
event notification so that subscriptions are checked properly. You
must set the verb for each business object that is to be sent to
the integration broker.
Figure 7 illustrates the placement of
the 'DefaultVerbName' in the Business Object Definitions.
Figure 7. Placement of
the 'DefaultVerbName' in the business object
definitions

