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:
When you download Enterprise Tester there will be an additional file available called: EnterpriseTester-X.X.XXXXX-Bin.zip
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.
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 (http://www.microsoft.com/express/Database/)
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. http://www.7-zip.org/
Once you have a suitable unzip tool, unpack the binary release file to a suitable directory - if you are unsure, popular locations include:
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
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:
<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;" />
<add key="connection.driver_class" value="NHibernate.Driver.SqlClientDriver" />
<add key="dialect" value="NHibernate.Dialect.MsSql2005Dialect" />
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.
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:
<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.
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.
\ODAC112021Xcopy\instantclient_11_2\oci.dll \ODAC112021Xcopy\instantclient_11_2\orannzsbb11.dll \ODAC112021Xcopy\instantclient_11_2\oraocci11.dll \ODAC112021Xcopy\instantclient_11_2\oraociei11.dll \ODAC112021Xcopy\odp.net20\bin\OraOps11w.dll \ODAC112021Xcopy\odp.net20\odp.net\bin\2.x\Oracle.DataAccess.dll
And insert the following block of xml on the next line:
And insert the following block of xml on the next line after </configSections>
<oracle.dataaccess.client> <settings> <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 --> </settings> </oracle.dataaccess.client>
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:
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=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
Change Enterprise Tester to use these values:
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;" />
Change Enterprise Tester to use these values:
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
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:
<appSettings> <add key="migration.providerName" value="Migrator.Providers.SqlServer.SqlServer2005Dialect" /> ... </appSettings>
Now after the last "add" entry, append these settings:
<add key="attachment.storage.garbagecollection.dwell" value="5" /> <add key="attachment.storage.garbagecollection.disable" value="false" /> <add key="attachment.storage.method" 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).
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.
(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.
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.
Next you will need to create a new application in IIS for Enterprise Tester.
You are now ready to launch 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.