IBM BJ0NJML Integration Guide - Page 210

Enterprise Beans, HTTP Servlet, Integration Web Services, Enterprise Service through

Page 210 highlights

Inbound Message Receipt The noted components are standard J2EE components which are deployed as part of the application EAR file. All these components are cluster-aware. Enterprise Beans HTTP Servlet With a single server, the provider URL for accessing the JNDI tree is the single server URL. With a cluster, the provider URL is the URL of any one of the servers that has the enterprise beans deployed. All members of the cluster share the JNDI tree, so any member of the cluster can look for and retrieve a cluster. As a result of the cluster look up, the client retrieves a cluster-aware proxy of the enterprise beans, which load balances all the subsequent calls that use that proxy. Load balancing happens transparently to the client code. There is no difference between the code for a single server and for a cluster setup. A separate enterprise bean is deployed for the object structure service, enterprise service, and standard service. The integration servlet is deployed across all members of the cluster. With a single server, the URL is the HTTP and HTTPS URL of that server. With a cluster, the URL is the HTTP and HTTPS URL of the load balancer for the cluster. A separate servlet is deployed for each type of service: object structure, enterprise, and standard service. The URL formats for each service are shown in the following table. The meaweb value represents the mxe.int.webappurl system property value. You configure this system property value in the System Properties application. Service URL Object Structure Service http://hostname:port/meaweb/os/object structure name Enterprise Service (bypassing http://hostname:port/meaweb/es/extsysname/enterprise service name queue) Enterprise Service (through the queue) http://hostname:port/meaweb/esqueue/extsysname/enterprise service name Standard Service http://hostname:port/meaweb/ss/standard service name Integration Web Services Integration Web services are homogeneously deployed across all the server members in the cluster. Web service access for a cluster is the same as for a single server, except that the Web service URL and Web Service Definition Language (WSDL) URL point to the cluster instead of to a specific server in the cluster. 196 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

Inbound Message Receipt
196
Integration Guide
The noted components are standard J2EE components which are deployed as part
of the application EAR file. All these components are cluster-aware.
Enterprise Beans
With a single server, the provider URL for accessing the JNDI tree is the single
server URL. With
a cluster, the provider URL is the URL of any one of the servers
that has the enterprise beans deployed. All members of the cluster share the JNDI
tree, so any member of the cluster can look for and retrieve a cluster.
As a result of the cluster look up, the client retrieves a cluster-aware proxy of the
enterprise beans, which load balances all the subsequent calls that use that proxy.
Load balancing happens transparently to the client code. There is no difference
between the code for a single server and for a cluster setup. A separate enterprise
bean is deployed for the object structure service, enterprise service, and standard
service.
HTTP Servlet
The integration servlet is deployed across all members of the cluster. With a single
server, the URL is the HTTP and HTTPS URL of that server. With a cluster, the
URL is the HTTP and HTTPS URL of the load balancer for the cluster. A separate
servlet is deployed for each type of service: object structure, enterprise, and
standard service.
The URL formats for each service are shown in the following table. The meaweb
value represents the
mxe.int.webappurl
system property value. You configure
this system property value in the System Properties application.
Integration Web Services
Integration Web services are homogeneously deployed across all the server
members in the cluster. Web service access for a cluster is the same as for a single
server, except that the Web service URL and Web Service Definition Language
(WSDL) URL point to the cluster instead of to a specific server in the cluster.
Service
URL
Object Structure Service
http://
hostname:port
/meaweb/os/
object structure name
Enterprise Service (bypassing
queue)
http://
hostname:port
/meaweb/es/extsysname/
enterprise service name
Enterprise Service (through
the queue)
http://
hostname:port
/meaweb/esqueue/extsysname/
enterprise service name
Standard Service
http://
hostname:port
/meaweb/ss/
standard service name