Kbase P132: What Type of Connection is Possible from Client to Server when the Progress versions differ
Autor |
  Progress Software Corporation - Progress |
Acesso |
  Público |
Publicação |
  12/04/2011 |
|
Status: Verified
GOAL:
Can a 9.1E client connect a OpenEdge 10 database
GOAL:
Can a OpenEdge 10 database be connected by a Progress 9.1E
GOAL:
Can a OpenEdge 10 database be connected by a prior version of client
GOAL:
What Progress versions are compatible using a client/server connection?
GOAL:
Can Progress version 9.x client connect to version 9.x Database Server?
GOAL:
What Progress versions are compatible using a shared memory connection?
GOAL:
Can a higher version Progress client connect to a lower version Progress database?
GOAL:
Can a lower version Progress client connect to a higher version Progress database?
GOAL:
Is there backward compatibility between Progress versions?
GOAL:
Is Progress backwards compatible between releases?
GOAL:
Can a Progress 9.1E client connect to Progress 9.1D server?
GOAL:
Can a version 10 client connect to a version 9 database?
GOAL:
Can a minor version Client connect to a Major version of a database?
GOAL:
Can different versions between Client and Server connect to each other?
GOAL:
What are the database connectivity rules between different OpenEdge releases ?
FACT(s) (Environment):
All Supported Operating Systems
Progress/OpenEdge Versions
FIX:
A client may connect to a database in self-service mode using shared memory /only/ when the client's version exactly matches the database server's version.
Example:
Client is version 9.1E04
Server is version 9.1E04
If the Major and Minor release numbers are the same for the client and the database then the client can make a single user direct connect to the database (i.e. no server is running for the database) and a self-service connection to a running database (i.e the database has been started for multi-user access)
If the client and server have different version numbers (including any of: Major, Minor, Maintenance, and Patch) and a server is running on the database, then the client *must* connect client/server.
That is, the server must be started with the -S parameter and the client must use -H, -S and -N as part of its connect statement or connection parameters.
Example:
mpro <dbname> -H <hostname> -S <servicename> -N TCP
prowin32 <dbname> -H <hostname> -S <servicename> -N TCP
CONNECT -db <dbname> -ld <ldbname> -H <hostname> -S <servicename> -N TCP
Clients are able to connect to database servers using Client/Server within the same Major release and 1 Major release prior.
Example 1:
A version 9.1E client can connect client/server to:
Any version 9.1x database server (same major release)
Any version 9.0x database server (same major release)
Any version 8.3x database server (1 major release prior)
Example 2:
A version 9.0B client can connect client/server to:
Any version 9.1x database server (same major release)
Any version 9.0x database server (same major release)
Any version 8.3x database server (1 major release prior)
Example 3:
A version 10.1x or 10.2x client can connect client/server to:
Any version 10.2x database server (same major release)
Any version 10.1x database server (same major release)
Any version 10.0x database server (same major release)
Any version 9.1x database server (1 major release prior)
Example 4:
A version 10x client CANNOT connect to version 8 database server (2 major releases EARLIER).
A version 9.1x client CANNOT connect to an OpenEdge 10.x database server (1 major release LATER).
A version 8.3E client CANNOT connect to a version 9.x database server (1 major release LATER).