Filter
Top Products
Common
Event
Infrastructure
event
catalog
to
determine
the
definitions
of
appropriate
events
and
their
properties.
The
events
must
be
defined
in
the
event
catalog
for
the
consumer
application
to
be
able
to
consume
the
sending
application’s
events.
The
“Common
Event
Infrastructure
event
catalog
definitions”
appendix
of
this
document
contains
XML
format
metadata
showing,
for
WebSphere
Business
Information
adapters,
the
event
descriptors
and
properties
the
consumer
application
should
search
for.
For
more
information
For
more
information
about
Common
Event
Infrastructure,
refer
to
the
Common
Event
Infrastructure
information
in
the
WebSphere
Business
Integration
Server
Foundation
documentation,
available
at
the
following
URL:
http://publib.boulder.ibm.com/infocenter/ws51help
For
sample
XML
metadata
showing
the
adapter-generated
event
descriptors
and
properties
a
consumer
application
should
search
for,
refer
to“Common
Event
Infrastructure
event
catalog
definitions.”
Common
Event
Infrastructure
event
catalog
definitions
The
Common
Event
Infrastructure
event
catalog
contains
event
definitions
that
can
be
queried
by
other
applications.
The
following
are
event
definition
samples,
using
XML
metadata,
for
typical
adapter
events.
If
you
are
writing
another
application,
your
application
can
use
event
catalog
interfaces
to
query
against
the
event
definition.
For
more
information
about
event
definitions
and
how
to
query
them,
refer
to
the
Common
Event
Infrastructure
documentation
that
is
available
from
the
online
IBM
WebSphere
Server
Foundation
Information
Center.
For
WebSphere
Business
Integration
adapters,
the
extended
data
elements
that
need
to
be
defined
in
the
event
catalog
are
the
keys
of
the
business
object.
Each
business
object
key
requires
an
event
definition.
So
for
any
given
adapter,
various
events
such
as
start
adapter,
stop
adapter,
timeout
adapter,
and
any
doVerbFor
event
(create,
update,
or
delete,
for
example)
must
have
a
corresponding
event
definition
in
the
event
catalog.
The
following
sections
contain
examples
of
the
XML
metadata
for
start
adapter,
stop
adapter,
and
event
request
or
delivery.
XML
format
for
“start
adapter”
metadata
<eventDefinition
name="startADAPTER"
parent="event">
<property
name
=”creationTime"
//Comment:
example
value
would
be
"2004-05-13T17:00:16.319Z"
required="true"
/>
<property
name="globalInstanceId"
//Comment:
Automatically
generated
by
Common
Event
Infrastructure
required="true"/>
<property
name="sequenceNumber"
//Comment:
Source
defined
number
for
messages
to
be
sent/sorted
logically
required="false"/>
<property
name="version"
//Comment:
Version
of
the
event
required="false"
defaultValue="1.0.1"/>
114
Adapter
for
Siebel
eBusiness
Applications
User
Guide