EB/EDI*SEC can be
used in multiple types of architectures. Following are some examples of
these architectures. These examples can be applied to e-business,
electronic banking, EDI, ....
File Transfer
Architecture:
In this
architecture the customer prepares his data in a connectionless
mode(Payorders, Commands, Declarations, ...) . When data is prepared
and validated it can be signed by authorised
signers. The data is then tarnsmitted to the partner via File
Transfer or a MHS.
The advantages of
this architecture is the data preparing in the connectionless
mode, all the information is local at the customer side and the huge
volumes of information which can be treated and transmitted. One of the
inconveniences is the update of software modules at the customer side.
In this
architecture EB/EDISEC can be utilized as library or batch commands
components at the customer side, server and the back-offices.
Full Web
Architecture:
In this
architecture the customer accesses to the partner via the Web and
prepares its data (Payorders, Commands, Declarations, ...). When data
is prepared and validated it can be signed by authorised
signers. All the (customer) databases are located at the
(partner) server side. Data are transmitted by submission. The
advantanges of the architecture is the central maintenance of the
application at the partner server side as well as the reduced number of
the customer technical staff . One of the inconveniences of
this architecture is the reduced information volume which can be
submitted.
In this
architecture EB/EDISEC is utilized as Java Applets at the customer
side. At the server side and back-offices EB/EDISEC can be
utilized as library or batch commands components.
Mixed Web/File
Transfer Architecture:
In this
architecture the customer prepares its data in a connectionless mode
(Payorders, Commands, Declarations, ...), then transfers the data to
the partner server side by File Transfer or MHS(1).
The partner
Web server picks the received data from the files
server(2).
The customer can
then connect to the Web server in order to validate and sign
the transmitted information(3).
In this
architecture EB/EDISEC is utilized as Java Applets at the customer side
(Web Access). For files transfer, the partner server side
and back-offices EB/EDISEC can be utilized as library or
batch commands components.
Alternative Mixed
Web/File Transfer Architecture:
In this
architecture the customer information is prepared, validated and signed
via Intranet on the customer server.
The signed data
can be then transmitted to the partner server by File Transfer or MHS.
In this
architecture EB/EDISEC is utilized as Java Applets at the customer side
(Web Access). For files transfer, the partner server side
and back-offices EB/EDISEC can be utilized as library or
batch commands components.
|