IBM E02HMLL-I Implementation Guide - Page 151

ControllerTraceLevel, DeliveryQueue, DeliveryTransport, DuplicateEventElimination

Page 151 highlights

However, if the destination application's application-specific component becomes unavailable after the connector controller forwards a service call request to it, the connector controller fails the request. If this property is set to false, the connector controller begins failing all service call requests as soon as it detects that the destination application-specific component is unavailable. The default is true. ControllerTraceLevel Level of trace messages for the connector controller. The default is 0. DeliveryQueue Applicable only if DeliveryTransport is JMS. The queue that is used by the connector to send business objects to InterChange Server Express. The default value is CONNECTORNAME/DELIVERYQUEUE. DeliveryTransport Specifies the transport mechanism for the delivery of events. Possible values are IDL for CORBA IIOP or JMS for Java Messaging Service. The default is IDL. The connector sends service call requests and administrative messages over CORBA IIOP if the value configured for the DeliveryTransport property is IDL. JMS: Enables communication between the connector and client connector framework using Java Messaging Service (JMS). If you select JMS as the delivery transport, additional JMS properties such as jms.MessageBrokerName, jms.FactoryClassName, jms.Password, and jms.UserName, appear in Connector Configurator Express. The first two of these properties are required for this transport. Important: There may be a memory limitation if you use the JMS transport mechanism for a connector running on InterChange Server Express. In this environment, you may experience difficulty starting both the connector controller (on the server side) and the connector (on the client side) due to memory use within the WebSphere MQ client. DuplicateEventElimination When you set this property to true, a JMS-enabled connector can ensure that duplicate events are not delivered to the delivery queue. To use this feature, the connector must have a unique event identifier set as the business object's ObjectEventId attribute in the application-specific code. This is done during connector development. This property can also be set to false. Note: When DuplicateEventElimination is set to true, you must also configure the MonitorQueue property to enable guaranteed event delivery. Chapter 7. Configuring connectors 139

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244
  • 245
  • 246
  • 247
  • 248
  • 249
  • 250
  • 251
  • 252
  • 253
  • 254
  • 255
  • 256
  • 257
  • 258
  • 259
  • 260
  • 261
  • 262
  • 263
  • 264
  • 265
  • 266
  • 267
  • 268
  • 269
  • 270
  • 271
  • 272
  • 273
  • 274
  • 275
  • 276
  • 277
  • 278
  • 279
  • 280
  • 281
  • 282
  • 283
  • 284
  • 285
  • 286
  • 287
  • 288
  • 289
  • 290
  • 291
  • 292
  • 293
  • 294
  • 295
  • 296
  • 297
  • 298
  • 299
  • 300
  • 301
  • 302

However,
if
the
destination
application’s
application-specific
component
becomes
unavailable
after
the
connector
controller
forwards
a
service
call
request
to
it,
the
connector
controller
fails
the
request.
If
this
property
is
set
to
false
,
the
connector
controller
begins
failing
all
service
call
requests
as
soon
as
it
detects
that
the
destination
application-specific
component
is
unavailable.
The
default
is
true
.
ControllerTraceLevel
Level
of
trace
messages
for
the
connector
controller.
The
default
is
0
.
DeliveryQueue
Applicable
only
if
DeliveryTransport
is
JMS.
The
queue
that
is
used
by
the
connector
to
send
business
objects
to
InterChange
Server
Express.
The
default
value
is
CONNECTORNAME/DELIVERYQUEUE
.
DeliveryTransport
Specifies
the
transport
mechanism
for
the
delivery
of
events.
Possible
values
are
IDL
for
CORBA
IIOP
or
JMS
for
Java
Messaging
Service.
The
default
is
IDL.
The
connector
sends
service
call
requests
and
administrative
messages
over
CORBA
IIOP
if
the
value
configured
for
the
DeliveryTransport
property
is
IDL
.
JMS:
Enables
communication
between
the
connector
and
client
connector
framework
using
Java
Messaging
Service
(JMS).
If
you
select
JMS
as
the
delivery
transport,
additional
JMS
properties
such
as
jms.MessageBrokerName,
jms.FactoryClassName
,
j
ms.Password
,
and
jms.UserName
,
appear
in
Connector
Configurator
Express.
The
first
two
of
these
properties
are
required
for
this
transport.
Important:
There
may
be
a
memory
limitation
if
you
use
the
JMS
transport
mechanism
for
a
connector
running
on
InterChange
Server
Express.
In
this
environment,
you
may
experience
difficulty
starting
both
the
connector
controller
(on
the
server
side)
and
the
connector
(on
the
client
side)
due
to
memory
use
within
the
WebSphere
MQ
client.
DuplicateEventElimination
When
you
set
this
property
to
true
,
a
JMS-enabled
connector
can
ensure
that
duplicate
events
are
not
delivered
to
the
delivery
queue.
To
use
this
feature,
the
connector
must
have
a
unique
event
identifier
set
as
the
business
object’s
ObjectEventId
attribute
in
the
application-specific
code.
This
is
done
during
connector
development.
This
property
can
also
be
set
to
false
.
Note:
When
DuplicateEventElimination
is
set
to
true
,
you
must
also
configure
the
MonitorQueue
property
to
enable
guaranteed
event
delivery.
Chapter
7.
Configuring
connectors
139