Kbase P56382: How to connect to a remote DataServer schema holder?
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
24/04/2009 |
|
Status: Verified
GOAL:
How to connect to a remote DataServer schema holder?
GOAL:
How to connect to a schema holder that resides in UNIX from a windows client?
GOAL:
How to connect to a schema holder that resides in Windows from an UNIX client?
FACT(s) (Environment):
DataServers
Progress 9.1x
OpenEdge 10.x
All Supported Operating Systems
FIX:
There are 2 ways that a remote schema holder can be connected:
1) using -RO parameter in the schema holder connection (not in the third part connection)
2) via remote Progress Server
In order to connect it via -RO the client must be able to give the path (UNC, mapped drive or any file service, eg: samba) to the location of the schema holder. Once this location is available by adding -RO to the connection parameters to the client it allows multiple connections to the same schema holder without a server process to manage the connections.
The following are examples of connections to remote schema's holder:
%DLC%\bin\prowin32.exe -db x:\HRApp\ShHR -RO
pro -db /db/webapp/shsports -RO
In order to connect via remote Progress Server, the schema holder needs to be run as a server which is similar to a progress Database running as a client/server mode.
Note that, in the machine where the schema holder is located, you need to have either workgroup or enterprise database license depending de number of clients that are going to be connected.
This are the steps to connect a remote schema holder via remote Progress Server:
1. proserve <schema holder name> -H <host name or IP address> -S <service name> -N tcp
2. Connect from a remote client
2a. Use the following from a remote client (Character or UNIX):
_progres <Schema holder name> -H <same value used in the step 1> -S < same value used in the step 1> -N tcp
OR
mpro <Schema holder name> -H <same value used in the step 1> -S <same value used in the step 1> -N tcp
2b. Use the following from a GUI client (Windows platform)
%DLC%\bin\prowin32.exe <Schema holder name> -H <same value used in the step 1> -S <same value used in the step 1> -N tcp