Filter
Top Products
them
to
multiple
collaboration
instances
simultaneously.
This
speeds
delivery
of
business
objects
to
the
integration
broker,
particularly
if
the
business
objects
use
complex
maps.
Increasing
the
arrival
rate
of
business
objects
to
collaborations
can
improve
overall
performance
in
the
system.
To
implement
concurrent
processing
for
an
entire
flow
(from
a
source
application
to
a
destination
application),
the
following
properties
must
configured:
v
The
collaboration
must
be
configured
to
use
multiple
threads
by
setting
its
Maximum
number
of
concurrent
events
property
high
enough
to
use
multiple
threads.
v
The
destination
application’s
application-specific
component
must
be
configured
to
process
requests
concurrently.
That
is,
it
must
be
multithreaded,
or
it
must
be
able
to
use
connector
agent
parallelism
and
be
configured
for
multiple
processes.
The
Parallel
Process
Degree
configuration
property
must
be
set
to
a
value
larger
than
1.
The
ConcurrentEventTriggeredFlows
property
has
no
effect
on
connector
polling,
which
is
single-threaded
and
is
performed
serially.
This
property
is
valid
only
if
the
value
of
the
RepositoryDirectory
property
is
set
to
<REMOTE>.
The
default
value
is
1.
ContainerManagedEvents
The
ContainerManagedEvents
property
allows
a
JMS-enabled
connector
with
a
JMS
event
store
to
provide
guaranteed
event
delivery,
in
which
an
event
is
removed
from
the
source
queue
and
placed
on
the
destination
queue
as
one
JMS
transaction.
When
this
property
is
set
to
JMS,
the
following
properties
must
also
be
set
to
enable
guaranteed
event
delivery:
v
PollQuantity
=
1
to
500
v
SourceQueue
=
/SOURCEQUEUE
You
must
also
configure
a
data
handler
with
the
MimeType
and
DHClass
(data
handler
class)
properties.
You
can
also
add
DataHandlerConfigMOName
(the
meta-object
name,
which
is
optional).
To
set
those
values,
use
the
Data
Handler
tab
in
Connector
Configurator.
Although
these
properties
are
adapter-specific,
here
are
some
example
values:
v
MimeType
=
text\xml
v
DHClass
=
com.crossworlds.DataHandlers.text.xml
v
DataHandlerConfigMOName
=
MO_DataHandler_Default
The
fields
for
these
values
in
the
Data
Handler
tab
are
displayed
only
if
you
have
set
the
ContainerManagedEvents
property
to
the
value
JMS.
Note:
When
ContainerManagedEvents
is
set
to
JMS,
the
connector
does
not
call
its
pollForEvents()
method,
thereby
disabling
that
method’s
functionality.
The
ContainerManagedEvents
property
is
valid
only
if
the
value
of
the
DeliveryTransport
property
is
set
to
JMS.
94
Adapter
for
Siebel
eBusiness
Applications
User
Guide