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

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, Informatica’s 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 Informatica’s 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 Informatica’s 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.


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.


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.


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


C h a p t e r 2

Installing on WebLogic under Windows


♦ 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.


3. Test the WebLogic Server installation.


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.


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 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.


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:

<Notice><WebLogic Server><Started WebLogic Admin Server “myserver” for domain “mydomain” running in Development Mode>

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


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\


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


C h a p t e r 3

Installing on WebLogic under UNIX


♦ 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.


3. Test the WebLogic Server installation.


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


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.


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:

<Notice><WebLogic Server><Started WebLogic Admin Server “myserver” for domain “mydomain” running in Development Mode>


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://<system_name>:7001/console


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/



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


C h a p t e r 4

Configuring the Metadata Reporter


♦ 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://<host_name>:<port_number>/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://<host_name>/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


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://<host_name>:<port_number>/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:<data_source_name>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 this is the database username, not the repository username.

DB Passwd Password for the username to connect to the database. The Metadata Reporter encrypts the password. After the first time you set up a repository, the Metadata Reporter Setup does not display the password on the screen. To change the password for a repository, enter a new password into this field.

DB Type Select the repository database type from the list.

Repositories Section


It is not necessary to enter information in the Advanced Settings section. If you wish to include additional JDBC database drivers, see “Configuring Advanced Settings” on page 38.

3. Click Update to add the repository information to the Metadata Reporter configuration.

4. Click Save Settings.

5. To test the configuration, click Test Settings. The test results display in a message frame:

Move the divider bar up to increase the size of the message frame.

6. For these settings to be used by the web server, restart the web server.

You should now be able to start the Metadata Reporter.

Configuring Advanced SettingsIf you have additional JDBC drivers you would like to use, you can configure them in the Advanced Settings section. The Metadata Reporter Setup loads the following JDBC drivers to work with the Metadata Reporter:

♦ Oracle JDBC Thin Driver

♦ Informix JDBC

♦ Sybase JDBC (also known as jConnect)

♦ DB2 JDBC

♦ JDBC/ODBC Bridge

If you want to use a JDBC driver that is not in the list, you can set it up in the Metadata Reporter Setup tool. The Metadata Reporter Setup saves the JDBC driver information in the

Divider Bar

Message Frame


configuration file. The next time you run the Metadata Reporter, you can connect to a repository using the new JDBC driver. You can add up to three JDBC drivers in the Metadata Reporter Setup tool.

To configure the Advanced Settings:

1. In the Advanced Settings section, type the class name of the JDBC driver you want to use.

The JDBC driver class name is supplied by your JDBC driver vendor. Check the JDBC driver documentation for the exact syntax. For example, the following is the class name for the Oracle Thin JDBC driver:

oracle.jdbc.driver.OracleDriver

2. To verify that your entry is correct, click Test Settings.

When the Metadata Reporter Setup loads a JDBC driver, it displays the following message in the message frame:

Loading driver: User-specified driver class...

If the Metadata Reporter Setup successfully loads the new JDBC driver, no error message displays.

If the Metadata Reporter Setup cannot find or successfully load the new JDBC driver, the following status message displays in the next line in the message frame:

Couldn't load the driver: java.lang.ClassNotFoundException...

Verify that the class name for the new JDBC driver is correct and that the driver is accessible.

Advanced Settings Section


3. Click Save Settings to save the new drivers to the configuration file.

4. Restart the web server so that the settings for the new JDBC drivers can take effect.


Troubleshooting

I installed the Merant ODBC drivers that come with PowerCenter and PowerMart. In the Metadata Reporter Setup, I configured a repository that uses the Merant ODBC drivers. When I start the Metadata Reporter, I get an error message that my Merant ODBC license has expired.

Check the license file for your Merant ODBC drivers. If you have the license files named lvodbc.lic and lvdw.lic, either rename them or move them to another directory. Make sure that you only have one license file named ivdw.lic.

You can find the license file in the c:\winnt\system32 directory. The ivdw.lic file is installed when you install the Merant ODBC drivers. If you do not have the ivdw.lic license file, reinstall the Merant ODBC drivers from the PowerCenter and PowerMart CD.

Troubleshooting 41


C h a p t e r 5

Using the Metadata Reporter


♦ Accessing the Metadata Reporter, 44

♦ Customizing a Report, 45

♦ Running a Report, 47

♦ Troubleshooting, 51

43

Accessing the Metadata Reporter

The Metadata Reporter enables you to run reports on repository metadata even if you do not have the Infomatica Server or Client tools installed on your workstation. You can run the Metadata Reporter from any workstation that has a web browser and has access to the web server where the Metadata Reporter application is installed.

You can generate reports on any repository that you set up to be accessible to the Metadata Reporter. Launch a browser and type the Metadata Reporter URL on the address bar to start the Metadata Reporter.

To start the Metadata Reporter:

1. Open a web browser.

2. On the address bar, type the URL to point to the Metadata Reporter.

Similar to the Metadata Reporter Setup, the URL you use to call the Metadata Reporter depends on your web server and how the web administrator sets up the web server. Check with the web administrator to make sure you have the correct URL.

You can use the following URL to access the Metadata Reporter. This URL format is commonly used to start servlet applications:

http://webserver_name:webserver_port/servlet/XMXServlet

Table 5-1 gives a description of the elements in the URL:

Note: If you have problems starting the Metadata Reporter, check with your system administrator to make sure that you are accessing the web server correctly.

Table 5-1. Metadata Reporter URL Elements

URL Element Required/Optional Description

webserver_name Required Web server name. You can also use the IP address.

webserver_port Required Web server port.

servlet Required Java keyword. In most installations, the keyword is servlet. However, the web administrator can define other keywords.

XMXServlet Required Name of the Metadata Reporter servlet.

44 Chapter 5: Using the Metadata Reporter

Customizing a Report

You can set parameters to customize a report in the Metadata Reporter by using wildcards, selecting from lists, or clicking the Browse button. You can use wildcards for all parameters except the repository and object type parameters. Set the repository and object type by selecting from lists. You can click the Browse button to set parameters for the repository, folder, and version.

All parameters are case-sensitive, and each report has its own list of parameters. For more details regarding the parameters of each report, see “Understanding the Report Details” on page 53.

WildcardsThe Metadata Reporter supports two wildcard characters:

♦ Percent symbol (%). Represents any number of characters and spaces.

♦ Underscore (_). Represents one character or space.

You can use wildcards in any number and combination in the same parameter. Leaving a parameter blank returns all values and is the same as using %. The following examples show how you can use the wildcards to set parameters.

Suppose you have the following values available to select:

items, items_in_promotions, order_items, promotions

The following list shows the return values for some wildcard combinations you can use:

The Browse ButtonAlthough each report has its own set of parameters, the repository, folder, and version are common to most reports. You can set these three parameters individually, or you can set them all at one time by using the Browse button.

Wildcard Combination Return Values

% items, items_in_promotions, order_items, promotions

<blank> items, items_in_promotions, order_items, promotions

%items items, order_items

item_ items

item% items, items_in_promotions

___m% items, items_in_promotions, promotions

%pr_mo% items_in_promotions, promotions

Customizing a Report 45

The Browse button is next to the repository parameter. When you click Browse, all the repositories accessible by the Metadata Reporter application display. To expand the repository tree and display the folders and versions, click the [+] sign. To collapse the tree, click the [-] sign.

Figure 5-1 shows the Browse window with one repository expanded to show a folder and version:

When you click a folder name, you select a folder and its repository. When you click a version, you select a folder version, the folder, and its repository. Once you make your selection, the Browse window disappears and the repository, folder, or version you select display on the Control Frame.

Note: Use the Metadata Reporter Setup application to set up the repositories that the Metadata Reporter displays on the Browse window and the repository selection list. For more information on how to set up repositories for the Metadata Reporter, see “Configuring the Metadata Reporter” on page 33.

Figure 5-1. Metadata Reporter Browse Window


Running a Report

Set up and run all Metadata Reporter reports in the Control Frame of the browser window. To run a report, complete the following steps:

1. Select the report you want to run.

2. Set the parameter values to customize the report.

3. Click Report to display the report on the Content Frame.

or

Click Print Report to display the report on a separate browser.

4. Click the browser Print button to send the report to the printer.

Step 1. Selecting a ReportTo select a report, click the icon for the report you want to run. The icon for the selected report changes color to show that it is selected.

In addition to the report icons, you can select other reports from the list of custom reports.

