Algorithm and its implementaion

Algorithms:

·         Where system requires customization, ORACLE provides for customizable algorithms (a.k.a plug-ins)

·         Base algorithms exist, but can be cloned and modified

·         Like “user exits”, but …

o    Unlike Change Handlers, more related to business functions and events

o    Also, unlike Change Handlers, use configurable (“soft”) parameters

·         At upgrades, custom algorithms will not be overwritten 

•        Online Admin menu used to define database components

o    Algorithm Types

o    Algorithms

o    Event / activity to which algorithm applies (e.g. FT freeze, phone number validation, etc.)

·         ORACLE Framework requires “implementation” class and various generated artifacts

·         Plug-ins “Call out” places in system (e.g. from Person to validate phone number) are known as algorithm spots

·         Each algorithm spot has interface class

·         Communication with algorithm takes place through interface

·         Interface provides abstraction between base and customization

Algorithm Annotation in OUAF :

4   Annotation specifies …

1.    Algorithm entity – i.e. where in system used – corresponds with entity defined on Algorithm Type (we will see shortly how to determine this name)

2.    Soft parameters expected – correspond with Algorithm Type parameter definitions

3.    Has Algorithm Component name (as specified on Algorithm Type) + “_Impl”

4.    Extends “_Gen” class – generated by Artifact Generator

Setter Methods:

  These methods invoked by business component to set hard parameters.       
                  1.    Sets phone number to validate – stored here for use later

2.    Sets phone type – ignored in this algorithm

Invoke method:

·         Invoke is the actual method where we include our business logic.

Getter methods:

·         These values are return by implementation program  to the frame work based on this values next functionality will done by framework.Logical steps to explain when these setter, Invoke and getter will call:

1.    Whenever spot call out occurs framework will invoke setXXX () methods to set the hard parameters.

2.    Framework executes invoke () method.

3.    Framework invokes getXXX () methods. Framework look for these values. (Some spots thse values must have to be retun else system error will occurs )

Algorithm Implementation using SDK :

Deploy and Configurations