DySE™ Script : Documentation
Home > DySE™ > Documentation   Updated: 16-Apr-2008

DySE™ Script Documentation

A video tutorial is available showing how to install DySE™. Click here to view the video tutorial.

How to read this documentation It is recommended that you start at the beginning of this document and read the chapters in order. Technical reference material that you only need to refer to when needed is located at the end of this documentation. The following icons are used:   Very important note.   Informational note.   Cautionary note.   Novice user note.   Unimplemented feature.   Tip.

Note:   "cgi-bin" directory The instructions in this documentation assume that your web server has a directory named cgi-bin where scripts are to be stored on your web server. Some web servers use a different name for this directory, such as: cgi-local, or cgi, or mainwebsite_cgi or something similar. In that case, where you see cgi-bin in any instruction, substitute it with the directory name that your web server uses.

» 1. Introduction to DySE™

This documentation provides:

1. Web server requirements.
2. An overview of DySE™ (Dynamic Store Engine).
3. Instructions on how to install the DySE™ viewer (view.pl).
4. Instructions on how to install and run a DySE™ module (make.pl).
5. Description of DySE™ module templates.

---

Web Server Requirements

DySE™ consists of cgi-bin perl scripts that you install on your linux/unix web server. The scripts cannot be run on your Windows personal computer and are not intended for a novice user. Experience using an FTP program and uploading cgi-bin perl scripts is requiring; perl programming experience is not required.

Important:   Web Server Requirements To be able to use DySE™, your web server must meet the following requirements: linux/unix web server with cgi-bin enabled. FTP enabled so you can upload files using FTP. mod_rewrite (.htaccess) enabled. 128 KB free disk space on web server. Additional disk space required by each DySE™ module database/template files; typically from 2 MB to 124 MB; see Merchant Module Sizes. (optional) Telnet/SSH login access enabled. (optional but recommended) Perl module LWP::Simple installed on your web server (this Perl module is used for internet access). If not installed, DySE™ will still work but auto-downloading of the merchant's datafeed will not be possible and you must manually download the merchant's datafeed file then upload it to your web server.

---

Overview of DySE™

DySE™ (short for "Dynamic Store Engine", pronounced "dice") is a modular system that makes it easy to quickly add products to your website. And because of its modularity, once you learn how to add one merchant, you use basically the same steps to add a different merchant. This modularity significantly reduces the learning curve.

The DySE™ system consists of two parts:

1. DySE™ Merchant Module: A DySE™ module for each merchant. The module consists of two components:

   1. cgi-bin perl script called make.pl that downloads the merchant's datafeed file and creates a product database file of that merchant's products.

   2. Customizable templates used when showing the products to the user.

   You run the make.pl script whenever you want to update the product database, such as once a day/week/month/quarter/etc. (can be run periodically via a cronjob). Each DySE™ module (make.pl script and templates) is designed to work with a particular merchant. For example, the DySE::InstrumentPro module is designed specifically for InstrumentPro.com.

   Note: If you want us to create a DySE™ module for a particular merchant, contact us (see also: Merchant FAQ).

2. DySE™ Viewer: The DySE™ viewer (view.pl) to access the product databases and output results to the user. The view.pl script runs (via mod_rewrite) each time the user accesses your website. The view.pl script is not specific to any merchant; the same view.pl script is used for all merchants. You can have more than one merchant on your website and you only need to install one copy of the view.pl script. And, the templates for each merchant all work the same way thus making it easier to modify/make templates. You can even use a default set of templates so all merchants on your website have a common look-and-feel.

---

Overview of Installing DySE™ System

Installing DySE™ consists of the following steps that are detailed in the rest of this documentation:

