Initiation and Process Flow

You can make each schema in the JADE database HTML thin client-capable, by defining an HTML‑enabled application instance. When it is initiated, this JADE application then communicates with the jadehttp library that is located on the Internet server.

By default, this application opens an instance of the NamedPipe or JadeInternetTCPIPConnection class with the name of the JADE application as its name, and waits for the jadehttp library to connect to the other end of the pipe or TCP/IP. When the pipe or TCP/IP is connected, it waits for HTML client requests to be sent over the pipe or TCP/IP. For details about implementing a TCP/IP connection, see "Connecting to JADE Applications from Internet Information Server (IIS)", in Chapter 2 of the JADE Installation and Configuration Guide.

When the first request for the JADE application is received, the IIS initiates the jadehttp library, and then calls the GetExtensionVersion entry point in the library to obtain the Internet Server Application Programming Interface (ISAPI) version that is being used. The library is initialized as part of this call, and it attempts to open a pipe or TCP/IP connection by using the JADE server node name.

To process multiple HTML client requests simultaneously, run additional copies of the JADE application. For details, see "Handling Multiple Copies of the JADE Program", in Chapter 1 of the JADE Installation and Configuration Guide. Each copy of the JADE application opens its own instance of the named pipe. The jadehttp library uses the additional pipe channels, as required. (By default, there are 10 pipe channels.)

If the connected JADE application terminates and breaks a pipe or TCP/IP channel, the library removes that pipe or TCP/IP from the list of available channels. When the JADE application is restarted, the library reestablishes the channel without any required intervention.

Web sessions are not closed when an application is terminated. They are closed only when the WebSession class removeSession method is called, a session timeout specified in the Session Timeout text box on the Web Options sheet of the Define Application dialog occurs (for details, see "Specifying Your HTML Thin Client Access Options", earlier in this chapter), or when all of the Web-enabled applications terminate normally.