Category Archives: BI Publisher

OBI Mobile App designer – A direct app for Any Platform, Any Device, Any Screen Size

Oracle introduced another great application called “Oracle BI Mobile App Designer (MAD)” in Release of Oracle Business Intelligence Enterprise Edition (Oracle BI EE). The Oracle BI Mobile App Designer (MAD) is a new design tool for business users easily to create stunning and interactive analytical applications for use on any major mobile device. With Oracle BI Mobile, businesses have been able to deploy full interactive dashboards with zero additional development using Oracle BI Mobile HD on iOS devices only, and now can create purpose-built mobile analytic applications for any smartphones and tablets with drag-and-drop simplicity using Oracle BI Mobile App Designer. BI Mobile App Designer complements BI Mobile HD and is packaged with BI Foundation Suite and the BI Mobile option to OBIEE.

OBI MAD Highlights:

  • Mobile-first Business Apps – BI Mobile App Designer is the ideal solution for users that want targeted, business-specific mobile apps that are easy and fast to build, require no programming expertise, and can be delivered to users across all the major mobile platforms and devices. Apps are built with support for touch and gestural interactions built in.
  • Intuitive App Design Interface – BI Mobile App Designer has a simple drag-and-drop interface that allows business users to select their data visualizations—including tables, charts, navigation panels, repeating grids, images, text narrative, etc.—and then drop these elements onto a palette to create mobile apps within minutes. Third-party plug-ins like Google Maps, Sunburst visualizer, etc., can be incorporated and used in a similar manner. A preview function allows users to preview their apps within a computer’s browser, or on a mobile device by scanning a QR code – without requiring any installation or configuration.
  • Portable Device, Platform, Screen-size Design – BI Mobile App Designer is certified to support iOS, Android, and Windows Mobile smartphones and tablets. Since it supports HTML5, most mobile browsers can run BI Mobile App Designer apps; it requires no plug-in, no installation, and no download from a third-party app store.
  • Enterprise Integration – Oracle BI Mobile App Designer is a part of and fully integrated with the Oracle BI Foundation. Users can create mobile apps with enterprise data from the BI Semantic layer (RPD), with data from BI Publisher data models, or even Excel data files, with seamless support for and the benefits of role-based data-level security that the Oracle BI Foundation suite provides

A sample Mobile app designer screen:

The result in iPad:

How to get this?

  • BI Mobile App Designer is available now as a patch to Oracle Business Intelligence Suite Enterprise Edition, version [patch number 17220944 at]
  • BI Mobile App Designer is licensed at no extra charge with Oracle BI Foundation Suite and Oracle BI Mobile.

I’ll keep you guys posted about my experiences with OBI MAD. Stay tuned…




Tags: , , , ,

