Java Reference
In-Depth Information
• Primary application server although serves all the request, a
backup server is configured to route traffic if primary goes
down.
• Data Integrity is achieved with security controls/
mechanisms which will prevent third party from making any
unauthorized access and/or changes to data.
• Database transactions would ensure data integrity as it will
be a full commit or a rollback based on success/failure status.
Extensibility and Maintainability
The following mechanisms were recommended for Zamco
Application
architecture
to
achieve
extensibility
and
maintainability:
• The logical separation of the application into different tiers
(Client, Presentation, Business Logic, Integration and EIS
tier) allows a system to be flexible and easily maintainable.
When there are any changes in presentation, it will be done at
presentation tier and it will not affect the other tiers. If there
are business logic changes only EJB components business
logic is altered and it will not affect other tiers and vice versa.
• The architecture uses command pattern at the web tier (JSF
Backing Bean classes) for handling web events. Therefore,
when new functionalities are added to the system, it will not
affect the existing system. We can easily create a new web
action by developing new BackingBean class and configure it
in
faces-config.xml
file.
Even
modifying
the
existing
functionality
becomes
easy
by
changing
the
respective
Backing Bean classes.
