<< Click to Display Table of Contents >>   Executing WebViewer

During WebViewer installation, files e3web.asp, e3web2.asp, docwrite.asp, docwrite2.asp, and e3downloader.cab become available for user configuration. These files are located on the same directory where Elipse E3 was installed, on the web folder.

•e3web.asp and docwrite.asp: Responsible for loading and starting E3Downloader ActiveX

•e3downloader.cab: ActiveX sent to a client computer that executes the installation of e3webviewer-x86-enu.exe

•e3web2.asp and docwrite2.asp: Responsible for loading and starting WebViewer's ActiveX, displaying the application executed on client computer's Internet Explorer

 

The docwrite2.asp page is initially configured as if E3 Server and the web server are executing on the same computer. However, users can change this page's source code to meet their needs. To do so, change the following line on docwrite2.asp file:

var Domain = getDomain();

 

To the following code:

var Domain = "IIS server's external IP";

 

If users want to inform a valid initial Screen, different from the one configured in the Domain, they must change the Screen parameter on docwrite2.asp file, typing in the Screen_Name value a valid application's Screen name, as in the next example.

<param name="Screen" value="Screen_Name">

 

If users want to inform whether a ping command to a server must occur before trying a connection, they must change the Ping parameter on docwrite2.asp file. Its value can be either "True" or "False", as in the next example.

<param name="Ping" value="True">

 

If this line is omitted, a ping command is executed.

If users want to specify a directory to save Elipse E3 Viewer's cache, they must change the CachePath parameter on docwrite2.asp file. If it is omitted, then Windows' default temporary directory is used, that is, the TEMP environment variable, as in the next example.

<param name="CachePath" value="Cache_Directory">

 

If users want WebViewer to search for other servers on a network if it cannot connect to a server specified in the Domain parameter, they must change the UseServers parameter on docwrite2.asp file. If this parameter is not informed, WebViewer tries to connect only to the server specified by the Domain parameter, which is its standard behavior (a "True" value). Changing this value to "False" only works for servers and WebViewers on the same network, as in the next example.

<param name="UseServers" value="False">

 

WebViewer's configuration to open in Read-Only mode is performed via StartReadOnly parameter, with values "True" or "False", on docwrite2.asp file. If this item does not exist, then it assumes a "False" value, a behavior compatible with previous versions, as in the next example.

<param name="StartReadOnly" value="False">

 

In both cases, this configuration is only effective when opening WebViewer. If this parameter is changed at run time, WebViewer's connection or reconnection is not affected at all.

If users want to navigate to a page other than the default after loading WebViewer, they must change the value attribute of the URLToLoad parameter on docwrite.asp file to a new address, as in the next example.

<param name="URLToLoad" value="URL">

 

If this line is omitted, the e3web2.asp page is then loaded.

If users want to specify whether WebViewer installer must or must not install Control Pad ActiveX from MS Forms, they must change the InstallACP parameter on docwrite.asp file with values "True" or "False", respectively. If this item does not exist, it assumes a "True" value, that is, the ActiveX Control Pad is installed, as in the next example.

<param name="InstallACP" value="True">

 

 

Both servers and WebViewer can execute on the same computer or on different computers. The next topics show how these situations apply.