Note that HREF has designed the license agreement so that this is perfectly legal for you to do. We wanted you to be able to develop on one machine and deploy on another. You are allowed to run your Hub, at whatever capacity you licensed, on both your development and testing servers.
This example assumes that Machines A and B are connected via LAN. If not, you need a few more duplicated files.
You may install to any drive. We recommend that you install to a directory \ht off the root of one of your drives, to keep the path names relatively short and so that the examples in the documentation will correspond closely to your actual setup.
Here is what you test to make sure you have things set up ok on Machine B:
http://localhost/ -- this tests your web server only http://localhost/scripts/runisa.dll?echo -- this tests your web server mapping to the webhub runner http://localhost/scripts/runisa.dll?hubapp:systeminfo -- this tests the hub and your graphics mappingsAll of the above should work before you make any INI file changes (and thereafter!).
Edit your href.ini file. Find the [webhub] section. Find the entry for IniFileName and set it to the correct location.
IniFileName=\\servername\c$\ht\hubmain.iniIt is important to use UNC naming conventions rather than drive letters when you are sharing files over a LAN. That way the definition will work when webhub runs on machine A or on machine B. You could copy this line into both href.ini files for consistency, just to be 100% sure that webhub was looking in exactly the same place for your setup in either case.
NB: there are times when you want to know which machine your app is running on. The SetupID property is meant for this. [? SetupID]
If you are using Delphi 3 and want to use packages, you will need to copy the whuball.dpl package file (after you build it) from Machine A to Machine B. It needs to be in the same directory as your custom EXEs, or on the DOS PATH.
Set the project output directory to ht\htexe -- on machine B. That way the project will build on the deployment machine. Or, build the EXE locally and just copy it to ht\htexe\ when you are really ready to test.
This directory (ht\htexe) is totally up to you. Your application will connect to the Hub regardless of where it runs from. The only thing is that some demos guess at the location for their database files (e.g. fish store) based on the location of the EXE. Therefore, for the demos, it is best to run them from ht\htexe\.
Your application INI and HTML files need to live on Machine B so that they can be served properly at run time. Your Delphi code can stay on Machine A, in any directory. We recommend that you make your own workspace, e.g. ht\practice\ or something on a totally separate directory tree.
When you set up the .Files list for your project (AppID|Edit Files), use UNC so that the chunk files are referenced on Machine B. For example:
[twebapp.files] pages=\\servername\c$\ht\practice\app1\chunks\pages.htm headfoot=\\servername\c$\ht\htdemos\htmldemo\shared\headfoot.htm
Remember that you have to pre-load your EXE before you test one of its pages. Run the EXE on Machine B, confirm that it shows on the Hub's connected panel, and then test one of its pages. You can always test AppID:INDEX as a quick check on any app. (Replace AppID with your own ID.)
If you have questions about any of these instructions, go to the Technical Support Center and request free support on installation.
Copyright © 1995-1998 HREF Tools Corp. All Rights Reserved.