IBM E02HMLL-I Implementation Guide - Page 143

Saving, configuration

Page 143 highlights

Resources The Resource tab allows you to set a value that determines whether and to what extent the connector agent will handle multiple processes concurrently, using connector agent parallelism. Not all connectors support this feature. If you are running a connector agent that was designed in Java to be multi-threaded, you are advised not to use this feature, since it is usually more efficient to use multiple threads than multiple processes. Setting trace/log file values When you open a connector configuration file or a connector definition file, Connector Configurator Express uses the logging and tracing values of that file as default values. You can change those values in Connector Configurator Express. To change the logging and tracing values: 1. Click the Trace/Log Files tab. 2. For either logging or tracing, you can choose to write messages to one or both of the following: v To console (STDOUT): Writes logging or tracing messages to the STDOUT display. Note: You can only use the STDOUT option from the Trace/Log Files tab for connectors running on the Windows platform. v To File: Writes logging or tracing messages to a file that you specify. To specify the file, click the directory button (ellipsis), navigate to the preferred location, provide a file name, and click Save. Logging or tracing message are written to the file and location that you specify. Note: Both logging and tracing files are simple text files. You can use the file extension that you prefer when you set their file names. For tracing files, however, it is advisable to use the extension .trace rather than .trc, to avoid confusion with other files that might reside on the system. For logging files, .log and .txt are typical file extensions. Data handlers The data handlers section is available for configuration only if you have designated a value of JMS for DeliveryTransport and a value of JMS for ContainerManagedEvents. Adapters that make use of the guaranteed event delivery enable this tab. See the descriptions under ContainerManagedEvents in the Standard Properties appendix for values to use for these properties. Saving your configuration file After you have created the configuration file and set its properties, you need to deploy it to the correct location for your connector. Save the configuration in an ICL project, and use System Manager to load the file into InterChange Server Express. The file is saved as an XML document. You can save the XML document in three ways: v From System Manager, as a file with a *.con extension in an Integration Component Library, or Chapter 7. Configuring connectors 131

  • 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

Resources
The
Resource
tab
allows
you
to
set
a
value
that
determines
whether
and
to
what
extent
the
connector
agent
will
handle
multiple
processes
concurrently,
using
connector
agent
parallelism.
Not
all
connectors
support
this
feature.
If
you
are
running
a
connector
agent
that
was
designed
in
Java
to
be
multi-threaded,
you
are
advised
not
to
use
this
feature,
since
it
is
usually
more
efficient
to
use
multiple
threads
than
multiple
processes.
Setting
trace/log
file
values
When
you
open
a
connector
configuration
file
or
a
connector
definition
file,
Connector
Configurator
Express
uses
the
logging
and
tracing
values
of
that
file
as
default
values.
You
can
change
those
values
in
Connector
Configurator
Express.
To
change
the
logging
and
tracing
values:
1.
Click
the
Trace/Log
Files
tab.
2.
For
either
logging
or
tracing,
you
can
choose
to
write
messages
to
one
or
both
of
the
following:
v
To
console
(STDOUT):
Writes
logging
or
tracing
messages
to
the
STDOUT
display.
Note:
You
can
only
use
the
STDOUT
option
from
the
Trace/Log
Files
tab
for
connectors
running
on
the
Windows
platform.
v
To
File:
Writes
logging
or
tracing
messages
to
a
file
that
you
specify.
To
specify
the
file,
click
the
directory
button
(ellipsis),
navigate
to
the
preferred
location,
provide
a
file
name,
and
click
Save
.
Logging
or
tracing
message
are
written
to
the
file
and
location
that
you
specify.
Note:
Both
logging
and
tracing
files
are
simple
text
files.
You
can
use
the
file
extension
that
you
prefer
when
you
set
their
file
names.
For
tracing
files,
however,
it
is
advisable
to
use
the
extension
.trace
rather
than
.trc
,
to
avoid
confusion
with
other
files
that
might
reside
on
the
system.
For
logging
files,
.log
and
.txt
are
typical
file
extensions.
Data
handlers
The
data
handlers
section
is
available
for
configuration
only
if
you
have
designated
a
value
of
JMS
for
DeliveryTransport
and
a
value
of
JMS
for
ContainerManagedEvents.
Adapters
that
make
use
of
the
guaranteed
event
delivery
enable
this
tab.
See
the
descriptions
under
ContainerManagedEvents
in
the
Standard
Properties
appendix
for
values
to
use
for
these
properties.
Saving
your
configuration
file
After
you
have
created
the
configuration
file
and
set
its
properties,
you
need
to
deploy
it
to
the
correct
location
for
your
connector.
Save
the
configuration
in
an
ICL
project,
and
use
System
Manager
to
load
the
file
into
InterChange
Server
Express.
The
file
is
saved
as
an
XML
document.
You
can
save
the
XML
document
in
three
ways:
v
From
System
Manager,
as
a
file
with
a
*.con
extension
in
an
Integration
Component
Library,
or
Chapter
7.
Configuring
connectors
131