Welcome To NCAOUG 2007

XML PublisherTechnologyPresented by : Kiran Kumar Akkiraju

Agenda Item #1 Document Management Requirements

Agenda Item #2 Issues with Classic Report Tools

Agenda Item #3 WHY XML Publisher???

Agenda Item #4 XML Publisher Concepts

Agenda Item #5 Demonstrate the Possibilities

Document Management Requirements

Document Management Requirements Rich Formatted Reports Partner Reports Financial Statements Government Forms Marketing Materials Contracts Checks Labels XML / EFT / EDI Multiple Destinations

No One System Can Do That

3rd party solutions are required to satisfybusiness requirements

Maintenance Cost More Costly Time consuming Complex systemsExpensive MaintenanceLabor intensive

Issues with Classic Reporting Tools

Classic Reporting Tools IssueReports must be in same geometry, font, margin, size etc.,

Classic Reporting Tools IssueMore resources

Classic Reporting Tools IssueMaintenance forever ..

Classic Reporting Tools Issues 1 data set : 10 layouts : 30 languages >> 300 reports Requires highly-skilled engineers for customization

Classic Reporting Tools IssuesData logicLayoutTranslationReport fileLess flexibilityHigh development costHigh customization costDifficult upgrade

Why XML Publisher

Why XML Publisher?

Integrated Document Management Oracle XML Publisher Authoring Managing DeliveringYour Business Documents Meet Business Requirements Remove Complexity Reduce Maintenance Cost Reduce Total Cost

XML Publisher ConceptSeparate data / layout / UI translationReport outputMore flexibilityReduced maintenanceData LogicLayoutTranslationXML Publisher

DeliveryServerXML Publisher ModulesDataSQLXMLWeb ServicesService BeansTemplateXLIFFXSLXMLTranslation CatalogsData HandlerTemplate ManagerTranslation HandlerPDFWordExcelMoreXMLEFT

XML Publisher Customization Business consultants use familiar desktop tools for layout customization Support for Multiple Data Sources

CONCEPTS

From Data to Delivery

Extract Once Publish Multiple Times

XML Publisher TechnologyR T FP D FX L SX S L

Adobe AcrobatMS WordMS ExcelXSL Editors

Templates PDF FormsGovernment formsTax FormsW-2XML PublisherUtilize the latest Forms from the Gov. web sitePDFDataReport Output

Templates PDF FormsInvoicesPurchase OrdersCheck printingXML PublisherAcrobatTemplate MatchesPrinting RequirementsPDFDataReport Output

Templates - RTFMarketing materialsContracts / QuotingFinancials reportsXML PublisherMS WordXSL:FORTFDataReport OutputAuthoring by marketing personnel

Templates - ExcelFinancials reportsBusiness reportsXML PublisherMS ExcelAuthoring by Business ConsultantsXSL:FOExcelDataReport Output

Templates eTextElectronic Payments (EFT / EDI)Bills ReceivableBank statementXML PublisherMS WordXSLRTFDataReport OutputAuthoring by IT / Business ConsultantEDIEFT

DemonstrationRTF TemplatePDF Template

Steps Involved1) Define Data Logic (Report definition)2) Register Data Logic in Oracle Applications Env.3) Define Layout4) Register Data Logic as Data Definition in XML Publisher5) Register Layout as a Template in XML Publisher6) Submit Registered Data Logic Program

Define Data Logic

Register Data LogicPhysical Report File NameConcurrent Program nameOutput Format : XML

Define LayoutHeaderMS-Word FieldsMSWORD FORM Fields

TRX_NUMBER

Register Data Logic as a Data Definition in XML PublisherConcurrent Program Short name

Template FileData DefinitionRegister Layout as a Template in XML Publisher

Submit Registered Data Logic ProgramConcurrent Program NameTemplate Name

Concurrent Program XML OutputXML Tags

Concurrent Program Output

Concurrent Program Output

SecurityPDF Security levels forRead only / EditableCopy TextPrintablePassword Protection

Language SupportXML Publisher ships with full set of Unicode FontsScalable Unicode font embeddingSupport for font mapping and font linkingXML Publisher is alone in supportingCJKBiDiUnicodeMLS

Language SupportCommunicate with partners around the world in their languages160 languages and 200 Territories (ISO Standards)Translate each template into 160 languagesNo dependency on the DB char setUtilize RTF or XLIFF for translation

XML PublisherBetter InformationFasterCheaper

Best in Class XML Publisher ProviderCome to our Booth for LIVE DEMOS and Chances to Win Fantastic Prizes

