The access to OBEROn database can be realized in different ways:

A - desktop client directly linked to the database
B - desktop client linked to an OBEROn RMI server
C - desktop client linked to an HTTP application server
D - 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.
E - mobile client linked to an HTTP application 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 you 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/client folder.


B - If the desktop client access OBEROn throw the OBEROn RMI server you 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.

You can find an example for the oberon.ini (RMI configuration) into the /etc/samples/client folder.


In addition to the client configuration you 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 you 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. Each database connection is associated to an RMI channel.
If you start up multiple RMI servers, the total number of database/RMI connections is given by the sum of the connections for each server.

You can find examples for the oberonRMI.ini into the /etc/samples/rmi_server folder.

C - If the desktop client access OBEROn throw the HTTP application server you need to set the HTTP URL in the configuration file (oberon.ini )

Notes:
- serverURL is valid for both the webservice publication and for all other OBEROn functionalities.
- if uid and pwd are not defined they will be asked during the OBEROn login.

You can find an example for the oberon.ini (HTTP configuration) into the /etc/samples/client folder.

D - 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.

(*) An HTTP server can also connect to another HTTP server setting in the oberon.properties the conntype=HTTP and the serverURL instead of the RMI registrry.

You can find examples for the oberon.properties into the /etc/samples/http_server folder.

E - Android applications haven't configuration files, but the HTTP connection parameters are defined in the application Preferences. It is convenient to define the main Activity as OnSharedPreferenceChangeListener implementation, so, when the user changes the parameter values, a new connection attempt is performed to check their validity.

To define the layout of preference panel you need to add an xml file in the resource folder ( for example: ./res/xml/preferece_layout.xml )

<PreferenceScreen xmlns:android="http://schemas.android.com/apk/res/android">

<PreferenceCategoryandroid:title="@string/CONNECTION_preferences">

<EditTextPreference
android:key="CONNECTION.serverURL"
android:title="@string/title_serverURL_preference"
android:summary="@string/summary_serverURL_preference"
android:dialogTitle="@string/title_serverURL_preference"
android:defaultValue="http://localhost:8080/oberon" />

<EditTextPreference
android:key="CONNECTION.application"
android:title="@string/title_application_preference"
android:summary="@string/summary_application_preference"
android:dialogTitle="@string/title_application_preference"
android:defaultValue="Application" />

<EditTextPreference
android:key="CONNECTION.uid"
android:title="@string/title_uid_preference"
android:summary="@string/summary_uid_preference"
android:dialogTitle="@string/title_uid_preference"
android:defaultValue="" />

<EditTextPreference
android:key="CONNECTION.pwd"
android:title="@string/title_pwd_preference"
android:summary="@string/summary_pwd_preference"
android:dialogTitle="@string/title_pwd_preference"
android:defaultValue="" />

<EditTextPreference
android:key="CONNECTION.connections"
android:title="@string/title_connections_preference"
android:summary="@string/summary_connections_preference"
android:dialogTitle="@string/title_connections_preference"
android:numeric="integer"
android:maxLength="2"
android:defaultValue="3"/>

</PreferenceCategory>

</PreferenceScreen>