How to Schedule a report in OBIEE 11g using Agents

Report Scheduling in OBIEE 11g

OBIEE reports are delivered to the recipients by ibots also known as OBIEE Delivers. Ibots are intelligent agent which delivers report based on the condition defined for specific timing. Report is executed to deliver by execution of trigger set based upon the condition.

Steps of Report Scheduling in OBIEE 11g

Following are the steps of Report scheduling in OBIEE 11g:

a) Login into OBIEE analytics http://host:port/analytics

b) On homepage of analytics Click on New and then click on Agent (Agent is the component with intelligence in 11g responsible for delivery of scheduled report.)

c) There appears an agent configuration page containing two section: overview and editable section. Overview section provides the summary of parameter set for delivery and editable section contain the different parameters required for delivery managed in multiple tabs. When the report delivery parameters are set then they are shown in overview.

d) General Tab: On General tab set the delivery priority to High, Normal or Low. And select the report Run as Property which can be used to maintain the user level security over analysis and dashboard. Run as contains two field Recipients and Specified User . Recipients are defined later during the process of this scheduling configuration whereas Specified User are the user of OBIEE defined from Console.

e) Schedule Tab: It is used to define the time parameter for agent to execute. Based on report scheduling frequency (defines the time period of agent execution) we need to set different parameters. There are different scheduling frequencies: Never, Once, Daily, Weekly and Monthly.

Based on these frequencies we need to define other time parameter. For example: following snapshot defines the different parameter required when scheduled Monthly.

Here we can select the month, day of month on which agent get executed, report run date etc.

Every configuration has Re-run Agent option which executes the agent continuously until the time defined with defined latency in terms of Minute. We can also define the end of report run date.

f) Condition Tab: This tab allows to define the condition (if any) which need to be true to run the agent and perform the associated action (defined later).

·         Click on radio button of Use a condition.

·         Click on Create button to create new condition from analysis or KPI (Key Performance Indicator) or click on browse button to browse for condition that you have previously created.

·         You can select between Analysis and KPI and click on Browse button.

·         Browse the analysis and define the condition. You can also test for the condition weather its true or false. Click on OK.

·         You can save the condition to catalog or test the condition.

g) Delivery Content: This defines the content which will be delivered to the Recipients . Content might be Analysis, Dashboard, Briefing Books or Condition Analysis.

There is a provision to define the report format for delivery. Report format are based on the content selected. You can define the delivery type like direct delivery of report or as an attachment. Message can also be delivered to the recipients in case when condition is false.

h) Recipients: This tab is used to mention the recipients of delivery content. Recipients can be any user of weblogic server or can be defined manually or obtained from analysis containing email address. You can also publish the agent for subscription for other user and also provide a customizing privilege of agent to the subscriber.

i) Destinations: This tab configuration defines the delivery medium of report. Here we can define the destinations which could be email, pager, mobile devices or handheld devices. You can also create an alert on dashboard and home page of analytics.

j) Actions: From this tab we can define additional task which can be perfumed during agent execution. We can execute different web services, scripts , perform HTTP request or call another agent too. This can be done for both successful or unsuccessful execution of agent.

This completes the configuration of agent ( ibot), based upon the configuration done agent will be executed