Oracle Data Profiling is a data investigation and quality monitoring tool. It allows business users to assess the quality of their data through metrics, to discover or infer rules based on this data and to monitor the evolution of data quality over time.
In this article I will explain which steps we have to follow to be able to investigate and profile data.
Overview
As I mentioned in the part one of this article Configuring OC4J Applications (i.e. BI Publisher) to work in Single Sign-On (SSO) Environment on IIS, we may need to use applications like BI Publisher on web application servers other than OC4J.
In this scenario we will see how to set up BI Publisher with Windows Native Authentication for Internet Information Services (IIS).
The way to make BI Publisher work in the SSO environment shown in this document is only one of the multiple possible solutions. Other deployment options (including for example SSO cookie or Oracle Application Server integration) can be implemented but considering your client infrustructure (i.e. IIS used all over) the Oracle Proxy integration may be the only choice.
The full topic of this article is a two part post; today I will explain how to enable the SSO mechanism for the OC4J native applications used in OBI architecture. An example of this would be BI Publisher.
I recently posted an article on how to set up OBIEE on IIS with SSO; this article is a continuation on this topic. OBI and its “analytics” application can be seamlessly deployed on IIS. However, there are some other applications in the OBI stack that don’t have this functionality. To give an example, BI Publisher or MS Office Add-in – by default can only be deployed on an OC4J Web Application server (or be a part of a wider Oracle Application Server architecture).
In this entry I will explain how to set up Single Sign-On for OBIEE in IIS environment. For those unfamiliar with the terminology, I'll start with just a quick overview to explain what IIS and OC4J are:
OBI is by default deployed on OC4J (Oracle Containers for Java) web application server. What does it actually mean? It simply means that the core OBI application will run on OC4J platform. This application by default is called “analytics” and the default port for OC4J is 9704 (as in http://hostname:9704/analytics).
Apart from the default installation we have other deployment options. One of the most popular being the IIS deployment – using Microsoft’s Internet Information Services instead of OC4J. Again we will have application called analytics, but the default IIS port will be 80 (as in http://hostname:80/analytics or simply http://hostname/analytics as 80 is the default HTTP port).
