Kbase 12622: building gateways
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
10/05/1998 |
|
building gateways
There are many configurations for running gateways. Some steps are
generic to all configurations. This Notebook Entry lists:
* The executables you need to build with PROBUILD to customize your
configuration set up.
* Some examples of startup options you need to execute to run the
gateway.
* Documentation you can reference when you work with gateway products.
___________________________________________
THE NECESSARY EXECUTABLES
* The Remote Gateway Broker
Choose 'Remote Gateway Broker' from the PROBUILD main menu's
list of options you can build. You need this executable to run
for those users who do not run on the machine that holds the
gateway files.
* The Remote Gateway Server (regarding the gateway you purchased;
for example, RMS)
The Gateway Broker spawns off this executable for a remote
client. This server accesses shared memory for the client.
Choose this option from the PROBUILD main menu if your system
has remote clients.
* PROGRESS 4GL, QUERY, or RUN-TIME with Gateway (may or may not be a
Remote Gateway)
You need to build this client executable to run with gateway
access. Choose PROGRESS 4GL, QUERY, or RUN-TIME from the
PROBUILD main menu. Then choose the gateway (for example, RMS)
from the next menu. If you are building a remote client, build
the remote version. If you are running from a DOS client, you do
not need PROBUILD. The _prowin and _ppgtwy files contain the
gateway configurable elements if purchased.
EXAMPLE STARTUP OPTIONS
When you set up your environment, include the following specific
gateway environment variables:
* PROBRKR - should point to the Remote Gateway Broker you build.
* RMSSRV - should point to the Remote Gateway Broker you build. RMS
is for the RMS Gateway. Each gateway's environment
variable is different. See the "Database Gateways Guide"
for more information.
* PROEXE - should point to the client executable you build to
configure with the gateway.
Follow these steps to start the exectables to run the gateway.
1) Start the Remote Gateway Broker on the machine that hosts the third
party database/files:
for UNIX or DOS -
probrkr -S servicename -H hostname -N network
for VMS -
PROGRESS/GATEWAY=START/HOST=/SERVICE=/NETWORK=
(NOTE: Do not specify a database name.)
2) This step is optional if you connect to the schema holder in
single-user or read-only mode.
Start the server for the schema holder:
for UNIX or DOS -
proserve schema -S servicename -H hostname -N network
for VMS -
PROGRESS/MULTI=START/HOST=/SERVICE=/NETWORK= schema
(NOTE: Schema is a database.)
DOCUMENTATION
* Database Gateways Guide - has a section for each gateway product
which:
- gives an overview of the gateway
- lists any differences between the gateway and PROGRESS
- contains a tutorial that shows you how to either set up the
gateway or reproduce a problem you have encountered.
- lists any features that are not available through the gateway
"Appendix A: Remote Database Gateway" is a good source for remote
configurations and set ups.
* 3GL Interface Guide - describes how to run PROBUILD to customize
executables for your gateway.
Progress Software Technical Support Note # 12622