• http://www.innosetup.com/
• http://www.installshield.com/
• http://www.wise.com/
• http://www.advancedinstaller.com/
• http://wix.sourceforge.net/
• http://nsis.sourceforge.net/

We advise our customers to use Inno Setup (http://www.innosetup.com/), it’s free, very stable and includes almost any feature you can need. It supports the execution of internal Pascal Scripting for complex tasks such registry manipulation and can use external DLLs to perform any other task.

In the cobrand folder (typically C:\DWebPro\cobrand) you can find an Inno Setup script (http://www.innosetup.com/) and a NSIS script (http://nsis.sourceforge.net/) you can use as template for creating your own install package.

Creating an install package that works on every system and configuration can be a complex task. We suggest you to read the "Best Practice Guidelines for Building Quality Installs" articles on the Windows Installer Team Blog.

Just a final note, remember to check the behavior of your web application under user with different privileges and under all the operating systems you will support.

Here is an example for use with ASP Classic 3.0 (VBScript):

<%
Dim DSN, conn
DSN = "DRIVER={Microsoft Access Driver (*.mdb)};" & _
      "DBQ=" & Server.MapPath("Northwind.mdb") & ";" & _
      "UID=admin;" & _
      "PWD=;" & _
      "ReadOnly=1;" & _
      "Exclusive=1;"
Set conn = Server.CreateObject("ADODB.Connection")
conn.Open(DSN)
%>

Here is an example for use with ColdFusion:

<CFQUERY NAME="qrySample"
 DBTYPE="dynamic"
 CONNECTSTRING="DRIVER={Microsoft Access Driver (*.mdb)};
                DBQ=#ExpandPath('\')#Northwind.mdb;
                UID=Admin;PWD=;ReadOnly=1;Exclusive=1;">
SELECT * FROM tblSample
</CFQUERY>

Using this method, you can use Microsoft Access databases directly from your CD/DVD without the need of copying it to the user’s hard drive.

To let you familiarize with this feature we have included in the DWebPro package the DWebPro Rewrite Engine Tester tool.

The DWebPro Rewrite Engine Tester Software

The use of this tool is very simple.

• Open the DWebPro Rewrite Engine Tester (Start -> Programs -> DWebPro -> Advanced Tools -> Rewrite Engine Tester).

• The Request Path field contains the path part of the requested URL.

• The Request Query String field contains the query string of the requested URL.

• The memo under the Rewrite button contains the mod_rewrite directives you want to test.

• Once you have filled the above fields with your information, click on the Rewrite button and you will get the rewritten path in the Rewritten Path field.

• The key/value list on the right contains the server variables supported by the URL Rewrite Engine.

Refer to the URL Rewrite Engine topic for more information on DWebPro url rewrite support.

The DWebPro ReBrander enables you to re-brand the dwebpro.exe file in a couple of minutes.

The DWebPro ReBrander Software

To rebrand the dwebpro.exe file follow these steps:

• Open the DWebPro ReBrander tool (Start -> Programs -> DWebPro -> Advanced Tools -> DWebPro ReBrander).

• It will automatically load the current dwebpro.exe version information.

• Fill the version information fields with your own information.

• Select an Icon File if you want to personalize the icon.

• Select a Destination File.

• Click on ReBrand button.

Refer to the DWebPro Licensing Model topic for more information about DWebPro ReBrand.

The DWebPro Encoder Software

DWebPro Encoder contains two components: a GUI (Graphical User Interface) that performs the file encryption and a PHP extension that decodes and runs the scripts. DWebPro Encoder is very easy to use. A summary of how to use this tool are as follows:

1. Select the folder containing the scripts to encode.

2. Select the destination folder.

3. Select the Encoding Type: PHP or ASP Classic.

4. Specify the extensions of the files to elaborate. For example: *.php; *.php3; *.php4; or *.asp; * .asa.

5. Click Compile.

The two available options are:

• Copy other files to automatically copy other files as well.

• Normalize only re-elaborates the content to prepare it for the encoding process. This option is useful for verifying the correct functioning of the encoder.

DWebPro supports also the major part of PHP encoders available on the market. Our PHP preconfigured packages include the extensions for the following encoders:

• Ioncube
• Zend Encoder
• SourceGuardian
• PHTML Encoder
• eAccelerator
• phpSHIELD
• Nu-Coder

The DWebPro License Bundler Software

This tool encodes the license and embeds it into the dwebpro.exe binary with a unique key based on the http.ini file and the files in the document root folder. In this way the generated executable (dwebpro.exe) will work only with that specific configuration and web application.

Using the DWebPro License Bundler tool is very easy:

• Open it from Start -> Programs -> DWebPro -> Security Tools -> DWebPro License Bundler.

• Change the various setting to fits your needs. Most of the times you should not need to change the default values.

• Click on Bundle License.

• Close the tool.

Keep in mind that the generated executable specified by the Destination file field will run only with the configuration file specified by the HTTP.INI File field and the web application located in the Document root field. If you made any change to those files you have to re-bundle the license otherwise you will raise the dwebpro_license_invalid_cd error message ("WARNING! The license is invalid for this CD/DVD!").

Refer to the DWebPro License Bundler topic for more information on DWebPro license bundling tools.

The supported error documents are:

• 403.htm

• 404.htm

• 500.htm

• 500-1.htm

When the ASP Classic 3.0 support raises an error (i.e. a parsing error or a runtime error), DWebPro executes the 500-100-vb.asp or the 500-100-js.asp files from the document root folder (usually deploy\www) depending on the language of the page that has raised the error (500-100-vb.asp for VBScript pages and 500-100-js.asp for JScript pages).

You can personalize all these files with your own graphics and style.

If you will use MySQL 4.1 (or above), you should use PHP 5.0 (or above). If you need to use PHP 4.4 and MySQL 4.1 (or above) you have to add the following string to the CustomParams field in the MySQL section:

--old-passwords

We recommend you to install PHP as ISAPI as it is a faster and more efficient interface than CGI, especially when PHP is executed on CD/DVD. Once you have installed PHP you can change its settings by editing the php.ini file in the deploy folder.

Download and install one of our preconfigured MySQL packages.

Download and install our preconfigured phpMyAdmin V.2.6.1 package.

Place your Web application files in the C:\DWebPro\deploy\www folder.

Start DWebPro (it should bring you to the phpMyAdmin section).

Create a MySQL database you will use for your Web site.

Import the dump of your MySQL database. This procedure can be done using any other MySQL client (for example, MySQL CC, DBTools, mysql.exe). When you connect to MySQL you MUST provide the correct port on which MySQL is listening . As default behavior, DWebPro starts any socket server on the first empty port. You can get the correct MySQL port using the following PHP code:

<?php
print(dwebpro_getvar("DWEBPRO_MYSQL_PORT"));
?>

Open your Web scripts and edit the MySQL connection settings to fit the following values:

<?php
$host = "127.0.0.1:" . dwebpro_getvar("DWEBPRO_MYSQL_PORT");
$database = "the database you have just created";
$username = "root";
$password = "";
?>

Burn the C:\DWebPro\deploy folder on a CD/DVD. You can place the contents of this folder in a subfolder of the CD/DVD, in this case you should put in the root folder both the autorun.inf and the autorun.exe files and edit the autorun.inf to point to the dwebpro.exe file in the subfolder. For instance, if you have placed the DWebPro files in the F:\website subfolder (where F: is the CD/DVD unit name), you have to edit the autorun.inf file as follows:

[autorun]
icon=website\dwebpro.exe
open=website\dwebpro.exe

If you want you can change the CD/DVD icon, change the icon setting in the autorun.inf file. The autorun.exe can be renamed into whatever you want (i.e., StartMe.exe). This program is provided to help the end user on starting DWebPro. It reads the autorun.inf directives and executes them, it is very useful when the end user has disabled the Windows autorun feature. Now you should be able to run you PHP/MySQL Web application with DWebPro. If you need to execute write operations on the MySQL database you have to configure DWebPro to copy the database files on the user file system. Read the MySQL section of the manual to understand the different ways this can be done. If in your configuration settings there are full paths like the following:

<?php
$root = "/urs/local/example.com/www/";
?>

You should rewrite them using a code like the following that will work correctly on any system:

<?php
$root = realpath(dirname(__FILE__) . "/../") . DIRECTORY_SEPARATOR;
?>

Here is a code excerpt that you should add to your web site config file to make PHP work correctly from CD/DVD:

<?php

/*
* This script contains some directives to make your PHP
* environment perfectly working on read only media like CD/DVD
*/

/* Session support */

ini_set('session.save_path', dwebpro_getvar('DWEBPRO_TEMP'));

/* MySQL support */

ini_set('mysql.default_port', dwebpro_getvar('DWEBPRO_MYSQL_PORT'));
ini_set('mysql.default_host', '127.0.0.1');
ini_set('mysql.default_user', 'root');
ini_set('mysql.default_password', '');

/* SMTP/Mail support */

ini_set('smtp_port', dwebpro_getvar('DWEBPRO_SMTPSERVER_PORT'));
ini_set('sendmail_from', 'support@dwebpro.com');

?>

<%
Dim DSN, DB_CONN
DSN = "DRIVER={Microsoft Access Driver (*.mdb)};" & _
      "DBQ=" & Server.MapPath("Northwind.mdb") & ";" & _
      "UID=admin;PWD=;ReadOnly=1;Exclusive=1;"
Set DB_CONN = Server.CreateObject("ADODB.Connection")
DB_CONN.Open(DSN)
%>

Where Northwind.mdb is your database file.

The last step is burning the deploy (usually C:\DWebPro\deploy) folder on a CD/DVD. See the details of this step in the Distribute PHP/MySQL Web Sites topic. If you need to execute write operations on the Microsoft Access database, you have to configure DWebPro to copy the database files onto the user’s file system. Read the Microsoft Access topic to understand the different ways this can be done. When DWebPro copies the database files onto the user’s file system, it provides way to find the destination folder. Here is sample code to create your own DSN to connect to a Microsoft Access database saved on the user’s file system:

<%
Dim DSN, DB_CONN
DSN = "DRIVER={Microsoft Access Driver (*.mdb)};" & _
      "DBQ=" & Request.ServerVariables("DWEBPRO_MSACCESS_DATADIR") & _
      "\Northwind.mdb;UID=admin;PWD=;"
Set DB_CONN = Server.CreateObject("ADODB.Connection")
DB_CONN.Open(DSN)
%>

The ASP Classic 3.0 Support provided by DWebPro contains some differences and many improvements over the one provided from the Microsoft. The main improvements are:

• New Server objects methods (FileExists, DirectoryExists, EjectCD, LockCD, UnlockCD, IsInternetConnected, MachineID, Encrypt, Decrypt, ReadBinaryFile)

• Mail object that replicates the CDONTS object behavior

• Server.Registry object that provides the ability to manipulate the system registry

• Request.Upload object for handling file upload without needing external COM objects

The 500-100-vb.asp and 500-100-js.asp files residing in the deploy\www folder have the same behavior of the 500-100.asp files of IIS. They are accessed when the ASP engine generates an error (during page parsing or runtime execution). You can customize these error pages to match the style of your Web site. Refer to the How To Personalize The HTTP Error Messages topic for more information on error documents customization.

A Note About ASP.NET

ASP.NET is a Microsoft Technology that represents the next evolution of the Active Server Pages Technology introduced with IIS 3.0 (and enhanced with the successive version of IIS). ASP.NET 1.1 and ASP.NET 2.0 normally require the presence of the Microsoft .NET Framework 1.1 and Microsoft .NET Framework 2.0, respectively.

This can be a huge problem for distributing stand alone Web sites on CD/DVD. Beginning with DWebPro version 6.5.1, we have introduced a new, unique feature that enables you to distribute ASP.NET 2.0 Web sites without requiring the presence of the Microsoft .NET Framework.

This is accomplished by installing the ASP.NET 2.0 Embedded package available from the Add-On page at the DWebPro Web site.

The proper order of tasks for creating your Web site for CD/DVD are:

1. Download the latest version of DWebPro

2. Download the necessary additional packages (for example, PHP and MySQL)

3. Install DWebPro and the additional packages.

4. Configure DWebPro (http.ini file). Refer to the DWebPro Configurator Tabs topic for more information.

5. Configure the add-on packages.

6. Create the databases, if used.

7. Copy your own Web site files into the C:\DWebPro\deploy\www folder.

8. Start DWebPro and verify if the Web site works properly.

9. Burn the contents of the C:\DWebPro\deploy folder and subfolders to the CD/DVD.

Additionally you can create a text file named autorun.inf and place it into the root folder of the CD/DVD. This file will launch DWebPro automatically, immediately after the CD/DVD is inserted in the user’s CD/DVD drive. Here is a simple example of the autorun.inf file content:

[autorun]
open=dwebpro\dwebpro.exe
icon=dwebpro\dwebpro.exe
label=DWebPro Demo Site

In the above example, it is assumed that the DWebPro files have been previously copied to the dwebpro subfolder of the CD/DVD.