The scope of this document is to explain the customization & extension of OBAPI for the following use cases:

• Customizing OBAPI application services and implement composite application services
• Adding pre-processing or post processing validations in the application services extension
• Adding Business Logic in pre hook or post hook points in the application services extension
• Altering the product behavior at customizations hooks provided as adapter calls in functional areas that are prone to change and in between modules that can be replaced (e.g. alerts, content management)
• Adding new fields to the OBAPI domain model and including it on the corresponding screen.
• Defining the security related access and authorization policies
• Defining different security related rules, validator and processing logics
• Customizing OBAPI UI
• Adding a new field or a table on the screen
• Removing fields from the UI

This document would be a useful tool for Oracle Consulting, bank IT and partners for customizing and extending the product.

The document is a developer’s extensibility guide and does not intend to work as a replacement of the functional specification which would be the primary resource covering the following:

• OBAPI installation & configuration.
• OBAPI parameterization as part of implementation.
• Functional solution and product user guide.

Out of scope

The scope of extensibility does not intend to suggest that OBAPI is forward compatible.