You are on page 1of 5

IFE is a windows service. Web service is hosted on the IFE.

In order to host Web Service on the Windows Service (IFE) the component required is WSE (WSE 3.0; web service extensions). q) What is difference between a Web Service & Web Service hosted on Windows Service? IFE is the only component which is allowed to interact with OA Master data base for any CREATE/UPDATE/DELETE Operations.

All the components say OA, Job Runner etc will interact with IFE and IFE thus interacts with OA Master DB for modification of data except read mode. Components have their own set of classes to read but not to Modify data of OA Master DB.

IFE acts like a watch dog which enforces the Business Rules for the OA Master Content DB. This implies that the Business rules are common across all the components that is going into OA Master Data. IFE is a framework created by ESP (Enterprise Shared Platform) It has various work flows to process the data. The work flows provide various options for the users to override the existing functionality. The options are Interfaces that are provided as Callouts. Callouts provide us to implement our own implementation (Code). IFE works in 2 modes ie synchronously and asynchronously.

The data model of OA Master is tightly coupled with IFE data model. Ie There is a Metadata for each of the table that corresponds to OA Master DB. Every attribute that comes in the payload must be defined in the Meta data tables.

The Queue table for Asynchronous Mode contains status 0=> Record Queued, 64 => In Process (IFE picked up), 128 => failure, 255 => Success, 32 => data synchronized. The status 32 helps to process the entity synchronously when a thread picked up in a Multi Thread Environment. Work flow of IFE : 1. Callout : are the interfaces to implement our own functionality through code. 2. Golden Copy (GC): the original existing Entity record 3. Change Manager : compares the GC Vs Payload 4. Audti Trial : gives the UI history IFE works in 2 different types as UI ie source=1 and Analyst and Vendor. Business Rules are implemented in 2 ways 1. Callout for Business Rule : the rules are defined a set of tables and are implemented in Callout during ingestion/process 2. Frame work Business Rule: also called JavaScript Business Rule: rules are implemented in Table but are executed by JavaScript.

IFE maintains a Cache; hence any changes should then restart the IFE.

IFE Data Model : OA Master DB has classified each of the attribute into 3 types ie 1. Normal 2. Complex 3. Partial The core table for OA Master DB = OA.ORGANIZATIONS Core table is the one which corresponds in 1 <==> 1. There are some extended tables to the core table ie oa.organizations has some extended table like hierarchy. All the attributes in the core table and in the extended table are called Normal types Every Entity will correspond to only 1 row in the core table and in the extended tables. Cannot have Delete Operation, only soft delete ie there cannot be Delete operation on the Row level. There can be column level Operations. There is some multi row table for the Entity. Tables like Address, Identifiers, Relationships, Names etc are all multi row tables. These tables are called Complex tables ie they have 1 <==> many. Each of the attribute in the Complex table is called Partial. There can be Row level Operation for Delete and column level Operations. This implies that every attribute in the payload must and should be defined in the Meta data and should correspond to the Meta Data Tables. The data in OA Master Db can be modified in 2 ways 1. Set based : if one are few attribute values are sent, out of may, then whole existing data is wiped off and the new insert with the new attribute values are inserted. 2. Non Set Based : only values that are supplied will be updated. The DB operations are performed by creating DML scripts dynamically by IFE. For every payload into IFE, if the action of the payload is T, (to be decided) Changes will take place in 2 ways. 1. DML will query based on the data in the payload, if the query do not resulted in data, then it understands it as a INSERT.

2. DML will query based on the data in the payload, if found then will try to find the Primary Key attributes from the table, and then based on the key it updates. Business Rules : There are 2 types of business rules 1. Rule implemented in Callout code with rule type=4 2. Java script code with rule type=1 rules are described in table ife.ATTRIBUTEVALIDATIONRULES RULEID, RULENAME are primary kesy. RULETYPE describes whether the rule is to be implemented as Callout Rule or java script rule. Query for insertion of a rule : INSERT INTO IFE.ATTRIBUTEVALIDATIONRULES ( RULEID, RULENAME, ENTITYTYPE, RULEDESCRIPTION, SEVERITY, ISENABLED, ISNULLABLE, RULETYPE, RULEBODY, ATTRIBUTESAFFECTED, VIOLATIONDESCRIPTIONTEMPLATE, ISBULKALLOWED ) VALUES ( 143, 'Valid Alias Name Effective From Date', 1, 'Valid Alias Name Effective From Date should be greater than or Equal to 01/01/1800', 1, 1, 0, 1, '( ORG_ALIAS_EFF_FROM_DATE >= new Date(1800,01,01) )', ',ORG_ALIAS_EFF_FROM_DATE', 'Valid Alias Name Effective From Date should be greater than or equal to 01/01/1800',

0 )

Tem