1. Request a DySE™ Merchant Key to unlock DySE™ from demo mode. Keys are free.
2. Download, unzip, and install the DySE™ view.pl viewer script.
3. Download, unzip, and install a DySE™ merchant module (make.pl script and template files).
4. Edit .htaccess file so web accesses are redirected to view.pl script via mod_rewrite.
5. Run the make.pl script to download the datafeed and make the database file.
6. Access web pages in your web browser to make sure the installation works properly.
7. If you want to add another merchant, repeat steps 3 through 6.

A video tutorial is available showing how to install DySE™. Click here to view the video tutorial.

---

A Brief Introduction to mod_rewrite

mod_rewrite is a built-in part of Apache web servers. It allows you to redirect one web address to another web address. The user sees the original web address in the Address bar of their web browser but is actually accessing something else on the web server. This redirection is what DySE™ is based on.

For example, if your website has the DySE::InstrumentPro merchant module (module for merchant InstrumentPro.com), when the user accesses /keyboards-midi/casio-lk-45-61-key.html then mod_rewrite internally redirects the web server to instead access /cgi-bin/dyse/view.pl?merch=instrumentpro&dir=&path=keyboards-midi/casio-lk-45-61-key.html which runs view.pl (with the specified parameters) and view.pl dynamically outputs the HTML for the "Keyboards/Midi > Casio LK-45 61 Key" product page. The user thinks they are accessing a .html file but the web server is actually running the view.pl script.

The configuration of mod_rewrite is specified in a .htaccess file (a text file) located in the main directory of your website.

» 2. DySE™ Merchant Module Sizes

Approximate sizes for each DySE™ Merchant Module are shown in the following table. Note: These numbers are approximate and will change when the merchant changes their product datafeed. The make.pl Time varies depending upon server capabilities and current server load.

Some disk space can be freed up by deleting the datafeed files after make.pl has completed. And, if you have multiple websites (on the same server) that use a particular script, one common datafeed file can be shared among them (using linux symbolic links) thus elminating duplicate copies of the datafeed. And, if you are using the same affiliate ID on more than one website, one common datafeed file can be shared among them (using linux symbolic links) thus eliminating duplicate copies of the database file.

» 3. DySE™ Merchant Keys

DySE™ runs in demo mode until you obtain a DySE™ Merchant Key file from us. Keys are free.

CRITICAL:   Demo mode In demo mode, all product links go to the merchant's home page and have no affiliate ID. After you install your DySE™ Merchant Key file, your affiliate ID will be included in your links.

Each key file is for a specific merchant affiliate ID. If you are using several DySE™ Merchant Modules, you will need to obtain a a DySE™ Merchant Key file for each one.

Click here to request a key file

While you are waiting to receive your key file, you can continue with the rest of the installation.

» 4. Download DySE™ view.pl

Important:   Install view.pl only once You only have to install the DySE™ view.pl script once. If you previously installed view.pl with another DySE™ merchant module, skip forward to the section "Download DySE™ Merchant Module".

1. Click here for the DySE™ view.pl download directory.

   The DySE™ view.pl viewer script is available for download as a Windows .zip file (dyse-yymmdd.zip) and as a linux/unix .tar.gz file (dyse-yymmdd.tar.gz).

   Note:   Version Number in filenames The yymmdd will be a 6-digit version number (year, month, date); for example, dyse-050123 indicates DySE™ view.pl version 5.01.23 released on January 23, 2005.

2. Download either the dyse-yymmdd.zip file or the dyse-yymmdd.tar.gz file if you prefer that file format.

   Important:   Download Directory Save the file into a directory that you can remember and can open later (e.g.: My Documents).

Important:   Substitutions In the following instructions, replace yymmdd with the 6-digit version number that appears in the name of the file that you downloaded.

» 5. Install DySE™ view.pl

Important:   Install view.pl only once You only have to install the DySE™ view.pl script once. If you previously installed view.pl with another DySE™ merchant module, skip forward to the section "Download DySE™ Merchant Module".

---

» cgi-bin Directory Structure

Before installing DySE™ view.pl and merchant modules, let's first look at what your cgi-bin directory will look like after the installation is completed:

Everything related to DySE™ goes in the /cgi-bin/dyse directory. The only exception to this is the .htaccess file and that goes in the / main directory of your website.

Inside /cgi-bin/dyse, each merchant module has its own sub-directory. That's also where view.pl goes. So, everything related to DySE::InstrumentPro goes in /cgi-bin/dyse/instrumentpro and everything related to DySE::Calendars goes in /cgi-bin/dyse/calendars and so on for other modules (shown above as merchantA ... merchantD). Each module gets its own directory. DySE™ can support an unlimited number of merchant modules (not just 4 as shown above). The default directory contains default templates.

---

» Installation

The DySE™ view.pl script is available for download as a Windows .zip file, as a Windows .exe self-extracting .zip file, and as a linux/unix .tar.gz file. Both download files have essentially the same contents.

Depending upon whether you want to download and unpack the .zip file (or .exe file) or the .tar.gz file, follow the instructions in one of the following sections:

• Install from .zip File (or .exe Self-Extracting .zip File)
• Install from .tar.gz File

---

» Contents

The .zip file, .exe file, and the .tar.gz file contain the following files:

Item Description Edit view.pl.lnk (in .zip file only). Windows shortcut to open view.pl for editing using Windows Notepad program. htaccess-directory.txt Sample .htaccess file to make store show up at a directory of the website, such as at www.domain.com/shop/ htaccess-homepage.txt Sample .htaccess file to make store show up at the home page of the website, such as at www.domain.com/ view.pl The DySE™ viewer script. default/ Directory containing default templates and graphic files used by those templates. The default templates are optional and are only used by the viewer if a merchant module does not have its own templates installed.

---

» Install from .zip File (or .exe Self-Extracting .zip File)

Important:   Substitutions In the following instructions, replace yymmdd with the 6-digit version number that appears in the name of the file that you downloaded.

1. Depending upon what file you downloaded, unpack either the dyse-yymmdd.zip file or the dyse-yymmdd.exe file:

   • .zip file: Open the dyse-yymmdd.zip file using your compression software (e.g.: CuteZip, WinZip) and unpack it to the folder where the .zip file itself is located (e.g.: My Documents) (or to some other folder that you regularly use for unpacking).

     Note: When unzipping the .zip file, be sure that your compression software is configured to recreate the .zip file's internal directory folder structure when unzipping, otherwise all the files will end up in one directory. For example, in WinZip, select menu item "Action > Extract..." and select the "Use folder names" checkbox option.

   • .exe file: Open the dyse-yymmdd.exe file and click Unzip to unpack it. You can specify the folder where to unpack to (e.g.: My Documents) (or to some other folder that you regularly use for unpacking). Note: The unpacking process will create a "Cusimano.com Scripts" folder that contains the equivalent contents as the.zip file.

2. Open the folder where you just unpacked the .zip or .exe (e.g.: My Documents).

   Note: If you unpacked from the .exe, you will see a "Cusimano.com Scripts" folder; open it.

3. Rename the dyse-yymmdd folder to dyse

4. Run your FTP program.

   Novice User:   FTP program explained FTP stands for "File Transfer Protocol". You use an FTP program to upload files to your web server. This is different than uploading files to your web server using a web-based "control panel" that some hosting companies provide so you can manage files on your web server. The following FTP programs are from 3rd-party companies. Some Windows-based FTP programs are: FTP Desktop CuteFTP WS_FTP more ...   Some Macintosh-based FTP programs are: Fetch Interarchy more...

5. In your FTP program:
   On the web server, go into the cgi-bin directory.
   On your local hard drive, go into the directory where you unpacked the .zip file (e.g.: My Documents).

   Important:   cgi-bin directory is a special; do not create it yourself The cgi-bin directory on your web server (the directory may be called cgi-local or cgi or something similar) is a special directory. If it does not already exist on your web server, do not create it yourself. Ask your hosting company if cgi-bin is enabled on your website account and what the directory is named.

6. Select the dyse directory located on your computer and upload it into the cgi-bin directory.

   Novice User:   Upload a directory and all its contents in one step With most FTP programs, you can upload an entire directory and all its contents by merely selecting the directory (as if you were selecting a single file) and clicking the upload command of your FTP program (as if you were uploading a single file).

   You should now have something like the following file structure on your web server:

   Important:   ASCII vs. Binary Transfer Mode Some FTP programs automatically select ASCII transfer mode for text files (e.g.: .html, .txt) and select binary transfer mode for binary files (e.g.: .gif, .jpg). If binary files are uploaded using ASCII transfer mode, those files will be corrupted and will not work (e.g.: graphics appear damaged). And if ASCII files (specifically .pl files) are uploaded in binary, they will not work (e.g.: 500 Internal Server Error). If you FTP program does not automatically select the appropriate transfer mode, then you should upload everything using binary transfer mode. Then go back and reupload the /cgi-bin/dyse/view.pl file using ASCII transfer mode.

   
   

   Important:   Upload view.pl using ASCII mode If your FTP program does not automatically upload .pl files using ASCII transfer mode, then reupload the view.pl file using ASCII transfer mode. If you're not sure how to select ASCII transer mode, run your FTP program and press F1 and search for help on keyword "ascii". Some FTP programs (such as CuteFTP) automatically select ASCII or BINARY transfer mode depending upon the file type (e.g.: ASCII for .pl and .html text files, and BINARY for .gif and .jpg graphic files).

7. On the web server, go into the dyse directory. Select view.pl and enable all of its execute permissions using the CHMOD command of your FTP program (chmod 755).

   Novice User:   CHMOD explained Try right-clicking on the file and selecting CHMOD or Properties, or press F1 and search for help on keyword "chmod" or "permissions". Your FTP program may display a window with a box that you can type into or with checkboxes that you can click:

8. You can now exit your FTP program.

9. Continue to the section "Test DySE™ view.pl" below to test view.pl.

---

» Install from .tar.gz File

Important:   Substitutions In the following instructions, replace yymmdd with the 6-digit version number that appears in the name of the file that you downloaded.

1. Run your FTP program.

   Novice User:   FTP program explained FTP stands for "File Transfer Protocol". You use an FTP program to upload files to your web server. This is different than uploading files to your web server using a web-based "control panel" that some hosting companies provide so you can manage files on your web server. The following FTP programs are from 3rd-party companies. Some Windows-based FTP programs are: FTP Desktop CuteFTP WS_FTP more ...   Some Macintosh-based FTP programs are: Fetch Interarchy more...

2. In your FTP program:
   On the web server, go into the cgi-bin directory.
   On your local hard drive, go into the directory where you saved the .tar.gz file (e.g.: My Documents).

   Important:   cgi-bin directory is a special; do not create it yourself The cgi-bin directory on your web server (the directory may be called cgi-local or cgi or something similar) is a special directory. If it does not already exist on your web server, do not create it yourself. Ask your hosting company if cgi-bin is enabled on your website account and what the directory is named.

3. Depending upon what FTP program you use, you may need to select binary transfer mode before continuing. If you're not sure what transfer mode your FTP program will use, then just continue to the next step.

   Novice User:   Binary transfer mode In your FTP program, press F1 and search for help on keyword "binary".

4. Upload dyse-yymmdd.tar.gz into your cgi-bin directory.

5. You can now exit your FTP program.

6. Login using Telnet/SSH.

   Novice User:   Telnet/SSH explained Telnet/SSH is a program that you run on your computer that allows you to login to your web server and type commands to your web server, such as to run the make.pl script. PuTTY (for Windows computers) is an excellent Telnet/SSH program and it is free (download puty.exe).

7. Go into the cgi-bin directory (using the cd command). Then type the following command:

   tar  -zxf  dyse-yymmdd.tar.gz

   For example: tar  -zxf  dyse-050123.tar.gz