New OBIEE Sample App V305 ( is released

The new OBIEE Sample app V305 Virtual box image is available on OTN to download @

Highlights of this Sample Application:

  • Optimized deploy and scalability : 64b enterprise install, auto IP recognition
  • BI .7 New Features : Front End – Back End
  • BI + Essbase Integration : PA (Physical Layer Aggregation) spin-off essbase cubes, Security, Calc scripts, Writebacks
  • BI + ORE Integration : Advanced ORE integration-interaction
  • BI + Db Advanced Analytics : Advanced Analytics, NDM, Db Web Services, ODM
  • BI + Endeca Integration : EID reading OBIEE, OBIEE navigating to EID
  • BI + EPM/FR Integration : FR examples, EPM Companion Pack Deploy
  • Other : BI custom functional interactions, Concurrency Simulation, Physical SQL generator




Tags: , , , , , ,

New BI Apps documentation (updated)

If anyone planning to install the new OBI Apps, Use the updated document from Oracle @



Tags: , , ,

How to perform a full load in BI Apps

In new BI APPS, the OOB tools (BI Application configuration Manager and Functional setup manager) are really helpful in terms of populating the Domain values automatically. And also it will provide a clear checklist of tasks that should be completed before doing a load. This is really an outstanding work from oracle to minimize the dependency on documentation to configure the BI Apps.

I have outlined the high-level steps to perform a BI Apps Full load into warehouse.

In BIACM (BI Application Configuration Manager): Login to biacm (http://<hostname>:<port>/biacm) and follow these instructions:

  1. Configure the Source System Connection Pool by choosing your Source Product Line and Version.

  2. Select the offerings e.g. Oracle Project Analytics/ Finance Analytics/ etc…

  3. Click on “Perform Functional Configurations” under Functional Configuration Task list and configure the Offerings in Functional Setup Manager (FSM). Here the FSM will provide us a checklist of the tasks we need to do like the list of parameters and other functional settings that we need to setup for a load.

  4. And come back to biacm application and click on “Manage Load Plans” under “Load Plans” Tasks list to create the Load Plans. In BI APPS, we have a provision to separate the Loads into mini batch loads to minimize the applications/database downtimes. Generally, we will create one Domain Load Plan (SDE, SIL) and one Source Extract and Load (SDE, SIL and PLP). But it’s all depends on the Load strategy we define and will create different set of Load plans like SDE, SIL and PLP.

    Domain Load Plan (SDE, SIL): which does extracting the data from Source system and populate the configuration files to load data into

    Source Extract and Load (SDE, SIL and PLP):

  5. Once we created the load plans, save them and generate the Load Plan details. Now click on Execute button to kick off the Load.

Once the Load plan is started, you can monitor the load with tasks by tasks status in ODI Console/ODI Studio. I would prefer the ODI studio as best practice to use to monitor the loads and troubleshooting the issues.

In ODI Studio:

After Load Plan started, Login to ODI Studio with biapps admin username and password, and navigate to Operator, to monitor the load plan with the steps (tasks) those are configured either in sequential or Parallel order for execution. Here you can see the overall Load Plan status by Tasks and also the summary of tasks execution to know how many are in the state of Done/Error/Running/Waiting etc..

We will troubleshoot the failed tasks and after issue fixes we have the ability to start that particular task individually. If any failed task ran successfully after fixes, The ODI will resume the load plan automatically to start next dependent (serial) tasks. Otherwise, we can also resume the Load plan with its “restart from the failure” option.

And also if we feel if the failed task is not a potential failure for the load, then we can “Mark as complete” it like DAC.

Upon Load Plan is successful, the ODI will load data into Warehouse and frees up the work tables where it was doing the transformations.

A sample Screen Shot of BI APPS Oracle Project Analytics Dashboard after a full load using ODI 11g:

Have a great time folks…




Tags: , , , , , , ,

Oracle Data Integrator(ODI) Component Architecture

The Oracle Data Integrator platform integrates in the broader Fusion Middleware platform and becomes a key component of this stack. Oracle Data Integrator provides its run-time components as Java EE applications, enhanced to fully leverage the capabilities of the Oracle WebLogic Application Server. Oracle Data Integrator components includes the FMW exclusive features for Enterprise-Scale Deployments, high availability, scalability, and hardened security.

Oracle Data Integrator Component Architecture

ODI Repositories

The central component of the architecture is the Oracle Data Integrator Repository. It stores configuration information about the IT infrastructure, metadata of all applications, projects, scenarios, and the execution logs. The architecture of the repository is designed to allow several separated environments that exchange metadata and scenarios (for example: Development, Test, Maintenance and Production environments). The repository also acts as a version control system where objects are archived and assigned a version number.

The ODI Repository is composed of one Master Repository and several Work Repositories. Objects developed or configured through the user interfaces are stored in one of these repository types.

Master Repository:

There is usually only one master repository that stores the following information:

  • Security information including users, profiles and rights for the ODI platform
  • Topology information including technologies, server definitions, schemas, contexts, languages and so forth.
  • Versioned and archived objects.

Work Repository:

The work repository is the one that contains actual developed objects. Several work repositories may coexist in the same ODI installation (for example, to have separate environments or to match a particular versioning life cycle). A Work Repository stores information for:

  • Models, including schema definition, data stores structures and metadata, fields and columns definitions, data quality constraints, cross references, data lineage and so forth.
  • Projects, including business rules, packages, procedures, folders, Knowledge Modules, variables and so forth.
  • Scenario execution, including scenarios, scheduling information and logs.

When the Work Repository contains only the execution information (typically for production purposes), it is then called an Execution Repository.

ODI Studio and User Interfaces:

Administrators, Developers and Operators use the Oracle Data Integrator Studio to access the repositories. This Fusion Client Platform (FCP) based UI is used for administering the infrastructure (security and topology), reverse-engineering the metadata, developing projects, scheduling, operating and monitoring executions.

ODI Studio provides four Navigators for managing the different aspects and steps of an ODI integration project:

  • Designer Navigator is used to design data integrity checks and to build transformations such as for example:
    • Automatic reverse-engineering of existing applications or databases
    • Graphical development and maintenance of transformation and integration interfaces
    • Visualization of data flows in the interfaces
    • Automatic documentation generation
    • Customization of the generated code

  • Operator Navigator is the production management and monitoring tool. It is designed for IT production operators. Through Operator Navigator, you can manage your interface executions in the sessions, as well as the scenarios in production.

  • Topology Navigator is used to manage the data describing the information system’s physical and logical architecture. Through Topology Navigator you can manage the topology of your information system, the technologies and their data types, the data servers linked to these technologies and the schemas they contain, the contexts, the languages and the agents, as well as the repositories. The site, machine, and data server descriptions will enable Oracle Data Integrator to execute the same integration interfaces in different physical environments.

  • Security Navigator is the tool for managing the security information in Oracle Data Integrator. Through Security Navigator you can create users and profiles and assign user rights for methods (edit, delete, etc.) on generic objects (data server, data types, etc.), and fine-tune these rights on the object instances (Server 1, Server 2, and so forth).


Oracle Data Integrator also provides a Java API for performing all these run-time and design-time operations. This Oracle Data Integrator Software Development Kit (SDK) is available for standalone Java applications and application servers.

Run-Time Agent:

At design time, developers generate scenarios from the business rules that they have designed. The code of these scenarios is then retrieved from the repository by the Run-Time Agent. This agent then connects to the data servers and orchestrates the code execution on these servers. It retrieves the return codes and messages for the execution, as well as additional logging information – such as the number of processed records, execution time and so forth – in the Repository. The Agent comes in two different flavors:

  • The Java EE Agent can be deployed as a web application and benefit from the features of an application server.
  • The Standalone Agent runs in a simple Java Machine and can be deployed where needed to perform the integration flows.

Both these agents are multi-threaded java programs that support load balancing and can be distributed across the information system. This agent holds its own execution schedule which can be defined in Oracle Data Integrator, and can also be called from an external scheduler. It can also be invoked from a Java API or a web service interface.

Oracle Data Integrator Console

Business users (as well as developers, administrators and operators), can have read access to the repository, perform topology configuration and production operations through a web based UI called Oracle Data Integrator Console. This web application can be deployed in a Java EE application server such as Oracle WebLogic.

To manage and monitor the Java EE and Standalone Agents as well as the ODI Console, Oracle Data Integrator provides a new plug-in that integrates in Oracle Fusion Middleware Control Console.



Tags: , , , , , , , , , , , , ,

OBI Apps installation and Configuration

Hello all, I am writing this post to provide the BI Apps installation steps along with OBIEE

If you didn’t install OBIEE then follow all the steps from starting. Otherwise, skip the first 4 steps and continue. but make sure you have the weblogic 10.3.6 or upgrade to it, which is mandatory for ODI and BI Apps products. The current BI APPS version is certified with just Oracle as Target db. So the Oracle db version should be +. Because ODI is using JDBC drivers to connect to Oracle and will open multiple JDBC connections during the load. The DB  versions prior to are not supporting multiple JDBC connections at a time. So Oracle are mandatory for successful ETL loads.

  • Install JDK 1.6.X (JDK 1.7 is not certified by ODI
  • Install weblogic 10.3.6 (ODI must be installed on WL 10.3.6)
  • Run OBIEE RCU utility to create BIPLATFORM and MDS schemas.
  • Install and configure OBIEE
  • Install ODI with All components and “Skip Repository Configuration” option.
  • Run OBI Apps RCU to create schemas for:
    • ODI Master and Work Repositories (DEV_BIA_ODIREPO)
    • Oracle Business Applications Components (DEV_BIACOMP)
    • Oracle Business Analytics Datwarehouse (DEV_DW)
    • Update to MDS schema.
  • Install BI Apps
  • Apply FMW Platform Patches: – This is an important step to avoid the BI Apps configuration failure irrespective of what type OBIEE installation (software only / Enterprise) you did. Download “Oracle Fusion Middleware Platform Patches for Oracle Business Analytics Applications Suite” from the Oracle Business Intelligence Applications media pack on Oracle Software Delivery Cloud.
    • D:\Middleware\Oracle_BI1\perl\bin> perl D:\Middleware\Oracle_BI1\biapps\tools\bin\ D:\Middleware\Oracle_BI1\biapps\tools\bin\apply_patches_import.txt
  • Update BIACOMP Schema with ATGLite patch scripts:
    • sqlplus DEV_BIACOMP/<Password>
    • SQL> D:\Middleware\Oracle_BI1\sdf\DW\ATGPF\sql\fndtbs_11170_upg.sql
  • Configure BI Apps Basically, The biapps configuration is a process of extending existed weblogic domain(bifoundation_domain) with deploying new applications like biacm,odiconsole and etc…
  • Integrate ODI security with OPSS:
    • D:\Middleware\user_projects\domains\bifoundation_domain\bin>setDomainEnv.cmd
    • D:\Middleware\user_projects\domains\bifoundation_domain>java weblogic.WLST D:\Middleware\Oracle_BI1\bifoundation\install\ embedded –ADMIN_USER_NAME weblogic –DOMAIN_HOSTNAME localhost –DOMAIN_PORT 7001 –DOMAIN_HOME_PATH D:\Middleware\user_projects\domains\bifoundation_domain
  • Setup ODI Studio to connect to BI Apps repository:
    • Open ODI Studio from windows Start à All Programs à Oracle à ODI Studio
    • In ODI Studio window, click on connect to Repository.
    • In Oracle Data Integrator Login window, Click on + icon to add a login credentials.
    • Provide all the details required as per the below screen.

    • Click Ok, and now you will see the Oracle Data Integrator Login window.
    • Login with the BI apps Admin username and password.
    • Upon Successful authentication, now we connected to BI Apps Repository.
    • In ODI Studio, On Left hand window, you can see the ODI Designer, Operator, Topology and Security tab panes for easy navigation to perform the required tasks.
    • Click on Designer pane, and expand the Project list. Here you will see the BI Apps project folder and its mappings directories.

Have a happy time with BI Apps with ODI J.



Tags: , , , , , ,