Versions Compared

Old Version 2

changes.mady.by.user Kirstin Seidel-Gebert

Saved on

compared with

New Version Current

changes.mady.by.user Annegret Bernhardt

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Published by Scroll Versions from space WINSTALLATION and version 24.0
Div
Classe2e-refDiv

Otp
Floatingfalse
maxHLevel2

Rp
Note
titleFailover 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.

Panel
borderColor#EAA01E
bgColorwhite
borderWidth2
borderStylesolid

Linux:

  1. Log-in as a root user.

  2. 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 Block
    languagebash
    rpm -U oracle-instantclient-basic-10.2.0.3-1.i386.rpm

  3. Create the following link on the host:

    Code Block
    languagebash
    cd /usr/lib/oracle/10.2.0.3/client/lib 
ln -s libclntsh.so.10.1 libclntsh.so
  4. Multiexcerpt
    MultiExcerptNamelanguage_settings

    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

Multiexcerpt include
MultiExcerptNameDatabase Preferences
nopaneltrue
PageWithExcerptInstalling and Configuring Database Access for DB2

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

KeyValueExample
ORACLE_HOMEPath to the Oracle client.D:\Oracle\ora11g
NLS_LANGOracle language settings (Unix only)AMERICAN_AMERICA.AL32UTF8
TNS_ADMINPath to the Oracle configuration sqlnet.ora (optional)D:\Oracle\ora11g
Tip
iconfalse

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 StringDescription
AliasDBString - 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 Block
(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.

Panel
titleOn this Page:

Table of Contents

Panel
titleRelated Pages: