CWA 14923-1:2004 en

J/eXtensions for Financial Services (J/XFS) for the Java Platform - Part 1: Base Architecture - Programmer's Reference


Over deze norm

Status Definitief
Aantal pagina's 86
Gepubliceerd op 01-06-2004
Taal Engels
J/XFS defines a standardized interface to all common financial devices which can be used by applications and applets1 written in the Java programming language. One of the reasons why these new banking applications are written in the Java language is that these programs are supposed to run on many different hardware platforms. One of the main obstacles in doing platform independent programming is accessing devices. One of the main goals of this standard is to allow access to banking devices in a 100% pure Java way on both thin and thick clients, e.g. on a network computer as well as in a Linux, WinNT, OS/2 or Unix workstation. Another goal is to allow the remote access to devices on different machines. Additional efforts have to be done to find and access these devices. This is the main reason why central administration processes and an additional communication layer are also defined by this architecture. If only local access to devices is needed, an implementation may omit this communication layer. No change is required to the Device Controls or Device Services. So, neither the application programmer nor the hardware manufacturer who programs a Device Service need be aware of whether or not a communication layer exists in the middle. Due to the nature of network computers which are supported as clients, it is not possible to guarantee that local persistent storage possibilities exist on each client. Therefore, any configuration information must be kept on a central server. If local storage exists and no central configuration possibilities are required, all configuration information can also be kept on the local workstation. The basic architecture of J/XFS is similar to the JavaPOS2 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 or applet - Device Control and Manager - Device Communication - Device Service The Device Control API defines the way a Java application or applet can communicate with a specific device. Additionally, the Device Control layer contains the central Device Manager which organizes access and location of the services. It is the central coordinating instance in any Java VM which must access financial devices. The Device Communication Layer is the layer which resolves the sharing of devices. It is invisible to the application. The only exception is that network errors are presented to the application. It must be able to cope with lost connections. The Device Service is the layer supplied by the device manufacturer for use with J/XFS. It has a defined API which allows the Device Control and Device Communication layer to request device actions and translates them into the device specific commands which are then sent to the physical attached device. The way of connecting to the local device is not defined in this standard, it is rather left to the service provider. In the case of devices which attach through the serial or parallel ports the Java CommAPI may be used. Thus, the Device Service layer may not be 100% pure Java but the complete basic infrastructure of J/XFS is.


ICS-code 35.240.40
Nederlandse titel J/eXtensions for Financial Services (J/XFS) for the Java Platform - Part 1: Base Architecture - Programmer's Reference
Engelse titel J/eXtensions for Financial Services (J/XFS) for the Java Platform - Part 1: Base Architecture - Programmer's Reference



Ga naar winkelwagen