Adapter
Development
Kit
(ADK)
A
development
kit
that
provides
some
samples
for
adapter
development,
including
sample
connectors
and
Object
Discovery
Agents
(ODAs).
connector
The
component
of
an
adapter
that
uses
business
objects
to
send
information
about
an
event
to
an
integration
broker
(event
notification)
or
receive
information
about
a
request
from
the
integration
broker
(request
processing).
A
connector
consists
of
the
connector
framework
and
the
connector’s
application-specific
component.
connector
framework
The
component
of
a
connector
that
manages
interactions
between
a
connector’s
application-specific
component
and
the
integration
broker.
This
component
provides
all
required
management
services
and
retrieves
the
meta-data
that
the
connector
requires
from
the
repository.
The
connector
framework,
whose
code
is
common
to
all
connectors,
is
written
in
Java
and
includes
a
C++
extension
to
support
application-specific
components
written
in
C++.
connector
controller
The
subcomponent
of
the
connector
framework
that
interacts
with
collaborations.
A
connector
controller
runs
within
InterChange
Server
and
initiates
mapping
between
application-specific
and
generic
business
objects,
and
manages
collaboration
subscriptions
to
business
object
definitions.
integration
broker
The
component
in
the
WebSphere
business
integration
system
that
integrates
data
among
heterogeneous
applications.
An
integration
broker
typically
provides
a
variety
of
services
that
include:
the
ability
to
route
data,
a
repository
of
rules
that
govern
the
integration
process,
connectivity
to
a
variety
of
applications,
and
administrative
capabilities
that
facilitate
integration.
Examples
of
integration
brokers:
the
WebSphere
Business
Integration
Message
Broker;
WebSphere
Business
InterChange
Server.
WebSphere
business
integration
system
An
enterprise
solution
that
moves
information
among
diverse
sources
to
perform
business
exchanges,
and
that
processes
and
routes
information
among
disparate
applications
in
the
enterprise
environment.
The
business
integration
system
consists
of
an
integration
broker
and
one
or
more
adapters.
Siebel
application
architecture
The
Siebel
application
architecture
contains
three
layers,
as
follows:
v
User
interface
objects
layer--This
layer
contains
the
visual
elements
that
the
user
interacts
with.
v
Business
objects
layer--This
layer
contains
both
business
components
and
business
objects.
A
business
component
is
a
fundamental
business
entity,
consisting
of
multiple
fields
that
represent
it.
A
business
object
is
a
collection
of
related
business
components.
The
Siebel
connector
communicates
with
this
layer
using
the
Siebel
Java
Data
Bean.
v
Data
objects
layer--This
layer
contains
the
object
definitions
which
provide
logical
representation
of
the
underlying
physical
database.
It
is
independent
of
the
installed
relational
database
management
system,
and
it
is
not
accessible
by
the
Siebel
Java
Data
Bean.
2
Adapter
for
Siebel
eBusiness
Applications
User
Guide