01.06.2013 Views

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

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

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

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Working with Unified Brokers<br />

• <strong>OpenEdge</strong> Management or <strong>OpenEdge</strong> Explorer — This browser-based<br />

user interface can be used in a Windows or UNIX machine to access<br />

configurations installed on UNIX or in Windows machines. See the<br />

<strong>OpenEdge</strong> online help for details about using <strong>OpenEdge</strong> Management or<br />

<strong>OpenEdge</strong> Explorer to configure Unified Broker properties files.<br />

• Comm<strong>and</strong>-line utilities — A comm<strong>and</strong>-line tool for Windows <strong>and</strong> UNIX that<br />

allows you to control basic activities such as starting, stopping, <strong>and</strong> querying<br />

servers <strong>and</strong> validating property files associated with <strong>OpenEdge</strong> products. For<br />

more information about the comm<strong>and</strong>-line utilities, see Chapter C,<br />

“Comm<strong>and</strong> <strong>and</strong> Utility Reference.”<br />

Note: The properties file that comes installed with your Unified Broker<br />

product includes one sample Unified Broker <strong>and</strong> NameServer<br />

instance for each type of Unified Broker that you can use as a guide.<br />

If you plan to configure instances on a UNIX host, you must modify the properties<br />

file (ubroker.properties) directly on the host for each Unified Broker instance.<br />

Note: To perform most configuration <strong>and</strong> administrative tasks, use either the<br />

mergeprop utility or <strong>OpenEdge</strong> Management or <strong>OpenEdge</strong> Explorer<br />

because each offers more capabilities than does the comm<strong>and</strong>-line<br />

utility.<br />

3. Using the <strong>OpenEdge</strong> Management or <strong>OpenEdge</strong> Explorer (or the management<br />

utility for your Unified Broker product), start up each Unified Broker instance. As it<br />

starts, each Unified Broker instance starts additional processes or accesses<br />

resources, depending on the product <strong>and</strong> its configuration.<br />

4. A client can now make a Unified Broker connection request after you verify that it<br />

knows:<br />

• The correct network location of the NameServer to access<br />

• The Application Service name required to connect to the broker that the client<br />

needs<br />

At any time after this step, you can also use any of the appropriate management<br />

utilities (mergeprop, <strong>OpenEdge</strong> Management or <strong>OpenEdge</strong> Explorer, or<br />

comm<strong>and</strong>-line) to shut down or query the status of any running Unified Broker<br />

instance.<br />

5. When you shut down an AdminServer process at any time <strong>and</strong> if you have not<br />

already shut the Unified Broker instance that it controls, the instance shuts down<br />

automatically when you shut down the AdminServer.<br />

During Unified Broker operation, in addition to checking NameServer <strong>and</strong> Unified<br />

Broker status using the <strong>OpenEdge</strong> Management or <strong>OpenEdge</strong> Explorer <strong>and</strong> utilities,<br />

you can also review log files being generated by the NameServer <strong>and</strong> Application<br />

Server instance.<br />

The properties file that comes installed with your Unified Broker product includes one<br />

sample Unified Broker <strong>and</strong> NameServer instance for each type of Unified Broker. This<br />

can be used as a guide.<br />

<strong>OpenEdge</strong> <strong>Getting</strong> <strong>Started</strong>: <strong>Installation</strong> <strong>and</strong> <strong>Configuration</strong> 285

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!