Progress
DataServer
for ORACLE Guide


Configuring the Explorer Administration Framework on UNIX

On UNIX, you configure the Progress Explorer administration framework by editing the $DLC/properties/ubroker.properties file. In this file, you provide configuration information for the AppServer, WebSpeed, and DataServers. For general information on how to work with the ubroker.properties file, see the Progress Installation and Configuration Guide Version 9 for Windows or the Progress Installation and Configuration Guide Version 9 for UNIX.

When you configure the DataServer for ORACLE, you are providing information that the Explorer administration framework can use to make sure that it is running the correct DataServer broker instance, and that the broker is spawning the appropriate DataServer process (_orasrv or a custom executable that you built with PROBUILD) and that it is running in the correct environment.

Table 3–6 describes the sections in the ubroker.properties file that apply to the DataServer for ORACLE. The file configures a default broker, orabroker1, which you can use as is or use as a template for your own configuration specifications.

Table 3–6: DataServer for ORACLE Sections 
Section
Description
[UBroker.OR]
Parent entity of DataServer for ORACLE brokers. It defines default property settings for all DataServer for ORACLE Broker instances.
[UBroker.OR.orabroker1]
Sample property entity of a DataServer for ORACLE Broker instance. It defines property settings for the DataServer for ORACLE Broker named orabroker1.
Note that although many of the settings in this section might work in your environment, some of the settings are for demonstration purposes only. You must specify the appropriate settings for:
srvrExecFile: Specify the pathname of DataServer executable you want to use. The default is $DLC/bin/_orasrv.
srvrStartupParam: Do not modify the parameters in this section. Note that the values assigned to the parameters are for the broker’s internal use only. For example, the values of the code-page parameters do not correspond to the values that your client connection might require. You can add startup parameters, however.
[Environment.orabroker1]
Environment settings that apply to the DataServer for ORACLE Broker named orabroker1. Be sure to set the variables to the appropriate values; the values in the file are for demonstration purposes only. ORACLE_HOME and ORACLE_SID are required. Add any environment variables that you want to apply to the DataServer’s environment to this section.

Here are the DataServer for ORACLE sections in the ubroker.properties file:

#  Default properties for broker instances serving Oracle DataServers
 # 
[UBroker.OR]
     operatingMode=State-aware
     classMain=com.progress.ubroker.broker.ubroker
     initialSrvrInstance=0
     minSrvrInstance=0
     maxSrvrInstance=256
     loggingLevel=3
     srvrStartupParam=
     description=Oracle DataServer Broker
 #
 # Sample Oracle DataServer Broker definition
 #
 [UBroker.OR.orabroker1]
     srvrExecFile=$DLC/bin/_orasrv
     srvrStartupParam=-svub -S orabroker1 -N TCP -U X -P X -hs 0 -s 40 
-cpinternal iso8859-1 -cpstream ibm850 -cpterm ibm850 -cpcase basic -cpcoll 
basic
     srvrLogFile=$WRKDIR/orabroker1.server.log
     brokerLogFile=$WRKDIR/orabroker1.broker.log
     portNumber=4445
     description=A sample Oracle DataServer Broker #
 #
 # Environment for Oracle DataServer Broker: orabroker1
 #
 [Environment.orabroker1]
     ORACLE_HOME=/usr/orant
     ORACLE_SID=ORCL 

For a complete description of the parameters included in each of these sections, see the comments in the $DLC/properties/ubroker.properties. Be sure to preserve the original $DLC/properties/ubroker.properties file. Work with a copy of the file. You must name the copy of the file ubroker.properties. After creating your own version of ubroker.properties, you can verify its settings by using the oraconfig utility. See "DataServer Command Line Utilities and Startup Parameters," for more information.

The ubroker.properties file is read on startup of the AdminServer process. For changes in any used environment variables to take effect, you must restart the AdminServer.

Configuring Multiple Brokers

You can configure multiple brokers by adding more [UBroker.OR.broker-name] and [Environment.broker-name] sections. Each broker instance must have a unique name. The brokers can share the properties that you define in the parent entity [UBroker.OR] section.

If you want to access multiple ORACLE databases, you must configure one broker per database and each broker must run in a separate directory and a distinct environment. For example, each broker must have a unique setting for ORACLE_SID.


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