E3Web.asp and DocWrite.asp Files

<< Click to Display Table of Contents >>

 

E3Web.asp and DocWrite.asp Files

Files E3Web.asp and DocWrite.asp are intended to load and start E3Downloader's ActiveX. The e3downloader.cab file is an ActiveX sent to the client computer and executes the installation of the e3webviewer-x86-enu.exe file. Files e3web2.asp and docwrite2.asp are intended to load and start WebViewer's ActiveX that shows the application executing on Internet Explorer's computer. They are all available for user configuration. These files are located on the directory where Elipse E3 was installed, on the web folder.

The docwrite2.asp page is configured considering that a E3 Server is executing on the same computer of the web server. However, users can change the source code of this page to meet any configuration. For more information, please check Elipse E3 User's Manual. Users can edit the docwrite2.asp file to include some settings. If users want to allow informing a valid initial Screen, different from the one configured in the Domain, they must change the next line, replacing Screen_name with a valid Screen name in the application.

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

 

If users want to inform the need to execute a ping command to the server before trying to connect, they must change the next line. Its value can be True or False.

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

 

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

To specify a directory to store Elipse E3 Viewer's cache, users must change the CachePath parameter on docwrite2.asp file. If it is not specified, a system's 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 the network if it cannot connect to the server specified in the Domain parameter, they must change the UseServers parameter on the docwrite2.asp file. If this parameter is not informed, WebViewer only tries to connect to the server specified in the Domain parameter, which is WebViewer's default 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">

 

The configuration of WebViewer to open in Read-Only mode is performed in the StartReadOnly parameter, according to the next example.

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

 

In both cases, this configuration is only effective when opening WebViewer. If this parameter changes during execution, WebViewer's connection or reconnection is not affected.

To navigate to a page different from the default after loading WebViewer, users must change the value attribute of the URLToLoad parameter on the docwrite.asp file to another address, as in the next example.

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

 

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

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

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

 

NOTE

If the InstallACP parameter is configured as "False", application Screens that use MS Forms may present errors while loading, if MS Forms objects were not previously installed by other applications, such as Microsoft Office.

Was this page useful?