8. Rename the dyse-yymmdd directory to dyse by typing the following command:

   mv  dyse-yymmdd  dyse

   For example: mv  dyse-050123  dyse

   You should now have something like the following file structure on your web server:

   

9. Change the "owner:group" of the dyse directory (and its contents) by typing the following command:

   Important:   Characters In the following command, the "-R" must be a capital R, and there must be two dashes before "reference=."

   
   

   chown  -R  --reference=.  dyse

10. For security reasons, limit the read/write/execute permissions of the dyse directory and of all the files that it contains, by typing the following command:

    Important:   Characters In the following command, the "-R" must be a capital R

    
    

    chmod  -R  go-w  dyse

11. Enable the execute permissions of the view.pl file by typing the following command:

    chmod  755  dyse/view.pl

12. Continue to the section "Test DySE™ view.pl" below to test view.pl.

» 6. Test DySE™ view.pl

1. Run your web browser. Access view.pl on your web server using the following special test URL (change the domain to your domain name, and change cgi-bin if you use a different directory):

   http://www.domain.com/cgi-bin/dyse/view.pl

   For example: http://www.mydomainname.com/cgi-bin/dyse/view.pl

2. If view.pl is working properly, then you should see something like the following:

   DySE view.pl v5.01.23

   If you see an error then see below.

3. view.pl is working properly.
   Continue to the section "Download DySE™ Merchant Module" below.

---

» Web server generated errors with view.pl

Otherwise, you may see one of the following web server generated errors:

• 500 Internal Server Error:

  1. Run your FTP program and verify that all of the file execute permissions of the file /cgi-bin/dyse/view.pl are set (CHMOD 755).

     

  2. Run your FTP program and examine the permissions of the directory /cgi-bin/dyse (just like a file, a directory also has permissions that you can set). Some servers report an error if a directory is set to CHMOD 777 (all permissions enabled) since that creates a security hole. Change the permissions of the /cgi-bin/dyse directory (from CHMOD 777) to CHMOD 755 (or if that still does not work, then try CHMOD 775).

     

  3. Reupload the view.pl file using ASCII transfer mode of your FTP program.
     And set the execute permissions of view.pl (CHMOD 755).

     Novice User:   ASCII transfer mode explained FTP programs can upload files in either of two ways: ASCII transfer mode or Binary transfer mode. ASCII transfer mode is used to upload files such as text files and .pl files that contain text. Binary transfer mode is used to upload files that contain binary data such as .gif, .jpg, and .tar.gz files. With ASCII transfer mode, carriage return / linefeed (CRLF) characters are translated to what the server expects (Windows/Macintosh and servers handle CRLF characters differently). With binary transfer mode, all data is uploaded exactly as is. If you're not sure how to select ASCII transer mode, run your FTP program and press F1 and search for help on keyword "ascii".

  4. It is assumed that your perl path is /usr/local/bin/perl   If it is different on your web server, then edit view.pl and change the first line to the correct path (you can use the Edit view.pl shortcut found in the .zip file to edit the view.pl file using the Windows Notepad editor). Then reupload the view.pl file and set the execute permissions of view.pl (CHMOD 755).

     Novice User:   Perl path If you're not sure what your perl path is, then ask your hosting company (tip: check your hosting company's online help/FAQ section). On some servers, the perl path is /usr/bin/perl

  5. Some web servers are configured such that cgi-bin script files must have a filename that ends with .cgi rather than the standard .pl ending. If your server requires the .cgi ending then rename view.pl to view.cgi   If you are not sure if your server requires the .cgi ending or the standard .pl ending, ask your hosting company or just go ahead and try renaming view.pl to view.cgi (if still does not work, just rename it back to view.pl).

     Very Important:   If using .cgi then use .cgi throughout If the viewer works when you rename it to view.cgi, then you must keep the following points in mind as you go through the rest of the DySE™ documentation: When you install make.pl (instructions in the next few chapters), you will have to similarly rename make.pl to make.cgi When you install .htaccess (instructions in the next few chapters), you must change the line in the .htaccess where it says view.pl to view.cgi In the rest of the DySE™ instructions where it says to access a URL that ends with view.pl or make.pl, instead access view.cgi or make.cgi, respectively; otherwise you will get a 404 File Not Found error.

  6. If you have access to your web server's error_log file, look at the last few lines to help isolate the problem.

  7. In rare cases: If your server uses Ensim and view.pl was working but has now stopped (and all other .pl files on our server have also stopped), check that the linux system file /var/log/httpd/suexec_log has not exceeded 2GB in size (2GB is the maximum file size that linux allows for any one file). If so, have your system administrator delete the /var/log/httpd/suexec_log file. Note: This file is in the "real" filesystem, it is not in your website's virtual filesystem; therefore, only the system administrator has permission to delete it.

