Kbase P37698: How to connect to a foriegn database if DataServer license is not installed on client?
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
24/09/2008 |
|
Status: Verified
GOAL:
How do I connect to foreign database if DataServer license is not installed on client?
GOAL:
What is a Remote DataServer Configuration?
FACT(s) (Environment):
DataServer
FIX:
If the DataServer license is not or can not be installed on the client machine, then this license will need to be installed elsewhere, on a separate machine. This type of configuration is called a Remote DataServer configuration. Here the client connects to the foreign database/datasource through the DataServer broker via -H, -S, -N.
Example of the Remote DataServer Configuration:
Host 1:
Client only license installed. Client will need to connect to the schema holder first and then the foreign image. Where the schema holder resides is not an issue. In this example, the schema holder is local to the client, however it can also be remote where client/server connection strings will need be used.
_progres/prowin32/_proapsv schema-holder -1 -db <schema_image> -dt <MSS/ODBC/ORACLE> -H host2 -N tcp -S broker-service
Host 2:
DataServer license installed. You must first start the DataServer broker in order to allow and accept remote client connections. There are several ways to start a a remote DataServer broker process on the host2 machine. For details, see one of the following sections with your DataServer Guide:
1. "Starting and Stopping a Broker Process with ProControl"
2. "Starting and Stopping a Broker Process from the Command Line"
Standard startup of the DataServer broker via the command line:
_probrkr -S broker-service -N tcp -H host2
Standard shutdown of the DataServer broker via the Command line:
proshut -Gw -S broker-service -N tcp -H host2
3. "Starting and Stopping a Broker Process from the Progress Explorer and Connecting a Client"
The DataServer broker will spawn a server process (_orarsv, _odbsrv, _msssrv) for each connection to connect to the foreign database/data source. Here you will need to define user logins/password for the foreign database/data source. All parameters can be passed from the client side. Location of the foreign database/data source can be anywhere as long as the foreign database's/data source's client can connect to it.
A complete client connection string:
_progres/prowin32/_proapsv schema-holder -1 -db <schema_image> -dt <MSS/ODBC/ORACLE> -H host2 -N tcp -S broker-service -U user -P password.
When using the Unified Broker, you must add the "-Dsrv svub,1" connection string to the client;
_progres/prowin32/_proapsv schema-holder -1 -db <schema_image> -dt <MSS/ODBC/ORACLE> -Dsrv svub,1 -H host2 -N tcp -S broker-service -U user -P password