Overview

Within the web folder you will find the file "web.config" - this is a XML file containing a number of settings which configure settings for the Enterprise Tester application, including what type of database to connect to and its connection string details.

By default this file is located: 

c:\Program Files\Catch Limited\Enterprise Tester\Web\web.config

Open the file using notepad, within it you will need to change 4 settings:

  • "migration.providerName"
  • Default connection string
  • connection.driver_class
  • dialect

These are the default settings:

"migration.providerName"

<appSettings>
          <add key="migration.providerName" value="Migrator.Providers.SqlServer.SqlServer2005Dialect" />   
</appSettings>

Default connection string

<add name="Default" connectionString="Data Source=.;Initial Catalog=EnterpriseTester;Integrated Security=True;MultipleActiveResultSets=true;" />

connection.driver_class

<add key="connection.driver_class" value="NHibernate.Driver.SqlClientDriver" />

dialect

<add key="dialect" value="NHibernate.Dialect.MsSql2005Dialect" />

Following are the web.config values you will need for each type of database:

We provide example connection strings for each database, but each database supports a number of different connection options - we recommend consulting the http://connectionstrings.com/ website for listings of the different connection strings you can try.

SQL Server

By default the web.config file comes with the settings necessary to connect to Sql Server or Sql Server Express - all you need to do is provide a connection string.

Your options are:

  1. Use the provided database with user-attached connection string.
<add name="Default" connectionString="Data Source=.\SQLExpress;AttachDbFilename=c:\inetpub\wwwroot\EnterpriseTester\Data\EnterpriseTester.mdf;Initial Catalog=EnterpriseTester;Trusted_Connection=Yes;"/>

2. Connect to an existing database, using integrated security.

When using integrated security, the database will be connected to using the username configured as the identify for the application pool in IIS.

<add name="Default" connectionString="Data Source=.\SQLExpress;Initial Catalog=EnterpriseTester;Integrated Security=True;" />

3. Connect to an existing database, using a sql username & password.

<add name="Default" connectionString="Server=Server123;Database=EnterpriseTester;User ID=bob;Password=pass123;Trusted_Connection=False;" />

Oracle

Enterprise Tester ships with 2 different Oracle drivers. For new installations we would recommend using the Managed Oracle driver. 

Managed Oracle Driver

Change Enterprise Tester to use these values:

migration.providerName: "Migrator.Providers.Oracle.OracleManagedDriverDialect"
connection.driver_class: "EnterpriseTester.Core.Dialects.OracleManagedDataClientDriver,EnterpriseTester.Common"
dialect: "NHibernate.Dialect.Oracle10gDialect"

And update the connection string to be like this:

<add name="Default" connectionString="User ID=SYSTEM;Password=password;Data Source=192.168.1.10:1521/orcl"/>

Unmanaged Oracle Driver

Check if This Topic Applies to You

This topic is for customer who are using Oracle unmanaged drivers.  Generally, this topic will be relevant to customers who are using an Oracle database where the original version of ET installed was 4.7 or early.

New Installations of Enterprise Tester

Enterprise Tester 4.8 and above supports managed ODP.Net drivers. No separate installation is required for managed ODP.Net drivers. We recommended using the managed drivers by all new Enterprise Tester customers who wish to connect to an Oracle database. For details on configuration settings required to be set in the web.config for the Oracle managed drivers please consult the "Database Configuration" topic.

Configuring Enterprise Tester to use Unmanaged Oracle drivers requires some additional manual steps. These are outlined in the "Oracle Driver Installation (unmanaged)" section.

Enterprise Tester requires the following values within the web.config:

migration.providerName: "Migrator.Providers.Oracle.OracleDialect"
connection.driver_class: "NHibernate.Driver.OracleDataClientDriver"
dialect: "NHibernate.Dialect.Oracle10gDialect"

The connection string to be something like the below (this will rely on TNSNAmes)

<add name="Default" connectionString="User ID=SYSTEM;Password=password;Data Source=192.168.1.10:1521/orcl"/>

Alternatively, you can specify the connection details inline, like this:

<add name="Default" connectionString="Data Source=(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=192.168.1.10)(PORT=1521)))(CONNECT_DATA=(SERVER=DEDICATED)(SERVICE_NAME=ETPROD)));User Id=SYSTEM;Password=password;" />

For more examples of Oracle ODP.Net connection strings, please see: http://connectionstrings.com/oracle#p12

PostgreSql

Change Enterprise Tester to use these values:

migration.providerName: "Migrator.Providers.PostgreSQL.PostgreSQL82Dialect"
connection.driver_class: "NHibernate.Driver.NpgsqlDriver"
dialect: "NHibernate.Dialect.PostgreSQL82Dialect"

And update the connection string to be like this:

<add name="Default" connectionString="Server=192.168.1.10;Port=5432;Database=et-prod;User Id=postgres;Password=Password123;Timeout=60;CommandTimeout=120;" />

MySql

Change Enterprise Tester to use these values:

migration.providerName: "Migrator.Providers.Mysql.MysqlDialect"
connection.driver_class: "NHibernate.Driver.MySqlDataDriver"
dialect: "EnterpriseTester.Core.Dialects.MySqlDialectEx, EnterpriseTester.Core"

And update the connection string to be like this:

<add name="Default" connectionString="Server=192.168.1.10;Database=et-prod;Uid=etuser;Pwd=password;" />

 More examples of connection strings can be found here: http://connectionstrings.com/mysql#p28

  • No labels