Configuring the Unified Broker framework in Windows
In Windows, you use OpenEdge Management or OpenEdge Explorer tool to configure the OpenEdge DataServer for Oracle in the Unified Broker framework. The Explorer has a default broker already defined, orabroker1.
To define and configure the OpenEdge DataServer for Oracle:
1. Make sure that the OpenEdge AdminServer is running.
2. Start the OpenEdge Management or OpenEdge Explorer.
3. Connect to the local/remote AdminServer.
4. From the left pane of OpenEdge Management or OpenEdge Explorer, select the Oracle DataServer folder and double-click. The list of existing DataServer brokers for Oracle appears in the right pane.
5. Select the DataServer instance whose properties you want to create or edit, and right-click. A pop-up menu appears.
Note: The OpenEdge DataServer for Oracle installation provides one predefined DataServer Broker (orabroker1) and one predefined NameServer (NS1). You can use these predefined components as a starting point for creating and configuring additional DataServer Brokers, and, if needed, NameServers. Each broker is referred to as an instance. Progress Software Corporation recommends using a NameServer configuration at all times. In such cases, the DataServer client's initial connection is to the NameServer. However, you can alternatively connect the DataServer directly to the broker instance by setting the -DataService value to none in the connection parameters of your schema holder or by adding the -DirectConnect parameter which will override your -DataService parameter. If you will always bypass the controlling NameServer, you should remove the controlling NameServer from your broker instance definition. See Starting the DataServer in the Unified Broker framework for more information about connecting the DataServer to the NameServer and the Broker.
6. Choose the Properties option from the pop-up menu. The Properties dialog box for that instance appears.
By default in the Property Editor Server category, the pathname of the DataServer executable that the broker runs is @{Startup\DLC\}bin\_orasrv.exe.
It is not recommended that you simultaneously run some DataServers for Oracle under brokers with controlling NameServers and others directly under brokers (that is, without controlling NameServers). This defeats the purpose of using a NameServer to control brokers. If you do this, the benefits of the NameServer are lost and load balancing is ineffective. Progress Software Corporation recommends that you always use a NameServer, with one exception: you can choose initially to connect directly to a broker to simplify confirming an initial connection. Once you establish a connection, Progress Software Corporation recommends that you reintroduce the NameServer into your configuration.
For more information on using OpenEdge Management or OpenEdge Explorer and details on the required settings, see the OpenEdge Management or OpenEdge Explorer online help.
