Kbase 16723: How to start and stop an OID or an OIB under UNIX
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
10/05/1998 |
|
How to start and stop an OID or an OIB under UNIX
This document helps to use an OID or an OIB under UNIX operating
systems accessed from a distant machine by a product such as Intersolv
ODBC or an ESQL small client application.
For VMS, or NT look at the commands Prooidrv, Prooibrk and Proshut
in your "System administration guide", "System administration
reference", "Embedded SQL Guide and Reference", or your "ODBC driver
Guide" manuals.
1. Pre-requisite
-------------
Depending on the configuration you want to use, you will need to
start a server on your database.
- Client-server configurations:
You need to start a server on your database with networking
parameters specified.
proserve dbname -N TCP -S prosv01 (-H is optional)
- Self-service configuration:
You need to start a server on your database. There is no need for
networking parameters here.
proserve sports
- Single-user configuration:
There is no need of a server up and running on your database.
2. Starting/stopping an OID
------------------------
To establish a connection via a Remote OID to a Progress database (in
self-service mode or in client-server mode), we need first to have an
OID running.
2.1. Environment variables
---------------------
The OID needs some of the environment settings used by the sever.
Some of them are particularly needed by the OID. Those variables
are:
- DLC: This variable is used by the OID to check the Progress.cfg
- PATH: This variable has to contain the $DLC/bin directory, otherwise
the OID will not be started in the next part. (There should be a
script in that directory named 'prooidrv' that will be used to start
the OID.)
- PROOIDRV: You can also set this variable to $DLC/bin/_prooidv in
your UNIX environment or in the script used to start the OID. This
variable is not needed but it can be used to start the OID.
Consequently its setting is highly recomended. (at the UNIX prompt
type: set PROOIDRV=$DLC/bin/_prooidv; export PROOIDRV)
2.2. Command to start manually an OID
--------------------------------
Depending on the configuration you choosed you will have to start the
OID in different ways. But first you will have to start the server
according to your configuration.
- Client-server configuration:
You will have to start the OID with the following parameters.
prooidrv -db dbname -S prosv01 -H host-machine -N TCP
-SV -S prosv02 -N TCP -m2
- Self-Service configuration:
The OID needs to be started with the following parameters.
prooidrv -db dbname -SV -S prosv02 -N TCP -m2
- Single-user configuration:
The OID needs to be started with the following parameters.
prooidrv -db dbname -SV -S prosv02 -N TCP -m2
2.3. Command to stop the OID
-----------------------
Type the following at the UNIX prompt for any of the previous
configuration: proshut -SV -S prosv02
2.4. Note
----
If you establish a connection to an OID started manually and then
close the connection, you will not find your OID process anymore. It
automatically shuts down.
If you are not able to establish a connection to a remote OID, try
first a connection to your database via a Local OID.
3. Starting/stopping an OIB
------------------------
To establish a connection via a Remote OIB to a Progress database (in
self-service mode or in client-server mode), we first need to have an
OIB running.
3.1. Environment variables
---------------------
The OIB as well needs some of the environment settings used by the
server. Some of them are particularly needed by the OID. Those
variables are:
- DLC: This variable is used by the OIB to check the progress.cfg
- PATH: This variable has to contain the $DLC/bin directory, otherwise
the OIB will not start. (There should be a script in that directory
named 'prooibrk' that will be used to start the OIB.)
- PROOIDRV: This variable is used by the OIB to spawn the OID.
Consequently this variable is NEEDED and has to be set to
$DLC/bin/_prooidv and then exported. (at the UNIX prompt type:
set PROOIDRV=$DLC/bin/_prooidv; export PROOIDRV)
- PROOIBRK: You can also set this variable to $DLC/bin/_prooibk in
your UNIX environment or in the script used to start the OIB. This
variable is not needed but it can be used to start the OIB.
Consequently its setting is highly recomended. (at the UNIX prompt
type: PROOIBRK=$DLC/bin/_prooibk; export PROOIBRK)
3.2. Command to start an OIB
-----------------------
The command to start an OIB is the same regardless of the
configuration you are using. The function of the OIB is to spawn an
OID for you with the parameters you will pass to establish then a
database connection.
Thus, at UNIX prompt, you just have to type:
prooibrk -SV -S prosv02 -N tcp
3.3. Command to stop the OIB
-----------------------
Here as well, the command to stop the OIB is the same for any
configuration used to access one database with an OIB. at UNIX prompt,
type:
proshut -SV -S prosv02
4. Notes
-----
4.1. For the server
--------------
- The service used to connect to a remote server is prosv01. It is
defined in the services files stored on the UNIX machine where the
database is located, and the machine where the OID/OIB is running
(if those two machines are different).
4.2 For the OID/OIB
---------------
- The service used to connect to a remote OID/OIB is 'prosv02'. It is
defined in the services files stored on the UNIX machine where the
OID/OIB is running and the machine from which you will connect them.
- The host machine where the remote database is located is named
'host-machine' and has been defined in the host file stored on the
UNIX machine where the OID/OIB is running (this is needed only for
a client-server configuration).
- If you don't have the 'prooidrv' and the 'prooibrk' script located
in the $DLC/bin directory then you can set the environment variables
PROOIDRV and/or PROOIBRK and replace 'prooidrv' and 'prooibrk' in
the command lines used to start an OID/OIB by $PROOIDRV and
$PROOIBRK respectively. You can also replace 'prooidrv' and
'prooibrk' in the command lines by $DLC/bin/_prooidv and
$DLC/bin/_prooibk respectively.
IMPORTANT NOTE: An OID/OIB configured in client-server is ONLY
qualified to run on a Progress 7.3C UNIX database
server and above.
Sebastien HAEFELE
(5 mar 1997)
Progress Software Technical Support Note # 16723