Enterprise Installation Guide
Welcome to the DreamFactory Enterprise Installation Guide. This manual covers what you need to know to install DreamFactory in the enterprise environment. This guide provides information about terminal server environments, Microsoft Windows SMS servers, and general tips on building any type of custom installer for our product.
This information is helpful for locked down client desktops where DreamFactory is expected to run on a protected volume, or situations where you want to automatically install certain projects on a large number of workstations. An additional benefit of the installation process is the ability to deploy a custom security policy with your projects. Complete security information is provided in the Security White Paper.
Introduction
This manual mainly covers installation on the Microsoft Windows familly of desktop computer operating systems. System administrators with Macintosh networks will also find useful information here that applies to their environment as well. The assets needed to create Macintosh installers are freely available from our web site.
The picture below shows the basic layout of a standard DreamFactory client installation. The DreamFactory folder is located in the Program Files folder at the root of the Windows file system. The pre-built installers available from the Downloads section of our web site will also create files and folders in this location. The DreamFactory directory pictured below can be used as a potential starting point for creating a custom installation image.
At the root level of the DreamFactory folder there is a security policy file named policy.dfsp. This file controls access to the client desktop and can be protected from the end user by password if desired. The dialogs.dfac project file is stored at the root of the Downloads folder. This is where the assets for new projects are stored. The Downloads folder is the security sandbox. Domain sandbox folders and sub-folders are created here, we have included the DreamFactory.com folder and bootfile.dfac project as an example. The developer certificate file certificate.dfdc identifies the author of the project files. The Strings, Help, and Scripts folders contain text files for normal operation of the control or executable. The Plugins folder contains the DLLs to support the various node types.
You will need to re-create this pattern of files and folders on the client desktop. You will also want to install an executable application, ActiveX Control, or Netscape Plug-In for running your projects. You can edit the security policy file to control exactly what permissions the desktop client has to access your file system and corporate networks. You can pre-install your security sandbox and any number of DreamFactory project files if desired.
All of the binary assets needed to create custom installers are included in the DreamFactory Enterprise product distribution. You may want a developer certificate file to identify yourself as the author of the project files, this is available from our sales department. The rest of this guide covers all of the installation issues and provides specific information on creating InstallShield custom installers for Microsoft Windows that can be deployed by SMS server or other means.
Normal Installation
Before going any farther, we should point out that you may not have to do anything at all to install DreamFactory for your company. You can simply create a folder on your Intranet or Internet server, put the DreamFactory developer certificate you received from us in the folder, and put your DreamFactory Projects in there with an HTML page for embedding the project. When you navigate to one of these pages, the ActiveX Control or Netscape Plug-In will be installed, the project will come down to the client, and everything will be initialized and start running. Or you can use one of our pre-built installers for Windows or Macintosh. In this situation a default DreamFactory Security Policy file is created, and that might be just fine for your purposes. There are some reasons why this might not be the ideal situation, or why you might want to customize your installation of DreamFactory in a more explicit way. These issues are discussed below.
First, some companies have "locked down" client desktops. This prevents users from accessing certain files or installing software. DreamFactory is designed to run correctly in a protected environment with no access to the file system, but obviously the client image must be pre-installed in this situation.
You may also want to grant write access to your sandbox folder if your project is quite dynamic and needs to create and delete nodes during runtime. To test if this is the case, open your project file, click the zoom box in the Utility Palette, and check the Locked Mode option. Now test your project, the creation of new nodes will trigger scripting errors. A few scripting changes may be needed to create a locked project that does what you want. An added benefit of this is that locked projects can be opened any number of times (multiple instances) on the client if necessary. The locked project is also incapable of accidently persisting a password or other sensitive information.
Second, some companies will want to install a custom DreamFactory Security Policy. This allows total control of all access to the client desktop, including the file system and network assets. When a standard web based installation occurs, a default policy is created. The Security White Paper documents the default settings for a new policy file. If you need to restrict or enable access to some particular asset, an end user could edit the default policy, but the most desirable situation from a security point of view is to simply install a custom security policy file that enforces the desired client permissions in the first place. The policy can be locked to prevent changes by the end user if desired. There is no way to prevent a determined end user from deleting the policy file or re-installing DreamFactory unless the desktop is locked in some way, see the discussion about this in the previous paragraph. This is exactly the same situation found in a Java or .Net client installation. However, DreamFactory projects offer the additional protection of locking the project file itself with a password, or running the project with all authoring privledges turned off.
To edit your policy file, simply open a project, click the zoom box in the Utility Palette, and click the Security Policy button. Be sure to test your project after changing any policies, because unauthorized file or network access will trigger a scripting error. Lock the security policy if you do not want the end user to change the settings. This information is stored in the policy.dfsp file in the DreamFactory folder, and must be included with your installation package.
Creating An Image
To create a client image for your DreamFactory installation, download or install the project from our web site with Administrative privledges. Run your projects and be sure everything is working. Open the Downloads folder and check to see that the sandbox folders and projects you need are included, and that the sandbox folders and projects you don't need to include have been deleted. You will want to place your DreamFactory developer certificate in your sandbox folder on the client. This file identifies you as the author of the projects. Do not change any of the files in the Help, Scripts, Strings, or Plugins folder. You have now created a disk image of the files that you need to install.
Important Note: To verify your developer certificate type the DialogCertificate() command into the message box or select "developer certificate" from the System Menu. This will display all the information on the certificate.
Some companies have a terminal server environment. In this case, you may simply have to run DreamFactory on each of the servers with administrative privledges, as described above. This makes the client image available to the end users. This situation is similar to a Citrix server; we are compatible with remote desktop systems like Citrix. If there are many terminal servers that require installation, it may be worth your while to create an installation package anyway. The next section covers the creation of MSI installers for Windows SMS Server or other client desktop management and installation systems.
Creating A Custom Installer
The DreamFactory Enterprise product distribution contains all of the files needed to create custom installers. Since all of our client software is freely available, you can use it in any appropriate way for your custom installation package. The DreamFactory Enterprise product distribution also contains three InstallShield X installation script files to be used as templates for building new installers for the DreamFactory Professional stand-alone executable, the DreamFactory Runtime ActiveX Control, or the DreamFactory Runtime Netscape Plug-In. InstallShield X can create Microsoft MSI installers which are the new standard installation system introduced by Microsoft for Windows 2000 and XP systems, but it can also be used on older operating systems in the Windows familly. InstallShield X is available from InstallShield for less than $2000. DreamFactory Software, Inc. can also build custom installers for you with a professional services contract.
First, download the Dreamfactory Enterprise product distribution zip file, and unzip the folder to your C drive. Inside the Enterprise folder there is an All_DF_Assets folder, and three folders with the three example InstallShield scripts. Open each of the example installation scripts and verify that InstallShield X can build the various installation packages. Now we are going to replace various files in the DF_All_Assets folder with files from your client image.
Replace the policy.dfsp file with your new security policy file if desired. Next, add your security sandbox folder with any pre-installed project files and download certificates. We recommend that the project files are unzipped, in other words, that they have not been zipped for internet deployment. If the client desktop is locked DreamFactory will not be able to create and open the unzipped version of the project.
Now go back to InstallShield X and use the Project Assistant to rebuild the installer. On the step titled "Application Files" you will want to modify the downloads folder to include your new sandbox folder and exclude our example folder. On the last step titled "Build Installation" you can create the new installation package. The setup.exe file that is created can be run in "silent mode" for use with an SMS server. You InstallShield X help system has much more information about creating MSI installers. These installation programs should be compatible with other remote administration systems as well.
Important Note: On the "Application Information" screen of the Project Assistant be sure to set the version number field to the latest DreamFactory version number. You can right-click the dfacappl.exe application file and select the "version" tab to see the current version number.
If you need to use some other installation system here are some additional notes about what to do. To install the Dreamfactory Professional stand-alone application, there is nothing needed other than creating the pattern of files and folders described above. The Netscape Plug-in version requires installation of the NPdfac.dll and dfacxpcom.xpt files into the Plugins folder next to your Opera, Firebird, Netscape, or Mozilla browser executable. The ActiveX Control version requires that the dfacactx.ocx and dfacactx.inf files are copied into the Downloaded Program Files folder in the Windows or WINNT folder, then the control must be installed with RegSvr32.exe or whatever control installation system you normally use. The ActiveX Control is self registering, so some additional registry entries are created in the normal places after the control is launched. The appendix below documents every file and registry entry that is installed by our software.
APPENDIX
This apendix documents the changes made to a standard Windows XP System Registry and File System during the installation process. The stand-alone application DreamFactory Professional is covered first, followed by the DreamFactory Runtime ActiveX Control and the DreamFactory Runtime Netscape Plug-In. Changes that occur as a result of any normal installation process, such as updates to system log files, are not documented here. These changes will vary by installation instance and operating system version. Other changes that occur as a side-effect of the installation process, such as updated registry entries for the most recently used application list, are also not discussed. This documentation focuses on system assets created or changed by our software and installation programs.
Stand Alone Application Installation Log
DreamFactory Professional for Windows is a standard executable file which is installed in the Program Files folder. Some registry entries are added to support program icons and to remember application settings. The DreamFactory Runtime ActiveX Control and Netscape Plug-In also install these files, as well as some additional files or registry entries.
New Files
The files below are part of the standard client installation. The files are placed in the DreamFactory folder which is located in the Program Files folder. The policy.dfsp file is the DreamFactory Security Policy, this controls access to the client desktop and can be protected from the end user by password. The dialogs.dfac project file is where the assets for new projects are stored. The Downloads folder is the security sandbox. Domain sandbox folders are added here, we have shown the bootfile.dfac project by example. The developer certificate file certificate.dfdc identifies the author of the project files. The Strings, Help, and Scripts folders contain text files for normal operation of the control or executable. The Plugins folder contains the DLLs to support the various node plugins.
c:\Program Files\DreamFactory\policy.dfsp c:\Program Files\DreamFactory\downloads\dialogs.dfac c:\Program Files\DreamFactory\downloads\dreamfactory.com\bootfile.dfac c:\Program Files\DreamFactory\downloads\dreamfactory.com\certificate.dfdc
Help text files contain the help system for the different node types and the system commands and functions.
c:\Program Files\DreamFactory\help\border.txt c:\Program Files\DreamFactory\help\button.txt c:\Program Files\DreamFactory\help\chart.txt c:\Program Files\DreamFactory\help\desktop.txt c:\Program Files\DreamFactory\help\draw.txt c:\Program Files\DreamFactory\help\guage.txt c:\Program Files\DreamFactory\help\icon.txt c:\Program Files\DreamFactory\help\list.txt c:\Program Files\DreamFactory\help\menu.txt c:\Program Files\DreamFactory\help\movie.txt c:\Program Files\DreamFactory\help\picture.txt c:\Program Files\DreamFactory\help\slider.txt c:\Program Files\DreamFactory\help\sound.txt c:\Program Files\DreamFactory\help\sprite.txt c:\Program Files\DreamFactory\help\system.txt c:\Program Files\DreamFactory\help\table.txt c:\Program Files\DreamFactory\help\text.txt c:\Program Files\DreamFactory\help\window.txt c:\Program Files\DreamFactory\help\xml.txt
Plugin DLL files contain the assets to implement the different node types.
c:\Program Files\DreamFactory\plugins\border.dll c:\Program Files\DreamFactory\plugins\button.dll c:\Program Files\DreamFactory\plugins\chart.dll c:\Program Files\DreamFactory\plugins\desktop.dll c:\Program Files\DreamFactory\plugins\draw.dll c:\Program Files\DreamFactory\plugins\guage.dll c:\Program Files\DreamFactory\plugins\icon.dll c:\Program Files\DreamFactory\plugins\list.dll c:\Program Files\DreamFactory\plugins\menu.dll c:\Program Files\DreamFactory\plugins\movie.dll c:\Program Files\DreamFactory\plugins\picture.dll c:\Program Files\DreamFactory\plugins\slider.dll c:\Program Files\DreamFactory\plugins\sound.dll c:\Program Files\DreamFactory\plugins\sprite.dll c:\Program Files\DreamFactory\plugins\table.dll c:\Program Files\DreamFactory\plugins\text.dll c:\Program Files\DreamFactory\plugins\window.dll c:\Program Files\DreamFactory\plugins\xml.dll
Script text files contain the default scripts for new nodes and projects.
c:\Program Files\DreamFactory\scripts\border.txt c:\Program Files\DreamFactory\scripts\button.txt c:\Program Files\DreamFactory\scripts\chart.txt c:\Program Files\DreamFactory\scripts\desktop.txt c:\Program Files\DreamFactory\scripts\draw.txt c:\Program Files\DreamFactory\scripts\guage.txt c:\Program Files\DreamFactory\scripts\icon.txt c:\Program Files\DreamFactory\scripts\library1.txt c:\Program Files\DreamFactory\scripts\library2.txt c:\Program Files\DreamFactory\scripts\library3.txt c:\Program Files\DreamFactory\scripts\library4.txt c:\Program Files\DreamFactory\scripts\library5.txt c:\Program Files\DreamFactory\scripts\library6.txt c:\Program Files\DreamFactory\scripts\list.txt c:\Program Files\DreamFactory\scripts\menu.txt c:\Program Files\DreamFactory\scripts\movie.txt c:\Program Files\DreamFactory\scripts\picture.txt c:\Program Files\DreamFactory\scripts\project.txt c:\Program Files\DreamFactory\scripts\root.txt c:\Program Files\DreamFactory\scripts\slider.txt c:\Program Files\DreamFactory\scripts\sound.txt c:\Program Files\DreamFactory\scripts\sprite.txt c:\Program Files\DreamFactory\scripts\table.txt c:\Program Files\DreamFactory\scripts\text.txt c:\Program Files\DreamFactory\scripts\window.txt c:\Program Files\DreamFactory\scripts\xml.txt c:\Program Files\DreamFactory\strings\kernalerrors.txt c:\Program Files\DreamFactory\strings\kernalstrings.txt c:\Program Files\DreamFactory\strings\porterrors.txt c:\Program Files\DreamFactory\strings\portstrings.txt
The DreamFactory Professional installation puts the executable file in the DreamFactory folder, and also places some example projects at the root of this folder. These files are not normally included in the installation program for DreamFactory Runtime.
c:\Program Files\DreamFactory\dfacappl.exe c:\Program Files\DreamFactory\bootfile.dfac c:\Program Files\DreamFactory\iowizard.dfac c:\Program Files\DreamFactory\thumbnail.dfac c:\Program Files\DreamFactory\wsdlwizard.dfac
Registry Entries
These registry entries set the application icon and the shell command for opening a new project. The DreamFactory Runtime ActiveX Control and Netscape Plug-In also create these registry entries, additional registry entries are documented below. These registry entries are automatically created by the software, and do not need to be created during the installation process.
HKEY_CLASSES_ROOT\.dfac HKEY_CLASSES_ROOT\.dfcb HKEY_CLASSES_ROOT\.dfdc HKEY_CLASSES_ROOT\.dfsp HKEY_CLASSES_ROOT\DreamFactory.Certificate HKEY_CLASSES_ROOT\DreamFactory.Certificate\DefaultIcon HKEY_CLASSES_ROOT\DreamFactory.Clipboard HKEY_CLASSES_ROOT\DreamFactory.Clipboard\DefaultIcon HKEY_CLASSES_ROOT\DreamFactory.Document HKEY_CLASSES_ROOT\DreamFactory.Document\DefaultIcon HKEY_CLASSES_ROOT\DreamFactory.Security HKEY_CLASSES_ROOT\DreamFactory.Security\DefaultIcon HKEY_CLASSES_ROOT\DreamFactory.Document\shell\Open\command
HKEY_LOCAL_MACHINE\SOFTWARE\Classes\.dfac HKEY_LOCAL_MACHINE\SOFTWARE\Classes\.dfcb HKEY_LOCAL_MACHINE\SOFTWARE\Classes\.dfdc HKEY_LOCAL_MACHINE\SOFTWARE\Classes\.dfsp HKEY_LOCAL_MACHINE\SOFTWARE\Classes\DreamFactory.Certificate HKEY_LOCAL_MACHINE\SOFTWARE\Classes\DreamFactory.Certificate\DefaultIcon HKEY_LOCAL_MACHINE\SOFTWARE\Classes\DreamFactory.Clipboard HKEY_LOCAL_MACHINE\SOFTWARE\Classes\DreamFactory.Clipboard\DefaultIcon HKEY_LOCAL_MACHINE\SOFTWARE\Classes\DreamFactory.Document HKEY_LOCAL_MACHINE\SOFTWARE\Classes\DreamFactory.Document\DefaultIcon HKEY_LOCAL_MACHINE\SOFTWARE\Classes\DreamFactory.Security HKEY_LOCAL_MACHINE\SOFTWARE\Classes\DreamFactory.Security\DefaultIcon HKEY_LOCAL_MACHINE\SOFTWARE\Classes\DreamFactory.Document\shell\Open\command
These registry entries remember various application settings and are updated by the product upon closing if possible. The first two entries remember the default manual file path by file type and the initial window position by window type. They will be added to somewhat as new file types or windows are used.
HKEY_CURRENT_USER\Software\DreamFactory\filepath.dfac HKEY_CURRENT_USER\Software\DreamFactory\windpos.debg HKEY_CURRENT_USER\Software\DreamFactory\number.autowrap HKEY_CURRENT_USER\Software\DreamFactory\number.defaultahead HKEY_CURRENT_USER\Software\DreamFactory\number.defaultcolor HKEY_CURRENT_USER\Software\DreamFactory\number.defaultslang HKEY_CURRENT_USER\Software\DreamFactory\number.entireword HKEY_CURRENT_USER\Software\DreamFactory\number.sensitive HKEY_CURRENT_USER\Software\DreamFactory\string.in1 HKEY_CURRENT_USER\Software\DreamFactory\string.in10 HKEY_CURRENT_USER\Software\DreamFactory\string.in11 HKEY_CURRENT_USER\Software\DreamFactory\string.in12 HKEY_CURRENT_USER\Software\DreamFactory\string.in13 HKEY_CURRENT_USER\Software\DreamFactory\string.in14 HKEY_CURRENT_USER\Software\DreamFactory\string.in15 HKEY_CURRENT_USER\Software\DreamFactory\string.in16 HKEY_CURRENT_USER\Software\DreamFactory\string.in2 HKEY_CURRENT_USER\Software\DreamFactory\string.in3 HKEY_CURRENT_USER\Software\DreamFactory\string.in4 HKEY_CURRENT_USER\Software\DreamFactory\string.in5 HKEY_CURRENT_USER\Software\DreamFactory\string.in6 HKEY_CURRENT_USER\Software\DreamFactory\string.in7 HKEY_CURRENT_USER\Software\DreamFactory\string.in8 HKEY_CURRENT_USER\Software\DreamFactory\string.in9 HKEY_CURRENT_USER\Software\DreamFactory\string.messtarget HKEY_CURRENT_USER\Software\DreamFactory\string.out1 HKEY_CURRENT_USER\Software\DreamFactory\string.out10 HKEY_CURRENT_USER\Software\DreamFactory\string.out11 HKEY_CURRENT_USER\Software\DreamFactory\string.out12 HKEY_CURRENT_USER\Software\DreamFactory\string.out13 HKEY_CURRENT_USER\Software\DreamFactory\string.out14 HKEY_CURRENT_USER\Software\DreamFactory\string.out15 HKEY_CURRENT_USER\Software\DreamFactory\string.out16 HKEY_CURRENT_USER\Software\DreamFactory\string.out2 HKEY_CURRENT_USER\Software\DreamFactory\string.out3 HKEY_CURRENT_USER\Software\DreamFactory\string.out4 HKEY_CURRENT_USER\Software\DreamFactory\string.out5 HKEY_CURRENT_USER\Software\DreamFactory\string.out6 HKEY_CURRENT_USER\Software\DreamFactory\string.out7 HKEY_CURRENT_USER\Software\DreamFactory\string.out8 HKEY_CURRENT_USER\Software\DreamFactory\string.out9 HKEY_CURRENT_USER\Software\DreamFactory\string.pouchpath HKEY_CURRENT_USER\Software\DreamFactory\string.textreplace HKEY_CURRENT_USER\Software\DreamFactory\string.textsearch HKEY_CURRENT_USER\Software\DreamFactory\string.version
The first registry key element may be different on your system depending on user codes.
HKEY_USERS\S-1-5-21-1060284298-1935655697-854245398-1004\Software\DreamFactory\filepath.dfac HKEY_USERS\S-1-5-21-1060284298-1935655697-854245398-1004\Software\DreamFactory\windpos.debg HKEY_USERS\S-1-5-21-1060284298-1935655697-854245398-1004\Software\DreamFactory\number.autowrap HKEY_USERS\S-1-5-21-1060284298-1935655697-854245398-1004\Software\DreamFactory\number.defaultahead HKEY_USERS\S-1-5-21-1060284298-1935655697-854245398-1004\Software\DreamFactory\number.defaultcolor HKEY_USERS\S-1-5-21-1060284298-1935655697-854245398-1004\Software\DreamFactory\number.defaultslang HKEY_USERS\S-1-5-21-1060284298-1935655697-854245398-1004\Software\DreamFactory\number.entireword HKEY_USERS\S-1-5-21-1060284298-1935655697-854245398-1004\Software\DreamFactory\number.sensitive HKEY_USERS\S-1-5-21-1060284298-1935655697-854245398-1004\Software\DreamFactory\string.in1 HKEY_USERS\S-1-5-21-1060284298-1935655697-854245398-1004\Software\DreamFactory\string.in10 HKEY_USERS\S-1-5-21-1060284298-1935655697-854245398-1004\Software\DreamFactory\string.in1111 HKEY_USERS\S-1-5-21-1060284298-1935655697-854245398-1004\Software\DreamFactory\string.in12 HKEY_USERS\S-1-5-21-1060284298-1935655697-854245398-1004\Software\DreamFactory\string.in13 HKEY_USERS\S-1-5-21-1060284298-1935655697-854245398-1004\Software\DreamFactory\string.in14 HKEY_USERS\S-1-5-21-1060284298-1935655697-854245398-1004\Software\DreamFactory\string.in15 HKEY_USERS\S-1-5-21-1060284298-1935655697-854245398-1004\Software\DreamFactory\string.in16 HKEY_USERS\S-1-5-21-1060284298-1935655697-854245398-1004\Software\DreamFactory\string.in2 HKEY_USERS\S-1-5-21-1060284298-1935655697-854245398-1004\Software\DreamFactory\string.in3 HKEY_USERS\S-1-5-21-1060284298-1935655697-854245398-1004\Software\DreamFactory\string.in4 HKEY_USERS\S-1-5-21-1060284298-1935655697-854245398-1004\Software\DreamFactory\string.in5 HKEY_USERS\S-1-5-21-1060284298-1935655697-854245398-1004\Software\DreamFactory\string.in6 HKEY_USERS\S-1-5-21-1060284298-1935655697-854245398-1004\Software\DreamFactory\string.in7 HKEY_USERS\S-1-5-21-1060284298-1935655697-854245398-1004\Software\DreamFactory\string.in8 HKEY_USERS\S-1-5-21-1060284298-1935655697-854245398-1004\Software\DreamFactory\string.in9 HKEY_USERS\S-1-5-21-1060284298-1935655697-854245398-1004\Software\DreamFactory\string.messtarget HKEY_USERS\S-1-5-21-1060284298-1935655697-854245398-1004\Software\DreamFactory\string.out1 HKEY_USERS\S-1-5-21-1060284298-1935655697-854245398-1004\Software\DreamFactory\string.out10 HKEY_USERS\S-1-5-21-1060284298-1935655697-854245398-1004\Software\DreamFactory\string.out11 HKEY_USERS\S-1-5-21-1060284298-1935655697-854245398-1004\Software\DreamFactory\string.out12 HKEY_USERS\S-1-5-21-1060284298-1935655697-854245398-1004\Software\DreamFactory\string.out13 HKEY_USERS\S-1-5-21-1060284298-1935655697-854245398-1004\Software\DreamFactory\string.out14 HKEY_USERS\S-1-5-21-1060284298-1935655697-854245398-1004\Software\DreamFactory\string.out15 HKEY_USERS\S-1-5-21-1060284298-1935655697-854245398-1004\Software\DreamFactory\string.out16 HKEY_USERS\S-1-5-21-1060284298-1935655697-854245398-1004\Software\DreamFactory\string.out2\out2 HKEY_USERS\S-1-5-21-1060284298-1935655697-854245398-1004\Software\DreamFactory\string.out3\out3 HKEY_USERS\S-1-5-21-1060284298-1935655697-854245398-1004\Software\DreamFactory\string.out4\out4 HKEY_USERS\S-1-5-21-1060284298-1935655697-854245398-1004\Software\DreamFactory\string.out5\out5 HKEY_USERS\S-1-5-21-1060284298-1935655697-854245398-1004\Software\DreamFactory\string.out6\out6 HKEY_USERS\S-1-5-21-1060284298-1935655697-854245398-1004\Software\DreamFactory\string.out7\out7 HKEY_USERS\S-1-5-21-1060284298-1935655697-854245398-1004\Software\DreamFactory\string.out8\out8 HKEY_USERS\S-1-5-21-1060284298-1935655697-854245398-1004\Software\DreamFactory\string.out9\out9 HKEY_USERS\S-1-5-21-1060284298-1935655697-854245398-1004\Software\DreamFactory\string.pouchpath HKEY_USERS\S-1-5-21-1060284298-1935655697-854245398-1004\Software\DreamFactory\string.textreplace HKEY_USERS\S-1-5-21-1060284298-1935655697-854245398-1004\Software\DreamFactory\string.textsearch HKEY_USERS\S-1-5-21-1060284298-1935655697-854245398-1004\Software\DreamFactory\string.version
Netscape Plug-In Installation Log
DreamFactory Runtime for Windows Netscape Plug-In is a standard Netscape Plug-In which is installed in the Plugins folder for Netscape, Mozilla, Firebird, or Opera. Additional files including the security sandbox are installed in the DreamFactory folder located in the Program Files folder, these are the same as documented for DreamFactory Professional, above. The registry entries for DreamFactory Professional above are also created by DreamFactory Runtime.
New Files
The Netscape Plugin file NPdfac.dll and the Live Connect file dfacxpcom.xpt are placed in the Plugins folder which is located in the Netscape (or Opera, Mozilla, etc.) folder which is located in the Program Files folder. The list of new files follows, below:
c:\Program Files\Netscape\Netscape\Plugins\NPdfac.dll c:\Program Files\Netscape\Netscape\Plugins\dfacxpcom.xpt
c:\Program Files\Opera\Plugins\NPdfac.dll c:\Program Files\Opera\Plugins\dfacxpcom.xpt
c:\Program Files\Mozilla Firefox\Plugins\NPdfac.dll c:\Program Files\Mozilla Firefox\Plugins\dfacxpcom.xpt
Registry Entries
The Netscape Plug-in does not create any additional registry entries other than the ones mentioned for DreamFactory Professional, above.
ActiveX Control Installation Log
DreamFactory Runtime for Windows Internet Explorer is a standard, self-registering ActiveX Control installed in the Downloaded Program Files folder, which is located in the Windows (or WINNT) folder. Additional files including the security sandbox are installed in the DreamFactory folder located in the Program Files folder, these are the same as documented for DreamFactory Professional, above. The registry entries for DreamFactory Professional above are also used by DreamFactory Runtime.
New Files
The ActiveX Control and INF file are placed in the Downloaded Program Files folder which is located in the Windows folder. The list of new files follows, below:
c:\Windows\Downloaded Program Files\dfacactx.ocx c:\Windows\Downloaded Program Files\dfacactx.inf
New Registry Entries
The ActiveX Control installation process sets certain registry entries and then calls RegSvr32.exe which creates additonal entries, finally calling the control itself which creates more entries during the auto-registration process. The example InstallShield projects sets a small number of initial entries and lets the Windows installation system handle everything else. This is similar to how the browser registers an ActiveX Control during runtime. The first set of registry entries shows all the entries the change after installation, and the second set shows the entries created by the installer.
HKEY_CLASSES_ROOT\.dfac
HKEY_CLASSES_ROOT\MIME\Database\Content Type\application/dreamfactory
HKEY_CLASSES_ROOT\CLSID\{226906C8-B911-11D5-82A3-0000F81A655B}
HKEY_CLASSES_ROOT\CLSID\{226906C8-B911-11D5-82A3-0000F81A655B}\Control
HKEY_CLASSES_ROOT\CLSID\{226906C8-B911-11D5-82A3-0000F81A655B}\InprocServer32
HKEY_CLASSES_ROOT\CLSID\{226906C8-B911-11D5-82A3-0000F81A655B}\MiscStatus
HKEY_CLASSES_ROOT\CLSID\{226906C8-B911-11D5-82A3-0000F81A655B}\MiscStatus\1
HKEY_CLASSES_ROOT\CLSID\{226906C8-B911-11D5-82A3-0000F81A655B}\ProgID
HKEY_CLASSES_ROOT\CLSID\{226906C8-B911-11D5-82A3-0000F81A655B}\ToolboxBitmap32
HKEY_CLASSES_ROOT\CLSID\{226906C8-B911-11D5-82A3-0000F81A655B}\TypeLib
HKEY_CLASSES_ROOT\CLSID\{226906C8-B911-11D5-82A3-0000F81A655B}\Version
HKEY_CLASSES_ROOT\CLSID\{226906C9-B911-11D5-82A3-0000F81A655B}
HKEY_CLASSES_ROOT\CLSID\{226906C9-B911-11D5-82A3-0000F81A655B}\InprocServer32
HKEY_CLASSES_ROOT\Interface\{226906C7-B911-11D5-82A3-0000F81A655B}\TypeLib
HKEY_CLASSES_ROOT\Interface\{226906C6-B911-11D5-82A3-0000F81A655B}
HKEY_CLASSES_ROOT\Interface\{226906C6-B911-11D5-82A3-0000F81A655B}\ProxyStubClsid
HKEY_CLASSES_ROOT\Interface\{226906C6-B911-11D5-82A3-0000F81A655B}\ProxyStubClsid32
HKEY_CLASSES_ROOT\Interface\{226906C6-B911-11D5-82A3-0000F81A655B}\TypeLib
HKEY_CLASSES_ROOT\Interface\{226906C7-B911-11D5-82A3-0000F81A655B}
HKEY_CLASSES_ROOT\Interface\{226906C7-B911-11D5-82A3-0000F81A655B}\ProxyStubClsid
HKEY_CLASSES_ROOT\Interface\{226906C7-B911-11D5-82A3-0000F81A655B}\ProxyStubClsid32
HKEY_CLASSES_ROOT\Interface\{226906C7-B911-11D5-82A3-0000F81A655B}\TypeLib
HKEY_CLASSES_ROOT\TypeLib\{226906C5-B911-11D5-82A3-0000F81A655B}\1.0
HKEY_CLASSES_ROOT\TypeLib\{226906C5-B911-11D5-82A3-0000F81A655B}\1.0\0\win32
HKEY_CLASSES_ROOT\TypeLib\{226906C5-B911-11D5-82A3-0000F81A655B}\1.0\FLAGS
HKEY_CLASSES_ROOT\TypeLib\{226906C5-B911-11D5-82A3-0000F81A655B}\1.0\HELPDIR
HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{226906C8-B911-11D5-82A3-0000F81A655B}
HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{226906C8-B911-11D5-82A3-0000F81A655B}\Control
HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{226906C8-B911-11D5-82A3-0000F81A655B}\InprocServer32
HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{226906C8-B911-11D5-82A3-0000F81A655B}\MiscStatus
HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{226906C8-B911-11D5-82A3-0000F81A655B}\MiscStatus\1
HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{226906C8-B911-11D5-82A3-0000F81A655B}\ProgID
HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{226906C8-B911-11D5-82A3-0000F81A655B}\ToolboxBitmap32
HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{226906C8-B911-11D5-82A3-0000F81A655B}\TypeLib
HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{226906C8-B911-11D5-82A3-0000F81A655B}\Version
HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{226906C9-B911-11D5-82A3-0000F81A655B}
HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{226906C9-B911-11D5-82A3-0000F81A655B}\InprocServer32
HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Interface\{226906C6-B911-11D5-82A3-0000F81A655B}
HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Interface\{226906C6-B911-11D5-82A3-0000F81A655B}\ProxyStubClsid
HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Interface\{226906C6-B911-11D5-82A3-0000F81A655B}\ProxyStubClsid32
HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Interface\{226906C6-B911-11D5-82A3-0000F81A655B}\TypeLib
HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Interface\{226906C7-B911-11D5-82A3-0000F81A655B}
HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Interface\{226906C7-B911-11D5-82A3-0000F81A655B}\ProxyStubClsid
HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Interface\{226906C7-B911-11D5-82A3-0000F81A655B}\ProxyStubClsid32
HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Interface\{226906C7-B911-11D5-82A3-0000F81A655B}\TypeLib
HKEY_LOCAL_MACHINE\SOFTWARE\Classes\TypeLib\{226906C5-B911-11D5-82A3-0000F81A655B}\1.0
HKEY_LOCAL_MACHINE\SOFTWARE\Classes\TypeLib\{226906C5-B911-11D5-82A3-0000F81A655B}\1.0\0\win32
HKEY_LOCAL_MACHINE\SOFTWARE\Classes\TypeLib\{226906C5-B911-11D5-82A3-0000F81A655B}\1.0\FLAGS
HKEY_LOCAL_MACHINE\SOFTWARE\Classes\TypeLib\{226906C5-B911-11D5-82A3-0000F81A655B}\1.0\HELPDIR
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\ModuleUsage\C:/WINDOWS/Downloaded Program Files/dfacactx.ocx
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\ModuleUsage\C:/WINDOWS/System32/mfc42.dll
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\ModuleUsage\C:/WINDOWS/System32/msvcrt.dll
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\ModuleUsage\C:/WINDOWS/System32/olepro32.dll
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SharedDLLs
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Code Store Database\Distribution Units\{226906C8-B911-11D5-82A3-0000F81A655B}\Contains\Files
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Code Store Database\Distribution Units\{226906C8-B911-11D5-82A3-0000F81A655B}\DownloadInformation
HKEY_LOCAL_MACHINE\SOFTWARE\Classes\.dfac
HKEY_LOCAL_MACHINE\SOFTWARE\Classes\MIME\Database\Content Type\application/dreamfactory
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Code Store Database\Distribution Units\{226906C8-B911-11D5-82A3-0000F81A655B}\InstalledVersion
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Code Store Database\Distribution Units\{226906C8-B911-11D5-82A3-0000F81A655B}
HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{226906C8-B911-11D5-82A3-0000F81A655B}\InprocServer32
HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Interface\{226906C7-B911-11D5-82A3-0000F81A655B}\TypeLib
The InstallShield Installer sets the following registry entries prior to installation.
HKEY_CLASSES_ROOT\Component Categories
HKEY_CLASSES_ROOT\Component Categories\{7DD95802-9882-11CF-9FA9-00AA006C42C4}
HKEY_CLASSES_ROOT\Component Categories\{7DD95801-9882-11CF-9FA9-00AA006C42C4}
HKEY_CLASSES_ROOT\MIME\DataBase
HKEY_CLASSES_ROOT\MIME\DataBase\Content Type
HKEY_CLASSES_ROOT\MIME\DataBase\Content Type\application/dreamfactory
HKEY_CLASSES_ROOT\CLSID\{226906C8-B911-11D5-82A3-0000F81A655B}
HKEY_CLASSES_ROOT\CLSID\{226906C8-B911-11D5-82A3-0000F81A655B}\Version
HKEY_CLASSES_ROOT\CLSID\{226906C8-B911-11D5-82A3-0000F81A655B}\TypeLib
HKEY_CLASSES_ROOT\CLSID\{226906C8-B911-11D5-82A3-0000F81A655B}\ToolboxBitmap32
HKEY_CLASSES_ROOT\CLSID\{226906C8-B911-11D5-82A3-0000F81A655B}\MiscStatus
HKEY_CLASSES_ROOT\CLSID\{226906C8-B911-11D5-82A3-0000F81A655B}\MiscStatus\1
HKEY_CLASSES_ROOT\CLSID\{226906C8-B911-11D5-82A3-0000F81A655B}\InprocServer32
HKEY_CLASSES_ROOT\CLSID\{226906C8-B911-11D5-82A3-0000F81A655B}\Implemented Categories
HKEY_CLASSES_ROOT\CLSID\{226906C8-B911-11D5-82A3-0000F81A655B}\Implemented Categories\{7DD95802-9882-11CF-9FA9-00AA006C42C4}
HKEY_CLASSES_ROOT\CLSID\{226906C8-B911-11D5-82A3-0000F81A655B}\Implemented Categories\{7DD95801-9882-11CF-9FA9-00AA006C42C4}
HKEY_CLASSES_ROOT\CLSID\{226906C8-B911-11D5-82A3-0000F81A655B}\EnableFullPage
HKEY_CLASSES_ROOT\CLSID\{226906C8-B911-11D5-82A3-0000F81A655B}\EnableFullPage\.dfac
HKEY_CLASSES_ROOT\CLSID\{226906C8-B911-11D5-82A3-0000F81A655B}\Control