This section describes all steps required to run a service that connects to databases:

• Installing SQL client tools
• Defining the SQL adapter preferences
• Defining database parameters

When installing the E2E Bridge, all additional libraries (E2E SQL Libraries, E2E SAP Libraries, and E2E Java Libraries) are being installed as well.
After a successful installation, the Bridge is capable to connect to database backends.

First, you need to install the client tools or the ODBC drivers and configure each database access if needed.
Databases like DB2 or Oracle are usually running on a dedicated database server. The Bridge opens a connection to the database server via the database client tools or ODBC.

Preconditions

The E2E Bridge has been successfully installed. When running the Bridge in server mode (as opposed to workstation mode), the E2E Bridge node instance has to be a member of an E2E Bridge domain. For more information on installation modes and E2E Bridge domains, refer to Installation Modes and Bridge Domain.

Database Client Library Versions (32 or 64 bit)

The database client library must have the same number of bits as the E2E xUML Runtime.

For ODBC configuration, you have to consider the following, if using a Windows 64-bit system:

For Windows 32-bit, always use Control Panel > Administrative Tools > Set up data sources (ODBC).

Installing Database Access

• To install database access to a DB2 database refer to Installing and Configuring Database Access for DB2.
• To install database access to an Oracle database refer to Installing and Configuring Database Access for Oracle.
• To install database access to a MySQL database refer to Installing and Configuring Database Access for MySQL.

If you want to access the installed database via the xUML Runtime that is embedded in E2E Builder, please note that you have to make the database client available to the Builder:

• Install a database client to the system you are running the Builder on.
• Make sure that the database client location makes part of the PATH variable.
  After having changed PATH, you need to restart MagicDraw to make it read the new content of PATH.

Defining the ODBC Database Parameters

All well-known databases like Oracle, DB2, Inter Base, Firebird, dBase, Access, FoxPro, Paradox, SQL Server, and so on can be connected via ODBC.
Install the required ODBC drivers and define the parameters for each connection.

Before starting a deployed xUML service that connects to a database backend, you may want to redefine required database parameters in the Bridge.
You find more information about database-specific information (database names and mappings) in section Database-Specific Mappings.

Select the xUML service in the navigation (in this example CustomerQuery and stop the service.

Switch to tab Settings. From the dropdown list, select the option SQL Adapter Connection in the Add-ons category.

The default parameters are defined in the component diagram of the xUML service (see CustomerQuery example below). The connection is defined by a dependency between the composite named CustomerQuery and the SQL alias customers. The database user and password are defined in the tagged value user on the SQL alias.

Enter the following database parameters and click Apply:

Key	Value
customers: DBType	Name of the SQL Service component e.g. ODBC
customers: DBName	Name of the database, e.g. NorthwindCustomers
customers:Connection Pooling
customers:Max Connection Reuse
customers: Max Connection Age
customers: Max Connection Idle Time

Now, select SQL Adapter Authorization from the list.

Enter the following database parameters and click Apply:

For more details on changing the settings refer to xUML Service Settings.