Try OpenEdge Now
skip to main content
DataServer for Oracle
Connecting the DataServer : Starting the remote DataServer : Starting the DataServer in the Unified Broker framework : On the client
On the client
After you have started the broker on the host machine, you can connect your UNIX or Windows client. Use the same parameters that you would use for connecting to the schema holder and Oracle in a standard configuration. In addition:
*Include the -Dsrv SVUB,1 parameter. This parameter allows you to connect to the broker administered by the Explorer.
*Include the -DataServicedata-service parameter to connect through a NameServer to the broker. The value for data-service must specify a valid name from the DataService list registered to this NameServer as defined by your appServiceNameList entry in the broker properties file. If a default DataService has been defined for your broker instance, you can omit this parameter and connect using the default service.
For diagnostic purposes, it is acceptable to bypass the NameServer connection and connect directly to the broker instance. To do this, specify the reserved DataService name "none" or add the -DirectConnect parameter as follows:
-DataService none
*Set the -S parameter to one of the following:
*The port number assigned to the controlling NameServer (when the -DataService value is not "none") or the port number of the broker instance that you started in the Explorer (when the -DataService value is "none")
*The service name in your service file, \windows-install-dir\system32\drivers\etc\services in Windows or /etc/services on UNIX, whose associated port matches the port of the controlling NameServer (when the -DataService value is not "none") or the broker instance that you started in the Explorer (when the -DataService value is "none")
*Set the -H parameter to the name of the machine where the NameServer and/or broker instance is running.
If you do not set the required -Dsrv SVUB,1 and optional -DataService data-service connection parameters as described in this section, the client is assumed to be configured for a standard OpenEdge broker and the -H and -S parameters are used to locate a Probroker executable on the appropriate host machine. By setting the SVUB parameter on, you redirect the -H and -S parameters to locate the appropriate NameServer and/or broker on the host machine.
The following example illustrates how to use these connection parameters for a client that connects to a NameServer:
CONNECT oraholder -db orademo -dt ORACLE -U bob -P bobpass -H host1
-S oraservice -DataService orabroker1 -Dsrv SVUB,1