IBM E02HMLL-I Implementation Guide - Page 30

Event, management, service, Connector, controllers, Repository, Database, connectivity, connection, - f my life

Page 30 highlights

Event management service The InterChange Server Express persistently stores every business object that it receives during the execution of a collaboration. This allows the InterChange Server Express to recover from an unexpected termination or from the failure of a collaboration without losing event notifications or calls. Connector controllers A connector controller is an interface between the client-side of a connector and the InterChange Server Express. A connector controller routes business objects as they traverse the IBM WebSphere Business Integration Server Express system, linking the client-side of connectors to collaborations and managing the mapping process. Through the connector controller, an administrator can: v Trace interactions between the InterChange Server Express and the connector agent. v Enable and disable interactions between the InterChange Server Express and the connector agent. v Specify the type of mapping to perform for each business object arriving from or departing to the connector agent. Repository The InterChange Server Express maintains configuration information and definitions of all objects in a persistent store called the InterChanger Server repository, which consists of a set of tables in a relational database. The tables store object definitions and configuration information in the form of XML documents. Database connectivity service The database connectivity service manages interactions between the InterChange Server Express and the repository. The database connectivity service interacts with the repository by means of the Java Database Connectivity API (JDBC). Database connection pools You can use the System Manager tool of the IBM WebSphere Business Integration Server Express system to define database connection pools in InterChange Server Express. User-defined database connection pools make it possible for developers to directly access relational databases from within a collaboration or map. This feature provides support for v Automated database connection life-cycle management v Simplified APIs for SQL statements and stored procedure execution v Container-managed transaction bracketing Transactional collaborations The IBM WebSphere Business Integration Server Express system supports services that can run a collaboration as if it were a type of transaction. Transactional qualities are desirable for collaborations where data consistency is important across applications. Like other transactions, a transactional collaboration involves a set of steps. If an error occurs, the InterChange Server Express can undo each completed step, performing a transaction-like rollback. 18 IBM WebSphere Business Integration Server Express and Express Plus: System Implementation Guide

  • 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

Event
management
service
The
InterChange
Server
Express
persistently
stores
every
business
object
that
it
receives
during
the
execution
of
a
collaboration.
This
allows
the
InterChange
Server
Express
to
recover
from
an
unexpected
termination
or
from
the
failure
of
a
collaboration
without
losing
event
notifications
or
calls.
Connector
controllers
A
connector
controller
is
an
interface
between
the
client-side
of
a
connector
and
the
InterChange
Server
Express.
A
connector
controller
routes
business
objects
as
they
traverse
the
IBM
WebSphere
Business
Integration
Server
Express
system,
linking
the
client-side
of
connectors
to
collaborations
and
managing
the
mapping
process.
Through
the
connector
controller,
an
administrator
can:
v
Trace
interactions
between
the
InterChange
Server
Express
and
the
connector
agent.
v
Enable
and
disable
interactions
between
the
InterChange
Server
Express
and
the
connector
agent.
v
Specify
the
type
of
mapping
to
perform
for
each
business
object
arriving
from
or
departing
to
the
connector
agent.
Repository
The
InterChange
Server
Express
maintains
configuration
information
and
definitions
of
all
objects
in
a
persistent
store
called
the
InterChanger
Server
repository
,
which
consists
of
a
set
of
tables
in
a
relational
database.
The
tables
store
object
definitions
and
configuration
information
in
the
form
of
XML
documents.
Database
connectivity
service
The
database
connectivity
service
manages
interactions
between
the
InterChange
Server
Express
and
the
repository.
The
database
connectivity
service
interacts
with
the
repository
by
means
of
the
Java
Database
Connectivity
API
(JDBC).
Database
connection
pools
You
can
use
the
System
Manager
tool
of
the
IBM
WebSphere
Business
Integration
Server
Express
system
to
define
database
connection
pools
in
InterChange
Server
Express.
User-defined
database
connection
pools
make
it
possible
for
developers
to
directly
access
relational
databases
from
within
a
collaboration
or
map.
This
feature
provides
support
for
v
Automated
database
connection
life-cycle
management
v
Simplified
APIs
for
SQL
statements
and
stored
procedure
execution
v
Container-managed
transaction
bracketing
Transactional
collaborations
The
IBM
WebSphere
Business
Integration
Server
Express
system
supports
services
that
can
run
a
collaboration
as
if
it
were
a
type
of
transaction
.
Transactional
qualities
are
desirable
for
collaborations
where
data
consistency
is
important
across
applications.
Like
other
transactions,
a
transactional
collaboration
involves
a
set
of
steps.
If
an
error
occurs,
the
InterChange
Server
Express
can
undo
each
completed
step,
performing
a
transaction-like
rollback.
18
IBM
WebSphere
Business
Integration
Server
Express
and
Express
Plus:
System
Implementation
Guide