IBM E02HMLL-I Implementation Guide - Page 119

Configuring, environment, variables, using, System, Manager, WebSphere, properties

Page 119 highlights

1. Click the Misc tab. 2. Do the following in the "Persistent Monitoring" pane: a. Select Continue in the Action on error drop-down menu if you want InterChange Server Express to continue running in the event of errors experienced by the persistent monitoring subsystem. Select Shutdown in the Action on error drop-down menu if you want InterChange Server Express to shut down in response to errors with the subsystem. b. Select the desired tracing level in the Persistent monitoring service drop-down menu to specify the tracing level for the subsystem. 3. For information on the interface elements in the "Flow Control" pane, see the System Administration Guide. 4. For information on the interface elements in the "Flow Monitoring" pane, see the System Administration Guide. 5. In the "Workflow Management" pane, type a number in the Business object consumer processor to indicate how many threads you want spawned to manage business objects participating in a long-lived business process. These threads deliver business objects from the collaboration runtime to the appropriate connector controllers when the business objects are retrieved from persistent storage to resume processing in a long-lived business process. For more information on long-lived business processes, see the Collaboration Development Guide. 6. For information on the "Server Memory" pane, see "Using the memory checker thread" on page 281. Configuring environment variables using System Manager At the "Environment Properties" tab, you can specify any Java user environment properties that might be required in the business integration system. Some environments may require such a variable to be specified; instead of adding them to the script that starts InterChange Server Express, you can add them to the configuration file by using the "Environment Properties" tab. Do the following to add a new environment property: 1. Click the Environment Properties tab. 2. Type the name for the property in the Property name field. 3. Type the value for the property in the Property value field. 4. Click Add Property. To delete a property, select the property and click Delete Property. To edit a property's value, select the property and edit the text in the Property value column for the property. Configuring WebSphere MQ properties using System Manager Do the following to configure the connectivity between InterChange Server Express and the WebSphere MQ persistent messaging software: 1. Click the WebSphere MQ tab. 2. Type the name of the computer on which the WebSphere MQ server is installed in the Host name field. 3. Type in the Port number field the port over which WebSphere MQ allows clients to communicate with the server. The default port is 1414. Chapter 5. Configuring InterChange Server Express 107

  • 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

1.
Click
the
Misc
tab.
2.
Do
the
following
in
the
“Persistent
Monitoring”
pane:
a.
Select
Continue
in
the
Action
on
error
drop-down
menu
if
you
want
InterChange
Server
Express
to
continue
running
in
the
event
of
errors
experienced
by
the
persistent
monitoring
subsystem.
Select
Shutdown
in
the
Action
on
error
drop-down
menu
if
you
want
InterChange
Server
Express
to
shut
down
in
response
to
errors
with
the
subsystem.
b.
Select
the
desired
tracing
level
in
the
Persistent
monitoring
service
drop-down
menu
to
specify
the
tracing
level
for
the
subsystem.
3.
For
information
on
the
interface
elements
in
the
“Flow
Control”
pane,
see
the
System
Administration
Guide
.
4.
For
information
on
the
interface
elements
in
the
“Flow
Monitoring”
pane,
see
the
System
Administration
Guide
.
5.
In
the
“Workflow
Management”
pane,
type
a
number
in
the
Business
object
consumer
processor
to
indicate
how
many
threads
you
want
spawned
to
manage
business
objects
participating
in
a
long-lived
business
process.
These
threads
deliver
business
objects
from
the
collaboration
runtime
to
the
appropriate
connector
controllers
when
the
business
objects
are
retrieved
from
persistent
storage
to
resume
processing
in
a
long-lived
business
process.
For
more
information
on
long-lived
business
processes,
see
the
Collaboration
Development
Guide
.
6.
For
information
on
the
“Server
Memory”
pane,
see
“Using
the
memory
checker
thread”
on
page
281.
Configuring
environment
variables
using
System
Manager
At
the
“Environment
Properties”
tab,
you
can
specify
any
Java
user
environment
properties
that
might
be
required
in
the
business
integration
system.
Some
environments
may
require
such
a
variable
to
be
specified;
instead
of
adding
them
to
the
script
that
starts
InterChange
Server
Express,
you
can
add
them
to
the
configuration
file
by
using
the
“Environment
Properties”
tab.
Do
the
following
to
add
a
new
environment
property:
1.
Click
the
Environment
Properties
tab.
2.
Type
the
name
for
the
property
in
the
Property
name
field.
3.
Type
the
value
for
the
property
in
the
Property
value
field.
4.
Click
Add
Property
.
To
delete
a
property,
select
the
property
and
click
Delete
Property
.
To
edit
a
property’s
value,
select
the
property
and
edit
the
text
in
the
Property
value
column
for
the
property.
Configuring
WebSphere
MQ
properties
using
System
Manager
Do
the
following
to
configure
the
connectivity
between
InterChange
Server
Express
and
the
WebSphere
MQ
persistent
messaging
software:
1.
Click
the
WebSphere
MQ
tab.
2.
Type
the
name
of
the
computer
on
which
the
WebSphere
MQ
server
is
installed
in
the
Host
name
field.
3.
Type
in
the
Port
number
field
the
port
over
which
WebSphere
MQ
allows
clients
to
communicate
with
the
server.
The
default
port
is
1414
.
Chapter
5.
Configuring
InterChange
Server
Express
107