The access to Oberon can be realized in three ways:

A - using a desktop client directly linked to the database
B - using a desktop client linked to an Oberon RMI server
C - using a browser with a HTTP(s)/SOAP connection to an application server. In this case, the application server can access to Oberon directly or throw the Oberon RMI server.

The desktop client (or web client), the Oberon RMI server, the Application Server and the database may be physically located on different machines.

A - When a desktop client is directly connected to the database we must declare in the configuration file (oberon.ini ) all connection parameters:

Notes:
- server/port and database are not required for the Oracle OCI connection as they are specified in the tnsnames.ora file and identified with the Oracle SID.
- if uid and pwd are not defined they will be asked during the Oberon login.
- the dbuser is not required when the Oberon connects to database with default user name
- the dbpwd is not required when the database user has the default password

You can find examples for the oberon.ini configuration into the /etc/samples folder.


B - If the desktop client access Oberon throw the Oberon RMI server we need to set the RMI service URL in the configuration file (oberon.ini )

Notes:
- registry can contain multiple URLs; this allows the client to connect to multiple Oberon RMI server instances on different servers and/or ports.
- if uid and pwd are not defined they will be asked during the Oberon login.

In addition to the client configuration we must set the Oberon RMI server parameters in the oberonRMI.ini

This file is subdivided in two part: the connection section and the driver list section. In the first part we must define the driver parameter selecting one of the driver name form the driver list section. Each driver section contains the connection parameters to different database type.
When the Oberon RMI server starts, it opens multiple database connections, this number is fixed with the connection parameters. If we start up multiple RMI servers, the total number of database connections is given by the sum of the connections for each server.

C - The usual access to Oberon is done by a web-browser, in this case the configuration file to edit is located on the application server, its name is : WEB-INF/classes/oberon.properties

When the application server accesses to Oberon indirectly via the Oberon RMI server(s), the oberon.properties must contains the RMI server URL(s):

and each RMI server must be properly configured editing the relative oberonRMI.ini file.