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.

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.

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 OpenEdge Management or OpenEdge Explorer. For more information about the mergeprop utility, see Mergeproputility overview.

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 Commandand 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.