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

More documents

Recommendations

Info

Chapter 10: Configuration • Install the necessary product components — Typically, this involves installing, on one or more network machines, the OpenEdge Unified Broker product and additional software components that are required to use the product, such as OpenEdge client or Web server software. If you plan to configure fault-tolerant servers or use load balancing, you must install a product that includes load balancing, or install the load-balancing option for your product. For more information on the OpenEdge product installation, see Chapter 3, “OpenEdge Installation Prerequisites,” Chapter 4, “Performing an OpenEdge Installation in Windows,” or Chapter 5, “Performing an OpenEdge Installation on UNIX or Linux,” and the Windows- or UNIX-specific online help. For more information on distributing resources in a Unified Broker environment, see the “Working with Unified Brokers” section on page 281. Once you complete these preliminary tasks, you can configure and start up Unified Broker instances. How to configure and start up Unified Broker instances The procedure that follows presents the general steps required to configure and start up Unified Broker instances. Although much of this information has previously been presented in this chapter’s earlier sections, it is helpful to have a general outline of the configuration and startup activities. The properties file that comes installed with your Unified Broker product includes one sample Unified Broker and NameServer instance for each type of Unified Broker. You can use these as a guide. To configure and start up Unified Broker instances: 1. Start the AdminServer process on the machine on which each Unified Broker is installed: • In Windows, OpenEdge installs the AdminServer as a service that starts automatically at system boot time. • On UNIX, you can have the AdminServer started at system startup by editing your boot script to execute the PROADSV command. For information on starting the AdminServer, see the “Starting the AdminServer” section on page 286. 2. Create and/or modify Unified Broker configurations using any of the following options: • Mergeprop utility — A command-line utility you can use through the Proenv command-line interface to manage the contents of all properties files of which the ubroker.properties file pertains to the Unified Brokers discussed in this section. The utility supports functionality similar to POpenEdge Management or OpenEdge Explorer. For more information about the mergeprop utility, see the “Mergeprop utility overview” section on page 294. 284 OpenEdge Getting Started: Installation and Configuration
Working with Unified Brokers • OpenEdge Management or OpenEdge Explorer — This browser-based user interface can be used in a Windows or UNIX machine to access configurations installed on UNIX or in Windows machines. See the OpenEdge online help for details about using OpenEdge Management or OpenEdge Explorer to configure Unified Broker properties files. • Command-line utilities — A command-line tool for Windows and UNIX that allows you to control basic activities such as starting, stopping, and querying servers and validating property files associated with OpenEdge products. For more information about the command-line utilities, see Chapter C, “Command and Utility Reference.” Note: The properties file that comes installed with your Unified Broker product includes one sample Unified Broker and NameServer instance for each type of Unified Broker that you can use as a guide. If you plan to configure instances on a UNIX host, you must modify the properties file (ubroker.properties) directly on the host for each Unified Broker instance. Note: To perform most configuration and administrative tasks, use either the mergeprop utility or OpenEdge Management or OpenEdge Explorer because each offers more capabilities than does the command-line utility. 3. Using the OpenEdge Management or OpenEdge Explorer (or the management utility for your Unified Broker product), start up each Unified Broker instance. As it starts, each Unified Broker instance starts additional processes or accesses resources, depending on the product and its configuration. 4. A client can now make a Unified Broker connection request after you verify that it knows: • The correct network location of the NameServer to access • The Application Service name required to connect to the broker that the client needs At any time after this step, you can also use any of the appropriate management utilities (mergeprop, OpenEdge Management or OpenEdge Explorer, or command-line) to shut down or query the status of any running Unified Broker instance. 5. When you shut down an AdminServer process at any time and if you have not already shut the Unified Broker instance that it controls, the instance shuts down automatically when you shut down the AdminServer. During Unified Broker operation, in addition to checking NameServer and Unified Broker status using the OpenEdge Management or OpenEdge Explorer and utilities, you can also review log files being generated by the NameServer and Application Server instance. The properties file that comes installed with your Unified Broker product includes one sample Unified Broker and NameServer instance for each type of Unified Broker. This can be used as a guide. OpenEdge Getting Started: Installation and Configuration 285
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: Working with Unified Brokers For ge
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 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: Running OpenEdge clients and server
Page 333 and 334: -N network-type Specifies the netwo
Page 335 and 336:
Running OpenEdge clients and server
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:
Page 444 and 445:
Page 446 and 447:
Page 448 and 449:
Appendix C: Command and Utility Ref
Page 450 and 451:
Page 452 and 453:
Page 454 and 455:
Page 456 and 457:
Page 458 and 459:
Page 460 and 461:
Page 462 and 463:
Page 464 and 465:
Page 466 and 467:
Page 468 and 469:
Page 470 and 471:
Page 472 and 473:
Appendix D: OpenEdge National Langu
Page 474 and 475:
Page 476 and 477:
Page 478 and 479:
Page 480 and 481:
Page 482 and 483:
Page 484 and 485:
Page 486 and 487:
Page 488 and 489:
Appendix E: NameServer and NameServ
Page 490 and 491:
Page 492 and 493:
Page 494 and 495:
Page 496 and 497:
Page 498 and 499:
Page 500 and 501:
Page 502 and 503:
Page 504 and 505:
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 524 and 525:
Page 526 and 527:
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 ...

Create successful ePaper yourself

Delete template?

Save as template?