Skip to main content
Skip table of contents

Installing and Configuring Database Access for Oracle

Failover Behavior

Oracle Transparent Application Failover (TAF) and Fast Connection Failover (FCF) are not supported. Instead, the Bridge uses an database independent replay mechanism for its Perstistent State persistency. This mechanism works only if TAF and FCF are switched off.

Installing the SQL Client Tools for Oracle

The Bridge supports Oracle since version 7.
Install the Oracle client tools and define the tnsnames.ora to open a successful connection to the database.

Linux:

  • Log-in as a root user.

  • Download the Oracle Instant Client Package - Basic, e.g. version 10.2.0.3. Note that you need a 64bit version when running a 64bit xUML RUNTIME. For OpenSUSE download the rpm package and start the installer:

    CODE
    rpm -U oracle-instantclient-basic-10.2.0.3-1.i386.rpm
  • Create the following link on the host:

CODE
cd /usr/lib/oracle/10.2.0.3/client/lib
ln -s libclntsh.so.10.1 libclntsh.so
  • To avoid encoding problems, such as special characters being messed up (e.g. the German umlauts), configure the language settings (NLS_LANG) in the Oracle database preferences for a Bridge installation on Unix (see further below, Defining the Oracle Database Preferences on the BRIDGE). Furthermore, in the UML model, set the tag charset="utf-8" on the database alias in the component diagram.

    Using that configuration the database client (Bridge) and the database server use the same encoding: strings in the xUML RUNTIME are Unicode, the database client uses Unicode (step 2) and Unicode is used between Oracle client and server (step 1). If native database storage is not Unicode, the Oracle server can convert the data.

Defining the Oracle Database Preferences on the Bridge

In a browser, open the Web-based user interface of the system, on which the Bridge is installed (see Checking the Installation). Enter a user id and password of a user with administration rights (the pre-defined user admin, for instance).
The welcome page is displayed.

In the Navigation, select the xUML Services item of the node instance you want to define the database preferences for and switch to tab Preferences:

Now, you can define the SQL adapter preferences for each database type. Select the DB2, Oracle, MySQL, or MSSQLServer Adapter in the drop down box and the parameters of the selected adapter are displayed.

Select the Oracle adapter, enter the following parameters and click Apply.

Key

Value

Example

ORACLE_HOME

Path to the Oracle client.

D:\Oracle\ora11g

NLS_LANG

Oracle language settings (Unix only)

AMERICAN_AMERICA.AL32UTF8

TNS_ADMIN

Path to the Oracle configuration sqlnet.ora (optional)

D:\Oracle\ora11g

If the path is already specified in the environment variables of your operating system, you do not have to set this parameter.

Overview on the Connection String Formats

Connection String

Description

Alias

DBString - the database name as it is specified in TNSNAMES.ORA file or looked up via Oracle LDAP.

Short Form

<server name>:<port>/<database or service name>

Long Form

The right hand side of tnsname.ora entries:

CODE
(DESCRIPTION =
	(ADDRESS_LIST =
		(ADDRESS = (PROTOCOL = TCP)(Host = <server name>)(Port = <port>))
	)
	(CONNECT_DATA =
		(SID = <service id>)
	)
)

It is also possible to configure the Oracle client as to use LDAP to access the connection information.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.