E-Business Suite authentication for BI Publisher

.

Think about an Oracle BI Applications environment built on top of Oracle Business Intelligence Enterprise Edition (OBIEE) in which the source system is the Oracle E-Business Suite (EBS), the access to OBIEE has been integrated with the E-Business Suite so when a user logs into the EBS system he has the rights to access OBIEE analytics without being prompted for user and password.

Everything works fine until someone decides to click on the “Report” link that belongs to the “Published reporting” (BI Publisher) and gets an error message indicating that the current user has no privileges to access it.

EBS authentication for BI Publisher

This guide contains the steps that need to be applied in order to integrate BI Publisher user authentication interface with EBS, so a user will be able to access the OBIEE (BI Publisher) environment if this user exists as an EBS user with the correct responsibilities assigned.

Continue reading this post >

Emailing reports to non OBI users using IBots

.

Sometimes companies need to distribute their OBI reports via email to their employees. For example the sales department needs to have the weekly sales report on their email inbox every Monday morning so they can start the day analysing the sales without having to download any report in OBI. This can be easily achieved by using IBots, as we can schedule them to send the reports to the users or groups that we want.

But let’s imagine now that as the sales figures are really good and the company decides to email them to organisations outside the company (newspapers, magazines…). In this case as we want to email reports to non OBI users we need to reconfigure the IBots as it is not configured by default to send reports by email to non OBI users.

In this article we are going to see how to send a report by email to users that do not belong to any of the defined OBIEE groups or are users by itself of OBIEE using iBots.

Continue reading this post >

OBIEE 10g High Availability

.

Sometimes there is a need to have OBIEE system operating during planned or unplanned downtime. Because of this reason OBIEE provides a high availability capability: it is possible to configure all OBIEE components in order to offer high availability. In this entry I am going to describe the process of configuring a high available OBIEE 10g system.

Before going to the configuration I want to clarify some concepts:

Availability is the degree to which an application, service, or function is accessible on demand. Based on this concept we can conclude that High Availability is a system continuously operational as long as possible.

High availability systems can be categorized into local high availability systems which are configured in a single data center and disaster recovery solutions systems which are usually geographically distributed. OBI Server only can be configured in the first case; all components of the BI Cluster Server feature must reside on the same LAN.

High availability comes from redundant systems and components. Local high availability solutions can be categorized, by their level of redundancy, into active-active where two or more active instances are working at the same time and active-passive where only one instance is active and others are in standby.

OBIEE provides for high availability through the use of native clustering, failover and load balancing capabilities. Let’s analyze the OBIEE 10g components and how they are communicated in a clustered environment.

Continue reading this post >

OC4J as a Windows Service

.

Some Oracle Application like BI Publisher 10g uses OC4J, which is an Oracle Application Server which enables J2EE applications to run. These set of containers, API and services have to be started manually at system start up and after system downtime.

It is annoying for system administrators to have manual task to take care of. So, if we are in a Windows environment, these tasks can be avoided if they are defined as an automatic start-up process within the MS Windows Service.

Installing OC4J as a MS Windows Services we will solve that inconvenience we will take a step further in automation wise and we will decrease the services downtimes.

Continue reading this post >

privacy policy - Copyright © 2000-2010 ClearPeaks

topnav