The report you select continues to be selected until you click another report icon or select another report from the custom report list.

Step 2. Setting ParametersOnce you select the report, you can customize it by setting the parameter values. The Metadata Reporter always selects the first repository on the list by default. If you do not select another repository or change any of the parameters, you get a report based on the default repository. For example, if you run the Source Schema Report without setting any parameters, you get a report on all the sources in the default repository.

Step 3. Displaying the ReportYou can display a report directly on the Content Frame or in a separate browser. Click Report to display the report on the Content Frame.

Running a Report 47

Figure 5-2 shows a Metadata Reporter report on the Content Frame:

Click Print View to display the report on a separate browser that shows only the Content Frame. On the new browser, you can see a larger portion of the report on the screen. You can view two different reports at the same time by displaying one report on the Content Frame and another on a separate browser.

Figure 5-2. Report Displayed on the Content Frame


Figure 5-3 shows a report displayed on a browser without the Control Frame:

The report is ready when the following message displays on the status bar of the browser window:

Done

Use the scroll bars to view the whole report.

Step 4. Printing the ReportYou can print a report directly from the Content Frame or from a separate browser.

Figure 5-3. Report Displayed on a Separate Browser

Running a Report 49

To print the report from the Content Frame:

1. After you display the report on the Content Frame, click in the Content Frame.

2. Click the Print button on the browser toolbar to send the report to the printer.

To print the report from a separate browser:

1. Click Print View on the Control Frame to display the report on a separate browser.

2. On the new browser, click the Print button on the toolbar to send the report to the printer.

When you send a report to the printer from either the Content Frame or a separate browser, the report prints as it appears on the browser. Reports are not formatted for page breaks.

You can run all Metadata Reporter reports using the same steps. For a detailed description of the parameters and the information displayed for each report, see “Understanding the Report Details” on page 53.


Troubleshooting

I just set up a new repository for the Metadata Reporter using the Metadata Reporter Setup. When I click the Browse button in the Metadata Reporter, I cannot see the repository in the list.

When you make changes to your Metadata Reporter setup, you cannot immediately see the changes in the Metadata Reporter. You need to reinitialize the Metadata Reporter to see the changes.

You can reinitialize the Metadata Reporter by restarting the servlet with a query. Add the following to the end of the URL that you use to access the Metadata Reporter:

?restart=1

The following URL resets the Metadata Reporter:

http://webserver_name:webserver_port/servlet/XMXServlet?restart=1

For more information on the URL used to start the Metadata Reporter, see “Accessing the Metadata Reporter” on page 44.

Warning: The restart query is an administrative tool only. It reads the Metadata Reporter properties and configuration files and reconnects to the database. Informatica recommends that you use it with caution.

Troubleshooting 51


C h a p t e r 6

Understanding the Report Details


♦ Overview, 54

♦ Report Descriptions, page 55.

53

Overview

This chapter provides a detailed description of each report available in the Metadata Reporter. It describes the different sections of the report and the columns that make up the body of the report.

In general, the reports contain a header section and a main section. The header section displays the report title and some general information about the report, such as the folder and version. The main section of the report displays information in columnar format.

Most reports contain links to other related reports. The links allow you to view more details about an object or, in the case of a shortcut, view details of a related object. On reports that refer to shortcuts, the Metadata Reporter displays only local shortcuts.

Use the Metadata Reporter to generate the following reports:

♦ Completed Session Details Report. See page 55.

♦ Completed Workflow Details Report. See page 58.

♦ Completed Worklet Details Report. See page 60.

♦ Invalid Mappings Report. See page 62.

♦ Job Report. See page 64.

♦ Lookup Table Dependency Report. See page 66.

♦ Mapping Report. See page 68.

♦ Mapplet Report. See page 75.

♦ Object to Mapping/Mapplet Dependency Report. See page 79.

♦ Session List Report. See page 81.

♦ Session Details Report. See page 83.

♦ Shortcut Report. See page 87.

♦ Source Schema Report. See page 90.

♦ Source to Target Dependency Report. See page 93.

♦ Target Schema Report. See page 95.

♦ Transformation Report. See page 98.

♦ Workflow List Report. See page 103.

♦ Workflow Details Report. See page 105

♦ Worklet List Report. See page 108.

♦ Worklet Details Report. See page 110.

Many reports, such as the Mapping Report, first display lists of objects that meet the report parameters. You can click an object name in the list to display a detail report on the object. Each of these detail reports is discussed separately below.

54 Chapter 6: Understanding the Report Details

Completed Session Details Report

The Completed Session Details Report provides information about the completion of a selected session. A session provides the Informatica Server with a set of instructions on how and when to move data from sources to targets. The Completed Session Details Report contains the following sections:

♦ Session. Provides detailed information about the selected session, such as whether the session is valid and reusable, and the session start and end time.

♦ Transformation Errors. Provides information about Transformation errors encountered during the session.

♦ Source Rows. Lists the number of rows successfully read or failed when the session ran.

♦ Target Rows. Lists information about the target rows included in the session, such as the number of rows successfully written to the target.

♦ Mapping. Provides the mapping name and version number.

♦ Instance Run Details. Provides details on each instance in a session, such as the number of rows applied during the session.

To run the Completed Session Details report, click the Jobs icon on the Metadata Reporter control frame. From the Job Report, click on a workflow name. From the Completed Workflow Details Report, click on the task instance name.

Note: To view the Completed Worklet Details Report, click the worklet instance name.

Completed Session Details Report 55

Figure 6-1 shows a sample Completed Session Details Report:

Report DetailsTable 6-1 lists the information that the Completed Session Details Report displays:

Figure 6-1. Sample Completed Session Details Report

Table 6-1. Completed Session Details Report Information

Section Information Link Description

Session Session Name No Name of the session.

Status No Indicates whether the session succeeded or failed.

Start time No Time the session began.

End Time No Time the session ended.

Log File Name No Name and file path of the log file.

Error Code No The error code generated by the Informatica Server.

Error Message No The error message text.


Transformation Errors Total Transformation Errors

No The total number of transformation errors.

First Error Code No Code of the first error that occurred in the session.

First Error Message

No The text of the first error message.

Source Rows Success Rows No The number of source rows that succeeded.

Failed Rows No The number of source rows that failed.

Target Rows Success Rows No The number of target rows that succeeded.

Failed Rows No The number of target rows that failed.

Mapping Mapping Name No Name of the mapping.

Version No Version of the mapping.

Instance Run Details Instance Name No Name of the session task instance.

Partition Name No The partition number if the session contains multiple partitions. For more information about pipeline partitions, see �Pipeline Partitioning� in the Workflow Administration Guide.

Group Name No Target groups, such as the XML group.

Transformation Type

No The transformation types used in the session.

Applied Rows No The number of rows successfully applied to the target.

Affected Rows No The number of rows affected by the specified operation.

Rejected Rows No The number of rows rejected in the session.

Throughput No Rate at which the Informatica Server reads or writes rows from sources or to targets. The rate is expressed as the number of rows per second.

Last Error Message No Last error message that occurred in the session.

Start Time No Time the instance began running.

End Time No Time the instance stopped running.

Mapplet Instance Name

No Name of the mapplet instance.

Transformation Name

No Name of the transformation instance.

Table 6-1. Completed Session Details Report Information


Completed Session Details Report 57

Completed Workflow Details Report

The Completed Workflow Details Report provides information about the completion of the selected workflow. The Completed Workflow Details Report contains the following sections:

♦ Workflow Run Details. Provides details about how a workflow ran. Includes information such as run options and error messages.

♦ Instance Run Details. Provides details about each instance in a workflow, such as the status and the start and end time.

To run the Completed Workflow Details Report, click the Jobs icon on the Metadata Reporter Control Frame, and then click the workflow name. From the Completed Workflow Details Report, you can link to a Completed Session Details Report by clicking the task instance name. For more information, see “Completed Session Details Report” on page 55.

Note: To view the Completed Worklet Details Report, click a worklet instance.

Figure 6-2 shows a sample Completed Workflow Details Report:

Figure 6-2. Sample Completed Workflow Details Report


Report DetailsTable 6-2 lists the information that the Completed Workflow Details Report displays:

Table 6-2. Completed Workflow Details Report Information


Workflow Workflow Name Yes Workflow name. Links to the Workflow Details Report.

Server Name No Name of the Informatica Server that ran the workflow.

Start Time No Time the workflow started.

End Time No Time the workflow ended.

User Name No Username that ran the workflow.

Run type No Run options. For example, Run on Demand indicates that the workflow must be manually started.

Log File Name No The path and log file name.

Status No Indicates whether the workflow succeeded or failed.

Error Code No Code of the error message generated by the Informatica Server.

Error Message No Text of the error message generated by the Informatica Server.

Instance Run Details

Instance Name Yes Name of the task instance. Links to the Completed Session Details Report.

Task Name No Name of the task created in the Workflow Manager.

Task Type No Type of the task.

Status No Indicates whether the instance succeeded or failed.

Start Time No Start time of the instance.

End Time No End time of the instance.

Completed Workflow Details Report 59

Completed Worklet Details Report

The Completed Worklet Details Report lists the completed worklets in a selected folder and provides basic information about the worklet. The Completed Worklet Details Report contains the following sections:

♦ Worklet. Provides information such as status, start time, and end time of the worklet.

♦ Instance Run Details. Provides details about each instance in a worklet, such as status and the start and end time.

To run the Completed Worklet Details Report from the Completed Workflow Details Report, click on the worklet instance name.

Note: To view the Completed Worklet Details Report, the selected worklet must be nested within a workflow.

Figure 6-3 shows a sample Completed Worklet Details Report:

Figure 6-3. Sample Completed Worklet Details Report


Report DetailsTable 6-3 lists the information that the Completed Worklet Details Report displays:

Table 6-3. Completed Worklet Details Report Information


Worklet Task Name No Name of the task in the worklet.

Start Time No Time the worklet started.

End Time No Time the worklet ended.

Status No Indicates whether the worklet succeeded or failed.

Instance Run Details

Instance Name No Name of each task instance within the worklet.

Task Name No Name of the task.

Task Type No Type of the task.

Status No Whether instance of the task succeeded or failed.

Start Time No Time the instance started.

End Time No Time the instance ended.

Completed Worklet Details Report 61

Invalid Mappings Report

A mapping with errors is an invalid mapping. You can save an invalid mapping, but you cannot run a session based on it. The Invalid Mappings Report lists the invalid mappings that exist in the repository.

Run the Invalid Mappings Report by selecting it from the custom report list on the Metadata Reporter Control Frame.

Figure 6-4 shows a sample Invalid Mapping Report. The mapping name links to a Mapping report:

ParametersTable 6-4 shows the parameters you can set to customize an Invalid Mappings Report:

Figure 6-4. Sample Invalid Mappings Report

Table 6-4. Invalid Mappings Report Parameters

Parameter Description

Repository Select the repository that stores the invalid mapping.

Folder Name Select the folder that stores the invalid mapping.

Version Name Select the version of the invalid mapping.

Mapping Name Select the invalid mapping to include in the report.


You can use wildcards to set parameters. If you do not set any parameter, the Metadata Reporter generates a report on all invalid mappings in the selected repository. For more information on setting the report parameters, see “Customizing a Report” on page 45.

Report DetailsTable 6-5 lists the information that the Invalid Mappings Report displays:

Table 6-5. Invalid Mapping Report Information

Information Link Description

Mapping Name Yes Invalid mapping name. Links to a Mapping Report.

Last Saved No Date and time the mapping was last saved.

Comments No Comments associated with the mapping.

Invalid Mappings Report 63

Job Report

The Job Report allows you to access completed job reports, which display details about how and when a job ran, and whether it ran successfully.

To run the Job Report, click the Job Report icon on the Metadata Reporter control frame. From the Job Report, you can link to further levels of detail by clicking the workflow to open the Completed Workflow Details Report. From the Completed Workflow Details report, click a worklet instance to view the Completed Worklet Details Report or click a task instance to view the Session Details Completion Report.

Note: To view the Completed Worklet Report, the selected worklet must be nested within a workflow.

Figure 6-5 shows a sample Job Report.

Figure 6-5. Sample Job Report


Parameters Table 6-6 lists the parameters you can set to customize a Job Report:

You can use wildcards to set parameters. If you do not set any parameters, the Metadata Reporter generates a report for all completed workflows in the selected repository. For more information on setting the report parameters, see “Customizing a Report” on page 45.

Report DetailsTable 6-7 lists the information that the Job Report displays:

Table 6-6. Job Report Parameters


Repository Select the repository that stores the session.

Folder Name Select the folder that stores the session.

Workflow Name Select the workflow to include in the report.

Table 6-7. Job Report Information


Workflow List Workflow Name Yes Name of the workflow. Links to the Completed Workflow Details Report.

Server Name No Name of the Informatica Server that runs the workflow.

Status No Indicates whether the workflow succeeded or failed.

User Name No Username that ran the workflow.

Start Time No Time the workflow started.

End Time No Time the workflow ended.

Error Code No Code of the error message generated by the Informatica Server.

Error Message No Text of the error message.

Log File Path and log file name.

Run type Run options configured. For example, Run on Demand indicates that the workflow must be manually started.

Job Report 65

Lookup Table Dependency Report

With a Lookup transformation, you can access data from relational tables and retrieve values based on specified conditions. The Lookup Table Dependency Report provides information on the lookup tables in the repository and the instances of Lookup transformations that use the tables. The report separates lookup transformations that are used in mappings and lookup transformations that are used in mapplets.

Run the Lookup Table Dependency Report by clicking the Lookup Table Dependency Report icon on the Metadata Reporter Control Frame.

Figure 6-6 shows a sample of a Lookup Table Dependency Report. In this folder, there are no lookups in mapplets:

Figure 6-6. Sample Lookup Table Dependency Report


ParametersTable 6-8 shows the parameters you can set to customize a Lookup Table Dependency Report:

You can use wildcards to set parameters. If you do not set any parameter, the Metadata Reporter generates a report on all lookup transformation instances in the selected repository. For more information on setting the report parameters, see “Customizing a Report” on page 45.

Report DetailsTable 6-9 lists the information that the Lookup Table Dependency Report displays. The Lookup Table Dependency Report lists the lookups used in mappings first, then the lookups in mapplets.

Table 6-9 lists the information that the Lookup Table Dependency Report displays.

Table 6-8. Lookup Table Dependency Report Parameters


Repository Select the repository that stores the Lookup transformation instance.

Folder Name Select the folder that stores the Lookup transformation instance.

Version Name Select the version of the Lookup transformation instance.

Lookup Name Select the Lookup transformation instance to include in the report.

Table 6-9. Lookup Table Dependency Report Information


Mapping Lookups Lookup Table Name No Lookup table name.

Mapping Name Yes Mapping where lookup transformation is found. Links to a Mapping Report.

Lookup Instance Name Yes Transformation instance that uses the lookup table. Links to a Transformation Instance Report. For details on the Transformation Instance Report, see �Transformation Report� on page 98.

Mapplet Lookups Lookup Table Name No Lookup table name.

Mapplet Name Yes Mapplet where lookup transformation is found. Links to a Mapplet Transformation Report.

Lookup Instance Name Yes Transformation instance that uses the lookup table. Links to a Transformation Instance Report. For details on the Transformation Instance Report, see �Transformation Report� on page 98.

Lookup Table Dependency Report 67

Mapping Report

A mapping represents the flow of data between source and target. It consists of the sources, targets, and the transformation objects that provide instructions to the Informatica Server on how to transform data.

The Mapping Report lists the mappings that exist in the repository and describes each object in the mapping. For each mapping, the report provides information on the following objects and connections:

♦ Sources

♦ Transformations

♦ Targets

♦ Layout

♦ Object-level connections

♦ Port-level connections

♦ Unconnected ports

When you run the Mapping Report, the Metadata Reporter displays a list of all the mappings in the repository that match the parameters you set. The list includes shortcuts to mappings. The mapping name refers to a shortcut if the Is Shortcut column is checked.

Run the Mapping Report by clicking the Mapping Report icon on the Metadata Reporter Control Frame.


Figure 6-7 shows the first section of the Mapping Report, listing the mappings that match the parameters:

Click the name of a mapping or shortcut to display the Mapping Report. If you click a shortcut name, the Metadata Reporter displays a Mapping Report on the associated mapping.

The Mapping Report contains a list of the types of objects and connections found in the report. Each object or connection type links to a list of objects or connections found in the mapping. If an object has an associated report, you can click the object name to display a report on that object.

For example, when you click the object type Source, the link takes you to the Mapping Sources area of the report where all the sources found in the mapping are listed. In the Mapping Sources area, you can click a source name to display the Source Schema Report for that source.

Figure 6-7. Sample Mapping List

Mapping Report 69

For port-level connections, the Mapping Report displays the name of the object containing the ports and then lists all the ports and connections for the object.

Figure 6-8 shows how you can click an object type to view a list of objects or an object name to view a report for an object:

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

Object type links to a list of all objects of that type found in the mapping.

Object name links to a report on the object.


ParametersTable 6-10 shows the parameters you can set to customize a Mapping Report:

You can use wildcards to set parameters. If you do not set any parameter, the Metadata Reporter generates a report on all mappings in the selected repository. For more information on setting the report parameters, see “Customizing a Report” on page 45.

Report DetailsTable 6-11 lists the information that the Mapping Report displays:

Table 6-10. Mapping Report Parameters


Repository Select the repository that stores the mapping.

Folder Name Select the folder that stores the mapping.

Version Name Select the version of the mapping.

Mapping Name Select the mapping to include in the report.

Table 6-11. Mapping Report Information


Mapping Is Valid No Indicates whether the mapping is valid. If the mapping is not valid, the Informatica Server cannot run any sessions using the mapping.

Last Saved No Date and time the mapping was last saved.

Comments No Comments associated with the mapping.

Mapping Sources Source Name Yes Name of a source found in the mapping. Links to a Source Schema Report.

Business Name No Source business name.

Database Name No Source database.

Database Type No Type of the source database.

Last Saved No Date and time the source was last saved.

Comments No Comments associated with the source.

Mapping Transformations Name Yes Name of a transformation found in the mapping. Links to a Transformation Report.

Type No Type of the transformation.

Last Saved No Date and time the transformation was last saved.

Comments No Comments associated with the transformation.

Mapping Report 71

Mapping Layout DiagramThe mapping report provides a way to display a diagram of the mapping within the report. Before generating the report, you create a diagram of the mapping in Graphics Interchange Format (*.gif ) and put it in the Metadata Reporter document directory in the web server. When you generate the Mapping report, the diagram automatically displays.

Mapping Targets Target Name Yes Name of a target found in the mapping. Links to a Target Schema Report.

Business Name No Target business name.

Last Saved No Date and time the target was last saved.

Comments No Comments associated with the target.

Mapping Layout Mapping Layout Diagram

No Graphic file associated with the mapping found in the web server Metadata Reported document directory of the web server. Blank if no graphic file can be found for the mapping. For details on the layout graphic file (.gif), see �Mapping Layout Diagram� on page 72.

Mapping Object-Level Connections

Connected From Yes Object that has output ports connected to the object shown in the Connected To column. Links to reports such as Source Schema Report or Transformation Report.

Connected To Yes Object that has input ports connected from the object shown in the Connected From column. Links to reports such as Target Schema Report or Transformation Report.

Mapping Port-Level Connections

Connected From Yes Output or input/output port connected to the port shown in the Connected To column. The name of the object that contains the ports displays before the list of ports and links to reports such as Source Schema Report or Transformation Report.

Connected To Yes Input or input/output port connected from the port shown in the Connected From column. The name of the object that contains the ports displays before the list of ports and links to reports such as Target Schema Report or Transformation Report.

Unconnected Ports ObjectName.PortName Yes The object name refers to an object that contains unconnected ports. The port name refers to a port in the object that is not connected to a port in any other object. The object name links to reports such as Mapplet Report or Transformation Report.

Table 6-11. Mapping Report Information



DirectoryThe Metadata Reporter searches for the graphic file in the Metadata Reporter document directory of the web server where the Metadata Reporter is installed. This is the same document directory that you set in the Locations section when you configure the Metadata Reporter. For more information on the document directory, see “Configuring the Metadata Reporter” on page 35.

FormatThe Metadata Reporter displays only graphic files in the GIF (*.gif ) format.

File NameThe graphic file name follows a strict format so that the Metadata Reporter can associate the graphic file with the right mapping. The file name must include the repository, folder, version, and name of the mapping, separated by underscores (_).

The Metadata Reporter can display a graphic file that uses the following file name format:

RepositoryName_FolderName_VersionName_MappingName.gif

Table 6-12 explains the elements of the graphic file name:

If the Metadata Reporter finds a graphic file that matches the repository, folder, version, and mapping name of the current mapping, it automatically displays it on the report.

Note: The Metadata Reporter uses a URL to access the graphic file. As a rule, URLs accept only US-ASCII characters. Since the graphic file name becomes part of the URL for accessing the layout diagram, the graphic file name must be in US-ASCII characters so that it can be part of a valid URL. For example, if the mapping name for the graphic file is not in US-ASCII, the Metadata Reporter cannot create a valid URL to access the graphic file and cannot display the layout diagram the report.

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

File Name Element Description

RepositoryName The repository that stores the mapping.

FolderName The folder that stores the mapping.

VersionName The version of the mapping.

MappingName The mapping name.

.gif The extension for the file.

Mapping Report 73

Figure 6-9 shows a Mapping report that displays a layout diagram and the format that the graphic file name must use:

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

Repository Name

Name of the Layout Diagram File: Production_XMLTutorial_010000_CalcDeptSalary.gif


Mapplet Report

A mapplet is a reusable object that represents a set of transformations. The Mapplet Report lists the mapplets in the repository and displays the properties and ports for each mapplet.

When you run the Mapplet Report, the Metadata Reporter displays a list of all the mapplets in the repository that match the parameters you set. Click a mapplet name to generate a Mapplet Report.

Run the Mapplet Report by clicking the Mapplet Report icon on the Metadata Reporter Control Frame.

Mapplet Report 75

Figure 6-10 shows the first section of the Mapplet Report, listing the mapplets that match the parameters:

Click the name of a mapplet to display the Mapplet Report. The Mapplet Report provides information in two sections: Properties and Ports. Each section name links to the area in the Mapplet report where it is described.

Figure 6-10. Sample Mapplet List


Figure 6-11 shows the property and port descriptions in a Mapplet Report:

ParametersTable 6-13 shows the parameters you can set to customize a Mapplet Report:

Figure 6-11. Sample Mapplet Report

Table 6-13. Mapplet Report Parameters


Repository Select the repository that stores the mapplet.

Folder Name Select the folder that stores the mapplet.

Version Name Select the version of the mapplet.

Mapplet Name Select the mapplet to include in the report.

Mapplet Report 77

You can use wildcards to set parameters. If you do not set any parameter, the Metadata Reporter generates a report on all mapplets in the selected repository. For more information on setting the report parameters, see “Customizing a Report” on page 45.

Report DetailsTable 6-14 lists the information that the Mapplet Report displays:

Table 6-14. Mapplet Report Information


Mapplet Is Valid No Indicates whether the mapplet is valid.

Type No Type of transformation.

Reusable No Indicates whether the mapplet is reusable or not.

Last Saved No Date and time the mapplet was last saved.

Comments No Comments associated with the mapplet.

Properties Mapplet Attribute No Mapplet attributes. For details on each mapplet attribute, see �Mapplets� in the Designer Guide.

Value No Attribute value.

Ports Port Name No Port name.

Datatype No Datatype of the port.

(P,S) No Precision and scale.

Port Type No Type of port:I = InputO = Output

Default Value Yes Default value assigned to the port.

Comments No Comments associated with the mapplet.


Object to Mapping/Mapplet Dependency Report

The Object to Mapping/Mapplet Dependency Report lists objects in the repository and the mappings or mapplets where they are found.

Run the Object to Mapping/Mapplet Dependency Report by clicking the Object to Mapping/Mapplet Dependency Report icon on the Metadata Reporter Control Frame.

Figure 6-12 shows an Object to Mapping/Mapplet Dependency Report that lists the objects in the repository that begin with the letter “C”, and the mappings and mapplets that contain them. Several different mappings and a mapplet use the source definition Customers.

Figure 6-12 shows a Object to Mapping/Mapplet Dependency Report:

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

Object to Mapping/Mapplet Dependency Report 79

ParametersTable 6-15 shows the parameters you can set to customize an Object To Mapping/Mapplet Dependency Report:

You can use wildcards to set parameters. If you do not set any parameters, the Metadata Reporter generates a report on all objects in the selected repository. Since there are usually a large number of objects in a repository, it might take the Metadata Reporter some time to generate the report. You might want to make sure that you narrow the scope of the report by setting parameters.

For more information on setting the report parameters, see “Customizing a Report” on page 45.

Report DetailsTable 6-16 lists the information that the Object to Mapping/Mapplet Dependency Report displays:

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


Repository Select the repository that stores the object.

Folder Name Select the folder that stores the object.

Version Name Select the version of the object.

Object Name Select the object to include in the report.

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


Mapping Objects Mapping Name Yes Name of the mapping that contains the object. Links to a Mapping Report.

Object Name Yes Name of the repository object in the mapping. Links to reports on repository objects such as Source or Target Schema Report, or Transformation Report.

Object Type No Type of repository object, such as Source Definition or Aggregator Transformation.

Mapplet Objects Mapplet Name Yes Name of the mapplet that contains the object. Links to a Mapplet Report.

Object Name Yes Name of the repository object in the mapplet. Links to reports on repository objects such as Source or Target Schema Report, or Transformation Report.

Object Type No Type of repository object, such as Source Definition or Aggregator Transformation.


Session List Report

The Session List Report displays the sessions available in the selected repository. A session provides the Informatica Server with a set of instructions on how and when to move data from sources to targets. To run the Session List Report, click the Sessions Report icon on the Metadata Reporter control frame. Click a session to display the detailed report discussed in “Session Details Report” on page 83.

Figure 6-13 shows a sample Session List Report:

Figure 6-13. Sample Session List Report

Session List Report 81

ParametersTable 6-17 shows the parameters you can set to customize a Session List Report:

You may want to narrow the scope of the report by setting parameters. You may also use wildcards to add flexibility to the parameters you set. If you do not set any parameters, the Metadata Reporter generates a report on all sessions in the selected repository. Since there are usually a large number of objects in a repository, it might take the Metadata Reporter some time to generate the report.

For more information on setting the report parameters, see “Customizing a Report” on page 45.

Report DetailsTable 6-18 lists the information that the Sessions List Report displays:

Table 6-17. Session List Report Parameters


Repository Select the repository that stores the session.

Folder Name Select the folder that stores the session.

Session Name Select the session.

Table 6-18. Session s List Report Information


Session Session Name Yes Name of the session. Links to the Session Details Report.

Is Valid No Indicates whether the session is valid. Changes to a mapping can invalidate the session. The Informatica Server cannot run an invalid session.

Last Saved No Date and time the session was last saved.

Mapping Name No Name of the mapping used in the session.

Mapping Version No Version of the mapping used in the session.

Comments No Comments associated with the session.


Session Details Report

The Session Details Report provides information about how a selected session ran. The Session Details Report contains the following sections:

♦ Session. Provides information such as session validity and the location of the log files associated with the session.

♦ Readers. Reports how information is read from a source. This includes the name of the instance, the reader type, and the name of the source connection created in the Workflow Manager.

♦ Writers. Reports how data is written to the target, including the session writer type and the name of the target connection created in the Workflow Manager.

♦ Components. Provides information about session components such as pre- and post-session commands.

♦ Partitions. Displays details about each transformation instance within a particular partition. For more information about pipeline partitions, see “Pipeline Partitioning” in the Workflow Administration Guide.

♦ Configuration Parameters. Provides information about parameters for the session. The report displays a list of the attributes and the values associated with those attributes. For details on configuring parameters, see “Session Parameters” in the Workflow Administration Guide.

To run the Session Details Report, click the Session Report icon on the Metadata Reporter control frame, and then click the session name.

Session Details Report 83

Figure 6-14 shows a sample Session Details Report:

Report DetailsTable 6-19 lists the information that the Sessions Detail Report displays:

Figure 6-14. Sample Session Details Report

Table 6-19. Sessions Detail Report Information


Session Is Valid No Indicates whether the session is valid. Changes to a mapping can invalidate the session. The Informatica Server cannot run an invalid session.

Is Reusable No Indicates whether the session is reusable.

Mapping name No Name of the mapping used in the session.


Mapping version No Version of the mapping used in the session.

Log File Name No Name and path of the log file.

Last Saved No Date and time the session was last saved.

Comments No Comments associated with the session.

Readers Yes Links to Readers section.

Writers Yes Links to Writers section.

Components Yes Links to Components section.

Partitions Yes Links to Partitions section.

Configuration Parameters

Yes Links to Configuration Parameters section.

Readers Instance Name No Name of the source qualifier instance.

Reader type No Source reader type: file, relational, or heterogeneous.

Connection No The name of the connection to the source created in the Workflow Manager.

Writer Instance Name No Name of the target instance.

Writer Type No Target writer type: file or relational.

Connection No The name of the connection to the target created in Workflow Manager.

Components Component Name No Name of components included in the workflow. These include the following: - pre-session commands- post-session commands- post-session failure commands- post-session success command- on success email- on failure email

Type No Component type: reusable, non-reusable, or none.

Partitions Instance Name No Displays details about each transformation instance within the partition. The partition name is the number assigned to the partition. For more information about pipeline partitions, see �Pipeline Partitioning� in the Workflow Administration Guide.

Instance Type No The type of instance.

Partition Count No The total number of partitions in the transformation instance.



Session Details Report 85

Configuration Parameters

Attribute No The name of the attribute. You can specify a parameter file for a session in a session properties. For details on configuring parameters, see �Session Parameters� in the Designer Guide.

Value No The value associated with the attribute.




Shortcut Report

Shortcuts allow you to use metadata across folders without making copies. You can have shortcuts to different types of objects in the repository. The Metadata Reporter lists shortcuts to four types of objects in the Shortcut Report:

♦ Source

♦ Target

♦ Transformation

♦ Mapping

You can select the type of shortcut to display. If you do not select the shortcut type, the Metadata Reporter displays shortcuts to sources by default. The Shortcut Report lists all the shortcuts in the repository that point to the objects that you select in the parameter.

Run the Shortcut Report by clicking its icon on the Metadata Reporter Control Frame.

Shortcut Report 87

Figure 6-15 shows a Shortcut Report for all sources in the repository:

ParametersTable 6-20 shows the parameters you can set to customize a Shortcut Report:

Figure 6-15. Sample Shortcut Report

Table 6-20. Shortcut Report Parameters


Repository Select the repository that stores the object that the shortcut points to.

Folder Name Select the folder that stores the object that the shortcut points to.

Version Name Select the version of the object that the shortcut points to.

Object Type Select the type of object the shortcut points to.

Object Name Select the object the shortcut points to.


You can use wildcards to set parameters. If you do not set any parameter, the Metadata Reporter generates a report that lists all shortcuts for all objects in the selected repository. For more information on setting the report parameters, see “Customizing a Report” on page 45.

Report DetailsTable 6-21 lists the information that the Shortcut Report displays:

Table 6-21. Shortcut Report Information


Shortcut Name Yes Name of the shortcut that points to the selected objects or to objects in the selected location. Links to a Mapping Report, Source Schema Report, Target Schema Report, or Transformation Report.

Shortcut Report 89

Source Schema Report

Source definitions describe the sources that provide data to the data warehouse. The Source Schema Report lists the source definitions in the repository and describes the schema for each source.

Run the Source Schema Report by clicking the Source Schema Report icon on the Metadata Reporter Control Frame.

Figure 6-16 shows the Source Schema Report with information about the source and details about the source columns:

Figure 6-16. Sample Source Schema Report


ParametersTable 6-22 shows the parameters you can set to customize a Source Schema Report:

If you select a field name as a parameter, the Metadata Reporter includes the source schema that contains the field name you select in the report. The Metadata Reporter displays all the columns of the source schema.

You can use wildcards to set parameters. If you do not set any parameter, the Metadata Reporter generates a report on all sources in the selected repository. For more information on setting the report parameters, see “Customizing a Report” on page 45.

Table 6-22. Source Schema Report Parameters


Repository Select the repository that stores the source.

Folder Name Select the folder that stores the source.

Version Name Select the version of the source.

Source Name Select the source to include in the report.

Field Name Select a field name of a table to include in the report.

Source Schema Report 91

Report DetailsTable 6-23 lists the information that the Source Schema Report displays:

Note: If the Source Schema Report includes a shortcut to another source, the shortcut name links to a Source Schema Report for the original source.

Table 6-23. Source Schema Report Information


Description No Description of the source.

Database Name No Source Database.

Business Name No Business name of the source.

Database Type No Type of the source database.

Column Name No Port name.

Business Name No Business name of the port.

DataType No Datatype.


Key Type No Key type: primary, foreign, or not a key.

Not Null No Indicates whether the port permits null values.

Description No Description of the port.


Source to Target Dependency Report

The Source to Target Dependency Report shows the data flow from the source to the target. The report lists all the source and target ports, the mappings in which the ports are connected, and the transformation expressions that show how data for the target ports is derived. The Metadata Reporter displays the report by source and source ports.

Run the Source to Target Dependency Report by clicking the Source to Target Dependency Report icon on the Metadata Reporter Control Frame.

Figure 6-17 shows a Source to Target Dependency Report:

Figure 6-17. Sample Source to Target Dependency Report

Source to Target Dependency Report 93

ParametersTable 6-24 shows the parameters you can set to customize a Source to Target Dependency Report:

You can use wildcards to set parameters. If you do not set any parameter, the Metadata Reporter generates a report on all sources and targets in the selected repository. For more information on setting the report parameters, see “Customizing a Report” on page 45.

Report DetailsTable 6-25 lists the information that the Source to Target Dependency Report displays:

Note: The name of each source included in the report links to a Source Schema Report.

Table 6-24. Source to Target Dependency Report Parameters


Repository Select the repository that stores the source and target.

Folder Name Select the folder that stores the source and target.

Version Name Select the version of the source and target.

Source Name Select the source to include in the report.

Target Name Select the target that connects to the source.

Table 6-25. Source to Target Dependency Report Information


Business Name No Business name of the source.

Source Field No Name of the source port that connects to the target port.

Source Field Business Name No Business name of the source port that connects to the target port.

Target Table Yes Name of the target table the source port connects to. Links to a Target Schema Report.

Target Table Business Name No Business name of the target table the source port connects to.

Target Field No Name of the target port that the source port connects to.

Target Field Business Name No Business name of the source port that connects to the target port.

Mapping Yes Name of the mapping where the source and target are found. Links to a Mapping Report.

Transformation Expression No Represents the instructions the Informatica Server follows to transform data. Expression displays only if you save the mapping with the Designer option Save MX Data enabled. For details on the Save MX Data option, see �Using the Designer� in the Designer Guide.


Target Schema Report

Target definitions describe the tables that store the data that passes through a mapping. The Target Schema Report lists the target definitions in the repository and describes the schema for each target.

Run the Target Schema Report by clicking the Target Schema Report icon on the Metadata Reporter Control Frame.

Target Schema Report 95

Figure 6-18 shows the Target Schema Report with information about the target and details about the target columns:

Figure 6-18. Sample Target Schema Report


ParametersTable 6-26 shows the parameters you can set to customize a Target Schema Report:

If you select a field name as a parameter, the Metadata Reporter includes the target schema that contains the field name you select in the report. The Metadata Reporter displays all the columns of the target schema.

You can use wildcards to set parameters. If you do not set any parameter, the Metadata Reporter generates a report on all targets in the selected repository. For more information on setting the report parameters, see “Customizing a Report” on page 45.

Report DetailsTable 6-27 lists the information that the Target Schema Report displays:

Note: If the Target Schema Report includes a shortcut to another target, the shortcut name links to a Target Schema Report for the original target.

Table 6-26. Target Schema Report Parameters


Repository Select the repository that stores the target.

Folder Name Select the folder that stores the target.

Version Name Select the version of the target.

Target Name Select the target to include in the report.

Field Name Select a field name of a target to include in the report.

Table 6-27. Target Schema Report Information

Information Description

Business Name Target business name.

Database Type Type of the target database.

Description Description of the target.

Column Name Port name.

Business Name Business name of the target column.

DataType Datatype.

(P,S) Precision and scale.

Key Type Key type: primary, foreign, or not a key.

Not Null Indicates whether the port permits null values.

Description Description of the port.

Target Schema Report 97

Transformation Report

Transformations are objects in the repository that generate or modify data. Each type of transformation has a different set of properties and transforms data in a different way. The Transformation Report lists reusable transformations in the repository, which you create in the Transformation Developer. The report displays the properties and ports for each transformation.

The Metadata Reporter provides reports on the following transformations:

♦ Advanced External Procedure

♦ Aggregator

♦ Expression

♦ External Procedure

♦ Filter

♦ Joiner

♦ Lookup

♦ Normalizer

♦ Rank

♦ Router

♦ Sequence Generator

♦ Sorter

♦ Stored Procedure

♦ Update Strategy

Run the Transformation Report by clicking the Transformation Report icon on the Metadata Reporter Control Frame.


Figure 6-19 shows the first section of the Transformation Report, listing the transformations that match parameters:

When you run the Transformation Report, the Metadata Reporter displays a list of transformations that match the parameters you set. Click the name of a transformation to display the Transformation Report.

The Transformation Report provides information in two sections: Properties and Ports. Each section name is a link to the area in the report where it is described.

Figure 6-19. Sample Transformation List

Transformation Report 99

Figure 6-20 shows the property and port descriptions for a Sequence Generator Transformation Report:

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


ParametersTable 6-28 shows the parameters you can set to customize a Transformation Report:

You can use wildcards to set parameters. If you do not set any parameter, the Metadata Reporter generates a report on all reusable transformations in the selected repository. For more information on setting the report parameters, see “Customizing a Report” on page 45.

Report DetailsTable 6-29 lists the information that the Transformation Report displays:

Table 6-28. Transformation Report Parameters


Repository Select the repository that stores the transformation.

Folder Name Select the folder that stores the transformation.

Version Name Select the version of the transformation.

Transformation Name Select the transformation to include in the report.

Table 6-29. Transformation Report Information


Transformation Type No Type of transformation.

Reusable No Indicates whether the transformation is reusable or not.

Last Saved No Date and time the transformation was last saved.

Comments No Comments associated with the transformation.

Properties Transformation Attribute No Transformation attributes. For details on each transformation attribute, see �Transformations� in the Designer Guide.

Value No Attribute value.

Ports Port Name No Port name.

Datatype No Datatype of the port.


Port Type No Type of ports available in the transformation. The ports can include one or more of the following types:I = InputL = LookupM = Master/DetailO = OutputP = Parameter OutputR = ReturnV = Variable

Transformation Report 101

Expression No Represents the instructions the Informatica Server follows to transform data. Expression displays only for transformations that use expressions such as Expression, Filter, or Router transformations and only if you save the mapping with the Designer option Save MX Data enabled. For details on the Save MX Data option, see �Using the Designer� the Designer Guide.

Group By No The column by which to group an aggregation. Displays only for the Aggregator transformation.

Default Value No Default value assigned to the port.

Comments No Comments associated with the port.

Table 6-29. Transformation Report Information



Workflow List Report

In the Workflow Manager, you define a workflow that describes how and when to run tasks related to extracting, transforming, and loading data. The Workflow List Report shows the workflows in the repository, which you create in the Workflow Manager. Each workflow listed links to a detailed report, discussed in “Workflow Details Report” on page 105.

To run the Workflow List Report, click the Workflows Report icon on the Metadata Reporter control frame.

Figure 6-21 shows a sample Workflow List Report:

Figure 6-21. Sample Workflow List Report

Workflow List Report 103

ParametersTable 6-30 shows the parameters you can set to customize a Workflow List Report:

You can use wildcards to set parameters. If you do not set any parameter, the Metadata Reporter generates a report on all workflows in the selected repository. For more information on setting the report parameters, see “Customizing a Report” on page 45.

Report DetailsTable 6-31 lists the information that the Workflows List Report displays:

Table 6-30. Workflow List Report Parameters


Repository Select the repository that stores the workflow.

Folder Name Select the folder that stores the workflow.

Workflow Name Select the name of the workflow.

Table 6-31. Workflow List Report Information


Workflow List Workflow Name Yes Name of the workflow. Links to the Workflow Details Report.

Is Valid No Indicates whether the workflow is valid.

Last Saved No Date and time the workflow was last saved.

Server Name No Name of Informatica Server specified to run the workflow.

Scheduler Name No Name of the scheduler.

Comments No Comments associated with the workflow.


Workflow Details Report

The Workflow Details Report lists the tasks in a selected workflow, and provides detailed information about how the workflow is configured. The Workflow Details Report contains the following sections:

♦ Workflow. Provides information about the workflow, such as whether or not the workflow is valid and the Informatica Server specified to run the workflow.

♦ Scheduler summary. Provides information such as start time, end time, and run options.

♦ Variables. Provides the names of variables included in the workflow and comments associated with the variables.

♦ Events. Provides information about Event-Raise and Event-Wait tasks.

♦ Instances. Provides information on each instance in the workflow such as task type and name.

♦ Object level connections. Provides information about object level connections, including conditions that must be met in order for the workflow to continue running.

To run the Workflow Details Report, click the Workflows Report icon on the Metadata Reporter control frame and click the workflow name.

Workflow Details Report 105

Figure 6-22 shows a sample Workflow Details Report.

Report DetailsTable 6-32 lists the information that the Workflow Details Report displays:

Figure 6-22. Sample Workflow Details Report

Table 6-32. Workflow Details Report Information


Workflow Is Valid No Indicates whether the workflow is valid.

Is Enabled No Indicates whether the workflow is enabled.

Server No Name of the Informatica Server specified to run the workflow.

Suspension Email No Whether suspension email is enabled. Enabling suspension email instructs the Informatica Server to send email when it suspends the workflow.

Last Saved No Date and time the workflow was last saved.



Scheduler Summary Yes Links to the Scheduler Summary section.

Variables Yes Links to the Variables section.

Events Yes Links to the Events section.

Instances Yes Links to the Instances section.

Object Level Connections

Yes Links to the Object Level Connections section.

Scheduler Summary

Scheduler Name No Name of the scheduler.

Is Reusable No Whether schedule is reusable.

Start Time No Start time of the scheduled workflow.

End Time No End time of the scheduled workflow.

Run Options No Run options. For example, Run on Demand indicates that the workflow must be manually started.

End Options No Options set for ending the workflow. Can include conditions such as completing a number of cycles or completing a particular task.


Variable Variable Name No Variables associated with the workflow.

Comments No Comments associated with the variable.

Events Event Name No Name of the Event.

Description No Type of event in the workflow. There are two types of events you can configure in a workflow: Event-Raise tasks and Event-Wait tasks.

Instances Instance Name No Name of the instance.

Task Type No Task type of the instance.

Is Enabled No Indicates whether the instance is enabled.

Comments No Comments associated with the instance.


From Instance Name No Each task within a workflow.

To Instance Name No The task that follows the task listed in the From Instance Name section.

Condition No Conditions that must be met in order for the workflow to continue running.

Table 6-32. Workflow Details Report Information


Workflow Details Report 107

Worklet List Report

A worklet is an object created with the Worklet Designer that represents a set of tasks. It can contain any task available in the Workflow Manager. You can nest worklets inside a workflow or inside another worklet. Generally, you create a worklet when you want to reuse a set of workflow logic in several workflows. The Worklets List Report shows the worklets in the selected repository. Each worklet listed links to a detailed report discussed in “Worklet Details Report” on page 110.

To run the Worklet List Report, click the Worklets Report icon on the Metadata Reporter control frame.

Figure 6-23 shows a sample Worklet List Report:

Figure 6-23. Sample Worklet List Report


ParametersTable 6-33 shows the parameters you can set to customize a Worklet List Report:

You can use wildcards to set parameters. If you do not set any parameter, the Metadata Reporter generates a report on all worklets in the selected repository. For more information on setting report parameters, see “Customizing a Report” on page 45.

Report DetailsTable 6-34 lists the information that the Worklet List Report displays:

Table 6-33. Worklet List Report Parameters


Repository Select the repository that stores the worklet.

Folder Name Select the folder that stores the worklet.

Worklet Name Select the name of the worklet.

Table 6-34. Worklet List Report Information


Worklet List Worklet Name Yes Name of the worklet. Links to the Detailed Worklets Report.

Is Valid No Indicates whether the worklet is valid.

Last Saved No Date and time the worklet was last saved.

Comments No Comments associated with the worklet.

Worklet List Report 109

Worklet Details Report

The Worklet Details Report lists the tasks in a selected worklet and the order the objects are to be run. The Worklet Details Report contains the following sections:

♦ Worklet. Provides information about the worklet, such as whether or not the worklet is valid or reusable, and when the worklet was last saved.

♦ Variables. Provides the name of variables included in the worklet and comments associated with the variables.

♦ Events. Provides information about Event-Raise and Event-Wait tasks in the worklet.

♦ Instances. Provides information about each instance in the workflow, such as task type and name.

♦ Object level connections. Provides information about object level connections in the workflow, including any conditions that must be met for the worklet to continue running.

To run the Worklet Details Report, click the Worklets Report icon on the Metadata Reporter control frame and click the worklet.

Figure 6-24 shows a Sample Worklet Details Report:

Figure 6-24. Sample Worklet Details Report


Report DetailsTable 6-35 lists the information that the Worklets Detail Report displays:

Table 6-35. Worklet Details Report Information


Worklet Is Valid No Indicates whether the worklet is valid.

Is Reusable No Indicates whether the worklet is reusable.

Last Saved No Date and Time the worklet was last saved.

Comments No Comments associated with the worklet.

Variables Yes Links to the Variables section.

Events Yes Links to the Events section.

Instances Yes Links to the Instances section.


Yes Name of the object level connection. Links to the Object Level Connections section.

Variables Variable Name No Variables associated with the worklet.

Comments No Comments associated with the variable.

Events Event Name No Name of Event.

Description No The type of event in the worklet. There are two types of events which you may configure in a worklet: Event-Raise tasks and Event-wait tasks.

Instances Instance Name Yes Name of the instance. Links to the Sessions List report.

Task Type No Task type of the instance.

Is Enabled No Indicates whether the instance is enabled.

Comments No Comments associated with the instance.


From Instance Name No The task instance.

To Instance Name No The task instance that follows the task listed in From Instance Task.

Condition No Conditions that must be met in order for the worklet to continue running.

Worklet Details Report 111


A p p e n d i x A

Error Messages

This appendix includes the following topics:

♦ Overview, 114

♦ Metadata Reporter Error Messages, 115

♦ Metadata Reporter Setup Error Messages, 116

113

Overview

This chapter lists the messages that the Metadata Reporter and the Metadata Reporter Setup might display when they encounter errors. Use this chapter to determine what causes the error messages to appear and how you can correct the problem.

After each error message is an explanation of the possible cause for the error and a recommended action. Before taking action, make sure to read all possible causes listed under the error message to identify the most likely source of your error.

If you follow the suggested instructions but the problem persists, please contact Informatica Technical Support for additional help.

114 Appendix A: Error Messages

Metadata Reporter Error Messages

The following messages might appear when you run the Metadata Reporter:

Fatal error during initialization. Please correct the servlet engine and try again.

Cause: The Metadata Reporter cannot start. The web server or the servlet engine may not be running, or you have not configured the Metadata Reporter.

Action: Make sure that the web server is running. Also make sure that you have configured the Metadata Reporter before you start using it by running the Metadata Reporter Setup.

Unknown repository:<repository name>. Please add that repository through XMXConfigServlet and restart the servlet engine

Cause: The Metadata Reporter does not recognize the repository name selected for the report.

Action: Run the Metadata Reporter Setup and set up the repository correctly to enable the Metadata Reporter to access it.

Report doesn't have an associated SQL query in the catalog.

Cause: The Metadata Reporter catalog of reports may be corrupted.

Action: Reinstall the Metadata Reporter.

Query execution failed. Please check to ensure that the database server version is supported and that the database server has sufficient resources to run this query.

Cause: You might be running a report that returns a large number of rows and the Metadata Reporter has lost connection to the repository.

Action: Make sure that your database server is functioning correctly. Restart the Metadata Reporter and run the report.

JDBC report metadata doesn't match that in the XMXCatalog. Report Column <column name> missing.

Cause: The Metadata Reporter catalog of reports may be corrupted.

Action: Reinstall the Metadata Reporter.

Metadata Reporter Error Messages 115

Metadata Reporter Setup Error Messages

The following messages might appear on the message frame of the Metadata Reporter Setup:

It is okay to get errors if you are not using the drivers that generated errors.

Cause: Informational message. When you run the Metadata Reporter Setup, it attempts to load several JDBC drivers. If it cannot find a driver, it returns an error message.

Action: If you do not use the database driver that generated the error, you do not need to do anything. If you use the database driver that generated the error, make sure that the JDBC driver is available in the database driver directory. Then test and save the Metadata Reporter Setup settings.

License query execution generated exception(s). (Only relevant if you are using Merant closed ODBC driver)

Cause: Merant Closed ODBC drivers might generate some license errors if you have old versions installed.

Action: Check the license file for your Merant ODBC drivers. If you have the license files named lvodbc.lic and lvdw.lic, either rename them or move them to another directory. Make sure that you only have one license file named ivdw.lic. You can find the license file in the c:\winnt\system32 directory. The ivdw.lic file is automatically installed when you install the Merant ODBC drivers. If you do not have the ivdw.lic license file, reinstall the Merant ODBC drivers from the PowerCenter and PowerMart CD.

116 Appendix A: Error Messages

I n d e x

Aaccessing

Metadata Reporter, 44reports, 44

BBrowse button, 45browsers

See web browsersbuttons

Browse, 45Print Preview, 48Print View, 50Report, 47

Ccode pages

See also Installation and Configuration GuideMetadata Reporter, 2

column descriptionCompleted Workflow Details, 59Completed Worklet Details Report, 61Invalid Mappings Report, 63Job Report, 65

Lookup Table Dependency Report, 67Mapping Report, 71Mapplet Report, 78Object to Mapping Dependency Report, 80Session Details Report, 84Session List Report, 82Sessions Report, 56Shortcut Report, 89Source Schema Report, 92Source to Target Dependency Report, 94Target Schema Report, 97Transformation Report, 101Workflow Details Report, 106Workflow List Report, 104Worklet Details Report, 111Worklet List Report, 109

Completed Session Details Reportcolumns, 56description, 55report details, 56

Completed Workflow Detailscolumns, 59report details, 59

Completed Workflow Details Reportdescription, 58

Completed Worklet Details Reportcolumns, 61description, 60report details, 61

117

Content Framedescription, 5printing reports, 50

Control Framedescription, 5

customizing reports, 45

Ddatabase connectivity

connecting to the repository, 4database drivers

DB2JDBC, 38Informix JDBC, 38JDBC, 4, 7JDBC/ODBC bridge, 38Metadata Reporter framework, 3ODBC, 4, 7Oracle JDBC Thin Driver, 38Sybase JDBC (jConnect), 38

DB2JDBC, 38description

Completed Session Details Report, 55Completed Workflow Details Report, 58Completed Worklet Details Report, 60Content Frame, 5Control Frame, 5Invalid Mappings Report, 62Job Report, 64Lookup Table Dependency Report, 66mapping, 68Mapping Report, 68Mapplet Report, 75Object to Mapping Dependency Report, 79Session Details Report, 83Session List Report, 81Shortcut Report, 87Source Schema Report, 90Source to Target Dependency Report, 93Target Schema Report, 95Transformation Report, 98Workflow Details Report, 105Workflow List Report, 103Worklet Details Report, 110Worklet List Report, 108

displaying reports, 47document directory

Metadata Reporter, 36documentation

conventions, xx

description, xviionline, xix

Eerror messages

Metadata Reporter, 115Metadata Reporter Setup, 116

Fframework

Metadata Reporter, 3

Ggraphic

Mapping Report, 72

IInformatica

documentation, xviiWebzine, xxi

Informix JDBC, 38installing

before you begin (UNIX), 24before you begin (Windows), 12deploying Metadata Reporter (UNIX), 30deploying Metadata Reporter (Windows), 20Metadata Reporter (UNIX), 29Metadata Reporter (Windows), 18overview, 7testing WebLogic install (UNIX), 28testing WebLogic install (Windows), 17WebLogic(UNIX), 25WebLogic(Windows), 13

Invalid Mappings Reportcolumns, 63description, 62parameters, 62report details, 63

JJava Servlet API, 3Java Virtual Machine, 3

118 Index

jconnect, 38JDBC

adding drivers, 38URL, 37using with Metadata Reporter, 4, 7, 34

JDBC/ODBC bridge, 38Job Report

columns, 65description, 64parameters, 65report details, 65

Llayout diagram

Mapping Report, 72Lookup Table Dependency Report


Mmapping

description, 68Mapping Report

columns, 71description, 68layout diagram, 72parameters, 71report details, 71repository objects, 68

Mapplet Reportcolumns, 78description, 75parameters, 77report details, 78

Metadata Reporteraccessing, 44adding repositories, 37benefits, 2configuring, 34configuring WebLogic to work with (UNIX), 27configuring WebLogic to work with (Windows), 16deploying on WebLogic (UNIX), 30deploying on WebLogic (Windows), 20document directory, 36error messages, 115framework, 3

installation overview, 7installing (UNIX), 29installing (Windows), 18installing with WebLogic (UNIX), 25installing with WebLogic (Windows), 13interface, 5overview, 2security, 6setup, 34setup error messages, 116testing configuration, 38URL, 44

Microsoft Internet Explorersupported web browsers, 7

NNetscape

supported web browsers, 7

OObject to Mapping Dependency Report

columns, 80description, 79

Object to Mapping/Mapplet Dependency Reportparameters, 80report details, 80

objectsMapping Report, 68Shortcut Report, 87

ODBCSee also Installation and Configuration Guideusing with Metadata Reporter, 4, 7

Oracle JDBC Thin Driver, 38overview

reports, 54

Pparameters

Invalid Mappings Report, 62Job Report, 65Lookup Table Dependency Report, 67Mapping Report, 71Mapplet Report, 77Object to Mapping/Mapplet Dependency Report, 80Session List Report, 82setting, 47

Index 119

Shortcut Report, 88Source Schema Report, 91Source to Target Dependency Report, 94Target Schema Report, 97Transformation Report, 101Workflow List Report, 104Worklet List Report, 109

percent symbolwildcard support, 45

Print Previewviewing reports, 48

printing reports, 49

Rreport details

Completed Session Details Report, 56Completed Workflow Details, 59Completed Worklet Details Report, 61Invalid Mappings Report, 63Job Report, 65Lookup Table Dependency Report, 67Mapping Report, 71Mapplet Report, 78Object to Mapping/Mapplet Dependency Report, 80Session Details Report, 84Session List Report, 82Shortcut Report, 89Source Schema Report, 92Source to Target Dependency Report, 94Target Schema Report, 97Transformation Report, 101Workflow Details Report, 106Workflow List Report, 104Worklet Details Report, 111Worklet List Report, 109

reportsCompleted Session Details Report, 55Completed Workflow Details Report, 58Completed Worklet Details Report, 60customizing, 45displaying, 47Invalid Mappings Report, 62Job Report, 64list, 54Lookup Table Dependency Report, 66Mapping Report, 68Mapplet Report, 75Object to Mapping Dependency Report, 79overview, 54

printing, 49running, 47selecting, 47Session Details Report, 83Session List Report, 81Shortcut Report, 87Source Schema Report, 90Source to Target Dependency Report, 93Target Schema Report, 95Transformation Report, 98Workflow Details Report, 105Workflow List Report, 103Worklet Details Report, 110Worklet List Report, 108

repositoriesadding, 37

runningreports, 47

SSave MX Data

See also Designer GuideTransformation Expression, 94, 102

securityMetadata Reporter, 6

selecting reports, 47servlet directory

definition, 8Session Details Report

columns, 84description, 83report details, 84

Session List Reportcolumns, 82description, 81parameters, 82report details, 82

setting parameters, 47Shortcut Report

columns, 89description, 87objects, 87parameters, 88report details, 89

Source Schema Reportcolumns, 92description, 90parameters, 91report details, 92

120 Index

Source to Target Dependency Reportcolumns, 94description, 93parameters, 94report details, 94

Sybase JDBC (jConnect), 38

TTarget Schema Report


testingMetadata Reporter configuration, 38Metadata Reporter deployment (UNIX), 30Metadata Reporter deployment (Windows), 20WebLogic Server install (UNIX), 28WebLogic Server install (Windows), 17

Transformation Reportcolumns, 101description, 98parameters, 101report details, 101transformation types, 98

troubleshootingODBC driver problems, 41repository problems, 51

Uunderscore

wildcard support, 45URL

Metadata Reporter, 44Metadata Reporter Setup, 36, 37

Wweb browsers

compatible with Metadata Reporter, 7Microsoft Internet Explorer, 7Netscape, 7support for Metadata Reporter, 3

web serversBEA WebLogic Server 6.1, 8Metadata Reporter framework, 3restarting, 38, 40

servlet directory, 8WebLogic

before you install (UNIX), 24before you install (Windows), 12configuring to work with Metadata Reporter (UNIX),

27configuring to work with Metadata Reporter

(Windows), 16installing with Metadata Reporter (UNIX), 25installing with Metadata Reporter (Windows), 13testing installation (UNIX), 28testing installation (Windows), 17

webzine, xxiwildcards

description, 45Workflow Details Report

columns, 106description, 105report details, 106

Workflow List Reportcolumns, 104description, 103parameters, 104report details, 104

Worklet Details Reportcolumns, 111description, 110report details, 111

Worklet List Reportcolumns, 109description, 108parameters, 109report details, 109

XXMXConfigServlet, 36, 37XMXServlet, 44

Index 121

122 Index

Documents

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