|
|
 |
Access Integration::Distributed Application Client application pattern::Runtime pattern
The Distributed Application Client::Runtime pattern is
well suited for server managed client applications without local user interface
components (known as headless).
The meaning of distributed application in this context addresses the fact that a
custom application is running on a (remote) device where user interaction for
application management is not possible. Good examples for this type of
applications are embedded applications (for example, in cars, home gateways,
set-top boxes, RFID readers).
The Distributed client services (headless) node and its corresponding server
part, the Distributed client extension services node, provide the underlying
services for the integration of such a remote application (and device) into
back-end business processes.
Distributed Application Client application pattern::Runtime pattern
(Click a node to get a detailed explanation.) Design Last Updated: 02-13-2006
The following services from the Distributed client extension services node are used:
- Relational database services
- Assured messaging services
- Device services
The Distributed client services contain the following counterparts to the server
services and the additional services:
- Managed client services and platform management:
- Java runtime
- Java application framework
- Platform management
- Access Services
- Web Container
- XML Parsing services
- Assured messaging services
- Pub/Sub messaging services
- WebServices
- Relational database services
- Device services
The managed client services and platform management are the heart of this
solution on the device. They provide an open standard Java application platform
(OSGi based) for extending the clients capabilities to address some of the
resource limitations of embedded devices. They also enable remote
management of these Java applications running in the OSGi framework
(bundles) through standard interfaces (OMA DM). The additional Access
services provide (sub-sets) of the J2EE server side services to allow a
synchronous (common) programming model on the device and the server.
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.
|  |
|