To enable extensibility, Oracle Banking Payments identifies the release type both during design and in runtime thereby restricting the development teams to add business logic in designated units only. This is to ensure the development teams of different release types use corresponding units to add business logic.

Kernel is the main product release and Cluster releases are made using Kernel as the base to develop Cluster specific functionality. This Cluster release can be further enhanced based on the customer specific requirements to develop a Custom release.

In such case, hierarchy of Release types would be as below: Kernel  Cluster  Custom

In some cases where the final set of requirements are not very different from Kernel release or if there are not many common requirements across the customers of a particular region, Kernel itself will be taken as base for Custom releases.

In such case, hierarchy of Release types would be as below: Kernel  Custom

In all these cases, it is required for the Kernel release to provide place holders for adding additional business logic both in Cluster and Custom releases.

The approach is to divide the programs (Java Script and PL/SQL Packages) into several logical stages and to provide ‘Pre’ and ‘Post’ handlers to Customization teams.