Click here to load reader

BI Publisher Best Practices

  • View
    45

  • Download
    4

Embed Size (px)

Text of BI Publisher Best Practices

Slide 1

Copyright 2012, Oracle and/or its affiliates. All rights reserved.#1Oracle BI Publisher Best PracticesRupesh VarmaPrincipal Product Manager

Copyright 2012, Oracle and/or its affiliates. All rights reserved.#2 The following is intended to outline our general product direction. It is intended for information purposes only, and may not be incorporated into any contract. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decision. The development, release, and timing of any features or functionality described for oracle's products remains at the sole discretion of oracle.Copyright 2012, Oracle and/or its affiliates. All rights reserved.#3Oracles Safe harbor statement

In this presentation we are not discussing any new features. Program AgendaOracle BI Publisher Enterprise OverviewReport Design Best PracticesData Modeling GuidelinesTemplate Design GuidelinesReporting GuidelinesQ & ACopyright 2012, Oracle and/or its affiliates. All rights reserved.#4Agenda-- Quick overview poll audience-- Talk about deployment & system requirements-- You will find several slides with some useful information about configuration options in the Appendix of this presentation.-- Talk about Report Design Best Practices (guidelines/recommendations for data model & template design)

-- Deployment & System requirement apply to the standalone (Enterprise version of BIP)

