OpenEdge Getting Started: Installation and Configuration - Product ...

More documents

Recommendations

Info

Appendix E: NameServer and NameServer Load Balancing Details Connection-level fault tolerance Connection-level fault tolerance enables a client (AppServer client, SonicMQ Adapter, WebSpeed Messenger, or DataServer client) to have its connection request satisfied by any NameServer from a set of related NameServers. You can configure NameServers for fault-tolerant operation using two different techniques, and you can use these techniques independently or together: • NameServer replication — Where you configure multiple NameServer instances within a single subnet on different machines to listen on the same UDP port. Clients send connection requests and Unified Brokers send registration requests to all NameServer instances using UDP broadcasting. Using UDP broadcasting, the registration information from brokers is replicated on each NameServer that is listening (hence NameServer replication). Similarly, each client connection request is sent to each of the replicated NameServers. • NameServer neighbors — Where you configure multiple NameServers on machines located in one or more subnets so that an initial NameServer instance receives the client connection request. If this initial NameServer cannot resolve the request, it passes the request on to a specified list of NameServer neighbors. These NameServer neighbors then attempt to resolve the connection request. Each NameServer neighbor represents the controlling NameServer for a separate Unified Broker instance. Using either or both techniques, a client can receive multiple responses from multiple NameServers. The client uses the first response that indicates that the requested Application Service was found. A client only receives a connection error if all NameServers that respond indicate that the Application Service cannot be found. In general, you can combine NameServer replication with NameServer neighbors to provide connection-level fault tolerance across an entire network. The sections that follow describe how to implement connection-level fault tolerance using these techniques. Using UDP broadcasting As described earlier, UDP is a connectionless protocol. This feature allows you to configure the following two types of communications with a NameServer: • Host request — The client or Unified Broker sends a message directly to a NameServer residing on a specific host and listening on a specific port. The IP address represents the actual network location of a specific host. Only the NameServer on the specified host and listening on the specified port receives the message. • Broadcast request — The client or Unified Broker sends a message specifying the UDP broadcast address of the NameServer host and the UDP port number on which the NameServer is listening. The UDP broadcast address represents the entire subnet where a host is located, and you can determine this address using the appropriate operating system commands from any host on the subnet. When a client or Unified Broker sends a UDP broadcast request, every NameServer on any host in the subnet that is listening on the specified port receives the message. 494 OpenEdge Getting Started: Installation and Configuration
Client Port >5162 Host >172.20.255.255 Understanding server-level and connection-level fault tolerance UDP broadcasting insulates the client and Unified Broker from having to know the exact host location of the NameServer. If there is some reason that you need to move the NameServer to a different machine in the same subnet, you can safely do it without having to change your client application or your Unified Broker configuration. Figure 10 shows a client and Unified Broker using UDP broadcasting to communicate with the NameServer. Using the UDP broadcast address, 172.20.255.255, this client and Unified Broker can communicate with a NameServer running on any host in the 172.20 subnet. Thus, you can use UDP broadcasting to support location transparency for a single NameServer. However, as Figure 10 implies, you can also use UDP broadcasting as the basis to support fault-tolerant NameServers using NameServer replication. NameServer [NameServer .NS1] location =local portNumber =5162 Host=172.20.0.7 Broadcast = 172 .20.255.255 Figure 10: NameServer replication Using NameServer replication NameServer [NameServer .NS1] location =local portNumber =5162 Host =172 .20.16.12 Broadcast = 172 .20.255.255 UDP broadcasting supports NameServer replication by allowing a client or Unified Broker request to be received by multiple NameServers listening on the same UDP port and configured on different machines within the same subnet. Because every host on a subnet receives every broadcast request, one or more of these hosts can support a NameServer that receives and handles the same messages. This provides fault tolerance for both a client connection request and a Unified Broker registration request. To configure and use replicated NameServers: Unified Broker [NameServer .NS1] location =remote portNumber =5162 hostName = 172 .20.255 .255 1. Run each NameServer instance on a separate host located within the same subnet. 2. Configure each NameServer instance to listen on the same UDP port. 3. Configure each client application to send its connection request and each Unified Broker to send its registration request using the subnet UDP broadcast address instead of the NameServer host address. There is one broadcast address for each subnet. Using this address and the specified UDP port number, a client or Unified Broker sends a single request that is recognized by every NameServer listening on that port in the subnet. OpenEdge Getting Started: Installation and Configuration 495
Page 1 and 2:
® ® PROGRESS® OPENEDGE® OpenEdg
Page 3 and 4:
Document Revision History Document
Page 5 and 6:
Contents Preface . . . . . . . . .
Page 7 and 8:
Contents Running the Progress Dynam
Page 9 and 10:
Contents AdminServer considerations
Page 11 and 12:
Contents Starting applications on a
Page 13 and 14:
Contents Character set, date, and n
Page 15 and 16:
Tables Contents Table 1: Windows sy
Page 17 and 18:
Contents Table 109: OpenEdge Develo
Page 19 and 20:
Preface This Preface contains the f
Page 21 and 22:
Chapter 4, “Performing an OpenEdg
Page 23 and 24:
Installation planning and performin
Page 25 and 26:
Preface Fixed-width bold Fixed-widt
Page 27 and 28:
Long syntax descriptions split acro
Page 29 and 30:
On UNIX platforms, use the OpenEdge
Page 31 and 32:
Preface normally appear. 4. The nam
Page 33 and 34:
Preface ACTION, ARISING OUT OF OR I
Page 35 and 36:
Preface PERFORMANCE OF THIS SOFTWAR
Page 37 and 38:
Preface ("SUN") AND ITS LICENSORS S
Page 39 and 40:
Preface advertising or otherwise to
Page 41:
Installation Chapter 1, Windows Ins
Page 44 and 45:
Chapter 1: Windows Installation Req
Page 46 and 47:
Page 48 and 49:
Page 50 and 51:
Page 52 and 53:
Page 54 and 55:
Page 56 and 57:
Page 58 and 59:
Page 60 and 61:
Page 62 and 63:
Chapter 2: UNIX Systems Installatio
Page 64 and 65:
Page 66 and 67:
Page 68 and 69:
Page 70 and 71:
Page 72 and 73:
Page 74 and 75:
Chapter 3: OpenEdge Installation Pr
Page 76 and 77:
Page 78 and 79:
Page 80 and 81:
Page 82 and 83:
Page 84 and 85:
Page 86 and 87:
Page 88 and 89:
Page 90 and 91:
Page 92 and 93:
Page 94 and 95:
Page 96 and 97:
Page 98 and 99:
Page 100 and 101:
Page 102 and 103:
Page 104 and 105:
Page 106 and 107:
Chapter 4: Performing an OpenEdge I
Page 108 and 109:
Page 110 and 111:
Page 112 and 113:
Page 114 and 115:
Page 116 and 117:
Page 118 and 119:
Page 120 and 121:
Page 122 and 123:
Page 124 and 125:
Page 126 and 127:
Page 128 and 129:
Page 130 and 131:
Page 132 and 133:
Page 134 and 135:
Page 136 and 137:
Page 138 and 139:
Page 140 and 141:
Page 142 and 143:
Page 144 and 145:
Page 146 and 147:
Page 148 and 149:
Page 150 and 151:
Page 152 and 153:
Page 154 and 155:
Page 156 and 157:
Page 158 and 159:
Page 160 and 161:
Page 162 and 163:
Page 164 and 165:
Page 166 and 167:
Page 168 and 169:
Page 170 and 171:
Page 172 and 173:
Page 174 and 175:
Page 176 and 177:
Page 178 and 179:
Page 180 and 181:
Page 182 and 183:
Page 184 and 185:
Page 186 and 187:
Page 188 and 189:
Page 190 and 191:
Chapter 6: Administration Utilities
Page 192 and 193:
Page 194 and 195:
Page 196 and 197:
Page 198 and 199:
Page 200 and 201:
Page 202 and 203:
Page 204 and 205:
Page 206 and 207:
Page 208 and 209:
Page 210 and 211:
Page 212 and 213:
Page 214 and 215:
Page 216 and 217:
Page 218 and 219:
Page 221 and 222:
Working in the OpenEdge Environment
Page 223 and 224:
JDKHOME Reviewing environment varia
Page 225 and 226:
Table 41 lists the supported enviro
Page 227 and 228:
PROCONV - The filename (or full pat
Page 229 and 230:
Setting OpenEdge Program Item prope
Page 231 and 232:
Getting started with the AdminServe
Page 233 and 234:
OpenEdge products supported by the
Page 235 and 236:
Running OpenEdge Running OpenEdge S
Page 237 and 238:
OpenEdge key and certificate stores
Page 239 and 240:
Table 43 shows the appropriate meth
Page 241 and 242:
Application development and deploym
Page 243 and 244:
Windows 64-bit For information on d
Page 245 and 246:
Working in the OpenEdge Environment
Page 247 and 248:
UNIX environment variables UNIX env
Page 249 and 250:
UNIX environment variables Table 44
Page 251 and 252:
UNIX environment variables Table 44
Page 253 and 254:
Setting SQL client environment vari
Page 255 and 256:
Getting started with the AdminServe
Page 257 and 258:
Understanding the built-in terminal
Page 259 and 260:
Understanding the built-in terminal
Page 261 and 262:
Managing OpenEdge Key and Certifica
Page 263 and 264:
Managing key stores for OpenEdge se
Page 265 and 266:
Managing key stores for OpenEdge se
Page 267 and 268:
Managing certificate stores for Ope
Page 269 and 270:
Managing certificate stores for Ope
Page 271 and 272:
Configuration 10 Once you have inst
Page 273 and 274:
Introducing OpenEdge Management and
Page 275 and 276:
Overview of OpenEdge Management or
Page 277 and 278:
Overview of OpenEdge Management or
Page 279 and 280:
AdminServer plugins.proper ties fil
Page 281 and 282:
Working with Unified Brokers Workin
Page 283 and 284:
Working with Unified Brokers For ge
Page 285 and 286:
Working with Unified Brokers • Op
Page 287 and 288:
Understanding and using the AdminSe
Page 289 and 290:
Understanding and using the AdminSe
Page 291 and 292:
Using OpenEdge Management or OpenEd
Page 293 and 294:
Saving configurations Using OpenEdg
Page 295 and 296:
Using the mergeprop utility Mergepr
Page 297 and 298:
Target file Mergeprop utility overv
Page 299 and 300:
Mergeprop utility overview • List
Page 301 and 302:
Mergeprop utility overview The foll
Page 303 and 304:
Mergeprop utility overview To execu
Page 305 and 306:
Property value formats Mergeprop ut
Page 307 and 308:
Ubroker.properties file and product
Page 309 and 310:
Ubroker.properties file structure U
Page 311 and 312:
Page 313 and 314:
Page 315 and 316:
Command-line utilities reference Co
Page 317 and 318:
Starting and Running OpenEdge 11 Th
Page 319 and 320:
Table 60: Windows GUI startup and s
Page 321 and 322:
Starting OpenEdge as a Windows serv
Page 323 and 324:
Starting the multi-user server or b
Page 325 and 326:
Starting OpenEdge on UNIX platforms
Page 327 and 328:
Starting OpenEdge on UNIX platforms
Page 329 and 330:
Running OpenEdge clients and server
Page 331 and 332:
Page 333 and 334:
-N network-type Specifies the netwo
Page 335 and 336:
Page 337:
OpenEdge Products and Components Pa
Page 340 and 341:
Chapter 12: OpenEdge Installation P
Page 342 and 343:
Page 344 and 345:
Page 346 and 347:
Page 348 and 349:
Page 350 and 351:
Page 352 and 353:
Page 354 and 355:
Page 356 and 357:
Page 358 and 359:
Page 360 and 361:
Page 362 and 363:
Page 364 and 365:
Page 366 and 367:
Page 368 and 369:
Page 370 and 371:
Page 372 and 373:
Page 374 and 375:
Page 376 and 377:
Page 378 and 379:
Page 380 and 381:
Page 382 and 383:
Page 384 and 385:
Page 386 and 387:
Page 388 and 389:
Page 390 and 391:
Page 392 and 393:
Page 394 and 395:
Page 396 and 397:
Page 398 and 399:
Page 400 and 401:
Page 402 and 403:
Page 404 and 405:
Page 406 and 407:
Page 408 and 409:
Page 410 and 411:
Page 412 and 413:
Page 414 and 415:
Page 416 and 417:
Page 418 and 419:
Page 420 and 421:
Page 422 and 423:
Page 424 and 425:
Page 426 and 427:
Page 428 and 429:
Page 430 and 431:
Appendix A: Preinstallation Checkli
Page 432 and 433:
Page 434 and 435:
Page 436 and 437:
Page 438 and 439:
Page 440 and 441:
Appendix B: Preinstallation Checkli
Page 442 and 443:
Appendix B: Preinstallation Checkli
Page 444 and 445: Appendix B: Preinstallation Checkli
Page 446 and 447: Appendix B: Preinstallation Checkli
Page 448 and 449: Appendix C: Command and Utility Ref
Page 472 and 473: Appendix D: OpenEdge National Langu
Page 488 and 489: Appendix E: NameServer and NameServ
Page 506 and 507: Appendix F: Configuration Models Sh
Page 508 and 509: Appendix F: Configuration Models Th
Page 510 and 511: Appendix F: Configuration Models No
Page 512 and 513: Appendix F: Configuration Models Cl
Page 514 and 515: Appendix F: Configuration Models Fi
Page 516 and 517: Appendix F: Configuration Models Fi
Page 518 and 519: Appendix F: Configuration Models Pr
Page 520 and 521: Appendix F: Configuration Models Co
Page 522 and 523: Appendix G: AdminServer Authorizati
Page 528 and 529: Index Arbitrary sum weight factors
Page 530 and 531: Index related to installation 209 E
Page 532 and 533: Index parameter server startup 330
Page 534 and 535: Index OpenEdge Adapter for Sonic ES
Page 536 and 537: Index accessing 75 Progress Dynamic
Page 538 and 539: Index 509 Single-user memory requir
Page 540: Index 381 Working directory defined
show all

OpenEdge Getting Started: Installation and Configuration - Product ...

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?