• 404 File Not Found:

  1. Retype the special test URL.

  2. Run your FTP program and verify that view.pl is in the /cgi-bin/dyse directory. If not, move it there.

• Your home page appears:

  • You probably have a .htaccess file that causes redirection to your home page when a file is not found (e.g.: ErrorDocument 404 /). Therefore, handle this error as a "404 File Not Found" error as indicated above.

  • It is also possible that a 500 Internal Server Error has occurred and that your hosting company has configured your server to redirect to the home page when such server errors occur. See 500 Internal Server Error above and try those solutions too.

» 7. Download DySE™ Merchant Module

As indicated in the Introduction to DySE™, DySE™ is a modular system consisting of a viewer (which you downloaded and installed as instructed above) and DySE™ merchant modules.

Listed below are the various DySE™ merchant modules.

DySE™ Merchant Module	Merchant	Download
DySE::AqAM v8.04.13	AquinasAndMore.com	Download
DySE::Audible v7.06.22	Audible.com	Download
DySE::BettyMills v7.06.22	BettyMills.com	Download
DySE::Calendars v8.04.13	Calendars.com	Download
DySE::CFB v7.06.22	CrazyforBargains.com	Download
DySE::GenericGifts v7.06.22	GenericGifts.com	Download
DySE::Hono v7.06.22	HouseOfNutrition.com	Download
DySE::InstrumentPro v7.10.18	InstrumentPro.com	Download
DySE::KimmyShop v7.06.22	KimmyShop.com	Download
DySE::NS v8.04.13	NetShops.com	Download
DySE::Rockler v7.06.22	Rockler.com	Download
DySE::StubHub v7.06.22	StubHub.com	Download
more modules coming soon

1. Click on the "Download" link of the merchant module that you want to download.

   Each DySE™ merchant module is available for download as a Windows .zip file (dyse-merchant-yymmdd.zip) and as a linux/unix .tar.gz file (dyse-merchant-yymmdd.tar.gz).

   Note:   Filename The merchant will be the merchant name and the yymmdd will be a 6-digit number (year, month, date); for example, dyse-instrumentpro-050123 indicates DySE::InstumentPro version 5.01.23 released on January 23, 2005 (InstrumentPro.com DySE™ merchant module).

2. Download either the dyse-merchant-yymmdd.zip file or the dyse-merchant-yymmdd.tar.gz file if you prefer that file format.

   Important:   Download Directory Save the file into a directory that you can remember and can open later, such as My Documents.

Important:   Substitutions In the following instructions, replace merchant and yymmdd with the merchant module name and the 6-digit version number that appears in the name of the file that you downloaded.

» 8. Install DySE™ Merchant Module

The following are generalized instructions on how to install a DySE™ merchant module. Once you learn how to install a merchant module, you will know how to install any DySE™ merchant module. They all work the same way.

Each DySE™ merchant module is available for download as a Windows .zip file, a Windows .exe self-extracting .zip file, and as a linux/unix .tar.gz file. Both download files have essentially the same contents.