-- RTF template design guidelines/recommendations/best practices are applicable across the board (EBS, PSFT, Siebel and other Oracle products that integrate with BI Publisher standalone using Web services (or embed our technology).

-- We will try to leave time for Q&A at the end, but feel free to ask questions as we go

Oracle BI Publisher EnterpriseOne EnvironmentAuthorGenerateDeliverBenefitsEliminate complexitySimplify report development & maintenanceReduce costsEliminate Multiple-point Solutions

Reports

Checks

Labels

DestinationsInvoices

XML / EFT / EDI

Copyright 2012, Oracle and/or its affiliates. All rights reserved.#BI Publisher is Oracles strategic product offering for pixel-perfect, printer quality, high-volume reporting. You can use it to generate all your business documents: invoices, purchase orders, billing statements, financial statements, EFT documents, government forms, marketing collaterals and all other type of customer facing documents. You can also use it to create management type reports that are suitable for online viewing.

Key Benefits===========It eliminates point solutions and reduces complexity.It offers one environment to author, generate, and deliver all your documents. As a result, it reduces costs by eliminating 3rd-party solutions and outdated homegrown systems that are difficult to maintain.It has the lowest TCO compared to other reporting solution/tool in the market today

5Layout Template TypesOutput FormatsDestinationsEmail

Printer

Fax

e-CommerceRepository

Data SourcesLayout Design ToolsWeb Services

Oracle, Oracle BI EE,Oracle BI Apps SQL Server

E-Business Suite, PeopleSoft,Siebel, JDE, Primavera

OLAP

Oracle BI Publisher EnterpriseFrom Data to Document to Delivery

Layout Editor MS Word MS Excel Adobe Flex XSLXSLXMLEDIEFTPDFHTMLExcelPPTCSVFlashRTFInteractive

Copyright 2012, Oracle and/or its affiliates. All rights reserved.#6Complete document generation AND delivery solution.Can extract and combine data from a variety of data sources.Business users can create report layouts using familiar desktop tools such as MS Word & Adobe professional on top of that data.Documents can be generated in a wide range of output formats, and can be delivered via multiple delivery channels based on the end users or recipients choice.

Architecture

BI PublisherCopyright 2012, Oracle and/or its affiliates. All rights reserved.#7Oracle Business Intelligence PublisherSeparate data logic, layout & translation benefitsgreater flexibility and reuse fewer reports and better report maintenanceoptimize data extraction and document generation processReport ArchitectureReport output

Data LogicLayoutTranslationBI Publisher

Copyright 2012, Oracle and/or its affiliates. All rights reserved.#8Oracle BI Publisher Scheduler 11gBI PublisherWeb serverBI PublisherWeb serverBI Publisher Reports Repository

Client

Client

Scheduler databaseJMS ResourcesEmail

Printer

Fax

Repository

File systemFAX Q.Printer Q.Email Q.FTP Q.WebDav Q.File Q.

Job QReport QBIP System TopicWeb server/JMS Provider(Web Logic, Active MQ)

Copyright 2012, Oracle and/or its affiliates. All rights reserved.# BI Publisher scheduler has been completely re-architected in 11g; it's based on Java Messaging Service (JMS) queue technology. Allows you to dedicate one or more BI Publisher servers exclusively for particular functions such as report generation, document generation or high demand delivery channels (FTP, Fax, WebDAV etc.). The default JMS provider for Oracle Business Intelligence Publisher 11g is Weblogic JMS. Alternatively Apache ActiveMQ can be configured as JMS provider.====== When a user submits a job, the job information is stored in the Quartz tables, and the necessary triggers to run the job are created. When a scheduled job is executed by the Quartz trigger, the job moves into the scheduler job queue (Job Q). The Job Processor determines whether a particular job needs to be handled by bursting engine or batch job process. At this stage the job is picked up by the respective engine/process and the business logic is executed. The report metadata is generated and captured into Report Queue. The job of the Report Processor is to keep listening to the Report Queue and generate the reports based on the metadata available. Once the report is generated it then passes on the delivery related information to Delivery Queue. The job of the Delivery Processors is to listen to the Delivery Queue and deliver the report using respective Delivery API(s).Failover Process In the event of failure of a node in the cluster the other node assigned for the same process will take over. 9Program AgendaOracle BI Publisher Enterprise OverviewReport Design Best PracticesData Modeling GuidelinesTemplate Design GuidelinesQ & ACopyright 2012, Oracle and/or its affiliates. All rights reserved.#10Data Generation

Data Source TypesFile (XML)SQL QueryMDX QueryLDAP QueryExcel SpreadsheetHTTP (XML Feed)Web ServiceOracle BI AnalysisData Sources

Copyright 2012, Oracle and/or its affiliates. All rights reserved.#What type of data source? Free to use any data source type you want o get the XML BIP can work with any data source as long as the data is provided in XML format For large reports, use a Data Template. This especially true for EBS, where often you have to choose between using Oracle Reports Vs Data Template. Using Oracle Reports may result in faster deployment (data structure is already defined in Oracle Reports), but Data Template is generally faster at data extraction.11Data Generation

JDBC Vs JNDI (SQL Type)Both types of connection use the same JDBC driverWith JNDI you can take advantage of connection poolingBetter performanceConnection already established to the sourceBest practice for reports with many parameters with SQL type LOVs attached to themBetter RDBMS resource managementConnection Types

2

1WebLogic ServerBI PublisherCopyright 2012, Oracle and/or its affiliates. All rights reserved.#What type of connection?JNDI Recommended because of connection pooling.For example when the report contains chained parameters, each time the report is executed, the parameters will initiate to open a db session every time, which is time consuming. But by using JNDI that precious time is avoided.12Data GenerationEnable for large reportsSlower performance, but prevents out-of-memory errorsUse with scheduled reports

Scalable Mode

Copyright 2012, Oracle and/or its affiliates. All rights reserved.#13Data Model DesignOptimize data extractionSimplify layout design for report developersReduce document generation time

ObjectivesCopyright 2012, Oracle and/or its affiliates. All rights reserved.#14Data Model DesignLeverage back-end system resources (when possible)Join dataFilter & group dataPerform expensive calculations & data transformationsSort dataConsider going against BI Server instead of extracting data directly from the source systemsUse BI Server Logical SQL instead of Answers/AnalysisData ExtractionSelect t."OFFICE_DSC" as "Office" sum(f."REVENUE") as Sales Sum" From "BISAMPLE"."SAMP_REVENUE_F f "BISAMPLE"."SAMP_OFFICES_D tWhere t."OFFICE_KEY"=f."OFFICE_KEY" group by t."OFFICE_DSC"20 Vs 20,000 recordsCopyright 2012, Oracle and/or its affiliates. All rights reserved.#Data extraction Leverage back-end system resources push expensive joins to the DB) Optimize your queries Filtering data (depending on report data requirement, filter data @ the source, or use parametrs)15Data Model DesignParameters & LOVsCache LOVS for better performanceFor large LOVs, pass NULL to the parameter when users select All & modify WHERE clause in Data Set query to use the NVL function.

For example:Where order_id=nvl(:p_ordid, order_id)

Data Extraction

Copyright 2012, Oracle and/or its affiliates. All rights reserved.#Parameters & LOVs -- Cache LOVs-- pass all, Vs pass Null)16Data Model DesignEvent triggersBefore Data TriggersGenerate dynamic SQLPopulate TEMP tablesSet user context

After Data TriggersInsert rows to a target tableSend notificationsClean or delete TEMP tablesData ExtractionSelect EMPLOYEE

Search related