eQuate Web — File Distribution and Start-up

Two installations

eQuate Web requires two installations on the web server users will browse to: AppDep (the Application Deployment System) and eQuateWeb itself. They can be installed in either order; the recommended sequence is AppDep first, then eQuateWeb.

Install AppDep

1. Run AppDep.exe on the web server.
2. Accept the default location (web root + AppDep) unless you have a strong reason to change it — alternate locations require extra path edits later.

Install eQuateWeb

1. Run eQuateWeb.exe on the web server. The installer creates eQuateWebClient with eQuateData and CGIEXE subdirectories and copies the runtime files.
2. If you installed outside the default web root, edit AppDep's Configuration.xml so the <RelativeURL> tag points at the actual eQuateWebClient path.
3. On an admin workstation that has the eQuate Developer's Edition, run WebLaunchConnections.exe to generate the launch parameters and paste them into Parameters.htm in eQuateWebClient.
4. Copy the user-developed eQuate application data files into eQuateData on the server.

IIS permissions for the CGI

• Mark eQuateWebCGI.exe (in eQuateWebClient\CGIEXE) with Read/Execute permissions.
• Add it to the IIS Web Service Extensions list with status Allowed.

Launching

Users browse to AppDep's launch.asp on the web server. The default launch.asp handles every web-launchable KMSYS product; to target eQuate Web specifically, append the application name as a query string.

http://<YourServer>/AppDep/launch.asp?eQuateWebClient