How to use CDBuilder

Required step: see video tutorials on using CDBuilder

See video tutorials on using CDBuilder.

Required step: Creating a project in CDBuilder

Start CDBuilder: Select Project, New to create a project. You should select a project input directory (where various files used for your CD will reside, e.g. database files and web content).

Put the database files into a subdirectory of your input directory, place your web content into another subdirectory.

Select an output directory (specify a relative input directory, e.g. like "../out") - it's the directory where the prototype (tree of folders and files) of CD will be copied to.

Go to → "Project" → "Site Settings" → "General" → "Main Properties" and specify the platforms that your product will support and the paths to the directory with the database files and web content which are RELATIVE to the input directory (e.g. if "c:\mycd1\in" is the project input directory and "c:\mycd1\in\webroot" is the directory with web content, specify "webroot" as the directory with web content, and so on and so forth for directories with database files.

WARNING! There is a detailed sample on directory layouts available in a separate document located here.

Required step: Specify other settings

Select → "Project" → "Site Settings" and specify database access modes in "Databases" → "MySQL" and "Databases" → "SQLite" (or turn off support for SQLite and MySQL there).

On the same page, in "Scripting Languages" you can specify a desired support type for each scripting language, and select the extensions you need.

Required step: Update database connection strings in your scripts:

If your product uses MySQL

  • If accessing MySQL database from Perl, update your DSN string to contain MySQL port number (stored in $ENV{MYSQL_PORT}) as done in /site/www/root/mysqldemo.pl from the full trial cd. Nothing needs changes in PHP scripts with respect to port number: PHP scripts will use correct port numbers automatically since it will be set in a dynamically-generated php.ini.
  • Update PHP/Perl/Python/Java scripts to use host=127.0.0.1 in a database connection string.

If your product uses SQLite

  • Convert SQLite databases to a proper format (understood by SQLite library shipped with the web server demo).
  • Update PHP and Perl scripts to use environment variables SQLITE_TABLES as a directory with SQLite database files in database connection strings as done in /site/www/root/sqlitedemo.php and /site/www/root/sqlitedemo.pl.

Optional step: Make your product more user friendly:

It's greatly recommended to add text to /README.html.

Specify the path to the splash screen and CDROM icon (not favicon!) relative to the project's input directory in Project, "Site Settings", "General", "Paths and the initial url".

Option Two: Protect your code from theft and analysis:

  • To protect JavaScript from analysis and theft and for mangling of your html, you can use the Stunnix JavaScript Obfuscator;
  • To protect VBScript from analysis and theft and for mangling of your html you can use Stunnix VBScript and ASP Obfuscator;
  • To protect Perl scripts from analysis and theft, you can use Stunnix Perl-Obfus - an advanced obfuscator and encoder for Perl source code;
  • To protect PHP scripts from analysis and theft, you can use IonCube PHP encoder - it's already integrated into SAWS and supported on all platforms!

Optional step: Request any help from us

Please contact us if you have any questions. If the PHP available with our evaluation software doesn't include the extension you need, or if you wish to make SAWS support other platforms, or need an Apache module to become supported by SAWS - we can also help you.

Required step: Create CDROM Trees

Click Build → "Rebuild Changed" - you should get a prototype of your cdrom in the project's output directory. It's recommended to use CDBuilder for creation of ISO files for burning to CD - just click "Tools", "Create ISO out of project's output directory..". Just burn it directly onto a CD.

The program that creates the ISO images or burns prototypes directly to CDROMs should preserve case of filenames for your CD to work on platforms other than Windows (the ISO creation facility of CDBuilder does this correctly, so it's greatly not recommended to use third-party tools instead of it). In order to be able top append or replace some data on the CD, it may be wise to burn CDs in multi-session mode and not close the last session.

If you need to create a desktop application from the CDROM, use the tree in the project output directory as a prototype for your application.

Suggested step: Enjoy!

Please enjoy our products and tell your friends about how fantastic this software worked for you!