This guide details to steps to install ET using a zip file.

There is now a binary release of Enterprise Tester available.  This release allows you to do an installation by using a “zip” file rather than using the Windows Installer (.MSI file). 

Installing Enterprise Tester from the binary release files is recommended for use by purchased users or those trial users who wish to deploy Enterprise Tester into an environment where they cannot configure the IIS Default Website to use the values required by the installer temporarily.

If you are trialing Enterprise Tester, we strongly advise using our MSI based installer which allows you to easily install Enterprise Tester and its prerequisite components.

Installing Enterprise Tester from the binary zip release involves:


The Enterprise Tester binary zip release requires the following prerequisite components to be installed:

Advantages of Performing A Zip File Installation

Where can I get the Zip File from?

When you download Enterprise Tester there will be an additional file available called:

What's in the Zip File?

When you unpack the zip file you will find this structure:

The Data and Web folders are the same as those installed into the "Enterprise Tester" directory, when using the existing Windows Installer (.MSI file).

Additionally there are 3 text files available:

Each time an upgrade is performed users must check the Upgrade text file and follow specific instructions relating to the release. 

Install prerequisites

Prior to installing please ensure you have the following installed:

If you do not have a database, we recommend installing Sql Server Express 2008 r2 (

Unzip the install files

Prior to installing Enterprise Tester you must unpack the zip file into a suitable directory.

If you do not have a suitable tool installed for unzip files we suggest downloading 7-zip, which is a powerful (and free) zip/unzip tool for windows operating systems.

Once you have a suitable unzip tool, unpack the binary release file to a suitable directory - if you are unsure, popular locations include:

c:\inetpub\wwwroot\Enterprise Tester\
c:\Program Files (x86)\Catch Limited\Enterprise Tester\

When the files have been unpacked you will find that you have a structure like this:

Data Folder – MySql Express database is found here
Web Folder – Application files are in this folder
changes.txt - readme file summarizing changes in each version of Enterprise Tester
install.txt – the document you are reading now

Configure the web.config file

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.

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

These are the default settings:


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

Default connection string

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


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


<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 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;" />


Configuring Enterprise Tester to use Oracle requires some additional manual steps.

  1. Install the Oracle ODAC/ODP.Net Client libraries for your edition of Oracle, as you normally would.
  2. Determine if your operating system is 32bit or 64bit, and download the appropriate ODAC xcopy release from here:
  3. Download the "XCopy" zip file.
  4. Once downloaded, unzip the file to a directory, and then copy the following files from the zip distribution in the \web\bin\ folder of your Enterprise Tester directory.

  5. Once copied, edit the web.config file, locate the end of the config sections element:

And insert the following block of xml on the next line:

And insert the following block of xml on the next line after </configSections>

   <add name="DllPath" value="C:\Program Files (x86)\Catch Limited\Enterprise Tester\Web\bin"></add>
   <add name="FetchSize" value="65536"></add>
   <add name="PromotableTransaction" value="promotable"></add>
   <add name="StatementCacheSize" value="10"></add>
   <add name="TraceFileName" value="c:\temp\odpnet2.log"></add>
   <add name="TraceLevel" value="0"></add> <!-- 63 -->
   <add name="TraceOption" value="0"></add> <!-- 1 -->

Updating the DllPath value to point to the \web\bin\ directory of your Enterprise Tester install.

6. Now change the following values within the web.config:

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

And update 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="/>

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

<add name="Default" connectionString="Data Source=(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=;User Id=SYSTEM;Password=password;" />

For more examples of Oracle ODP.Net connection strings, please see:


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=;Port=5432;Database=et-prod;User Id=postgres;Password=Password123;Timeout=60;CommandTimeout=120;" />


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=;Database=et-prod;Uid=etuser;Pwd=password;" />       

 More examples of connection strings can be found here:

Attachment configuration (optional)

By default Enterprise Tester will store attachments in the database.  This behaviour can be configured, such that attachments are stored on the file system.  To do so, open the web.config file and locate the appSettings section:

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

Now after the last "add" entry, append these settings:

<add key="" value="5" />
<add key="" value="false" />
<add key="" value="FileSystemCas" />

This will then begin storing attachments in the default location of ../Data/Attachments/

Please consult the Enterprise Tester Installation guide for more details (section 6.5.3 Storing Attachments in a File System).

Configuring an application pool

Before configuring an application pool for Enterprise Tester to use, you should give some thought to the application pools identity.

By default in IIS6 application pools are configured with the identity "Network Service" or "Local System", under IIS7/7.5 they are created with "ApplicationPoolIdentity" by default, but can also default to "Local System", "Local Service" or "Network Service".

If this service is a member of an Active Directory domain we recommend creating a specific domain service account for use by Enterprise Tester, this will be useful when configured network filesystem access for the Enterprise Tester and makes it easier to identify Enterprise Tester and give it permissions to a database when using integrated security.


  1. Go to Control Panel -> Administrative Tools
  2. Launch IIS Administrator
  3.   Expand the server node.
  4. Click on "Application Pools"
  5. Click on "Add Application Pool..." under Actions.
  6. Give the new application pool a descriptive name such as "Enterprise Tester".
  7. Select ".Net Framework v2.0.50727" from the .Net Framework version list.
  8. Select "Integrated" for the managed pipeline mode.
  9. Click OK to create the new application pool.
  10. Right click on the new application pool and select "Advanced Settings.."
  11. Under the "Process Model" section, change the Identity to your service account (if you have decided to use one).

(Optional) - If you are using a 64bit operating system, and plan on using Enterprise Architect integration with .EAP files, you will need to change the option "Enable 32-Bit Applications" to true.  Note: This will not be possible if you are using the Oracle 64bit ODP.Net drivers.


  1. Go to Start -> Administrative Tools -> Internet Information Services (IIS) Manager
  2. Expand the "Web Service Extension" node.
  3. Click on the "ASP.NEt v2.0.50727" Node.
  4. Click the "Allow" button, if it's not already enabled.
  5. Expand the "Application Pools" node.
  6. Right click on "Application Pools" and select New -> Application Pool.
  7. Give the Application Pool a descriptive ID such as "Enterprise Tester"
  8. Right click on the new Application pool and select "Properties"
  9. Move the to "Identity" tab and change the application pool identity to a configurable account, specifing the username and password of your domain service account.
  10. Click OK to save the changes.

At this point you may find it useful to consult the timeout's mini-guide (which can be downloaded from the catch website) and configure the timeout/recycling settings for the application pool, a common complaint from customers is that the timeouts are too short by default in IIS, so changing these to longer values is advisable.

Creating a new application for IIS

Next you will need to create a new application in IIS for Enterprise Tester.


  1. Within IIS Manager, expand the "Sites" node.
  2. Expand the "Default Web Site" node.
  3. Right click and select "Add Application".
  4. Enter an alias for the site we suggest "EnterpriseTester"
  5. Click the "Select..." button next to the application pool, and select the application pool you created in the previous step.
  6. Click the elipsis "..." next to the Physical Path, and browser to the "Web" folder of your Enterprise Tester install.
  7. Click "OK" to create the new application.


  1. Within IIS Manager, expand the "Web Sites" node.
  2. Expand the "Default Web Site" node.
  3. Right click and select "New -> Virtual Directory"
  4. Click "Next"
  5. Enter an alias for the virtual directory, we suggest "EnterpriseTester".
  6. Click "Next"
  7. Click "Browse.." and select the path to the "Web" folder of your Enterprise Tester install.
  8. Click "Next"
  9. Select  "Read" and "Run scripts" check boxes.
  10. Click "Next"
  11. Right click on the new site and select "Properties..."
  12. Select the "Virtual Directory" tab and click "Create"
  13. Select the application pool you created in the previous step from the "Application pool:" drop down list.
  14. Click the "Configuration" button.
  15. Under "wildcard application maps" click "Insert..."
  16. Click "Browse..."
  17. Browse to "C:\Windows\Microsoft.Net\Framework\v2.0.50727"
  18. Select "aspnet_isapi.dll" and click "Open"
  19. Uncheck "Verify that file exists"
  20. Click "OK" to save the mapping.
  21. Under "Application extensions" click the "Add..." button.
  22. Click "Browse..."
  23. Browse to "C:\Windows\Microsoft.Net\Framework\v2.0.50727"
  24. Select "aspnet_isapi.dll" and click "Open"
  25. Enter the extension ".rails"
  26. Check "Script engine".
  27. Uncheck "Verify that file exits".
  28. Click "OK"
  29. On the properties dialog for the new site, now switch to the "ASP.Net" tab.
  30. From the "ASP.Net" version drop down ensure "2.0.50727" is selected.
  31. Click OK to close the dialog and save changes.

You are now ready to launch Enterprise Tester for the first time.

Launching Enterprise Tester for the first time

From a browser on the same server as Enterprise Tester, access the website - by default this will probably be: http://localhost/EnterpriseTester/

Or use whichever URL is appropriate for the Default Web site settings that are in place.

You will experience a delay (normally between 1 and 2 minutes) while Enterprise Tester creates the necessary tables and populates them in the target database, after which you will see a "Step 1 of 3" wizard page displayed, prompting you to create a new organization.

At this stage you can continue with the installation and setup of Enterprise Tester as per the installation guide available for download from the Enterprise Tester website:

Refer to Section 3.3 "Initial Configuration" for more details.