SUMMARY:
This provides a checklist to insure that your ORACLE product will run properly with WebSpeed 1.0.
SOLUTION:
1) Make sure all necessary ORACLE software is installed, an
ORACLE database is up and running, and any networking
required (including ORACLE, SQL*NET) is functional. Be
sure to check all versions for compatibility with PROGRESS.
2) Get the ORACLE DBA to set the OPEN_CURSORS parameter to
250 or more in the init.ora parameter file. This file
is equivalent to PROGRESS startup.pf file. The ORACLE
database will need to be shut down and restarted after
this parameter has been changed.
3) Make sure you have a DBA account on the ORACLE database
that is not system or sys, and has access to all the ORACLE
tables you will be needing. If you are converting an existing PROGRESS database to ORACLE, you will need to refer to the DataServer Guide for instructions on how to do this.
4) If you are running under UNIX, make sure you have an OS
account running the Bourne shell that can "su" to the
user root, and get the system administrator, as you will be needing the root password to build the DataServer executable.
5) Install the PROGRESS DataServer for ORACLE software
anywhere you like. (For the rest of this document, this
DataServer directory will be referred to as /u/dlc.)
6) Install the WebSpeed 1.x software into a different directory
from the one you used in step 5. (For the rest of this document the WebSpeed directory will be referred to as /u/wsrt.)
7) WebSpeed needs to know that there is a DataServer out
there so it can build an executable accordingly. It
does not know it by default, so the configuration file
progress.cfg needs to be copied from /u/dlc to /u/wsrt.
8) Move to /u/wsrt/probuild/eucapp and run the buildenv
script. This sets all the environmental variables
necessary to PROBUILD the new executables. Make sure
you run it from the OS prompt as the ". buildenv"
command because PROGRESS needs the environmental variables
in other shells.
9) Check to see that the $ORALIB environmental variable has
a long character value. This variable points to the
ORACLE libraries that PROGRESS will be linking to.
There should be a "-L" string somewhere near the
beginning of this value.
10) Run the PROBUILD script from /u/wsrt/probuild/eucapp.
(We have found that by running this script with ". probuild"
it seems to iron out a few problems with different environments.) The type of executables you need to build will vary depending
upon your configuration. Refer to Section 3.1 -- DataServer
Modules in the PROGRESS DataServer for ORACLE Guide to
determine which executables, if any, you need to build.
11) Once you have built the link script, run it from the
operating system. When prompted for a password, enter
in the root user's password. This is needed to set the
correct permissions.
12) In your wtb.cnf file replace the _wta executable
reference with the name of the executable you just
built. If you can get into Data Administration module
with the executable, skip to step 17.
13) Unset any value of $DLC. Move to /u/dlc/probuild/eucapp
and run buildenv (again, using the ". buildenv" syntax.)
14) Once you have established that the $ORALIB variable
exists, run PROBUILD from this direactory (again,
building the PROGRESS client as per step 10.)
15) Run the link script and supply the root password when prompted. You no longer need the system administrator after this.
16) Make sure the $PROEXE environment variable points to
this new executable.
17) Using whichever executable works, get into the Data
Administration module and create, then connect to, a
database that is a copy of the EMPTY database. This
will be your schema holder.
18) Under the DataServers menu option, choose ORACLE Utilities,
and then Create DataServer Schema. When prompted, enter
anything you like as the logical database name (as long as
it is not the same as the schema holder name) and supply
the -U <username> and -P password> for the ORACLE user
mentioned in step 3. Then hit OK.
19) After a brief processing delay, you will be prompted for the username and password again. Since you have already entered
them in the first screen, you can click on OK without supplying any information. (Do not hit Cancel, as this will throw you out
of the process altogether!) You will then be presented with a
dialog box asking for criteria to select which ORACLE
objects to map into the schema holder. Here you enter "Table"
in the Object type field, and you may want to add an Object
Owner (ORACLE Username) to limit the search even further.
20) After a short processing time, it then presents to you a
list of all the ORACLE objects it found satisfying your
criteria. Select the objects you want mapped into
PROGRESS by moving through the list and hitting the
space bar to select them. Once you have all your
objects chosen, hit OK to process them.
21) This will shortly complete and control will be returned to
the Data Administration menu. Exit out of this module.
22) In your wtb.cnf file (in your WebSpeed working
directory), in the Agent Parameters section, modify your
database connection parameters to look like this:
-db <schema> -db <ora> -U <username> -P <password> -dt
ORACLE where
<schema> = the name of your schema holder from step 17,
<ora> - the logical name you used in step 18,
<username> = the ORACLE username from step 3, and
<password> = the ORACLE password from step 3.
You should now be able to start WebSpeed agents that can connect to your local ORACLE database.
References to Written Documentation:
PROGRESS DataServer for ORACLE Guide, Section 3.1 -- DataServer Modules.