Skip to main content

Patterns for e-business > Select Business pattern > Select Application pattern >
c


Access Integration::Thin Client application pattern::Runtime patterns

The Runtime pattern for the Thin Client application pattern allows users with Web browser clients such as a desktop or laptop to access online (web) applications. This Runtime pattern is representative of enterprise applications using the J2EE programming model.

Thin Client application pattern::Runtime pattern
(Click a node to get a detailed explanation.)
Design Last Updated: 02-13-2006
Thin Client application pattern: Runtime pattern Click for more information Click for more information Click for more information Click for more information Click for more information Click for more information Click for more information Click for more information Click for more information

The Web Server Redirector node delivers HTML content to the Client component where it is rendered by the HTML Web browser. The page layout is designed for standard Web resolutions such as 1024x768, but can scale as standard within the browser for other resolutions such as 800x600 or 1280x1024.
A simple solution to support a limited number of additional devices with smaller screen sizes would be to provide device dependent HTML pages. The user agent of the Web browser can be used to determine and activate the appropriate JSP for the application. The big drawback of this solution is that for each device with a smaller screen then the standard size will need a separate JSP, which will need to be developed and maintained. For example, a WML browser found in a WAP found will have a much smaller screen size than a standard PC based Web browser client. In order to keep the development effort for the View components to a minimum, the variety of devices with which the application is accessed should be limited. This is only practical if an enterprise can defines the type of device that will access the enterprise application, thus reducing the number of pages that must be customized and maintained.


There are two key drivers that distinguish the need for using the portal variation of the Thin Client runtime pattern:

  • Access to role-based and/or personalized aggregated content
  • Content adaption and rendering for different device types

Thin Client application pattern::Runtime pattern=portal variation
(Click a node to get a detailed explanation.)
Design Last Updated: 02-13-2006
Thin Client application pattern: Runtime pattern portal variation Click for more information Click for more information Click for more information Click for more information Click for more information Click for more information Click for more information Click for more information Click for more information Click for more information Click for more information Click for more information Click for more information

The demand to access information from less sophisticated devices is increasing. The Thin client extension services provide Web browser access to a wide range of devices including high function devices such as desktops and laptops, as well as lower function PDAs, mobile phones and RFID readers.
The Thin client extension services extend the existing Presentation services with multi-device support for online access (e.g. to a Portal). They are preferably implemented in an Application server environment. The extension services might also provide multi device online access to collaboration services.
Note, that no specific services on the client (device) side are required to achieve this so that very thin clients (low function devices can be used). Depending on the capabilities of the device, the Thin client::Runtime pattern might be combined with the Roaming Connectivity runtime pattern to gain secure managed access to the corporate network.

Next, review product mappings or review the Roaming Connectivity::Runtime pattern, that covers all aspects of remote access to a secured computing environment using in-secure networks and/or devices.

c