1. Web@aGlance Installation
Smooth sailing...

2. Verify network - TCP/IP Know your data source
BEFORE Installation
Acquire software:
Web server, MS Frontpage, AAG/OPC data source
Verify network - TCP/IP
Client host - Server host
Know your data source
Install & verify Web server
Install & verify Frontpage
8/23/2019

3. Acquire Software Webserver - which one??
Internet Information Server (4.0)
Personal Web Server
sources:
Microsoft website
NT 4.0 Options Pack
installation order significant for certain SP’s
Essentially, you can expect good performance with IIS 4.0 and greater. On NT 4.0 Server, it's referred to as IIS On NT Workstation, it's still IIS 4.0, but commonly referred to as Personal Web Server. MS Frontpage ships with a webserver called "Personal Web Server", but it's different and will cause pain to those who try!
We've tested and passed V2.5 for both the Windows 2000 Professional
and Server editions.
Our testing of the latest Waag covered the areas of installation, compatibility with the IIS V5 web server, and compatibility with the IE5 browser and Java Runtime shipped with Windows We have no known outstanding problems
in any of these areas.
8/23/2019

4. Acquire Software Microsoft Frontpage 98, 2000 @aGlance/OPC Data Source
Do NOT install FP Personal Web server
@aGlance/OPC Data Source
available from Emation or PMIS vendor
8/23/2019

5. Verify Network TCP/IP - IP name resolution DNS? DHCP? Hosts?
PING by IP name client server
Additionally FTP or Telnet verifies UDP connection
communicates with datasources (a course in itself!). @aGlance uses ONC/RPC middleware over TCP/IP. Key to communication is IP name resolution. In order to and TCP/IP must be properly configured on both client and server, and mutual IP name resolution must be possible.
8/23/2019

6. Knowing Data Source @aGlance or OPC data server
same or different host/platform?
Server security - permissions?
Read, write, shutdown? What/how implemented in data server?
Methods (server callbacks) supported
Types of data?
Current - usually straight forward
Server implementation defines schemes for history
A key point is servers can run on any of a number of different platforms - but it's all transparent to the end user. A Waag user needs only a browser and doesn't need to know or care whether the control system is HP-UX or OpenVMS or NT or ....
Regarding itself provides for a sophisticated security mechanism. Combining this with Web server security and NTFS security provides very flexible and powerful access control.
8/23/2019

7. Web Server Verification
Connect to default home page
name>
Web server management tool
stop/start web server
creating aliases (virtual directories)
setting directory access - read, script, execute
Web server security
NTFS file protection?
Authentication?
8/23/2019

8. Frontpage Installation & Verification
Straightforward installation
Create (save) test web
Just a reminder that order of installation is important. If you make a mistake and install Frontpage before the Webserver, you may lose out on Frontpage extensions. If you install Waag before Frontpage, entry on the toolbar will be omitted - fixing this requires editting the registry, or more simply reinstalling waag.
8/23/2019

9. Installation Install Web@aGlance
license file available? Default 1-hour timeout
install detects common web servers
Verify aliases and directory access via Web server admin tool - ie Microsoft Management Console
/aagweb [read] /cgi-bin [execute]
demo
@aGlance Administration - Server Hosts
For distributors, an 8-hour timeout is also available. License files may be applied either during or after installation, and may be upgraded in place.
Regarding Administration - the server host list should contain the IP Name(s) where the data source resides.
8/23/2019

10. Upgrading from iWEB/FIXWEB
installs over iWEB/FIXWEB
Server Connection Suite Server for iFIX/ FIX32
Supported methods:
All current data methods, Read & Write
Polling only (no monitor)
History: Distributed history supported; Interval & Statistics only (no actual/event history)
Documentation- \aag\fix\fixserv.doc
Configuring server - c:\<windir>\fixserv.ini
enabling writes, changing the server name, enabling logging, default history path, and more…
8/23/2019

11. Using WAAG for Control with iFIX/FIX32
Enable WAAG writes
WriteEnable=1 (\<windir>aagweb.ini)
Configure tag(s) for writes in FIX
FIX server for writes
Using AAG Admin set server host permission AAG_FIX_READWRITE
WriteEnable=1 ; (\<windir>fixserv.ini)
Restart AAG server for FIX
8/23/2019

12. Did everything right but something’s wrong….
WAAG Overview Documentation - Troubleshooting
Logging -
CGI logging: c:\<windir>\aagweb.ini
Web server logging
AAG logging
OPC/AAG server logging
8/23/2019

13. Set sail!
Questions?
8/23/2019

14. End
8/23/2019