DOCSLIB.ORG

Introduction to Tivoli Enterprise Data Warehouse

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Introduction to Tivoli Enterprise Data Warehouse Front cover Introduction to Tivoli Enterprise Data Warehouse Insider’s guide to Tivoli Enterpise Data Warehouse Best practices for creating data marts Integration with all major OLAP tools Vasfi Gucer William Crane Chris Molloy Sven Schubert Roger Walker ibm.com/redbooks International Technical Support Organization Introduction to Tivoli Enterprise Data Warehouse May 2002 SG24-6607-00 Take Note! Before using this information and the product it supports, be sure to read the general information in “Notices” on page xvii. First Edition (May 2002) This edition applies to Tivoli Enterprise Data Warehouse Version 1.1. Comments may be addressed to: IBM Corporation, International Technical Support Organization Dept. JN9B Building 003 Internal Zip 2834 11400 Burnet Road Austin, Texas 78758-3493 When you send information to IBM, you grant IBM a non-exclusive right to use or distribute the information in any way it believes appropriate without incurring any obligation to you. © Copyright International Business Machines Corporation 2002. All rights reserved. Note to U.S Government Users – Documentation related to restricted rights – Use, duplication or disclosure is subject to restrictions set forth in GSA ADP Schedule Contract with IBM Corp. Contents Figures . .ix Tables . xv Notices . xvii Trademarks . xviii Preface . xix The team that wrote this redbook. xx Notice . xxi Comments welcome. xxii Chapter 1. Introducing building blocks. 1 1.1 Business Intelligence. 2 1.2 Business driving forces . 2 1.3 Main Business Intelligence terms . 3 1.3.1 Operational databases . 4 1.3.2 Online transaction processing (OLTP) . 4 1.3.3 Data warehouse . 5 1.3.4 Data mart . 5 1.3.5 External data source . 5 1.3.6 Online analytical processing (OLAP) . 6 1.3.7 OLAP server . 6 1.3.8 Metadata: A definition . 7 1.3.9 Drill-down . 7 1.3.10 Operational versus informational databases. 8 1.3.11 Data mining . 9 1.4 Different Business Intelligence implementations. 9 1.4.1 Summary table . 10 1.4.2 OLTP data in separate server . 10 1.4.3 Single data mart . 12 1.5 Data warehouse architecture and processes . 14 1.5.1 Data sources . 15 1.5.2 Extraction/propagation . 15 1.5.3 Transformation/cleansing . 16 1.5.4 Data refining . 16 1.5.5 Physical database model . 17 1.5.6 Logical database model . 18 1.5.7 Metadata information . 19 © Copyright IBM Corp. 2002 iii 1.5.8 Operational data source (ODS). 20 1.5.9 Data mart . 22 1.5.10 Presentation and analysis tools . 23 1.6 DB2 DataWarehouse Manager . 25 1.7 Tivoli Enterprise Data Warehouse. 27 1.7.1 The problem . 27 1.7.2 The solution. 29 1.7.3 Benefits of using Tivoli Enterprise Data Warehouse. 31 Chapter 2. Tivoli Enterprise Data Warehouse architecture . 33 2.1 Tivoli Enterprise Warehouse components. 34 2.1.1 Basic components. 34 2.1.2 How Tivoli Enterprise Data Warehouse is packaged . 36 2.2 Tivoli Enterprise Data Warehouse architecture. 37 2.2.1 Single machine installation . 37 2.2.2 Distributed installation . 38 2.2.3 Distributed installation with remote warehouse agents . 40 2.2.4 Central data warehouse data model . 42 2.2.5 Data mart’s star schema . 43 2.3 Applications with Tivoli Enterprise Data Warehouse. 45 Chapter 3. Installation and configuration . 47 3.1 Planning for Tivoli Enterprise Data Warehouse . 48 3.1.1 Selecting port numbers . 48 3.1.2 Other network checks . 51 3.2 Hardware and software requirements . 53 3.2.1 Hardware requirements. 53 3.2.2 Software requirements . 54 3.2.3 Database requirements. 55 3.2.4 Web browser requirements . 56 3.2.5 Report Interface requirements . 57 3.2.6 AIX system requirements . 57 3.2.7 Solaris system requirements. 58 3.3 Stand-alone Tivoli Enterprise Data Warehouse . 59 3.3.1 Windows DB2 Universal Database installation . 60 3.3.2 Tivoli Enterprise Data Warehouse installation . 61 3.4 Distributed Tivoli Enterprise Data Warehouse . 67 3.4.1 DB2 Universal Database installation. 68 3.4.2 Tivoli Enterprise Data Warehouse installation . 70 3.5 Tivoli Enterprise Data Warehouse configuration . 76 3.5.1 Specifying the control database for the Data Warehouse Center . 77 3.5.2 Test sources and targets in the Data Warehouse Center . 79 3.5.3 Installing warehouse packs . 81 iv Introduction to Tivoli Enterprise Data Warehouse Chapter 4. Implementation of the Report Interface . 89 4.1 Tivoli Enterprise Data Warehouse Report Interface . 90 4.2 Basic customization. 91 4.2.1 Roles . 91 4.2.2 Users. 94 4.2.3 User groups. 97 4.2.4 Data marts. 100 4.3 Types of reports . 104 4.3.1 How star schemas are used to create reports . 104 4.3.2 Summary reports. 108 4.3.3 Extreme case reports . 119 4.3.4 Health reports . 122 Chapter 5. Integration of application data to central data repository . 127 5.1 Why you might need to integrate your own data . 128 5.1.1 Mapping data to the existing schema . 128 5.1.2 Supplementing the existing schema . ..
Load more

