Internet Inside; Java Tpclasses - AMX NETLINX PROGRAMMING LANGUAGE Manual

Internet Inside

The Internet Inside
from the master. The web pages provide a user interface that mimics the look and feel of an AMX touch
panel. In fact, TPDesign generates the web pages.
The components of Internet Inside are as follows:
When TPDesign generates the web pages for NetLinx it creates all of the files necessary and places them
into a local directory. The created files must be downloaded to the NetLinx master into a sub-directory of
the
/USER
in a directory named
If you decide to download the files to the NetLinx master, you'll have to use an FTP client. The FTP user
name must be "NetLinx" (case sensitive) and the password is "password" (case sensitive). The default
directory returned by FTP is doc:/user. The user must create a subdirectory of /user and download all of
the files into that newly created directory.

Java TPClasses

The Java TPClasses client code runs in the users web browser and is loaded when the
loaded. The Java TPClasses code performs several different functions, including providing the look and
feel of the user interface and providing the communication mechanism to the WDM. The
communication connection between TPClasses and WDM is a persistent TCP/IP connection using TCP
port 10510 by default. The TCP port number may be changed, if necessary, by editing the
and
WDM.CONF
<param name="connectport" value="10500">
The
INDEX.HTM
the NetLinx master. This device number must have NetLinx code written to support it. Typically, a
simple
DEFINE_COMBINE
utilized that provides identical functionality to the web user interface that the "real" touch panel has.
TPDesign provides a facility for setting the device number and range of devices for the web user
interface. However, the device number and range may be changed by editing the following line in the
INDEX.HTM
<param name="devrange1" value="225,228,4">
NetLinx Programming Language Reference Guide
™
feature of the NetLinx master allows a web browser to retrieve web pages directly
Java TPClasses – The Java client code that runs on the browser essentially emulating a touch
panel.
WDM – Web Device Manager. A software module that runs on the NetLinx masters that
proxies control information to the master on behalf of the Java client.
PNG files – Portable Network Graphics. Bitmap graphics that get displayed in the browser.
Both touch panel icons and touch panel bitmaps get converted to PNG files for the Java client
to display.
XML files - Extensible Markup Language. Page definition files that describe that layout of
each page. The Java client loads one of the XML files for every page flip that occurs (load on
demand) and, therefore, are not loaded into the browser when the client makes its initial
connection.
HTML file – There is a single HTML file called INDEX.HTM for each user interface. The
HTML file contains just enough information to get the Java client up and running.
WDM Configuration file – The WDM references a configuration file (WDM.CONF) to
determine its operational parameters.
directory. For example, a board room system that contains a NetLinx master might be placed
as a subdirectory of
/BoardRoom
files. The line in the
INDEX.HTM
file also contains the NetLinx device number that the web user interface will connect to
between the "real" touch panel and the web user interface device number is
file:
.
/USER
file that needs to change is:
Internet Inside
INDEX.HTM file
INDEX.HTM
207