Enterprise Application Engine and BOM Technologies

There are BOM classes that are directly referenced by clients without using interfaces. While interface-based design is preferred for loose coupling, direct class references exist in some parts of the architecture for practical reasons like simplicity or performance.

BOM is developed using POJOs (Plain Old Java Objects) rather than JSPs (for web presentation) or Servlets (for web request handling). POJOs are simple Java objects that don't depend on specialized frameworks, making them lightweight and testable.

BOM uses the Factory pattern to instantiate objects in the BOM graph per client request. The Factory pattern centralizes object creation logic, allowing for controlled instantiation and easy management of object lifecycles. Adapter is for interface compatibility, Singleton ensures single instances.

BOM uses IBM DB2 UDB (Universal Database) for persistence. DB2 is IBM's enterprise relational database, commonly used in enterprise Java applications, especially in financial services. Oracle and SQL Server are competing products, while DBM is not a standard database product name.

In business services, Mapper classes are used to map between VO (Value Objects) and BOM (Business Object Model) objects. Mappers handle data transformation between different object models, ensuring proper conversion and maintaining separation of concerns.

In BRMS (Business Rule Management System), Rule Flow controls the flow of execution of rules. Rule Flow defines the sequence and conditions under which business rules are executed. Business Flow Diagram is a general concept, Rule Deployment Descriptor handles deployment configuration.

UML (Unified Modeling Language) is the standard visual modeling language for specifying, visualizing, constructing, and documenting business objects and software systems. It uses various diagram types to represent system structure and behavior.

The BOM (Business Object Model) uses the IDecisionEngineManager interface to communicate with the Rules Engine. This interface provides methods for invoking business rules and retrieving decisions.

The Business Delegate pattern acts as an intermediary between the Presentation layer (client tier) and Business Services layer. It reduces coupling and provides a simple unified interface to the business tier, hiding implementation details.

Hibernate is an ORM (Object-Relational Mapping) persistence framework specifically designed for database operations. Spring is a broader framework with multiple capabilities including dependency injection and MVC, not primarily a persistence framework. Struts is a web MVC framework.

Application Engine provides an alternative to traditional COBOL or SQR programs for background SQL processing. The 'Both' option correctly indicates that it replaces both COBOL and SQR, which were commonly used for batch processing and reporting.

Application Engine programs support both row-by-row processing (option 1) and set-based processing (option 2), making 'both 1 and 2' the correct answer. Set-based processing is generally preferred for performance, while row-by-row is used when business logic requires it. SQL statements are used within both approaches but are not a processing method themselves.

Application Engine does NOT generate SQL or PeopleCode - it executes SQL statements and PeopleCode that developers write. The platform provides a framework for running existing code, not a code generation tool.

All Application Engine programs must contain at least one section named MAIN, which serves as the entry point for the program execution. SECTION is a general term, STEP01 is a naming convention but not required, and ACTION refers to operations within steps.

A STEP is the smallest unit of work that can be committed within an Application Engine program. MAIN is a section containing steps, SECTION is a container for steps, and ACTION represents operations within a step. Steps can be committed individually, providing transaction control.

In PeopleSoft Application Engine, a STEP is the smallest executable unit - it contains actions that are executed as a committed unit of work. MAIN is the program level, SECTION is a grouping of steps, and ACTION is not a valid PeopleSoft AE construct.

In PeopleSoft Application Engine, a step cannot contain both a Call Section action and a PeopleCode action - they are mutually exclusive. SQL can coexist with Call Section. Do While/Do Until/Do Select are different actions that can be combined.

PeopleSoft Application Engine allows a maximum of 7 actions in a single step. This includes combinations of SQL, Call Section, Do While, Do Until, Do Select, Do When, XSLT, and PeopleCode - though some combinations like PeopleCode with Call Section are mutually exclusive.

The ReUse Statement property in PeopleSoft Application Engine is specifically designed for SQL action types. This property allows SQL statements to be reused across multiple executions, improving performance by avoiding re-parsing. It applies to all SQL actions including SQL, Do When, Do While, Do Until, and Do Select. It does not apply to PeopleCode actions or Call Section actions, which have different execution models.

When a Do Select action uses the Select/Fetch option, Application Engine defers all commits until the entire step completes successfully. This is because Select/Fetch opens a cursor and processes rows sequentially - committing mid-stream would close the cursor and break the iteration. Other commit options on the step are ignored until the Do Select finishes all rows. This ensures data consistency throughout the fetch loop.