ADF Business Component
ADF Business Component
ADF Business Component is a Java and XML based framework for
developing:
·
Business logic, including validation and default
logic
·
Queries
·
Transaction Handling
·
Data access
The Advantage of ADF Business Component over UI-enforced
business logic is reusability. For example, a single ADF Business Component
layer can provide the business logic for all a company’s needs. The business
components can be used again and again, with multiple interfaces.
Advantage of ADF BC:
1.
By maintaining a cache of data in memory, ADF BC
reduces the number of database trips required by an application resulting in
improved performance and scalability.
2.
ADF BC allows the business logic to be written
in Java, which saves the trouble of intergrating a Java GUI or JSP application
with business logic written in PL/SQL code.
3.
Removing the business logic out of the database,
and keeps the database from handling anything bud data which increase an application’s
modularity and efficiency
5 Components of ADF BC Architecture
·
Entity
Object à
represents a table in simple terms. It defines the table’s attributes
(columns), data types, validation on the data, primary keys and the entire
business logic that needs to be defined for pushing data into the target table.
·
Entity
Associations àdefines
the join or the link among EO’s and VO’s. Associations defines link between
EO’s, and they can be considered as PrimaryKey/ForeignKey relationships between
tables.
·
View
Objects à The
view object can be based on EO's, which are similar to SQL queries used to
extract data, or it can be programatically populated, or with a static list.
However VO's based on EO's are most used option. While a few validations can be
done even at the VO level, it's better to have business logic on the EO's as
this will help provide a central point for all VO's dependent on them.
·
View
Links à
defines the link between VO’s and can be based on an association or on
attributes
·
Application
Modules àThe
application module packages the VO's and serves as the data control.The AM
creates and manages the database transaction for ADF Model layer. It is the
Application Module that exposes the data needed by the client. So, for an end
user, the interaction and transactional capabilities are provided by the
application module.