Setting up database connection
=======================

The same utility is invoked to: create, modify, test, delete and re-order collective 
and non-collective database connections. Collective connection modification is 
in the hands of BODC's IT group and is normally only effected at times of 
password change. Here we are concerned with non-collective (personal) connections 
to databases; these connections are required for Edteva functions. 

On Windows there is an icon at m:\sitewide\bodc\edserplo\DBConnections

Drag it to your desktop.

On Linux the command is: dbconnections.

Invoking the utility fires up a GUI to allow the user to effect the changes mentioned above. 

A word about 'ordering'. You can ignore it for the time being but Edserplo will, in 
certain situations, try connections to diffferent DBMS in the order displayed for a given 
connection name.  If it fails with the first it will go on to the next.

Storage of non-collective connections on Windows
----------------------------------------------------------------------
DatabaseConns.inf holds the information in encrypted form in a directory called .EDSERPLO 
which is set up under c:\Documents and Settings\<userLogonId>. 
The directories will be created as needed.

On Linux/Unix
--------------------
DabaseConns.inf holds the information in encrypted form in the ~/.EDSERPLO directory.

Conventions
-----------------
In setting up the connection one should make the connection name the same as the database ID 
(case will be ignored). The connection which is to be used has to be in the .oracle.edteva 
file where it is identified as the first word. The password now becomes redundant. 
The .oracle.edteva file is to be placed in c:\Documents and Settings\<userLogonId> on Windows 
and on Linux/Unix placed at  ~ or in the current directory (which overrides the former).

Thus there may be many connections available to use but .edteva.oracle nominates the one 
you want. This may not be of significance to most users but it is extremely useful for 
software developers.

Creating .edteva.oracle
-----------------------
Creating the named file from scratch is a problem on Windows. I suggest copying it from 
Linux.

Creating a new entry
------------------------------
To use the standard Oracle server - BIDBASE - you put in, for the location, 

@bidsbase:1521:bia

Once having entered the password (twice) you can test the connection.

Editing an existing Entry
-------------------------
Click on the entry of interest. It can then be edited.

Edserplo usage
--------------
You may discover that things are not working when you invoke Edserplo. With 
the Edserplo session still going check that your .edteva.oracle file is OK and  if 
that's alright make sure the name matches the one in DatabaseConns.inf. 
Check the connection is OK too by testing. 

SGL (2008/05/30)