Recommended publications
  • Solaris 10 807 Release Notes
    Solaris 10 8/07 Release Notes Oracle Corporation 500 Oracle Parkway Redwood City, CA 94065 U.S.A. Part No: 820–1259–13 August 2007 Copyright © 2008, 2011, Oracle and/or its affiliates. All rights reserved. License Restrictions Warranty/Consequential Damages Disclaimer This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. Warranty Disclaimer The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. Restricted Rights Notice If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable: U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms set forth in the applicable Government contract,and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007).
    [Show full text]
  • An Introduction to the X Window System Introduction to X's Anatomy
    An Introduction to the X Window System Robert Lupton This is a limited and partisan introduction to ‘The X Window System’, which is widely but improperly known as X-windows, specifically to version 11 (‘X11’). The intention of the X-project has been to provide ‘tools not rules’, which allows their basic system to appear in a very large number of confusing guises. This document assumes that you are using the configuration that I set up at Peyton Hall † There are helpful manual entries under X and Xserver, as well as for individual utilities such as xterm. You may need to add /usr/princeton/X11/man to your MANPATH to read the X manpages. This is the first draft of this document, so I’d be very grateful for any comments or criticisms. Introduction to X’s Anatomy X consists of three parts: The server The part that knows about the hardware and how to draw lines and write characters. The Clients Such things as terminal emulators, dvi previewers, and clocks and The Window Manager A programme which handles negotiations between the different clients as they fight for screen space, colours, and sunlight. Another fundamental X-concept is that of resources, which is how X describes any- thing that a client might want to specify; common examples would be fonts, colours (both foreground and background), and position on the screen. Keys X can, and usually does, use a number of special keys. You are familiar with the way that <shift>a and <ctrl>a are different from a; in X this sensitivity extends to things like mouse buttons that you might not normally think of as case-sensitive.
    [Show full text]
  • README for X11R7.5 on Netbsd Rich Murphey David Dawes Marc Wandschneider Mark Weaver Matthieu Herrb Table of Contents What and Where Is X11R7.5?
    README for X11R7.5 on NetBSD Rich Murphey David Dawes Marc Wandschneider Mark Weaver Matthieu Herrb Table of Contents What and Where is X11R7.5?..............................................................................................3 New OS dependent features...............................................................................................3 Configuring X for Your Hardware.....................................................................................4 Running X..............................................................................................................................5 Kernel Support for X............................................................................................................5 Rebuilding the X Distribution...........................................................................................7 Building New X Clients.......................................................................................................8 Thanks.....................................................................................................................................8 What and Where is X11R7.5? X11R7.5 is an Open Source version of the X Window System that supports several UNIX(R) and UNIX-like operating systems (such as Linux, the BSDs and Solaris x86) on Intel and other platforms. This version is compatible with X11R6.6, and is based on the XFree86 4.4.0RC2 code base, which, in turn was based on the X consortium sample implementation. See the Copyright Notice1. The sources for X11R7.5
    [Show full text]
  • IBM Tivoli Endpoint Manager for Patch Management Continuous Patch Compliance Visibility and Enforcement
    IBM Software Data Sheet Tivoli IBM Tivoli Endpoint Manager for Patch Management Continuous patch compliance visibility and enforcement With software and the threats against that software constantly evolving, Highlights organizations need an effective way to assess, deploy and manage a con- stant flow of patches for the myriad operating systems and applications in ● Automatically manage patches for multi- their heterogeneous environments. For system administrators responsible ple operating systems and applications across hundreds of thousands of end- for potentially tens or hundreds of thousands of endpoints running vari- points regardless of location, connection ous operating systems and software applications, patch management type or status can easily overwhelm already strained budgets and staff. IBM Tivoli® ● Reduce security and compliance risk by Endpoint Manager for Patch Management balances the need for fast slashing remediation cycles from weeks deployment and high availability with an automated, simplified patching to days or hours process that is administered from a single console. ● Gain greater visibility into patch compli- ance with flexible, real-time monitoring Tivoli Endpoint Manager for Patch Management, built on BigFix® and reporting technology, gives organizations access to comprehensive capabilities ● Provide up-to-date visibility and control for delivering patches for Microsoft® Windows®, UNIX®, Linux® and from a single management console Mac operating systems, third-party applications from vendors including Adobe®, Mozilla, Apple and Java™, and customer-supplied patches to endpoints—regardless of their location, connection type or status. Endpoints can include servers, laptops, desktops, and specialized equip- ment such as point-of-sale (POS) devices, ATMs, and self-service kiosks. Apply only the correct patches to the correct endpoint One approach to patch management is to create large patch files with a large update “payload” and distribute them to all of the endpoints, regardless of whether they already have all of the patches or not.
    [Show full text]
  • Appendix A. Installation and Troubleshooting
    The Almagest A-1 Appendix A. Installation and Troubleshooting Authors: Joseph T. Buck Christopher Hylands Alan Kamas Other Contributors: Stephen Edwards Edward A. Lee Kennard White A.1 Introduction This appendix consists of the following sections: • “Obtaining Ptolemy” on page A-1 discusses how to obtain Ptolemy. • “Ptolemy mailing lists and the Ptolemy newsgroup” on page A-2, discusses various forums for discussion about Ptolemy. • “Installation” on page A-3 discusses how to install Ptolemy. • “Troubleshooting” on page A-15 discusses how to find and fix problems in Ptolemy. • “Known bugs” on page A-32 lists known problems in Ptolemy. • “Additional resources” on page A-39 discusses other resources. A.2 Obtaining Ptolemy Ptolemy binaries are currently available for the following architectures: HP running HPUX10.20, Sun 4 (Sparc) running Solaris2.5.1,. In addition, Ptolemy has been compiled on SunOS4.x HPUX9.x, Linux RedHat 5.0, NetBSD_i386, IBM RS/6000 AIX4.x, SGI Irix6.x and the DEC Alpha Digital Unix 4 platforms. These additional platforms are not supported in- house and thus these ports are not tested and may not be complete. Installing the full system requires about 150 Megabytes of disk space (more if you optionally remake). The demonstration version of Ptolemy, “Ptiny,” only requires 12 Mega- bytes of disk space. All versions requires at least 8 Megabytes of physical memory. For the latest information on Ptolemy, get the Frequently Asked Questions list. Send electronic mail to [email protected] with the message: get ptolemy-hackers.FAQ in the body (not the subject) of the message.
    [Show full text]
  • Enhancing Xfree86 Security
    Enhancing XFree86 Security Matthieu Herrb July 2003 Libre Software Meeting Introduction Libre Software Meeting 1 What is XFree86 ? • a Free implementation of the X Window System, based on X.Org’s sample implementation (X11R6.6). • History: X386 (Three Eight Six) → XFree86 (Free Eight Six) • Runs on: Unix™, SVR4, *BSD, Linux, Windows (Cygwin), Mac OS X, etc. • Foundation for most modern GUIs and Desktops on Linux/Unix-like systems. Libre Software Meeting 2 Security concerns - summary Client side: Setuid clients Scripting toolkits Networking: connection setup / connection sniffing Server side: Server is setuid root Various issues: xdm, xfs, proxies Libre Software Meeting 3 Chapter 1 Client side security Libre Software Meeting 4 Which problems ? Traditional application level security: handling (and limiting) privileges Some remaining issues: • xterm (on systems where pty allocation needs root) • xlock like applications • ICCM and other scriptable X Toolkits and applications → out of the scope of this talk. Libre Software Meeting 5 Chapter 2 Networking issues Libre Software Meeting 6 Security at the transport level Access control done mainly at the transport level: if a client is able to get a connection to the X server, it can take full control of it: • display windows • get events • send synthetic events to other windows • change X resource database • access server-side data (atoms, pixmaps, etc) • tweak video modes Libre Software Meeting 7 X11 Transport Security models Transport types: • TCP • local (Unix domain sockets + SVR4 local) connections • SYSV SHM Authentication types: • Host based - xhost • Magic cookies - xauth • XDM • Kerberos, SUN-DES-1 (not widely used AFAIK) Too many people still use xhost + ..
    [Show full text]
  • Release Notes for Xfree86® 4.7.0 the Xfree86 Project, Inc August 2007
    Release Notes for XFree86® 4.7.0 The XFree86 Project, Inc August 2007 Abstract This document contains information about the various features and their current sta- tus in the XFree86 4.7.0 release. 1. Introduction to the 4.x Release Series XFree86 4.0 was the first official release of the XFree86 4 series. The current release (4.7.0) is the latest in that series. The XFree86 4.x series represents a significant redesign of the XFree86 X server,with a strong focus on modularity and configurability. 2. Configuration: aQuickSynopsis Automatic configuration was introduced with XFree86 4.4.0 which makes it possible to start XFree86 without first creating a configuration file. This has been further improved in subsequent releases. If you experienced any problems with automatic configuration in a previous release, it is worth trying it again with this release. While the initial automatic configuration support was originally targeted just for Linux and the FreeBSD variants, as of 4.5.0 it also includes Solaris, NetBSD and OpenBSD support. Full support for automatic configuration is planned for other platforms in futurereleases. If you arerunning Linux, FreeBSD, NetBSD, OpenBSD, or Solaris, try Auto Configuration by run- ning: XFree86 -autoconfig If you want to customise some things afterwards, you can cut and paste the automatically gener- ated configuration from the /var/log/XFree86.0.log file into an XF86Config file and make your customisations there. If you need to customise some parts of the configuration while leav- ing others to be automatically detected, you can combine a partial static configuration with the automatically detected one by running: XFree86 -appendauto If you areusing a platform that is not currently supported, then you must try one of the older methods for getting started like "xf86cfg", which is our graphical configuration tool.
    [Show full text]
  • Installation Guide Eclipse 3 / Eclipse 2
    Installation Guide Eclipse 3 / Eclipse 2 Solaris ddx Version 2.2 for Solaris 2.6, 2.7 (7) and 2.8 (8) December 10, 2001 Peritek Corporation. Phone 800-281-4567 [email protected] www.peritek.com Table of Contents List of Tables...................................................................................................................................3 1 Overview.......................................................................................................................................4 1.1 Platform Support ....................................................................................................................4 1.2 Getting help ............................................................................................................................5 1.3 Using this manual...................................................................................................................5 2 Hardware Installation..................................................................................................................6 2.1 Installing the Eclipse PMC ....................................................................................................6 2.2 Installing Eclipse CPCI...........................................................................................................7 2.3 Installing Eclipse PCI.............................................................................................................7 3 Configuring the Eclipse as a Console Device.............................................................................8
    [Show full text]
  • Tivoli Monitoring for Microsoft Applications V6.1.1
    IBM United States Announcement 208-122, dated May 20, 2008 Tivoli Monitoring for Microsoft Applications V6.1.1 Ordering information ..................................7 Overview Terms and conditions ................................ 9 IBM Electronic Services ...........................10 The IBM Tivoli® Monitoring for Microsoft® Applications Entry V6.1.1 Prices .......................................................10 offering provides a limited use entitlement for the Windows® operating system agent in IBM Tivoli Monitoring for Microsoft Applications. IBM Tivoli Monitoring for Microsoft Applications Advanced V6.1.1 is a Microsoft system and application monitoring tool that provides the capabilities to comprehensively monitor, alert, and report on the availability of Microsoft applications and the environment they run on. For additional information, refer to Software Announcement 208-065, dated March 25, 2008. Planned availability date • May 23, 2008: Electronic software delivery • May 23, 2008: Media and documentation IBM United States Announcement 208-122 IBM is a registered trademark of International Business Machines Corporation 1 IBM Tivoli Enhanced Value-Based Pricing terminology IBM Tivoli® Enhanced Value-Based Pricing: IBM Tivoli software products are priced using IBM Tivoli's Enhanced Value-Based Pricing. The Enhanced Value-Based Pricing system is based upon the IBM Tivoli Environment-Managed Licensing Model, which uses a managed-environment approach — whereby price is determined by what is managed rather than the number and type
    [Show full text]
  • W an in Ii D a I Ies-] W Retl N E Futui !W S Ire
    ' L H p i E ^ B | TwinI Falls'teacherB ftilcMs I . 'orira'newlt/luster. ' to retuiri'.ta.lo stateT.’K V i l l In steps of old rinasters.; fc : IW I ’ SIsports; 8^ ^ M liiai|ii MAGIC VAUry. D4 p Good Momiming # ■ t m 4 6 I ^ MONDAY ' # "Low: 29 H ^ November 26,20077 j Sunny and wlntf ^ 75 cents ' DtttOKOBr- ;:JL' i n i ii e s - ]N e !WS ' M atta/aOeyjxm« i ....... .. ............................ Hearing T ow i a nd a iw r e tlf u t u ii r e may decidle I ^wrhether H h ppumps go) | K d[iry in 200118 ly M H•learing e pits valleey M i g gnp-Qundwateruser;rs ; ■ j ag'Igainst fish farmeers: BjHirKattCbristesseQ TlmeiImea-Newa wrttor____________ I k ' AftAfter years of w ater squabl>lcl)les, a K hearcaring to determine thc fadate of ^ MagiJq^ c Valley’s groundwater pumimpcn - . M a m begiicgins Wednesday that could fitflnnlly sort)rt out who gets acccss to Id.'ld.-iIio|i ThThe hearing stems from call;alls by surfsjrface sprlng-water users CClear B Sprirprings Foods' Snake River Farmm niid A • < Bluelue Lakes TVout Farm. Tlic GshI farm-(: crsrs have asked thc slate to forcef grouroundwater pumpers to stop didraw- inglg Vw ater that tlie uout farms■ snysj is . theirleirs under Idalio’s ilrst-coinc.:. Ifirst* servtcrved water law, ■ ■ L j HIIM The case has a longand tumululltUQUS — —ilWlthiil 111** . blstcilstory.This spring, IdahoDcporurtm ent O M itthttitfikilM•N rtM d of.WMar 9 » a m m<san m ttw proem* 4 sn t^dfsr r»dai]daiza in|«d'M riltf tt^ y«ir ^ .,c«^ a ^UrHctttpa Tb* itste't wtHnter bo0 tt «t8 comUcr ofif VW ater Resourceal Directorr 1Dave dosing iW n , ^ ; ',■.
    [Show full text]
  • CGD Compute Infrastructure Upgrade Plan
    CGD Compute Infrastructure Upgrade Plan 1.0 Introduction The CGD Information Systems (IS) Group (ISG) is charged with providing a modern, progressive, and stable computing environment for the CGD user community. Scientists, engineers, and support staff should be able to concentrate on their individual duties without worrying about systems administration. The current infrastructure is being redesigned and upgraded to meet this goal. Achieving this on a restricted budget requires careful planning, time for implementation, and communication between the user community and the systems staff. Services provided by infrastructure systems will be distributed to provide ease of recovery, ease of upgrade, and flexibility to meet the growing needs of the Division. Hardware will be reused where possible, and eliminated if beyond reasonable use. Automation of services (software builds, user addition/deletion, etc) will be key to managing the growing demands. 2.0 Future CGD Computing Trends Written surveys from 2001 and meetings with each of the sections have revealed a wide variety of needs, desires, and deficiencies. Each section has a unique set of needs that often do not complement other sections. The one common factor among all sections is that more of everything will be needed to meet the common CGD goals: · More disk space for project data, home directories, and e-mail. · More Linux support to take advantage of the price/performance x86 hardware offers. · More computational processing power for modeling development. · More Microsoft products to support presentation/documentation efforts. · More laptops (MS and Linux) for travel and home use. 3.0 General Problems Computers have a useful life span that averages three years.
    [Show full text]
  • Monitoring: Become More Proactive Through Effective Historical Analysis
    1 IBM Software Group | Tivoli Software Monitoring: Become More Proactive Through Effective Historical Analysis Ed Woods Session 9633 Consulting IT Specialist Tuesday, August 9 th IBM Corporation 1:30-2:30 PM © 2011 IBM Corporation IBM Software Group | Tivoli Software Agenda How can you use history to improve your real-time monitoring strategy? Are you getting the most from your investment in monitoring and management solutions? How can you leverage history to improve your overall performance and availability? What are the most effective ways to use history to solve common problems? What are the optimal ways to collect historical information? How can you use history to become more proactive with real-time monitoring and management? Become More Proactive Through Effective Historical Analysis © 2011 IBM Corporation 2 IBM Software Group | Tivoli Software The Importance Of History Data Why History Can Be Essential To Your Overall Strategy Not all problems or events can be seen and analyzed in real time – Inevitably some analysis will need to be done after the fact using such functions as Near Term History, snapshot history, or report analysis History provides an understanding of what happened in the past – History of application performance and response time – CICS/IMS response time, DB2 thread activity, z/OS batch activity – History of resource utilization and resource issues – DASD, memory/paging, CPU, pools – History of alerts and issues – What alerts fired and how often History can be used to help visualize what may happen in the
    [Show full text]