In Windows, you can use the Progress Explorer tool to configure the DataServer for ODBC.
Note: This section describes how to access Progress Explorer to configure the DataServer for ODBC on Windows. It does not explain how to connect the DataServer. For connection instructions, see Starting and stopping a broker process from the Progress Explorer and connecting a client. For information about Progress Explorer, see the Progress Explorer online Help.
To access the Progress Explorer:
1. Make sure that the AdminServer is running.
2. Start Progress Explorer.
From the Windows Desktop choose StartProgramsOpenEdgeProgress Explorer Tool.
The Progress Explorer appears in the MMC framework.
3. Connect to localhost.
4. From the Progress Explorer's left pane, select the ODBC DataServer folder and double-click. The list of existing DataServer brokers for ODBC 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 DataServer for ODBC installation provides one predefined DataServer Broker (odbbroker1) and one predefined NameServer (NS1). Each broker is referred to as an instance. See the Progress Explorer online Help for more information. You can use these predefined components as a starting point for creating and configuring additional DataServer Brokers, and, if needed, NameServers. For information about the NameServer's role in a configuration, see OpenEdge Getting Started: Installation and Configuration.
6. Choose the Properties option from the pop-up menu. The Properties dialog box for that instance appears.
7. Configure the DataServer broker by setting general DataServer properties, owner information properties, application service properties, logging settings, environment variables, and others. For details on these settings, see the Progress Explorer online Help.
Note: By default, your DataServer for ODBC broker instances are defined with a controlling NameServer and are provided with a default Data Service. 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. For more information about connecting the DataServer to the NameServer and the broker, see Starting and stopping a broker process from the Progress Explorer and connecting a client.
It is not recommended that you simultaneously run some DataServers for ODBC 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 recommends that you reintroduce the NameServer into your configuration.
Once you have completely set up your environment, you can build the schema holder for your ODBC data source. For more information on creating a schema holder, see Creating a schema holder.
