IWS
supports two types of Web Browsers for use with Thin Clients;
Microsoft Internet Explorer, which supports ActiveX Controls, and
the InduSoft-developed Secure Viewer. Both browsers
can use used concurrently with the Web Server, and the choice of
browser depends on the project requirements. The Secure Viewer is
targeted at plant floor use, while the Internet Explorer browser is
generally more appropriate for desktop applications or where the
Thin Client needs to connect to different project servers.
Configuring Microsoft Internet
Explorer
There is really very little that needs to be done to
configure Microsoft Internet Explorer to be used as a Web Browser
for a Thin Client. The primary items are:
- Make sure ActiveX Controls are enabled.
The settings to control this are generally found in
. Click on the Custom Level button and be sure to allow the
ISSymbol ActiveX Control to be installed, then you can return to a
higher security level. (Otherwise, be sure to install the ISSymbol
ActiveX Control manually).
- Be sure VBScript is supported on your PC. This is
generally not an issue with desktop PCs, but it can be an issue on
Windows Embedded devices. You will need to be sure the VBRun.dll is
installed and registered on your PC.
If you are going to use Microsoft Internet Explorer as
your Web browser for Thin Client projects, you may want to remove
some navigation bars and buttons to reduce the amount of space
taken up by these items.
You can create an icon on the desktop that is a
shortcut to your startup web page on the Web Server. This will take
you to the web page when you click on the icon. Additionally, you
can put this shortcut in the Startup folder so that the Web page is
automatically started whenever the browser is started.
Installing the Secure Viewer
Installing on Windows PC
You will need to install the Secure Viewer from your
CD (or download from the
InduSoft Web site). Follow the following steps:
- Request the Secure Viewer installer from your
software vendor, save it to the designated computer, and start
it.
- Follow the instructions of the installation wizard.
There are only two settings that must be configured during
installation:
- URL: Enter the URL or
filepath of the project file (project_name.app) on the Web
Server.
- Server IP: Enter the
IP address or hostname of the Data Server (a.k.a. TCP/IP
Server).
- Finish the installation and click Finish to close the installer.
The installation wizard automatically installs and
registers the Thin Client ActiveX component (ISSymbol.ocx), so if
you have correctly configured the URL
and Server IP settings, then the
Secure Viewer should be ready to go.
Note: For
additional security of the runtime environment, add a shortcut to
the Secure Viewer (Viewer.exe) to the Startup directory in Windows.
Viewer.exe will install into the \Bin sub-folder where the
IWS program
installs.
Installing on Windows
Embedded
You can also install the Secure Viewer on a Windows
Embedded device, by copying the necessary files to the device's
non-volatile memory. To install Secure Viewer:
- Determine the OS version and processor type of the
Windows Embedded device, and then find the corresponding sub-folder
in the IWS program
directory. For example, for Windows CE 5.0 running on a MIPS
processor, find the […]\InduSoft Web Studio
v7.0\Redist\WinCE
5.0\MIPS\Bin sub-folder.
- Select the following files in the sub-folder:
- IndVkStd.dll
- ISSymbolCE.ocx
- Tagi.bin
- Viewer.exe
- ViewerCfg.exe
- Copy the files to non-volatile memory on the Windows
Embedded device.
- Register the ISSymbol control on the Windows
Embedded device by executing the following command from the
Prompt window:
regsvrce.exe "\ISSymbolPath\ISSymbolCE.ocx"
Example:
regsvrce.exe "\Storage Card\ISSymbolCE.ocx"
- Save the registry settings to keep ISSymbolCE.ocx registered when you reboot the
Windows Embedded device.
Tip: Check the
device manufacturer's documentation for how to save the registry
settings.
- Start the Secure Viewer by running Viewer.exe.
Changing the Secure Viewer
Configuration
After initial installation, the configuration of the
Secure Viewer is saved in the
viewer.ini file, which should be in the same
directory as
Viewer.exe. (This should
be in the
\Bin sub-folder where the
Secure Viewer program is installed). There are two ways to change
the configuration of the Secure Viewer after it has been installed.
First, you can run the Viewer configuration utility (
ViewerCfg.exe) that was also installed.
Note: On
WIndows Vista and Windows 7, the Secure Viewer configuration
utility must have Administrator privileges to run properly. It
should be installed with those privileges by default, but if you
still have problems, then check the file properties for
ViewerCfg.exe and make sure
Run as Administrator is
selected.
The configuration utility provides the following
options:
The second way to change the configuration of the
Secure Viewer is to manually edit the
viewer.ini file with a text editor. The structure
of the file is as follows:
[Options]
nosplash= // Enable (0) or disable (1) the splash window
noprogressbar= // Enable (0) or disable (1) the progress bar
ds1= // Data Server Primary
ds2= // Data Server Secondary
dsp= // Data Server Port
wtg1= // Web Tunneling Gateway Primary
wtg2= // Web Tunneling Gateway Secondary
url= // URL from project file (*.app)
proxyip= // Proxy Address
proxyp= // Proxy Port
ceemul= // Enable (1) or disable (0) CEView emulation
Example
PC with
IWS runtime project (has both Web Server
(NTWebServer or IIS) and Data Server):
- IP Address is 192.168.1.106
- Project name is SecureViewerTest
- Project file is SecureViewerTest.app
Secure Viewer configuration dialog:
- Data Server IP = 192.168.1.106
- TCP Port = 1234
- URL =
http://192.168.1.106//SecureViewerTest.app
Alternatively, you could edit the viewer.ini file:
[Options]
url=http://192.168.1.106//SecureViewerTest.app
noprogressbar=1
ds1=192.168.1.106
nosplash=1
ds2=
dsp=1234
wtg1=
wtg2=
user=Guest
[OEM]
Splash=Splash.bmp //this is a splash screen
Note:
- Your InduSoft Web
Studio runtime license must support a Secure Viewer
(Thin Client) otherwise the connection to the Data Server will be
refused.
- Be sure to put NTWebServer in your project folder
(not Web sub-folder) or point IIS
to your project folder.