DS/CWA 16008-7
J/eXtensions for Financial Services (J/XFS) for the Java Platform - Release 2009 - Part 7: Alarm Device Class Interface - Programmer's Reference
| Organization: | DS |
| Publication Date: | 28 September 2009 |
| Status: | active |
| Page Count: | 22 |
| ICS Code (IT applications in banking): | 35.240.40 |
scope:
This document describes the Alarm device classes based on the basic architecture of J/XFS which is similar to the JavaPOS architecture. It is event driven and asynchronous. Three basic levels are defined in JavaPOS. For J/XFS this model is extended by a communication layer, which provides device communication that allows distribution of applications and devices within a network. So we have the following layers in J/XFS: - Application - Device Control and Manager - Device Communication - Device Service Application developers program against control objects and the Device Manager which reside in the Device Control Layer. This is the usual interface between applications and J/XFS Devices. Device Control Objects access the Device Manager to find an associated Device Service. Device Service Objects provide the functionality to access the real device (i.e. like a device driver). During application startup the Device Manager is responsible for locating the desired Device Service Object and attaching this to the requesting Device Control Object. Location and/or routing information for the Device Manager reside in a central repository. For Alarm Devices the basic Device Control class is extended with a method specific to this device which is described on the following pages.
Document History