Release 10.1A: OpenEdge Getting Started:
Installation and Configuration

> ## Overview of Unified Broker administration

> There are two preliminary tasks you must complete before you can begin configuring and operating a Unified Broker product:

> - Configure all machines involved in product installation and operation — This depends on how you plan to distribute your product and its applications on a network. For more information on configuring OpenEdge products on a network, see Appendix F "Configuration Models."

> - Install the necessary product components — Typically, this involves installing, on one or more network machines, the OpenEdge Unified Broker product and whatever software components 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," either Chapter 4, "Performing an OpenEdge Installation in Windows," or Chapter 5, "Performing an OpenEdge Installation on UNIX," and the Windows- or UNIX-specific online help.

> For more information on the distributing resources in a Unified Broker environment, see the "Distributing machines for a Unified Broker product" section.

> Once you complete these preliminary tasks, you can configure and start up Unified Broker instances, as shown in Figure 11–2.

> Figure 11–2: OpenEdge Unified Broker administration overview

> | To configure and start up Unified Broker instances:

> 1. Start the AdminServer process on each Unified Broker and NameServer installation machine. 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 more information on starting the AdminServer, Windows users see Chapter 7, "Working in the OpenEdge Environment in Windows," and UNIX users see Chapter 8, " Working in the OpenEdge Environment on UNIX."

> 2. Once the AdminServer is running, use the Progress Explorer to create and modify NameServer and Unified Broker configurations. You can use the Progress Explorer locally in a Windows machine or remotely from any Windows machine to access configurations installed on UNIX or in Windows machines. You can also use a text editor to create these configurations directly in the `ubroker.properties` file that is local to the NameServer or Unified Broker product installation machine, whether or not the AdminServer is running.

> For more information on configuring NameServer and Unified Broker components, see the "Configuring OpenEdge Unified Broker components" section.

> 3. Using the Progress Explorer (or the `NSMAN` utility), start the NameServer that you have configured to coordinate client access to one or more Unified Broker instances. For more information, see the "Starting OpenEdge Unified Brokers" section.

> Note: Figure 11–2 shows the NameServer running on the Unified Broker installation machine. However, the NameServer can run on any network machine that is accessible to all of the clients and Unified Broker instances that it coordinates.

> 4. Using the Progress Explorer (or the management utility for your Unified Broker product), start up each Unified Broker instance coordinated by the NameServer that you started in Step 3. As it starts, each Unified Broker instance starts additional processes or accesses resources, depending on the product and its configuration.

> 5. After a Unified Broker starts up, it registers its network address and the Application Services it supports with the NameServer that you started in Step 3.

> 6. A client can now make a Unified Broker connection request after you ensure 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 Step 5, you can also use the Progress Explorer or the appropriate management utility to shut down or query the status of any running NameServer or Unified Broker instance.

> 7. You can shut down an AdminServer process at any time. If you have not already shut down the NameServer and 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 Progress Explorer and utilities, you can also review log files being generated by the NameServer and Application Server instance. For more information on working with these files, see the "Configuring OpenEdge Unified Broker log files" section.

Copyright © 2005 Progress Software Corporation www.progress.com Voice: (781) 280-4000 Fax: (781) 280-4095