Setup Steps: Install Program Files

1. Create an empty test IIS website on your server or workstation This website will be used in the following steps when peforming an e-commerce and E-Business framework installation.

If you are using Windows 2003 Server you must include the following settings in your IIS website:

  1. User the [configuration] settings for the website, enable:
  2. Under Web Server Extensions, eanable:

2. Run the installation program by executing the executable file which you downloaded SendSafe.exe or SendSafePlus.exe. It is recommended that the robot be installed on the web server. This is not required, but does make the installation a easier for a first time install.

The sendsafe files are not locked to a specific computer so it is possible to install the files on your workstation then copy them to the server (via FTP).

3. Follow the instructions provided by the installation program. Once installation is complete the directories and files will have been setup on your computer.

4. Register the DDLs listed below on your server.
Use the batch file: regRequiredDLLs.bat (supplied) or manually register using this syntax: regsvr32 nameofdll.dll

The typical location for these files is the same directory as the SendSafe robot. This is the default directory into which these *.dll files are installed. If this location is acceptable then all you do is execute the batch file: regRequiredDLLs.bat. The DLLs which must be registered are listed below (these must be registered because they are also accessed via COM by ASP server-side code). The other DLLs found in this directory do not need to be registered but must be located in the same directory OR PATH as the jsof.exe executable.

DLLs requiring registration:

  1. SendSafeReadBinary.dll
  2. emsmtp.dll
  3. empop3.dll
  4. emmsg.dll
  5. emimap4.dll
  6. emmailstore.dll
  7. emprint.dll

DLLs which cannot be registered:

  1. pfpro.dll

DLLs which should not be registered:

  1. ibizpay2.dll
  2. ipwssl6.dll

NOTE: If you will be running the DLL object on a server, it is important that the object be installed and registered in a directory with proper access permissions. If you are using the DLL objects in an IIS application, the security context of the objects will be inherited from the IIS login account. All anonymous access to an IIS web server is logged in under an anonymous login account. When IIS is installed, it creates an NT user account with the name IUSR_SERVER, where SERVER is the computer name of the server. This is the account which specifies the rights for anonymous users accessing the server. If a user is logged on to a specific account, that is they are not accessing the web server anonymously, then the security context of the objects will be inherited from that account. In order for the web server to load the object, it must be registered in a directory in which the security context, has read and execute access.

NOTE: If you are running the objects in an IIS application, which is set to run in its own address space, the security rights for the IWAM_SERVER_NAME account will be used instead of the IUSR_SERVER_NAME account for anonymous access.

Manual DLL setup (i.e. not using the regRequiredDLLs.bat)

The basic syntax for registering a DLL is: regsvr32 /s SendSafeReadBinary.dll.

To replace or upgrade a DLL requires either removal plus replacement or redirection. The tool Oleview.exe will list all registered DLLs (C:\Program Files\Microsoft Visual Studio\COMMON\Tools). The tool regsvr32.exe can be used to deregister a DLL or a redirection file can be used; see below for details.

The SendSafe DDLs will be found under the "ALL" node in the COM tree.

Applications can depend on a specific version of a shared DLL and start to fail if another application is installed with a newer or older version of the same DLL. There are two ways to ensure that your application uses the correct DLL: DLL redirection and side-by-side components. Developers and administrators should use DLL redirection for existing applications, because it does not require any changes to the application. If you are creating a new application or updating an application and want to isolate your application from potential problems, create a side-by-side component. To use DLL redirection, create a redirection file for your application. The redirection file must be named as follows: App_name.local. For example, if the application name is Editor.exe, the redirection file should be named Editor.exe.local. You must install the .local file in the application directory. You must also install the DLLs in the application directory. The contents of a redirection file are ignored, but its presence causes Windows to check the application directory first whenever it loads a DLL, regardless of the path specified to LoadLibrary or LoadLibraryEx. If the DLL is not found in the application directory, then these functions use their usual search order. For example, if the application c:\myapp\myapp.exe calls LoadLibrary using the following path: "c:\program files\common files\system\mydll.dll"

And, if both c:\myapp\myapp.exe.local and c:\myapp\mydll.dll exist, LoadLibrary loads c:\myapp\mydll.dll. Otherwise, LoadLibrary loads c:\program files\common files\system\mydll.dll. Alternatively, if a directory named c:\myapp\myapp.exe.local exists and contains mydll.dll, LoadLibrary loads c:\myapp\myapp.exe.local\mydll.dll.

5. Setup E-Business framework files.
If you purchased the E-Business framework, you will find a directory labeled "E-Business framework" in the folder into which SendSafe was installed. This directory contains an entire working website skeleton. The key E-Business framework ASP files are located in the subdirectory named "Includes." You should perform the following steps before continuing with the SendSafe setup.

  1. Copy the global.inc.asa files
    From: \E-Business framework\SendSafe\global.inc.asa
    To: \ServerSideCode\asp\SendSafe\global.inc.asa
  2. Copy the entire "E-Business framework" directory to the test website you created earlier.

6. Install ImageMagick.
ImageMagick is an advanced image processing system which is distributed free under a GPL license. ImageMagick is used by SendSafe to resize and process image files. Since a very wide range of commercial software systems use ImageMagick, you may already of ImageMagick installed on your computer.

Please see the ImageMagick website for additional information and installation specifics.

A copy of the 16 bit DLL version of ImageMagick in included with this SendSafe installation. The ImageMagick install can be found in the the subdirectory named "ImageMagick" within the SendSafe root installation directory. Please install ImageMagick Now by executing the installation file found in the "ImageMagick" subdirectory (<SendSafe installation root>\ImageMagick\ImageMagick-6.3.0-0-Q16-windows-dll.exe).

To perform a manual installation of ImageMagick follow these steps:

  1. Extract the ImageMagick files from the installation file to a temporary location
  2. Copy the installation files to the desired location
  3. Set the environment variables PATH to root installation directory of ImageMagick (same as MAGICK_HOME below). Be sure to set the ImageMagick path before all other entires (the imagemagick file convert.exe has the same name as a Windows system untility)
  4. Set other environment variable MAGICK_HOME to root installation directory of ImageMagick
    (set MAGICK_HOME = "C:\Program Files\ImageMagick-6.3.0-Q16")
  5. Setup the registry
    (see the file: "<SendSafe installation root>\ImageMagick\ImageMagic Registry Settings.reg")
  6. Type at a command prompt: C:>convert -version
    You should see:
    Version: ImageMagick 6.3.0 10/14/06 Q16 http://www.imagemagick.org
    Copyright: Copyright (C) 1999-2006 ImageMagick Studio LLC