All of our preconfigured packages (see Add-On Packages topic) are completely stand alone and all required files are copied to the deploy folder (and subfolders). You will not experience any change in the behavior of other applications on your PC.

All the messages shown by DWebPro are saved in the messages.ini file located in the deploy folder. You can edit this file manually or preferably use the DWebPro Translator tool. DWebPro shows these messages in the user language depending on the Windows International Settings. You can test DWebPro under different languages in two ways:

1. Configure Windows International Settings with the language you want to test.

2. Open the messages.ini file in the deploy folder and rename the language section you want to test with your actual language and then rename your actual language section to something else (for example, from [english] to [original english]).

Yes, you can. Just copy the True Type Fonts (*.ttf or *.ttc) in use to the deploy folder (or subfolder) and then specify the custom font in the Font section of the http.ini file. In this way DWebPro automatically installs and uninstalls the fonts at runtime and makes them available for use by your Web site. An example of how to specify a custom font in the http.ini file is shown below:

[Fonts]
Batang=##DWEBPRO_PATH##\fonts\batang.ttc

Each name/value pair in the [Fonts] section of http.ini specifies the custom font you intend to use in your Web application.

DWebPro provides a command line parameter (-f filename) that allows you to specify the DWebPro configuration file to use upon startup. For example, the following command starts DWebPro and specifies a custom INI file for use:

dwebpro.exe -f my-ini-file.ini

Yes, just add a ";" char at the beginning of the row where you want to add a comment like in the following example:

[Main]
 
; Remember to set the Browser -> URL field to Url=http://##DWEBPRO_HOSTNAME##:##DWEBPRO_WEBSERVER_PORT##/
; to use the dwebpro.cd host name in the browser address bar.
  
HostName=dwebpro.cd

You will be able to personalize both startup and shutdown splash screens with any DWebPro commercial license. Open the http.ini file and edit the [SplashScreen] section to define custom startup/shutdown splash screens (refer to the Splash Screens tab topic for more information), as shown below:

[SplashScreen]
 
; Startup settings 
 
Startup.Show=1
Startup.Time=2000
Startup.WaitForInit=1
Startup.FileName=##DWEBPRO_PATH##\data\splash.jpg
Startup.MaskColor=#000000
 
; Startup Flash settings 
 
Startup.Flash.Movie=
Startup.Flash.Width=0
Startup.Flash.Height=0
Startup.Flash.Quality=
Startup.Flash.BGColor=
Startup.Flash.WMode=
Startup.Flash.Loop=0
Startup.Flash.Menu=0
 
; Shutdown settings 
 
Shutdown.Show=0
Shutdown.Time=0
Shutdown.WaitForShutdown=1
Shutdown.FileName=##DWEBPRO_PATH##\data\splash.jpg
Shutdown.MaskColor=#000000
 
; Shutdown Flash settings 
 
Shutdown.Flash.Movie=
Shutdown.Flash.Width=0
Shutdown.Flash.Height=0
Shutdown.Flash.Quality=
Shutdown.Flash.BGColor=
Shutdown.Flash.WMode=
Shutdown.Flash.Loop=0
Shutdown.Flash.Menu=0

Custom startup and shutdown splash screens can be bitmap images (*.bmp), jpeg images (*.jpg) or Flash movies (*.swf).

Also note that you can use the Mask Color box to the right of the Splash Screen boxes to define the transparency color for the displayed graphic. Refer to the DWebPro Internal Constants topic for further information on paths when specifying the location of your custom startup/shutdown splash screens.

Open the http.ini file and list all of the DLLs and OCXs that DWebPro must register at runtime in the ActiveX field of the [Main] section, as shown below. Note that if you are editing http.ini manually, you must separate each DLL or OCX file with a pipe "|" character. If you prefer to use the DWebPro Configurator to add or edit these entries, you will use the Main tab.

[Main]
ActiveX=NETStreams.dll|newobjectspack1.dll|SQLITECOMUTF8.dll

If the correct registration/unregistration process of the components requires additional user interaction, you can use DWebPro's External Software feature to perform this work. Refer to the External Software topic for more information.

Prior to distributing any third-party ActiveX or COM objects, please ensure that you are authorized to distribute such components with your application.

Several fields in the [Main] section of http.ini apply to these customizations. If you prefer to use the DWebPro Configurator to add or edit these entries, you will use the Main tab. As an example of how to define a custom tray icon, About box (with a transparent color specified), and hint text, refer to the following:

[Main]
ShowIcon=1
TrayIcon=##DWEBPRO_PATH##\data\myicon.ico
AboutBox=##DWEBPRO_PATH##\data\myabout.bmp
MaskColor=#0000FF
ShowHint=1
Hint=Widget Web

Keep in mind that the tray icon, hint text, and the About box cannot be customized for users with the "FREE for non-commercial use" license. For more information on the DWebPro FREE license, refer to the Limitations of the FREE License topic. For information on DWebPro licensing options, refer to the DWebPro Licensing Model topic.

The fields in http.ini specific to the creation of directories are in the [DirectoryN] section, where N is the unique [Directory] section number for automatically creating directories. The numbering of these sections starts from 0 and must be sequential at intervals of 1. If you prefer to use the DWebPro Configurator to add or edit these entries, you will use the Directories tab.

The example below instructs DWebPro to create the web_files directory on the user's hard drive if it does not exist, clear out all files from that directory, copy (and overwrite, if necessary) all files from the ##DWEBPRO_PATH##\web_files directory to the directory on the user's hard drive, and to display the copy progress window as the copy occurs. In addition, note that DWebPro will clear all of the files in the hard drive directory location upon shutting down and will also remove the directory.

