Difference between revisions of "Installation"
(→SQL Server) |
(→Server Requirements) |
||
| (18 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
== Server Requirements == | == Server Requirements == | ||
| − | * IIS running on Windows 2000 or higher | + | === Up to Version 1.02 === |
| − | * | + | |
| − | * MS Ajax Control Toolkit | + | * IIS running on Windows 2000 or higher |
| + | * .Net Framework 2.0 | ||
| + | * [http://www.codeplex.com/AjaxControlToolkit/Release/ProjectReleases.aspx?ReleaseId=11121 MS Ajax Control Toolkit] | ||
* SQL Server 2000 or higher | * SQL Server 2000 or higher | ||
| + | * ODP.Net from [http://www.oracle.com/technology/software/tech/windows/odpnet/utilsoft.html Oracle Data Access Components 11g] (optional; required for Oracle connectivity) | ||
| + | * Npgsql (optional; required for PostgreSql connectivity) | ||
| − | == | + | === From Version 1.03 on === |
| + | |||
| + | * IIS running on Windows XP or higher | ||
| + | * .Net 3.5 Service Pack 1 | ||
| + | * SQL Server 2000 or higher | ||
| + | * ODP.Net from [http://www.oracle.com/technology/software/tech/windows/odpnet/utilsoft.html Oracle Data Access Components 11g] (optional; required for Oracle connectivity) | ||
| + | * Npgsql (optional; required for PostgreSql connectivity) | ||
| + | |||
| + | == Installation == | ||
=== SQL Server === | === SQL Server === | ||
| − | * Create a database | + | Open Enterprise Manager (SQL 2000) or SQL Management Studio (SQL 2005+) |
| + | |||
| + | * Create a database (select a case-insensitive collation such as Latin1_General_CI_AS) | ||
* In the database, run the scripts: | * In the database, run the scripts: | ||
| − | * | + | * Create.sql |
| − | * | + | * Initialize Users.sql |
| + | * Value Script.sql | ||
| + | * Code Snippet.sql | ||
| − | + | (The names of the sql scripts are preceded by "dbs" plus the version number) | |
| − | + | The Users table contains one record with the ID "Administrator". You can change the ID to your desired username to log in to the application. | |
SQL Server must allow SQL Server authorization. | SQL Server must allow SQL Server authorization. | ||
| Line 24: | Line 40: | ||
* SQL Server authorization | * SQL Server authorization | ||
| − | * no password policy | + | * no password policy |
| − | * dbo access to the database. | + | * allow dbo access to the database. |
=== IIS Server === | === IIS Server === | ||
| − | * Create a directory, virtual directory, or website in IIS Administrator | + | * Create a directory, virtual directory, and create an application; or create a website in IIS Administrator |
| − | * Extract web.zip into the directory | + | * Extract web.zip (dbs*webpub.zip) into the directory |
| − | * | + | * If the zip contains a file called web.publish.config, rename it to web.config |
| + | * Otherwise, copy web.config into the directory | ||
* Locate the connection string in web.config and adjust server name, catalog, username, and password. | * Locate the connection string in web.config and adjust server name, catalog, username, and password. | ||
| + | |||
| + | The web.zip filename is preceded by "dbs" + date + version. | ||
| + | |||
| + | == Upgrade == | ||
| + | |||
| + | === SQL Server === | ||
| + | |||
| + | Open Enterprise Manager (SQL 2000) or SQL Management Studio (SQL 2005+) and locate the existing dbscript database. | ||
| + | |||
| + | * Open a query window in the database and run the scripts | ||
| + | |||
| + | * database upgrade script named "dbs" + new version + "from" + old version + ".sql" | ||
| + | |||
| + | * Value Script.sql | ||
| + | |||
| + | * Code Snippet.sql | ||
| + | |||
| + | Occasionally additional SQL files need to be run during update. In such cases, the files are named | ||
| + | "dbs [version number] . [sequence number] . [ etc ].zip" | ||
| + | |||
| + | === IIS Server === | ||
| + | |||
| + | Extract the contents of web.zip (dbs*webpub.zip) into the web application directory. | ||
| + | |||
| + | The web.zip filename is preceded by "dbs" + date + version. | ||
| + | |||
| + | Starting with version 1.03, the web.publish.config is always included in the web.zip, and extracting the zip will not accidentally delete the existing web.config file. Manually check whether there are new settings in the web.publish.config which need to be transferred to the web.config file. | ||
| + | |||
| + | == Configuration == | ||
| + | |||
| + | === Update Notifications === | ||
| + | |||
| + | ==== Version 0.99 through 1.01 ==== | ||
| + | |||
| + | dbscript 0.99 introduces Update Notifications. This feature fetches information about new versions of dbscript from update.devio.at. | ||
| + | |||
| + | By default, the information is fetched by client-side Javascript. | ||
| + | |||
| + | You can configure the update notification behavior by setting the UpdateMode column in the Configuration table to: | ||
| + | |||
| + | * 0 ... client side fetch | ||
| + | * 1 ... server side fetch (the IIS machine needs to have connection to the Internet) | ||
| + | * -1 .. disabled | ||
| + | |||
| + | In Internet Explorer, client-side update fetch may lead to a security warning about accessing a different website from script. | ||
| + | |||
| + | To avoid the message, add update.devio.at to a zone that allows cross-domain access. See this [http://support.microsoft.com/kb/829934 MSDN KB entry] for more information. | ||
| + | |||
| + | ==== Version 1.02 and higher ==== | ||
| + | |||
| + | dbscript 1.02 introduces Update Notifications via JSONP. This feature fetches information about new versions of dbscript from update.devio.at. | ||
| + | |||
| + | You can configure the update notification behavior by setting the UpdateMode column in the Configuration table to: | ||
| + | |||
| + | * 1 ... enabled | ||
| + | * every other value .. disabled | ||
| + | |||
| + | dbscript 1.03 provides the new menu command "Updates" to allow the user to check for updated versions manually. | ||
| + | |||
| + | == Register License == | ||
| + | |||
* Start your webbrowser and navigate to the URL of your installation | * Start your webbrowser and navigate to the URL of your installation | ||
* Login using the selected username without password | * Login using the selected username without password | ||
* Navigate to Settings, upload you license key file | * Navigate to Settings, upload you license key file | ||
Latest revision as of 12:43, 15 September 2010
Contents
Server Requirements[edit]
Up to Version 1.02[edit]
- IIS running on Windows 2000 or higher
- .Net Framework 2.0
- MS Ajax Control Toolkit
- SQL Server 2000 or higher
- ODP.Net from Oracle Data Access Components 11g (optional; required for Oracle connectivity)
- Npgsql (optional; required for PostgreSql connectivity)
From Version 1.03 on[edit]
- IIS running on Windows XP or higher
- .Net 3.5 Service Pack 1
- SQL Server 2000 or higher
- ODP.Net from Oracle Data Access Components 11g (optional; required for Oracle connectivity)
- Npgsql (optional; required for PostgreSql connectivity)
Installation[edit]
SQL Server[edit]
Open Enterprise Manager (SQL 2000) or SQL Management Studio (SQL 2005+)
- Create a database (select a case-insensitive collation such as Latin1_General_CI_AS)
- In the database, run the scripts:
- Create.sql
- Initialize Users.sql
- Value Script.sql
- Code Snippet.sql
(The names of the sql scripts are preceded by "dbs" plus the version number)
The Users table contains one record with the ID "Administrator". You can change the ID to your desired username to log in to the application.
SQL Server must allow SQL Server authorization.
Create a database login:
- SQL Server authorization
- no password policy
- allow dbo access to the database.
IIS Server[edit]
- Create a directory, virtual directory, and create an application; or create a website in IIS Administrator
- Extract web.zip (dbs*webpub.zip) into the directory
- If the zip contains a file called web.publish.config, rename it to web.config
- Otherwise, copy web.config into the directory
- Locate the connection string in web.config and adjust server name, catalog, username, and password.
The web.zip filename is preceded by "dbs" + date + version.
Upgrade[edit]
SQL Server[edit]
Open Enterprise Manager (SQL 2000) or SQL Management Studio (SQL 2005+) and locate the existing dbscript database.
- Open a query window in the database and run the scripts
- database upgrade script named "dbs" + new version + "from" + old version + ".sql"
- Value Script.sql
- Code Snippet.sql
Occasionally additional SQL files need to be run during update. In such cases, the files are named "dbs [version number] . [sequence number] . [ etc ].zip"
IIS Server[edit]
Extract the contents of web.zip (dbs*webpub.zip) into the web application directory.
The web.zip filename is preceded by "dbs" + date + version.
Starting with version 1.03, the web.publish.config is always included in the web.zip, and extracting the zip will not accidentally delete the existing web.config file. Manually check whether there are new settings in the web.publish.config which need to be transferred to the web.config file.
Configuration[edit]
Update Notifications[edit]
Version 0.99 through 1.01[edit]
dbscript 0.99 introduces Update Notifications. This feature fetches information about new versions of dbscript from update.devio.at.
By default, the information is fetched by client-side Javascript.
You can configure the update notification behavior by setting the UpdateMode column in the Configuration table to:
- 0 ... client side fetch
- 1 ... server side fetch (the IIS machine needs to have connection to the Internet)
- -1 .. disabled
In Internet Explorer, client-side update fetch may lead to a security warning about accessing a different website from script.
To avoid the message, add update.devio.at to a zone that allows cross-domain access. See this MSDN KB entry for more information.
Version 1.02 and higher[edit]
dbscript 1.02 introduces Update Notifications via JSONP. This feature fetches information about new versions of dbscript from update.devio.at.
You can configure the update notification behavior by setting the UpdateMode column in the Configuration table to:
- 1 ... enabled
- every other value .. disabled
dbscript 1.03 provides the new menu command "Updates" to allow the user to check for updated versions manually.
Register License[edit]
- Start your webbrowser and navigate to the URL of your installation
- Login using the selected username without password
- Navigate to Settings, upload you license key file