Depending upon whether you want to download and unpack the .zip file (or .exe file) or the .tar.gz file, follow the instructions in one of the following sections:

• Install from .zip File (or .exe Self-Extracting .zip File)
• Install from .tar.gz File

---

» Contents

In general, the .zip file, the .exe file, and the .tar.gz file of each DySE™ merchant module contains the following files:

Item Description Edit make.pl.lnk (in .zip file only). Windows shortcut to open make.pl for editing using Windows Notepad program. htaccess-directory.txt Sample .htaccess file to make store show up at a directory of the website, such as at www.domain.com/shop/ htaccess-homepage.txt Sample .htaccess file to make store show up at the home page of the website, such as at www.domain.com/ make.pl The DySE™ make script. You run this script. make2.pl Sub-script used internally by make.pl. You do not run this script. templates/ Directory containing templates and graphic files used by the templates. templates-set1/ templates-set2/ templates-set3/ templates-set4/ templates-set5/ templates-set6/ Additional template sets. Each directory contains templates and graphic files used by those templates. The number of template sets depends upon the particular merchant module. Some merchant modules contain less than 6 template sets.

FAQ:   What does make2.pl do? The make.pl program optionally runs the make2.pl program during the "process category items" section of the make process. It does this to prevent the web server's RAM memory usage from peaking and remaining high (which can happen if a category has a very large number of products). If make2.pl cannot run or is missing, then make.pl internally does the equivalent of what make2.pl would do.

---

» Install from .zip File (or .exe Self-Extracting .zip File)

Important:   Substitutions In the following instructions, replace merchant and yymmdd with the merchant module name and the 6-digit version number that appears in the name of the file that you downloaded.

1. Depending upon what file you downloaded, unpack either the dyse-merchant-yymmdd.zip file or the dyse-merchant-yymmdd.exe file:

   • .zip file: Open the dyse-merchant-yymmdd.zip file using your compression software (e.g.: CuteZip, WinZip) and unpack it to the folder where the .zip file itself is located (e.g.: My Documents) (or to some other folder that you regularly use for unpacking).

     Note: When unzipping the .zip file, be sure that your compression software is configured to recreate the .zip file's internal directory folder structure when unzipping, otherwise all the files will end up in one directory. For example, in WinZip, select menu item "Action > Extract..." and select the "Use folder names" checkbox option.

   • .exe file: Open the dyse-merchant-yymmdd.exe file and click Unzip to unpack it. You can specify the folder where to unpack to (e.g.: My Documents) (or to some other folder that you regularly use for unpacking). Note: The unpacking process will create a "Cusimano.com Scripts" folder that contains the equivalent contents as the.zip file.

2. Open the folder where you just unpacked the .zip or .exe (e.g.: My Documents).

   Note: If you unpacked from the .exe, you will see a "Cusimano.com Scripts" folder; open it.

3. Rename the dyse-merchant-yymmdd folder to merchant (for example, rename dyse-instrumentpro-050123 to instrumentpro).

   Important:   Use all lowercase Use all lowercase. For example, "instrumentpro" will work, while "InstrumentPro" will not work.

4. Run your FTP program.
   On the web server, go into the cgi-bin directory.
   On your local hard drive, go into the directory where you unpacked the .zip file (e.g.: My Documents).

5. Then go into the dyse sub-directory on your web server.

   Note:   /cgi-bin/dyse  Directory You created the /cgi-bin/dyse sub-directory when you installed the DySE™ viewer.

6. Select the merchant directory located on your computer (e.g.: instrumentpro directory) and upload it into the /cgi-bin/dyse sub-directory.

   Novice User:   Upload a directory and all its contents in one step With most FTP programs, you can upload an entire directory and all its contents by merely selecting the directory (as if you were selecting a single file) and clicking the upload command of your FTP program (as if you were uploading a single file).

   You should now have something like the following file structure on your web server: