of 144 /144
Metadata Reporter Guide INFORMATICA ® POWERCENTER ® 6 INFORMATICA ® POWERMART ® 6 (V ERSION 6.0)

PowerCenter/PowerMart Metadata Reporter Guidedbmanagement.info/Books/MIX/MetaRpt_Informatica.pdf · Informatica, PowerMart, PowerCenter, PowerCenterRT, PowerChannel, PowerConnect,

Embed Size (px)

Text of PowerCenter/PowerMart Metadata Reporter Guidedbmanagement.info/Books/MIX/MetaRpt_Informatica.pdf ·...

  • Metadata Reporter Guide

    INFORMATICA POWERCENTER 6INFORMATICA POWERMART 6(VERSION 6.0)

  • Informatica PowerCenter/PowerMart Metadata Reporter GuideVersion 6.0June 2002

    Copyright (c) 2002 Informatica Corporation.All rights reserved. Printed in the USA.

    This software and documentation contain proprietary information of Informatica Corporation, they are provided under a license agreement containing restrictions on use and disclosure and is also protected by copyright law. Reverse engineering of the software is prohibited. No part of this document may be reproduced or transmitted in any form, by any means (electronic, photocopying, recording or otherwise) without prior consent of Informatica Corporation.

    Use, duplication, or disclosure of the Software by the U.S. Government is subject to the restrictions set forth in the applicable software license agreement as provided in DFARS 227.7202-1(a) and 227.7702-3(a) (1995), DFARS 252.227-7013(c)(1)(ii) (OCT 1988), FAR 12.212(a) (1995), FAR 52.227-19, or FAR 52.227-14 (ALT III), as applicable.

    The information in this document is subject to change without notice. If you find any problems in the documentation, please report them to us in writing. Informatica Corporation does not warrant that this documentation is error free.Informatica, PowerMart, PowerCenter, PowerCenterRT, PowerChannel, PowerConnect, PowerPlug, PowerBridge, ZL Engine, and MX are trademarks or registered trademarks of Informatica Corporation in the United States and in jurisdictions throughout the world. All other company and product names may be trade names or trademarks of their respective owners.

    Portions of this software are copyrighted by MERANT, 1991-2000.

    Apache SoftwareThis product includes software developed by the Apache Software Foundation (http://www.apache.org/).The Apache Software is Copyright (c) 2000 The Apache Software Foundation. All rights reserved.Redistribution and use in source and binary forms of the Apache Software, with or without modification, are permitted provided that the following conditions are met:1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.3. The end-user documentation included with the redistribution, if any, must include the following acknowledgment: This product includes software developed by the Apache Software Foundation (http://www.apache.org/).Alternately, this acknowledgment may appear in the software itself, if and wherever such third-party acknowledgments normally appear.4. The names Xerces and Apache Software Foundation must not be used to endorse or promote products without prior written permission of the Apache Software Foundation.5. Products derived from this software may not be called Apache, nor may Apache appear in their name, without prior written permission of the Apache Software Foundation.THE APACHE SOFTWARE IS PROVIDED AS IS AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANT ABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE APACHE SOFTWARE FOUNDATION OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.The Apache Software consists of voluntary contributions made by many individuals on behalf of the Apache Software Foundation and was originally based on software copyright (c) 1999, International Business Machines, Inc.,http://www.ibm.com. For more information on the Apache Software foundation, please see http://www.apache.org/.

    DISCLAIMER: Informatica Corporation provides this documentation as is without warranty of any kind, either express or implied, including, but not limited to, the implied warranties of non-infringement, merchantability, or use for a particular purpose. The information provided in this documentation may include technical inaccuracies or typographical errors. Informatica could make improvements and/or changes in the products described in this documentation at any time without notice.

  • Table of Contents

    List of Figures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii

    List of Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix

    Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiNew Features and Enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii

    Designer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii

    Informatica Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii

    Metadata Reporter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xiv

    Repository Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xiv

    Repository Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xiv

    Transformation Language . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv

    Workflow Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv

    About Informatica Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvii

    About this Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xix

    About PowerCenter and PowerMart . . . . . . . . . . . . . . . . . . . . . . . . . . .xix

    Document Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xx

    Other Informatica Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xxi

    Accessing the Informatica Webzine . . . . . . . . . . . . . . . . . . . . . . . . . . . .xxi

    Visiting the Informatica Web Site . . . . . . . . . . . . . . . . . . . . . . . . . . . .xxi

    Visiting the Informatica Developer Network . . . . . . . . . . . . . . . . . . . . .xxi

    Obtaining Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxii

    Chapter 1: Understanding the Metadata Reporter . . . . . . . . . . . . . . . . 1Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

    Metadata Reporter Framework . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

    Web Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

    Web Browser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

    Database Connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

    Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

    Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

    Before You Begin Installing the Metadata Reporter . . . . . . . . . . . . . . . . . . . . 7

    Required Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

    Installation Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

    Table of Contents iii

  • Chapter 2: Installing on WebLogic under Windows . . . . . . . . . . . . . 11Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

    Step 1. Installing the WebLogic Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

    Step 2. Configuring the WebLogic Server . . . . . . . . . . . . . . . . . . . . . . . . . . 16

    Step 3. Testing the WebLogic Server Installation . . . . . . . . . . . . . . . . . . . . . 17

    Step 4. Installing the Metadata Reporter . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

    Step 5. Deploying the Metadata Reporter . . . . . . . . . . . . . . . . . . . . . . . . . . 20

    Chapter 3: Installing on WebLogic under UNIX . . . . . . . . . . . . . . . . . 23Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

    Step 1. Installing the WebLogic Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

    Step 2. Configuring the WebLogic Server . . . . . . . . . . . . . . . . . . . . . . . . . . 27

    Step 3. Testing the WebLogic Server Installation . . . . . . . . . . . . . . . . . . . . . 28

    Step 4. Installing the Metadata Reporter . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

    Step 5. Deploying the Metadata Reporter . . . . . . . . . . . . . . . . . . . . . . . . . . 30

    Chapter 4: Configuring the Metadata Reporter . . . . . . . . . . . . . . . . . 33Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

    Configuring the Metadata Reporter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

    Configuring Locations Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

    Configuring Repository Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

    Configuring Advanced Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

    Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

    Chapter 5: Using the Metadata Reporter . . . . . . . . . . . . . . . . . . . . . . 43Accessing the Metadata Reporter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

    Customizing a Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

    Wildcards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

    The Browse Button . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

    Running a Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

    Step 1. Selecting a Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

    Step 2. Setting Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

    Step 3. Displaying the Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

    Step 4. Printing the Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

    Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

    iv Table of Contents

  • Chapter 6: Understanding the Report Details . . . . . . . . . . . . . . . . . . 53Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

    Completed Session Details Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

    Report Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

    Completed Workflow Details Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

    Report Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

    Completed Worklet Details Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

    Report Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

    Invalid Mappings Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

    Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

    Report Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

    Job Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

    Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

    Report Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

    Lookup Table Dependency Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

    Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

    Report Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

    Mapping Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

    Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

    Report Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

    Mapping Layout Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

    Mapplet Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

    Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

    Report Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

    Object to Mapping/Mapplet Dependency Report . . . . . . . . . . . . . . . . . . . . 79

    Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

    Report Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

    Session List Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

    Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

    Report Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

    Session Details Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

    Report Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

    Shortcut Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

    Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

    Report Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

    Source Schema Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

    Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

    Table of Contents v

  • Report Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

    Source to Target Dependency Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

    Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

    Report Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

    Target Schema Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

    Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

    Report Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

    Transformation Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

    Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

    Report Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

    Workflow List Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

    Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

    Report Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

    Workflow Details Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

    Report Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

    Worklet List Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108

    Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

    Report Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

    Worklet Details Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110

    Report Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

    Appendix A: Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114

    Metadata Reporter Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115

    Metadata Reporter Setup Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . 116

    Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

    vi Table of Contents

  • List of Figures

    Figure 1-1. Metadata Reporter Framework . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

    Figure 1-2. Metadata Reporter Control and Content Frames . . . . . . . . . . . . . . . . . . . . . . . . . . 5

    Figure 4-1. Metadata Reporter Configuration Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

    Figure 5-1. Metadata Reporter Browse Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

    Figure 5-2. Report Displayed on the Content Frame . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

    Figure 5-3. Report Displayed on a Separate Browser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

    Figure 6-1. Sample Completed Session Details Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

    Figure 6-2. Sample Completed Workflow Details Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

    Figure 6-3. Sample Completed Worklet Details Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

    Figure 6-4. Sample Invalid Mappings Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

    Figure 6-5. Sample Job Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

    Figure 6-6. Sample Lookup Table Dependency Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

    Figure 6-7. Sample Mapping List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

    Figure 6-8. Sample Mapping Report Showing Links to Object Descriptions and Reports . . . . . 70

    Figure 6-9. Sample Mapping Report Showing a Layout Diagram . . . . . . . . . . . . . . . . . . . . . . 74

    Figure 6-10. Sample Mapplet List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

    Figure 6-11. Sample Mapplet Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

    Figure 6-12. Sample Object to Mapping/Mapplet Dependency Report . . . . . . . . . . . . . . . . . . 79

    Figure 6-13. Sample Session List Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

    Figure 6-14. Sample Session Details Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

    Figure 6-15. Sample Shortcut Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

    Figure 6-16. Sample Source Schema Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

    Figure 6-17. Sample Source to Target Dependency Report . . . . . . . . . . . . . . . . . . . . . . . . . . 93

    Figure 6-18. Sample Target Schema Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

    Figure 6-19. Sample Transformation List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

    Figure 6-20. Sample Transformation Report for a Sequence Generator Transformation . . . . . 100

    Figure 6-21. Sample Workflow List Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

    Figure 6-22. Sample Workflow Details Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

    Figure 6-23. Sample Worklet List Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108

    Figure 6-24. Sample Worklet Details Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110

    List of Figures vii

  • viii List of Figures

  • List of Tables

    Table 5-1. Metadata Reporter URL Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

    Table 6-1. Completed Session Details Report Information . . . . . . . . . . . . . . . . . . . . . . . . . . 56

    Table 6-2. Completed Workflow Details Report Information . . . . . . . . . . . . . . . . . . . . . . . . 59

    Table 6-3. Completed Worklet Details Report Information . . . . . . . . . . . . . . . . . . . . . . . . . . 61

    Table 6-4. Invalid Mappings Report Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

    Table 6-5. Invalid Mapping Report Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

    Table 6-6. Job Report Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

    Table 6-7. Job Report Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

    Table 6-8. Lookup Table Dependency Report Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

    Table 6-9. Lookup Table Dependency Report Information . . . . . . . . . . . . . . . . . . . . . . . . . . 67

    Table 6-10. Mapping Report Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

    Table 6-11. Mapping Report Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

    Table 6-12. File Name Format for Mapping Report Layout Diagram . . . . . . . . . . . . . . . . . . . 73

    Table 6-13. Mapplet Report Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

    Table 6-14. Mapplet Report Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

    Table 6-15. Object to Mapping/Mapplet Dependency Report Parameters . . . . . . . . . . . . . . . . 80

    Table 6-16. Object to Mapping/Mapplet Dependency Report Information . . . . . . . . . . . . . . . 80

    Table 6-17. Session List Report Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

    Table 6-18. Session s List Report Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

    Table 6-19. Sessions Detail Report Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

    Table 6-20. Shortcut Report Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

    Table 6-21. Shortcut Report Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

    Table 6-22. Source Schema Report Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

    Table 6-23. Source Schema Report Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

    Table 6-24. Source to Target Dependency Report Parameters . . . . . . . . . . . . . . . . . . . . . . . . 94

    Table 6-25. Source to Target Dependency Report Information . . . . . . . . . . . . . . . . . . . . . . . 94

    Table 6-26. Target Schema Report Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

    Table 6-27. Target Schema Report Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

    Table 6-28. Transformation Report Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .101

    Table 6-29. Transformation Report Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .101

    Table 6-30. Workflow List Report Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .104

    Table 6-31. Workflow List Report Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .104

    Table 6-32. Workflow Details Report Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .106

    Table 6-33. Worklet List Report Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .109

    Table 6-34. Worklet List Report Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .109

    Table 6-35. Worklet Details Report Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .111

    List of Tables ix

  • x List of Tables

  • Preface

    Welcome to PowerCenterRT, PowerCenter, and PowerMart, Informaticas integrated suite of software products that delivers an open, scalable data integration solution addressing the complete life cycle for data warehouse and analytic application development. PowerCenter and PowerMart combine the latest technology enhancements for reliably managing data repositories and delivering information resources in a timely, usable, and efficient manner.

    The PowerCenter/PowerMart metadata repository coordinates and drives a variety of core functions including extracting, transforming, loading, and managing. The Informatica Server can extract large volumes of data from multiple platforms, handle complex transformations on the data, and support high-speed loads. PowerCenter and PowerMart can simplify and accelerate the process of moving data warehouses from development to test to production.

    Note: Unless otherwise indicated, when this guide mentions PowerCenter, it refers to both PowerCenter and PowerCenterRT.

    xi

  • New Features and Enhancements

    This section describes new features and enhancements to PowerCenter 6.0 and PowerMart 6.0.

    Designer Compare objects. The Designer allows you to compare two repository objects of the same

    type to identify differences between them. You can compare sources, targets, transformations, mapplets, mappings, instances, or mapping/mapplet dependencies in detail. You can compare objects across open folders and repositories.

    Copying objects. In each Designer tool, you can use the copy and paste functions to copy objects from one workspace to another. For example, you can select a group of transformations in a mapping and copy them to a new mapping.

    Custom tools. The Designer allows you to add custom tools to the Tools menu. This allows you to start programs you use frequently from within the Designer.

    Flat file targets. You can create flat file target definitions in the Designer to output data to flat files. You can create both fixed-width and delimited flat file target definitions.

    Heterogeneous targets. You can create a mapping that outputs data to multiple database types and target types. When you run a session with heterogeneous targets, you can specify a database connection for each relational target. You can also specify a file name for each flat file or XML target.

    Link paths. When working with mappings and mapplets, you can view link paths. Link paths display the flow of data from a column in a source, through ports in transformations, to a column in the target.

    Linking ports. You can now specify a prefix or suffix when automatically linking ports between transformations based on port names.

    Lookup cache. You can use a dynamic lookup cache in a Lookup transformation to insert and update data in the cache and target when you run a session.

    Mapping parameter and variable support in lookup SQL override. You can use mapping parameters and variables when you enter a lookup SQL override.

    Mapplet enhancements. Several mapplet restrictions are removed. You can now include multiple Source Qualifier transformations in a mapplet, as well as Joiner transformations and Application Source Qualifier transformations for IBM MQSeries. You can also include both source definitions and Input transformations in one mapplet. When you work with a mapplet in a mapping, you can expand the mapplet to view all transformations in the mapplet.

    Metadata extensions. You can extend the metadata stored in the repository by creating metadata extensions for repository objects. The Designer allows you to create metadata extensions for source definitions, target definitions, transformations, mappings, and mapplets.

    xii Preface

  • Numeric and datetime formats. You can define formats for numeric and datetime values in flat file sources and targets. When you define a format for a numeric or datetime value, the Informatica Server uses the format to read from the file source or to write to the file target.

    Pre- and post-session SQL. You can specify pre- and post-session SQL in a Source Qualifier transformation and in a mapping target instance when you create a mapping in the Designer. The Informatica Server issues pre-SQL commands to the database once before it runs the session. Use pre-session SQL to issue commands to the database such as dropping indexes before extracting data. The Informatica Server issues post-session SQL commands to the database once after it runs the session. Use post-session SQL to issue commands to a database such as re-creating indexes.

    Renaming ports. If you rename a port in a connected transformation, the Designer propagates the name change to expressions in the transformation.

    Sorter transformation. The Sorter transformation is an active transformation that allows you to sort data from relational or file sources in ascending or descending order according to a sort key. You can increase session performance when you use the Sorter transformation to pass data to an Aggregator transformation configured for sorted input in a mapping.

    Tips. When you start the Designer, it displays a tip of the day. These tips help you use the Designer more efficiently. You can display or hide the tips by choosing Help-Tip of the Day.

    Tool tips for port names. Tool tips now display for port names. To view the full contents of the column, position the mouse over the cell until the tool tip appears.

    View dependencies. In each Designer tool, you can view a list of objects that depend on a source, source qualifier, transformation, or target. Right-click an object and select the View Dependencies option.

    Working with multiple ports or columns. In each Designer tool, you can move multiple ports or columns at the same time.

    Informatica Server Add timestamp to workflow logs. You can configure the Informatica Server to add a

    timestamp to messages written to the workflow log.

    Expanded pmcmd capability. You can use pmcmd to issue a number of commands to the Informatica Server. You can use pmcmd in either an interactive or command line mode. The interactive mode prompts you to enter information when you omit parameters or enter invalid commands. In both modes, you can enter a command followed by its command options in any order. In addition to commands for starting and stopping workflows and tasks, pmcmd now has new commands for working in the interactive mode and getting details on servers, sessions, and workflows.

    Error handling. The Informatica Server handles the abort command like the stop command, except it has a timeout period. You can specify when and how you want the Informatica Server to stop or abort a workflow by using the Control task in the workflow. After you start a workflow, you can stop or abort it through the Workflow Monitor or pmcmd.

    New Features and Enhancements xiii

  • Export session log to external library. You can configure the Informatica Server to write the session log to an external library.

    Flat files. You can specify the precision and field length for columns when the Informatica Server writes to a flat file based on a flat file target definition, and when it reads from a flat file source. You can also specify the format for datetime columns that the Informatica Server reads from flat file sources and writes to flat file targets.

    Write Informatica Windows Server log to a file. You can now configure the Informatica Server on Windows to write the Informatica Server log to a file.

    Metadata Reporter List reports for jobs, sessions, workflows, and worklets. You can run a list report that lists

    all jobs, sessions, workflows, or worklets in a selected repository.

    Details reports for sessions, workflows, and worklets. You can run a details report to view details about each session, workflow, or worklet in a selected repository.

    Completed session, workflow, or worklet detail reports. You can run a completion details report, which displays details about how and when a session, workflow, or worklet ran, and whether it ran successfully.

    Installation on WebLogic. You can now install the Metadata Reporter on WebLogic and run it as a web application.

    Repository Manager Metadata extensions. You can extend the metadata stored in the repository by creating

    metadata extensions for repository objects. The Repository Manager allows you to create metadata extensions for source definitions, target definitions, transformations, mappings, mapplets, sessions, workflows, and worklets.

    pmrep security commands. You can use pmrep to create or delete repository users and groups. You can also use pmrep to modify repository privileges assigned to users and groups.

    Tips. When you start the Repository Manager, it displays a tip of the day. These tips help you use the Repository Manager more efficiently. You can display or hide the tips by choosing Help-Tip of the Day.

    Repository ServerThe Informatica Client tools and the Informatica Server now connect to the repository database over the network through the Repository Server.

    Repository Server. The Repository Server manages the metadata in the repository database. It accepts and manages all repository client connections and ensures repository consistency by employing object locking. The Repository Server can manage multiple repositories on different machines on the network.

    xiv Preface

  • Repository connectivity changes. When you connect to the repository, you must specify the host name of the machine hosting the Repository Server and the port number the Repository Server uses to listen for connections. You no longer have to create an ODBC data source to connect a repository client application to the repository.

    Transformation Language New functions. The transformation language includes two new functions, ReplaceChr and

    ReplaceStr. You can use these functions to replace or remove characters or strings in text data.

    SETVARIABLE. The SETVARIABLE function now executes for rows marked as insert or update.

    Workflow ManagerThe Workflow Manager and Workflow Monitor replace the Server Manager. Instead of creating a session, you now create a process called a workflow in the Workflow Manager. A workflow is a set of instructions on how to execute tasks such as sessions, emails, and shell commands. A session is now one of the many tasks you can execute in the Workflow Manager.

    The Workflow Manager provides other tasks such as Assignment, Decision, and Event-Wait tasks. You can also create branches with conditional links. In addition, you can batch workflows by creating worklets in the Workflow Manager.

    DB2 external loader. You can use the DB2 EE external loader to load data to a DB2 EE database. You can use the DB2 EEE external loader to load data to a DB2 EEE database. The DB2 external loaders can insert data, replace data, restart load operations, or terminate load operations.

    Environment SQL. For relational databases, you may need to execute some SQL commands in the database environment when you connect to the database. For example, you might want to set isolation levels on the source and target systems to avoid deadlocks. You configure environment SQL in the database connection. You can use environment SQL for source, target, lookup, and stored procedure connections.

    Email. You can create email tasks in the Workflow Manager to send emails when you run a workflow. You can configure a workflow to send an email anywhere in the workflow logic, including after a session completes or after a session fails. You can also configure a workflow to send an email when the workflow suspends on error.

    Flat file targets. In the Workflow Manager, you can output data to a flat file from either a flat file target definition or a relational target definition.

    Heterogeneous targets. You can output data to different database types and target types in the same session. When you run a session with heterogeneous targets, you can specify a database connection for each relational target. You can also specify a file name for each flat file or XML target.

    New Features and Enhancements xv

  • Metadata extensions. You can extend the metadata stored in the repository by creating metadata extensions for repository objects. The Workflow Manager allows you to create metadata extensions for sessions, workflows, and worklets.

    Oracle 8 direct path load support. You can load data directly to Oracle 8i in bulk mode without using an external loader. You can load data directly to an Oracle client database version 8.1.7.2 or higher.

    Partitioning enhancements. To improve session performance, you can set partition points at multiple transformations in a pipeline. You can also specify different partition types at each partition point.

    Server variables. You can use new server variables to define the workflow log directory and workflow log count.

    Teradata TPump external loader. You can use the Teradata TPump external loader to load data to a Teradata database. You can use TPump in sessions that contain multiple partitions.

    Tips. When you start the Workflow Manager, it displays a tip of the day. These tips help you use the Workflow Manager more efficiently. You can display or hide the tips by choosing Help-Tip of the Day.

    Workflow log. In addition to session logs, you can configure the Informatica Server to create a workflow log to record details about workflow runs.

    Workflow Monitor. You use a tool called the Workflow Monitor to monitor workflows, worklets, and tasks. The Workflow Monitor displays information about workflow runs in two views: Gantt Chart view or Task view. You can run, stop, abort, and resume workflows from the Workflow Monitor.

    xvi Preface

  • About Informatica Documentation

    The complete set of printed documentation for PowerCenterRT, PowerCenter, and PowerMart includes the following books:

    Designer Guide. Provides information needed to use the Designer. Includes information to help you create mappings, mapplets, and transformations. Also includes a description of the transformation datatypes used to process and transform source data.

    Getting Started. Provides basic tutorials for getting started. Also contains documentation about the sample repository.

    Installation and Configuration Guide. Provides information needed to install and configure the PowerCenter and PowerMart tools, including details on environment variables and database connections.

    Metadata Reporter Guide. Provides information on how to install and use the web-based Metadata Reporter to generate reports on the metadata in PowerCenter and PowerMart repositories.

    Repository Guide. Provides information needed to administer the repository using the Repository Manager or the pmrep command line program. Includes details on functionality available in the Repository Manager, such as creating and maintaining repositories, folders, users, groups, and permissions and privileges.

    Transformation Language Reference. Provides syntax descriptions and examples for each transformation function provided with PowerCenter and PowerMart.

    Transformation Guide. Provides information on how to create and configure each type of transformation in the Designer.

    Troubleshooting Guide. Lists error messages that you might encounter while using PowerCenter or PowerMart. Each error message includes one or more possible causes and actions that you can take to correct the condition.

    Workflow Administration Guide. Provides information to help you create and run workflows in the Workflow Manager, as well as monitor workflows in the Workflow Monitor. Also contains information on administering the Informatica Server and performance tuning.

    Documentation available with our other products includes:

    Informatica Metadata Exchange SDK User Guide. Provides information about the second generation of Metadata Exchange interfaces for PowerCenter and PowerMart repositories.

    Informatica PowerChannel User Guide. Provides information on how to transport compressed and encrypted data through a secure channel.

    PowerConnect for IBM MQSeries User and Administrator Guide. Provides information to install PowerConnect for IBM MQSeries, build mappings, extract data from message queues, and load data to message queues.

    About Informatica Documentation xvii

  • PowerConnect for PeopleSoft User and Administrator Guide. Provides information to install PowerConnect for PeopleSoft, extract data from PeopleSoft systems, build mappings, and run workflows to load PeopleSoft source data into a warehouse.

    PowerConnect for SAP BW User and Administrator Guide. Provides information to install and configure PowerConnect for SAP BW to load source data into an SAP Business Information Warehouse.

    PowerConnect for SAP R/3 Analytic Business Components Guide. Provides information on installing and working with Analytic Business Components for PowerConnect for SAP R/3, including descriptions of repository objects and how you can use them to load a data warehouse.

    PowerConnect for SAP R/3 User and Administrator Guide. Provides information to install PowerConnect for SAP R/3, build mappings, and run workflows to extract data from SAP R/3 and load data into SAP R/3.

    PowerConnect for Siebel User and Administrator Guide. Provides information to install PowerConnect for Siebel, extract data from Siebel systems, build mappings, and run workflows to load Siebel source data into a data warehouse.

    PowerConnect for TIBCO User and Administrator Guide. Provides information to install PowerConnect for TIBCO, build mappings, extract data from TIBCO messages, and load data into TIBCO messages.

    PowerConnect Software Development Kit Developer Guide. Provides information to install PowerConnect SDK and build plug-ins to extract data from third-party applications and load data into third-party applications.

    Metadata Exchange for Data Models User Guide. Provides information on how to extract metadata from leading data modeling tools and import it into PowerCenter/PowerMart repositories through Informatica Metadata Exchange SDK.

    Metadata Exchange for OLAP User Guide. Provides information on how to use export multi-dimensional metadata from PowerCenter/PowerMart repositories into the Hyperion Integration Server through Informatica Metadata Exchange SDK.

    xviii Preface

  • About this Book

    The Metadata Reporter Guide provides information on how to install, configure, and use the Metadata Reporter. It also describes the reports that you can generate with the Metadata Reporter. It is written for the web administrator who installs and administers web applications and for the developer who administers the data warehouse.

    This guide assumes you have knowledge of web servers and servlet engines, relational database drivers, and PowerCenter and PowerMart. For additional information on related web server issues, refer to your web server documentation.

    The material in this book is available for online use.

    About PowerCenter and PowerMartThis guide contains information about PowerCenterRT, PowerCenter, and PowerMart. The documentation explicitly mentions software features that differ between the products.

    If You Are Using PowerCenterRTWith PowerCenterRT, you receive all product functionality, including the ability to register multiple servers, share metadata across repositories, and partition pipelines. PowerCenterRT includes the Zero Latency engine, which enables real-time, high performance, data integration for business analytics and operational data stores.

    A PowerCenterRT license lets you create a single repository that you can configure as a global repository, the core component of a PowerCenterRT domain.

    When this guide mentions a PowerCenterRT Server, it is referring to an Informatica Server with a PowerCenterRT license.

    If You Are Using PowerCenterWith PowerCenter, you receive all product functionality, including the ability to register multiple servers, share metadata across repositories, and partition pipelines.

    A PowerCenter license lets you create a single repository that you can configure as a global repository, the core component of a PowerCenter domain.

    When this guide mentions a PowerCenter Server, it is referring to an Informatica Server with a PowerCenter license.

    If You Are Using PowerMartThis version of PowerMart includes all features except distributed metadata, multiple registered servers, and pipeline partitioning. Also, the various PowerConnect products available with PowerCenter or PowerCenterRT are not available with PowerMart.

    About this Book xix

  • When this guide mentions a PowerMart Server, it is referring to an Informatica Server with a PowerMart license.

    Document ConventionsThis guide uses the following formatting conventions:

    If you see It means

    italicized text The word or set of words are especially emphasized.

    boldfaced text Emphasized subjects.

    italicized monospaced text This is the variable name for a value you enter as part of an operating system command. This is generic text that should be replaced with user-supplied values.

    Note: The following paragraph provides additional facts.

    Tip: The following paragraph provides suggested uses.

    Warning: The following paragraph notes situations where you can overwrite or corrupt data, unless you follow the specified procedure.

    monospaced text This is a code example.

    bold monospaced text This is an operating system command you enter from a prompt to execute a task.

    xx Preface

  • Other Informatica Resources

    In addition to the product manuals, Informatica provides these other resources:

    Informatica Webzine

    Informatica web site

    Informatica Developer Network

    Informatica Technical Support

    Accessing the Informatica WebzineThe Informatica Documentation Team delivers an online journal, the Informatica Webzine. This journal provides solutions to common tasks, conceptual overviews of industry-standard technology, detailed descriptions of specific features, and tips and tricks to help you develop data warehouses.

    The Informatica Webzine is a password-protected site that you can access through the Customer Portal. The Customer Portal has an online registration form for login accounts to its webzine and web support. To register for an account, go to the following URL:

    http://my.Informatica.com/

    If you have any questions, please email [email protected]

    To better serve your needs, the Informatica Documentation Team welcomes all comments and suggestions. You can send comments and suggestions to:

    [email protected]

    Visiting the Informatica Web SiteYou can access Informaticas corporate web site at http://www.informatica.com. The site contains information about Informatica, its background, upcoming events, and locating your closest sales office. You will also find product information, as well as literature and partner information. The services area of the site includes important information on technical support, training and education, and implementation services.

    Visiting the Informatica Developer Network The Informatica Developer Network is a web-based forum for third-party software developers. You can access the Informatica Developer Network at http://devnet.informatica.com. The site contains information on how to create, market, and support customer-oriented add-on solutions based on Informaticas interoperability interfaces.

    Other Informatica Resources xxi

  • Obtaining Technical SupportThere are many ways to access Informatica technical support. You can call or email your nearest Technical Support Center listed below or you can use our WebSupport Service.

    Both WebSupport and our Customer Site require a user name and password. To receive a user name and password, please contact us at [email protected] or call 866-563-6332 or 650-385-5800.

    North America / South America Africa / Asia / Australia / Europe

    Informatica Corporation2100 Seaport Blvd.Redwood City, CA 94063Phone: 866.563.6332 or 650.385.5800Fax: 650.213.9489Hours: 6 a.m. - 6 p.m. (PST/PDT)email: [email protected]

    Informatica Software Ltd.6 Waltham ParkWaltham Road, White WalthamMaidenhead, BerkshireSL6 3TNPhone: 44 870 606 1525Fax: +44 1628 511 411Hours: 9 a.m. - 5:30 p.m. (GMT)email: [email protected]

    BelgiumPhone: +32 15 281 702Hours: 9 a.m. - 5:30 p.m. (local time)

    FrancePhone: +33 1 41 38 92 26Hours: 9 a.m. - 5:30 p.m. (local time)

    GermanyPhone: +49 1805 702 702Hours: 9 a.m. - 5:30 p.m. (local time)

    NetherlandsPhone: +31 306 082 089Hours: 9 a.m. - 5:30 p.m. (local time)

    SingaporePhone: +65 322 8589Hours: 9 a.m. - 5 p.m. (local time)

    SwitzerlandPhone: +41 800 81 80 70Hours: 8 a.m. - 5 p.m. (local time)

    xxii Preface

  • C h a p t e r 1

    Understanding the Metadata Reporter

    This chapter includes the following topics:

    Overview, 2

    Metadata Reporter Framework, 3

    Interface, 5

    Security, 6

    Before You Begin Installing the Metadata Reporter, 7

    1

  • Overview

    The Metadata Reporter is a web-based application that allows you to run reports against any repository metadata. Informatica does not support direct access into the repository metadata. The Metadata Reporter allows you to examine your metadata without directly accessing the repository. You do not have to understand the underlying tables in the repository or know SQL or the transformation language to run the Metadata Reporter and access information you need about your repository.

    You can install the Metadata Reporter on a server with a UNIX or Windows operating system running an appropriate web server. You can run the Metadata Reporter using a browser on any workstation that can connect to the web server.

    The Metadata Reporter can generate reports on metadata in repositories that use different character codes. See Code Pages in the Installation and Configuration Guide for the list of code pages that PowerCenter and PowerMart support.

    The Metadata Reporter provides the following benefits:

    The Metadata Reporter is comprehensive. You can run reports on any repository. The reports provide information about all types of metadata objects.

    The Metadata Reporter is easily accessible. Because the Metadata Reporter is web-based, you can generate reports from any machine that has access to the web server where the Metadata Reporter is installed. You do not need direct access to the repository database, your sources or targets, or PowerCenter or PowerMart.

    The Metadata Reporter allows you to go from one report to another easily. The name of any metadata object that displays on a report links to an associated report. As you view a report, you can generate reports for objects on which you need more information.

    The reports in the Metadata Reporter are customizable. The Metadata Reporter allows you to set parameters for the metadata objects to include in the report.

    The Metadata Reporter gives you insight into your repository that enhances your ability to analyze and manage your repository efficiently.

    2 Chapter 1: Understanding the Metadata Reporter

  • Metadata Reporter Framework

    You install the Metadata Reporter on a web server. On the machine where you have the web server you also need to install database drivers. The Metadata Reporter uses the database drivers to connect to the database server where the repository resides. The web server, Metadata Reporter, and the database drivers must all be installed on the same machine. You can use a browser on any workstation to connect to the web server and run the Metadata Reporter.

    Figure 1-1 illustrates where the different components of the Metadata Reporter reside in a typical network. Although this diagram shows the web server and repository on separate servers, they can all be on the same machine.

    Web ServerYou can run the Metadata Reporter with BEA WebLogic Server 6.1. You may be able to run the Metadata Reporter servlet with another web server that runs the Java Virtual Machine (JVM) and supports the Java Servlet API.

    Web BrowserAlthough the Metadata Reporter is browser-independent, it requires a browser that supports JavaScript and accepts cookies. Most browsers support JavaScript. However, some early browsers might not support JavaScript, so make sure that you use a recent version of your browser. Also make sure that you configure your browser to accept cookies from the Metadata Reporter.

    Figure 1-1. Metadata Reporter Framework

    Repository Database

    Metadata Reporter

    Database DriversBrowser

    BrowserBrowser

    Web Server

    Metadata Reporter Framework 3

  • Database ConnectivityThe JDBC (Java Database Connectivity) API is the fastest way for the Metadata Reporter to connect to the repository. The JDBC API is a Java programming interface from Sun that provides a standard for Java applications to access databases. The API enables the Metadata Reporter servlet to connect to a repository database quickly with native JDBC drivers. Informatica recommends that you use JDBC drivers to connect to repositories from the Metadata Reporter.

    You can also use ODBC (Open Database Connectivity) to connect to the repository. The JDBC-ODBC bridge enables ODBC drivers to be used as JDBC drivers. Although it is slower than native JDBC drivers, the JDBC-ODBC bridge provides a way for the Metadata Reporter to access some data sources for which there are no JDBC drivers. You can use any ODBC driver with the Metadata Reporter that you use with PowerCenter and PowerMart. For more information on using ODBC drivers in PowerCenter and PowerMart, see Using ODBC in the Installation and Configuration Guide.

    4 Chapter 1: Understanding the Metadata Reporter

  • Interface

    The Metadata Reporter application window has two sections:

    Control Frame. Set up and start reports in this section. On the Control Frame, you can click any of several icons that represent the reports available, or you can select other reports available in the custom report list. You can also set parameters to customize your reports in the Control Frame.

    Content Frame. Reports display in this section. When you start the Metadata Reporter, the Content Frame displays brief instructions on how to run reports. When you click Report, the report you select displays on the Content Frame.

    Figure 1-2 shows the Control Frame and the Content Frame at the start of the Metadata Reporter application:

    Figure 1-2. Metadata Reporter Control and Content Frames

    Control Frame

    Content Frame

    Custom Report List

    Interface 5

  • Security

    Safeguard the Metadata Reporter URL and make it available to only those who are allowed access to the repository. The Metadata Reporter is not secure. There is no mechanism in the Metadata Reporter to limit user access or to control repository privileges.

    When you set up the Metadata Reporter, you create a file with a user name and password for each repository you want to access. The Metadata Reporter uses this username and password when it logs into a repository database. You might want to create separate user accounts with read-only access to each repository database. Configure the Metadata Reporter to use these read-only accounts to access the repositories. Once you set up the Metadata Reporter, you can run the Metadata Reporter from a browser without logging into the repository database. The Metadata Reporter automatically accesses the repository using the read-only accounts.

    Make sure that only those who are authorized can access your repository metadata with the Metadata Reporter.

    Warning: The Informatica repository tables have an open architecture. Although you can view the repository tables, Informatica strongly advises against altering the tables or data within the tables. Informatica is not responsible for any corrupt data caused by customer alteration of the repository tables or data within those tables.

    6 Chapter 1: Understanding the Metadata Reporter

  • Before You Begin Installing the Metadata Reporter

    Before you install and configure the Metadata Reporter, you need to have a number of components installed and working correctly. The system administrators for each of these systems must perform the installation and configuration tasks for their respective systems.

    Required ComponentsBefore you install the Metadata Reporter, ensure you have the following components installed and working correctly:

    PowerCenter or PowerMart with a repository. You use the Metadata Reporter to generate reports on repository metadata. Therefore, you need to install PowerCenter or PowerMart correctly and create at least one repository database.

    Since the Metadata Reporter needs to be installed with a web server, do not install it at the same time you install PowerCenter or PowerMart.

    Database drivers. The Metadata Reporter connects to the repository database with a database driver. Therefore, you need to install a database driver on the machine where you install the Metadata Reporter. Make sure that you can connect to the repository database from the Metadata Reporter machine.

    Informatica recommends that you use a JDBC driver to connect to the repository from the Metadata Reporter. If you use a JDBC driver, install and configure it according to the instructions from the database vendor. Verify that you can connect to the repository.

    If you use ODBC drivers, install them correctly and create a system ODBC data source name for your repository database. Verify that you can successfully connect to the repository database with the ODBC driver. You can use any ODBC driver with the Metadata Reporter that you use with PowerCenter and PowerMart. For more information on creating data source names, see Using ODBC in the Installation and Configuration Guide.

    Web browser. You access the Metadata Reporter through a browser. The Metadata Reporter displays reports on a web browser that supports JavaScript and accepts cookies.

    You can use the following web browsers with the Metadata Reporter:

    Microsoft Internet Explorer 5.0 or higher

    Netscape 4.5 or higher

    Generally, you can use the Metadata Reporter with any web browser that supports JavaScript and cookies.

    Installation OverviewAfter you install and verify the required components, you are ready to begin the Metadata Reporter installation process.

    Before You Begin Installing the Metadata Reporter 7

  • The Metadata Reporter installation program requires that you install the Metadata Reporter into the applications directory of a web server. Therefore, you must install and configure the web server before you install the Metadata Reporter. In general, you complete the following steps to install the Metadata Reporter:

    1. Install BEA WebLogic Server 6.1.

    2. Configure the WebLogic Server.

    3. Test the web server.

    4. Install the Metadata Reporter.

    5. Deploy the Metadata Reporter on the WebLogic Server.

    6. Configure the Metadata Reporter.

    Step 1. Installing BEA WebLogic Server 6.1You can use BEA WebLogic Server 6.1 with the Metadata Reporter. For more information, see Installing on WebLogic under Windows on page 11 or Installing on WebLogic under UNIX on page 23.

    For information on installing the Metadata Reporter with IBM WebSphere, see the Supplemental Guide.

    Step 2. Configuring the WebLogic ServerAfter you install the WebLogic Server, you need to configure the server to work with the Metadata Reporter. You add a file to WebLogic 6.1, which enables the WebLogic Server to work with the Metadata Reporter. You disable a file so the Metadata Reporter parsers can work with the WebLogic Server. Finally, you configure the classpath to locate and recognize the file you added to the library directory. For information on configuring the server with Windows, see Step 2. Configuring the WebLogic Server on page 16. For information on configuring the server for UNIX, see Step 2. Configuring the WebLogic Server on page 27.

    Step 3. Testing the WebLogic ServerAfter you install the BEA WebLogic Server, you test it to ensure that it runs properly. For information on testing the WebLogic Server on Windows, see Step 3. Testing the WebLogic Server Installation on page 17. For information on testing the WebLogic Server on UNIX, see Step 3. Testing the WebLogic Server Installation on page 28.

    Step 4. Installing the Metadata ReporterAfter you verify that the web server runs properly, you are ready to install the Metadata Reporter. The Metadata Reporter must be installed into the applications directory of the web server.

    8 Chapter 1: Understanding the Metadata Reporter

  • The web application directory is the directory in which the Metadata Reporter files reside. When you install the Metadata Reporter, it creates an imr folder or directory and creates the following subdirectories:

    en

    Help

    ja

    WEB-INF

    The class and library files are located under the WEB-INF directory. For information on installing the Metadata Reporter on Windows, see Step 4. Installing the Metadata Reporter on page 18. For information on installing the Metadata Reporter on UNIX, see Step 4. Installing the Metadata Reporter on page 29.

    Step 5. Deploying the Metadata ReporterAfter you install the Metadata Reporter as a web application, you deploy it on the WebLogic Server, which enables the server to locate and recognize the Metadata Reporter files. You then verify that it is deployed as a web application in the WebLogic console. For information on deploying the Metadata Reporter on Windows, see Step 5. Deploying the Metadata Reporter on page 20. For information on deploying the Metadata Reporter on UNIX, see Step 5. Deploying the Metadata Reporter on page 30.

    Step 6. Configuring the Metadata ReporterAfter you deploy the Metadata Reporter on the web server, you need to configure the Metadata Reporter to enable it to connect to the repository. The Metadata Reporter has a setup tool that enables you to configure the following settings:

    The location of the Metadata Reporter files

    The connectivity information that enables the Metadata Reporter to access each repository

    The class names of your additional JDBC drivers

    For information on how to configure these settings, see Configuring the Metadata Reporter on page 33.

    Before You Begin Installing the Metadata Reporter 9

  • 10 Chapter 1: Understanding the Metadata Reporter

  • C h a p t e r 2

    Installing on WebLogic under Windows

    This chapter includes the following topics:

    Overview, 12

    Step 1. Installing the WebLogic Server, 13

    Step 2. Configuring the WebLogic Server, 16

    Step 3. Testing the WebLogic Server Installation, 17

    Step 4. Installing the Metadata Reporter, 18

    Step 5. Deploying the Metadata Reporter, 20

    11

  • Overview

    You can run the Metadata Reporter on the BEA WebLogic Server version 6.1.

    For information on installing Metadata Reporter on IBM WebSphere, see the Supplemental Guide.

    Note: You cannot install the BEA WebLogic Server on top of a previously installed BEA WebLogic Server 6.0 or 6.1 installation. You must first uninstall the previous version of the BEA WebLogic Server.

    After you complete the steps listed in Before You Begin Installing the Metadata Reporter on page 7, you are ready to install and configure the Metadata Reporter on the WebLogic Server.

    Complete the following steps to install and configure the Metadata Reporter on WebLogic:

    1. Install the WebLogic Server.

    2. Configure the WebLogic Server.

    3. Test the WebLogic Server installation.

    4. Install the Metadata Reporter.

    5. Deploy the Metadata Reporter on WebLogic.

    After you complete these steps, you need to configure the Metadata Reporter. For information on configuring the Metadata Reporter, see Configuring the Metadata Reporter on page 33.

    12 Chapter 2: Installing on WebLogic under Windows

  • Step 1. Installing the WebLogic Server

    Before you install the Metadata Reporter, you must install the WebLogic Server.

    To install the WebLogic Server:

    1. Stop running web servers.

    2. Run the WebLogic installer application.

    The installation program welcomes you to WebLogic 6.1.

    3. Click Next.

    4. Accept the terms of the license agreement, and then click Next.

    The Installation program displays information about WebLogic.

    5. Click Next.

    6. Choose to install a server with or without examples, and then click Next.

    Step 1. Installing the WebLogic Server 13

  • 7. Specify a directory in which to install the web server.

    You can create a new home directory or use an existing home directory. The following example shows the default directory for BEA:

    C:\bea

    8. Click Next

    9. Specify a product installation directory.

    The following example shows the default product directory for BEA:

    C:\BEA\wlserver6.1

    You can browse to choose another directory, or use an existing BEA home directory.

    10. Click Next.

    14 Chapter 2: Installing on WebLogic under Windows

  • 11. Specify a domain name, a server name, a listen port and a secure listen port.

    The default values are shown in the following dialog box:

    12. Choose No when the installation program asks if you would like to install WebLogic as a Windows service.

    13. Click Next.

    14. Enter a system password that is between 8 and 20 characters in length, and verify the password.

    15. Click Install, and then click Finish to exit the installation program.

    Step 1. Installing the WebLogic Server 15

  • Step 2. Configuring the WebLogic Server

    After you install the WebLogic Server, you need to configure the server to work with the Metadata Reporter. You add the CR064391_rel610sp2.jar file to WebLogic 6.1, which enables the WebLogic Server to work with the Metadata Reporter. You disable the xmlx.jar file by renaming it. This allows the Metadata Reporter parsers to work with the WebLogic Server.

    To configure the WebLogic Server:

    1. Locate the following file from the downloads directory on the PowerCenter/PowerMart installation CD:

    CR064391_rel610sp2.jar

    2. Copy it to the WebLogic library directory.

    The following example shows the library directory when you choose default settings during the WebLogic installation:

    c:\bea\wlserver6.1\lib

    3. Disable the xmlx.jar file in the WebLogic library directory by renaming it.

    Use a name such as Backup_xmlx.jar, so that you can locate the file.

    Note: Informatica does not recommend you remove this file, as you may need it to run other applications.

    4. Locate the startWebLogic.cmd file.

    The following example shows the location of the WebLogic.cmd file when you choose default settings during the WebLogic installation:

    C:\bea\wlserver6.1\config\mydomain

    5. Right-click on the file, and choose Edit to open it.

    6. Modify the classpath to include the file you copied into the WebLogic library directory.

    Place the .jar file at the beginning of the classpath. The following example shows the classpath after the CR064391_sp2.jar file is added:

    set CLASSPATH=.;.\lib\CR064391_rel610sp2.jar;.\lib\j2ee12.jar;.\lib\weblogic_sp.jar;.\lib\weblogic.jar

    7. Save the changes to startWebLogic.cmd.

    16 Chapter 2: Installing on WebLogic under Windows

  • Step 3. Testing the WebLogic Server Installation

    After you configure the WebLogic Server, verify that you can start it by testing the default server included in the WebLogic installation.

    To verify the WebLogic Server installation:

    1. Choose Start Default Server from the Windows Start menu.

    2. Log onto the default server using the system identity and password you set when you installed the WebLogic Server.

    3. Verify that the server starts.

    The server starts in development mode by default. The following example shows the server start message that displays if you choose default settings during WebLogic installation:

    Step 3. Testing the WebLogic Server Installation 17

  • Step 4. Installing the Metadata Reporter

    After you test the WebLogic Installation, you are ready to install the Metadata Reporter.

    To Install the Metadata Reporter:

    1. Stop the WebLogic Server.

    2. Launch the Informatica Platform installation program from the PowerCenter/PowerMart installation CD.

    The installation program welcomes you to the Informatica platform setup.

    3. Click Next.

    4. Select the Metadata Reporter, and then click Next.

    The installation program welcomes you to the Informatica Metadata Reporter setup.

    5. Click Next.

    The installation program alerts you that you must have a suitable web server installed.

    6. Click Next.

    7. Click Browse to specify the destination folder for installing the Metadata Reporter.

    This folder must be the applications directory of the WebLogic Server. The following example shows the location of the applications directory if you accept default settings when you install WebLogic:

    C:\bea\wlserver6.1\config\mydomain\applications

    18 Chapter 2: Installing on WebLogic under Windows

  • 8. Click Next to begin the installation.

    The Metadata Reporter creates an imr directory with the following subdirectories:

    en

    Help

    ja

    WEB-INF

    The class and library files are located under the WEB-INF directory.

    9. Exit when the Metadata Reporter installation program informs you that the installation has completed.

    You do not need to restart the machine.

    Step 4. Installing the Metadata Reporter 19

  • Step 5. Deploying the Metadata Reporter

    After you install the Metadata Reporter as a web application, you deploy it on the WebLogic Server, which enables the server to locate and recognize the Metadata executable and non-executable files. You then verify that it is deployed as a web application in the WebLogic console.

    To deploy the Metadata Reporter:

    1. Choose Start Default Console from the Windows Start menu, and log onto the console.

    The console welcomes you to the BEA WebLogic Server.

    2. Click the Web Applications node in the left panel.

    The Web Applications table displays in the right pane listing all deployed web applications.

    3. Click Install a New Web Application.

    4. Enter the location of the imr folder you installed on the WebLogic Server, or click Browse navigate to the folder.

    The following example shows the location of the imr folder when you install WebLogic using default settings:

    C:\bea\wlserver6.1\config\mydomain\applications\imr\

    20 Chapter 2: Installing on WebLogic under Windows

  • 5. Click the Web Applications node in the left pane.

    The Web Application table displays in the right pane listing deployed web applications. An imr entry displays in the table:

    6. Click imr.

    The Web Applications Descriptor screen displays. The Descriptor screen lists the name, URL, path, deployment order, and deployed status of the Web Application.

    imr Deployed

    Deployment Status

    Step 5. Deploying the Metadata Reporter 21

  • 7. Verify that the Deployed checkbox is selected.

    8. Click the Targets tab, and verify that myserver is chosen.

    9. Close the WebLogic Server console.

    Now you are ready to configure the Metadata Reporter. For information on configuring the Metadata Reporter, see Configuring the Metadata Reporter on page 33.

    myserver

    22 Chapter 2: Installing on WebLogic under Windows

  • C h a p t e r 3

    Installing on WebLogic under UNIX

    This chapter includes the following topics:

    Overview, 24

    Step 1. Installing the WebLogic Server, 25

    Step 2. Configuring the WebLogic Server, 27

    Step 3. Testing the WebLogic Server Installation, 28

    Step 4. Installing the Metadata Reporter, 29

    Step 5. Deploying the Metadata Reporter, 30

    23

  • Overview

    You can run the Metadata Reporter on the BEA WebLogic Server version 6.1.

    For information on installing Metadata Reporter on IBM WebSphere, see the Supplemental Guide.

    Note: You cannot install the BEA WebLogic Server on top of a previously installed BEA WebLogic Server 6.0 or 6.1 installation. You must first uninstall the previous version of the BEA WebLogic Server.

    After you complete the steps listed in Before You Begin Installing the Metadata Reporter on page 7, you are ready to install and configure the Metadata Reporter on the WebLogic Server.

    Complete the following steps to install and configure the Metadata Reporter on WebLogic:

    1. Install the WebLogic Server.

    2. Configure the WebLogic Server.

    3. Test the WebLogic Server installation.

    4. Install the Metadata Reporter.

    5. Deploy the Metadata Reporter.

    24 Chapter 3: Installing on WebLogic under UNIX

  • Step 1. Installing the WebLogic Server

    Before you install the Metadata Reporter, you must install the WebLogic Server.

    To install the WebLogic Server on Unix:

    1. Locate the WebLogic installer for UNIX.

    You will need the java installer wrapped in a shell script bundled with JDK 1.3.1 with a filename ending in .bin.

    2. Log onto the target UNIX system, and open a command line shell.

    3. Enter the following command to invoke the installation procedure:

    sh filename.bin -i console

    where filename is the name of the WebLogic Server installer specific to your platform.

    4. Select a language to use during installation.

    The installation program welcomes you to WebLogic 6.1.

    5. Press Enter.

    6. Press Enter to accept the terms of the license agreement.

    7. Choose to install a server with or without examples.

    8. Specify a BEA home directory.

    If you enter a new directory, you must enter the full pathname. The following example shows the default BEA home directory:

    /home3/bea

    9. Choose a product directory.

    The following example shows the default product directory:

    /home3/bea/wlserver6.1

    10. Select a number from the following list to accept or modify the default configuration values.

    11. Enter values for each setting you want to modify, and press Enter to save the value.

    Setting Default Value

    1- Modify WebLogic Admin Domain Name mydomain

    2- Modify Server Name myserver

    3- Modify Listen Port 7001

    4- Modify Secure SSL Listen Port 7002

    5- Done Configuration n/a

    Step 1. Installing the WebLogic Server 25

  • 12. Enter 5 to indicate you completed the configuration.

    13. Enter a system password that contains between 8 and 20 characters.

    The program begins installing and notifies you when the installation completes.

    14. Press Enter to exit the installation program.

    26 Chapter 3: Installing on WebLogic under UNIX

  • Step 2. Configuring the WebLogic Server

    After you install the WebLogic Server, you need to configure the server to work with the Metadata Reporter. You add the CR064391_rel610ap2.jar file to the WebLogic 6.1 library directory, which enables the WebLogic Server to work with the Metadata Reporter. You disable the xmlx.jar file by renaming it. This allows the Metadata Reporter parsers to work with the WebLogic Server.

    To configure the WebLogic Server:

    1. Locate the following file from the downloads directory on the PowerCenter/PowerMart Installation CD:

    CR64391_rel610sp2.jar

    2. Copy it to the WebLogic library directory.

    The following example shows the location of the library directory when you choose default settings during the WebLogic installation:

    /home3/bea/wlserver6.1/lib

    3. Disable the xmlx.jar file in the WebLogic library directory by renaming it.

    Use a name such as Backup_xmlx.jar, so that you can locate the file later.

    Note: Informatica does not recommend you remove this file, as you may need it to run other applications.

    4. Locate the startWebLogic.sh file.

    The following example shows the location of the startWebLogic.sh file when you choose default settings during the WebLogic installation:

    /home3/bea/wlserver6.1/config/mydomain

    5. Open the file for editing.

    6. Modify the classpath to include the .jar file you copied into the WebLogic library directory.

    Place the file at the beginning of the classpath. The following example shows the classpath after the file is added:

    set classpath=.;./lib/CR064391_rel610sp2.jar;./lib/j2ee12.jar;./lib/weblogic_sp.jar;./lib/weblogic.jar

    7. Save the changes to the startWebLogic.sh file.

    Step 2. Configuring the WebLogic Server 27

  • Step 3. Testing the WebLogic Server Installation

    After you configure the WebLogic Server, verify that you can start it by testing the default server included in the WebLogic installation.

    To verify the WebLogic Server installation:

    1. Start the WebLogic default server by entering the following command:

    ./startWebLogic.sh

    2. Log onto the server using the system identity and password you set when you installed the WebLogic Server.

    3. Verify that the server starts.

    The server starts in development mode by default. The following example shows the server start message that displays if you choose default settings during WebLogic installation:

    28 Chapter 3: Installing on WebLogic under UNIX

  • Step 4. Installing the Metadata Reporter

    After you verify that the WebLogic Server is configured properly, you are ready to install the Metadata Reporter.

    To install the Metadata Reporter:

    1. Stop the WebLogic Server by entering the following command:

    CTRL-C

    2. Mount the installation PowerCenter/PowerMart CD and locate the Unixserv directory.

    3. Choose AIX, HP-UX, or Solaris.

    4. Open the installation program.

    Using a Bourne shell, type ./install.

    Using a C-shell, type sh install.

    5. Select the appropriate language.

    6. Enter the product key.

    7. Choose to install Metadata Reporter.

    8. Specify a directory in which to install the Metadata Reporter.

    Enter the path of the applications directory of the WebLogic Server you installed. The following example shows the location of the applications directory if you accept default settings during the WebLogic installation:

    /home3/BEA/wlserver6.1/config/mydomain/applications

    The Metadata Reporter creates an imr directory with the following subdirectories:

    en

    Help

    ja

    WEB-INF

    The Metadata Reporter places the class and library files in the WEB-INF directory. The program notifies you when the installation is complete.

    9. Press Enter. The installation program returns to the main menu.

    10. Enter 0 to exit the installation program.

    Step 4. Installing the Metadata Reporter 29

  • Step 5. Deploying the Metadata Reporter

    After you install the Metadata Reporter as a web application, you deploy it on the WebLogic Server, which enables the server to locate and recognize the Metadata executable and non-executable files. You then verify that it is deployed as a web application in the WebLogic console.

    1. Start the WebLogic Server console by pointing your web browser to the following URL if the web browser is on the same machine as your host:

    http://localhost:7001/console

    If the web browser is on a different machine from the host, point your browser to the following URL:

    http://:7001/console

    2. Click the Web Applications node in the left pane.

    The Web Applications table displays in the right pane listing deployed web applications.

    3. Click Install a New Web Application.

    4. Enter or navigate to the imr directory you installed on the WebLogic Server.

    The following example shows the location of imr when you install WebLogic using default settings:

    /home3/bea/wlserver6.1/config/mydomain/applications/imr/

    5. Click the Web Applications node in the left pane.

    30 Chapter 3: Installing on WebLogic under UNIX

  • The Web Application table displays in the right pane listing all deployed web applications. An imr entry should appear in the table.

    6. Click imr to open the Web Applications Descriptor screen.

    The descriptor screen lists the name, URL, path, deployment order, and deployed status of the Web Application.

    7. Verify that the Deployed checkbox is selected.

    imr Deployed

    Deployment Status

    Step 5. Deploying the Metadata Reporter 31

  • 8. Click the Targets tab, and verify that myserver is chosen.

    9. Close the WebLogic Server console.

    Now you are ready to configure the Metadata Reporter. For information on configuring the Metadata Reporter, see Configuring the Metadata Reporter on page 33.

    myserver

    32 Chapter 3: Installing on WebLogic under UNIX

  • C h a p t e r 4

    Configuring the Metadata Reporter

    This chapter includes the following topics:

    Overview, 34

    Configuring the Metadata Reporter, 35

    Troubleshooting, 41

    33

  • Overview

    Once you deploy the Metadata Reporter on the web server, you can configure the Metadata Reporter.

    The Metadata Reporter has a setup tool that enables you to configure the Metadata Reporter properties and set it up to connect to repositories.

    The Metadata Reporter setup saves the following information to a configuration file:

    The location of the Metadata Reporter non-executable files

    The connectivity information that enables the Metadata Reporter to access each repository

    The class names of your additional JDBC drivers

    When you install the Metadata Reporter, the installation program copies two sets of files into the web server:

    Executable files consisting of Java classes

    Non-executable files consisting of HTML and XSL files

    When you run the Metadata Reporter, it connects to the repository database directly and generates reports without requiring a user login. This is possible because the Metadata Reporter Setup saves the connectivity information for each repository in the configuration file.

    The Metadata Reporter Setup loads several common JDBC drivers. However, if you want to use a JDBC driver that the Metadata Reporter does not load, you can set it up with the Metadata Reporter Setup. For a list of the JDBC drivers that the Metadata Reporter loads, see Configuring Advanced Settings on page 38.

    34 Chapter 4: Configuring the Metadata Reporter

  • Configuring the Metadata Reporter

    After you configure the web server to recognize the Metadata Reporter, you are ready to configure the Metadata Reporter. You will need to set up configuration settings for the following sections of the Metadata Reporter:

    Locations. In the Locations section, you configure the location of the non-executable files so the Metadata Reporter can locate and use them.

    Repositories. In the Repositories section, you configure connectivity information to allow the Metadata Reporter to access repositories.

    Advanced Settings. In the Advanced Settings section, you configure any additional JDBC drivers you want to use.

    Figure 4-1 shows the sections of the Metadata Reporter configuration settings.

    Figure 4-1. Metadata Reporter Configuration Settings

    Configuring Locations SettingsYou configure locations settings so that the Metadata Reporter is able to locate and use the non-executable files you install on the WebLogic Server.

    Repositories

    Locations

    Advanced Settings

    Configuring the Metadata Reporter 35

  • To configure the Locations section of the Metadata Reporter:

    1. To start the Metadata Reporter setup, open the following URL in your web browser:

    http://:/imr/XMXConfigServlet

    2. In the Locations section, specify the file system path for the Metadata Reporter document directory. This is the path to the imr directory you set up when you install imr on WebLogic. The following example shows the default location for the imr directory if you choose default settings during the Metadata Reporter installation:

    C:\BEA\wlserver6.1\config\mydomain\applications\imr\

    Be sure to terminate the file system path with a backslash.

    3. In the Locations section, specify the following URL for the Metadata Reporter document directory:

    http:///imr/

    Be sure to terminate the URL with a slash.

    Configuring Repository SettingsYou configure repository settings so that the Metadata Reporter can connect and log onto the repository where metadata is stored.

    Locations Section

    36 Chapter 4: Configuring the Metadata Reporter

  • To configure the Repositories section of the Metadata Reporter:

    1. To start the Metadata Reporter setup, open the following URL in your web browser:

    http://:/imr/XMXConfigServlet

    2. In the Repositories section, click Add Repository. A new row appears.

    Enter the following information:

    Field Required Information

    Repository Name Alias to the repository that you want to include in your reports. Repository aliases must be in US-ASCII. The alias does not have to match the repository name listed in the Repository Manager.

    JDBC URL The JDBC driver URL. This is not the same as the document directory URL you enter in the Locations section.The syntax of the JDBC URL you use comes from the JDBC driver vendor. If you use ODBC, use the following syntax: Jdbc:odbc:The data source name is the ODBC data source name for the repository specified in the Windows ODBC Data Sources control panel.

    DB User Username to connect to the repository database. Note that t