Overview

The HTML thin client mode enables you to use the Internet to access your JADE applications. Web browsers, such as Microsoft Explorer, provide a convenient client interface to JADE data on distributed servers.

The HTML thin client mode provides the following features.

Automatic generation of the Web interface

The JADE development environment enables you to create Web pages. You can create a JADE application in one complete graphical environment, and deploy this application on the Web. HyperText Markup Language (HTML) code is generated automatically.
Session management

JADE creates a session for each user who accesses a JADE application from an HTML thin client. The TCP/IP communications protocol is used to access JADE applications from the Internet through a Web server.
Import of external HTML files

JADE enables you to import external HTML files by using a JADE development environment wizard. Corresponding classes and properties are created for each HTML file that is imported. For details, see "Adding and Maintaining HTML Documents", in Chapter 12 of the JADE Development Environment User’s Guide.
Web browsers

The dynamically generated HTML code enables you to generate a single user interface that is compatible with multiple browsers (that is, with any browser that is compliant with HTML 3.2).
Web server

The Microsoft Internet Information Server (IIS) or the Apache HTTP Server is used as the Web server.

The HTTP or HTTPS communication protocol is used to send and receive messages between the Internet and a Web server for Web services, REST services, and Web-enabled applications.

The connection between the JADE Web application and the jadehttp module can be over TCP/IP or a named pipe. When running JADE in HTML thin client mode using a named pipe, your JADE application and IIS must reside on the same workstation. When using a TCP/IP connection, the machine hosting IIS or Apache HTTP Server can be different from the machine that is running the JADE application, to provide greater security via firewalls.

If you are uploading images from another machine for a JADE Web-enabled form over a TCP/IP connection, the Firewall parameter in the [Jadehttp Files] section of the JadeHttp initialization file or the Firewall configuration directive in the JADE mod_ jadehttp module and the Firewall parameter in the [WebOptions] section of the JADE initialization file must both be set to true.
Direct Web services

Use the TCP communication protocol for direct Web services.

The TCP protocol for direct Web services communication works only between JADE systems.

For direct Web services, the machine name must contain the machine name or the IP address followed by a colon (:) character then by a TCP port number on which this service is offered.
JADE clients

The user interface for a standard (fat) JADE client can be the same as that defined for an HTML thin client, or it can be different, enabling you to have one object model but with different views of that model. The JADE clients can run Web-enabled applications, Web services, and REST services.
Security

You can implement security using:
- Operating system security and IIS or Apache HTTP Server security for data access
- Secure Sockets Layer (SSL) for data transmission
For details, see "Internet Access Support", in Chapter 2 of the JADE Object Manager Guide.

To ensure that an application specified in a Web browser cannot cause an attachment to a non-JADE environment within a Windows operating system, you must specify the name of the Web application to which users can connect as a section name within the jadehttp.ini file, as follows.
```
[application-name]
```
An attempt to attach to an application is made only to the applications whose names are specified as section names in the jadehttp.ini file.

For details about the paths that the jadehttp library file derives for files, see [Jadehttp Files] Section" under "Configuring JadeHttp for Remote Connections", in Chapter 2 of the JADE Installation and Configuration Guide. See also "Configuring JadeHttp for Remote Connections" and "Controlling the Location of Files Uploaded via a Web Application" under "Configuring Your JADE Software", in Chapter 2 of the JADE Installation and Configuration Guide.

If you want to restrict the number of Web-enabled, Web services, or REST services applications, you can set the LimitPortRange parameter in the [WebOptions] section of the JADE initialization file to true. This prevents applications from using a port number that exceeds the starting port number plus the number of copies of the application. When you set this parameter to true, an application cannot be started when the port limit is exceeded, and a message is output to the jommsg.log file.

If you want to change the number of seconds after which Web-enabled, Web services, or REST services applications wait for message transfers to complete before timing out, specify the ReadTimeout parameter in the [WebOptions] section of the JADE initialization file with the appropriate number of seconds. The default value is 600 seconds (10 minutes) but you can specify this parameter and set it to zero (0) if you do not want the application to time out waiting for message transfers to complete. (You can prefix this parameter with the name of the application if you want different applications to have different message transfer timeout values.)