IBM BJ0NJML Integration Guide - Page 178

Creating and Configuring a Queue

Page 178 highlights

Creating and Configuring a Queue Creating and Configuring a Queue You can use separate queues, one for each external system that you use. Queues can be configured for use with publish channels and enterprise services that integrate with one or more external systems. Queue creation and configuration involves multiple steps. 1 Create and configure the message queue on the application server. 2 In the External Systems application, add properties to the queue. The following properties are available for each queue. Property Queue JNDI Name Queue Connection Factory Name Initial Context Factory Provider URL User ID Password Inbound Sequential Compress Maximum Try Count Description References the Java Naming and Directory Interface (JNDI) name that is configured on the application server. A default value is provided. References the Connection Factory name that is configured on the application server. A default value is provided. A value that you must configure when you do not to use the default queues and do not use a provided application server. A value that you must configure when you do not to use the default queues and do not use a provided application server. The user ID that you configure when the queue is secured on the application server. The password that is configured when the queue is secured in the application server for the user ID. Identifies whether the queue is used for inbound processing. If the inbound value is null, the system uses the queue for outbound processing. Identifies whether the queue is a sequential queue. If the sequential value is null, the system uses the queue for continuous queue processing. Identifies whether the messages are compressed when they are written to the queue and decompressed when they are pulled from the queue. Compression provides significantly reduced message sizes. The standard Java Inflater and Deflater APIs (java.util.zip) are used for compression. Identifies how many times the integration framework attempts to reprocess a message after it encounters an error. The system continues to retry the message until the count value is met. The value of this property must be set to zero when an error queue is implemented. You can create additional queues to meet system needs. If you do not use the default queues, use an application server provider for your queue configuration. Use the System and Enterprise Services tabs in the External Systems application. 164 Integration 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
  • 303
  • 304
  • 305
  • 306
  • 307
  • 308
  • 309
  • 310
  • 311
  • 312
  • 313
  • 314
  • 315
  • 316
  • 317
  • 318
  • 319
  • 320
  • 321
  • 322
  • 323
  • 324
  • 325
  • 326
  • 327
  • 328
  • 329
  • 330

Creating and Configuring a Queue
164
Integration Guide
Creating and Configuring a Queue
You can use separate queues, one for each external system that you use. Queues
can be configured for use with publish channels and enterprise services that
integrate with one or more external systems. Queue creation and configuration
involves multiple steps.
1
Create and configure the message queue on the application server.
2
In the External Systems application, add properties to the queue.
The following properties are available for each queue.
You can create additional queues to meet system needs. If you do not use the
default queues, use an application server provider for your queue
configuration.
Use the System and Enterprise Services tabs in the External Systems
application.
Property
Description
Queue JNDI Name
References the Java Naming and Directory Interface (JNDI) name that
is configured on the application server. A default value is provided.
Queue Connection Factory Name
References the Connection Factory name that is configured on the
application server. A default value is provided.
Initial Context Factory
A value that you must configure when you do not to use the default
queues and do not use a provided application server.
Provider URL
A value that you must configure when you do not to use the default
queues and do not use a provided application server.
User ID
The user ID that you configure when the queue is secured on the
application server.
Password
The password that is configured when the queue is secured in the
application server for the user ID.
Inbound
Identifies whether the queue is used for inbound processing. If the
inbound value is null, the system uses the queue for outbound
processing.
Sequential
Identifies whether the queue is a sequential queue. If the sequential
value is null, the system uses the queue for continuous queue
processing.
Compress
Identifies whether the messages are compressed when they are written
to the queue and decompressed when they are pulled from the queue.
Compression provides significantly reduced message sizes. The
standard Java Inflater and Deflater APIs (java.util.zip) are used for
compression.
Maximum Try Count
Identifies how many times the integration framework attempts to
reprocess a message after it encounters an error. The system continues
to retry the message until the count value is met. The value of this
property must be set to zero when an error queue is implemented.