Confguration Manager Administrative UI to manage system confguration or your BI Applications Global parameters -Language setup -Currency setup -Extract dates elps you !anage setup data" load and extend t#e $are#ouse %!onitor and !anage Load &lans t#at perorm t#e E'L %Enables migration o confguration inormation rom fle %BIAC! #elps maintain and monitor (omains !appings and (omain !ember !appings" )ource (omains" *are#ouse (omains and *are#ouse *are#ouse (omain ierarc#ies %+ou %+ou can edit current (omains or extend $it# ne$ (omain !appings %'#e ,unctional )etup !anager tass screen lins to a specifc BIAC! screen or t#e domain so you can edit t#e specifc mapping BIAC! can be used to maintain t#e Global and (ata Load &arameters lie I.I'IAL/E0'1AC'/(A'E" I)/)()/(E&L2+E(" etc
Ability to export and import confguration rom fle3 BI Applications Confguration !anager 4BIAC!5 $it# prebuilt metadata or confguring" running" and monitoring t#e E-L E-L' ' processes or source-specifc containers 3 BI Applications Confguration !anager 4BIAC!5 $it# prebuilt metadata or confguring" running" and monitoring t#e E-L E-L' ' processes or source-specifc containers 3 Load Plan Generator (LPG) is a plug-in to BIAC! t#at generates Load &lans to load desired )ubset o act tables to be populated into BI Apps (ata *are#ouse '#e Load &lan Lie Lie Cycle consists o t#e ollo$ing ollo$ing &#ases6 7(efne Load &lan 8(efne Load &lan properties 8C#oose t#e appropriate (ata )ource 8)elect t#e re9uired ,act Groups 7Generate Load &lans 8L&G Generates &lan based on design-time and run-time dependencies 8L&G trims out unnecessary tass 8Creates steps across : p#ases )(E" )IL and &L& 8Adds in additional steps or 'able maintenance
Execute Load Plan —Executes
steps o t#e Load &lan
8Creates Load &lan Instances 8)tore eac# load plan run inormation i restarted under t#e same Load &lan Instance
7!onitor Load &lans 8!onitor Load &lan runs rom BIAC!
8!onitor Load &lan runs rom 2perator Load plans can be defned rom !anage Load &lans %.e$ Load &lans can eit#er be created rom scratc# or copied rom existing Load &lans '#e Load &lans 'ypes are designed $it# t#e ability to clearly separate t#e )(E and )IL;&L& p#ases %'#is enables to reduce source system do$ntime only to t#e )(E p#ase3
Load Plan Types %'#ese are t#e available Load &lan 'ypes 7)ource Extract 4)(E5 8Includes 'ass t#at extract re9uired tables rom source 7)ource Extract and Load 4)(E" )IL < &L&5 8Includes 'ass t#at extract rom source" load into $are#ouse and related post process 7*are#ouse Load 4)IL < &L&5 82nly includes load into *are#ouse and post process 7(omain only Extract and Load 4)(E < )IL5 8Extracts only (omain related records rom source
Load Plan Generation %Load &lans need to be generated once defned only t#en t#ey can be run3 %2nce Generate is cliced" L&G resolves all dependencies based on metadata stored in repository
Load Plan Execution %Load &lans can be run by clicing t#e Execute button once generated3 %!ultiple Load &lans s#ould not be run in parallel
Load Plan Monitoring %Load &lans can be monitored rom t#e 2(I Console by clicing !anage Execution )tatus
Restarting Load Plans %Load &lans can be restarted i a ailure is encountered %In order to avoid ine=cient E'L t#ey can be restarted eit#er rom &oint o ailure or based on t#e setup in t#e Load &lan
Restarting Load Plans %Any )erial Load &lan step is al$ays set to 1estart rom ,ailure 7In case o ailure in a se9uence o sub-steps" t#e load resumes rom ailed step %Any &arallel Load &lan step is al$ays set to 1estart rom ,ailed C#ildren 7'#is ensures only t#e ailed steps in a set o parallel steps being run are executed again3 %Any )cenario step is al$ays set to 1estart rom ailure 7I a sub-step o a scenario ails" t#en restart $ill execute t#e scenario rom t#e ailed sub step
Handling Load Plan Failures %In case a Load &lan cannot be restarted because o ailures $it#in a single step" it can be !ared as Complete so rest o t#e Load &lan is not #eld up %'#e ailed scenario $ill need to be #andled and rerun separately %Care needs to be taen to #andle all dependencies i a load plan is run separately %Also care needs to be taen to reset t#e scenario variables to Load &lan run values
Handling Load Plan Failures %In case a scenario is regenerated in t#e middle o a Load &lan ailure" t#en t#e Load &lan does not picup t#e latest scenario %In t#is case eit#er t#e Load &lan can be restarted rom scratc# or t#e Load &lan can be !ared as Complete and scenario executed separately $it# t#e rig#t variable values
Stopping Load Plans %Load &lans can be stopped by using t#e )top Load &lan rom t#e context menu o t#e 2(I )tudio or t#e 2(I Console %Load &lans can be stopped ater a logical point o completion 4)top .ormal5 or be stopped immediately at current point o execution 4)top Immediate5
Source ependent Extract(SE)! %Is source-specifc and supports universal business adaptors %Exposes simplifed business entities rom complex source systems %Converts source-specifc data to universal staging table ormat %Is lig#t$eig#t and designed or perormance and parallelism %Is extensible
Source "ndependent Load(S"L)! %Encapsulates $are#ouse load logic %andles6 7)lo$ly c#anging dimensions 7>ey looup resolution; surrogate ey generation 7Insert;update strategies 7Currency conversion 7(ata consolidation
%Uses bul loaders
Post Load Process(PLP)! %&ost Load &rocesses are executed ater t#e dimensions and acts are populated %A typical example $ould be to transorm a base act table into an aggregate table %&L& tass are source independent Load plan types include: - Source Extract (SDE): Includes only those tasks that extract from the source and loads data into staging tables. - Source Extract and Load (SDE, SIL, and PLP): Includes all tasks to extract from the source and load the data warehouse tables. - Warehouse Load (SIL and PLP): Includes only those tasks that extract from the staging tables and load the data warehouse tables. - Domain-Only: Includes all tasks required to extract domain-related records from the source and load the data into the domain-related tables in the Oracle usiness !nalytics "arehouse. Functional Setup Manager Administrative UI to trac < manage implementation pro?ects and re9uired unctional setup steps Enables you to select BI Applications o@erings and ,unctional areas t#at are re9uired %Generates a list o confguration tass t#at need to completed beore a ,ull Load is run %'#e generated tass can be assigned to di@erent developers and can be monitored rom t#e ,unctional )etup !anager
The Oracle Business Analytics Warehouse supports the following currency types: # Document currency. The currency in which the transaction was performed and the
related document was stored in. For example, if your company purchases a des from a supplier in France, the document currency will liely !e in "uros. # #ocal currency. The accounting currency of the legal entity or ledger in which the
transaction occurred. # $lo!al currency. The Oracle Business Analytics Warehouse stores up to three
group currencies configured using the Oracle Business %ntelligence Data Warehouse Administration &onsole. For example, if your company is a multinational enterprise with head'uarters in the (nited )tates, ()D *() Dollars+ will !e one of the three glo!al currencies. The glo!al currencies must !e preconfigured prior to loading data so that exchange rates can !e applied to the transactional data as it is loaded into the data warehouse. For e-ery monetary amount extracted from the source, the "T# mapping stores the document and local amounts in the target ta!le. %t also stores the correct exchange rates re'uired to con-ert the document amount into each of the three glo!al currencies. $enerally, there will !e eight columns on a fact ta!le for each
amount: one local amount, one document amount, three glo!al amounts, and three exchange rates used to calculate the glo!al amount. To configure the glo!al currencies you want to report: 1.
%n DA&, go to the Design -iew, and select the appropriate custom container from the dropdown list.
2.
Display the )ource )ystem arameters ta!.
3.
#ocate the following parameters, and set the currency code -alues for them in the /alue field *maing sure to the -alues are consistent with the source system exchange rate ta!le+:
00$#OBA#12&(332&OD" *for the first glo!al currency+. 00$#OBA#42&(332&OD" *for the second glo!al currency+. 00$#OBA#52&(332&OD" *for the third glo!al currency+. When Oracle B% Applications con-erts your transaction records6 amount from document currency to glo!al currencies, it also re'uires the exchange rate types to use to perform the con-ersion. For each of the glo!al currencies, Oracle B% Applications also ena!les you to specify the exchange rate type to use to perform the con-ersion. Oracle B% Applications also pro-ides three glo!al exchange rate types for you to configure. Oracle B% Applications also con-erts your transaction records6 amount from document currency to local currency. #ocal currencies are the !ase currencies in which your accounting entries and accounting reports are recorded. %n order to perform this con-ersion, Oracle B% Applications also ena!les you to configure the rate type that you want to use when con-erting the document currency to the local currency. To configure exchange rate types: 1.
%n DA&, go to the Design -iew, and select the appropriate custom container from the dropdown list.
2.
Display the )ource )ystem arameters ta!.
3.
#ocate the following DA& parameters and set the exchange rate type -alues for them in the /alue field: 00$#OBA#123AT"2T7" 00$#OBA#423AT"2T7"
*rate type for $#OBA#12&(332&OD"+ *rate type for $#OBA#42&(332&OD"+
00$#OBA#523AT"2T7"
*rate type for $#OBA#12&(332&OD"+
00D"FA(#T2#O&23AT"2T7"
*rate type for document to local currency+.
Exchange Rate ETL:
The exchange rates are stored in the ta!le W2"8&923AT"2$. For eoplesoft implementations, W2"8&923AT"2$ is loaded using from W2"8&923AT"2$) which is populated using mapping )D"2)FT2"xchange3ateDimension.
#ttp6;;oracletuition3blogspot3in;D;;bi -apps--confgurationdocument3#tml Tas#s in Functional Setup Manager %'#e confguration tass listed by ,unctional )etup !anager can be o t#e ollo$ing types 7'ass to confgure (ata Load &arameters 8'I!E/G1AI." I.I'IAL/E0'1AC'/(A'E" etc 7'ass to manage (omains and !appings 8(omain maps or employee dimension 7'ass to confgure 1eporting &arameters 8,)C!/!A)'E1/21G 7'ass t#at provide inormation %Completion o t#e basic setup tass ensures a ull load run" but may not be accurate %All t#e recommended tass need to be completed or an accurate load o t#e data into t#e $are#ouse 2nce an implementation is started t#e tass can be traced t#roug# ,)! and monitored or completion
Creatin an Im!lementation Pro"ect $he steps to create an implementation pro%ect are not displayed in the slide. $o create an implementation pro%ect& in the $asks bar& select Implementations ' (anage Implementation )ro%ects to display the (anage Implementation )ro%ects page. $hen choose !ctions ' *reate to enter a name for the pro%ect and select the offering to implement. $o make offerings easier to manage& Oracle recommends that you deploy one offering per pro%ect. In other words& if you are deploying three offerings& then create three implementation pro%ects. In this example& you ha+e installed Oracle ,inancial !nalytics and you create an
implementation pro%ect to configure the $L for Oracle ,inancial !nalytics. $o configure $L for Oracle ,inancial !nalytics& you must create at least one implementation pro%ect. "hen you create an implementation pro%ect& you select the offering to deploy as part of that pro%ect. Once you create an implementation pro%ect& ,( generates the tasks required to configure the specified offering. y default& the tasks are assigned to the I !dministrator user. If required& you can optionally assign tasks to functional de+elopers& who will then perform the tasks. /se the 01o to $ask2 column to complete functional configuration tasks.
Typical Financial $nalytics Confgurations %,inancial Analytics re9uires various tass to be completed" some common ones are explained6 %Confgure Initial Extract (ate %GL account and GL )egment dimension confguration or EB) %!anage (omains and !ember !appings or Employee (imension %Confgure (ata Load &arameters or )ot (elete %)peciy Gregorian Calendar (ate 1anges %)peciy t#e Ledger or )et o Boos or $#ic# General Ledger (ata is Extracted
Confgure "nitial Extract ate %I.I'IAL/E0'1AC'/(A'E is a date parameter $#ic# is applied to )(E mappings in order to limit transactional data extraction rom source to (*3 %Initial extract date in BIAC!
Confgure GL $ccounts and GL Seg%ents &or E'S %GL accounts are ey Fex felds and $#ic# are stored in GL/C2(E/C2!BI.A'I2.) table3 %Accounting Fex feld structure $ill be stored in ,.(/I(/,LE0/)'1UC'U1E)
Setting up a Full Load %arious steps need to be completed successully inorder to complete a ,ull Load successully %2verall t#e steps are as ollo$s6 7)etup )ource )ystem (etails in BIAC! 7Enable t#e licensed 2@erings and !odules in ,)! 7Create Implementation &ro?ects in ,)! 7Assign &ending 'ass to ,unctional (evelopers in ,)! 7Complete &ending 'ass in ,)! 7!onitor all necessary tass completion in ,)! 7&erorm (omains and !appings confguration 7Generate a Load &lan 7Execute and 1un a ,ull Load Assign o$ners and due dates to tass -(omain setup
% Ensures setups are complete and easily interrogated
#dmin Ser$er A *ebLogic (omain consists o one Admin )erver3 '#e Admin )erver consists o a HEE Admin ConsoleJ application $#ic# is *ebLogicKs UI or providing management unctions across t#e *ebLogic domain6 #ttp6;;local#ost6;console In addition" 2racle Enterprise !anager is also deployed to t#e Admin )erver3 E! provides )ystem !anagement and monitoring capability across t#e $#ole 2racle BI (omain6 #ttp6;;local#ost6;em
%anaed Ser$er Contains deployed HEE application components3 A *ebLogic (omain can #ave multiple !anaged )ervers" eac# o $#ic# can run on a di@erent mac#ine BIAC! and ,)! are deployed on t#e !anaged )erver bi/server6 http:33localhost:45673biacm O8I *onsole and !gent are deployed on the (anaged er+er odi9ser+er:
#ttp6;;local#ost6;odiconsole
&ode %anaer
A daemon process t#at provides remote start" stop" restart and monitoring capabilities or *ebLogic processes3 Eac# mac#ine running *ebLogic $ill #ave one 4and only one5 .ode !anager process
Oracle 'I System Com!onents
'#e same processes as $it# 2BIEE g" $it# an additional 2racle &rocess !anager .otifcation )erverJ 42&!.5 component responsible or remote start;stop;ping o )ystem Components3 2&!. can be controlled rom t#e command-line or via Enterprise !anager3 2&!. is re9uired on every 2BIEE mac#ine
Oracle 'I EE Com!onents !nalytics : 1i+es "eb access *onfig (anager : )opulates the 8omain +alues automatically ,( : ,unctional etup (anger which )opulates the 8omain +alues au tomatically and will pro+ide a clear check list of tasks that should be completed before doing a full load Load )lan 1enerator : L)1 is a utility for generating O8I plans !$1 Lite :
O8I 8; : O8I )latform includes an 8; that allows de+elopers to write codes that perform tasks similar to the ones done using O8I tudio biacm: http://
:/biacm Analytics: http://:/analytics
*no+lede %odule >no$ledge !odules are at t#e core o t#e 2racle (ata Integrator Enterprise Edition arc#itecture3 %'#ey mae all 2racle (ata Integrator Enterprise Edition processes modular" Fexible" and extensible3 %>no$ledge !odules implement t#e actual data Fo$s and defne t#e templates or generating code across t#e multiple systems involved in eac# process3 %>no$ledge !odules are generic" because t#ey allo$ data Fo$s to be generated regardless o t#e transormation rules3 %2(I Enterprise Edition provides a compre#ensive library o >no$ledge !odules" $#ic# can be tailored to implement existing best practices 4or example" or #ig#est perormance" or ad#ering to corporate standards" or or specifc vertical no$#o$53
no$ledge module is a code template containing t#e se9uence o commands necessary to implement a data integration tas3 %'#ere are di@erent predefned no$ledge modules or loading" integration" c#ecing" reverse-engineering" ?ournaliMing" and deploying data services3 %All no$ledge modules $or by generating code to be executed at run time3 %>!s can be specifed as Global" allo$ing t#em to be s#ared across multiple pro?ects3
”
3racle '" $pplications Specifc 4Ms .e$ >!s or BI Apps scenarios6 %I>! BIApps 2racle Control Append %I>! BIA&&) 2racle Event Nueue (elete Append %I>! BIA&&) 2racle ,act Incremental Update %I>! BIA&&) 2racle Incremental Update %I>! BIA&&) 2racle &eriod (elete Append %I>! BIA&&) 2racle )lo$ly C#anging (imension %I>! BIA&&) )NL 'arget 2verride %.ested I>! BIA&&) 2racle Control Append %.ested I>! BIA&&) 2racle Event Nueue (elete Append L4M '"$PPS S5L to 3racle (Multi Transport) %'#e >! is designed to load rom any I)2 -O compliant database to 2racle %It reads rom t#e selected database and $rites into 2racle 'emporary 'able created dynamically %It is typically used in most o t#e )ource (ependent Extracts %It supports extraction rom 2racle (atabases using (B Lins %It supports extraction rom )() )c#ema $#en available %It also supports standard H(BC extraction
A (B LI.> needs to be pre created manually in t#e database and s#ould be named in t#e specifc syntax belo$ or t#is to $or '#e option can also be overridden using >! 2ptions in t#e Fo$ tab %'#e interace can be c#anges to pic up rom )() )c#ema ?ust by c#anging t#e option in !anage (ata Load &arameters $#ic# sets t#e Global variable I)/)()/(E&L2+E( (atabase Lins are supported or 2racle (ata )ources %Global parameter E'L/)1C/IA/(BLI.> needs to be set or t#e (B LI.> to be used
What Is an #ent. %An agent is a runtime component o 2(I t#at orc#estrates t#e integration process3 %It is a lig#t$eig#t Hava program t#at retrieves code rom t#e repository at run time3 %At design time" developers generate scenarios rom t#e business rules t#at t#ey #ave designed3 '#e code o t#ese scenarios is t#en retrieved rom t#e repository by t#e agent at run time3 %'#is agent t#en connects to t#e data servers" and orc#estrates t#e code execution on t#ese servers3 Agents are lig#t$eig#t Hava processes t#at orc#estrate t#e execution o ob?ects at run time3 %Agents can do one o t#e ollo$ing6 7Execute ob?ects on demand
7Execute according to predefned sc#edules
/sin the 0+o 0y!es o1 #ents %(eploying a Hava EE agent in a Hava EE Application )erver 42racle *ebLogic )erver56 7In 2(I" defne t#e Hava EE agent in 'opology .avigator3 7In 2(I" create t#e *L) template or t#e Hava EE agent3 7(eploy t#e template directly using *L) Confguration *iMard3 %Using a standalone agent6 7Launc# an Agent3 7(isplay )c#eduling Inormation3 7)top t#e Agent3 %Advantages o Hava EE agents over standalone agents6 7ig# availability 7!ultiple agents" using Co#erence 7Load balancing 7Connection pooling bac to repositories
What Is 2e$erse-Enineerin. %1everse-engineering is an automated process to retrieve metadata to create or update a model in 2(I %,or example" 1>!s detects t#e description o tables" columns" data types" constraints" and comments rom a database to load t#e repository %2racle BI Applications 2(I repository contains t#e relevant source data models" 1>! needs to be run only to import customiMed tables in t#e source system
%ethods 1or D'%S 2e$erseEnineerin =tandard re+erse-engineering: 7Uses Hava (atabase Connectivity 4H(BC5 eatures to retrieve metadata" $#ic# is t#en $ritten to t#e 2(I repository 71e9uires a suitable driver
%CustomiMed reverse-engineering6 71eads metadata rom t#e application;database system repository" and t#en $rites t#is metadata in t#e 2(I repository 7Uses a tec#nology-specifc strategy" implemented in a 1everse-Engineering >no$ledge !odule 41>!5 8,or eac# tec#nology" t#ere is a specifc 1>! t#at tells 2(I # o$ to extract metadata or t#at specifc tec#nology3
3aria4le Ste!s %(eclare ariable step type6 7It orces a variable to be taen into account3 7Use t#is step or variables used in transormations" or in t#e topology3 %)et ariable step type6 7It assigns a value to a variable or increments t#e numeric value o t#e variable3 %1eres# ariable step type6 7It reres#es t#e value o t#e variable by executing t#e defned )NL 9uery3 %Evaluate ariable step type6 7It compares t#e variable value $it# a given value" according to an operator3 7+ou can use anot#er variable in t#e alue feld3