This presentation will give you an overview of the technology used in XML Publisher.This presentation will give you an overview of the technology used in XML Publisher.Costly Time consuming Complex systems Highly-skilled engineersrequired to maintain the3rd party software serversThis presentation will give you an overview of the technology used in XML Publisher.The classic approach to reporting is to combine all of the elements of a report into a single entity, the data definition, the layout and the translation. This report file is very unwieldy and causes problems due to its inflexibility. If a report is required that has even a minor layout change a new report file must be created to support the new requirement even thou the data definition is exactly the same. If another version of a report is required at runtime in a different language then a new report file must be created to support the new language. This approach leads to more time and expense in maintaining the report files. The classic approach to reporting is to combine all of the elements of a report into a single entity, the data definition, the layout and the translation. This report file is very unwieldy and causes problems due to its inflexibility. If a report is required that has even a minor layout change a new report file must be created to support the new requirement even thou the data definition is exactly the same. If another version of a report is required at runtime in a different language then a new report file must be created to support the new language. This approach leads to more time and expense in maintaining the report files. The classic approach to reporting is to combine all of the elements of a report into a single entity, the data definition, the layout and the translation. This report file is very unwieldy and causes problems due to its inflexibility. If a report is required that has even a minor layout change a new report file must be created to support the new requirement even thou the data definition is exactly the same. If another version of a report is required at runtime in a different language then a new report file must be created to support the new language. This approach leads to more time and expense in maintaining the report files. The classic approach to reporting is to combine all of the elements of a report into a single entity, the data definition, the layout and the translation. This report file is very unwieldy and causes problems due to its inflexibility. If a report is required that has even a minor layout change a new report file must be created to support the new requirement even thou the data definition is exactly the same. If another version of a report is required at runtime in a different language then a new report file must be created to support the new language. This approach leads to more time and expense in maintaining the report files. This presentation will give you an overview of the technology used in XML Publisher.XML Publisher breaks the three components apart and treats them separately at design time, at runtime the three are brought back together by XML Publisher to generate the final formatted, translated output. There is an immediate gain in that this model is far more flexible i.e. a single data definition can support multiple layouts, multiple translations can be applied at runtime to generate translated output. This leads to a reduction in maintenance costs for all concerned.This slide summarizes the modules that make up XML Publisher.Data Data engines are registered with the data handler, these can be any engine that generates XML such as Oracle Reports, Service Beans, etc.Template - the layout templates to be used for the final output are stored and managed in the Template Manager. These templates are created using familiar desktop tools such as MS Word, MS Excel or Adobe Acrobat.Translation the translation handler will manage the translation that is required at runtime. Deliver the delivery server will take the output document and deliver to various destinations such as printer, email, fax, etc. The classic approach to reporting is to combine all of the elements of a report into a single entity, the data definition, the layout and the translation. This report file is very unwieldy and causes problems due to its inflexibility. If a report is required that has even a minor layout change a new report file must be created to support the new requirement even thou the data definition is exactly the same. If another version of a report is required at runtime in a different language then a new report file must be created to support the new language. This approach leads to more time and expense in maintaining the report files. This presentation will give you an overview of the technology used in XML Publisher.The classic approach to reporting is to combine all of the elements of a report into a single entity, the data definition, the layout and the translation. This report file is very unwieldy and causes problems due to its inflexibility. If a report is required that has even a minor layout change a new report file must be created to support the new requirement even thou the data definition is exactly the same. If another version of a report is required at runtime in a different language then a new report file must be created to support the new language. This approach leads to more time and expense in maintaining the report files. The classic approach to reporting is to combine all of the elements of a report into a single entity, the data definition, the layout and the translation. This report file is very unwieldy and causes problems due to its inflexibility. If a report is required that has even a minor layout change a new report file must be created to support the new requirement even thou the data definition is exactly the same. If another version of a report is required at runtime in a different language then a new report file must be created to support the new language. This approach leads to more time and expense in maintaining the report files. Users can design layout templates using familiar desktop applications such as Adobe Acrobat and MS Word, there are now many XSL editors available on the market for the user to take advantage of.Templates PDF FormsWhen communicating with 3rd parties there is a requirement that the communication medium should be of an exact format e.g. tax forms. PDF forms can be downloaded from these 3rd parties such as the government and used as report templates. These forms often include fields already embedded in the form layout, in this case the user is able to map the field names to XML data element names. At runtime the PDF form is merged with the XML data to create a filled copy of the original PDF form. Templates PDF Forms (2)For partner documents such as invoices, purchase orders, etc that require a specific format for their layout, PDF forms can be used. Once the layout is designed, form fields can then be embedded in the document, these can then be mapped to the required XML data elements. At runtime the XML data is merged to create a filled PDF document. Templates RTFRTF templates provide an easy to use interface e.g. Microsoft Word to create and customize report formats. Marketing departments can quickly take advantage of their existing marketing collateral, personalizing the final output for prospects and customers, generating high fidelity marketing materials. Contracts are very textual documents and require a period negotiation, rtf templates and outputs allow simple design of the contract template and the RTF output allows the two parties to update the contract document during the negotiation period.RTF templates lend themselves very well to financial reports, the layouts can be built very easily and are highly customizable.

The RTF templates are internally converted to XSL-FO, at runtime the XSL is applied to the incoming XML data, the resulting object can then be converted to PDF, RTF or HTML outputs.

Templates ExcelMany financial report consumers such as accountants use Excel extensively in their day to day work. Excel templates lend themselves to financial and business report. Excel outputs allow those consumers to check the data in Excel itself. The charting capabilities of Excel can also be exploited using the Excel templstes.Templates eTexteText templates are a special type of RTF template that allow users to define EFT and EDI formats. These are very straightforward templates that look very similar to the document used to define the EFT/EDI file specification. At runtime these are converted to XSL and applied to the XML data to produce the flat text output file required.This presentation will give you an overview of the technology used in XML Publisher.SecurityXML Publisher allows the user to produce secure PDF output, with security levels covering:Read Only/EditableCopy TextPrintablePassword Protection Language SupportIn todays global economy the support for languages is paramount, XML Publisher ships with a full set of unicode fonts, a font mapping and sub-setting engine has been built; as the output is created the engine picks the font glyphs required for the languages used, these are then embedded inside the document as a new font. This ensures that the final output will contain the required fonts and no specific fonts are required on the printer.XML Publisher is alone in supporting:CJKBiDiUnicodeMLSThis compares favorably against other PDF engines.Language Support (2)XML Publisher allows users to create templates in 160 languages in 200 territories, there is no dependency on the database character set. Customers can use either XLIFF technology to have their templates translated or provide translators with the whole template, this is great advantage, allowing translators to translate templates in context.This presentation will give you an overview of the technology used in XML Publisher.