[Directory0]
Path=##DWEBPRO_TEMP##\web_files
CopyFrom=##DWEBPRO_PATH##\web_files
Overwrite=1
ShowCopyProgressWindow=1
ClearOnStartUp=1
ClearOnShutDown=1

For this example, the following copy progress window displays during the copy of the files from the CopyFrom location to the Path location.

Copy Progress dialog

Refer to the DWebPro Internal Constants topic for additional information on paths.

The fields in http.ini that define whether DWebPro displays user warning messages are in the [Warnings] section. If you prefer to use the DWebPro Configurator to edit these entries, you will use the Warnings tab.

[Warnings]
Main=1
ActiveXService=1
ASPNETServerService=1
ASPServerService=1
CrontabService=1
DirectoriesService=1
ExternalSoftwaresService=1
FirebirdService=1
LockCDService=1
MsAccessService=1
MySQLService=1
PostgreSQLService=1
SQLiteService=1
HSQLDBService=1
SMTPServerService=1
WebServerService=1
BrowserService=1
ColdFusionService=1
TomcatService=1
ZopeService=1
MDACService=1
MSDEService=1
FlashPlayerService=1
WindowsInstallerService=1

The Main field refers to the DWebPro general main process, so setting this field to 0 will disable warning messages generated by the DWebPro general main process.

The [ShellExecN] section(s) of http.ini defines the execution of external applications upon startup, shutdown, or both startup and shutdown of DWebPro. The N in [ShellExecN] refers to a unique [ShellExec] section number. The numbering of these sections starts from 0 and must be sequential at intervals of 1. If you prefer to use the DWebPro Configurator to add or edit these entries, you will use the External Software tab. The section of http.ini below shows an application defined to execute upon startup of DWebPro and to hide that application from the user (refer to section [ShellExec0]). This example also specifies an application to execute upon shutdown of DWebPro (refer to section [ShellExec1]):

[ShellExec0]
Path=##DWEBPRO_PATH##\mystartupapp.exe
Params=
DefaultDir=##DWEBPRO_PATH##
ShowModal=HIDE
Wait=0
ExecAndWait=0
StartOn=0
 
[ShellExec1]
Path=##DWEBPRO_PATH##\myshutdownapp.exe
Params=
DefaultDir=##DWEBPRO_PATH##
ShowModal=NORMAL
Wait=0
ExecAndWait=0
StartOn=1

The [WindowsRequirements] section of http.ini specifies the required Windows versions supported by your Web application. If you prefer to use the DWebPro Configurator to add or edit these entries, you will use the Windows Requirements tab. The example below specifies that Windows 2000 and higher, except for Windows Vista and Windows Longhorn Server, are supported:

[WindowsRequirements]
WindowsVersions.WindowsNT40PreSP6Workstation=0
WindowsVersions.WindowsNT40PreSP6Server=0
WindowsVersions.WindowsNT40PreSP6AdvancedServer=0
WindowsVersions.WindowsNT40Workstation=0
WindowsVersions.WindowsNT40Server=0
WindowsVersions.WindowsNT40AdvancedServer=0
WindowsVersions.Windows95=0
WindowsVersions.Windows95OSR2=0
WindowsVersions.Windows98=0
WindowsVersions.Windows98SE=0
WindowsVersions.WindowsMe=0
WindowsVersions.Windows2000Pro=1
WindowsVersions.Windows2000Server=1
WindowsVersions.Windows2000AdvancedServer=1
WindowsVersions.WindowsXPPro=1
WindowsVersions.Windows2003Server=1
WindowsVersions.Windows2003AdvancedServer=1
WindowsVersions.WindowsVista=0
WindowsVersions.WindowsLonghornServer=0

If a user attempts to run your Web application with an unsupported Windows version, the following message box displays:

Unsupported Windows version message

Similar to the UNIX cron command, the DWebPro cron feature starts a process that executes commands at specified dates and times. You can enable the DWebPro cron feature by editing http.ini as shown below. This feature can also be enabled or disabled using the Cron section of the DWebPro Configurator.

The cron command consists of lines of six fields each. The fields are separated by spaces or tabs. The first five are integers that specify the following:

• minute (0-59)

• hour (0-23)

• day of the month (1-31)

• month of the year (1-12)

• day of the week (0-6 with 0=Sunday)

Each of these patterns may be either an asterisk (meaning all valid values) or a list of elements separated by commas. An element is either a number or two numbers separated by a minus sign (meaning an inclusive range). Notice the time is in 24 hour format, 0 is midnight and 13 is one in the afternoon. The sixth field is a string to be executed at the times specified by the first five fields. For example, if the operation starts with the GET string, DWebPro executes an HTTP request toward the specified URL (for example, GET http://127.0.0.1:8080/cron.php).

The following example calls the timerscript.php script every hour:

EnableCron=1
Count=1
Cron0=0 * * * * GET http://127.0.0.1:8080/timerscript.php

The following example calls the timerscript.php script every day at 1PM:

EnableCron=1
Count=1
Cron0=0 13 * * * GET http://127.0.0.1:8080/timerscript.php

The following example calls the timerscript.php script the first and 15th of every month as well as on every Tuesday at exactly midnight:

EnableCron=1
Count=1
Cron0=0 0 1,15 2 GET http://127.0.0.1:8080/timerscript.php

DWebPro primary Web server supports SSL (https://) protocols for secure HTTP connections. Refer to the SSL Support settings in the Web Server topic for more information on secure connections.

Try adding the following code before the "use CGI;" statement of your Perl scripts:

$CGITempFile::TMPDIRECTORY = $ENV{"TEMP"};